21 Td-Ddgbe N

TM-Series
Technical Description
Double DGbE xWDM, Basic Unit (TPDDGBE R1)
Rev N, 2009-11-30
Technical Description
Quad MultiRate Transponder (TPQMR R1, R2)
Rev S, 2009-02-10
IN COMMERCIAL CONFIDENCE
DOUBLE DUAL GBE TRANSPONDER
Date: Doc. number: Rev: Page
© Transmode 2009-11-30 TD-TPDDGBE N 2 (39)
Table of Content
1 General...............................................................................................................3
1.1 In commercial confidence ...............................................................................................3
1.2 Document Revision History.............................................................................................3
2 Functional Description........................................................................................4
2.1 General ...........................................................................................................................4
2.2 TPDDGBE.......................................................................................................................5
3 Applications ........................................................................................................7
3.1 CWDM networking ..........................................................................................................7
3.2 DWDM networking ..........................................................................................................8
4 Functionality .......................................................................................................9
4.1 Line protection ................................................................................................................9
4.2 Loop-back .....................................................................................................................10
4.3 Optical Interfaces ..........................................................................................................10
4.4 GbE broadcast ..............................................................................................................11
4.5 Client configuration. ......................................................................................................12
4.6 Synchronization ............................................................................................................12
4.7 Signal format on xWDM layer .......................................................................................12
4.8 Performance monitoring................................................................................................12
4.9 GbE channel utilization .................................................................................................13
4.10 Management channel ...................................................................................................13
4.11 Monitor points ...............................................................................................................13
4.12 Alarms...........................................................................................................................13
4.13 Product data..................................................................................................................14
4.14 Remote inventory..........................................................................................................14
4.15 Consequent actions ......................................................................................................15
4.16 Trail Trace.....................................................................................................................16
5 Networking considerations ...............................................................................17
5.1 Protected links ..............................................................................................................17
5.2 Using TPQMR as regenerator transponder...................................................................19
6 Setting up TPDDGBE via ENM GUI.................................................................20
6.1 ENM Frame Overview...................................................................................................21
6.2 Verbose mode...............................................................................................................22
6.3 Equipment Frame .........................................................................................................23
6.4 NE configurations..........................................................................................................24
6.5 TPDDGBE in Transponder mode (“tpDDGbE”).............................................................25
6.5.1 Equipment view, unit and interface settings ..................................................................25
6.5.2 “Inventory” tab...............................................................................................................26
6.5.3 “Line” tab.......................................................................................................................27
6.5.4 “Line PM” tab ................................................................................................................28
6.5.5 “PPP” tab ......................................................................................................................29
6.5.6 “Client” tab ....................................................................................................................30
6.5.7 “Protection” tab .............................................................................................................31
6.6 TPDDGBE in Regenerator mode (”tpDDbER”) .............................................................32
6.6.1 “Inventory” tab...............................................................................................................33
6.6.2 “Line” tab.......................................................................................................................34
7 Mechanical Layout ...........................................................................................35
7.1 Transponder configuration ............................................................................................36
7.2 Regenerator configuration.............................................................................................37
8 Technical data ..................................................................................................38
Transmode Systems AB © 2009 Transmode Systems AB

Box 42114 All rights reserved. No part of this document
SE-126 14 Stockholm may be reproduced without written Home page: www.transmode.com
SWEDEN permission of the copyright holder
1 GENERAL
The specifications and information within this manual are subject to change without further
notice. All statements, information and recommendations are believed to be accurate but
are presented without warranty of any kind. Users must take full responsibility for their
application of any products.
In no event shall Transmode Systems AB be liable for any indirect, special, consequential
or incidental damages, including, without limitation, lost profits or loss or damage to data
arising from the use or inability to use this manual, even if Transmode or its suppliers have
been advised of the possibility of such damages.
1.1 In commercial confidence

The manual is provided in commercial confidence and shall be treated as such.
1.2 Document Revision History
Revision Date Description of changes

A 2005-03-18 Creation
B 2005-06-30 - Transition to new Transmode format.
(A3.2 release) - Introduction of new overlay with clarified text information.
- Addition of cascade Transponder functionality
- Support for 100km CWDM SFP’s
C 2005-10-31 A4.0 content; DWDM SPF support
D 2005-12-20 Updated with A4.1 content. Line protection.
E 2006-04-20 Enhanced information in section 8
F 2006-06-20 TRX10006 has better RX sensitivity. See chapter 8
G 2006-08-20 - More detailed info on tables with optical data.
- Addition of ENM GUI information
- Improved chapter on management channels
H 2007-04-27 Updated with release 8.0 content;
- low band CWDM SFP’s
- support for 100Base-T
I 2007-12-21 Update with rel 10.0 content; new DWDM SFP
Removal of channel mapping on MDU’s.
J 2008-05-28 Change of logotype
Change of structure and enhanced information.
K 2009-01-16 Corrected optical data on TRX100014/xx
L 2009-02-10 Changed front page
M 2009-06-15 Removal of technical data of transceivers in chapter 8. See
Dimensioning Guidelines in System Manual for details!
New table added showing supported transceivers.
N 2009-11-30 Updated power consumption values in chapter 8

2 FUNCTIONAL DESCRIPTION
2.1 General
WDM is an analogue technique and requires a controlled environment for error free
transmission. Transponders and Muxponders serve as buffers between the “client layer”
and the “WDM domain”. As a result, client equipment of different types (e.g. SDH, IP
routers) and from different vendors can be connected to the Transmode network without
any impact on the transmission path through the network.
A Transponder/Muxponder also enables encapsulation of the client signal into a digital

wrapper, i.e. extra bytes are added to the client signal at the client ingress point and
removed at the client egress point. These OH-bytes can be used for a number of features,
such as
- Introduction of quality check of the WDM signal enabling Performance Management

(PM) as well as Fault Management (FM) in the transmission domain.
- Insertion of management channels that are used to connect to other nodes in the
network for management purposes. Also called “Embedded” or “In-band”
management channels.
- Insertion of coding that detects and corrects bit errors; Forward Error Correction
(FEC). This is typically needed for long-haul transport of 10Gb/s signals since it
gives the signal similar transmission performance as a 2.5Gb/s signal in an amplified
network.
- Insertion of path information that can be used to validate the connection.
- Security features like Automatic Laser Shut-down (ALS) that shuts down the laser
upon a fiber cut.

2.2 TPDDGBE
Figure 1: Double DGbE Transponder
The TPDDGBE is a unit having two individual Dual GbE Transponder functions on the
same board. Each of the two Transponders electrically multiplexes two GbE-signals onto
one wavelength channel having a line rate of 2,488Gb/s.
Performance Data is collected from client and line interfaces, embedded management
channels provides easy remote management connectivity and loop-back functionalities can
be used for faultfinding etc. PM-data is presented according to G.826 via the node or
network manager
Pluggable Transceivers (SFP’s) are used on both client and line interfaces enabling
configurations that exact match current and future needs.
The TPDDGBE can be used in multiple configurations;
1. As two separate Transponder functions, each aggregating 2x GbE-signals where the

line signal can be singular or duplicated for line protection (tpDDGbE).
2. As four separate regenerator functions (tpDDGbER).
At start-up of the unit, it is loaded with one of two SW-images giving the above two
functions. The MIB-name and GUI will change accordingly.
The TPDDGBE has an on-board microprocessor that contains the unit SW for managing
the unit. In stand-alone configuration it will also contain the node manager SW, TM-ENM.
In regenerator mode all eight ports (client and line ports) are equipped with CWDM/DWDM
SFP’s having the interface performance needed to bridge the links eastbound and
westbound. As an example, it is possible to use CWDM SFP’s facing west and DWDM
SFP’s facing east to make a CWDM to DWDM translation.

The TPDDGBE uses an internal clock oscillator to generate the outgoing data signals.
There is thus no jitter accumulation as for units using through-timing. Consequently a
higher number of NE’s can be cascaded.
The selection between normal transponder mode and regenerator mode is done when the
TPDDGBE is inserted into a chassis/subrack. The TPDDGBE must be taken out of service
if this mode is to be changed.
In CU-less applications, e.g. in a TM-101/-102 chassis, a TPDDGBE will by default set into
transponder mode.

3 APPLICATIONS
3.1 CWDM networking

The TPDDGBE can be used in CWDM or DWDM networking by using CWDM or DWDM
SFP transceivers towards any of the available CWDM/DWDM MDU’s and/or AD-filters.
A typical application for the TPDDGBE is broadband networks for collection of multiple
GbE-signals in e.g. ADSL/DSLAM and Triple-Play networks.
Figure 2: Single-fiber CWDM networking example
The figure shows an example point-to-point CWDM network where the TPDDGBE is used
at the end nodes as well as a regenerator function in an intermediate node.
Up to 8 channels can be established in the single-fiber configuration giving 16 GbE-

channels per single-fiber. The example above shows a setup using 4 channels.
CWDM networking solutions on fiber-pair configurations is also supported. See

“Dimensioning Guidelines” within the System Manual for more details on configuration
alternatives and losses through the optical components.

3.2 DWDM networking

The usage of pluggable transceivers (SFPs) enables the TPDDGBE to be used in either
CWDM or DWDM applications.
The below example shows a configuration where the TPDDGBE is used in a CWDM
collector network and relayed through an amplified DWDM link up to a head-end node
where all GbE-signals are extracted.
Figure 3: Combined CWDM and DWDM networking example
See “Dimensioning Guidelines” for more information on amplified DWDM networks.

4 FUNCTIONALITY
4.1 Line protection

The TPDDGBE can be set into a line protection mode by adding yet another line
transceiver (SFP). This protection alternative will not introduce any losses in the optical
domain since the switching is performed electrically within the unit.
Figure 4 shows a simplified network example that shows what parameters and criteria’s
that are used as base for switching.
Figure 4: Line protection
Protection switch is generated upon “Loss Of Signal”, “Loss Of Frame” and

“FarEndLineError”

4.2 Loop-back
Each TPDDGBE function can be set in loop-back mode. The loop-back is of remote client
loop-back type, i.e. the client signal is looped as shown in the figure. Loop-back is set per
client signal independently. The client signal is transmitted to the Client Tx interface and
looped back towards the line. The incoming GbE signal is not transported out from the unit.
The wrapper on the line side is not affected by this loop-back.
This loop-back function can be used to e.g. validate a connection from near-end to hand-
over to a client system.
Client Line
Figure 5: Loop-back
Note! Loop between two client ports using external patch cords is not supported when
using electrical SFP’s (TRX1000025)
4.3 Optical Interfaces

The following GbE transceivers are provided on the client side:
• MM/850nm SFP
• SM/1310nm SFP
• Electrical SFP for 1000BASE-T
• Electrical SFP for 100BASE-T
On the WDM side, different variants of transceiver plug-in modules can be selected with
different range characteristics, i.e.
• CWDM 40km@2.5Gb/s
• DWDM 100km@2.5Gb/s
• DWDM 180km@2.5Gb/s
See chapter 8 for list of supported transceivers and “Dimensioning Guidelines” within the
System Manual for details on optical data.

4.4 GbE broadcast

The TPDDGBE can also be used in IP broadcast networks, i.e. where the GbE signals are
transmitted uni-directional. This is achieved by activating the loop-back function on the
client side. This loop-back acts as a “drop and continue” function giving the two received
GbE-signals to be transmitted at the client ports as well as looping them back on the
transmit direction of the line side.
The line protection feature enables protected broadcast configurations. The figure below
shows a protected broadcast example on a single-fiber configuration. The second half of
the TPDDGBE units is not used in the example, but could be used for bi-directional GbE
traffic to collect IP-traffic from e.g. DSLAM networks. It is thus possible to combine a
broadcast and GbE collection network in this configuration.
Figure 6: Protected broadcast configuration

Note that the embedded management channels will not operate in broadcast mode.
Note that electrical SFP’s are not currently supported in broadcast mode.
Note that the protection is revertive, i.e. switch-back to default direction is done when this is
comes back into operation. This is required to avoid “isolated” islands. See I&C manual for
more details.
In TNM the right path will always be shown with a line and the left path with a dotted line.
When using protection in broadcast mode it is important to understand that if performing a

forced switch to left- or right the traffic might not pass to the other satellite nodes in the ring
if not the same forced switch is done on the rest of the members in the broadcast ring.

4.5 Client configuration.

Each Transponder function on the TPDDGBE is configured via the management system for
either:
• GbE client 1 only, i.e. any signal on GbE client 2 is blocked

• GbE client 2 only, i.e. any signal on GbE client 1 is blocked
• 2x GbE, i.e. both client 1 and client 2 are opened
4.6 Synchronization
From client input to xWDM interface: An internal synch source generates the transmitted
clock rate.
From xWDM to client interfaces: An internal synch source generates the transmitted clock
rate.
All outgoing signals are thus re-timed using an internal sync source.
4.7 Signal format on xWDM layer

The WDM signal format is a Transmode proprietary signal. The line rate is 2,488Gb/s, i.e.
equal to STM-16/OC-48 but not using the STM-16/OC-48 framing format.
4.8 Performance monitoring

Performance Monitoring (PM) is provided on the incoming and outgoing CWDM signals as
well as incoming and outgoing client signals.
The PM data is retrieved every 15min/24h and presented according to the G.784/G.826
standard:
• ES – Errored Seconds
• SES – Severe Errored Seconds.
• BBE – Background Block Errors
• UAS – Unavailable Second
PM on client signals is imitating ITU-T G.826 standard based on CRC and 8B/10B coding
errors.
PM on line signals is imitating ITU-T G.826 standard based on CRC errors.

4.9 GbE channel utilization

The utilization of each client port is monitored and the effective usage of the GbE capacity
is presented in % of the max capacity.
This is retrieved every 15min/24h.
4.10 Management channel

An internal management channel is added to the traffic channel via special OH bytes. This
channel is used by node manager TN-ENM and network manager Transmode TNM to
reach and manage remote nodes within the network.
The TPDDGBE unit supports two management channels (DCC-channels). In Transponder

mode both line ports carries DCC channels. If line protection is activated, the same DCC-
channels are copied to both working and protect interfaces.
When the TPDDGBE is set into regenerator mode the regen transponder no 4 (R4 on front)
carries the DCC channels (i.e. ports 13 - 14 and 15 - 16). This is a fixed setting so this
transponder function shall be used first to ensure management access.
4.11 Monitor points

A number of analogue data can be retrieved from the unit:
• Board temperature: Given in Centigrade

• Received optical power level
• Laser Bias current
• Optical output power
• Laser temperature: only on DWDM SFP’s.
They are also used to generate indications based upon defined thresholds. Actual
parameters will vary between different SFP types.
4.12 Alarms
Any generated alarms are collected by the Control Unit and accessible via the node
manager TM-EMN or network manager Transmode TNM. The status LED (STS-LED) on
the board front indicates the severity of the active alarms. See chapter 7.
See “Troubleshooting guide” in volume “Operation & Commissioning” of the System

Manual for listing of alarms and procedures to resolve them.

4.13 Product data

All boards/units within a TM-3000/-301/-101 Network Element have unit related information
stored in non-volatile memory banks. This information is stored at production and is
required for administration and startup of the boards.
The information is divided into three main groups:
• Environmental data - Contains data, which is read and used without knowledge of
production data version
• Generic board data - Contains administrative data, which is included on all boards,
both active and passive.
• Specific board data - Data needed for proper board operation.
Some alarms are based on the presence of this information:
• “Vital Product Data Missing”: Information in the board data memory bank that is vital to
manage the unit is missing. This alarm is classified as “critical” and may require board
replacement.
• “Non-vital Product Data Missing”: Information in the board data memory bank that is
not vital to manage the unit is missing. This alarm is classified as “minor”.
See System Manual Volume C, Operation & Maintenance for further details.
4.14 Remote inventory

Specific inventory data can be retrieved locally or remotely. The information provided is:
• Unit name
• Unit HW Product number
• HW revision
• Unit SW product number
• SW revision
• Firmware revision
• Unit Manufacturer
• Unit serial number
Data can also be retrieved from the SFP’s giving information about
• vendor name
• serial number
• wavelength
• interface type MM, SM or TP (Twisted Pair for 1000Base-T)
• distance type

4.15 Consequent actions
Figure 7: Consequent actions per DGBE-function
Loss of input client signal:
• WDM side: the affected GbE signal will generate idle signaling. Since the management
channel is carried on the WDM signal, the objective is to keep the WDM output signal
alive regardless of status of the input signals on the client side.
• Near-end client output port will not be affected.
• On the far-end output port, the affected GbE signal will be shut down or be forced on
(selectable).
In regenerator mode AIS signalling will be generated downstream upon an uplink failure.
This AIS indication will render a protection switch and the downstream end node. All units
receiving the AIS signal will generate an alarm.

Loss of line signal:
• Output near-end client ports: Both are shut down or forced on (selectable). The latter
will give idle data out.
• Output near-end line port: ALS scheme or forced on (selectable).
• Output far-end client ports: Dependent on consequent action on incoming WDM signal
to far-end node. If WDM signal active, no change on client outputs. If WDM signal shut
down, then outputs either shuts down or forced on (selectable)
4.16 Trail Trace

A Trail Trace functionality enables insertion of a value (16 bytes) in the outgoing line signal
and setting the same value as the expected Trail Trace
in the far end receiving WDM interface. This functionality can be used to ease the
installation procedures by providing a quick validation of an optical wavelength channel
setup.
Trail Trace is inserted in both line ports.

5 NETWORKING CONSIDERATIONS
5.1 Protected links

The DCN solution must be planned carefully for protected networks since isolated islands
may occur upon a link failure. These isolated islands can occur when intermediate
regenerator sites are used in-between the end nodes.
For links without intermediate regeneration sites there is no risk for isolated islands. The
management traffic can thus follow the traffic as it is switched. This configuration is set via
“Wrapper mode” (see chapter 6.5.7 on page 31) and via the selection “Follow traffic”. This
means that the management traffic channel will follow the traffic upon a protection switch.
For links with intermediate regeneration sites, the “Wrapper mode” is recommended to be
set into “Fixed to default”. This means that the management traffic channel will continue to
be transmitted on the default line ports (see chapter 7.1) regardless of protection switching.
Figure 8: Example network; protected with intermediate regenerator nodes
The above figure show an example CWDM network where one of the TPDDGBE functions
is used. Management access is only done in node A. The figure shows that the “default”
Tx-Rx line ports 13 – 14 are used for the upper path, and the other Tx-Rx ports 9 – 10 are
used for the lower path. Also note that the ports 13 – 14 and 15 – 16 are used on the
TPDDGBE units that are in regenerator mode. This is according to the statement in chapter
4.10.
The Wrapper mode is set to “Fixed to default” in Node A and Node C. This means that the
management traffic will be fixed to ports 13-14 regardless of the protection switch setting.
When the network is set into operation it is thus important to activate the upper path first so
that this becomes the “active” path and the other is “stand-by”. This will ensure
management connectivity to nodes A – B1 – C.

Note! There is no wrapper connection established on the lower path. There is thus no
management connection to node B2. The quality status of the lower (stand-by) path is
however fully monitored in nodes A and C and any traffic affecting faults will generate a
degraded service indication.
Management access to the nodes in the lower path can be achieved using local DCN
access if available. Alternatively the second TPDDGBE function can be used. This second
alternative is described below.
Figure 9: Example network; protected with intermediate regenerator nodes, step 2
The default Tx-Rx ports on the second TPDDGBE function are ports 15 & 16. These are
connected to the lower path. As on the first TPDDGBE function, the wrapper mode is set to
“Fixed to default” in Node A and Node C.
With this setup the first TPDDGBE function establishes a fixed management channel on
the upper path (A – B1 – C) and the second TPDDGBE function over the lower path
(A – B1 – C). We now have full management access to all nodes in the network regardless
of protection switching.
Note! There is no connection between default Tx-Rx ports and protection settings. These
two are set independently. In the above network example it is recommended to use the
same paths as “active” and “stand-by”. On the first TPDDGBE function the active path shall
be set to ports 13 – 14 and on the second to ports 11 – 12.
If a fiber break occurs between node A and node B1 it is still possible to get management
access to node B1 via A – B2 – C – B1. There are thus no isolated islands as would have
been the case if both TPDDGBE functions have been setup in the exact same way.
It is thus equally important to plan the DCN network as the traffic connections in a network
to get a secure and proper behaviour.

5.2 Using TPQMR as regenerator transponder

In some cases a TPQMR might be used as a regenerator transponder.
If using TPDDGBEs with one or more TPQMRs between, see example above, the laser
mode must be set to “on” on the TPDDGBE units. This is done in the following way:
GUI Double-click on Actual Board Æ Line tab Æ Name List-box Æ Laser

Mode
CLI ::wdm::if Æ wanted port Æ set laserMode
Do not forget to perform the same settings in the other end as well.

6 SETTING UP TPDDGBE VIA ENM GUI

After login to the ENM using a web browser, the initial view is the Equipment view. The
appearance will differ depending on what chassis that is used. The figure below shows the
view that is presented when logging into a TM-3000.
Figure 10: ENM GUI
The window has several clickable objects as well as menu links. A certain configuration
window or information object can be reached via menu links or via clickable objects. Some
buttons will change color to reflect alarm status (e.g. fan and power buttons). This will be
explained in more detail in the sections that follow.

6.1 ENM Frame Overview

There are three main frames through which the node can be managed.
The “left frame” is a static frame that is always seen in the browser. Pressing on the
equipment link will bring the user back to the starting point.
The “top frame” is dynamically updated and shows the number of alarms and the highest
severity among them.
The biggest frame is the “equipment frame”. This frame is changed according to the
choices made on all the three frames.
See the figure below to see a split view of these three frames.
Figure 11: ENM GUI Split View

6.2 Verbose mode

The browser can be set in two modes where different depth of information is presented.
This setting is done via the “Browser settings” that is shown on the menu to the left.
For normal operation of a NE the browser shall be set in Verbose mode “off”. This will
present the most relevant information and settings and provide a more compact display of
the different windows.
Figure 12: Verbose Mode
The default setting is “Verbose mode” in “off” mode. To activate verbose mode, click in the
tic-box and press “Apply”. Some configurations can only be done with the verbose mode
activated. This will vary from unit to unit.
When needed configurations have been done it is recommended to reset the verbose
mode to “off”.

6.3 Equipment Frame

The equipment frame seen in the figure below points out interesting information and areas
with information on what happens when clicking on them.
Figure 13: Equipment Frame
The “Chassis tab” indicates the chassis type. If several chassis are connected into a single
NE entity, the included chassis’ will be found under separate tabs. A Control Unit (CU) is
required to connect multiple chassis into one NE. It is thus not possible to combine multiple
TM-101 chassis in this way since no CU is used in this configuration.
The “Save configuration status” icon changes color when there are unsaved changes in the
configuration.
A warning window will be presented upon logout from the ENM if there are unsaved
changes. It is then possible to save, leave unsaved or cancel the logout via this window.
All un-saved configurations will be lost if the node is re-booted. It is possible to log-in again
and do the save command. All unsaved configurations and settings will however be lost
upon a re-boot of the unit.
For each of the Traffic Units (TU’s) there is an area that can be clicked on to show the
active alarms for that unit. To configure a TU there is an empty area that can be clicked on
and a board wizard will pop up.

6.4 NE configurations
When a node is to be commissioned the first time a number of configuration steps must be
taken on both NE and board level. To ease this process a Node and Board Wizard is
provided. The wizards present a series of pages where configuration data is entered. Every
page has a help text where all parameters are described.
The NE related configuration is done via the “Node Installation Wizard” and is activated via
the menu item “Getting started” to the left. The following data is entered:
• DNS and Node Name
• IP address
• Default Gateway
• Date and time (NTP)
• SNMP Traps
• Passwords
• Radius and Tacacs+ settings
• Backup upload settings
• Backup/Restart settings
The entered values are saved and activated after completion of the wizard when the
“finish” button is pressed. The above parameters can also be set “manually” via the
corresponding configuration windows.
The board/unit related settings can be done via the “Board Wizard”. The “Board Wizard”
will prompt for different parameters depending on the unit type.
For TM-3000 and TM-301 chassis the “Board Wizard” will include all installed units in the
card cage.
Some pages have a series of buttons at the bottom.
“Refresh”: Updates all values on the page.
“Apply”: Performed changes are activated (note that the change is not saved)
“Multi Set”: Enables setting of multiple parameters that are related and relevant
“View Table”: All related and relevant data is listed in table format
“Help”: Opens an information window on parameters
For additional information on how to commission on node and network level, see the
“Installation & Commissioning” sections within the System Manual.

6.5 TPDDGBE in Transponder mode (“tpDDGbE”)
6.5.1 Equipment view, unit and interface settings
When clicking on one of the interfaces on the TPDDGBE unit in the equipment view, the
following window is presented.
A number of tabs enable access to information and entering of data related to both
unit/board and interfaces. The tabs will differ between different units. The above figure
shows the tabs that are presented for the TPDDGBE.
In the above example the first tab is named “tpDDGbE:1:4”. This means that this is a
TPDDGBE Transponder placed in subrack no1 and in slot no 4.
The nomenclature is
“MIB name”:”subrack no”:”slot no”.
This is used generally for all units.
Interfaces are named in a similar way.

“interface type”:”slot no”:”Tx port – Rx port”
where “interface type” is either “wdm” for line interfaces or “client” for client interfaces.

6.5.2 “Inventory” tab
The figure shows an example inventory screen dump from the ENM GUI.
Note that this unit also has a “Firmware revision”. This parameter is only relevant for units
with FPGA’s (programmable arrays).
Inventory information on the optical transceivers is found under the tabs “Line” and “Client”.

6.5.3 “Line” tab
Under the tabs “Line” and “Client” information in optical parameters can be found, alarm
thresholds can be set and inventory data on the transceivers is shown etc.
The TPDDGBE in Transponder mode can be configured for three “Distribution roles”:
• “terminalMultiplexor”
• “broadcastHub”
• “broadcastSatellite”
The “terminalMultiplexor” role is used for standard bi-directional links. The broadcast roles
are used in uni-directional broadcast networks (see chapter 4.4).
Press the “Help” button for more information on the configurable items.

6.5.4 “Line PM” tab
Below is an example screen dump from the ENM GUI showing the PM data presented via
the tab “Line PM”. A similar tab for the client signals (“Client PM”) provides PM data for
each individual client interface. Thresholds can be set to activate alarms.

6.5.5 “PPP” tab
The “PPP” tab is used to setup the management communication channel using the OH-
bytes bytes within the line signal. See “Designing DCN Network Plans” and “Configuration
Guide” within the Installation & Commissioning volume for more details on how to establish
PPP-links.

6.5.6 “Client” tab
The drop-down menu at “Name” is used to select which client signal to be viewed. The
nomenclature used is:
client:”subrack no”:”slot position”:”Tx port number” – “Rx port number”
Each of the four client signals can be viewed and configured.

6.5.7 “Protection” tab
The “protection” tab is used to activate the line protection functionality (see chapter 4.1 and
chapter 7).
The DCN solution must be planned carefully for protected networks since isolated islands
may occur upon a link failure. These isolated islands can occur when intermediate
regenerator sites are used in-between the end nodes.
For links without intermediate regeneration sites there is no risk for isolated islands. The
management traffic can thus follow the traffic as it is switched. This configuration is set via
“Wrapper mode” and via the selection “Follow traffic”. This means that the management
traffic channel will follow the traffic upon a protection switch.
For links with intermediate regeneration sites, the “Wrapper mode” is recommended to be
set into “Fixed to default”. This means that the management traffic channel will continue to
be transmitted on the default line ports (see chapter 7.1) regardless of protection switching.
See 5.1 for more information on this subject.
Note that each end node must be configured identically.

6.6 TPDDGBE in Regenerator mode (”tpDDbER”)

A different GUI is presented if the TPDDGBE is configured for regenerator mode. As an
example, no “Client” tab exists since all interfaces are of “line” type.
The “Line PM” and “PPP” tabs are identical as for the Transponder mode and is not
repeated below.
The below screen dump show an example of the “tpDDGbER” tab

6.6.1 “Inventory” tab
The figure shows an example inventory screen dump from the ENM GUI.
Inventory information on the optical transceivers is found under the tab “Line”.

6.6.2 “Line” tab
In the regenerator mode all interfaces are of “line” type. See chapter 7 on how the ports are
used in this mode.
If having more than two TPDDGBE units in repeater mode between two terminating
TPDDGBE units and if the wrapper is terminated in the repeaters (ports 13-14 and 15-16),
it is recommended to set Laser mode to on “on” rather than the default “als” on the line
ports of the repeaters. This is to avoid disturbances on the wrapper signal when you have
fibre-breaks in surrounding links. Note that the laser class of the link can be of Class 1M if
DWDM SFP’s are used.

7 MECHANICAL LAYOUT
New (from A3.2) Transmode overlay and previous (up to A3.1) Lumentis version

7.1 Transponder configuration
Port usage in line protection configuration. Note the position of the protection ports.
DGBE Transponder no 1:
Client 1: Tx-Rx Ports 1-2

Line 1(A): Tx-Rx Ports 13-14 (also referred as the “default” ports)
Line 1(B) (prot): Tx-Rx Ports 9-10
DGBE Transponder no 2:

Line 2(A) Tx-Rx Ports 15-16 (also referred as the “default” ports)
Line 2(B) (prot): Tx-Rx Ports 11-12

7.2 Regenerator configuration
Cascade Transponder R1: Tx-Rx Ports 1-2 & 3-4

Note! Management channels are default set to the Cascade transponder R4. Always start
use these ports first when building a network! See chapter 4.10

8 TECHNICAL DATA
Table 1: Misc data

Parameter Value Comment
~25 W w/o line protection. ~26W with line prot
Power consumption Max value
~28W in regenerator mode
Weight 0,6 kg
3us 1)
Latency 1) In repeater mode
9us
Timing Re-timing in both directions Full 3R
Line rate 2,488Gb/s Equal to STM-16/OC-48 rate
Embedded mgmt ch 320 kbit/s Channel capacity
Table 2: HW Revision history
Product number Rev Introduced

Release
st
TPDDGBE R1A A3.1 1 released version.
Some SW upgrades are traffic affecting since the FPGA code is changed. Please contact
Transmode TAC support for information and details on upgrades.
Table 3: Supported Transceivers

Client format
TPDDGBE
Traffic Unit
Item code
TRX100007 C/L GbE Optical
TRX100040 C/L GbE Optical
TRX100041 C GbE Optical
TRX100014/bb L/C GbE Optical
TRX100074/bb C GbE Optical
TRX100028/xxx L/C GbE Optical
TRX100073/xxx L -
FE electrical
TRX100025 C
GbE Electrical
C= Can be used on client port, L= can be used on line port
The TRX100025 enables electrical 100Mb/s Ethernet (FE) signal to be transported. This
requires that is both ends uses same TRX. The 100Mb/s signal is upscaled in the TRX to a
GbE line rate and transported as such.
For technical data on supported transceivers, see Dimensioning Guidelines within the
System Manual!

Table 4: Measuring and monitoring
Parameter/requirement Unit Min/ Accuracy/ Hysteresi

max/ resolution s
def Min/max
WDM IF: Received power level dBm -28/-7/- 1/0.1
measurement
WDM IF: Received power level low dBm -28/-7/-25
WDM IF: Received power level high dBm -28/-7/-8
WDM IF: Loss of signal activation threshold dBm -28/-7/-27 1
Table 5: Network functions
Parameter/function Values Type Description

Client signal format GbE R Readable client format.
The speed of the client signal (1000
Client signal bitrate 1250 R
Mbps)
Loopback on/off RW Loopback of client signal


21 Td-Ddgbe N

Uploaded by

Copyright:

Available Formats

21 Td-Ddgbe N

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

21 Td-Ddgbe N

Uploaded by

Copyright:

Available Formats

TM-Series

Transmode Systems AB © 2009 Transmode Systems AB

1.1 In commercial confidence

1.2 Document Revision History

Revision Date Description of changes

Transmode Systems AB © 2009 Transmode Systems AB

A Transponder/Muxponder also enables encapsulation of the client signal into a digital

- Introduction of quality check of the WDM signal enabling Performance Management

- Insertion of path information that can be used to validate the connection.

Transmode Systems AB © 2009 Transmode Systems AB

Figure 1: Double DGbE Transponder

The TPDDGBE can be used in multiple configurations;

1. As two separate Transponder functions, each aggregating 2x GbE-signals where the

2. As four separate regenerator functions (tpDDGbER).

Transmode Systems AB © 2009 Transmode Systems AB

Transmode Systems AB © 2009 Transmode Systems AB

3.1 CWDM networking

Figure 2: Single-fiber CWDM networking example

Up to 8 channels can be established in the single-fiber configuration giving 16 GbE-

CWDM networking solutions on fiber-pair configurations is also supported. See

Transmode Systems AB © 2009 Transmode Systems AB

3.2 DWDM networking

Figure 3: Combined CWDM and DWDM networking example

See “Dimensioning Guidelines” for more information on amplified DWDM networks.

Transmode Systems AB © 2009 Transmode Systems AB

4.1 Line protection

Figure 4: Line protection

Protection switch is generated upon “Loss Of Signal”, “Loss Of Frame” and

Transmode Systems AB © 2009 Transmode Systems AB

The wrapper on the line side is not affected by this loop-back.

4.3 Optical Interfaces

Transmode Systems AB © 2009 Transmode Systems AB

4.4 GbE broadcast

Figure 6: Protected broadcast configuration

When using protection in broadcast mode it is important to understand that if performing a

Transmode Systems AB © 2009 Transmode Systems AB

4.5 Client configuration.

• GbE client 1 only, i.e. any signal on GbE client 2 is blocked

4.7 Signal format on xWDM layer

4.8 Performance monitoring

PM on line signals is imitating ITU-T G.826 standard based on CRC errors.

Transmode Systems AB © 2009 Transmode Systems AB

4.9 GbE channel utilization

This is retrieved every 15min/24h.

4.10 Management channel

The TPDDGBE unit supports two management channels (DCC-channels). In Transponder

4.11 Monitor points

• Board temperature: Given in Centigrade

See “Troubleshooting guide” in volume “Operation & Commissioning” of the System

Transmode Systems AB © 2009 Transmode Systems AB

4.13 Product data

The information is divided into three main groups:

• Specific board data - Data needed for proper board operation.

Some alarms are based on the presence of this information:

4.14 Remote inventory

Transmode Systems AB © 2009 Transmode Systems AB

4.15 Consequent actions

Figure 7: Consequent actions per DGBE-function

Loss of input client signal: