SYSTEM DESCRIPTION

XMC20 R16A
Product Features and Characteristics
XMC20 System Description
Document ID 1KHW028870

Document edition XMC20 System Release: R16A

Revision: A
Date: 2022-10-10

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

XMC20 | SYSTEM DESCRIPTION

Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 XMC20 Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.1 XMC25 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 XMC25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 XMC23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.4 XMC22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.5 XMC20 Packet Based Core. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.6 XMC20 Circuit Based Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.7 XMC20 Protocol Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.8 XMC20 Core and Service Units Overview . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.9 XMC20 Auxiliary Units Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3 XMC20 Traffic Services and Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.1 Traffic Services Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.2 XMC20 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.3 Application Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4 Content Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Architecture and Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1 XMC20 Subracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.2 Mechanical Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.1.3 Internal Traffic Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.1.4 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.2 XMC20 Traffic Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.2.1 Core Unit CENT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.2.2 Core Unit COGE7 and COGE7-F. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.2.3 Core Unit COGE5 and COGE5-F. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.2.4 WAN Port Expansion Unit EXPU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.2.5 Encryption Unit SECU1-4, SECU1F4, SECU1-8 and SECU1F8 . . . . . . . . . . . . 61
2.2.6 Ethernet Service Units ETO12 and ETO12-F. . . . . . . . . . . . . . . . . . . . . . 64
2.2.7 Ethernet Service Unit ETE24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.2.8 Ethernet Service Unit SUP12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.2.9 Ethernet service unit SUSE2 and SUSE2-F . . . . . . . . . . . . . . . . . . . . . . 68
2.2.10 Ethernet Service Units VRX10 and VRX10-F. . . . . . . . . . . . . . . . . . . . . . 70
2.2.11 Ethernet Service Units SABO1 and SABO1-F . . . . . . . . . . . . . . . . . . . . . 71
2.2.12 Ethernet Service Unit SABE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.2.13 Ethernet Service Unit ETAG1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.2.14 SDH and EoS Service Unit STM14 . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
2.2.15 SDH and EoS Service Unit NUSA1 and NUSA1-F . . . . . . . . . . . . . . . . . . . 77
2.2.16 SDH and EoS Service Unit NUSA2. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.2.17 E1 Service Unit SELI8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.2.18 E1 Circuit Emulation Service Unit SATP8 . . . . . . . . . . . . . . . . . . . . . . . 81
2.2.19 TDM SHDSL Service Unit SDSL8 . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.2.20 Media Gateway Unit VOIP1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.2.21 Voice Frequency Processing Unit VFTLX . . . . . . . . . . . . . . . . . . . . . . . 86
2.2.22 PSTN Service Units SUPM1 and SUPM2 . . . . . . . . . . . . . . . . . . . . . . . 87
2.2.23 ISDN-BA Voice Service Unit ISDN4 . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.2.24 Voice Frequency Filter Box FIL16 . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.2.25 E&M Voice Service Unit TUEM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2.2.26 Magneto Line Voice Service Unit IMAG1 . . . . . . . . . . . . . . . . . . . . . . . . 91
2.2.27 FXO Voice Service Unit TUXA1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2.2.28 Data Service Unit TUDA1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.2.29 E0 Service Unit TUGE1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.3 XMC20 Auxiliary Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
2.3.1 Dual Power Input Unit DUA25 (XMC25 R2 and XMC25) . . . . . . . . . . . . . . . . 96
2.3.2 Dual Power Input Unit DUA23 (XMC23 and XMC22). . . . . . . . . . . . . . . . . . 96

Copyright 2022 Hitachi Energy. All rights reserved. 3

XMC20 | SYSTEM DESCRIPTION

2.3.3 Fan Unit COOL4 (XMC25 R2 and XMC25). . . . . . . . . . . . . . . . . . . . . . . 97

2.3.4 Fan Unit COOL6 (XMC23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.3.5 Fan Unit COOL8 (XMC22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2.3.6 Alarm Unit ALMU4-F (XMC25 R2 and XMC25) . . . . . . . . . . . . . . . . . . . . 100
2.3.7 Alarm Unit ALMU6-F (XMC23) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
2.3.8 Alarm Unit ALMU8-F (XMC22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2.3.9 Air Flow Optimization Unit ETMP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
2.4 Cabling and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
2.4.1 Electrical Signal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
2.4.2 Optical Signal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.4.3 Power Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2.4.4 XMC20 Cable Tray and Grounding Bar. . . . . . . . . . . . . . . . . . . . . . . . . 103
2.4.5 COOL4 and ALMU4-F Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.4.6 DUA25 Alarm Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.4.7 DUA23 Alarm Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
2.5 ESD/EMC, Grounding and Earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3 XMC20 System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1 System Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.1 Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.2 Core Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.1.3 Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2 ESW and Feature Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2.1 ESW Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2.2 Feature License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.3 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.4 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.5 Operation and Maintenance for Traffic Functions. . . . . . . . . . . . . . . . . . . . . . . . . 111
3.5.1 Status and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.5.2 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.5.3 Ethernet Port Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.6 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.7 SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.8 PTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.9 PPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.10 Heat Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.11 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.11.1 DC Power Supply Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.11.2 AC Power Supply Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4 XMC20 Traffic and Equipment Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.1 Network Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.1.1 Network Scenarios for MPLS-TP Virtual Private Wire Services . . . . . . . . . . . . 118
4.1.2 Network Scenarios for MPLS-TP Virtual Private LAN Services . . . . . . . . . . . . 119
4.1.3 Network Scenario for LAN Island Interconnection using VPLS . . . . . . . . . . . . . 120
4.1.4 Network Scenario for Provider Network Access with Dual Homing. . . . . . . . . . . 121
4.2 Ethernet Traffic Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.2.1 MPLS-TP Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
4.2.2 Ethernet Switch with VLAN Support . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4.2.3 Circuit Emulation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4.2.4 NGN Voice Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4.2.5 Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.3 TDM Traffic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.3.1 SDH Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.3.2 EoS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.3.3 PDH Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.3.4 EoP Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.3.5 Voice Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.3.6 Legacy Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4.4 Protection Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Copyright 2022 Hitachi Energy. All rights reserved. 4

XMC20 | SYSTEM DESCRIPTION

4.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

4.4.2 Equipment Protection of the Core Unit . . . . . . . . . . . . . . . . . . . . . . . . . 140
4.4.3 Equipment Protection of Service Units . . . . . . . . . . . . . . . . . . . . . . . . . 140
4.4.4 Ethernet Traffic Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4.4.5 TDM Traffic Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5 Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.1 Management Systems Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.2 ECST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.3 Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
5.4 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
5.5 UNEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.6 DIRAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6 Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.1 Traffic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.1.1 Customer VLAN Bridge Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.1.2 MPLS-TP Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.1.3 Encryption Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
6.1.4 TDM Cross Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
6.1.5 TDM Timing Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
6.1.6 TDM Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.1.7 NGN Voice Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
6.2.1 Traffic Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
6.2.2 Management Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.2.3 Synchronization Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
6.2.4 Alarm Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
6.2.5 Power Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
6.3 Performance Control and Management Functions . . . . . . . . . . . . . . . . . . . . . . . . 168
6.3.1 System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
6.3.2 Traffic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.4 XMC25 R2 and XMC25 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
6.4.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
6.4.2 System Control and Management Functions . . . . . . . . . . . . . . . . . . . . . . 173
6.4.3 Mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6.4.4 COOL4 Fan Unit (R2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.4.5 ALMU4-F Alarm Unit (R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.4.6 DUA25 Dual Power Supply Input Unit . . . . . . . . . . . . . . . . . . . . . . . . . 181
6.4.7 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.4.8 Power Dissipation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.5 XMC23 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.5.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.5.2 System Control and Management Functions . . . . . . . . . . . . . . . . . . . . . . 183
6.5.3 Mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
6.5.4 COOL6 Fan Unit (R2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.5.5 COOL6 Fan Unit (R3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6.5.6 ALMU6-F Alarm Unit (R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6.5.7 DUA23 Dual Power Supply Input Unit . . . . . . . . . . . . . . . . . . . . . . . . . 193
6.5.8 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
6.5.9 Power Dissipation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.6 XMC22 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.6.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.6.2 System Control and Management Functions . . . . . . . . . . . . . . . . . . . . . . 195
6.6.3 Mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.6.4 COOL8 Fan Unit (R1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.6.5 COOL8 Fan Unit (R2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6.6.6 ALMU8-F Alarm Unit (R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6.6.7 DUA23 Dual Power Supply Input Unit . . . . . . . . . . . . . . . . . . . . . . . . . 204
6.6.8 POAC1 AC/DC Power Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Copyright 2022 Hitachi Energy. All rights reserved. 5

XMC20 | SYSTEM DESCRIPTION

6.6.9 Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

6.6.10 Power Dissipation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.7 EMC/ESD and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.7.1 EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.7.2 ESD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.7.3 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.7.4 Earthing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.8 Environmental Conditions and Dependability . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.8.1 Ambient Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.8.2 Dependability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
7 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
7.1 Associated XMC20 Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
7.2 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Copyright 2022 Hitachi Energy. All rights reserved. 6

XMC20 | SYSTEM DESCRIPTION PREFACE

1 Preface
This document gives a technical description of the network elements of the XMC20 family:
• XMC25 R2,
• XMC25,
• XMC23,
• XMC22.

Figure 1: XMC25 R2 and XMC25 (left), XMC23 (middle) and XMC22 (right)

The network element types offer generally the same capabilities and specifications. The term
“XMC20” is thus used to name the network element type XMC25 R2, XMC25, XMC23 or
XMC22. Where certain features or characteristics apply to a specific network element type only,
the respective network element type is named explicitly.

1.1 General
The XMC20 network elements act as multi-service access nodes and are based on the follow-
ing concept:
• All in one compact subrack:
− Multi-service access for voice, narrow- and broadband TDM data circuits, narrow- and
broadband Ethernet data service delivery.
− Multi-transport supporting electrical and optical Ethernet up to 10 Gbit/s, SDH transport
up to STM-16, PDH transport with E1 and SHDSL copper transmission.
− Multi-technology within a single chassis, providing an extensive circuit-based core with a
128 x 2 Mbit/s cross connect as well as packet-based core functionality with a switching
capacity of up to 258 Gbit/s.
− Protocol/format conversions.
• Very high modularity and flexibility allows for unequaled variety of network element configu-
rations.
• High density, compact size, high scalability and outdoor capability.
• Active or passive cooling.
• “Any service, any slot” architecture.

Copyright 2022 Hitachi Energy. All rights reserved. 7

XMC20 | SYSTEM DESCRIPTION PREFACE

1.2 XMC20 Network Elements

1.2.1 XMC25 R2
The XMC25 R2 is a network element of medium to large capacity. It can be used either as multi-
service access system for point of presence applications or as a network element carrying out
networking functions (e.g. digital cross-connect, gateway, channel bank).
The XMC25 R2 uses a 19-inch subrack with 21 slots, 1 or 2 core units, and up to 20 or 19 ser-
vice units as interface to the subscribers’ premises.
The XMC25 R2 is powered from a DC power supply (-48 VDC or -60 VDC nominal voltage),
and optionally via a dual power interface from two redundant primary power supplies.
The XMC25 R2 subrack can be operated with a fan unit (active cooling) or without a fan unit
(passive cooling). Interfaces for external alarm inputs and outputs are available on the fan unit
(active cooling) or on the alarm unit (passive cooling).

1.2.2 XMC25
The XMC25 is a network element with the same size and characteristics as the XMC25 R2 net-
work element, with the exception of the lower backplane transport capacity.

1.2.3 XMC23
The XMC23 is a compact network element of medium capacity. It can be used either as multi-
service access system for customer located applications or as a versatile compact transmission
system.
The XMC23 relies on the system design of the XMC25 and offers the same services as the
XMC25. It uses a 19-inch rack mountable subrack with 8 slots, housing 1 or 2 core units, and up
to 7 or 6 service units as interface to the subscribers’ premises.
The design of the XMC23 allows versatile equipment installation vertically and horizontally in
racks and cabinets.
The XMC23 is powered from a DC power supply (-48 VDC or -60 VDC nominal voltage), and
optionally via a dual power interface from two redundant primary power supplies.
The XMC23 subrack can be operated with a fan unit (active cooling) or without a fan unit (pas-
sive cooling). Interfaces for external alarm inputs and outputs are available on the fan unit
(active cooling) or on the alarm unit (passive cooling).

1.2.4 XMC22
The XMC22 is a compact network element of small capacity. It can be used either as multiser-
vice access system for customer located applications or as a versatile compact transmission
system.
The XMC22 relies on the system design of the XMC23 and offers the same services as the
XMC23 and XMC25. It uses a 19-inch rack mountable subrack with 4 slots, housing 1 core unit,
and up to 3 service units as interface to the subscribers’ premises.
The design of the XMC22 allows versatile equipment installation vertically and horizontally in
racks and cabinets.
The XMC22 is powered from a DC power supply (-48 VDC or -60 VDC nominal voltage), and
optionally via a dual power interface from two redundant primary power supplies.
The XMC22 can alternatively be powered from an AC power supply together with an optional
battery backup DC power supply.
The XMC22 subrack can be operated with a fan unit (active cooling) or without a fan unit (pas-
sive cooling). Interfaces for external alarm inputs are available on the fan unit. The subrack
operated without a fan unit provides no external alarm interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 8

XMC20 | SYSTEM DESCRIPTION PREFACE

1.2.5 XMC20 Packet Based Core

The packet based core of the XMC20 is built up from several individual Ethernet switching
devices located on the core unit and on the Ethernet service units. Together these intercon-
nected switching devices emulate one physical switching device, called “XMC20 Switch”.
Each Ethernet service unit and the core unit plugged and assigned in the XMC20 subrack con-
tributes its switch ports to the XMC20 Switch, i.e. the XMC20 Switch ports are located on the
core unit and on the service units. From a spanning tree protocol viewpoint, the XMC20
behaves as one RSTP entity.
But there are also some Ethernet service units operating as a stand alone bridge with its own
RSTP entity. These units access the XMC20 Switch via an Ethernet connection on the XMC20
backplane. These backplane ports are handled like an external port of the XMC20 Switch.
For an overview of all XMC20 service units please refer to section 1.2.8 XMC20 Core and Ser-
vice Units Overview (on page 12).
The physical interconnection of all switching devices is done with 40 Gbit/s, 10 Gbit/s or 1 Gbit/s
Ethernet links from the service unit to the active core unit and to the standby core unit. All Ether-
net links present three types of Ethernet stars.
• the 40 Gbit/s Ethernet links form the 40GbE star,
• the 10 Gbit/s Ethernet links form the 10GbE star,
• the 1 Gbit/s Ethernet links form the 1GbE star.
The active and the standby core unit are in addition connected with two 10 Gbit/s Ethernet links.
The maximum switching capacity of the XMC25 R2 subrack is 258 Gbit/s.

XMC20

Packet data interfaces

Stand alone bridge
GbE star

Packet
network
Packet data interfaces Packet transport

XMC20 Switch

Ethernet bridge

Figure 2: XMC20 packet based core with XMC20 Switch and stand alone bridge

The XMC20 Switch supports two functions:

• VLAN Bridge
In IEEE standard 802.1Q (2011) terminology the VLAN Bridge function of the XMC20 Switch
is a Customer Bridge. In a customer bridged network (CBN), C-tags are used to separate dif-
ferent VLANs (i.e. C-VLANs).
• MPLS-TP Transport
Both functions can be used simultaneously in one XMC20 network element.

Risk of operating trouble!

There are no restrictions to use the VLAN Bridge and the MPLS-TP Transport func-
tions simultaneously in small applications. However both functions are very power-
ful and need a lot of resources.
→ For this reason Hitachi Energy does not recommend to use both functions
simultaneously in one XMC20 network element for larger applications.

Copyright 2022 Hitachi Energy. All rights reserved. 9

XMC20 | SYSTEM DESCRIPTION PREFACE

1.2.6 XMC20 Circuit Based Core

The circuit based core of the XMC20 is built around the TDM bus in the subracks backplane.
The TDM bus with the corresponding access circuits presents a distributed cross connect sys-
tem with an access capacity of 128 x 2 Mbit/s. Cross connections are available at the P12 layer
(up to 128 x P12) or at the P0 layer (up to 4096 x P0).
Each TDM based service unit and the core unit have write access to the TDM bus according to
the service units or core units TDM traffic capacity. Each TDM based service unit and the core
unit have read access to the whole TDM bus
The TDM bus allows to configure unidirectional and bidirectional cross connections between
any port or channel of any TDM based service unit or the core unit.

XMC20

TDM voice interfaces PDH transport

TDM bus

TDM
network

TDM data interfaces SDH transport

TDM cross connection

Figure 3: XMC20 circuit based core

1.2.7 XMC20 Protocol Conversion

For an overview of all XMC20 service units please refer to section 1.2.8 XMC20 Core and Ser-
vice Units Overview (on page 12).

1.2.7.1 Ethernet over PDH

The XMC20 comprises Ethernet service units providing access to the TDM bus. Ethernet traffic
from the front port or the backplane Gbit/s Ethernet interface can be transported in PDH chan-
nels of up to 16 x 2 Mbit/s via the TDM bus to a PDH or SDH transport unit.
Note that the PDH channel carrying the Ethernet traffic can be transported in a VC-12 via the
SDH network.

Copyright 2022 Hitachi Energy. All rights reserved. 10

XMC20 | SYSTEM DESCRIPTION PREFACE

XMC20

PDH transport

TDM bus
TDM
network
Packet data interfaces
with EoP
SDH transport
EoP

Packet data interfaces GbE star Packet transport

Packet
network

TDM cross connection

Ethernet bridge

Figure 4: XMC20 EoP protocol conversion

1.2.7.2 Ethernet over SDH

The XMC20 comprises SDH service units providing the Ethernet over SDH functionality. Ether-
net traffic from the front port or the backplane Gbit/s Ethernet interface can be transported in
SDH channels of up to 12 x VC-4 via the SDH transport unit.

XMC20
TDM
SDH transport EoS network
GbE star

Packet
Packet data interfaces Packet transport
network

Ethernet bridge

Figure 5: XMC20 EoS protocol conversion

1.2.7.3 PDH over Ethernet

The XMC20 comprises a circuit emulation service unit providing the transport of TDM based
data traffic via IP packets. The service unit accesses up to 8 x P12 TDM based data traffic in
structured or unstructured format from the TDM bus, maps the TDM traffic into IP packets and
forwards the IP packets via the GbE star to the packet transport unit.
The circuit emulation service supports the following protocols:
• Structure Agnostic Transport over Packet (SAToP),
• Circuit Emulation Service over Packet Switched Network (CESoPSN),
• Circuit Emulation Services over Ethernet (CESoETH).

Copyright 2022 Hitachi Energy. All rights reserved. 11

XMC20 | SYSTEM DESCRIPTION PREFACE

XMC20

TDM voice interfaces

TDM bus

GbE star
Circuit Emulation

SAToP Packet
TDM data interfaces CESoPSN Packet transport
network
CESoETH

TDM cross connection

Ethernet bridge

Figure 6: XMC20 circuit emulation protocol conversion

1.2.7.4 Voice over IP

The XMC20 provides a voice gateway service unit for the transport of TDM based voice traffic
via IP packets using the SIP protocol, i.e. offering the voice over IP (VoIP) service. The service
unit can serve up to 1216 PSTN subscribers. It accesses the voice signals from the TDM bus,
maps the TDM traffic into IP packets and forwards the IP packets via the GbE star to the packet
transport unit.
The VoIP service uses the “Real-Time Transport Protocol” (RTP) protocol for the encapsulation
of the voice streams.

XMC20
TDM bus

GbE star

TDM voice interfaces Voice over IP

Packet
FXS Packet transport
SIP network
ISDN-BA

TDM cross connection

Ethernet bridge

Figure 7: XMC20 VoIP protocol conversion

1.2.8 XMC20 Core and Service Units Overview

The following plug-in units are available for the XMC20:
• The core unit CENT2 implements the control function and a central Ethernet switch with
VLAN support (IEEE, 802.1Q). It offers four SFP/SFP+ cages for electrical or optical GbE or
10 GbE interfaces and one electrical 10/100/1000BASE-T Ethernet interface.
The CENT2 implements a routing function for the data communication network and the PDH
timing functions.
• The core unit COGE5 implements the control function and a central Ethernet switch with
VLAN support (IEEE, 802.1Q). It offers two SFP/SFP+ cages for electrical or optical GbE or
10 GbE interfaces and three electrical 10/100/1000BASE-T Ethernet interfaces.
The COGE5 implements a routing function for the data communication network and the PDH
timing functions.
The core unit COGE5-F provides the same functionality as the COGE5 but can be operated
in a subrack with passive cooling. The COGE5-F is two slots wide.

Copyright 2022 Hitachi Energy. All rights reserved. 12

XMC20 | SYSTEM DESCRIPTION PREFACE

• The WAN port expansion unit EXPU1 offers 4 SFP+ based 10 Gbit/s Ethernet interfaces and
one QSFP+ based 40 Gbit/s Ethernet interface. The unit expands the number of WAN ports
of the CENT2 core unit. The Ethernet front ports are directly attached to the switch circuit of
the core unit.
The EXPU1 unit is operable in the XMC25 R2 subrack with the CENT2 core unit.
• Encryption units with Ethernet interfaces towards the core unit and towards the MPLS trans-
port network:
− The encryption unit SECU1-8 implements four encryption engines for the encryption of
four bidirectional Ethernet streams, each with up to 1024 LSPs, partitioned into two inde-
pendent functional units. It offers eight SFP cages for Ethernet traffic interfaces and one
electrical 10/100/1000BASE-T Ethernet interface for the management of the two func-
tional units.
The encryption unit SECU1F8 provides the same functionality as the SECU1-8 but can
be operated in a subrack with passive cooling. The SECU1F8 is two slots wide.
− The encryption unit SECU1-4 implements two encryption engines for the encryption of
two bidirectional Ethernet streams, contained in one functional unit. It offers four SFP
cages for Ethernet traffic interfaces and one electrical 10/100/1000BASE-T Ethernet inter-
face for the management of the functional unit.
The encryption unit SECU1F4 provides the same functionality as the SECU1-4 but can
be operated in a subrack with passive cooling. The SECU1F4 is two slots wide.
• Service units with Ethernet interfaces towards the subscribers:
− ETE24: 24 electrical 10/100/1000BASE-T Ethernet interfaces.
− ETO12: 12 SFP based 100 or 1000 Mbit/s Ethernet interfaces.
The service unit ETO12-F provides the same functionality as the ETO12 but can be oper-
ated in a subrack with passive cooling. The ETO12-F is two slots wide.
− SUP12: 12 electrical 10/100/1000BASE-T Ethernet interfaces with power over Ethernet
(PoE) support.
• The service unit SUSE2 offers 24 SHDSL EFM (Ethernet in the First Mile) interfaces towards
the subscribers.
The service unit SUSE2-F provides the same functionality as the SUSE2 but can be oper-
ated in a subrack with passive cooling. The SUSE2-F is two slots wide.
• The service unit VRX10 offers 12 SFP based 100 or 1000 Mbit/s Ethernet interfaces. The
unit performs (stand alone) routing functions with up to 16 virtual router instances.
The service unit VRX10-F provides the same functionality as the VRX10 but can be operated
in a subrack with passive cooling. The VRX10-F is two slots wide.
• Service units with Ethernet interfaces towards the subscribers and performing stand alone
switching functions:
− SABO1: 12 SFP based 100 or 1000 Mbit/s Ethernet interfaces. The unit performs (stand
alone) switching functions.
The service unit SABO1-F provides the same functionality as the SABO1 but can be
operated in a subrack with passive cooling. The SABO1-F is two slots wide.
The SABO1 and SABO1-F service units use the same hardware as the ETO12 and
ETO12-F service units.
− SABE1: 12 electrical 10/100/1000BASE-T Ethernet interfaces with power over Ethernet
(PoE) support. The unit performs (stand alone) switching functions.
The SABE1 service unit uses the same hardware as the SUP12 service unit.
• The service unit ETAG1 offers 4 electrical 10/100BASE-T Ethernet interfaces towards the
subscribers. The unit performs (stand alone) switching and routing functions and offers
Ethernet over PDH transport with a maximum capacity of 16 x 2 Mbit/s.
• Service units with PSTN a/b (POTS, FXS) interfaces towards the subscribers:
− SUPM1: 16 interfaces,
− SUPM2: 64 interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 13

XMC20 | SYSTEM DESCRIPTION PREFACE

• The service unit ISDN4 offers 4 * ISDN-BA interfaces towards the subscribers.
• The FIL16 unit is a voice frequency high voltage line filter box for 19-inch rack mounting. The
box has a height of 1 HU. It provides 16 2-wire line interfaces and is connected to the FXS
voice service unit SUPM1 or SUPM2 of the XMC20. The box is mounted outside the XMC20
subrack.
• The service unit IMAG1 offers 8 magneto line voice interfaces towards the subscribers. The
IMAG1 provides the conversion between the magneto line interface and the E&M voice and
signaling interfaces of the TUEM1 unit.
• The service unit TUEM1 offers 8 E&M interfaces towards the subscribers, each consisting of
a 2-wire or 4-wire voice interface and 2 E&M signaling interfaces.
• The service unit TUXA1 offers 12 POTS voice a/b interfaces towards the local exchange
(FXO).
• The service unit TUDA1 offers 4 TDM data interfaces according to V.24/V.28, V.35, X.24/
V.11 or RS485. The available port bandwidth is in the range from 0.3 kbit/s up to 1984 kbit/s.
In addition the service unit offers 1 electrical 10/100BASE-T Ethernet interface with Ethernet
over PDH transport with a maximum bandwidth of 1’984 kbit/s.
• The service unit TUGE1 offers 8 codirectional E0 interfaces or alternatively 2 contradirec-
tional E0 interfaces towards the subscribers.
• The service unit SDSL8 offers eight SHDSL interfaces towards SHDSL CPEs for TDM ser-
vices or towards another SDSL8 unit using the trunk mode.
• The service unit SELI8 offers 8 E1 interfaces towards other G.703/G.704 interfaces or local
exchanges.
• The service unit STM14 is an SDH service unit offering 2 STM-4/STM-1 interfaces and 2
STM-1 interfaces. Four electrical 10/100/1000BASE-T Ethernet interfaces are used for EoS
applications.
• The service units NUSA1, NUSA1-F and NUSA2 are SDH service units offering 2 STM-16/
STM-4 interfaces and 2 STM-4/STM-1 interfaces. Four electrical 10/100/1000BASE-T Ether-
net interfaces are used for EoS applications.
The NUSA1-F unit provides the same functionality as the NUSA1 unit but can be operated in
a subrack with passive cooling. The NUSA1-F unit is two slots wide.
The service unit NUSA2 provides the same functionality as the NUSA1 but provides in addi-
tion 48 E12 front ports for the transport over SDH. The NUSA2 unit is two slots wide.
• The service unit SATP8 provides a circuit emulation service with a capacity of 8 x P12 from
the XMC20 TDM bus. It supports the SAToP, CESoPSN and CESoETH protocols for the
encapsulation of TDM bit streams using up to 64 Pseudo Wires. In addition it provides 8 E1
interfaces at the unit front ports.
• The service unit VOIP1 acts as a SIP gateway for voice over IP, serving up to 1216 PSTN
subscribers from the XMC20 TDM bus. It uses the SIP protocol for the call setup and the
RTP protocol for the encapsulation of the voice streams.
• The service unit VFTLX acts as a voice frequency processing unit. It provides echo cancel-
ers for up to 2 x 208 PSTN subscribers from the XMC20 TDM bus.
The traffic units are explained in detail in section 2.2 XMC20 Traffic Units (on page 47).

1.2.9 XMC20 Auxiliary Units Overview

The following auxiliary units are available for the XMC25 R2 and XMC25:
• The auxiliary dual-connection unit DUA25 allows the powering of the XMC25 R2 or XMC25
subrack from two redundant primary power supplies.
• The auxiliary fan unit COOL4 provides the active cooling of the XMC25 R2 or XMC25 sub-
rack and the external alarm interfaces.
• The auxiliary alarm unit ALMU4-F provides the same alarm interfaces as the COOL4 and
can be used for the passive cooling application of the XMC25 R2 or XMC25 subrack.
The following auxiliary units are available for the XMC23:

Copyright 2022 Hitachi Energy. All rights reserved. 14

XMC20 | SYSTEM DESCRIPTION PREFACE

• The auxiliary dual-connection unit DUA23 allows the powering of the XMC23 subrack from
two redundant primary power supplies.
• The auxiliary fan unit COOL6 provides the active cooling of the XMC23 subrack and the
external alarm interfaces.
• The auxiliary alarm unit ALMU6-F provides the same alarm interfaces as the COOL6 (R3)
and can be used for the passive cooling application of the XMC23 subrack.
The following auxiliary units are available for the XMC22:
• The auxiliary dual-connection unit DUA23 allows the powering of the XMC22 subrack from
two redundant primary power supplies.
• The auxiliary fan unit COOL8 provides the active cooling of the XMC22 subrack and the
external alarm interfaces.
• The auxiliary alarm unit ALMU8-F provides the same alarm interfaces as the COOL8 (R2)
and can be used for the passive cooling application of the XMC22 subrack.
• The auxiliary XMC22 AC power kit, consisting of the POAC1 AC/DC converter, the AC/DC
backplane and the required assembly material, provides the AC powering for the XMC22
with an optional battery backup.
• The auxiliary air flow optimization unit ETMP1 allows the operation of the XMC20 subrack,
equipped with SFP-based core and service units, in ambient temperatures up to 65°C.
The auxiliary units are explained in detail in section 2.3 XMC20 Auxiliary Units (on page 96).

1.3 XMC20 Traffic Services and Applications

1.3.1 Traffic Services Overview

The XMC20 offers the following traffic interfaces:

Table 1: XMC20 traffic interfaces

Interface XMC25 XMC25 XMC23 XMC22
R2
Optical Ethernet up to 40 Gbit/s X - - -
Optical Ethernet up to 10 Gbit/s X X X X
Electrical and optical Ethernet up to 1 Gbit/s X X X X
SHDSL EFM (ITU-T G.991.2, Annex B and G) X X X X
SHDSL TDM (ITU-T G.991.2, Annex B and G) X X X X
PSTN (analog POTS interface, FXS) X X X X
PSTN (analog POTS interface, FXO) X X X X
ISDN-BA (digital voice interface) X X X X
E&M voice 2-wire and 4-wire, plus signaling X X X X
Magneto line X X X X
E0 (G.703) X X X X
E1 (G.703 / G.704, CO or desktop CPE) X X X X
STM-1 (optical or electrical) X X X X
STM-4 (optical) X X X X
STM-16 (optical) X X X X
Ethernet over SDH (EoS) for up to 12 x VC-4 X X X X
Ethernet over PDH (EoP) for up to 2 Mbit/s X X X X
X.24 / V.11 X X X X
V.35 X X X X
V.24 / V.28 X X X X

Copyright 2022 Hitachi Energy. All rights reserved. 15

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 1: XMC20 traffic interfaces (continued)

Interface XMC25 XMC25 XMC23 XMC22
R2
RS485 2-wire and 4-wire X X X X
V.36 (via desktop CPE) X X X X

The XMC20 offers the gateway services:

Table 2: XMC20 gateway services

Interface XMC25 XMC25 XMC23 XMC22
R2
Circuit Emulation Service (CESoP) for up to 2 X X X X
Mbit/s
Voice over IP (VoIP) for up to 1216 POTS ports X X X X

XMC20
TDM voice interfaces:
- POTS, FXO, 2-wire
PDH transport:
- POTS, FXS, 2-wire
- E1
- ISDN-BA, 2B1Q
- SHDSL TDM
- E&M, 2/4-wire
- Magneto line network
TDM bus, 128 x 2 Mbit/s

SDH transport:
TDM data interfaces: - STM-1
- E0, 64 kbit/s E12
- STM-4
- E1, 2048 kbit/s - up to 48 VC-12
- STM-16
- SHDSL, up to 2048 kbit/s EoS
- X.24/V.11, up to 2048 kbit/s - up to 12 VC-4
- V.35, up to 2048 kbit/s
- V.36, up to 2048 kbit/s
- V.24/V.28, up to 128 kbit/s CESoP
- RS485, 2/4-wire, up to 600 kbit/s - 2048 kbit/s

Packet data interfaces with EoP

VoIP
- up to 2048 kbit/s
- 64 kbit/s
- 10/100BASE-TX

Packet data interfaces: Packet transport:

GbE star

Packet
- 10/100/1000BASE-T - 10/100/1000BASE-T network
- 100/1000BASE SFP based - 100/1000BASE SFP based
- 1000BASE-BX10/20/40/60 - 10GBASE-LR
- SHDSL, up to 5696 kbit/s - SHDSL, up to 5696 kbit/s

Figure 8: XMC20 multi-service and multi-transport capabilities

Legend:
− EoP: Ethernet over PDH
− EoS: Ethernet over SDH
− CESoP: Circuit Emulation Service over Packet
− VoIP: Voice over IP

Copyright 2022 Hitachi Energy. All rights reserved. 16

XMC20 | SYSTEM DESCRIPTION PREFACE

1.3.2 XMC20 Management

The XMC20 management concept is based on the XMC20 network element manager (ECST)
for local and remote management and the UNEM network element manager for remote man-
agement from the Network Management Centre / Network Operation Centre.
The UNEM offers Northbound Interfaces (NBI) for the OSS integration. The UNEM can manage
both, XMC20 network elements and XMC20 networks, while the ECST manages single XMC20
network elements only.

1.3.3 Application Description

The variety of interfaces supports the following services and applications:
• Ethernet frame transport over packet networks,
• Ethernet frame switching:
− untagged frames,
− priority tagged frames,
− C-VLAN ID tagged frames,
• Ethernet frame transport over MPLS:
− untagged frames,
− priority tagged frames,
− C-VLAN ID tagged frames,
• Ethernet frame transport over PDH,
• Ethernet frame transport over SDH,
• Ethernet frame transport over SHDSL,
• IP packet routing,
• TDM transport over PDH,
• TDM transport over SHDSL,
• TDM transport over SDH,
• circuit emulation service, i.e. TDM transport over packet networks,
• voice over IP service, i.e. TDM voice transport over packet networks,
• legacy data services,
• voice services.
All the above services are offered in parallel.
Several network scenarios can be implemented with the XMC20. The three basic topologies are
− the star,
− the linear-chain, and
− the ring topology.
The XMC20 can be deployed in clusters, i.e. several XMC20 subracks are located at the same
location with a common backhaul interface.

1.3.3.1 Ethernet Frame Switching and Transport over Packet Networks

The XMC20 Switch can be configured to function as a VLAN aware Ethernet bridge. Ethernet
ports on service units and SHDSL EFM ports assigned to the VLAN Bridge can be configured to
play different roles. Depending of the role and the incoming and outgoing tagging the frames are
handled differently.
• Ingress direction
− Untagged frames and priority tagged frames become tagged with the port VLAN ID and
are forwarded, or are dropped.
− Tagged frames are forwarded, or are dropped.
− Tagged frames get a VLAN tag added with the port VLAN ID and are forwarded (Q-in-Q).

Copyright 2022 Hitachi Energy. All rights reserved. 17

XMC20 | SYSTEM DESCRIPTION PREFACE

• Egress direction
− All frames are forwarded.
− Frames tagged with the port VLAN ID get the VLAN tag removed and are forwarded.
− Frames not tagged with the port VLAN ID are forwarded unchanged.
− Frames not tagged with the port VLAN ID are dropped.
The SFP based Ethernet ports on the core unit and WAN port expansion unit support link
speeds up to 10 Gbit/s. Typically these ports are used to access the packet network.
The other Ethernet ports on the core unit and the Ethernet ports on the service units support link
speeds up to 1 Gbit/s. The SHDSL EFM ports support up to 22.7 Mbit/s using the aggregation
function.
The XMC20 supports class of service (CoS) handling, according to IEEE 802.1Q. The 8 priority
levels are mapped to traffic classes. The traffic classes correspond to queues in the XMC20
Switch. The core and the service units have 8 queues in egress direction.
The XMC20 Switch behaves as one RSTP entity.

1.3.3.2 Ethernet Frame Transport over MPLS Networks

The XMC20 Switch can be configured to function as an MPLS-TP Transport equipment. In this
case the XMC20 can act as a Label Switching Router (LSR) or Label Edge Router (LER). The
MPLS-TP implementation with XMC20 supports the VPWS service, VPLS service, OAM fea-
tures, QoS and protection switching.
Ethernet ports pointing to the customer side and used for an MPLS-TP VPWS service have to
be configured as Pseudo Wire Access Circuits (PWAC). PWAC ports are located on Ethernet
service units, on the core units or on the WAN port expansion units. PWAC ports are attached
to a Virtual Private Wire Service with one of the following service types:
• AC (Attachment Circuit) Port Based, No Change
Untagged, priority tagged and VLAN tagged frames are forwarded unchanged.
• AC Port Based, Add PW Tag
Untagged, priority tagged and VLAN tagged frames are forwarded with an added Pseudo
Wire VLAN tag.
• AC VLAN Based, No Change
VLAN tagged frames with the configured VLAN tag ID are forwarded unchanged.
• AC VLAN Based, Change Tag
VLAN tagged frames with the configured VLAN ID are forwarded with a modified VLAN ID.
• AC VLAN Based, Add PW Tag
VLAN tagged frames with the configured VLAN ID are forwarded with an added Pseudo Wire
VLAN tag.
• AC Untagged, No Change
Untagged frames are forwarded unchanged.
• AC Untagged, Add PW Tag
Untagged frames are forwarded with an added Pseudo Wire VLAN tag.
Ethernet ports pointing to the customer side and used for an MPLS-TP VPLS service have to be
configured as Customer VLAN Ports (CVP). CVP ports are located on Ethernet service units, on
the core units or on the WAN port expansion units. CVP ports are attached to the XMC20
Switch, the XMC20 Switch is attached to the VPLS pseudo wires via the switch virtual interface
(SVI), using one of the following service types:
• Change VLAN
VLAN tagged frames with the configured SVI VLAN ID are forwarded with a modified VLAN
ID.
• No Change
VLAN tagged frames with the configured SVI VLAN ID are forwarded unchanged.

Copyright 2022 Hitachi Energy. All rights reserved. 18

XMC20 | SYSTEM DESCRIPTION PREFACE

Ethernet ports pointing to the network side and used for an MPLS-TP Transport service have to
be configured as MPLS-TP ports. MPLS-TP ports are located on the core units or the WAN port
expansion units. MPLS-TP ports forward Ethernet packets with LSP MPLS labels and Pseudo
Wire MPLS labels.
MPLS-TP ports can also be VLAN tagged, i.e. they are logical subinterfaces assigned to physi-
cal transport interface.
The XMC20 supports co-routed LSPs, i.e. forward and reverse direction LSPs are routed over
the same path. MPLS tunnels can be protected or unprotected.
The SFP based Ethernet ports on the core unit and WAN port expansion unit support link
speeds up to 10 Gbit/s. Typically these ports are used to access the packet network.
The other Ethernet ports on the core unit and the Ethernet ports on the service units support link
speeds up to 1 Gbit/s.
As a security feature the ingress rate of an Ethernet port can be limited. In addition rate limiters
can be applied for MPLS-TP tunnels.

1.3.3.3 IP Packet Routing

The XMC20 core unit implements an IP router. This router is used for the management commu-
nication via a data communication network (DCN).
The router has therefore
• up to 16 numbered or unnumbered PPP links accessing the DCN,
• up to 10 numbered or unnumbered MCC (MPLS-TP management communication channel)
links accessing the DCN, and
• two (COGE5) or eight (CENT2) Ethernet interface to connect a network manager.
The XMC20 service unit ETAG1 implements a general purpose IP router. The router has
• up to 64 numbered or unnumbered PPP and multilink PPP links with configurable HDLC
framing.
The XMC20 service units VRX10 and VRX10-F implement up to 16 virtual router instances
usable as general purpose IP routers. The routers have
• up to 256 virtual router interfaces, and
• up to 32 loopback interfaces.
All routers support the OSPF protocol and static routing.

1.3.3.4 TDM Transport Services

TDM transport services are often used for legacy applications or for the MAC frame transport
via a TDM network.
XMC20 offers the following SDH, PDH and SHDSL interfaces:
• STM-16, STM-4 and STM-1 interfaces:
− SDH Terminal Multiplexer application
− SDH Add/Drop Multiplexer application
− Termination of 2 Mbit/s TDM signals
− Ethernet over SDH (EoS) application
• E1 interfaces:
− Transparent P12 signal transport
− Terminated P12 signal transport
− Ethernet over PDH (EoP) application
• SHDSL TDM interfaces:
− Transparent P12 signal transport
− Terminated P12 signal transport
− Partially filled P12 signal transport
− Ethernet over PDH (EoP) application

Copyright 2022 Hitachi Energy. All rights reserved. 19

XMC20 | SYSTEM DESCRIPTION PREFACE

1.3.3.5 Circuit Emulation Service

Circuit Emulation Service over packet (CESoP) provides the emulation of a legacy TDM service
over a packet network. The packet network can be an Ethernet network, an IP network, or even
a MPLS network. Interworking functions (IWF) perform the mapping of the TDM signals into
packets and vice versa.
The CESoP application with XMC20 provides the following benefits:
• Transport of n x 64 kbit/s and structured and unstructured 2 Mbit/s TDM signals over the
packet network.
• Transport of TDM timing signals over the packet network.
• Synchronous operation of the gateway functions, i.e. the traffic signals are all synchronized
to the NE timing which is traceable to a primary reference clock (PRC).
• Plesiochronous operation of the gateway functions, i.e. the traffic signals are transported
using the customer originated service timing.

1.3.3.6 Voice over IP Service

Voice over IP (VoIP) provides the conversion of legacy voice signals to IP packets and vice
versa.
The analog or digital voice is transported to the PSTN or ISDN-BA unit of the XMC20 in the
base-band. The PSTN unit implements the analog telephone subscriber interfaces, the ISDN-
BA unit implements the ISDN subscriber interfaces.
The VoIP application with XMC20 is based on the SIP protocol. The SIP access gateway func-
tionality is implemented in a separate unit, mapping and demapping the voice signals to and
from IP packets.
The VoIP application with XMC20 provides the following benefits:
• Transport of PSTN (POTS) and ISDN-BA TDM signals over the packet network using the
RTP protocol, i.e. no requirement for a direct access to the PSTN network.
• Termination of the inband and out-of-band signaling and conversion to the SIP protocol.

1.3.3.7 Legacy Data Services

The XMC20 offers the access to legacy data services. All these legacy services make use of the
TDM transport facilities of the XMC20.
XMC20 offers the following data services:
• Data interfaces:
− E0 interface (64 kbit/s)
− V.24/V.28 interface
− V.35 interface
− X.24/V.11 interface
− RS485 interface
− Subrates asynchronous from 0.3 kbit/s to 38.4 kbit/s
− Subrates synchronous from 0.3 kbit/s to 56 kbit/s
− Synchronous data rates from 64 kbit/s to 1984 kbit/s
− Data conferencing function for linear and star network applications
• Ethernet interfaces with PDH transport:
− 10/100BASE-T interface
− Ethernet switching and routing
− OSPF and static IP routing
− Support of HDLC, PPP and MLPPP
− PDH transport with a maximum bandwidth of 16*2 Mbit/s

Copyright 2022 Hitachi Energy. All rights reserved. 20

XMC20 | SYSTEM DESCRIPTION PREFACE

1.3.3.8 Voice Services

The XMC20 offers the access to legacy voice services. All these legacy services make use of
the TDM transport facilities of the XMC20.
XMC20 offers the following voice services:
• Voice interfaces:
− Voice 2-wire analog interface (FXS)
− Voice 2-wire analog interface (FXO)
− Voice ISDN-BA with 2B1Q line code
− Voice 2/4-wire interface with E&M signaling
− Voice 2-wire magneto line interface
− Voice conferencing function for linear and star network applications

1.4 Content Changes

This section provides an overview on content that has been changed with the current XMC20
system release “R16A” with respect to the last release, and content that has been added or
changed in previous system releases.
For more information about feature availability please refer to [1KHW028868] Release Note
“XMC20 System Release R16A” of the current system release.
The following table provides information about functionality that has been added or enhanced
with the current system release.

Table 3: Changes provided with the release “R16A”

Area Features Details Units
Link Protection ERPS supported again enhanced Link Protection Ethernet switch-
ing units

Table 4: Changes provided with the release “R15B”

Area Features Details Units
Core unit New core unit COGE7, COGE7-F. new section 2.2.2 Core Unit COGE7,
COGE7 and COGE7-F COGE7-F
(on page 54)
Services and WAN port expansion unit with four 10 Gbit/s enhanced section 2.2.4 WAN Port EXPU1
functional unit Ethernet ports and one 40 Gbit/s Ethernet Expansion Unit EXPU1
port (first release). (on page 60)
Security Access Control List for chassis switch ser- new section 4.2.5.6 Access Chassis switch
vice units. Control Lists (ACLs) service units
(on page 129)
Services LLDP support for neighbor discovery. new section 4.2.2.4 LLDP Core units,
(on page 125) chassis switch
service units,
stand-alone
bridging units

Table 5: Changes provided with the release “R15A”

Area Features Details Units
Network element New high capacity network element type new section 1.2.1 XMC25 XMC25 R2
XMC25 R2 R2 (on page 8)
Services and WAN port expansion unit with four 10 Gbit/s new section 2.2.4 WAN Port EXPU1
functional unit Ethernet ports and one 40 Gbit/s Ethernet Expansion Unit EXPU1
port (on page 60)

Copyright 2022 Hitachi Energy. All rights reserved. 21

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 5: Changes provided with the release “R15A” (continued)

Area Features Details Units
Voice processing Voice frequency processing unit with echo new section 2.2.21 Voice VFTLX
cancelers Frequency Processing
Unit VFTLX (on
page 86)
Voice processing Support of PSTN FXO subscribers enhanced section 2.2.20 Media VOIP1
Gateway Unit VOIP1
(on page 84)
Management New user class “support” available, provid- enhanced section 6.4.2.4 Man- XMC25 R2,
ing the user with expanded troubleshooting agement Access (on XMC25,
data. page 175) XMC23,
XMC22
Management IPSec for management communication no reduced section 6.4.2.4 Man- XMC25,
longer supported. agement Access (on XMC23,
page 175) XMC22
QoS LSP rate limiters for MPLS-TP tunnels. enhanced section 4.2.5.2 Rate COGE5
Limiters (on page 128)
Services MPLS-TP ports as VLAN based subinter- enhance- section 2.2.5 Encryp- SECU1
faces can be encrypted with the SECU1 ment tion Unit SECU1-4,
encryption unit SECU1F4, SECU1-8
and SECU1F8 (on
page 61)
Synchronization Support of UDP/IPv4 based PTP transport. enhance- section 6.1.5 TDM Tim- XMC25,
Fully compliant to ITU-T G.8275.2 and ment ing Source (on XMC23,
IEEE1588-2019. page 156) XMC22
Synchronization PTP Master Clock support with UDP/IPv4 enhance- section 6.1.5 TDM Tim- XMC25,
based PTP transport. ment ing Source (on XMC23,
page 156) XMC22
Synchronization PPS output on the core unit CENT2 enhance- section 6.2.3 Synchro- CENT2
ment nization Interfaces (on
page 165)
Data Interfaces Synchronous data transport up to 2048 kbit/ enhance- section 2.2.28 Data TUDA1
s ment Service Unit TUDA1
(on page 93)

Table 6: Changes provided with the release “R14A”

Area Features Details Units
Network access Provider edge dual homing access via two enhance- section 4.1.4 Network XMC20
provider network elements. ment Scenario for Provider
Network Access with
Dual Homing (on
page 121)
QoS LSP rate limiters for MPLS-TP tunnels. new section 4.2.5.2 Rate CENT2
Limiters (on page 128)
QoS Egress shaper per class type on MPLS-TP new section 4.2.5.4 Egress CENT2
ports. Class Type Shapers
(on page 128)
Management Two VLAN based management interfaces. enhanced COGE5
Synchronization Support of “PTP Ordinary/Boundary and enhanced COGE5
Transparent Clock” mode with PTP VLAN
based synchronization.
Network element Maximum ambient temperature for the enhanced section 6.8.1.3 Opera- XMC20
operation of the XMC20 network element tion (on page 207)
increased from 60°C to 65°C.

Copyright 2022 Hitachi Energy. All rights reserved. 22

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 6: Changes provided with the release “R14A” (continued)

Area Features Details Units
OAM TDM pattern generator and analyzer usable new section 6.3.1 System XMC20
for diagnostics. Level (on page 168)
Synchronization Support of XMC20 operating as PTP (IEEE reduced section 3.6 Synchroni- XMC20
1588v2) Grand Master removed zation (on page 113)

Table 7: Changes provided with the release “R8B SP01”

Area Features Details Units
Network element The slot 13 of the XMC25 and XMC23 sub- enhanced section 6.4.1 Architec- XMC25,
racks is usable for TDM service units inde- ture (on page 171) and XMC23
pendent of the core unit type plugged in slot section 6.5.1 Architec-
11. ture (on page 182)
Management Authentication of the network element man- enhanced section 5.2 ECST (on XMC25,
ager UNEM via public/private key exchange page 145) XMC23,
XMC22

Table 8: Changes provided with the release “R8B”

Area Features Details Units
Services and Encryption units with two or four encryption new section 2.2.5 Encryp- SECU1-4,
functional unit engines, managed by UNEM and the tion Unit SECU1-4, SECU1F4,
DIRAC server. SECU1F4, SECU1-8 SECU1-8,
The new units are the successors of the and SECU1F8 (on SECU1F8
SECU1 and SECU1-F encryption units. page 61)
Management Key management server DIRAC for the new section 5.6 DIRAC (on DIRAC
generation and deployment of encryption page 149)
Master Keys
Network element Update of referenced EMC standards enhanced section 6.7 EMC/ESD XMC25,
and Safety (on XMC23,
page 205) XMC22
Services and Routing unit with up to 16 virtual routers enhanced section 2.2.10 Ethernet VRX10,
functional unit and DHCP relay agent Service Units VRX10 VRX10-F
and VRX10-F (on
page 70)
Management Update of the SNMP MIBs. enhanced section 5.4 SNMP (on XMC25,
page 146) XMC23,
XMC22

Table 9: Changes provided with the release “R8A SP01”

Area Features Details Units
Services and Ethernet standalone switching units with new section 2.2.11 Ethernet SABO1,
functional unit optical Ethernet ports Service Units SABO1 SABO1-F
and SABO1-F (on
page 71)
Services and Ethernet standalone switching units with new section 2.2.12 Ethernet SABE1
functional unit electrical (PoE) Ethernet ports Service Unit SABE1 (on
page 73)
Core unit Fast equipment protection enhanced section 2.2.1 Core Unit CENT2
CENT2 (on page 51)
Synchronization Simultaneous support of PTP Transparent enhanced section 3.6 Synchroni- XMC25,
Clock and Boundary Clock with the CENT2 zation (on page 113) XMC23,
core unit. XMC22,
COGE5

Copyright 2022 Hitachi Energy. All rights reserved. 23

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 9: Changes provided with the release “R8A SP01” (continued)

Area Features Details Units
Synchronization Network element timing transfer via SHDSL enhanced section 2.2.9 Ethernet SUSE2,
from LT to NT. service unit SUSE2 and SUSE2-F
SUSE2-F (on page 68)
Synchronization Full compliance of the Network Element enhanced section 6.2.3 Synchro- XMC25,
Clock with ITU-T G.8262/Y.1362 (07/2010) nization Interfaces (on XMC23,
Option 1. page 165) XMC22
Maximum frequency tolerance reduced.
Management Enhanced GUI for the packet connectivity. enhanced XMC25,
Graphical view for G.826 performance data. XMC23,
XMC22

Table 10: Changes provided with the release “R8A”

Area Features Details Units
Core unit Core unit with access to the 10 GbE star of new section 2.2.1 Core Unit CENT2
the XMC20 backplane. CENT2 (on page 51)
Fast equipment protection switchover.
Increased number of VLAN based ports of
the management router.
Services and SHDSL EFM transport unit, 24 subscriber new section 2.2.9 Ethernet SUSE2,
functional unit ports service unit SUSE2 and SUSE2-F
SUSE2-F (on page 68)
QoS Port shaping at the XMC20 Switch egress new section 4.2.5.3 Egress XMC20
ports Port Shapers (on
page 128)

Table 11: Changes provided with the release “R6D”

Area Features Details Units
Management Export restriction free element manager enhanced ECST
ECST, and ESW for the core unit COGE5 XMC20
removed
Document Hitachi Energy branding. enhanced - -
New document number
Alarming Enhanced fan unit COOL8 (R2) for the enhanced section 6.6 XMC22 XMC22
XMC22 with 2 alarm outputs. Characteristics (on
New alarm unit ALMU8-F for the XMC22 page 194)
with passive cooling.
Network element Revised MTTF values of the fan units. enhanced section 6.4 XMC25 R2 COOL4,
and XMC25 Character- COOL6,
istics (on page 171), COOL8
section 6.5 XMC23
Characteristics (on
page 182), section 6.6
XMC22 Characteristics
(on page 194)
QoS Enhanced rate limiters: enhanced section 4.2.5.2 Rate XMC25,
1 Rate - 3 Color, and Limiters (on page 128) XMC23,
2 Rate - 3 Color. XMC22
Services and Routing unit with four virtual routers and 12 new section 2.2.10 Ethernet VRX10,
functional unit Ethernet front interfaces Service Units VRX10 VRX10-F
and VRX10-F (on
page 70)

Copyright 2022 Hitachi Energy. All rights reserved. 24

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 11: Changes provided with the release “R6D” (continued)

Area Features Details Units
Network access MPLS-TP ports as VLAN based subinter- enhance- section 4.2.1 MPLS-TP XMC25,
faces. ment Transport (on XMC23,
page 121) XMC22
Network access Customer network access to the core net- enhance- section 4.1.3 Network
work via two provider edges (dual homing) ment Scenario for LAN Island
Interconnection using
VPLS (on page 120)

Table 12: Changes provided with the release “R6C”

Area Features Details Units
Services and Encryption unit with four encryption engines new section 2.2.5 Encryp- SECU1
functional unit tion Unit SECU1-4,
SECU1F4, SECU1-8
and SECU1F8 (on
page 61)
Management Export restriction free element manager new section 5.2 ECST (on ECST
ECST, and ESW for the core unit COGE5 page 145) XMC20
Link Protection R- supported for XMC20 bridge ports for enhanced section 4.1.3 Network XMC25,
Ethernet and MPLS interworking Scenario for LAN Island XMC23,
Interconnection using XMC22
VPLS (on page 120)
Link Protection RSTP supported for XMC20 bridge ports enhanced section 4.4.4.2 Rapid XMC25,
spanning tree protocol XMC23,
(RSTP) (on page 141) XMC22
Services and Configurable queue management on the enhanced section 2.2.3 Core Unit COGE5
functional unit COGE5 unit COGE5 and COGE5-F
(on page 57)
Services and Fast equipment protection for the core unit enhanced section 6.4.2.1 Control COGE5
functional unit COGE5 System (on page 173),
section 6.5.2.1 Control
System (on page 183)

Table 13: Changes provided with the release “R6B”

Area Features Details Units
Services and Support of circuit emulation protocols enhanced section 2.2.18 E1 Cir- SATP8
functional unit CESoPSN and CESoETH on the SATP8 cuit Emulation Service
unit. Unit SATP8 (on
page 81)
Services and ISDN-BA voice unit, 4 subscriber ports, new section 2.2.23 ISDN-BA ISDN4
functional unit 2B1Q line code. Voice Service Unit
ISDN4 (on page 88)
Management Update of the supported Windows operat- enhanced section 5.2 ECST (on ECST, UNEM
ing systems for the Element Manager ECST page 145),
and the Network Element Manager UNEM section 5.5 UNEM (on
page 147)

Copyright 2022 Hitachi Energy. All rights reserved. 25

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 13: Changes provided with the release “R6B” (continued)

Area Features Details Units
Management Support of SNMP v1, v2c and v3 for fault new section 5.4 SNMP (on XMC25,
management page 146) XMC23,
Network access Support of MPLS-TP Virtual Private LAN enhanced section 4.2.1.2 VPLS XMC22
Services Transport Function (on
page 122)
OAM Support of LSP Ping and Trace Route on enhanced section 1.3.3.2 Ethernet
MPLS-TP ports Frame Transport over
MPLS Networks (on
page 18)
QoS Configurable mapping of attachment cir- enhanced section 4.2.1.3 Traffic
cuits PCP to pseudo wire EXP Prioritization (on
page 123)
Security Rate limiters on Ethernet ports new section 4.2.5.2 Rate
Limiters (on page 128)
Link Protection ERPS, RSTP and MSTP no longer sup- reduced
ported
Synchronization Support of PTP (IEEE 1588v2) Grand Mas- enhanced section 3.6 Synchroni- XMC25,
ter Clock mode zation (on page 113) XMC23,
XMC22,
COGE5
TDM encapsula- Support of the Circuit Emulation Service enhanced section 2.2.18 E1 Cir- SATP8
tion over Packet Switch Network (CESoPSN) cuit Emulation Service
Unit SATP8 (on
page 81)
Voice interfaces Voice frequency high voltage line filter box new section 2.2.24 Voice FIL16
Frequency Filter Box
FIL16 (on page 89)

Table 14: Changes provided with the release “R6A”

Area Features Details Units
Service unit name HW name for the VOIP1 unit corrected changed section 2.2.20 Media VOIP1
Gateway Unit VOIP1
(on page 84)
Network element New XMC25 subrack revisions R3A and enhanced section 3.11.1 DC XMC25
R3B with modified front cover: Power Supply Inter-
- Subrack revision R3A with maximum faces (on page 115)
power supply current 30 A
- Subrack revision R3B with maximum
power supply current 45 A
Network element New network element type XMC22: new section 6.6 XMC22 XMC22
- Subrack XMC22 with 4 slots Characteristics (on
- 1 slot for core unit page 194)
- 3 slots for service units
- Fan unit COOL8
- Dual power supply unit DUA23
- AC/DC power converter POAC1
Synchronization Support of PTP (IEEE 1588v2) for the enhanced section 3.6 Synchroni- XMC25,
PETS synchronization using COGE5 ports zation (on page 113) XMC23,
XMC22,
COGE5
Network access Support of the MPLS-TP Transport func- new section 4.2.1 MPLS-TP XMC25,
tion with XMC20 as Label Edge Router Transport (on XMC23,
(LER) or Label Switching Router (LSR), page 121) XMC22,
using COGE5 ports as MPLS-TP uplink COGE5
ports

Copyright 2022 Hitachi Energy. All rights reserved. 26

XMC20 | SYSTEM DESCRIPTION PREFACE

Table 14: Changes provided with the release “R6A” (continued)

Area Features Details Units
Voice interfaces Magneto line interface unit, 8 ports new section 2.2.26 Mag- IMAG1
neto Line Voice Ser-
vice Unit IMAG1 (on
page 91)

Table 15: Changes provided with the release “R4D”

Area Features Details Units
Data interfaces Transition coding for data interfaces up to enhanced section 2.2.28 Data TUDA1
19.2 kbit/s Service Unit TUDA1
(on page 93)
Voice gateway Maximum number of subscribers increased enhanced section 2.2.20 Media VOIP1
to 1216. Gateway Unit VOIP1
MFC-R2 port type added. (on page 84)
ISDN-PRA port type added.
Services and Faster equipment protection switchover enhanced / section 2.2.15 SDH and NUSA1,
functional unit time. reduced EoS Service Unit NUSA2
Maximum EoS capacity reduced to 12 VC-4 NUSA1 and NUSA1-F
equivalents. (on page 77),
section 2.2.16 SDH and
EoS Service Unit
NUSA2 (on page 79)

Table 16: Changes provided with the release “R4C”

Area Features Details Units
Data interfaces Contradirectional 64 kbit/s interface accord- enhanced section 2.2.29 E0 Ser- TUGE1
ing to G.703 vice Unit TUGE1 (on
page 95)
Services and STM-16, STM-4, STM-1 transport unit, 4 new section 2.2.16 SDH and NUSA2
functional unit electrical Ethernet front ports, 48 E12 front EoS Service Unit
ports. Up to 32 EoS groups. NUSA2 (on page 79)

Copyright 2022 Hitachi Energy. All rights reserved. 27

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2 Architecture and Views

2.1 XMC20 Subracks

2.1.1 Architecture

2.1.1.1 XMC25 R2
The XMC25 R2 uses a 19-inch subrack with 21 slots, one or two core units and up to 20 or 19
service units.
The XMC25 R2 supports core and service units as listed in section 2.2 XMC20 Traffic Units (on
page 47).
The XMC25 R2 allows to implement 1:1 equipment protection for the core unit. The slots for the
working core unit and the protecting core unit are slots 11 and 13, respectively. The slot concept
with and without redundancy is shown in Figure 10.

Please note:
The slot 13 of the XMC25 R2 subrack is not usable for Ethernet service units.

Please note:
The slot 9 and slot 15 of the XMC25 R2 subrack using the CENT2 core unit can be
equipped with the 40 Gb Ethernet WAN port expansion unit EXPU1.

Please note:
The slot 1, slot 8 to slot 15, and slot 21 of the XMC25 R2 subrack using the CENT2
core unit are not usable for 10 Gb Ethernet service units.
→ The support of 10 Gb Ethernet service units in the slot 9 and slot 15 of the
XMC25 R2 subrack using the CENT2 core unit will be available in a future
release.
Slot Slot Slot
1 11 21

S S S S S S S S S S C S S S S S S S S S S
U U U U U U U U U U U U U U U U U U U U U

a)

Slot Slot Slot Slot

1 11 13 21

S S S S S S S S S S C S C S S S S S S S S
U U U U U U U U U U U U U U U U U U U U U

b)

Figure 9: Slot concept of the XMC25 R2

Legend:

Copyright 2022 Hitachi Energy. All rights reserved. 28

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

a XMC25 R2 without core unit (CU) redundancy

core unit with single slot width
20 service units (SU)
b XMC25 R2 with core unit (CU) redundancy
core unit with single slot width
19 service units (SU)
The service unit ETE24 offers 24 interfaces towards the subscribers; other service units offer 4
to 16 interfaces towards the subscribers.
The units in the subrack are powered from the DC power supply (-48 VDC or -60 VDC nominal
voltage) via the backplane, and optionally via DUA25 (dual power interface). Each unit has its
own power converter, i.e. no dedicated power converter units are used. The optional dual power
supply unit DUA25 allows the powering of the XMC25 R2 subrack from 2 redundant primary
power supplies.
The COOL4 fan unit provides active cooling for the XMC25 R2 and implements external alarm
interfaces. Active cooling of the subrack allows to deploy any available core or service unit.
Without the COOL4 unit, i.e. with passive cooling only the following core and service units can
be used:
− SECU1F4,
− SECU1F8,
− NUSA1-F,
− ETO12-F, SABO1-F,
− SUSE2-F,
− VRX10-F,
− ETE24 1, SUP12, SABE1,
− SELI8, SATP8 1, STM14 1, SDSL8, ETAG1,
− SUPM1,
− ISDN4,
− VOIP1 1,
− VFTLX 1,
− TUDA1, TUGE1, TUEM1, TUXA1,
− IMAG1.

Please note:
The dual power supply unit DUA25 feeding up to 30 A requires active cooling.
→ It must only be operated in a subrack equipped with the optional fan unit
COOL4.

Please note:
The dual power supply unit DUA25 feeding up to 25 A can be operated without
active cooling.
The alarm unit ALMU4-F can be used in a passive cooling application to provide the external
alarm interfaces for the XMC25 R2.

2.1.1.2 XMC25
The XMC25 uses a 19-inch subrack with 21 slots, one or two core units and up to 20 or 19 ser-
vice units.
The XMC25 supports core and service units as listed in section 2.2 XMC20 Traffic Units (on
page 47).

1. Passive cooling is restricted to specific hardware releases. Refer to section 2.2 XMC20 Traffic Units (on
page 47).

Copyright 2022 Hitachi Energy. All rights reserved. 29

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The XMC25 allows to implement 1:1 equipment protection for the core unit. The slots for the
working core unit and the protecting core unit are slots 11 and 13, respectively. The slot concept
with and without redundancy is shown in Figure 10.

Please note:
The slot 13 of the XMC25 subrack is not usable for Ethernet service units.
Slot Slot Slot Slot Slot Slot
1 11 21 1 11 21

S S S S S S S S S S C S S S S S S S S S S S S S S S S S S S S C S S S S S S S S S
U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U

a) b)

Slot Slot Slot Slot Slot Slot Slot Slot

1 11 13 21 1 11 13 21

S S S S S S S S S S C S C S S S S S S S S S S S S S S S S S S C C S S S S S S S
U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U

c) d)

Figure 10: Slot concept of the XMC25

Legend:
a XMC25 without core unit (CU) redundancy
core unit with single slot width
20 service units (SU)
b XMC25 without core unit (CU) redundancy
core unit with double slot width
19 service units (SU)
c XMC25 with core unit (CU) redundancy
core unit with single slot width
19 service units (SU)
d XMC25 with core unit (CU) redundancy
core unit with double slot width
17 service units (SU)
The service unit ETE24 offers 24 interfaces towards the subscribers; other service units offer 4
to 16 interfaces towards the subscribers.
The units in the subrack are powered from the DC power supply (-48 VDC or -60 VDC nominal
voltage) via the backplane, and optionally via DUA25 (dual power interface). Each unit has its
own power converter, i.e. no dedicated power converter units are used. The optional dual power
supply unit DUA25 allows the powering of the XMC25 subrack from 2 redundant primary power
supplies.
The COOL4 fan unit provides active cooling for the XMC25 and implements external alarm
interfaces. Active cooling of the subrack allows to deploy any available core or service unit.
Without the COOL4 unit, i.e. with passive cooling only the following core and service units can
be used:
− COGE5-F,

Copyright 2022 Hitachi Energy. All rights reserved. 30

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− SECU1F4,
− SECU1F8,
− NUSA1-F,
− ETO12-F, SABO1-F,
− SUSE2-F,
− VRX10-F,
− ETE24 1, SUP12, SABE1,
− SELI8, SATP8 1, STM14 1, SDSL8, ETAG1,
− SUPM1,
− ISDN4,
− VOIP1 1,
− VFTLX 1,
− TUDA1, TUGE1, TUEM1, TUXA1,
− IMAG1.

Please note:
The dual power supply unit DUA25 feeding up to 30 A requires active cooling.
→ It must only be operated in a subrack equipped with the optional fan unit
COOL4.

Please note:
The dual power supply unit DUA25 feeding up to 25 A can be operated without
active cooling.
The alarm unit ALMU4-F can be used in a passive cooling application to provide the external
alarm interfaces for the XMC25.

2.1.1.3 XMC23
The XMC23 uses a rack-mountable 19-inch subrack with 8 slots, used with one or two core
units, and up to 6 or 7 of the service units.
The subrack is mounted horizontally into a 19-inch rack. Alternatively, the XMC23 can also be
mounted vertically, e.g. on a wall.
The same core units and service units as with the XMC25 are used; please refer to section 2.2
XMC20 Traffic Units (on page 47).
The XMC23 allows to implement 1:1 equipment protection for the core unit. The slots for the
working core unit and the protecting core unit are slots 11 and 13, as in the XMC25. The slot
concept with and without redundancy is shown in Figure 11.

Please note:
The slot 13 of the XMC23 subrack is not usable for Ethernet service units.

1. Passive cooling is restricted to specific hardware releases. Refer to section 2.2 XMC20 Traffic Units (on
page 47).

Copyright 2022 Hitachi Energy. All rights reserved. 31

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Slot Slot Slot Slot Slot Slot

7 11 14 7 11 14

S S S S C S S S S S S S C S S
U U U U U U U U U U U U U U U

a) b)

Slot Slot Slot Slot Slot Slot Slot

7 11 13 14 7 11 13

S S S S C S C S S S S S C C
U U U U U U U U U U U U U U

c) d)

Figure 11: Slot concept of the XMC23

Legend:
a XMC23 without core unit (CU) redundancy
core unit with single slot width
7 service units (SU)
b XMC23 without core unit (CU) redundancy
core unit with double slot width
6 service units (SU)
c XMC23 with core unit (CU) redundancy
core unit with single slot width
6 service units (SU)
d XMC23 with core unit (CU) redundancy
core unit with double slot width
4 service units (SU)
The units in the subrack are powered from the DC power supply (-48 VDC or -60 VDC nominal
voltage) via the backplane, and optionally via DUA23 (dual power interface). Each unit has its
own power converter, i.e. no dedicated power converter units are used. The optional dual power
supply unit DUA23 allows the powering of the XMC23 subrack from 2 redundant primary power
supplies.
The COOL6 fan unit provides the active cooling for the XMC23 and implements external alarm
interfaces. Active cooling of the subrack allows to deploy any available core or service unit.
Without the COOL6 unit, i.e. with passive cooling, only the following core and service units can
be used:
− COGE5-F,
− SECU1F4,
− SECU1F8,
− NUSA1-F,
− ETO12-F, SABO1-F,
− SUSE2-F,
− VRX10-F,
− ETE24 1, SUP12, SABE1,

Copyright 2022 Hitachi Energy. All rights reserved. 32

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− SELI8, SATP8 1, STM14 1, SDSL8, ETAG1,

− SUPM1,
− ISDN4,
− VOIP1 1,
− VFTLX 1,
− TUDA1, TUGE1, TUEM1, TUXA1,
− IMAG1.
The alarm unit ALMU6-F can be used in a passive cooling application to provide the external
alarm interfaces for the XMC23.

Please note:
Passive cooling with the horizontally mounted XMC23 subrack is not possible.
→ A horizontally mounted XMC23 subrack requires active cooling with a fan unit.

2.1.1.4 XMC22
The XMC22 uses a rack-mountable 19-inch subrack with 4 slots, used with one core unit, and
up to 3 of the service units.
The subrack is mounted horizontally into a 19-inch rack. Alternatively, the XMC22 can also be
mounted vertically, e.g. on a wall.
The XMC22 supports the core unit COGE5. The same service units as with the XMC25 are
used; please refer to section 2.2 XMC20 Traffic Units (on page 47).
The XMC22 supports no 1:1 equipment protection for the core unit.
Slot Slot Slot Slot
9 11 9 11

S S C S S S C
U U U U U U U

a) b)

Figure 12: Slot concept of the XMC22

Legend:
a XMC22 with core unit (CU) with single slot width
3 service units (SU)
b XMC22 with core unit (CU) with double slot width
2 service units (SU)
The units in the subrack are powered from the DC power supply (-48 VDC or -60 VDC nominal
voltage) via the backplane, and optionally via DUA23 (dual power interface). The DC power can
also be provided by the optional AC/DC power converter POAC1. Each unit has its own power
converter, i.e. no dedicated power converter units are used. The optional dual power supply unit
DUA23 allows the powering of the XMC22 subrack from 2 redundant primary power supplies.
The COOL8 fan unit provides the active cooling for the XMC22 and implements external alarm
interfaces. Active cooling of the subrack allows to deploy any available core or service unit.
Without the COOL8 unit, i.e. with passive cooling, only the following core and service units can
be used:

1. Passive cooling is restricted to specific hardware releases. Refer to section 2.2 XMC20 Traffic Units (on
page 47).

Copyright 2022 Hitachi Energy. All rights reserved. 33

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− COGE5-F,
− SECU1F4,
− SECU1F8,
− NUSA1-F,
− ETO12-F, SABO1-F,
− SUSE2-F,
− VRX10-F,
− ETE24 1, SUP12, SABE1,
− SELI8, SATP8 1, STM14 1, SDSL8, ETAG1,
− SUPM1,
− ISDN4,
− VOIP1 1,
− VFTLX 1,
− TUDA1, TUGE1, TUEM1, TUXA1,
− IMAG1.
The alarm unit ALMU8-F can be used in a passive cooling application to provide the external
alarm interfaces for the XMC22.

Please note:
Passive cooling with the horizontally mounted XMC22 subrack is not possible.
→ A horizontally mounted XMC22 subrack requires active cooling with a fan unit.

2.1.2 Mechanical Design

2.1.2.1 Subrack Construction

The XMC25 R2, XMC25, XMC23 and XMC22 subracks provide the mechanical packaging for
the units and the backplane with electrical connections to the bus structures and the power sup-
ply. The subracks are compact constructions with removable front covers. The covers provide
apertures so that the LED indicators on the unit fronts remain visible even with the front cover
installed. The XMC25 R2, the XMC25 and the XMC23 subracks are provided with a cable tray.
The XMC22 has a 19-inch adapter used for the mounting of the optional AC/DC power con-
verter POAC1.
The basic construction practice for the subracks and their auxiliary elements relies on the 19-
inch standard. Adapters are available for ETSI installations.
Illustrations of the subracks with and without front cover are provided in
• Figure 21: "XMC25 R2 and XMC25 with front cover" (on page 44), and Figure 22: "XMC25
R2 and XMC25 subrack (sample) and cable tray without front cover" (on page 44) (both for
XMC25 R2 and XMC25);
• Figure 24: "XMC23 with front cover (horizontal mounting)" (on page 46), and Figure 25:
"XMC23 subrack (sample) without front cover (horizontal mounting)" (on page 46) (both for
XMC23);
• Figure 26: "XMC22 with front cover (horizontal mounting)" (on page 47), and Figure 27:
"XMC22 subrack (sample) without front cover (horizontal mounting)" (on page 47) (both for
XMC22).

1. Passive cooling is restricted to specific hardware releases. Refer to section 2.2 XMC20 Traffic Units (on
page 47).

Copyright 2022 Hitachi Energy. All rights reserved. 34

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.1.2.2 XMC25 R2 and XMC25 Subrack

The main dimensions of the XMC25 R2 and XMC25 subracks and the auxiliary elements are
provided in Figure 13.
The total width, including mounting flanges for 19-inch mounting, of the XMC25 R2 and XMC25
subracks is 482.6 mm. The width of the subracks main body without the mounting flanges is
448.7 mm.

Rack

Heat deflection shield

2 HU (if required)

COOL4 as separate
1 HU unit

XMC25 R2 and
XMC25 subrack
(19 inch)
6 HU consists of mechanics
and backplane

DUA25 (optional)

2 HU
Cable tray (19 inch)

60.2 mm 241.6 mm

2.5 mm 304.3 mm

Figure 13: XMC25 R2 and XMC25 subrack design and main dimensions (side view)

Please note:
The standard heat deflection shield has a height of 2 HU. For subrack installations
with constricted room in a rack a heat deflection shield with a reduced height of 1
HU is available.

2.1.2.3 XMC23 Subrack

The main dimensions of the XMC23 subrack are provided in Figure 14.
The total width, including mounting flanges for 19-inch mounting, of the XMC23 subrack is 482.6
mm when mounted horizontally. The width of the subrack main body without the mounting
flanges is 443.0 mm.

Copyright 2022 Hitachi Energy. All rights reserved. 35

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Rack

XMC23 subrack
(19 inch horizontally
mounted)
4 HU consists of
(176.1 mm)
mechanics and
backplane

60.2 mm 241. 1 mm

2.0 mm 303.3 mm

Figure 14: XMC23 subrack design and main dimensions (side view)

2.1.2.4 XMC22 Subrack

The main dimensions of the XMC22 subrack are provided in Figure 15.
The total width, including mounting flanges for 19-inch mounting, of the XMC22 subrack is 482.6
mm when mounted horizontally. The width of the subrack main body without the mounting
flanges is 437.3 mm.

Rack

XMC22 subrack
2.2 HU (19 inch horizontally
(94.9 mm) mounted)
consists of mechanics
and backplane

60.2 mm 241. 1 mm

2.0 mm 303.3 mm

Figure 15: XMC22 subrack design and main dimensions (side view)

2.1.2.5 Plug-in Units

All the plug-in units of the XMC20 are designed for standard subracks of 6 HU and have the
same height, the same depth, and typically the same width (20.32 mm). The PCB size is 233 x
220 mm. The plug-in units fit into the XMC25 R2, XMC25, XMC23 and XMC22 subrack.

Please note:
There are units using the double width of the typical plug-in units:
→ Width 40.64 mm.
→ XMC20 units with double width:
- COGE5-F
- SECU1F4
- SECU1F8
- NUSA1-F

Copyright 2022 Hitachi Energy. All rights reserved. 36

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

- NUSA2
- ETO12-F
- SABO1-F
- VRX10-F
- ETE24
- SUSE2-F.
Two fixing screws secure the units plugged into the subrack. Two pull-out handles at the top
and the bottom of the front of the unit help you to insert the units into and remove the units from
the subrack.
A standardized connector system connects the signals of the units to the backplane. All units
have access to the -48V / -60V DC power supply voltage. Packet based units feature connec-
tors providing access to the 1 GbE star and/or to the 10 GbE star and to the subrack internal
control bus (CBUS). TDM based units as e.g. the SELI8, SDSL8, or SUPM1 have access to the
TDM bus (PBUS) and to the CBUS.
Front connectors are provided for traffic and control signal interfaces. The standard connector
for traffic signal interfaces provides a latching system that can be released without tools.
Fixing screw

Pull-out handle R1D

37900064

Unit and Traffic LEDs

Latching clips

Pull-out handle

Fixing screw

Figure 16: Plug-in unit with standard front connector (sample)

2.1.2.6 Auxiliary Units

A fan unit (COOL4) and a heat deflection shield for controlled air convection are available for
the XMC25 R2 and XMC25. The monitoring of the fan operation is integrated in the XMC25 R2
and XMC25 monitoring and alarm system.
In applications with passive cooling, i.e. without the COOL4 unit the optional alarm unit ALMU4-
F can be deployed. ALMU4-F offers the same external alarm interfaces as the COOL4.
The XMC25 R2 or XMC25 is powered from a single power supply (-48 VDC or -60 VDC). The
connector is placed on the backplane. With the optional DUA25 multi-connection device, the
XMC25 R2 or XMC25 supports dual power supply from primary power supplies (-48 VDC or -60
VDC). The DUA25 is incorporated in the XMC25 R2 or XMC25 subrack when installed. The
monitoring of the supplying batteries is integrated in the XMC25 R2 or XMC25 alarm system.

Copyright 2022 Hitachi Energy. All rights reserved. 37

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The XMC23 fan unit COOL6 is mounted into a special slot of the subrack. The COOL6 unit is
monitored by the core unit. The monitoring of the fan operation is integrated in the XMC23 moni-
toring and alarm system.
In applications with passive cooling, i.e. without the COOL6 unit the optional alarm unit ALMU6-
F can be deployed. ALMU6-F offers the same external alarm interfaces as the COOL6 (R3).
The XMC23 is powered from a single power supply (-48 VDC or -60 VDC). The connector is
placed on the backplane. With the optional DUA23 multi-connection device, the XMC23 sup-
ports dual power supply from primary power supplies (-48 VDC or -60 VDC). The connection
device is mounted on the XMC23 cable tray when installed.
The XMC22 fan unit COOL8 is mounted into a special slot of the subrack. The COOL8 unit is
monitored by the core unit. The monitoring of the fan operation is integrated in the XMC22 moni-
toring and alarm system.
In applications with passive cooling, i.e. without the COOL8 unit the optional alarm unit ALMU8-
F can be deployed. ALMU8-F offers the same external alarm interfaces as the COOL8 (R2).
The XMC22 is powered from a single power supply (-48 VDC or -60 VDC). The connector is
placed on the backplane. With the optional DUA23 multi-connection device, the XMC22 sup-
ports dual power supply from primary power supplies (-48 VDC or -60 VDC). The connection
device is mounted on the XMC22 19-inch adapter when installed.
The XMC22 can alternatively be powered from an mains power source. The AC/DC converter
POAC1, as part of the XMC22 AC power kit, provides the necessary -48 VDC voltage for the
subrack. The POAC1 unit is placed on the XMC22 19-inch adapter when installed.

2.1.2.7 Installation
The XMC25 R2 or XMC25 allows installation in 19-inch and ETSI racks. Four XMC25 R2 or
XMC25 subracks can be installed in a 7 feet high 19-inch rack.
The XMC23 allows installation in 19-inch and ETSI racks. The XMC23 is typically mounted hori-
zontally. Please refer to Figure 24: "XMC23 with front cover (horizontal mounting)" (on page 46)
for a view on a horizontally mounted XMC23 subrack.
Vertical mounting of the XMC23 subrack is not typical for rack installations. Hitachi Energy pro-
vides no installation material to support this type of installation. Vertical installation is typically
used with a wall mounting adapter.
The XMC22 can be installed in 19-inch racks. The XMC22 is typically mounted horizontally.
Please refer to Figure 26: "XMC22 with front cover (horizontal mounting)" (on page 47) for a
view on a horizontally mounted XMC22 subrack.
Vertical mounting of the XMC22 subrack can be done e.g. directly on a wall. Hitachi Energy pro-
vides no installation material to support this type of installation.

2.1.3 Internal Traffic Communication

2.1.3.1 XMC25 R2

Please note:
The core units COGE5, and COGE5-F, COGE7 and COGE7-F do not support the
40 GbE double star.
→ To access the double 40 GbE star you have to use the core unit CENT2.

Please note:
The core units COGE5, and COGE5-F, COGE7 and COGE7-F do not support the
10 GbE double star.
→ To access the double 10 GbE star you have to use the core unit CENT2.
The XMC25 R2 provides a set of bus systems in the backplane for the internal traffic transport:

Copyright 2022 Hitachi Energy. All rights reserved. 38

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• 40 GbE double star:

A double star architecture interconnecting independently slot 9 and slot 15 with 40 Gbit/s to
the core unit slot and 40 Gbit/s to the redundant core unit slot. Accordingly, each 40 GbE
star consists of 2 serial 40 Gbit/s Ethernet links.
The 40 GbE double star provides the internal Ethernet connections for the WAN port expan-
sion unit EXPU1.
• 10 GbE double star:
A double star architecture interconnecting independently every slot with 10 Gbit/s to the core
unit slot and 10 Gbit/s to the redundant core unit slot. Accordingly, each 10 GbE star con-
sists of 20 serial 10 Gbit/s Ethernet links, plus two 10 Gbit/s Ethernet point-to-point connec-
tions between the two core unit slots, which are used with core unit equipment protection
(see section 4.4 Protection Concept (on page 139)).
The 10 GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.
• 10 Gbit/s point-to-point connections:
There are additional 10 Gbit/s point-to-point connections between the service units in slot 4
and 6 and between service units in slot 18 and 20.
These connections can be used for equipment protection of service units, e.g. NUSA1.
• GbE double star:
A double star architecture interconnecting independently every slot with 1 Gbit/s to the core
unit slot and 1 Gbit/s to the redundant core unit slot. Accordingly, each GbE star consists of
20 serial Gbit/s Ethernet links, including a 1 Gbit/s Ethernet point-to-point connection
between the two core unit slots, which is used with core unit equipment protection (see sec-
tion 4.4 Protection Concept (on page 139)).
The GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.
• CBUS:
The CBUS contains signals used for the interworking of the units in a subrack, like control
signals, clock lines, chassis ground and power supply.
• PBUS:
The PBUS is a TDM bus offering a capacity of 128 x 2 Mbit/s for TDM traffic. The PBUS is
used in the TDM voice and data applications. The PBUS allows placement of any TDM ser-
vice unit in any of the slots 1 to 21 (except slot 11 which is reserved for the core unit), and
creation of cross connections between these TDM service units. For more details refer to
section 6.4.1 Architecture (on page 171).

Copyright 2022 Hitachi Energy. All rights reserved. 39

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

XMC25 R2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

CBUS
PBUS

GbE star
to slot 11

GbE star
to slot 13

10 GbE star
to slot 11

10 GbE star
to slot 13

10 Gb

40 GbE star
to slot 11

40 GbE star
to slot 13

Figure 17: XMC25 R2 internal bus systems

2.1.3.2 XMC25

Please note:
The core units COGE5, and COGE5-F, COGE7 and COGE7-F do not support the
10 GbE double star.
→ To access the double 10 GbE star you have to use the core unit CENT2.
The XMC25 provides a set of bus systems in the backplane for the internal traffic transport:
• 10 GbE double star:
A double star architecture interconnecting independently every slot with 10 Gbit/s to the core
unit slot and 10 Gbit/s to the redundant core unit slot. Accordingly, each 10 GbE star con-
sists of 20 serial 10 Gbit/s Ethernet links, plus two 10 Gbit/s Ethernet point-to-point connec-
tions between the two core unit slots, which are used with core unit equipment protection
(see section 4.4 Protection Concept (on page 139)).
The 10 GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.

Copyright 2022 Hitachi Energy. All rights reserved. 40

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• 10 Gbit/s point-to-point connections:

There are additional 10 Gbit/s point-to-point connections between the service units in slot 4
and 6 and between service units in slot 18 and 20.
These connections can be used for equipment protection of service units, e.g. NUSA1.
• GbE double star:
A double star architecture interconnecting independently every slot with 1 Gbit/s to the core
unit slot and 1 Gbit/s to the redundant core unit slot. Accordingly, each GbE star consists of
20 serial Gbit/s Ethernet links, including a 1 Gbit/s Ethernet point-to-point connection
between the two core unit slots, which is used with core unit equipment protection (see sec-
tion 4.4 Protection Concept (on page 139)).
The GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.
• CBUS:
The CBUS contains signals used for the interworking of the units in a subrack, like control
signals, clock lines, chassis ground and power supply.
• PBUS:
The PBUS is a TDM bus offering a capacity of 128 x 2 Mbit/s for TDM traffic. The PBUS is
used in the TDM voice and data applications. The PBUS allows placement of any TDM ser-
vice unit in any of the slots 1 to 21 (except slot 11 which is reserved for the core unit), and
creation of cross connections between these TDM service units. For more details refer to
section 6.4.1 Architecture (on page 171).

XMC25
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

CBUS
PBUS

GbE star
to slot 11

GbE star
to slot 13

10 GbE star
to slot 11

10 GbE star
to slot 13

10 Gb

Figure 18: XMC25 internal bus systems

Copyright 2022 Hitachi Energy. All rights reserved. 41

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.1.3.3 XMC23

Please note:
The core units COGE5, and COGE5-F, COGE7 and COGE7-F do not support the
10 GbE double star.
→ To access the double 10 GbE star you have to use the core unit CENT2.
The XMC23 provides basically the same set of bus systems in the backplane for the internal
traffic transport as the XMC25:
• 10 GbE double star:
A double star architecture interconnecting independently every slot with 10 Gbit/s to the core
unit slot and 10 Gbit/s to the redundant core unit slot. Accordingly, each 10 GbE star con-
sists of 7 serial 10 Gbit/s Ethernet links, plus two 10 Gbit/s Ethernet point-to-point connec-
tions between the two core unit slots, which are used with core unit equipment protection
(see section 4.4 Protection Concept (on page 139)).
The 10 GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.
• 10 Gbit/s point-to-point connections:
There are additional 10 Gbit/s point-to-point connections between service units in slot 7 and
9.
These connections can be used for equipment protection of service units, e.g. NUSA1.
• GbE double star:
A double star architecture interconnecting independently every slot with 1 Gbit/s to the core
unit slot and 1 Gbit/s to the redundant core unit slot. Accordingly, each GbE star consists of
7 serial Gbit/s Ethernet links, including a 1 Gbit/s Ethernet point-to-point connection between
the two core unit slots, which is used with core unit equipment protection (see section 4.4
Protection Concept (on page 139)).
The GbE double star can provide the internal Ethernet connections of the XMC20 Switch
and the external connections to stand alone bridge units.
• CBUS:
The CBUS contains signals used for the interworking of the units in a subrack, like control
signals, clock lines, chassis ground and power supply.
• PBUS:
The PBUS is a TDM bus offering a capacity of 128 x 2 Mbit/s for TDM traffic. The PBUS is
used in the TDM voice and data applications. The PBUS allows placement of any TDM ser-
vice unit in any of the slots 7 to 14 (except slot 11 which is reserved for the core unit), and
creation of cross connections between these TDM service units. For more details refer to
section 6.4.1 Architecture (on page 171).

Copyright 2022 Hitachi Energy. All rights reserved. 42

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

XMC23
7 8 9 10 11 12 13 14

CBUS
PBUS

GbE star
to slot 11

GbE star
to slot 13

10 GbE star
to slot 11

10 GbE star
to slot 13

10 Gb

Figure 19: XMC23 internal bus systems

2.1.3.4 XMC22
The XMC22 bus systems in the backplane are a subset of the XMC25 bus system:
• GbE star:
A star architecture interconnecting independently every slot with 1 Gbit/s to the core unit slot.
Accordingly, each GbE star consists of 3 serial Gbit/s Ethernet links.
The GbE star can provide the internal Ethernet connections of the XMC20 Switch and the
external connections to stand alone bridge units.
• CBUS:
The CBUS contains signals used for the interworking of the units in a subrack, like control
signals, clock lines, chassis ground and power supply.
• PBUS:
The PBUS is a TDM bus offering a capacity of 128 x 2 Mbit/s for TDM traffic. The PBUS is
used in the TDM voice and data applications. The PBUS allows placement of any TDM ser-
vice unit in any of the slots 9 to 12 (except slot 11 which is reserved for the core unit), and
creation of cross connections between these TDM service units. For more details refer to
section 6.4.1 Architecture (on page 171).

XMC22
9 10 11 12

CBUS
PBUS

GbE star
to slot 11

Figure 20: XMC22 internal bus systems

2.1.4 Views

2.1.4.1 XMC25 R2 and XMC25

The XMC25 R2 and XMC25 have front access for all signal and power cables. A removable
cover closes the front of the subrack. The cable tray below the subrack allows for an easy instal-
lation of the signal cables.

Copyright 2022 Hitachi Energy. All rights reserved. 43

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The construction of the subrack and the cable connections provide Faraday cage like EMC
characteristics, provided that the front cover is installed and that the signal cables have been
installed and shielded as instructed.

Figure 21: XMC25 R2 and XMC25 with front cover

Figure 22: XMC25 R2 and XMC25 subrack (sample) and cable tray without front cover

Copyright 2022 Hitachi Energy. All rights reserved. 44

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 23: XMC25 R2 and XMC25 installation with COOL4 and heat deflection shields

2.1.4.2 XMC23
The XMC23 has front access for all signal and power cables. A removable cover closes the
front of the subrack. The cables are led to the right side of the horizontally mounted subrack and
are fixed to a cable flange as shown in Figure 25.
As for the XMC25 R2 or XMC25, the construction of the subrack and the cable connections pro-
vide Faraday cage like EMC characteristics, provided that the front cover is installed (as shown
in Figure 24) and that the signal cables have been installed and shielded as instructed.

Copyright 2022 Hitachi Energy. All rights reserved. 45

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 24: XMC23 with front cover (horizontal mounting)

Figure 25: XMC23 subrack (sample) without front cover (horizontal mounting)

2.1.4.3 XMC22
The XMC22 has front access for all signal and power cables. A removable cover closes the
front of the subrack. The cables are led to the right side of the horizontally mounted subrack.
As for the XMC25 R2 or XMC25, the construction of the subrack and the cable connections pro-
vide Faraday cage like EMC characteristics, provided that the front cover is installed (as shown
in Figure 26) and that the signal cables have been installed and shielded as instructed.

Copyright 2022 Hitachi Energy. All rights reserved. 46

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 26: XMC22 with front cover (horizontal mounting)

Figure 27: XMC22 subrack (sample) without front cover (horizontal mounting)

2.2 XMC20 Traffic Units

There are eight different groups of XMC20 units applicable to XMC25 R2, XMC25, XMC23,
XMC22:
• Core units with access to the GbE star:
− CENT2 (refer to section 2.2.1 Core Unit CENT2 (on page 51)).
− COGE7 and COGE7-F (refer to section 2.2.2 Core Unit COGE7 and COGE7-F (on
page 54)).
− COGE5 and COGE5-F (refer to section 2.2.3 Core Unit COGE5 and COGE5-F (on
page 57)).
• Core units with access to the 10 GbE star:
− CENT2 (refer to section 2.2.1 Core Unit CENT2 (on page 51)).
• Service units with access to the GbE star:

Please note:
The service units ETO12, ETE24, SUP12, SABO1, SABE1, SUSE2, VRX10,
NUSA1, NUSA2 use the GbE star access only, when the subrack is operated with
a COGE5 or COGE7 core unit. When the subrack is operated with a CENT2 core
unit the service units access the 10 GbE star for the transport of user traffic.

Copyright 2022 Hitachi Energy. All rights reserved. 47

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− SECU1-4, SECU1F4, SECU1-8 and SECU1F8, if enabled by a DIP-switch (refer to sec-

tion 2.2.5 Encryption Unit SECU1-4, SECU1F4, SECU1-8 and SECU1F8 (on page 61)).
− ETO12 and ETO12-F (refer to section 2.2.6 Ethernet Service Units ETO12 and ETO12-F
(on page 64)). The GbE star is only used with the core unit COGE5 or COGE7.
− ETE24 (refer to section 2.2.7 Ethernet Service Unit ETE24 (on page 65)).
− SUP12 (refer to section 2.2.8 Ethernet Service Unit SUP12 (on page 67)).
− SABO1 and SABO1-F (refer to section 2.2.11 Ethernet Service Units SABO1 and
SABO1-F (on page 71)).
− SABE1 (refer to section 2.2.12 Ethernet Service Unit SABE1 (on page 73)).
− SUSE2 and SUSE2-F (refer to section 2.2.9 Ethernet service unit SUSE2 and SUSE2-F
(on page 68)).
− VRX10 and VRX10-F (refer to section 2.2.10 Ethernet Service Units VRX10 and VRX10-
F (on page 70)).
− STM14 (refer to section 2.2.14 SDH and EoS Service Unit STM14 (on page 76)).
− NUSA1 and NUSA1-F (refer to section 2.2.15 SDH and EoS Service Unit NUSA1 and
NUSA1-F (on page 77)).
− NUSA2 (refer to section 2.2.16 SDH and EoS Service Unit NUSA2 (on page 79)).
− SATP8 (refer to section 2.2.18 E1 Circuit Emulation Service Unit SATP8 (on page 81)).
− VOIP1 (refer to section 2.2.20 Media Gateway Unit VOIP1 (on page 84)).
− ETAG1 (refer to section 2.2.13 Ethernet Service Unit ETAG1 (on page 74)).
• Service units with access to the 10 GbE star:

Please note:
The slot 1, slot 8 to slot 15, and slot 21 of the XMC25 R2 subrack using the CENT2
core unit are not usable for 10 Gb Ethernet service units.
→ The support of 10 Gb Ethernet service units in the slot 9 and slot 15 of the
XMC25 R2 subrack using the CENT2 core unit will be available in a future
release.
− ETO12 and ETO12-F (refer to section 2.2.6 Ethernet Service Units ETO12 and ETO12-F
(on page 64)).
− ETE24 (refer to section 2.2.7 Ethernet Service Unit ETE24 (on page 65)).
− SUP12 (refer to section 2.2.8 Ethernet Service Unit SUP12 (on page 67)).
− SABO1 and SABO1-F (refer to section 2.2.11 Ethernet Service Units SABO1 and
SABO1-F (on page 71)).
− SABE1 (refer to section 2.2.12 Ethernet Service Unit SABE1 (on page 73)).
− SUSE2 and SUSE2-F (refer to section 2.2.9 Ethernet service unit SUSE2 and SUSE2-F
(on page 68)).
− VRX10 and VRX10-F (refer to section 2.2.10 Ethernet Service Units VRX10 and VRX10-
F (on page 70)).
− NUSA1 and NUSA1-F (refer to section 2.2.15 SDH and EoS Service Unit NUSA1 and
NUSA1-F (on page 77)).
− NUSA2 (refer to section 2.2.16 SDH and EoS Service Unit NUSA2 (on page 79)).
• Service units with access to the 40 GbE star:
− EXPU1 (refer to section 2.2.4 WAN Port Expansion Unit EXPU1 (on page 60)).
• Service units with access to the PBUS (TDM bus):
− SUPM1 (refer to section 2.2.22 PSTN Service Units SUPM1 and SUPM2 (on page 87)).
− SUPM2 (refer to section 2.2.22 PSTN Service Units SUPM1 and SUPM2 (on page 87)).
− ISDN4 (refer to section 2.2.23 ISDN-BA Voice Service Unit ISDN4 (on page 88)).
− TUEM1 (refer to section 2.2.25 E&M Voice Service Unit TUEM1 (on page 90)).
− TUXA1 (refer to section 2.2.27 FXO Voice Service Unit TUXA1 (on page 92)).

Copyright 2022 Hitachi Energy. All rights reserved. 48

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− TUDA1 (refer to section 2.2.28 Data Service Unit TUDA1 (on page 93)).
− TUGE1 (refer to section 2.2.29 E0 Service Unit TUGE1 (on page 95)).
− SELI8 (refer to section 2.2.17 E1 Service Unit SELI8 (on page 80)).
− SDSL8 (refer to section 2.2.19 TDM SHDSL Service Unit SDSL8 (on page 83)).
− STM14 (refer to section 2.2.14 SDH and EoS Service Unit STM14 (on page 76)).
− NUSA1 and NUSA1-F (refer to section 2.2.15 SDH and EoS Service Unit NUSA1 and
NUSA1-F (on page 77)).
− NUSA2 (refer to section 2.2.16 SDH and EoS Service Unit NUSA2 (on page 79)).
− SATP8 (refer to section 2.2.18 E1 Circuit Emulation Service Unit SATP8 (on page 81)).
− VOIP1 (refer to section 2.2.20 Media Gateway Unit VOIP1 (on page 84)).
− VFTLX (refer to section 2.2.21 Voice Frequency Processing Unit VFTLX (on page 86)).
− ETAG1 (refer to section 2.2.13 Ethernet Service Unit ETAG1 (on page 74)).
• Service units with no backplane traffic access:
− SECU1-4, SECU1F4, SECU1-8 and SECU1F8, if disabled by a DIP-switch (refer to sec-
tion 2.2.5 Encryption Unit SECU1-4, SECU1F4, SECU1-8 and SECU1F8 (on page 61)).
− IMAG1 (refer to section 2.2.26 Magneto Line Voice Service Unit IMAG1 (on page 91)).
• Auxiliary units:
− DUA25 (XMC25 R2 and XMC25, refer to section 2.3.1 Dual Power Input Unit DUA25
(XMC25 R2 and XMC25) (on page 96)).
− DUA23 (XMC23 and XMC22, refer to section 2.3.2 Dual Power Input Unit DUA23
(XMC23 and XMC22) (on page 96)).
− COOL4 (XMC25 R2 and XMC25, refer to section 2.3.3 Fan Unit COOL4 (XMC25 R2 and
XMC25) (on page 97)).
− COOL6 (XMC23 only, refer to section 2.3.4 Fan Unit COOL6 (XMC23) (on page 98)).
− COOL8 (XMC22 only, refer to section 2.3.5 Fan Unit COOL8 (XMC22) (on page 99)).
− ALMU4-F (XMC25 R2 and XMC25, refer to section 2.3.6 Alarm Unit ALMU4-F (XMC25
R2 and XMC25) (on page 100)).
− ALMU6-F (XMC23 only, refer to section 2.3.7 Alarm Unit ALMU6-F (XMC23) (on
page 100)).
− ALMU8-F (XMC22 only, refer to section 2.3.8 Alarm Unit ALMU8-F (XMC22) (on
page 101)).
− ETMP1 (refer to section 2.3.9 Air Flow Optimization Unit ETMP1 (on page 102)).
The Figure 28 shows the implementation of the core unit and the different service units in the
XMC25 R2, XMC25, XMC23 or XMC22. The traffic flow is from the network side to the customer
side and vice versa.
Further below you will find a view and a description of the features of each of the XMC20 units.

Copyright 2022 Hitachi Energy. All rights reserved. 49

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Customer XMC25 R2 or XMC25 or XMC23 or XMC22 Network

side side
Ethernet WAN Port 10GbE (4)

40 GbE
Expansion Unit,
40 GbE (1)
EXPU1

10GbE (4)
Ethernet (12) Ethernet Service Unit, Core Unit
ETO12, ETO12-F CENT2 GbE (1)

Ethernet (24) Ethernet Service Unit, 10GbE (4)

ETE24 Core Unit
CENT2 GbE (1)
Ethernet (12) Ethernet Service Unit, (redundancy)
SUP12
Ethernet (12) Ethernet Service Unit, 10GbE (2)
VRX10, VRX10-F Core Unit
COGE5, COGE5-F GbE (3)
SHDSL (24) SHDSL (EFM) Service Unit,
SUSE2, SUSE2-F Core Unit 10GbE (2)

Ethernet (12) Ethernet Service Unit, COGE5, COGE5-F GbE (3)

SABO1, SABO1-F (redundancy)

Ethernet (12) Ethernet Service Unit,

SABE1 SHDSL (EFM) SHDSL (24)
Service Unit,
SUSE2, SUSE2-F

10 GbE

1 GbE
E1 (8) Circuit Emulation Service Unit,
SATP8 STM-16 (2)
SDH and EoS STM-4 (2)
Ethernet Service Unit, Service Unit
Ethernet (4)
ETAG1 NUSA1, NUSA1-F
GbE (4)
SHDSL (8) SHDSL (TDM) Service Unit
STM-16 (2)
SDSL8
STM-4 (2)
E1 (8) E1 G.703 Service Unit SDH and EoS
Service Unit
PBUS

SELI8 E1 (48)
NUSA2
FXS voice (16) FXS voice Service Unit GbE (4)
SUPM1
FXS voice (64) FXS voice Service Unit STM-4 (2)
SDH and EoS STM-1 (2)
SUPM2 Service Unit
ISDN voice (4) ISDN-BA voice Service Unit Circuit Emulation STM14
GbE (4)
ISDN4 Service Unit,
SATP8 E1 G.703
Data (4) Data Service Unit, E1 (8)
Ethernet (1) TUDA1 Service Unit
Ethernet Service Unit, SELI8
E&M voice (8) E&M voice Service Unit,
ETAG1
TUEM1 SHDSL (TDM) SHDSL (8)
FXO voice Service Unit, Service Unit
FXO voice (12)
TUXA1 SIP Voice over IP SDSL8
Service Unit,
E0 (8) E0 G.703 Service Unit, codirectional VOIP1 10GbE (4)
Encryption Unit
TUGE1
SECU1-4, SECU1F4
E0 (2) E0 G.703 Service Unit, contradirectional Voice Frequency
TUGE1 Processing Service Unit,
VFTLX Encryption Unit 10GbE (8)
Magneto (8) Magneto line Service Unit
IMAG1 SECU1-8, SECU1F8

Figure 28: Unit implementation in the XMC25 R2, XMC25, XMC23 and XMC22

Please note:
The XMC22 does not support a redundant core unit.

Copyright 2022 Hitachi Energy. All rights reserved. 50

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.1 Core Unit CENT2

Figure 29: CENT2 unit view

The CENT2 is the 1-slot wide core unit of the XMC25 R2, XMC25 and XMC23. It must be oper-
ated in an actively cooled XMC20 subrack.
The core unit CENT2 comprises functions for the whole network element (NE) and for the core
unit itself:
Main NE functions:
• Management and control of the XMC20 subrack and all plug-in units,
• Database to store management information,
• Control of the system operation.
• Monitoring of the system performance.
• PDH and Ethernet synchronization functions.
• Local management Ethernet interface.
• Management communication, including routing functions.
− Support of SSH for the management communication.
− Support of SNMP for the management communication.
• Access to the alarm interfaces on the fan or alarm unit.
Main core unit functions:
• Ethernet VLAN Bridge as function of the XMC20 Switch between the CENT2 Ethernet front
ports and the Ethernet service unit ports.

Copyright 2022 Hitachi Energy. All rights reserved. 51

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• MPLS-TP Transport as function of the XMC20 Switch between the CENT2 Ethernet front
ports and the Ethernet service unit ports.
• Five Ethernet traffic front ports, four SFP+ based 10 GbE interfaces and one 10/100/
1000BASE-T interface.
• Support of PTP for electrical and optical Ethernet traffic front interfaces.
− PTP Boundary Clock
− PTP Ordinary Clock
− PTP Transparent Clock
• Support of RSTP (802.1D-2004, compatible with STP) for electrical and optical Ethernet traf-
fic front interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Configurable egress queue sizes using a customer specific CPS.
The core unit features 1:1 equipment protection with switch-over time below 50 ms (for details
refer to section 4.4.2 Equipment Protection of the Core Unit (on page 140)).
The interfaces at the front panel of the core unit CENT2 are shown in Figure 30.

R1A
12345678

ESI/ESO synchronization
interfaces

ETR synchronization interfaces

Electrical 10/100/1000BASE-T interface

(local management port)

Electrical 10/100/1000BASE-T interface

(traffic interface)

SFP/SFP+ module cages:

Optical GbE or 10GbE interfaces
(traffic interfaces)

Figure 30: CENT2 interfaces

Copyright 2022 Hitachi Energy. All rights reserved. 52

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

CENT2 comprises four SFP+ (Small Form factor Pluggable) cages which can be equipped with
industry standard electrical or optical 1000BASE-xx transceivers (SFP modules), or optical
10GBASE-xx transceivers (SFP+ modules) and used as traffic interfaces. The SFP or SFP+
modules are not included with the CENT2 unit by default.
One electrical 10/100/1000BASE-T interfaces is also usable as traffic interface.
For the VLAN Bridge function all five traffic interfaces can be configured to be used as access
port, trunk port, trunk with native VLAN port or general port, individually per port.
For the MPLS-TP Transport function all five traffic interfaces can be configured to be used as
Pseudo Wire Access Circuit port or as MPLS-TP physical port or as MPLS-TP logical port (sub-
interface), individually per port.
Four of the five Ethernet ports support the PTP protocol and can be used as slave or master
PTP ports.
In addition, the core unit also offers an Ethernet port for the local management access (electrical
10/100BASE-TX).
The CENT2 unit offers synchronization I/O signals (two symmetrical clock inputs and two sym-
metrical clock outputs, 120 Ohm, 2048kHz). Two inputs and one output are used for PDH refer-
ence clock signals on the XMC20. One input and one output are used for SDH reference clock
signals.
The ETR interface provides a PPS output to synchronize external equipment.

Please note:
The “time of day” input/output and the “pulse per second” input interfaces will be
supported in a future release.
The CENT2 has four LEDs for the indication of unit and traffic failures.

Copyright 2022 Hitachi Energy. All rights reserved. 53

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.2 Core Unit COGE7 and COGE7-F

Figure 31: COGE7 (left) and COGE7-F (right) unit view

The COGE7 is the 1-slot wide core unit of the XMC25, XMC23 and XMC22. It must be operated
in an actively cooled XMC20 subrack.
The COGE7-F is the 2-slot wide core unit of the XMC25, XMC23 and XMC22. It can be oper-
ated in actively and passively cooled XMC20 subracks.
COGE7 and COGE7-F are functionally identical. In the following the term “COGE7” is thus used
to name the core units COGE7 and COGE7-F.
The core unit COGE7 comprises functions for the whole network element (NE) and for the core
unit itself:
Main NE functions:
• Management and control of the XMC20 subrack and all plug-in units,
• Database to store management information,
• Control of the system operation.
• Monitoring of the system performance.
• PDH and Ethernet synchronization functions.
• Local management Ethernet interface.
• Management communication, including routing functions.
− Support of SSH for the management communication.
− Support of SNMP for the management communication.
• Access to the alarm interfaces on the fan or alarm unit.
Main core unit functions:

Copyright 2022 Hitachi Energy. All rights reserved. 54

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Ethernet VLAN Bridge as function of the XMC20 Switch between the COGE7 Ethernet front
ports and the Ethernet service unit ports.
• MPLS-TP Transport as function of the XMC20 Switch between the COGE7 Ethernet front
ports and the Ethernet service unit ports.
• Five Ethernet traffic front ports, two SFP+ based 10 GbE interfaces, two SFP based 1 GbE
interfaces and one 10/100/1000BASE-T interface.
• Support of PTP for electrical and optical Ethernet traffic front interfaces.
− PTP Boundary Clock
− PTP Ordinary Clock
− PTP Transparent Clock
• Support of RSTP (802.1D-2004, compatible with STP) for electrical and optical Ethernet traf-
fic front interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Configurable egress queue sizes using a customer specific CPS.
The core unit features 1:1 equipment protection (for details refer to section 4.4.2 Equipment
Protection of the Core Unit (on page 140)).
The interfaces at the front panel of the core unit COGE7 are shown in Figure 32.

Copyright 2022 Hitachi Energy. All rights reserved. 55

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

R1B R1B
37900374 37900374

Synchronization interfaces

Electrical 10/100BASE-TX interface

(local management port)

Electrical 10/100/1000BASE-T interface

(traffic interface)

SFP module cages:

Optical GbE interfaces
(traffic interfaces)

SFP/SFP+ module cages:

Optical GbE or 10GbE interfaces
(traffic interfaces)

Figure 32: COGE7 (left) and COGE7-F (right) interfaces

COGE7 comprises two SFP+ (Small Form factor Pluggable) cages which can be equipped with
industry standard electrical or optical 1000BASE-xx transceivers (SFP modules), or optical
10GBASE-xx transceivers (SFP+ modules) and used as traffic interfaces. The SFP or SFP+
modules are not included with the COGE7 unit by default.
COGE7 comprises two SFP (Small Form factor Pluggable) cages which can be equipped with
industry standard electrical or optical 1000BASE-xx transceivers (SFP modules) and used as
traffic interfaces. The SFP modules are not included with the COGE7 unit by default.
One electrical 10/100/1000BASE-T interface is also usable as traffic interface.
For the VLAN Bridge function all five traffic interfaces can be configured to be used as access
port, trunk port, trunk with native VLAN port or general port, individually per port.
For the MPLS-TP Transport function all five traffic interfaces can be configured to be used as
Pseudo Wire Access Circuit port or as MPLS-TP physical port or as MPLS-TP logical port (sub-
interface), individually per port.
Four of the five Ethernet ports support the PTP protocol and can be used as slave or master
PTP ports.

Copyright 2022 Hitachi Energy. All rights reserved. 56

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

In addition, the core unit also offers an Ethernet port for the local management access (electrical
10/100BASE-TX).
The COGE7 unit offers synchronization I/O signals (two symmetrical clock inputs and two sym-
metrical clock outputs, 120 Ohm, 2048kHz). Two inputs and one output are used for PDH refer-
ence clock signals on the XMC20. One input and one output are used for SDH reference clock
signals.
The COGE7 has four LEDs for the indication of unit and traffic failures.

2.2.3 Core Unit COGE5 and COGE5-F

Figure 33: COGE5 (left) and COGE5-F (right) unit view

The COGE5 is the 1-slot wide core unit of the XMC25, XMC23 and XMC22. It must be operated
in an actively cooled XMC20 subrack.
The COGE5-F is the 2-slot wide core unit of the XMC25, XMC23 and XMC22. It can be oper-
ated in actively and passively cooled XMC20 subracks.
COGE5 and COGE5-F are functionally identical. In the following the term “COGE5” is thus used
to name the core units COGE5 and COGE5-F.
The core unit COGE5 comprises functions for the whole network element (NE) and for the core
unit itself:
Main NE functions:
• Management and control of the XMC20 subrack and all plug-in units,
• Database to store management information,
• Control of the system operation.

Copyright 2022 Hitachi Energy. All rights reserved. 57

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Monitoring of the system performance.

• PDH and Ethernet synchronization functions.
• Local management Ethernet interface.
• Management communication, including routing functions.
− Support of SSH for the management communication.
− Support of SNMP for the management communication.
• Access to the alarm interfaces on the fan or alarm unit.
Main core unit functions:
• Ethernet VLAN Bridge as function of the XMC20 Switch between the COGE5 Ethernet front
ports and the Ethernet service unit ports.
• MPLS-TP Transport as function of the XMC20 Switch between the COGE5 Ethernet front
ports and the Ethernet service unit ports.
• Five Ethernet traffic front ports, two SFP+ based 10 GbE interfaces and three 10/100/
1000BASE-T interfaces.
• Support of PTP for electrical and optical Ethernet traffic front interfaces.
− PTP Boundary Clock
− PTP Ordinary Clock
− PTP Transparent Clock
• Support of RSTP (802.1D-2004, compatible with STP) for electrical and optical Ethernet traf-
fic front interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Configurable egress queue sizes using a customer specific CPS.
The core unit features 1:1 equipment protection (for details refer to section 4.4.2 Equipment
Protection of the Core Unit (on page 140)).
The interfaces at the front panel of the core unit COGE5 are shown in Figure 34.

Copyright 2022 Hitachi Energy. All rights reserved. 58

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

R1B R1B
37900374 37900374

Synchronization
interfaces

Electrical 10/100BASE-TX interface

(local management port)

Electrical 10/100/1000BASE-T
interfaces
(traffic interface)

SFP/SFP+ module cages:

Optical 1 GbE or 10 GbE interfaces
(traffic interface)

Figure 34: COGE5 (left) and COGE5-F (right) interfaces

COGE5 comprises two SFP+ (Small Form factor Pluggable) cages which can be equipped with
industry standard electrical or optical 1000BASE-xx transceivers (SFP modules), or optical
10GBASE-xx transceivers (SFP+ modules) and used as traffic interfaces. The SFP or SFP+
modules are not included with the COGE5 unit by default.
Three electrical 10/100/1000BASE-T interfaces are also usable as traffic interfaces.
For the VLAN Bridge function all five traffic interfaces can be configured to be used as access
port, trunk port, trunk with native VLAN port or general port, individually per port.
For the MPLS-TP Transport function all five traffic interfaces can be configured to be used as
Pseudo Wire Access Circuit port or as MPLS-TP physical port or as MPLS-TP logical port (sub-
interface), individually per port.
Four of the five Ethernet ports support the PTP protocol and can be used as slave or master
PTP ports.
In addition, the core unit also offers an Ethernet port for the local management access (electrical
10/100BASE-TX).
The COGE5 unit offers synchronization I/O signals (two symmetrical clock inputs and two sym-
metrical clock outputs, 120 Ohm, 2048kHz). Two inputs and one output are used for PDH refer-

Copyright 2022 Hitachi Energy. All rights reserved. 59

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

ence clock signals on the XMC20. One input and one output are used for SDH reference clock
signals.
The COGE5 has four LEDs for the indication of unit and traffic failures.

2.2.4 WAN Port Expansion Unit EXPU1

Figure 35: EXPU1 unit view

The EXPU1 is a 1-slot wide WAN port expansion unit of the XMC20. It must be operated in an
actively cooled XMC20 subrack.
It provides four SFP/SFP+ based 1 Gbit/s / 10 Gbit/s Ethernet ports and one QSFP+ based 40
Gbit/s Ethernet port. The SFP+ or QSFP+ modules are not included with the EXPU1 unit by
default.
The unit is connected to the CENT2 core unit via the double 40 GbE star of the XMC25 R2 sub-
rack.
The EXPU1 unit provides the following functions:
• Front ports usable as WAN ports.
• The EXPU1 unit front ports are connected via the 40 GbE star to the switching circuit of the
CENT2 core unit.
• The front ports can be operated as Ethernet traffic ports or as MPLS-TP ports.

Copyright 2022 Hitachi Energy. All rights reserved. 60

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Support of RSTP (802.1D-2004, compatible with STP) for optical Ethernet traffic front inter-
faces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Support of Synchronous Ethernet including ESMC messages.
• Support of VLAN based PTP in Ordinary/Boundary and Transparent Clock mode.
• No port based PTP boundary clock mode supported.
• Maximum eight 1 GbE / 10 GbE ports per XMC25 R2 subrack (2 units).
• Aggregate throughput rate up to 40 Gbit/s (upstream and downstream) at frame sizes < 9194
bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
The EXPU1 has two LEDs for unit and traffic failure indication.

2.2.5 Encryption Unit SECU1-4, SECU1F4, SECU1-8 and SECU1F8

Figure 36: SECU1-4 (left) and SECU1F4 (right) unit view

Copyright 2022 Hitachi Energy. All rights reserved. 61

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 37: SECU1-8 (left) and SECU1F8 (right) unit view

The SECU1-4 and SECU1-8 are the 1-slot wide encryption units of the XMC25 R2, XMC25,
XMC23 and XMC22. They must be operated in an actively cooled XMC20 subrack.
The SECU1F4 and SECU1F8 are the 2-slot wide encryption units of the XMC25 R2, XMC25,
XMC23 and XMC22. They can be operated in actively and passively cooled XMC20 subracks.
SECU1-4 and SECU1F4 are functionally identical, SECU1-8 and SECU1F8 are functionally
identical. In the following the term “SECU1” is used to name the encryption units SECU1-4,
SECU1F4, SECU1-8 and SECU1F8. Where certain features or characteristics apply to a spe-
cific encryption unit only, the SECU1-4, SECU1F4, SECU1-8 or SECU1F8 is named explicitly.
The encryption unit SECU1 provides the following main features:
• The SECU1 unit plugged in a XMC20 subrack is powered from the subrack.
• The SECU1 unit provides a TRNG (True Random Number Generator) realized with a QRNG
(Quantum Random Number Generator).
• The SECU1 unit has two LEDs for the indication of unit and traffic failures.
• The SECU1 unit is managed either
− via the backplane Gb Ethernet connection to the core unit(s), if the front management
port is disabled via DIP-switch, or
− via the front management port (electrical Ethernet 10/100/1000BASE-T interface), if the
front management port is enabled via DIP-switch.
• The SECU1 unit provides one (SECU1-4 and SECU1F4) or two (SECU1-8 and SECU1F8)
functional units.
Each functional unit provides the following functions (if managed via the backplane Gb Ethernet
connection):
• Four SFP+ (Small Form factor Pluggable) cages which can be equipped with industry stan-
dard optical 1000BASE-xx transceivers (SFP modules), or optical 10GBASE-xx transceivers

Copyright 2022 Hitachi Energy. All rights reserved. 62

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

(SFP+ modules). The SFP or SFP+ modules are not included with the SECU1 unit by
default.
• Two encryption engines per functional unit.
• Two bidirectional Ethernet streams can be encrypted and unencrypted.
− The unencrypted port of an encryption engine is connected to a local MPLS-TP port or a
local MPLS-TP subinterface (VLAN based) of a core unit or WAN port expansion unit.
− The encrypted port of an encryption engine provides the WAN connection.
• AES-256 GCM encryption mode per traffic flow.
• MPLS tunnel configuration via UNEM and DIRAC servers.
• Master key generation via DIRAC server, acting as key management server.
• 2048 keys per encryption engine, i.e. 1024 encrypted LSPs with two master keys each per
engine to arbitrary endpoints.
• Management channel between local and remote SECU1 units.
• Transparency for OAM messages.
• Packet delay compensation for PTP.
• Access to the XMC20 Switch only for management traffic. No user traffic accesses the
XMC20 Switch.
• Tamper protection of sensitive signals and data with mechanical shields on the boards com-
ponent and solder sides.
• CLI based management access to SECU1.
If the SECU1 unit is managed via the front management port the following items differ from the
above functional unit functions:
• Manual configuration of the MPLS tunnels via CLI.
• Manual configuration of the master keys via CLI.
• No management access via the XMC20 Switch.
• No subrack internal management access.

Copyright 2022 Hitachi Energy. All rights reserved. 63

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.6 Ethernet Service Units ETO12 and ETO12-F

Figure 38: ETO12 (left) and ETO12-F (right) unit view

Please note:
The service units ETO12 and SABO1 use the same hardware unit named ETO12.

Please note:
The service units ETO12-F and SABO1-F use the same hardware unit named
ETO12-F.
The ETO12 is a 1-slot wide Ethernet service unit of the XMC20. It has 12 SFP-based optical or
electrical 100 Mbit/s or 1000 Mbit/s Ethernet interfaces. The unit must be operated in an actively
cooled XMC20 subrack.
The ETO12-F is a 2-slot wide Ethernet service unit of the XMC20. It can be operated in actively
and passively cooled XMC20 subracks.
ETO12 and ETO12-F are functionally identical. In the following the term “ETO12” is thus used to
name the Ethernet service units ETO12 and ETO12-F.
The ETO12 unit is connected to the core unit via the double GbE star and the double 10 GbE
star.
The ETO12 unit provides the following functions:
• 12 SFP-based Ethernet interfaces for the connection of standard Ethernet equipment.
• Electrical or optical 100 Mbit/s or 1000 Mbit/s Ethernet port; connector type, transport
medium and reach according to the plugged SFP module.

Copyright 2022 Hitachi Energy. All rights reserved. 64

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Hardware ready for synchronous Ethernet.

• Maximum 240 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 84 ports per XMC23 subrack (7 units).
• Maximum 36 ports per XMC22 subrack (3 units).
• Ethernet switch with VLAN support as part of the XMC20 Switch between the units Ethernet
front ports and other Ethernet service unit and core unit ports.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical and optical Ethernet front
interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate throughput rate up to 10 Gbit/s (upstream and downstream) at frame sizes < 1522
bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The ETO12 has two LEDs for unit and traffic failure indication.

2.2.7 Ethernet Service Unit ETE24

Figure 39: ETE24 unit view

The ETE24 is a 2-slot wide Ethernet service unit of the XMC20. It provides 24 electrical Ether-
net interfaces 10/100/1000BASE-T. The unit is connected to the core unit via the double GbE

Copyright 2022 Hitachi Energy. All rights reserved. 65

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

star and the double 10 GbE star. The unit with HW release R1x must be operated in an actively
cooled XMC20 subrack. The unit with HW release R2A or newer can be operated in actively
and passively cooled XMC20 subracks.
The ETE24 unit provides the following functions:
• 24 electrical interfaces 10/100/1000BASE-T for the connection of standard Ethernet equip-
ment.
• Hardware ready for synchronous Ethernet.
• Maximum 240 ports per XMC25 R2 or XMC25 subrack (10 units).
• Maximum 72 ports per XMC23 subrack (3 units).
• Maximum 24 ports per XMC22 subrack (1 unit).
• Ethernet switch with VLAN support as part of the XMC20 Switch between the units Ethernet
front ports and other Ethernet service unit and core unit ports.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical Ethernet front interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate throughput rate up to 10 Gbit/s (upstream and downstream) at frame sizes < 1522
bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The ETE24 has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 66

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.8 Ethernet Service Unit SUP12

Figure 40: SUP12 unit view

Please note:
The service units SUP12 and SABE1 use the same hardware unit named SUP12.
The SUP12 is a 1-slot wide Ethernet service unit of the XMC20. It provides 12 electrical Ether-
net interfaces 10/100/1000BASE-T supporting power over Ethernet. The unit is connected to the
core unit via the double GbE star and the double 10 GbE star. It can be operated in actively and
passively cooled XMC20 subracks.
The SUP12 unit provides the following functions:
• 12 electrical interfaces 10/100/1000BASE-T for the connection of standard Ethernet equip-
ment.
• Power over Ethernet with up to 30 W per port (PoE+). Up to 84 W of accumulated power
budget for all PoE ports.
• Isolation for indoor PoE applications.
• Hardware ready for synchronous Ethernet.
• Maximum 240 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 84 ports per XMC23 subrack (7 units).
• Maximum 36 ports per XMC22 subrack (3 units).
• Ethernet switch with VLAN support as part of the XMC20 Switch between the units Ethernet
front ports and other Ethernet service unit and core unit ports.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical Ethernet front interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 67

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate throughput rate up to 10 Gbit/s (upstream and downstream) at frame sizes < 1522
bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The SUP12 has two LEDs for unit and traffic failure indication.

2.2.9 Ethernet service unit SUSE2 and SUSE2-F

Figure 41: SUSE2 (left) and SUSE2-F (right) unit view

The SUSE2 is a 1-slot wide service unit of the XMC20. It has 24 SHDSL EFM subscriber inter-
faces. The unit must be operated in an actively cooled XMC20 subrack.
The SUSE2-F is a 2-slot wide Ethernet service unit of the XMC20. It can be operated in actively
and passively cooled XMC20 subracks.
SUSE2 and SUSE2-F are functionally identical. In the following the term “SUSE2” is thus used
to name the service units SUSE2 and SUSE2-F.
The SUSE2 unit is connected to the core unit via the double GbE star and the double 10 GbE
star.
The SUSE2 unit provides the following functions:
• 24 SHDSL EFM interfaces according ITU-T G.991.2, Annexes A, B, F and G.

Copyright 2022 Hitachi Energy. All rights reserved. 68

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Handshaking procedures according to ITU-T G.994.1.

• EFM compliance according to IEEE 802.3-2012 section five.
• Line codes TCPAM 16, TCPAM 32 and TCPAM 64.
• Maximum user data rate per line interface 11.4 Mbit/s.
• Line aggregation 1 to 4 lines, user data rate up to 22.78 Mbit/s.
• Support of different rates on aggregated lines.
• Support of the trunk application.
• Network element timing forwarding in the trunk application from LT to NT.
• Configurable user bandwidth.
• Configurable power backoff.
• Maximum 480 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 168 ports per XMC23 subrack (7 units).
• Maximum 72 ports per XMC23 subrack (3 units).
• Ethernet switch with VLAN support as part of the XMC20 Switch between the units SHDSL
front ports and other Ethernet service unit and core unit ports.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical Ethernet front interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate throughput rate up to 136 Mbit/s (upstream and downstream).
• Ethernet frame sizes from 42 to 2024 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The SUSE2 has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 69

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.10 Ethernet Service Units VRX10 and VRX10-F

Figure 42: VRX10 (left) and VRX10-F (right) unit view

The VRX10 is a 1-slot wide Ethernet service unit of the XMC20. It has 12 SFP-based optical or
electrical 100 Mbit/s or 1000 Mbit/s Ethernet interfaces. The unit must be operated in an actively
cooled XMC20 subrack.
The VRX10-F is a 2-slot wide Ethernet service unit of the XMC20. It can be operated in actively
and passively cooled XMC20 subracks.
VRX10 and VRX10-F are functionally identical. In the following the term “VRX10” is thus used to
name the Ethernet service units VRX10 and VRX10-F.
The VRX10 unit is connected to the core unit via the double GbE star and the double 10 GbE
star.
The VRX10 unit provides the following functions:
• 12 SFP-based Ethernet interfaces for the connection of standard Ethernet equipment.
• Electrical or optical 100 Mbit/s or 1000 Mbit/s Ethernet port; connector type, transport
medium and reach according to the plugged SFP module.
• Hardware ready for synchronous Ethernet.
• Maximum 240 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 84 ports per XMC23 subrack (7 units).
• Maximum 36 ports per XMC22 subrack (3 units).
• IPv4 routing with up to 16 virtual router instances.
• OSPF routing and static routing.

Copyright 2022 Hitachi Energy. All rights reserved. 70

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Up to 256 virtual router interfaces, untagged, priority tagged or VLAN tagged.

• Up to 32 loopback interfaces.
• DHCP relay agent.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Wire speed packet forwarding.
• IP MTU size up to 1500 bytes. Hardware ready for MTU size up to 9000 bytes.
• Security features:
− Rate limiter for the virtual router interfaces.
• 1:1 equipment protection. 1
The VRX10 has two LEDs for unit and traffic failure indication.

2.2.11 Ethernet Service Units SABO1 and SABO1-F

Figure 43: SABO1 (left) and SABO1-F (right) unit view

Please note:
The service units ETO12 and SABO1 use the same hardware unit named ETO12.

1. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.

Copyright 2022 Hitachi Energy. All rights reserved. 71

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Please note:
The service units ETO12-F and SABO1-F use the same hardware unit named
ETO12-F.
The SABO1 is a 1-slot wide Ethernet service unit of the XMC20. It has 12 SFP-based optical or
electrical 100 Mbit/s or 1000 Mbit/s Ethernet interfaces. The unit must be operated in an actively
cooled XMC20 subrack.
The SABO1-F is a 2-slot wide Ethernet service unit of the XMC20. It can be operated in actively
and passively cooled XMC20 subracks.
SABO1 and SABO1-F are functionally identical. In the following the term “SABO1” is thus used
to name the Ethernet service units SABO1 and SABO1-F.
The SABO1 unit is connected to the core unit via the double GbE star and the double 10 GbE
star.
The SABO1 unit provides the following functions:
• 12 SFP-based Ethernet interfaces for the connection of standard Ethernet equipment.
• Electrical or optical 100 Mbit/s or 1000 Mbit/s Ethernet port; connector type, transport
medium and reach according to the plugged SFP module.
• Hardware ready for synchronous Ethernet.
• Maximum 240 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 84 ports per XMC23 subrack (7 units).
• Maximum 36 ports per XMC22 subrack (3 units).
• Local Ethernet switch with VLAN support.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical and optical Ethernet front
interfaces.
• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate switching capacity up to 12 Gbit/s at frame sizes < 1522 bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The SABO1 has two LEDs for unit and traffic failure indication.

Please note:
The bridge on the SABO1 unit is not part of the XMC20 Switch.
→ The SABO1 bridge accesses the XMC20 Switch via the backplane 1 Gbit/s or
10 Gbit/s Ethernet link as an external port.

Copyright 2022 Hitachi Energy. All rights reserved. 72

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.12 Ethernet Service Unit SABE1

Figure 44: SABE1 unit view

Please note:
The service units SUP12 and SABE1 use the same hardware unit named SUP12.
The SABE1 is a 1-slot wide Ethernet service unit of the XMC20. It provides 12 electrical Ether-
net interfaces 10/100/1000BASE-T supporting power over Ethernet. The unit is connected to the
core unit via the double GbE star and the double 10 GbE star. It can be operated in actively and
passively cooled XMC20 subracks.
The SABE1 unit provides the following functions:
• 12 electrical interfaces 10/100/1000BASE-T for the connection of standard Ethernet equip-
ment.
• Power over Ethernet with up to 30 W per port (PoE+). Up to 84 W of accumulated power
budget for all PoE ports.
• Isolation for indoor PoE applications.
• Hardware ready for synchronous Ethernet.
• Maximum 240 ports per XMC25 R2 or XMC25 subrack (20 units).
• Maximum 84 ports per XMC23 subrack (7 units).
• Maximum 36 ports per XMC22 subrack (3 units).
• Local Ethernet switch with VLAN support.
• Support of RSTP (802.1D-2004, compatible with STP) for electrical Ethernet front interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 73

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Support of VLAN QoS with Class of Service (CoS) handling (802.1Q): 8 CoS by eight priority
queues, with strict priority scheduling or weighted round robin (WRR) scheduling per queue.
• Aggregate switching capacity up to 12 Gbit/s at frame sizes < 1522 bytes.
• MAC frame sizes from 64 to 9216 bytes.
• Security features:
− Rate limiter for subscriber traffic.
• Configurable egress queue sizes using a customer specific CPS.
The SABE1 has two LEDs for unit and traffic failure indication.

Please note:
The bridge on the SABE1 unit is not part of the XMC20 Switch.
→ The SABE1 bridge accesses the XMC20 Switch via the backplane 1 Gbit/s or
10 Gbit/s Ethernet link as an external port.

2.2.13 Ethernet Service Unit ETAG1

Figure 45: ETAG1 unit view

The ETAG1 is a 1-slot wide Ethernet service unit of the XMC20. It is a versatile networking unit
with the main purpose of connecting Ethernet LANs over TDM links. It provides 4 electrical
Ethernet interfaces 10/100BASE-T and accesses the PBUS with a maximum capacity of 16 x
P12. The unit provides also access to the GbE star. It can be operated in actively and passively
cooled XMC20 subracks.
The ETAG1 unit provides the following functions:

Copyright 2022 Hitachi Energy. All rights reserved. 74

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• 4 Ethernet LAN front interfaces:

− 10/100Base-TX.
− Bridge port type (access/trunk) user configurable.
• Up to 64 TDM WAN interfaces on the PBUS:
− Bandwidth per interface 1x64 kbit/s up to 2048 kbit/s, with multilink PPP up to the total
WAN bandwidth.
− Total bandwidth 8x2 Mbit/s or 16x2 Mbit/s depending on unit mode.
− PPP/HDLC user configurable.
− Multilink PPP.
− Bridge port type (access/trunk) user configurable.
• Virtual interface:
− Selective routing per VLAN.
− Inter-VLAN routing.
− Connection between bridged and routed network segments.
• Bridge:
− Transparent MAC bridging.
− VLAN aware MAC bridging.
− RSTP (STP).
− Multiple bridge instances.
• IP router:
− Static routing.
− OSPF routing.
− RIP routing.
− Virtual router redundancy protocol, VRRP.
• QoS functions:
− 4 TX queues per interface.
− Strict priority scheduling.
• 1:1 equipment protection.

Please note:
The bridge on the ETAG1 unit is not part of the XMC20 Switch.
→ The ETAG1 bridge accesses the XMC20 Switch via the backplane Gbit/s Ether-
net link as an external port.

Copyright 2022 Hitachi Energy. All rights reserved. 75

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.14 SDH and EoS Service Unit STM14

Figure 46: STM14 unit view

The STM14 is a 1-slot wide SDH uplink service unit of the XMC20. It provides 2 STM-4/STM-1
dual speed and 2 STM-1 single speed ports and 4 10/100/1000BASE-T ports for the Ethernet
over SDH (EoS) application. STM14 accesses the PBUS with a maximum capacity of 67 x P12
and also connects to the Gb-Ethernet star. The unit with HW release R1x must be operated in
an actively cooled XMC20 subrack. The unit with HW release R2A or newer can be operated in
actively and passively cooled XMC20 subracks.
The STM14 unit can be configured as an SDH access system with termination and add/drop
functionality from STM-4 and STM-1 trunks. The interfaces can be used as aggregate inter-
faces, or as tributary interfaces for the access to subtended network elements. The interfaces
are implemented on STM14 with four SFP cages.
Ethernet traffic from the front Ethernet ports or from the core unit is transported over up to four
Ethernet over SDH (EoS) channels. Two of the four EoS channels are shared with the connec-
tions to the Gb-Ethernet star.
The STM14 unit implements also the synchronous equipment timing source (SETS) for the unit.
The STM14 unit provides the following functions:
• 2 STM-4/STM-1 dual speed ports, STM-4 with optical SFP modules, STM-1 with optical or
electrical SFP modules.
• 2 STM-1 single speed ports, with optical or electrical SFP modules.
• SDH cross connect for 18x18 AU-4, 33x33 TU-3 and 693x693 TU-12.
• Access to the PBUS with up to 67 P12 signals.
• Four 10/100/1000BASE-T Ethernet ports used for the Ethernet over SDH (EoS) application.

Copyright 2022 Hitachi Energy. All rights reserved. 76

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• EoS framing procedure GFP according ITU-T G.7041.

• Virtual concatenation according to ITU-T G.783.
• Link capacity adjustment (LCAS) scheme according to ITU-T G.7042.
• Synchronous equipment timing source (SETS) with local oscillator.
• Multiplex section protection on the unit.
• Subnetwork connection protection between any virtual channels on the unit.
• 1:1 equipment protection.
• Performance monitoring according to ITU-T G.826.

Please note:
The Eos links on the STM14 unit are not part of the XMC20 Switch.
→ The XMC20 Switch accesses one of the EoS links via the backplane Gbit/s
Ethernet link as an external port.
The STM14 has two LEDs for unit- and traffic related failure indication.

2.2.15 SDH and EoS Service Unit NUSA1 and NUSA1-F

Figure 47: NUSA1 (left) and NUSA1-F (right) unit view

The NUSA1 is a 1-slot wide SDH uplink service unit of the XMC20. It provides 2 STM-16/STM-4
dual speed and 2 STM-4/STM-1 dual speed ports and 4 10/100/1000BASE-T ports for the
Ethernet over SDH (EoS) application. NUSA1 accesses the PBUS with a maximum capacity of
64 x P12 and also connects to the Gb-Ethernet star. The unit must be operated in an actively
cooled XMC20 subrack.

Copyright 2022 Hitachi Energy. All rights reserved. 77

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The NUSA1-F is a 2-slot wide SDH and EoS service unit of the XMC20. It can be operated in
actively and passively cooled XMC20 subracks.
NUSA1 and NUSA1-F are functionally identical. In the following the term “NUSA1” is thus used
to name the SDH and EoS service units NUSA1 and NUSA1-F.
The NUSA1 unit can be configured as an SDH access system with termination and add/drop
functionality from STM-16, STM-4 and STM-1 trunks. The interfaces can be used as aggregate
interfaces or as tributary interfaces for the access to subtended network elements. The inter-
faces are implemented on NUSA1 with four SFP cages.
Ethernet traffic from the front Ethernet ports or from the XMC20 Switch is transported over up to
32 Ethernet over SDH (EoS) channels.
The NUSA1 unit implements also the synchronous equipment timing source (SETS) for the unit.
The NUSA1 unit provides the following functions:
• 2 STM-16/STM-4 dual speed ports with optical SFP modules.
• 2 STM-4/STM-1 dual speed ports, STM-4 with optical SFP modules, STM-1 with optical or
electrical SFP modules.
• SDH cross connect for 125x125 AU-4, 48x48 TU-3 and 1261x1261 TU-12.
• Access to the PBUS with up to 64 P12 signals.
• Four 10/100/1000BASE-T Ethernet ports used for the Ethernet over SDH (EoS) application.
• Up to 32 EoS channels.
• EoS framing procedure GFP according ITU-T G.7041.
• Virtual concatenation according to ITU-T G.783.
• Link capacity adjustment (LCAS) scheme according to ITU-T G.7042.
• Synchronous equipment timing source (SETS) with local oscillator.
• Multiplex section protection on the unit or with a protecting unit in a dedicated subrack slot.
• Subnetwork connection protection between any virtual channels on the unit.
• 1:1 equipment protection.
• Performance monitoring according to ITU-T G.826.
The NUSA1 has two LEDs for unit- and traffic related failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 78

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.16 SDH and EoS Service Unit NUSA2

Figure 48: NUSA2 unit view

The NUSA2 is a 2-slot wide SDH uplink service unit of the XMC20. It provides 2 STM-16/STM-4
dual speed and 2 STM-4/STM-1 dual speed ports, 4 10/100/1000BASE-T ports for the Ethernet
over SDH (EoS) application and 48 E12 ports for the SDH transport. NUSA2 accesses the
PBUS with a maximum capacity of 64 x P12 and also connects to the Gb-Ethernet star. The unit
must be operated in an actively cooled XMC20 subrack.
The NUSA2 unit can be configured as an SDH access system with termination and add/drop
functionality from STM-16, STM-4 and STM-1 trunks. The interfaces can be used as aggregate
interfaces or as tributary interfaces for the access to subtended network elements. The inter-
faces are implemented on NUSA2 with four SFP cages.
Ethernet traffic from the front Ethernet ports or from the XMC20 Switch is transported over up to
32 Ethernet over SDH (EoS) channels.
PDH traffic from the front E12 ports is transported transparently via VC-12 over SDH.
The NUSA2 unit implements also the synchronous equipment timing source (SETS) for the unit.
The NUSA2 unit provides the following functions:
• 2 STM-16/STM-4 dual speed ports with optical SFP modules.
• 2 STM-4/STM-1 dual speed ports, STM-4 with optical SFP modules, STM-1 with optical or
electrical SFP modules.
• SDH cross connect for 125x125 AU-4, 48x48 TU-3 and 1309x1309 TU-12.
• Access to the PBUS with up to 64 P12 signals.
• 48 E12 (G.703) ports used for the transparent PDH transport over SDH application.

Copyright 2022 Hitachi Energy. All rights reserved. 79

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Four 10/100/1000BASE-T Ethernet ports used for the Ethernet over SDH (EoS) application.
• Up to 32 EoS channels.
• EoS framing procedure GFP according ITU-T G.7041.
• Virtual concatenation according to ITU-T G.783.
• Link capacity adjustment (LCAS) scheme according to ITU-T G.7042.
• Synchronous equipment timing source (SETS) with local oscillator.
• Multiplex section protection on the unit or with a protecting unit in a dedicated subrack slot.
• Subnetwork connection protection between any virtual channels on the unit.
• 1:1 equipment protection.
• Performance monitoring according to ITU-T G.826.
The NUSA2 has two LEDs for unit- and traffic related failure indication.

2.2.17 E1 Service Unit SELI8

Figure 49: SELI8 unit view

The SELI8 is a 1-slot wide E1 (2048 kbit/s) service unit of the XMC20. It provides 8 E1 (2048
kbit/s) ports according to ITU-T G.703 / G.704. The unit can be operated in actively and pas-
sively cooled XMC20 subracks.
The SELI8 is connected to other TDM units as e.g. SDSL8 or SUPM1 via the backplane of the
XMC20 giving access to TDM based services.
It supports TDM voice and data services.
The SELI8 unit provides the following functions:

Copyright 2022 Hitachi Energy. All rights reserved. 80

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• 8 E1 ports (8 x 2048 kbit/s according to ITU-T G.703).

• 120 Ω symmetrical and 75 Ω asymmetrical line impedances.
• Frame alignment and multiframe alignment according to ITU-T G.704.
• Transparent handling of 2048 kbit/s signals or termination of n x 64 kbit/s frame structure.
• Access to the TDM bus in the XMC20 and cross connection for PDH P12 and P0 signals.
• Diagnostic loop activation: Loop 1, 1A and 2.
• Performance monitoring according to ITU-T G.826.
The SELI8 has two LEDs for unit- and traffic related failure indication.

2.2.18 E1 Circuit Emulation Service Unit SATP8

Figure 50: SATP8 unit view

The SATP8 unit is a 1-slot wide circuit emulation service over packet (CESoP) unit for the
XMC20. SATP8 provides up to 64 Pseudo Wires towards the packet network with a total capac-
ity of 8 x 2048 kbit/s. The unit provides also 8 E1 front ports. In total up to 64 Pseudo Wires and
8 E1 ports access the TDM bus (PBUS) on the backplane of the XMC20 subrack.
The unit with HW release R1x must be operated in an actively cooled XMC20 subrack. The unit
with HW release R2A or newer can be operated in actively and passively cooled XMC20 sub-
racks.
The SATP8 unit maps TDM based data traffic into packet based Pseudo Wires. It accesses
P0_nc (n x 64 kbit/s) and P12 (2048 kbit/s) voice and data signals via PBUS from any other
TDM unit accessing the PBUS.

Copyright 2022 Hitachi Energy. All rights reserved. 81

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The Pseudo Wires are connected to the GbE packet bus on the backplane of the XMC20 sub-
rack.
The SATP8 unit provides the following functions:
• 8 structure agnostic Pseudo Wires (8 x 2048 kbit/s), or
• 64 structure aware Pseudo Wires (64 x N x 64 kbit/s),
• 8 E1 TDM trunk ports (8 x 2048 kbit/s according to ITU-T G.703),
• 120 Ω symmetrical and 75 Ω asymmetrical line impedances,
• Frame alignment and multiframe alignment according to ITU-T G.704,
• Transparent handling of 2048 kbit/s signals or termination of n x 64 kbit/s frame structure,
• Access to the TDM bus in the XMC20 and cross connection for PDH P12 and P0 signals.
• Diagnostic loop activation,
• TDM pattern generator and analyzer for bit error rate tests and round trip delay measure-
ments,
• Performance monitoring according to ITU-T G.826,
• Front panel access for the E1 ports. One shielded cable is connected to the front panel. It
carries all 8 subscriber lines,
• Support of SAToP (Structure Agnostic TDM over Packet) service,
• Support of CESoPSN (Circuit Emulation Service over Packet Switched Networks),
• Support of CESoETH (Circuit Emulation Service over Ethernet, MEF8), structure agnostic
and structure aware,
• Adaptive and synchronous clock recovery modes for all Pseudo Wires.
The SATP8 has two LEDs for unit- and traffic related failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 82

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.19 TDM SHDSL Service Unit SDSL8

Figure 51: SDSL8 unit view

The SDSL8 unit is a 1-slot wide SHDSL (TDM) service unit for the XMC20. It has 8 SHDSL
interfaces towards the subscriber CPEs or to another SDSL8 unit (trunk mode) and is con-
nected to the TDM bus on the backplane of the XMC20 subrack. It can be operated in actively
and passively cooled XMC20 subracks.
SDSL8 is used for SHDSL according to ITU-T G.991.2.
The SDSL8 unit provides the following functions:
• 8 SHDSL interfaces according to
− ITU-T, G.991.2, Annex B (SHDSL in European networks).
• Support of data rates up to 2’048 kbit/s.
• Support of pair bonding (4-wire mode).
• Support of the following applications:
− Transparent 2 Mbit/s client link.
− Structured 2 Mbit/s client link.
− Fractional 2 Mbit/s client link.
− n x 64 kbit/s data link.
− Fractional n x 64 kbit/s data link.
− Trunk application.
• Support of X.21 interfaces (on CPE).
• Support of V.35 and V.36 interfaces (on CPE).
• Support of Ethernet interfaces (on CPE).

Copyright 2022 Hitachi Energy. All rights reserved. 83

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Support of E1 interfaces (on CPE).

• Support of regenerators.
• Handshaking procedures according to G.994.1.
• Remote power feeding for CPEs.
• DSL test loops.
The SDSL8 has two LEDs for unit and traffic failure indication.

2.2.20 Media Gateway Unit VOIP1

Figure 52: VOIP1 hardware unit view

Please note:
The service units VOIP1 and VFTLX use the same hardware unit named VOIP1.
The VOIP1 unit acts as a SIP media gateway for voice over IP for PSTN and ISDN-BA user
ports. The unit with HW release up to R1C must be operated in an actively cooled XMC20 sub-
rack. The unit with HW release R1D or newer can be operated in actively and passively cooled
XMC20 subracks.
VOIP1 plays the role of a user agent in the SIP architecture and communicates with SIP call
servers. POTS and ISDN-BA signaling is terminated and packetized to SIP. The VOIP1 unit
converts TDM based voice traffic into IP packets. It accesses PSTN (FXS and FXO, POTS) and
ISDN Basic-Rate Access (BA) services via PBUS from the SUPM1, SUPM2 (PSTN FXS),
TUXA1 (PSTN FXO) and ISDN4 (ISDN-BA) units.
The IP data signal is connected to the core unit via the double GbE star.
The VOIP1 unit provides the following functions:

Copyright 2022 Hitachi Energy. All rights reserved. 84

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Up to 1216 PSTN FXS or FXO subscribers,

• Up to 304 ISDN-BA subscribers,
• Up to 20 ISDN-PRA ports,
• Up to 96 MFC-R2 ports,
• Up to 200 active voice channels (the VOIP1 unit supports up to 80 active voice channels
when using the G.729A codec. The G.711 codec is used for the remainder of the channels
up to 200),
• G.711 codec and support of silence suppression,
• G.729A codec and support of silence suppression,
• Traffic handling capacity of up to 9’750 BHCA,
• Inband transport of modem- and Fax-data with the G.711 codec,
• Fax relay service according to T.38,
• Transport of 64 kbit/s clear channel data,
• DTMF relay according to RFC 2833,
• The SIP protocol is used for setting up / tearing down the connection between a TDM based
voice channel and an IP based channel,
• The SIP protocol is used for the conversion of PSTN and ISDN signaling into SIP messages
and vice versa,
• IP traffic transport via the GbE star on the backplane of the XMC20 subrack to/from the core
unit,
• IP QoS with DSCP control for control and media paths,
• VLAN tagging according to 802.1Q for control and media paths,
• Priority tagging according to 802.1p for control and media paths,
• RTP transport protocol for voice and data,
• RTCP support for maintenance data collection,
• 1:1 equipment protection,
• DTMF for CLIP,
• Session Timer,
• Overlap Dialing,
• Private Extension according to RFC 3325 (IMS adaptation).
The VOIP1 unit has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 85

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.21 Voice Frequency Processing Unit VFTLX

Figure 53: VFTLX unit view

Please note:
The service units VOIP1 and VFTLX use the same hardware unit named VOIP1.
The VFTLX unit acts as a voice frequency processing unit. For each bidirectional channel the
VFTLX unit provides two echo cancelers, eliminating the echo coming from the subscriber con-
nected to the near end linecard, and eliminating the echo coming from the subscriber connected
to the far end linecard.
The unit with HW release up to R1C must be operated in an actively cooled XMC20 subrack.
The unit with HW release R1D or newer can be operated in actively and passively cooled
XMC20 subracks.
The VFTLX unit provides the following functions:
• Up to 208 voice frequency processes,
• two echo cancelers per voice frequency process for PSTN subscribers,
• transparent forwarding of CAS,
• 1:1 equipment protection.
The VFTLX unit has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 86

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.22 PSTN Service Units SUPM1 and SUPM2

Figure 54: SUPM1 (left) and SUPM2 (right) unit view

The SUPM1 and SUPM2 units are 1-slot wide service units of the XMC20 offering PSTN FXS
voice user ports. This type of user ports is also called 2-wire analog interface, or a/b-interface,
or POTS port.
The SUPM1 unit can be operated in actively and passively cooled XMC20 subracks 1.
The SUPM2 unit must be operated in actively cooled XMC20 subracks.
The PSTN units are connected to a P12 transport unit (STM14, NUSA1, NUSA2, SELI8,
SDSL8) via the PBUS in the backplane of the XMC20.
The SUPM1 offers 16 user ports, the SUPM2 unit offers 64 user ports.
The SUPM1 and SUPM2 units provide the following common functions:
• PSTN user ports according to ITU-T Q.552.
• BORSCHT functionality:
− Battery feed.
− Overvoltage protection.
− Ringing injection.
− Supervision.
− Codec.
− Hybrid.
− Testing.

1. When operating the SUPM1 unit in a passively cooled subrack the loop current is limited to 23.5 mA.

Copyright 2022 Hitachi Energy. All rights reserved. 87

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Voice impedances configurable for different countries and applications.

• Input and output level configuration.
• V5CAS operation mode (internal communication).
• Onboard ringing generator.
• Onboard line-test function.
• Thermal management.
• Protection against equipment damage caused by faulty installation of cables.
The SUPM1 and SUPM2 units have two LEDs for unit and traffic failure indication.

2.2.23 ISDN-BA Voice Service Unit ISDN4

Figure 55: ISDN4 unit view

The ISDN4 unit is a 1-slot wide service unit of the XMC20. It has 4 ISDN-BA user ports. The unit
can be operated in actively and passively cooled XMC20 subracks.
The ISDN4 unit is connected to the IP gateway unit VOIP1 via the PBUS in the backplane of the
XMC20.
The ISDN unit provides the following functions:
• 4 ISDN-BA user ports according to ETSI TS 102 080,
• Line code 2B1Q according to ETSI TS 102 080 Annex A,
• Remote powering of NT1,
• Performance monitoring of the access digital section,
• Performance grading of the access digital section,

Copyright 2022 Hitachi Energy. All rights reserved. 88

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Onboard line-test function,

• Diagnostic loop activation: Loop 1 and 2,
• Front side shutdown button and shutdown indication LED,
• Thermal management,
• Protection against equipment damage caused by faulty installation of cables,
• Front panel access. One shielded cable is connected to the front panel. It carries all 4 sub-
scriber lines.
The ISDN4 has two LEDs for unit and traffic failure indication.

2.2.24 Voice Frequency Filter Box FIL16

Figure 56: FIL16 unit view

The FIL16 unit is voice frequency high voltage line filter box for 19-inch rack mounting. The box
has a height of 1 HU. It provides 16 2-wire line interfaces and is connected to the FXS voice
service unit SUPM1 or SUPM2 of the XMC20.
The XMC20 unit provides the following main functions:
• High voltage common mode filtering.
• Operates in the voice frequency band with low insertion loss.
• Low ringing voltage loss.
• One front connector towards the line, one front connector towards the voice service unit.
• Passive filtering, no powering required.
The FIL16 unit is mounted outside the XMC20 subrack, i.e. it is directly mounted into a 19-inch
rack.

Copyright 2022 Hitachi Energy. All rights reserved. 89

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.25 E&M Voice Service Unit TUEM1

Figure 57: TUEM1 unit view

The TUEM1 unit is a 1-slot wide service unit of the XMC20. It has 8 E&M user ports. Each E&M
user port consists of one 2-wire or 4-wire voice port and two E&M signaling ports. The unit can
be operated in actively and passively cooled XMC20 subracks.
The main applications of the TUEM1 unit are:
− Inter-exchange connections, supporting E&M interface types I to V.
− Terminal equipment connections, e.g. for party line subscriber sets or modems for data
over voice transmission.
TUEM1 is connected to a P12 transport unit (STM14, NUSA1, NUSA2, SELI8, SDSL8) via the
PBUS in the backplane of the XMC20.
The TUEM1 unit provides the following functions:
• 8 analog voice interfaces with a telephony bandwidth of 300 Hz to 3.4 kHz, configurable to 2-
wire or 4-wire access mode, ITU-T G.711.
• 16 E&M signaling interfaces, where each voice channel offers 2 E&M signaling channels.
• Voice conferences with participants from the TUEM1 unit or any voice circuit available in
XMC20:
− Up to 10 conferences per unit.
− Up to 17 participants per conference.
− Up to 32 participants per unit.
• Conference type:
− Multipoint-to-multipoint.

Copyright 2022 Hitachi Energy. All rights reserved. 90

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

− Point-to-multipoint.
• 1:1 equipment protection.
• 1+1 linear trail protection (LTP).
• 1+1 subnetwork connection protection with inherent monitoring (SNC/I).
• Performance monitoring.
• Maintenance functions:
− Test signal insertion, per user port and conference participant.
− Out of service, per user port and conference participant.
− Loops, voice and signaling front -to-front loop and back-to-back loop.
The TUEM1 has two LEDs for unit and traffic failure indication.

2.2.26 Magneto Line Voice Service Unit IMAG1

Figure 58: IMAG1 unit view

The IMAG1 unit is a 1-slot wide service unit of the XMC20. It has 8 magneto line user ports. The
unit can be operated in actively and passively cooled XMC20 subracks.
The main application of the IMAG1 unit is the conversion of the 2-wire magneto line interface to
the E&M voice and signaling interface format, i.e. the IMAG1 has to be operated together with a
TUEM1 unit.
The IMAG1 operates without embedded software, i.e. no ESW has to be installed.
The IMAG1 unit provides the following functions:
• 8 analog magneto line voice interfaces with a telephony bandwidth of 300 Hz to 3.4 kHz.

Copyright 2022 Hitachi Energy. All rights reserved. 91

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Ring signal detection on the magneto line.

• Ring signal feeding to the magneto lines. The on board ring generator generates the ring sig-
nal which is locally switched to the magneto line.
• Galvanic separation between the magneto line and the 2-wire voice interface of the TUEM1
unit.
• 8 E&M voice interfaces, to be connected to the E&M voice interface of a TUEM1 unit.
• Conversion between the magneto line signaling and the E&M signaling of the TUEM1 unit.
• 8 E&M signaling interfaces, to be connected to the E&M signaling interface of a TUEM1 unit.
The IMAG1 has one LED for unit failure indication.

2.2.27 FXO Voice Service Unit TUXA1

Figure 59: TUXA1 unit view

The TUXA1 unit is a 1-slot wide service unit of the XMC20. It has PSTN FXO voice user ports
voice interfaces. It can be operated in actively and passively cooled XMC20 subracks.
The TUXA1 unit connects its FXO interface to a local exchange FXS interface, simulating the
functions of a telephone set. With the TUXA1 unit the telephone connection to an exchange can
be extended via a TDM network.
The TUXA1 offers 12 user ports.
TUXA1 is connected to a P12 transport unit (STM14, NUSA1, NUSA2, SELI8, SDSL8) via the
PBUS in the backplane of the XMC20.
The TUXA1 unit provides the following functions:

Copyright 2022 Hitachi Energy. All rights reserved. 92

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Analog voice interfaces (FXO) with a telephony bandwidth of 300 Hz to 3.4 kHz, 2-wire
access mode, ITU-T G.711.
• Out-of-band signaling functions:
− On-hook and off-hook.
− Hook flash.
− Pulse dialing.
− Ground key function.
− Ringing.
− Metering.
− Polarity reversal.
• Wide range of configurable line impedances.
• 1+1 linear trail protection (LTP).
• 1+1 subnetwork connection protection with inherent monitoring (SNC/I).
• Performance monitoring.
• Maintenance functions:
− Test signal insertion, per user port.
− Voice back-to-back loop.
The TUXA1 has two LEDs for unit and traffic failure indication.

2.2.28 Data Service Unit TUDA1

Figure 60: TUDA1 unit view

Copyright 2022 Hitachi Energy. All rights reserved. 93

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The TUDA1 unit is a 1-slot wide service unit of the XMC20. It has four TDM data ports. Each
data port is configurable to
− V.24/V.28, or
− V.35 (Appendix II), or
− X.24/V.11, or
− RS485 2-wire, or
− RS485 4 wire.
In addition it provides one electrical Ethernet interfaces 10/100BASE-T for Ethernet over PDH
(EoP) transport.
The unit can be operated in actively and passively cooled XMC20 subracks.
TUDA1 is connected to a P12 transport unit (STM14, NUSA1, NUSA2, SELI8, SDSL8) via the
PBUS in the backplane of the XMC20.
The TUDA1 unit provides the following functions:
• Four data interfaces, independently configurable as DCE interface type.
• The DCE interfaces support the transmission modes:
− Asynchronous mode for subrates from 0.6 kbit/s to 38.4 kbit/s.
− Synchronous mode for subrates from 0.6 kbit/s to 56 kbit/s.
− Synchronous mode for nx64 data rates from 1x64 kbit/s to 32x64 kbit/s.
− Oversampling mode for data rates from 0 kbit/s to 600 kbit/s.
− Transition coding for data rates from 0 kbit/s to 19.2 kbit/s.
• The synchronous nx64 transmission modes provide the codirectional or contradirectional
timing operation.
• Data conferences with participants from the TUDA1 unit or any TDM circuit available in
XMC20:
− Up to 212 conferences per unit.
− Up to 16 participants per conference.
− Maximum participant bandwidth is 31x64 kbit/s.
− Maximum conferencing bandwidth per unit is 848x64 kbit/s.
• Conference type:
− Multipoint-to-multipoint.
− Point-to-multipoint.
• One Ethernet interface 10/100BASE-T for Ethernet over PDH transport.
• 1:1 equipment protection.
• 1+1 linear trail protection (LTP).
• 1+1 subnetwork connection protection with inherent monitoring (SNC/I).
• Performance monitoring.
• Maintenance functions:
− Test signal insertion, per user port and conference participant.
− Out of service, per user port and conference participant.
− Loops, data front -to-front loop and back-to-back loop.
The TUDA1 has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 94

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.2.29 E0 Service Unit TUGE1

Figure 61: TUGE1 unit view

The TUGE1 unit is a 1-slot wide service unit of the XMC20. It has 8 E0 (G.703) codirectional
interfaces. Alternatively the TUGE1 unit can be operated with 2 E0 (G.703) contradirectional
interfaces. It can be operated in actively and passively cooled XMC20 subracks.
TUGE1 is connected to a P12 transport unit (STM14, NUSA1, NUSA2, SELI8, SDSL8) via the
PBUS in the backplane of the XMC20.
The TUGE1 unit provides the following functions:
• 8 full duplex codirectional data interfaces according to ITU-T G.703, independently configu-
rable, or
• 2 full duplex contradirectional data interfaces according to ITU-T G.703, independently con-
figurable.
• Synchronous 64 kbit/s transmission with co- or contradirectional timing operation.
• Timing adaptation of asynchronous transmit signals with octet slips.
• 1+1 linear trail protection (LTP).
• 1+1 subnetwork connection protection with inherent monitoring (SNC/I).
• Performance monitoring.
• Maintenance functions:
− Front-to-front loop.
− Back-to-back loop.
The TUGE1 has two LEDs for unit and traffic failure indication.

Copyright 2022 Hitachi Energy. All rights reserved. 95

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.3 XMC20 Auxiliary Units

2.3.1 Dual Power Input Unit DUA25 (XMC25 R2 and XMC25)

With the DUA25 multi-connection unit, it is possible to power the XMC25 R2 and XMC25 sub-
rack from two redundant primary power supplies.
The DUA25 is installed in the XMC25 R2 or XMC25 subrack on the bottom of the backplane.

Please note:
The dual power supply unit DUA25 feeding up to 30 A requires active cooling.
→ It must only be operated in a subrack equipped with the optional fan unit
COOL4.

Please note:
The dual power supply unit DUA25 feeding up to 25 A can be operated without
active cooling.

Figure 62: DUA25 unit view

The DUA25 unit provides the following functions:

• Two external power supplies are connected in parallel to the DUA25. DUA25 provides the
power supply for the subrack.
• The nominal values for the primary voltage are -48 VDC and -60 VDC with the 0 volt poten-
tial connected to signal ground. The maximum current is 30 A.

Please note:
The XMC25 R2 subrack and the XMC25 subrack revisions R2A, R2B and R3B pro-
vide a maximum power supply current of 45 A. When using the DUA25 the maxi-
mum power supply current is limited to 30 A.
→ If you need dual power input with a higher current rating please contact your
Hitachi Energy sales representative.
• The availability of both power supplies is supervised and a failure is alarmed. For this pur-
pose, the DUA25 has an alarm interface with two alarm signals. This alarm interface is con-
nected to the alarm input interface of the COOL4 or ALMU4-F unit. The COOL4 or ALMU4-F
alarm input interfaces are connected to the core unit for alarm processing.
• Surge protection on power supply input side.
• Protection against reverse polarity.

2.3.2 Dual Power Input Unit DUA23 (XMC23 and XMC22)

With the DUA23 multi-connection unit, it is possible to power the XMC23 or XMC22 subrack
from two redundant primary power supplies.
The DUA23 is installed on the cable tray of the XMC23 or on the 19-inch adapter of the XMC22.
A specific cable tray for the XMC23 is available for this purpose.

Copyright 2022 Hitachi Energy. All rights reserved. 96

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 63: DUA23 unit view

The DUA23 unit provides the following functions:

• Two external power supplies are connected in parallel to the DUA23. DUA23 provides the
power supply for the subrack. The nominal values for the primary voltage are -48 VDC and -
60 VDC with the 0 volt potential connected to signal ground. The maximum current is 15 A.
• The availability of both power supplies is supervised and a failure is alarmed. For this pur-
pose, the DUA23 has an alarm interface with two alarm signals. This alarm interface is con-
nected to the alarm input interface of the COOL6, ALMU6-F, COOL8 or ALMU8-F unit. The
COOL6, ALMU6-F, COOL8 or ALMU8-F alarm input interfaces are connected to the core
unit for alarm processing.
• Surge protection on power supply input side.
• Protection against reverse polarity.

2.3.3 Fan Unit COOL4 (XMC25 R2 and XMC25)

The XMC25 R2 and XMC25 applications with active cooling require the fan unit COOL4 for the
forced ventilation of the subrack. All XMC20 units which can be operated with passive cooling
are listed in section 2.1.1.1 XMC25 R2 (on page 28) and section 2.1.1.2 XMC25 (on page 29).
With all other units active cooling is mandatory to evacuate the locally dissipated heat.
The COOL4 has 10 individually monitored fans that are integrated in a 19-inch subrack (1 HU).
The COOL4 is powered from the XMC25 R2 or XMC25 subrack while the core unit monitors the
alarms from the fan unit.
The fan unit COOL4 mounted in the rack just above the XMC25 R2 or XMC25 subrack, without
any distance between the two parts. It has the performance to evacuate up to 1800 W from the
XMC25 R2 or XMC25 subrack.
The speed of the fans is temperature controlled, in order to optimize the noise behavior and the
MTTF. The fans turn with low speed for air temperatures below the lower threshold temperature
(20°C) and with their maximum speed for air temperatures above the upper threshold tempera-
ture (35°C). Between the temperature thresholds, the speed of the fans is proportional to the air
temperature. Please note that the air temperature is measured at the point where it leaves the
subrack.
The COOL4 has 2 completely separate internal power supply circuits which facilitate redundant
power supply for the fans. 3 LEDs indicate the status of the power supply and the fans.
The COOL4 provides 2 alarm output interfaces and 12 alarm input interfaces. These alarm
interfaces are connected to the core unit for alarm processing via a power and alarm cable from
the COOL4 front to the backplane. The alarm output interfaces can be used e.g. for the control
of alarm lamps or bells. The alarm input interfaces are used for the reception of the DUA25
alarms and may be used for the reception of external equipment alarms, like “battery low”, “air
condition failure”, “door open” etc.

Copyright 2022 Hitachi Energy. All rights reserved. 97

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 64: COOL4 unit view

A heat deflection shield for the evacuation of the hot air to the front or to the rear of the rack can
be installed above the subrack or below the cable tray.

Figure 65: Heat deflection shield view

2.3.4 Fan Unit COOL6 (XMC23)

The XMC23 applications with active cooling require the fan unit COOL6 for the forced ventilation
of the subrack. All XMC20 units which can be operated with passive cooling are listed in section
2.1.1.3 XMC23 (on page 31). With all other units active cooling is mandatory to evacuate the
locally dissipated heat.
Active cooling is also mandatory for the horizontally mounted XMC23 subrack, regardless of the
unit types deployed.

Figure 66: View of the COOL6 (R3) fan unit

The COOL6 fan unit has four individually monitored fans that are integrated into a pluggable
unit.

Copyright 2022 Hitachi Energy. All rights reserved. 98

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The COOL6 unit is plugged into the top part of the vertically mounted subrack, or into the left
hand side when mounted horizontally, respectively. It has the performance to evacuate up to
600 W from the XMC23 subrack.
The speed of the fans is temperature controlled, in order to optimize the noise behavior and the
MTTF. The fans turn with low speed for air temperatures below the lower threshold temperature
and with their maximum speed for air temperatures above the upper threshold temperature.
Between the temperature thresholds, the speed of the fans is proportional to the air tempera-
ture. Please note that the air temperature is measured at the point where it leaves the subrack.
The COOL6 has 4 separate internal power supply circuits to power the fans individually. 3 LEDs
indicate the status of the power supply and the fans.
The COOL6 provides 12 alarm input interfaces on its front. These alarm interfaces are con-
nected to the core unit via the backplane for alarm processing. The alarm input interfaces are
used for the reception of external equipment alarms, like “battery low”, “air condition failure”,
“door open” etc.
Moreover, the COOL6 (R3) provides 2 alarm output interfaces, which can be used e.g. for the
control of alarm lamps or bells.

2.3.5 Fan Unit COOL8 (XMC22)

The XMC22 applications with active cooling require the fan unit COOL8 for the forced ventilation
of the subrack. All XMC20 units which can be operated with passive cooling are listed in section
2.1.1.4 XMC22 (on page 33). With all other units active cooling is mandatory to evacuate the
locally dissipated heat.
Active cooling is also mandatory for the horizontally mounted XMC22 subrack, regardless of the
unit types deployed.

Figure 67: View of the COOL8 (R1) fan unit

The COOL8 fan unit has two individually monitored fans that are integrated into a pluggable
unit.
The COOL8 unit is plugged into the top part of the vertically mounted subrack, or into the left
hand side when mounted horizontally, respectively. It has the performance to evacuate up to
380 W from the XMC22 subrack.
The speed of the fans is temperature controlled, in order to optimize the noise behavior and the
MTTF. The fans turn with low speed for air temperatures below the lower threshold temperature
and with their maximum speed for air temperatures above the upper threshold temperature.
Between the temperature thresholds, the speed of the fans is proportional to the air tempera-
ture. Please note that the air temperature is measured at the point where it leaves the subrack.
The COOL8 has 2 separate internal power supply circuits to power the fans individually. 3 LEDs
indicate the status of the power supply and the fans.

Copyright 2022 Hitachi Energy. All rights reserved. 99

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

The COOL8 provides 4 alarm input interfaces on its front. These alarm interfaces are connected
to the core unit via the backplane for alarm processing. The alarm input interfaces are used for
the reception of external equipment alarms, like “battery low”, “air condition failure”, “door open”
etc.
Moreover, the COOL8 (R2) provides 2 alarm output interfaces, which can be used e.g. for the
control of alarm lamps or bells.

2.3.6 Alarm Unit ALMU4-F (XMC25 R2 and XMC25)

The ALMU4-F is an alarm unit used in place of the fan unit COOL4 in a passively cooled
XMC25 R2 or XMC25.
The ALMU4-F has the same alarm interfaces as the COOL4. The ALMU4-F provides 2 alarm
output interfaces and 12 alarm input interfaces. The interfaces for the alarm signals and the
ALMU4-F power supply are on the unit front panel.
The ALMU4-F is powered from the XMC25 R2 or XMC25 subrack while the core unit monitors
the alarms from the alarm unit.
The ALMU4-F is typically installed above the XMC25 R2 or XMC25 subrack.

Figure 68: ALMU4-F R1B unit

2.3.7 Alarm Unit ALMU6-F (XMC23)

The ALMU6-F is an alarm unit used in place of the fan unit COOL6 in a passively cooled
XMC23.

Please note:
Passive cooling with the horizontally mounted XMC23 subrack is not possible.
→ A horizontally mounted XMC23 subrack requires active cooling with a fan unit.
The ALMU6-F has the same alarm interfaces and the same mechanical specification as the
COOL6 (R3). The ALMU6-F provides 2 alarm output interfaces and 12 alarm input interfaces.
The interfaces for the alarm signals are on the unit front panel.
The ALMU6-F is internally powered from the XMC23 subrack while the XMC23 core unit moni-
tors the alarms from the alarm unit.

Copyright 2022 Hitachi Energy. All rights reserved. 100

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 69: ALMU6-F unit

2.3.8 Alarm Unit ALMU8-F (XMC22)

The ALMU8-F is an alarm unit used in place of the fan unit COOL8 in a passively cooled
XMC22.

Please note:
Passive cooling with the horizontally mounted XMC22 subrack is not possible.
→ A horizontally mounted XMC22 subrack requires active cooling with a fan unit.
The ALMU8-F has the same alarm interfaces and the same mechanical specification as the
COOL8 (R2). The ALMU8-F provides 2 alarm output interfaces and 4 alarm input interfaces.
The interfaces for the alarm signals are on the unit front panel.
The ALMU8-F is internally powered from the XMC22 subrack while the XMC22 core unit moni-
tors the alarms from the alarm unit.

Figure 70: ALMU8-F unit

Copyright 2022 Hitachi Energy. All rights reserved. 101

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.3.9 Air Flow Optimization Unit ETMP1

When increasing the maximum ambient temperature of the XMC20 subrack from +60°C to
+65°C without taking any measures the SFP module temperature can exceed the maximum
allowed case temperature.
To lower the SFP case temperature the cooling of the SFP modules must be improved. The air-
flow has to be improved by placing specific air flow optimization units in the neighboring subrack
slots of units with SFP interfaces. The air flow optimization unit for XMC20 is named ETMP1.
The ETMP1 is a purely passive unit and provides no LEDs at the unit front or any other electri-
cal components on the unit.

Please note:
It is also possible to use XMC20 service units with a low power dissipation instead
of an air flow optimization unit.

Figure 71: ETMP1 unit

For further information please refer to [1KHW029121] Application Note “Extended Temperature
Range Operation”.

2.4 Cabling and Connections

2.4.1 Electrical Signal Interfaces

All signal cables are connected to the corresponding service or core units via front connectors.
The XMC20 uses the following connectors for its electrical front interfaces:

Copyright 2022 Hitachi Energy. All rights reserved. 102

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

• Standard connector for traffic signals (SUPM1, SUPM2, ISDN4, FIL16, TUEM1, TUXA1,
TUGE1, IMAG1, SELI8, SDSL8, SATP8, SUSE2);
The standard connector for the XMC20 service units features connector frames based on the
standard DIN 41 612. The connector caps of the cables can be locked to the units by means
of latching clips (refer to Figure 16: "Plug-in unit with standard front connector (sample)" (on
page 37));
• Metral ® with 4x6 male contacts for data interfaces (TUDA1);
• RJ45 for Ethernet interfaces (CENT2, COGE7, COGE5, ETE24, SUP12, SABE1, STM14,
ETAG1, TUDA1);
• SFP modules with electrical STM-1 interfaces (coaxial; STM14, NUSA1, NUSA2);
• SFP modules with electrical Gigabit Ethernet interfaces (RJ45; CENT2, COGE7, COGE5,
ETO12, SABO1, VRX10);
• Micro DSub-9 Connector, symmetrical clock input/output 120 Ω (CENT2, COGE7, COGE5);
• Micro DSub-9 Connector, “time of day” and “pulse per second” input/output 120 Ω (CENT2);
• Molex Mini-Fit, for alarm input (8 pins) and output (6 pins) interfaces (COOL4, COOL6,
COOL8, ALMU4-F, ALMU6-F, ALMU8-F).

2.4.2 Optical Signal Interfaces

All optical signal cables are connected to the corresponding service or core units via front con-
nectors.
The XMC20 uses the following connectors for its optical front interfaces:
• QSFP+ modules with optical 40 Gigabit Ethernet interfaces (LC; EXPU1);
• SFP+ modules with optical 10 Gigabit Ethernet interfaces (LC; CENT2, COGE7, COGE5,
SECU1, EXPU1);
• SFP modules with optical Gigabit Ethernet interfaces (LC, SC; CENT2, COGE5, SECU1,
ETO12, SABO1, VRX10);
• SFP modules with optical STM-4 and STM-1 interfaces (LC; STM14);
• SFP modules with optical STM-16, STM-4 and STM-1 interfaces (LC; NUSA1, NUSA2);
The XMC20 uses the SFP cages, supporting those SFP modules that comply with the INF-
8074i specification. In most cases, LC connectors are used.

2.4.3 Power Interfaces

Power cables are connected to the power interface of the corresponding network element.
The XMC20 uses the following connectors for its power interfaces:
• Terminal block with 2 x 4 terminals (+, -) for -48 VDC /-60 VDC connection (XMC25 R2 and
XMC25),
• Terminal block with 2 x 3 clamp terminals (+, -, ), for -48 VDC / -60 VDC connection
(XMC23 and XMC22).

2.4.4 XMC20 Cable Tray and Grounding Bar

The signal cables are fed to the XMC25 R2 or XMC25 cable tray or to the XMC23 cable tray
below the subrack (refer to Figure 72 or to Figure 73).
The cable tray provides strain relief and holds the cables in position for the units in the subrack
above. The cable tray also features two connection points for the power supply. Thus, the sub-
rack can be installed and removed independently from the cable tray and any installed cables.
The XMC22 subrack with its 19-inch adapter provides no cable tray. The signal cables have to
be fixed directly to the rack.
The grounding bar for signal cables is in front at the bottom of the subrack. It connects the
screens of the signal cables to the equipment ground. A simple clamping mechanism holds and

Copyright 2022 Hitachi Energy. All rights reserved. 103

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

connects the cable screens to the grounding bar. The grounding bar is a part of the construction
of the subrack and consists of two independent halves (XMC25 R2 and XMC25).
The bar features a thread for the connection of the protective earth or it can also be used as a
bonding point for wrist straps for maintenance.

Figure 72: Signal cables and grounding bar in the XMC25 R2 and XMC25

The cable tray provides the connection point for the primary power supply circuit. The standard
connection point is for 1 DC power supply circuit.
For the XMC23, the cables are fixed to the cable tray as shown in Figure 73.

Copyright 2022 Hitachi Energy. All rights reserved. 104

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

Figure 73: Fixing signal cables in the XMC23 (top view for horizontal mounting)

Figure 74: XMC25 R2 and XMC25 cabling practice

Copyright 2022 Hitachi Energy. All rights reserved. 105

XMC20 | SYSTEM DESCRIPTION ARCHITECTURE AND VIEWS

2.4.5 COOL4 and ALMU4-F Cable

The COOL4 unit or the ALMU4-F unit is connected to the XMC25 R2 or XMC25 backplane with
a cable. This cable provides the power supply of the COOL4 or ALMU4-F and it also connects
the alarm I/O control and the COOL4 or ALMU4-F alarm control signals to the core unit via a
backplane connector. Hence, the 2 alarm output- and the 12 alarm input interfaces on the
COOL4 or ALMU4-F front are connected to the core unit via this cable.

2.4.6 DUA25 Alarm Cable

The DUA25 has an alarm cable that is connected to a dedicated alarm input interface of the
COOL4 unit in the XMC25 R2 or XMC25.

2.4.7 DUA23 Alarm Cable

The DUA23 has an alarm cable that is connected to a dedicated alarm input interface of the
COOL6, ALMU6-F, COOL8 or ALMU8-F unit in the XMC23 or XMC22.

2.5 ESD/EMC, Grounding and Earthing

The subrack with the front cover installed represents a Faraday cage like construction if the
cables are connected to the cable grounding bar as instructed. Conductive metal sheets all
around the subrack protect the XMC20 from ESD and electromagnetic fields.
The 19-inch mounting flanges of the subrack are conductive and provide a conductive contact to
the rack if the rails of the rack provide a conductive surface.
When in operation, the XMC20 is protected against ESD in accordance with IEC 61000-4-2 and
in accordance with the specified EMC properties, provided that
• all parts have been installed as instructed in the technical customer documentation,
• all the equipment is properly grounded,
• the XMC20 subrack is installed with its front cover,
• Hitachi Energy approved cables are used.
Hitachi Energy gives no warranty for cables manufactured by third party and will not accept
liability for EMC/ESD compliance if its equipment is operated with cables that are not
approved by Hitachi Energy.
The positive potential of the primary DC power supply is connected with the system ground. The
system ground connects internally to the construction of the subrack.
Earthing and bonding of XMC20 equipment in telecommunication centers is in relation to safety,
functional performance and EMC:
• The XMC20 complies with the principles of Common Bonding Networks (CBN) as described
in the standard ETSI EN 300 253 V2.1.1 (2002-04). It is designed for the integration accord-
ing to the configuration shown in EN 300 253, Figure 2: “Example of a CBN/MESH-BN con-
figuration with common d.c. return conductor connected to the CBN at multiple points”.

Copyright 2022 Hitachi Energy. All rights reserved. 106

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

3 XMC20 System Services

3.1 System Control

3.1.1 Principles
The system control of the XMC20 relies on processors on the service units (traffic units) and on
a central control block. The central control block is placed on the core unit of the XMC20.
The main tasks of the central control block are:
• Management of the NE configuration.
• Control of the system operation.
• Management communication.
• PDH synchronization.
• Monitoring of the system performance.
The system control uses decentralized processing for the different tasks. The service units pro-
vide local unit control and control of their traffic interfaces.
Most service unit processors use a dedicated communication channel (ICN = Internal Communi-
cation Network) for the communication between the core unit and the service units. The ICN is
embedded in the physical structure of the backplane.
Some newer service units use the Gb Ethernet star connection to the core unit for the manage-
ment communication.

Please note:
When operating the XMC20 subrack with the COGE5 or COGE7 core unit, the user
traffic makes also use of the GbE star instead of the 10 GbE star.
→ The GbE star bandwidth must be shared between the user traffic and the man-
agement traffic.

Table 17: Service units managed via the GbE star connection
Service/core unit introduced with XMC20 release
CENT2 R8A
COGE7 R15B
COGE5 R4C
EXPU1 R15A
ETO12 R4C
ETE24 R4C
SUP12 R4C
SABE1 R8A SP01
SABO1 R8A SP01
SUSE2 R4D
NUSA1 R4C
NUSA2 R4C
VRX10 R6D

The unit management via the Gb Ethernet star is tagged with the VLAN ID 4094 and uses the
queue of the traffic class 7.

Copyright 2022 Hitachi Energy. All rights reserved. 107

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

3.1.2 Core Unit

A major task of the central control block, which is a part of the core unit CENT2 or COGE7 or
COGE5 is the maintenance of the NE database, which stores the complete NE configuration.
This information will serve to reconfigure units that have been restarted or replaced. All the
information on system or unit configuration is stored and administrated via the management
information database.
The XMC20 provides 1:1 equipment protection for the core unit. The description of this function
is given in section 4.4.2 Equipment Protection of the Core Unit (on page 140).
The core unit also contains the interfaces for the local NE management communication (with the
ECST/UNEM).
The core unit has two high performance on-board CPUs and uses software download for its unit
and network element specific embedded softwares (ESWs).

3.1.3 Service Units

Service units are units with specialized traffic functions and interfaces. The local control handles
all aspects of the local unit management and traffic processing. This includes (traffic function
related activities are not considered here):
• Monitoring of the local unit,
• Provisioning of the local unit configuration,
• Access to local inventory data,
• Driving local function indicators (alarm LEDs),
• Local storage of ESW,
• Communication with the core unit.
The service units use software download for their local embedded software (ESW).

3.2 ESW and Feature Management

3.2.1 ESW Management

Download of embedded software (ESW) is a standard commissioning and maintenance process
for the core and service units of the XMC20.
With the XMC20, ESW can be downloaded and installed on NE level.
The download procedure is executed during normal system operation without disturbing running
services. At least 2 ESW versions can be stored on one unit. The first ESW is currently exe-
cuted, while the second one is a new version to be launched. The ESW is stored directly in the
flash memory of the unit. This mechanism speeds up the activation of the new software. Activa-
tion of a new software version can be performed either on schedule or immediately. Scheduled
activation allows operators to launch a new version at a given time, for instance within a mainte-
nance window, without any further manual intervention. Immediate activation is used for mainte-
nance activities performed on the system.
Launching a new ESW release requires rebooting of the unit.
ESW download is integrated in the management concept of the XMC20 with corresponding
diagnostic functions:
• The ESW installation is configured via the ECST/UNEM.
• Installed ESW can be checked at any time with the built-in inventory management function
and the SW installation status function.
Accordingly, there is no need for local access to the NE, since the ESW download uses the
same management communication channels as the standard management functions with local
and remote access.

Copyright 2022 Hitachi Energy. All rights reserved. 108

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

3.2.2 Feature License Management

Feature license management allows customers to buy equipment with standard functionality
(hardware and/or software) at a basic price and to add functions as needed simply by buying
new licenses.
With the feature license management scheme, only one ESW per unit is required. This ESW
supports all the unit features.
With the appropriate license a customer gets the certified right to use the functions and features
listed on the XMC20 R16A Feature License in addition to the basic functions.

3.3 Inventory
The XMC20 inventory function provides detailed information on the installed hardware and ESW
in the subrack.
Inventory data includes:
• Unit name,
• Name of the installed ESW and detailed version identification,
• Name of the bootloader and detailed version identification,
• Supplier part number and version identification,
• Manufacturer identification,
• Manufacturer part and serial number.
All inventory data – with the exception of the installed ESW – is stored in protected local mem-
ory during the manufacturing and provisioning process.
Beyond this function, the SDSL8 and SUSE2 units supports the request of inventory data from
the connected 3rd party or Hitachi Energy CPE.

3.4 Fault Management

The XMC20 fault management detects equipment, function and transmission failures, or more
generally monitors the availability of the equipment and transmission paths. This includes an
alarm system with various interfaces for the indication of faults and failures. These interfaces
include local alarm indication and, depending on configured options, entries in the alarm list, the
alarm logbook, the syslog message list and SNMP trap reporting.
There are dedicated logbooks available, i.e.:
• Alarm logbook.
• Configuration logbook.
• Equipment logbook.
• Event logbook.
• Session logbook.
The alarm logbook provides the details generated by the fault management as shown in Figure
75.

Copyright 2022 Hitachi Energy. All rights reserved. 109

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

Defect Correlation Integration of Fault Translation of Failures into

Anomaly Defect Filter Defect Fault Cause Failure Unit Alarm LED
Filter Causes into Failures Unit Alarms
f1
f3 f4 f5

Translation of Failures into

Traffic Alarm LED
Traffic Alarms
Monitoring true/false f6
Persistence Time
Absent Time Service Affecting
Translation of Failures into
Alarm Relay
Service Affecting Alarms
f71
Non-Service Affecting
Translation of Failures into
Alarm Relay
Non-Service Affecting Alarms
f72

Logbook Entries

Figure 75: Fault management filters and indications

• Alarm generation (according to ETS 300 417-1-1):

Each unit of the XMC20 NE is able to detect equipment and/or traffic related defects and
anomalies. For further processing, these defects and anomalies are transformed into fault
causes with the defect correlation filter.
For each of the fault causes you can set a reporting option (via the ECST/UNEM) which
enables or blocks the further processing of the fault causes (monitoring true or false). Only
fault causes with the monitoring set to true will be considered for further processing. Fault
causes with the monitoring set to false will not be considered.
A fault cause is declared a failure if the fault cause persists for a certain time, called the per-
sistence time (Set Threshold). The failure is cleared if the fault cause is absent for a certain
time, called the absent time (Clear Threshold). You can set persistence time and absent time
individually per fault cause.
• Alarm processing and indication:
The XMC20 is able to store time stamped information on events and failures in dedicated
logbooks. It is possible to transfer the contents of the logbooks and the pending alarms of
the NE to the ECST/UNEM for display and inspection. Alarms are generated based on fail-
ures.
The XMC20 system provides six severity levels for the alarms according to ITU X.733. The
severity levels which represent service affecting and non-service affecting conditions ordered
from most severe to least severe are Critical, Major, Minor and Warning:
− Critical
This severity level indicates that a service affecting condition has occurred and an imme-
diate corrective action is required.
− Major
This severity level indicates that a service affecting condition has developed and an
urgent corrective action is required.
− Minor
This severity level indicates the existence of a non-service affecting fault condition and
that corrective action should be taken in order to prevent a more serious (for example,
service affecting) fault.
− Warning
This severity level indicates the detection of a potential or impending service affecting
fault (i.e. a non-service affecting fault condition), before any significant effects have been
felt. Action should be taken to further diagnose (if necessary) and correct the problem in
order to prevent it from becoming a more serious service-affecting fault.
− Cleared
The cleared severity level indicates the clearing of one or more previously reported
alarms.

Copyright 2022 Hitachi Energy. All rights reserved. 110

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

− Notification
There is an additional alarm severity not according to ITU-T X.733. The Notification is
used for XMC20 external alarm or status notifications. No XMC20 NE alarm severity and
no relay contact is activated when a notification alarm is active.
An alarm or entry to the alarm logbook is created only if the alarm monitoring is set to true.
With an active failure, the corresponding unit or traffic alarm indicator LED on the front panel
of the unit is activated. All unit failures and traffic related fault causes are signaled via the
local fault indication LEDs on the front panel of the affected unit(s).
With a critical or major alarm condition, the “service affecting alarm” relay contact is switched
over. With a minor or warning alarm condition, the “non-service affecting alarm” relay contact
is switched over. The relay contacts are implemented on COOL4, ALMU4-F, COOL6,
ALMU6-F, COOL8 and ALMU8-F.

Please note:
The active “service affecting alarm” relay releases the “non-service affecting alarm”
relay.
→ Only one of the two alarm relays can be active.
The current alarm condition and the logbooks can be loaded for display and inspection to the
ECST/UNEM at any time.
The alarm list available with the UNEM polling shows the current alarm state for the polled
network elements, i.e. the access network.
• Notifications:
Important system functions and some unit processes can generate notifications. The notifica-
tion function helps you to find out the relationship between NE internal events and possible
failures associated with these events. Notifications create an entry in the event logbook of
the NE.
• Syslog:
Changes in system or in logbooks facilities as
− System,
− Alarm logbook,
− Event logbook,
− Configuration logbook,
− Equipment logbook,
− Session logbook,
can be reported to a remote syslog server via the syslog function. The XMC20 allows config-
uration of up to 10 syslog destinations, each with its individual severity threshold and facility
sources.
• SNMP traps can be reported to an SNMP manager.

3.5 Operation and Maintenance for Traffic Functions

The XMC20 has functions and features to support the operation and maintenance of the XMC20
traffic functions. This includes status and maintenance functions as well as performance moni-
toring.

3.5.1 Status and Maintenance

The XMC20 offers status and maintenance functions for the supervision and active testing of
functions and traffic signals. Status and maintenance commands are executed immediately and
are not part of the persistent configuration.
Examples of status and maintenance functions are:
• Link status of Ethernet interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 111

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

• Bridge and router status.

• TDM traffic signal status.
• DSL line status
− line state,
− attenuation,
− SNR margin,
− power back-off.
• Loops
− front-end loop,
− back-end loop.
• Traffic tests
− test signal insertion,
− out of service of a port.
The detailed list of all status and maintenance functions is contained in the specification section
of this document. Please refer to section 6.3.2 Traffic Functions (on page 169).

3.5.2 Performance Monitoring

The XMC20 supports performance monitoring for the traffic of the certain service units. Perfor-
mance monitoring data are stored in the local unit database. Depending on the processed traf-
fic, different performance monitoring groups are available:
• ITU-T G.826 performance monitoring group:
Based on counts of anomalies and faults of the traffic signal in one-second periods, G.826
performance monitoring evaluates the following parameters per traffic measurement point:
− ES (Errored Seconds),
− SES (Severely Errored Seconds),
− BBE (Background Block Errors),
− UAT (Unavailable Time).
• Other performance monitoring groups:
Other performance monitoring groups count specific events associated with the traffic signal
per traffic measurement point, e.g. with packet counters on Ethernet ports. This includes,
among others, the following counter groups:
− MIB-2 interface table,
− Miscellaneous port statistics.
The performance is calculated for 24-hours intervals (up to 8 records), and 15-minutes intervals
(up to 108 records).
The detailed list of all performance management counters is contained in the specification sec-
tion of this document. Please refer to section 6.3.2 Traffic Functions (on page 169).

3.5.3 Ethernet Port Maintenance

The XMC20 Switch Ethernet ports support the mirroring maintenance function. Any of the
XMC20 Switch ports can be configured as mirror port which copies ingress and/or egress traffic
of any other XMC20 Switch port to the mirror port.
In addition the XMC20 Switch ports provide statistics counters according to the following MIBs:
• IF MIB
− In octets
− In unicast packets
− In multicast packets
− In broadcast packets

Copyright 2022 Hitachi Energy. All rights reserved. 112

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

− In errors
− Out octets
− Out unicast packets
− Out multicast packets
− Out broadcast packets
− Out errors
• EtherLike MIB
− In pause frames
− Out pause frames
− FCS errors
− MAC transmit errors
− MAC receive errors
− In frames too long
− Deferred transmissions
− Late collisions
− Excessive collisions
• RMON MIB
− Drop events
− CRC align errors
− In undersize packets
− In oversize packets
− In fragment packets
− In jabber packets
− Collisions
− In packets
− In octets
− In packets of different sizes

3.6 Synchronization
Due to the nature of Ethernet frame based traffic, there are no synchronization functions
required in the XMC20 using Ethernet traffic exclusively.
However, a PETS (Plesiochronous Equipment Timing Source) function is implemented on the
core unit for TDM voice and data traffic functions and functions like E1 circuit emulation.
The following sources can be used for the synchronization of the PETS:
• Internal oscillator,
• 2.048 MHz synchronization input signal,
• Ethernet timing of a core unit front port (synchronous Ethernet),
• PTP timing of a core unit front port (IEEE 1588 v2), port based or VLAN based,
• Received clock from a service unit (e.g. SELI8, STM14),
• TCXO of the SATP8 unit,
• SETS of a STM14, NUSA1 or NUSA2 unit.
Accordingly, the PETS clock of a XMC20 NE can be synchronized to the PETS clock of another
XMC20 NE or to an external clock signal.
The XMC20 NE performs the PETS clock source selection according to a predefined priority for
each clock source, or according to the received quality level (QL). The QL is transported in the
SSM of a PDH or SDH traffic signal or in the ESMC of an Ethernet traffic signal.

Copyright 2022 Hitachi Energy. All rights reserved. 113

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

Moreover, the synchronization output interface can be used for the synchronization of external
equipment.
The SATP8 unit provides a clock source with its on-board TCXO. This clock source is used as
timing reference for the adaptive timing recovery circuits of the Pseudo Wires on the SATP8
unit.
The STM14, NUSA1 and NUSA2 units implement the synchronous equipment timing source
(SETS) for the synchronization of the units SDH traffic. SDH synchronization is not part of the
core unit synchronization function.
The core unit is configurable to be a PTP Ordinary Clock, a PTP Boundary Clock, a PTP Trans-
parent Clock, using the core unit Ethernet front ports as PTP slave or PTP master ports. If a
core unit port is configured as Boundary Clock or Ordinary clock slave port, the PTP timing can
be used to synchronize the frequency and phase of the PETS.
If the PTP packet transport is VLAN based the PTP packet stream can be used simultaneously
as Ordinary or Boundary Clock to synchronize the network element, and as Transparent Clock
to forward PTP packets with time stamp corrections.

3.7 SNTP
SNTP (simple network time protocol) is used for the synchronization of time and date of the
XMC20 NE to the time and date provided by an SNTP server. The SNTP server can be installed
on any computer, e.g. on a workstation with running UNEM, or on a PC with running ECST.
Some SNTP servers return the time from an atomic clock or a highly accurate radio frequency
clock.
The XMC20 acts as an SNTP client when configured in unicast operation mode. The client uses
the UDP transport protocol and sends a request packet to the server. The server then responds
with a specially formatted data packet that contains the time information and some information
that allows for the calculation of the packet delay. The protocol specifies that the returned time
is sent in UTC (coordinated universal time, also known as Greenwich mean time). The time is
displayed in local time on the XMC20 NE. You can configure a NE local time zone for the
XMC20.
When configured in broadcast operation mode, the XMC20 can also receive timing information
from SNTPv3 broadcast servers. Note that SNTPv4 is not supported in the current release.

3.8 PTP
PTP (Precision Time Protocol) is used for the synchronization of time and date of the XMC20
NE to the time and date provided by a GPS Receiver acting as IEEE 1588 Grand Master Clock.
The PTP time and date is distributed to the XMC20 NEs through a packet switched network and
received by XMC20 NEs on the Ethernet ports of the core units COGE5 and CENT2.
The PTP packet transport can be Ethernet based for physical and logical (VLAN) ports, or it can
be UDP/IP based for logical (VLAN) ports.
A XMC20 network element with the CENT2 core unit, using the UDP/IPv4 based packet trans-
port, can act as PTP master for up to 32 subordinate network elements, allowing a scalable PTP
network layout.

3.9 PPS
The CENT2 provides an electrical PPS output to synchronize any external equipment to the
XMC20 timing.

3.10 Heat Management

When using active cooling the XMC25 R2, XMC25, XMC23 and XMC22 are designed for opera-
tion in the ambient temperature range of −25° C up to +65° C, according to ETSI EN 300 019-1

Copyright 2022 Hitachi Energy. All rights reserved. 114

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

(equivalent to class 3.3, extended range). Active cooling requires the usage of the fan unit
COOL4 (XMC25 R2 and XMC25), COOL6 (XMC23) or COOL8 (XMC22).
With passive cooling operation, i.e. without the fan unit, the ambient temperature range is
reduced to −25° C up to +55° C, according to ETSI EN 300 019-1 (equivalent to class 3.3).
The COOL4 of the XMC25 R2 and XMC25 has ten individually monitored fans that are inte-
grated in a 19-inch subrack.
The COOL6 of the XMC23 has four individually monitored fans.
The COOL8 of the XMC22 has two individually monitored fans.
The speed of the fans of COOL4, COOL6 and COOL8 is temperature controlled, in order to
optimize the noise behavior and the MTTF.
The failure of one fan is indicated by a non-service affecting alarm. This has no impact on the
MTTF, if the failed fan is replaced within 48 hours. The failure of more than one fan is indicated
by a service affecting alarm. In this case, the failed fans have to be replaced immediately or the
system has to be shut down, in order to prevent an MTTF reduction or even equipment damage.
There are several temperature sensors implemented on the XMC20 boards. They allow the
monitoring of the temperature inside the subrack and reducing or even switching off services in
the case of local overheating.
Temperature limits can be set on network element level that generate an alarm when crossed.
Current, minimum, and maximum temperature can be read out via the element manager. Both
minimum temperature and maximum temperature can be reset via the element manager.
When stacking XMC20 subracks, heat evacuation requires the installation of heat deflection
shields. A heat deflection shield directs the hot air from the electronic equipment to the front or
to the rear of the rack. For XMC23 and XMC22 a heat deflection shield is required particularly
when vertical mounting is selected.
The maximum heat evacuation per XMC25 R2 and XMC25 subrack is 1800 W. With passive
cooling operation, i.e. without the fan unit, the maximum heat evacuation is reduced to 500 W.
The maximum heat evacuation per XMC23 subrack is 600 W. With passive cooling operation,
i.e. without the fan unit, the maximum heat evacuation is reduced to 200 W.
The maximum heat evacuation per XMC22 subrack is 380 W. With passive cooling operation,
i.e. without the fan unit, the maximum heat evacuation is reduced to 80 W. Passive cooling is
only possible without the AC/DC converter POAC1.

3.11 Power Supply

3.11.1 DC Power Supply Interfaces

The units of the XMC20 subrack are directly powered from the DC power supply with a nominal
voltage of -48 VDC or -60 VDC, according to ETSI EN 300 132-2. Each unit has its own power
converter, i.e. no dedicated power converter units are required. The DUA25 unit allows the pow-
ering of the XMC25 R2 and XMC25 subrack from 2 redundant primary power supplies (batter-
ies), whereas the DUA23 allows the same for the XMC23 and XMC22.
The XMC20 interfaces for external DC power supply are specified as follows:
• XMC25 R2:
− Nominal voltage: -48 VDC or -60 VDC
− Voltage range: -40.0 VDC … -72 VDC with DUA25
− Voltage range: -39.5 VDC … -72 VDC without DUA25
− Maximum continuous current:

XMC25 R2
With DUA25 30 A
Without DUA25 45 A

Copyright 2022 Hitachi Energy. All rights reserved. 115

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

• XMC25:
− Nominal voltage: -48 VDC or -60 VDC
− Voltage range: -40.0 VDC … -72 VDC with DUA25
− Voltage range: -39.5 VDC … -72 VDC without DUA25
− Maximum continuous current:

XMC25 subrack revisions XMC25 subrack revision

R2A, R2B and R3B R3A
With DUA25 30 A 30 A
Without DUA25 45 A 30 A

• XMC23:
− Nominal voltage: -48 VDC or -60 VDC
− Voltage range: -40.0 VDC … -72 VDC with DUA23
− Voltage range: -39.5 VDC … -72 VDC without DUA23
− Maximum continuous current:

XMC23
With DUA23 15 A
Without DUA23 15 A

• XMC22:
− Nominal voltage: -48 VDC or -60 VDC
− Voltage range: -40.0 VDC … -72 VDC with DUA23
− Voltage range: -39.5 VDC … -72 VDC without DUA23
− Maximum continuous current:

XMC22
With DUA23 8A
Without DUA23 8A

The XMC25 R2 subrack and the XMC25 subrack revisionsR2 (and later) with active cooling are
designed for a maximum power consumption of 1800 W. The XMC23 subrack with active cool-
ing is designed for a maximum power consumption of 600 W. The XMC22 subrack with active
cooling is designed for a maximum power consumption of 380 W.
The contribution of each unit to the power consumption on the external power supply is avail-
able with the technical specifications (user manuals) of the units. The total power consumption
has to be considered for the specification of the capacity of the external power supply.
Please note that the primary DC input voltage is not generally monitored as this is considered to
be a function of the battery supervision/power rectifier. Only the DUA25 and DUA23 units will
monitor the input voltages and generate alarms if the voltages are too low. The power convert-
ers on the units are switching off if the input voltage is too low.

3.11.2 AC Power Supply Interfaces

The hardware supplement XMC22 AC power kit available for the XMC22 subrack provides
direct AC powering for the subrack from a mains power supply.
The XMC22 AC power kit consists of
• POAC1 AC/DC converter,
• AC/DC backplane, and
• assembly material for the backplane.

Copyright 2022 Hitachi Energy. All rights reserved. 116

XMC20 | SYSTEM DESCRIPTION XMC20 SYSTEM SERVICES

The POAC1 interfaces for external AC power supply are specified as follows:
− Nominal input voltage: 115 VAC or 230 VAC
− Input voltage range: 90.0 VAC … 264 VAC
− Maximum continuous input current:

POAC1
115 VAC 4.5 A
230 VAC 2.2 A

− Output voltage range: 52.0 VDC … 53.0 VDC

− Maximum continuous output current: 8 A
− Maximum continuous output power: 350 W
As a supplement to the AC powering a 48 V lead-gel battery with a capacity of 10 Ah to 40 Ah
can be connected to the POAC1 unit. In case of an AC mains failure the supply of the XMC22 is
secured by the battery.
The backup battery is charged by the POAC1 AC/DC converter with a maximum current of 2 A.
The battery is not provided by Hitachi Energy
The POAC1 unit supervises the AC mains voltage and the AC/DC converter output voltage, fail-
ures are alarmed.

Copyright 2022 Hitachi Energy. All rights reserved. 117

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4 XMC20 Traffic and Equipment Functions

4.1 Network Aspects

The XMC20 using MPLS-TP offers two types of layer 2 virtual private networks (L2 VPN):
• Virtual Private Wire Service (VPWS), and
• Virtual Private LAN Service (VPLS).

4.1.1 Network Scenarios for MPLS-TP Virtual Private Wire Services

In case of VPWS two Label Edge Router (LER) devices provide a logical connection such that a
pair of CE devices appears to be connected by a single logical layer 2 circuit.
LER devices act as layer 2 circuit switches. Layer 2 circuits are attached to pseudo wires and
then mapped onto tunnels in the service providers network. A tunnel is transported on a pair of
bidirectional Label Switch Paths (LSP). A tunnel can either be specific to a particular VPWS, or
be shared among several pseudo wires of VPWS or VPLS.
A tunnel provides a point-to-point connection between the two LER devices where the CE
devices are attached to. The LER devices can be connected directly or via one or several Label
Switch Router (LSR) devices.
The XMC20 can be configured to be a LER, a LSR or a network element providing the LER and
LSR functionality simultaneously. The XMC20 supports up to 2000 tunnel terminations in a LER
and up to 3500 bidirectional LSPs in a LSR.

MPLS
Network pseudo wire 1
pseudo wire 2

CE LER 1 LSR LSR LER 2 CE

tunnel 1 tunnel 1 tunnel 1

working LSP 1 working LSP 2 working LSP 3

Figure 76: VPWS with one unprotected tunnel

In order to increase the availability of the L2 VPN, the tunnel can be a extended with a second
pair of LSPs, providing a protection path between the two LER devices. In case of a failure in
one of the working LSPs the traffic is rerouted via the protection LSPs.

tunnel 1
tunnel 1 working LSP 2 MPLS
working LSP 1 Network tunnel 1
working LSP 3

LSR LSR
pseudo wire 1

CE LER 1 LER 2 CE
pseudo wire 2
LSR LSR
tunnel 1 tunnel 1
protection LSP 1 tunnel 1 protection LSP 3
protection LSP 2

Figure 77: VPWS with one protected tunnel

Copyright 2022 Hitachi Energy. All rights reserved. 118

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.1.2 Network Scenarios for MPLS-TP Virtual Private LAN Services

In case of VPLS, several LER devices provide a logical connection such that CE devices
belonging to a specific VPLS appear to be connected by a single LAN.
In a VPLS, a CE device attaches, possibly through an access network, to a bridge module
inside the LER. The bridge module attaches to a VPLS forwarder and to one or more pseudo
wires. Tunnels connect all the LERs in the virtual LAN. A tunnel is transported on a pair of bidi-
rectional Label Switch Paths (LSP). It can either be specific to a particular VPLS, or be shared
among several pseudo wires of VPWS or VPLS.
Typically a full mesh connectivity is implemented between the LERs, but the XMC20 supports
also the setup of hierarchical VPLS (H-VPLS) for large scale deployments.
The LER performs forwarding of user data packets based on information in the layer 2 header,
such as a MAC destination address and VLAN tags.
The XMC20 supports up to 100 VPLS instances in a LER.
tunnel 1
working LSP 2
pseudo wire 1
LER 2 CE
tunnel 1
working LSP 1 tunnel 3
working LSP 1
LSR
pseudo wire 3
MPLS LSR
CE LER 1
Network tunnel 3
working LSP 2

LSR
tunnel 2 LER 3 CE
working LSP 1
tunnel 2
pseudo wire 2 working LSP 2

Figure 78: VPLS with tree unprotected tunnels

In order to increase the availability of the L2 VPN, a tunnel can be a extended with a second
pair of LSPs, providing a protection path between the two LER devices. In case of a failure in
one of the working LSPs the traffic is rerouted via the protection LSPs.
Figure 79 shows the working and the protection paths for the tunnel 1 between LER 1 and LER
2. The tunnel 2 between LER 1 and LER 3, and the tunnel 3 between LER 2 and LER 3 are not
labeled.
tunnel 1
working LSP 2
pseudo wire 1
LER 2 CE
tunnel 1
working LSP 1 tunnel 1
protection LSP 3
LSR

MPLS LSR
CE LER 1 pseudo wire 3
Network

LSR
tunnel 1 LER 3 CE
protection LSP 1
tunnel 1
protection LSP 2
pseudo wire 2

Figure 79: VPLS with one protected tunnel and two unprotected tunnels

Copyright 2022 Hitachi Energy. All rights reserved. 119

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.1.3 Network Scenario for LAN Island Interconnection using VPLS

In the examples above the customer network is connected via a single CE to the LER of the
MPLS core network.
In case the customer network is connected via two CE devices to a LER there is a risk of a MAC
address black hole issue when using RSTP on the CE facing ports. In this case the CE facing
ports on the LER must be configured to the R-L2GP (Reverse L2 Gateway Protocol) mode.

CPE LER 2 CE
R-L2GP

CPE MPLS
CE 1 LER 1
Network
Customer
Network
(LAN)
R-L2GP LER 3 CE

CE 2
CPE

CPE designated port

RSTP isolated root port

blocked port

Figure 80: Customer network connected with two CE to the LER

The LER sends BPDUs to the CE 1 and CE2 presenting itself as a root bridge. In symmetric
LAN ring topologies the blocked port is on the opposite side of the root bridge.
In case the customer network is connected via two CE devices to two LER (CE dual homing)
the CE facing ports on the LER must be configured to the R-L2GP mode.
TC Propagation to VPLS

CPE R-L2GP
MPLS-TP LER CE
Core
Network
CPE CE 1 LER 1
Customer
Network VPLS
(LAN) full mesh

CE 2 LER 2
CPE
LER CE
R-L2GP
CPE TC Propagation to VPLS

designated port

root port

blocked port

Figure 81: Customer network connected with two CE to two LER

Any topology change (TC) notification received by LER 1 or LER 2 from the customer network
must be forwarded to all LER being part of the affected VPLS: The LER must be aware which
LER, LER 1 or LER 2, must be addressed to access the CPEs in the customers network. The
CE dual homing setup is restricted to the MPLS-TP VPLS service type.
In LER 1 (and LER 2) a TC notification received from LER 2 (or LER 1) must be forwarded to
the spanning tree of the customer network.

Copyright 2022 Hitachi Energy. All rights reserved. 120

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

The forwarding of TC notifications inside the VPLS uses the PW OAM message “MAC with-
draw”.

Please note:
No BPDUs are sent over the MPLS core network.
→ The spanning tree is isolated in the customer network.

4.1.4 Network Scenario for Provider Network Access with Dual Homing
In a hierarchical VPLS (H-VPLS) the provider edge (PE) network element is connected to the
provider MPLS-TP core network with a spoke connection. To increase the availability of the
MPLS-TP network the PE network can be attached with two Pseudo Wires to two provider net-
work elements in parallel (PE dual homing).
Primary
Spoke PW MPLS-TP
working Core
Network
P1 P3 CE
Dual Homed PE

MPLS-TP
CE PE Access
Network VPLS
full mesh
Secondary P2 P4 CE
Spoke PW
protecting

Figure 82: Provider Edge network element connected with two PW to the core network

During normal operation only the working Pseudo Wire connecting the PE to the core network
(P1) is active. The protecting Pseudo Wire to P 2 is deactivated.
In case the primary spoke Pseudo Wire fails or the P1 network element fails the working
Pseudo Wire is deactivated and the protecting Pseudo Wire is activated.
The MAC address tables in all provider network elements participating in the affected VPLS
must be flushed: The P1 to P4 network elements must be aware which network element must
be addressed to access the PE network element in the MPLS-TP access network. The forward-
ing of the flush command inside the VPLS uses the PW OAM message “MAC withdraw”.
The PE dual homing setup is restricted to the MPLS-TP VPLS service type.

4.2 Ethernet Traffic Functions

4.2.1 MPLS-TP Transport

One of the main Ethernet traffic functions of the XMC20 is the MPLS-TP Transport (based on
RFC 5921). This function is implemented on the core unit, the WAN port expansion unit, and on
the Ethernet service units ETO12, ETE24, SUP12, SUSE2, NUSA1 and NUSA2.

4.2.1.1 VPWS Transport Function

Any port that is configured as Pseudo Wire Attachment Circuit (PWAC) or as Customer VLAN
Port (CVP) connects to a Virtual Private Wire Service (VPWS).
Any port on a core unit or WAN port expansion unit that is configured as MPLS-TP port is used
as uplink port towards the MPLS network.
An MPLS-TP port can be a physical port or can be a logical port. In this case it is a VLAN based
subinterface attached to a physical Ethernet port.

Copyright 2022 Hitachi Energy. All rights reserved. 121

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

XMC20
Pseudo Wire Tunnel

Eth port PWAC Core Unit

port-x GbE PW
backplane MPLS-TP 10GbE
Eth port PWAC LSP working port-1
port-y TN MPLS-TP
PW 10GbE
ETxxx LSP protection port-2

SUP12

Eth port PWAC GbE

port-x PW TN LSP working
backplane
EoS port PWAC
eos-y MPLS-TP 1GbE
PW TN LSP working port-5
NUSA1, NUSA2

DSL port PWAC GbE

port-x PW TN LSP working
backplane
PWAC

SUSE2

Figure 83: MPLS-TP VPWS transport in XMC20

Please note:
As an alternative to a MPLS-TP port on the core unit, a MPLS-TP port on a WAN
port expansion unit can be used.

4.2.1.2 VPLS Transport Function

Any port that is configured as Customer VLAN Port (CVP) connects to the VLAN Bridge, based
on the XMC20 Switch, and via the switch virtual interface (SVI) to the pseudo wires of a Virtual
Private LAN Service (VPLS).
The XMC20 Switch consists of all switch elements implemented on the core unit and the Ether-
net service units and which are interconnected via the GbE-star or the 10 GbE-star.
Any port on a core unit or WAN port expansion unit that is configured as MPLS-TP port is used
as uplink port towards the MPLS network.
An MPLS-TP port can be a physical port or can be a logical port. In this case it is a VLAN based
subinterface attached to a physical Ethernet port.

Copyright 2022 Hitachi Energy. All rights reserved. 122

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

XMC20
Pseudo Wire Tunnel

Eth port CVP SVI Core Unit

port-x GbE PW
backplane MPLS-TP 10GbE
Eth port CVP VPLS LSP working port-1
port-y Forwarder TN MPLS-TP
PW 10GbE
ETxxx LSP protection port-2

SUP12
XMC20
Switch
Eth port CVP
port-x GbE PW
backplane VPLS
EoS port CVP Forwarder
eos-y MPLS-TP 1GbE
PW TN LSP working port-5
NUSA1, NUSA2

DSL port CVP

port-x GbE
backplane

SUSE2

Figure 84: MPLS-TP VPLS transport in XMC20

Please note:
As an alternative to a MPLS-TP port on the core unit, a MPLS-TP port on a WAN
port expansion unit can be used.

4.2.1.3 Traffic Prioritization

The MPLS-TP Transport function supports the pipe model according to RFC 3270 to perform
the following tasks:
• Ingress QoS information of the user traffic is tunneled transparently through an MPLS-TP
network, and
• Control the LSP QoS information used during the packet transport through the MPLS-TP
network.

4.2.1.4 Traffic Scheduling

The XMC20 Switch Ethernet ports all have 8 queues in egress direction. Also the XMC20
Switch internal ports to the GbE star have 8 queues in egress direction. Hence, all external and
internal XMC20 Switch ports support 8 traffic classes.
Traffic scheduling controls the order of sending packets from the 8 queues (traffic classes) at
the egress side of the Ethernet ports.
The XMC20 supports five scheduling profiles, configured per network element. At each physical
port of the XMC20 Switch one of the five profiles is configured to be applied.
The XMC20 supports two scheduling algorithms:
• Strict Priority (SP)
• Weighted Round Robin (WRR)

Copyright 2022 Hitachi Energy. All rights reserved. 123

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.2.2 Ethernet Switch with VLAN Support

4.2.2.1 Ethernet Transport

One of the main Ethernet traffic functions of the XMC20 is the VLAN Bridge (based on IEEE
802.1Q). This function is implemented on the core unit and on the Ethernet service units
ETO12, ETE24, SUP12, SUSE2, NUSA1 and NUSA2. Any port that is configured as Customer
VLAN Port (CVP) connects to the VLAN Bridge, based on the XMC20 Switch.
The XMC20 Switch consists of all switch elements implemented on the core unit and the Ether-
net service units and which are interconnected via the GbE-star or the 10 GbE-star.

Please note:
The WAN port expansion unit EXPU1 implements no switch element.
For more detailed information please refer to [1KHW028875] User Manual “Ethernet Switching”.
XMC20

Port Core Unit

Port
CVP VLAN-ID
Eth port
1 1 Port Port
GbE VLAN-ID
backplane CVP 10GbE
CVP 1 1
Eth port
2 1

ETxxx
SUP12
XMC20
Switch

Port
Port
CVP VLAN-ID
DSL port
1 1
GbE
backplane CVP 1GbE
CVP 1 5
DSL port
2 1

SUSE2

Figure 85: VLAN bridging with single tagging in XMC20

Please note:
As an alternative to an uplink port on the core unit, an uplink port on a WAN port
expansion unit can be used.

4.2.2.2 Traffic Prioritization

The transport requirements for the various types of services (voice, video, data) are completely
different. Whereas delay and retransmission is not a problem for data traffic real-time voice traf-
fic is very delay sensitive. For this reason it is essential to give more important network traffic
precedence over less important traffic. However there is no guarantee that a packet arrives on
time; it means only the packet will be handled before other packets with a lower priority.
The XMC20 Switch supports class of service (CoS) handling, according to IEEE 802.1Q. This
approach is considered as relative Quality of Service (QoS).
Alternatively to the layer 2 priority the XMC20 supports IPv4 DSCP (differentiated services code
point) for layer 3 traffic classification.

4.2.2.3 Traffic Scheduling

Refer to section 4.2.1.4 Traffic Scheduling (on page 123).

Copyright 2022 Hitachi Energy. All rights reserved. 124

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.2.2.4 LLDP
LLDP is supported as of system release R15B. It provides the following characteristics:
• Supported on Core Unit and chassis switch Service Units ports, as well as on stand-alone
bridging units SABE1, SABO1 (including backplane port).
• LLDP is disabled by default, and can be enabled on all Ethernet ports (on all 'Port Types'
except PWAC mode; PWAC ports will tunnel the protocol).
• Destination Multicast Address of transmitted LLDP PDUs can be configured per port. Values:
− “Nearest Bridge”: 01-80-C2-00-00-0E (default). Used to address the next bridge in the
LAN (independent of bridge type). LLDP PDUs are not tunneled by any bridge type.
− “Nearest non-TPMR Bridge”: 01-80-C2-00-00-03. Supported by Customer and Service
Provider Bridges. Used to address next Customer or Service Provider Bridge. LLDP
PDUs are tunneled by TPMR Bridges.
− “Nearest Customer Bridge”: 01-80-C2-00-00-00. Only supported by Customer Bridges.
Used to address the next Customer Bridge in the LAN. LLDP PDUs are tunneled by Ser-
vice Provider Bridges and TPMR Bridges.
• In ECST, LLDP is managed within the Switching main tab, under “Protocols”.
• No LLDP support in UNEM.
LLDPDUs are always untagged, similar to BPDUs.
An LLDPDU has the format as described below. The protocol contains a set of information ele-
ments (TLVs). The red TLVs are mandatory; they are always included. The blue TLVs are the
“basic management TLV set”. They are optional and only included in the LLDPDU when
enabled in the LLDP port configuration. Note that more optional TLVs exist per IEEE standard;
however, we don't support them.
• Ethernet header:
− Source MAC address
− Destination MAC address (multicast address as described above)
• LLDP:
− Chassis ID
− Port ID
− Time To Live
- Port Description
- System Name
- System Description
- System Capabilities
- Management Address (only sent on MPLS-TP ports with section MCC enabled)
• End of LLDPDU

4.2.3 Circuit Emulation Service

The XMC20 supports the transport of P12 TDM signals over the packet based network, based
on the circuit emulation service over packet (CESoP). This enables a smooth migration from
legacy TDM networks to packet based transport without changing the customer’s equipment.

Copyright 2022 Hitachi Energy. All rights reserved. 125

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

TDM TDM
TDM TDM TDM
Customer Customer
Transport Network Transport
Equipment Equipment

Migration of TDM based

transport to packet based
transport with CESoP

TDM CESoP CESoP TDM

Packet
Customer IWF or IWF or Customer
Equipment Gateway Network Gateway Equipment

Figure 86: Migration from TDM transport to packet based transport

The XMC20 supports several circuit emulation protocols for the encapsulation of TDM bit
streams as Pseudo Wires over packet switching networks (PSN):
• SAToP protocol and structure agnostic CESoETH protocol:
With this method, XMC20 provides transport of 2’048 kbit/s signals and of n x 64 kbit/s in
structured 2’048 kbit/s (P12) signals.
• CESoPSN protocol and the structure aware CESoETH protocol:
With this method, XMC20 provides transport of n x 64 kbit/ signals and of n x 64 kbit/s in
structured 2’048 kbit/s (P12) signals.
Separation of different CESoP services is done with VLANs.
With the CESoP services, the XMC20 provides applications as
• PABX connection,
• Leased line,
• Network element synchronization,
• Mobile base station access,
• CESoP aggregation node,
• n x 64 kbit/s signal grooming.
For more detailed information please refer to [1KHW028883] User Manual “SATP8”.

4.2.4 NGN Voice Application

Next Generation Network (NGN) is a convergence of different networks to provide all types of
services, from basic voice services to advanced broadband multimedia services. With NGN, the
traffic is transported in packets. NGN can be grouped in two categories:
• Telephony NGN
Telephony NGN provides telephony services to legacy terminals such as analog and ISDN
phones that are not NGN capable (PSTN and ISDN-BA emulation). It focuses on class 5 and
class 4 switch replacements.
• Multimedia NGN
Multimedia NGN provides advanced multimedia services to intelligent terminals (e.g. IP
phones).
In a SIP NGN, the signaling and transport functions are both located in the gateway. The SIP
softswitch functions “proxy server” and “registrar server” just support the routing of the calls,
they are not mandatory. Accordingly, the following elements are introduced by the SIP NGN
architecture:

Copyright 2022 Hitachi Energy. All rights reserved. 126

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

• The gateway (GW) is responsible for the media stream conversion, i.e. the conversion of
TDM based voice signals into IP packets and the signaling protocol termination. In Figure 87,
two types of Media Gateways are shown, the Access Gateway and the Trunking Gateway:
− The Access Gateway (AG) supports line side interfaces, e.g. for analog or ISDN-BA
phones.
− The Trunking Gateway is located between the PSTN and the packet network. It termi-
nates circuit-switched trunks in the PSTN and virtual circuits in the packet network. It is
controlled by a SIP enabled softswitch with the H.248/MEGACO protocol.
• There are two types of softswitches:
− The SIP softswitch contains the SIP proxy server and SIP registrar server functions.
The registrar makes the location of a subscriber available to the proxy server.
The proxy forwards the SIP call control messages into the network.
− The SIP/MEGACO softswitch handles both the SIP and the H.248/MEGACO protocols.
This type of softswitch controls the trunking gateway and implements also the signaling
gateway to the SS7.

Softswitch: Softswitch:
- Registrar - Signaling Gateway SS7
- Proxy - SIP - H.248 MGC

Class 5
Switch

Analog Phone VoIP IP Trunking PSTN

Access Gateway Network Gateway

ISDN Phone

Figure 87: Basic architecture of SIP NGN telephony with XMC20

The XMC20 provides the functions of an access gateway for the telephony NGN, serving PSTN
(POTS) and ISDN-BA subscribers.
On the line side, PSTN units (SUPM1 and SUPM2) provide the PSTN service access and ISDN
units (ISDN4) provide the ISDN-BA service access.
The IP subscriber (media) gateway unit (VOIP1) provides the media conversion and bridges the
traditional telephone to telephony NGN.
The IP traffic transport to the core network is provided by the core unit or WAN port expansion
unit with its electrical and optical GbE interfaces.
For more detailed information please refer to [1KHW028879] User Manual “VOIP1”.

4.2.5 Security Features

The XMC20 offers security features to protect the NE from attacks of a malicious user.

4.2.5.1 Ingress Storm Control

The ingress storm control feature limits the ingress traffic of the following traffic types:
• Unknown unicast,
• Known unicast,
• Multicast, and
• Broadcast.
The traffic types can be enabled individually per VLAN Bridge port. The traffic threshold is con-
figurable between 0% and 100% of the selected port speed.

Copyright 2022 Hitachi Energy. All rights reserved. 127

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.2.5.2 Rate Limiters

The rate limiting (policing) function is available for Customer VLAN Ports (CVP), for Pseudo
Wire Access Circuit (PWAC) ports and for Router Ports as a rate limiter. It is available on the
following core and service units:
• CENT2,
• COGE7, COGE7-F,
• COGE5, COGE5-F,
• EXPU1,
• ETE24,
• ETO12, ETO12-F,
• SUP12,
• VRX10, VRX10-F,
• SABE1,
• SABO1, SABO1-F,
• NUSA1, NUSA1-F,
• NUSA2.
The rate limiter can be configured to
− 1 Rate - 2 Color,
− 1 Rate - 3 Color, or
− 2 Rate - 3 Color.
The rate limiters are implemented according to MEF 10.3. The Coupling Flag is fixed to 1, the
Color Mode is fixed to Color Blind. The rate limiter can be port based or VLAN based.
When using the XMC20 as MPLS-TP network element the incoming traffic on an MPLS-TP tun-
nel can be rate limited using LSP rate limiters.
The rate limiter operates in the 1 Rate - 2 Color mode and is implemented according to MEF
10.3. The Coupling Flag is fixed to 1, the Color Mode is fixed to Color Blind.

4.2.5.3 Egress Port Shapers

The XMC20 network element implements on all egress ports of the XMC20 Switch port based
shapers.
The port shaper is implemented using a token bucket with a constant fill rate, corresponding to
the shaping rate, and a token bucket size corresponding to the burst size.
The egress shaper has the goal to limit the egress traffic to a mean bit rate.

4.2.5.4 Egress Class Type Shapers

The XMC20 network element implements on the egress ports port-1 to port-4 of the CENT2
core unit class type based shapers.
The class type shaper is implemented using a token bucket with a constant fill rate, correspond-
ing to the shaping rate, and a token bucket size corresponding to the burst size.
The egress class type shaper has the goal to limit the egress traffic of certain class type traffic
flows to a mean bit rate.

4.2.5.5 Firewalls
The XMC20 network element implements a SW and a HW firewall to protect the NE CPU.
The SW firewall has the goal to defend the system against an NE CPU overload and against
forwarding of unsolicited packets.
The HW firewall covers the core and service units Ethernet front ports managed by the XMC20
Switch, excluding the local management interface. The HW firewall implements an overall rate
limiter.

Copyright 2022 Hitachi Energy. All rights reserved. 128

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.2.5.6 Access Control Lists (ACLs)

Access control lists provide the network operator with filters to manage traffic allowed to enter
the network at the UNI ports.
ACLs are supported on UNI ports:
• CVP ports
• PWAC ports
• ACLs are supported on
− Chassis switch UNI ports on service units: ETE24, ETO12, ETO12-F, SUP12, SUSE2,
SUSE2-F, NUSA1, NUSA1-F, NUSA2 (Ethernet and EoS ports 1-12).
• ACLs are not supported on
− MPLS-TP ports,
− MPLS-TP PWs,
− NUSAx EPL ports,
− VRX10, VRX10-F ports.
For each UNI interface the user can choose to apply ACLs at either
• Ethernet (L2)
• IPv4/ARP (L3/L4)
You cannot mix both types at the same UNI port. The table below summarizes how this choice
impacts the available filters and applicable packets:

ACL Type Ethernet IPv4 ACE ARP ACE Match IPv4 Match ARP Match IPv6 Match other
ACE Packets Packet Packets Packets
IPv4/ARP       
Ethernet       

If the user chooses IPv4/ARP ACLs, IPv6 and other L2 packets pass through without access
control.

4.2.5.6.1 ACLs
The structure of an ACL is:
• It contains an ordered list of ACE filter rules.
• The ACE filter rules are processed in order and stop at the first matching filter
• Each ACE can specify a forward or drop action
• An ACL may contain either
− Ethernet ACEs
− IPv4 and ARP ACEs
• If packet does not match any ACE then it will be default forward

4.2.5.6.2 ACL interface associations

An ACL is applied at an interface by making an association between a physical UNI port, an
ACL and the direction (ingress only).
A physical UNI port and direction may be associated with multiple ACLs. When a port is associ-
ated with multiple ACLs, the ACLs are processed in ascending order of association sequence
index (see information model).

4.2.5.6.3 ACE types

The following types of ACE are supported:
• Ethernet
• IPv4

Copyright 2022 Hitachi Energy. All rights reserved. 129

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

• ARP
An ACE may match zero or more packet header fields contents detailed in the table below. If a
field is not specified then any content matches and if no fields are specified then the packet of
that type always matches.
• Address fields contain both value and mask so that filters can match on IP subnets or a set
of MAC addresses.
• TCP/UDP port fields allow range to allow either specific ports or a range to be specified
• All other fields are single value only.

4.3 TDM Traffic Functions

4.3.1 SDH Transport

The SDH service units STM14, NUSA1 and NUSA2 can be configured as an SDH access sys-
tem with termination and add/drop functionality from STM-16, STM-4 and STM-1 trunks. Typical
applications are the termination of VC-n traffic in linear networks (terminal multiplexer TM) and
add/drop of VC-n traffic in linear or ring networks (add/drop multiplexer ADM).
The following SDH interfaces are supported:
• two interfaces STM-16 or STM-4 (NUSA2 and NUSA1):
− STM-16 optical or
− STM-4 optical,
• two interfaces STM-4 or STM-1 (STM14, NUSA1 and NUSA2):
− STM-4 optical or
− STM-1 electrical or optical,
• two interfaces STM-1 (STM14):
− 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 ser-
vice unit configuration.
The STM14, NUSA1 and NUSA2 units access TDM services via the PBUS. Up to 64 or 67 P12
tributary signals can directly be accessed and transported in the SDH network via any of the
available SDH interfaces.
The NUSA2 unit accesses TDM services also via its E12 front interfaces. Up to 48 transparent
P12 tributary signals can directly be accessed and transported in the SDH network via any of
the available SDH interfaces.

Copyright 2022 Hitachi Energy. All rights reserved. 130

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

10 / 10 / 10 / 10 /
100 / 100 / 100 / 100 /
1000 1000 1000 1000 STM-4 / STM-4 /
STM-1 STM-1
BASE-T BASE-T BASE-T BASE-T STM-1 STM-1

ETH ETH ETH ETH SDH SDH SDH SDH STM14

PHY PHY PHY PHY SFP SFP SFP SFP
4x 4x 1x 1x
AU-4 AU-4 AU-4 AU-4
AU-4 Cross Connect
24 x 504 x
TU-3 TU-12
TU-3 TU-12
Cross Connect Cross Connect
8x 9x 100 x 67 x
VC-4 VC-3 VC-12 VC-12
EoS P-12

2 x Mux 2:1

1Gb Ethernet PBUS

Figure 88: STM14 overview

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

NUSA1
ETH ETH ETH ETH SDH SDH SDH SDH
PHY PHY PHY PHY SFP SFP SFP SFP

4x 4x 16 x 16 x
AU-4 AU-4 AU-4 AU-4
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
VC-4 VC-3 VC-12 VC-12
EoS P-12
2 x 1GbE
8 x 100MbE
Ethernet Switch

10Gb Ethernet 1Gb Ethernet PBUS

Figure 89: NUSA1 overview

Copyright 2022 Hitachi Energy. All rights reserved. 131

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

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 NUSA2

E12
PHY PHY PHY PHY SFP SFP SFP SFP

4x 4x 16 x 16 x
AU-4 AU-4 AU-4 AU-4
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

10Gb Ethernet 1Gb Ethernet PBUS

Figure 90: NUSA2 overview

4.3.2 EoS Transport

The STM14, NUSA1 and NUSA2 units access Ethernet services via the unit’s four electrical 10/
100/1000BASE-T front interfaces and the Gb-Ethernet star from the core unit(s).
With the STM14 unit, Ethernet traffic is transported over up to four Ethernet over SDH (EoS)
groups. Each EoS group consists of a number of virtual channels (VC):
• up to 8 x VC-4,
• up to 9 x VC-3,
• up to 63 x VC-12 per EoS group, up to 100 x VC-12 per STM14 unit.
With the NUSA1 and NUSA2 units, when using the unswitched mode, Ethernet traffic from the
Ethernet front ports is transported over four Ethernet over SDH (EoS) groups bypassing the
XMC20 Switch. In addition Ethernet traffic from the XMC20 Switch is transported over up to 28
EoS groups. When using the switched mode, i.e. the Ethernet front ports access the XMC20
Switch, Ethernet traffic from the XMC20 Switch is transported over up to 32 EoS groups.

Please note:
Using the MPLS-TP Transport function the number of EoS groups is limited to 12.
Each EoS group consists of a number of virtual channels (VC):
• up to 12 x VC-4,
• up to 24 x VC-3,
• up to 63 x VC-12 per EoS group, up to 252 x VC-12 per NUSA1 or NUSA2 unit.
The EoS groups use virtual concatenation of the VCs and support the link capacity adjustment
scheme (LCAS).

Copyright 2022 Hitachi Energy. All rights reserved. 132

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

On the STM14 unit two of the four EoS channels are shared with the connections to the Gb-
Ethernet star. The Gb Ethernet star connects the STM14 unit to the working and protecting core
units.

4.3.3 PDH Transport

The TDM service units STM14, NUSA1, NUSA2, SELI8, SATP8 and SDSL8 can be used as
transport units for PDH signals.
The XMC20 supports the following PDH signals:
• P12 (2048 kbit/s) without a signal structure, plesiochronous to the system clock.
• P12 (2048 kbit/s) with a signal structure according to ITU-T G.704, synchronous to the sys-
tem clock,
− with or without CRC4 in time slot 0,
− with or without CAS in time slot 16.
• P0_nc (n x 64 kbit/s) synchronous to the system clock.
• P0 (64 kbit/s) synchronous to the system clock.
All PDH signals from the tributary side and from the transport side access the PBUS. The PBUS
with its access circuits acts as a blocking free distributed cross connect system with a switching
capacity of 128 x P12.
P12 signals are terminated (in point-to-point network applications) or can be transparently
through connected (in linear or ring network applications).
The SELI8 and SATP8 units provide a transport capacity of 8 x P12 with their eight E1 (ITU-T
G.703) interfaces. They connect to another E1 interface. P0 and P0_nc signals are multiplexed
to P12 signals for the transport.
The SELI8 and SATP8 units can also act as PDH tributary units.
The SDSL8 unit provides a transport capacity of up to 8 x P12 with its eight SHDSL (ITU-T
G.991.2) interfaces. It connects to another SHDSL interface in trunk mode. P0 and P0_nc sig-
nals can be multiplexed to P12 signals for the transport. SDSL8 supports also transport modes
with a bandwidth from 1 to 32 time slots, using a minimum transport capacity corresponding to 3
time slots.
The SDSL8 unit can also act as a PDH tributary unit, accessing one of the available SHDSL
CPEs. The CPE then provides the E1 or data interfaces.
The STM14, NUSA1 and NUSA2 units offer a transport capacity of 64 x P12 with their STM-16,
STM-4 or STM-1 interfaces. The NUSA2 unit offers in addition a transport capacity of 48 x P12
from the E12 front ports. The SDH service units use the asynchronous mapping mode of a P12
signal to a VC-12. P0 and P0_nc signals are multiplexed to P12 signals for the transport.

Please note:
The STM14 supports up to 67 x P12 access to PBUS.
→ This capacity is only usable with at least 3 x P12 unidirectional traffic.

Copyright 2022 Hitachi Energy. All rights reserved. 133

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

8x 8x 4x 4x 4x
E1 SHDSL STM-x STM-x STM-x

SDH SDH SDH

E1 SHDSL
SFP SFP SFP
AU-4 AU-4 AU-4
SELI8, SATP8

AU-4 AU-4 AU-4

Cross Connect Cross Connect Cross Connect

NUSA2
SDSL8
PDH

STM14
TU-12 TU-12 TU-12
transport

NUSA1
TU-12 TU-12 TU-12
Cross Connect Cross Connect Cross Connect
VC-12 VC-12 VC-12 VC-12
P-12 P-12 P-12 P-12 P-12 P-12

PBUS E12

P-12 P-12 P-12 P-12

Voice Data E1 SHDSL

PDH
tributary

SHDSL
CPE

P-12

Figure 91: PDH transport overview

4.3.4 EoP Transport

The ETAG1 unit accesses Ethernet services via the unit’s four electrical 10/100BASE-TX front
interfaces. The TUDA1 unit offers one 10/100BASE-TX front interface.
The ETAG1 unit supports bridging and routing applications. Routing protocols are OSPF, RIP or
static routing.
With routing the IP packets are forwarded from the LAN to the PDH transport with IP over PPP
or over multilink PPP.
With bridging the Ethernet frames are forwarded from the LAN to the PDH transport with one of
the following bridging modes:
• MAC to HDLC,
• PPP,
• Multilink PPP.
ETAG1 supports up to 64 TDM transport interfaces with a total capacity of up to 32’764 kbit/s.
With the TUDA1 unit the Ethernet frames are forwarded from the LAN to the PDH transport with
MAC to HDLC bridging. TUDA1 supports one TDM transport interface, the maximum transport
capacity is 31 x 64 kbit/s.
With a DTM CPE connected to a SDSL8 unit the Ethernet frames are forwarded from the LAN
to the PDH transport with MAC to HDLC bridging. The DTM CPE support one TDM transport
interface for Ethernet traffic, the maximum transport capacity is 2048 kbit/s.

Copyright 2022 Hitachi Energy. All rights reserved. 134

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.3.5 Voice Services

The XMC20 voice service units offer different analog voice interfaces:
• The SUPM1 unit has 16 FXS 2-wire interfaces, the SUPM2 unit has 64 FXS 2-wire inter-
faces.
The units connect to a subscribers telephone set. In downstream direction the interfaces
generate ringing, metering and polarity reversal, and provide the line feeding. In upstream
direction the interfaces detect onhook and offhook states, ground key states, pulse dialing
and flash pulses. DTMF dialing is transported inband.
Signaling information is transported via CAS.
• The TUXA1 unit has 12 FXO 2-wire interfaces.
It connects to a local exchange. In downstream direction the interfaces detect ringing, meter-
ing and polarity reversal. In upstream direction the interfaces generate onhook and offhook
states, ground key states, pulse dialing and flash pulses.
Signaling information is transported via CAS.
• The TUEM1 unit has 8 analog 2-wire or 4-wire voice interfaces with 2 E&M signaling inter-
faces per voice interface.
E&M signaling information is transported via CAS. TUEM1 supports the E&M interface types
I to V.
It connects to a subscribers telephone set which must be powered with a local battery. The
TUEM1 can also be used to interconnect local exchanges using the E&M interfaces.
• The IMAG1 unit has 8 analog 2-wire magneto line voice interfaces.
The IMAG1 unit converts the magneto line voice and signaling to the E&M voice and signal-
ing format. It operates in conjunction with the TUEM1 unit.
The IMAG1 connects to a subscribers telephone set which must be powered with a local bat-
tery.
For the transport over a TDM network each voice channel uses one time slot (64 kbit/s) and
uses CAS for the signaling information.
Figure 92, Figure 93 and Figure 94 show POTS, E&M and Magneto line voice applications with
point to point network scenarios.

TDM TDM
Network Network

Inter- Inter- Inter- Inter-

face PDH face face PDH face
transport transport
P-12 P-12 P-12 P-12

PBUS PBUS PBUS PBUS

P-12 P-12 P-12 P-12

Phone to
Phone to
SUPM1
SUPM1
SUPM1

local
TUXA1

phone
exchange
application
application
Voice Voice Voice Voice

16 x 16 x 16 x 12 x
FXS FXS FXS FXO

Figure 92: POTS voice services overview

Copyright 2022 Hitachi Energy. All rights reserved. 135

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

TDM TDM
Network Network

Inter- Inter- Inter- Inter-

face PDH face face PDH face
transport transport
P-12 P-12 P-12 P-12

PBUS PBUS PBUS PBUS

P-12 P-12 P-12 Local P-12

Phone to exchange to

TUEM1
TUEM1
TUEM1
TUEM1

phone local
application exchange
Voice Voice Voice application Voice

8x 8x 8x 8x
E&M E&M E&M E&M

Local Local
battery battery
phone phone

Figure 93: E&M voice services overview

TDM
Network

Inter- Inter-
face PDH face
transport
P-12 P-12

PBUS PBUS

P-12 P-12
Phone to
TUEM1
TUEM1

IMAG1
IMAG1

phone
application
Voice Voice Voice Voice

Telephone set with E&M voice E&M voice Telephone set with
magneto handle and and signaling and signaling magneto handle and
local battery local battery

Figure 94: Magneto line voice services overview

Figure 95 shows a voice application example with a multipoint to multipoint network scenario. All
telephone sets connected to the voice network are interconnected. The multipoint network sce-
nario makes use of the voice conference feature offered by the TUEM1 unit.

Copyright 2022 Hitachi Energy. All rights reserved. 136

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

Since there is no local exchange involved the telephone sets must provide the call setup and
tear down procedures by their own or with the support of the voice service unit:
• With the SUPM1 unit operated in the phone-phone mode, as soon as one subscriber goes
offhook, all telephone sets connected to the multipoint network start ringing.
• When using the TUEM1 unit the connected telephone sets must use inband signaling to
address a specific other telephone set. This type of telephone sets supports also group calls.
In this application the E&M signaling port is not used.
Beside the multipoint to multipoint network scenario there is also a simpler point to multipoint
network scenario available. One master telephone set can access all slave telephone sets, but
the slave telephone sets can only access the master telephone set.

TDM

PBUS
Network
PBUS

Conference TDM

PBUS
Network
TUEM1

SUPM1 TDM
TUEM1 Network

PBUS

SUPM1
TUEM1
Conference
TUEM1

PDH transport

Figure 95: Multipoint voice services overview

4.3.6 Legacy Data Services

The XMC20 legacy data service units offer different data interfaces:
• The TUGE1 unit has 8 E0 (ITU-T G.703) codirectional 64 kbit/s interfaces or alternatively 2
E0 (ITU-T G.703) contradirectional 64 kbit/s interfaces.
It connects to a subscribers DTE. The interface provides the synchronous data service.
• The TUDA1 unit has 4 data interfaces. Each data port is configurable to
− V.24/V.28, or
− V.35 (Appendix II), or
− X.24/V.11, or
− RS485 2-wire, or

Copyright 2022 Hitachi Energy. All rights reserved. 137

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

− RS485 4 wire.
The TUDA1 plays the DCE role and connects to a subscribers DTE.
The interface provides the asynchronous data service for subrates from 0.6 kbit/s to
38.4 kbit/s and synchronous data service for subrates from 0.6 kbit/s to 56 kbit/s.
The interface provides the synchronous data service for nx64 data rates from 1x64 kbit/s to
32x64 kbit/s with codirectional or contradirectional timing operation.
The TUDA1 offers several data conferences where the data signals of the connected confer-
ence participants are superimposed with a wired AND function. This implies that the idle
state of a DTE must be an all-1 signal.
CAS can be used to transport some specific interface control signals.
• The SDSL8 with a connected DTM CPE offers one data interface, configurable to
− V.24, or
− V.35, or
− V.36, or
− X.21.
The DTM CPE plays the DCE role and connects to a subscribers DTE.
The interface provides the asynchronous data service for subrates from 0.6 kbit/s to
38.4 kbit/s and synchronous data service for subrates from 0.6 kbit/s to 56 kbit/s.
The interface provides the synchronous data service for nx64 data rates from 1x64 kbit/s to
32x64 kbit/s with codirectional or contradirectional timing operation.
Figure 96 shows data applications with point to point network scenarios.

TDM TDM
Network Network

Inter- Inter- Inter- Inter-

face PDH face face PDH face
transport transport
P-12 P-12 P-12 P-12

PBUS PBUS PBUS PBUS

P-12 P-12 P-12 P-12 TUGE1

TUGE1
TUDA1

SDSL8

Data SHDSL Data Data

4x 8x 8x
X.24/V.11 SHDSL E0 E0
V.24/V.28
V.35
CPE

RS485

Data

1x
X.21
V.24
V.35
V.36

Figure 96: Data services overview

Copyright 2022 Hitachi Energy. All rights reserved. 138

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

Figure 97 shows a data application example with a multipoint to multipoint network scenario. All
DTEs connected to the data network are interconnected. The multipoint network scenario
makes use of the data conference feature offered by the TUDA1 unit. All conference partici-
pants must be configured to the same bandwidth.
Beside the multipoint to multipoint network scenario there is also a simpler point to multipoint
network scenario available. One master DTE can access all slave DTEs, but the slave DTEs
can only connect to the master DTE.

TDM

PBUS
Network
PBUS

Conference TDM

PBUS
Network
TUDA1

TUDA1 TDM
TUGE1 Network

PBUS

TUDA1
TUGE1
Conference
TUDA1

PDH transport

Figure 97: Multipoint data services overview

4.4 Protection Concept

4.4.1 Overview
XMC20 network elements are used in different topologies, such as ring, star, and linear/daisy-
chain structures. In all topologies, the protection concept has to provide continuous availability
of the XMC20 network in the case of link and equipment failures.
All the XMC20 network elements support rapid spanning tree protocol (RSTP) for the implemen-
tation of link protection.
The XMC20 network elements provide 1:1 traffic protection for the MPLS-TP tunnels using the
VPWS and VPLS services.
The XMC20 network elements provide 1+1 traffic protection for the TDM signals on the PBUS
and on the STM14, NUSA1 and NUSA2 units.
The XMC20 network elements support 1:1 equipment protection for the core unit CENT2,
COGE7 and COGE5, and also for the STM14, NUSA1, NUSA2, VOIP1, VFTLX, ETAG1,
VRX10 1, TUEM1 and TUDA1 service units.

Please note:
The XMC22 supports no equipment protection for the COGE5, NUSA1 and NUSA2
units.

1. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.

Copyright 2022 Hitachi Energy. All rights reserved. 139

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

With 1:1 equipment protection, a protecting resource is provided for a single working resource.

4.4.2 Equipment Protection of the Core Unit

The XMC25 R2, XMC25 and XMC23 provide 1:1 equipment protection for the core unit.
The working unit is plugged in slot 11 of the subrack. The redundant unit is plugged in slot 13 of
the subrack. Per default the working unit is the active unit, performing the subrack control func-
tions, and the redundant unit is the standby unit.
The standby core unit is in hot (CENT2) or warm (COGE7 and COGE5) standby mode. The NE
configuration and NE database stored on the standby unit are updated with every “Save” opera-
tion and are thus identical to the information on the active unit. Hence, the standby unit can take
over the control of the system with a cloned database.
The switch circuits on the active and the standby core unit are both part of the XMC20 Switch.
This means also that all Ethernet front ports on the standby core unit, except the local manage-
ment port, are active.
The switch-over can affect traffic for a short period. The switch-over due to an equipment failure
is non-revertive.
The control and monitoring of the core unit equipment protection are functions on the NE level
and do not require special configuration on the core unit level.

4.4.3 Equipment Protection of Service Units

The service units
• NUSA1,
• NUSA2,
• STM14,
• VOIP1,
• VFTLX,
• ETAG1,
• VRX10, 1
• TUEM1, and
• TUDA1
support 1:1 equipment protection.
It is possible to backup a working service unit with one backup service unit of the same HW type
and running the same ESW.
On the service units the external interfaces cannot be protected.
• On the STM14 and NUSA1 units only the traffic with PBUS access can be protected.
• On the NUSA2 unit the traffic with PBUS access and traffic from the E12 front ports can be
protected.
• On the TUEM1 and TUDA1 units only the conference circuits can be protected.
• On the ETAG1 units only the bridging and routing functions can be protected.
• On the VRX10 units the routing functions and the external interfaces (using an external
bridge) can be protected. 1
The switch-over can affect traffic for a short period. The switch-over due to an equipment failure
is non-revertive.
A status dialog on the unit level allows you to control and monitor the service unit equipment
protection.

1. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.

Copyright 2022 Hitachi Energy. All rights reserved. 140

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

4.4.4 Ethernet Traffic Protection

Redundancy improves the availability of the network by implementing alter-native paths. Having
multiple paths for data to traverse the network allows for a single path to be disrupted without
impacting the connectivity of devices on the network.
However because of multiple paths exist to a destination a protocol is needed to prevent loops
in the ring.

4.4.4.1 Linear Protection Switching (LPS) for MPLS-TP

The XMC20 supports linear protection switching (LPS) for bidirectional LSPs between two
LERs. LPS makes use of the BFD continuity check (CC) for the end-to-end supervision of the
working and of the protection LSP, where the LOC defect is used as signal fail (SF) condition.
LPS supports the 1:1 protection architecture type:
• Under normal conditions the user traffic is routed exclusively through the working LSP. The
protection LSP remains free.
• In case of a fault condition the user traffic is switched over from the working LSP to the pro-
tection LSP at both ends of the tunnel, i.e. the LPS switching type is bidirectional. This keeps
the LSP as co-routed bidirectional LSP.
The LPS operation type can be revertive or non-revertive.

4.4.4.2 Rapid spanning tree protocol (RSTP)

In switched networks where availability is important redundant paths must be created to assure
connectivity. However, this type of network configuration can result in frames circulating indefi-
nitely (broadcast storms) and consequently crashing the network. In order to avoid this problem
the spanning tree protocol (STP, IEEE 802.1D) has traditionally been implemented on switches.
STP reduces the physical topology to an active tree topology that reaches all segments of the
network. To achieve this, the switches/bridges exchange BPDU (bridge packet data units) proto-
col frames to coordinate which ports will be active (designated or root port) forwarding traffic
and which will remain as backup (alternate, backup or disabled port) discarding traffic.
When a port failure is detected on a designated port then an alternate port will become desig-
nated. The election of designated, alternate and backup (second port on a switch) ports is done
according to the path cost, physical topology and port priority they are assigned.
For inter-operation purposes of Ethernet LANs and MPLS-TP the XMC20 supports the R-
(Reverse Layer 2 Gateway Protocol). A port configured to the R- mode acts as a pseudo root
bridge with a manually configured pseudo MAC address.
The time STP requires to reconfigure the network topology (convergence time) is dependent on
the network topology and number of switches. This time is relatively long in STP and therefore
RSTP as an improved version of this protocol, reducing significantly the convergence time. In
order to profit from RSTP all switches have to work on this mode, otherwise they will work in
STP mode to keep compatibility.
The XMC20 implements RSTP 802.1D-2004 (compatible with STP).
With RSTP, the convergence time is roughly in the range of 300 ms (for the point-to-point link
between 2 switches) to 5 seconds (for ring topologies with up to 19 switches).

4.4.4.3 Ethernet ring protection switching (ERPS)

The XMC20 implements ERPS ITU G.8032v2 (03/2010) with configuration of the ring ID as
described in G.8032 (02/2012).
ERPS provides a protection mechanism that has been designed to operate in topologies that
are commonly deployed in carrier networks (i.e. ring topologies) and meets the stringent avail-
ability requirements of today’s services.
ERPS allows to switch within 50 ms in an Ethernet ring as it is possible in traditional PDH and
SDH networks.

Copyright 2022 Hitachi Energy. All rights reserved. 141

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

Please note:
On the XMC20 ERPS can only coexist with RSTP but not with MSTP.
However on a physical port either ERPS or RSTP can be activated.

4.4.5 TDM Traffic Protection

The SDH and PDH traffic in the XMC20 network element can be 1+1 protected.

working working
TDM
protecting network protecting

Server Server Server Server

layer layer layer layer
XMC20

XMC20
Bridge Selector
Transmit signal Receive signal

Figure 98: 1+1 protection

A signal to be protected is bridged to the working and protecting channel at the transmitting net-
work element. At the receiving network element the working or protecting signal is selected
dependent of the received signal quality.
Protection switching can be
• Unidirectional or bidirectional,
• Revertive or non revertive.

Please note:
The availability of protection parameters as
− holdoff time,
− guard time,
− wait to restore time,
− operation type revertive or non-revertive,
− CAS AIS supervision,
− switching type unidirectional or bidirectional,
is dependent of the unit and application.
→ Please refer to the relevant user manuals.
XMC20 supports
• SNCP/I: Inherently monitored subnetwork connection protection.
SNCP/I is supported for the following traffic signal types:
− VC-4 unterminated,
− VC-3 unterminated,
− VC-12 unterminated,
− P12 unstructured (transparent mode),
− P0_nc without CAS AIS supervision.

Copyright 2022 Hitachi Energy. All rights reserved. 142

XMC20 | SYSTEM DESCRIPTION XMC20 TRAFFIC AND EQUIPMENT FUNCTIONS

• SNCP/N: Non-intrusively monitored subnetwork connection protection.

SNCP/N is supported for the following traffic signal types:
− VC-4 terminated,
− VC-3 terminated,
− VC-12 terminated,
− P12 structured (monitored mode, future release).
• LTP: Linear trail protection.
LTP is supported for the following traffic signal type:
− P0_nc with CAS AIS supervision.
The protection mode of a connection termination point (e.g. SNCP, LTP) is given by the capabil-
ities of the relevant unit or application respectively. The protection mode may be fixed or config-
urable by the application (implicit or explicit configuration). Please refer to the corresponding
unit user manuals.
In addition the STM14, NUSA1 and NUSA2 units support 1+1 multiplex section protection
(MSP). Please refer to the STM14, NUSA1 or NUSA2 user manual for further information.

Copyright 2022 Hitachi Energy. All rights reserved. 143

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

5 Network Management System

5.1 Management Systems Overview

A single XMC20 subrack is considered as a network element (NE).
To provide economic and flexible management for all NE configurations, the XMC20 manage-
ment concept is based on a layer approach, as shown in Figure 99:
• the ECST element manager (EM) for local and remote management activities of a single
XMC20,
• an SNMP interface provided by the XMC20 (traps and inform only in the current release, and
basic configuration of the SNMP parameters),
• Syslog provides a reporting function to logging destination servers,
• the UNEM network element manager (NEM) for remote management of a XMC20 network
from the network management center / network operation center,
• the UNEM offers northbound interfaces (NBI) for the OSS integration,
• the DIRAC server deploys the Master Keys for the MPLS tunnel encryption to the SECU1
Crypto Engines, and forwards the encrypted MPLS tunnel configuration from UNEM to the
SECU1 Crypto Engines.
The element managers and management access for the different network element types are
according to the following tables:

Table 18: Element managers and NE types

NE type UNEM ECST DIRAC
XMC25 R2 yes yes no
XMC25 yes yes no
XMC23 yes yes no
XMC22 yes yes no
UMUX yes no no
SECU1 unit no 1 yes yes

1. MPLS tunnel encryption configuration via DIRAC server

Table 19: Element managers and management access

Management access UNEM ECST DIRAC
Direct Proprietary with TCP/IP over Ethernet no yes no
Remote Proprietary with TCP/IP over Ethernet yes yes no
Remote Proprietary with encrypted HTTPS over Ethernet no no yes

Copyright 2022 Hitachi Energy. All rights reserved. 144

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

Network manage- Element manage- Crypto Engine

ment with UNEM ment with ECST management with
DIRAC

Hitachi Energy pro- Hitachi Energy pro-

prietary over TCP/ prietary over
IP HTTPS

Ethernet LAN

Element manage-
Communication ment with ECST
Network

XMC20 NE

Ethernet LAN Ethernet point-to-point

connection

XMC20
Network

Figure 99: XMC20 management concept overview

For secure management access, the XMC20 supports SSH for the encryption of the manage-
ment communication to/from the XMC20.
Once provisioned, the XMC20 is able to run its services autonomously, without any interaction
with the management system.
The XMC20 configuration is stored on the core unit, i.e. this information is used to reconfigure
XMC20 units that have been restarted or replaced.

5.2 ECST
The ECST can configure and manage the XMC20 equipment. It has a graphical user interface
(GUI) with shelf view and tree based view to manage an NE. The GUI provides a structured
user interface with dialogs, selection boxes, graphs and mouse selection.
The ECST provides local or remote access to one NE at a time, either for NE configuration or
for NE status and/or performance monitoring. The ECST can run several instances for the man-
agement of several NEs at the same time.
The ECST can be connected to an NE in one of the following ways:
• Local access via the Ethernet local management port or via an Ethernet network interface on
the core unit or on an Ethernet service unit.
• Remote access via an Ethernet network, with a connection to an Ethernet interface on the
core unit or on an Ethernet service unit.
The XMC20 management communication is based on TCP/IP.
With ECST, the configuration can be done with the XMC20 on line, i.e. units are configured if
they are physically available in the subrack. The configuration is stored in the database on the
NE and not interpreted by ECST, i.e. the parameter and resource check is done on the NE.

Copyright 2022 Hitachi Energy. All rights reserved. 145

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

The configuration can be saved on the element manager for backup, and can be restored to the
network element when required.
Alternatively the configuration can be done offline with a XMC20 simulation. Any unit 1 can be
placed in a virtual subrack and configured. The configuration of the simulated XMC20 has to be
saved and can then be restored to the real network element later on.
The ECST is used for initial commissioning, NE configuration, fault management, and perfor-
mance management.
The ECST provides the following functions for the management of NEs of small networks:
• Configuration (including the configuration of profiles),
• Fault management (alarm list),
• Performance monitoring,
• Status and diagnostic (loops etc.),
• Line testing,
• Management of user authentication and authorization by user classes,
• NE inventory (HW, SW, resource utilization),
• SW management (upgrade of ESW),
The following security features are provided by the ECST:
• Local user authentication via user classes and passwords, or authentication via a RADIUS
server,
• Local user authentication via public/private keys,
• SSH encryption for the management communication,
• SNMPv3 for the management communication.
ECST can be deployed on PCs or Laptops running the Windows or Linux operating systems as
listed in [1KHW028868] Release Note “XMC20 System Release R16A”.

5.3 Syslog
The XMC20 provides a syslog message sender device that is able to send messages from dif-
ferent sources to up to ten syslog destinations. The XMC20 supports different syslog facilities,
as e.g.
• Alarm logbook,
• Event logbook,
• Configuration logbook,
• Equipment logbook,
• Session logbook,
• System.
The IP addresses of the syslog destinations can be configured in the XMC20. Each destination
entity provides a message filter configuration for the System and Alarm logbook facilities that
defines up to which severity syslog messages are sent to the respective destination.

5.4 SNMP
The XMC20 NEs offer a standard SNMP interface towards network management systems. With
the current release of the XMC20, the following MIBs are supported:
• Agent MIBs
− SNMPv2-MIB (RFC 3418)
− SNMP-FRAMEWORK-MIB (RFC 3411)
− SNMP-TARGET-MIB (RFC 3413)

1. The SECU1 in offline mode is not configurable

Copyright 2022 Hitachi Energy. All rights reserved. 146

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

− SNMP-NOTIFICATION-MIB (RFC 3413)

− SNMP-VIEW-BASED-ACM-MIB (RFC 3415)
− SNMP-COMMUNITY-MIB (RFC 3584)
− SNMP-USER-BASED-SM-MIB (RFC 3414)
− SNMPv2-TC (RFC 2579)
• Other MIBs
− RMON2-MIB (RFC 4502)
− RMON-MIB (RFC 2819)
− BRIDGE-MIB (RFC 4188)
− Q-BRIDGE-MIB (RFC 4363)
− IANAifTypeMIB
− IF-MIB (RFC 2863)
− ENTITY-MIB (RFC 6933)
− INET-ADDRESS-MIB (RFC 4001)
− ENTITY-SENSOR-MIB (RFC 3433)
− ALARM-MIB (RFC 3877)
− PW-TC-STD-MIB (RFC 5542)
• Private MIBs
− XMC-SMI
− XMC-IF-EXT-MIB
− XMC-IANA-BFD-TC-STD-MIB
− XMC-BFD-STD-MIB
− XMC-MPLS-QOS-EXT-MIB
− XMC-UNI-EVC-MIB
− XMC-ETH-PORT-MIB
− XMC-NE-MIB
− XMC-ALARM-EXT-MIB
− XMC-DIAGNOSTIC-MIB
The SNMP functionality implemented in the XMC20 provides easy activation with any of the
three SNMP versions v1, v2c, or v3. In the current release, trap and inform functions are avail-
able for the above MIBs.

5.5 UNEM
The UNEM provides administration and simultaneous supervision and performance control for
all network elements (XMC20 and UMUX) of medium to large access networks. Depending on
the type of workstation, the UNEM can manage up to several thousand NEs.
The key to the deployment of UNEM is its architecture, which is designed with distributed man-
agement in mind and is based on a modern hardware platform.
The UNEM architecture consists of the following components:
• NEM desktop,
• NEM configurator,
• NEM network browser,
• Core, including database,
• North-bound interfaces,
• South-bound interfaces (agents).
The south-bound interfaces (agents) can be divided into
• Hitachi Energy proprietary agents,

Copyright 2022 Hitachi Energy. All rights reserved. 147

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

• SNMP agents.

OSS
Operat ion Support
Syst em

NEM Nort hbound

NEM
Network Int erf aces
Configurator
Browser (SNMP, CLI)

NEM
Desktop

Dat abase Proprietary

ary SNMP
Propriet
Propriet ary SNMP
SNMP
Agent
Agent Agent
Agent
NEM Core Agent Agent

XMC20 /
UMUX / third party
network

Figure 100: UNEM architecture

An optimized multi-process implementation for the different UNEM functions creates a high sys-
tem performance.
UNEM provides the user with two main interfaces:
• NEM configurator: This browser style interface allows setting up all the details of the man-
agement network and defining the security aspects. In addition, it provides access to the NE
configuration management and limited access to the fault management.
• NEM network browser: The network browser provides the operator with a graphical view of
the network in the form of maps for the supervision and the carrying out of the day-to-day
management of the NEs, including full fault management.
The UNEM accesses the NE via an Ethernet network, with a connection to an Ethernet interface
on the core unit or on an Ethernet service unit.
The XMC20 management communication is based on TCP/IP.
The main functions of the UNEM are as follows:
• Fault and performance management
To ensure that the operator can quickly locate and analyze problems in the network and can
take actions to prevent traffic disruptions, UNEM offers the following functions:
− Fault management,
− Status monitoring and diagnostics,
− Performance management, including an automatic performance data collection tool.
• Configuration management
With the configuration management of UNEM, the operator is able to define and configure
units in the network elements. Since the configuration of the XMC20 in UNEM is based on
ECST, the configuration is also performed on line, i.e. the XMC20 units are configured while
they are physically available in the subrack. A network element configuration can be stored
as a backup on the UNEM, and restored to the network element if required.
The configuration and deployment of encrypted MPLS tunnels is done via the DIRAC server.

Copyright 2022 Hitachi Energy. All rights reserved. 148

XMC20 | SYSTEM DESCRIPTION NETWORK MANAGEMENT SYSTEM

• Security management
The UNEM security administration ensures that only authorized users have access to infor-
mation they are responsible for.
Apart from restricting potentially damaging functions to selected operators, UNEM provides
warning messages before they are executed.
• Inventory management
Inventory data is collected periodically from all NEs and stored in the UNEM database.
It is possible to export the inventory data in XML format for integration into an OSS (opera-
tion support system) or BSS (billing support system).
• System management
The system management of UNEM provides the operator with the following functions:
− Activity history,
− NE discovery,
− NE alarm synchronization,
− NE inventory synchronization,
− NE performance data collection,
− System alarms.
The UNEM offers the following northbound interfaces (NBI) for OSS integration:
• SNMP for fault management and basic inventory data,
• CLI for inventory data reports.
The UNEM and UNEM client can be deployed on workstations running a Linux operating sys-
tem. The supported operating system releases are listed in [1KHW028868] Release Note
“XMC20 System Release R16A”.
The UNEM client runs also on PCs / Laptops running the Windows operating systems as listed
in [1KHW028868] Release Note “XMC20 System Release R16A”.

5.6 DIRAC
The DIRAC server is a centralized key management system and is responsible for the genera-
tion and distribution of the Master Keys used by the SECU1 Crypto Engines. The random num-
bers required for the Master Keys are generated by a Quantis USB device, attached to the
DIRAC server.
The DIRAC server has a command line interface (CLI) through which it is managed. In addition
there is a secure interface between the network management system UNEM and the DIRAC
server in order to synchronize paired information (Crypto Engine identifiers, encrypted MPLS
tunnels and tunnel endpoints, DIRAC server alarm status) between both systems.
The communication between the DIRAC server and UNEM is done via a REST interface, based
on HTTPS.
The DIRAC server also forwards the MPLS tunnels and tunnel endpoints configuration informa-
tion from the UNEM to all SECU1 Crypto Engines in the DIRAC system via secured channels
over insecure Ethernet or MPLS-TP links. The DIRAC server maintains a database with all
SECU1 Crypto Engines in the XMC20 network, and with all deployed MPLS tunnels.
The DIRAC server is deployed on workstations running a Linux operating system. The sup-
ported operating system releases are listed in [1KHW028868] Release Note “XMC20 System
Release R16A”.

Copyright 2022 Hitachi Energy. All rights reserved. 149

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6 Specifications

6.1 Traffic Functions

6.1.1 Customer VLAN Bridge Functionality

XMC25 R2 or XMC25 or XMC23 or XMC22

Implementation
- Core Units CENT2,
COGE7, COGE7-F,
COGE5, COGE5-F
- WAN port expansion units EXPU1
- Service Units ETO12, ETO12-F,
ETE24,
SUP12,
SUSE2, SUSE2-F
NUSA1, NUSA1-F
NUSA2
Customer bridge functionality Switching (Ethernet traffic) according to IEEE
802.1Q
Subscriber Ethernet Services
- Compliance MEF 3.0 CE (Carrier Ethernet)
- Service types E-Line Release 1
E-LAN Release 1
E-Tree Release 1
- Referenced standards MEF 6.2:
EVC Ethernet Services Definitions Phase 3
MEF 10.3:
Ethernet Services Attributes Phase 3
MEF 45:
Multi-CEN L2CP
MEF 45.0.1:
OVC Services Requirements for L2CP
Number of bridging instances 1
Physical ports
- Number of physical ports 245
- Interface types 10/100/1000BASE-T
100BASE-xx (SFP) 1
1000BASE-xx (SFP) 1
10GBASE-xx (SFP+) 1
SHDSL EFM
VLAN
- VLAN support according to IEEE 802.1Q (port and tag based)
- Number of VLANs supported 4089
- VLAN EtherType 0x8100 (single tagged frames)
0x8100 (Q-in-Q frames)
Ethernet switching
- Subrack switching capacity, bidirectional Combined capacity of up to 258 Gbit/s,
depending on the subrack type and utilized units.
Wire speed traffic forwarding @ 84 bytes/frame

Copyright 2022 Hitachi Energy. All rights reserved. 150

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- MAC table wire speed MAC address learning
CAM table size
- 16’000 addresses per service or core unit
- 64’000 addresses per XMC20 network element
- Maximum frame size supported 2 9’216 octets 3
- Traffic prioritization CoS handling, according to IEEE 802.1Q:
8 queues on egress ports,
8 queues on backplane ports,
each queue with selectable scheduling:
- strict priority scheduling or
- weighted round robin (WRR) scheduling, with
assignable weight per queue.
DSCP aware queuing
- Traffic classification based on:
- Port (port default priority)
- Ethernet priority bits
- IP DSCP field
- Link Layer Discovery Protocol (LLDP) Supported on core units and chassis switch service
units ports, as well as on stand-alone bridging units
SABE1, SABO1 (including backplane port).
LLDP disabled by default; can be enabled on all
Ethernet ports of port types ‘None’, ‘CVP’ and
‘MPLS-TP’. ‘PWAC’ ports will tunnel the protocol.
Destination multicast address of transmitted LLDP
PDUs can be configured per port. Values:
- “Nearest Bridge”: 01-80-C2-00-00-0E (default).
LLDP PDUs are not tunneled by any bridge type.
- “Nearest non-TPMR Bridge”: 01-80-C2-00-00-03.
Supported by Customer and Service Provider
Bridges. LLDP PDUs are tunneled by TPMR
Bridges.
- “Nearest Customer Bridge”: 01-80-C2-00-00-00.
Only supported by Customer Bridges. LLDP PDUs
are tunneled by Service Provider Bridges and
TPMR Bridges.
- In ECST, LLDP is managed within the Switching
main tab, under “Protocols”.
- No LLDP support in UNEM.
- Access Control Lists (ACL) ACLs are supported on UNI ports:
- CVP ports,
- PWAC ports.
ACLs are supported on
- Chassis switch UNI ports on service units: ETE24,
ETO12, ETO12-F, SUP12, SUSE2, SUSE2-F,
NUSA1, NUSA1-F, NUSA2 (Ethernet and EoS
ports 1-12).
ACLs are not supported on
- MPLS-TP ports,
- MPLS-TP PWs,
- NUSAx EPL ports,
- VRX10, VRX10-F ports.
For each UNI interface the user can choose to apply
ACLs at either:
- Ethernet (L2),
- IPv4/ARP (L3/L4).

Copyright 2022 Hitachi Energy. All rights reserved. 151

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- TDM encapsulation Encapsulation of TDM bit streams as Pseudo Wires
over packet switching networks (PSN):
- SAToP (structure agnostic)
- CESoPSN (structure aware)
- CESoETH (structure agnostic)
- CESoETH (structure aware)
Security features Ingress storm control
Ingress rate limiter per port
Ingress rate limiter per VLAN
Ingress rate limiter per MPLS-TP tunnel
HW and SW firewall
- Maximum number of VLAN rate limiters (including 250 per service or core unit
the number of CVP and PWAC ports) 2500 per network element
- Maximum number of MPLS-TP tunnel rate limiters 500 (with COGE5 and COGE7)
2000 (with CENT2)
Spanning tree
- Number of interfaces (ports) with STP/RSTP active 64
Ethernet protection
- Number of interfaces (ports) with ERPS active 12
- Number of ERPS instances 12
- Number of ERPS protected VLAN groups 64
Authentication
- Maximum number of ports with 802.1X authentica- 256 4
tion enabled

1. For the recommended SFP+ and SFP module types please contact your local Hitachi Energy represen-
tative or refer to the Hitachi Energy Extranet.
2. Please note that depending of the used Ethernet equipment or service unit the effectively usable maxi-
mum frame size can be smaller than the specified value.
3. Excessive jumbo frame traffic leads to high buffer resource usage and may lead to frame loss on other
ports.
4. 802.1X will be available in a future release.

6.1.2 MPLS-TP Functionality

XMC25 R2 or XMC25 or XMC23 or XMC22

MPLS-TP functionality IETF RFC 5921 (07/2010)
A Framework for MPLS in Transport Networks
Implementation
- Core Units CENT2,
COGE7, COGE7-F,
COGE5, COGE5-F
- WAN port expansion units EXPU1
- Service Units ETO12, ETO12-F,
ETE24,
SUP12,
SUSE2, SUSE2-F
NUSA1, NUSA1-F
NUSA2
- Attachment Circuits On core and service units
- MPLS-TP ports On core units and WAN port expansion units:
- Physical ports
- VLAN based logical ports

Copyright 2022 Hitachi Energy. All rights reserved. 152

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

Network element deployment Label Edge Router (LER)
Label Switching Router (LSR)
MPLS-TP services Virtual Private Wire Service (VPWS)
Virtual Private LAN Service (VPLS)
Capacity
- Maximum number of MPLS-TP ports 5 physical ports per core unit
4 physical ports per WAN port expansion unit
50 logical ports per network element (VLAN based),
shared with the physical ports
- Maximum number of bidirectional LSPs in LER 500 (with COGE7 or COGE5)
(unprotected, 1 PW per LSP) 2000 (with CENT2)
- Maximum number of bidirectional LSPs in LSR 300 (per non-redundant COGE7 or COGE5)
600 (with redundancy of COGE7 or COGE5, in and
out on different COGE7 or COGE5)
3500 (with CENT2)
- Maximum number of bidirectional LSP End-Points 600 per COGE7 or COGE5 unit
in LSR 3500 per CENT2 unit
- Maximum number of terminated Tunnels in LER 250 (with COGE7 or COGE5)
2000 (with CENT2)
- Maximum number of bidirectional PW (shared 330 (with COGE7 or COGE5)
between VPWS and VPLS) 2000 (with CENT2)
- Maximum number of VPLS instances 50 (with COGE7 or COGE5)
100 (with CENT2)
- Maximum number of mesh & spoke PWs in a 30 (with COGE7 or COGE5)
VPLS instance 50 (with CENT2)
- Maximum number of member ports (CVP) per SVI 30 (with COGE7 or COGE5)
VLAN 50 (with CENT2)
- Maximum number of member ports (CVP) of all 500 (with COGE7 or COGE5)
SVI VLANs 1000 (with CENT2)
- Maximum number of Linear Protection Switching 250
(LPS) groups
OAM Continuity Check (CC)
Remote Defect Indication (RDI)
LSP Ping
LSP Trace Route
Delay Measurement (DM)
Protection switching 1:1
- Protection operation type revertive
non-revertive
- Protection switching type bidirectional
- Number of protected tunnels up to 250 (with COGE7 or COGE5)
up to 1000 (with CENT2)
- Number of protected tunnels with switching time < up to 50 (with COGE7 or COGE5)
50 ms up to 250 (with CENT2)
- Number of protected tunnels with switching time < up to 200 (with COGE7 or COGE5)
500 ms up to 750 (with CENT2)

6.1.3 Encryption Functionality

XMC25 R2 or XMC25 or XMC23 or XMC22

Implementation
- Encryption Units SECU1-4, SECU1F4, SECU1-8, SECU1F8

Copyright 2022 Hitachi Energy. All rights reserved. 153

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- Unencrypted ports Connected to an MPLS-TP port of the core unit or
the WAN port expansion unit
Connected to an MPLS-TP subinterface (VLAN
based) of the core unit or the WAN port expansion
unit
- Encrypted ports Connected to the WAN
Capacity
- Number of functional units 1 per encryption unit (SECU1-4, SECU1F4)
2 per encryption unit (SECU1-8, SECU1F8)
- Number of encryption engines 2 per functional unit
- Number of unencrypted ports 2 per functional unit
- Number of encrypted ports 2 per functional unit
- Number of random number generators 1 per encryption unit
- Traffic flows 1024 independent encrypted traffic flows (LSPs) per
encryption engine and direction
Support of 1024 encryption end points in a network
Asymmetrical encryption process Master key encryption
- Algorithm ECC (Elliptic Curve Cryptography), ECDH (Elliptic
Curve Diffie-Hellman)
- Key length 521 bit
(NIST P-521 defined in FIPS 186-4)
- Key replacement via DIRAC server
Symmetrical encryption process Session key and data encryption
- Algorithm AES-GCM (Galois/Counter Mode) for encryption
and authentication
- Key length 256 bit
- Key replacement 60 seconds or longer
(automatic)
Authentication X.509 certificate based
Per traffic flow
Master key generation Setting via CLI
Setting via key management server (DIRAC), key
change without traffic interruption
Session key generation and distribution Based on the local random number generator
Key is generated for the transmit direction
Key configurable for every traffic flow (MPLS tunnel)
Key change without traffic interruption
Random number generator HW based True Random Number Generator
(TRNG)
Traffic encryption MPLS interface based:
- MPLS port
- MPLS-TP subinterface (VLAN based)
MPLS packets with an inner MPLS label of 13 and a
TTL value of ≤ 127 are not encrypted
Authentication overhead Additional tag with up to 16 bytes after the encrypted
payload of all payload packets
Traffic delay Latency between bridged ports < 4 µs (10 Gbit/s)
Latency between bridged ports < 30 µs (1 Gbit/s)
Delay compensation for PTP packets
Delay variation for PTP packets < 50 ns

Copyright 2022 Hitachi Energy. All rights reserved. 154

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

Traffic jitter and wander Clock regenerator with through-timing capability
Jitter requirements for 1000Base-X and 10GBase-R
according to IEEE 802.3
Tamper protection Prevents mechanical manipulation
Tamper detection by heat sink (mechanical housing)
Tamper proof private key storage

6.1.4 TDM Cross Connect

XMC25 R2 or XMC25 or XMC23 or XMC22

Maximum number of TDM connections 4096
Maximum number of connection termination points 4096
(CTP)
Unit placement for TDM services A TDM unit can be placed in any slot of the XMC20
subrack except slot 11 which is reserved for the core
unit
Cross connection layers P0_nc (n x 64 kbit/s) synchronous
P12 (2048 kbit/s) plesiochronous
VC-12
VC-3
VC-4
Protection switching times Specification corresponding to the transfer time Tt
definition in ITU-T G.808.1
- P0_nc LTP (based on CAS AIS) ≤ 320 ms
- P0_nc SNCP/I ≤ 50 ms
- P12 SNCP/I
- P12 SNCP/N
- VC-12 SNCP/I ≤ 50 ms
- VC-12 SNCP/N
- VC-3 SNCP/I
- VC-3 SNCP/N
- VC-4 SNCP/I
- VC-4 SNCP/N
- STM-1 MSP unidirectional ≤ 50 ms
- STM-1 MSP bidirectional
- STM-4 MSP unidirectional
- STM-4 MSP bidirectional
- STM-16 MSP unidirectional
- STM-16 MSP bidirectional
Synchronous multiplexing and connections of ITU-T G.736 (03/1993)
P12 and P0_nc traffic signals Characteristics of a synchronous digital multiplex
equipment operating at 2048 kbit/s

ITU-T G.704 (10/1998)

Synchronous frame structures used at 1544, 6312,
2048, 8448 and 44 736 kbit/s hierarchical levels

ITU-T G.706 (04/1991)

Frame alignment and cyclic redundancy check
(CRC) procedures relating to basic frame structures
defined in Recommendation G.704

ITU-T G.823 (03/2000)

The control of jitter and wander within digital net-
works which are based on the 2048 kbit/s hierarchy

Copyright 2022 Hitachi Energy. All rights reserved. 155

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

Primary PCM multiplexing ITU-T G.732 (11/1988)
Characteristics of primary PCM multiplex equipment
operating at 2048 kbit/s
Plesiochronous connections of ITU-T G703 (11/2001)
P12 traffic signals Physical/electrical characteristics of hierarchical dig-
ital interfaces

ITU-T G.823 (03/2000)

The control of jitter and wander within digital net-
works which are based on the 2048 kbit/s hierarchy
Connections of VC-12, VC-3 and VC-4 traffic signals ITU-T G.785 (11/1996)
Characteristics of a flexible multiplexer in a synchro-
nous digital hierarchy environment

ITU-T G.783 (03/2006)

Characteristics of synchronous digital hierarchy
(SDH) equipment functional blocks
Protected connections ITU-T G.808.1 (03/2006)
Generic protection switching - Linear trail and sub-
network protection
Network element synchronization ITU-T G.823 (03/2000)
The control of jitter and wander within digital net-
works which are based on the 2048 kbit/s hierarchy
ITU-T G.8262/Y.1362 (07/2010)
Timing characteristics of a synchronous Ethernet
equipment slave clock (option 1)
ITU-T G.8264/Y.1364 (10/2008)
Distribution of timing information through packet net-
works
ITU-T G.8275.2/Y.1369.2 (06/2016)
Precision time protocol telecom profile for phase/
time synchronization with partial timing support from
the network

IEEE Std 1588-2019 (11/2019)

IEEE Standard for a Precision Clock Synchroniza-
tion Protocol for Networked Measurement and Con-
trol Systems
SDH network interface synchronization ITU-T G.813 (03/2003)
Timing characteristics of SDH equipment slave
clocks (SEC)
TDM service synchronization in CES applications ITU-T G.8261/Y.1361 (05/2006)
Timing and synchronization aspects in packet net-
works

6.1.5 TDM Timing Source

XMC25 R2 or XMC25 or XMC23 or XMC22

PETS Plesiochronous Equipment Timing Source
ITU-T G.8262/Y.1362 (07/2010)
Timing characteristics of a synchronous Ethernet
equipment slave clock (option 1)
- Implementation Core unit
- Frequency tolerance ± 9.2 ppm
- Free running frequency accuracy ± 4.6 ppm
- Jitter transfer minimum bandwidth 1 Hz

Copyright 2022 Hitachi Energy. All rights reserved. 156

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- Jitter transfer maximum bandwidth 10 Hz
- Jitter transfer maximum gain 0.2 dB
- Timing sources 4 PDH or Ethernet traffic sources
4 PTP traffic sources
2 synchronization inputs
1 internal oscillator
- Timing selection Priority based
Quality level based

SETS Synchronous Equipment Timing Source

ITU-T G.8262/Y.1362 (07/2010)
Timing characteristics of a synchronous Ethernet
equipment slave clock (option 1)
- Implementation Service unit STM14
Service unit NUSA1, NUSA1-F
Service unit NUSA2
- Frequency tolerance ± 4.6 ppm
- Jitter transfer maximum bandwidth 10 Hz
- Jitter transfer maximum gain 0.2 dB
- Timing sources 4 SDH traffic sources (STM14)
8 SDH traffic sources (NUSA2, NUSA1, NUSA1-F
with EQP)
4 PDH or Ethernet traffic sources
1 synchronization input
1 internal oscillator
- Timing selection Priority based
Quality level based
PTP, Precision Time Protocol ITU-T G.8275.2/Y.1369.2 (06/2016)
Precision time protocol telecom profile for phase/
time synchronization with partial timing support from
the network

IEEE Std 1588-2019 (11/2019)

IEEE Standard for a Precision Clock Synchroniza-
tion Protocol for Networked Measurement and Con-
trol Systems
PTP implementation on the core unit - Port based
- Ethernet VLAN based (layer 2)
- UDP/IPv4 VLAN based (layer 3)
- Clock types Ordinary Clock, slave ports
Boundary Clock, slave and master ports
Transparent Clock
- PTP messages rates per second for slave streams Announce: 1/2, 1, 2, 4, 8
Sync: 2, 4, 8, 16, 32, 64
Delay: 2, 4, 8, 16, 32
- PTP messages rates per second for IP VLAN mas- Announce: 1/4, 1/2, 1, 2
ter streams Sync: 1/4, 1/2, 1, 2, 4, 8, 16, 32
Delay: 1/4, 1/2, 1, 2, 4, 8, 16, 32
- PTP ports on CENT2 4 optical 1GbE or 10GbE ports
1 electrical 1GbE port
- PTP ports on COGE5 2 optical 10GbE ports
2 of 3 electrical 1GbE ports
- PTP VLANs (Ethernet or IP based) up to 10, shared with the number of PTP ports con-
figured to “Ordinary/Boundary Clock”
- PTP master mode, IP VLAN based 3 (CENT2 only)

Copyright 2022 Hitachi Energy. All rights reserved. 157

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- PTP slaves per PTP master, IP VLAN based 20
- PTP clock sources 4
- Timing selection Priority based
Quality level based (tree networks only)

6.1.6 TDM Encapsulation

XMC25 R2 or XMC25 or XMC23 or XMC22

Implementation
- Circuit emulation unit SATP8
- TDM encapsulation Encapsulation of TDM bit streams as Pseudo Wires
over packet switching networks (PSN):
SATP8:
- SAToP (structure agnostic), RFC 4553
- CESoPSN (structure aware), RFC 5086
- CESoETH (structure agnostic), MEF 8
- CESoETH (structure aware), MEF 8
TDM bit rates 2048 kbit/s
N x 64 kbit/s in structured 2 Mbit/s (P12)
Pseudo Wire transport capacity SATP8:
- 8 x 2048 kbit/s, bidirectional; structured or unstruc-
tured
Pseudo Wire synchronization ITU-T G.8261, adaptive and synchronous

6.1.7 NGN Voice Functionality

XMC25 R2 or XMC25 or XMC23 or XMC22

Implementation
- Media gateway unit VOIP1
Media gateway control protocol SIP according to IETF RFC 3261
Voice algorithm ITU-T G.711 PCM-64 kbit/s
Fax Voice Band Data or T.38
Modem Voice Band Data
DTMF Inband or RFC 2833
Echo cancellation ITU-T G.168,
up to 128 ms tail length
G.711 codec PCM A-law companding
Support of silence suppression according to G.711,
Appendix II
G.729A codec Support of silence suppression according to G.729B

PSTN user port access capacity 1216 FXS or FXO

ISDN-BA user port access capacity 304
Maximum number of simultaneous voice channels 200
with the G.711 codec
Maximum number of simultaneous voice channels 80
with the G.729A codec (+120 G.711 voice channels)
Traffic handling capacity 9’750 BHCA at CCR < 99.99%

Copyright 2022 Hitachi Energy. All rights reserved. 158

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

SIP requests:
INVITE, ACK, BYE, CANCEL, RFC 3261
NOTIFY, REGISTER
UPDATE RFC 3311
INFO RFC 2976
REFER RFC 3515
PRACK RFC 3262
SIP responses:
1xx, 2xx, 3xx, 4xx, 5xx, 6xx supported
SIP compliances:
SIP basic call flow RFC 3665
An offer / answer model with SDP RFC 3264
Reliability of provisional responses in RFC 3262
SIP
Privacy mechanism for SIP RFC 3323
Private extensions to SIP for asserted RFC 3325
identity within trusted networks

6.2 Interfaces

6.2.1 Traffic Interfaces

6.2.1.1 Network Interfaces

XMC25 R2 or XMC25 or XMC23 or XMC22

Ethernet interfaces
- Implementation Core unit CENT2
- 1 x RJ45 electrical 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
- 4 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
10GBASE-xx acc. to SFF-8431 1
Ethernet interfaces
- Implementation Core unit COGE7, COGE7-F
- 1 x RJ45 electrical 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
- 2 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
- 2 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
10GBASE-xx acc. to SFF-8431 1
Ethernet interfaces
- Implementation Core unit COGE5, COGE5-F
- 3 x RJ45 electrical 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over

Copyright 2022 Hitachi Energy. All rights reserved. 159

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- 2 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
10GBASE-xx acc. to SFF-8431 1
Ethernet interfaces
- Implementation WAN port expansion unit EXPU1
- 4 x SFP+ cage 10GBASE-xx acc. to SFF-8431 1
- 1 x QSFP+ cage 40GBASE-xxx acc. to SFF-8436 1
Ethernet interfaces
- Implementation Encryption unit SECU1-4, SECU1F4
- 4 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
10GBASE-xx acc. to SFF-8431 1
Ethernet interfaces
- Implementation Encryption unit SECU1-8, SECU1F8
- 8 x SFP+ cage 1000BASE-xx acc. to INF-8074i 1
(with SFP DDM support)
10GBASE-xx acc. to SFF-8431 1
SHDSL EFM interfaces
- Implementation SHDSL transport unit SUSE2, SUSE2-F
- 24 x SHDSL ports (EFM) According to ITU-T, G.991.2, Annex A, B, F and G
Pair bonding (up to 4 lines)
Connector frame: DIN 41612
SDH interfaces
- Implementation SDH transport unit NUSA1, NUSA1-F, NUSA2
- 2 x SFP cage STM-16 (optical) (NUSA1, NUSA1-F, NUSA2 only)
- S-16.1, S-16.2, L-16.1, L-16.2, X-16.2, CWDM,
Bidi,
or STM-4 (optical)
- S-4.1, S-4.2, L-4.1, L-4.2, X-4.2, CWDM, Bidi,
acc. to INF-8074i
- 2 x SFP cage STM-4 (optical)
- S-4.1, S-4.2, L-4.1, L-4.2, X-4.2, CWDM, Bidi,
or STM-1 (optical or electrical)
- S-1.1, L-1.1, L-1.2, X-1.2, CWDM, Bidi, G.703,
acc. to INF-8074i
SDH interfaces
- Implementation SDH transport unit STM14
- 2 x SFP cage STM-4 (optical)
- S-4.1, S-4.2, L-4.1, L-4.2, X-4.2, CWDM, Bidi,
or STM-1 (optical or electrical)
- S-1.1, L-1.1, L-1.2, X-1.2, CWDM, Bidi, G.703,
acc. to INF-8074i
- 2 x SFP cage STM-1 (optical or electrical)
- S-1.1, L-1.1, L-1.2, X-1.2, CWDM, Bidi, G.703,
acc. to INF-8074i
PDH interfaces
- Implementation PDH transport unit SELI8
- 8 x E1 ports According to ITU-T G.703, G.704
120 Ω symmetrical or 75 Ω asymmetrical
Connector frame: DIN 41612
PDH interfaces
- Implementation PDH transport unit SATP8
- 8 x E1 ports According to ITU-T G.703, G.704
120 Ω symmetrical or 75 Ω asymmetrical
Connector frame: DIN 41612

Copyright 2022 Hitachi Energy. All rights reserved. 160

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

PDH interfaces
- Implementation PDH transport unit SDSL8
- 8 x SHDSL ports (TDM) According to ITU-T, G.991.2, Annex B
Pair bonding (4 wire mode)
n x 64 kbit/s duplex over 1 or 2 pairs
Remote power supply for DTM CPE or DTU CPE
desktop
Connector frame: DIN 41612

1. For the recommended QSFP+, SFP+ and SFP module types please contact your local Hitachi Energy
representative or refer to the Hitachi Energy Extranet.

6.2.1.2 Subscriber Interfaces

XMC25 R2 or XMC25 or XMC23 or XMC22

Ethernet interfaces
- Implementation Service unit ETO12, ETO12-F
- 12 x SFP cage 12 x 100BASE-X/1000BASE-X/T
EFM acc. to IEEE 802.3ah
Ethernet interfaces
- Implementation Service unit ETE24
- 24 x RJ45 electrical 24 x 10/100/1000BASE-T
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
EFM acc. to IEEE 802.3ah
Ethernet interfaces
- Implementation Service unit SUP12
- 12 x RJ45 electrical 12 x 10/100/1000BASE-T
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
EFM acc. to IEEE 802.3ah
Power over Ethernet PoE and PoE+
Ethernet interfaces
- Implementation Service unit VRX10, VRX10-F
- 12 x SFP cage 12 x 100BASE-X/1000BASE-X/T
- Routing Static routing
OSPF dynamic routing, RFC2328
Ethernet interfaces
- Implementation Service unit SABE1
- 12 x RJ45 electrical 12 x 10/100/1000BASE-T
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
EFM acc. to IEEE 802.3ah
Power over Ethernet PoE and PoE+
Ethernet interfaces
- Implementation Service unit SABO1, SABO1-F
- 12 x SFP cage 12 x 100BASE-X/1000BASE-X/T
EFM acc. to IEEE 802.3ah
Ethernet interfaces
- Implementation Service unit ETAG1
- 4 x RJ45 electrical 4 x 10/100BASE-T
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
Ethernet over PDH (EoP) 16 x 2 Mbit/s via any P12
transport unit

Copyright 2022 Hitachi Energy. All rights reserved. 161

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- Switching PPP, RFC1661
Multilink PPP, RFC1990
MAC/PPP, RFC1638
IP/PPP, RFC1332
MAC/HDLC encapsulation
- Routing Static routing
OSPF dynamic routing, RFC2328
RIPv2 dynamic routing, RFC2453
VRRP, RFC3768
Ethernet interfaces
- Implementation Service unit STM14, NUSA1, NUSA1-F, NUSA2
- 4 x RJ45 electrical 4 x 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
EoS via local SDH ports
Ethernet interfaces
- Implementation Service unit TUDA1
- 1 x RJ45 electrical 4 x 10/100BASE-T
auto-negotiation (half / full-duplex mode)
automatic MDI/MDIx switch-over
SHDSL EFM interfaces
- Implementation SHDSL transport unit SUSE2, SUSE2-F
- 24 x SHDSL ports (EFM) According to ITU-T, G.991.2, Annex A, B, F and G
Pair bonding (up to 4 lines)
Connector frame: DIN 41612
SHDSL Interfaces
- Implementation Service unit SDSL8
- 8 x SHDSL ports (TDM) According to ITU-T, G.991.2, Annex B
Pair bonding (4 wire mode)
n x 64 kbit/s duplex over 1 or 2 pairs
Remote power supply for DTM CPE or DTU CPE
desktop
Connector frame: DIN 41612
E1 Interfaces
- Implementation Service unit SELI8
- 8 x E1 ports According to ITU-T G.703, G.704
120 Ω symmetrical or 75 Ω asymmetrical
Connector frame: DIN 41612
E1 Interfaces
- Implementation Service unit SATP8
- 8 x E1 ports According to ITU-T G.703, G.704
120 Ω symmetrical or 75 Ω asymmetrical
Connector frame: DIN 41612
E0 Interfaces
- Implementation Service unit TUGE1 1
- 8 x E0 ports According to ITU-T G.703, codirectional
120 Ω symmetrical
Connector frame: DIN 41612
- 2 x E0 ports According to ITU-T G.703, contradirectional
120 Ω symmetrical
Connector frame: DIN 41612
Data Interfaces
- Implementation Service unit TUDA1

Copyright 2022 Hitachi Energy. All rights reserved. 162

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- 4 x data ports Interface type configurable:
V.24/V.28
V.35
X.24/V.11
RS485 2-wire
RS485 4-wire
Connector: 4 x Metral 4x6
- Line rate Subrate asynchronous 0.6 to 38.4 kbit/s
Subrate synchronous 0.6 to 56 kbit/s
Synchronous 1x64 to 32x64 kbit/s
Data Transmission
- Implementation DTM CPE or DTU CPE desktop connected to ser-
vice unit SDSL8
- 1 x E1 port According to ITU-T G.703, G.704
120 Ω symmetrical (RJ45) or
75 Ω asymmetrical (BNC)
- 1 x X.21/V.11 port DSub-15 connector
- 1 x V.35 port MF-34 connector
- 1 x V.36 port DSub-37 connector
PSTN FXS
- Implementation Service unit SUPM1
- 16 x PSTN ports According to ITU-T Q.552 (General transmission
characteristics).
The voice impedance is configurable in the element
manager.
Connector frame: DIN 41612
PSTN FXS
- Implementation Service unit SUPM2
- 64 x PSTN ports According to ITU-T Q.552 (General transmission
characteristics).
The voice impedance is configurable in the element
manager.
Connector frame: 2 x DIN 41612
E&M voice and signaling
- Implementation Service unit TUEM1
- 8 x voice ports 2-wire or 4-wire.
600 Ω voice impedance.
Connector frame: DIN 41612
- 16 x signaling ports 2 E&M signaling ports per voice port.
Connector frame: DIN 41612
Magneto line voice and signaling
- Implementation Service unit IMAG1
- 8 x magneto line voice ports 2-wire.
600 Ω voice impedance.
Connector frame: DIN 41612
- 8 x E&M voice ports Connected to the TUEM1 unit.
- 8 x E&M signaling ports Connected to the TUEM1 unit.
PSTN FXO
- Implementation Service unit TUXA1
- 12 x PSTN ports According to ITU-T Q.552 (General transmission
characteristics).
The voice impedance is configurable in the element
manager.
Connector frame: DIN 41612

Copyright 2022 Hitachi Energy. All rights reserved. 163

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

ISDN-BA with 2B1Q line code
- Implementation Service unit ISDN4
- 4 x ISDN-BA ports According to ETSI TS 102 080 Annex A.
Connector frame: DIN 41612
PSTN high voltage common mode filter box
- Implementation Service unit FIL16
- 16 PSTN ports Connected to SUPM1 or SUPM2 FXS unit.
Connector frame: DIN 41612
- 16 PSTN ports Connected to the line.
Connector frame: DIN 41612
- Mounting Directly into the 19-inch rack

1. The codirectional or contradirectional interfaces can only be used alternatively.

6.2.2 Management Interfaces

XMC25 R2 or XMC25 or XMC23 or XMC22

Ethernet interfaces
- Implementation Core unit CENT2, COGE7, COGE7-F, COGE5,
COGE5-F
Ethernet service units
- 1 x RJ45 electrical local management port 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x
(CENT2), or
10/100BASE-TX acc. to IEEE 802.3 (COGE7,
COGE7-F, COGE5, COGE5-F)
auto-negotiation (half / full-duplex mode),
automatic MDI/MDIx switch-over,
TCP/IP based,
not routed
- Any RJ45 based Ethernet port of the XMC20 10/100/1000BASE-T acc. to IEEE 802.3 / 802.3x,
Switch auto-negotiation (half / full-duplex mode),
automatic MDI/MDIx switch-over,
TCP/IP based,
VLAN tagged or untagged,
routed
- Any SFP/SFP+/QSFP+ based Ethernet port of the 1000BASE-xx acc. to INF-8074i 1,
XMC20 Switch 10GBASE-xx acc. to SFF-8431 1,
40GBASE-xxx acc. to SFF-8436 1,
TCP/IP based,
VLAN tagged or untagged,
routed
MPLS interfaces
- Implementation Core unit CENT2, COGE7, COGE7-F, COGE5,
COGE5-F
WAN port expansion unit EXPU1
Any MPLS-TP port on a core unit or WAN port
expansion unit,
routed,
- section based
- LSP based
TDM interfaces
- Implementation TDM service units
Any P12 or P0_nc channel on a PDH or SDH ser-
vice unit,
routed

Copyright 2022 Hitachi Energy. All rights reserved. 164

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

Ethernet interfaces
- Implementation Encryption unit SECU1-4, SECU1F4, SECU1-8,
SECU1F8,
local management access
- 1 x RJ45 electrical local management port 10/100/1000BASE-T acc. to IEEE 802.3,
auto-negotiation (half / full-duplex mode),
automatic MDI/MDIx switch-over,
TCP/IP based

1. For the recommended QSFP+, SFP+ and SFP module types please contact your local Hitachi Energy
representative or refer to the Hitachi Energy Extranet.

6.2.3 Synchronization Interfaces

XMC25 R2 or XMC25 or XMC23 or XMC22

2 MHz Synchronization Input / Output According to ITU-T, G.703
- Number of inputs 2
- Input jitter tolerance ITU-T G.813, Figure 9
- Input wander tolerance ITU-T G.813, Table 10
- Number of outputs 1 related to the PETS clock domain
1 related to the SETS clock domain(s)
- Maximum output jitter, PETS clock domain ITU-T G.823, Table 5, SEC requirements
- Maximum output jitter, SETS clock domain ITU-T G.813
- Implementation Core unit CENT2, COGE7, COGE7-F, COGE5,
COGE5-F
- Synchronization system PETS (1 input, 1 output) 1
SETS (1 input, 1 output)
- Frequency 2048 kHz
± 4.6 ppm for PETS
± 4.6 ppm for SETS
- Impedance 120 Ω or high impedance, symmetrical
PPS Output
- Time code format PPS
1 pulse per second, rising edge aligned with the sec-
ond boundary, pulse width 1 ms.
- Implementation CENT2
1 electrical
- Standard ITU-T V.11 (RS-422)
- Impedance 120 Ω (active), high impedance (inactive)

1. On the COGE5 both synchronization inputs can be used for the PETS domain.

6.2.4 Alarm Interfaces

XMC25 R2 or XMC25
For the specification of the alarm interfaces on COOL4 or ALMU4-F, please refer to section 6.4.4 COOL4
Fan Unit (R2) (on page 177) or section 6.4.5 ALMU4-F Alarm Unit (R1) (on page 179).

Copyright 2022 Hitachi Energy. All rights reserved. 165

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC23
For the specification of the alarm interfaces on COOL6 or ALMU6-F, please refer to section 6.5.4 COOL6
Fan Unit (R2) (on page 187) or section 6.5.5 COOL6 Fan Unit (R3) (on page 189) or section 6.5.6
ALMU6-F Alarm Unit (R1) (on page 191).

XMC22
For the specification of the alarm interfaces on COOL8 or ALMU8-F, please refer to section 6.6.4 COOL8
Fan Unit (R1) (on page 198) or section 6.6.5 COOL8 Fan Unit (R2) (on page 200) or section 6.6.6
ALMU8-F Alarm Unit (R1) (on page 202).

6.2.5 Power Interfaces

XMC25 R2
DC power interface
Interface access XMC25 R2 subrack
Power supply interface according EN 300 132-2 V2.3.6, interface “A”
Nominal voltages
- -48 VDC, voltage range -40.0 VDC … -57 VDC with DUA25
-39.5 VDC … -57 VDC without DUA25
- -60 VDC, voltage range -50.5 VDC … -72 VDC
(-75 VDC for max. 5 minutes / month)
Maximum continuous current
- XMC25 R2, without DUA25 45 A
- XMC25 R2, with DUA25 30 A (active cooling), 25 A (passive cooling)
Recommended fusing
- XMC25 R2, without DUA25 50 A slow blow
- XMC25 R2, with DUA25 30 A slow blow
Connection points for power supply circuits
- XMC25 R2 Standard 2 on the cable tray
- XMC25 R2 Protected (1+1 with DUA25) 2 on DUA25, 1 connection to the subrack
Power supply interface for core and service units:
- nominal supply voltage:
-48 VDC or -60 VDC
- normal service voltage range: -39.5 VDC … -72 VDC
The equipment function is according to the specifi-
cation.
- abnormal service voltage range: 0 VDC to -39.5 VDC, and
The equipment function is not guaranteed, but -72 VDC to -75 VDC
equipment will not be damaged.

XMC25
DC power interface
Interface access XMC25 subrack
Power supply interface according EN 300 132-2 V2.3.6, interface “A”
Nominal voltages
- -48 VDC, voltage range -40.0 VDC … -57 VDC with DUA25
-39.5 VDC … -57 VDC without DUA25
- -60 VDC, voltage range -50.5 VDC … -72 VDC
(-75 VDC for max. 5 minutes / month)

Copyright 2022 Hitachi Energy. All rights reserved. 166

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25
Maximum continuous current
- XMC25 subrack revisions R2A, R2B and R3B, 45 A
without DUA25
- XMC25 subrack revision R3A, without DUA25 30 A
- XMC25, with DUA25
30 A (active cooling), 25 A (passive cooling)
Recommended fusing
- XMC25 subrack revisions R2A, R2B and R3B, 50 A slow blow
without DUA25
- XMC25 subrack revision R3A, without DUA25 30 A slow blow
- XMC25, with DUA25
30 A slow blow
Connection points for power supply circuits
- XMC25 subrack revisions R2A, R2B and R3B 2 on the cable tray
Standard 1 on the cable tray
- XMC25 subrack revision R3A Standard 2 on DUA25, 1 connection to the subrack
- XMC25 Protected (1+1 with DUA25)
Power supply interface for core and service units:
- nominal supply voltage:
-48 VDC or -60 VDC
- normal service voltage range: -39.5 VDC … -72 VDC
The equipment function is according to the specifi-
cation.
- abnormal service voltage range: 0 VDC to -39.5 VDC, and
The equipment function is not guaranteed, but -72 VDC to -75 VDC
equipment will not be damaged.

XMC23
DC power interface
- Interface access XMC23 subrack
- Power supply interface according EN 300 132-2 V2.3.6, interface “A”
Nominal voltages
- -48 VDC, voltage range -40.0 VDC … -57 VDC with DUA23
-39.5 VDC … -57 VDC without DUA23
- -60 VDC, voltage range -50.5 VDC … -72 VDC
(-75 VDC for max. 5 minutes / month)
Maximum continuous current 15 A
Recommended fusing 15 A slow blow
Connection points for power supply circuits 1 on the cable tray
2 with DUA23
Power supply interface for core and service units:
- nominal supply voltage:
-48 VDC or -60 VDC
- normal service voltage range: -39.5 VDC … -72 VDC
The equipment function is according to the specifi-
cation.
- abnormal service voltage range: 0 VDC to -39.5 VDC, and
The equipment function is not guaranteed, but -72 VDC to -75 VDC
equipment will not be damaged.

XMC22
DC power interface
- Interface access XMC22 subrack
- Power supply interface according EN 300 132-2 V2.3.6, interface “A”

Copyright 2022 Hitachi Energy. All rights reserved. 167

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC22
- Nominal DC voltages -48 VDC
-60 VDC
- Voltage range, -48 VDC -40.0 VDC … -57 VDC with DUA23
-39.5 VDC … -57 VDC without DUA23
- Voltage range, -60 VDC -50.5 VDC … -72 VDC
(-75 VDC for max. 5 minutes / month)
- Maximum continuous current 8A
- Recommended fusing 8 A slow blow
- Connection points for power supply circuits 1 on the 19-inch adapter
2 with DUA23
AC power interface
- Interface access POAC1 AC/DC converter
(part of the optional XMC22 AC power kit)
- POAC1 specification refer to section 6.6.8.2 Specification (on page 204)
- Backup battery, optional 48V, 10 Ah … 40 Ah
- Recommended fusing for the backup battery 10 A
Power supply interface for core and service units:
- nominal supply voltage:
-48 VDC or -60 VDC
- normal service voltage range: -39.5 VDC … -72 VDC
The equipment function is according to the specifi-
cation.
- abnormal service voltage range: 0 VDC to -39.5 VDC, and
The equipment function is not guaranteed, but -72 VDC to -75 VDC
equipment will not be damaged.

6.3 Performance Control and Management Functions

6.3.1 System Level

XMC25 R2 or XMC25 or XMC23 or XMC22

System level alarm system:
- Alarm indicators LEDs
relay contacts (XMC25 R2, XMC25 and XMC23
only)
- Lists NE fault list, logbook
- Logbooks dedicated logbooks for alarms, events, configura-
tion, equipment, and session management
- Inventory data for hardware and NE software system
- Software installation status for NE wide ESW installation and installation prog-
ress
TDM diagnostics TDM pattern generator and analyzer: 1
- Bit error counter
- Performance management data collection
- Round trip delay measurement
- Bit rates n x 64 kbit/s, n = 1 … 31
2048 kbit/s (transparent)

Copyright 2022 Hitachi Energy. All rights reserved. 168

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- Test pattern PRBS 223-1
PRBS 215-1
PRBS 26-1
PRBS 223-1 inverted
PRBS 215-1 inverted
PRBS 26-1 inverted
Fixed pattern (8 bit)
CAS

1. On a XMC20 network element with the CENT2 core unit this feature will be supported in a future release.

6.3.2 Traffic Functions

XMC25 R2 or XMC25 or XMC23 or XMC22

Status and Maintenance
- Core unit CENT2, COGE7, COGE7-F, COGE5, status of Ethernet interfaces is monitored
COGE5-F mirroring
Ethernet statistics
LSP Ping
LSP Trace Route
Status and Maintenance
- WAN port expansion unit EXPU1 status of Ethernet interfaces is monitored
mirroring
Ethernet statistics
LSP Ping
LSP Trace Route
- ETO12, ETO12-F, ETE24, SUP12 status of Ethernet interfaces is monitored
mirroring
Ethernet statistics
- SABE1, SABO1, SABO1-F status of Ethernet interfaces is monitored
Ethernet statistics
- SUSE2, SUSE2-F status of SHDSL interfaces is monitored
status of Ethernet interfaces is monitored
mirroring
Ethernet statistics
- VRX10, VRX10-F status of Ethernet interfaces is monitored
routing ARP tables
OSPF routing status monitoring
ping, traceroute
- ETAG1 status of Ethernet interfaces is monitored
multilink PPP status
bridge status monitoring
routing ARP tables
OSPF routing status monitoring
RIP routing status monitoring
ping, traceroute
- STM14, NUSA2, NUSA1, NUSA1-F status of the SETS is monitored
status of SDH interfaces is monitored
status of the MSP is monitored
status of the terminated VC-4, VC-3 and VC-12 is
monitored
status of the EoS group is monitored
status of Ethernet interfaces is monitored
status of CRC-4 frame alignment
P12 front end and back end loops
mirroring (NUSA2, NUSA1, NUSA1-F only)
Ethernet statistics (NUSA2, NUSA1, NUSA1-F only)

Copyright 2022 Hitachi Energy. All rights reserved. 169

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- SELI8 status of CRC-4 frame alignment
front end and back end loops
- SATP8 status of E1 interfaces is monitored
front end and back end loops
Pseudo Wire status is monitored
Pseudo Wire ping, ARP table, and statistics
Circuit Emulation timing is monitored
TDM pattern generator and analyzer:
- Bit error counter
- Round trip delay measurement
- VOIP1 status of the PSTN and ISDN-BA user ports is moni-
tored
IP ping request
- SDSL8 status of SHDSL interfaces is monitored
line restart
- SUPM1, SUPM2 status of the PSTN user ports is monitored
line testing
- ISDN4 status of the ISDN-BA user ports is monitored
line testing
- TUEM1 status of the E&M signaling ports is monitored
line and conference participant “out of service”
line and conference participant “test signal insertion”
front end and back end loops
- TUXA1 status of the PSTN user port signaling is monitored
line testing
back end loop
- TUDA1 status of the data ports is monitored
line and conference participant “out of service”
line and conference participant “test signal insertion”
front end and back end loops
- TUGE1 status of the data ports is monitored
front end and back end loops

Performance monitoring according to ITU-T G.826

performance calculation for
24 hours intervals (up to 8 records) and
15 minutes intervals (up to 108 records)
- SUSE2, SUSE2-F performance measurement at the SHDSL layer, on
the regenerators and on the CPE,
performance measurement at the Ethernet layer.
- VRX10, VRX10-F performance measurement at the Ethernet inter-
faces:
General counters,
Ethernet counters,
Egress queue counters
performance measurement at the loopback inter-
faces:
MIB-2 statistics
performance measurement at the virtual router inter-
faces:
MIB-2 statistics,
IF-MIB IfX statistics
- ETAG1 performance measurement at the Ethernet inter-
faces and the bridge instances:
MIB-2 statistics,
RSTP statistics,
Protection switchover events.

Copyright 2022 Hitachi Energy. All rights reserved. 170

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- ISDN4 performance measurement at the permanently acti-
vated digital section
- TUDA1 performance measurement on the data ports and on
the conference participants:
Protection switchover events
- TUGE1 performance measurement on the E0 ports:
Protection switchover events,
Positive and negative octet slips
- TUEM1 performance measurement on the E&M ports and
on the conference participants:
Protection switchover events
- TUXA1 performance measurement on the PSTN ports:
Protection switchover events
- SDSL8 performance measurement at the SHDSL layer and
on the remote desktop
- SELI8 performance measurement on the E1 ports
- SATP8 performance measurement on the E1 ports and on
the Pseudo Wires
- STM14, NUSA2, NUSA1, NUSA1-F SETS source switchover events,
MSP switchover events,
performance measurements at the SDH ports,
performance measurements at the terminated VC-4,
VC-3 and VC-12 layers,
VC-4 pointer adjustment events,
performance measurements at the P12 layer,
EoS group statistics

6.4 XMC25 R2 and XMC25 Characteristics

6.4.1 Architecture

System architecture fully modular

open architecture
Subrack 19-inch with 21 slots
- slot 1 … 10 service units 1
- slot 11 core unit
- slot 12 service unit 1
- slot 13 protecting core unit or TDM service unit 2
- slots 14 … 21 service units 1
- slots 9 and 15 WAN port expansion unit 3
- slots 4 and 6 slot pair for NUSA2, NUSA1, NUSA1-F EQP
- slots 18 and 20 slot pair for NUSA2, NUSA1, NUSA1-F EQP
Implementation configurable, according to requirements
Units
- Core units CENT2, COGE7, COGE7-F, COGE5, COGE5-F 4
- Encryption units SECU1-4, SECU1F4, SECU1-8, SECU1F8
- WAN port expansion unit EXPU1 3

Copyright 2022 Hitachi Energy. All rights reserved. 171

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

- Service units ETO12, ETO12-F, ETE24, SUP12

SUSE2, SUSE2-F
VRX10, VRX10-F
SABO1, SABO1-F, SABE1
ETAG1
SELI8
SATP8
VOIP1
VFTLX
TUDA1
SUPM1, SUPM2
ISDN4
IMAG1
TUEM1
TUXA1
TUGE1
SDSL8
STM14, NUSA2, NUSA1, NUSA1-F
- Auxiliary units COOL4
ALMU4-F
DUA25
FIL16
Equipment protection
- Core unit CENT2, COGE7, COGE7-F, COGE5, 1:1 equipment protection
COGE5-F
- SDH transport unit NUSA2, NUSA1, NUSA1-F 1:1 equipment protection
- SDH transport unit STM14 1:1 equipment protection (PBUS access part only)
- Media gateway unit VOIP1 1:1 equipment protection
- Voice frequency processing unit VFTLX 1:1 equipment protection
- IPv4 routing unit VRX10, VRX10-F 1:1 equipment protection 5
- Ethernet switching and routing unit ETAG1 1:1 equipment protection (bridging and routing func-
tions only)
- Data interface unit TUDA1 1:1 equipment protection (conference part only)
- E&M voice interface unit TUEM1 1:1 equipment protection (conference part only)
Internal bus system
- 1 GbE double star interconnection of every slot with 1 Gbit/s to the core
unit slot and the redundant core unit slot (including
GbE point-to-point connection between the core unit
slots)
- 10 GbE double star interconnection of every slot with 10 Gbit/s to the
core unit slot and the redundant core unit slot
(including four 10 GbE point-to-point connections
between the core unit slots)
- 40 GbE double star 6 interconnection of slot 9 and slot 15 with 40 Gbit/s to
the core unit slot and the redundant core unit slot
- PBUS internal TDM bus for up to 128 x 2048 kbit/s (unidi-
rectional)
- CBUS internal bus for control, clocking, powering etc.
Unit software (ESW) downloaded
Configuration software based, with ECST and UNEM

1. With a CENT2 core unit plugged in a XMC25 R2 subrack, the slots 1, 8 to 15 and 21 are not usable for
the service units ETE24, ETO12, SUP12, SUSE2, VRX10, SABO1, SABE1, NUSA1, NUSA2.
2. The service units ETE24, ETO12, SUP12, SUSE2, VRX10, SABO1, SABE1, NUSA1, NUSA2, STM14,
SATP8, VOIP1, ETAG1 and SECU1 are not usable in slot 13.
3. An EXPU1 WAN port expansion unit must be plugged in slot 9 or slot 15 of a XMC25 R2 subrack. The
core units COGE5 and COGE7 do not support the operation with the EXPU1 unit.

Copyright 2022 Hitachi Energy. All rights reserved. 172

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

4. The core units COGE5, COGE5-F, COGE7 and COGE7-F will be supported in the XMC25 R2 subrack
in a future release.
5. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.
6. The 40 GbE double star is not available in the XMC25 subrack.

6.4.2 System Control and Management Functions

6.4.2.1 Control System

Basic control system distributed processor system

Central system control (core unit) dedicated unit with master processor
Service units local slave processors
Management Information Base (MIB)
- Configuration data Configuration data stored on core unit
→ storage of complete NE configuration
Equipment protection of the core unit 1:1 (slots 11 and 13)
- Type of protection warm standby, non-revertive
- MIB of redundant unit permanently updated
- Core unit switch-over - automatic failure driven
- on ECST/UNEM command
CENT2 unit switch-over traffic signal downtime,
manual switch-over via ECST,
MPLS-TP traffic signals
- User traffic connected to the core unit < 50 ms 1
- User traffic connected to a service unit, 50 services < 50 ms 1
- User traffic connected to a service unit, 1000 ser- < 50 ms 1
vices
CENT2 unit switch-over traffic signal downtime,
core unit removed or failed,
250 protected MPLS-TP traffic signals
- Active core unit removed or failed, working tunnels < 50 ms 1
on the active core unit
- Active core unit removed or failed, working tunnels < 50 ms 1
on the standby active core unit
- Standby core unit removed or failed, working tun- no downtime
nels on the active core unit
- Standby core unit removed or failed, working tun- according to the configured MPLS-TP BFD CC inter-
nels on the standby core unit val
COGE5 or COGE7 unit switch-over traffic signal
downtime,
manual switch-over via ECST
- with MPLS-TP, user traffic typical 2 to 5 s, depending of the configuration 1
- with xSTP, user traffic typical 2 to 5 s, depending of the configuration 1
- without xSTP, user traffic typical 2 s, depending of the configuration 1
COGE5 or COGE7 unit switch-over traffic signal
downtime,
active core unit removed
- with MPLS-TP, user traffic typical 2 to 5 s, depending of the configuration 1
- with xSTP, user traffic typical 2 to 5 s, depending of the configuration 1
- without xSTP, user traffic typical 1 s, depending of the configuration 1
Timing function
- Timing synchronization SNTPv3
PTP

Copyright 2022 Hitachi Energy. All rights reserved. 173

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

- Synchronization modes unicast, broadcast

- NE Time local time, with time zones

1. For further details please contact Hitachi Energy customer support.

6.4.2.2 NE Software System

Unit software (ESW) stored directly in flash memory of the unit (core and
service units)
SW download (for ESW) ESW installation controlled by UNEM / ECST
NE wide ESW installation
At least 2 ESW versions can be stored on a unit
Activation of the new ESW on schedule or immedi-
ately
Feature license management allows you to buy equipment with basic functionality
(hardware and/or software) and upgrade with new
feature licenses

6.4.2.3 Management Functions

Configuration management for NE incl. ESW

traffic functions
Performance management for NE
traffic signals
Fault management
- Hardware failures NE and units
- ESW configuration/operation NE and units
- Failures and performance traffic signals
Alarm generation and reporting
- Generation and severity programmable
- Indication local indicators
relay contacts
- Reporting alarm lists
logbooks
export of table data to csv or xml files
syslog (up to 10 destinations, RFC 5424)
remote access
SNMP

Copyright 2022 Hitachi Energy. All rights reserved. 174

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

SNMP MIBs Agent MIBs

- SNMPv2-MIB (RFC 3418)
- SNMP-FRAMEWORK-MIB (RFC 3411)
- SNMP-TARGET-MIB (RFC 3413)
- SNMP-NOTIFICATION-MIB (RFC 3413)
- SNMP-VIEW-BASED-ACM-MIB (RFC 3415)
- SNMP-COMMUNITY-MIB (RFC 3584)
- SNMP-USER-BASED-SM-MIB (RFC 3414)
- SNMPv2-TC (RFC 2579)
Other MIBs
- RMON2-MIB (RFC 4502)
- RMON-MIB (RFC 2819)
- BRIDGE-MIB (RFC 4188)
- Q-BRIDGE-MIB (RFC 4363)
- IANAifTypeMIB
- IF-MIB (RFC 2863)
- ENTITY-MIB (RFC 6933)
- INET-ADDRESS-MIB (RFC 4001)
- ENTITY-SENSOR-MIB (RFC 3433)
- ALARM-MIB (RFC 3877)
- PW-TC-STD-MIB (RFC 5542)
Private MIBs
- XMC-SMI
- XMC-IF-EXT-MIB
- XMC-IANA-BFD-TC-STD-MIB
- XMC-BFD-STD-MIB
- XMC-MPLS-QOS-EXT-MIB
- XMC-UNI-EVC-MIB
- XMC-ETH-PORT-MIB
- XMC-NE-MIB
- XMC-ALARM-EXT-MIB
- XMC-DIAGNOSTIC-MIB
Inventory management for hardware and software
Management tools ECST
UNEM
DIRAC

6.4.2.4 Management Access

Local management access Ethernet local management port, not routed

Remote management access - VLAN Bridge port of the XMC20 Switch, routed
- MPLS-TP port of the XMC20 Switch, routed
- P12 or P0_nc channels, routed
Management routing function - Static routing
- OSPF dynamic routing, RFC2328
- VRRP virtual routing, RFC3768
Management router interfaces - 2 VLAN interfaces (COGE5 and COGE7), 2 VRRP
instances per interface
- 8 VLAN interfaces (CENT2), 2 VRRP instances
per interface
- 16 TDM interfaces, PPP encapsulation, RFC1661
(maximum TDM bandwidth is 16’384 kbit/s)
- 10 MPLS-TP MCC interfaces, RFC5718 (maxi-
mum rate is 2’048 kbit/s)
- 8 loopback interfaces

Copyright 2022 Hitachi Energy. All rights reserved. 175

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

User authentication - local authentication in the NE with userclass and

password
- local authentication in the NE with public/private
keys (for UNEM only)
- remote authentication via RADIUS server, with
local authentication fallback
User classes - session manager
- support
- manager
- maintenance
- information
Management access security Security on network layer with SSH

6.4.3 Mechanics

6.4.3.1 Construction

Card cage for XMC20 units 19-inch practice

Modularity subrack
cable tray
heat deflection shield
fan unit or alarm unit
Installation into racks
- 19-inch direct
- ETSI (applicable standard ETS 300 119-4) with adapters
Basic construction metallic
- Sides and rear sheet metal
- Top and bottom perforated sheet metal
- Front front cover
Connection of signal and power cables
- Power supply integrated connector
- Shields of signal cables grounding bars in front
- Cable installation and strain relief matching cable tray
Degree of protection, IP code (IEC 60529) IP20
- Solid particle protection level 2, > 12.5 mm
- Liquid ingress protection level 0, not protected
Pollution degree IEC 62368-1, 2
Class of equipment IEC 62368-1, class I

6.4.3.2 Capacity and Slots

Slots
- Number of slots 21
- Slot width 20.32 mm
4 HP
Allocation of units to slots flexible, slot 11 dedicated

6.4.3.3 Dimensions

19-inch subrack without front cover 482.6 x 309.5 x 279.7 mm

(W x H x D)
19-inch subrack with front cover 482.6 x 309.5 x 304.3 mm
(W x H x D)

Copyright 2022 Hitachi Energy. All rights reserved. 176

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Cable tray 482.6 x 87.1 x 240 mm

(W x H x D)
Heat deflection shield 2 HU 482.6 x 87.8 x 228 mm
(W x H x D)
Heat deflection shield 1 HU 482.6 x 43.3 x 228 mm
(W x H x D)
Construction and layout 19-inch and ETSI mounting practice
refer to Figure 13: "XMC25 R2 and XMC25 subrack
design and main dimensions (side view)" (on
page 35)

6.4.3.4 Weight

19-inch subrack without front cover 6.44 kg

(without units)
Front cover 1.25 kg
Cable tray 0.87 kg
Heat deflection shield 2 HU 1.58 kg
Heat deflection shield 1 HU 1.00 kg
ETSI adapters 2 HU (set) 0.09 kg
ETSI adapters 9 HU (set) 0.41 kg
ETSI adapters 11 HU (set) 0.50 kg
Weight of units refer to the unit user manuals

6.4.4 COOL4 Fan Unit (R2)

6.4.4.1 Construction

Unit construction 19-inch practice

1 HU (44.45 mm)
Installation into racks
- 19-inch direct
- ETSI (applicable standard ETS 300 119-4) with adapters
Connection of signal and power cable front access

6.4.4.2 Specification

Number of fans 10
Operation temperature controlled
- minimum speed ≤ 35 °C
- maximum speed ≥ 50 °C
Performance, average
minimum speed (free blowing):
- air velocity 1 m/s
- transported air volume 330 m3/h
- pressure drop 25 Pa
- noise 51 dBA @ 1 m
maximum speed (free blowing):
- air velocity 2 m/s
- transported air volume 600 m3/h
- pressure drop 80 Pa
- noise 63 dBA @ 1 m

Copyright 2022 Hitachi Energy. All rights reserved. 177

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Noise
[dBA]

65

60

55

50

45
-20 -10 0 10 20 30 40 50 60 70 80
Temperature
[°C]

6.4.4.3 Alarm Interface

Alarm inputs:
- Number 12
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
- Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED
- Partial unit failure 1 yellow LED
- Total unit failure 1 red LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

Copyright 2022 Hitachi Energy. All rights reserved. 178

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.4.4.4 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- switch on voltage (power up) -35 VDC
- switch off voltage (power down) -27 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply)
- minimum speed (with all fans operating,
T < 35 °C) ≤ 29 W
- maximum speed (with all fans operating,
T > 50 °C) ≤ 58 W
Connector Molex Mini-Fit Jr.

6.4.4.5 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -10°C … +70°C
- Minimum start up temperature -25°C

6.4.4.6 Mechanical Parameters

Overall dimensions (W x H x D) 482.6 x 43.6 x 248.6 mm

Construction 19-inch and ETSI mounting
Weight COOL4 without packaging 2.80 kg
Weight COOL4 power cable 0.06 kg
Weight ETSI adapters 1 HU 0.05 kg

6.4.4.7 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F)

- partial failure (1 fan failed) 10.3 years
- total failure (>1 fan failed) 1176 years

Please note:
The COOL4 failure prediction model shows that 10% of fan units will fail when
operated at a constant ambient temperature of 50°C after 1.34 years.
→ Therefore, if COOL4 is expected to be operated in high temperature environ-
ments, Hitachi Energy recommends to provision reasonable stock to minimize
replacement time.

6.4.5 ALMU4-F Alarm Unit (R1)

6.4.5.1 Construction

Unit construction 19-inch practice

1 HU (44.45 mm)
Installation into racks
- 19-inch direct
- ETSI (applicable standard ETS 300 119-4) with adapters
Connection of signal and power cable front access

Copyright 2022 Hitachi Energy. All rights reserved. 179

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.4.5.2 Alarm Interface

Alarm inputs:
- Number 12
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
- Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

6.4.5.3 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply) ≤1W
Connector Molex Mini-Fit Jr.

6.4.5.4 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -25°C … +55°C

6.4.5.5 Mechanical Parameters

Overall dimensions (W x H x D) 482.6 x 43.6 x 248.8 mm

Construction 19-inch and ETSI mounting
Weight ALMU4-F without packaging 1.60 kg

Copyright 2022 Hitachi Energy. All rights reserved. 180

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Weight ALMU4-F power cable 0.06 kg

Weight ETSI adapters 1 HU 0.05 kg

6.4.5.6 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 602 years

6.4.6 DUA25 Dual Power Supply Input Unit

Power inputs U1
U2

6.4.6.1 Interfaces

Power output to XMC20 UTF

Alarm outputs Supervision U1
Supervision U2

6.4.6.2 Specifications

Input voltage range -40.0 … -75 VDC

Maximum reverse polarity +75 VDC
Maximum output current 30 A
Typical power dissipation at maximum current 10 W

6.4.6.3 Alarm Interface

Alarm threshold voltage -33 ± 3 VDC

Alarm polarity active open
Electrical contacts:
- Type solid state
- Current ≤ 10 mA
- Voltage drop @ 10 mA ≤2V
- Open contact maximum voltage -75 V
- Leakage current @ -75 V ≤ 100 μA
Connector Molex Mini-Fit Jr.

6.4.6.4 Mechanical Parameters

Installation Mechanically integrated in the XMC25 R2 or XMC25

subrack
Overall dimensions (W x H x D) 438 x 31.7 x 52.6 mm
Weight without packaging 0.41 kg

6.4.6.5 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 1610 years

Copyright 2022 Hitachi Energy. All rights reserved. 181

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.4.7 Power Consumption

Maximum admissible power consumption of a

XMC25 R2 or XMC25, continuous
- at -48 VDC 1800 W (XMC25 R2, and XMC25 subrack revision
R2A and later)
- at -60 VDC 1800 W (XMC25 R2, and XMC25 subrack revision
R2A and later)

6.4.8 Power Dissipation

Maximum power dissipation in a XMC25 R2 or

XMC25 subrack
- with active cooling (with fan unit) 1800 W (XMC25 R2, and XMC25 subrack revision
R2A and later)
- with passive cooling (without fan unit) 500 W

6.5 XMC23 Characteristics

6.5.1 Architecture

System architecture fully modular

open architecture
Subrack 19-inch mountable (horizontal mounting) with 8 slots
(slots numbered 7 … 14)
- slot 7 … 10, 12, 14 service units
- slot 11 core unit
- slot 13 protecting core unit or TDM service unit 1
- slots 7 and 9 slot pair for NUSA2, NUSA1, NUSA1-F EQP
Implementation configurable, according to requirements
Units
- Core units CENT2, COGE7, COGE7-F, COGE5, COGE5-F
- Encryption units SECU1-4, SECU1F4, SECU1-8, SECU1F8
- Service units ETO12, ETO12-F, ETE24, SUP12
SUSE2, SUSE2-F
VRX10, VRX10-F
SABO1, SABO1-F, SABE1
ETAG1
SELI8
SATP8
VOIP1
VFTLX
TUDA1
SUPM1, SUPM2
ISDN4
IMAG1
TUEM1
TUXA1
TUGE1
SDSL8
STM14, NUSA2, NUSA1, NUSA1-F

Copyright 2022 Hitachi Energy. All rights reserved. 182

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

- Auxiliary units COOL6

ALMU6-F
DUA23
FIL16
Equipment protection
- Core unit CENT2, COGE7, COGE7-F, COGE5, 1:1 equipment protection
COGE5-F
- SDH transport unit NUSA2, NUSA1, NUSA1-F 1:1 equipment protection
- SDH transport unit STM14 1:1 equipment protection (PBUS access part only)
- Media gateway unit VOIP1 1:1 equipment protection
- Voice frequency processing unit VFTLX 1:1 equipment protection
- IPv4 routing unit VRX10, VRX10-F 1:1 equipment protection 2
- Ethernet switching and routing unit ETAG1 1:1 equipment protection (bridging and routing func-
tions only)
- Data interface unit TUDA1 1:1 equipment protection (conference part only)
- E&M voice interface unit TUEM1 1:1 equipment protection (conference part only)
Internal bus system
- GbE double star interconnection of every slot with 1 Gbit/s to the core
unit slot and the redundant core unit slot (including
GbE point-to-point connection between the core unit
slots
- 10 GbE double star interconnection of every slot with 10 Gbit/s to the
core unit slot and the redundant core unit slot
(including four 10 GbE point-to-point connections
between the core unit slots)
- PBUS internal TDM bus for up to 128 x 2048 kbit/s (unidi-
rectional)
- CBUS internal bus for control, clocking, powering etc.
Unit software (ESW) downloaded
Configuration software based, with ECST and UNEM

1. The service units ETE24, ETO12, SUP12, SUSE2, SABO1, SABE1, VRX10, NUSA1, NUSA2, STM14,
SATP8, VOIP1, ETAG1 and SECU1 are not usable in slot 13
2. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.

6.5.2 System Control and Management Functions

6.5.2.1 Control System

Basic control system distributed processor system

Central system control (core unit) dedicated unit with master processor
Service units local slave processors
Management Information Base (MIB)
- Configuration data Configuration data stored on core unit
→ storage of complete NE configuration
Equipment protection of the core unit 1:1 (slots 11 and 13)
- Type of protection warm standby, non-revertive
- MIB of redundant unit permanently updated
- Core unit switch-over automatic failure driven
on ECST/UNEM command
CENT2 unit switch-over traffic signal downtime,
manual switch-over via ECST,
MPLS-TP traffic signals

Copyright 2022 Hitachi Energy. All rights reserved. 183

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

- User traffic connected to the core unit < 50 ms 1

- User traffic connected to a service unit, 50 tunnels < 50 ms 1
- User traffic connected to a service unit, 2000 tun- < 50 ms 1
nels
CENT2 unit switch-over traffic signal downtime,
core unit removed or failed,
250 protected MPLS-TP traffic signals
- Active core unit removed or failed, working tunnels < 50 ms 1
on the active core unit
- Active core unit removed or failed, working tunnels < 50 ms 1
on the standby active core unit
- Standby core unit removed or failed, working tun- no downtime
nels on the active core unit
- Standby core unit removed or failed, working tun- according to the configured MPLS-TP BFD CC inter-
nels on the standby core unit val
COGE5 or COGE7 unit switch-over traffic signal
downtime,
manual switch-over via ECST
- with MPLS-TP, user traffic typical 2 to 5 s, depending of the configuration 1
- with xSTP, user traffic typical 2 to 5 s, depending of the configuration 1
- without xSTP, user traffic typical 2 s, depending of the configuration 1
COGE5 or COGE7 unit switch-over traffic signal
downtime,
active core unit removed
- with MPLS-TP, user traffic typical 2 to 5 s, depending of the configuration 1
- with xSTP, user traffic typical 2 to 5 s, depending of the configuration 1
- without xSTP, user traffic typical 1 s, depending of the configuration 1
Timing function
- Timing synchronization SNTPv3
PTP
- Synchronization modes unicast, broadcast
- NE Time local time, with time zones

1. For further details please contact Hitachi Energy customer support.

6.5.2.2 NE Software System

Unit software (ESW) stored directly in flash memory of the unit (core and
service units)
SW download (for ESW) ESW installation controlled by UNEM / ECST
NE wide ESW installation
At least 2 ESW versions can be stored on a unit
Activation of the new ESW on schedule or immedi-
ately
Feature license management allows you to buy equipment with basic functionality
(hardware and/or software) and upgrade with new
feature licenses

6.5.2.3 Management Functions

Configuration management for NE incl. ESW

traffic functions
Performance management for NE
traffic signals

Copyright 2022 Hitachi Energy. All rights reserved. 184

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Fault management
- Hardware failures NE and units
- ESW configuration/operation units
- Failures and performance traffic signals
Alarm generation and reporting
- Generation and severity programmable
- Indication local indicators
- Reporting alarm lists
logbooks
export of table data to csv or xml files
syslog (up to 10 destinations, RFC 5424)
remote access
SNMP
SNMP MIBs Agent MIBs
- SNMPv2-MIB (RFC 3418)
- SNMP-FRAMEWORK-MIB (RFC 3411)
- SNMP-TARGET-MIB (RFC 3413)
- SNMP-NOTIFICATION-MIB (RFC 3413)
- SNMP-VIEW-BASED-ACM-MIB (RFC 3415)
- SNMP-COMMUNITY-MIB (RFC 3584)
- SNMP-USER-BASED-SM-MIB (RFC 3414)
- SNMPv2-TC (RFC 2579)
Other MIBs
- RMON2-MIB (RFC 4502)
- RMON-MIB (RFC 2819)
- BRIDGE-MIB (RFC 4188)
- Q-BRIDGE-MIB (RFC 4363)
- IANAifTypeMIB
- IF-MIB (RFC 2863)
- ENTITY-MIB (RFC 6933)
- INET-ADDRESS-MIB (RFC 4001)
- ENTITY-SENSOR-MIB (RFC 3433)
- ALARM-MIB (RFC 3877)
- PW-TC-STD-MIB (RFC 5542)
Private MIBs
- XMC-SMI
- XMC-IF-EXT-MIB
- XMC-IANA-BFD-TC-STD-MIB
- XMC-BFD-STD-MIB
- XMC-MPLS-QOS-EXT-MIB
- XMC-UNI-EVC-MIB
- XMC-ETH-PORT-MIB
- XMC-NE-MIB
- XMC-ALARM-EXT-MIB
- XMC-DIAGNOSTIC-MIB
Inventory management for hardware and software
Management tools ECST
UNEM
DIRAC

6.5.2.4 Management Access

Local management access Ethernet local management port, not routed

Remote management access - VLAN Bridge port of the XMC20 Switch, routed
- MPLS-TP port of the XMC20 Switch, routed
- P12 or P0_nc channels, routed
Management routing function - Static routing
- OSPF dynamic routing, RFC2328
- VRRP virtual routing, RFC3768

Copyright 2022 Hitachi Energy. All rights reserved. 185

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Management router interfaces - 2 VLAN interfaces (COGE5 and COGE7), 2 VRRP

instances per interface
- 8 VLAN interfaces (CENT2), 2 VRRP instances
per interface
- 16 TDM interfaces, PPP encapsulation, RFC1661
(maximum TDM bandwidth is 16’384 kbit/s)
- 10 MPLS-TP MCC interfaces, RFC5718 (maxi-
mum rate is 2’048 kbit/s)
- 8 loopback interfaces
User authentication - local authentication in the NE with userclass and
password
- local authentication in the NE with public/private
keys (for UNEM only)
- remote authentication via RADIUS server, with
local authentication fallback
User classes - session manager
- support
- manager
- maintenance
- information
Management access security Security on network layer with SSH

6.5.3 Mechanics

6.5.3.1 Construction

Card cage for XMC20 units 19-inch practice when mounted horizontally
Modularity subrack
cable tray
fan unit or alarm unit
Installation into racks
- 19-inch with adapters
- ETSI (applicable standard ETS 300 119-4) with adapters
Basic construction metallic
- Sides and rear sheet metal
- Top and bottom perforated sheet metal
- Front front cover
Connection of signal and power cables
- Power supply integrated connector
- Shields of signal cables grounding bars in front
- Cable installation and strain relief matching cable tray
Degree of protection, IP code (IEC 60529) IP20
- Solid particle protection level 2, > 12.5 mm
- Liquid ingress protection level 0, not protected
Pollution degree IEC 62368-1, 2
Class of equipment IEC 62368-1, class I

6.5.3.2 Capacity and Slots

Slots
- Number of slots 8
- Slot width 20.32 mm
4 HP
Allocation of units to slots flexible, slot 11 dedicated

Copyright 2022 Hitachi Energy. All rights reserved. 186

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.5.3.3 Dimensions

Subrack without front cover 458.45 x 176.1 x 280.3 mm

(W x H x D)
Subrack with front cover 458.45 x 176.1 x 303.3 mm
(W x H x D)
19-inch mountable subrack with front cover, includ- 482.6 x 176.1 x 303.3 mm
ing 19-inch adapters
(W x H x D)
ETSI rack mountable subrack with front cover, 532.4 x 176.1 x 303.3 mm
including ETSI adapters
(W x H x D)
Cable tray 138.0 x 166.5 x 49.2 mm
(W x H x D)
Construction and layout 19-inch and ETSI mounting practice
refer to Figure 14: "XMC23 subrack design and main
dimensions (side view)" (on page 36)

6.5.3.4 Weight

19-inch subrack without front cover 4.45 kg

(without units, without 19-inch adapter)
Front cover 0.71 kg
Cable tray, included with the 19-inch adapter 0.18 kg
ETSI adapters 4 HU (set) 0.35 kg
Weight of units refer to the unit user manuals

6.5.4 COOL6 Fan Unit (R2)

6.5.4.1 Construction

Unit construction special plug-in unit to XMC23 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs front access connectors

6.5.4.2 Specification

Number of fans 4
Operation temperature controlled
- minimum speed ≤ 20 °C
- maximum speed ≥ 35 °C
Performance, average:
minimum speed (free blowing):
- transported air volume 210 m3/h
- noise 50 dBA @ 1 m
maximum speed (free blowing):
- transported air volume 360 m3/h
- noise 59 dBA @ 1 m

Copyright 2022 Hitachi Energy. All rights reserved. 187

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Noise
[dBA]

65

60

55

50

45
-20 -10 0 10 20 30 40 50 60 70 80
Temperature
[°C]

6.5.4.3 Alarm Interface

Alarm inputs:
- Number 12
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED
- Partial unit failure 1 yellow LED
- Total unit failure 1 red LED

6.5.4.4 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- switch on voltage (power up) -35 VDC
- switch off voltage (power down) -27 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply)
- minimum speed (with all fans operating,
T < 20 °C) ≤ 10 W
- maximum speed (with all fans operating,
T > 35 °C) ≤ 24 W
Connector on the backplane Molex Mini-Fit Jr.

6.5.4.5 Ambient Conditions

Specifications according to the common system specification, except the following parameters:

Copyright 2022 Hitachi Energy. All rights reserved. 188

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Operation
- Temperature range -10°C … +70°C
- Minimum start up temperature -25°C

6.5.4.6 Mechanical Parameters

Overall dimensions (W x H x D) 165 x 40 x 235 mm

Construction plug-in unit
Weight COOL6 without packaging 0.650 kg

6.5.4.7 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F)

- partial failure (1 fan failed) 13.6 years
- total failure (>1 fan failed) 1’667 years

Please note:
The COOL6 failure prediction model shows that 10% of fan units will fail when
operated at a constant ambient temperature of 50°C after 2.45 years.
→ Therefore, if COOL6 is expected to be operated in high temperature environ-
ments, Hitachi Energy recommends to provision reasonable stock to minimize
replacement time.

6.5.5 COOL6 Fan Unit (R3)

6.5.5.1 Construction

Unit construction special plug-in unit to XMC23 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs and outputs front access connectors

6.5.5.2 Specification

Number of fans 4
Operation temperature controlled
- minimum speed ≤ 35 °C
- maximum speed ≥ 50 °C
Performance, average:
minimum speed (free blowing):
- transported air volume 200 m3/h
- noise 48 dBA @ 1 m
maximum speed (free blowing):
- transported air volume 360 m3/h
- noise 59 dBA @ 1 m

Copyright 2022 Hitachi Energy. All rights reserved. 189

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Noise
[dBA]

65

60

55

50

45
-20 -10 0 10 20 30 40 50 60 70 80
Temperature
[°C]

6.5.5.3 Alarm Interface

Alarm inputs:
- Number 12
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED
- Partial unit failure 1 yellow LED
- Total unit failure 1 red LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

Copyright 2022 Hitachi Energy. All rights reserved. 190

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.5.5.4 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- switch on voltage (power up) -35 VDC
- switch off voltage (power down) -27 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply)
- minimum speed (with all fans operating,
T < 35 °C) ≤ 10 W
- maximum speed (with all fans operating,
T > 50 °C) ≤ 24 W
Connector on the backplane Molex Mini-Fit Jr.

6.5.5.5 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -10°C … +70°C
- Minimum start up temperature -25°C

6.5.5.6 Mechanical Parameters

Overall dimensions (W x H x D) 165 x 40 x 235 mm

Construction plug-in unit
Weight COOL6 without packaging 0.650 kg

6.5.5.7 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F)

- partial failure (1 fan failed) 13.5 years
- total failure (>1 fan failed) 1’667 years

Please note:
The COOL6 failure prediction model shows that 10% of fan units will fail when
operated at a constant ambient temperature of 50°C after 2.45 years.
→ Therefore, if COOL6 is expected to be operated in high temperature environ-
ments, Hitachi Energy recommends to provision reasonable stock to minimize
replacement time.

6.5.6 ALMU6-F Alarm Unit (R1)

6.5.6.1 Construction

Unit construction special plug-in unit to XMC23 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs and outputs front access connectors

Copyright 2022 Hitachi Energy. All rights reserved. 191

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.5.6.2 Alarm Interface

Alarm inputs:
- Number 12
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the battery (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

6.5.6.3 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC battery) ≤1W
Connector on the backplane Molex Mini-Fit Jr.

6.5.6.4 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -25°C … +55°C

6.5.6.5 Mechanical Parameters

Overall dimensions (W x H x D) 165 x 40 x 235 mm

Construction plug-in unit
Weight ALMU6-F without packaging 0.30 kg

Copyright 2022 Hitachi Energy. All rights reserved. 192

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.5.6.6 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 602 years

6.5.7 DUA23 Dual Power Supply Input Unit

Power inputs U1
U2

6.5.7.1 Interfaces

Power output to XMC20 UTF

Alarm outputs Supervision U1
Supervision U2

6.5.7.2 Specifications

Input voltage range -40.0 … -75 VDC

Maximum reverse polarity +75 VDC
Maximum output current 15 A
Typical power dissipation at maximum current 5W

6.5.7.3 Alarm Interface

Alarm threshold voltage -29 … -34 VDC

Alarm polarity active open
Electrical contacts:
- Type solid state
- Current ≤ 10 mA
- Voltage drop @ 10 mA ≤2V
- Open contact maximum voltage -75 V
- Leakage current @ -75 V ≤ 100 μA
Connector Molex Mini-Fit Jr.

6.5.7.4 Mechanical Parameters

Installation Mounted on the XMC23 cable tray

Overall dimensions (W x H x D) excluding front
panel overlap 32 x 42 x 143 mm
Weight without packaging, including alarm cable
0.31 kg

6.5.7.5 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 1604 years

6.5.8 Power Consumption

Maximum admissible power consumption of a

XMC23, continuous
- at -48 VDC 600 W
- at -60 VDC 600 W

Copyright 2022 Hitachi Energy. All rights reserved. 193

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.5.9 Power Dissipation

Maximum power dissipation in a XMC23 subrack

- with active cooling (with fan unit) 600 W
- with passive cooling (without fan unit) 200 W

6.6 XMC22 Characteristics

6.6.1 Architecture

System architecture fully modular

open architecture
Subrack 19-inch mountable (horizontal mounting) with 4 slots
(slots numbered 9 … 12)
- slot 9 … 10, 12 service units
- slot 11 core unit
Implementation configurable, according to requirements
Units
- Core units COGE7, COGE7-F, COGE5, COGE5-F
- Encryption units SECU1-4, SECU1F4, SECU1-8, SECU1F8
- Service units ETO12, ETO12-F, ETE24, SUP12
SUSE2, SUSE2-F
VRX10, VRX10-F
SABO1, SABO1-F, SABE1
ETAG1
SELI8
SATP8
VOIP1
VFTLX
TUDA1
SUPM1, SUPM2
ISDN4
IMAG1
TUEM1
TUXA1
TUGE1
SDSL8
STM14, NUSA2, NUSA1, NUSA1-F
- Auxiliary units COOL8
ALMU8-F
DUA23
XMC22 AC power kit (includes the AC/DC converter
POAC1)
FIL16
Equipment protection
- SDH transport unit STM14 1:1 equipment protection (PBUS access part only)
- Media gateway unit VOIP1 1:1 equipment protection
- Voice frequency processing unit VFTLX 1:1 equipment protection
- IPv4 routing unit VRX10, VRX10-F 1:1 equipment protection 1
- Ethernet switching and routing unit ETAG1 1:1 equipment protection (bridging and routing func-
tions only)
- Data interface unit TUDA1 1:1 equipment protection (conference part only)
- E&M voice interface unit TUEM1 1:1 equipment protection (conference part only)

Copyright 2022 Hitachi Energy. All rights reserved. 194

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Internal bus system

- GbE single star interconnection of every slot with 1 Gbit/s to the core
unit slot
- PBUS internal TDM bus for up to 128 x 2048 kbit/s (unidi-
rectional)
- CBUS internal bus for control, clocking, powering etc.
Unit software (ESW) downloaded
Configuration software based, with ECST and UNEM

1. Equipment protection with the VRX10 unit is only supported up to the ESW release r2.

6.6.2 System Control and Management Functions

6.6.2.1 Control System

Basic control system distributed processor system

Central system control (core unit) dedicated unit with master processor
Service units local slave processors
Management Information Base (MIB)
- Configuration data Configuration data stored on core unit
→ storage of complete NE configuration
Timing function
- Timing synchronization SNTPv3
PTP
- Synchronization modes unicast, broadcast
- NE Time local time, with time zones

6.6.2.2 NE Software System

Unit software (ESW) stored directly in flash memory of the unit (core and
service units)
SW download (for ESW) ESW installation controlled by UNEM / ECST
NE wide ESW installation
At least 2 ESW versions can be stored on a unit
Activation of the new ESW on schedule or immedi-
ately
Feature license management allows you to buy equipment with basic functionality
(hardware and/or software) and upgrade with new
feature licenses

6.6.2.3 Management Functions

Configuration management for NE incl. ESW

traffic functions
Performance management for NE
traffic signals
Fault management
- Hardware failures NE and units
- ESW configuration/operation units
- Failures and performance traffic signals
Alarm generation and reporting
- Generation and severity programmable
- Indication local indicators

Copyright 2022 Hitachi Energy. All rights reserved. 195

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

- Reporting alarm lists

logbooks
export of table data to csv or xml files
syslog (up to 10 destinations, RFC 5424)
remote access
SNMP
SNMP MIBs Agent MIBs
- SNMPv2-MIB (RFC 3418)
- SNMP-FRAMEWORK-MIB (RFC 3411)
- SNMP-TARGET-MIB (RFC 3413)
- SNMP-NOTIFICATION-MIB (RFC 3413)
- SNMP-VIEW-BASED-ACM-MIB (RFC 3415)
- SNMP-COMMUNITY-MIB (RFC 3584)
- SNMP-USER-BASED-SM-MIB (RFC 3414)
- SNMPv2-TC (RFC 2579)
Other MIBs
- RMON2-MIB (RFC 4502)
- RMON-MIB (RFC 2819)
- BRIDGE-MIB (RFC 4188)
- Q-BRIDGE-MIB (RFC 4363)
- IANAifTypeMIB
- IF-MIB (RFC 2863)
- ENTITY-MIB (RFC 6933)
- INET-ADDRESS-MIB (RFC 4001)
- ENTITY-SENSOR-MIB (RFC 3433)
- ALARM-MIB (RFC 3877)
- PW-TC-STD-MIB (RFC 5542)
Private MIBs
- XMC-SMI
- XMC-IF-EXT-MIB
- XMC-IANA-BFD-TC-STD-MIB
- XMC-BFD-STD-MIB
- XMC-MPLS-QOS-EXT-MIB
- XMC-UNI-EVC-MIB
- XMC-ETH-PORT-MIB
- XMC-NE-MIB
- XMC-ALARM-EXT-MIB
- XMC-DIAGNOSTIC-MIB
Inventory management for hardware and software
Management tools ECST
UNEM
DIRAC

6.6.2.4 Management Access

Local management access Ethernet local management port, not routed

Remote management access - VLAN Bridge port of the XMC20 Switch, routed
- MPLS-TP port of the XMC20 Switch, routed
- P12 or P0_nc channels, routed
Management routing function - Static routing
- OSPF dynamic routing, RFC2328
- VRRP virtual routing, RFC3768
Management router interfaces - 2 VLAN interfaces (COGE5 and COGE7), 2 VRRP
instances per interface
- 16 TDM interfaces, PPP encapsulation, RFC1661
- (maximum TDM bandwidth is 16’384 kbit/s)
- 10 MPLS-TP MCC interfaces, RFC5718
- (maximum rate is 2’048 kbit/s)
- 8 loopback interfaces

Copyright 2022 Hitachi Energy. All rights reserved. 196

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

User authentication - local authentication in the NE with userclass and

password
- local authentication in the NE with public/private
keys (for UNEM only)
- remote authentication via RADIUS server, with
local authentication fallback
User classes - session manager
- support
- manager
- maintenance
- information
Management access security Security on network layer with SSH

6.6.3 Mechanics

6.6.3.1 Construction

Card cage for XMC20 units 19-inch practice when mounted horizontally
Modularity subrack
19-inch adapter
fan unit
AC/DC converter
Installation into racks
- 19-inch with adapters
Basic construction metallic
- Sides and rear sheet metal
- Top and bottom perforated sheet metal
- Front front cover
Connection of signal and power cables
- Power supply integrated connector
- Shields of signal cables grounding bars in front
- Cable installation and strain relief directly on the rack
Degree of protection, IP code (IEC 60529) IP20
- Solid particle protection level 2, > 12.5 mm
- Liquid ingress protection level 0, not protected
Pollution degree IEC 62368-1, 2
Class of equipment IEC 62368-1, class I

6.6.3.2 Capacity and Slots

Slots
- Number of slots 4
- Slot width 20.32 mm
4 HP
Allocation of units to slots flexible, slot 11 dedicated

6.6.3.3 Dimensions

Subrack without front cover 458.45 x 94.9 x 280.3 mm

(W x H x D)
Subrack with front cover 458.45 x 94.9 x 303.3 mm
(W x H x D)

Copyright 2022 Hitachi Energy. All rights reserved. 197

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

19-inch mountable subrack with front cover, includ- 482.6 x 94.9 x 303.3 mm
ing 19-inch adapters
(W x H x D)
19-inch adapter 85.3.0 x 90.8 x 242.5 mm
(W x H x D)
Construction and layout 19-inch mounting practice
refer to Figure 15: "XMC22 subrack design and main
dimensions (side view)" (on page 36)

6.6.3.4 Weight

19-inch subrack without front cover 2.76 kg

(without units, without 19-inch adapter)
Front cover 0.49 kg
19-inch adapter 0.31 kg
XMC22 AC power kit (excluding POAC1) 0.08 kg
Weight of units refer to the unit user manuals

6.6.4 COOL8 Fan Unit (R1)

6.6.4.1 Construction

Unit construction special plug-in unit to XMC22 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs front access connectors

6.6.4.2 Specification

Number of fans 2
Operation temperature controlled
- minimum speed ≤ 35 °C
- maximum speed ≥ 50 °C
Performance, average:
minimum speed (free blowing):
- transported air volume 100 m3/h
- noise 45 dBA @ 1 m
maximum speed (free blowing):
- transported air volume 180 m3/h
- noise 58 dBA @ 1 m

Copyright 2022 Hitachi Energy. All rights reserved. 198

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Noise
[dBA]

60

55

50

45

40
-20 -10 0 10 20 30 40 50 60 70 80
Temperature
[°C]

6.6.4.3 Alarm Interface

Alarm inputs:
- Number 4
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED
- Partial unit failure 1 yellow LED
- Total unit failure 1 red LED

6.6.4.4 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- switch on voltage (power up) -35 VDC
- switch off voltage (power down) -27 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply)
- minimum speed (with all fans operating,
T < 20 °C) ≤ 4.5 W
- maximum speed (with all fans operating,
T > 35 °C) ≤ 11.5 W
Connector on the backplane Molex Mini-Fit Jr.

6.6.4.5 Ambient Conditions

Specifications according to the common system specification, except the following parameters:

Copyright 2022 Hitachi Energy. All rights reserved. 199

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Operation
- Temperature range -10°C … +70°C
- Minimum start up temperature -25°C

6.6.4.6 Mechanical Parameters

Overall dimensions (W x H x D) 85 x 42 x 235 mm

Construction plug-in unit
Weight COOL8 without packaging 0.29 kg

6.6.4.7 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F)

- partial failure (1 fan failed) 17.7 years
- total failure (>1 fan failed) 1’667 years

Please note:
The COOL8 failure prediction model shows that 10% of fan units will fail when
operated at a constant ambient temperature of 60°C after 3.2 years.
→ Therefore, if COOL8 is expected to be operated in high temperature environ-
ments, Hitachi Energy recommends to provision reasonable stock to minimize
replacement time.

6.6.5 COOL8 Fan Unit (R2)

6.6.5.1 Construction

Unit construction special plug-in unit to XMC22 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs front access connectors

6.6.5.2 Specification

Number of fans 2
Operation temperature controlled
- minimum speed ≤ 35 °C
- maximum speed ≥ 50 °C
Performance, average:
minimum speed (free blowing):
- transported air volume 100 m3/h
- noise 45 dBA @ 1 m
maximum speed (free blowing):
- transported air volume 180 m3/h
- noise 58 dBA @ 1 m

Copyright 2022 Hitachi Energy. All rights reserved. 200

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

Noise
[dBA]

60

55

50

45

40
-20 -10 0 10 20 30 40 50 60 70 80
Temperature
[°C]

6.6.5.3 Alarm Interface

Alarm inputs:
- Number 4
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the DC power supply (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED
- Partial unit failure 1 yellow LED
- Total unit failure 1 red LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

Copyright 2022 Hitachi Energy. All rights reserved. 201

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.6.5.4 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- switch on voltage (power up) -35 VDC
- switch off voltage (power down) -27 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC power supply)
- minimum speed (with all fans operating,
T < 20 °C) ≤ 4.5 W
- maximum speed (with all fans operating,
T > 35 °C) ≤ 11.5 W
Connector on the backplane Molex Mini-Fit Jr.

6.6.5.5 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -10°C … +70°C
- Minimum start up temperature -25°C

6.6.5.6 Mechanical Parameters

Overall dimensions (W x H x D) 85 x 42 x 235 mm

Construction plug-in unit
Weight COOL8 without packaging 0.29 kg

6.6.5.7 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F)

- partial failure (1 fan failed) 17.6 years
- total failure (>1 fan failed) 1’667 years

Please note:
The COOL8 failure prediction model shows that 10% of fan units will fail when
operated at a constant ambient temperature of 60°C after 3.2 years.
→ Therefore, if COOL8 is expected to be operated in high temperature environ-
ments, Hitachi Energy recommends to provision reasonable stock to minimize
replacement time.

6.6.6 ALMU8-F Alarm Unit (R1)

6.6.6.1 Construction

Unit construction special plug-in unit to XMC22 subrack, 1 HU (44.45

mm)
Installation into subrack plug-in unit, fixed with screws
Connection of signals and power via backplane connector
Connection of alarm inputs and outputs front access connectors

Copyright 2022 Hitachi Energy. All rights reserved. 202

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.6.6.2 Alarm Interface

Alarm inputs:
- Number 4
- User defined names for input signals yes
- Active signal level configurable via ECST/UNEM
- active ground
- active open
Thresholds for detection:
- Reference positive terminal of the battery (earth)
- “Ground state” range -8 V … +75 V with respect to reference
- “Open state” range -75 V … -16 V with respect to reference
- Surge immunity 1.2/50 µs surge impulses with U = ± 2000 V
Connector Molex Mini-Fit Jr.

Optical alarm indications:

- Unit powered 1 green LED

Alarm outputs:
- Number 2
- Type switch over contact relays
- Use alarm status of NE
- “Service Affecting Alarm”
- “Non-Service Affecting Alarm”
- Current admissible < 200 mA
- Open contact max. voltage 80 V
- Insulation (any alarm output lead to earth) 750 VRMS / 50 Hz / 60 s
Conditions at the alarm outputs in case of
Power fail:
- “Service Affecting Alarm” output active
- “Non-Service Affecting Alarm” output not active
Connector Molex Mini-Fit Jr.

6.6.6.3 Power Supply

Voltage range
- nominal -48 VDC, -60 VDC
- range -39.5 VDC … -75 VDC
- resistance to reverse polarity +75 VDC
Power consumption (-48 VDC battery) ≤1W
Connector on the backplane Molex Mini-Fit Jr.

6.6.6.4 Ambient Conditions

Specifications according to the common system specification, except the following parameters:
Operation
- Temperature range -25°C … +55°C

6.6.6.5 Mechanical Parameters

Overall dimensions (W x H x D) 85 x 42 x 235 mm

Construction plug-in unit
Weight ALMU8-F without packaging 0.20 kg

Copyright 2022 Hitachi Energy. All rights reserved. 203

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.6.6.6 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 602 years

6.6.7 DUA23 Dual Power Supply Input Unit

Please refer to section 6.5.7 DUA23 Dual Power Supply Input Unit (on page 193).

6.6.8 POAC1 AC/DC Power Converter

6.6.8.1 Construction

Unit construction special plug-in unit for the 19-inch adapter of the
XMC22 subrack
Installation into subrack plug-in unit, fixed with screws
Connection of AC and DC power via AC/DC backplane connectors
Connection of alarm outputs via AC/DC backplane connector to COOL8 or
ALMU8-F

6.6.8.2 Specification

Nominal input voltages - 115 VAC,

- 230 VAC
Input voltage range 90 VAC … 264 VAC
Maximum continuous input current
- @ 230 VAC 2.2 A
- @ 115 VAC 4.5 A
External fuse 6A class B
Output voltage -52.0 VDC … -53.0 VDC
Maximum continuous output current 8A
Maximum backup battery charge current 2A
Maximum continuous output power 350 W
Maximum usable output power for the XMC22
- without backup battery 350 W
- with backup battery 244 W

6.6.8.3 Ambient Conditions

Specifications according to the common system specification.

6.6.8.4 Mechanical Parameters

Overall dimensions (W x H x D) 105 x 41 x 199 mm

Construction plug-in unit
Weight POAC1 unit without packaging 1.12 kg

6.6.8.5 Dependability

Calculated MTTF at 35 °C (MIL-HDBK-217F) 6.5 years

Copyright 2022 Hitachi Energy. All rights reserved. 204

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

6.6.9 Power Consumption

Maximum admissible power consumption of a

XMC22, continuous
- at -48 VDC 380 W
- at -60 VDC 380 W

6.6.10 Power Dissipation

Maximum power dissipation in a XMC22 subrack

- with active cooling (with fan unit) 380 W
1
- with passive cooling (without fan unit) 80 W

1. Passive cooling is only possible without the AC/DC converter POAC1 mounted in the XMC22 subrack.

6.7 EMC/ESD and Safety

6.7.1 EMC

6.7.1.1 Product Family Standard

XMC25 R2 or XMC25 or XMC23 or XMC22

Public Telecommunication network equipment ETSI EN 300 386 V1.6.1
Additional EMC requirements and resistibility ETSI ES 201 468 V1.3.1, test level 2
requirements for telecommunication equipment for
enhanced availability of service
Railway applications - Electromagnetic compatibil- EN 50121-4 (2016)
ity - Part 4: Emission and immunity of the signaling IEC 62236-4 (2018)
and telecommunications apparatus

6.7.1.2 Emission

XMC25 R2 or XMC25 or XMC23 or XMC22

Conducted emission 0.15 MHz … 30 MHz EN 55032, class A
Radiated emission 30 MHz … 6000 MHz EN 55032, class A

6.7.1.3 Immunity

XMC25 R2 or XMC25 or XMC23 or XMC22

Electromagnetic field 80 MHz … 1000 MHz, 20 V/m
(IEC/EN 61000-4-3) 1 GHz … 6 GHz, 10 V/m
Conducted common mode HF disturbance 150 kHz … 80 MHz,
(IEC/EN 61000-4-6) modulated 1 kHz 80% AM, 10 V
Fast transients/bursts
(IEC/EN 61000-4-4)
- on power supply IF (CDN) 2 kV
- on traffic signal interfaces (capacitive clamp) 1 kV
Surge immunity ITU-T K.20 and ITU-T K.45
(IEC/EN 61000-4-5)
- Traffic and control interfaces common mode: 2 kV 1.2/50 µs (8/20 µs)
differential mode: 1 kV 1.2/50 µs (8/20 µs)

Copyright 2022 Hitachi Energy. All rights reserved. 205

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- Power supply interface common mode: 1 kV 1.2/50 µs (8/20 µs)
differential mode: 0.5 kV 1.2/50 µs (8/20 µs)

6.7.2 ESD

XMC25 R2 or XMC25 or XMC23 or XMC22

Electrostatic Discharge (IEC/EN 61000-4-2) contact discharge: 8 kV
air discharge: 15 kV

6.7.3 Safety

XMC25 R2 or XMC25 or XMC23 or XMC22

Safety according to IEC 62368-1:2014
Audio/video, information and communication tech-
nology equipment - Part 1: Safety requirements
Railway applications EN 50124-1 (2001) +A1 +A2
Insulation coordination - Part 1: Basic require-
ments - Clearances and creepage distances for all
electrical and electronic equipment

6.7.4 Earthing

XMC25 R2 or XMC25 or XMC23 or XMC22

Earthing and bonding for XMC20 ETSI EN 300 253 V2.2.1 (2015-06),
designed for integration acc. to the configuration
shown in figure 2 of this EN.

6.8 Environmental Conditions and Dependability

6.8.1 Ambient Conditions

6.8.1.1 Storage

XMC25 R2 or XMC25 or XMC23 or XMC22

Environmental class
- All equipment (exclusive batteries) ETSI EN 300 019-1-1, class 1.2
Temperature range -25°C … +65°C
Humidity class 1.2
Biological and chemical active substances not specified

6.8.1.2 Transport

XMC25 R2 or XMC25 or XMC23 or XMC22

Environmental class ETSI EN 300 019-1-2, class 2.2
- All equipment (exclusive batteries)
Temperature ranges
- ambient air for unventilated enclosures -25°C … +70°C

Copyright 2022 Hitachi Energy. All rights reserved. 206

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

- ambient air for ventilated enclosures or outdoor
-25°C … +40°C
Humidity class 2.2
Vibration random Acceleration Spectral Density
- ASD @ 10-200 Hz
1.0 m2s-3
- ASD @ 200-2000 Hz 0.3 m2s-3
Biological and chemical active substances not specified

6.8.1.3 Operation

XMC25 R2 or XMC25 or XMC23 or XMC22

Environmental class
- All equipment (exclusive batteries) ETSI EN 300 019-1-3, class 3.3
Temperature range (extended), with active cooling
- Operation of XMC20, altitude up to 2000 m
- Operation of XMC20, altitude up to 5000 m -25°C … +65°C 1
-25°C … +50°C
Temperature range, with passive cooling 2
- Operation of XMC20, altitude up to 2000 m -25°C … +55°C
- Operation of XMC20, altitude up to 5000 m -25°C … +45°C
- Minimum start up temperature -25°C
Humidity 0% … 95%, non-condensing
Mechanical conditions
- Subrack, core unit, service units ETSI EN 300 019-1-8, class Special (3M5)
Biological and chemical active substances not specified
Explosive atmosphere not allowed

1. Operation above 60°C requires optimization of the air flow around units that are equipped with SFPs.
Please refer to [1KHW029121] Application Note “Extended Temperature Range Operation”.
2. Passive cooling operation of the XMC23 and XMC22 subrack requires vertical mounting of the subrack.

6.8.2 Dependability

XMC25 R2 or XMC25 or XMC23 or XMC22

Calculated MTTF at 35 °C (MIL-HDBK-217F)
- XMC25 R2 subrack 86 years
- XMC25 subrack 100 years
Calculated MTTF at 35 °C (MIL-HDBK-217F)
- XMC23 subrack 206 years
Calculated MTTF at 35 °C (MIL-HDBK-217F)
- XMC22 subrack 491 years
Calculated MTTF at 35 °C (MIL-HDBK-217F)
Plug in units > 50 years per unit (typical)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.4.4 COOL4 Fan Unit (R2)
Fan unit COOL4 (on page 177)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.4.5 ALMU4-F Alarm Unit
Alarm unit ALMU4-F (R1) (on page 179)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.5.4 COOL6 Fan Unit (R2)
Fan unit COOL6 (on page 187) and section 6.5.5 COOL6 Fan Unit
(R3) (on page 189)

Copyright 2022 Hitachi Energy. All rights reserved. 207

XMC20 | SYSTEM DESCRIPTION SPECIFICATIONS

XMC25 R2 or XMC25 or XMC23 or XMC22

Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.5.6 ALMU6-F Alarm Unit
Alarm unit ALMU6-F (R1) (on page 191)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.6.4 COOL8 Fan Unit (R1)
Fan unit COOL8 (on page 198) and section 6.6.5 COOL8 Fan Unit
(R2) (on page 200)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.6.6 ALMU8-F Alarm Unit
Alarm unit ALMU8-F (R1) (on page 202)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.4.6 DUA25 Dual Power
Dual supply input unit DUA25 Supply Input Unit (on page 181)
(XMC25 R2 and XMC25)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.5.7 DUA23 Dual Power
Dual supply input unit DUA23 Supply Input Unit (on page 193)
(XMC23 and XMC22)
Calculated MTTF at 35 °C (MIL-HDBK-217F) please refer to section 6.6.8.5 Dependability (on
AC/DC converter POAC1 page 204)

Copyright 2022 Hitachi Energy. All rights reserved. 208

XMC20 | SYSTEM DESCRIPTION ANNEX

7 Annex

7.1 Associated XMC20 Documents

[1KHW028868] Release Note “XMC20 System Release R16A”

[1KHW028873] User Manual “Management Communication”

[1KHW028875] User Manual “Ethernet Switching”

[1KHW028883] User Manual “SATP8”

[1KHW028879] User Manual “VOIP1”

[1KHW028866] Product Description “Feature Licenses for XMC20”

[1KHW029121] Application Note “Extended Temperature Range Operation”

7.2 Feature Licenses

Part of the XMC20 functionality is subject to feature licenses. For more information on feature
licenses please refer to [1KHW028866] Product Description “Feature Licenses for XMC20”.

Copyright 2022 Hitachi Energy. All rights reserved. 209

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: 1KHW028870

Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.