FOX61x SystemDescription 1KHW002464

ABB Power Systems
FOX61x
System Description
User Manual
User Manual FOX61x
System Description
Release History: Release 1: May 2012
Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

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 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 authorised 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 contained 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 network
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.
Blank pages: Any blank page present is to accommodate double-sided printing.
Document No.: 1KHW002464
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © May 2012 by ABB Switzerland Ltd
Table of Contents
1 Preface 7
1.1 Precautions and safety 7
1.2 Symbols and notations 7
1.3 Interfaces and circuit categories 7
1.4 Document history 8
1.5 Definition of terms 8
1.6 Feature licences 10
2 Overview 11
2.1 Network element view 11
2.2 Network element description 13
2.3 Control functions 16
3 Installation 17
3.1 FOX61x subrack 17
3.2 FOX units for passive cooling operation 17
4 Functional description 19
4.1 Management connection 19
4.2 Date and time management 21
4.3 Redundant Core Unit CESM1 (future release) 22
4.4 Fan unit - FAMO1 (FOX615), option 23
4.5 Alarm unit - FAMO1-F (FOX615), optional 27
4.6 Fan unit - FAMO2 (FOX612), optional 29
4.7 Redundant power supply - DUPF1 (FOX615), optional 33
4.8 Redundant power supply - DUPF2 (FOX612), optional 35
5 Commissioning and operation 37

5.1 Optical alarm indications 37
5.2 Fan unit operation 39
5.3 Packet services 43
5.4 TDM services 43
6 Maintenance 45
6.1 Overview 45
6.2 Handling of units 45
6.3 ESW upgrade 46
System Description ManualUser Guide 3

7 FOXCST reference 47
7.1 Introduction 47
7.2 AP: / ne 49
7.3 AP: / fan 67
7.4 AP: / fan / alarm-a 69
7.5 AP: / bridging tbd 70
7.6 AP: / managementNetwork 70
7.7 AP: /unit-x 70
8 Annex 71
8.1 Associated FOX documents 71
4 System Description ManualUser Guide

Figures
Figure 1: FOX615 view without front cover 11

Figure 2: FOX615 view with front cover mounted 12
Figure 3: FOX612 view without front cover 12
Figure 4: FOX612 view with front cover mounted 13
Figure 5: FOX61x with CU and SU 15
Figure 6: FOX61x, tree view in FOXCST tbd 22
Figure 7: FAMO1 unit 23
Figure 8: FAMO1 block diagram 24
Figure 9: FAMO1 front panel with alarm input interfaces 25
Figure 10: FAMO1 front panel with alarm output interfaces 26
Figure 11: FAMO1 front panel with interface towards the FOX615 subrack 26
Figure 12: FAMO1 front panel with LED status indicators 27
Figure 13: FAMO1-F unit tbd 27
Figure 14: FAMO1-F block diagram 28
Figure 15: FAMO1-F front panel with LED status indicator 29
Figure 16: FAMO2 R2 unit 30
Figure 17: FAMO2 R2 block diagram 30
Figure 18: FAMO2 front panel with alarm input interfaces 32
Figure 19: FAMO2 front panel with LED status indicators 32
Figure 20: DUPF1 block diagram 33
Figure 21: DUPF1 unit including the power and alarm cables 33
Figure 22: DUPF1 contact output versus input voltage 34
Figure 23: DUPF2 block diagram 35
Figure 24: DUPF2 unit including the alarm cable 35
Figure 25: DUPF2 contact output versus input voltage 36
Figure 26: Control unit LEDs and service unit LEDs 37
Figure 27: MOM (managed objects model) of the FOX 47

PREFACE
1 Preface
1.1 Precautions and safety
Before you handle any FOX equipment make sure you comply with the rele-
vant safety advices.
1.2 Symbols and notations
This user manual uses the following symbols:
Please note:
Shows a significant information.
Indicates a possibly hazardous context. The possible hazard is indi-

cated with a symbol and a description.
A further description is added to describe the details of the hazard.
→ Possible actions are given as in this paragraph.
Warns of hazardous circumstances. The hazard is specified.

A description of the danger is added.
→ Possible actions are given as in this paragraph.
1.3 Interfaces and circuit categories
Table 1: Electrical interfaces and circuit categories

Interface Circuit category according Max. rating
to EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC < 30 A
Alarm interface TNV2 < 72 VDC < 10 mA
FAMO1 or FAMO1-F inputs
Alarm interface SELV <6V < 10 mA
FAMO1 or FAMO1-F outputs
Alarm interface TNV2 < 72 VDC < 10 mA
FAMO2 inputs

PREFACE
1.4 Document history
Table 2: Document history

Date FOX Changes since previous version
Release
May 2012 R1 First release for the FOX615/612.
1.5 Definition of terms
Table 3: Specific terms and abbreviations

Term Explanation
CESM1 Designates the core and control unit CESM1 of FOX.
CESM1-F Designates the core and control unit CESM1-F of FOX.
CESM1-F is functionally identical to the CESM1 unit, but can
be deployed in FOX61x subracks with passive cooling.
In this user guide, the term CESM1 is used to name the
CESM1 and CESM1-FF. Where certain features or characteris-
tics apply to the CESM1-F only, the CESM1-F is named explic-
itly.
EPSI1 Designates the service unit EPSI1, Ethernet switching and
routing with Ethernet over PDH transport unit of FOX.
LEDE1 Designates the service unit LEDE1, E1 line card of FOX.
FOX In this user manual, the term “FOX” is used to name the net-
work element types FOX612 and FOX615. Where certain fea-
tures or characteristics apply to a specific network element type
only, the respective network element type is named explicitly.
FOX61x The term “FOX61x” is used to name the network element types
FOX612 or FOX615.
SAMO2 Designates the service unit SAMO2, SDH transport unit for
TDM and Ethernet traffic of FOX.
SAMO2-F Designates the service unit SAMO2-F of FOX.
SAMO2-F is functionally identical to the SAMO2 unit, but can
be deployed in FOX subracks with passive cooling.
In this user manual, the term SAMO2 is used to name the
SAMO2 and SAMO2-F. Where certain features or characteris-
tics apply to the SAMO2-F only, the SAMO2-F is named explic-
itly.
DATI1 Designates the service unit DATI1, TDM G.SHDSL line card of
FOX.
ETOP1 Designates the service unit ETOP1, optical Ethernet transport
unit of FOX.

PREFACE
Table 3: Specific terms and abbreviations (continued)

Term Explanation
ETOP1-F Designates the service unit ETOP1-F, optical Ethernet trans-
port unit of FOX.
ETOP1-F is functionally identical to the ETOP1 unit, but can be
deployed in FOX subracks with passive cooling.
In this user manual, the term ETOP1 is used to name the
ETOP1 and ETOP1-F. Where certain features or characteris-
tics apply to the ETOP1-F only, the ETOP1-F is named explic-
itly.
ELET1 Designates the service unit ELET1, electrical Ethernet trans-
port unit of FOX.
LESU1 Designates the service unit LESU1, POTS subscriber interface
(FXS) unit of FOX.
SAMO1 Designates the service unit SAMO1, SDH transport unit for
TDM and Ethernet traffic of FOX.
LEDS1 Designates the service unit LEDS1, TDM data interface and
Ethernet interface unit of FOX.
LEDA1 Designates the service unit LEDA1, voice and E&M signalling
interface unit of FOX.
LECO1 Designates the service unit LECO1, E0 interface unit of FOX.
LEXI1 Designates the service unit LEXI1, POTS exchange interface
(FXO) unit of FOX.
AP Access point
CAS Channel Associated Signalling
CPE Customer Premises Equipment, general term for equipment at
the customer site
CTP Connection Termination Point
CU Control Unit or Core Unit
DXC Digital Cross Connect
E1 Physical layer of the ITU-T G.703 2048 kbit/s traffic signal
FOXCST Enhanced Configuration Software Tool
ESW Embedded Software
(M)CAS (Mercury) CAS
MF Management Function
MO Managed Object
MOM Managed Objects Model
NE Network Element
P0 Logical layer of the 64 kbit/s traffic signal
P0-nc Logical layer of the n x 64 kbit/s traffic signal, concatenated P0
signal
P12 Logical layer of the 2048 kbit/s traffic signal with or without a
structure according to ITU-T G.704
PBUS PDH based bus in the FOX
PDH Plesiochronous Digital Hierarchy
PETS Plesiochronous Equipment Timing Source
POTS Plain Old Telephone Service
PSTN Public Switched Telephone Network

PREFACE
Table 3: Specific terms and abbreviations (continued)

Term Explanation
S12 Logical layer of the VC-12 traffic signal. A VC-12 has a trans-
port capacity of 2’176 kbit/s.
S3 Logical layer of the VC-3 traffic signal. A VC-3 has a transport
capacity of 48’384 kbit/s.
S4 Logical layer of the VC-4 traffic signal. A VC-4 has a transport
capacity of 149’760 kbit/s.
SHDSL Symmetrical High speed DSL
SU Service Unit
TDM Time Division Multiplexing
1.6 Feature licences
Part of the FOX functionality is subject to feature licences. For more informa-
tion on feature licences please refer to FOX61x Release Notes.

OVERVIEW
2 Overview
2.1 Network element view
Figure 1: FOX615 view without front cover

OVERVIEW
Figure 2: FOX615 view with front cover mounted
Figure 3: FOX612 view without front cover

OVERVIEW
Figure 4: FOX612 view with front cover mounted
Please note:
Some FOX units require more space for the front cabling than the standard
front cover offers. For these applications a front cover with extended depth is
available.
→ Please make sure not to close the front cover unless all units inserted
are compatible with the front cover.
For more information on the type of front cover needed, please refer to
FOX615 Installation Manual or refer to FOX612 Installation Manual.
2.2 Network element description
The FOX61x is a network element can be used either as multiservice 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 FOX61x includes a packet based core and a circuit based core. Protocol
conversion functions allow the transport of Ethernet frames over PDH or
SDH.
The packet based core of the FOX is built up from several individual Ether-
net switching devices located on the core unit and on the Ethernet service
units. However, from a system's perspective, the FOX network element
behaves as one single integrated bridge, called “chassis switch”. Each
Ethernet service unit and the core unit plugged and assigned in the FOX
subrack contributes its switch ports to the chassis switch, i.e. the chassis
switch ports are located on the core unit and on the service units.
The circuit based core of the FOX is built around the TDM bus in the sub-
racks backplane. The TDM bus with the corresponding access circuits pre-
sents a distributed cross connect system with a an access capacity of 128 x

OVERVIEW
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).
tbd The FOX61x provides syslog functionality with ten configurable syslog
destinations, and with configurable syslog sources. The sources can be the
event logbook, the configuration logbook, the equipment logbook, the ses-
sion logbook, system related messages, and/or application and protocol
related messages. For more information, please refer to FOXCST Operation
Manual.
The time stamps in logbooks, and the network element internal time are
based on the built-in clock. The NE clock is set to UTC while the element
manager (FOXCST) allow the display of the NE time as local time. Setting of
time zones on the element manager is supported. For more information,
please refer to refer to FOXCST Operation Manual.
The FOX configuration database is stored in a non-volatile memory on the
control unit, or on the two control units if redundancy is implemented.
2.2.1 Subrack
2.2.1.1 Subrack mounting
The FOX61x subrack is a 19-inch mountable subrack with 21 slots (FOX615)

or 8 slots (FOX612). It is intended for horizontal mounting into a 19-inch rack
or an ETSI rack. The FOX612 can also be mounted directly to a wall.
2.2.1.2 Subrack capacity and slots
The FOX61x can house one or two core units in dedicated slots. In addition
the subrack houses one to twenty (FOX615) or one to seven (FOX612) ser-
vice units.
The FOX612 subrack is a compact version of the FOX615 subrack. The
slots in the FOX612 are numbered according to their designation in the
FOX615 and their functionality corresponds principally to the slot usage in
the FOX615.
The FOX612 uses the same units and provides the same services as the
FOX615.
Abbreviations:
• CU = Control Unit
• SU = Service Unit

OVERVIEW
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 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
FOX612
FOX615
Figure 5: FOX61x with CU and SU
For more information on the subrack refer to FOX61x Product Features and
Characteristics.
2.2.1.3 Subrack cooling
To evacuate the heated air from the subrack, a passive or active cooling can
be used.
Passive cooling, i.e. without a fan unit, requires the deployment of specific
functional units. The maximum ambient temperature and the maximum
power dissipation are reduced compared to the actively cooled subrack.
Please note:
Passive cooling with the horizontally mounted FOX612 subrack is not possi-
ble.
→ A horizontally mounted FOX612 subrack requires active cooling with a
fan unit.
Active cooling, i.e. with a fan, requires the deployment of a subrack specific
fan unit FAMO1 (FOX615) or FAMO2 (FOX612). For details about these
units please refer to section Fan unit - FAMO1 (FOX615), option (on
page 23) or refer to section Fan unit - FAMO2 (FOX612), optional (on
page 29).

OVERVIEW
2.2.1.4 Subrack powering
The FOX61x subrack can be powered from a single or from a dual (redun-
dant) power supply.
For redundant power feeding, a specific redundant power supply unit DUPF1
(FOX615) or DUPF2 (FOX612) is used. For details about this unit please
refer to section 4.7 Redundant power supply - DUPF1 (FOX615), optional
(on page 33) or refer to section 4.8 Redundant power supply - DUPF2
(FOX612), optional (on page 35).
2.3 Control functions
2.3.1 Unit control

The control within the FOX61x relies on processors on the service units (traf-
fic units) and on a central control block on the core unit CESM1.
The main tasks of the central control block are
• Management of the NE configuration
• Control of the system operation
• Management communication
• Synchronisation
• Monitoring of the system performance
For more details, refer to FOX61x Product Features and Characteristics,
section “System control”.
2.3.2 Management communication

Management access to the FOX61x is done using the local manager
FOXCST, or the network manager FOXMAN-UN.
For more details about management communication, refer to FOXCST Oper-
ation Manual.
For instructions to the initial connection to the FOX61x, refer to FOXCST
Installation.

INSTALLATION
3 Installation
3.1 FOX61x subrack
For the installation of the FOX61x subrack please refer to FOX615 Installa-
tion Manual or refer to FOX612 Installation Manual.
3.2 FOX units for passive cooling operation
Attention to temperature range!

The maximum ambient temperature of a FOX with passive cooling (without
an active fan unit) is 55°C.
Functional units with a high power dissipation cannot be operated without
active cooling. For the operation of a FOX61x subrack with passive cooling,
ABB offers therefore some modified high power units that can be used with
passive cooling. The Table 4 shows the high power functional units, that
have to be actively cooled, with their passively cooled equivalents.
Table 4: Active or passive cooling FOX units

Function Active cooling Passive cooling
unit unit
Core and control unit, 10GbE switch CESM1 CESM1-F
12 SFP based Ethernet interfaces ETOP1 ETOP1-F
4 STM-16/STM-4/STM-1 interfaces, 4 electrical SAMO2 SAMO2-F
Ethernet interfaces, 32 EoS groups

FOX units requiring active cooling must not be operated in a FOX subrack
without an operational fan unit.

INSTALLATION
Functional units with a low power dissipation can be operated with active
and with passive cooling. The Table 5 shows the low power functional units,
that can be used without modification in actively and passively cooled sub-
racks.
Table 5: Active and passive cooling FOX units

Function Active and pas-
sive cooling unit
8 SHDSL interfaces, TDM based DATI1
8 E1 interfaces, G.703/G.704 LEDE1
4 V.24/V.28, V.35, X.24/V.11, RS485 data inter- LEDS1
faces, 1 Ethernet interface, packet over PDH
8 E&M interfaces, 2-wire/4-wire voice LEDA1
12 FXO interfaces, 2-wire LEXI1
8 E0 interfaces, G.703, codirectional LECO1
16 PSTN a/b interfaces LESU1
4 Ethernet interfaces, managed switch, routing, EPSI1
packet over PDH.
All FOX units not listed in this section can only be used with actively cooled
subracks.

FUNCTIONAL DESCRIPTION
4 Functional description
4.1 Management connection
4.1.1 Initial management connection

The initial management connection to a FOX network element can only be
R1B
done locally using a direct connection from a PC to the Ethernet local man-
agement interface on the FOX control unit plugged in slot-11.
37900374
The following prerequisites and steps have to be performed:

• Install an appropriate version of the element manager FOXCST on a PC.
• Connect an Ethernet cable from the PC to the Ethernet local manage-
Local management ment interface on the FOX control unit plugged in slot-11.
interface
• Connect to the FOX with the user class “manager”.
• Download the ESWs of the control unit to the network element and acti-
vate the ESWs.
• Disconnect and reconnect with the user class “session manager”.
• Initialize the passwords for the different user classes.
• Disconnect and reconnect with the user class “manager”.
• Assign the core unit to make it available for commissioning.
• Download the required ESWs to all service units, restart and assign the
units to make them available for commissioning.
• The FOX network element is now ready for configuration.
Please note:
For the installation procedures and the detailed initial connection procedure
please refer to FOXCST Installation Manual.
4.1.2 Local management connection

Local management of a FOX network element is done via the Ethernet local
management interface of the active control unit. It allows a direct connection
to the system using a point-to-point connection. The purpose of the local
management interface is commissioning and maintenance of the FOX via a
local craft device.
For systems with a redundant control unit (future release), it is possible to
connect the Ethernet local management interfaces of both the active and
standby control units to the local craft device (e.g. via a switch). Only the
Ethernet interface of the active control unit communicates. The Ethernet
interface of the standby control unit is deactivated.
The Ethernet interface is of the type 10/100BASE-TX and supports auto-
negotiation with half- and full-duplex mode and automatic MDI/MDIx switch-
over.
The IP address is fixed to 192.168.1.1 and belongs to the 192.168.1 subnet,
i.e. the IP address of the element manager PC must be in the range
192.168.1.2 to 192.168.1.254.

Network element management is done with the element manager FOXCST,

using a ABB proprietary TCP/IP connection.
Risk of operating trouble!

The IP address of the local management interface is fixed and identical on
all control units. It is therefore not possible to access more than one active
control unit from one local craft device via a switch.
Please note:
For more information about the FOX local management please refer to
FOXCST Operation Manual.
4.1.3 Remote management connection

Remote management of a FOX network element is done via an Ethernet port
or via a data communication network (DCN).
The Ethernet connection allows a remote connection to the system using an
Ethernet port of the chassis switch via an inband transport of the manage-
ment communication.
In order to be able to connect to your FOX61x from a remote FOXCST or
UNEM via inband management traffic, you need to pre-configure your
FOX61x’s IP address and management VLAN ID via a local management
connection.
The DCN connection allows a remote connection to the system using an
embedded communication channel (ECC) of the SDH or PDH transport
units. The management communication is terminated in the router instance
of the CESM1 unit.
The DCN method for the remote management of your FOX61x requires the
configuration of your FOX61x’s IP address, router parameters and DCN
transport channels via a local management connection.
Network element management is done with the FOXCST, using a ABB pro-
prietary TCP/IP connection.
Please note:
For more information about the FOX remote management please refer to

4.2 Date and time management
The FOX NE uses UTC as a time base for time-dependent management

actions, e.g. time scheduled ESW download. However, there is an exception
to this behaviour within the media gateway context, where local NE time is
used.
FOXCST uses local NE time for all its time-dependent actions. For each data
transaction between a FOX NE and FOXCST the time indications are com-
puted according to the time zone setting on the element manager (PC).

Some functions in the FOX (e.g. performance management) do not work
unless date and time are set.
4.2.1 SNTP implementation

In FOX a SNTP client is implemented (as proposed in RFC 2030) which is
able to keep the system clock automatically updated.
It has three operations modes:
• Broadcast
It listens for broadcast messages delivered by the SNTP server with the
clock information (NTP mode 5).
• Unicast
It queries the SNTP server (NTP mode 3) to update the system clock
information periodically (every configured «Polling Period»).
• Disabled
The SNTP client is not working and thus the clock time is not updated.
Two SNTP servers can be defined when working in unicast mode. In case
that the primary server is not available the secondary server will be used.
As a work around in case of a missing SNTP server, any Windows® PC can
run a NTP service, which responds to SNTP clients in unicast mode.
Alternatively date and time can be set manually. Refer to section AP: / ne,
Status - Date And Time - Time (on page 60).

The SNTP client implementation in the current FOX release does only sup-
ports SNTPv3.
→ Please use a SNTPv3 server.

Untagged SNTP messages can only be accepted by interfaces configured
as “Access Port”. For SNTP messages to be accepted by inband manage-
ment (e.g. via a trunk port) they must be tagged with the valid management
VLAN ID (default is 4089).
For configuration details refer to paragraph AP: / ne, Configuration - Date
And Time - SNTP Client (on page 50).

4.3 Redundant Core Unit CESM1 (future release)
In the FOX61x, the core unit CESM1 can be implemented with redundancy.
For this purpose, a second CESM1 unit is placed in the subrack. The first
CESM1 unit is placed in slot 11, the second, redundant CESM1 unit is
placed in slot 13. For more details about CESM1 commissioning and opera-
tion, refer to FOX61x CESM1.
On unit level, both of the CESM1 have to be configured identically, i.e. unit
specific settings need to be done on each of the two units. The redundancy
function itself does not need to be configured or activated. It is active by
default as soon as the correct HW and ESW are available in the two slots,
11 and 13. The two units are presented as shown in the following sample
screenshot in the FOXCST:
Figure 6: FOX61x, tree view in FOXCST tbd
On network element level, the following status/maintenance functions are

available:
• display the status of the two core units (active, stand-by) involved in the
redundancy,
• display the synchronisation status of the two databases,
• display the synchronisation status of the system configuration,
• display the synchronisation status of the basic software infrastructure of
the stand-by unit,
• manual commands to switch between active and stand-by unit.
For more information on the commissioning and operation of the core unit
redundancy, please refer to section 7.2.5.8 AP: / ne, Status - Redundancy
(on page 63).

4.4 Fan unit - FAMO1 (FOX615), option
4.4.1 General
The FAMO1 is a fan unit for the evacuation of the heated air that is produced
in the FOX615. The FAMO1 is equipped with 10 fans built into a 19-inch
subrack. Adapters are available for ETSI rack installation.
The FAMO1 has 10 individually monitored fans that are integrated in a 19-
inch subrack (1 HU). The FAMO1 is internally powered from the FOX615
subrack while the FOX615 core unit monitors the alarms from the fan unit.
The FAMO1 is installed above the FOX615 subrack and is able to evacuate
up to 1200 W from the FOX615 subrack. The fans begin operation even
below the operational voltage range for FOX615. The fan unit stops opera-
tion at a lower voltage than the power down voltage threshold of the venti-
lated FOX615.
The fan speed is temperature controlled. It can be kept to a minimum at low
ambient temperatures extending the lifetime of the fans and reducing noise.
The speed rises automatically with higher temperatures.
The FAMO1 has 3 x 4 alarm inputs for external alarm signals and two relay
alarm outputs for system alarms. The interfaces for the alarm signals and the
FAMO1 power supply are on the unit front panel.
Three LEDs indicate local failures and the operational state of the fan unit:
• A green LED monitors the FAMO1 input power.
• A yellow LED indicates fan unit partial failure.
• A red LED indicates fan unit total failure.
The FAMO1 provides two relays for network element alarm outputs.

Units requiring active cooling may overheat and be damaged quickly if the
fans are not running. Natural air convection is not sufficient to evacuate the
locally dissipated heat.
→ Make sure that the FAMO1 unit is operational whenever the FOX sub-
rack is equipped with units requiring active cooling and is powered up.
Figure 7: FAMO1 unit

4.4.2 Block diagram

FOX
internal
power
interface Converter 1 PTC 1
Fan 1
UTF Input Fuse 1 DC Power fail 1 Speed signal 1
-48/-60 V DC Filter DC Control 1
GND Converter 2 PTC 2

Fan 2
Fuse 2 DC Power fail 2 Speed signal 2
Control 2
DC
FOX
.....
.....
.....
internal
inventory
interface Fan unit
Inventory
Data PTC 10
Fan 10
Speed signal 10
Thermistor
FOX
internal
alarm System alarm interface and control Control, monitoring and alarming
interface SNA Relay SAA Relay
LED green LED yellow LED red
Alarm inputs
Power Partial Total

..... failure failure
1 12
Figure 8: FAMO1 block diagram
• Legend:
SAA = Service Affecting Alarm
SNA = Service Not affecting Alarm
The architecture of the FAMO1 uses redundancy for the most important sub-
systems. This ensures that adequate ventilation is maintained even after the
failure of an internal DC/DC converter or a fan.
The UTF voltage from the power supply is filtered and fed via fuses to the
redundant DC/DC converters. A blown fuse isolates the converter from the
supply and allows the second converter to keep working. The fuses are not
user serviceable. The FAMO1 has to be sent to the factory for repair.
The DC/DC converters provide their temperature controlled output voltage
via two diodes to the common rail for the power supply of the fans and the
monitoring circuit. Individual PTC resistors in each fan supply circuit protect
the common rail from failures and short circuits in fans.
The fans provide individual speed signals for operation control and monitor-
ing. The control block detects low speed and not operating fans and takes
the appropriate actions.

4.4.3 Installation
For details on the installation, refer to FOX615 Installation Manual.
4.4.4 Interfaces
4.4.4.1 Alarm input interfaces
FAMO1 provides 12 alarm input interfaces. These alarm interfaces are con-
nected to the core unit for processing and delivery.
The alarm input interfaces are used for the reception of the DUPF1 alarms
as well as for external equipment alarms (e.g. “low battery”, “high tempera-
ture”, “door open”).
The input alarm interfaces are shown in the figures below as F3, F4 and F5.
The individual input interfaces are arranged in groups with one connector per
group.
Table 6: Arrangement of alarm inputs

F3 interface F4 interface F5 interface
alarm-1 alarm-5 alarm-9
alarm-3 alarm-7 alarm-11 a
a.Please note that if the optional DUPF1 unit is installed, the “alarm-11” and “alarm-12”
signals are reserved by default for the “Power supply 1 failed” and “Power supply 2
failed” alarms of the DUPF1.
For details of the DUPF1 alarm interface connection, please refer to FOX615 Installa-
tion Manual.
F3 F4 F5
fan 48 VDC 19" 1U R2 A
37970003 2111743473
50 2011 W44
moving fans
refer to handbook
F2: Alarm outputF3: Alarm inputs F4 :Alarm inputs F5: Alarm inputs
1 -2 1-4 5 -8 9 -12
Figure 9: FAMO1 front panel with alarm input interfaces
Please note:
For details on the pin-out of the interfaces refer to FOX615 Installation Man-
ual.

4.4.4.2 Alarm output interfaces
The FAMO1 provides the interface F2 for the output of the two system alarm
signals:
• Service affecting alarm (SAA)
• Service NOT affecting alarm (SNA)
The alarm output interfaces can be used e.g. for the control of alarm lamps,
bells, etc.
F2
37970003 2111743473
50 2011 W44
moving fans
refer to handbook
1 -2 1-4 5 -8 9 -12
Figure 10: FAMO1 front panel with alarm output interfaces
4.4.4.3 Interface to FOX
The interface F1 on the FAMO1 connects the fan unit to the FOX615 core
unit via a connector on the subrack backplane.
The interface F1 provides the powering and management connection.
F1
37970003 2111743473
50 2011 W44
moving fans
refer to handbook
1 -2 1-4 5 -8 9 -12
Figure 11: FAMO1 front panel with interface towards the FOX615 sub-
rack
4.4.4.4 Optical interfaces
The FAMO1 has three LEDs to indicate the status of the power supply and
the fans.


37970003 2111743473
50 2011 W44
moving fans
refer to handbook
1 -2 1-4 5 -8 9 -12
Partial breakdown (yellow )

Total breakdown (red)
Power (green )
Figure 12: FAMO1 front panel with LED status indicators
For details of meaning and activation of the LED indicators, refer to section
Monitoring and alarming (on page 40).
4.5 Alarm unit - FAMO1-F (FOX615), optional
4.5.1 General
The FAMO1-F is an alarm unit used in place of the fan unit FAMO1 in a pas-
sively cooled FOX615.
The FAMO1-F has the same alarm interfaces as the FAMO1. The FAMO1-F
has 3 x 4 alarm inputs for external alarm signals and two relay alarm outputs
for system alarms. The interfaces for the alarm signals and the FAMO1-F
power supply are on the unit front panel.
The FAMO1-F is internally powered from the FOX615 subrack while the
FOX615 core unit monitors the alarms from the alarm unit.
The FAMO1-F is typically installed above the FOX615 subrack. Adapters are
available for ETSI rack installation.
One LED indicates local failures and the operational state of the alarm unit:
• A green LED monitors the FAMO1-F input power.
Figure 13: FAMO1-F unit tbd

4.5.2 Block diagram

FOX internal
power interface
UTF
Input Filter
-48/-60 VDC
GND
FOX internal
inventory interface Alarm unit
Inventory Data
FOX internal
alarm interface System alarm interface and control
SNA Relay SAA Relay
LED green
Alarm inputs
Power
.....
1 12
Figure 14: FAMO1-F block diagram
• Legend:
SAA = Service Affecting Alarm
SNA = Service Not affecting Alarm
4.5.3 Installation
4.5.4 Interfaces
4.5.4.1 Alarm input interfaces
Please refer to section Alarm input interfaces (on page 25) for a description
of the FAMO1-F alarm input interfaces.
4.5.4.2 Alarm output interfaces
Please refer to section Alarm output interfaces (on page 26) for a description
of the FAMO1-F alarm output interfaces.
4.5.4.3 Interface to FOX
Please refer to section Interface to FOX (on page 26) for a description of the
FAMO1-F interface to the FOX.
The FAMO1-F has one LED to indicate the status of the power supply.

alarm 48 VDC 19 " 1U R2 A

37970003 2111743473
50 2011 W44
1 -2 1-4 5 -8 9 -12
Power (green)
Figure 15: FAMO1-F front panel with LED status indicator
4.6 Fan unit - FAMO2 (FOX612), optional
4.6.1 General
The FAMO2 is a fan unit for the evacuation of the heated air that is produced
in the FOX612. The FAMO2 is equipped with 2 fans (FAMO2 R1) or 4 fans
(FAMO2 R2) built into a unit designed for the FOX612. This unit fits to a ded-
icated slot on top (vertical subrack installation) or to the left (horizontal sub-
rack installation) of the FOX612 subrack.
The FAMO2 has individually monitored fans. The FAMO2 is internally pow-
ered from the FOX612 subrack while the FOX612 core unit monitors the
alarms from the fan unit.
The FAMO2 is able to evacuate up to 425 W from the FOX612 subrack. The
fans begin operation even below the operational voltage range for FOX612.
The fan unit stops operation at a lower voltage than the power down voltage
threshold of the ventilated FOX612.
The fan speed is temperature controlled. It is kept to a minimum at low ambi-
ent temperatures extending the lifetime of the fans and reducing noise. The
speed rises automatically with higher temperatures.
The FAMO2 has 3 x 4 alarm inputs for external alarm signals on the unit
front panel.
Three 3 LEDs indicate local failures and of the operational state of the fan
unit:
• A green LED monitors the FAMO2 input power.
• A yellow LED indicates fan unit partial failure.
• A red LED indicates fan unit total failure.

Units requiring active cooling may overheat and be damaged quickly if the
fans are not running. Natural air convection is not sufficient to evacuate the
locally dissipated heat.
→ Make sure that the FAMO2 unit is operational whenever the FOX sub-
rack is equipped with units requiring active cooling and is powered up.

Figure 16: FAMO2 R2 unit
4.6.2 Block diagram

FOX
internal
power
interface Converter 1
Fan 1
UTF Input Fuse 1 DC Power fail 1 Speed signal 1
-48/-60 V DC Filter DC Control 1
GND Converter 2
Fan 2
Control 2
DC
FOX Converter 3
internal Fan 3
Fuse 3 DC Power fail 3
inventory Speed signal 3
interface Fan unit DC Control 3
Inventory
Data Converter 4
Fan 4
Control 4
DC
Thermistor
FOX
internal
alarm System alarm interface Control, monitoring and alarming
interface and control
LED green LED yellow LED red
Alarm inputs
Power Partial Total

..... failure failure
1 12
Figure 17: FAMO2 R2 block diagram
Please note:
The FAMO2 R1 has two individually powered fans, the FAMO2 R2 has four
individually powered fans.
→ FAMO2 R2 provides a more homogenous air flow.

The architecture of the FAMO2 uses redundancy for the most important sub-
systems. This ensures that adequate ventilation is maintained even after the
failure of an internal DC/DC converter or a fan.
The UTF voltage from the power supply is filtered and fed via fuses to the
redundant DC/DC converters. A blown fuse isolates the converter(s) from
the supply and allows the second converter(s) to keep working. The fuses
are not user serviceable. The FAMO2 has to be sent to the factory for repair.
The DC/DC converters provide their temperature controlled output voltage
directly to a fan.
The fans provide individual speed signals for operation control and monitor-
ing. The control block detects low speed and not operating fans and takes
the appropriate actions.
4.6.3 Installation
4.6.4 Interfaces
4.6.4.1 Alarm Input interfaces
FAMO2 provides 12 alarm input interfaces. These alarm interfaces are con-
nected to the core unit for processing and delivery.
The alarm input interfaces are used for external equipment alarms (e.g. “low
battery”, “high temperature”, “door open”).
The input alarm interfaces are shown in the figures below as F3, F4 and F5.
The individual input interfaces are arranged in groups with one connector per
group.
Table 7: Arrangement of alarm inputs

F3 F4 F5
a.Please note that if the optional DUPF2 unit is installed, the “alarm-9” and “alarm-10”
signals are reserved by default for the “Power supply 1 failed” and “Power supply 2
failed” alarms of the DUPF2.
For details of the DUPF2 alarm interface connection, please refer to FOX612 Installa-
tion Manual.

F3 F4 F5
F3: Alarm inputs F4: Alarm inputs F5: Alarm inputs
1-4 5-8 9-12
R2A
37970038 4919709605
11W31
50
Figure 18: FAMO2 front panel with alarm input interfaces
Please note:
For details on the pin-out of the interfaces refer to FOX612 Installation Man-
ual.
Please note:
For the electrical specification of the alarm interfaces refer to FOX61x Prod-
uct Features and Characteristics.
The FAMO2 has three LEDs to indicate the status of the power supply and
the fans.
F3: Alarm inputs F4: Alarm inputs F5: Alarm inputs

1-4 5-8 9-12
R2A
37970038 4919709605
11W31
50
Power (green )
Total breakdown (red )
Partial breakdown (yellow)
Figure 19: FAMO2 front panel with LED status indicators
For details of meaning and activation of the LED indicators, refer to section
Monitoring and alarming (on page 40).

4.7 Redundant power supply - DUPF1 (FOX615),

optional
4.7.1 General
There is a hardware supplement that can be installed in order to provide the
FOX615 system a second primary power supply to be used as a redundant
source. This hardware supplement is called DUPF1 (DUal Power Input).
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 supported
is 30 A.
The two input voltages UT1 and the UT2 are connected via diodes and fed
as the UTF voltage to the FOX subrack. The ground potential of the two
input voltages are directly connected.
From the DC To the
power distribution subrack
UT 1 UTF
-48/-60 V DC -48/-60 VDC
Monitor
GND GND
UT 2 Power supply
-48/-60 V DC PSC1 failed
Monitor
GND Power supply
PSC2 failed
Figure 20: DUPF1 block diagram
DUPF1 provides also surge protection on the power supply input side and
protection against reverse polarity.
The availability of both power supplies is monitored and failures are alarmed.
For this purpose, the DUPF1 has an alarm interface with two alarm signals.
This alarm interface is connected to the alarm input interface of the FAMO1
or FAMO1-F unit. The FAMO1 or FAMO1-F alarm input interfaces are con-
nected to the core unit for alarm processing.
Figure 21: DUPF1 unit including the power and alarm cables

Once the installation has been done, and all cables are connected, the sys-
tem will be ready for use.
DUPF1 requires configuration via FOXCST as the alarm generation is pro-
duced with active open polarity while the default alarm configuration of all
external alarms as active closed. Set the alarm polarity to “Active Open” at
the AP: /fan/alarm-a, Configuration - General:
4.7.2 Installation
4.7.3 Alarms in DUPF1

The DUPF1 monitors its 2 feeding power supplies and creates a dedicated
alarm signal for a power supply failure. The alarm signals are forwarded to
the FOX core unit via the alarm interface of the FAMO1 or FAMO1-F.
The alarm polarity of the DUPF1 is active open.
The default set-up uses the FAMO1 or FAMO1-F alarm inputs “alarm-11”
and “alarm-12” for power supply failures (interface F5) as shown in the table
below.
Table 8: DUPF1 alarm interface power supply failures default

settings
FAMO1 or FAMO1-F alarm interface F5
F5 DUPF1 alarm Remark
alarm-9 n/a For customer specific usage
alarm-11 “Power supply 1 failed” DUPF1
For details of the DUPF1 alarm interface cabling refer to FOX615 Installation
Manual, section “Alarm Interfaces”.
The power failure is detected or cleared as follows:
Table 9: Detection and clearing of power failures

Power supply voltage Power supply failure Alarm contact
alarm
falls below 30 VDC active open
raises above 36 VDC inactive closed
+75V
-75V
-36V
-30V
0V
closed open
Input voltage
UT 1 or UT 2
Figure 22: DUPF1 contact output versus input voltage

4.8 Redundant power supply - DUPF2 (FOX612),

optional
4.8.1 General
There is a hardware supplement that can be installed in order to provide the
FOX612 system a second primary power supply to be used as a redundant
source. This hardware supplement is called DUPF2 (DUal Power Input).
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 supported
is 15 A.
The two input voltages UT1 and the UT2 are connected via diodes and fed
as the UTF voltage to the FOX subrack. The ground potential of the two
input voltages are directly connected.
From the DC To the
power distribution subrack
UT 1 UTF
-48/-60 V DC -48/-60 VDC
Monitor
GND GND
UT 2 Power supply
-48/-60 V DC PSC1 failed
Monitor
GND Power supply
PSC2 failed
Figure 23: DUPF2 block diagram
DUPF2 provides also surge protection on the power supply input side and
protection against reverse polarity.
The availability of both power supplies is monitored and failures are alarmed.
For this purpose, the DUPF2 has an alarm interface with two alarm signals.
This alarm interface is connected to the alarm input interface of the FAMO2
unit. The FAMO2 alarm input interfaces are connected to the core unit for
alarm processing.
Figure 24: DUPF2 unit including the alarm cable
Once the installation has been done, and all cables are connected, the sys-
tem will be ready for use.

DUPF2 requires configuration via FOXCST as the alarm generation is pro-

duced with active open polarity while the default alarm configuration of all
external alarms as active closed. Set the alarm polarity to “Active Open” at
the AP: /fan/alarm-a, Configuration - General.
4.8.2 Installation
4.8.3 Alarms in DUPF2

The DUPF2 monitors its 2 feeding power supplies and creates a dedicated
alarm signal for a power supply failure. The alarm signals are forwarded to
the FOX via the alarm interface of the FAMO2.
The alarm polarity of the DUPF2 is active open.
The default set-up uses the FAMO2 alarm inputs “alarm-9” and “alarm-10”
for power supply failures (interface F5) as shown in the table below.
Table 10: DUPF2 alarm interface power supply failures, default

settings
FAMO2 alarm interface F5
F5 DUPF2 alarm Remark
For details of the DUPF2 alarm interface cabling refer to FOX612 Installation
Manual, section “Alarm Interfaces”.
The power failure is detected or cleared as follows:
Table 11: Detection and clearing of power failures

Power supply voltage Power supply failure Alarm contact
alarm
falls below 29 VDC active open
raises above 34 VDC inactive closed
+75V
-75V
-34V
-29V
0V
closed open
Input voltage
UT 1 or UT 2
Figure 25: DUPF2 contact output versus input voltage

COMMISSIONING AND OPERATION
5 Commissioning and operation

5.1 Optical alarm indications
5.1.1 General
The optical fault and alarm indication on the FOX units is part of the fault
management system of the FOX network element.
All control and service units feature 2 fault indicator LEDs:
• UNIT LED (LED situated on the left, see Figure 26)
The unit LED signals hardware failures or a general non-availability of the
unit. The units provide a multifunctional red/green LED indicator at this
position.
• TRAFFIC LED (LED situated on the right, see Figure 26)
The traffic LED indicates failures of traffic functions or subunit functions.
The control unit implements two additional LEDs:
• ACTIVE LED (LED situated lower left, see Figure 26)
The active LED signals an active control unit.
• LOCKED LED (LED situated lower right, see Figure 26)
The locked LED signals the locking state of the PETS.
Some service units implement an additional, application specific LED.
Please refer to the corresponding user manual.
Control unit Service unit
CESM1
XXXXx R1B XXXXx R1B

37900374 37900374
UNIT TRAFFIC UNIT TRAFFIC
ACTIVE LOCKED
Figure 26: Control unit LEDs and service unit LEDs

5.1.2 Control unit LED description

Table 12: Control unit LED description
LED name Colour State Meaning
UNIT red failure The unit is not in service. The unit is not able to provide the
(or booting) requested function due to:
- equipment failure (total breakdown),
- mismatch of HW and/or SW.
Replace the HW and/or ESW to recover from this situation.
Note: A redundant control unit has a constantly lit UNIT LED
during booting.
green/red booting or waiting The unit has not been taken in service yet or the unit has not
blinking 1 Hz been provisioned.
Recovery from this situation is done by taking the unit in ser-
vice with FOXCST.
green running The unit is up and running, it is ready to provide the required
service.
dark failure The system is not powered, or outage of the power supply on
the unit, or outage of the LED.
TRAFFIC red failure One or more active failures on the unit independent from sever-
ity. Information about the failure/s can be obtained via
FOXCST.
Note: This definition is valid for the active and the standby unit.
dark normal Error free operation.
This is the default state under normal circumstances.
ACTIVE green active The unit is active, i.e. controls the other units in the subrack.
dark standby The unit is in standby. If the UNIT LED is green, the unit is
ready to take over the operation in case the active unit will fail.
LOCKED green locked The PDH equipment timing source (PETS) is locked to a syn-
chronisation source.
dark not locked The PETS is not locked to a synchronisation source.
There are certain FOX states which are identified by the different control unit
LED state combinations according to the following table.
Table 13: Control unit specific LED state combinations

State LED
UNIT TRAFFIC ACTIVE LOCKED
Stay in Bootloader green/red ON ON ON
blinking 1 Hz
Launch Application green/red OFF OFF OFF
blinking 1 Hz
Formatting a green/red blinking OFF OFF
blinking 1 Hz 4 Hz
Reset to factory settings green/red blinking blinking 4 Hz blinking 4 Hz
ongoing a blinking 1 Hz 4 Hz (alternating with LOCKED) (alternating with ACTIVE)
Reset to factory settings green/red ON blinking 1 Hz blinking 1 Hz
concluded a blinking 1 Hz (alternating with LOCKED) (alternating with ACTIVE)
a. These states are not relevant for normal operation and maintenance of the FOX
system.

5.1.3 Service unit LED description

Table 14: Service unit LED description
LED name Colour State Meaning
UNIT red failure The unit is not in service. The unit is not able to provide the
requested function due to:
- equipment failure (total breakdown)
- mismatch of HW and/or SW
Replace the HW and/or ESW to recover from this situation.
green/red booting or waiting The unit has not been taken into service yet or the unit has not
blinking 1Hz been provisioned.
Recovery from this situation is done by taking the unit into ser-
vice with FOXCST.
green running The unit is up and running, it is ready to provide the required
service.
dark failure The system is not powered, or outage of the power supply on
the unit, or outage of the LED, or the control unit is booting.
TRAFFIC red failure One or more active failures on the unit independent from sever-
ity. Information about the failure/s can be obtained via
FOXCST.
Note: This definition is valid for the active and the standby unit.
dark normal Error free operation.
This is the default state under normal circumstances.
5.2 Fan unit operation
5.2.1 General
When power is turned on, the fan speed is kept to the maximum for approxi-
mately 5 seconds. After that, the temperature controlled supply voltage starts
to regulate the fan speed.
Up to 20°C of ambient temperature the fans are made to turn at their mini-
mum speed. This reduces ventilation noise under normal ambient tempera-
ture conditions and increases the lifetime of the fans. With increasing ambi-
ent temperature the fan speed is increased in a linear way to its maximum
which is reached at 35°C.
The fan unit fan speeds are individually monitored. A fan is considered failed
if its speed falls significantly below the minimum. This overrides the tempera-
ture control and automatically drives the remaining fan(s) to emergency high
speed to compensate for the failure. This may also cause the failed fan to
restart. Emergency high speed is roughly 10% higher than maximum speed.
The outputs of the two DC/DC converters of the FAMO1 are also monitored.
Each converter is capable of driving all fans indefinitely at emergency high
speed. A failed converter does not override the temperature control of the
fan speed as a fan failure would.
The outputs of the two or four DC/DC converters of the FAMO2 are also
monitored. Each fan has its own converter.
A failed converter causes a partial failure alarm, indicating to the mainte-
nance personnel that the fan unit has to be replaced.

Please note:
The air temperature is measured at the point where it leaves the subrack.
5.2.2 Monitoring and alarming

The fan unit operation control monitors and indicates the operation and fail-
ures of the fan unit subsystems as shown in the table below:
Table 15: Fan failure types and related alarming

Failure of alarms as Front panel LEDs
one fan or converter more than one fan or Partial Fan Total Fan green yellow red
more than one converter Breakdown Breakdown
- - Off Off on off off
X - On Off on on off
- X Off On on off on
The green front panel LED is “on” as long as the power supply voltage UTF
is available.
5.2.3 Fan unit management functions

The fan unit has management functions (MFs) as shown in section AP: / fan
(on page 67) and AP: / fan / alarm-a (on page 69).
Please note:
For standard management functions refer to FOXCST Operation Manual.
5.2.4 Measures for protection against high temperature

The FOX61x supports alarming of NE temperature levels. In order to prevent
equipment failures due to high temperatures, you should set the temperature
levels in the NE configuration dialogue, “Temperature Limits”, to appropriate
values.
You may also enable battery power saving alarms by connecting an external
temperature sensor to one of the alarm inputs of the fan unit, and configuring
the appropriate settings in the NE configuration dialogue, “Battery Power
Saving”.
For more information on these configuration dialogues, please refer to sec-
tions AP: / ne, Configuration - Temperature Limits (on page 56) and AP: / ne,
Configuration - Battery Power Saving (on page 54).

5.2.5 Recommended action in case of a fan unit failure

5.2.5.1 Partial failure
If a fan unit reports a partial failure (the yellow LED is “on” and the “Partial
Fan Breakdown” alarm is active), it must be replaced as soon as possible.

A single fan failure may have occurred directly over a high power unit. The
total air flow is roughly maintained, but the temperature below the failed fan
will rise.
→ ABB recommends a replacement of the fan unit within 24 hours.
5.2.5.2 Total failure
A total failure without a preceding partial failure is very improbable. The

MTTF for a total failure of the FAMO2 unit is more than 1’500 years. It would
also happen if someone inadvertently pulled the FAMO1 power cable. Nor-
mally there is ample warning.
Apart from power to FAMO1 missing, there are two possible reasons for a
total failure:
• More than one fan has failed. If two failed fans are located directly above
high power units, the temperature can rise to a degree that the units do
not operate correctly and/or units with temperature monitoring start to
switch off their services. Some fans may still be operating.
• Both converters have failed. No fans are operating. Temperature of high
power units rises within minutes to a level where damage may occur.
Apart from power to FAMO2 missing, there are three possible reasons for a
total failure:
• More than one converter has failed.
• More than one fan has failed.
• At least one converter and at least one fan (powered by another con-
verter) have failed.
If a fan unit reports a total failure (the red LED is “on” and the “Total Fan
Breakdown” alarm is active), it must be replaced immediately.

As it is practically impossible to distinguish between the cases with and with-
out remaining operating fans, the worst case has to be assumed, i.e. no
operating fans are left.
→ ABB recommends to switch off the subrack immediately as an emer-
gency measure.
→ Replace the defective fan unit before switching on the subrack again.

The temperature of high power units without ventilation rises within minutes
to a level where damage may occur.

5.2.5.3 Replacement of a defective FAMO1

Temperature will rise very quickly in a FOX615 subrack with high power dis-
sipation and no ventilation.
→ It is imperative that the time without ventilation during replacement of
the fan unit is kept to an absolute minimum.
→ Downtime must be kept to less than three minutes where high power
units are in operation.
Prepare the replacement in the following way:
• Unpack the replacement FAMO1 and have it ready.
• Remove the 4 screws holding the installed FAMO1. It will be held in place
by the FOX615 subrack beneath it.
• Take all cables out of their holding clips on the left and right hand side of
the FAMO1.
• Unplug all alarm input and alarm output cables (on the right hand side of
the FAMO1).
Now you are ready to replace the faulty FAMO1 with the new one:
• Unplug the supply cable on the left hand side and remove the FAMO1.
• Immediately put the new FAMO1 in place without screwing it to the rack
and plug in the supply cable on the left hand side. The fans should start
running at high speed for at least 5 seconds before the speed regulation
sets in.
Complete the installation:
• Plug in the alarm input and alarm output cables.
• Fit the 4 holding screws and tighten them.
• Place all cables back in their holding clips.
For a complete description of the general installation procedure, please refer
to FOX615 Installation Manual, section “Installation Procedures - Fan Unit”.
5.2.5.4 Replacement of a defective FAMO2

Temperature will rise very quickly in a FOX612 subrack with high power dis-
sipation and no ventilation.
→ It is imperative that the time without ventilation during replacement of
the fan unit is kept to an absolute minimum.
→ Downtime of the fan unit must be kept to less than three minutes
where high power units are in operation.
Prepare the replacement in the following way:
• Unpack the replacement FAMO2 and have it ready.
• Remove the 2 screws securing the FAMO2 in its slot.
• Unplug all alarm input cables from their connector sockets.
Now you are ready to replace the faulty FAMO2 with the new one:
• Remove the defective FAMO2 unit.

• Immediately plug in the new FAMO2. The fans should start running at
high speed for at least 5 seconds before the speed regulation sets in.
Complete the installation:
• Plug in the alarm input cables.
• Fit the 2 holding screws and tighten them.
For a complete description of the general installation procedure, please refer
to FOX612 Installation Manual, section “Installation Procedures - Fan Unit”.
5.3 Packet services
For basics on configuration and operation of the FOX61x please refer to

For the commissioning and operation of packet services please refer to
FOX61x Ethernet Services.
5.4 TDM services
For basics on configuration and operation of the FOX61x please refer to

For the commissioning and operation of TDM services please refer to
FOX61x TDM Services Manual.


MAINTENANCE
6 Maintenance
6.1 Overview
The FOX61x requires no particular preventive maintenance if the equipment

is installed and operated in accordance with the instructions that are pro-
vided with the FOX and its units.
However, special maintenance procedures may apply for some units. In
such a case, the corresponding user manual provides the information on the
maintenance procedure.
Standard maintenance procedures are:
• Re-commissioning of the system due to new service requirements
• Updating the ESW for units
• Performance control
• Implementation of redundancy or protection
• Replacement of faulty units
In the case of failures or other problems, you should use the diagnostic tools
provided with the FOX system including Fault List and Log Book. The corre-
sponding user manuals describe the application and possibilities of these
tools.
It is possible to control all the diagnostic functions and read corresponding
information and alarms via the FOXCST.
6.2 Handling of units
It is possible to plug or remove any unit from the powered FOX subrack. If a
unit is extracted, the traffic and functions affected by the respective unit are
interrupted.
Plugging a unit into the wrong slot position does not cause damage to the
unit or to the surrounding equipment. For successful system operation, take
care to adhere to the rules for the correct unit to slot assignment in the sub-
rack. This applies in particular for the control units.
Consider all units as equipment with components that are sensitive to dis-
charges of static electricity. The danger of such discharges becomes espe-
cially important in the case of maintenance.
Electrostatic discharges. Risk of equipment damage!

Equipment is sensitive to electrostatic discharges and may be damaged if
handled without wearing a grounded wristband.
→ To handle the equipment, proceed as instructed in the document
FOX615 Installation Manual or FOX612 Installation Manual.

MAINTENANCE
Please note:
The original packaging provides the best protection for the units.
→ Keep the units in their packaging until you insert the units into the sub-
rack.
→ Restore the units in their packaging after removal from the subrack.
6.3 ESW upgrade
ESW might have to be upgraded with new releases. In that case, follow the
steps described in section 7.4, “ESW handling with FOXCST” of FOXCST
Operation Manual.

FOXCST REFERENCE
7 FOXCST reference
This section gives a complete FOXCST reference of the managed objects,
properties, and commands of the FOX61x as far as these are not yet cov-
ered in the generic description in FOXCST Operation Manual.
7.1 Introduction
Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the spe-
cific parts of the FOX61x.
The Figure 27 shows the access point (AP) tree for the FOX network ele-
ment with its managed objects.
<ap >
FOX61x
1 <ap >
fan
12 <ap >
alarm-a
1 <ap >
bridging
1 <ap >
managementNetwork
1...21 <ap >

unit-x
Figure 27: MOM (managed objects model) of the FOX tbd
With these managed objects (MOs) the following functions are covered:
Table 16: FOX61x Managed Objects (MOs)

MO Description of the management functions
/, FOX61x Network element configuration, fault management and status:
Management access control, password handling, manage-
ment interface, session management, SNMP, Syslog.
Security features, IPSec, RADIUS, QoS.
Synchronisation output, plesiochronous equipment timing
source.
Redundancy control.
System time, temperature control, logbooks, inventory data.
The detailed properties are described in AP: / ne (on page 49).

FOXCST REFERENCE
Table 16: FOX61x Managed Objects (MOs) (continued)

MO Description of the management functions
/fan Fault management of the fan unit, inventory data, status infor-
mation.
The detailed properties are described in AP: / fan (on page 67)
/fan/alarm-a Configuration and fault management of the fan units alarm
inputs.
The detailed properties are described in AP: / fan / alarm-a (on
page 69)
/bridging tbd Configuration the network element wide multicast settings, the
multicast VLANs and the multicast groups per VLAN.
Further information can be found in AP: / bridging tbd (on
page 70)
/managementNet- Management of data communication network (DCN) and
work router.
Further information can be found in AP: / managementNetwork
(on page 70)
/unit-x Management of all control units and service units, plugged in
slot-x.
Further information can be found in AP: /unit-x (on page 70)
For each of the managed objects, properties and commands, the GUI “Tree
Views” are given.
This reference section comprises the management functions:
• Overview,
• Main,
• Configuration,
• Fault Management,
• Performance Management, and
• Status.
Most of the APs only offer a part of the management functions listed above.
The order of appearance of the management function descriptions is in
accordance with the APs in the FOXCST AP tree and the availability of the
management functions of each AP.
In the tables of the sections below, the parameter default values for proper-
ties are underlined.
Please note:
For better legibility of numbers in this user manual, inverted commas are
used when the number’s size exceeds three digits (e.g. 40’000). In parame-
ter entry fields of the FOXCST, these inverted commas must not be entered.
Instead, the numbers are entered without these inverted commas (e.g.
40000).
Please note:
Screenshots presented in this reference are examples and show configura-
tions or data that may not correspond to the view you see when managing
your FOX equipment.

FOXCST REFERENCE
7.2 AP: / ne
Please note:
The Access Point (AP) named “ne” in the AP tree of the FOXCST shows the
additional information “FOX612” or “FOX615”. For reasons of simplicity and
clarity, this additional information is not shown in the following sections since
it is not used while navigating in the FOXCST.
Please note:
In the FOXCST dialogue windows the “ne” AP is identified with a forward
slash “/”. In the following sections the identifier “/” is used instead of the iden-
tifier “ne”.
7.2.1 AP: / ne, Overview

For a description of the
− “Overview - Active Alarms”, and
− “Overview - TDM Connections”
management functions, please refer to FOXCST Operation Manual.
7.2.2 AP: / ne, Main

7.2.2.1 AP: / ne, Main - General

− “Main - General”
management function, please refer to FOXCST Operation Manual.
7.2.2.2 AP: / ne, Main - Inventory

− “Main - Inventory”
7.2.3 AP: / ne, Configuration

7.2.3.1 AP: / ne, Configuration - Modify Password tbd

− “Configuration - Modify Password”

FOXCST REFERENCE
7.2.3.2 AP: / ne, Configuration - Configuration Management * tbd

− “Configuration - Configuration Management”
Please note:
When you execute the command “Initialize” on NE level while having set the
“Configuration - Packet, Bridge, Bridge Mode” and “Configuration - Packet,
Bridge, VLAN S-Tag Ethertype” parameters to a value different from the
defaults (“802.1Q” and “0x8100”, respectively), you need to restart the
CESM1 unit(s) after the initialization has been completed in order to get back
to the default settings for the “Packet, Bridge” operation parameters. tbd
7.2.3.3 AP: / ne, Configuration - Packet tbd

− “Configuration - Packet”
management function, please refer to FOX61x Ethernet Services.
Please note:
When you execute the command “Initialize” on NE level while having set the
“Bridge Mode” and “VLAN S-Tag Ethertype” parameters to a value different
from the default (“802.1Q” and “0x8100”, respectively), you need to restart
the CESM1 unit(s) after the initialization has been completed in order to get
back to the default settings for the “Packet, Bridge” operation parameters.
7.2.3.4 AP: / ne, Configuration - Session Management

− “Configuration - Session Management”
7.2.3.5 AP: / ne, Configuration - Radius Client

− “Configuration - Radius Client”
7.2.3.6 AP: / ne, Configuration - Date And Time - SNTP Client
Please note:
Only SNTPv3 is supported by the FOX NE.

FOXCST REFERENCE
Table 17: AP: / ne, Configuration - Date And Time - SNTP Client
Operation Name Parameter Name Range Descriptions / Details
Operation Mode Mode a Disabled The SNTP function is not used on the NE, i.e.
the correct time must be set manually.
Unicast The specified SNTP server is contacted in uni-
cast mode.
Broadcast The specified SNTP server is contacted in
broadcast mode.
Primary Server Address <IP v4 address> IP address of the primary SNTP server.
The default IP address is empty.
Secondary Server Address <IP v4 address> IP address of the secondary SNTP server.
The default IP address is empty.
Polling Interval Polling Interval 60 … 86’400 sec Time interval between two SNTP server queries
by the SNTP client (NE) in unicast mode.
Broadcast Delay Delay 0 … 1000 msec Configurable broadcast delay correction
because SNTP is not able to calculate this value
from the time stamps.
a. refer to RFC 1769, section 5 «NTP client operations» for details

FOXCST REFERENCE
7.2.3.7 AP: / ne, Configuration - Date And Time - Time Zone
Table 18: AP: / ne, Configuration - Date And Time - Time Zone
Ne Local Time Zone GMT-12:00 … GMT+13:00 Any worldwide official time zone may be
selected.
The NE calculates its “Local NE Time” from this
setting.
The “Local NE Time” is used in the SIP media
gateway context, see appropriate service user
manual.
Daylight Saving  The daylight saving feature is also known under
the term «Summer time», typically one hour plus
the corresponding time zone. For the current
FOXCST release this parameter is disabled and
can not be configured.

FOXCST REFERENCE
7.2.3.8 AP: / ne, Configuration - Date And Time - Time Source Selection tbd
Table 19: AP: / ne, Configuration - Date And Time - Time Source
Selection tbd
Time Sources from Time Source 1 <MO address> Select the MO address of the unit offering the
Time Source 2 <MO address> time source, e.g. /unit-1.
Time Source 3 <MO address>

Time Source 4 <MO address>
Time Sources Prior- SNTP Client 1…8 Select the priority of the time source.
ity Disabled 1 is the highest priority
Time Source 1 1…8 Select the priority of the time source.

Disabled 1 is the highest priority




FOXCST REFERENCE
7.2.3.9 AP: / ne, Configuration - QoS

− “Configuration - QoS”
management function, please refer to FOX61x Ethernet Services.
7.2.3.10 AP: / ne, Configuration - SNMP tbd

− “Configuration - SNMP”
7.2.3.11 AP: / ne, Configuration - Syslog Destinations

− “Configuration - Syslog Destinations”
7.2.3.12 AP: / ne, Configuration - Syslog Sources

− “Configuration - Syslog Sources”
7.2.3.13 AP: / ne, Configuration - Battery Power Saving
For those applications with both mains power and battery power feeding, the
FOX supports a user configurable emergency operation with reduced power
requirement. By taking some units out of operation, the critical services can
run for a longer time period with battery power feeding.
Please note:
External wiring is required from the mains power supply alarm output to the
fan unit’s alarm detection input. For details on the pin-out of alarm interfaces
refer to FOX615 Installation Manual and FOX612 Installation Manual.
Please note:
Battery power saving is only supported on selected service units. All other
units cannot be added to the “power saving list”.
→ Please refer to FOX61x Release Notes for a list of the service units
supporting battery power saving.

FOXCST REFERENCE
Add unit Remove unit
Table 20: AP: / ne, Configuration - Battery Power Saving

Battery Power Sav-  The function «Battery Power Saving» is acti-
ing Enabled vated and all units in the power saving list will be
held in reset state after a mains loss alarm has
been detected and the activation time has
expired.
 The «Battery Power Saving» function is disa-
bled.

FOXCST REFERENCE
Table 20: AP: / ne, Configuration - Battery Power Saving (continued)

Mains Power alarm-1 … alarm-12 One of the 12 alarm inputs on the fan or alarm
Supervision Input unit can be configured as supervision input for
the mains power loss. An active alarm is inter-
preted as loss of mains power. External wiring
between the mains power unit and the FOX NE
must be provided by the operator.
Power Saving Mode Activation 1 … 1000 min Time interval between detection of a mains loss
Activation Thresh- and the activation of the reset state for all units in
old Times the power saving list. Service breakdowns for
mains interruptions below the activation thresh-
old time are thus prevented.
Deactivation 1 … 1000 min Time interval between detection of restored
mains power and the return to normal operation
state for all units. This time period should allow
the battery to recharge.
Units Reset for Unit unit-1 … unit-21 A list of units that are to be held in reset state
Power Saving after a mains loss alarm has been detected and
the activation time has expired. This list is called
“power saving list” in this context.
Add Unit… Unit unit-1 … unit-21 Add a new unit to the power saving list.
The units to be added must be assigned, not yet
included in the list and must not be core units.
Remove Unit… Unit unit-1 … unit-21 Remove a unit from the power saving list.
7.2.3.14 AP: / ne, Configuration - IPSec

− “Configuration - IPSec”
7.2.3.15 AP: / ne, Configuration - Temperature Limits
A temperature sensor is located on the CESM1 unit. Its current readings can
be accessed at the AP: /, Status - Temperature, refer to section AP: / ne,
Status - Temperature (on page 66). Furthermore the temperature sensor can
trigger two alarms of different severity at user configurable temperature lev-
els.

FOXCST REFERENCE
Table 21: AP: / ne, Configuration - Temperature Limits

Exceed Set 20 … 60 … 70 °C Temperature at which an over-temperature
alarm is activated:
TLE Temperature Limit Exceeded.
Clear 20 … 58 … 70 °C Temperature at which an active over-tempera-
ture alarm is cleared.
Keep a reasonable difference between «Set»
and «Clear» (Hysteresis).
Warning Set 20 … 55 … 70 °C Temperature at which an over-temperature
warning is activated:
TLA Temperature Limit Approaching.
Keep the warning limits below the alarm limits.
Clear 20 … 53 … 70 °C Temperature at which an active over-tempera-
ture warning is cleared.
Keep a reasonable difference between «Set»
and «Clear» (Hysteresis).
7.2.3.16 AP: / ne, Configuration - ESO

− “Configuration - ESO”

FOXCST REFERENCE
7.2.3.17 AP: / ne, Configuration - PETS

− “Configuration - PETS”
7.2.4 AP: / ne, Fault Management

For the a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
management functions, please refer to FOXCST Operation Manual. The fol-
lowing table lists the fault causes of the AP: /.
Table 22: AP: / ne, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
USDF Save Of User Data Equipment  Major The process of saving user data from
Failed Alarm a voice application into the specific
user database on the NE has failed.
TLE NE Temperature Limit Equipment  Major The “exceed, set” temperature thresh-
Exceeded Alarm old that has been configured on NE
level has been reached or exceeded.
Also see section AP: / ne, Configura-
tion - Temperature Limits (on
page 56).
TLA NE Temperature Limit Equipment  Warning The “warning, set” temperature
Approaching Alarm threshold that has been configured on
NE level has been reached or
exceeded. Also see section AP: / ne,
Configuration - Temperature Limits
(on page 56).
PCSL All Selected PETS Communication  Minor The PETS has lost all clock sources
Clock Sources Lost Alarm that have been configured as selecta-
ble sources.
LOSP1 Loss Of Signal On PDH Communication  Warning The signal that has been configured
Clock Source 1 Alarm on the PETS clock source line 1 is
lost.
lost.
lost.
lost.
REDCOP CU Redundancy Com- Communication  Major A problem in the communication
munication Problem Alarm between the active core unit and the
standby core unit has been detected.
This might be due to a HW or SW
related problem on the CESM1
unit(s).

FOXCST REFERENCE
Table 22: AP: / ne, Fault Management (continued)

Affecting Severity
REDPAN Protecting CU Active Equipment  Major The redundant CESM1 core unit is
But Not Assigned Alarm available and active, but it is not
assigned. Make sure both CESM1 are
assigned.
REDPRA Protecting CU Active Equipment  Major The redundant CESM1 core unit is
Alarm active, i.e. a switch-over from the
default active core unit to the default
standby core unit has occurred.
SUF SNTP Unicast Failed Communication  Major The SNTP client has not received an
Alarm answer from its configured SNTP
server while in unicast mode.
SBF SNTP Broadcast Failed Communication  Major The SNTP client has not received an
Alarm SNTP broadcast message as
expected from its configured SNTP
server while in broadcast mode.
RSF RADIUS Server Failed Communication  Major The communication to the configured
Alarm RADIUS server has failed.
TNA System Time Not Avail- Equipment  Minor The system time has not been set, or
able Alarm the synchronisation to an SNTP
server has not been possible.
HWIC Hardware Incompatible Equipment  Major The available HW is not compatible
With Configuration Alarm with the required HW stored in the
database. You may need to change
the HW or re-create the NE configura-
tion.
SWIC Software Incompatible Equipment  Major The available NE SW is not compati-
With Configuration Alarm ble with the required SW stored in the
database. You may need to upgrade,
or downgrade the ESW, or re-create
the configuration with the currently
running ESW.
GSW General Software Equipment  Major An ESW internal error has been
Alarm Alarm detected that might inhibit the ESW
from running correctly.
MFA Maintenance Function Communication  Warning A maintenance function is active. Nor-
Active Alarm mally, maintenance functions are acti-
vated by an operator via the “status”
management function on a specific
AP.

FOXCST REFERENCE
7.2.5 AP: / ne, Status

7.2.5.1 AP: / ne, Status - Date And Time - Time
Table 23: AP: / ne, Status - Date And Time - Time

Set Date And Time Open the FOXCST dialogue to enter the date
and time.
Clock Time Date And Time yyyy-mm-dd T hh:mm:ss The «T» as delimiter between «dd» and «hh» is
predefined in the entry window.
Summary Local Host Time yyyy-mm-ddThh:mm:ss The local time for the FOXCST host is calculated
as UTC plus the time zone shift.
UTC yyyy-mm-ddThh:mm:ss Coordinated Universal Time
Local NE Time yyyy-mm-ddThh:mm:ss Current NE time
Time Zone <time zone> Shows the actually configured time zone, with
the time shift between UTC and the local NE
time.

FOXCST REFERENCE
7.2.5.2 AP: / ne, Status - Date And Time - SNTP Client
Table 24: AP: / ne, Status - Date And Time - SNTP Client
Primary Server Sta- Status Up The primary time server is up and reachable.
tus
Down The primary time server is down or not reacha-
ble. The NE has tried to contact the server, but
there was no response.
Unknown The primary time server state is unknown. This is
the default state which lasts till the first contact.
Secondary Server Status Up The secondary time server is up and reachable.
Status
Down The secondary time server is down or not reach-
able. The NE has tried to contact the server, but
there was no response.
Unknown The secondary time server state is unknown.
This is the default state which lasts till the first
contact.
The secondary time server is not contacted as
long the primary time server is up.
Last Response Date And Time yyyy-mm-ddThh:mm:ss Last time a message response arrived.
Time
Offset ns Offset between local and remote time in ns.
Last Jump Time Date And Time yyyy-mm-ddThh:mm:ss Last time a new time was set with a correction
which was bigger than 2 seconds.
Last Adjustment Date And Time yyyy-mm-ddThh:mm:ss Last time an adjustment occurred with a correc-
Time tion, which was between 20 ms and 2 seconds.

FOXCST REFERENCE
7.2.5.3 AP: / ne, Status - Date And Time - Time Source tbd
Table 25: AP: / ne, Status - Date And Time - Time Source tbd
Time Sources Source SNTP Client List of all time sources
Time Source 1
Time Source 2
Time Source 3
Time Source 4
APaddress <MO address> MO address of the time source.
Disabled time sources have an empty APad-
dress
Priority 1…8 Configured priority of the time source.
Disabled
Selected  The time source is selected or not.

Operational State Up The time source operational state is up or down.
Down
Time Source Switch Switch Event Coun- 0 … Number of time source switch-over events since
Events ter the last counter reset.
Reset Reset the switch event counter.
Get ToDExtTimeSr- Open the time source logbook.
cLogbook The time source logbook lists all time source
related events with the corresponding time
stamps.
7.2.5.4 AP: / ne, Status - Management Interface

− “Status - Management Interface”

FOXCST REFERENCE
7.2.5.5 AP: / ne, Status - Session Management

− “Status - Session Management”
7.2.5.6 AP: / ne, Status - Radius Client

− “Status - Radius Client”
7.2.5.7 AP: / ne, Status - IPSec

− “Status - IPSec”
7.2.5.8 AP: / ne, Status - Redundancy
The Status - Redundancy dialogue allows you to perform a manual or forced

switch-over from the working to the protecting CESM1 unit and vice versa.
A manual switch-over is performed if all conditions below are fulfilled:
• The protecting CESM1 unit is not isolated.
• The protecting CESM1 unit is present and assigned.
• The protecting CESM1 units database is compatible.
• The configuration database is saved.
• The protecting unit must be hardware compatible with the working unit.
The following requirements must be fulfilled that the two units are
deemed as hardware compatible:
− Identical unit function. The unit function is composed of the 5 first
characters of the unit name, e.g. CESM1. The unit name is available
at the AP:/ unit-x: Main - Equipment, Unit.
− Identical board identification, e.g. 382. The board identification is avail-
able at the AP:/ unit-x, Main - Inventory, Board ID.
− Identical hardware variant. The hardware variant is the truncation of
the hardware key divided by 256, e.g. 101/256 = 0. The hardware key
is available at the AP:/ unit-x, Main - Inventory, Hardware Key.
A forced switch-over is performed if all conditions below are fulfilled:
• The protecting CESM1 unit is not isolated.
• The protecting CESM1 unit is present and assigned.
• The protecting CESM1 units database is compatible.
For further information please refer to FOX61x CESM1.
Please note:
A switch-over affects traffic and leads to a service interruption. For informa-
tion about the switch-over time, please refer to FOX61x Product Features
and Characteristics.

FOXCST REFERENCE

A forced switch-over (command “Forced Switch”) may lead to a complete
interruption of the services, and may even interrupt the communication from
your management system to the network element, depending on the status
of the standby unit before switching.
→ It is strongly recommended to use the “Manual Switch” command for a
manual switch-over.
Table 26: AP: / ne, Status - Redundancy

NE Configuration Overall Configura-  The NE configuration has been saved to the
Status tion Status, Saved database of the active core unit and mirrored to
And Database Mir- the database of the redundant core unit.
rored
 Either the NE configuration has not yet been
saved or it has not yet been mirrored.
Detailed Configura- Not Saved The current configuration is not saved non-vola-
tion Status, NE tile on the NE
Save Status
User Data Not Saved Just some user data are not saved
Saved The current configuration is saved non-volatile
on the NE
Not Available The save status is unknown to the FOXCST
Incompatible The current NE configuration is incompatible
Backup Done A backup of the NE configuration was done

FOXCST REFERENCE
Table 26: AP: / ne, Status - Redundancy (continued)

Detailed Configura-  The NE database is mirrored, the standby core
tion Status, NE unit is ready to take over.
Database Mirrored
 NE database not mirrored, thus the standby core
unit is not ready to take over.
Core Unit Roles Active Unit /unit-11 Only equipped units are listed
/unit-13
Stand-By Unit /unit-11
/unit-13
Core Unit Status Redundant Unit  A redundant core unit is equipped
Present
 No redundant core unit is equipped
Protection Enabled  The core unit redundancy function is enabled
 The core unit redundancy function is disabled
All Components  The core unit redundancy function is enabled
Synchronised and the standby core unit is ready to take over.
 The standby core unit is not ready to take over.
Equipments Com-  The core unit equipment involved for redundancy
patible is compatible from a HW and SW point of view.
 The core unit equipment involved for redundancy
is not compatible either from a HW or from a SW
point of view.
Units Isolated  The standby core unit is currently isolated from
the protection group. The standby core unit is not
ready to take over.
 No core unit is currently isolated from the protec-
tion group. The standby core unit is ready to take
over
Manual Switch-Over The active core unit becomes the standby core
unit and vice versa.
This operation causes a user traffic interruption.
An appropriate warning is displayed.
Forced Switch-Over The active core unit becomes the standby core
unit and vice versa.
This operation causes a user traffic interruption.
An appropriate warning is displayed.
Isolate Units Command that removes the standby core unit
from the protection group, i.e. disables the
redundancy.
Join Units Command that re-activates the redundancy.

FOXCST REFERENCE
7.2.5.9 AP: / ne, Status - Temperature
tbd
Table 27: AP: / ne, Status - Temperature

Current Temperature -25 … 70 °C The currently measured temperature on the NE.
Max. Temperature -25 … 70 °C The maximum measured temperature on the NE
since the last «Reset Min.Max.» action.
Min. Temperature -25 … 70 °C The minimum measured temperature on the NE
since the last Reset «Min.Max.» action.
Reset Min.Max. Reset the memory for minimal and maximal tem-
perature
7.2.5.10 AP: / ne, Status - ESO

− “Status - ESO”
7.2.5.11 AP: / ne, Status - PETS

− “Status - PETS”

FOXCST REFERENCE
7.3 AP: / fan
7.3.1 AP: / fan, Overview

− “Overview - Active Alarms”
management function, please FOXCST Operation Manual.
7.3.2 AP: / fan, Main

7.3.2.1 AP: / fan, Main - General

7.3.2.2 AP: / fan, Main - Equipment
The Main - Equipment tab is standard except that there are no “Assign”,
“Unassign”, “Restart” and “Stop In Boot” commands, as there is no software
on this unit:
Table 28: AP: / fan, Main - Equipment

Operation Name Parameter Name Range Descriptions/Details
Equipment Status State Unknown Shows the current equipment state.
Empty
Plugged
OK
Incompatible
Failed
Not Applicable
Hardware FAMO1 Shows the hardware name.
FAMO1-F
FAMO2

FOXCST REFERENCE
Table 28: AP: / fan, Main - Equipment (continued)

Software <empty> This field is empty since the fan unit does not
have software.
Serial Number 0 … 31 characters Shows the serial number of the fan unit.
Manufacturer Name 0 … 31 characters Shows the manufacturer name of the fan unit.
Model Name 0 … 31 characters Shows the model name or number of the fan
unit.
7.3.2.3 AP: / fan, Main - Inventory

− “Main - Inventory”
Please note that the fan unit does not have a processor and hence does not
provide information in the following fields:
• Bootloader
• Processor
7.3.3 AP: / fan, Fault Management

management functions, please FOXCST Operation Manual. The following
table lists the fault causes of the current AP.
Table 29: AP: / fan, Fault Management

Affecting Severity
TBF Total Fan Breakdown Equipment false Critical A total failure of the fan unit has
Alarm occurred. For details, please refer to
section Total failure (on page 41).
PBF Partial Fan Breakdown Equipment false Minor A partial failure of the fan unit has
Alarm occurred. For details, please refer to
section Partial failure (on page 41).
FEF Fan Equipment Failure Equipment false Critical An equipment failure in the fan unit
Alarm hardware has been detected that is
not related to the fans.

FOXCST REFERENCE
7.4 AP: / fan / alarm-a
7.4.1 AP: / fan / alarm-a, Overview

− “Overview - Active Alarms”
7.4.2 AP: / fan / alarm-a, Main

7.4.3 AP: / fan / alarm-a, Configuration

7.4.3.1 AP: / fan / alarm-a, Configuration - General
Table 30: AP: / fan / alarm-a, Configuration - General

Polarity Polarity Active Closed Select this if you want the alarm is shown as
active for a closed alarm input contact.
Active Open Select this if you want the alarm is shown as
active for an open alarm input contact.
7.4.4 AP: / fan / alarm-a, Fault Management

management functions, please FOXCST Operation Manual. The following
table lists the fault causes of the current AP.
Table 31: AP: / fan / alarm-a, Fault Management

Affecting Severity
EAL External Alarm Environmental Alarm false Warning An external alarm has occurred. The cause for
this alarm depends on the circuit or equipment
connected to the alarm contacts for the respec-
tive alarm.

FOXCST REFERENCE
7.5 AP: / bridging tbd
For a description of the AP “/ bridging” with all its management functions and
its subordinate APs please refer to FOX61x Ethernet Services.
7.6 AP: / managementNetwork
For a description of the AP “/ managementNetwork” with all its management

functions and its subordinate APs please FOXCST Operation Manual.
7.7 AP: /unit-x
For all details of the APs “/unit-x” where “x” is the slot number in the FOX61x
subrack, please refer to the user manual of the type of unit you want to oper-
ate in the respective slot.
Please refer to FOX61x Release Notes for information on which units can be
operated in the FOX61x with the current release.

ANNEX
8 Annex
8.1 Associated FOX documents
1KHW002459 FOX615 Release Notes

1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002467 FOX61x TDM Services
1KHW002469 FOX61x CESM1
1KHW002473 FOX61x LEDE1
1KHW002476 FOX61x SAMO1
1KHW002478 FOX61x LEDS1
1KHW002477 FOX61x SAMO2

ANNEX

ANNEX

Contact us
ABB Switzerland Ltd

Power Systems
1KHW002464 © Copyright 2012 ABB. All rights reserved.

Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: utility.communication@ch.abb.com
www.abb.com/utilitycommunication

FOX61x SystemDescription 1KHW002464

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FOX61x SystemDescription 1KHW002464

Uploaded by

Copyright:

Available Formats

ABB Power Systems

Release History: Release 1: May 2012

Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHW002464

ABB Switzerland Ltd

5 Commissioning and operation 37

System Description ManualUser Guide 3

4 System Description ManualUser Guide

Figure 1: FOX615 view without front cover 11

System Description ManualUser Guide 5

1.2 Symbols and notations

This user manual uses the following symbols:

Indicates a possibly hazardous context. The possible hazard is indi-

Warns of hazardous circumstances. The hazard is specified.

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

System Description ManualUser Guide 7

1.4 Document history

Table 2: Document history

1.5 Definition of terms

Table 3: Specific terms and abbreviations

8 System Description ManualUser Guide

Table 3: Specific terms and abbreviations (continued)

System Description ManualUser Guide 9

Table 3: Specific terms and abbreviations (continued)

1.6 Feature licences

10 System Description ManualUser Guide

Figure 1: FOX615 view without front cover

System Description ManualUser Guide 11

Figure 2: FOX615 view with front cover mounted

Figure 3: FOX612 view without front cover

12 System Description ManualUser Guide

Figure 4: FOX612 view with front cover mounted

2.2 Network element description

The FOX61x is a network element can be used either as multiservice access

System Description ManualUser Guide 13

The FOX61x subrack is a 19-inch mountable subrack with 21 slots (FOX615)

2.2.1.2 Subrack capacity and slots

14 System Description ManualUser Guide

Figure 5: FOX61x with CU and SU

2.2.1.3 Subrack cooling

System Description ManualUser Guide 15

2.2.1.4 Subrack powering

2.3 Control functions

2.3.1 Unit control

2.3.2 Management communication

16 System Description ManualUser Guide

3.2 FOX units for passive cooling operation

Attention to temperature range!

Table 4: Active or passive cooling FOX units

Attention to temperature range!

System Description ManualUser Guide 17

Table 5: Active and passive cooling FOX units

18 System Description ManualUser Guide

4.1.1 Initial management connection

The following prerequisites and steps have to be performed:

4.1.2 Local management connection

System Description ManualUser Guide 19

Network element management is done with the element manager FOXCST,

Risk of operating trouble!

4.1.3 Remote management connection

20 System Description ManualUser Guide