OTN Systems | XTran Manual

MASTERS IN MISSION CRITICAL COMMUNICATIONS

XTran Interface Module: 16-GEP-L

(S30924-Q220-X101)
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

OTN Systems NV COPYRIGHT AND TRADE SECRETS/LIABILITY

____ ____

Industrielaan 17b, 2250 Olen, Belgium The present document and its contents remain the property
of OTN Systems NV and shall not, without prior written
Tel: +32 14 25 28 47 consent, be copied or transmitted or communicated to third
Fax: +32 14 25 20 23 parties, nor be used for any other purpose than such as
E-mail: info@otnsystems.com underlies their delivery to the addressee.
www.otnsystems.com
The present document and its contents may change in the
Ref. No.: XE-M844-E-4 course of time or may not be suitable in a specific situation.
Issued October, 2021 Consequently, they are recommended as suggested
guideline only.
Specifications subject to change as design
improvements are implemented. OTN Systems NV hereby disclaims any liability for any
©2021 OTN Systems NV - All rights reserved. damages that may result from the use of the present
document unless it is used with respect to the operation
and maintenance of equipment originally manufactured by
OTN Systems NV and covered by its standard warranty.

Page 2 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

Contents

1. INTRODUCTION ......................................................................................................... 5
1.1 General............................................................................................... 5
1.2 Manual References ............................................................................. 5

2. MODULE DESCRIPTION .............................................................................................. 6

2.1 Front Panel ......................................................................................... 6
2.1.1 Insert/Remove Module from Node ........................................................... 6
2.1.2 LEDs............................................................................................................ 6
2.1.3 Connectors ................................................................................................. 7
2.2 Functional Operation .......................................................................... 8
2.2.1 Media Module for Ethernet: Interfacing to a LAN Network ..................... 8
2.2.2 I/O with the Central Switching Module (=CSM) ........................................ 9
2.2.3 Ethernet Service ........................................................................................ 9
2.2.4 Voice Service ............................................................................................ 11
2.2.5 Layer2: VLAN handling............................................................................. 11
2.2.6 Layer2: QoS (=Quality of Service) ............................................................ 11
2.2.7 Layer2: MSTP (=Multiple Spanning Tree) ................................................ 12
2.2.8 Layer2: Link Aggregation/LAG (=Link Aggregation Group)...................... 12
2.2.9 Layer2: IGMP Snooping (IGMP = Internet Group Management Protocol)13
2.2.10 Storm Control on Ethernet LAN Port ....................................................... 14
2.2.11 Port Mirroring .......................................................................................... 14
2.2.12 RGERP (=Redundant Gigabit Ethernet Protocol) Support ....................... 15
2.2.13 MRP (=Media Redundancy Protocol) Support ........................................ 15
2.2.14 PoE (=Power Over Ethernet).................................................................... 16
2.2.15 Hardware Edition ..................................................................................... 17
2.3 Onboard Interfaces ........................................................................... 18

3. MODULE SPECIFICATIONS ........................................................................................ 18

3.1 General Specifications....................................................................... 18
3.2 Other Specifications .......................................................................... 18
3.3 Ordering Information ........................................................................ 18

4. ABBREVIATIONS ...................................................................................................... 19

List of figures
Figure 1 Front Panel ...................................................................................................................... 6
Figure 2 RJ45 Ethernet port........................................................................................................... 7
Figure 3 General Example ............................................................................................................. 8
Figure 4 Detailed Example............................................................................................................. 9
Figure 5 Ethernet Service Overview on L2/L3 IFM ...................................................................... 10
Figure 6 MST Example ................................................................................................................. 12
Figure 7 Link Aggregation and LAGs ............................................................................................ 13

XE-M844-E-4 Page 3 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

Figure 8 PIM/IGMP/IMGP Snooping Overview ........................................................................... 14

Figure 9 Port Mirroring Example ................................................................................................. 15
Figure 10 RGERP: General Example............................................................................................. 15
Figure 11 MRP: General Example ................................................................................................ 16
Figure 12 PoE Example ................................................................................................................ 17
Figure 13 16-GEP-L: Side View..................................................................................................... 18

List of Tables
Table 1 Manual References ........................................................................................................... 5
Table 2 LED Indications In Boot Operation ................................................................................... 6
Table 3 LED Indications in Normal Operation ............................................................................... 7
Table 4 RJ45 Ethernet port: Pin Assignments ............................................................................... 7
Table 5 Other Specifications........................................................................................................ 18

Page 4 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

1. INTRODUCTION
1.1 General
This document is valid as of XTran Release 4.6.
This document describes the 16-GEP-L interface module (=IFM) which provides Layer2
functionality. This IFM must be used in core nodes, see Ref. [3b] in Table 1.
This IFM is also referred to as a ‘L2 IFM’ that has 16 electrical LAN (LAN = Local Area Network)
ports on the front panel: 16*1Gbps RJ45 ports. 8 ports (port 9→16) support PoE. Each
individual port can be configured via TXCare (=XTran Management System).
16-GEP-L refers to ‘16 ports – Gigabit Ethernet PoE – LAN’.
Verify the 'XTran Bandwidth Overview' manual (Ref. [100] in Table 1) to see in which node and
IFM slot this IFM can be used.
Main supported features:
• Gigabit Ethernet LAN Ports: 16 x RJ45: 10/100/1000BASE-T copper;
• Port[9..16] support PoE: PoE IEEE 802.3at;
• 4 back end ports, each 10 Gbps, to the CSM;
• Layer2 Switch:
• L2 VLAN handling;
• QoS;
• MSTP (=Multiple Spanning Tree);
• LAG (=Link Aggregation) + LACP (=Link Aggregation Control Protocol);
• IGMP Snooping (IGMP=Internet Group Management Protocol).
• Port Mirroring;
• Storm Control;
• RGERP (=Redundant Gigabit Ethernet Ring Protocol) Support;
• MRP (=Media Redundancy Protocol) Support.

1.2 Manual References

Table 1 is an overview of the manuals referred to in this manual. ‘&’ refers to the language
code, ‘*’ refers to the manual issue. All these manuals can be found in the TXCare Help.
Table 1 Manual References

Ref. Number Title

[1] XA-M801-&-* XTran Installation and Operation
[2Mgt] XA-M830-&-* TXCare Management Operation
[2Eth] XA-M831-&-* XTran Ethernet Services
[2Leg] XA-M832-&-* XTran Legacy Services
[2Net] XA-M833-&-* XTran Network Operation
[3b] XB-M840-&-* XTran Core Nodes: XT-2215-A
[4] XB-M803-&-* XTran Switching Module: CSM310-A/CSM540-A
[8] XA-M810-&-* XTran General Specifications
[100] XA-M828-&-* XTran Bandwidth Overview

XE-M844-E-4 Page 5 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

2. MODULE DESCRIPTION
2.1 Front Panel

LEDs
Socket Head 8 RJ-45 Port LEDs 8 RJ-45
Cap Screw 1 Gbps Ethernet 1 Gbps Ethernet
Ports without PoE Ports with PoE

Figure 1 Front Panel

2.1.1 Insert/Remove Module from Node

See ‘XTran Installation and Operation Manual’ Ref.[1] in Table 1.

2.1.2 LEDs
a. IFM LEDs
The meaning of the LEDs depends on the mode of operation (= boot or normal) in which this
L2 IFM currently is running. After plugging in the module or rebooting it, the module turns into
the boot operation, see Table 2. After the module has gone through all the cycles in the table
below (=rebooted successfully), the module turns into the normal operation, see LEDs in
Table 3.

Table 2 LED Indications In Boot Operation

Cycle PI PF FLT
1 ✓ --- ---

2 ✓ --- ✓
3 ✓ --- ---

✓ : LED is lit / --- : LED is not lit. The sub cycle times may vary. The entire boot cycle time [1→3] takes less than 1 minute.

Page 6 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

Table 3 LED Indications in Normal Operation

LED Color Status

PI (=Power Input) Not lit, dark +12V power input to the board not OK
Green +12V power input to the board OK
PF (=Power Failure) Not lit, dark power generation on the board itself is OK
Red power generation on the board itself is erroneous
FLT (=FauLT) Not lit, dark no other fault or error situation, different from PF, is active on the module
Red a fault or error situation, different from PF, is active on the module
1G Port (Port 1..16) Not lit, dark The link on port<port n°> is down
LA<port n°>
Yellow lit The link on port<port n°> is up, no activity
(=Link Activity)
Yellow blinking The link on port<port n°> is up, with activity
1G Port (Port 1..16) Dark 10 Mbps
S<port n°>
Orange,lit 1000 Mbps
(=Speed)
Green, lit 100 Mbps

2.1.3 Connectors
This module has following ports:
• Port1…16 = RJ45 Ethernet port: 10/100/1000Base-T Gigabit Ethernet copper port. Use
CAT5E shielded cables for 10/100Base-T and CAT6 shielded cables for 1000Base-T to
connect these ports.
Pin1 Pin8

RJ-45 Port
LEDs

LED La (=Link Activity) LED S (=Speed)

Figure 2 RJ45 Ethernet port

Table 4 RJ45 Ethernet port: Pin Assignments

Pin No. Signal 100/100Base-T Signal 1000Base-T

1 Transmit output (+) DA+
2 Transmit output (-) DA-
3 Receive input (+) DB+
4 --- DC+
5 --- DC-
6 Receive input (-) DB-
7 --- DD+
8 --- DD-

XE-M844-E-4 Page 7 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

2.2 Functional Operation

This L2 IFM performs following major tasks:

2.2.1 Media Module for Ethernet: Interfacing to a LAN Network

WAN ports interconnect nodes within the XTran network (MPLS-TP) whereas LAN ports
interconnect the nodes with the network. The L2 IFM has only LAN ports. Interconnecting
nodes on the WAN side must be done via LAN/WAN Ethernet IFMs (4-GC-LW, ...).
A LAN port talks Ethernet and a WAN port talks MPLS-TP. As a result, the node can serve as
an edge node (or LER = Label Edge Router) where traffic is received on a LAN port, mapped
into pseudowire and forwarded to the correct label switched path on a WAN port.
For a configured application service, the node can operate as a:
• LER = Label Edge Router or access node: The node is located on the edge between the LAN
and WAN. The node converts Ethernet into MPLS-TP and vice versa;
• LSR = Label Switching Router: The node is fully located in the WAN. The node has no end-
points for the configured application service, it only forwards MPLS-TP traffic via label
switched paths;

TXCare PC
(=XTran Management)
XT-2215-A Node

LSR

16-GEP-L IFM 16-GEP-L IFM

router LER LER router

XTran MPLS-TP
Network
LSR
LSR

LAN WAN LAN

Figure 3 General Example

Page 8 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

WAN: MPLS-TP (on fiber) → between XTran nodes

1G LAN: Ethernet (on copper) → external devices
10G LAN: Ethernet (on fiber) → external devices
40G LAN: Ethernet (on fiber) → external devices

1-40G-LW (WAN)
WAN (via 40G, QSFP on fiber)
4-10G-LW (LAN) 4-10G-LW (LAN)

XTran Node

IFM7: 1-40G-LW IFM6: 1-40G-LW

CSM Switch CSM Switch

CSM540-A ETH → MPLS-TP CSM540-A ETH → MPLS-TP

IFM11 IFM11
4-10G-LW 4-10G-LW
16-GEP-L (LAN) 16-GEP-L (LAN)

IFM14 IFM14
16-GEP-L 16-GEP-L

LAN1 LAN2 LAN3 LAN4

Figure 4 Detailed Example

2.2.2 I/O with the Central Switching Module (=CSM)

This L2 IFM receives Ethernet traffic via its front panel ports and forwards this to the CSM via
this L2 IFM back end ports on the CSM. The CSM does all the processing on this data
(synchronization, CRC checks, conversions, switching…). The resulting data will be forwarded
via the backplane to one of the IFMs in the node.

2.2.3 Ethernet Service

a. General
The access or end-points of this L2 IFM communicate over the XTran network via an Ethernet
service. This service must be configured via TXCare. This service can operate port or VLAN
based. An Overview can be found in the figure below. An overview of the L2/L3 IFMs is shown
in the ‘Protocol and feature support matrix’ in Ref.[2Net] in Table 1.

XE-M844-E-4 Page 9 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

Port Based Including L2/L3 IFMs = mixed = VLAN based (front→ back end) + Port based (back end → CSM)

VLAN Based Port Based

L2/L3 IFM CSM

VLAN A,B F A
XTran
B VLAN A,B
r a VFI 1 VLAN A,B
Port Based VLAN B o B
c VLAN C,D
n C VFI 2 VLAN C,D
(Mixed VLAN VLAN C,D t k
service) D

2 mixed services, 1 per back end port! 1 VFI per mixed service 2 Services

L2/L3 IFM CSM

VLAN Based: VLAN A,B F A
XTran
B
r VFI A VLAN A
Single VLAN VLAN B o B a
c
VLAN A,B,C,D
n VFI B VLAN B
(each VLAN its VLAN C,D t C k
VFI C VLAN C
own service) D
VFI D VLAN D

4 services on 1 back end port 1 VFI per VLAN 4 Services

IN: Add QinQ VLAN

OUT: Remove QinQ VLAN VLAN X = QinQ VLAN

IN
L2/L3 IFM CSM
VLAN Based: IN
XTran
VLAN A,B F A
Multi VLAN r Q a
B
VLAN X (A,B) VLAN Y (C,D)
VLAN B o B
in c VFI X VLAN X (A,B)
via QinQ n
VLAN C,D t C Q
k
VFI Y VLAN Y (C,D)
D
OUT OUT

2 services on 1 back end port 1 VFI per QinQ VLAN 2 Services

LAN WAN

L2/L3 IFM CSM

VLAN Based: XTran
VLAN A,B F A
Single VLAN r
B
a
VLAN B o B
Local Service n
VLAN C,D t C
c
k
(each VLAN its D
own service)

4 local services No service on back end port No VFI No Services

Figure 5 Ethernet Service Overview on L2/L3 IFM

b. Port Based (=Mixed Service)

Use this mode if all the traffic on a port must be transported transparently in one and the
same service. Each port based service will consume an entire back end port on this L2 IFM.
This means that no other service, either port based or VLAN based, can be configured on the
used back end port. Each port based service consumes one VFI in the CSM. This service is a
hybrid or mixed service that partially acts as a pure Port based on the WAN side (VLAN
unaware) and partially as a VLAN based (single VLAN) service on the LAN side. The single VLAN
services will be embedded (= child) in the port based service (=parent).

Page 10 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

c. VLAN Based: Single VLAN

Use this mode if each VLAN (ID) on a port must have its own service. Ethernet packets with
the configured VLAN ID will be forwarded in this service, other VLAN IDs and untagged packets
will be dropped. This behavior can be overruled by a more advanced VLAN processing in the
‘VLAN Tagging/Untagging’ feature in TXCare. This feature also supports VLAN translation
which replaces VLAN ID ‘x’ into VLAN ID ‘y’. Each back end port on this L2 IFM can carry
multiple VLAN based services. Each Single VLAN based service consumes one VFI in the CSM.
If you have many single VLAN based services originating in one node, it’s better to consider
Multi VLAN services for a more efficient usage of VFIs in the CSM.

d. VLAN Based: Multi VLAN / QinQ

With QinQ, a VLAN based service can carry multiple VLANs instead of just one. QinQ is a
feature that operates at the back end ports of this L2 IFM. For incoming traffic (IN: LAN to
WAN), this feature adds an outer VLAN (=QinQ VLAN with EtherType 0x8100) around the
existing VLANs resulting in double VLAN tagged Ethernet packets towards the CSM. For
outgoing traffic from the CSM (OUT: WAN to LAN), the QinQ VLAN is removed. Each back end
port on this L2 IFM can carry multiple VLAN based services. Each Multi VLAN based service
consumes one VFI in the CSM.

e. VLAN Based: Single VLAN Local Service

A Single VLAN Local service:
• Is a VLAN based service between only the front ports on L2 IFMs;
• Does not use back end ports, tunnels, WAN ports or the XTran network. As a result, this
service does not consume network bandwidth;
• Requires an external cable if IFMs of different nodes participate in the service.

f. Configuration
See Ref. [2Eth] in Table 1 for more configuration information in TXCare.

2.2.4 Voice Service

The ports of this L2 IFM can be used in a Voice service. This service must be configured via
TXCare. See Ref. [2Leg] in Table 1 for more configuration information on a Voice service in
TXCare.

2.2.5 Layer2: VLAN handling

Both port based and VLAN based Ethernet services are supported in which VLANs can be
handled (tagging/untagging behavior, QoS, ...). See Ref. [2Eth] in Table 1 for more
configuration information in TXCare.

2.2.6 Layer2: QoS (=Quality of Service)

Each Ethernet service can be assigned its own quality of service (bandwidth, priority,
burstsize). See Ref. [2Eth] in Table 1 for more configuration information in TXCare.

XE-M844-E-4 Page 11 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

2.2.7 Layer2: MSTP (=Multiple Spanning Tree)

MSTP originally defined in IEEE 802.1s and later merged into IEEE 802.1Q-2003, defines an
extension to RSTP to further develop the usefulness of VLANs. This MSTP instance configures
a separate Spanning Tree for all VLANs included in this instance and blocks all but one of the
possible alternate paths within each Spanning Tree.
If there is only one VLAN in the network, single (traditional) STP works appropriately. If the
network contains more than one VLAN, the logical network configured by single STP would
work, but it is possible to make better use of the alternate paths available by using an alternate
spanning tree for different VLANs or groups of VLANs. More than one VLAN can be assigned
to one MST instance. Multiple MST regions can be operational, each having its own MSTP
instances. The IST (MSTP) instance monitors the entire Region, the CST (MSTP) instance
monitors the links between the regions.
MSTP in a port based service is supported network wide whereas MSTP in a VLAN based
service is supported only locally (not over this L2 IFM back end ports). CAUTION: using MSTP
over a VLAN based service over the back end ports causes a loop!
MSTP is fully supported on L2 IFMs. By default, MSTP is enabled on L2 IFMs even if no MSTP
is configured in TXCare. See Ref. [2Eth] in Table 1 for more configuration information in
TXCare.
Block port = Avoid loop
Region1

MSTP1

L2/L3 ETH L2/L3 ETH

11 14

MSTP2

10 12 15
L2/L3 ETH L2/L3 ETH L2/L3 ETH
MSTP1

Region2

Figure 6 MST Example

2.2.8 Layer2: Link Aggregation/LAG (=Link Aggregation Group)

Link Aggregation is the bundling (=aggregation) of multiple physical Ethernet ports between a
source and destination side into one combined logical Ethernet port. A LAG is a combination
of multiple Ethernet LAN ports with the same port speed within one logical port group,
maximum 8 ports per LAG and 8 LAGs per node. The Link Aggregation is the communication
between two LAGs. E.g. one LAG in one XTran node and the second LAG in a third party
switch/application. For 1G ports, all the ports of the source and destination LAG must be in
autonegotiation.
NOTE: LACP (=Link Aggregation Control Protocol) is supported: LACP provides a method to
control the bundling of several physical ports together to form a single logical
channel. LACP allows a network device to negotiate an automatic bundling of links by

Page 12 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

sending LACP packets to the peer (directly connected device that also implements
LACP).
NOTE: LAG on the back end ports is not supported.

LAG is configured in TXCare. See Ref. [2Eth] in Table 1 for more configuration information in
TXCare and an overview of all the IFMs/ports that can be combined in the LAG.

Figure 7 Link Aggregation and LAGs

2.2.9 Layer2: IGMP Snooping (IGMP = Internet Group Management Protocol)

IGMP snooping is designed to prevent hosts on a local network from receiving traffic for a
multicast group they have not explicitly joined. Via IFMs that support IGMP snooping (see
support matrix in Ref. [2Net] in Table 1), it provides the XTran nodes with a mechanism to
diminish multicast traffic from links that do not contain a multicast listener (an IGMP client).
The XTran node will, by default, flood multicast traffic to all the ports in a broadcast domain
(or the VLAN equivalent). Multicast can cause unnecessary load on host devices by requiring
them to process packets they have not solicited.

CAUTION: IGMP Snooping is MAC based on L2 IFMs.

IGMP snooping allows the XTran node to only forward multicast traffic to the ports that have
solicited them. IGMP snooping is not a protocol but a layer 2 optimization for the layer 3 IGMP
protocol. IGMP Snooping takes place internally on IFMs that support it.
Snooping is therefore especially useful for bandwidth-intensive IP multicast applications such
as IPTV. IGMP Snooping is configured in TXCare. See Ref. [2Eth] in Table 1 for more
configuration information in TXCare.
NOTE: The mentionned PIM (=Protocol-Independent Multicast) and IGMP protocol in the
figure below is only supported on the L3 IFMs. An overview of the L3 IFMs is shown
in the ‘Protocol and feature support matrix’ in Ref.[2Net] in Table 1.

XE-M844-E-4 Page 13 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

MC = Multicast / RP = Rendez-Vous Point / BSR = Bootstrap Router / Q = Querier

MC1 Source MC7 Source

MC2 Source

IGMP
MC1..7
L3 ETH IGMP L2/L3 ETH Host
IGMP
Q 14
Snooping
Receiver
RP

PIM
IGMP
BSR
Q 15
IGMP
Snooping
MC1..6
L3 ETH L3 ETH L2/L3 ETH Host
Receiver

MC3 Source MC5 Source

MC4 Source MC6 Source

Figure 8 PIM/IGMP/IMGP Snooping Overview

2.2.10 Storm Control on Ethernet LAN Port

A traffic storm is the growing of excessive network traffic due to Ethernet packets flooding the
LAN. Such a storm can for example occur because of a data loop in the network due to no or
misconfiguration of redundancy protocols (MSTP, RGERP, MRP, …). These storms degrade the
network performance and must be avoided whenever possible. The storm control feature:
• is an extra protection against these traffic storms;
• can be configured on the IFM ports;
• limits the amount of unlearned received data (Unicast, Broadcast, Multicast) on the LAN
port ingress or input side;
• limits the amount of transmitted data (all data) on the LAN port egress or output side;
• Data that exceeds the configured limitations will be dropped. As a result, a possible data
storm cannot overload the node processor or the node will limit outgoing data.
See Ref. [2Eth] in Table 1 for more configuration information in TXCare.

2.2.11 Port Mirroring

Port Mirroring is a network debugging or monitoring feature. It is used in the XTran node to
send a copy of network packets seen on a source port (=mirrored port) to a destination port
(=mirroring port). This feature can be used for network appliances that require monitoring of
network traffic, such as an intrusion-detection system etc... Port mirroring is supported when
source and destination ports are located in the same L2 IFM. See Ref. [2Net] in Table 1 for
more configuration information in TXCare.

Page 14 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

Figure 9 Port Mirroring Example

2.2.12 RGERP (=Redundant Gigabit Ethernet Protocol) Support

An ETS (=Industrial Ethernet Switch) ring network can be physically connected to the XTran
network via ports on this IFM. RGERP is used in ETS ring networks to avoid broadcast storms
and Ethernet loops. See Ref. [2Eth] in Table 1 for more configuration information in TXCare.

TXCare XTran Node

RGERP
Entry Node +
Ring port

XTran MPLS-TP XTran MPLS-TP

Network Network
RGERP
Entry Node +
Ring port

Monitored Link RGERP Access Ring RGERP Access Ring

RGERP interrupting the loop

by blocking the port
Access switches
running RGERP
RGERP Ring Master

Figure 10 RGERP: General Example

2.2.13 MRP (=Media Redundancy Protocol) Support

The MRP is a protocol (IEC 62439-2) especially designed for industrial applications which need
a predictable fail-over time. This protocol can only be used in a ring-topology network and
makes sure that the ring network stays loop-free. MRP does in ring networks what spanning
tree does in meshed networks but with much faster convergence times. The ring has one
selected MR Manager (MRM) and a number of MR Clients (MRC). The two XTran nodes act as
MRC. See Ref. [2Eth] in Table 1 for more configuration information in TXCare.

XE-M844-E-4 Page 15 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

TXCare XTran Node

MRP
Entry Node +
Ring port

XTran MPLS-TP XTran MPLS-TP

Network MRC Network
MRP
Entry Node + MRC
Ring port

Monitored Link MRP Access Ring MRP Access Ring

MRC MRC MRM MRC

Access switches
running MRP
MRM interrupting the loop
by blocking the port

Figure 11 MRP: General Example

2.2.14 PoE (=Power Over Ethernet)

NOTE: An NSM-A is required to deliver PoE.
PoE is a technology that allows a Powered Device (=PD, e.g. IP telephones, IP cameras etc.) to
receive power from ‘Power Sourcing Equipment’ (=PSE, e.g. the XTran node). An example with
PoE on/off can be found in Figure 12.
XTran nodes are able to deliver PoE when one (or two) external PoE PSU(s) is (are) connected
to the NSM via the PoE connectors. A possible external PoE PSU and how to connect it can be
found in the manual Ref. [3b], see Table 1.
The PD receives power in parallel to data, over the existing CAT-5 Ethernet infrastructure. PoE
integrates data and power on the same cable, it keeps the structured cabling safe and does
not interfere with concurrent network operation.
PoE delivers a minimum of 48V of DC power over shielded/unshielded twisted-pair wiring for
terminals consuming less than 25.5 Watts of power.
Before the power is delivered to a connected device, a protocol measures whether that device
is a PoE device and how much power it needs (power classification). If required, the necessary
power will be delivered by the PSE with a maximum of 32 Watts per port.
PoE is supported on port [9..16] of the 16-GEP-L module. All these ports can deliver power
according to the 802.3af (PoE) and 802.3at (PoE+) standard.
Via TXCare it is possible to enable/disable PoE per port and to verify which ports in each node
are PoE enabled;
Power management is supported, i.e. the XTran node decides in an intelligent way which PoE
ports will get power and which ones will not. There are a lot of possible scenarios in which
power management must tune its delivered power on each port. Some configuration/status
parameters in TXCare used by power management are:
• External PoE PSU power;
• Available power budget;

Page 16 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

• Power Priority / Port Priority;

• Power Class (class 0, 1, 2, 3, 4 configured and detected);
• Power management also offers PoE diagnostics in TXCare.

PoE Power & Data

Data
Power

External PoE PSUs:

AC/DC: V30812-A5020-A97 PoE Connector Cable
DC/DC: V30812-A5020-A98 (S30927-C1-A30)
NSM-A
56 56
VDC VDC

PoE
16-GEP-L

External PSU

PoE Not Supported PoE Supported

Figure 12 PoE Example

2.2.15 Hardware Edition

The hardware edition of this IFM has been factory set and can not be changed! It can be read
out via TXCare, see Ref. [2Mgt] in Table 1.

XE-M844-E-4 Page 17 of 19
XTran Interface Module: 16-GEP-L eXcellence in TRANsport

2.3 Onboard Interfaces

Figure 13 16-GEP-L: Side View

3. MODULE SPECIFICATIONS
3.1 General Specifications
For general specifications like temperature, humidity, EMI... see Ref.[8] in Table 1.

3.2 Other Specifications

Table 5 Other Specifications

Description Value
Weight 0.415 kg / 0.91 lb
MTBF 72 years at 25°C/77°F
Power Consumption 14.0 W (measured at 25°C/77°F, with data transport)
Module Size width: 186 mm / 7.3 inches
height: 43.05 mm / 1.69 inches
depth: 195 mm / 7.68 inches

3.3 Ordering Information

• 16-GEP-L: S30924-Q220-X101

Page 18 of 19 XE-M844-E-4
eXcellence in TRANsport XTran Interface Module: 16-GEP-L

4. ABBREVIATIONS
BE Back End Port
CE Conformité Européenne
CSM Central Switching Module
EMI Electromagnetic Interference
ETS Industrial Ethernet Switch
FLT Fault
FP Front Port
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IFM InterFace Module
IGMP Internet Group Management Protocol
LACP Link Aggregation Control Protocol
LAG Link Aggregation
LAN Local Area Network
LER Label Edge Router
LSA Link State Advertisement
LSR Label Switching Router
MRC Media Redundancy Clients
MRM Media Redundancy Manager
MRP Media Redundancy Protocol
MSTP Multiple Spanning Tree
MTBF Mean Time Between Failures
PIM Protocol-Independent Multicast
PoE Power Over Ethernet
QoS Quality of Service
RGERP Redundant Gigabit Ethernet Ring Protocol
TXCare XTran Management System
VFI Virtual Forwarding Interface
VID VLAN ID
VLAN Virtual LAN
WAN Wide Area Network
XTran eXcellence in Transport

XE-M844-E-4 Page 19 of 19