FOX61x CESM1 1KHW002469

ABB Power Systems
FOX61x
CESM1, CESM1-F
User Manual
User Manual FOX61x
CESM1, CESM1-F
Release History: Release 1: December 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.: 1KHW002469
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 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
2 Introduction 9
2.1 General 9
2.2 Unit View 11
2.3 Block diagram 11
3 Specification 13
3.1 Feature licences 13
3.2 CESM1 function overview 13
3.3 CESM1-F function overview 16
3.4 Versions 17
4 Installation 19
4.1 Prerequisites 19
4.2 Slots 20
4.3 Compatibility 21
4.4 Connections and cables 21
5 Functional description 29
5.1 Applications 29
5.2 Interfaces 33
5.3 Equipment protection EQP (core unit redundancy) 37
6 Commissioning 39
6.1 Commissioning prerequisites for CESM1 39
6.2 First ESW download to a CESM1 unit 40
6.3 Configuring an external Ethernet port 43
6.4 Commissioning RSTP 45
6.5 Commissioning MSTP 45
6.6 Core unit redundancy 46
7 Operation and maintenance 47

7.1 Unit Optical Indicators 47
CESM1, CESM1-FUser Manual 3

7.2 Maintenance 49
7.3 Unit and network element ESW download 49
7.4 Setting up mirror ports 54
7.5 RSTP status 55
7.6 MSTP status 55
7.7 Redundancy 56
8 FOXCST reference 57
8.1 Introduction 57
8.2 AP: / unit-x: CESM1 60
8.3 AP: / unit-x / neController 62
8.4 AP: / unit-x / neController / esi-y 64
8.5 AP: / unit-x / port-a 65
8.6 AP: / unit-x / port-a / mau 74
8.7 AP: / unit-x / iports 75
8.8 AP: / unit-x / iports / iport-b 75
8.9 AP: / unit-x / iports / iport-b / mau 82
9 Annex 83
9.1 Associated documents 83
4 CESM1, CESM1-FUser Manual

Figures
Figure 1: CESM1 unit application with a subtending FOX 10

Figure 2: CESM1 (left) and CESM1-F (right) unit view 11
Figure 3: Block diagram of CESM1 12
Figure 4: FOX subracks with core unit CESM1 in slot 11 20
Figure 5: FOX subracks with core unit CESM1 in slot 11 and redundant core unit CESM1 in slot 13 21
Figure 6: CESM1 (left) and CESM1-F (right) front panel and interface connectors 22
Figure 7: Ethernet link LEDs on the electrical Ethernet interfaces 23
Figure 8: Side view of the subrack including cabling and cable tray 27
Figure 9: Management traffic access on the CESM1 unit 30
Figure 10: Jumper position and setting for esi-1 and esi-2 36
Figure 11: Fault and status indication LEDs on the CESM1 unit 47
Figure 12: MOM for CESM1 58

PREFACE
1 Preface
1.1 Precautions and safety
Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety
requirements as defined in EN 60950 (Safety of Information Technology
Equipment).
Please refer to the following document:
1KHW002497 FOX61x Precautions and Safety.
1.2 Symbols and notations
This User Manual uses the following symbols:
Risk of operating trouble!

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

CESM1 interface Circuit category according to Max. rating
EN 60950-1 Voltage Current
Local power supply TNV2 < 72 VDC < 2.0 A
Electrical Gigabit or SELV <3V < 10 mA
Fast Ethernet
Synchronization SELV <3V < 10 mA

PREFACE
Table 2: Optical interfaces a

CESM1 interface Parameter Max. rating
Remarks
b
Optical Gigabit and Laser class 1
10 Gigabit Ethernet (according to EN 60825-1)
Optical transmitted power c - 7 dBm
Transmitted wavelength 850 nm, non-visible
1310 nm, radiation
1550 nm
a. The listed optical properties are related to the SFPs plugged in the CESM1 unit.
b. As the laser protection class 1 is complied, dangerous radiation cannot be emitted.
Thus, special precautions for failures or laser warnings are not necessary.
c. Optical transmitted power, modulation and wavelengths are typical values for SFP/
SFP+ modules, however these values may vary depending on SFP/SFP+ types
and manufacturers.
Please refer to SFP/SFP+ manufacturers data sheets for more details.
1.4 Document history
Table 3: Document history

Date FOX Changes since previous version
release
December 2012 R1 First version of the document for the FOX61x release.
1.5 Definition of terms
For an explanation of terms used in this document please refer to

1KHW028514 FOX61x Abbreviations and Terms.

INTRODUCTION
2 Introduction
This section presents a general introduction to the use of this document and
the unit it describes.
The section is closed with a unit view in section Unit View (on page 11) and
a block diagram in section Block diagram (on page 11).
2.1 General
This document describes the architecture and functions of the CESM1 and
CESM1-F units and shows, how these units are commissioned and operated
as part of the FOX.
This document is restricted to the unit related aspects. Network element
related functions are described in the following documents:
• 1KHW002464 FOX61x System Description:
Generic network element related functions as e.g. time of day manage-
ment or temperature supervision.
• 1KHW002466 FOXCST Operation:
FOX element manager (FOXCST) and management access related func-
tions.
• 1KHW002468 FOX61x Ethernet Services:
FOX chassis switch architecture, switching related functions and layer 2
protocols, as e.g. RSTP.
• 1KHW002467 FOX61x TDM Services.
FOX TDM traffic architecture and functions for PDH and SDH.
The CESM1 is the 1 slot wide core and control unit for the multiservice
access nodes FOX615 and FOX612, that must be operated in actively
cooled subracks. The CESM1-F is a 2 slot wide functional equivalent to the
CESM1 unit that can be operated in passively cooled subracks.
The CESM1 and CESM1-F units combine the typical management functions
of a core unit like embedded software distribution, system alarming, perfor-
mance monitoring, etc., with an Ethernet switch including VLAN functionality.
The CESM1 and CESM1-F units provide several interface types in the front
panel like SFP/SFP+ cages for backhaul connectivity, electrical GbE as for
subtending FOX systems or co-located Ethernet equipment, electrical FE for
management purposes and micro D-Sub 9 for synchronization.

INTRODUCTION
FOX
Ethernet
ETOP1 / Ethernet Packet
DTE ELET1 Network
Ethernet ETOP1 /
DTE ELET1
CESM1
Ethernet ETOP1 /
DTE ELET1
Ethernet ETOP1 / Ethernet

DTE ELET1
FOX
Ethernet ETOP1 / Ethernet
DTE ELET1
CESM1
Figure 1: CESM1 unit application with a subtending FOX
The network elements FOX615 and FOX612 permit full redundancy of the
control unit and its traffic interfaces when operated in slot 11 by inserting and
configuring a second control unit in slot 13.
The details described in this document base on a specific CESM1 or
CESM1-F embedded software (ESW) version. For more details about the
ESW version required for the described functionality, please refer to
1KHW002459 FOX61x Release Notes.

INTRODUCTION
2.2 Unit View
Figure 2: CESM1 (left) and CESM1-F (right) unit view
Figure 2 shows the CESM1 and CESM1-F units with their front panels and
interfaces. On the front plate are four LEDs for unit- and traffic status indica-
tion.
2.3 Block diagram
The figure below shows the functional block diagram of the CESM1 unit. For
more information regarding these functions, please refer to section Func-
tional description (on page 29).

INTRODUCTION
1… 5
Front Connector
1GbE/10GbE access
20x1GbE 3x1GbE
2x10GbE Trunk IF, 2x1GbE/10GbE
Switching Subtending IF,
Management IF
CPU 1 …2
Front Connector
Unit
Synchronisation
Sync
& Redundancy
Control
PBUS access
Front Connector
Routing 1
CPU Local
1xFE
NE Management IF
Backplane access
Subrack Optical
internal Alarm Alarm indicator
communication (4 LEDs)
Power
Figure 3: Block diagram of CESM1

SPECIFICATION
3 Specification
The CESM1 unit uses the following feature licences, provides the functions
listed below and conforms to the corresponding standards and recommenda-
tions (conformance to applicable parts of the standards).
3.1 Feature licences
This unit is subject to one or several feature licences. The following licences
are available for this unit.
Table 4: Feature licences relevant for this unit

Licence ID Short Description Description
CESM_10GbE Lic CESM1 10GbE usage FOX Feature Licence for using 10GbE uplink with CESM1 unit
- right to use per card
For more information on feature licences please refer to 1KHW002459

FOX61x Release Notes.
3.2 CESM1 function overview
The CESM1 unit provides the following functions and supports the following
standards:
Table 5: CESM1 function overview - system features

Feature Rating or standard Release
Central management point for the FOX615 network ele- r1a
ment
Central management point for the FOX612 network ele- r1a
ment
Embedded software download r1a
Alarm collection and notification r1a
Syslog, sources and destinations RFC 3164 r1a
External alarm interfacing via backplane and manage- r1a
ment
Unit configuration delivery r1a
Synchronization interface inputs 2 r1a
- Frequency 2.048 MHz
- Connector type Micro D-Sub
- Impedance 120 Ω according to ITU-T G.703
Synchronization interface outputs 2
- Frequency 2’048 kHz
- Connector type
Micro D-Sub
- Impedance
120 Ω according to ITU-T G.703

SPECIFICATION
Table 5: CESM1 function overview - system features (continued)

th
SFP modules INF-8074 (12 May 2001), r1a
Specification for SFP (Small Form factor Pluggable)
Transceiver
SFP+ modules SFF-8431 (6th July 2009), r1a
Specifications for Enhanced Small Form Factor
Pluggable Module SFP+
SFP DDM (Digital Diagnostic & Monitoring) r1a
SFP+ DDM (Digital Diagnostic & Monitoring)
- CESM1 unit redundancy (future release)
Table 6: CESM1 function overview - management interfaces

Electrical Gigabit Ethernet ports: 10BASE-T, 100BASE-TX, 1000BASE-T r1a
- Number of ports 3
- Connector type RJ45
- Impedance 100 ± 15 Ω, frequency band 1 … 16 MHz
Optical Gigabit Ethernet ports: 1000BASE-SX/-LX/-EX/-ZX r1a
10GBASE-LR a
- Number of ports 2
- Connector type (1000BASE-xx) SFP, complying with [INF-8074] specification
- Connector type (10GBASE-xx) SFP+, complying with [SFF-8431] specification
Local management port: 10BASE-T, 100BASE-TX r1a
- Number of ports 1
- Connector type RJ-45
Remote authentication via RADIUS server r1a
Routing Static routing r1a
OSPF
- Number of bridge interfaces 1 r1a
- Number of TDM interfaces 16 r1a
- Capacity of the TDM interfaces up to 2 Mbit/s per interface (P12 or P0_nc) r1a
up to 16 Mbit/s total
a. 10GBASE-SR and -ER SFP+ modules will be available in a future release
Table 7: CESM1 function overview - Ethernet switching

Gigabit Ethernet switching IEEE 802.3-2008, CSMA/CD access method and r1a
physical specifications
IEEE 802.3z-1998, Gigabit Ethernet
Synchronous Ethernet Will be available in a future release
Electrical Gigabit Ethernet ports: 10BASE-T, 100BASE-TX, 1000BASE-T r1a
- Number of ports 3
- Connector type RJ45

SPECIFICATION
Table 7: CESM1 function overview - Ethernet switching (continued)

Optical Gigabit Ethernet ports: 1000BASE-SX/-LX/-EX/-ZX r1a
10GBASE-LR a
- Number of ports 2
- Connector type (1000BASE-xx) SFP, complying with [INF-8074] specification
- Connector type (10GBASE-xx) SFP+, complying with [SFF-8431] specification
VLAN support IEEE 802.1Q-1998, Virtual bridged Local Area Net- r1a
works
Port VLAN
VLAN QoS with Class of Service IEEE 802.1p, Traffic Class Expediting and Dynamic r1a
Multicast Filtering (in 802.1D-1998)
QoS Priority scheduler, r1a
- Strict priority
- Shaped Deficit Weighted Round Robin
Multiple Spanning Tree Protocol (MSTP), with configur- IEEE 802.1Q-2011, Media Access Control (MAC) r1a
able Bridges and Virtual Bridge Local Area Networks
- Port cost
- Port priority
- Dynamic path cost
Rapid Spanning Tree Protocol (RSTP), with configur- IEEE 802.1D-2004, Media Access Control (MAC) r1a
able Bridges, section 17
- Port cost
- Port priority
- Dynamic path cost
Spanning Tree Protocol (STP) compatibility IEEE 802.1D-1998, Media Access Control (MAC) r1a
Bridges,
802.1t MAC bridges Amendment 1
a. 10GBASE-SR and -ER SFP+ modules will be available in a future release
Table 8: CESM1 function overview - fault management

Fault management ITU-T X.733, Alarm Reporting r1a
Table 9: CESM1 function overview - equipment features

a
Power consumption r1a
- Power supply range VBAT refer to 1KHW002460 FOX61x Product Features
and Characteristics
- Current consumption (typical with max. traffic load)
at VBAT = -48VDC 0.62 A
- Maximum total power requirements from battery,
at VBAT = nominal voltage 30 W
Mechanical parameters r1a
- Construction practice 19 inches
- Height of the unit (1 HU = 44.45mm) 6 HU
- Width of the unit (1 TE = 5.08mm) 4 TE (1 slot)
- Size of the PCB (H x D) 233 mm x 220 mm
- Weight of the CESM1 unit
434 g
Unit cooling Operation with fan unit (active ventilation r1a

SPECIFICATION
Table 9: CESM1 function overview - equipment features (continued)

Reliability r1a
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 46 years
a. The given power consumption figures are without SFP/SFP+ modules. The power
consumption of a SFP/SFP+ module is up to 1 W
Table 10: CESM1 function overview - other standards

Emission refer to 1KHW002460 FOX61x Product Features and Characteristics r1a
Immunity refer to 1KHW002460 FOX61x Product Features and Characteristics r1a
Safety refer to 1KHW002460 FOX61x Product Features and Characteristics r1a
SFP/SFP+ modules:
according to the manufacturer’s data sheets (typically IEC 60825-1 Class 1
laser product)
Ambient conditions refer to 1KHW002460 FOX61x Product Features and Characteristics r1a
Error free operation up to 60°C ambient temperature is only guaranteed
with SFP/SFP+ modules specified for the industrial temperature range (up
to 85°C).
3.3 CESM1-F function overview
The CESM1-F unit provides the same functions and supports the same
standards as the CESM1 unit, with the following exceptions:
Table 11: CESM1-F function overview - equipment features

Mechanical parameters r1a
- Width of the unit (1 TE = 5.08mm) 8 TE (2 slots)
- Weight of the CESM1-F unit 1’700 g
Unit cooling Operation without fan unit (passive ventilation). r1a
Vertical mounting of the units is mandatory.
Reliability r1a
- Calculated MTTF at 35 °C (MIL-HDBK-217F) 23 years
Table 12: CESM1-F function overview - other standards

Ambient conditions refer to 1KHW002460 FOX61x Product Features r1a
and Characteristics
Error free operation up to 55°C ambient tempera-
ture is only guaranteed with SFP/SFP+ modules
specified for the industrial temperature range (up to
85°C).

SPECIFICATION
3.4 Versions
For detailed information about the released CESM1 hardware (HW) and
embedded software (ESW) versions supporting all the previously mentioned
features, please refer to 1KHW002459 FOX61x Release Notes.

SPECIFICATION

INSTALLATION
4 Installation
This section describes how to install the CESM1 core unit in a FOX and the
connectors and cables that are required for installation.
4.1 Prerequisites
Before installing a CESM1 unit take care to follow the safety advice as listed
in 1KHW002497 FOX61x Precautions and Safety.
For the installation of FOX HW, refer to 1KHW002461 FOX615 Installation or
refer to 1KHW002462 FOX612 Installation.
The required local manager (FOXCST) version to commission and operate
the FOX system must be according to 1KHW002459 FOX61x Release
Notes.
Along with this FOXCST version, two embedded softwares (ESW) according
to 1KHW002459 FOX61x Release Notes must be installed in the CESM1
unit:
Table 13: ESW types for the CESM1 unit

ESW name ESW application
cesun_rxxxx Unit control and operation
cesne_rxxxx Network element control and operation
Please note:
The unit ESW and network element ESW must be operated as pairs, i.e.
having the same release designation.
→ E.g. use the ESW cesun_r1axx and cesne_r1ayy, where the “r1a” part
of the ESW names must match.
Valid combinations of hardware (HW) and embedded software (ESW) ver-
sions are given in 1KHW002459 FOX61x Release Notes.
For a description of the first ESW download and assignment to the CESM1
unit please refer to 1KHW002465 FOXCST Installation.
For a general description of the ESW download and assignment to a CESM1
unit which is already in service please refer to 1KHW002466 FOXCST Oper-
ation.
For a specific description of the ESW download and assignment to a CESM1
unit which is already in service or to a redundant CESM1 unit please refer to
section Unit and network element ESW download (on page 49).
For a description of how to bring the unit ESW or the network element ESW
of a CESM1 unit which is already in service into the bootloader state please
refer to section Unit and network element ESW download (on page 49).

INSTALLATION
4.2 Slots
For FOX systems with only one CESM1 unit, this unit must be placed in slot
11, as shown in Figure 4. All other slots can be equipped with service units
(SU).
Please note:
The CESM1-F unit occupies slot-11 and slot-12 in the FOX subrack.
FOX615 FOX612
Slot Slot Slot Slot Slot Slot
1 11 21 7 11 14
C C
E E
S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
U U U U U U U U U U M U U U U U U U U U U U U U U M U U U
1 1

1 11 21 7 11 14
C C
E E
S S
S S S S S S S S S S M S S S S S S S S S S S S S M S S
U U U U U U U U U U U U U U U U U U U U U U U U U
1 1
- -
F F
Figure 4: FOX subracks with core unit CESM1 in slot 11
In systems with an additional, redundant core unit (future release), the

redundant CESM1 is placed in slot 13 as shown in Figure 5. All other slots
can be equipped with service units (SU).

INSTALLATION
Please note:
The CESM1-F units occupy slot-11 to slot-14 in the FOX subrack.
FOX615 FOX612
1 11 21 7 11 14
C C C C
E E E E
S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
U U U U U U U U U U M U M U U U U U U U U U U U U M U M U
1 1 1 1

1 11 21 7 11 14
C C C C
E E E E
S S S S
S S S S S S S S S S S S S S S S S S S S S
U U U U U U U U U U M M U U U U U U U U U U U M M
1 1 1 1
- - - -
F F F F
Figure 5: FOX subracks with core unit CESM1 in slot 11 and redun-
dant core unit CESM1 in slot 13
4.3 Compatibility
4.3.1 FOX units

CESM1 is compatible with any other FOX unit with an ESW release of the
FOX system release R1 or later. Please refer to 1KHW002459 FOX61x
Release Notes.
4.3.2 Previous ESW revisions

The CESM1 unit with ESW release ci5xx_r1c is the first release for the FOX
release R1.
4.4 Connections and cables
4.4.1 Front connector of the CESM1 unit

The CESM1 front panel connections are implemented as shown in Figure 6.

INSTALLATION
Fixing screw
Pull-out handle with

CESM1 R1B CESM1-F R1B
37900374 37900374 identification label
Optical status indications
micro-D-Sub 9-pin female connector: Pin External Synchronization

(synchronization interfaces) 1 Input ESI-2 a
pin 6 pin 1 2 Input ESI-1 a
3 GND
4 Output ESO-2 a
pin 9 pin 5 5 Output ESO-1 a
6 Input ESI-2 b
7 Input ESI-1 b
8 Output ESO-2 b
RJ-45 8-contact female connector :
9 Output ESO-1 b
Electrical 10/100BASE-TX interface
(local management port)
port-5 RJ-45 8-contact female connectors:

Electrical 10/100/1000BASE-T interfaces
(traffic interfaces )
port-4 pin 1 10/100Base-T 1000Base-T

Pin
MDI MDI-X MDI MDI-X
1 Tx+ Rx+ D1+ D2+
pin 8
2 Tx- Rx- D1- D2-
port-3 3 Rx+ Tx+ D2+ D1+
4 D3+ D4+
5 D3- D4-
6 Rx- Tx- D2- D1-
7 D4+ D3+
8 D4- D3-
port-2
SFP/SFP+ module cages:
Optical GbE or 10GbE interfaces
(traffic interfaces )
port-1
Tx
Rx
Pull-out handle
Fixing screw
Figure 6: CESM1 (left) and CESM1-F (right) front panel and interface
connectors
The electrical Ethernet interfaces provide two LEDs indicating the link activity
state and the link state:

INSTALLATION
Activity
Link
Figure 7: Ethernet link LEDs on the electrical Ethernet interfaces
The activity LED has the following states:

− Yellow blinking: Traffic activity.
− Dark: No traffic.
The link LED has the following states:
− Green: 10/100/1000 Mbit/s link up.
− Dark: Link down.
4.4.2 SFP+ 10GbE optical modules and cables

The 10GbE optical interfaces on CESM1 consist of two SFP+ (Small Form
factor Pluggable Plus) module cages.
The CESM1 unit only provides the mechanical infrastructure for SFP+ mod-
ules: This is a cage and a host board connector. CESM1 allows hot swap-
ping of SFP+ modules.
Please note:
SFP+ modules must be fully MSA (Multi-Source Agreement) compliant [SFF-
8431]. Please note that only ABB’s recommended SFP+ modules should be
used in order to guarantee inter-working with the CESM1 unit.
The recommended SFP module types are:
• 10GBASE-SR (850 nm) (available in a future release)
• 10GBASE-LR (1310 nm)
• 10GBASE-ER (1310 nm) (available in a future release)
The selection of the transceiver and the media type will determine the maxi-
mum distance allowed according to the transmission media specifications.
For details on connectors and pins for this interface, please refer to [SFF-
8431].
SFP+ modules plugged into the CESM1 operate by default in “auto negotia-
tion” PHY mode.
Please note:
10GbE optical interfaces only support 10’000 Mbit/s Full Duplex fixed opera-
tion mode.
SFP+ DDM (Digital Diagnostic & Monitoring) is supported on the SFP+ mod-
ules that are plugged in the SFP cages of the CESM1 unit provided that the
module itself is supporting this feature.
The optical 10GbE interfaces (SFP+ modules) are equipped with industry
standard duplex LC connectors. Connection to other types of connectors as

INSTALLATION
e.g. SC or FC-PC is possible with converter cables (optical jumpers) or via

an optical distribution frame.
The CESM1 unit performs as specified
• with optical multimode fibres conforming to ITU-T G.651.1 recommenda-
tion (850 nm SFP), or
• with optical single mode fibres conforming to the ITU-T G.652 recommen-
dation with a differential group delay value ≤ 0.5 ps/√km (1310 nm and
1550 nm SFP).
4.4.3 SFP GbE optical modules and cables

The GbE optical interfaces on CESM1 consist of two SFP (Small Form factor
Pluggable) module cages.
The CESM1 unit only provides the mechanical infrastructure for SFP mod-
ules: This is a cage and a host board connector. CESM1 allows hot swap-
ping of SFP modules.
Please note:
SFP modules must be fully MSA (Multi-Source Agreement) compliant [INF-
8074]. Please note that only ABB’s recommended SFP modules should be
used in order to guarantee inter-working with the CESM1 unit.
The recommended SFP module types are:
• 1000BASE-SX (850 nm)
• 1000BASE-LX (1310 nm)
• 1000BASE-EX (1310 nm)
• 1000BASE-ZX (1550 nm)
The selection of the transceiver and the media type will determine the maxi-
mum distance allowed according to the transmission media specifications.
For details on connectors and pins for this interface, please refer to [INF-
8074].
SFP DDM (Digital Diagnostic & Monitoring) is supported on the SFP mod-
ules that are plugged in the SFP cages of the CESM1 unit provided that the
module itself is supporting this feature.
The optical 1GbE interfaces (SFP modules) are equipped with industry
standard duplex LC connectors. Connection to other types of connectors as
e.g. SC or FC-PC is possible with converter cables (optical jumpers) or via
an optical distribution frame.
The CESM1 unit performs as specified
• with optical multimode fibres conforming to ITU-T G.651.1 recommenda-
tion (850 nm SFP), or
• with optical single mode fibres conforming to the ITU-T G.652 recommen-
dation with a differential group delay value ≤ 0.5 ps/√km (1310 nm and
1550 nm SFP).
4.4.4 Electrical Ethernet interface cable

CESM1 provides three electrical Ethernet traffic interfaces according to IEEE
802.3, 802.3u and 802.3ab specifications, and they support:
• 10BASE-T
• 100BASE-TX

INSTALLATION
• 1000BASE-T
CESM1 provides one electrical Ethernet local management port according to
IEEE 802.3 and 802.3u specifications, and it supports:
• 10BASE-T
• 100BASE-TX
All four interfaces are presented as RJ-45 connectors with automatic crosso-
ver functionality so they may be connected to both host and switch inter-
faces. Therefore both, crossover and straight cables can be used.
Please note:
For error free transmission, category 5e SF/UTP Ethernet cables are
required at least. This assumes that the equipment on the remote end also
supports transmission on category 5e cables. If this is not the case, we rec-
ommend the use of category 6 cables.
Electrical 10BASE-T/100BASE-TX/1000BASE-T ports on CESM1 support
auto-negotiation with parallel detection.
Auto-Negotiation allows the highest performance mode to be automatically
selected on a given link.
Please note:
CESM1 Ethernet electrical interfaces are configured in auto negotiation
mode by default.
Please note:
With auto negotiation switched off, a crossed cable has to be used to con-
nect to another CESM1 since the interface cannot automatically select the
mode.
The following table shows the behaviour of CESM1 when connecting an
external Ethernet device:
Table 14: CESM1 mode of operation

CESM1 mode External Equipment mode CESM1 election
Auto negotiation Auto negotiation 1000 Mbit/s Full Duplex
Auto negotiation 1000 Mbit/s Full Duplex 1000 Mbit/s Full Duplex
Auto negotiation 1000 Mbit/s Half Duplex 1000 Mbit/s Half Duplex

INSTALLATION
Please note:
When using LACP (future release), full duplex is mandatory.
Please note:
When connecting Ethernet ports configured in manual mode (no auto-negoti-
ation) to Ethernet ports in auto-negotiation mode, the link may be up but the
duplex settings may be inconsistent. This can result in poor throughput per-
formance on the link.
The previous note applies to any Ethernet device and is a consequence of
the behaviour of Auto-Negotiation and Parallel Detection. When a port sup-
porting auto-negotiation is connected to a port not supporting auto-negotia-
tion, the port supporting auto-negotiation will revert to parallel detection: This
can detect the link type (10BASE-T or 100BASE-TX) but will assume half-
duplex operation (reference IEEE 802.3 clause 28.2.3.1 note 2). If the far
side port is manually configured in full-duplex mode, then there is an incon-
sistent configuration and the side operating in half-duplex may experience
collisions while transmitting data.
Please note:
Ethernet cables can be ordered from ABB.
4.4.5 Synchronization interface cable

The synchronization interface permits to connect the following signals
according to ITU-T G.703:
• two symmetrical clock inputs (2048 kHz):
− ESI-1,
− ESI-2.
• two symmetrical clock outputs (2048 kHz):
− ESO-1,
− ESO-2.
The interface is implemented on CESM1 by means of a micro D-Sub con-
nector.
Please note:
This cable can be ordered from ABB.
4.4.6 Cable fixing

In the FOX615, cables connecting to the CESM1 unit or other units in gen-
eral should be guided and attached to the cable tray as indicated in Figure 8.
For more detailed information, please refer to 1KHW002461 FOX615 Instal-
lation.

INSTALLATION
Figure 8: Side view of the subrack including cabling and cable tray
In the FOX612, cables connecting to the CESM1 unit or other units should
be guided and attached similarly to the way shown in Figure 8 above. For
more detailed information, please refer to 1KHW002462 FOX612 Installa-
tion.
4.4.7 Cabling with CESM1 redundancy

When using a redundant core unit in slot 13 (future release), cabling is differ-
ent. Since the core unit HW is duplicated, some of the front connections
have to be duplicated as well. The cables that have to be connected twice
are the following:
• Ethernet cable to the local management port
The Ethernet cables to the two CESM1 units can be connected e.g. via
an Ethernet switch to the local manager. Note that the two management
ports of the two CESM1 units have fixed IP addresses:
− CESM1 unit in slot-11: 192.168.1.1.
− Redundant CESM1 unit in slot-13: 192.168.1.2.
The Ethernet local management port on the standby core unit is disabled.
The Ethernet local management port on core unit running in the network
element bootloader is enabled.
• Synchronization input (ESI) interface cable

INSTALLATION
The ESI input is terminated with a 120 Ohm termination resistor. In case
the two inputs on the working CESM1 unit and on the redundant CESM1
unit are connected in parallel, one of the two inputs should have high
impedance. Refer also to section Synchronization interface (on page 35).
• Ethernet cables to the traffic interfaces
For maximum protection against failures, also electrical and optical
cables from a switching or routing device to ports 1 to 5 of the CESM1
unit need to be connected to both units, the working and the standby
CESM1. In this case, RSTP or MSTP might be required. Please read the
important note on RSTP/MSTP configuration in section Equipment pro-
tection EQP (core unit redundancy) (on page 37).

FUNCTIONAL DESCRIPTION
5 Functional description
This section provides a functional description of the CESM1 core unit and its
interfaces. For the description of a configuration example refer to section
Commissioning (on page 39).
5.1 Applications
The CESM1 core unit controls the configuration and operation of the FOX
system, maintains an updated database with relevant information for each
configured unit and it performs Ethernet switching between every Ethernet
service unit as part of the FOX chassis switch.
It also provides redundancy through 1:1 equipment protection when two core
units are plugged and configured (future release). The following sections
cover these aspects in more detail.
5.1.1 Hardware control

One of the main functions of the CESM1 unit is to control the service units at
hardware level. This comprises the following functions:
• Check the presence of service units
• Supervise the core unit redundancy status
• Activate/deactivate the units
• Reset the units
• Read the unit alarm status
• Read the unit inventory data
• Provide clock information
• Control signals to the redundant CESM1
5.1.2 System management

System management is an important function that affects all units in a run-
ning system. Each unit of the NE contributes to the management functions:
• Inventory management
• Configuration management
• Status
• Fault management
• Performance management
The CESM1 core unit has some particular functions for the management of
the system:
• Loading an NE system configuration and making it effective (configura-
tion management)
• Monitoring all the unit functions, collection and classification of the fail-
ures and creation of triggers for consequent actions (fault management)
• Management communication with the outside world to allow local and
remote operation and maintenance of the NE, i.e. support of all the pro-
vided management functions

NE management is a system level function and is described in 1KHW002466

FOXCST Operation.
5.1.3 Management traffic and routing

CESM1
NE Management
- accessible from the Local Management Port with the
IP Address A .
VLAN untagged traffic
- accessible from all other router ports with the
IP Addresses B , and C to R .
Local Mgmt P12 transport
Port tdmInterfaces/ppp-1
- IP Address = A OSPF Router - IP Address = C
P12/P0-nc
PBUS
Element Manager vlanInterface:
- IP Address = B tdmInterfaces/ppp-16 P12/P0-nc
- VLAN ID = Mgmt-VID - IP Address = R
NE management via Ethernet
Implicit Access Port NE management via a TDM link

VLAN untagged traffic (not shown in the AP tree ;
with PVID = Mgmt-VID) IP traffic is routed between the
vlanInterface and the tdmInterfaces
.
Packet Access Port The Local Management Port cannot

become an OSPF router interface.
Network - PVID = Mgmt-VID
Bridge
(Chassis Switch)
Packet
Trunk Port
Network
VLAN tagged traffic with VID= Mgmt-VID.

The Mgmt-VID must be added to the Bridge
Figure 9: Management traffic access on the CESM1 unit
5.1.3.1 Ethernet remote management
When connecting FOX to a routed network, inband management traffic can

be forwarded to a traffic port of the CESM1 or to any other Ethernet port of
the FOX chassis switch.
If the inband management traffic is VLAN tagged, the management traffic
accesses the FOX chassis switch via a “trunk” port, a “trunk with native
VLAN” port or a “general” port supporting tagged Ethernet frames. The man-
agement traffics VLAN ID must be the same as configured in the vlanInter-
face of the FOX Management Interface (FOXCST Management Interfaces,
managementNetwork/vlanInterface). The management VLAN ID must also
be added to the bridge (FOXCST Switching, Switching/Bridges/bridge-1,
VLANs).
The NE management VLAN ID for management can be configured in the
range 1 … 4089. It is not recommended to use the default VLAN ID 1 as the
management VLAN ID.
If the inband management traffic is untagged, the management traffic
accesses the FOX chassis switch via an “access” port, a “trunk with native
VLAN” port or a “general” port supporting untagged Ethernet frames. The
port VLAN ID of the access ports (PVID) must be the same as configured in
the vlanInterface of the FOX Management Interface (FOXCST Management
Interfaces, managementNetwork/vlanInterface).

The FOX can also be managed via up to 16 TDM interfaces of the CESM1
router using the PPP protocol (FOXCST Management Interfaces, manage-
mentNetwork/tdmInterfaces/ppp-x).
Management traffic is routed between the routers VLAN interface and the
TDM interfaces.
Please note:
For the configuration of the management VLAN ID, refer to 1KHW002466
FOXCST Operation.

Changing the management VLAN ID can result in loss of the management
connections, depending on the network topology.
Please note:
For further information on the management connections and the manage-
ment routing functions of the FOX, please refer to 1KHW002465 FOXCST
Installation and 1KHW002466 FOXCST Operation.
5.1.3.2 Ethernet local management
Local management access is provided via the Local Management Port,

implemented with a 10/100BASE-TX Ethernet port. The Ethernet interface
supports autonegotiation with half- and full-duplex mode and automatic MDI/
MDIx switchover.
The IP address is fixed to 192.168.1.1 (CESM1 plugged in slot-11) or
192.168.1.2 (redundant CESM1 plugged in slot-13) 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.3 to 192.168.1.254.

The IP addresses of the local management ports are 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.
Management traffic accesses the Router with untagged Ethernet traffic. The
Local Management Port cannot become an OSPF router interface. Further-
more the 192.168.1 subnet will not be distributed by the router as connected
network.
5.1.4 Switching
The CESM1 unit provides five external Ethernet interfaces acting as FOX
chassis switch ports:
• three electrical GbE for electrical GbE, and
• two SFP/SFP+ modules for optical or electrical GbE or optical 10GbE.
Moreover, it has 20 internal ports in the backplane of 1 Gbit/s each granting
access to every other unit in the subrack, connecting the Ethernet switch
devices being part of the chassis switch or connecting Ethernet switch
devices not being part of the chassis switch.

The CESM1 unit has also two internal ports of 10 Gbit/s connecting a redun-
dant CESM1 unit (future release).
CESM1 permits switching traffic at wire speed between all its ports.

Under heavy load situations from the tributary side and when using the same
VLAN priority (CoS) for all or many traffic streams, congestion might occur in
upstream direction due to the limited packet buffer resources in the switching
circuit.
Please note:
Management traffic coming from the CESM1 management router and enter-
ing the FOX chassis switch is per default tagged with a VLAN priority CoS4.
→ To avoid collisions of tagged management traffic with user traffic it is
recommended to use other VLAN priorities for the user traffic.
The following table summarises the main features of the CESM1 switch cir-
cuit.
Table 15: CESM1 switch features

Feature Details
Generic Main feature L2 switching
No. of ports 28
Internal packet buffer 1.5 MB
MAC addresses up to 16’000 a
VLAN VLAN support (802.1Q) Yes
VLAN no. 4089 (1-4089)
VLAN tag stacking support (802.1ad) No b
IVL (Independent VLAN Learning) c Yes
QoS CoS (802.1p) Yes
Output queues 8
Weighted scheduling Yes
Shaping support Yes (future release)
Link functions RSTP according 802.1D-2004 Yes
MSTP according 802.1s Yes
Link aggregation (802.1AX) No b
a. 16’000 is the maximum value reachable with random MAC addresses (real traffic in
the field). Note that with sequential MAC addresses as they are used in stress or
acceptance test scenarios the maximum value can be reduced.
b. Will be available in a future release.
c. MAC learning on a per VLAN basis.
The FOX chassis switch is a VLAN aware switch. The CESM1 external
Ethernet interfaces are used as bridge ports of the FOX chassis switch and
support all available bridge port modes as described in the 1KHW002460
FOX61x Product Features and Characteristics.
The CESM1 internal ports, connecting Ethernet switch devices being part of
the chassis switch, all transport VLAN tagged frames.

The CESM1 internal ports, connecting Ethernet switch devices not being
part of the chassis switch, are handled as an external bridge port, i.e. they
transport VLAN tagged or untagged frames.
The management functions of the CESM1 Ethernet ports are described at
two different places:
• The 1KHW002468 FOX61x Ethernet Services describes all bridge port
parameters of the Ethernet interfaces which are used as external ports of
the FOX chassis switch:
− port mode,
− port VLAN ID,
− acceptable frame types (for the general port mode only),
− default priority,
− ingress filtering,
− VLAN membership,
− trust mode,
− priority regeneration.
• This User Manual describes the physical port parameters of the external
and internal Ethernet interfaces:
− MTU size,
− flow control (available in a future release),
− queue scheduling.
5.1.5 Link protection functions

Link protection functions as e.g. RSTP or Link Aggregation are features of
the FOX chassis switch. Please refer to 1KHW002468 FOX61x Ethernet
Services.
5.1.6 Security features

Security features as e.g. ingress storm control are features of the FOX chas-
sis switch. Please refer to 1KHW002460 FOX61x Product Features and
Characteristics.
5.1.6.1 Ingress storm control
Protection against excessive ingress rates of unknown unicast, multicast and

broadcast traffic.
5.1.6.2 Excessive protocol traffic
Protection against excessive (malicious) protocol traffic that must be handled

by the CPU (BPDUs, IGMP, MVRP, etc.).
5.2 Interfaces
The interfaces in the CESM1 unit can be classified as follows:

• Traffic ports (for trunking or subtending purposes)

• Management
• synchronization
• Backplane
• External alarms
5.2.1 Traffic ports

Traffic ports are the five Ethernet front ports of the CESM1. Traffic ports are
part of the FOX chassis switch. Traffic ports can be configured to be
• Access ports, or
• Trunk ports, or
• Trunk with native VLAN ports, or
• General ports.
The port VLAN handling is depending of the configured port mode. Please
refer to 1KHW002468 FOX61x Ethernet Services and to 1KHW002459
FOX61x Release Notes for further information.
Because of the wide range of available distances that can be covered with
optical interfaces, the SFP/SFP+ interfaces (ports 1 and 2) are considered
as network interfaces.
These interfaces support SFP+ modules with 10GBASE-LR according to
their respective standards, or support SFP modules with 1000BASE-SX/-LX/
-EX/-ZX according to their respective standards.
CESM1 provides two SFP cages (port-1 and port-2) where different SFP/
SFP+ modules can be inserted to satisfy network needs.
For details about SFP+ modules, refer to section SFP+ 10GbE optical mod-
ules and cables (on page 23). For details about SFP modules, refer to sec-
tion SFP GbE optical modules and cables (on page 24).
The selection of the transceiver and the media type (single mode or multi
mode fibre) will determine the maximum distance allowed according to the
SFP/SFP+ provider specifications.
For details on connectors and pins for this interface please refer to “SFF-
8431” and to “INF-8074”.
The SFP/SFP+ modules provide duplex LC connectors.
Please note:
SFP/SFP+ modules are hot swappable. This means that you can plug or
remove the modules during operation of the unit.
→ We strongly recommend however to remove the fibre before plugging
or unplugging an SFP/SFP+ module.
In principle, any of the electrical or optical Ethernet front ports can be used
as subtending interface, i.e. a further FOX network elements can be con-
nected to this port. However, electrical interfaces have a limited reach com-
pared with the optical interfaces and are therefore normally used in subtend-
ing configurations.
The three electrical Ethernet interfaces (port-3, port-4, and port-5) support
10/100/1000BASE-T/TX according to IEEE 802.3 specifications. The inter-
faces are implemented by means of an RJ-45 connector with auto-negotia-
tion. Fixed operation modes (speed, half/full duplex modes) are also availa-
ble. These interfaces support automatic cross over functionality allowing
straight or cross over cables to be connected.

The traffic ports support Ethernet frames bigger than 1522 bytes called
jumbo frames. The maximum frame length supported is 9’216 octets (also
refer to section AP: / unit-x / port-a (on page 65)).
Any of the five traffic ports can be used for inband management communica-
tions or as a dedicated (untagged) management port by configuring the port
VLAN-ID to the management VLAN-ID.
The internal ports (GbE star) connecting the service units are used in two
applications:
• Connection of an Ethernet service unit participating in the chassis switch.
In this case the port has a fixed configuration, except the queue handling
(MTU sizes and queue scheduling).
• Connection of a service unit not participating in the chassis switch. In this
case the internal port offers the same amount of configuration parameters
as an external port, except the link speed and duplex mode.
A service unit not participating in the chassis switch can e.g. provide
access to the Ethernet over PDH (EoP) or Ethernet over SDH (EoS)
transport facilities.
Please note:
The switch device on the redundant CESM1 unit participates in the FOX
chassis switch.
All of the five Ethernet front ports and the internal ports to the service units
support RSTP, MSTP and LACP (future release). For more details about
RSTP and MSTP on the Ethernet ports, please refer to 1KHW002468
FOX61x Ethernet Services.
5.2.2 Management ports

Please refer to section Management traffic and routing (on page 30).
5.2.3 Mirror ports

Any of the five Ethernet front ports of the CESM1 unit, and any other Ether-
net port of the chassis switch, can be configured to be a mirror port. In this
case, frames from any other front port or from any of the backplane GbE
ports or from the host processor port can be copied to this port.
For the port to be mirrored, you can select the direction, i.e. ingress frames,
egress frames, or both.
For more information please refer to 1KHW002464 FOX61x System Descrip-
tion.
5.2.4 Synchronization interface

This interface is implemented by means of a micro D-Sub connector. It pro-
vides two symmetrical clock signal inputs of 2.048 MHz with an impedance
of 120 Ohms according to ITU-T G.703 (esi-1 and esi-2), and two symmetri-
cal clock signal outputs of 2.048 MHz with the same impedance (eso-1 and
eso-2).
The impedance of the input interface can be determined by a jumper on the
board. This is necessary when a redundant CESM1 is placed in slot 13. In
this case, you can connect a synchronization source to two CESM1 synchro-
nization input interfaces in parallel (e.g. to both esi-1 on unit-11 and esi-1 on
unit-13).

Please note:
Equipment protection with a redundant core unit CESM1 will be available in
a future release.
When using an external line termination, you have to set the synchronization
inputs on the two CESM1 boards to high impedance. This is done with the
jumper situated just behind the synchronization interface connector on the
CESM1 board. The upper jumper is for esi-2 whereas the lower jumper is for
esi-1. Plugging the jumper on the two lower pins sets the interface imped-
ance to 120 Ohms. Plugging the jumper on the two upper pins sets the inter-
face impedance to “high”.
jumper for ESI -2,

set to high impedance
jumper for ESI -1,

set to impedance 120 Ohm
3
2 jumper set to high impedance
1
3
2 jumper set to impedance 120 Ohm
1
Figure 10: Jumper position and setting for esi-1 and esi-2
5.2.5 Backplane interfaces

5.2.5.1 1GbE double star
Slot 11 and 13 of the FOX subrack have point-to-point connections of 1 Gbit/

s each to every other slot in the subrack via the backplane, allowing the
interconnection of the switch devices on the Ethernet service units to the
FOX chassis switch.
Switch devices on service units not participating in the chassis switch are
also connected via the 1 Gbit/s link. In this case the backplane Ethernet port
is handled the same as an external (front) port.
5.2.5.2 10GbE links
Slot 11 and 13 have two point-to-point connections of 10 Gbit/s to intercon-

nect the working CESM1 unit with the redundant CESM1 unit.

Please note:
a future release.
5.2.5.3 CBUS
The CBUS (Control BUS) contains signals used for the interworking of the
units in a subrack like slot select control signals, alarms, power supply, and
inventory information.
5.2.5.4 PBUS
The PBUS contains signals for synchronization, distribution of PDH signals,

and internal communication.
CESM1 and all service units have access to the PBUS in order to exchange
information using the ABB proprietary protocol ICN (Internal Communication
Network).
The ICN is used for the management communication between the core unit
and service units within the subrack.
Among others the main functions of the ICN bus are:
• Service unit configuration and fault management
Configuration, monitoring, alarm collection, and software installation with
the service units.
• Broadcasting of operational parameters
Time and date, synchronization signals, etc.
• Exchange of data between working and redundant control unit
Update or exchange of information between control units including status
and alarm information.
• Service unit to service unit communication
The communication of the ICN uses a proprietary protocol stack. The lower
layers of the stack rely on an HDLC synchronous bus with a speed of 5 Mbit/
s. The communication of the ICN is based on a multi master principle.
5.3 Equipment protection EQP (core unit redundancy)
Please note:
a future release.


COMMISSIONING
6 Commissioning
This section presents how to configure and bring into operation the CESM1
unit and its main functions. For operation, i.e. status and maintenance func-
tions refer to section Operation and maintenance (on page 47).
To find a description on how to configure system services and inter-work
functionality with service units please
• refer to 1KHW002468 FOX61x Ethernet Services for FOX Ethernet traffic
aspects,
• refer to 1KHW002467 FOX61x TDM Services for FOX TDM traffic
aspects,
• refer to 1KHW002464 FOX61x System Description for FOX615 and
FOX612 general aspects.
6.1 Commissioning prerequisites for CESM1
The following prerequisites must be fulfilled for the commissioning of a

CESM1 unit:
6.1.0.1 CESM1 unit
A CESM1 must be physically plugged in slot 11 of the FOX subrack. Please

make sure the HW fulfils the requirements stated in 1KHW002459 FOX61x
Release Notes.
Please note:
When you power up the CESM1 unit for the first time (from factory default
settings), all LEDs will be “ON”. This state means that the network element
bootloader is active but there is no application software (ESW) to launch.
You will need to install an appropriate ESW.
→ For the installation procedures and the detailed initial connection pro-
cedure please refer to 1KHW002465 FOXCST Installation.
A redundant CESM1 unit (if required) must be physically plugged in slot 13
of the FOX subrack. This is mandatory if you want to implement core unit
redundancy. It is not required if you do not want core unit redundancy.
Please note:
a future release.
6.1.0.2 FOXCST
FOXCST needs to be installed on a PC, and a management connection from

the FOXCST to the FOX needs to be up and running. For details about the
installation and operation of the FOXCST, please refer to 1KHW002466
FOXCST Operation.

COMMISSIONING
The amount and accessibility of operations depend on the user profile with
which you are logged in. For more information, please refer to 1KHW002466
FOXCST Operation.
Please note:
Ethernet cabling should be connected to both the master and the redundant
CESM1 if redundancy is implemented.
→ In this case, care must be taken to correctly configure RSTP/MSTP
settings in order to avoid broadcast storms.
For all FOXCST and management connection related topics please refer to
1KHW002466 FOXCST Operation.
For a specific description of the ESW download and assignment to a CESM1
unit which is already in service or to a redundant CESM1 unit please refer to
section Unit and network element ESW download (on page 49).
6.2 First ESW download to a CESM1 unit

An ESW installation may perform also a firmware upgrade which will take
about 30 s. During the firmware upgrade the TRAFFIC LED blinks with 5 Hz.
→ Do NOT disrupt power during this upgrade procedure!
When inserting a CESM1 unit the first time into a FOX subrack the unit is
running in the network element bootloader, no ESW is installed.
You need to install valid ESW on the CESM1 unit in slot 11. If you implement
core unit redundancy, you need to install the identical ESW on the CESM1
units in both slot 11 and slot 13.
Note that you have to install two ESW, one for the unit management and one
for the network element management:
• The unit ESW (cesun_r1cxx) is installed at the AP: /unit-x.
• The NE ESW (cesne_r1cxx) is installed at the AP: /unit-x/neController.
Please make sure the ESW version fulfils the requirements stated in
1KHW002459 FOX61x Release Notes.
First ESW download This action list shows step by step how to download the appropriate ESWs
to a CESM1 unit which is plugged the first time into a FOX subrack.
The following main steps have to be performed to install the ESW:
• Connect to the FOX with the user class “manager”.
• Download the NE ESW of the core unit to the network element and acti-
vate the ESW.
• 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”.
• Download the unit ESW to the core unit, restart and assign the unit to
make it available for commissioning.

COMMISSIONING
The “unit-x” stands for either “unit-11”, or “unit-13”, or for both in a sequential
order.
Please note:
For the detailed initial connection procedure please refer to 1KHW002465
FOXCST Installation.
Management connection Proceed as follows:

1. Connect an Ethernet cable from the PC to the Ethernet local manage-
ment port on the FOX control unit plugged in slot-11.
2. Wait until the CESM1 unit has booted.
 The upper two LEDs on the unit front are red.
 The lower two LEDs on the unit front are green.
3. Connect to the FOX with the user class “manager”.
 FOXCST menu “File - Connect”.
 The “Connect to” dialogue opens.
 Select the previously configured connection, e.g. Connection =
FOX_Local.
 Select the authentication = Local.
 Select the user class = Manager.
 Leave the password empty.
 Click “OK”.
4. Download the NE ESW of the control unit to the NE and activate the
ESW.
 FOXCST “Tree View”, select unit-11.
 Open the “Main - Software” management function.
 In the “Software On Element Manager” section select the cesne_rxx
ESW and click “Download”.
 Wait until the ESW appears in the “Software On Unit” table.
 In the “Configuration” section select Software = cesne_rxx and click
“Start Software”.
Please note:
When the CESM1 unit is running in the network element bootloader the
“Save to NE” command is executed automatically when the configuration is
modified.
→ The operator is not allowed to execute a manual “Save to NE” com-
mand.
5. Wait until the CESM1 unit has booted. This takes several minutes.
 The upper left LED on the unit front is red/green blinking.
 The upper right LED on the unit front is red.
 The lower two LEDs on the unit front are dark.
6. Disconnect the FOXCST from the FOX.
 FOXCST menu “File - Close”.

COMMISSIONING
7. Reconnect to the FOX with the user class “session manager”.

 FOXCST menu “File - Connect”.
 The “Connect to” dialogue opens.
 Select the previously configured connection, e.g. Connection =
FOX_Local.
 Select the authentication = Local.
 Select the user class = Session Manager.
 Leave the password empty.
 Click “OK”.
8. Initialize the passwords for the different user classes.
 FOXCST menu “Tools - Modify Password …”.
 The “Modify Password” dialogue opens.
 Select the User Class = Manager.
 Leave the Old Password empty.
 Enter the New Password.
 Enter the same password in the Confirm New Password field.
 Click “Apply”.
 Modify the passwords of all other required user classes.
 Click “OK”.
Please note:
When the operator is connected with the user class “Session Manager” the
modified.
mand.
9. Disconnect the FOXCST from the FOX.
 FOXCST menu “File - Close”.
 The management access on the FOX is initialized.
Assign and start software Proceed as follows:

1. Reconnect with the user class “manager”.
2. Download the required ESWs to all plugged units and start the ESW.
 FOXCST menu “Tools - Software Download …”.
 The “Software Download” dialogue opens.
 In the “Software to install” column select the cesun_rxx ESW to be
installed on the CESM1 unit. Note that the /unit-11/neController is
already running with the NE ESW cesne_rxx.
 Click “Download and Start …”.
 The “Parameters for command Download and Start” dialogue opens.
 Select the Algorithm = System Release Upgrade.
 Click “OK”.
3. Wait until the CESM1 unit has booted. This takes several minutes.
 The upper left LED on the unit front is red/green blinking.
 The upper right LED on the unit front is red.
 The lower two LEDs on the unit front are dark.
4. Assign the CESM1 unit to make it available for commissioning.
 FOXCST “Tree View”, select unit-11: CESM1.
 Open the “Main - Equipment” management function.
 Click “Assign”.

COMMISSIONING
5. Set the system time.

 FOXCST “Tree View”, select ne: FOX.
 Open the “Status - Date And Time - Time” management function.
 Click “Set Date And Time”.
 The “Set Date And Time” dialogue opens.
 Click “OK”.
 The FOX network element is now ready for configuration.
 If no service units are plugged all alarms are cleared.
 The upper left LEDs on the CESM1 unit front is green.
 If no service units are plugged the upper right LED on the CESM1
unit front is dark.
 The lower two LEDs on the CESM1 unit front are green.
End of instruction
6.3 Configuring an external Ethernet port
In order to configure one of the Ethernet front ports in CESM1, the following
steps have to be performed. If you are using a redundant CESM1, the steps
must be performed on both CESM1, the active core unit (unit-11) and the
standby core unit (unit-13).
The “unit-x” stands for either “unit-11”, or “unit-13”, or for both in a sequential
order.
Port configuration This action list shows step by step how to configure an external Ethernet
port. The given example uses mostly the default values.
The following assumptions and identifiers are used:
 The CESM1 unit is assigned.
 The port to be configured has the identifier port-5.
 The bridge port is a trunk port and forwards the VLANs with VLAN ID
100 and 101.
Configure the physical port Proceed as follows:

parameters 1. Select the “Tree View” of the FOXCST.
2. Navigate to the port parameters:

 AP:/unit-x/port-5, Main - Physical.
3. Configure the MTU size:
 MTU = 1578 Octets.
4. Disable the flow control:
 Flow Control, Admin = .
5. Navigate to the port QoS parameters:
 AP:/unit-x/port-5, QoS - QoS Scheduling.
6. Select the queue scheduling profile as it is defined in the FOXCST
“Switching” view at Switching/Bridges, bridge-1/QoS, Scheduling Pro-
files:
 Profile Index = 2.
7. Execute “Apply”.
 The Ethernet physical port is completely configured.

COMMISSIONING
Configure the bridge parame- Proceed as follows:

ters
1. Select the “Switching” view of the FOXCST.
2. Navigate to the bridge-1 parameters:
 AP:/Switching/Bridges.
3. Click on the bridge-1 row of the bridge table:
 The bridge-1 configuration dialogue opens.
4. Navigate to the General parameters:
 AP:/Switching/Bridges, bridge-1/General.
5. Configure the aging time of the MAC learning:
 Aging Time = 300 s.
7. Navigate to the QoS parameters:
 AP:/Switching/Bridges, bridge-1/QoS.
8. Configure the scheduling profile 2:
 Select Profile = 2.
9. Set the scheduling algorithm of the traffic classes 0 to 6:
 Select Scheduling Algorithm = Weighted Round Robin.
 The bridge is completely configured.
Configure the bridge port Proceed as follows:

parameters
1. Select the “Switching” view of the FOXCST.
2. Navigate to the port parameters of bridge-1:
 AP:/Switching/Bridges/bridge-1, Ports.
3. Select the port mode of /unit-x/port-5:
 Mode = Trunk.
4. Click on the port-5 row of the port table:
 The port-5 configuration dialogue opens.
5. Navigate to the QoS parameters:
 AP:/unit-x/port-5/QoS.
6. Configure the trust mode:
 Trust L2 = .
 Trust L3 = .
 The bridge port is completely configured.
Configure the bridge VLAN Proceed as follows:

parameters 1. Select the “Switching” view of the FOXCST.
2. Navigate to the VLAN parameters of bridge-1:

 AP:/Switching/Bridges/bridge-1, VLANs.
3. Add the VLAN 100:
 Click the “Create” button.
 The “Create a new VLAN” dialogue opens.
4. Enter the VLAN parameters:
 VLAN ID = 100.
 Name = VLAN_100.
 Click the “OK” button.

COMMISSIONING
5. Add the VLAN 101:

 Click the “Create” button.
 The “Create a new VLAN” dialogue opens.
6. Enter the VLAN parameters:
 VLAN ID = 101.
 Name = VLAN_101.
 Click the “OK” button.
 The VLANs for the bridge-1 are completely configured.
Activation Proceed as follows:

1. Select the “Tree View” of the FOXCST.
2. Navigate to the port parameters:
 AP:/unit-x/port-5, Main - General:
3. Set the administrative state of the port-5 to up
 Interface Status, Admin Status = Up.
 The “Operational Status” changes to “Up”.
 The port is activated.
Save the configuration Proceed as follows:

1. Save the configuration to the NE flash memory:
 Execute “Save to NE”.
 The configuration is saved.
End of instruction
6.4 Commissioning RSTP
The management functions for the commissioning of RSTP are located in

the FOXCST tab “Switching”.
For a description of this functionality please refer to 1KHW002468 FOX61x
Ethernet Services.
6.5 Commissioning MSTP
The management functions for the commissioning of MSTP are located in

the ECST tab “Switching”.
Ethernet Services.

COMMISSIONING
6.6 Core unit redundancy
Please note:
a future release.

OPERATION AND MAINTENANCE
7 Operation and maintenance

This section presents how to operate the CESM1 unit once it has been com-
missioned. For a description on how to configure and bring into operation the
CESM1 unit and its main functions, refer to section Commissioning (on
page 39).
7.1 Unit Optical Indicators
The CESM1 unit has four LED optical indicators showing information about
the unit, traffic, status and lock state.
The following figure shows the LED layout on the unit.
XXXXx R1B
ANR_37900374
UNIT TRAFFIC
ACTIVE LOCKED
Figure 11: Fault and status indication LEDs on the CESM1 unit
The operating state of the CESM1 unit can be known by reading the LED
optical indicators from the CESM1 unit front.
The following table shows the signalling of the CESM1 LEDs and their
meaning.

Table 16: LED signalling on CESM1

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
Recovery from this error situation is done usually by replacement
of unit HW or ESW.
Green / Red Booting / waiting The unit has not been taken into service yet or the unit has not
(blinking 1 Hz) been provisioned.
- During the booting process the initial software installation is pro-
gressing on the control unit. The CESM1 will not respond to man-
agement communications as long as it is in the booting state.
- In the waiting state the control unit is waiting for configuration.
The waiting state lasts as long as the CESM1 has no configura-
tion. In this state, the CESM1 can only provide the “point to point”
type of management communication. This means that only the
Ethernet local management port will allow a direct connection for
initial commissioning.
Recovery from this situation is done by taking the unit into service
with FOXCST.
Green Running The unit is up and running, it is ready to provide the required ser-
vice.
- The internal resources are available and the CESM1 controls the
NE.
- All management functions, e.g. configuration management, fault
management and software management are available.
Off Failure The system is not powered or there is an outage of power supply
on the unit or an outage of the LED.
TRAFFIC Red Failure One or more active failures on the unit, independent of the sever-
ity.
More detailed information is provided by FOXCST.
Note: This definition is valid for both, active and standby unit.
Off Normal Normal (error free) operation.
This is the default state.
ACTIVE Green Active The unit is active, i.e. controls the other units in the subrack.
Off Standby The unit is standby. If the UNIT LED is green, the unit is ready to
take over the operation in case the active unit will fail.
The standby operation state is only possible for the redundant unit
in an NE with 1+1 equipment protection for the control unit.
LOCKED Green Locked The NE is locked to a synchronization source.
Off Not locked The NE is not locked to a synchronization source.
Please note:
When CESM1 is started up for the first time (from factory default settings), all
LEDs will be “ON”. This state means that the network element bootloader
(bco5n_rxxxx) is active but there is no application software (ESW) to launch.
For the installation of application software (ESW), please refer to
1KHW002466 FOXCST Operation.

7.2 Maintenance
7.2.1 Inventory data

It is possible to read inventory data from the CESM1 unit via the FOXCST at
the following access points:
• AP: /unit-x, Main - Inventory,
for unit related information, and
• AP: /unit-x/neController, Main - Inventory,
for NE control processor related information.
The detailed HW information is described in section AP: / unit-x, Main (on
page 60) and in section AP: / unit-x / neController, Main (on page 62).
7.3 Unit and network element ESW download

The assignment of new unit ESW or network element ESW to CESM1
requires a restart of the unit. Thus, the installation of new ESW on the
CESM1 unit affects all traffic functions.

An ESW upgrade may perform also a firmware upgrade which will take
about 30 s. During the firmware upgrade the TRAFFIC LED blinks with 5 Hz.
→ Do NOT disrupt power during this upgrade procedure!
Please note:
The unit ESW and network element ESW must be operated as pairs, i.e.
having the same release designation.
→ E.g. use the ESW cesun_r1cxx and cesne_r1cyy, where the “r1c” part
of the ESW name must match.
7.3.1 Unit ESW and network element ESW download on a running

CESM1 unit
The unit ESW (UN ESW) and the network element ESW (NE ESW) can be
downloaded and started on a running CESM1 unit using the FOXCST menu
“NE/Software Download…” or via the FOXCST at the access points AP: /
unit-x, Main - Software and AP: /unit-x/neController, Main - Software.
ESW download for the unit The instructions below assume

and the network element • the FOXCST accesses the above mentioned access points.
• the CESM1 unit is plugged in slot-11.
The following actions must be performed to download and start the
• network element ESW, and the
• unit ESW.

Download procedure Proceed as follows:

1. Set up a management connection to the FOX network element.
 Select the user class “manager”. This is necessary to receive the
access rights for downloading ESWs to the units of the NE.
2. Select the AP: /unit-11, i.e. the CESM1 unit.
 The AP: /unit-11 is running with the unit ESW (cesun_rxxxx).
3. Open the management function (MF) “Main” and select the tab “Soft-
ware”.
 Select the new CESM1 UN ESW (cesun_r1cxx) in the list of “Soft-
ware On Element Manager” and click “Download”.
 Wait until the download is terminated and the ESW appears in the list
“Software On Unit”.
4. In “Configuration” select the downloaded ESW under “Software”.
 Check that “Software Installation” is set to “Manual Start”.
6. Select the AP: /unit-11/neController.

 The AP: /unit-11/neController is running with the network element
ESW (cesne_rxxxx).
7. Open the MF “Main” and select the tab “Software”.
 Select the new CESM1 NE ESW (cesne_r1cxx) in the list of “Soft-

11. Start the new unit software.
 In the MF “Main” of the AP: /unit-11, i.e. the CESM1 unit, click the
command button “Start Software”.
 This reboots the unit ESW of the control unit.
12. Start the new network element software.
 In the MF “Main” of the AP: /unit-11/neController, i.e. the network ele-
ment, click the command button “Start Software”.
 This reboots the network element ESW of the control unit.

7.3.2 Unit ESW download on a running CESM1 unit

The unit ESW (UN ESW) can be downloaded and started on a running
CESM1 unit using the FOXCST menu “NE/Software Download…” or via the
FOXCST at the access point AP: /unit-x, Main - Software.
ESW download for the unit The instructions below assume

• the FOXCST accesses the above mentioned access point.
The following actions must be performed to download and start the unit
ESW.

 The AP: /unit-11 is running with the unit ESW (cesun_rxxxx).
 Select the new CESM1 UN ESW (cesun_r1cxx) in the list of “Soft-

7. Start the new software.
 In the MF “Main” of the AP: /unit-11, i.e. the CESM1 unit, click the
command button “Start Software”.
 This reboots the unit ESW and the network element ESW of the con-
trol unit.
8. Wait until the unit has booted.
 The new UN (unit) ESW is installed and running at the AP: /unit-11.
End of instruction
7.3.3 Network element ESW download on a running CESM1 unit

The network element ESW (NE ESW) can be downloaded and started on a
running CESM1 unit using the FOXCST menu “NE/Software Download…” or
via the FOXCST at the access point AP: /unit-x/neController, Main - Soft-
ware.

ESW download for the The instructions below assume

network element • the FOXCST accesses the above mentioned access point.
The following actions must be performed to download and start the network
element ESW.

2. Select the AP: /unit-11/neController.
 The AP: /unit-11/neController is running with the network element
ESW (cesne_rxxxx).
 Select the new CESM1 NE ESW (cesne_r1cxx) in the list of “Soft-

 In the MF “Main” of the AP: /unit-11/neController click the command
button “Start Software”.
 This reboots the unit ESW and the network element ESW of the con-
trol unit.
8. Wait until the unit has booted and reconnect.
 The new NE (network element) ESW (cesne_r1cxx) is installed and
running at the AP: /unit-11/neController.
End of instruction
7.3.4 Set the CESM1 unit into the network element bootloader

Please be aware of the fact, that a core unit in the bootloader can only be
accessed locally via the Ethernet local management port.
The bootloader state can be used to e.g. delete all ESW from a unit or for
debug purposes.
The CESM1 unit is assumed to be plugged in slot-11.

Set to the network element The following actions must be performed to bring a running CESM1 unit into
bootloader the network element (NE) bootloader.
Bootloader procedure Proceed as follows:

 Select the user class “manager”.
 The AP: /unit-11 is running with the unit ESW (cesun_r1cxx).
3. Open the MF “Main” and select the tab “Equipment”.
 Execute the command “Stop In Boot”.
 Confirm the warning message by clicking the “OK” button.
 The CESM1 unit reboots.
4. Wait until the unit has booted and reconnect as “manager”.
 The AP: /unit-11 is the only AP available in the AP tree.
 The AP: /unit-11 is now running in the network element bootloader
(bco5n_rxxxx).
End of instruction
Please note:
To exit from the NE bootloader an NE ESW must be configured and applied
at the AP: /unit-x, Main - Software before restarting the unit.
→ Refer also to section Set the CESM1 unit into the unit bootloader (on
page 53).
7.3.5 Set the CESM1 unit into the unit bootloader

Please be aware of the fact, that a core unit in the bootloader can only be
accessed locally via the Ethernet local management port.
The bootloader state can be used to e.g. delete all ESW from a unit or for
debug purposes.
The CESM1 unit is assumed to be plugged in slot-11.
Set to the unit bootloader The following actions must be performed to bring a running CESM1 unit into
the unit (UN) bootloader.
Bootloader procedure Proceed as follows:

 Select the user class “manager”.
 The AP: /unit-11 is running with the unit ESW (cesun_r1cxx).
3. Open the MF “Main” and select the tab “Equipment”.
 Execute the command “Stop In Boot”.
 Confirm the warning message by clicking the “OK” button.
 The CESM1 unit reboots.
4. Wait until the unit has booted and reconnect as “manager”.
 The AP: /unit-11 is the only AP available in the AP tree.
 The AP: /unit-11 is now running in the network element bootloader
(bco5n_rxxxx).


 If the desired NE ESW is not available on the unit select the CESM1
NE ESW (cesne_r1cxx) in the list of “Software On Element Manager”
and click “Download”.
Please note:
When the CESM1 unit is running in the network element bootloader the
modified.
mand.

 In the MF “Main” of the AP: /unit-11 click the command button “Start
Software”. This reboots the redundant control unit.
9. Wait until the unit has booted, disconnect and reconnect as “manager”.
 The AP: /unit-11 is now running in the unit bootloader (bco5u_rxxxx).
 The AP: /unit-11/neController is running the NE ESW (cesne_r1cxx).
End of instruction
Please note:
To exit from the UN bootloader a UN ESW must be configured and applied
at the AP: /unit-x, Main - Software before restarting the unit.
7.4 Setting up mirror ports
In certain situations, you may need to monitor frames from any of the FOX
chassis switch ports on a CESM1 front port. For this purpose, any of the five
Ethernet front ports can be configured to be a mirror port.
Assuming the case where you want to mirror all frames that are sent by the
port-1 of a service unit in slot 20 to the CESM1 unit, and you have one front
port of the CESM1 yet unused (e.g. port-5), you may proceed as follows to
get the frames to a monitoring equipment connected to that spare front port.

Configure a mirror port Proceed as follows:

1. Select the “Tree View” of the ECST.
2. Navigate to the CESM1 port parameters:
 AP:/unit-11/port-5, Overview - Mirroring.
3. Add a mirrored port table entry:
 Click “Add …”.
 The “Add Mirroring Entry” dialogue opens.
 Set the Copy Direction = Copy TX only
4. Add the source port:
 In the “source” row click “…”.
 The “Select an Access Point” dialogue opens.
 Tick the box of port-1 of the unit-20.
 Click “OK”.
5. Add the destination port:
 In the “destination” row click “…”.
 The “Select an Access Point” dialogue opens.
 Tick the box of port-5 of the unit-11.
 Click “OK”.
 Click “OK” in the “Add Mirroring Entry” dialogue.
 The mirror port is completely configured.
End of instruction
Now you connect your monitoring equipment to port-5 of the CESM1 unit
and start monitoring.
7.5 RSTP status
The management functions for the operation of RSTP are located in the
FOXCST tab “Switching”.
Ethernet Services.
7.6 MSTP status
The management functions for the operation of MSTP are located in the
ECST tab “Switching”.
Ethernet Services.

7.7 Redundancy
Please note:
a future release.

FOXCST REFERENCE
8 FOXCST reference
This section gives a complete reference of the managed objects, properties,
and commands of the CESM1 service unit as far as these are not covered in
the generic descriptions in 1KHW002466 FOXCST Operation.
In this section, you will find the following information:
• An introduction (section Introduction (on page 57)),
• Unit management commands and parameters (section AP: / unit-x:
CESM1 (on page 60)),
• Internal ports management commands and parameters (sections AP: /
unit-x / iports (on page 75) and AP: / unit-x / iports / iport-b (on page 75)),
• Network element management commands and parameters (section AP: /
unit-x / neController (on page 62)),
• ESI parameters (section AP: / unit-x / neController / esi-y (on page 64)),
• Ethernet Front port management commands and parameters (section
AP: / unit-x / port-a (on page 65)).
8.1 Introduction
Below, you will find a detailed description of all the configuration parameters
and operations belonging to the managed objects model (MOM) for the
CESM1 core unit operated in a FOX.
The Figure 12 shows the access point (AP) tree for the CESM1 unit with its
managed objects.

FOXCST REFERENCE
<ap >
FOX
<ap >
1...2 unit-x: CESM1
cesun_r1c
<ap>
1
neController
2 <ap>
esi-y
5 <ap>
port-a
cesne_r1c
1 <ap>
mau
1 <ap>
iports
19 <ap>
iport-b
1 <ap >
mau
Figure 12: MOM for CESM1
With these managed objects (MOs) the following functions are covered:
Table 17: Managed objects (MOs) for CESM1

MO Description of the management functions
unit-x: CESM1 Rxx Restart of the unit, management of the unit ESW, labelling,
(cesun_r1c) indication of equipment status, read of inventory data, access
to logbooks. Configuration of unit parameters and equipment
protection parameters, creating or deleting of data confer-
ences.
The detailed properties are described in AP: / unit-x: CESM1
(on page 60).
neController Management of the NE ESW, labelling, indication of equipment
(cesne_r1c) status, read of inventory data, access to logbooks.
The detailed properties are described in AP: / unit-x / neCon-
troller (on page 62).
esi-y Management of the external synchronization inputs, fault man-
agement.
The detailed properties are described in AP: / unit-x / neCon-
troller / esi-y (on page 64).

FOXCST REFERENCE
Table 17: Managed objects (MOs) for CESM1 (continued)

MO Description of the management functions
port-a Management of the Ethernet front ports. The AP “port-a”
includes both, 1000BASE-X/10000BASE-R SFP Ethernet ports
(port-1 and port-2), and electrical 10/100/1000BASE-T Ether-
net ports (port-3 to port-5).
The detailed properties are described in AP: / unit-x / port-a (on
page 65).
mau The mau provides the fault management functions of the SFPs.
The detailed properties are described in AP: / unit-x / port-a /
mau (on page 74) and in AP: / unit-x / iports / iport-b / mau (on
page 82).
iports The iports AP contains all internal Ethernet ports.
iport-b Management of the Ethernet internal ports. The internal ports
connect all service units with the core unit CESM1.
The detailed properties are described in AP: / unit-x / iports /
iport-b (on page 75).
Please note that Ethernet switching related operations like VLAN tagging, fil-
tering, etc. are part of the managed object “bridges” on NE level, which is
described in 1KHW002468 FOX61x Ethernet Services.
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,
• Statistics, and
• Fault Management.
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.

FOXCST REFERENCE
Please note:
For better legibility of numbers in this user guide, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter
entry fields of the FOXCST, these inverted commas must not be entered.
Instead, the numbers are entered without these inverted commas (e.g.
40000).
Please note:
Screenshots presented in this reference are examples and show configura-
tions or data that may not correspond to the view you see when managing
your FOX equipment.
8.2 AP: / unit-x: CESM1
The name “unit-x” stands for:

• the “unit-11” if only one CESM1 is operated in the FOX, or
• the “unit-13” if, in addition to unit-11 a redundant CESM1 is operated in
the FOX.
Please note:
a future release.
8.2.1 AP: / unit-x, Overview

For a description of the
− “Overview - Alarms”
management function, please refer to 1KHW002466 FOXCST Operation.
− “Overview - Mirroring”
management function, please refer to 1KHW002464 FOX61x System
Description.
8.2.2 AP: / unit-x, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”
management functions, please refer to 1KHW002466 FOXCST Operation.

FOXCST REFERENCE
8.2.3 AP: / unit-x, Configuration

8.2.3.1 AP: / unit-x, Configuration - Clock Synchronization
Table 18: AP: / unit-x, Configuration - Clock Synchronization

Operation Name Parameter Name Range Descriptions / Details
Transmit Clock Synchronized to NE  Synchronize the transmit timing of the Ethernet front
Clock Enabled  ports to the PETS of the active CESM1 unit.
8.2.4 AP: / unit-x, Fault Management

For the a description of the general aspects of the
− “Fault Management - Status”, and
− “Fault Management - Configuration”
The following table lists the fault causes of the current AP.
Table 19: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Default Description
Affecting Severity
SWM Software Mismatch Equipment  Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment  Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to the
unit.
SWIN Software Incompatible Equipment  Major The running ESW is not compatible with
With Network Element Alarm the version required by the NE type or
version.
CCE Configuration or Cus- Processing  Major An invalid configuration has been
tomization Error Error Alarm accepted by the unit by mistake.
To get rid of the alarm redo the complete
configuration or reboot the unit.
If the alarm persists please contact ABB.
HWIC Hardware Incompatible Equipment  Major The plugged HW is not compatible with
With Configuration Alarm the unit configuration HW stored in the
database. You may need to change the
HW or re-create the configuration for the
unit.
SWIC Software Incompatible Equipment  Major The ESW running on the unit is not com-
With Configuration Alarm patible with the unit configuration stored
in the database. You may need to
upgrade, or downgrade the ESW, or re-
create the configuration with the cur-
rently running ESW.

FOXCST REFERENCE
Table 19: AP: / unit-x, Fault Management (continued)

Affecting Severity
GSW General Software Equipment  Major The FOX has detected an unspecific
Alarm Alarm problem with the ESW running on this
unit.
MFA Maintenance Function Communica-  Warning An operator initiated maintenance func-
Active tion Alarm tion is active on this unit.
UNAV Unit Not Available Equipment  Critical The unit that is configured is either not
Alarm plugged or not recognized due to a fail-
ure.
NSW No Application Soft- Equipment  Major There is no application ESW installed on
ware Alarm the unit, or the application ESW has not
yet finished its boot process.
UNAS Unit Not Assigned Equipment  Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, execute
the “Assign” command in the “Main”
function of the unit.
UIC Unit Incompatible Equipment  Major The inserted unit is not compatible with
Alarm the assigned unit.
PWRSVE Battery Power Saving Equipment  Critical Power saving is active on the unit, i.e. it
Alarm is kept in the “reset” state during battery
power backup.
Power saving is not supported on the
CESM1 unit.
8.3 AP: / unit-x / neController
8.3.1 AP: / unit-x / neController, Overview

8.3.2 AP: / unit-x / neController, Main

− “Main - General”,
− “Main - Equipment”,
− “Main - Inventory”,
− “Main - Logbooks”, and
− “Main - Software”

FOXCST REFERENCE
Please note:
In the “Main - Equipment” management function only the “Equipment Status”
properties are available. The “Assignment Status” properties and the equip-
ment commands are not applicable.
8.3.3 AP: / unit-x / neController, Fault Management

Table 20: AP: / unit-x / neController, Fault Management

Affecting Severity
SWM Software Mismatch Equipment  Minor The running ESW does not match the
Alarm assigned ESW.
SSWNA Scheduled Software Equipment  Minor The ESW that is scheduled for installa-
Not Available Alarm tion is not available on the unit. Make
sure that the ESW is downloaded to the
unit.
SWIN Software Incompatible Equipment  Major The running ESW is not compatible with
With Network Element Alarm the version required by the NE type or
version.
HWIC Hardware Incompatible Equipment  Major The plugged HW is not compatible with
With Configuration Alarm the unit configuration HW stored in the
database. You may need to change the
HW or re-create the configuration for the
unit.
SWIC Software Incompatible Equipment  Major The ESW running on the unit is not com-
With Configuration Alarm patible with the unit configuration stored
in the database. You may need to
upgrade, or downgrade the ESW, or re-
create the configuration with the cur-
rently running ESW.
GSW General Software Equipment  Major The FOX has detected an unspecific
Alarm Alarm problem with the ESW running on this
unit.
MFA Maintenance Function Communica-  Warning An operator initiated maintenance func-
Active tion Alarm tion is active on this unit.
UNAV Unit Not Available Equipment  Critical The unit that is configured is either not
Alarm plugged or not recognized due to a fail-
ure.
NSW No Application Soft- Equipment  Major There is no application ESW installed on
ware Alarm the unit, or the application ESW has not
yet finished its boot process.
UNAS Unit Not Assigned Equipment  Warning The unit is not assigned and cannot be
Alarm configured. To assign the unit, execute
the “Assign” command in the “Main”
function of the unit.
UIC Unit Incompatible Equipment  Major The inserted unit is not compatible with
Alarm the assigned unit.

FOXCST REFERENCE
Table 20: AP: / unit-x / neController, Fault Management (continued)

Affecting Severity
PWRSVE Battery Power Saving Equipment  Critical Power saving is active on the unit, i.e. it
Alarm is kept in the “reset” state during battery
power backup.
Power saving is not supported on the
CESM1 unit.
8.4 AP: / unit-x / neController / esi-y
8.4.1 AP: / unit-x / neController / esi-y, Overview

8.4.2 AP: / unit-x / neController / esi-y, Main

8.4.2.1 AP: / unit-x / neController / esi-y, Main - General
For the Main / General dialogue, refer to 1KHW002466 FOXCST Operation.
Please note:
The administrative state of the ESI-1 and ESI-2 ports is controlled by the
PETS configuration. The administrative state is set to up as soon as the ESI
port is given a PETS clock priority other than “Disabled”.
→ For more information please refer to 1KHW002467 FOX61x TDM Ser-
vices
8.4.3 AP: / unit-x / neController / esi-y, Fault Management

Table 21: AP: / unit-x / neController / esi-y, Fault Management

Affecting Severity
LOS Loss Of Signal Communica-  Major There is no signal applied on the ESI
tion Alarm interface.
Please note:
The alarm state of the ESI-1 and ESI-2 ports can only be active if the corre-
sponding ESI port is selected as PETS clock source, i.e. given a PETS clock
priority other than “Disabled”.

FOXCST REFERENCE
8.5 AP: / unit-x / port-a
The CESM1 front Ethernet ports (port-a) are used for the connection of
external equipment.
Please note:
The local management port on the CESM1 unit is part of the management
interfaces and is described in 1KHW002466 FOXCST Operation.
The CESM1 implements two different types of Ethernet front ports:
• 2 SFP/SFP+ based ports (port-1 and port-2), and
• 3 electrical ports (port-3, port-4 and port-5).
The SFP/SFP+ based ports provide SFP cages for the implementation of
SFP/SFP+ modules. The supported speeds are 1000 Mbit/s (1 Gbit/s) and
10’000 Mbit/s (10 Gbit/s) according to the deployed SFP or SFP+ module.
The electrical ports provide speeds of 10, 100 or 1000 Mbit/s.
8.5.1 AP: / unit-x / port-a, Overview

− “Overview - Mirroring”
management function, please refer to 1KHW002464 FOX61x System
Description.
8.5.2 AP: / unit-x / port-a, Main

8.5.2.1 AP: / unit-x / port-a, Main – General
For a description of the “Labels” and “Alarm Status” parameters in the

− “Main - General”

FOXCST REFERENCE
Table 22: AP: / unit-x / port-a, Main – General

Interface Status Admin Status Up Select “Up” to bring the port into service
Down Select “Down” to take the port out of service.
Oper Status Up Shows the operational state is up. The state can only be
up if the administrative state is up and there are cur-
rently no failures.
If the port is SFP based the type must also be config-
ured.
Down Shows the operational state is down.
Testing Shows the port is in a testing state.

FOXCST REFERENCE
8.5.2.2 AP: / unit-x / port-a, Main – SFP
The Main - SFP management function is only available for the SFP based
ports:
• port-1, and
• port-2.
Table 23: AP: / unit-x / port-a, Main – SFP

Type Type Configuration None No SFP module is plugged
<List of SFP module Select the type of the plugged SFP module.
types> This should correspond to the Type Status
parameter.
Type Status None No SFP module is plugged
<Detected SFP module Shows the type of the plugged SFP module.
types>
Equipment Inven- Equipment State Ok Equipment state of the plugged SFP module.
tory Unknown
Empty
Plugged
Mismatch
Failed
Manufacturer Serial 0 … 16 characters These description fields provide information
Number about the vendor, part number, revision and pro-
Manufacturing Date 0 … 10 characters duction date.
Manufacturer ID 0 … 16 characters
Manufacturer Part 0 … 16 characters
Number

FOXCST REFERENCE
Table 23: AP: / unit-x / port-a, Main – SFP (continued)

Status Module Tempera- -2’147’483’648 … SFP module temperature, displayed in °C.
ture 2’147’483’647 °C
Supply Voltage -Infinity … Infinity mV SFP supply voltage, displayed in mV.
TX Bias Current -Infinity … Infinity uA SFP bias current, displayed in μA.
TX Output Power -2’147’483’648 … Optical power at the transmit interface, displayed
2’147’483’647 dBm in dBm.
RX Input Power -2’147’483’648 … Optical power at the receive interface, displayed
2’147’483’647 dBm in dBm.
8.5.2.3 AP: / unit-x / port-a, Main – Physical
Table 24: AP: / unit-x / port-a, Main – SFP

MAC Address 00:00:00:00:00:00 … Shows the physical (MAC) address of this port.
ff:ff:ff:ff:ff:ff This parameter is read-only.
Port Speed 10’000’000 bit/s Shows the port speed.
100’000’000 bit/s This parameter is read-only.
1’000’000’000 bit/s
10’000 Mbit/s
MTU 64 … 1’578 … 9’194 Maximum Transmission Unit, i.e. maximum IP
Octets, packet size.
step 2 Octets The MTU size is calculated including the IP
headers.

FOXCST REFERENCE
Table 24: AP: / unit-x / port-a, Main – SFP (continued)

Speed And Duplex Admin Auto Autonegotiation
10BaseT HD 10 Mbit/s, half duplex
10BaseT FD 10 Mbit/s, full duplex
100BaseTX HD 100 Mbit/s, half duplex
100BaseTX FD 100 Mbit/s, full duplex
1000BaseT FD 1 Gbit/s, full duplex
1000Base<xx> FD 1 Gbit/s, full duplex (for SFP modules only).
The <xx> string designates the SFP type, e.g.
SX.
10GigBase<xx> 10 Gbit/s, full duplex (for SFP+ modules only).
LR.
Operational 10BaseT HD 10 Mbit/s, half duplex
10BaseT FD 10 Mbit/s, full duplex
100BaseTX HD 100 Mbit/s, half duplex
100BaseTX FD 100 Mbit/s, full duplex
1000BaseT FD 1 Gbit/s, full duplex
1000Base<xx> FD 1 Gbit/s, full duplex (for SFP modules only).
SX.
10GigBase<xx> 10 Gbit/s, full duplex (for SFP+ modules only).
LR.
Other The speed and duplex setting cannot be deter-
mined or the port state is down.
Flow Control Admin  Port Ethernet flow control according to IEEE
 802.3x.
Flow control is a mechanism which allows the
Operational  receiving party of a connection to control the rate
 of the sending party.
Port Speed 10’000’000 bit/s Shows the port speed.
100’000’000 bit/s This parameter is read-only.
1’000’000’000 bit/s
10’000 Mbit/s
Please note:
Flow Control will be supported in a future release.
Please note:
For an overview on the specific characteristics of FOX chassis switch ports,
please refer to 1KHW002460 FOX61x Product Features and Characteristics.

FOXCST REFERENCE
8.5.3 AP: / unit-x / port-a, QoS

8.5.3.1 AP: / unit-x / port-a, QoS – QoS Scheduling
Table 25: AP: / unit-x / port-a, QoS – QoS Scheduling

QoS Scheduling Profile 1…5 Select the QoS scheduling profile number.
QoS scheduling profiles are configured with
ECST in the “Switching” view at Switching/
Bridges, bridge-1/QoS, Scheduling Profiles.
8.5.4 AP: / unit-x / port-a, Statistics

8.5.4.1 AP: / unit-x / port-a, Statistics – General
Table 26: AP: / unit-x / port-a, Statistics – General

64
RX Counters RX Octets 0…2 -1 Number of ingress octets
64
RX Unicast Packets 0…2 -1 Number of ingress unicast packets
RX Multicast Packets 0 … 264 -1 Number of ingress multicast packets
64
RX Broadcast Packets 0…2 -1 Number of ingress broadcast packets
32
RX Errors 0…2 -1 Number of ingress errored packets

FOXCST REFERENCE
Table 26: AP: / unit-x / port-a, Statistics – General (continued)

64
TX Counters TX Octets 0…2 -1 Number of egress octets
64
TX Unicast Packets 0…2 -1 Number of egress unicast packets
64
TX Multicast Packets 0…2 -1 Number of egress multicast packets
TX Broadcast Packets 0 … 264 -1 Number of egress broadcast packets
32
TX Errors 0…2 -1 Number of egress errored packets
Please note:
The statistics counter restart with 0 when they reach their upper range limit.

FOXCST REFERENCE
8.5.4.2 AP: / unit-x / port-a, Statistics – Ethernet

FOXCST REFERENCE
Table 27: AP: / unit-x / port-a, Statistics – Ethernet

64
Error Counters FCS Errors 0…2 -1 Number of ingress frames with FCS errors
64
Mac Transmit Errors 0…2 -1 Number of egress frames with a MAC sublayer transmit
error
Mac Receive Errors 0 … 264 -1 Number of ingress frames with a MAC sublayer receive
error
Oversized RX Frames 0 … 264 -1 Number of ingress frames that exceed the maximum per-
mitted frame size. This counter represents the FrameToo-
Longs counter of the Etherlike MIB.
Drop Events 0 … 232 -1 Number of ingress drop events
32
CRC Align Errors 0…2 -1 Number of ingress packets with CRC alignment errors
Undersize Packets 0… 232 -1 Number of ingress undersized packets (< 64 bytes)
Oversize Packets 0 … 232 -1 Number of ingress oversized packets that were longer
than the maximum permitted packet size
Fragment Packets 0 … 232 -1 Number of ingress fragment packets
Jabber Packets 0… 232 -1 Number of ingress jabber packets
Collision Counters a Deferred Transmissions 0 … 232 -1 Number of egress frames for which the first transmission
attempt is delayed because the medium is busy
Collisions 0 … 232 -1 Number of estimated collisions
Late Collisions 0… 232 -1 Number of times that a collision is detected later than one
slot time into the transmission of a packet.
Excessive Collisions 0 … 232 -1 Number of frames for which transmission fails due to
excessive collisions
Pause Frame Coun- RX Pause Frames 0 … 264 -1 Number of ingress pause MAC control frames
ters TX Pause Frames 0 … 264 -1 Number of egress pause MAC control frames
Receive Statistics Received Packets 0… 264 -1 Number of ingress packets
Received Octets 0… 264 -1 Number of ingress octets
64
64 Octets 0…2 -1 Number of ingress packets with a size of 64 octets
65 to 127 Octets 0 … 264 -1 Number of ingress packets with a size of 65 to 127 octets
64
128 to 255 Octets 0…2 -1 Number of ingress packets with a size of 128 to 255
octets
256 to 511 Octets 0 … 264 -1 Number of ingress packets with a size of 256 to 511
octets
octets
1024 to 1518 Octets 0 … 264 -1 Number of ingress packets with a size of more than 1024
octets
a. These counters are not available for 10 GbE interfaces. They are always 0.
Please note:
8.5.5 AP: / unit-x / port-a, Fault Management


Table 28: AP: / unit-x / port-a, Fault Management

Affecting Severity
LOS Loss Of Signal Communica-  Major The signal has been lost on the front
tion Alarm port, backplane port or redundant port.
Make sure the connector is plugged on
the front port and the remote equipment
is transmitting a signal.
On an internal port there is no signal
applied between the switch and the
backplane GbE star. This may be due to
a unit not sending a signal on this inter-
face. If this failure persists, you might
need to reboot the respective unit.
8.6 AP: / unit-x / port-a / mau
8.6.1 AP: / unit-x / port-a / mau, Overview

8.6.2 AP: / unit-x / port-a / mau, Main

8.6.3 AP: / unit-x / port-a / mau, Fault Management

Please note:
The mau fault management applies only to the SFP based Ethernet ports.
Table 29: AP: / unit-x / port-a / mau, Fault Management

Affecting Severity
ENA Equipment Not Availa- Equipment  Major There is no SFP/SFP+ module plugged,
ble Alarm or the SFP/SFP+ module cannot be rec-
ognized. Make sure you are using a
compatible SFP/SFP+ module on this
port.
FOXCST REFERENCE
Table 29: AP: / unit-x / port-a / mau, Fault Management (continued)

Affecting Severity
TRF Transmitter Failure Equipment  Major The transmitter part of the SFP/SFP+
Alarm module reports a failure. This may be
due to a HW failure. You may need to
replace the SFP/SFP+ module.
8.7 AP: / unit-x / iports
8.7.1 AP: / unit-x / iports, Overview

8.7.2 AP: / unit-x / iports, Main

8.8 AP: / unit-x / iports / iport-b
The CESM1 internal backplane Ethernet ports (iport-b) connect every ser-
vice unit plugged in the same network element via the GbE star. The back-
plane ports are 1GbE electrical ports. The speed of the ports is fixed.
The characteristics are identical for all internal ports iport-b:
• b = 1 … 10, 12, 14 … 21 in a FOX615,
• b = 7 … 10, 12, 14 in a FOX612.
8.8.1 AP: / unit-x / iports / iport-b, Overview

8.8.2 AP: / unit-x / iports / iport-b, Main

8.8.2.1 AP: / unit-x / iports / iport-b, Main – General
For a description of the “Labels” and “Alarm Status” parameters in the


FOXCST REFERENCE
Table 30: AP: / unit-x / iports / iport-b, Main – General

Interface Status Admin Status Up Select “Up” to bring the internal port into service
Down The internal port cannot be set to the Down state.
Oper Status Up Shows the operational state is up. The state can only be
up if the administrative state is up and there are cur-
rently no failures.
Down Shows the operational state is down.
Testing Shows the port is in a testing state.

FOXCST REFERENCE
8.8.2.2 AP: / unit-x / iports / iport-b, Main – Physical
Table 31: AP: / unit-x / iports / iport-b, Main – Physical

Port Speed 1’000’000’000 bit/s Shows the port speed.
This parameter is read-only.
MTU 1978 … 9’194 Octets Maximum Transmission Unit, i.e. maximum IP
packet size.
The MTU size is calculated including the IP
headers.
Speed And Duplex Admin 1000BaseX FD 1’000 Mbit/s, full duplex
<empty>
Operational 1000BaseT FD 1’000 Mbit/s, full duplex
Other The internal Ethernet port is not operational
Flow Control Admin  Port Ethernet flow control according to IEEE
 802.3x.
Flow control is a mechanism which allows the
Operational  receiving party of a connection to control the rate
 of the sending party.
Please note:
Flow Control will be supported in a future release.
Please note:
For an overview on the specific characteristics of FOX chassis switch ports,
please refer to 1KHW002460 FOX61x Product Features and Characteristics.

FOXCST REFERENCE
8.8.3 AP: / unit-x / iports / iport-b, QoS

8.8.3.1 AP: / unit-x / iports / iport-b, QoS – QoS Scheduling
Table 32: AP: / unit-x / iports / iport-b, QoS – QoS Scheduling

QoS Scheduling Profile 1…5 Select the QoS scheduling profile number.
QoS scheduling profiles are configured with
ECST in the “Switching” view at Switching/
Bridges, bridge-1/QoS, Scheduling Profiles.
8.8.4 AP: / unit-x / iports / iport-b, Statistics

8.8.4.1 AP: / unit-x / iports / iport-b, Statistics – General
Table 33: AP: / unit-x / iports / iport-b, Statistics – General

64
RX Counters RX Octets 0…2 -1 Number of ingress octets
64
RX Unicast Packets 0…2 -1 Number of ingress unicast packets
RX Multicast Packets 0 … 264 -1 Number of ingress multicast packets
64
RX Broadcast Packets 0…2 -1 Number of ingress broadcast packets
32
RX Errors 0…2 -1 Number of ingress errored packets

FOXCST REFERENCE
Table 33: AP: / unit-x / iports / iport-b, Statistics – General (contin-

64
TX Counters TX Octets 0…2 -1 Number of egress octets
64
TX Unicast Packets 0…2 -1 Number of egress unicast packets
64
TX Multicast Packets 0…2 -1 Number of egress multicast packets
TX Broadcast Packets 0 … 264 -1 Number of egress broadcast packets
32
TX Errors 0…2 -1 Number of egress errored packets
Please note:

FOXCST REFERENCE
8.8.4.2 AP: / unit-x / iports / iport-b, Statistics – Ethernet

FOXCST REFERENCE
Table 34: AP: / unit-x / iports / iport-b, Statistics – Ethernet

64
Error Counters FCS Errors 0…2 -1 Number of ingress frames with FCS errors
64
Mac Transmit Errors 0…2 -1 Number of egress frames with a MAC sublayer transmit
error
Mac Receive Errors 0 … 264 -1 Number of ingress frames with a MAC sublayer receive
error
Oversized RX Frames 0 … 264 -1 Number of ingress frames that exceed the maximum per-
mitted frame size. This counter represents the FrameToo-
Longs counter of the Etherlike MIB.
Drop Events 0 … 232 -1 Number of ingress drop events
32
CRC Align Errors 0…2 -1 Number of ingress packets with CRC alignment errors
Undersize Packets 0… 232 -1 Number of ingress undersized packets (< 64 bytes)
Oversize Packets 0 … 232 -1 Number of ingress oversized packets that were longer
than the maximum permitted packet size
Fragment Packets 0 … 232 -1 Number of ingress fragment packets
Jabber Packets 0… 232 -1 Number of ingress jabber packets
Collision Counters a Deferred Transmissions 0 … 232 -1 Number of egress frames for which the first transmission
attempt is delayed because the medium is busy
Collisions 0 … 232 -1 Number of estimated collisions
Late Collisions 0… 232 -1 Number of times that a collision is detected later than one
slot time into the transmission of a packet.
Excessive Collisions 0 … 232 -1 Number of frames for which transmission fails due to
excessive collisions
Pause Frame Coun- RX Pause Frames 0 … 264 -1 Number of ingress pause MAC control frames
ters TX Pause Frames 0 … 264 -1 Number of egress pause MAC control frames
Receive Statistics Received Packets 0… 264 -1 Number of ingress packets
Received Octets 0… 264 -1 Number of ingress octets
64
64 Octets 0…2 -1 Number of ingress packets with a size of 64 octets
65 to 127 Octets 0 … 264 -1 Number of ingress packets with a size of 65 to 127 octets
64
128 to 255 Octets 0…2 -1 Number of ingress packets with a size of 128 to 255
octets
octets
octets
1024 to 1518 Octets 0 … 264 -1 Number of ingress packets with a size of more than 1024
octets
a. These counters are not available for 10 GbE interfaces. They are always 0.
Please note:

FOXCST REFERENCE
8.9 AP: / unit-x / iports / iport-b / mau
8.9.1 AP: / unit-x / iports / iport-b / mau, Overview

8.9.2 AP: / unit-x / iports / iport-b / mau, Main


ANNEX
9 Annex
9.1 Associated documents
1KHW028514 FOX61x Abbreviations and Terms
1KHW002497 FOX61x Precautions and Safety
1KHW002459 FOX61x Release Notes
1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002463 FOX61x Lightning Protection
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002467 FOX61x TDM Services
1KHW002468 FOX61x Ethernet Services
1KHW002470 FOX61x LESU1
1KHW002471 FOX61x ETOP1
1KHW002472 FOX61x ELET1
1KHW002473 FOX61x LEDE1
1KHW002474 FOX61x DATI1
1KHW002475 FOX61x EPSI1
1KHW002476 FOX61x SAMO1
1KHW002477 FOX61x SAMO2
1KHW002478 FOX61x LEDS1
1KHW002479 FOX61x LEDA1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1

ANNEX
1KHW002482 FOX61x Electrical Cables

Contact us
ABB Switzerland Ltd
1KHW002469 © Copyright 2012 ABB. All rights reserved.

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: [email protected]
www.abb.com/utilitycommunication

FOX61x CESM1 1KHW002469

Uploaded by

Copyright:

Available Formats

FOX61x CESM1 1KHW002469

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 CESM1 1KHW002469

Uploaded by

Copyright:

Available Formats

ABB Power Systems

Release History: Release 1: December 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.: 1KHW002469

ABB Switzerland Ltd

7 Operation and maintenance 47

CESM1, CESM1-FUser Manual 3

4 CESM1, CESM1-FUser Manual

Figure 1: CESM1 unit application with a subtending FOX 10

CESM1, CESM1-FUser Manual 5

1.2 Symbols and notations

This User Manual uses the following symbols:

Risk of operating trouble!

1.3 Interfaces and circuit categories

Table 1: Electrical interfaces and circuit categories

CESM1, CESM1-FUser Manual 7

Table 2: Optical interfaces a

1.4 Document history

Table 3: Document history

1.5 Definition of terms

For an explanation of terms used in this document please refer to

8 CESM1, CESM1-FUser Manual

CESM1, CESM1-FUser Manual 9

Ethernet ETOP1 / Ethernet

Figure 1: CESM1 unit application with a subtending FOX

10 CESM1, CESM1-FUser Manual

2.2 Unit View

Figure 2: CESM1 (left) and CESM1-F (right) unit view

2.3 Block diagram

CESM1, CESM1-FUser Manual 11

Figure 3: Block diagram of CESM1

12 CESM1, CESM1-FUser Manual

3.1 Feature licences

Table 4: Feature licences relevant for this unit

For more information on feature licences please refer to 1KHW002459

3.2 CESM1 function overview

Table 5: CESM1 function overview - system features

CESM1, CESM1-FUser Manual 13

Table 5: CESM1 function overview - system features (continued)

Table 6: CESM1 function overview - management interfaces

a. 10GBASE-SR and -ER SFP+ modules will be available in a future release

Table 7: CESM1 function overview - Ethernet switching

14 CESM1, CESM1-FUser Manual

Table 7: CESM1 function overview - Ethernet switching (continued)

a. 10GBASE-SR and -ER SFP+ modules will be available in a future release

Table 8: CESM1 function overview - fault management

Table 9: CESM1 function overview - equipment features

CESM1, CESM1-FUser Manual 15

Table 9: CESM1 function overview - equipment features (continued)

Table 10: CESM1 function overview - other standards

3.3 CESM1-F function overview

Table 11: CESM1-F function overview - equipment features

Table 12: CESM1-F function overview - other standards

16 CESM1, CESM1-FUser Manual

CESM1, CESM1-FUser Manual 17

18 CESM1, CESM1-FUser Manual

Table 13: ESW types for the CESM1 unit

CESM1, CESM1-FUser Manual 19