—

USER MANUAL

FOX61x
Release Notes R2D

SELI8 User Manual

Document ID 1KHW028633

Document revision FOX61x System Release: R2D

Edition: 1
Date: 2017-08-17

Copyright and confidentiality Copyright in this document vests in ABB Switzerland Ltd (hereinafter referred to
as ABB).
Manuals and software are protected by copyright. All rights reserved. The copy-
ing, reproduction, translation, conversion into any electronic medium or
machine scannable form is not permitted, either in whole or in part. The con-
tents of the manual may not be disclosed by the recipient to any third party,
without the prior written agreement of ABB.
An exception is the preparation of a backup copy of the software for your own
use. For devices with embedded software, the end-user license agreement on
the enclosed CD applies.
This document may not be used for any purposes except those specifically
authorized by contract or otherwise in writing by ABB.

Disclaimer ABB has taken reasonable care in compiling this document, however ABB
accepts no liability whatsoever for any error or omission in the information con-
tained herein and gives no other warranty or undertaking as to its accuracy.
ABB can accept no responsibility for damages, resulting from the use of the net-
work components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
ABB reserves the right to amend this document at any time without prior notice.
The product/software/firmware or the resulting overall solution are designed
for data processing and data transmission and may therefore be connected to
communication networks. It is your sole responsibility to provide and continu-
ously ensure a secure connection between the product/software/firmware or
the resulting overall solution and your network or any other networks (as the
case may be). You shall establish and maintain any appropriate measures (such
as but not limited to the installation of firewalls, application of authentication
measures, encryption of data, installation of anti-virus programs, etc.) to pro-
tect the product/software/firmware or the resulting overall solution, the net-
work, its system and all the interfaces against any kind of security breaches,
unauthorized access, interference, intrusion, leakage and/or theft of data or
information. ABB and its affiliates are not liable for damages and/or losses
related to such security breaches, any unauthorized access, interference, intru-
sion, leakage and/or theft of data or information.
Although ABB provides functionality testing on the products including related
firmware and software that we release, you should institute your own testing
program for any product updates or other major system updates (to include but
not limited to firmware/software changes, configuration file changes, third
party software updates or patches, hardware exchanges, etc.) to ensure that
the security measures that you have implemented have not been compromised
and system functionality in your environment is as expected.

Copyright © 2018 ABB 2

FOX61x | RELEASE NOTES R2D

Contents

1 Introduction and Overview 4

2 Release Contents 8
2.1 Overview 8
2.2 New Release Contents 8
2.3 Contents of Previous Releases 10
2.4 Fixed Bugs 11
2.5 Feature Licences 13
2.6 FOX61x Subrack and Infrastructure 14
2.6.1 Overview 14
2.6.2 FOX615 Subrack and Infrastructure 14
2.6.3 FOX612 Subrack and Infrastructure 15
2.7 Units 15
2.7.1 Overview 15
2.7.2 Control Units 17
2.7.3 Service Units 18
2.7.4 Embedded Software 21
2.8 Management Software 21
2.8.1 Overview 21
2.8.2 FOXCST 22
2.8.3 FOXMAN-UN 23
2.9 Compatibility and Upgrades 23
2.9.1 System Compatibilities 23
2.9.2 Profile Versions 23
2.9.3 Upgrades 25
2.10 Technical Product Documentation 25
2.10.1 Overview 25
2.10.2 FOX61x and FOXCST Technical Product Documentation 26
2.10.3 Associated Technical Product Documentation 28

3 Limitations 29
3.1 Overview 29
3.2 Current Limitations for the FOX61x System 30
3.3 Management Software 35
3.3.1 FOXCST 35

29 January 2018 3
FOX61x | RELEASE NOTES R2D

1 Introduction and Overview

This release note describes the system release R2D contents of ABB’s FOX61x. The release note specifies the features, functions, and compo-
nents of the release and describes identified limitations of features and functions which apply for the present release.
The release note has parts with contents as follows: Introduction and Overview
• Introduction and Overview describes the subject of the release note and provides a short overview of the structure
and the contents of the release note.
• Release Contents describes the contents of the FOX61x R2D release. The description includes hardware components,
management and embedded software as well as product documentation. The content description specifies also
associated products as far as relevant for the consistency of the FOX61x release.
• Limitations describes known limitations of functions and features.
Please note that detailed feature descriptions of the FOX61x R2D release and specifications of the FOX61x R2D components are not included
in this release note but are provided in 1KHW002460 FOX61x Product Features and Characteristics.

Please note:
The manual 1KHW002460 FOX61x Product Features and Characteristics may describe features that have not yet been released,
but are planned as a late deliverable or as part of a maintenance release of the current system release.
If you need additional information, please contact your ABB sales representative.
The abbreviations used in this release note are explained in Table 1: “Abbreviations”.

Table 1: Abbreviations
Abbreviation Plain text Description (optional)
AC Accessory Extension of the short name describing the category of the short named item.
ECLI Embedded Command Line Interface Embedded management interface using command lines for managing nodes.
ED Extended Depth Extended depth front cover is required for operation of units with electrical or optical Ethernet ports.
EQP Equipment Protection Feature that allows a HW redundancy by using two units of the same type.
ERPS Ethernet Ring Protection Switching
ESW Embedded Software Application software which is downloaded to and runs on FOX61x control units or service units. The
software files have the extension “.esw”.
EXP MPLS Experimental Bits
ETSI European Telecommunications
Standards Institute

29 January 2018 4
FOX61x | RELEASE NOTES R2D

Table 1: Abbreviations (continued)

Abbreviation Plain text Description (optional)
FOX Fiber Optic Multiplexer Name for the FOX61x product family. Includes the FOX61x network element types FOX615 and FOX612
with new functionality compared to previous release of the FOX61x product family.
FOX61x Name for the FOX61x product family. Includes the FOX61x network element types FOX615 andFOX612
with new functionality compared to previous release of the FOX61x product family.
FOXCLI FOX Command Line Interface Embedded management interface using command lines for managing nodes.
GUI Graphical User Interface
HW Hardware In the Limitations tables the items “embedded software” (ESW) and “hardware” (HW) are quoted in
[HW] the same column. For the clear distinction from ESW the hardware is quoted in brackets [HW].
n.a. not applicable
NE Network Element Generic term for managed elements in a network.
OS Operating System Operating system (and version) required to run the specified application software. The application
software is released for the specified OS(s) only.
PCP Priority Code Point
PTP Precision Time Protocol
PWAC Pseudo Wire Attachment Circuits
Ref. Reference Normally a reference to a FOX61x system release.
Rel. Release Release (version)
SE Set Extension of the short name describing the category of the short named item.
SIM Simulator Simulator files used for FOXCST offline configuration of FOX61x control units or service units. The
simulator files have the extension “.sim”.
SR System Release Used in tables for the specification of FOX61x system releases.
[SR] In the Limitations tables the items “FOXCST” and “system release” (SR) are quoted in the same col-
umn. For the clear distinction from FOXCST the system release is quoted in square brackets [SR].
SU Service Unit Category of FOX61x units which provide traffic services.
SW Software
Ver. Version Mainly used to describe the version of hardware components.
VPLS Virtual Private LAN Service
VPWS Virtual Private Wire Service

29 January 2018 5
FOX61x | RELEASE NOTES R2D

The syntax used in this release note for NEs, unit hardware, ESW, and unit functions is as follows:
• The expression “FOX61x” may be used to indicate that the feature or function given is applicable to FOX615 and
FOX612.
• The name of a unit is given by an acronym of either
− 4 upper case characters and a digit (e.g. CESM1, LEDS1, etc.), or
− one of the above acronyms complemented with “-F” to indicate that the unit is based on a special HW variant for
fanless operation (e.g. CESM1-F, ETOP1-F, SAMO2-F).
In this release note, placeholder characters may be used in the name if appropriate; they are delimited with <> brack-
ets.
Example:
− CESM<x> where <x> may stand for “0”, “1”, i.e. CESM0, CESM1.
An optional “RnX” without brackets after the acronym of the unit describes the version of the unit hardware. The unit hardware version is
given if the specification of the version has a relevance. The character “R” stands for “Release”. Example: “CESM1 R1A”.

Please note:
The unit ESW (function) is specified in lower case characters after the unit name and the optional hardware version.
Example: “LEDS1 R1A leds1_r2f”, or “LEDS1 leds1_r2f” are read as follows:
• LEDS1: unit name
• R1A: version of the LEDS1 unit hardware (this is optional; the hardware version is provided if relevant)
• leds1_r2f: unit ESW including released version of the ESW (in this example “r2f” is the basic ESW version; the character “r”
stands for “release”)
• leds1_r2f03: the unit ESW usually provides a version identifier that exceeds 3 alphanumerics, also see the note below.

Please note:
The above shown syntax corresponds closely to the information presented in the GUI of the management tool FOXCST. In the NE’s
tree structure the FOXCST GUI shows the ESW in brackets () with indication of the release test version appended to the basic ESW
version. The ESW versions given in the present release note usually include this level of detail. Therefore the ESW Name & Version
column in Table 6: “Control Units Hardware and Software” and Table 7: “Service Units Hardware and Software R1D” includes the
full ESW version ID.
→ Example for the LEDS1 unit: the FOXCST GUI tree view shows “LEDS1 R1A (leds1_r2f03)”, where “leds1_r2f” indicates the
released basic ESW version while the supplement “03” indicates the software version passing the release test.

29 January 2018 6
FOX61x | RELEASE NOTES R2D

Please note:
Hotfix ESW is numbered as shown above, but with an extension appended to the release test version, e.g. “leds1_r1a19_01”, where
“_01” indicates the hotfix version passing the release test. The ESW versions given in the present release note may not include this
level of detail.

29 January 2018 7
FOX61x | RELEASE NOTES R2D

2 Release Contents

2.1 Overview
The tables in section 2 Release Contents specify the components of the FOX61x R2D system release in terms of compatible hardware and soft-
ware including the related technical product documentation.
The FOX61x R2D system release has components as follows:
• Feature licences, see Table 3: “Feature Licences for FOX61x”;
• FOX61x subracks and infrastructure, see Table 4: “FOX615 Subrack and Infrastructure” and Table 5: “FOX612 Subrack
and Infrastructure”;
• Pluggable units, see Table 6: “Control Units Hardware and Software” and Table 7: “Service Units Hardware and
Software R1D”;
• Embedded software carriers, see Table 8: “Embedded software for NEs, core units, and service units”;
• Management software, see Table 9: “FOXCST Management Software”;
• Profile versions, see Table 10: “Profile Versions and CPS Versions per Unit and ESW”;
• Technical product documentation, see Table 11: “FOX61x and FOXCST technical product documentation”.
The manual FOX61x Product Features and Characteristics (1KHW002460) provides a detailed specification and description of the FOX61x R2D
functionality, including the functionality that has been added or changed with the current system release.
The FOX61x R2D system release as specified in this section has been fully tested and functionally verified. Known limitations of the FOX61x
R2D system release are specified in Limitations, or in each of the ESW Release Notes published together with new ESW.
For an overview of commercial function packages and ordering please contact your ABB sales representative.
For an overview on feature licensing, refer to section 2.5 Feature Licences.

Please note:
When operating a FOX612 or FOX612 subrack without fan unit vertical mounting is mandatory.

2.2 New Release Contents

The FOX61x R2D system release includes functionality and pluggable units that target the Mission Critical Systems (MCS) markets. It enhances
the feature set of the previous FOX61x system release.
The following new features or functions have been added, or changes have been made since the previous FOX61x system release or since the
previous issue of this release note:

29 January 2018 8
FOX61x | RELEASE NOTES R2D

• Enhanced Quality of Service, based on Traffic Engineering. The QoS implementation has been completely reworked,
affecting the switching and MPLS-TP applications.
• Rate limiters improved, provide now also “1 rate - 3 color” and “2 rate - 3 color” modes.
• Handling of Drop Precedence added for green and yellow packets.
• Traffic classification can be done VLAN based (EVC), with priority overwrite.
• VLAN based sub-interfaces on the core unit CESM1/CESM1-F, to be used as MPLS-TP interfaces.
• Support of dual homed customer networks (ABB specific implementation).
• New router unit EROP1 providing four virtual router instances, up to 256 virtual router interfaces, and 12 SFP-based
Ethernet front ports (100 Mbit/s or 1000 Mbit/s). The unit is also available as a 2-slot wide unit EROP1-F for fanless
operation.
• The SW firewall on the FOX61x nodes has been reworked; the packet rate limiter has been improved.
• New and improved data collector for collection of troubleshooting data in case of a node error. The data collector is
now integrated in FOXCST and can be started from the FOXCST menu.
• A new version of the local craft terminal FOXCST (R2E), with a further improved GUI, enhancing usability and working
efficiency. FOXCST now also supports:
− Indication of MPLS-TP nodes that are managed by FOXMAN-UN.
− Improved GUI presentation of Performance Monitoring (PM) data.
• Integration of the SENC1 unit for end-to-end encryption of MPLS-TP traffic (currently for FOA only).
• Integrations of the SAMO5 unit as a SAMO1 replacement for SDH networks.

Please note:
The previously released version of FOXCST (R2D) is not fully compatible with the ESWs released with the present system release,
mainly due to the changes in the QoS implementation. We therefore strongly recommend to only use the latest FOXCST version
(R2E) for management of the FOX61x nodes.

Please note:
Some switching protocols as main feature are not supported in this release. This statement is in particular related to the features
MSTP and ERPS. Therefore customer VLAN ports (CVP) do not provide configuration of these protocols.
→ Use the FOXCST GUI “Basic Settings” for setting up a management connection. This allows the creation of an Ethernet access
port. If you want to make use of an inband management access via an Ethernet trunk port use the “Switching” tab in the
FOXCST GUI exclusively to set that port to “Trunk” mode.
→ If you require VLAN switching with MSTP and/or ERPS as main features for your applications please use the software (ESW)
versions as released with the FOX61x R1D system release.

29 January 2018 9
FOX61x | RELEASE NOTES R2D

2.3 Contents of Previous Releases

The following features or functions had been added previously as part of the R2A, R2B, or R2C system releases or described in a previous issue
of this release note.

Please note:
A part of the features of the R1 system releases are not supported in the FOX61x R2 system releases. This specifically applies to
ERPS and MSTP (also see the notes in section 2.2 New Release Contents).
• MPLS-TP functionality has been extended. Note that a feature license is required for MPLS-TP operation, see section
2.5 Feature Licences.
In addition to the Virtual Private Wire Service (VPWS) and the Virtual Private LAN Service (VPLS) the MPLS-TP feature
now also includes:
− Support of VLAN-based VPWS configuration on CVP ports, allowing VPWS and VPLS on the same port.
− Support of E-Tree (H-VPLS).
− Extended MPLS-TP OAM features: BFD, Linear Protection, Delay Measurements.
− Improved inter-operability with third-party MPLS-TP devices.
• Enhanced (reduced) switch-over time for core unit equipment protection.
• Enhanced (reduced) delay variation for EoS traffic.
• Support of R-L2GP (bridge port mode configuration).
• Support of user specific default values in FOXCST or FOXMAN-UN for MPLS configuration parameters.
• Configurable mapping of attachment circuits PCP to pseudo wire EXP.
• Support of PTP (IEEE 1588v2) Grand Master Clock mode.
• Support of new Sa bit mode on the units SAMO2, SAMO2-F, SAMO3, LEDE1, and SAMO1.
• COSI1 increased number of bearer channels from 912 to 1216.
• Additional traffic type “Known Unicast” in Broadcast Storm Control configuration (available with FOXCST R2D /
FOXMAN-UN R10C only).
• A new version of the local craft terminal FOXCST (R2D), with a further improved GUI, enhancing usability and working
efficiency. FOXCST now also supports
− user settable default values for MPLS configuration parameters,
− modification of existing TDM cross connections.
Note that the FOXCST installation has been separated into two parts:
− the FOXCST for online management of FOX61x nodes, and
− the offline installation of a virtual machine (MSimVM) based on Oracle VM VirtualBox.
The VirtualBox version required is at least v4.x (recommended v5.x).

29 January 2018 10
FOX61x | RELEASE NOTES R2D

• MPLS-TP functionality has been added to the core unit CESM1 / CESM1-F (feature license required for MPLS-TP oper-
ation, see section 2.5 Feature Licences). The MPLS-TP feature includes:
− Virtual Private LAN Service (VPLS);
− Virtual Private Wire Service (VPWS);
− PE Router and P Router functionality;
− point to point unidirectional and bidirectional (plus co-routed) LSPs;
− structure agnostic TDM over Packet (E1 over MPLS);
− the service units ETOP1 / ETOP1-F, ELET1, and EPOI1 providing pseudo wire attachment circuits (PWAC).
• Support of MPLS OAM: LSP Ping and Trace Route on MPLS-TP ports.
• Configurable mapping of attachment circuits PCP to pseudo wire EXP.
• Support of Precision Time Protocol PTP (IEEE 1588v2), including Grand Master Clock mode.
• Rate limiters on Ethernet ports.
• Support of SNMP v1, v2, and v3 for fault management.
• A software firewall that protects the core unit CPU from packets that may be a security threat.
• Support of the 4-slot subrack type FOX612 (see section 2.6 Units).
• A new version of the local craft terminal FOXCST (R2B), with a further improved GUI, enhancing usability and working
efficiency.
• Integration of packet teleprotection units OPIC2, TEGO1 and TEPI2.

Please note:
The units without specific HW variant for fanless operation can also be operated in a subrack with passive cooling, except SAMO3
which requires forced ventilation. The FOX61x system description provides more information on environmental conditions for dif-
ferent types of operation.

2.4 Fixed Bugs

The following table provides information on bugs on system level that have been fixed since the last release of the product. For bug fixes on
unit level please refer to the ESW release notes for the respective unit.

Table 2: System Level Bugs Fixed since Last Release

Type Description Reference ID
Fixed bugs: OSPF Summarization does not work. 34257
Management VLAN over VPLS is not working. 35826

29 January 2018 11
FOX61x | RELEASE NOTES R2D

Table 2: System Level Bugs Fixed since Last Release (continued)

Type Description Reference ID
Stop In Boot procedure is not working for upgrading service units from 35855
R2A to R2B, if CESM1 is already running with R2B ESW.
Traffic Class is not set properly when the QoS mode of a VPLS PW is con- 38466
figured as “Specified Value”.
Non-Urgent alarm output of fan unit does not work. 38620
CSR17520
Advertisement for 120 or more intra area routes fails. 38630
Datacollector may not work properly. 38653
MCC interfaces not becoming operational after configuration. 38720
PTP packets are mapped to egress queue 7. 38768
NE SW: Management of ICN HDLC Unit heavily disturbed if ESW upload 39442
takes place. CSR18160
Alarms present on unavailable APs or when unit removed. 39507
CSR18161

29 January 2018 12
FOX61x | RELEASE NOTES R2D

2.5 Feature Licences

The FOX61x features listed in Table 3: “Feature Licences for FOX61x” below are licensed and available separately.

Please note:
The right to use the licensed features is given per NE (network element or subrack), or per card (pluggable unit), depending on the
feature licence. Where a licence is given per NE, it is applicable per FOX615, FOX612 or FOX612 subrack. Where a licence is given per
card, it is applicable per hardware unit or service unit named in the short name or in the description of the licence.
Where feature licences are applicable per card, and where redundancy (EQP) is used two licences need to be purchased (one per
card).

Table 3: Feature Licences for FOX61x

Licence ID Short name Description Right to use
MPLS Lic CESMx MPLS-TP Feature Licence for Multi-Protocol Label Switching (MPLS). per subrack
ERPS Lic CESMx ERPS Feature Licence for Ethernet Ring Protection Switching for CESMx per node
E1-EQP Lic SAMO3 E1Prot Feature Licence for E1 port protection of SAMO3. per subrack
Sync-E Lic CESMx SyncE Feature Licence for Synchronous Ethernet functionality for CESM1 or CESM1-F. per card
PTP Lic CESMx PTP Feature Licence for Precision Time Protocol for CESM1 or CESM1-F per card
10GE Lic CESMx 10 GbE Feature Licence for 10GbE for CESMx and SENC1) per card
LCR Lic COSI1 LCR Feature Licence for Local Call Routing for COSI1 per card
DSL-Trunk Lic DATI1 DSL trunk Feature Licence for DSL trunks, DATI1 to DATI1 interconnection. per card
L3-ROUTE Lic EPSI1 L3 Routing Feature Licence for OSPF Routing functionality with EPSI1. per card
8P12 Lic SAMO1 additional 8x P12 Feature Licence for additional 8x P12 accessing the SDH in SAMO1 per card
STM16 Lic SAMO2/3 STM16 Feature Licence for STM-16 operation of SAMO2, SAMO2-F or SAMO3 per card

29 January 2018 13
FOX61x | RELEASE NOTES R2D

2.6 FOX61x Subrack and Infrastructure

2.6.1 Overview
The tables below describe the FOX61x subracks and the related infrastructure required for the installation and operation of the FOX61x net-
work elements. Some of the infrastructure is optional (applicability depends on the requirements of the FOX61x installation).
The FOX61x components and related infrastructure released for the FOX61x R2D system are described in terms of
• FOX61x subracks and front covers,
• Fan and alarm units,
• Dual powering (option),
• Heat directing shields (options),
• Adapters for ETSI installation practice (options),
• Installation kit(s) (options).
Supplementary and third party equipment (e.g. splitters etc.) operating with the FOX61x but not directly bound to the present system release
may be available. This type of equipment and cables are not described in the tables below.
For information on such equipment and cables please contact your ABB sales representative.
Please note that ABB approved cables are required. ABB 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 ABB. For details on cables please refer
1KHW002498 FOX61x Electrical Cables provided with the FOX61x documentation.

2.6.2 FOX615 Subrack and Infrastructure

Table 4: FOX615 Subrack and Infrastructure

Function Unit HW FOX61x Description / Remarks
Name Ver. Short text Symbol Available NE type

FOX615 R3 FOX615 subrack config. FOX615 standard FOX615 FOX615 subrack with ED cover, 19" / 8 HU, 21 slots, 10GbE and GbE double star, TDM
bus, including cable tray and power cable.
FAMO1-IM R2 FAMO1 fan 48VDC 19" 1U FAMO1 standard FOX615 Heat management, 48VDC fan unit for FOX615, 19" / 1 HU including power/signal cable.
12 alarm inputs, 2 alarm outputs. Consumable.
DUPF2-IM R1 DUPF2 dual power input DUPF2 standard FOX615 Dual power input for FOX615 - DUPF2 (for installation in the FOX615 subrack).
FAMO1-F R1 FAMO1-F alarm unit fanless FAMO1-F standard FOX615 Alarm unit for fanless FOX615 subrack, 1 HU, 12 alarm inputs and 2 alarm outputs.

29 January 2018 14
FOX61x | RELEASE NOTES R2D

2.6.3 FOX612 Subrack and Infrastructure

Table 5: FOX612 Subrack and Infrastructure

Function Unit HW FOX61x Description / Remarks
Name Ver. Short text Symbol Available NE type

FOX612 R1 FOX612 subrack config. FOX612 standard FOX612 FOX612 subrack with ED cover. 19" / 4 HU, 8 slots, 10GbE and GbE double star, TDM
bus.
FAMO2-IM R3 FAMO2 R3 fan 48VDC FAMO2 standard FOX612 Heat management, 48VDC fan unit for FOX612. 12 alarm inputs and 2 alarm outputs.
Consumable.
DUPF1-IM R1 DUPF1 dual power input DUPF1 standard FOX612 Dual power input for FOX612 - DUPF1.
FAMO2-F R1 FAMO2-F Alarm unit fanless FAMO2-F standard FOX612 Alarm unit for fanless FOX612 subrack, 1 HU, 12 alarm inputs and 2 alarm outputs.

2.7 Units

2.7.1 Overview
The tables in Control Units and in Service Units describe the pluggable units for the FOX615, the FOX612, or the FOX612 subracks in terms of
compatible unit hardware and software available for the functionality of the FOX61x R2D system release. The FOX61x R2D system release sup-
ports types of pluggable units as follows:
• Control units, see Table 6: “Control Units Hardware and Software”
• Service units, see Table 7: “Service Units Hardware and Software R1D”
The units are compatible with the FOX61x network elements indicated in the “FOX61x NE Type” column. The release reference in the “System
Release” column gives the system release (including service pack, if applicable) with which the specified function (essentially determined by
the ESW type and version) has been introduced.

Please note:
The FOX61x R2D System Description may include a description of features or units that are not part of the current release, but will
be available after the initial FOX61x R2D release. This applies specifically to the SENC1 unit.

Please note:
The following units without specific HW variant for fanless operation can also be operated in a subrack with passive cooling (also
see section 2.7 "Units"):
• EPSI1,

29 January 2018 15
FOX61x | RELEASE NOTES R2D

• ELET1 (HW version R2A or later required),

• CEPI1,
• DATI1,
• LEDE1,
• SAMO1 (HW version R2A or later required),
• EPOI1,
• LESU1,
• LEDS1,
• LEDA1,
• LECO1,
• LEXI1,
• TEPIx,
• OPICx,
• COSI1 R1D or more recent HW versions.
The following units must not be operated in a subrack with passive cooling:
• CESM1 (use CESM1-F for operation in a subrack with passive cooling),
• ETOP1 (use ETOP1-F for operation in a subrack with passive cooling),
• SAMO2 (use SAMO2-F for operation in a subrack with passive cooling),
• SENC1 (use SENC1-F for operation in a subrack with passive cooling),
• DEFM1 (use DEFM1-F for operation in a subrack with passive cooling),
• EROP1 (use EROP1-F for operation in a subrack with passive cooling),
• COSI1 HW versions up to R1C (use COSI1 R1D or later for operation in a subrack with passive cooling).
The FOX61x system description provides more information on environmental conditions for different types of operation.
The tables below show the current status of HW and ESW at the time of publication of the present Release Note.

Please note:
For details on the features and functions provided with the units in the current system release please refer to the section “Specifi-
cation” in the user manual of the respective unit, or to 1KHW002460 FOX61x Product Features and Characteristics.
The regular embedded software and - if applicable - additional hotfix software are available for download in ABB’s Extranet. As an option the
embedded software for each of the units is also available as a collection on a CD-ROM/DVD (refer to section 2.7.4 Embedded Software).
ABB strongly recommends to check the Extranet periodically for up-to-date hotfixes. A hotfix ESW is a regular ESW that is functionally identi-
cal to released ESW but provides one or several bug fixes.

29 January 2018 16
FOX61x | RELEASE NOTES R2D

2.7.2 Control Units

Table 6: Control Units Hardware and Software

Function Unit HW ESW Name & Sys- FOX61x Remarks / Description
Name Rel. Short text Symbol Version Version tem NE Type
Release
CESM1-IM r2d CESM1 2xSFP+/10GbE CESM1 R1D cesun_r2d13 (R2D) FOX615, Central card (core unit) with 2 x SFP+ and 3 x RJ-45 GbE front connec-
3xRJ45 R2A..R2C cesne_r2d14 FOX612 tors, RJ-45 management interface. SFP+ front connectors usable for
10GbE (by using SFP+) and for 1GbE (by using SFP). 10GbE backplane
connection to redundant CESM1, 1GbE backplane connections
towards Service Units. Usable in FOX615/FOX612/FOX612. Redun-
dancy not supported in FOX612.
CESM1 2xSFP+/10GbE CESM1-F R1D FOX615, Central card (core unit) with 2 x SFP+ and 3 x RJ-45 GbE front connec-
3xRJ45, R2A..R2C FOX6121) tors, same as CESM1, but for fanless operation. Requires 2 slots in the
Passive Cooling subrack. Redundancy not supported in FOX612.
CESM2-IM r2d CESM2 2xSFP+/10GbE CESM2 R2A..R2B cesun_r2d13 (R1D) FOX615, Central card (core unit) with 2 x SFP+ and 3 x RJ-45 GbE front connec-
1xRJ45+2xSFP/1GbE cesne_r2d14 FOX612 tors, RJ-45 management interface. SFP+ front connectors usable for
10GbE (by using SFP+) and for 1GbE (by using SFP). 10GbE backplane
connection to redundant CESM1, 1GbE backplane connections
towards Service Units. Usable in FOX615/FOX612.
CESM2 2xSFP+/10GbE CESM2-F R2A..R2B Central card (core unit) with 2 x SFP+ and 3 x RJ-45 GbE front connec-
1xRJ45+2xSFP/1GbE tors, same as CESM1, but for fanless operation. Requires 2 slots in the
subrack.
1) When operated in a FOX612 subrack vertical mounting is mandatory.

In the table above, releases specified in brackets () in the “System Release” column refer to the FOX61x system release. The current system
release is “R2D”.

Please note:
When operating core units with redundant HW, make sure to use two core units with identical HW states. Using different HW
states for the core units running in slot 11 and slot 13 of a FOX615 or FOX612 subrack may have a negative impact on system stabil-
ity and on upgrade procedures.
Further notes:
• ABB provides cables for the interfaces of the CESM1. For information of cables and cable lengths available, please
contact your sales representative.
• Please note that ABB approved cables are required. ABB 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 ABB.

29 January 2018 17
FOX61x | RELEASE NOTES R2D

• A list with approved SFP modules for operation with the FOX61x systems and units are published in ABB’s Extranet.

2.7.3 Service Units

Table 7: Service Units Hardware and Software R1D

Function Unit HW ESW Name & Version System FOX61x Description / Remarks
Name Rel. Short text Symbol Version Release NE Type

CEPI1-IM r4a CEPI1 CESoPacket GW + 8 E1 CEPI1 R2A..R2B cepi1_r4a19 (R1D) FOX615, Service unit for circuit emulation (CESoP) with gate-
FOX612 way between TDM bus and Ethernet star. 8x E1 ports.
Capacity 8x 2 Mbit/s.
COSI1-IM r2d COSI1 VoIP SMG 912ch COSI1 R1C..R1D cosi1_r2d05 (R2D) FOX615, VoIP high density Subscriber Media Gateway Unit, SIP
FOX612 protocol, 1216 subscriber channels. Up to two feature
licences required. Operation with forced ventilation
mandatory.
EPOI1-IM r2d SUP12 ELE ETH POE 12xGbE EPOI1 R1A..R1C epoi1_r2d13 (R2D) FOX615, Power over Ethernet Switching unit, 12x 10/100/
FOX612 1000BaseT Ethernet Ports. All ports can be configured
with PoE.
EPSI1-IM r2c EPSI1 Ethernet Aggreg. unit EPSI1 R1A..R1G epsi1_r2c02_06 (R1C) FOX615, 4 x 10/100BaseT Ethernet aggregation unit for TDM
FOX612 management channel.
ELET1-IM r2d ELET1 ELE ETH 24xGbE ELET1 R2A..R2B elet1_r2d13 (R2D) FOX615, Ethernet Switching unit with 24x 10/100/1000BaseT
FOX612 Ethernet Ports. Requires 2 slots in the subrack. Also
supports fanless operation.
EROP1-IM r1a EROP1 Router Unit EROP1 R1A erop1_r1a16 (R2D) FOX615, Router unit with four virtual router instances, up to 256
FOX612 virtual router interfaces, and 12 SFP-based Ethernet
front ports (100 Mbit/s or 1000 Mbit/s).
EROP1 Router Unit, Passive EROP1-F R1A FOX615, Router unit with four virtual router instances, up to 256
Cooling FOX6121) virtual router interfaces, and 12 SFP-based Ethernet
front ports (100 Mbit/s or 1000 Mbit/s). Requires 2
slots in the subrack. For fanless operation.
ETOP1-IM r2d ETOP1 OPT / EL. ETH 12xGbE ETOP1 R2A..R2B etop1_r2d13 (R2D) FOX615, Ethernet Switching unit with 12x 100 Mbit/s and/or
FOX612 1000 Mbit/s via Optical/Electrical SFPs.
ETOP1-F OPT / EL. ETH 12xGbE, ETOP1-F R1B..R1C FOX615, Ethernet Switching unit with 12x 100 Mbit/s and/or
Passive Cooling FOX6121) 1000 Mbit/s via Optical/Electrical SFPs. Requires 2
slots in the subrack. For fanless operation.
DATI1-IM r5d DATI1 SHDSL TDM 8-port DATI1 R1A..R1D dati1_r5d02_04 (R1C) FOX615, SHDSL TDM unit, 2-wire and 4-wire mode, with 8x
FOX612 G.SHDSL ports, for connection to DTM-M.

29 January 2018 18
FOX61x | RELEASE NOTES R2D

Table 7: Service Units Hardware and Software (continued)R1D

Function Unit HW ESW Name & Version System FOX61x Description / Remarks
Name Rel. Short text Symbol Version Release NE Type

LECO1-IM r1d LECO1 TDM G.703 IF 8-port LECO1 R1C..R1D leco11_r1d03 (R1D) FOX615, TDM unit, G.703, 64 kbit/s co-directional interface, 8
FOX612 ports,
120 Ohms, 1:1 protection.
r1a LECO1 TDM G.703 IF 2-port con- leca1_r1a02_03 TDM unit, G.703, 64 kbit/s contra-directional interface,
tra-dir 2 ports, 120 Ohms, 1:1 protection.
LEDA1-IM r2d LEDA1 2/4W E&M VF 8-port LEDA1 R1D leda1_r2d02 (R1D) FOX615, E&M voice interface unit 2/4-wire, 1:1 protection, voice
FOX612 conference, 8 ports.
LEDE1-IM r5b LEDE1 E1 TDM unit 8-ports LEDE1 R1A..R1D lede1_r5b03_03 (R1D) FOX615, E1 interface unit with 8x E1 ports acc. to ITU-T G.703/
FOX612 G.704.
LEDS1-IM r2f LEDS1 4x Data IF 1x ETH LEDS1 R1E..R1F leds1_r2f03 (R1D) FOX615, TDM unit with 4x multi-protocol serial interfaces: X.24/
FOX612 V.11; V.24/V.28; V.35; RS485 - configurable, point-to-
point and (multi-)point-to-multipoint operation, one
10/100Base-T Ethernet interface.
LESU1-IM r2c LESU1 POTS 16-port LESU1 R1D..R1E lesu1_r2c03 (R1D) FOX615, POTS interface unit with 16x subscriber line interfaces
FOX612 (no splitters).
LEXI1-IM r2c LEXI1 EXCH IF a/b 12-port LEXI1 R1D..R1E lexi1_r2c03 (R1D) FOX615, POTS Foreign Exchange Office (FXO) interface unit 12-
FOX612 ports, 2-wire analogue.
OPIC1-IM r1d OPIC1 OPT PROT IF OPIC1 R1A opic1_r1d02_01 (R2D) FOX615, FOX61x optical protection interface unit, 4 ports.
FOX612
OPIC2-IM r1c OPIC2 OPT PROT IF OPIC2 R1A opic2_r1c02_02 (R2D) FOX615, FOX61x optical protection interface unit, 4 ports +
FOX612 IRIG-B.
SAMO5-IM r1a SAMO5 SDH STM-4/1 EoS SAMO5 R1A samo2_r3e02 (R2D) FOX615, SDH line unit with STM-4/STM-1 and EoS, 4 x SFP
FOX612 based SDH STM-4/STM-1 ports, 4 x electrical Ethernet
ports (100/1000BaseT).
SAMO5 SDH STM-4/1 EoS, SAMO5-F R1A FOX615, SDH line unit with STM-4/STM-1 and EoS, 2 x SFP
Passive Cooling FOX6121) based SDH STM-4/STM-1 ports, 4 x electrical Ethernet
ports (100/1000BaseT). Requires 2 slots in the sub-
rack. For fanless operation.
SAMO2-IM r3d SAMO2 SDH STM-1/4/16 EoS SAMO2 R1D..R1G samo2_r3e02 (R2D) FOX615, SDH line unit with STM-16/4/1 interfaces, supporting
FOX612 EoS, 4 x electrical Ethernet ports (100/1000BaseT).
Feature license for STM-16 operation required.
SAMO2 SDH STM-1/4/16 EoS, SAMO2-F R1D..R1G FOX615, SDH line unit with STM-16/4/1 interfaces, supporting
Passive Cooling FOX6121) EoS, 4 x electrical Ethernet ports (100/1000BaseT).
Requires 2 slots in the subrack. For fanless operation.
Feature license for STM-16 operation required.

29 January 2018 19
FOX61x | RELEASE NOTES R2D

Table 7: Service Units Hardware and Software (continued)R1D

Function Unit HW ESW Name & Version System FOX61x Description / Remarks
Name Rel. Short text Symbol Version Release NE Type

SAMO3-IM r3d SAMO3 SDH STM1/4/16 EoS E1 SAMO3 R1A..R1E samo2_r3e02 (R2D) FOX615, SDH line unit with STM-16*/STM-4/STM-1, EoS and E1-
FOX612 front ports, physical E1 front port protection (feature
license required). 2-slot width mechanics. Operation
with forced ventilation mandatory.
Feature license for STM-16 operation required.
SENC1-IM r1b SENC1 4xSFP+/10GbE-1Gbps SENC1 R1B senc1_Release.swu, (R2D) FOX615, Encryption Unit for MPLS-TP, two separate function
senc1_1g_encryp- FOX612 blocks with 4 SFP-based traffic ports each, for connec-
tor.swu, tion to the core unit front ports and to the remote site,
senc1_10g_encryp- hardware-based quantum random number generator
tor.swu (QRNG).
TEPI1-IM r2b TEPI1 Teleprot IF TEPI1 R1A..R1D tepi1_r2b02 (R2D) FOX615, FOX61x teleprotection unit, 4 commands, 6 relays, 16
FOX612 binary inputs, 8 binary outputs.
TEPI2-IM r1b TEPI2 Teleprot IF TEPI2 R1A tepi2_r3b03_02 (R2D) FOX615, FOX61x teleprotection unit, 4 commands, 6 relays, 12
FOX612 binary inputs, 12 binary outputs, 1 IRIG-B.
TEGO1-IM r1a TEGO1 GOOSE IF TEGO1 R1A tego1_r1a11 (R2D) FOX615, GOOSE unit, 4 SFP ports, IRIG-B.
FOX612
1) When operated in a FOX612 or FOX612 subrack vertical mounting is mandatory.
In the tables above, the releases specified in brackets () in the “System Release” column refer to the FOX61x system release in which the ESW
has been first released. The current system release is “R2D”.
HW versions identified with R1x or similar designate R1A, R1B, R1C, etc., as applicable. This applies correspondingly for all other HW versions
R2x, R3x, etc.
The sub column “Rel.” of “Function” in the above tables refers to the function release which is directly determined by the ESW version. For that
reason the function release is identical to the version of the ESW.

Please note:
ABB provides cables for all interfaces of the service units. For information on cables and cable lengths available, please contact
your sales representative.
ABB approved cables are required. ABB 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 ABB.

29 January 2018 20
FOX61x | RELEASE NOTES R2D

2.7.4 Embedded Software

Embedded software (consisting of ESW files and SIM files) is provided for download in ABB’s Extranet. Optionally a disc (CD-ROM or DVD) can
be requested as shown in the table below.

Table 8: Embedded software for NEs, core units, and service units
Function ESW FOX61x Description / Remarks
Name Rel. Short Text Version Name NE Type

SW-CD R2D ABB SW CD 2… January 2018 FOX615, Disc with the embedded software (ESW) for the FOX61x units and NEs released with the FOX61x
FOX612 system R2D.

Please note:
A set of ESW files (used for installation on units) and SIM files (used for offline configuration) is also included in the extended
installation package for the local manager “FOXCST” (see Table 9: “FOXCST Management Software”).

2.8 Management Software

2.8.1 Overview
The table below describes the FOXCST management software for the FOX61x network elements. The FOX61x R2D system release has manage-
ment software with GUIs as follows:
• FOXCST network element manager (local craft terminal),
• FOXMAN-UN network manager.
The FOXMAN-UN network manager supports the management of the network elements of ABB’s main access & transport network system
families.

29 January 2018 21
FOX61x | RELEASE NOTES R2D

2.8.2 FOXCST

Table 9: FOXCST Management Software

ABB Standard Package Supported Description / Remarks
Name Operating System SW Name FOX61x NE
Types
SW CD Windows 10, foxcst_r2e12... FOX615, The FOXCST R2E (full encryption support) software can be requested via techni-
Windows 8.1 Professional (64 bit), FOX612 cal support. Optionally FOXCST R2E is also available as disc package (ABB ver-
Windows 7 Ult/Pro/Ent (64 bit). sion).
The disc package contains:
- FOXCST R2E installer for windows (exe),
- MSim Virtual Environment installer for Windows (exe) for FOXCST R2E offline
use (requires Oracle VM VirtualBox),
- FOXCST R2E Release Notes.

Please note:
FOXCST R2E may also run on other Windows versions than the ones indicated in Table 9: “FOXCST Management Software”, e.g.
Windows 8.1 (32 bit), Windows 7 Ult/Pro/Ent (32 bit), Windows Server 2003, Windows Server 2008 R2 (64 bit), Windows Server 2012
Standard. However some restrictions may apply with these versions.

Please note:
Minimum PC HW requirements that must be met for operation of the FOXCST R2E management software:
- Dual core CPU with 3 GHz clock, 64 bit architecture;
- CPU supporting virtualization (VT-x / AMD-V);
- Virtualization must be activated in the BIOS;
- 2 GB RAM;
- 2 GB of free disk space for installation of FOXCST and unit software files;
- 10 Mbit/s Ethernet LAN port.

Please note:
Recommended PC HW requirements for operation of the FOXCST R2E management software:
- Intel i5 CPU (or similar), 64 bit architecture;
- CPU supporting virtualization (VT-x / AMD-V);
- Virtualization must be activated in the BIOS;
- 4 GB RAM;
- 4 GB of free disk space for installation of FOXCST and unit software files;
- 100 Mbit/s Ethernet LAN port.

29 January 2018 22
FOX61x | RELEASE NOTES R2D

Please note:
The FOXCST R2E management software is backward compatible and also supports the FOX61x network elements of the R1D, R1C,
and R1A system releases.

2.8.3 FOXMAN-UN
The FOXMAN-UN is comprehensive management software managing network elements and networks. The FOXMAN-UN has a modular archi-
tecture which allows distributed and scalable installations. Operation control and NE access have multi-session capabilities, while the FOX-
MAN-UN core manages one central database and all the north bound interfaces.
The FOXMAN-UN network element manager runs on workstations or servers with Linux (Red Hat Enterprise) operating systems. Versions and
requirements are specified in the applicable FOXMAN-UN release note.
The FOXMAN-UN R10C SP01 includes the FOXCST R2E management software and supports the FOX61x NEs and functions of the FOX61x R2D
system release. However, FOXCST must be activated in FOXMAN-UN prior to be used.
The documentation for the FOXMAN-UN R10C SP01 software (and following versions if available) can be downloaded from the ABB Extranet
once it has been released. The FOXMAN-UN R10C SP01 software please contact your local ABB sales representative.

2.9 Compatibility and Upgrades

2.9.1 System Compatibilities

The FOX61x R2D system release provides cross connections on 64 kbit/s, n x 64 kbit/s, and E1 level. This feature and related functions are only
available for the TDM based units listed in Service Units. No other units than the ones listed in Service Units Hardware and Software R1D are
compatible with this feature. It is not allowed to operate other than the above specified units in the subrack or run these units with ESW ver-
sions other than specified in Table 7: “Service Units Hardware and Software R1D”.

2.9.2 Profile Versions

The ESW released for some of the units listed in Table 6: “Control Units Hardware and Software” and Table 7: “Service Units Hardware and
Software R1D” uses specific versions of profiles for the purpose of pre-configuring a specific set of parameters on the respective units. Please
refer to the table below for a list of profile versions per unit and ESW valid for the current system release.

29 January 2018 23
FOX61x | RELEASE NOTES R2D

Table 10: Profile Versions and CPS Versions per Unit and ESW
Unit Name ESW Name and Version Profiles or CPS, Version ID Comments
CEPI1 cepi1_r4a19 None. Unit without individual profiles
CESMx, cesne_r2d14 None. Unit without individual profiles.
CESMx-F cesun_r2d13
COSI1 cosi1_r2d05 CustomParameterSet: Unit with custom parameter set.
COSI_ABB_R5A032
COSI_ABB_LCR_R5A092
DATI1 dati1_r5d02_04 None. Unit without individual profiles.
EPOI1 epoi1_r2d13 None. Unit without individual profiles.
EPSI1 epsi1_r2c02_06 None. Unit without individual profiles.
ELET1 elet1_r2d13 None. Unit without individual profiles.
EROP1, erop1_r1a16 None. Unit without individual profiles.
EROP1-F
ETOP1, etop1_r2d13 None. Unit without individual profiles.
ETOP1-F
LECO1 leco11_r1d03 None. Unit without individual profiles.
leca1_r1a02_03
LEDE1 lede1_r5b03_03 None. Unit without individual profiles.
LEDS1 leds1_r2f03 None. Unit without individual profiles.
LEDA1 leda1_r2d02 None. Unit without individual profiles.
LESU1 lesu1_r2c03 None. Unit without individual profiles.
LEXI1 lexi1_r2c03 None. Unit without individual profiles.
OPIC1 opic1_r1d02_01 None. Unit without individual profiles.
OPIC2 opic2_r1c02_02 None. Unit without individual profiles.
SAMO2, samo2_r3e02 None. Unit without individual profiles.
SAMO2-F
SAMO3 samo2_r3e02 None. Unit without individual profiles.
SAMO5, samo2_r3e02 None. Unit without individual profiles.
SAMO5-F
SENC1 (None) None. Unit without individual profiles.
TEGO1 tego1_r1a11 None. Unit without individual profiles.

29 January 2018 24
FOX61x | RELEASE NOTES R2D

Table 10: Profile Versions and CPS Versions per Unit and ESW (continued)
Unit Name ESW Name and Version Profiles or CPS, Version ID Comments
TEPI1 tepi1_r2b02 None. Unit without individual profiles.
TEPI2 tepi2_r1b03_02 None. Unit without individual profiles.

Profiles or CPS other than those listed in Table 10: “Profile Versions and CPS Versions per Unit and ESW” are incompatible with the current sys-
tem release and must not be used together with the units and ESW shown in Table 10: “Profile Versions and CPS Versions per Unit and ESW”.
Compatible default profiles are automatically loaded in the FOXCST and available in the “CPS & Profile Tool” when the respective ESW is
imported.

2.9.3 Upgrades

Please note:
Hotfixes may be available from ABB for the ESW of any FOX61x unit. Please check the ABB Extranet for ESW hotfixes.

Please note:
An upgrade from node configurations created with FOX61x R1D release contents to the current FOX61x R2D system release is sup-
ported. The migration from a R1D based node configuration to a R2D node configuration is however subject to a specific proce-
dure. This is due to the different feature sets of the involved system releases; the FOX61x R2D system release does not support
ERPS, which was supported in FOX61x R1D. Details are described in an Engineering Bulletin (EB).

Risk of operating trouble!

Before starting any upgrade procedures make sure that you do neither have an equipment failure in your FOX61x, nor that you
have irregular HW, and/or ESW from an irregular FOX61x system release installed on any of the units. Any deviation from this rule
may severely impact the upgrade procedure and may lead to a non-working system after the upgrade attempt.
If you have questions regarding the upgrade, please contact ABB technical support.

2.10 Technical Product Documentation

2.10.1 Overview
The tables below describe the technical product documentation related to the FOX61x R2D system release. The product documentation is sep-
arated in two groups:

29 January 2018 25
FOX61x | RELEASE NOTES R2D

• FOX61x and FOXCST technical product documentation

• Associated technical product documentation
The tables for “associated technical product documentation” show product documentation which is related to equipment and management
software that is (optionally) available to operate and manage the FOX61x in a network environment.

2.10.2 FOX61x and FOXCST Technical Product Documentation

The technical documentation for the current release can be accessed on the ABB Extranet. Optionally it is also available on a disc (DVD or CD-
ROM). The documentation for the present FOX61x system release R2D includes the following documents:

Table 11: FOX61x and FOXCST technical product documentation

Item Name ABB Number Document Name ESW ref. System FOX61x Remarks
Release NE type
FOX61x Customer 1KHW002492 -- -- (R2D) Disc with compilation of the FOX61x technical product
Documentation disc documentation as follows:
1KHW002460 FOX61x Product Features and Characteristics -- (R2D) 61x Provides an overview of the FOX61x systems and their
functions.
1KHW028633 FOX61x Release Notes R2 -- (R2D) 61x Includes a description of known limitations of the FOX-
61x R2D system release and the related functions. This
part of the release note is updated as required.
1KHW002465 FOXCST Installation -- (R2D) 61x Provides information for installation of FOXCST and
connection to a FOX61x network element.
1KHW002466 FOXCST Operation -- (R2D) 61x Provides information for the operation of the local man-
agement tool FOXCST for FOX61x systems.
1KHW002462 FOX612 Installation -- (R2D) 612 The FOX612 installation guide does not depend on a
specific system release.
1KHW002461 FOX615 Installation -- (R2D) 615 The FOX615 installation guide does not depend on a
specific system release.
1KHW002464 FOX61x System Description -- (R2D) 61x Provides information which is specific for the operation
of the FOX612 and the FOX615.
1KHW002467 FOX61x TDM Services -- (R2D) 61x Provides detailed information required for the proper
commissioning of units supporting TDM services in the
FOX61x.
1KHW002468 FOX61x Ethernet Services -- (R2D) 61x Provides information required for the setup and opera-
tion of the Ethernet switch functions in the FOX61x.
1KHW028618 FOX61x MPLS-TP -- (R2C) 61x Provides information on MPLS-TP based services

29 January 2018 26
FOX61x | RELEASE NOTES R2D

Table 11: FOX61x and FOXCST technical product documentation (continued)

Item Name ABB Number Document Name ESW ref. System FOX61x Remarks
Release NE type
1KHW028522 FOX61x Management Communication -- (R2D) 61x Provides information on the management communica-
tions functionality in the FOX61x.
1KHW002498 FOX61x Electrical Cables -- (R2D) 61x Provides detailed specifications of the electrical cables
for FOX61x.
1KHW002469 FOX61x CESM1, CESM1-F cesun_r2d (R2D) 61x
cesne_r2d
1KHW002469 FOX61x CEPI1 cepi1_r4a (R2C) 61x
1KHW028559 FOX61x COSI1 cosi1_r2c (R2D) 61x
1KHW002474 FOX61x DATI1 dati1_r5d (R2D) 61x
1KHW002472 FOX61x ELET1 elet1_r2c (R2D) 61x
1KHW028550 FOX61x EPOI1 epoi1_r2d (R2D) 61x
1KHW002475 FOX61x EPSI1 epsi1_r2c (R2D) 61x
1KHW028911 FOX61x EROP1, EROP1-F erop1_r1a16 (R2D) 61x
1KHW002471 FOX61x ETOP1, ETOP1-F etop1_r2c (R2D) 61x
1KHW002473 FOX61x LEDE1 lede1_r5b (R2D) 61x
1KHW002481 FOX61x LECO1, LECA1 leco11_r1d, (R2D) 61x
leca1_r1a
1KHW002479 FOX61x LEDA1 leda1_r2d (R2D) 61x
1KHW002478 FOX61x LEDS1 leds1_r2f (R2D) 61x
1KHW002470 FOX61x LESU1 lesu1_r2c (R2D) 61x
1KHW002480 FOX61x LEXI1 lexi1_r2c (R2D) 61x
1KHW002484 FOX61x OPIC1 opic1_r1c (R2D) 61x
1KHW028635 FOX61x OPIC2 opic2_r1c (R2D) 61x
1KHW028684 FOX61x TEGO1 tego_r1a (R2C) 61x
1KHW002483 FOX61x TEPI1 tepi1_r2b (R2D) 61x
1KHW028634 FOX61x TEPI2 tepi2_r1b (R2D) 61x
1KHW002476 FOX61x SAMO1 samo1_r3f (R2D) 61x
1KHW028668 FOX61x SAMO2, SAMO3, SAMO5 samo2_r2c (R2C) 61x

Releases specified in brackets () refer to the FOX61x system release in which the document has been last published or reworked.

29 January 2018 27
FOX61x | RELEASE NOTES R2D

2.10.3 Associated Technical Product Documentation

Please note:
The FOXMAN-UN product documentation is available for download on ABB’s Extranet. If you have questions regarding the
FOXMAN-UN software or documentation, please contact your ABB sales representative.

Please note:
The documentation for FOXMAN-UN R10C SP01 may not yet be available at the time of publication of the present release note.

29 January 2018 28
FOX61x | RELEASE NOTES R2D

3 Limitations

3.1 Overview
This section describes known HW related limitations of the FOX61x R2D system release and SW related deviations from specified system
behaviour of the FOX61x R2D system functions. In this document both types are handled under the term “limitations”. Software limitations
that are relevant to the functional units of the FOX61x R2D system release are listed in the ESW release notes (see note below).
The chapter Limitations lists both cleared limitations (see Table 12: “Cleared Limitations for the FOX61x System”) and current limitations (see
Table 13: “Current Limitations for the FOX61x System”) for the release contents described in this Release Note.
A limitation can have temporary or permanent significance:
• Temporary
Limitations are temporary if it is possible to fix them. Typically this type of limitation is due to deficiencies of the
system implementation.
For temporary limitations, a fix is foreseen to clear the limitation. Depending on the impact of the deficiency and its
fix, it is not always possible to precisely schedule such a release.
• Permanent
Limitations are permanent (“Permanent”) if it is not (reasonably) possible to fix them. Typically this type of limitation
is inherent to the system implementation or given by the chip sets used.
If available, ABB provides a workaround to eliminate or reduce the impact of a limitation.
The abbreviations used in the tables of the present Release Note are explained in Table 1: “Abbreviations”.

Please note:
Limitations that are related to the ESW of pluggable units are not listed in this section, but are published in the “ESW Release
Note” attached to the ESW/SIM files for each of the units.
You can get the ESW release note’s PDF file from the unit’s ESW zip file that is published on the ABB Extranet, or optionally from
the ESW CD-ROM/DVD.
Limitations that have been cleared since the previous system release are listed in Table 12: “Cleared Limitations for the FOX61x System” below.

Table 12: Cleared Limitations for the FOX61x System

System Function Area First Found in Limitation Description Id
or Unit (SR) ESW [HW]
NE OSPF routing (R2C) -- OSPF Summarization does not work. Fixed with (R2D). 34257

29 January 2018 29
FOX61x | RELEASE NOTES R2D

Table 12: Cleared Limitations for the FOX61x System (continued)

System Function Area First Found in Limitation Description Id
or Unit (SR) ESW [HW]
NE Management (R2B) -- Management VLAN must not use VPLS. Fixed with (R2D). 35826
38607
NE System (R2B) -- “Stop In Boot” procedure is not working for upgrading service units Fixed with (R2D). 35855
from R2A to R2B if CESM1 is already running with R2B ESW.
NE MPLS-TP / VPLS (R2C) -- Traffic Class not set properly when the QoS mode of a VPLS PW is con- Fixed with (R2D). 38466
figured as “Specified Value”.
NE OSPF routing (R2C) -- Advertisement for 120 or more intra area routes fails. Fixed with (R2D). 38630
NE Datacollector (R2C) -- Datacollector may not work properly. Fixed with (R2D). 38653
NE MPLS-TP MCC (R2C) -- MCC interfaces not becoming operational after configuration. Fixed with (R2D). 38720
NE PTP (R2C) -- PTP packets are mapped to egress queue 7. Fixed with (R2D). 38768

In the above table release indications in round brackets, e.g. (R2C) indicate the respective FOX61x system release (SR).

3.2 Current Limitations for the FOX61x System

Limitations listed in Table 13: “Current Limitations for the FOX61x System” are FOX61x system level limitations, or unit related limitations that
affect the inter-operation between different units for the current release.

Table 13: Current Limitations for the FOX61x System

System Function Area First Found in Limitation Description Workaround Id
or Unit (SR) ESW [HW]
NE SAMO2-F (R1C) [R1A, R1B] Operation temperature range of When one or several SAMO2-F units are operated in a sub- Use active air flow with fans (install a --
FOX61x in fanless operation with rack without fan unit, the environmental temperature for fan unit in the subrack), or use HW R1C
SAMO2-F limited to -25° C .. +50° the subrack must not rise above +50° C. This is applicable or later.
C. only to the HW versions R1A and R1B. From HW version R1C
onwards the temperature range is -25° C .. +55° C.
NE Security (R1C) -- ARP requests flooding vulnera- CESM1 may reboot in some ARP request flood scenarios. None. 32064
bility.
NE Security (R1C) -- SSH host key fingerprint not SSH host key fingerprint reading is missing. None. 34623
readable.

29 January 2018 30
FOX61x | RELEASE NOTES R2D

Table 13: Current Limitations for the FOX61x System (continued)

System Function Area First Found in Limitation Description Workaround Id
or Unit (SR) ESW [HW]
NE System (R1C) -- No indication provided in Reconfiguration of FOX61x may take up to 2 minutes for a During the reconfiguration time there is 27545
FOXCST when configuration of large configuration. During this time there is no indication no indication in FOXCST of progress or 28970
FOX61x is completed. in FOXCST of progress or completion of the reconfigura- completion of the reconfiguration. In
tion. order to avoid Ethernet traffic loops,
perform the following sequence:
- Enable RSTP on the Ethernet port,
apply config and wait 2 minutes;
- Set Ethernet port to admin state “up”.
NE System (R1C) -- Slot 13 may not be used for chas- The use of slot 13 is restricted to Use slot 1-10, 12, 14-21 for all other ser- 28102
sis switch based service units. - a redundant core unit (CESM1), or vice units.
- a TDM based service unit (DATI1, LEDE1, LESU1, LEDS1,
LEDA1, LECO1, LEXI1).
NE EQP (R1C) -- EQP: working unit becomes not The issue has been observed with the following procedure: - Plug a protecting unit; 30496
always active if protecting unit - working unit up and running (active), protecting unit not - Make sure the unit has completely
is missing. available; booted before removing the other
- insert protecting unit; unit in the EQP group.
- remove working unit (some seconds later);
- protecting unit goes to standby and stays standby at
least for 2 minutes;
- insert working unit;
- remove protecting unit (some seconds later) ;
- working unit goes to standby and stays standby.
NE Ethernet (R1C) -- Ethernet flow control is not sup- When autonegotiation is enabled flow control is not sup- None. 28116
Switching ported. ported. Manual mode for flow control is implemented but
has not been fully verified.
NE Ethernet (R1C) -- Port mirroring: Destination port An access or trunk port configured as mirroring destina- Configure the mirroring destination 28239
Switching doesn’t block bridging traffic tion port will also transmit bridging traffic of the VLAN(s) it port as follows:
and protocol traffic. is a member of (and BPDUs if STP is enabled). - Port Mode “General”, without VLAN
membership,
- STP disabled.
NE Ethernet (R1C) -- Ethernet Rx counters not count- The Ethernet Received Statistic counters count not only Rx None. 30705
Switching ing correctly. frames but also Tx frames.
NE MPLS-TP (R2A) -- Mirroring doesn't work properly Mirroring of egress traffic only possible if mirror port is on None. 32408
if mirror port is on the same unit different unit from traffic port. Mirroring of ingress traffic
as the mirrored traffic. works.
NE MPLS-TP (R2D) -- Transit XC of single label traffic The S-bit of the outer label is always set to zero in a transit None, this is a BobCat1 chip hardware 33302
corrupts S-bit. node, even in case of single label packets. limitation.

29 January 2018 31
FOX61x | RELEASE NOTES R2D

Table 13: Current Limitations for the FOX61x System (continued)

System Function Area First Found in Limitation Description Workaround Id
or Unit (SR) ESW [HW]
NE MPLS-TP (R2A) -- Source MAC address of the The MAC address of the backplane port is used instead of None. 33970
MPLS packet sent out from the the MAC address of the MPLS interface. This is a hardware
LER is not correct. limitation of the switch device.
NE MPLS-TP/MCC (R2A) -- Static routes using MCC. Static routes using next hop address as Gateway (con- Configure MCC interface as numbered 34320
nected network on MCC-interface) are successfully work- interface with a '/30' network, Enable
ing only if OSPF is enabled on this MCC-interface, i.e. OSPF on this interface, configure static
neighbour detected via OSPF. routes using the OSPF neighbour as
gateway.
NE MPLS-TP/MCC (R2A) -- “NE Basic Settings / Manage- Using “NE Basic Settings / Management Interfaces” the Do not use “NE Basic Settings / Man- 34466
ment Interfaces”: the PVID will PVID will not be configured on selected port and may over- agement Interfaces”.
not be configured on selected write settings done earlier on this specific port.
port.
NE MPLS-TP/LPS (R2B) A protected tunnel may come up Behaviour is according to RFC6378: If protection LSP is up None. 34752
on the protecting path after cre- before working LSP, WTR is started and traffic switched to
ation or CESM1 switch-over. protection LSP.
NE Ethernet (R2B) -- Storm Control feature is not Storm Control feature is not supported on bridge ports Configure a rate limiter on a CVP port 35854
Switching supported on bridge ports that (CVP) that are part of a VPLS (i.e. member of an SVI VLAN). which is prone to broadcast storms.
are part of a VPLS.
NE System (R2B) -- Configuration problem after In a chassis with a stand-alone Ethernet unit (e.g. SAMO1) After “Initialize” restart the stand-by 36131
“Initialize” when stand-alone and a redundant CESM1 (stand-by), new configuration (via CESM1 in slot 13.
Ethernet unit and redundant restore or FOXCST) after “Initialize” is not correctly applied
CESM1 are in the chassis. to the NE and a CCE alarm is raised.
NE MPLS-TP (R2B) -- No MPLS traffic after a specific After the following re-configuration scenario, configura- Before deleting the tunnel (step 4) wait 36491
re-configuration scenario. tion in the NE is incomplete and no MPLS traffic is trans- until FOXCST synchronization with NE
mitted: is completed (i.e. no activity in FOXCST
1. Create a VPLS configuration and save it “Communication State” bar).
2. Delete the VPLS pseudowires via FOXCST
3. Perform “Load”
4. Delete tunnel while FOXCST synchronization is still ongo-
ing (“Communication State” active).
NE MPLS-TP/LPS (R2B) -- A protected tunnel may come up Behaviour is according to RFC6378: If protection LSP is up None. 37009
on the protecting path after cre- before working LSP, WTR is started and traffic switched to
ation or CESM1 switch-over. protection LSP.
NE MPLS-TP / VPLS (R2B) -- If VLAN ingress filtering is disa- Ingress VLAN filtering is normally enabled on bridge ports Always use ingress VLAN filtering. 36032
bled it can result in duplicated and checks the ingress port is a VLAN member.
frames in VPLS VLANs. However in the General port mode it can be disabled; if this
is done then for VPLS VLANs it can result in duplicated
frames sent to local bridge ports.

29 January 2018 32
FOX61x | RELEASE NOTES R2D

Table 13: Current Limitations for the FOX61x System (continued)

System Function Area First Found in Limitation Description Workaround Id
or Unit (SR) ESW [HW]
NE MPLS-TP / VPLS (R2B) -- Too many VPLS VLAN bridge A combination of too many VPLS VLANs and bridge ports Check the limit if using more than 16 36389
port members may overload the that are members of them can overload the active core unit VPLS instances: 16 VPLS x 30 bridge
switch if using more than 16 switch. ports = 480 members.
VPLS instances. The total number of bridge port members of VPLS VLANs
must not exceed 500.This limit is not validated by the man-
agement system or the node.
NE OSPF routing R1B r1c FOXCST GUI regarding OSPF See limitation. Note that the routing table under ‘router’ None. 28714
limited to 512 entries, except might have more than 512 table entries but only 512 will be 29505
Link State which is limited to shown on FOXCST. Note that the FOXCST fails to read out
4096, and External Link State more than 2500 table entries.
2048 entries.
NE OSPF routing -- r1c Incomplete propagation of host Host routes to connected PPP peers are learned by IP via None. 28949
routes. PPP-daemon, but not propagated to OSPF module, there-
fore not shown in the router status view.
NE OSPF routing -- r1d FOXCST routing table shows FOXCST routing table '/managementNetwork/router, Sta- None. 29302
several entries for the same des- tus, Routing' shows several entries for the same destina-
tination network, even though tion network, even though only one route is actually
only one route is actually applied.
applied.
NE OSPF routing -- r1d OSPF router will not detect loss Connectivity loss is not detected as the vlanInterface is a None. 29520
of connectivity to the subnet C-VLAN bridged port and not a router port. The respective
connected via vlanInterface. subnet will therefore still be advertised via OSPF, even if
the access to the subnet is lost.
NE OSPF routing -- r1d OSPF interworking issue FOX- Interoperability with FOX51x using “static host If” is not None. 29530
61x - FOX51x. always working.
NE Security -- r2b No routing prevention between Routing is not prevented between the local management None. 37580
local mgmt port and OSPF net- port and the OSPF network. the OSPF network can there-
work. fore be pinged even if the firewall is enabled.
NE OSPF routing -- r1h OSPF is not working if IPSec is See description. None. 37873
used on the corresponding
router interface.
NE VRRP -- r1h Incorrect VLAN priority of VRRP VRRP packets are sent out with priority 0 regardless of the None. 38299
packets. configuration value “Management VLAN CoS”.
NE OSPF routing (R2C) -- Numbered interfaces are listed Numbered interfaces are listed twice in routing table with None. 38647
twice in routing table. a correct (as a connected interface) and an incorrect entry
(as an interface at a neighbour node that is reachable in a
single hop via an unnumbered interface).

29 January 2018 33
FOX61x | RELEASE NOTES R2D

Table 13: Current Limitations for the FOX61x System (continued)

System Function Area First Found in Limitation Description Workaround Id
or Unit (SR) ESW [HW]
NE Mirroring (R2C) -- Port mirroring not working When mirroring tagged traffic from an service unit to None. 38203
properly at higher rates. another service unit, only a part of the packets is for-
warded to the mirror port at line rates above 50%.
NE MPLS-TP / (R2C) -- VPWS on a Q-in-Q CVP port does When Q-in-Q is used the ingress tag on the frame is None. 38286
VPWS not work. ignored and the port PVID is used.
NE MPLS-TP OAM (R2C) -- MTU size in Echo Reply from MTU size in Echo Reply from transit node is fixed set to None. 38457
transit node has fixed size. 1586 bytes.
NE MPLS-TP (R2D) -- PW counters in RX direction is In case of VPLS as well as VPWS when VLAN tag is added, None. 39258
overcounting by 4 octets/pack- and depending on location of interfaces in the chassis, PW
ets in specific configuration. counters in RX direction may show values that are 4
octets/packets too high.
NE MPLS-TP VLAN (R2D) -- On the MPLS-TP sub-interface of On the MPLS-TP sub-interface of the LER, the PCP value of At the VPN provider port, traffic classifi- 39388
sub-interface the LER, the PCP value of the the transport VLAN is always 0 for pseudowires in mode cation shall be based on VLAN ID, not on
transport VLAN is wrong. 'Ethernet Tagged' and Port Priority in mode “Ethernet”. the received PCP value.
NE PTP (R2C) -- “Clock Domain” w/o effect. PTP frames are considered, regardless if “clock domain” Do not use “Clock Domain” parameter. 38600
value corresponds to the setting on the NE.
NE Ethernet Port (R2C) -- PTP may fail if PHY is set to If port is set to fixed 100BaseTX FD and admin state After restart/power cycle, system 38648
100BaseTX FD. “down” on power on, and then change to admin state “up”, works as expected.
PTP may fail. Use “auto” for speed and duplex.
CESM1 Time (R1C) r1c Time source updates offset Time accuracy may exceed the specified accuracy. None. 27216
accuracy deviation. 28091
NE SNMP (R2D) -- SNMP Target MIB entries over- See Limitation. None. 39279
written by restore operation.
NE Delay Measure- (R2D) -- Configuring more than four LSPs Limitation only exists with MPLS over VLAN sub-interfaces. Make sure to not configure time stamp- 39534
ment for time stamping on same CCE was seen with 8 LSPs. ing for more than 4 LSPs on a port.
physical port may lead to CCE.

In the above table release indications in round brackets, e.g. (R2D) indicate the respective FOX61x system release (SR).

29 January 2018 34
FOX61x | RELEASE NOTES R2D

3.3 Management Software

3.3.1 FOXCST
Any known limitations valid for the FOXCST are listed in the FOXCST Release Notes that are published together with the FOXCST installer (for
information on FOXCST management software see section 2.8.2 FOXCST).

29 January 2018 35
_
ABB Switzerland Ltd
Power Grids
Bruggerstrasse 72
CH-5400 Baden

Phone: +41 844 845 845

(Customer Contact Center)
E-mail: [email protected]

www.abb.com/communicationnetworks

Document ID: 1KHW028633

© Copyright 2018 ABB. All rights reserved.

Specifications subject to change without notice.