Product Description

Commercial in Confidence
Product Description
Nimbra One/300 series
HIGH PERFORMANCE MULTI-SERVICE EDGE/ACCESS SWITCH
This is the product description for Nimbra One/300 series switches and its modules. The information
presented in this document may be subject to change without notice. For further information on product
status and availability, please contact info@netinsight.net or visit www.netinsight.net
Product Description Nimbra One/300 series 1(79) 2009-04-15

NID2655 Rev. B7
Copyright 2006-2009 by Net Insight AB, Sweden. All rights reserved. This document may not be reproduced
in whole or in part without the expressed written permission of Net Insight AB
While this document intends to describe the products to highest possible accuracy, the fast pace of product
development may alter the functionality or characteristics given for a certain product within this document.
Therefore:
The specifications and information in this document are provided "as is" and are subject to change without
notice. All statements, information, and recommendations in this document are provided without warranty of
any kind, expressed or implied, including without limitation any warranty concerning the accuracy, adequacy,
or completeness of such specifications and information or the result to be obtained from using such
specifications or information. Net Insight AB shall not be responsible for any claims attributable to errors,
omissions, or other inaccuracies in the specifications or information in this document, and in no event shall
Net Insight AB be liable for direct, indirect, special, consequential or incidental damages arising out of the
use or inability to use this document.
Net Insight and Nimbra are trademarks of Net Insight AB, Sweden. All other trademarks are the property of
their respective owners.
Net Insight AB
Box 42093
SE-126 14 Stockholm
Sweden
Phone: +46 8 685 04 00
Fax: +46 8 685 04 20
E-mail: info@netinsight.net
April 2009
Stockholm, Sweden

NID2655 Rev. B7
TABLE OF CONTENTS
1 PRODUCT OVERVIEW........................................................................................................................................................... ...5
2 NIMBRA ONE/300 SERIES SYSTEM STRUCTURE................................................................................................................7

2.1 NIMBRA ONE/300 SERIES ARCHITECTURE.................................................................................................................... 8
2.2 NIMBRA ONE BASE UNIT............................................................................................................................................ ......8
2.3 NIMBRA 300 SERIES BASE UNIT ....................................................................................................................................9
2.4 SW MANAGEMENT.................................................................................................................................................... ......10
2.5 INTERNAL SWITCH MODULE........................................................................................................................... ..............12
3 TRUNK AND ACCESS INTERFACES............................................................................................................................. ........22

3.1 TRUNK/ACCESS MODULE COMMON FUNCTIONALITY..............................................................................................23
3.2 1 GBPS OPTICAL TRUNK MODULE...............................................................................................................................24
3.3 4 X OC-3/STM-1 TRUNK MODULE........................................................................................................................... .......26
3.4 2 X OC-12/STM-4 TRUNK MODULE......................................................................................................................... .......28
3.5 OC-48/STM-16 X-ADM MODULE........................................................................................................................... ..........30
3.6 4 X DS3/E3 TRUNK MODULE................................................................................................................................... .......33
3.7 4 X OC-3/STM-1 ACCESS MODULE................................................................................................................................ 35
3.8 FAST AND GIGABIT ETHERNET ACCESS MODULE.....................................................................................................38
3.9 E1/T1 ACCESS MODULE............................................................................................................................................ .....40
3.10 SDI VIDEO ACCESS MODULE....................................................................................................................... ...............43
3.11 ASI TRANSPORT ACCESS MODULE............................................................................................................................46
3.12 8 X ASI TRANSPORT ACCESS MODULE.....................................................................................................................49
3.13 8 X AES/EBU ACCESS MODULE................................................................................................................................... 52
3.14 HD-SDI FUNCTIONALITY ON THE NIMBRA 340-HD....................................................................................................55
4 MANAGEMENT....................................................................................................................................................................... .59
4.1 INTERFACES AND MANAGEMENT NETWORK.............................................................................................................59
4.2 FAULT MANAGEMENT................................................................................................................................................. ....61
4.3 PERFORMANCE MANAGEMENT................................................................................................................................... .62
4.4 NIMBRA VISION.......................................................................................................................................... .....................63
5 SERVICE PROVISIONING.................................................................................................................................................... ...64

5.1 BASIC CONCEPTS.......................................................................................................................................................... .64
5.2 ETS – ETHERNET TRANSPORT SERVICE....................................................................................................................65
5.3 ITS – ISOCHRONOUS TRANSPORT SERVICES...........................................................................................................66
6 NETWORK RESTORATION ............................................................................................................................... ....................68

6.1 RE-ROUTING................................................................................................................................................................... .68
6.2 1+1 PROTECTION ........................................................................................................................................................ ...69
6.3 ASI/SDI PROTECTION..................................................................................................................................... ................70
6.4 TRUNK MANAGER APPLICATION..................................................................................................................................70

NID2655 Rev. B7
7 SPECIFICATIONS............................................................................................................................................................ ........71
7.1 PHYSICAL......................................................................................................................................................................... 71
7.2 MANAGEMENT................................................................................................................................................................ .72
7.3 GIGABIT ETHERNET (BUILT-IN; NIMBRA 300 SERIES)................................................................................................72
7.4 ASI (BUILT-IN; NIMBRA 340)................................................................................................................................ ............72
7.5 4 X SONET/SDH SFP (BUILT-IN; NIMBRA 360)..............................................................................................................73
7.6 HD-SDI (BUILT-IN; NIMBRA 340-HD)........................................................................................................................ .......73
7.7 POWER ...................................................................................................................................................................... ......73
7.8 ENVIRONMENT.......................................................................................................................................................... ......73
7.9 REGULATORY COMPLIANCE........................................................................................................................ .................73
7.10 NETWORK INTERFACE PLUG-IN MODULES..............................................................................................................74
7.11 NIMBRA 360 BASE AND GOLD CLOCK OPTIONS.......................................................................................................75
7.12 ORDERING INFORMATION............................................................................................................................... ............76
8 USER DOCUMENTS............................................................................................................................................................... .77
9 ACRONYMS AND ABBREVIATIONS.............................................................................................................................. ........77

NID2655 Rev. B7
1 Product Overview
The Nimbra One/300 series is a family of modular multi-service edge/access switches targeting operators of
media rich networks. Currently the series include the Nimbra One, Nimbra 340, Nimbra 340-HD and the
Nimbra 360 switches.
Nimbra One is an eight-slot subrack with vertically mounted plug-in units. The Nimbra 300 series is a
slimmed down version of the Nimbra One with room for two horizontally mounted plug-in units. With its fixed
built-in Gigabit Ethernet and Video or Trunk ports it provides a cost-effective solution for transport of
demanding video and data applications.
Key features include:
• Multi-service platform with fixed built-in ports for common applications
• Unsurpassed switching granularity down to 512 kbps
• Highest network utilization 95+%
• Optical control plane with signaled end-to-end provisioning and restoration
• Guaranteed 100% QoS independent of network load
• Unique Multicast support with full QoS for any level of forking
• Large selection of pluggable optical interfaces including CWDM and DWDM
• Transport security/integrity by inherent channel isolation
• Extremely low wander and jitter
• Very simple management and handling
Figure 1. Nimbra 360 (with two 8 x ASI Transport Access modules inserted)
In order to optimize cost and flexibility the Nimbra 300 series Base Unit has built-in ports for Gigabit Ethernet
(all) and DVB-ASI (Nimbra 340) or HD-SDI (Nimbra 340-HD) or SONET/SDH trunks (Nimbra 360).
The Nimbra 300 series switches are fully interoperable with the Nimbra One and the Nimbra 600 series of
multiservice switches both from transport and management point of view. All features including signaled end-
to-end provisioning and restoration are supported in a mixed network with different Nimbra products.
With the Element Manager that is part of the Nimbra 300 series product, all aspects of the switch are easily
managed and controlled. The Element Manager has any easy-to-use Web-GUI and can also be managed
through the command line. Additionally, Nimbra 300 series supports managing by any SNMP v3 compliant
Network Management System (for example Nimbra Vision). The Nimbra 300 series has a number of
configuration, fault and performance management functions that makes services easy to provision and
maintain.
The Nimbra One/300 series modular switch includes the following Base Units, Access (Service) and Trunk
and modules:

NID2655 Rev. B7
Unit/Module Short description
Nimbra One An 8-slot modular subrack, with redundant power feeding
A 2-slot modular subrack, with redundant power feeding

Nimbra 340 Base Unit
and fixed Gigabit Ethernet and ASI ports
Nimbra 340-HD Base Unit
and fixed Gigabit Ethernet and HD-SDI ports
and fixed Gigabit Ethernet and SONET/SDH trunk ports
Nimbra 360 Base Unit
and (optionally) ports for distribution of time (Time Transfer
functionality).
OC-48/STM-16 X-ADM Module 2-port OC-48c/STM-16c trunk interface with on-board
(a.k.a. 2 x OC-48/STM-16 Trunk Module) switch matrix for high capacity ring operation
2 x OC-12/STM-4 Trunk Module 2-port STM-4c/OC-12c trunk interface
4 x OC-3/STM-1 Trunk Module 4-port STM-1/OC-3c trunk interface
4 x DS3/E3 Trunk Module 4-port DS3/E3 trunk interface
1 Gbps Optical Trunk Module Cost effective trunk interface for dark/grey fiber
E1 and T1 Access Module Eight full duplex ports for framed/unframed E1 and T1
Fast Ethernet Access Module Eight ports 10/100 Ethernet auto sensing module
Gigabit Ethernet Access Module Modular optics (SFP) Gigabit Ethernet module
SDI Video Access Module 4 ports (2 RX + 2 TX) 270 Mbps SDI BT.601 video
ASI Transport Access Module 4 (2 RX +2 TX) ports DVB-ASI
8 x ASI Transport Access Module 8 ports DVB-ASI, each configurable as IN or OUT
8 x AES/EBU Access Module 8 AES/EBU ports, each configurable as IN or OUT

4 ports (SFP), Channelized STS-3c/STS-1 /
4 x OC-3/STM-1 Access Module
VC-4 interface for OC-3/STM-1 compatible services
Table 1.List of Nimbra One/300 series Units and Modules

The Nimbra One/300 series is built according to telecoms standards for reliable functionality both in studio or
central office environments. Example of carrier class features are:
• Support for multiple topologies. Ring, bus, p-t-p, meshed structures.
• Several protection schemes: Mesh (fast re-route) protection, linear 1+1
• Simple Management. Support for HTTP, SNMP, RMON and CLI
• Extensive performance monitoring
• Hot-swap in service replacement of plug-in units
• Redundant -48V power feeding
• Visual Alarms (LED and Web-GUI)

NID2655 Rev. B7
2 Nimbra One/300 series system structure
The figure below shows a simplified overview of the Nimbra system structure.
Value Added Services
Element Manager
Nimbra Visison
Nimbra OS (NimOS)
and basic Applications
HW platforms
Figure 2. The Nimbra System Structure

A Nimbra node minimally comprises a HW platform, NimOS and an Element Manager. This would be a pure
switching node. The Nimbra One/300 series also comprises basic Applications and optionally Value Added
Services. All systems can be managed via the Nimbra Vision network management system, or other SNMP
compatible NMS.
The current HW platforms are the Nimbra 300 series multi-service switches with its plug-in units, the similar
but larger 8-slot Nimbra One and the Nimbra 600 series of core/edge switches. NimOS, Net Insight’s optical
control plane, comprises a set of functions for establishment and control of Services. These include
signaling, routing, topology discovery, resource management and synchronization establishment. Also
Service management such as re-establishment of circuits in case of failure, and general configuration, fault
and performance management is part of NimOS.
Basic Applications includes support to run the basic Services, i.e. currently ETS, SDI, HD-SDI, ASI,
Sonet/SDH, PDH and AES/EBU (these services will be explained in detail later).
The Element Manager can handle all aspects of the node. Its main interface is the Web GUI, by which it is
simple to configure the node and maintain it with respect to faults and performance. For more detailed
control the resource editing CLI can be used. The latter can also be used for scripting the configuration of
the node.
The HW platform, NimOS and the Element Manager are all part of a sales package; i.e. NimOS, Basic
Applications and the Element Manager are bundled with the chosen HW platform1. In this system model
there are two optional parts, the Value Added Services and the Nimbra Vision NMS.
Value Added Services are optional functionality that enhances the use of the system with respect to the
Basic Applications. Typical Value Added Services are ETS/ASI/SDI Multicast services, which provides
guaranteed QoS point-to-multipoint distribution services. This service enables typically Video distribution
service with high QoS and resilience, saving bandwidth and equipment costs for the operator.
The Nimbra Vision Network Management System is a NMS that is tailored for the Nimbra system. It provides
topology maps, network service and customer management, fault and performance monitoring. It is thus
very well suited for the Nimbra multi-service network. But an operator who already has an own NMS can
integrate Nimbra products into its service domain since the standardized SNMP v3 protocol is used for
network management.
A further exploration of the Nimbra system is given by the companion document "System Description -
Nimbra Platform" that explains in more detail system functionality (see references in chapter 8).
1
To be precise, the mentioned SW is bundled together, as a "GX license" with the Nimbra One Control Module or the
Nimbra 300 series Base Unit.

NID2655 Rev. B7
2.1 Nimbra One/300 series architecture
The Nimbra 300 series is based on the following hardware components:
• The Base Unit, containing
• Switch (Internal Switch Module)
• Control (Internal Node controller)2
• Mechanics (subrack including duplicated fans and power supply with optional redundancy)
• Built-in access interfaces
• Interface plug-in units – Trunk and Access modules
2.2 Nimbra One Base Unit
Figure 3. Nimbra One Base Unit

The Nimbra One Base Unit is an 11.4 RU high subrack with a depth of 240 mm..
2.2.1 Mechanics
The mechanics is based on the 19-inch standard, according to IEC 60297.
The unit consists of a chassis, a backplane with eight slots + two slots for DC voltage filter units and a fan
pack.
2
Only Nimbra 300 series, separate plug-in module on Nimbra One

NID2655 Rev. B7
The chassis has dimensions 505x445x270 mm (HxWxD). All handling is from the front. This means that it is
possible to mount two Nimbra Ones back-to-back in a 600 mm deep ETSI rack, or against a wall, and thus
conserve floor space.
The backplane also contains the Internal Switch Module function.
A fan package including three temperature-controlled fans with inherent redundancy is mounted on top of
the base unit.
Two -48 VDC power inlets are positioned on the right side. Either inlet or both can power the unit. Inlets are
monitored and an alarm is issued if power disappears on one inlet. For 115/220 VAC feeding optional AC/DC
converter systems are available.
2.3 Nimbra 300 series Base Unit
Figure 4. Nimbra 340. (Nimbra 340-HD has the same appearance, but HD-SDI
instead of ASI on the fixed access ports)
Figure 5. Nimbra 360. Note the 4 SFP ports at the right side, comprising trunk
interface functionality

NID2655 Rev. B7
The Nimbra 300 series Base Unit is a 2RU high subrack with a depth of 240 mm, that can be fitted in
ordinary an ordinary 19 inch cabinet, or directly on a table or a shelf. Note that the depth makes it possible to
place two Nimbra 300 series back-to-back in a 600 mm ETSI cabinet. All access to the unit is from the front.
2.3.1 Mechanics
The mechanics is based on the 19-inch standard, according to IEC 60297.
The unit consists of a chassis, a motherboard, and a passive backplane with two slots that connect the plug-
in units to the motherboard.
The chassis has dimensions 88x445x240 mm (HxWxD). All handling is from the front. This means that it is
possible to mount two Nimbra 300 series back-to-back in a 600 mm deep ETSI rack, or against a wall, and
thus conserve floor space.
The motherboard contains the main circuitry of the node. It can be divided into four major parts:
• The Internal Switch Module function
• The Node Controller function
• The Gigabit Ethernet Access function
• The ASI or HD-SDI Access or SONET/SDH trunk function
These parts will be described in detail in the following chapters.
A fan package including three temperature-controlled fans with inherent redundancy is mounted on the left
side of the base unit subrack, above the interface modules. Air is flowing from right to left.
Two -48 VDC power inlets are positioned on the left side. Either inlet or both can power the unit. Inlets are
monitored and an alarm is issued if power disappears on one inlet. For 115/220 VAC feeding optional AC/DC
converters are available, both cord attached and rack mounted.
2.4 SW Management
Software releases for the Nimbra system is delivered as so called GX system releases. A GX release
consists of a number of Application Packages (AP). If the revision of any of the Application Packages are
stepped, the GX release number will step. The AP is the lowest visible level of the the SW system. In
principle it is not necessary to care about APs, since the GX revision uniqely identifies the set APs from
which is defined and any change in these are thus reflected as a change in the GX revision.
An Application Packages is loaded on a hardware module (that support remote upgrade), for example the
base unit, control module or interface boards (most). An application package can either consist of SW only
(for example the NimOS image that runs on the Node Controller), mixed SW/FW (the Ethernet APs) or FW
only (most trunk/access boards).
Software is upgraded with a single command that inspects the current configuration and upgrades the
changed APs in order to align the system to the targeted GX level. It is possible to upgrade from the CLI,
Web GUI or from Nimbra Vision. Hardware units are then restarted as needed to complete the upgrade.

NID2655 Rev. B7
AP (NimOS)
Application
Package (SW/FW) SW/FW
AP (NimOS BL)
Interface Board Node Controller

HW
Nimbra One/300 series Base Unit
Figure 1. Software structure in the Nimbra One/300 series

The alignment state of the installed software can be checked in the Web GUI (from GX4.4) making it easy to
check that no Application Packages deviates from the GX baseline.

NID2655 Rev. B7
2.5 Internal switch module
The Internal Switch Module (ISM) resides in the backplane of the Nimbra One and on the mother-board of
the Nimbra 300 series
The primary function of the Internal Switch Module is to transport data and control signals between all
connected modules, i.e. between the Base Unit and the Trunk/Access modules.
The Internal Switch Module has a ring-bus topology with following characteristics:
 Switching capacity. 5 Gbps for bi-directional only traffic. For uni-directional only traffic the switching
capacity is 2.5-12.5 (Nimbra 300) and 2.5-20 Gbps (Nimbra One). The difference is due to the fact that
ISM of the Nimbra One has 8 ports while the Nimbra 300 series ISM has 5 ports.
 Total number of switch ports, Nimbra One. Eight. Of these one is a reserved for the Control Module
and the other for trunk/access boards.
 Total number of switch ports, Nimbra 300 series. Five. Of these three are mapped to the node
controller function, the fixed Gigabit Ethernet port and fixed ASI ports, respectively. Two ports are
connected to the slots for external trunk/access boards.
The ISM performs Space switching while Time slot switching is performed by the trunk interfaces. The delay
in the ISM is usually negligible but can theoretically be 125 s. However the varying delay in the ISM is
compensated by a corresponding “opposite” delay in the time switching trunk modules, that makes the total
delay constant.
2.5.1 Internal Switch Module Overview, Nimbra One

The backplane has eight interfaces for Control, Trunk and Access modules. Every other backplane interface
is connected to the lower side of the ring and every other to the upper side of the ring. Each has a unique
position address describing its position in the ring bus. In configuring Nimbra One the slots are arranged
from 1 to 8 from left to right.
2.5.1.1 Backplane Structure

The structure of the backplane ring bus with modules connected to the upper and the lower side of the ring
means that two different boards and front-panels are used. One for the modules connected to the lower side
of the ring and one for the modules connected to the upper. The two types of modules are called type A and
type B. Type A connects to the upper side of the backplane and B to the lower side.
Some traffic boards are implemented as symmetric boards that will fit in both A and B positions. These
boards are termed “X” boards. Slot A1 is dedicated for the Control Module (or "Node Controller", NC).

NID2655 Rev. B7
A1 B2 A3 B4 A5 B6 A7 B8
(NC)
Figure 1. Data flow between plug-in units on the backplane. Each arrow represents
a 2.5 Gbps flow of data.
The backplane (ISM) is a pipelined bus connected in a circle. The slots on the ring bus fills up data or drains
off data circulating in the ring bus. All data coming in to the slot is clocked stepwise through the internal pipe
until it reaches its destination slot. For bi-directional traffic only the capacity is 5 Gbps3. For uni-directional
traffic the switch capacity reaches from 17.5 Gbps (neighbor-neighbor traffic, 7 slots), down to 2.5 Gbps .
For dimensional purposes, it is suggested to use the typical value of 5 Gbps.4
2.5.2 Internal Switch Module Overview, Nimbra 300 series

The switch backplane, the Internal Switch Module (ISM), is implemented using a ring-bus architecture.
The module has five interfaces (slots) for node controller, internal Gigabit Ethernet and ASI ports and for the
two external plug-in unit bays. Each has a unique position address describing its position in the ring bus (see
2.5.2).
The ISM performs Space switching while Time slot switching is performed by the DTM trunk interfaces. Thus
delay in the ISM is negligible (order of s) in comparison with the time switching trunk modules. Under high
ring-bus load, data is stored in FIFOs and is emitted to the ring-bus when resources are available. Note that
the total delay through the node is constant, independent of the load. Data that is temporarily store waiting
for ring-bus access will spend correspondingly less time in the transmit FIFOs at the egress.
3
Capacity specifications can be confusing. For bi-directional only traffic the following "equation" specifies the switching
capacity of the Nimbra 300 series: (in-traffic) = (out-traffic) = 5 Gbps. The sum ranges over both access and trunk
interfaces.
4
The ring bus can alternatively be considered as a unidirectional DTM ring with a "frame-size" of 5000 slots per 125ms. Out
of these 5000 slots 4800 is used for "payload" and 200 slots for internal communication. "Payload" here includes user plane
traffic, DTM inter-node signalling and in-band management traffic. Signalling consumes 1 slot per trunk link (in each
direction) and in-band management may consume between 0 and several slots on each link depending on the in-band
management network topology.
So to be more exact the available capacity for "payload" is 4800 x 0.512 = 2457.6 Mbps, for each segment on the ring.
Thus, for bi-directional only "payload" traffic, the maximum switching capacity is 4915.2 Mbps. For the ring bus as a whole,
the corresponding switching capacity is 5000 x 0.512 x 2 = 5.12 Gbps.

NID2655 Rev. B7
Node
Controller
External Built-in
Slot #2 A/H/T ports
(lower)
Built-in External Slot

GbE port #1 (upper)
Figure 2. Data flow between Internal Switch Module ports. Each arrow represents a
data flow capacity of 2.5 Gbps. A/H/T represents ASI (Nimbra 340), HD-SDI
(Nimbra 340-HD) and Trunk (Nimbra 360)
The passive backplane connects the two external slots to the ring-bus. The slots on the ring-bus fill up data
or drain off data circulating in the ring bus. All data coming in to the slot is clocked stepwise through the
internal pipeline until it reaches its destination slot. Each ring-bus segment has a capacity of 2.5 Gbps.
Having five segments, the aggregated switching capacity of the ring-bus is thus 12.5 Gbps. This is the
capacity for neighbor-neighbor traffic, where each ring-bus port would destine all its traffic to its nearest
downstream neighbor. However, this is a rather unrealistic case. Instead, consider bi-directional traffic only.
Then the capacity is exactly 5 Gbps. For dimensional purposes, it is suggested to use the typical value of
maximum 5 Gbps for offered load.
The Element Manager representation of the ports are according to the table below:
Element Manager
Physical port/modules
numbering
0 Built-in Control Module
1 Plug-in unit slot #1 (upper)
2 Plug-in unit slot #2 (lower)
3 Built-in ASI ports (340) / Built-in HD-SDI ports (340-HD) / Built-in Trunk
ports (360)
4 Built-in Gigabit Ethernet port
Table 1.Mapping between slot position indicator in the Element Manager and the
physical ports/modules on the Nimbra 300 series
2.5.3 Channel capacities

Within a Nimbra One/300 switch each channel is assigned a unique Local Channel Identifier (LCI) that
identifies the channel within the switch. Before the GX4.1.3 release the partitioning of LCI values was such
that multicast channels had LCIs ranging from 0 – 127 and unicast channel had higher LCI values. This sat
a limit of the number of multicast channels to 128. From the GX4.1.3 release this scheme has altered such
that now unicast channels allocates LCIs from 2047 and downwards while multicast channels allocates from
0 and upwards. This implies an absolute limit of 2048 channels within a Nimbra One/300 and this number
refers to the sum of unicast and multicast channels.
Note however that the practical limit of channels may be lower since each channel consumes resources
(processing as well as memory) and to many channel in a Nimbra One/300 may degrade performance, in

NID2655 Rev. B7
for example a fiber cut scenario, to unacceptable levels. Since the performance may depend on a number of
factors, only coarse recommendations can be given.
The following numbers are recommended max values:
• ETS unicast: 100 (bi-directional) ETS channels in one Nimbra One/300
• ASI/SDI/STS-3c/VC-4/STS-1/E1/T1/AES/EBU unicast:
Limited by number of external ports in a Nimbra One.
• ETS/ASI/SDI/STS-3c/VC-4/STS-1/E1/T1/AES/EBU multicast:
X originating multicast tunnels to Y destinations, where X and Y are given by:
X < 100
X*Y < 1000
Higher channel densities are possible but performance will degrade. For higher capacity switching of DTM
channels, a switch in the Nimbra 600 series should be considered.
2.5.4 Switch transit delay

The transit delay through a Nimbra One/300 switch is constant, but the absolute value depends on a number
of factors.
1. Switch configuration (i.e. what trunk interfaces that are used)
2. Relative phase between incoming and outgoing DTM frame
3. Initialization effects
4. Time slot switching
The delay will be assessed for each trunk module but a short explanation is given below. 79 gives an
“empirical” table of expected delays that can be used to asess the total delay in a Nimbra One/300 network.
2.5.4.1 Switch configuration

The original switching architecture in Nimbra One/300 is a Time-Space (TS) switch architecture. The ISM
ring bus itself is a pure Space switch, delivering DTM data slots to a chosen PIU slot position in the switch.
The time switching stage is handled on the trunk modules, in the transmit path. This means that a when a
data slot arrives on the RX interface it is tagged with the physical destination address (the out physical PIU)
and when it arrives to the out board, a time slot switching is performed (if the out board is a trunk module).
The delay from in-port to the out board is in general negligible as compared to the time spent in the time
switching frame buffers on the out board. This means that the total transit time is mainly given by the amount
of frame buffering in the TX path of the trunk modules.
However, with the newer breed of trunk modules starting from the OC-48/STM-16 X-ADM module (the 2 x
OC-48/STM-16 trunk module) an local switch was designed onto the board in order to by-pass traffic that
are destined via another trunk port on the same board. This in order to save the limited ring bus from
switching by-pass traffic. See chapter 3.5 for a detailed description of this kind of trunks.
In this context the on-board switch matrix adds transit delay to the ingress (RX) path. For by-pass traffic
however, no extra delay is added. In the TX path the both types of trunks works identically.
2.5.4.2 Relative phase

The delay from this factor comes from the fact that incoming frames are phase aligned to the common
outgoing frame phase that is governed from the Node Synchronization function. The phase of the incoming
frame is absolutely arbitrary and the delay from this factor can thus be 0 – 125 s.
2.5.4.3 Initialization effects

When the frame stores are initialized it is strived to have as small frame delay as possible. However, there
are corner cases where the initialization could add one frame buffer to the delay. Thus the delay is specified
in terms of max and typical delays, where the typical delay excludes these corner cases.

NID2655 Rev. B7
2.5.4.4 Time slot switching

The transit delay of a certain slot is of course dependent of the relative in and out position within the frame.
I.e. if a time slot arrives in the beginning of a frame and leaves the node in the end of a frame it will suffer
the longest possible time switching delay. However this is just time switching within a frame and will thus not
add per switch hop, since time slots can be switch back and forth within the frame at each switch. Its
contribution to the end-to-end delay is thus in the range (-125 – 125) s and is thus not considered in the
switch transit delay.
2.5.5 Network/Node Synchronization

On the Nimbra One the Control Module houses the Node Synchronization (NS) function. On the Nimbra 300
series it is housed in the Base Unit. The node may be synchronized from one of the following sources
• External Synchronization Input (front panel BNC (300) or SMB (One))
• From a trunk module
• From the internal/local oscillator
The NS function performs a selection among the available sync signals, as ordered by the DSYP (network
synchronization) protocol. If a selected sync signal fails, the NS function will enter hold-over mode and
output a sync signal that is very close to the network frequency (that the NS function has learned while it
was in locked mode) until DSYP has found a new sync signal. In general this holdover time is less than a
couple of seconds. There is no discontinuity in phase during these operations.
Normally a node is synchronized via one of its trunk interfaces. But one node in the network must be sync
master. The sync master is a node that is either synchronized from an external sync source or if no external
sync source is available, DSYP will promote the local oscillator of one (arbitrary) node as sync master.
The internal oscillator housed in the Nimbra One Base Unit is of Stratum 4 quality while it is of Stratum 3
quality in the 300 series.
The only configuration that has to be performed to have a running network synchronization is to decide a
priority for the external sync sources. I.e. a node with an external sync source attached shall have a priority
of this source assigned. Thus for a network it is suitable to have a central node as a primary reference and
another node attached to a second sync source as backup.
Depending on the application, the network can function without any external synchronization sources, i.e.
synchronized to a Nimbra One/300 series local oscillator. More information on the synchronization system is
given in the helper document Synchronization Overview (NID2568).
2.5.6 Time Transfer functionality (Nimbra 360)

The Nimbra 360 can optionally be equipped with firmware for special timing functionality, Time Transfer (TT),
to serve the needs of, for example, Digital Terrestrial Television (DTT) distribution networks. The TT
functionality provides distribution of absolute time to the nodes of a Nimbra 360 network, with near-GPS
accuracy.
The TT function in each node processes the TT information in order to achieve the absolute time. The TT
function is specified to have a time accuracy degradation of maximum ±1.5 s for 10 consecutive node
hops, given that external delay asymmetries are negligible.
The accuracy of this absolute time is dependent on the following factors:
• Delay asymmetry of the TT path (intrinsic and external)
• The accuracy of the processing function
• Jitter and wander of the line signal
The first part is the most important. The function assumes that the round-trip delay can be divided into two
equal one-way delays. There is no way to resolve asymmetric delays from a round-trip delay measurement.
The round-trip delay can be divided into an intrinsic part and an external part. The intrinsic delays, i.e.
differences in egress and ingress transit times for different trunk interfaces, are handled by the system. The

NID2655 Rev. B7
external part is the transmission delay between two nodes. For example, a 10-meter fiber length difference
between nodes will contribute with a 25 ns error.
If a delay asymmetry is known (by for example a calibration procedure), it can be fed into the processing, via
the management system, as a link parameter to compensate out. If both ends of a link are connected to a
GPS source the link in-between can be automatically calibrated for asymmetry. The calibrated parameters
are stored in persistent memory.
The error contribution from processing can be considered negligible. The same is true for the line jitter
contribution since jitter is averaged out by the filter mechanisms. Wander will manifest itself as a slowly
changing delay and will be canceled by the TT function (active wander reduction is a virtue of the TT
method).
The TT functionality requires support from the trunk interfaces. The built-in trunk-ports of the Nimbra 360
support TT functionality, as well as all the trunk interfaces of the new Nimbra 600 series.
2.5.7 Hot-swap
For maintenance reasons, the Nimbra One/300 series backplane supports insertion and extraction of trunk
and access modules during operation. This is called hot-swap. It is implemented for all Trunk and Access
modules. On each module a push button switch provide the Hot-swap function by generating a request for
service signal to the backplane. The Node controller then informs that the requested board can be taken out
of service by lighting the Remove LED.
2.5.8 Power Supply

The Nimbra One/300 series has two independent inlets of -48 VDC power. The incoming -48 V power is
distributed out to all the modules. Each plug-in unit has its own DC-DC converter for down-conversion of the
voltage. The design allows load sharing so that both supplies are loaded if both are present.
For 115/230 VAC power supply, optional AC/DC converters can be ordered. Either cord attached or rack-
mounted converters are available. Used in pairs these gives redundant AC power supply and are easy to
exchange if needed.
2.5.8.1 Power consumption

Nimbra One is rated to a maximum of 300W. Typical power consumption is between 100-150W.
The Nimbra 300 series consumes maximum 80W fully equipped. Typical consumption is around 50-60 W.
Power consumption of an unequipped Nimbra 300 series Base Unit is around 25-30 W.
2.5.9 Node Controller function

On the Nimbra One the Node Controller function resides on the Control Module plug-in unit. On the 300
series it is integrated on the motherboard of the base unit. The Node controller controls most aspects of the
Nimbra 300 series. All operating software, such as protocol processing and node management is loaded on
the Node controller, which also controls the internal communication with each trunk and access module.
Note however, that the node controller is not involved in the data transfer phase, which is handled entirely by
the traffic modules.
The Node Controller function can store two system images, i.e. two versions of the system. This is mainly
used when upgrading remotely to a newer version of NimOS.
2.5.9.1 Real Time Clock

The Node controller contains a battery-backed real-time clock for preserving the date and time while the
board is not powered.

NID2655 Rev. B7
2.5.9.2 Temperature monitoring

The inherent sensors on the module handle the temperature monitoring. It will trig an alarm when the
temperature is too high or to low. There are four alarm levels at estimated ambient temperatures of -5 (23), 5
(41), 40 (104) and 55 (131) degrees Celsius (Fahrenheit).
2.5.9.3 Reset
The Reset button on the front performs a SW reset of the node. It is pressed with a pointed tool or pen.
2.5.9.4 Status LED

The Status LED will give a steady green light from power-up until the system is ready, then it is turned off.
2.5.9.5 External Sync ports

The External Sync ports are used for
1. To provide a Reference Clock signal to the node (and the network). This signal must conform to the
format as specified in ITU-T G.703.10, a square or sine wave shaped 2048/1544 kHz clock. A
proprietary 8 kHz mode is also supported from GX4.4.
2. To provide a Reference Clock signal from the network to external equipment. It presents a timing signal
that is always locked to the currently selected Reference Clock of the network. Frequency is 2048 kHz.
From GX4.4 it is possible to configure the output frequencies to 2048/1544/8 kHz
When using the input port a priority should be assigned to the Reference Clock from the Element Manager.
Only one Reference Clock is active within the whole network at each time and the one is chosen in priority
order by DSYP. Thus it is only necessary to equip a few nodes in the network with Reference Clocks, one
being the Primary Reference Clock and the other Secondary, Third etc. Reference clocks as decided by their
relative priorities.
2.5.9.6 Time Transfer ports (Nimbra 360)

From GX4.4 the Nimbra 360 Time/Sync Interface (TSI) ports has the following functionality:
TSI 1:
Normal sync mode:
IN (Sync BNC): 2048/1544/8 kHz autosense
OUT (PPS BNC): 2048/1544/8 kHz configurable; default 2048 kHz
Time Transfer mode:
TSI 1 port pair configurable as IN/OUT
IN: PPS (PPS BNC) + 10 MHz (Sync BNC) fixed
OUT: PPS (PPS BNC) + 10 MHz (Sync BNC) fixed
TSI 2:
Normal sync mode:
IN: (Sync BNC): N/A (not used)
OUT: (PPS BNC): 2048/1544/8 kHz N/A (slaved on TSI1 normal sync mode OUT
configuration)
Time Transfer mode:

TSI 2 port pair always OUT
IN: N/A (not used)
OUT: PPS (PPS BNC) + 10 MHz (Sync BNC) fixed

NID2655 Rev. B7
2.5.9.7 Alarm I/O ports (Nimbra One Control Module, Nimbra 340/340-HD)
A nine-pin female D-SUB connector. From GX4.4 Alarm I/O funtionality is supported. There are 6 inputs and
1 output.
Inputs:
The input alarms are configurable with respect to Alarm State Type/Severity/Text. Input trigger can either be
change of a TTL voltage (High > 2.0V, Low < 0.8V) or by just closing the input contact to ground (Input goes
from internal High → Low).
Output:
The output typically closes a circuit (i.e. for relay control) when a configurable node alarm condition occurs.
2.5.9.8 Management ports

The Nimbra One/300 series is equipped with Local Management ports for Serial and Ethernet connections.
It may also be managed remotely via the in-band management function over the network.
The following management interfaces are supported:
• Command Line Interface
• Web Interface
• IP on SLIP on serial line
• IP on DLE on DTM link
• HTTP, Server with basic authentication
• FTP, Server and Client
• NTP, Server and Client
• SNMP Version 2c, 3, MIB II
• Telnet, Server and Client
See chapter 4.2 for more information on the in-band management network.
LED Activity Description

Ethernet Green
Have link
Control Left Flashing
Activity on link
Port green
Orange 100 Mbps link
Right
Off 10 Mbps link
Green Unit is booting
Status
Off Ready
Table 1.LEDs related to the Node controller function
2.5.9.9 Alarm handling

The Node controller receives and handles alarm and performance data from the traffic boards and from the
equipment. The following alarm types exists:
• Communications
• Environment
• Equipment
• Quality of Service

NID2655 Rev. B7
Alarms are described in more detail under respective interface board. A survey over alarm types and causes
is given in the helper document Alarm Survey Nimbra One/340 (NID2004).
2.5.9.10 Performance Monitoring

The Performance management function is based on ITU-T G.826 and measures the following performance
parameters for both trunk interfaces and service end-points5,6:
• Errored seconds (ES)
• Severely errored second (SES)
• Background block errors (BBE) (ITS connections only)
• Unavailable seconds (UAS)
• Slip Seconds (SS) (trunk interfaces only)
Performance data is collected in 15 minutes and 24 hour bins. Up to 96 15 min bins and 30 24 hour bins can
be stored for a trunk interface or service. The amount of stored performance data is limited by the amount of
free on-board storage.
2.5.10 Built-in traffic interfaces (Nimbra 300 series)
2.5.10.1 Nimbra 340

The Nimbra 340 features two types of built-in access interfaces
• 1 x Gigabit Ethernet, SFP-LC connector
• 2 in + 2 out ASI, 2 in + 2 out + 2 monitor BNC connectors
The functionality and characteristics of these built-in ports are the same as for their corresponding plug-in
units, the
• Gigabit Ethernet Access Module (see 3.8)
• ASI Transport Access Module (see 3.11)
2.5.10.2 Nimbra 340-HD

The Nimbra 340-HD features two types of built-in access interfaces
• 1 in + 1 out HD-SDI, 2 in + 2 out + 2 monitor BNC connectors
The functionality of the HD-SDI ports are described in chapter 3.13.
2.5.10.3 Nimbra 360

The Nimbra 360 features a built-in GbE port:
and four (4) SFP ports for SONET/SDH trunk functionality:
• 4 x OC-3/STM-1 Trunk
The Nimbra 360 Base Unit can optionally be upgraded (FW upgrade) to run
• 4 x OC-12/STM-4 Trunk
• 2 x OC-48/STM-16 Trunk (2 SFP ports becomes unused with this option)
on the SFP ports.
5
The PM function is not yet implemented for the E1/T1 Access Module
6
PM on the Ethernet Access Modules are not based on ITU-T G.826 methods, but rather on RMON performance metrics

NID2655 Rev. B7
The functionality and characteristics of these built-in ports are the same as for their corresponding plug-in
units, the
• Gigabit Ethernet Access Module (see 3.8)
• 4 x OC-3/STM-1 Trunk Module ( “S32” version, see 3.3)
• 2 x OC-12/STM-4 Trunk Module (see 3.4)
• OC-48/STM-16 X-ADM Module (see 3.5)
except for the fact that there are 4 ports on the OC-12/STM-4 trunk option on the Nimbra 360.

NID2655 Rev. B7
3 Trunk and Access Interfaces
The Trunk Modules performs the Time-switching part of the Nimbra One/300 series switching function and
provides the interconnect to other Nimbra system switches. Currently Nimbra One/300 series supports the
following Trunk Modules
Trunk Module Characteristics

1 Gbps Optical Trunk 1 Gbps interface for dark fiber or CWDM. 8B10B encoding. 1940 slots.
Module SM 1310 nm short-haul or 1550 nm long-haul optical interface
4 x OC-3/STM-1 Trunk Four 155.52 Mbps interfaces compatible with SONET OC-3 and SDH
Module STM-1. 288 slots. SFP optics for short/intermediate/long haul.
Two 622.08 Mbps interfaces compatible with SONET OC-12c and SDH
2 x OC-12/STM-4
STM-4c. 1152 slots. Built in three-way switch matrix. Replaceable SFP
Trunk Module
optics for intermediate/long haul.
Two 2488.32 Mbps interfaces compatible with SONET OC-48c and SDH
OC-48/STM-16 X-
STM-16c. 4608 slots. Built in three-way switch matrix. Replaceable SFP
ADM Module
optics.
4 x DS3/E3 Trunk Four 45 or 34 Mbps PDH compatible electrical interfaces. 84 or 65 slots
Module respectively.
Table 1.Trunk Modules supported by Nimbra 300 series

The Access Modules adapts specific service data for transport of the network. Presently the following
services are supported:
Access Module Characteristics

1 x GbE. VLAN based forwarding on ETS channels. Replaceable SFP optics
Gigabit Ethernet
for short/intermediate/long haul.
8 x 10/100 Ethernet. VLAN based forwarding on ETS channels. RJ-45
Fast Ethernet
connectors.
SDI Video 2 in + 2 out + 2 monitoring ports. BNC connectors.
ASI Transport 2 in + 2 out + 2 monitoring ports. BNC connectors.
8 x ASI Transport 8 in/out (configurable all in or all out) + 1 monitoring port. BNC connectors.
8 x AES/EBU 8 in/out (configurable all in or all out) + 1 monitoring port. BNC connectors.
4 x OC-3/STM-1 4 port, SFP optics for short/intermediate/long haul
PDH E1 8 x E1 G.703 compatible ports. RJ-48C ports 120 
PDH T1 8 x T1 G.703 compatible ports. RJ-48C ports 100 
Table 2.Access Modules supported by Nimbra 300 series

While the Trunk/Access modules for the Nimbra One and 300 series respectively have similar functionality
they have different physical form factor and can not be exchanged between the two platforms.
Some of the (older) plug-in units does not support remote firmware upgrade. If new functionality is
introduced in these plug-in units it is done via a hardware upgrade procedure. In these cases, Net Insight will
offer an HW upgrade service to customers that request the new functionality.

NID2655 Rev. B7
3.1 Trunk/Access Module Common Functionality
All Trunk and Access Modules features a number of LEDs and a press button that will be described here.
LED/Button Description
Steady green light: Power on
Power
Off: Power off
Steady green light: Module can safely be removed
Remove Blinking green light: Module is out of order
Off: Module not ready to be removed
When pressed and the corresponding LED is lit, the module is prepared
Request Removal
for removal
Table 3.Common Trunk/Access Module functionality

NID2655 Rev. B7
3.2 1 Gbps Optical Trunk Module
The 1 Gbps Optical Trunk Module is adapted for running DTM over Gigabit Ethernet optics. The 1 Gbps
Optical link speed is 1 Gbps (1.25 Gbaud). The number of slots in the frame is 1940. Note that the interface
is not compatible with Gigabit Ethernet, it merely uses the same type of optical transceivers and low level
encoding (8B/10B).
3.2.1 Optical Interface

The 1 Gbps Optical Trunk Module has a single 1.25 Gbaud duplex fiber optic interface (LC connector) with a
single mode optical transceiver. There are a short haul and a long haul version of the module. The short haul
device is powered from 3.3V and uses 1310nm transmit wavelength. The long haul version is powered from
5V and uses a longer wavelength (1550nm) and has a higher optical launch power.
3.2.2 Switch Delay

The switch delay through the 1 Gbps Optical Trunk Module is mainly given by the time switching buffer in the
TX path. See chapter 2.5.4 for a discussion of the transit delay within a Nimbra One/300 switch.
Path Max delay (s) Typical delay (s)

RX - ISM -TX 380 190
Table 4.Switching delay of the 1 Gbps Optical Trunk Module
3.2.3 Power
Power is applied to the 1 Gbps Optical Trunk Module via the backplane. Nominally, 48V DC is brought onto
the board and converted locally to +5V DC and 3.3V DC using DC-DC converters. Power consumption of
the 1 Gbps Optical Trunk Module will not exceed 12W.
3.2.4 LEDs
The 1 Gbps Optical Trunk Module has four front panel LEDs in a similar fashion as other Nimbra One/300
series trunk modules. The LED functions and colors are as shown in the following table.
LED no Activity Description

Green DTM frame locking acquired
DTM Rx
Off Loss of DTM frame
Green Transmitting
DTM TX
Off Idle
Green Board out of service – ready for extraction
Service
Off Board in service
Power Green 5V and 3.3V power sources up
Table 5.LEDs on 1 Gbps Optical Trunk Module front
3.2.5 Hot-swap
The 1 Gbps Optical Trunk Module has a service switch on the front panel, "Removal request", which allows
Hot-swap according to section 2.5.7.

NID2655 Rev. B7
3.2.6 Remote upgrade

The module supports remote upgrade of firmware.

NID2655 Rev. B7
3.3 4 x OC3/STM1 Trunk Module
The 4 x OC-3/STM-1 Trunk module is available in two versions, the original version and a newer version
that is released in Q1 2008.
XS31 Nimbra One Original version, prepared for Forward

3S31 Nimbra 300 Error Correction (optional)
NPS0009-
XS32 Nimbra One New version, prepared for Time
3S32 Nimbra 300 Transfer (optional)
Table 6.The two versions of the 4 x OC-3/STM-1 Trunk Module

When differing, the original version will be denoted S31 and the new version S32 in this document, from the
last 3 letters of the product number.
The 4 x OC-3/STM-1 Trunk module offers four 155.52 Sonet/SDH compatible trunk interfaces for the Nimbra
One/300 family of products. It enables multi-service operation with guaranteed QoS and high utilization over
standard OC-3/STM-1 connections or leased lines. The interface maps 288 slots into a STS-3c SPE/VC-4.
Out of this capacity one slot is used for internal signaling and 0 - X slots for management purposes, where X
depends on the configuration of the in-band management network. This means that up to 146.944 Mbps
(287 slots) can be used for user payload, resulting in a link overhead of less than 2%.
The S31 version of the module is prepared for Forward Error Correction functionality for transport over un-
reliable media. This functionality is provided as an optional firmware module. The S32 version will support
the optional Time Transfer functionality (chapter 2.5.6). It is planned to also support Forward Error
Correction on the S32 version. When implemented the S31 version will be phased out.
3.3.1 External Interface

The 4 x OC-3/STM-1 Trunk Module has four (4) Small Form-factor Pluggable (SFP) ports that can be fitted
with opto-modules for different distances and physical media. Short Range (SR1), Intermediate Range (IR1)
and Long Range (LR1/LR2) modules are available. From the element manager it is possible to extract
inventory information on the currently inserted SFP module, such as type and version.
3.3.2 Delay Performance

The two versions differ in the delay performance. This is because the newer 3S2 version have an on-board
switch matrix of the type that is described in chapter 3.5 about the 2 x OC-48/STM-16 trunk module.
The delay of the original 3S1 version (that doesn't have the on-board switch matrix) through the transmit
path is mainly attributed to the time switching memory which typically stores 1-2 frames and thus gives
about 125-250s delay of the signal. The typical receive path delay through the 4 x OC-3/STM-1 Trunk
Module is a few microseconds.
See chapter 2.5.4 for a discussion of the transit delay within a Nimbra One/300 switch.
Thus the following table gives the delay times.
Ver. Path Max delay ( s ) Typical delay ( s )

S31 RX – ISM – TX 390 190
S32 RX – ISM – TX 630 315
S32 RX – TX (by-
390 190
pass)
Table 7.Switching delay of the two 4 x OC-3/STM-1 Trunk Modules

NID2655 Rev. B7
3.3.3 Power
Power is applied to the 4 x OC-3/STM-1 Trunk Module via the backplane as described in 2.5.8. The power
consumption does not exceed 12W.
3.3.4 LED
The 4 x OC-3/STM-1 Trunk Module has two front panel LEDs for power and service, and four LEDs per port
showing path transmit status, path receive status, section/line transmit status and section/line receive status.
The LED functions and colors are as shown in 3.3.4.

Green DTM in frame locked state
Path Rx
Green Always on
Path TX
Off N/A
Red Flashing LOS; SFP absent
Red MS/L-AIS; LOF; DEG
Section/Line Rx
Green None of above
Off N/A
Red Flashing Wrong SFP type; SFP laser failure
Section/Line TX Green None of above
Off N/A
Service
Green Power sources up
Power
Off No power on board
Table 8.LEDs on 4 x OC-3/STM-1 Trunk Module front
3.3.5 Hot-swap
The 4 x OC-3/STM-1 Trunk Module has a service switch on the front panel, "Removal request", which allows
3.3.6 Optional FEC155 Firmware Module

For use over unreliable media, such as microwave links, the “3S1” version of the 4 x OC-3/STM-1 Trunk
Module can be equipped with an optional firmware that provides Forward Error Correction (FEC), based on
a (255,237,t=9) Reed-Solomon code. It is possible to correct up to 648 errored bits in an error burst.
With this firmware 261 slots are mapped into the STS-3c/VC-4 payload, instead of 288 slots. The firmware
allows 2 FEC enabled ports on the board, the other two ports becomes disabled, i.e. unusable.

The modules supports remote upgrade of firmware.

NID2655 Rev. B7
3.4 2 x OC12/STM4 Trunk Module
The 2 x OC-12/STM-4 Trunk Module provides two 622 Mbps SONET/SDH trunk interfaces for the Nimbra
One/300 series.
The board is equipped with a non-blocking switch matrix that off-loads the Nimbra back-lane. The principle
of the on-board switch matrix is the same as for the OC-48/STM-16 X-ADM Module, see chapter 3.5. The
interface maps 1152 slots into a STS-12c SPE/VC-4-4c. Out of this capacity one slot is used for internal signaling
and 0 - X slots for management purposes, where X depends on the configuration of the in-band management
network. This means that up to 589.312 Mbps (1151 slots) can be used for user payload on each interface,
resulting in a link overhead of less than 2%.

The switch delay through the 2 x OC-12/STM-4 Trunk Module is mainly given by the time switching matrix
buffers in the on-board switch matrix. See chapter 2.5.4 for a discussion of the transit delay within a Nimbra
One/300 switch.

RX – ISM – TX 630 315
RX – TX (by-pass) 390 190
Table 9.Switching delay of the 2 x OC-12/STM-4 Trunk Module

The 2 x OC-12/STM-4 Trunk Module has two Small Form-factor Pluggable (SFP) ports that can be fitted with
opto-modules for different distances and physical media. Short Range (SR1), Intermediate Range (IR1),
Long Range (LR1/LR2) plug-ins are available. From the element manager it is possible to extract inventory
information on the currently inserted SFP module, such as type and version.
3.4.3 Power
Power is applied to the 2 x OC-12/STM-4 Trunk Module via the backplane as described in 2.5.8. The power

NID2655 Rev. B7
3.4.4 LED
The 2 x OC-12/STM-4 trunk module has two front panel LEDs for power and service, and four LEDs per port

Green DTM frame locking; at least one DTM trunk enabled
Path Rx
Off Loss of DTM frame; no DTM trunk enabled
Green Transmitting; at least one DTM trunk enabled
Path TX
Off Idle; no DTM trunk enabled
Off Port disabled or SFP general failure
Red Flashing LOS, LOF, MS/L-AIS or DEG alarms
Section/Line Rx
Green Flashing N/A
Green Receive port operating
Red Flashing SFP TX laser failure or sending MS-AIS
Section/Line TX
Green Flashing N/A
Green Transmit port operating
Service
Power
Table 10.LEDs on 2 x OC-12/STM-4 Trunk Module front
3.4.5 Hot-swap
The 2 x OC-12/STM-4 Trunk Module has a service switch on the front panel, "Removal request", which
allows Hot-swap according to section 2.5.7.


NID2655 Rev. B7
3.5 OC48/STM16 XADM Module
The OC-48/STM-16 X-ADM Module (a.k.a the 2 x OC-48/STM-16 Trunk Module) introduces a stepwise
increase in performance for the Nimbra One/300 series. With 2 (two) OC-48/STM-16 ports on one module it
increases the capacity 8-fold from the OC-12/STM-4 module and 5-fold from the 1 Gbps Optical module. In
order for the Nimbra 300 series backplane to handle the increased load an on-board switching matrix on the
trunk module has been introduced. This means that the backplane is off-loaded from the burden of by-
passing traffic which will pass directly between the two ports of the module. Only traffic destined for this
particular node is dropped to the backplane. In this way it is possible to build high capacity ring network
whose capacity can be increased in steps of 2.5 Gbps by inserting more OC-48/STM-16 X-ADM Modules.
c c
a
SFP SFP
Back-plane
interface
b
Figure 1. Principal diagram of the OC-48/STM-16 X-ADM Module, showing the two
SFP ports and the on-board switching matrix. The letters represent
a) The by-pass traffic flow
b) Traffic dropped to the node
c) Multicast traffic emitted on both ports
The board features 2 SFP (Small Form-factor Pluggable) ports that can be fitted with opto-modules for
different distances and physical media. From the element manager it is possible to extract information on the
currently inserted module, such as type and version and, if supported by the module, characteristic
information such as wavelength etc.
The on-board switch matrix can switch traffic between the two ports and the backplane in any combination,
where some of the combinations are illustrated in 3.5. Typically the bulk traffic will be switched between the
two external ports and a smaller amount will be dropped to the backplane. The backplane interface has a
capacity of 2.5 Gbps (4752 slots) bi-directional. Although a ring configuration is very natural for this trunk
module, both ports can be used completely independent of each other in any topology such as ring, point-to-
point and mesh.
Each framer maps 4608 DTM slots into each STS-48c SPE/VC-4-16c according to the ETSI ES 201 803-4
specification. Each slot carry 512 kbps payload which results in a total payload of 2359.296 Mbps. Out of
this capacity one slot is always used for internal signaling and 0 to x slots for management purposes, where
x depends on the configuration of the in-band management network. This means that up to 2358.784 Mbps
can be used for user payload, resulting in an overhead less than 2%.

The switch delay through the 2 x OC-48/STM-16 Trunk Module is mainly given by the time switching matrix
buffers in the on-board switch matrix. See chapter 2.5.4 for a discussion of the transit delay within a Nimbra
One/300 switch.

NID2655 Rev. B7

RX – ISM – TX 630 315
RX – TX (by-pass) 390 190
Table 1.Switching delay of the 2 x OC-48/STM-16 Trunk

The OC-48/STM-16 Trunk Module has two Small Form-factor Pluggable (SFP) ports that can be fitted with
opto-modules for different distances and physical media. Short Range (SR1), Intermediate Range (IR1),
Long Range (LR1/LR2) and CWDM plug-ins are available. From the element manager it is possible to
extract inventory information on the currently inserted SFP module, such as type and version.
3.5.3 Power
Power is applied to the OC-48/STM-16 X-ADM Module via the backplane as described in 2.5.8. Power
consumption of the module will not exceed 20W.
3.5.4 LED
The OC-48/STM-16 module has two front panel LEDs for power and service, and four LEDs per port

Green DTM frame locking; at least one DTM trunk enabled
Path Rx
Off Loss of DTM frame; no DTM trunk enabled
Green Transmitting; at least one DTM trunk enabled
Path TX
Off Idle; no DTM trunk enabled
Red Flashing LOS, LOF, MS/L-AIS or DEG alarms
Section/Line Rx
Green Flashing N/A
Green Receive port operating
Red Flashing SFP TX laser failure or sending MS-AIS
Section/Line TX
Green Flashing N/A
Green Transmit port operating
Service
Power
Table 2.Table 1. LEDs on OC-48/STM-16 X-ADM module front
3.5.5 Hot-swap
The OC-48/STM-16 Trunk Module has a service switch on the front panel, "Removal request", which allows

NID2655 Rev. B7


NID2655 Rev. B7
3.6 4 x DS3/E3 Trunk Module
The 4 X DS3/E3 Trunk module offers four 45 or 34 Mbps PDH compatible trunk interfaces for the Nimbra
One/300 family of products. It enables multi-service operation with guaranteed QoS and high utilization over
standard DS3/E3 connections or leased lines. The interface maps 84 or 65 slots respectively into a DS3 or
E3 frame. Out of this capacity typically one slot is used for internal signaling and 0 - X slots for management
purposes, where X depends on the configuration of the in-band management network. This means that up to
42.496 Mbps (DS3) and 32.768 Mbps (E3) can be used for user payload, resulting in an overhead of only
about 1.5%.
3.6.1 Electrical Interface

The 4 X DS3/E3 Trunk Module is equipped with four pairs of standard 75 ohm BNC connectors for the
DS3/E3 interfaces. The interface specifications comply with ANSI T1.102 (DS3) and ITU-T G.703 (E3), with
a minimum reach of 450 feet / 137 m.

The switch delay through the 4 x DS3/E3 Trunk Module is mainly given by the time switching buffer in the TX
path. See chapter 2.5.4 for a discussion of the transit delay within a Nimbra One/300 switch.

RX - ISM -TX 380 190
Table 3.Switching delay of the 4 x DS3/E3 Trunk Module
3.6.3 Power
Power is applied to the 4 X DS3/E3 Trunk Module via the backplane as described 2.5.8. The power
3.6.4 LED
The 4 X DS3/E3 Trunk module has got LEDs in a similar fashion as other Nimbra One trunk modules. The
LED functions and colors are as shown below.

Green DTM frame locking acquired
4 x DS3/E3 Rx
Green Transmitting
4 x DS3/E3 Tx
Off Idle
Service
Power
Table 4.LEDs on 4 X DS3/E3 Trunk Module front

NID2655 Rev. B7
3.6.5 Hot-swap
The 4 X DS3/E3 Trunk Module has a service switch on the front panel, "Removal request", which allows

3.6.7 Operational modes

The 4 x DS3/E3 Trunk Module can be run as either a 4 x DS3 or a 4 x E3 board. The operational mode must
be set at boot time.

NID2655 Rev. B7
3.7 4 x OC3/STM1 Access module
The OC-3/STM-1 Access Module provides the Nimbra 300 series switch with an STS-3c/STS-1 SPE
(SONET) or a VC-4 (SDH) interface for transport of any OC-3/STM-1 compatible service over DTM. The
module features 4 independent bi-directional ports. Each port is equipped with optional SFP’s modules,
available in four optional ranges.
Each OC-3/STM-1 port can transport either one STS-3c SPE/VC-4 or three STS-1 SPE. The board uses the
SONET mapping for STS-1/VC-3 where 1 x STS-1/VC-3 is mapped into an AU-3 and 3 x AU-3 is multiplexed
into an AU-4 which is mapped into an OC-3/STM-1. Thus the SDH mapping 3 x VC-3 to 3 x TUG-3 to AU-4
is not supported.
The board provides for up to 12 independent bi-directional channels (in the STS-1 case) that can be
connected to any other OC-3/STM-1 Access module in the network. Thus the network can act as a
"distributed cross-connect" for STS-3c/VC-4 / STS-1 connections.
4 x OC-3/STM-1
STS-3c/VC-4
STS-1
Figure 1. Example of STS-3c SPE/VC-4 and STS-1 SPE connection modes on the
OC-3/STM-1 Access Module .
Each port maps an STS-3c SPE/VC-4 into 296 DTM slots or three STS-1 SPE into 100 slots each.
At the egress an internal Stratum 3 quality oscillator clocks out the OC-3/STM-1 signal. Alternatively loop-
timing (i.e. the RX port times the TX port) is used to clock out the OC-3/STM-1 signal. Frequency differences
between the ingress signal and the egress signal is handled by pointer adjustments on the egress interface.
OC-3/STM-1 Access Characteristics:
•Four bi-directional interfaces
•SPF options
STM-1 I-1.1/OC-3 SR-1 (MM. 1310nm)
STM-1 S-1.1/OC-3 IR-1 (SM,1310nm)
STM-1 L-1.1/OC-3 LR-1 (SM, 1310nm)
STM-1 L-1.2/OC-3 LR-2 (SM,1550nm)

•Framing
OC-3 STS-3c, ANSI T1.105
OC-3 STM-1, ITU-T Rec G.707

•Mapping
SONET STS-3c SPE/STS-1 SPE
SDH VC-4
•Performance management based on ITU-T G.826

NID2655 Rev. B7
•Timing modes
Loop timing : Slaved to SDH/SONET network
Source timing: Slaved to on-board oscillator

•Multicast support of OC-3/STM-1 streams (using the OC-3/STM-1 MC optional SW)

The delay of the OC-3/STM-1 access module through transmit path is mainly attributed to the transmit buffer
delay which typically saves one frame and thus gives about 125s delay of the signal. The typical receive
path delay through the OC-3/STM-1 access module is a few microseconds.
3.7.2 Power
Power is applied to the OC-3/STM-1 Access module via the backplane as described in 2.5.8. Power
consumption of the module will not exceed 15W.
3.7.3 LED
The OC-3/STM-1 access module has LEDs for power, service, transmit and receive status, transmit and
receive mode.

Green AU-4 (VC-4)
Mode RX
Off 3xAU-3 (3xVC-3)
Green Operating
Flashing green DTM Loop-back
Status RX
Flashing red Fault
Off SFP transceiver removed or wrong type
Green AU-4
Mode TX
Off 3xAU-3
Green Operating
Flashing green Line loop-back
Status TX
Flashing red Fault
Off SFP transceiver removed or wrong type
Service
Green 5V and 3.3V power sources up
Power
Table 1.LEDs on OC-3/STM-1 Access module front
3.7.4 Hot-swap
The OC-3/STM-1 Access module has a service switch on the front panel, "Removal request", which allows

NID2655 Rev. B7
3.7.5 Loop-back
The module support line and system side loop-back per physical port.
3.7.6 Protection switching

Each channel can be protected in a 1+1 configuration for sub 50ms protection switching. To use 1+1
protection switching the working and protect paths should be set up using source routing (see 5.1 for a brief
description of source routing) in order to make sure that the paths are diverse.


NID2655 Rev. B7
3.8 Fast and Gigabit Ethernet Access Module
The Fast Ethernet Access Module and the Gigabit Ethernet Access Modules are plug-in units (PIU) to the
Nimbra One/300 series. The service provided by the boards is called Ethernet Transport Service (ETS).
ETS provides a transparent Ethernet channel over the DTM network while utilizing the good properties of the
DTM technology such as dedicated capacity and real-time characteristics. ETS maps one ore many
IEEE802.1Q VLAN tag(s) to an Ethernet channel. Alternatively untagged traffic can be mapped to a default
VLAN and thereafter to a channel.
A maximum of 246 Ethernet channels can be supported in one Nimbra 300 series node. Any of the 4096
IEEE 802.1Q VLAN tags can be used for tagging. There is however a limit that allows only for simultaneous
use of 1024 configured VLANs in a Nimbra 300 series node, and maximum 512 configured VLANs on an
ETS end-point. A VLAN need only be unique at the PIU. That is, the same VLAN can be used multiple times
in the network as long as they are unique at the end PIU. The same VLAN can therefore be used in two
separate plug-in units in the same node.
Each channel has configurable bandwidth in steps of 512 kbps. From an Ethernet point-of-view, an Ethernet
channel can be seen as a learning bridge between two Ethernet segments. ETS thus learns which
addresses that are on the adjacent side and refrains from forwarding them across the channel. ETS
forwards spanning tree protocol data although it does not run the spanning tree protocol itself.
The ETS service is described in greater detail in 5.2.
The boards also support 802.1P/diffserv priority for prioritization of traffic towards an Ethernet channel.
Fast Ethernet Access Module characteristics:
• Eight ports 10/100 Base-T Ethernet auto-sensing
• Supports Ethernet Transport Service (ETS™)
• Features Hot-swap functionality
Gigabit Ethernet Access Module characteristics:

• One SFP LC (interchangeable) fiber optic 1 Gbps Ethernet port7
• Supports Ethernet Transport Service (ETS™)
• Features Hot-swap functionality
3.8.1 Power
Power is applied to the Ethernet Access modules via the backplane as to any other module.
Power consumption of the Ethernet module is 25W nominal.
3.8.2 Interfaces
Fast Ethernet Access
The Fast Ethernet Access module has eight ports 100Base-T with RJ45 connectors.
Gigabit Ethernet Access
The Gigabit Ethernet Access has one Small Formfactor Pluggable LC type connector for different reach
modules. The reaches are (approximately and subject to fiber quality)
1000BaseSX: 500m (850nm wavelength)
1000BaseLX: 10km (1310nm wavelength)
1000BaseLX70: 70km (1550nm wavelength)
7
The module doesn't currently support electrical (1000Base-T) SFPs.

NID2655 Rev. B7
3.8.3 LED
The Fast Ethernet Access module provides three LEDs for each Ethernet port showing Link/Activity, 10/100
Mbps, duplex.
The LED functions and colors are as shown in the following table.

Green Link up
1
Green flashing Link activity
Green 100 Mbps
2
Off 10 Mbps
Green Full duplex
3
Off Half duplex
Table 1.LEDs on Fast Ethernet Access module front
3.8.4 Hot-swap
The Ethernet Access modules has a service switch on the front panel, "Removal request", which allows Hot-
swap according to section 2.5.7.

The Ethernet Access modules supports remote upgrade of firmware.

NID2655 Rev. B7
3.9 E1/T1 Access Module
The E1/T1 Access subsystem supports an E1 or T1 clear channel unstructured transport service. From
outside the DTM domain, the PDH tunnel will appear as a cable with constant delay.
Characteristics:
• Eight bi-directional E1/T1 interfaces.
• Comply to G.703 §6/§2
• Protection switching
• Supports multicast of E1/T1 signals
• Fault handling
3.9.1 Performance
• Maximum output jitter of an E1 transmit port conforms to G.823 §2.
• Jitter and wander tolerance of an E1 receive port conforms to G.823 §3
• Protection switching is performed within 50 ms from the occurrence of a DTM DUF or DOF alarm.
• Delay through ingress: <50 μs
• Delay through egress: <400 μs
The line bit rate is 2048 kbps and 1544 kbps respectively for the E1 and T1 services according to G.703.
From Rx to TX two uni-directional channels consisting of 5 (4) slots are set up for the client E1 (T1) stream.
3.9.2 Interface
The E1 physical interface at 120 ohm conforms to the G.703 §6. Line bit rate is 2048 kbps with a tolerance
of +- 50 ppm. HDB3 and AMI line coding is supported.
The T1 physical interface conforms to the G.703 §2. Line bit rate is 1544 kbps with a tolerance of +- 50 ppm.
B8ZS and AMI line coding is supported.
3.9.3 Power
Power is applied to the E1/T1 Access module via the backplane as to any other module. Power consumption
will not exceed 12W.
3.9.4 LED
Each E1/T1 port is equipped with one LED per direction indicating on the TX port:
DUF Data Under Flow
DOF Data Over Flow
AIS Alarm Indication Signal
On the Rx side:
LOS Loss Of Signal
AIS Alarm Indication Signal
The LED functions and colors are as shown in the following table.

NID2655 Rev. B7

Red DUF
Flashing Red Receiving AIS from remote end or DOF
TX Green OK
Flashing Green Line loop-back active
Off Administratively down
Maintenance alarm LOS
Red
Receiving AIS
Flashing Red Green
Rx OK
Flashing Green
DTM loop-back active
Off
Administratively down
Table 1.LEDs on E1/T1 Access module front
3.9.5 Hot-swap
The E1/T1 Access modules have a service switch on the front panel, "Removal request", which allows Hot-
swap according to section 2.5.7.
3.9.6 Performance monitoring

From version A2 of the 8 x E1/T1 Access modules performance monitoring of E1/T1 connections over the
network is supported. Performance data is presented using an ITU-T G.826 style as described in chapter
2.5.9.10
3.9.7 Loop-back
The E1/T1 Access module supports both DTM Loop-back and line Loop-back. In Line Loop-back mode data
is sent normally out on DTM side. In DTM Loop-back AIS is sent out on the line side.
Access Card
Rx I/f
DTM External
Network Equipment
Tx I/f
= Line loopback = DTM loopback
Figure 1. E1/T1 Access module Loop-back modes

Each channel can be protected in a 1+1 configuration for sub 50ms protection switching (typically well below
10ms switch-over time). To use 1+1 protection switching the working and protect paths should be set up
using source routing (see 5.1 for a brief description of source routing) in order to make sure that the paths
are diverse.

NID2655 Rev. B7

The E1 and T1 Access Modules does not support remote upgrade of firmware.

NID2655 Rev. B7
3.10 SDI Video Access Module
The Access Modules of Nimbra One/300 series adapts specific service data for transport over the network
via the Nimbra One/300 series backplane. The SDI Video Access Module offers 270 Mbps SDI interfaces to
the Nimbra 300 series, allowing full uncompressed SDI signals to be transported over the network based on
the ITU-R BT.601/656 (SMPTE 259-C) video standards. The SDI Video Access module uses 563 slots per
SDI channel.
The module supports the Serial Data Transport Interface (SDTI), according to SMPTE 305M, for carrying
data within the 270 Mbps signal.
The SDI Video Access Module includes two Transmit and two Receive SDI ports. A Receive port takes an
SDI or SDTI signal and maps it into a fixed size network channel that is transported across the backplane of
the Nimbra One/300 series, across the network and to one or several Transmit SDI ports in other nodes. The
system also allows for setting up a channel to Transmit ports in the same Nimbra One/300 series or even to
the same Module.

The SDI physical interfaces, Transmit and Receive, are BNC connectors at 75 ohm.
3.10.2 Monitor ports

To each port pair there is one monitoring port that also uses a BNC connector at 75 ohm. The monitoring
port can be configured via a switch button on the front panel, to copy either incoming or outgoing data from
the in/out port pair. It can thus be used to either monitor that a correct signal arrives to the in-port, or be used
to copy the outgoing data, effectively providing a "bi-casting" function on the outgoing signal.

The module only supports 1+1 protection using external equipment, such as signal splitters or distribution
amplifiers together with external change-over units (selector). The module can be configured to shut down,
or squelch, the output upon a fault condition (“TX mute” functionality), hereby shortening the response time
for the external selector unit, which can then also be of a simpler version that only detects Loss Of Signal.
3.10.4 SDI Multicast

Multicast is a way to transport data from one single source to many destinations without any need to
duplicate data on multiple channels. Each individual destination point can either be network or source
routed. They can furthermore be dynamically added and deleted while a connection is still administratively
up.
The ports on the SDI Video Access Module can be the source and destination of such multicast channels for
SDI traffic. A multicast channel can be terminated on ports on several SDI Video Access Modules in the
same Nimbra One/300 series. However, the same multicast channel cannot be terminated on both TX ports
on the same SDI module. It is possible to duplicate the TX signal using the monitoring ports of the SDI Video
Access Module 2.x.

The SDI Video Access module supports performance monitoring of SDI connections over the network.
Performance data is presented using an ITU-T G.826 style as described in chapter 2.5.9.10

NID2655 Rev. B7
3.10.6 Loop-back
Loop-back is a mechanism whereby data received on an interface (from network or external equipment) is
looped back to the place it came from. Combined with an in or out of service measurement, loop-back
modes can be used as an aid to track down problems (e.g. bit errors) caused by network connections.
Network TX I/f Rx
Network External
(via backplane) Equipment
Network Rx I/f TX
= Network Loopback (Network Rx  Network TX) = Line Loopback (I/f Rx  I/f TX)
Figure 2. Loop back modes

Loop-back modes supported by the SDI Video Access Module are both Network and Line. While the former
forwards data from Network Rx to interface TX and Network TX, the latter forwards data from interface Rx to
interface TX and Network TX In both cases data is looped as close to the interface connectors as possible to
include or exclude as many circuits as possible.
3.10.7 Hot-swap
The SDI Video Access Module allows for insertion and extraction of modules during operation. This is called
Hot-swap. The SDI Video Access module has a push button switch on the front panel that generates a
request for service signal to the Node controller. The Node controller then informs that the requested board
can be taken out of service by lighting the Remove LED as described in section 1.7. The module can then
be removed and replaced by a new module.
3.10.8 LED
Each SDI video port is equipped with one LED per traffic port.

Green Active
TX
Red Data Under Flow (DUF)
Red flashing Data Overflow (DOF) or Alarm Indication Signal (AIS)
Green Active
Rx
Red Loss Of Signal (LOS)
Red flashing Loss Of Frame Pulses – no Time Reference Signal found (LOFP)
Table 1.LEDs on SDI Video Access module front

The monitoring ports features the following LEDs and buttons.

Monitor-Out (TX) Green Monitor port in TX stream mode
(One per monitor port) Off TX stream not active
Monitor-In (Rx) Green Monitor port in Rx stream mode
(One per monitor port) Off Rx stream not active

NID2655 Rev. B7
Button selects TX (Out) or Rx (In) stream from ASI port

Select (Monitor 1) (Button)
pair 1 to be forwarded to Monitor port 1
Table 2.LEDs / buttons for the monitoring ports on SDI Video Access module
3.10.9 Alarms
The normal interface alarms are supported by the SDI Video Access Module as shown in the table below:
I/f TX Severity I/f Rx

AIS Alarm Indication Signal Minor Alarm Indication Signal
LOFP N/A Minor Loss Of Frame Pulses
LOS N/A Major Loss Of Signal
DUF Data Underflow Major N/A
DOF Data Overflow Major Data Overflow
Table 3.Alarms sent from SDI Module

The SDI Video Access Modules does not support remote upgrade of firmware.

NID2655 Rev. B7
3.11 ASI Transport Access Module
The Access Modules of Nimbra One/300 series adapts specific service data for transport over the network
via the backplane of the Nimbra One/300 series. The ASI Transport Access Module provides simultaneous
transport of up to four (two in each direction) independent MPEG-2 Transport Streams (TS). The capacity
across the network of each transport channel can be configured to match the actual size of the TS.
The ASI board can handle MPEG-2 transport streams from 2 – 200 Mbps.
The ASI Transport Access Module accepts and transmits MPEG-2 Transport streams according to ISO/IEC
13818-1 (ITU-T H.222), with either 188 byte packets or 204 byte packets. An ASI channel across the
network can be unicast to one receiving port or multicast to several receiving ports. The channel can be set-
up via the management interface or be scheduled via the scheduling mechanism.
The board also has two monitoring ports. Each port can duplicate either the incoming or outgoing signal of
an in-out port pair. They can thus be used for monitoring the incoming ASI stream or for duplicating an
outgoing stream (“bi-casting”).

The ASI physical interface, Transmit and Receive, are Female BNC connectors at 75 ohm.
To each port pair there is one monitoring port, also using a female BNC connector at 75 ohm. Each
monitoring port can be configured via a switch button on the front panel, to copy either incoming or outgoing
data from its in/out port pair. It can thus be used to either monitor that a correct signal arrives to the in-port,
or be used to copy the outgoing data, effectively providing a "bi-casting" function on the outgoing signal.

or squelch, the output upon a fault condition, thereby shortening the response time for the external selector
unit, which can then also be of a simpler version that only detects Loss Of Signal.
3.11.3 ASI Multicast

up.
The ports on the ASI Transport Access Module can be the source and destination of such multicast channels
for ASI traffic. A multicast channel can be terminated on two ports on different ASI Transport Access Modules
in the same Nimbra One/300 series. However, the same multicast channel cannot be terminated on both TX
ports on the same ASI module.

The ASI Transport Access module supports performance monitoring of ASI connections over the network.
3.11.5 Loop-back
modes can be used as an aid to track down problems (e.g. bit errors) caused by network connections.

NID2655 Rev. B7
Network TX I/f Rx
Network External
Network Rx I/f TX

Loop-back modes supported by the ASI Access Module are Network and Line. While the former forwards
data from network Rx to interface and network TX, the latter forwards data from interface Rx to interface and
network TX In both cases data is looped as close to the interface connectors as possible to include or
exclude as many circuits as possible.
3.11.6 Hot-swap
The ASI Access Module allows for insertion and extraction of modules during operation. This is called Hot-
swap. The ASI Access module has a push button switch on the front panel that generates a request for
service signal to the Node controller. The Node controller then informs that the requested board can be
taken out of service by lightning the Remove LED as described in 1.5 LED. The module can then be
removed and replaced by a new module.
3.11.7 LED
The ASI and monitoring ports have LEDS and buttons as shown below.

Transmitting, data OK
Green
Disabled
Off
Line Loopback mode
Out (TX) Green flashing
Data Underflow in TX play-out buffer (DUF)
Red
Data Overflow in TX play-out buffer (DOF) or Alarm
Red flashing
Indication Signal (AIS)
Green Receiving, data OK
Off Disabled
In (Rx) Green flashing Network Loopback mode
Red flashing Loss Of Frame Pulses – loss of packet alignment
Monitor-Out (TX) Green Monitor port in TX stream mode
Monitor-In (Rx) Green Monitor port in Rx stream mode
Button selects TX (Out) or Rx (In) stream from ASI
port pair 1 to be forwarded to Monitor port 1
Button selects TX (Out) or Rx (In) stream from ASI
port pair 2 to be forwarded to Monitor port 2
Table 1.LEDs and buttons on the ASI Transport Access module

NID2655 Rev. B7
3.11.8 Alarms
The following alarms are supported by the ASI Transport Access:
I/f Tx Severity I/f Rx

LOFP N/A Minor Loss Of Frame Pulses
Table 2.Alarms sent from ASI Module

The ASI Transport Access Module does not support remote upgrade of firmware

NID2655 Rev. B7
3.12 8 x ASI Transport Access Module
The 8 x ASI Transport Access module is a further development of the 2 + 2 x ASI Transport Access module
(see 3.11). The major differences is that it supports 8 ports for which each can be used as either a In or Out
port, configurable. There are smaller functional upgrades as well and it supports 1+1 DTM network
protection.
The 8 X ASI board can handle MPEG-2 transport streams from 2 – 212 Mbps.
The 8 X ASI Transport Access Module accepts and transmits MPEG-2 Transport streams according to
ISO/IEC 13818-1 (ITU-T H.222), with either 188 byte packets or 204 byte packets. An ASI channel across
the network can be unicast to one receiving port or multicast to several receiving ports. The channel can be
set-up via the management interface or be scheduled via the scheduling mechanism.
The board also has one monitoring port. This port can monitor any other of the 8 ports. There is a push-
button on the front that selects the port that shall be monitored. Selection can also be done from the Element
Manager.
Both spread-byte and burst transmission modes are handled by the board.

The ASI physical ports are Female BNC connectors at 75 ohm. Each port can be configured as In or Out in
order to maximize utilization of the board. The ports has a reach of 275 m (900 ft).

The module supports 1+1 protection DTM network protection switching as described in 6.2. Note that this is
not supported on the older 2 + 2 ASI module and thus can only be used for connections between two 8 x ASI
Transport modules.
For use with external 1+1 change-over units, the module can be configured to shut down, or squelch, the
output upon a fault condition, thereby shortening the response time for the external selector unit.
3.12.3 ASI Multicast

up.
The ports on the 8 X ASI Transport Access Module can be the source and destination of such multicast
channels for ASI traffic. It is possible to have several ports on the same board as belonging to the same
multicast tree. This is different from the older 2 + 2 ASI board, see 3.11.3.

The 8 X ASI Transport Access module supports performance monitoring of ASI connections over the
network. Performance data is presented using an ITU-T G.826 style as described in chapter 2.5.9.10
On the Interface EM page the estimated bandwidth of the incoming Transport Stream is displayed.
3.12.5 Loop-back
Loop-back in the ordinary sense is not supported since all ports on the 8 x ASI are completely independent
and there is no concept of a "port pair". However, similar functionality can be obtained by operational
procedures.
Line loop-back:

NID2655 Rev. B7
Alternative A: The return channel is connected to the monitor port. In this way any In signal can be looped to
the monitor port, close to the interface side.
Alternative B: Signal In on port x is connected to Out on port y using the element manager. In this way a
loop-back can be set up remotely. Note that this loop-back will traverse the complete RX path of the board
plus the Nimbra One/300 backplane + the complete TX path of the board.
Network loop-back:
Can be performed by connecting a patch cable between the monitor port and any other port. In this way it is
possible to set up (also remotely) any of the Out signals to be passed to the monitor port, which is then
connected to an In port for the return path. This loop-back mode complements the Line loop-back alternative
A in loop-back coverage.
3.12.6 Hot-swap
The 8 X ASI Access Module allows for insertion and extraction of modules during operation. This is called
Hot-swap. The 8 X ASI Access module has a push button switch on the front panel that generates a request
for service signal to the Control Module. The Control Module then informs that the requested board can be
taken out of service by lightning the Remove LED as described in 1.5 LED. The module can then be
removed and replaced by a new module.
3.12.7 LED
The ASI and monitoring ports have LEDS and buttons as shown in 3.12.7.
Port mode Status LED Description

Green Receiving OK
In: RX mode, (TX ON Off Disabled
LED OFF) Red Loss of Signal (LOS)
Red flashing (Loss of Frame or Congestion) AND (NOT LOS)
Transmitting OK
Green
Disabled
Out: TX mode (TX On Off
Loss Of Signal (LOS)
LED ON) Red
(Loss of Frame or Alarm Indication Signal or
Red flashing
Congestion) AND (NOT LOS)
Monitor-mode: (TX ON According to Rx
Port is being monitored.
LED flashing green) or TX status
Monitor port TX ON
Green (Monitor port enabled) AND (One port is monitored)
LED and Monitor port
Off (Monitor port disabled) OR (No port is monitored)
Status LED
Button selects cyclically port 1-8 for forwarding of
Select (Button)
data to the monitor port.
Table 3.LEDs and buttons on 8 X ASI Transport Access Module's front

NID2655 Rev. B7
3.12.8 Defects and alarms

The following defects are recognized by the 8 X ASI Transport Access module:
Priority TX Port RX Port

Highest Loss of Data (LOS) Loss Of Signal (LOS)
Alarm Indication Signal (AIS) Loss of Frame (LOF)
Loss of Frame (LOF) Loss of Data (LOD)
Loss of Data (LOD)
Table 4.Defects recognized by the 8 x ASI board

The 8 x ASI Transport Access Module supports remote upgrade of firmware.

NID2655 Rev. B7
3.13 8 x AES/EBU Access Module
The 8 x AES/EBU Access Module enables transport of AES/EBU sampled audio. It handles all standard
sample rates and will compress the pre-amble to save transport bandwidth without sacrifying transparency
(see 52 below).
The 8 X AES/EBU Access Module accepts and transmits sampled audio streams according to AES3-2003,
at the following sample rates
32, 48, 96, 192, 44.1, 88.2, 176.4 kHz.
An AES/EBU channel across the network can be unicast to one receiving port or multicast to several
receiving ports. The channel can be set-up via the management interface or be scheduled via the
scheduling mechanism. The channel can also be 1+1 protected for < 50 ms fail-over switching.
The board also has one monitoring port. This port can monitor any other of the 8 ports. There is a push-
button on the front that selects the port that shall be monitored. Selection can also be done from the Element
Manager.
Sample rate [kHz] # of allocated slots

32 4
48 6
96 12
192 23
44,1 6
88,2 11
176,2 21
Table 5. Slot allocation for supported sample rates

The ASI physical ports are Female BNC connectors at 75 ohm complying to AES-3id-2001. Each port can
be configured as In or Out in order to maximize utilization of the board. The ports has a reach of 330 m
(1000 ft).

The module supports 1+1 protection DTM network protection switching as described in 6.2.
For use with external 1+1 change-over units, the module can be configured to shut down, or squelch, the
output upon a fault condition, thereby shortening the response time for the external selector unit.
3.13.3 AES/EBU Multicast

up.
The ports on the 8 X AES/EBU Access Module can be the source and destination of such multicast channels
for ASI traffic. It is possible to have several ports on the same board as belonging to the same multicast tree.

NID2655 Rev. B7
3.13.4 Transparent mode

The signal is clocked out with the same frequency as it was clocked in, i.e. using through-timing.

The 8 x AES/EBU Access module supports performance monitoring of audio channels over the network.
3.13.6 Loop-back
Loop-back in the ordinary sense is not supported since all ports on the 8 x AES/EBU are completely
independent and there is no concept of a "port pair". However, similar functionality can be obtained by
operational procedures.
Line loop-back:
Alternative A: The return channel is connected to the monitor port. In this way any In signal can be looped to
the monitor port, close to the interface side.
Alternative B: Signal In on port x is connected to Out on port y using the element manager. In this way a
loop-back can be set up remotely. Note that this loop-back will traverse the complete RX path of the board
plus the Nimbra One/300 series backplane + the complete TX path of the board.
Network loop-back:
Can be performed by connecting a patch cable between the monitor port and any other port. In this way it is
possible to set up (also remotely) any of the Out signals to be passed to the monitor port, which is then
connected to an In port for the return path. This loop-back mode complements the Line loop-back alternative
A in loop-back coverage.
3.13.7 Hot-swap
The 8 x AES/EBU Access Module allows for insertion and extraction of modules during operation. This is
called Hot-swap. The 8 X AES/EBU Access module has a push button switch on the front panel that
generates a request for service signal to the Control Module. The Control Module then informs that the
requested board can be taken out of service by lightning the Remove LED as described in 1.5 LED. The
module can then be removed and replaced by a new module.
3.13.8 LED
The AES and monitoring ports have LEDS and buttons as shown below.
Port mode Status LED Description

Green Receiving OK
In: RX mode, (TX ON Off Disabled
LED OFF) Red Loss of Signal (LOS)
Red flashing (Loss of Frame or Congestion) AND (NOT LOS)
Transmitting OK
Green
Disabled
Out: TX mode (TX On Off
Loss Of Signal (LOS)
LED ON) Red
(Loss of Frame or Alarm Indication Signal or
Red flashing
Congestion) AND (NOT LOS)
Monitor-mode: (TX ON According to Rx
Port is being monitored.
LED flashing green) or TX status
Monitor port TX ON Green (Monitor port enabled) AND (One port is monitored)

NID2655 Rev. B7
LED and Monitor port

Off (Monitor port disabled) OR (No port is monitored)
Status LED
Button selects cyclically port 1-8 for forwarding of
Select (Button)
data to the monitor port.
LEDs and buttons on 8 x AES/EBU Access Module's front
3.13.9 Defects and alarms

The following defects are recognized by the 8 x AES/EBU Access module:
Priority TX Port RX Port

Highest Loss of Data (LOS) Loss Of Signal (LOS)
Alarm Indication Signal (AIS) Loss of Frame (LOF)
Loss of Frame (LOF) Loss of Data (LOD)
Loss of Data (LOD)
Table 6.Defects recognized by the 8 x AES/EBU board

The 8 x AES/EBU Access Module supports remote upgrade of firmware.

NID2655 Rev. B7
3.14 HDSDI functionality on the Nimbra 340HD
The HD-SDI ports on the Nimbra 340-HD offers a High Definition SDI interface for switched transport of
1485/1483.5 Mbps HD-SDI streams, allowing full uncompressed HD-SDI signals to be transported over the
network based on the SMPTE 292M video standards.
The Nimbra 340-HD has two Transmit and two Receive HD-SDI physical ports. The unit handles one in-
coming and one out-going HD-SDI stream. Thus one of the two In/Out pairs of physical ports can be used at
a time. It is configurable from the Element Manager which In and Out ports that should be used for the HD-
SDI streams.
An In-port takes an HD-SDI bit stream and maps it into a fixed size network channel that is transported
across the backplane of the Nimbra 340, across the network and to one or several HD-SDI Out-ports in
other nodes. There are two modes of operation, one for the "integer" frame rate video formats at 1485 Mbps,
and the other for the "fractional" frame rate video formats at 1483.5 Mbps. 1485 Mbps video formats
consumes 2901 DTM slots per channel and 1483.5 Mbps video formats consumes 2898 DTM slots per
channel. The channel overhead is about 0.02%.

The HD-SDI physical interfaces, In and Out, are BNC connectors at 75 ohm. The ports handles transmission
distances up to 90 meters using standard Belden 1694A cable.
3.14.2 Monitor ports

To each port pair there is one monitoring port that also uses a BNC connector at 75 ohm. The monitoring
port can be configured via a switch button on the front panel, to copy either incoming or outgoing data from
the in/out port pair. It can thus be used to either monitor that a correct signal arrives to the in-port, or be used
to copy the outgoing data, effectively providing a "bi-casting" function on the outgoing signal.
3.14.3 HD-SDI stream formats

Video source format detection is performed on the incoming signal. The result is presented in the Element
Manager according to System nomenclature as shown in the table below. A special case is 1920x1080i @
50 Hz since this active picture format exists in two different framing formats. To distinguish between these
the total number of lines is shown for the (almost obsolete) 1250 lines signal.
Samples
Samples per Active lines Frame rate Scanning Total lines
System nomenclature per total
active line per frame [Hz] format per frame
line
1920x1035i @ 60 Hz 1920 1035 30 2:1 interlace 2200 1125
1920x1035i @ 59.94 Hz 1920 1035 30 / 1.001 2:1 interlace 2200 1125
1920x1080i @ 50 Hz (1250
1920 1080 25 2:1 interlace 2376 1250
lines)
1920x1080i @ 60 Hz 1920 1080 30 2:1 interlace 2200 1125
1920x1080i @ 59.94 Hz 1920 1080 30 / 1.001 2:1 interlace 2200 1125
1920x1080i @ 50 Hz 1920 1080 25 2:1 interlace 2640 1125
1920x1080p @ 30 Hz 1920 1080 30 Progressive 2200 1125
1920x1080p @ 29.97 Hz 1920 1080 30 / 1.001 Progressive 2200 1125
Table 7.Supported HD video formats

NID2655 Rev. B7
Video formats falls into two categories, the first supported by the nominal 1485 Mbps rate, and the other
supported by the 1483.5 Mbps bit rate (the ones having a "1.001" in the denominator in the "Frame rate"
column above). The bit rate mode must be configured in the Element Manager (to either 1485 Mbps or
1483.5 Mbps).
3.14.4 HD-SDI Multicast

up.
The HD-SDI ports can be the source and destination of such multicast channels for HD-SDI traffic. It is
possible to multicast to both Out ports of a Nimbra 340-HD. Together with duplication of an Out port using
the monitor port it is possible to have four copies of an Out HD-SDI stream.

The HD-SDI ports supports performance monitoring of HD-SDI connections over the network. Performance
data is presented using an ITU-T G.826 style as described in chapter 2.5.9.10
3.14.6 Loop-back
modes can be used as an aid to track down problems caused by network connections.
Network TX I/f Rx
Network External
Network Rx I/f TX

Loop-back modes supported by the HD-SDI ports are both Network and Line. While the former forwards
data from Network Rx to interface TX and Network TX, the latter forwards data from interface Rx to interface
TX and Network TX In both cases data is looped as close to the interface connectors as possible to include
or exclude as many circuits as possible.

or squelch, the output upon a fault condition, thereby shortening the response time for the external selector
unit, which can then also be of a simpler version that only detects Loss Of Signal.
3.14.8 LED
Each HD-SDI video port is equipped with one LED per traffic port.

NID2655 Rev. B7
Green Active
Green flashing Line loopback
Out Off Administratively down
Red Data Under Flow (DUF)
Red flashing Data Overflow (DOF) or Alarm Indication Signal (AIS)
Green Active
Green flashing Network loopback
In Off Administratively down
Red flashing Loss Of Frame Pulses – no Time Reference Signal found (LOFP)
Table 1.LEDs for HD-SDI ports

The monitoring ports has the following LEDs and buttons.

Monitor-Out (Out) Green Monitor port in TX stream mode
Monitor-In (In) Green Monitor port in Rx stream mode
Table 2.LEDs / buttons for the monitoring ports on the Nimbra 340-HD
3.14.9 Alarms
Interface alarms that are supported by the HD-SDI interfaces are shown in the table below:
I/f TX Severity I/f Rx

LOF N/A Minor Loss Of Frame Pulses
Table 3.Alarms sent from HD-SDI ports of the Nimbra 340-HD
3.14.10 Technical specifications HD-SDI interface

Line impedance: 75 ohm
TX return loss: >15 dB (5-1485 MHz)
RX return loss: >15 dB (5-1485 MHz)
TX signal amplitude: 800 mV ±10%
DC offset: +0.5 to -0.5 V
Rise and fall times: (20%-80%) max 270 ps, differ <100 ps
Input lock-up time: Less then one line-duration

NID2655 Rev. B7
Input frequency tolerance: ±10 ppm

Output frequency: Locked to input frequency (nominal 1.485 GHz or 1485/1.001 GHz)
Output timing jitter: < 1 UI (Band-pass filter 10 Hz – 1.485 GHz, 20 dB/dec roll-off).
Output alignment jitter: < 0.2 UI (Band-pass filter 100 kHz – 1.485 GHz, 20 dB/dec roll-off).
Wander: < 22.6 ppb/s (Low-pass filter 1 Hz corner, 20 dB/dec roll-off) during
normal network operation.
Board latency: TX direction: <150 μs; RX direction:<10 μs
Reach: 90 m (Belden 1694A cable)

NID2655 Rev. B7
4 Management
As previously mentioned, management operations can be performed via a command line interface (CLI),
web browser (http), or an optional network management system (Nimbra Vision or third party system) over
SNMP. This chapter briefly describes the functionality in these different interfaces.
4.1 Interfaces and management network
4.1.1 Command Line Interface

The CLI provided by the Nimbra Operations System (NimOS) is quite straightforward, basically consisting of
SET and GET operations on managed objects in the node. Thus, all possible operations can be performed
over the CLI, and for experienced users it may actually be faster to use than the web interface. In addition to
this, it provides the possibility to automate tasks via scripts and batch files.
4.1.2 Web Interface

NimOS contains an embedded web server that allows the user to access network nodes via a standard web
browser. Almost all functions in the node can be graphically managed via this interface. Although all
operations are initiated in a single node at a time, the extensive signaling protocols provided in the Nimbra
platform help to make many network-wide operations quite convenient. As an example, when provisioning a
connection across a network, only the end-nodes for the connection need to be configured and the operator
never needs to bother about the topology of the rest of the network.
The web manager supports two user categories, read-only and full access. A read-only user is only allowed
to view status information and may not perform any configuration operations.
Examples of functionality in the Web interface:
• Status and Alarm Monitoring
• Maintenance of equipment and software
• Nimbra network configuration
• Provisioning of ETS and ITS connections
• Performance monitoring
• ITS and ETS Scheduling
4.1.3 SNMP Interface

Operations that involve many nodes within a network are often cumbersome to execute from an element
manager. NimOS therefore also provides an SNMP agent (SNMP v3 compatible) and a number of MIBs that
can be accessed from a central management system. As the central SNMP manager has knowledge of all
nodes in the network, it can execute operations on many network elements based on a single request from
the operator. The MIBs supported include enterprise MIBs that are primarily used by the Nimbra Vision
network manager, but NimOS also implements some standard SNMP MIBs that can be accessed from third
party network managers.
Standard MIBs:
• MIB-2
• RMON statistics group
• Entity MIB, entity physical group

NID2655 Rev. B7
Enterprise MIBs:
• Event MIB (SNMP Notifications for alarms and events)
• ETS MIB (ETS configuration and statistics)
• Ethconf MIB (Configuration of Ethernet access interfaces)
• ITS MIB (SONET/SDH, PDH, SDI and ASI configuration)
• DTM MIB
• PM MIB (G.826 performance counters)
• ChMgr MIB (Channel manager)
• Config MIB
4.1.4 In-band and Out-band Management Channels

The Nimbra platform supports in-band management communication between nodes. No additional hardware
is required for this. The in-band channel is a service in the network, which will use its own connections. The
management traffic is therefore separated from all other traffic. In case of a failure in the network the
management traffic will automatically be rerouted. At least one Nimbra node must act as a gateway between
the in-band and the out-band management networks to route the IP traffic. The bandwidth of the in-band
channel is 512 kbps.
The in-band management network uses the DTM LAN Emulation, DLE, service. With DLE a separate logical
management network is created over the DTM network infrastructure. Each network node is then
administered by accessing it over the DLE segment. See the Element Manager manual for a comprehensive
description of how to use DLE.
It is also possible to manage the network via an out-band management network. In this case each network
element is connected to an external DCN via the control ports of the switch (Ethernet or Serial, see 2.5.9.8).

NID2655 Rev. B7
4.2 Fault Management
The Fault management function gives the operator of a network the necessary means to localize and repair
faults in the network. Defects are detected and isolated, as close as possible, to the source. Alarm filtering is
used to avoid alarms triggered by short glitches and to avoid that secondary alarms are reported when root
cause alarm is detected during defect correlation. Defect correlation is used to show only the root fault
cause of a detected defect and thus be able to suppress secondary defects. The resulting fault cause is
reported as an alarm, which is logged in the Alarm log. A summary of currently active alarms is presented on
request to a user.
Each active alarm is assigned a severity as defined by the following and in compliance with ITU-T X.733:
• Critical
The Critical severity level indicates that a service affecting condition has occurred and an immediate
corrective action is required. Such a severity can be reported, for example, when a managed object
becomes totally out of operation and its capability must be restored.
• Major
The Major severity level indicates that a service affecting condition has developed and an urgent
corrective action is required. Such a severity can be reported, for example, when there is a
severe degradation in the capability of the managed object and its full capability must be restored.
• Minor
The Minor severity level indicates the existence of a non-service affecting fault condition and that
corrective action should be taken in order to prevent a more serious (for example, service affecting) fault.
Such a severity can be reported, for example, when the detected alarm condition is not currently
degrading the capacity of the managed object.
• Warning
The Warning severity level indicates the detection of a potential or impending service affecting fault,
before any significant effects have been felt. Action should be taken to further diagnose (if necessary)
and correct the problem in order to prevent it from becoming a more serious service affecting fault.
Path connectivity events can be filtered with a persistence filter that filters out the effects of transient failure
in lower network layers. Persistence filtering has the effect that the lower layer can restore the connectivity
without causing alarming and re-routing of services in the upper layer. Persistence filtering can be
configured on a per-interface basis. The timer associated with the persistence filter is configurable from 0 to
10,000 ms.
Alarm monitoring is scalable according to the number of circuits/interfaces provisioned in the switch.
The system also logs and displays events such as configuration changes, alarms and other system related
events.
Current active/standby status is displayed via the management interface for node controller, switch module,
and access interface.
Diagnostic functions are available to detect failure and/or degradation of all significant hardware and
software components. These components include the system chassis, power subsystem, hardware cards
and sub-cards, external interfaces and ports, the operating system, and software modules. External
interface diagnostics include line and network loopback.
Hardware, software and firmware inventory reporting is available for all modules.

NID2655 Rev. B7
4.3 Performance Management
The Performance management function performs collection of measurement data to allow a network
operator to base the planning of network reconfiguration and maintenance on statistics reports on the
performance of network resources.
All monitoring points are sampled every second. If a parameter cannot be calculated, e.g. because a sample
is unavailable or a sample is outside the value range of the measurement point, the performance interval is
declared invalid. New performance calculations are started every even 15 minutes (hh:00, hh:15, hh:30,
hh:45) and 24 h (00:00), respectively. All monitoring points are then reset.
Performance reports are issued at the end of the measurement intervals. The performance reports are
logged. The size of the PM log is configurable to store up to 96 latest 15 min reports and 30 latest 24 h
reports. The PM function is scalable according to the number of circuits/interfaces provisioned in the switch.
A threshold can be defined for each performance parameter: An alarm is issued when a threshold is
crossed. Threshold crossing alarms are reset after a complete measuring period where the threshold value
has not been exceeded.
The system also generates real-time Degraded Signal (DEG) alarms. It is possible to select the degraded
threshold for the DEG alarm.
The Nimbra 600 series supports performance management to ITU-T G.826 based on SONET/SDH and
DTM performance primitives. G.826 statistics are available for all trunk interfaces.
4.3.1 Trunk interface
Performance monitoring of trunks covers the part of the network between adjacent Nimbra nodes. A node-to-
node trunk connection involves termination and generation of several SONET/SDH layers
(Section/Regenerator Section, Line/Multiplex Section, and Higher-Order Path). A trunk connection always
consists of a single higher-order path and in many cases also of a single line/MS and a single section/RS.
PM data is therefore accumulated to 15min/24h parameters at the higher-order path layer only. Only near-
end statistics are provided since far-end data is available from the remote node. The following parameters
are available for each near-end VC-4-Xc/STS-Nc path:
• ES (Errored Seconds)
• SES (Severely Errored Seconds)
• BBE (Background Block Errors)
• UAS (Unavailable Seconds)
• SS (Slip Seconds)
In addition, the accumulated counter values since last read-out of the following SONET/SDH overhead may
be monitored:
B1, B2, B3, M0, M1, G1 REI, PJE+ TX, PJE- TX, PJE+ Rx, PJE- Rx.
The current values of the following received bytes are also available:
J0, S1, J1, C2.
4.3.2 Physical layer
All optical trunk interfaces also support monitoring of the following parameters at the physical layer:
• Transceiver temperature
• Laser bias current
• Transmitted optical power
• Received optical power

NID2655 Rev. B7
4.4 Nimbra Vision
Nimbra Vision is a comprehensive network management tool providing a superior overview of the operation
of a Nimbra network. With Nimbra Vision the operator has full control of the activities inside the network.
While the Element Manager enables the precise configuration of a certain node, the Network Manager gives
a consolidated overview of the network status and enables end-to-end service provisioning at the network
layer. From the Nimbra Vision network map it is possible to drill down from network to node view by double-
clicking on a node icon, thereby launching the element manager.
Nimbra Vision continuously monitors the network for faults and performance degradation. ITU-T G.826
methods are used to provide a standardized way of measuring performance in order to support flexible
service-level agreements (SLAs). Nimbra Vision uses SNMPv1/2c/3 for fault and performance management,
ensuring maximum compatibility also with 3rd party equipment. The Nimbra Vision Network Manager is
highly configurable to meet the operator's need of integration with existing systems. Collected data, whether
it is fault, performance, or network inventory data, can be searched and filtered in any order that suits the
operator.
Introduced in Nimbra Vision 5.0, the operator now also has the ability to provision services end-to-end
across the network with full graphical support. Source and destination nodes are selected from the Nimbra
Vision map. If automatic routing is chosen the actual route through the network may easily be displayed in
the map using the Channel Trace function. The option of predefined source routing is also available in
Nimbra Vision, again using the map to quickly define the path through the network.
Third-party management systems may be connected either to the north-bound interface of Nimbra Vision for
fault and performance management, or directly to the SNMP interface of the gateway network element(s) for
fault, performance, and configuration management.

NID2655 Rev. B7
5 Service Provisioning
This chapter describes the actual end-user services that can be provisioned in Nimbra networks from Net
Insight. These services are based on features provided in the underlying network.
The following types of transport services are supported:
• ETS, Ethernet Transport Service
• ITS, Isochronous Transport Services (e.g. for PDH/SDH/SONET and ASI/SDI transport services)
In the following sections, there are also descriptions of the options (value added services) that are available
in conjunction with the basic transport.
5.1 Basic concepts
A trail termination point (TTP) is a logical entity in a node. The TTPs are used as originating and terminating
points for connections, i.e. connections are set-up between TTPs. The TTP is also used as a point to where
a local physical interface is associated. I.e. for a TTP to be fully configured, it must also have an associated
physical interface. Administrative data, such as customer id and purpose can be assigned to a TTP.
Performance data counters may also associated with TTPs.
originating node terminating node
physical connection physical

interface TTP TTP interface
association association
Figure 1. Connection from a TTP in the originating node to the TTP in the
terminating node. Physical access interfaces are associated with the TTPs
to allow transport of data form external equipment.
A connection may have different characteristics, such being multicast, source routed, and/or 1+1 protected.
It depends on the capabilities of the service and/or the device whether the characteristic is available.
A connection can be of type unicast or multicast. A unicast connection has exactly one destination, while a
multicast connection can have multiple destinations.
A connection can be source routed. When a connection is source routed, it is pre-defined at the source (the
originating node) what path its channel shall take through the network. For a strict source routed channel,
the channel path is established through each node and interface exactly as specified. For a loose source
routed channel, the channel is established using additional nodes as needed to reach the destination. Note
that if no source route is specified, it acts as the special case with a loose source route specifying neither
nodes nor interfaces.
A connection can be 1+1 protected8. A protected connection consists of two established channels from the
TTP in the originating node to the TTPs in the terminating nodes. The channels should be configured to take
different paths through the network, using source routing. The connection is not 1+1 protected, it uses only
one channel. 1+1 protected connections are used for services that require a hot stand-by channel for quick
recovery in case of a network problem.
8
1+1 fast protection switching is service dependent. See 6.2

NID2655 Rev. B7
5.2 ETS – Ethernet Transport Service
5.2.1 Service description

ETS provides connectivity between Ethernet ports located anywhere on the rim of a Nimbra network. The
main features and characteristics are as follows
• Transparent transport. Ethernet frames will be unchanged between ingress and egress ports and both IP,
IPX/SPX traffic can be transported
• The ingress and egress module can choose path based on IEEE802.1Q VLAN tags
• VLAN tags need not be globally unique within the network, thus providing scalability in the provisioning of
VPN services on top of the Nimbra network.
• Bit rate is individually selectable for all connections
• Dedicated transport channels ensure that traffic characteristics are unaffected by network size and other
traffic in the network
• Ethernet user priority (IEEE 802.1p) and IP Diffserv are supported, ensuring that high priority Ethernet
packets are mapped first onto the ETS channels
• ETS connections benefit from the re-establishment mechanism in the Nimbra system if redundancy is
provided in the network
• ETS multicast is supported for uni-directional connections
• Scheduling of ETS connections is supported
5.2.2 Configuration
The following objects, shown in the picture below, are involved when provisioning an ETS connection:
EthPort A physical Ethernet port on an access module. A default VLAN can be assigned to
untagged packets received on an Ethernet port
ETSClient A dynamically created “virtual port”. Two ETS clients are connected across a Nimbra
network by two channels (one for each direction)
VLAN As defined in IEEE802.1Q. Both Ethernet ports and ETS clients must be associated to
one or more VLANs
1+ 1
VLAN ETSClient
1+
1
EthPort
Connectivity between Ethernet ports and ETS clients on an access module is defined by what VLANs they
belong to. If Port X and a Client Y both belong to VLAN Z, all packets with VLAN tag Z arriving to client Y
from the Nimbra network will be transmitted on Port X and all traffic with VLAN tag Z arriving at Port X will be
sent on the outgoing channel belonging to Client Y.
As both Ethernet ports and ETS clients may belong to several VLANs it is, for example, possible to distribute
traffic from a single Ethernet port to different remote sites based on the VLAN tags in the packets.

NID2655 Rev. B7

Most of the MIB-2 counters for Ethernet are available on both the Ethernet access ports and on the ETS
clients. It is thus possible to monitor utilization of connections, and to localize possible transmission
problems within the network.
5.2.4 ETS Scheduling

The scheduling function for ETS connections can for example be used to adapt the bit rate to remote offices
in a VPN during different hours of the day, or to provide connectivity only during daytime.
The following capabilities are provided by the scheduling function:
• Set single time-point(s) for change of capacity on a connection
• Set daily time-point(s) for change of capacity on a connection
• Set weekly time-point(s) for change of capacity on a connection
Each of the time-points must of course have a new bit rate for the connection associated to them.
5.2.5 ETS Multicast

ETS multicast provides a point-to-multipoint service in a Nimbra network. Main differences compared to ETS
unicast are:
• An ETS multicast connection is uni-directional, whereas an ETS unicast connection always is bi-
directional
• There is only one source but there may be many destinations. All traffic fed to the source will be received
in all destinations
5.3 ITS – Isochronous Transport Services
ITS currently include support for five different types of signals, namely
SDH/SONET Synchronous Payload Envelopes / Virtual Containers within SDH/SONET access
interfaces
PDH Plesiochronous Digital Hierarchy signals e.g. DS1 or DS3
HD/SD SDI Serial Digital Interface. A standard used within the professional media industry for
interfacing to equipment generating 1485/270 Mb/s uncompressed video signals.
ASI Asynchronous Serial interface. A standard for transmitting MPEG-2 coded video,
commonly applied in distribution of digital TV. The bit rate of the actual payload in the
signal may vary.
AES/EBU Audio Engineers Society/European Broadcasting Union. A standard for transmission
of sampled audio signals. A number of fixed sample rates exists.
Although the transported traffic is different in these standards, the management and provided capabilities
are very similar, and they are therefore handled by a common service application.
5.3.1 Service description

The basic ITS provides connectivity between access ports located anywhere on the rim of a Nimbra
network. The main features and characteristics are as follows:
• Dedicated transport channels ensure that traffic characteristics comply with stringent requirements on
timing (jitter and wander) regardless of network size and other traffic in the network

NID2655 Rev. B7
• Capacity on ASI connections can be adapted to the actual bit rate of the payload in the transported
stream
• ITS connections benefit from the re-establishment mechanism in the Nimbra system if redundancy is
provided in the network
• Mission critical connections can be redundancy protected
• Multicast of all traffic types is supported
• Scheduling of ITS connections is available
5.3.2 Configuration
Provisioning of basic, point-to-point, ITS connections is simple. The procedure consists of identifying the two
access interfaces that are end-points for the connection, create an originating Trail Termination Point (TTP)
for one of the interfaces and a terminating TTP for the other and then associate these two TTPs to each
other.
This will yield a uni-directional connection. For a PDH or SDH/SONET connection, which is always bi-
directional, the procedure has to be repeated for the other direction.

ITS services can be monitored with respect to
• Traffic that enters the interfaces (Access PM)
• Traffic that has been transported through the DTM network (Connection PM)
The following performance monitoring functions for ITS traffic are available:
• Monitor performance of a connection end-to-end based on the ITU standard G.826
• Measure unavailable seconds, defects and anomalies in 15 minute and 24 hour intervals
• Raise alarms if user-defined thresholds are exceeded
Performance monitoring on a customer’s connection can for example be used to check conformance to
quality parameters defined in service level agreements. Note that not all hardware, most notably older HW,
support access and/or connection PM.
5.3.4 ITS Scheduling

The scheduling function for ITS connections can for example be used to provide connectivity for live SDI
transmissions from an arena that is in use only during a limited number of hours each day.
The following capabilities are provided by the scheduling function:
• Set single time-point(s) for establishment/removal of connection
• Set daily time-point(s) for establishment/removal of connection
• Set weekly time-point(s) for establishment/removal of connection
5.3.5 ITS Multicast

ITS multicast has the following properties:
• Distributes the signal from one sender to many receivers that may be located on several, geographically
separated sites.
• Based on point-to-multipoint channels which means that traffic characteristics will be the same as for
unicast connections and that capacity requirements on a single data-link in the network never exceeds
what is required for a unicast connection, regardless of the number of receivers.

NID2655 Rev. B7
6 Network Restoration
A Nimbra network provides various options for automatic restoration of services in case of network failures.
The network restoration solution can be tailored to the individual demands on service availability. The
Nimbra solution supports any mix of 1+1 protection, predefined rerouting, or hop-by-hop rerouting in any
network topology.
6.1 Rerouting
6.1.1 Channel Establishment

When provisioning a circuit in the network, the Nimbra platform will automatically establish a path through
the network between the endpoints of the circuit, and establish the circuit over that path.
Circuits can either be hop-by-hop routed or source routed. In case of hop-by-hop routing the built-in dynamic
routing algorithm will automatically find the shortest path end-to-end through the network for the circuit.
When a connection is source routed, the path through the network is pre-defined at the source (the
originating node). For a strict source routed channel, the channel path is specified through all nodes and
interfaces in the network. For a loose source routed channel only a subset of nodes and interfaces is
specified, and the channel is established using additional nodes as needed to reach the destination.
Sometimes, it is not possible to use the best path through the network. A typical example of this case is
when a link does not have enough free capacity to establish the requested channel over it. This will only be
detected by the node directly before the link with insufficient capacity, since the other nodes are not aware of
how much capacity is available on that link. The node before the link with insufficient capacity will then try all
other possible next hops towards the destination. If it fails to find any next hop with sufficient capacity, it will
send an error message back to the previous node for the channel. That node will then try all other possible
next hops and so on until the channel reaches the final destination or it has come back all the way to the
source node and it has tried all possible next hops. This mechanism is called crankback
6.1.2 Handling of Failures

There are two main types of failures that can occur, link failures where a single fiber or a pair of fibers are
cut and node failures where a node stops responding or reboots. Both types of failures are detected by the
nodes closest to the error. In the case of link failures this is the two nodes connected to either end of the
fiber and in the case of node failures the nodes that are connected to the failed node via a fiber.
When a node detects a failure, it responds by tearing down all channels that are affected by the failure. In
the case of a link failure, this means that all channels running over the failed fiber will be torn down. If the
connection between two nodes consists of a single fiber pair, then all channels running over both fibers in
the pair will be torn down in case one of the fibers fails. This is done since it is impossible to supervise a
channel running over a uni-directional link. However, if two nodes are interconnected with two fiber pairs and
they suffer a single fiber failure, then channels on the remaining three fibers will remain unaffected.
The channels are torn down by sending control messages to both the source and the destination for each
channel. This means that both the sender and the receiver will notice that a channel has been torn down
and can take appropriate action.
Restoration is handled by the source node for each channel. When it receives the control message saying
that the channel has been torn down, it will immediately try to reestablish the channel. It does this by
performing a normal channel establishment. This normally means that it will try to reestablish the channel
along the same path as the failed channel. If this fails, the crankback mechanism will kick in and find another
path through the network. After some time, DRP will also have detected the new network topology and
updated all routing tables in the network. Channels can then avoid the failed link and find the shortest path
through the network without utilizing crankback. Dynamic re-routed services may be regroomed to follow the
currently most optimal route upon user instruction. For each channel, three source routes can be specified.

NID2655 Rev. B7
These will be applied in priority order, i.e. when establishing (or re-establishing) the connection, the first
source route will be tried first. If the connection set-up fails it will use the second source and then the third.
To regroom a connection it is thus only necessary to re-establish the connection.
If a network failure affects a multicast channel, all destinations downstream from the point-of-failure will be
removed from the multicast tree. The source node will be notified that the destinations have been removed
and will try to add the removed destinations as receivers for the channel again.
A main benefit of the re-routing function is that there is no need to keep redundant links on “hot standby”.
Spare capacity can be shared between services and utilization is therefore improved significantly. Another
benefit is that multiple failures can be handled in networks with more than one alternative path.
The time it takes to re-establish the circuit over the alternative path is dependent on how many nodes that
are part of the alternative path, and thus have to participate in the node signaling that takes place to re-route
the channel, and on how many circuits that need to be re-routed simultaneously. Re-establishment of a
circuit using re-routing will typically take from 300ms up to one or a couple of seconds, depending on
network size, number of channels affected etc.
6.1.3 Connection Re-establishment Interval

If a channel establishment fails, i.e. there is no path from the source to the destination with enough capacity
available, the source node will wait for a period of time X before it tries to establish the channel again. The
time it waits can be changed by setting the "Minimum interval" and "Maximum interval" for the channel. The
first time it waits (i.e. after the first failed attempt at setting up the channel), X will be equal to the "Minimum
interval". For each subsequent failure, X will be doubled as long as X is less than "Maximum interval". After
that, X will always equal "Maximum interval". This is called an exponential backoff algorithm, since the time
between establishment attempts increase exponentially with the number of tries.
The "Minimum interval"-parameter will thus decide how aggressively the node tries to reestablish the
channel directly after a failure. The "Maximum interval"-parameter decides how often the node tries to
reestablish the channel in case the error situation persists for a longer period of time.
6.1.4 Precedence
It is also possible to prioritize the recovery of certain channels over others based on how critical they are.
This function called ‘precedence’ allows the system to re-establish highest priority channels first. Setting
precedence to on for a channel means that the system will prioritize this channel over other channels. This
means two things:
• When a link or node failure is detected, the channels with precedence set to on will be torn down first.
This means that the sending node will be notified of the error sooner and can start reestablishing these
channels first.
• If a node has several channels to establish, it will establish all channels with precedence on first.
6.2 1+1 Protection
1+1 protected connections are used for services that require a hot stand-by channel for fast recovery
(<50ms) in case of a network problem. This is typical for telecoms applications and is supported for the
T1/E1/STS-1/STS-3c/VC-4 services. Working and protecting paths through the network are specified using
source routing.
The principle of 1+1 protection is characterized by:
i. Splitting the channel into two identical channels in the source node
ii. Transporting the split channels through individual paths through the network, using strict or loose
source-routing
iii. Joining the two channels in the destination node, by selecting one of them according to a switch
criterion.
It is single-ended in the sense that the decision to perform a switch is taken locally, i.e. no signaling between
end nodes is necessary.

NID2655 Rev. B7
The 1+1 protection mechanism may also optionally be combined with re-routing, whereby 1+1 protection is
used as primary restoration mechanism and in case both the working and protection paths have failed the
dynamic re-route protection will be activated.
6.3 ASI/SDI protection
The requirements on availability of broadcast video signals are so high that in many cases equipment
redundancy is required. The split and join of the client signal is then performed by external splitters or
distribution amplifiers and by change-over units. In order to help the change-over units to make a swift
decision, ASI and SDI interfaces can be configured to "squelch" the output signal momentarily if the port
detects an upstream error. Very fast switch over times can be achieved in this way.
SDI and the 2+2 port ASI interfaces for the Nimbra 340 or Nimbra One does not support internal 1+1,
however the fast re-route mechanism as described in 6.1 applies to these services.
However the 8 x ASI Transport Access module supports internal 1+1 protection switching according to 6.2.
6.4 Trunk Manager application
The Trunk Manager is the part of the Element Manager that controls the Trunk Modules. It provides a
common look and feel for the various Nimbra 300 series trunk interfaces. Differences may occur depending
on capabilities of the specific interface. Common functions to all trunk interfaces are
• Interface name and status information
• Advanced configuration
• Current alarms
The advanced configuration part includes setting of parameters that may differ between SDH and Sonet,
such as the SS bits of the pointer. See the Element Manager Manual for a description on how to set the
different options.
6.4.1 The signal failure filter

The signal failure filter, which can be set for all trunk modules, deserves some more explanation. When a
DTM signal is disturbed enough to loose frame synchronization, i.e. enter LOFS state, the link is taken down
and all channels on the link are subject to re-routing in order to find a working path to the destination. This is
clearly contra-productive if a lower layer handles protection switching. Typically in Sonet/SDH and WDM
networks, these handles protection switching within 50ms, with much lesser impact than complete re-routing
of all channels.
To avoid this re-routing situation in cases where lower layer protection switching can be used, a LOFS filter
time can be set. The filter can be set to any time between 0 - 2000 ms, where 50 ms is default . If the filter is
set to for instance 70 ms, the system will ignore LOFS alarms and hope that the lower layer has restored the
connectivity within that time. If the LOFS condition still prevails after 70 ms the link will be taken down with
all its consequent actions. If the connectivity is restored within the 70 ms traffic flows as usual.
Since the action applies to all types of "glitches", not only protection switching, the function is also usable in
situations where for example severe bit errors rates would jeopardize the frame synchronization.
Correct use of the Signal failure filter can reduce the amount of re-routing and signaling in the network
substantially and increase the general availability.

NID2655 Rev. B7
7 Specifications
7.1 Physical
7.1.1 Nimbra One

Form factor 19'' rack mountable or free standing
Switching Capacity 5 Gbps for bi-directional only traffic
Switch Modularity 1 Control Module plus 7 interface module slots
Plug-in unit types Control Module, Access or Trunk modules, vertically mounted
Cooling Temperature controlled fan, vertical airflow
Height 505 mm (19.9 inch)
Width 445 mm (17.5 inch)
Depth 240 mm (9.4 inch) mounting depth, 270 mm (10.6 inch)
Rack mounting 19"
Size, packaged unit 62 x 57 x 39 cm (24.4 x 22.4 x 15.4 inch)
Weight, packaged unit 23 kg (50 lb)
Module Height 6 HE (266.7mm/10.5 in)

Module front Width 50mm /2'' (finger strips for EMC excluded)
Module Depth 175.2mm / 6.9'' (montage excluded)
208mm / 8.2'' (montage included)
Module Weight 0.5kg / 1.1 lb
All modules are based on Europe standard with 2x192-pool contact gear.
7.1.2 Nimbra 300 series

Form factor 19'' rack mountable or free standing
Switching Capacity 5 Gbps for bi-directional only traffic
Switch Modularity 2 interface module slots
Plug-in unit types Access or Trunk, horizontally mounted
Cooling Temperature controlled fan, airflow from left to right
Height 88mm (3.5 inch)
Width 445 mm (17.5 inch)
Depth 240 mm (9.4 inch)
Rack mounting 19"
Size, packaged unit 57 x 50 x 21 cm (22.4 x 19.7 x 8.3 inch)
Weight, packaged unit 7.4 kg (16.3 lb)

NID2655 Rev. B7
Module Height 6 HE (266.7mm/10.5 in)

Module front Width 30mm /1.18'' (finger strips for EMC excluded)
Module Depth 175.2mm / 6.9'' (montage excluded)
208mm / 8.2'' (montage included)
Module Weight 0.5kg / 1.1 lb
All modules are based on Europe standard with 2x192-pool contact gear.
7.2 Management
Interfaces
• Command Line Interface
• Web Interface
• IP on SLIP on serial line
• IP on DLE on DTM link
• HTTP, Server with basic authentication
• FTP, Server and Client
• NTP, Server and Client
• SNMP Version 1, 3, MIB II
• Telnet, Server and Client
Control Ports
• Serial port 115kbps, RS232C, RJ45 Twisted pair
• Ethernet port 10/100Mbps, 100Base-T, RJ45 Twisted pair
Synchronization
• External Clock Reference 2048/1544 kHz, ITU-T G.703.10, SMB (One) / BNC (300) coaxial
• Output Synchronization Signal 2048/1544 kHz, SMB (One) / BNC (300) coaxial
7.3 Gigabit Ethernet (Builtin; Nimbra 300 series)
Interface Port for SFP-LC modules
Mapping 1000 Mbps Ethernet to IEEE 802.3 –2002, IEEE 802.3z,
ETSI ES 201 803-7
VLAN: IEEE 802.1Q
Priority: IEEE 802.1p
7.4 ASI (Builtin; Nimbra 340)
Interfaces 2 in + 2 out, BNC 75  to CENELEC EN 50083-9, ETSI TR 101 290,
ETSI ES 201 803-11
Mapping 2 - 200 Mbps MPEG-2 TS

NID2655 Rev. B7
7.5 4 x SONET/SDH SFP (Builtin; Nimbra 360)
Interfaces Four (4) ports for SFP-LC modules
Framing STS-3c (ANSI T1.105)/STM-1 (ITU-T G.707)9
Mapping STS-3c SPE /VC-4 Synchronous (ETSI ES 201 803-4)
7.6 HDSDI (Builtin; Nimbra 340HD)
Interfaces 2 in + 2 out (supporting 1 in + 1 out HD stream), BNC 75  to SMPTE 292M, ETSI ES
201 803-11
Mapping 1485 Mbps HD video formats
1483.5 Mbps HD video formats
7.7 Power
Duplicated power inputs
Input voltage -48 VDC, Max: -60V, Min: -40 V
Power consumption Max 300 W (One) / Max 80 W (300); Fully equipped
Typical 100-150 W (One) / 50-60 W (300)
Optional 115/230 VAC feeding via external power converters
(cord attached or rack mounted available)
7.8 Environment
Operating temperature 5 to 40 ºC (41 to 104 ºF)
(short term) -5 to 55 ºC (23 to 131 ºF)
Relative humidity 10% to 90% (non-condensing)
Storage temperature -40 to 70ºC (-40 to 156 ºF)
Storage humidity 10% to 90% (non-condensing)
7.9 Regulatory Compliance
Safety EN 60950, IEC 60950, UL 60950
Regulatory Markings CE-Mark 93/68/EEC
EMC-Directive 2004/108/EC
EMC ETSI EN 300 386
Electromagnetic Emissions FCC Part 15 Class A
9
Optionally STS-12c/STS-48c / STM-4/STM-16, requires firmware upgrade license

NID2655 Rev. B7
7.10 Network interface plugin modules
Physical No of
Interface Data Rate Port Specification
Medium ports
Connector: SFP LC
On-board 7.5 Gbps switching matrix
OC-48/STM-16 X-ADM Module 2488 Mbps SM fiber 2 Exchangeable opto modules for Short
Haul, Intermediate Range and Long
Haul
Connector: SC
Wavelength 1310 nm
Launched Power:
Min: -11.5 dBm
1 Gbps Optical Trunk Module SH 1000 Mbps SM fiber 1
Receiver sensitivity:
Min: –19 dBm
Receiver saturation:
Min: -3dBm
Connector: SC
Wavelength 1550 nm
Launched Power:
Min: 0 dBm
1 Gbps Optical Trunk Module LH 1000 Mbps SM fiber 1
Receiver sensitivity:
Min: -24 dBm
Receiver saturation:
Min: -3 dBm
Connector: SFP LC
2 x OC-12/STM-4 Trunk Module 622 Mbps SM fiber 2 Exchangeable opto modules for
Intermediate Range and Long Range
Connector: SFP
Exchangeable opto modules for Short
SM fiber / Haul, Intermediate Range and Long
4 x OC-3/STM-1 Trunk Module 155 Mbps 4
Coax Haul. LC connector.
Exchangeable module for STM-1e
(electrical with 1.0/2.3 connectors)
45 or 34
4 x DS3/E3 Trunk Module Coax 4 4 Rx, 4 Tx BNC 75 ohm
Mbps
SFP modules, available options:
STM-1 I-1.1/OC-3 SR-1 (MM.
1310nm)
MM, SM STM-1 S-1.1/OC-3 IR-1 (SM,1310nm)
4 x OC-3/STM-1 Access Module 155 Mbps fiber / 4
Coax STM-1 L-1.1/OC-3 LR-1 (SM,
1310nm)
STM-1 L-1.2/OC-3 LR-2 (SM,1550nm)
STM-1e (1.0 / 2.3 connector)
Twisted
E1 Access Module 2.048 Mbps 8 RJ48 120 ohm
pair
Twisted
T1 Access Module 1.544 Mbps 8 RJ48 100 ohm
pair
Twisted
Fast Ethernet Access Module 8p 10/100 Mbps 8 RJ45
pair
Gigabit Ethernet Access 1G MM, SM 1 SFP modules
fiber / GbE SX (500m) 850nm, MM, LC
twisted pair GbE LX (10km) 1310nm, SM, LC

NID2655 Rev. B7
GbE ZX (70km) 1550nm, SM, LC

1000BASE-T, RJ-45
SDI Video Access Module 270 Mbps Coax 4 (2 In, 2 Out) BNC 75 ohm
2-200 Mbps
ASI Transport Access Module Coax 4 (2 In, 2 Out) BNC 75 ohm
MPEG-2 TS
2-212 Mbps (8 in/out; configurable per port) BNC
8 x ASI Transport Access Module Coax 8
MPEG-2 TS 75 ohm
32,48,96,172
,44.1,88.2,
(8 in/out; configurable per port) BNC
8 x AES/EBU Access Module 176.4 kHz Coax 8
75 ohm
sampled
audio (AES3)
Table 1.Nimbra One/300 series Interfaces specification
7.11 Nimbra 360 BASE and GOLD clock options
Clock option BASIC GOLD
Phase Noise 10 Hz -85 dBc/Hz -110 dBc/Hz
100 Hz -100 dBc/Hz -120 dBc/Hz
1 kHz -110 dBc/Hz -130 dBc/Hz
Hold over stability 1 min < 1x10 -10
< 2x10-11
(after stabilization)
1h < 1x10-9 < 5x10-11
24 h < 5x10-9 < 1,5x10-10
Stabilization period for full hold over 1 day 7 days
compliance
Table 2. 10 MHz oscillator performance on Nimbra 360 Basic and Gold respectively
NPQ0013-DW01 Nimbra 360 Base Unit (Basic)
NPQ0013-DWG1 Nimbra 360 Base Unit, LPN oscillator option (Gold)

NID2655 Rev. B7
7.12 Ordering information
7.12.1 Nimbra One

NPQ0007-0001 Nimbra One Base Unit
NPS0006-0001 Control Module
NPA0005-0006 Blind panel
NPA0010-0001 -48 VDC Filter Unit
NPA0002-0030 Nimbra One Power Cable
NPA0015-0001 Fan Tray for Nimbra One
NPA0006-0001 Control Module Serial Adapter (for Nimbra One)
NPS0022-XS31 OC-48/STM-16 X-ADM Module
NPS0019-X001 2 x OC-12/STM-4 Trunk Module
NPS0009-XS31 4 x OC-3/STM-1 Trunk Module (optional FEC support)
NPS0009-XS32 4 x OC-3/STM-1 Trunk Module (optional TT support)
NPS0027-X001 4 x DS3/E3 Trunk Module
NIP1133 1 Gbps Optical Trunk Module SH (A)
NIP1134 1 Gbps Optical Trunk Module SH (B)
NIP1238 1 Gbps Optical Trunk Module LH (A)
NIP1239 1 Gbps Optical Trunk Module LH (B)
NPS0029-A001 E1 Access Module (A)
NPS0029-B001 E1 Access Module (B)
NPS0030-A001 T1 Access Module (A)
NPS0030-B001 T1 Access Module (B)
NPS0004-A001 ASI Transport Access Module (A)
NPS0004-B001 ASI Transport Access Module (B)
NPS0005-A001 SDI Video Access Module (A)`
NPS0005-B001 SDI Video Access Module (B)
NPS0010-X001 Gigabit Ethernet Access Module
NPS0017-X001 Fast Ethernet Access Module
NPS0020-XS31 4 x OC-3/STM-1 Access Module
NPS0031-X001 8 x ASI Transport Access Module
NPS0050-X001 8 x AES/EBU Access Module
7.12.2 Nimbra 300 Series

NPQ0011-3W01 Nimbra 340 Base Unit
NPQ0011-HW01 Nimbra 340-HD Base Unit
NPQ0013-DW01 Nimbra 360 Base Unit
NPQ0013-DWG1 Nimbra 360 Base Unit, LPN oscillator option
NPM0016-3004 4 x OC-12/STM-4 firmware for Nimbra 360
NPM0016-3016 2 x OC-48/STM-16 firmware for Nimbra 360
NPM0017-36T1 Time Transfer firmware for Nimbra 360
NPA0031-3401 AC/DC Converter for Nimbra 300 series
NPA0030-3001 Blind Panel
NPA0032-0001 Mounting kit for 19" mount of Nimbra 3xx
NPA0028-0030 Power Cable for Nimbra 3xx, -48VDC, L=3m
NPS0031-3001 8 x ASI Transport Access Module
NPS0004-3001 ASI Transport Access Module
NPS0005-3001 SDI Video Access Module
NPS0050-3001 8 x AES/EBU Access Module
NPS0010-3001 Gigabit Ethernet Access Module
NPS0017-3001 Fast Ethernet Access Module
NPS0020-3S31 4 x OC-3/STM-1 Access Module
NPS0029-3001 E1 Access Module
NPS0030-3001 T1 Access Module
NPS0009-3S31 4 x OC-3/STM-1 Trunk Module (optional FEC support)
NPS0009-3S32 4 x OC-3/STM-1 Trunk Module (optional TT support)
NPS0019-3001 2 x OC-12/STM-4 Trunk Module
NPS0022-3S31 OC-48/STM-16 X-ADM Module

NID2655 Rev. B7
NPS0027-3001 4 x DS3/E3 Trunk Module

NPS0028-3001 1Gbps Optical Trunk Module SH
NPS0028-3L01 1Gbps Optical Trunk Module LH
8 User Documents
1. Element Manager User's Manual, Nimbra One, Nimbra 300 series (NID601)
2. Nimbra One, Installation and Maintenance Manual (NID 743)
3. Nimbra 300 series, Installation and Maintenance Manual (NID2473)
4. System Description - Nimbra Platform (NID 1998)
5. Service Provisioning using SNMP (NID2062)
6. Alarm Survey Nimbra One/340 (NID2004)
7. Synchronization Overview (NID2568)
9 Acronyms and abbreviations
Throughout the text in this document, the following abbreviations apply:
AES/EBU Audio Engineers Society / European Broadcasting Union
ASI Asynchronous Serial Interface
CLI Command Line Interface
CWDM Coarse Wavelength Division Multiplexing
DCN Data Communications Network
DLE DTM LAN Emulation
DSYP DTM Synchronization Protocol
DTM Dynamic synchronous Transfer Mode
DWDM Dense Wavelength Division Multiplexing
E1, E2, E3, E4 European PDH multiplex levels with transfer speeds of 2, 8, 34 and 140 Mb/s respectively
ETS Ethernet Transport Service
FEC Forward Error Correction
GUI Graphical User Interface
ITS Isochronous Transport Service
OC-N Optical Carrier level N
PDH Plesiochronous Digital Hierarchy, a way to multiplex several telephony trunks into one bit-stream
PLL Phase Locked Loop
RX Receive
SDH Synchronous Digital Hierarchy
SDI Serial Digital Interface
SFP Small Formfactor Pluggable
SNMP Simple Network Management Protocol
SOF Start of Frame
SONET Synchronous Optical Network
SPE Synchronous Payload Envelope (SONET)
STM-N Synchronous Transport Module level N (SDH)
STS-N Synchronous Transport Signal level N (SONET)
STS-Nc Concatenated Synchronous Transport Signal level N (SONET)
T1, T2, T3 American PDH multiplex levels with transfer speeds of 1.5, 6 and 45 Mb/s respectively
TT Time Transfer

NID2655 Rev. B7
TX Transmit
VC Virtual Container (SDH)
VC-4-Xc Virtual Container level 4 concatenated (SDH)
VT Virtual Tributary (SONET)

NID2655 Rev. B7
Appendix 1 Typical transit delays
Delay type Transit type [from – to] Delay [ms]

Trunk/Switch Access → 1/2/4-port Trunk 0,2
1-port Trunk → Access 0
2/4-port trunk → Access 0,2
1-port trunk → 1/2/4-port trunk 0,2
2/4-port Trunk → 1/2/4-port Trunk (different boards) 0,35
2/4-port Trunk → 2/4-port Trunk (same board) 0,2
Access E1/T1 egress 0,38
SDI egress 0,25
ASI egress 5 @ 8 Mbps
AES/EBU egress 0.67 @ 48 kHz
All accesses ingress 0
Table 1. Typical transit delays for Nimbra One/300 series units

The table above gives empirically measured switch delays, or typical delays. The delay through a Nimbra
One/300 series switch is fixed, but can differ as described in the product description. With the table above it
should be possible to calculate a typical end to end delay (except for fiber transit delay) by adding the delays
of each each switch, according to the transit type. The actual delay will differ due to that each element has a
more complex delay dependence involving relative phases between nodes etc, but the sum of the typical
values should give approximately correct values for a chain of links.
The ASI and AES/EBU accesses has an egress delay that is inversely proportional to the service bandwidth.
I.e the ASI i/f with a delay of about 5 ms @ 8 Mbps has a delay of about 2.5 ms @ 16 Mbps and so on.
The delay of the Ethernet interfaces are not analyzed but expected to be around 0 on a ms scale.

NID2655 Rev. B7

Product Description

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Product Description

Hochgeladen von

Copyright:

Verfügbare Formate

Commercial in Confidence

Product Description Nimbra One/300 series 1(79) 2009-04-15

Product Description Nimbra One/300 series 2(79) 2009-04-15

2 NIMBRA ONE/300 SERIES SYSTEM STRUCTURE................................................................................................................7

3 TRUNK AND ACCESS INTERFACES............................................................................................................................. ........22

5 SERVICE PROVISIONING.................................................................................................................................................... ...64

6 NETWORK RESTORATION ............................................................................................................................... ....................68

Product Description Nimbra One/300 series 3(79) 2009-04-15

8 USER DOCUMENTS............................................................................................................................................................... .77

9 ACRONYMS AND ABBREVIATIONS.............................................................................................................................. ........77

Product Description Nimbra One/300 series 4(79) 2009-04-15

Product Description Nimbra One/300 series 5(79) 2009-04-15

Unit/Module Short description

Nimbra One An 8-slot modular subrack, with redundant power feeding

A 2-slot modular subrack, with redundant power feeding

2 x OC-12/STM-4 Trunk Module 2-port STM-4c/OC-12c trunk interface

4 x OC-3/STM-1 Trunk Module 4-port STM-1/OC-3c trunk interface

4 x DS3/E3 Trunk Module 4-port DS3/E3 trunk interface

ASI Transport Access Module 4 (2 RX +2 TX) ports DVB-ASI

8 x ASI Transport Access Module 8 ports DVB-ASI, each configurable as IN or OUT

8 x AES/EBU Access Module 8 AES/EBU ports, each configurable as IN or OUT

Table 1.List of Nimbra One/300 series Units and Modules

Product Description Nimbra One/300 series 6(79) 2009-04-15

Value Added Services

Figure 2. The Nimbra System Structure

Product Description Nimbra One/300 series 7(79) 2009-04-15

Figure 3. Nimbra One Base Unit

Product Description Nimbra One/300 series 8(79) 2009-04-15

Product Description Nimbra One/300 series 9(79) 2009-04-15

These parts will be described in detail in the following chapters.

Product Description Nimbra One/300 series 10(79) 2009-04-15

Interface Board Node Controller

Figure 1. Software structure in the Nimbra One/300 series

Product Description Nimbra One/300 series 11(79) 2009-04-15

2.5.1 Internal Switch Module Overview, Nimbra One

2.5.1.1 Backplane Structure

Product Description Nimbra One/300 series 12(79) 2009-04-15

2.5.2 Internal Switch Module Overview, Nimbra 300 series

Product Description Nimbra One/300 series 13(79) 2009-04-15

Built-in External Slot

2.5.3 Channel capacities

Product Description Nimbra One/300 series 14(79) 2009-04-15

2.5.4 Switch transit delay

2.5.4.1 Switch configuration

2.5.4.2 Relative phase

2.5.4.3 Initialization effects

Product Description Nimbra One/300 series 15(79) 2009-04-15

2.5.4.4 Time slot switching

2.5.5 Network/Node Synchronization

2.5.6 Time Transfer functionality (Nimbra 360)

Product Description Nimbra One/300 series 16(79) 2009-04-15

2.5.8 Power Supply

2.5.8.1 Power consumption

2.5.9 Node Controller function

2.5.9.1 Real Time Clock

Product Description Nimbra One/300 series 17(79) 2009-04-15

2.5.9.2 Temperature monitoring

2.5.9.4 Status LED

2.5.9.5 External Sync ports

2.5.9.6 Time Transfer ports (Nimbra 360)

Time Transfer mode:

Product Description Nimbra One/300 series 18(79) 2009-04-15

STM-1 I-1.1/OC-3 SR-1 (MM. 1310nm)