0% found this document useful (0 votes)
192 views22 pages

M153 6 BORA X3M A4 E Screen

Uploaded by

Alex
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
192 views22 pages

M153 6 BORA X3M A4 E Screen

Uploaded by

Alex
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

OTN Manual

BORA-X3M Network Card


S30824-Q123-X103: 2500 Mbps, N42C/N42E node
S30824-Q123-X108: 2500 Mbps, N415 node
S30824-Q123-X102: 622 Mbps, N42C/N42E node
S30824-Q123-X107: 622 Mbps, N415 node
Doc. No.: AD-M153-E-6
COPYRIGHT AND TRADE SECRETS/LIABILITY
The present document and its contents remain the property of OTN Systems NV and shall not, without prior
written consent, be copied or transmitted or communicated to third parties, nor be used for any other purpose
than such as underlies their delivery to the addressee.

The present document and its contents may change in the course of time or may not be suitable in a specific
situation. Consequently, they are recommended as suggested guideline only.
OTN Systems NV hereby disclaims any liability for any damages that may result from the use of the present
document unless it is used with respect to the operation and maintenance of equipment originally
manufactured by OTN Systems NV and covered by its standard warranty.
Open Transport Network BORA-X3M Network Card

Contents List of Figures

1. INTRODUCTION ......................................................4 Figure 1 Network Reconfiguration: Quick=’0’, 120 ms ......... 6


1.1 General ..........................................................4 Figure 2 Network Reconfiguration: Quick=’1’, 50 ms ........... 6
1.2 Reference Documents ...................................4 Figure 3 Overview of Strap Settings JP600 ......................... 6
Figure 4 BORA-X3M Side View (Straps + DIP switch) ........ 6
2. CARD DESCRIPTION ..............................................4
Figure 5 Functional Operation of the TRMs ......................... 7
2.1 Functional Operation and Network Card
Figure 6 FPGA: Overview.................................................... 8
Tasks .............................................................4
Figure 7 Add/Drop Circuit .................................................... 8
2.2 Redundant Cards...........................................5
Figure 8 OTN-X3M Ring Frame in X3M-2500 ..................... 8
2.3 Functional Blocks...........................................5
Figure 9 OTN-X3M Ring Frame in X3M-622 ....................... 8
2.3.1 Strap Clear-NVRAM ......................................5
Figure 10 BORA-X3M: Front Panel ................................... 11
2.3.2 DIP Switches .................................................5
Figure 11 Headset symbols ............................................... 13
2.3.3 LIU .................................................................7
Figure 12 OTN Stand-Alone Clock .................................... 21
2.3.4 FPGA .............................................................8
Figure 13 OTN Slaved to an External Clock ...................... 21
2.3.5 Central Controller...........................................9
Figure 14 SDH integrated in OTN-X3M ............................. 21
2.3.6 Communication with the Interface Cards .......9
Figure 15 SONET integrated in OTN-X3M ........................ 21
2.3.7 Temperature Sensing .................................. 10
2.3.8 Alarms ......................................................... 10
2.3.9 Engineering Order Wire (EOW) ................... 10
2.3.10 NSM Interface .............................................. 10 List of Tables
2.3.11 OMS/OVS Interface ..................................... 10
2.3.12 Software Interfaces ...................................... 10
2.3.13 Self-test ....................................................... 10 Table 1 Reference Documents ............................................ 4
2.4 Visual Indications and Connectors on the Table 2 DIP Switch Settings ................................................ 5
Front Panel .................................................. 11 Table 3 OMS Connector: LED Description ........................ 11
2.4.1 LED Indications............................................ 11 Table 4 SY LED ................................................................. 11
2.4.2 Alphanumeric Display .................................. 11 Table 5 Full Display Example ............................................ 12
2.4.3 Connectors .................................................. 12 Table 6 OMS Connector: Pin Allocations .......................... 12
2.4.4 Hidden RESET button ................................. 13 Table 7 Display Data during Normal Operation ................. 14
2.5 Card Specifications ...................................... 13 Table 8 Display Data during Start-Up or in Case of Errors 15
Table 9 Error codes: Error/Fatal/Event/Status ................... 16
3. INSTALLATION GUIDELINES ............................... 20
Table 10 DIP switch settings ............................................. 20
4. ERROR LOCATION ............................................... 20 Table 11 DIP switches: OTN-X3M stand-alone ................. 21
Table 12 DIP switches: OTN-X3M slaves to ext. clock ...... 21
5. OPTICAL SIGNAL DISTANCES ............................ 20 Table 13 DIP switches: OTN-X3M with SDH Network ....... 21
Table 14 DIP switches: OTN-X3M with SONET Network .. 21
6. CLOCKING AND LOOP TIMING ........................... 20
6.1 What is Loop Timing (LT) ? ......................... 20
6.2 OTN-X3M Stand-alone (=no LT) .................. 20
6.3 OTN-X3M Slaved to an External Clock Signal
(=no LT) ....................................................... 20
6.4 SDH/SONET integrated in OTN-X3M
(=possible LT) .............................................. 20

7. LIST OF ABREVIATIONS ...................................... 22

AD-M153-E-6 Page 3 of 22
Open Transport Network BORA-X3M Network Card

1. INTRODUCTION Table 1 Reference Documents

1.1 General Ref. Number Title


This document describes the BORA-X3M network card: [1] AA-D100-&-* OTN Product Description

- S30824-Q123-X103, 2500 Mbps for N42C/N42E [2] AA-M921-* ESD Regulations


[3] AB-M408-&-* OTN-N42C/N42E Node
- S30824-Q123-X108, 2500 Mbps for N415
[4] AB-M118-&-* OTN-N415 Node
- S30824-Q123-X102, 622 Mbps for N42C/N42E [5] AG-M330-&-* OMS User Manual
- S30824-Q123-X107, 622 Mbps for N415 [6] AD-M155-&-* OTN TRM Modules
[7] AA-M205-&-* OTN Installation and Operation
X3M-2500 is supported as of OMS V4.5. This card is a new Manual
version of the BORA2500-X3M card (S30824-Q95). It is
indicated in the OMS which card is used (Q95  a. I/O with the Line Interface Units (LIU)
Generation = first; Q123  Generation = second).
Status and control data of SFP modules and SDH
X3M-622 is supported as of OMS V5.2.
framers, such as the SFP type and SDH/SONET
BORA2500-X3M and BORA-X3M (2500) network cards are alarms, are exchanged between the Line Interface
compatible if they have the correct loadware versions. Units and the FPGA and/or the microprocessor.
These loadware versions can be found on the OTNnet b. I/O with the Interface Cards
(https://extranet.otnsystems.com/) in the ‘compatibility’
section. The network card is responsible for processing status
and control data and for controlling the flow of user
The BORA-X3M, equipped with two TRMs (Transmit/
data between the interface cards and the optical ring
Receive Modules), represents the central control block of
via the node's backplane.
an OTN node, controls communication between the
interface cards and the optical ring and provides the c. I/O with the OMS
interface to the OTN Management System (OMS).
An embedded 10 Mbps Ethernet ring, communicating
The TRMs are hot-pluggable SFP (Small Form Factor over IP, interconnects all BORA-X3M network cards of
Pluggable) type OTRs that can be replaced from the front, an OTN network to the remote management OMS.
without having to remove the BORA-X3M card from the
node. An OMS can also be connected locally to the network
card via the 10/100 BASE-T Ethernet front panel
The N42C/N42E node provides two network card slots in connection.
order to increase OTN-X3M reliability/availability with
respect to the OTN family (N415 has one network card d. Alarming
slot). Both slots can host a network card at the same time,
with one network card acting as redundant/backup card When the network card does not receive synchroniza-
versus the other, which means that network cards are hot- tion signals from neighboring nodes in the ring (see
pluggable. Hot-pluggable also implies taking the ESD rules §2.3.8), a major and a minor alarm are generated and
into consideration. indicated by LEDs on the front panel of the network
card.
The BORA-X3M network card has been designed for
installation in an N42C/N42E/N415 node. Via the status & control bus on the backplane, the
alarm signals can be made available for external
In X3M-2500, the LIUs (Line Interface Units) of the BORA- processing at the digital input/output connector of the
X3M are SDH STM-16c and SONET OC-48c compatible on node's NSM/NSM415 (Node Support Module) module.
the fiber.
Each alarm is also visible on the OMS, just like the
In X3M-622, the LIUs (Line Interface Units) of the BORA- states of any digital input signal connected to the
X3M are SDH STM-4c and SONET OC-12c compatible on NSM/NSM415.
the fiber.
e. Status and Control Data of the Node

The BORA-X3M can communicate with the modules of


1.2 Reference Documents its node and/or the OTN network elements in 3 ways:

Table 1 is an overview of the documents being referred to - In the usual OTN manner via the Status & Control
in this document, ‘&’ refers to the language code and ‘*’ bus on the node’s backplane.
refers to the document issue.
- Via an additional high-performance TDM bus on
the node's backplane.

2. CARD DESCRIPTION - Via the embedded 10 Mbps Ethernet


communication channel.
2.1 Functional Operation and Network Card Tasks
The majority of node monitoring and controlling
The BORA-X3M network card can be used in an OTN-X3M functions in an OTN-X3M network are realized through
network. The BORA-X3M carries out the following major the NSM/NSM415 module being part of every node
tasks: equipped with BORA-X3M network cards.

AD-M153-E-6 Page 4 of 22
Open Transport Network BORA-X3M Network Card

f. Optical Ring Management a. Network Reconfiguration Switch1: QUICK

The network card manages the optical ring by carrying ATTENTION!


out the following tasks.
Quick Reconfiguration is possible as of OMS v7.3.
- Frame generation (in the master node).
- Start-up and synchronization of both rings. It is forbidden to set QUICK to ‘1’ when older network
- Determination of master node. cards are in the ring that do not have the QUICK
- Node reconfiguration in error situations. dipswitch onboard !!! If QUICK has to be set to ‘1’,
- Transfer of error indications to neighboring nodes. make sure all the network cards in this ring have set
- Extensive self-tests. this QUICK setting to ‘1’.
- Activation of major and minor alarm.
This setting has impact on reconfiguration times and
2.2 Redundant Cards must be the same on each network card that belongs
to the same ring. By default, this switch is set to ‘0’ or
Two BORA-X3M network cards (both 2500 Mbps or both
‘normal reconfiguration’.
622 Mbps) can be installed in one node in order to increase
the node’s availability. The two cards are connected ‘0’ = normal reconfiguration (120 ms); if a single fiber
optically in series, like two nodes in a conventional OTN. break occurs in the active OTN-X3M ring (e.g. primary
Only one network card is active at a time, the second card ring), the complete redundant OTN-X3M ring (e.g.
being in hot-standby mode. The active card is indicated on secondary ring) becomes the active ring. All nodes
the NSM module by means of a lit LED. have to swap from the active to the passive ring, which
takes approximately 100 ms. See Figure 1.
A direct point-to-point connection via the backplane
between two network cards installed in the same node ‘1’ = fast reconfiguration (< 50 ms); if a single fiber
allows the cards to monitor each other through heartbeat break occurs in the active OTN-X3M ring (e.g. primary
signals. Loss of a heartbeat signal results in the takeover of ring), the adjacent nodes to the fiber break go in
the second card and the creation of an alarm. loopback. This means that only these adjacent nodes
change their data flow states, e.g. from PP to PS and
The standby network card is continuously updated, so any
from PP to SP (see also §2.4.2). The other nodes are
takeover is realized with current node and network details.
not impacted and keep their data flow state PP, but
Just as in the conventional OTN, failure of one network show LB (=loopback) on the display; without fiber
card will result in a single ring being formed through break, PPqk is shown on the display. See Figure 2.
loopback, whereas failure of two network cards (active or The more nodes in the network, the bigger the
standby) in different nodes will produce separate rings. reconfiguration time, with a worst case of 50 ms for
very large networks (110 nodes, 1000 km fiber).
2.3 Functional Blocks
A double fiber break always results in loopback mode,
2.3.1 Strap Clear-NVRAM either in normal or fast reconfiguration.

See Figure 3. See Figure 4 for a side view of the BORA- b. Loop Timing (LT1, LT2), SDH/SONET
X3M network card showing the ‘Clear-NVRAM’ strap.
What is loop timing?
When the power supply of a network card is switched off,
the NVRAM ensures that existing services and IFC control See Chapter 6.1.
data can be recovered upon reboot. Once in the 'off' state,
the network card can hold its existing services almost Configure loop timing
forever, because these are stored in a FLASH EEPROM or
This DIP switch in Figure 4 is needed to configure loop
NVRAM (=NON VOLATILE RAM) upon switching off.
timing when the OTN network must be slaved to an
When the power supply of the network card is switched on external SDH or SONET network. With loop timing, the
(reboot), the NVRAM strap setting determines what is going SDH framer uses the same clock as the received data
to happen. stream’s one for transmission.

a. When the strap is up (clear), the NVRAM is initialized All the nodes in the network must have the same
with default system values, i.e. existing services and SDH/SONET setting (either all SONET or all SDH).
IFC control data are lost. The network card shows ‘CLR
Table 2 DIP Switch Settings
NVRAM’ on the front panel display (see Figure 10).
After switching off the network card, setting the strap
back to its normal position (strap is down) and Switch Description Value
switching on the network card again, all existing Switch1 Normal Reconfig., 120 ms ‘0’ in all nodes
services are cleared and it still shows ‘FAIL EC2’. The QUICK Quick Reconfig., <50 ms ‘1’ in all nodes
backplane stays disabled until the OMS writes its
programmed services back onto the network card. SDH External network is SONET ‘0’ in all nodes
External network is SDH ‘1’ in all nodes
b. When the strap is down (normal), all existing services
and IFC control data are recovered and still No external network All nodes the same,
operational. all ‘0’ or all ‘1’
LT2 (1) No loop timing, default ‘0’
2.3.2 DIP Switches
Configure loop timing in ‘1’
The network card is equipped with several DIP switches. TRMX2 (1)
Other DIP switches on the card, but not visible on Figure 4,
are spare switches. The following two switches are active:

AD-M153-E-6 Page 5 of 22
Open Transport Network BORA-X3M Network Card

Normal Reconfiguration
QUICK = ‘0’, 120 ms reconfig. time

PP PP SS SS

OTN-X3M OTN-X3M

PP PP SS SS
single fiber break secondary ring
on active ring becomes active

Figure 1 Network Reconfiguration: Quick=’0’, 120 ms

Fast Reconfiguration
QUICK = ‘1’, <50 ms reconfig. time

PPqk PPqk LB LB

OTN-X3M OTN-X3M

SP
PPqk PPqk PS
ring in
single fiber break loopback
on active ring adjacent adjacent
node node

Figure 2 Network Reconfiguration: Quick=’1’, 50 ms

Clear Clear
Card Issue
Msb Lsb
1234
NVRAM

NVRAM

‘1’
‘0’

Clear
NV-RAM

strap up = clear NVRAM, init backup RAM


strap down = normal after init backup RAM

Figure 3 Overview of Strap Settings JP600


QUICK
SDH

LT1
LT2

1234
‘1’
‘0’

Figure 4 BORA-X3M Side View (Straps + DIP switch)

AD-M153-E-6 Page 6 of 22
Open Transport Network BORA-X3M Network Card

c. Card Issue and works on a 32 kbps level (cf the other members of
the OTN family).
This DIP switch in Figure 4 indicates the network card
issue. The user is not allowed to change these Error checking tests are carried out at the optical level
settings. MSB and LSB are screened onto the PC (Optical Signal Loss), at the SDH level (B1, B2 and B3
board. A switch in the upper position indicates a logical Bit Error Rate tests) and on the embedded OTN frame
‘1’. The card issue can be read from the display or (CRC check).
from the OMS.
The LIUs are responsible for the transmission and
The node and ring number are being set through DIP reception of time-multiplexed frames between sub-
switches on the NSM/NSM415 module (see Ref. [3], [4] in sequent nodes and for the transmission of data and the
Table 1) clock signal to the network card.

2.3.3 LIU Figure 5 represents the functional operation of optical


transceiver modules (TRMX1 and TRMX2) in a BORA-
a. General X3M network card.
The network card is fitted with two optical SFP c. Eye Safety
transceiver modules that can be replaced hot-
pluggable through the front panel. The optical transceiver module is a class 1 laser
product and complies with IEC 825-1, EN60825 and
Transceivers are available as I (Intra-Office), S1 and FDA 21 CFR 1040.10.
S2 (Short Haul), and L1 and L2 (Long Haul) versions.
Their optical characteristics can be found in Ref. [6]. d. Status and Control Data

These replaceable TRM transceiver modules convert In order to allow for LIU monitoring and remote control,
the optical signal of the OTN ring to an equivalent the LIU provides a number of status and control bits
electrical signal, and vice versa (see Figure 5). The which can be accessed via the OMS.
SDH/SONET/OTN framing is detected in non-
replaceable separate chips on the card. - BORA-X3M card type: X3M-2500 or X3M-622

The TRMs can be used with: - TRM Information


This information enables OMS to determine which
- 50/125 or 62.5/125 µm multi-mode fibers type of transceiver module is installed on the
- 9/125 µm single-mode fibers network card of a node.

The S and I type codes are derived from the SDH - SDH Framer configuration data
notation. Unfortunately, the SONET notation is
reversed with respect to the S and I codes. - SDH Framer settings

The CWDM (=Coarse Wavelength Division Multi– - SDH Framer status data
plexing) technique allows to simultaneously
e. TRM specifications
transmit/multiplex multiple frequencies on the optical
fiber. The CWDM TRMs have colored handles. The See Ref. [6].
color indicates which wavelength is transmitted by the
TRM. (So)
Secondary BORA-X3M
See Ref. [6] for an overview of the TRM types. Ring TRMX2

Optical
b. Functional Operation Previous Transmitter
Node
SDH
In X3M-2500, the OTN data is transmitted between FRAMER
nodes in an STM-16c or OC-48c concatenated Primary Optical
container. Ring Receiver
(Pi)
In X3M-622, the OTN data is transmitted between F
nodes in an STM-4c or OC-12c concatenated P
container. G
~
µ Proc. 155.52
Mhz A
The SDH/SONET link layer performs SDH signal
TRMX1
termination, SDH synchronization, SDH clock recovery, (Po)
bit error measurement and word alignment. Primary Optical
Ring Transmitter

The BORA-X3M places the OTN frame in the SDH


FRAMER
SDH/SONET payload over the optical link. The OTN
frame carries both user data (for the interface cards) Next Optical
and OTN overhead data (such as OTN-EOW and OMS Node Receiver

node communication). As a result, the SDH or SONET


overhead bytes are not used by the OTN application, Secondary
and can be modified by other devices without Ring
disturbing the OTN. (Si)

The add/drop functionality between interface cards and Figure 5 Functional Operation of the TRMs
OTN frame is implemented in the GRIAE gate array,

AD-M153-E-6 Page 7 of 22
Open Transport Network BORA-X3M Network Card

2.3.4 FPGA
Mgmt. Comm. Channel
Processor

The gate array (GRIAE) contains the core logic to support


the optical rings, synchronize with other nodes, reconfigure
nodes, and add/drop user data between interface cards ET Tables 1
and ring. New FPGA configuration data can be downloaded
from the OMS. The FPGA comprises the following major
functional elements (see Figure 6 for a high-level overview
of the FPGA): SDH Ring
Add/
Framers Interfaces
Drop
I/F
a. Ring Interface

The ring interface contains the logic to support the


optical rings, e.g. generation and recognition of the
8
time-multiplexed OTN frames, synchronization with the
Sync.
other nodes in the network and node reconfiguration in S&C
the event of network failures. S&C Bus

The GRIA state machine decides which path the data


stream follows, e.g. the switches between primary and Figure 6 FPGA: Overview
secondary ring are controlled by the GRIA in case of
reconfiguration due to an error. The configuration is
shown on the alphanumeric display.

b. Embedded Communication Channel Framer


Rx Framer
MUX
An embedded communication channel interconnects all Tx
Internal
nodes within the OTN network with the OTN Connections
management system via an in-band 10 Mbps Ethernet
ring. The Ethernet ring is accessible via the OMS
connector on the card's front panel. Although it would
Drop Add
be possible to interconnect other external IP devices Buffer
Buffer
via this Ethernet ring, Ethernet traffic different from
OMS and OVS traffic is not allowed on this interface
because it could disturb existing services.

c. Add/Drop Mechanism
Backplane

In X3M-2500: On the ring each OTN-X3M frame is


represented by 9216 bytes including 128 system bytes. Figure 7 Add/Drop Circuit
This results in 9088 data bytes and a net data rate of
2326 Mbps. See Figure 8.

In X3M-622: On the ring each OTN-X3M frame is X3M-2500: 9216 bytes = system + data bytes, X = system byte
represented by 2304 bytes including 75 system bytes.
This results in 2229 data bytes and a net data rate of
570.624 Mbps. See Figure 9. X X X
… X

In X3M-2500/X3M-622: The add/drop circuit (see 9088 bytes = data bytes


Figure 7) removes the bits intended for the node from
the incoming data stream and distributes them in …
accordance with its configuration tables to the correct
interface cards via the backplane. In the reverse
direction, data arriving from the interface cards via the Figure 8 OTN-X3M Ring Frame in X3M-2500
backplane is multiplexed to the outgoing data stream.
Ring side and backplane timing are decoupled from
each other through frame buffers. A flexible buffer
handles the effects of phase difference between the X3M-622: 2304 bytes = system + data bytes, X = system byte
transmitted and received frames.

For the add/drop circuit the data bit rate has been X X X
… X
enlarged by adding 256 extra time slots, where these
are only used for internal connections between 2229 bytes = data bytes
interfaces with a net bandwidth of maximum 256 Mbps.
On the add interface, data in these extra time slots is …
not being sent to the output framer but to the drop
interface instead resulting in a virtual internal ring in the
FPGA. The internal connection therefore does not use Figure 9 OTN-X3M Ring Frame in X3M-622
or reduce ring bandwidth.

AD-M153-E-6 Page 8 of 22
Open Transport Network BORA-X3M Network Card

d. Backplane Interfacing - Checking the FPGA and memories during self-


tests.
The backplane interface provides for data and status &
control communication between the interface cards and - Distributed switching (e.g. video).
the network card(s).
- Alarms.
- For exchanging user data, the interface cards are
connected in a star configuration to the network - Communication with the interface cards via the
card (to both, if two network cards are installed) TDM bus.
resulting in an individual data bus for each
- Communication between redundant network cards
interface card. Data transfer is full duplex.
via a dedicated link.
- Status & control information is exchanged between b. Memories
network card(s) and interface cards, power
supplies and NSM/NSM415 module via a common Three different memories support network card
low-speed bus as with earlier OTN systems. For operation.
high-speed applications, status and control During operation, the SDRAM holds the system
information is exchanged with the microprocessor application software and working memory required by
via the 2 Mbps TDM bus. this embedded portion of the management func-
tionality.
e. EOW Interface
The RTOS and application software for the
The EOW interface is connected to the EOW connector microprocessor is stored in a flash EEPROM, in which
(microphone and headset) on the card's front panel. also the Ethernet MAC address is kept. The
f. Synchronization microcontroller program consists of a fixed part (the
BOOT code) and a variable part containing application
The FPGA interfaces with various clock circuits on the data, FPGA configuration data and the IP address. The
network card providing clock signals for circuit, node or entire original firmware is factory-installed during
network operation. A connection is also provided for production. Afterwards, new firmware for the adjustable
synchronization of the OTN ring by an external clock portion can be downloaded from the OMS. While
signal at the ext-clock connector on the card's front downloading the application and FGPA configuration
panel (only if the system card is ring master). data, the network remains functional. When the new
firmware is activated, however, the connections with
For default settings of the clock bits on the the node concerned are disrupted during restart.
NSM/NSM415-module, the ring master is the system
card with the lowest MAC address. A system card can A non-volatile RAM (NVRAM) acts mainly as backup
be favored as ring master by changing the clock bits on RAM during power failures and ensures that services
the NSM/NSM415 module (see ref. [3]). and control bits are kept (except video switching).
When the power is restored, the microprocessor copies
g. Microprocessor Interface the stored data from the NVRAM to the corresponding
function blocks as FPGA, TRMS, etc. The node can
An interface provides for communication between the now restore the services and control bits immediately
FPGA and the microprocessor via the processor's without having to wait for the OMS to download this
buffered data and access bus. data.

During normal node operation, the configuration tables in


the FPGA know which OTN frame bits have to be added to
2.3.5 Central Controller
or dropped from the backplane (interfaces) into the node.
The central controller platform comprises the micro- The configuration tables are initialized by the OMS.
processor and the system memories. Therefore, should the microprocessor fail, the gate array
continues to process the OTN ring data; only the
a. Microprocessor microprocessor's tasks described above are not supported.
The microprocessor can be reset without affecting the
A powerful industrial microprocessor, running on a node's add/drop functionality.
LINUX real-time operating system is used to initialize,
control and monitor the gate-array. The processor
realizes the following major tasks: 2.3.6 Communication with the Interface Cards

- Communication with the TRMs. For communication with the interface cards, the backplane
is equipped with several buses.
- Controlling the SDH framers.
a. Data Bus
- Communication with SDRAM, flash and NVRAM.
For the exchange of user data, the interface cards are
- Processing temperature sensing. connected in star configuration to the network card (to
both, if two network cards are installed), which results
- Reading the card's hardware edition. in an individual data bus for each interface card. Data
- Driving the display. transfer is full duplex. Via these buses, the gate array
drops the user data from the ring to the correct
- Interfacing with the card's Ethernet switch for interface cards. Simultaneously, user data from the
communication with the local OMS or for OMS interface is multiplexed into the outgoing transmission
communication via the embedded 10 Mbps bit stream. Low-speed (LX) and high-speed (HX) data
communication channel. is transferred via the same buses.

AD-M153-E-6 Page 9 of 22
Open Transport Network BORA-X3M Network Card

b. Status/Control Bus Point-to-point communication between both nodes is


possible if the microphone and headphone (black
Status & control information is exchanged between connector) are plugged in in one other node.
network card(s) and interface cards, power supplies
and the NSM/NSM415 module via a common low- Only these nodes can speak and listen to each other. Other
speed S&C bus as with earlier OTN systems. Also, for nodes can listen into this conversation as well, but their
high-speed applications, status and control information microphones must be unplugged. This function is used
is directly exchanged between interface cards or during installation or maintenance activities.
modules and the microprocessor via the 2 Mbps TDM
bus. The EOW interface performs the analog/digital conversion
(PCM) and vice versa, and detects whether a microphone
The FPGA can request different status data, such as is plugged in.
the card type, from the interface cards. The network
support module NSM/NSM415 and the OMS can read The EOW link does not have to be programmed via the
out and interpret this data. OMS, since the required frame bits are reserved in the OTN
overhead.
The OMS can set different parameters of the interface
cards via the gate array and the status/control bus. The EOW function in a node can only be used when this
node can be reached, meaning that at least one ring must
2.3.7 Temperature Sensing be in the SYNC2 state.

Given that excessive temperatures could adversely affect 2.3.10 NSM Interface
the lifetime of electronic components, the network card is
equipped with temperature sensing. A sensor monitors the The network card communicates with the NSM/NSM415
temperature surrounding the network card and the node support module via the backplane status and control
corresponding circuitry decides whether the temperature is (S&C) bus.
within range or out of range. In range = [-20°C/-4°F 
2.3.11 OMS/OVS Interface
+70°C/158°F]. The temperature status is reported to the
OMS and via the S&C bus on the backplane to the The OMS is connected to a network card via a 10/100
NSM/NSM415 indicating the temperature state by means of BASE-T Ethernet interface. This is also the interface that is
a LED. used when video switching via OVS is used. The
microprocessor and the connected OMS communicate via
The temperature will be reported on the display only if the
measured temperature is out of range. an Ethernet controller in the microprocessor and the
TCP/IP protocol. Each network card has its unique Ethernet
2.3.8 Alarms address. The MAC and IP addresses are stored in the flash
EEPROM.
a. Output
Certain alarm conditions can be configured in the OMS As a security precaution to avoid unauthorized access, the
to activate the major/minor alarm contacts on the NSM. OMS port can be disabled at remote sites via the
'OMS/MGT Port Security' feature in OMS, see Ref.[5] in
The network card itself does not offer an alarm Table 1 for more information.
connector. However, on its front panel the network card
offers two red LEDs indicating major and minor alarms ATTENTION!
as configured in OMS. This also means that the Ma/Mi
LEDs on the network card behave similar as the  Ethernet traffic different from OMS and OVS traffic is
‘OUTPUT LED1’ (=minor) and ‘OUTPUT LED2’ not allowed on this interface because it could disturb
(=major) on the NSM/NSM415. existing services.
Default configuration: a lit major alarm LED (Ma)
2.3.12 Software Interfaces
indicates that neither of the rings is in the SYNC2
status. A lit minor alarm LED (Mi) indicates that at least In the OTN-X3M network the network element and network
one ring is in the SYNC0 status. Major and minor alarm functionality are distributed throughout the system. The
situations also occur when the node is switched off (no decentralized portion of the management functions mainly
power). resides in the network card of the nodes and can be
b. Input addressed via the communication channel. Through a
External alarm conditions can be injected into the OMS number of specific APIs, external systems can activate the
via the digital I/O connector on the NSM/NSM415 functions of the internal OTN system. The most obvious of
module. These alarms can be assigned a logical name these software interfaces is the OMS native API and OVS
API. Others would be Webserver, SNMP, OPC, etc.
in the OMS. The network card itself does not
participate in this alarms-input flow. For a more detailed description of these applications, see
2.3.9 Engineering Order Wire (EOW) Ref. [1] and [5] in Table 1.

2.3.13 Self-test
A headset with microphone (S26361-F2D87-L1) can be
plugged into the 3.5mm jacks (EOW connector) on the When switching on the supply voltage, the node goes
network card's front panel. through a self-test, before switching itself into the ring.
Requesting and acknowledging an EOW link is realized For that purpose, the microprocessor initializes specific
through the corresponding pushbutton on the node’s registers of the gate-array. The network card is then
NSM/NSM415 module. The red CALL LED on the network completely tested, e.g. the microprocessor’s ROM and
card is lit, whenever a microphone (red connector) is RAM memories, the gate array, etc. The TRM modules are
plugged into a network card somewhere in the network. also checked for type number, status and control logic,

AD-M153-E-6 Page 10 of 22
Open Transport Network BORA-X3M Network Card

electrical loop-back, etc. After the self-test, a number of Table 3 OMS Connector: LED Description
settings determining the card's operation, such as the
node’s hardware address and any errors detected during LED Color Status
the self-test, are read into the FPGA.
R&T Orange Link down
2.4 Visual Indications and Connectors on the Front
Panel R&T Not lit, dark Link up
R Green Link up, Ethernet packets are
The BORA-X3M front panel (Figure 10) is equipped with being received at the front panel.
the following:
T Green Link up, Ethernet packets are
- LED indications being transmitted at the front
panel.
- an alphanumeric display

- connectors
Table 4 SY LED
- a hidden reset button
Color Description
2.4.1 LED Indications
Red The OTN-X3M ring is in SYNC0
The following LEDs can be found on the network card's
front panel: R, T, CALL, Ma, Mi, SDH, BER, and SY. No color When receiving SYNC1 frames

a. R and T LEDs on the OMS connector Green When receiving SYNC2 frames

The OMS can access the OTN-X3M network via the


OMS connector. This connector has two integrated bi- c. Ma and Mi LEDs
color LEDs, which can be lit green or orange. The
description of these LEDs can be found in Table 3. A lit Ma (Major alarm) LED shows that the network card
has raised a major alarm. A lit Mi (Minor alarm) LED
b. Call LED indicates that a minor alarm has been raised by the
network card. The alarm situations that result in a
The lit Call LED indicates that an EOW microphone Minor or Major alarm are configured in the OMS. See
has been plugged into a network card somewhere in also §2.3.8. Major (Minor) alarms created in the
the network. N42C/N42E/N415 Alarm Relais Tab in OMS are
displayed on the Ma(Mi) Leds on the front panel. A lit
BORA-X3M

SFP Module LED indicates an active alarm.

d. SDH LED

A lit SDH LED indicates that an OOF (=Out Of Frame)


SDH alarm has been detected via the line interface.

DISP.
e. BER LED
O R
M A lit BER LED indicates that a CRC Bit error in OTN-
S T frame (GRIA) has been detected.
Call Ma Mi

E
The BER LED is lit for at least 100 ms upon each
O failure. A dark LED indicates an error-free period of
W
100 ms.
SDH BER SY
f. LED SY
T So
R
M Bicolor LED, See Table 4.
X
2 Pi
During start-up (self-test) and in case of an error, the
SDH BER SY
bicolor SY LED does not have the functions as
T Po described in Table 4. During self-tests, the LED is
R
M continuously lit red.
X
1 Si

2.4.2 Alphanumeric Display

The 4-character alphanumeric display provides information


on node operation and settings. The upper character in the
CLK
display is the MSB.
RESET

Display during normal operation


BORA-X3M

During normal operation the main display cycle shows by


default sequentially the following information, each for
approximately 1 second.
Figure 10 BORA-X3M: Front Panel

AD-M153-E-6 Page 11 of 22
Open Transport Network BORA-X3M Network Card

Table 5 Full Display Example


NOTE: (N<no>) refers to the cycles in Table 7.
Repeats Cycle No. Display
1. Network card type (N1).
Normal Cycle
2. Own (this) address of the network card (N3). 1 BORA2500-X3M-8S
3. Node flow and master/slave configurations (N5). 2 THIS R10 0200 SYS1
Contin-
4. Active and redundant network card status (N6). uously 3 LINK PP-S
4 ACT
5. External clock or not (optional, N7).
Extended Cycle 1 (Push button again)
6. Error codes (if any), (N_err) see more info further on.
1 PREV R10 0100 SYS1
Extended display with pushbutton 2 THIS R10 0200 SYS1
3 times
Below the alphanumeric display, a pushbutton is available 3 NEXT R10 0300 SYS2
allowing to access an extended display. Pushing this button 4 LINKqk PP-S
once changes the display from the main to the extended
display cycle. Pushing this button several times in a row Extended Cycle 2 (Push button again). CONDITIONAL
makes the display scroll through the different items of the CYCLE: only displayed when the measured
extended list. If you want to observe an item for a while, do temperature on the network card is out of range
not push the button any longer. After a while, the display (<-20°C/-4°F or >+70°C/158°F)
will return to the default main display cycle automatically. 3 times 1 TEMP 72.5°C
See the extended cycle below: Extended Cycle 3 (Push button again)
NOTE: (N<no>) refers to the cycles in Table 7. 1 IP 192.168.93.230
3 times
2 HOST X3Mv2_1675
1. Prev-this-next node/Link/Quick (X3M info = N2/N3/N4/
N5). Extended Cycle 4 (Push button again)
1 TRM1 M 850nm
2. Temperature in °C measured on the card. This cycle is 3 times
only displayed in an alarm situation when the 2 TRM2 I 1310nm
temperature is out of range (<-20°C/-4°F or
>+70°C/158°F). Extended Cycle 5 (Push button again)
1 HW PLD EDITION 3 / GRIA
3. IP Address + hostname: Example: 192.168.093.104 + 3 times EDITION 18 / MCFRAMER
HOST X3Mv2_1675. EDITION 0
4. TRMX1 & TRMX2 type (I, S1,S2, M, L1, L2); (Ref. [6]). Extended Cycle 6 (Push button again)
5. Hardware versions (framer, FPGA, EPLD). 1 SW BOOT_1.0.3 /
X3M_3.3.4 /
3 times X3M_FB_2.20.0 /
6. Software versions (boot, application).
X3M_V2_3.3.4
7. Frame type: SDH or SONET.
Extended Cycle 7 (Push button again)
8. MAC Address: Example: 0800 0672 BF24. 3 times 1 Carrier SON
9. Identification of the previous (PSYS), the own/this Extended Cycle 8 (Push button again)
(TSYS), and the next (NSYS) network card for start-up.
3 times 1 MAC 0800 0672 E619
See Table 5 for a full X3M-2500 display example. Table 7 Extended Cycle 9 (Push button again)
explains the display data during normal operation.
1 PSYS 1135 CLK2
Display during Start-up or in Case of Errors 3 times 2 TSYS 26FC CLK2
Table 8 shows the information displayed during start-up 3 NSYS 0011 CLK1
(self-test) or in case of errors (Table 9). If, after the self-test,
the node is not switched into the ring due to internal errors, Table 6 OMS Connector: Pin Allocations
an error code is displayed indicating why this did not
happen. Pin No. Signal
2.4.3 Connectors 1 Transmit output (+)
The network card front panel is equipped with the following 2 Transmit output (-)
connectors: 3 Receive input (+)
a. OMS: A twisted-pair screened RJ45 female connector 4,5 ---
(see Figure 10) to connect the OMS or OVS. This 6 Receive input (-)
connection operates according to the 10/100 Mbps
BASE-T Ethernet standard and provides access to the 7,8 ---
Ethernet communication channel in the ring and/or to
the microprocessor (see Table 6 for pin allocations).

AD-M153-E-6 Page 12 of 22
Open Transport Network BORA-X3M Network Card

e. Electromagnetic Compatibility

- Emission: EN 61000-6-3 and EN 61000-6-4, EN


55022 (Class B);
- Immunity: EN 61000-6-1 and EN 61000-6-2.
Microphone input Headphone output
f. Power Consumption (with two TRMs)

Figure 11 Headset symbols - BORA-X3M +5 V: 3.6 A

g. Card Size

b. EOW: Two 3.5 mm jacks (one for the microphone and - Height: 262 mm
one for the headphone, see Figure 11) for the EOW - Length: 236 mm
(Engineering Order Wire) headset. - Width: 25.25 mm (5TE)

c. TRMX1+TRMX2: 2 Duplex LC female optical h. OMS/OVS Connection


connectors; one connector for TRMX2, receiving and - Via a twisted pair RJ45 connector for 10/100 Mbps
transmitting the optical signals RX2 and TX2, and one BASE-T Ethernet interface.
for TRMX1, receiving and transmitting the optical
signals RX1 and TX1. i. Certification
d. CLK: A 50Ω male SMB connector to connect an - CE Marking
external TTL clock signal. An external clock signal of - EMC directive 2004/108/EC
36.864 MHz ± 25 ppm, 2.048 MHz ± 25ppm (E1) or - LVD directive 2006/95/EC
1.544 MHz ± 25ppm (T1) is required. When this
network card is the Ring Master, the clock will be j. System Data Rate (X3M-2500)
slaved to this external signal.
- SDH data rate: 2488.32 Mbps
- OTN data rate: 2326.528 Mbps
2.4.4 Hidden RESET button
k. System Data Rate (X3M-622)
This pushbutton is hidden and accessible through a small
hole at the bottom of the front panel. Pushing the RESET - SDH data rate: 622.08 Mbps
button for a few seconds clears the alphanumerical display - OTN data rate: 570.624 Mbps
and forces a warm start of the microprocessor without
l. Optical Data Rate (X3M-2500)
affecting the fixed services of the network card.
- Optical Data Rate = SDH Data Rate
If the warm restart has reached boot cycle S4 in Table 8,
= 2488.32 Mbps
and the RESET button is pushed again for a few seconds,
the FPGA is reloaded and the node will optically leave the m. Optical Data Rate (X3M-622)
ring (=cold boot).
- Optical Data Rate = SDH Data Rate
= 622.08 Mbps
2.5 Card Specifications n. Eye Safety
a. Temperature (node surrounding) - The integrated optical transceiver modules are
class 1 laser products and comply with IEC 825-1,
- Operation:
EN60825 and FDA21 CFR 1040.10.
-20 °C to +55 °C
-4 °F to +131 °F o. Ordering Information
- Start-up: - Nodes:
-10 °C to +55 °C - The BORA-X3M modules can be installed in
+14 °F to +131 °F N42C/N42E/N415 nodes.
- Storage and shipping: - OMS Software Release:
-20 °C to +70 °C
-4 °F to +158 °F - OMS v4.5 and up (X3M-2500)
- OMS v5.2 and up (X3M-622)
b. Relative Humidity (non-condensing)
- BORA-X3M Modules in X3M-2500:
- Operation: 20 % to 80 % at 25 °C (+77 °F)
(node surrounding) - BORA-X3M S30824-Q123-X103 (N42C/N42E)
- BORA-X3M S30824-Q123-X108 (N415)
- Storage and shipping: 20 % to 95 %
- BORA-X3M Modules in X3M-622:
c. Weight (with two TRMs)
- BORA-X3M S30824-Q123-X102 (N42C/N42E)
- BORA-X3M: approx. 520 g - BORA-X3M S30824-Q123-X107 (N415)
(approx. 1.14 pounds)
- SFP OTR Modules (see Ref. [6])
d. MTBF at +25 °C (+77 °F) (without TRMs)

- 51 years (=2238 FITs)

AD-M153-E-6 Page 13 of 22
Open Transport Network BORA-X3M Network Card

Table 7 Display Data during Normal Operation

Cycle Display (text scrolls Explanation


over display)
N1 BORAbbbb-X3M-#S bbbb = X3M bandwidth
#S = amount of slots
Examples:
- BORA2500-X3M-8S / BORA2500-X3M-4S
- BORA622-X3M-8S / BORA622-X3M-4S
N2 PREV Rrr nnnn SYSp Number of previous system card compared to the transmission direction on the
data-carrying ring.
rr = ring number
nnnn = node number
p = position of system card in node (1 = left, 2 = right)
Example:
PREV R10 0100 SYS1
= Network card in ring 10, node 0100 in the left slot.
If a node is in loopback mode, the previous and next node numbers are the same. If
the previous or next node number cannot be read, node number 'NA' will be
displayed.
N3 THIS Rrr nnnn SYSp Number of own system card. (See also cycle N2 for more information)
N4 NEXT Rrr nnnn SYSp Number of next system card compared to the transmission direction on the data-
carrying ring. (See also cycle N2 for more information)
N5 Link XXqk-Y X3M link information
XX = Node configuration (PP, PS, SP, SS or LB)
qk = is only displayed if ‘quick’ setting is on and no single fiber break;
See §2.3.2a for more info on the quick setting.
Y = M: Master system card/S: Slave system card
the node configuration indication (PP, PS, SP, SS or LB) shows the direction of the
data flow through the node:
- PP: from the primary input (Pi) to the primary output (Po).
- PS: from the primary input (Pi) to the secondary output (So).
- SP: from the secondary input (Si) to the primary output (Po).
- SS: from the secondary input (Si) to the secondary output (So).
- LB: there is a loopback in the OTN ring and the loopback has occurred in other
nodes; the nodes having formed the loopback will display PS or SP.
Example:
PP-S
= data flow in the node is from primary input to primary output and the node is
configured as slave.

AD-M153-E-6 Page 14 of 22
Open Transport Network BORA-X3M Network Card

N6 ACT ACT = Active


PAS No errors have been detected during the self-test, or the card is stand-alone (in the
STB node) without serious errors. The card comes into the ring, and the add/drop
NIS functionality is operational. However, the network card software application may
DEF decide to disable the add/drop functionality in case of configuration data errors.
PAS = Passive
No (serious) errors have been detected during the self-test. The card comes into the
ring and the network card software is operational. The add/drop functionality is
disabled. The node configuration data on the network card is not yet up to date with
the configuration data of the active network card.
STB = Hot Stand-by
No (serious) errors have been detected during the self-test. The card comes into the
ring and the network card software is operational. The add/drop functionality is
disabled. The node configuration data on a stand-by network card is kept up to date
by the active network card, such that the standby network card can take over the
functionality from the active network card if the latter becomes erroneous or on the
operator's request.
NIS = Not In Service
Serious errors have been discovered during the self-test, but the card is still able to
participate in the ring even though the add/drop functionality is disabled. Data
received from the previous network card is transmitted without changes to the next
system card. The card functions as a repeater.
DEF = Defect
Serious errors have been discovered during the self-test, potentially causing
disruption of the OTN-X3M network. The card will not participate in the network,
causing loopback at network level.
N7 EClk Z Only when an external clock is applied, the display indicates whether or not the
network card is slaved to this clock.
- EClk -: the network card is slaved to the data clock (if configured as slave) or
uses the local 36.864 MHz oscillator (if configured as master and if incoming
external clock is invalid).
- EClk 2 MHz: the network card is slaved to an external E1 2.048 MHz clock (and
is thus master).
- EClk 1.5 MHz: the network card is slaved to an external T1 1.544 MHz clock
(and is thus master).
- EClk 36 MHz: the network card is slaved to an external 36.864 MHz clock.

N_err Error code(s) This cycle is only displayed in case of error(s).


Normal faults are preceded by ERR
Critical faults are preceded by FAIL
If none occur, this field is not displayed and the display returns to the first main cycle
N1. More than one error may occur resulting in more error cycles with the error
codes accordingly. After the errors have been displayed, the display always returns
to first main cycle N1.

Table 8 Display Data during Start-Up or in Case of Errors

Cycle Character Explanation


4 3 2 1
S1 X 3 M Processor has started up
S2 < Bandwidth X3M Ring > Possible values:
2500/622
S3 B O O T Boot control is handed over to kernel
S4  Flash file system has been mounted
S5 B O O T Boot in progress
S6   FPGA has been configured
S7 B O O T Boot in progress
S8    All self-tests have been executed
S9 B O O T Boot in progress
S10     Applications have been started
Optional Error Code Any time during start-up, an error code may be displayed
depending on the stage in which an error has been detected.

AD-M153-E-6 Page 15 of 22
Open Transport Network BORA-X3M Network Card

Table 9 Error codes: Error/Fatal/Event/Status

Display Category Self-test Explanation Curative action


detected
ERRORS
ERR E11 ERROR NO Application failure. Program problem during Let the card run during at least 10
normal operation minutes. Then reboot. The error
should now disappear. If the card
starts rebooting spontaneously
again then replace it.
ERR E31 ERROR YES Error detected in Framer1 (TRMX1, SIPO) Reboot the card, if the problem
persists then replace it.
ERR E32 ERROR YES Error detected in Framer2 (TRMX2, PISO) Reboot the card, if the problem
persists then replace it.
ERR E33 ERROR NO Routine test detected error in SFP1 Replace SFP1
ERR E34 ERROR NO Routine test detected error in SFP2 Replace SFP2
ERR E35 ERROR YES Self-test detected error during data loop test Reboot the card, if the problem
TRMX1 persists then replace it.
ERR E36 ERROR YES Self-test detected error during data loop test Reboot the card, if the problem
TRMX2 persists then replace it.
ERR E3C ERROR YES Temperature sensor failure Replace card
ERR E3D ERROR NO Error on Status & Control bus Communication problem between
NSM and BORA. Or the BORA, or
the NSM, or the node (backplane)
must be replaced
ERR E3K ERROR NO GRIA FPGA FUSE Replace the card
ERR E3P ERROR NO GIGE FUSE Replace the card
ERR E3Q ERROR NO GIGE SFP Replace ETX SFP
ERR E3R ERROR YES BCM Replace the card
ERR E3S ERROR NO BCM COMMUNICATION Replace the card
ERR E40 ERROR NO NVRAM CRC error - section NODE Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E41 ERROR NO NVRAM CRC error - section IFC1 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E42 ERROR NO NVRAM CRC error - section IFC2 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E43 ERROR NO NVRAM CRC error - section IFC3 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E44 ERROR NO NVRAM CRC error - section IFC4 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E45 ERROR NO NVRAM CRC error - section IFC5 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E46 ERROR NO NVRAM CRC error - section IFC6 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E47 ERROR NO NVRAM CRC error - section IFC7 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E48 ERROR NO NVRAM CRC error - section IFC8 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E49 ERROR NO NVRAM CRC error - section ETX Try reloading the NVRAM control
data from OMS, if this fails then
replace the card

AD-M153-E-6 Page 16 of 22
Open Transport Network BORA-X3M Network Card

Display Category Self-test Explanation Curative action


detected
ERR E4A ERROR NO NVRAM CRC error - section X1 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4B ERROR NO NVRAM CRC error - section X2 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4C ERROR NO NVRAM CRC error - section TRMX1 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4D ERROR NO NVRAM CRC error - section TRMX2 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4E ERROR NO NVRAM CRC error - section BRD Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4F ERROR NO NVRAM CRC error - section HWF Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4G ERROR NO NVRAM CRC error - section TLM1 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4H ERROR NO NVRAM CRC error - section TLM2 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4I ERROR NO NVRAM CRC error - section PRM1 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4J ERROR NO NVRAM CRC error - section PRM2 Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4K ERROR NO NVRAM CRC error - section VLAN Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4L ERROR NO NVRAM CRC error - section ULM CTRL Try reloading the NVRAM control
data from OMS, if this fails then
replace the card
ERR E4M ERROR NO NVRAM CRC error - section Try reloading the NVRAM control
GigeETXCommon CTRL data from OMS, if this fails then
replace the card
ERR E4N ERROR NO NVRAM CRC error - section GigeETXPort1 Try reloading the NVRAM control
CTRL data from OMS, if this fails then
replace the card
ERR E4P ERROR NO NVRAM CRC error - section GigeETXPort2 Try reloading the NVRAM control
CTRL data from OMS, if this fails then
replace the card
ERR E4Q ERROR NO NVRAM CRC error - section Try reloading the NVRAM control
GigeETXSegment1 CTRL data from OMS, if this fails then
replace the card
ERR E50 ERROR NO NVRAM CRC error - section ARAM Try reloading the connection data
from OMS, if this fails then replace
the card
ERR E51 ERROR NO ULM NVRAM CRC error - section ARAM Try reloading the connection data
from OMS, if this fails then replace
the card
ERR E60 ERROR NO Communication between redundant system Or the active, or the standby card,
cards fails or both have to be replaced
ERR E61 ERROR NO Update of redundant network card fails Make sure that the loadware of the
network cards is compatible, if the
problem persists replace the
network cards

AD-M153-E-6 Page 17 of 22
Open Transport Network BORA-X3M Network Card

Display Category Self-test Explanation Curative action


detected
ERR E70 ERROR YES Error loading driver Reboot the card, if the problem persists
then replace it.
ERR E72 ERROR NO Error loading daemon Reboot the card, if the problem persists
then replace it
ERR E80 ERROR NO Error mounting file system Reboot the card, if the problem persists
then replace it
ERR E90 ERROR NO Power Supply failure Possible error in configure data from
OMS, check power supply configuration
on OMS, if this is correct, then one of the
power supplies is failing and has to be
replaced
ERR EB1 ERROR NO Bandwidth fault on IFC1 Reboot the card, if the problem persists
then replace it

ERR EB2 ERROR NO Bandwidth fault on IFC2 Reboot the card, if the problem persists
then replace it

ERR EB3 ERROR NO Bandwidth fault on IFC3 Reboot the card, if the problem persists
then replace it

ERR EB4 ERROR NO Bandwidth fault on IFC4 Reboot the card, if the problem persists
then replace it

ERR EB5 ERROR NO Bandwidth fault on IFC5 Reboot the card, if the problem persists
then replace it

ERR EB6 ERROR NO Bandwidth fault on IFC6 Reboot the card, if the problem persists
then replace it

ERR EB7 ERROR NO Bandwidth fault on IFC7 Reboot the card, if the problem persists
then replace it

ERR EB8 ERROR NO Bandwidth fault on IFC8 Reboot the card, if the problem persists
then replace it
ERR EC0 ERROR NO TRMX1 optical fiber cabling fault Switch TRMX1 and TRMX2 fiber
ERR EC1 ERROR NO TRMX2 optical fiber cabling fault Switch TRMX1 and TRMX2 fiber
ERR EC3 ERROR NO Mismatch ring/NSM number Indicates the NSM ring/node number has
been changed on a running system
without rebooting the BORA => reboot
BORA
ERR EC6 ERROR NO 4-slot BORA in 8-slot NODE Replace card with an 8-slot type BORA
ERR MAC ERROR NO The Ethernet MAC number is invalid Replace card
ERR NODE ERROR YES Invalid node number Or the NSM has an invalid node number
configured, or the BORA or the NSM is
defective. Check and replace card if
necessary
ERR RING ERROR YES Invalid ring number Or the NSM has an invalid ring number
configured, or the BORA or the NSM is
defective. Check and replace card if
necessary
ERR SFPO ERROR NO No valid OTN SFP modules detected Reboot the card; if the problem persists
then replace it.
FATAL ERRORS
FAIL ECA FATAL NO Auto loopback2 in GRIA FPGA active Reboot the card; if the problem persists
then replace it.
FAIL EC2 FATAL YES Mismatch between Ring and NVRAM node Set correct Ring & Node number in OMS
number. When this error is active, the (BORA screen). Check if the ring & node
backplane is disabled. number on the NSM are valid. Replace
NSM. Replace BORA.
FAIL E10 FATAL NO Error starting applications - Program Otherwise this is due to the fact that the
initialization fails number in NVRAM control data does not
match the NSM data => check
configuration data, fix and reload the card
from OMS.

AD-M153-E-6 Page 18 of 22
Open Transport Network BORA-X3M Network Card

Display Category Self-test Explanation Curative action


detected
FAIL E12 FATAL NO Error during GRIA load NOTE: changing the ring/node number
on NSM always requires a reboot
FAIL E13 FATAL NO Error loading ULM Reboot the card; if the problem persists
then replace it.
FAIL E14 FATAL NO Error loading GIGE Reboot the card; if the problem persists
then replace it.
FAIL E1A FATAL NO Kernel crash Reboot the card; if the problem persists
then replace it.
FAIL E1B FATAL NO Application crash Reboot the card; if the problem persists
then replace it.
FAIL E2A FATAL NO Failure reading kernel image Reboot the card; if the problem persists
then replace it.
FAIL E30 FATAL YES GRIA hardware error Clear the NVRAM, reboot and reload
the card via OMS. If the card starts
booting spontaneously, then replace it
FAIL E37 FATAL YES RAM failure Reboot the card; if the problem persists
then replace it.
FAIL E3A FATAL YES Error detected in Ethernet communication Reboot the card; if the problem persists
then replace it.
FAIL E3E FATAL NO Add/drop table parity error Reboot the card; if the problem persists
then replace it.
FAIL E3F FATAL YES HDLC bus self-test failure (2Mbit Reboot the card; if the problem persists
backplane communication) then replace it.
FAIL E3G FATAL NO No NSM card present Replace the card
FAIL E3H FATAL NO ULM A/D XOR Reboot the card; if the problem persists
then replace it.
FAIL E3I FATAL YES ULM FPGA Replace NSM and/or BORA
FAIL E3N FATAL YES GIGE FPGA Reboot the card; if the problem persists
then replace it.
FAIL E71 FATAL YES Error loading critical driver Reboot the card; if the problem persists
then replace it.
FAIL E73 FATAL NO Error loading critical daemon Reboot the card, if the problem persists
then replace it
FAIL E81 FATAL NO Error mounting critical file system Reboot the card, if the problem persists
then replace it
FAIL OS! FATAL NO OS Failure Reboot the card; if the problem persists
then replace it.
FAIL FATAL NO No (valid SFP) modules detected. Reboot the card; if the problem persists
SFP? Backplane will not be activated. then replace it.
EVENTS
IPCH EVENT NO IP settings changed - The system will boot
ORSC EVENT NO OMS requested reset - The system will
cold reboot
ORST EVENT NO OMS requested reset - The system will
reboot
SWCC EVENT NO Download complete - A cold boot will follow
SWCH EVENT NO Download complete - A warm boot will
follow
STATUS
ACT STATUS NO This system card is the active copy
DEF STATUS NO The system card has a major defect, it is
not operational any longer
NIS STATUS NO The system card is not in service, but can
be reached by the OMS
PAS STATUS NO The system card is the standby copy, but it
is not up to date yet
STB STATUS NO The system card is the standby copy and it
is ready for takeover

AD-M153-E-6 Page 19 of 22
Open Transport Network BORA-X3M Network Card

3. INSTALLATION GUIDELINES processing clocks. If both network clocks are in spec, or


meet each other requirements, the synchronization occurs
See Ref. [7] in Table 1. automatically and no loop timing must be configured.
ATTENTION: If no automatic synchronization occurs (synchronization
Pushing the test button of the NSM/NSM415 for at least alarms), one network must provide the master clock and
three seconds will deactivate the status/control bus of the the other network slaves to this master clock. It must be
ACTIVE BORA for one minute. In this minute you can agreed between the network operators which clock will act
safely plug in or pull out a redundant network card without as master. The most accurate and secure clock of the two
disturbing any services. networks must be chosen as master clock. As a result, the
other network must configure loop timing.

If loop timing is used, it must be configured in


4. ERROR LOCATION network1 OR in network2 but never in both networks
together.
Check the LEDs and the alphanumeric display on the
network card when switching on the supply voltage and 6.2 OTN-X3M Stand-alone (=no LT)
during the optical connection. Repair errors, if any.
(See Figure 12, Table 11) In this situation, one of the nodes
a. If no LED is lit on the network card, then check: in the ring will be clock master. It does not matter for the
- the supply voltage presence user which system card this is. All system cards have their
- the power supply connection own internal clock crystal. The system card with the lowest
- the fuses on the power supply modules or the MAC address will be the master, whereas the other nodes
network card synchronize to the node with the lowest MAC address.

b. If an error code occurs on the alphanumeric display, All the nodes in the network must have the same
replace the network card. SDH/SONET setting (either all SONET or all SDH).

6.3 OTN-X3M Slaved to an External Clock Signal (=no


c. If the green LEDs on the network card are not lit
LT)
(above the TRM modules), the node is not
synchronized. Check the optical connections. (See Figure 13, Table 12) The OTN-X3M frame will
d. If the red LEDs on the network card are lit (above the synchronize to the ‘master clock’. If the master clock fails,
TRM modules), the node is not synchronized. Check OTN-X3M will synchronize to the ‘spare clock’. If both
the optical connections. clocks are missing or erroneous, OTN-X3M will synchronize
to the node with the lowest MAC address (can be any node
e. If the alphanumeric display continues to display FAIL in the ring).
followed by a fatal error code (see Table 8 and
Table 9), then there is a fatal error on the network card; This will only happen if the clock bit settings on the NSM
non-fatal error codes, if any, are displayed after cycle module have been set correctly for the node containing the
N6 (see Table 7 and Table 9). network card to which the external clock has been applied
See Ref.[3]/[4] and Table 12.
f. In case of non-fatal errors, the BORA-X3M program will
6.4 SDH/SONET integrated in OTN-X3M (=possible
try to operate normally, possibly with reduced
LT)
functionality.

g. In case of fatal errors, the BORA-X3M cannot operate (See Figure 14, Table 13) The OTN-X3M clock will be the
in an acceptable way any longer. node with the lowest MAC address, and can be any node in
the ring (not necessarily the node connected to the external
h. Failures where "self-test detected" indicates ‘yes’ (see subnetwork).
Table 9) can only be set/cleared by executing self-tests
(cold boot!). The link between node 10 and 20 will be synchronized to
the SDH clock that both nodes discover in the receiver, and
i. CHECK THE QUICK SETTING (see §2.3.2a). that is independent of the OTN-X3M clock.

If the sub-network were a SONET network, the


5. OPTICAL SIGNAL DISTANCES SDH/SONET DIP switch in Figure 4 would be set to value
‘0’ in all nodes.
See Ref. [6] in Table 1.
Table 10 DIP switch settings

6. CLOCKING AND LOOP TIMING Switch Description Position/value


Also refer to Ref. [3] and Ref. [4] in Table 1 for the DIP SDH External network is SONET ‘Down’ in all nodes
switch settings on the NSM/NSM415 module.
External network is SDH ‘Up’ in all nodes
6.1 What is Loop Timing (LT) ?
No external network All nodes the
Loop timing is a mechanism that can be configured in a same, all ‘Up’ or all
network (e.g. OTN) to slave its network clock to another ‘Down’.
external network master clock (e.g. SDH or SONET).
LT2 (1) No loop timing, default ‘Down’
Always try without loop timing first!
Configure loop timing in ‘Up’
When two different networks (e.g. OTN and SDH) are TRMX2 (1)
linked to each other, they have to synchronize their data

AD-M153-E-6 Page 20 of 22
Open Transport Network BORA-X3M Network Card

Table 11 DIP switches: OTN-X3M stand-alone

DIP switch location Switch Position/value NODE 10 NODE 20

LT1/LT2/SDH DIP switch on SDH All nodes the NO EXTERNAL


BORA-X3M same, all ‘Up’ or CLOCK
(See Figure 4) all ‘Down’.

LT2 ‘Down’ in
NODE 40 NODE 30
all nodes

LT1 ‘Down’ in Figure 12 OTN Stand-Alone Clock


all nodes

S3 DIP switch NSM/NSM415 CLK(1,0) ‘10’ all nodes


module, switches (3;4)
Master Clock Spare Clock
Table 12 DIP switches: OTN-X3M slaves to ext. clock

DIP switch location Switch Position/value NODE


NODE 10
10 NODE
NODE 20
20

LT1/LT2/SDH DIP switch SDH All nodes the


on BORA-X3M same, all ‘Up’ or EXTERNAL
(See Figure 4) all ‘Down’. CLOCK

LT2 ‘Down’ in all nodes

LT1 ‘Down’ in all nodes NODE


NODE 40
40 NODE
NODE 30
30

S3 DIP switch CLK(1,0) Node10=’00’


Figure 13 OTN Slaved to an External Clock
NSM/NSM415 module, Node20=‘01’
switches (3;4) Other Nodes=’10’

Table 13 DIP switches: OTN-X3M with SDH Network


T T

DIP switch location Switch Position/value NODE


NODE 10
10
R
M
SDH R
M NODE
NODE 20
20
X X
2
LT1/LT2/SDH DIP switch SDH ‘Up’ in all nodes 1

on BORA-X3M
(See Figure 4) LT2 Node10=’down’
Node20=’up’
Other Nodes=’down’

LT1 Node10=’up’
Node20=’down’ NODE
NODE 40
40 NODE
NODE 30
30
Other Nodes=’down’

S3 DIP switch CLK(1,0) ‘10’ all nodes Figure 14 SDH integrated in OTN-X3M
NSM/NSM415 module,
switches (3;4)

T T
Table 14 DIP switches: OTN-X3M with SONET Network R SONET R
NODE
NODE 10
10 M M NODE
NODE 20
20
X X
1 2
DIP switch location Switch Position/value

LT1/LT2/SDH DIP switch SDH ‘Down’ all nodes


on BORA-X3M
(See Figure 4) LT2 Node10=’down’
Node20=’up’
Other Nodes=’down’ NODE
NODE 40
40 NODE
NODE 30
30

LT1 Node10=’up’
Node20=’down’ Figure 15 SONET integrated in OTN-X3M
Other Nodes=’down’

S3 DIP switch CLK(1,0) ‘10’ all nodes


NSM/NSM415 module,
switches (3;4)

AD-M153-E-6 Page 21 of 22
Open Transport Network BORA-X3M Network Card

7. LIST OF ABREVIATIONS

AC Alternating Current SDH Synchronous Digital Hierarchy


ACT Active SDRAM Static Data Random Access Memory
API Application Programming Interface SFP Small Form factor Pluggable
ARAM Allocation RAM SNMP Small Network Management Protocol
BCM BCM5382 Broadcom Chip SONET Synchronous Optical NETwork
BER Bit Error Rate STB Standby
BORA Broadband Optical Ring Adapter STM-16 Synchronous Transport Mode for 2.5Gbps
SDH
CLK Clock
STM-4 Synchronous Transport Mode for 0.622 Gbps
CRC Cyclic Redundancy Check
SDH
CWDM Coarse Wavelength Division Multiplexing TCP Transmission Control Protocol
DC Direct Current TDM Time Division Multiplexing
DIP Dual Inline Package TRM Transceiver Module
EEPROM Electrically Erasable Programmable Read- TRO Transceiver Module OTN
Only Memory
TTL Transistor Transistor Logic
EMC ElectroMagnetic Compatibility
ULM Universal Link Module
EN European Norm
EOW Engineering Order Wire
EPLD Erasable Programmable Logic Device
ESD ElectroStatic Discharge
ET(H) Ethernet
FEC Fast Ethernet Controller
FPGA Field Programmable Gate Array
GPOI General Purpose Output/Input
GRIAE Gigabit Ring Interface Adaptor Enhanced
HDLC High-level Data Link Control
HS High Speed
HW HardWare
IEC International Electrotechnical Commission
IP Internet Protocol
I/O Input/Output
IFC InterFace Card
LED Light Emitting Diode
LIU Line Interface Unit
LSB Least Significant Bit
LT Loop Timing
LVD Low Voltage Directive
LX Low Speed Extreme
Ma Major (alarm)
MAC Media Access Control
Mi Minor (alarm)
MSB Most Significant Bit
MTBF MeanTime Between Failures
NSM Node Support Module
NVRAM Non Volatile RAM
OC-48 Optical Carrier for 2.5Gbps SONET
OMS OTN Management System
OOF Out Of Frame
OPC Ole for Process Control
OTN Open Transport Network
OTR Optical Transmitter and Receiver
P/B PushButton
PCB Printed Circuit Board
PCM Pulse Coded Modulation
PSU Power Supply Unit
RAM Random Access Memory
ROM Read-Only Memory
RTOS Real-Time Operating System
S&C Status & Control
SCC System Communication Controller

AD-M153-E-6 Page 22 of 22

You might also like