22 Td-gfpmxp10 Q

TM-Series
Technical Description
10-port GFP xWDM Muxponder (GXP10/2500-SFP R1, R2)
Rev Q, 2009-06-15
IN COMMERCIAL CONFIDENCE
10-PORT GFP MUXPONDER
Date: Doc. number: Rev: Page
© Transmode 2009-06-15 TD-GFPMXP10 Q 2 (42)
Table of Content
1 GENERAL ..........................................................................................................3
1.1 In commercial confidence ...............................................................................................3
1.1.1 Document Revision History.............................................................................................3
2 FUNCTIONAL DESCRIPTION...........................................................................4
2.1 General description .........................................................................................................4
2.2 10-port GFP Muxponder Unit ..........................................................................................4
2.2.1 Transparent GFP mapping, GFP-T.................................................................................5
2.2.2 Frame-based GbE Operation, GFP-F .............................................................................5
2.3 Traffic combinations ........................................................................................................6
2.3.1 Client interface ................................................................................................................7
2.3.2 Line interface ..................................................................................................................8
2.4 Bandwidth & rate limit settings ........................................................................................9
2.5 Mapping of client signals.................................................................................................9
2.6 Embedded management channel .................................................................................13
2.7 VC-3/VC-4 Trail Trace Identifier....................................................................................13
2.8 Performance monitoring................................................................................................15
2.9 GbE channel utilization .................................................................................................17
2.10 Monitor points ...............................................................................................................17
2.11 Alarms...........................................................................................................................17
2.12 Trail Trace.....................................................................................................................18
2.13 Protection configuration ................................................................................................18
2.14 Product data..................................................................................................................18
2.15 Remote inventory..........................................................................................................19
2.16 Loop-back .....................................................................................................................19
2.17 Consequent actions ......................................................................................................20
2.18 Synchronization ............................................................................................................21
2.18.1 Client input ....................................................................................................................21
2.18.2 Line output ....................................................................................................................21
2.18.3 Line input ......................................................................................................................21
2.18.4 Client output..................................................................................................................21
2.18.5 Example of GXP10/2500-SFP Synchronization ............................................................22
3 Applications ......................................................................................................23
3.1.1 CWDM networking ........................................................................................................23
3.1.2 DWDM networking ........................................................................................................24
3.1.3 SDH/SONET networking...............................................................................................25
4 Setting up GXP10/2500-SFP via ENM GUI .....................................................26
4.1 ENM Frame Overview...................................................................................................27
4.2 Verbose mode...............................................................................................................28
4.3 Equipment Frame .........................................................................................................29
4.4 NE configurations..........................................................................................................30
4.5 Equipment view, unit and interface settings ..................................................................31
4.5.1 “Inventory” tab...............................................................................................................32
4.5.2 “Line” tab.......................................................................................................................33
4.5.3 “Line PM” tab ................................................................................................................35
4.5.4 “PPP” tab ......................................................................................................................36
4.5.5 “Client” tab ....................................................................................................................37
4.5.6 “Sync” and “Sync Source” tabs .....................................................................................38
5 MECHANICAL LAYOUT ..................................................................................39
6 Mounting...........................................................................................................40
7 TECHNICAL DATA ..........................................................................................41
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 us or inability to use this manual, even if Transmode Systems AB 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.1.1 Document Revision History
Revision Date Description of changes

A 2004-09-10 1st release
B 2005-01-05 Added information on used STS-1’s and VC-4’s
Added transceiver type for ESCON. Removal of superfluous
C 2005-01-10
transceiver.
Added information on GbE channel utilization. Updated
D 2005-03-20
functionality in A3.1 release
Added revision history table in chapter 4. Transition to new
E 2005-06-30 Transmode format. Introduction of new overlay with clarified
text information
Updated with additional traffic combinations introduced in
F 2005-09-30
A4.0
G 2006-04-20 Updates for A5.0 release.
H 2006-06-20 Improved Rx sensitivity (4dB) on TRX10006.
Updated with Release 6.1 content:
RDI functionality
I 2006-08-20
New 80km/1550nm SFP (TRX100054)
Addition of ENM GUI information
Updated with release 8.0 content; low band CWDM SFP’s
J 2007-04-27
and BNC video SFP’s.
K 2007-06-29 Addition of latency data for Fibre Channel
Updated with 10.0 content; new DWDM SFP
L 2007-12-21
Removal of channel mapping on MDU’s etc.
M 2008-03-14 Change of logotype
N 2009-01-16 Corrected optical data on TRX100014/xx
O 2009-01-30 Corrected overload value on TRX100007
P 2009-02-10 New document front
Updated with rel 13.0 content
Q 2009-06-15
Removal of optical data tables in chapter 7
Release 13.0 update:
The unit is shipped in a SDH or SONET mode. The difference between the two modes is
the handling of the S1-byte within the OH-section which differs between SDH and SONET.

2 FUNCTIONAL DESCRIPTION
2.1 General description

WDM is an analogue technique and requires a controlled environment for error-free
transmission of the traffic. Transponders/Muxponder serves as buffers between the “client
layer” and the “WDM domain”. They also add functional enhancements, like multiplexing to
utilize the wavelengths more efficiently, performance management to supervise and
monitor the status and embedded management channels to provide secure and easy
management access to all NE’s. As a result, client equipment of different types (e.g. SDH,
IP routers) and from different vendors can be connected to the TM-series network without
any impact on the transmission path through the network.
2.2 10-port GFP Muxponder Unit
Figure 1: 10-port GFP Muxponder
The 10-port xWDM Muxponder performs mapping of 10 client signals into a

STM-16/OC-48 line signal according to the GFP-standard.
The unit supports both Transparent (GFP-T) as well as Framed GFP (GFP-F) mapping
according to G.7041 and performs virtual (VCAT) and contiguous (CCAT) concatenation as
defined in ITU-T G.707, G.783 and ANSI T1.105
In Transparent mode (GFP-T) all supported traffic signals are transported transparently
and protocol independent. The Framed mode (GFP-F) enables bandwidth and channel rate
limiting for GbE-signals via IEEE 802.3z Ethernet MAC functionality.
The unit supports the following traffic types:
• GbE
• 1G Fibre channel (1G FC) & FICON
• 2G Fibre channel (2G FC) & 2G FICON
• ESCON
• DVB-ASI (Digital Video Broadcast - Asynchronous Serial Interface)
Note: FICON and Fibre Channel (FC) are treated as “same” traffic type and everywhere FC
is stated also FICON is valid.
In Frame based GFP mode (GFP-F) a rate limited transport of up to 10x GbE signals is
supported.
The unit is prepared for LCAS (Link Capacity Adjustment Scheme) as defined in
ITU-T G.7042 for hitless change of GbE channel rates. LCAS is not currently supported.

The client ports are equipped with SFP’s to match the traffic type they shall carry.
The line interface can be equipped with either CWDM or DWDM SFP’s to enable the
10-port GFP Muxponder to be used in either CWDM or DWDM networks.
PM data is extracted every 15min/24h and presented according to G.784/G.826 on all

tributaries and line signal. The unit also has embedded management channel for node
access via the node and network management system.
2.2.1 Transparent GFP mapping, GFP-T
• Performs transparent GFP processing for all client protocols using 64B/65B encoding
on a per-port basis.
• GFP-encapsulated data is mapped in right sized SONET/SDH using virtual or

contiguous concatenation.
2.2.2 Frame-based GbE Operation, GFP-F
• Supports both full-rate and fractional-rate frame-based GbE mapping into SONET/SDH
frames.
• Each port integrates a full IEEE 802.3z Ethernet MAC and supports extensive RMON
statistics.
• 48KBytes ingress FIFO’s on each port allowing loss-less flow control between the unit
and remote switches using IEEE 802.3x for distances up to ~10km.
• Individual bandwidth allocation per GbE in steps of VC-3 or VC-4
• Full Duplex according to IEEE 802.3z (1000Base-X)
• Ethernet packet sizes 64 up to 9600 bytes (Jumbo frames)

2.3 Traffic combinations

All mapping is done according to the SDH standard. The traffic signals can be mapped into
the STM-16 (OC-48) payload using VC-4 (STS-3c) or VC-3 (STS-1) frames.
Note: VC-3 mapping is done via AU-3 (i.e. non-ETSI mapping). VC-4 is according to the
ETSI mapping standard as defined in G.707
The following pre-defined Traffic combinations are provided:

Table 1: Summary of traffic mapping in VCAT and CCAT mode for SDH and SONET
Traffic SDH mapping GFP-mode Concatenation Command
combination
2x 1G FC 2x VC4-6V GFP-T VCAT fcx2VcatVc4
1x 2G FC 1x VC4-12V GFP-T VCAT fc2GVcatVc4
1x 2G FC 1x VC4-16c GFP-T CCAT fc2G
8x ESCON/DVB-ASI 8x VC4-2V GFP-T VCAT dvbEsconx8VcatVc4
8x ESCON/DVB-ASI 8x VC4-2C GFP-T CCAT dvbEsconx8
6x ESCON/DVB-ASI 6x VC3-4V GFP-T VCAT esconx6FcGbE
+ 1x FC /GbE + 1x VC4-7V
4x ESCON/DVB-ASI 4x VC4-2C GFP-T CCAT dvbEsconx4FcGbE
+ 1x FC /GbE + VC4-8C
10x ESCON 10x VC3-4V GFP-T VCAT esconx10
10x GbE 10x VC3-xV GFP-F VCAT framedGbEx10
10x GbE 10x VC4-xV GFP-F VCAT framedGbEx10Vc4
2x GbE / FC 2x VC4-8c GbE in GFP-F CCAT fcGbEx2
or GFP-T
FC in GFP-T
2x GbE/FC 2x VC4-7v GbE in GFP-F VCAT fcGbEx2VcatVc4
or GFP-T
FC in GFP-T
Note: GbE can be framed or transparently mapped. Framed mapping must be used if over-
subscription is used. All other formats are transparently mapped.
See chapter 2.5 for information on port restrictions.
Other mapping combinations can be provided on request.
A number of VC-3/VC-4’s are unused depending on selected traffic combination and also
depending on how many client signals that are connected. Unused VC-3/VC-4 frames are
market “unequipped” via the C2-byte (all 0’s) to enable usage of these frames within an
intermediate SDH network.

2.3.1 Client interface
Before any client signal can be interfaced to the unit, a client transceiver plug-in module
(SFP) must be inserted. The following variants are provided:
• GbE/FC MM – A transceiver for Multimode signals from 100Mb/s to 2Gb/s, i.e.

- DVB Video
- ESCON
- GbE
- 1G Fibre channel
- 2G Fibre channel
• GbE/FC SM – A transceiver for Single Mode signals from 100Mb/s to 2Gb/s, i.e.
- DVB Video
- ESCON
- GbE
- 1G Fibre channel
- 2G Fibre channel
• GbE electrical – A SFP with RJ45 interface for 1000Base-T signals.
• ESCON MM – A 1310 nm transceiver for ESCON signals of MM-type.
With the 8.0 release a set of new SFP’s are introduced to support Electrical DVB-SDI and
Electrical DVB-ASI, both operating at 270Mb/s.
Note that these are uni-directional formats and that the SFP’s are of Tx and Rx type
respectively.
• DVB-ASI: Transmit version, DVB-ASI TX: (TX100064)

Receive version, DVB-ASI RX: (RX100065)
All above have a standard 75ohm BNC interface.
See section 7 for information on what SFP types that support these traffic types.

2.3.2 Line interface
The line interface can be equipped with uncolored, CWDM or DWDM SFP’s.
Uncolored:
• 2km/1310nm type (I-16.1)

• 15km/1310nm type (S-16.1)
• 80km/1550nm type (L-16.2)
CWDM:
• 40km/20dB type
• 80km/28dB type
• 100km/30dB type
DWDM:
• 120km/28dB type
The distance values indicate max distance due to dispersion. When interfacing to
SDH/SONET systems standard 1310 nm short-haul SFP’s interfaces can be used.
Non-Transmode SFP’s can be used as a temporarily solution without guarantee on

performance. Usage of non-Transmode SFP’s is logged and a notification is presented in
the TM-ENM. Optical PM-parameters will not be retrieved from non-Transmode SFP’s.

2.4 Bandwidth & rate limit settings

In the GFP-F mode the GbE-signals shall be allocated a max bandwidth and optionally a
rate limit within that max bandwidth. The bandwidth allocation is done into VC-3 or VC-4
payloads.
In the VC-3 alternative the max bandwidth is set in number of VC-3 frames (with payload of
48,3Mb/s). The max number of available VC-3 frames is 48. A GbE-signal in GFP-F mode
requires minimum 21x VC-3 frames to be transported with full throughput.
In the VC-4 alternative the max capacity is set in number of VC-4. The max number if
VC-4 is 16. A GbE-signal in GFP-F mode requires minimum 7x VC-4 frames to be
transported with full throughput.
Optionally, a GbE-signal can be further rate limited within the allocated max bandwidth
capacity. The minimum channel rate is 10Mb/s. The rate can then be set in steps of 1Mb/s
up to the full capacity, as defined by the max bandwidth setting.
Changes in max bandwidth (e.g. VC-3 settings) will introduce bit errors on all ports.
Changes in rate limit is not traffic affecting.
2.5 Mapping of client signals

All settings are done via CLI or GUI (Web Browser Interface)
• 2x 1G FC (GFP-T): Client ports 9 & 10 (Tx/Rx-ports 17-18 & 19-20) must be used.
Each of the 1G Fibre channel signals is mapped into 2x VC4-6V via VCAT (Virtual
Concatenation).
• 1x 2G FC (GFP-T): Client port 10 must be used (Tx/Rx-ports 19-20).

The 2Gb/s Fibre channel signal is mapped into 1x VC4-12V via VCAT or into
1x VC4-16c via CCAT.
• 8x ESCON/DVB (GFP-T): Client ports 1 (Tx/Rx-ports 1-2) to 8 (Tx/Rx-ports 15-16)

must be used. The ESCON/DVB signals are mapped into 8x VC4-2V via VCAT or
8x VC4-2C via CCAT).
Ports 1-8 can carry ESCON or DVB-ASI in any mix. A client port can configured for
ESCON or DVB-ASI without any mapping reconfiguration
• 6x ESCON/DVB (GFP-T) + 1x FC (GFP-T) /GbE (GFP-T or GFP-F): Client ports 1 to

6 (Tx/Rx-ports 1 to 12) shall be used for the ECON/DVB signals. The FC/GbE signal
shall be applied on client port 10 (Tx/Rx-port 19-20). The ESCON/DVB signals are
mapped into VC-3-4V containers. The FC/GbE signal is mapped into a VC4-7V
container.

• 4x ESCON/DVB (GFP-T) + 1x FC (GFP-T) /GbE (GFP-T or GFP-F): Client ports 1 to

4 (Tx/Rx-ports 1 to 8) shall be used for the ECON/DVB signals. The FC/GbE signal
shall be applied on client port 10 (Tx/Rx-port 19-20). The ESCON/DVB signals are
mapped into VC-4-2C containers. The FC/GbE signal is mapped into a VC4-8C
container.
• 10x ESCON (GFP-T): Client ports 1 (Tx/Rx-ports 1-2) to 10 (Tx/Rx-ports 19-20) are
used. A fixed mapping into VC3-4V containers is done. Client port 1 (Tx/Rx-ports 1-2)
is allocated to the first 4 VC3-4V’s. Client port 2 (Tx/Rx-ports 3-4) is allocated to VC3-
4V no 5 – 8, and so on. Since a fixed allocation is done, the client ports 1 to 10 can be
used freely without any traffic hits.
• 10x GbE (GFP-F): The GbE-signals can be mapped in two ways:

- via VCAT VC3-xV mapping
- via VCAT VC4-xV mapping
Any of the Client ports 1 (Tx/Rx-ports 1-2) to 10 (Tx/Rx-ports 19-20) can be used.
Allocation of VC-3/-4 capacity is done per port in consecutive order. Note: Un-used
ports in-between used ports cannot be allocated capacity without traffic effects.
Example: Client ports 1,2, 5 and 6 are used and allocated a certain VC-4 capacity.
Client ports 3 and 4 can thus not be opened at a later stage and given capacity without
affecting ongoing traffic. Note also that any changes to activated allocation of VC-4
bandwidth will be traffic affecting. In the example above, opening client ports 7 to 10 at
a later stage will also be traffic affecting.
• 2xFC/GbE: Client ports 9 and 10 (Tx/Rx-ports 17-18 & 19-20) must be used. A fixed
mapping into 2x VC4-8c (or 2x VC4-7c) containers is done per signal type. The GbE’s
can be mapped using GFP-T or GFP-F. In the GFP-F configuration, the GbE-signals
can be allocated a certain capacity within the 2x VC4-8c (or 2x VC4-7v) bandwidth.
The FC’s are mapped according to GFP-T.
Figure 2 and Figure 3 shows the above described mappings. In Table 1 a summary of the
mapping for VCAT and CCAT is shown

Figure 2: Virtual and Contiguous concatenation alternatives

Figure 3: Virtual and Contiguous concatenation alternatives

2.6 Embedded management channel

The GFP Muxponder uses the D4-D10 bytes in the SDH/SONET frame as an embedded
management channel. This channel is used for internal management communication.
2.7 VC-3/VC-4 Trail Trace Identifier

When the 10-port xWDM Muxponder is connected to an SDH network containing
VC-3/VC-4 cross connects, there is possibility that one or more VC-3/VC-4 frames are lost
or replaced with incorrect VC-3/VC-4 frames. A lost VC-3/VC-4 frame will render an alarm
(VcGroupfail). To enable easy identification and verification of the received VC-3/VC-4
frames, the J1 path trace byte can be set via the ENM. By setting a known value at the
transmit end and checking them at the receive end it is possible to identify which VC-3/VC-
4 that is incorrect and enable further fault finding within the intermediate SDH network.
The path trace is set per client interface. All VC-3/VC-4 frames connected to the client
interface are managed as a group. There are two options on setting the VC-4 Trace
Identifier (15 bytes);
1. Individual VC-level (individualVcLevel): Enables setting of the first 9 bytes. The

remaining bytes are set by the ENM to provide group and sequence information to
indicate that the VC-3/VC-4 is part of a group and what sequence number it has within
that group (see Table 2). The first 9 bytes (part 1 – 4 in table) are given as default
value. These can be changed to any type of information if needed.
2. Group VC-level (VcGroupLevel): Enables entry using all bytes in the path trace (15
bytes). The same value will be inserted in all J1 bytes within the group. There is thus
not possible to distinguish e.g. the sequence number of an individual VC-3/VC-4 within
a group. The first 9 bytes (part 1 – 4 in table) are given as default value. These can be
changed and extended up to 15 bytes with any type of information if needed.
Table 2: Path trace settings for individual VC-level:

Part Description Note
1 Last 6 figures of node IP # (xxx.xxx) Default values
2 Rack # (hex), string can be
3 Slot # manually changed
4 Port # (Note! Value equals client port, not tx/rx port)
5 # of VC’s in group Automatically
6 VC4-seq # within group generated, not
7 VC4 # within STM16 Frame settable (hex)
The J1 trace is inserted via the “Client” tab in the ENM GUI. See also chapter 4.5.5.
See examples below.

Example 1:
A GFP Muxponder is configured for 2x GbE/FC using 2x VC4-7v configuration. The unit is placed
in a node with IP 192.168.1.164 (c0.a8.01.a4 in hex), in chassis 1, slot 4. On client port 10
(tx/rx-port 19-20) the following default J1 values are inserted when selecting
“individualVcLevel”:
VC4 # 1 : 01.a4 14a070108

VC4 # 2 : 01.a4 14a070209
VC4 # 3 : 01.a4 14a07030a
VC4 # 4 : 01.a4 14a07040b
VC4 # 5 : 01.a4 14a07050c
VC4 # 6 : 01.a4 14a07060d
VC4 # 7 : 01.a4 14a07070e
As stated above, the first 4 parts (IP-address, Chassis#, Slot#, Client port#) can be
replaced by an arbitrary value. Up to 9 positions (i.e. 9 bytes) can be changed. The
remaining 3 parts will be unaffected.
The string “stockholm” is entered (fills all 9 bytes/positions). This will give the following J1
bytes:
VC4 # 1 : stockholm070108
VC4 # 2 : stockholm070209
VC4 # 3 : stockholm07030a
VC4 # 4 : stockholm07040b
VC4 # 5 : stockholm07050c
VC4 # 6 : stockholm07060d
VC4 # 7 : stockholm07070e
Example 2:
Same conditions as above, but now using “VcGroupLevel”.
As stated above, the first 4 parts (IP-address, Chassis#, Slot#, Client port#) is inserted on
all J1-bytes as default:
VC4 # 1 : 01.a4 14a

VC4 # 2 : 01.a4 14a
VC4 # 3 : 01.a4 14a
VC4 # 4 : 01.a4 14a
VC4 # 5 : 01.a4 14a
VC4 # 6 : 01.a4 14a
VC4 # 7 : 01.a4 14a
A string “helloworld12345” (total of 15 positions/bytes) is entered as J1-value.

“helloworld12345” will then be inserted on all J1’s within the group.

2.8 Performance monitoring

Data error collection for PM statistical data is performed within this unit.
The PM data are collected every 15min and 24hours and presented according to
G.874/G.826 standard:
• ES – Errored Seconds
• SES – Severely Errored Seconds.
• BBE – Background Block Errors
• UAS – Unavailable Second
The data is stored in the node and retrieved by the network manager TNM for statistical
presentation and calculations. Up to 96 loggings of 15min values and 40 loggings of 24h
values can be stored within the NE. The number of logged values is settable; default is
32x 15min values and 7x 24h values.
Data collection is done on
• incoming client signals

• outgoing client signals
• incoming line signal
Detected CRC errors, frame losses and 8B10B coding errors are fitted into the G.826
hierarchy according to the following:
Errored Seconds (ES): A second shall be classified as errored if any of the following
defects or anomalies is detected on a signal:
- Loss Of Signal
- Bitrate Mismatch
- Equipment Fail
- Loss Of Synchronization
- Link Down
- Decoding Error (8B10B)
- Disparity Error
- Frame Error1
- Symbol Error
- Invalid Transmission Word
Severely Errored Second (SES): A second shall be classified as severely errored if any of
the following defects is detected on a signal:
- Loss Of Signal
- Bitrate Mismatch
- Loss Of Synchronization
- Link Down
- More than 30% Decoding Error (8B10B),
- Disparity Error
- Frame Error1
- Symbol Error

Background Block Errors (BBE): The background block error counter shall be incremented
for each anomaly (e.g. errored block) not occurring as part of a Severely Errored Second:
- Decoding Error (8B10B)

- Disparity Error
- Frame Error
- Symbol Error
- Dropped packets in GFP-F mode and rate limiting
Unavailable Second (UAS): A period of unavailable time begins at the onset of ten (10)
consecutive SES events. A new period of available time begins at the onset of ten
consecutive non-SES events. Every second during the unavailable time state is classified
as an Unavailable Second (UAS).
Time
10 s <10 s 10 s
Unavailability detected Availability detected
Unavailable period Available period
Severely Errored Second

T1313780-98
Errored Second (non-SES)
Error-free Second
Figure 4: Example of unavailability determination (G.826)

2.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.
In the ENM GUI the GbE utilization values are presented under the tab “Client”.
2.10 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.
2.11 Alarms
Any generated alarms are accessible via 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 “Troubleshooting Guide” within the Operation and Maintenance volume of the System
Manual for details on generated alarms.

2.12 Trail Trace

Trail Trace uses the J0 byte in the line signal (STM-16/OC-48). The Trail Trace
functionality can be used in installation/commissioning activities to verify that the fiber
cabling and patch cord connections have been done correctly.
The J0-byte is automatically set to a default value (includes IP-address, chassis type etc)
or can be set to a user defined value.
The trail trace function has a settable alarm mode: ‘on’ or ‘off’. When set to ‘on’ the
messages in the ‘Expected Trace’ and ‘Received Trace’ fields are compared and if they
differ a “Trace Identifier Mismatch” alarm is activated. When set to ‘off’ the mismatch alarm
shall be disabled or cleared if already activated.
2.13 Protection configuration

The GFP MuxPonder unit does in current release not support the O-SNCP configuration
where the protection switching is performed by turning client interface laser on/off.
Protected configurations can be applied via the Fiber Protection Unit or via resilience
operations within the client equipment.
2.14 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.

2.15 Remote inventory

An on-board EE-PROM enables remote extraction of inventory data. The information
provided is:
• Description: i.e. Unit name

• Management name: e.g. tpqmr:1:2 (unit type/chassis no/slot no)
• Hardware Product; i.e. article number (TPQMR)
• Hardware revision
• Software product; i.e. product code for unit SW
• Software revision
• Firmware revision
• Product data revision (see chapter 2.14)
• Serial number; unique number for this individual
• Manufacturer (i.e. Transmode Systems AB)
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
See chapter 4.5.3 for info details on how inventory is presented via the ENM GUI.
2.16 Loop-back
Far-end client loopback is supported, i.e. each remote client port can be set into loopback
mode. This is done in the ENM GUI via the “Client” tab.

2.17 Consequent actions
Figure 5: Consequent actions upon loss of input signals
The behavior of the output on the client interface is given by the “Forward ALS” setting.
Upon loss of near-end input client signal, the far-end client output is
• shut down if “Forward ALS” is enabled
• idle signal if “Forward ALS” is disabled
Upon loss of input wdm-signal, the outgoing client signals are
• shut down if “Forward ALS” is enabled
• idle signal if “Forward ALS” is disabled
The wdm transmitter is by default set in ALS mode (Automatic Laser Shut Down) as
defined in IEC 60825-2 & G.664. The client outputs on the far-end is affected as above.
Upon “vcGroupFailed” (in VCAT) will shut down corresponding client signal if “Forward
ALS” is enabled. If “Forward ALS” is not enabled, the client Tx will keep transmitting.
MS-RDI is inserted in the upstream when the input line interface detects LOF, LOS or AIS.
MS-RDI will only work if ALS is not enabled since ALS will shut down the upstream signal
upon loss of input signal.

2.18 Synchronization
The synchronization can be divided into four separately clock domains:
• Client input
• Line output
• Line input
• Client output
Synch table with priority settings:

- Manual: The sync source is set manually to the internal oscillator having a
S1-byte value of 11 (decimal) Rec. G.813 Option I (SEC).
- Auto: Selects (if available) the incoming STM-16 line signal as sync source. If
available, a comparison between the S1-bytes of the two sources is performed. If
equal, the priority setting gives the selection of sync source. If not equal, the source
having the best S1-byte quality is selected. Upon loss of external sync, automatic
switch is done to internal. Upon regain of external, the selection of sync source is
based on S1-byte values.
See also chapter 4.5.1
2.18.1 Client input
The client input clocks are used for the GFP encapsulation.
2.18.2 Line output
The STM-16/OC-48 line signal can be clocked via an internal oscillator or by the incoming
STM-16/OC-48 line signal.
2.18.3 Line input
The incoming line signal is used for the deframing processing of the SDH/SONET signal
and can also be used to clock the outgoing line signal.
2.18.4 Client output
An internal oscillator is used to clock the client signals. Four different oscillators are used
depending on the traffic format used.
Note!
The above synchronization is only supported by the R2-version (released in A4.0 October
2005). The R1-version has only the internal oscillator as sync source.

2.18.5 Example of GXP10/2500-SFP Synchronization
Figure 6: Synchronization example for GXP10/2500-SFP
Introduction
The user want to setup a synchronization plan for the network described in Figure 6. The
user wants the synchronization mode to be automatic and therefore automatic
synchronization mode is set in both nodes.
Node A
• The synchronization mode is set to auto.
• Administrative state on line sync source and the internal oscillator are set to up.
Node B
• The synchronization mode is set to auto.
• Administrative state on line sync source and the internal oscillator are set to up.
If there is no SDH network between the nodes, the recommended way of setting up the
synchronization is to let one of the GXP10/2500-SFP boards be synchronized using the
internal oscillator and one to synchronize on the incoming line signal.

3 APPLICATIONS
3.1.1 CWDM networking
The 10-port GFP MuxPonder 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.
The 10-port GFP MuxPonder can be combined with any other Traffic units provided in the
TM-3000/-301/-101 series.
Figure 7: Single-fiber CWDM and DWDM networking alternatives
The figure shows the CWDM networking alternatives operating on single-fiber

configurations as well as fiber-pair configurations. See also “Dimensioning Guidelines”
within the System Manual for more details on configuration alternatives and losses through
the optical components.

3.1.2 DWDM networking
Figure 8: DWDM alternatives
The above figure shows the single-fiber and 32ch fiber-pair configurations. The
GXP10/2500-SFP can also be used in 80ch configurations via the MDU40/50G-EVEN unit.
See Dimensioning Guidelines for more information on amplified DWDM networks.

3.1.3 SDH/SONET networking
The 10-port GFP MuxPonder can also be used as an ingress/egress to a SDH/SONET

network for transporting e.g. SAN or GbE traffic as shown below.
Figure 9: GFP MuxPonder used in combination with a SDH/SONET network.
A SDH/SONET network that does not directly support e.g. GbE-traffic can in this way carry
up to 10x GbE signals encapsulated in a STM-16/OC-48 frame.

4 SETTING UP GXP10/2500-SFP 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.

4.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

4.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”.

4.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.

4.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.

4.5 Equipment view, unit and interface settings

When clicking on one of the interfaces on the GXP10/2500-SFP 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 GXP10/2500-SFP.

4.5.1 “Inventory” tab
The figure shows an example inventory screen dump from the ENM GUI.
The “TRX”-button will open a new window showing inventory data on all SFP’s on the unit.

4.5.2 “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.
Note that client interfaces are named “client” and line interfaces are named “wdm”.
Press the “Help” button for more information on the configurable items.

The button “Change” at “Traffic combination” is used to set the traffic combinations as
defined in chapter 2.3. The below screen dump show the dialogue window that is opened.
The GbE signals can in the GFP-F mode be allocated a certain number of VC-3’s or VC-
4’s. For these traffic combinations the entry boxes under “Bandwidth (VC-3)” and
“Bandwidth (VC-4)” are used. The numbers beside the entry boxes are client Tx-Rx port
numbers. Enter the number of VC-3’s or VC-4’s that shall be allocated for the GbE signal
that is connected to respective ports.
Press “Apply” to activate the settings.

4.5.3 “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.

4.5.4 “PPP” tab
The “PPP” tab is used to setup the management communication channel using the D4-D10
bytes within the STM-16/OC-48 OH. See “Designing DCN Network Plans” and
“Configuration Guide” within the Installation & Commissioning volume for more details on
how to establish PPP-links.

4.5.5 “Client” tab
The content under the “Client” tab will differ depending on what traffic format it carries since
some parameters and settings are irrelevant. As an example “GbE utilization” is only
presented for GbE signals. Select client port via the drop-down menu under “”Name”.
Some traffic combinations (that are set under the “line” tab”) include alternatives signal
formats, e.g. “fcGbEx2” can be used to carry Fibre Channel on one port and a GbE (GFP-T
or GFP-F) on the other. The button “Change” under “Signal format” is the used to set these
parameters.

4.5.6 “Sync” and “Sync Source” tabs
The below screen dump shows the “Sync Source” tab of the ENM GUI. The drop-down
menu under “name” has two selections: “ss:1:10” and “ss:1:10:21-22”. The first represents
the internal oscillator since no port numbers are included in “ss:1:10”. The second
alternative represents the line interface since ports since the port numbers 21-22 are
included in the name.
The “Priority” can be set using a value between 1 to 16 where 1 is highest priority and 16 is
the lowest.
The “Auto” or “Manual” mode is set under the tab “Sync” as shown in the below example.

5 MECHANICAL LAYOUT

6 MOUNTING
The 10-port GFP MuxPonder can be mounted with other Traffic units in the TM-3000 or
TM-301 chassis. In these configurations a Control Unit (CU) carries the node manager SW
(TM-ENM) that is accessed via CLI or GUI (web-browser). The CU provides an aggregated
management view of the network element with a singular IP-address.
The 10-port GFP MuxPonder can also be mounted in the 1U TM-101/-102 chassis. Since
this is a singular Traffic Unit solution, it is a configuration without a CU. The TM-ENM then
resides within the 10-port GFP MuxPonder, still providing CLI and web browser interface. A
CU-less configuration is also possible within the TM-301 chassis but this will require one
IP-address per Traffic unit in most cases.
TM-301
TM-3000
TM-101
See separate documentation on the TM-3000, TM-301 and TM-101.

7 TECHNICAL DATA
Table 3: General data
Parameter Value Comment
Power consumption 30W Max value with SFP’s
- Internal oscillator (+/-20ppm)
Sync source Rec. G.813 Option I (SEC) (S1-byte = 11, decimal)
- Incoming line signal
- ESCON
- 1000Base-T, -LX, -SX IEEE 802.3ab, IEEE 802.3z
Supported Client
- 1G Fibre channel (& FICON)
signals
- 2G Fibre channel (& FICON)
- DVB-ASI
Line signal STM-16/OC-48
Embedded mgmt ch 488 kbit/s Channel capacity
Table 4: Latency for GbE

Packet
Configuration Latency
size
FCGBEx2VcatVc4 (7VC4, transparent) 1518 50,4us
FCGBEx2VcatVc4 (7VC4, transparent) 64 51,4us
FCGBEx2VcatVc4 (7VC4, framed) 1518 50,2us
FCGBEx2VcatVc4 (7VC4, framed) 64 27,9us
FCGBEx2 (cont, 8VC4, transparent) 1518 4,1us
FCGBEx2 (cont, 8VC4, transparent) 64 4,2us
FCGBEx2 (cont, 8VC4, framed) 1518 24,5us
FCGBEx2 (cont, 8VC4, framed) 64 3,5us
Table 5: Latency for Fibre Channel

Traffic config Delay @ 4 byte payload Delay @ 2112 byte payload
dvbEsconx4FcGbE 4,410us 4,371us
fcGbEx2 4,454us 4,295us
esconx6FcGbE 35,254us 34,454us
fcGbEx2VcatVc4 35,082us 34,419us
fcx2VcatVc4 34,222us 33,402us
fc2G 2,974us 2,945us
fc2GVcatVc4 30,097us 29,396us
Table 6: Product revision information

Product number (HW object) Rev Introduced
Release
R1A A3.0
1st released version.
(0ct 2004)
R2A A4.0 Synch source
GXP10/2500-SFP
(Oct 2005) functionality added
R2A/1 Component revision
change

Table 7: Support transceivers
GXP10/2500-SFP
Traffic Unit
Item code
TRX100007 C/L
TRX100040 C/L
TRX100054 C/L
TRX100041 C
TRX100006 C
TRX100075 C
TRX100035 C
TRX100014/bb L/C
TRX100015/bb L/C
TRX100026/bb L/C
TRX100074/bb C
TRX100028/xxx L/C
TRX100073/xxx L/C
TX100064 C
RX100065 C
The table lists what SFP/XFP transceivers that are supported. “L/C” indicates that the TRX
is typically used on line side. “C/L” indicates that the TRX is typically used on client side.
Table 8: Support matrix TRX vs traffic format

1000Base-Fx (GbE)
STM-16
ESCON
1G FC
2G FC
OC-48
Item code
TRX100007 X X X X X X
TRX100041 X X X
TRX100006 X X X
TRX100075 X
TRX100035 X
TRX100014/bb X X X X X X
TRX100074/bb X X
TRX100028/xxx X X
TRX100073/xxx X X
See “Dimensioning Guidelines” within System Manual for details on optical data


22 Td-gfpmxp10 Q

Uploaded by

Copyright:

Available Formats

22 Td-gfpmxp10 Q

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

22 Td-gfpmxp10 Q

Uploaded by

Copyright:

Available Formats

TM-Series

Transmode Systems AB © 2009 Transmode Systems AB

1.1 In commercial confidence

1.1.1 Document Revision History

Revision Date Description of changes

Release 13.0 update:

Transmode Systems AB © 2009 Transmode Systems AB

2.1 General description

2.2 10-port GFP Muxponder Unit

Figure 1: 10-port GFP Muxponder

The 10-port xWDM Muxponder performs mapping of 10 client signals into a

The unit supports the following traffic types:

Transmode Systems AB © 2009 Transmode Systems AB

PM data is extracted every 15min/24h and presented according to G.784/G.826 on all

2.2.1 Transparent GFP mapping, GFP-T

• GFP-encapsulated data is mapped in right sized SONET/SDH using virtual or

2.2.2 Frame-based GbE Operation, GFP-F

• Individual bandwidth allocation per GbE in steps of VC-3 or VC-4

• Full Duplex according to IEEE 802.3z (1000Base-X)

• Ethernet packet sizes 64 up to 9600 bytes (Jumbo frames)

Transmode Systems AB © 2009 Transmode Systems AB

2.3 Traffic combinations

The following pre-defined Traffic combinations are provided:

See chapter 2.5 for information on port restrictions.

Other mapping combinations can be provided on request.

Transmode Systems AB © 2009 Transmode Systems AB

2.3.1 Client interface

• GbE/FC MM – A transceiver for Multimode signals from 100Mb/s to 2Gb/s, i.e.

• GbE electrical – A SFP with RJ45 interface for 1000Base-T signals.

• ESCON MM – A 1310 nm transceiver for ESCON signals of MM-type.

• DVB-ASI: Transmit version, DVB-ASI TX: (TX100064)

All above have a standard 75ohm BNC interface.

Transmode Systems AB © 2009 Transmode Systems AB

2.3.2 Line interface

• 2km/1310nm type (I-16.1)

Non-Transmode SFP’s can be used as a temporarily solution without guarantee on

Transmode Systems AB © 2009 Transmode Systems AB

2.4 Bandwidth & rate limit settings

2.5 Mapping of client signals

• 1x 2G FC (GFP-T): Client port 10 must be used (Tx/Rx-ports 19-20).

• 8x ESCON/DVB (GFP-T): Client ports 1 (Tx/Rx-ports 1-2) to 8 (Tx/Rx-ports 15-16)

• 6x ESCON/DVB (GFP-T) + 1x FC (GFP-T) /GbE (GFP-T or GFP-F): Client ports 1 to

Transmode Systems AB © 2009 Transmode Systems AB

• 4x ESCON/DVB (GFP-T) + 1x FC (GFP-T) /GbE (GFP-T or GFP-F): Client ports 1 to

• 10x GbE (GFP-F): The GbE-signals can be mapped in two ways:

Transmode Systems AB © 2009 Transmode Systems AB

Figure 2: Virtual and Contiguous concatenation alternatives

Transmode Systems AB © 2009 Transmode Systems AB

Figure 3: Virtual and Contiguous concatenation alternatives

Transmode Systems AB © 2009 Transmode Systems AB

2.6 Embedded management channel

2.7 VC-3/VC-4 Trail Trace Identifier

1. Individual VC-level (individualVcLevel): Enables setting of the first 9 bytes. The

Table 2: Path trace settings for individual VC-level:

See examples below.

Transmode Systems AB © 2009 Transmode Systems AB

VC4 # 1 : 01.a4 14a070108

Same conditions as above, but now using “VcGroupLevel”.

VC4 # 1 : 01.a4 14a