342-90001-PS

Issue 1.1
August 2019

JunglePAX

Technical Practice
and
Installation Manual

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 2

JunglePAX

Technical Practice and Installation Manual

Copyright © GE Multilin Inc. 2016-2018, All Rights Reserved

The copyright of this document is the property of GE Multilin Inc. This document must not be
copied, reprinted or reproduced in any material form, either wholly or in part, without the written
consent of GE Multilin Inc.

GE Multilin Inc. reserves the right to make changes and modifications to any part of this
document without notice.

GE Multilin Inc. is not responsible for any damages or losses incurred as a result of out-of-date or
incorrect information contained in this document.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 3

WARNINGS
HAZARDOUS VOLTAGE: To completely isolate JunglePAX from input power source,
the input power to both power supply modules needs to be disconnected.

DISCONNECT DEVICE: A switch or circuit-breaker shall be included in the end-use

equipment or building installation. The switch shall be in close proximity to the
equipment and within easy reach of the operator. The switch shall be marked as the
disconnecting device for the equipment.

Ground terminal of JunglePAX should be connected directly to the installation’s

protective earth ground. Use 12 AWG (3.31 mm2) wire for this connection.

The laser radiation is infrared and invisible. Do not attempt to look into the laser.
Use only laser-safe SFP modules (per IEC 60825-1 and IEC 60950-1).

Exercise extreme caution when connecting power supply inputs to voltages higher
than 60 V.

The SFP cage, heat sink and heat spreader on the Core Unit may be very hot!
The heat sink and heat spreader on the Power Supply Unit may be very hot!

This product is to be installed only in restricted access areas (dedicated equipment

rooms, electrical closets, or the like).

ATTENTION
DANGER DE TENSION: La tension des deux blocs d’alimentation doit être coupée
afin d’isoler complètement le JunglePAX de la source d’alimentation.

DISPOSITIF DE DÉCONNEXION : L’équipement d’utilisation finale ou l’installation du

bâtiment devront être équipés d’un disjoncteur. Le commutateur doit être à étroite
proximité de l’équipement et facilement accessible par l’opérateur. Le commutateur
doit être marqué comme dispositif de déconnexion pour l’équipement.

La borne de terre du dispositif JunglePAX doit être directement raccordée à la terre

de protection (masse) de l’installation. Utiliser un câble 12 AWG de 3.31 mm2 pour le
raccordement.

Le rayonnement laser est infrarouge et invisible. Ne tentez pas de regarder le

faisceau laser. N’utiliser que des modules laser SFP sécuritaires (selon les normes
CEI 60825-1 et CEI 60950-1).

Faire preuve de précaution lors de la connection du block d’alimentation à une

tension supérieure à 60 V.

Le réceptable du module SFP, le dissipateur et le répartiteur de chaleur de l’unité

centrale peuvent être très chaud! Le dissipateur de chaleur et le répartiteur de
chaleur du bloc d’alimentation peuvent être très chaud!

Ce produit doit être installé uniquement dans des zones d’accès restreint (local
technique dédié, armoires électriques ou autres).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 4

TABLE OF CONTENTS
SECTION PAGE
1. INTRODUCTION .................................................. 8
Handling and Packing ..........................................................................8
Earthing.................................................................................................9
Class A Compliance .............................................................................9
Revision History ...................................................................................9

2. MPLS .................................................................. 10
What is MPLS? ....................................................................................10
MPLS Operation ..................................................................................10
MPLS Routers .................................................................................... 11
Label-Switched Paths ....................................................................... 11
Routing ............................................................................................... 12
LSP Protection ................................................................................... 13
Pseudowires ........................................................................................13
VPWS ...................................................................................................14
VPLS .....................................................................................................14
MPLS-TP ..............................................................................................15

3. PRODUCT OVERVIEW ...................................... 17

Features and Benefits .........................................................................17
Use of MPLS-TP Technology ............................................................ 17
Enhanced MPLS-TP Features ........................................................... 18
Synchronous Ethernet for Tight Jitter Control ............................... 18
Integrated MPLS-TP Converged Platform ....................................... 18
Operation in Harsh Environment ..................................................... 18
Extended Operating Temperature Range ........................................ 18
Wide Range of Applications ............................................................. 19
Flexible Network Architecture .......................................................... 19
Interoperation with MPLS Network Elements ................................. 19
Interoperation with JungleMUX DS0 / 64 kbps Level Interface
Units.................................................................................................... 19
Comprehensive OAM ........................................................................ 19
Integrated Network Management ..................................................... 20

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 5

Scalability ........................................................................................... 20
Flexible Bandwidth Utilization .......................................................... 20
Hot Swappable Units ......................................................................... 20

4. PRODUCT STRUCTURE ................................... 21

5. EQUIPMENT SHELF .......................................... 23

Backplane ............................................................................................24

6. CORE UNIT......................................................... 27
Interfaces .............................................................................................28
Fiber-Optic WAN Ports ...................................................................... 28
NMS Ports .......................................................................................... 30
Serial Craft Interface Port ................................................................. 30
USB Port ............................................................................................. 30
Timing Connections .......................................................................... 31
Micro SD Card Socket ....................................................................... 31
LED Indications ...................................................................................31
Unit/System Status LEDs .................................................................. 31
WAN Port Status LEDs ...................................................................... 31
Core Unit Insertion ..............................................................................32
Core Unit Ejection ...............................................................................33

7. DC POWER SUPPLY UNIT ................................ 34

Overview ..............................................................................................34
Faceplate LED .....................................................................................35
Faceplate Connections .......................................................................35
DC Power Supply Unit Insertion ........................................................36
DC Power Supply Unit Ejection .........................................................36

8. AC POWER SUPPLY UNIT ................................ 38

Overview ..............................................................................................38
Faceplate LED .....................................................................................38
Faceplate Connections .......................................................................39
AC Power Supply Unit Insertion ........................................................40
AC Power Supply Unit Ejection .........................................................41

9. ACCESS UNITS.................................................. 42
General Information ............................................................................42

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 6

Access Unit LED Indications ............................................................ 42

Access Unit Insertion ........................................................................ 43
Access Unit Ejection ......................................................................... 45
Access Unit Reset ............................................................................. 45
SFP Ethernet Access Unit (EF-4A) ....................................................46
SFP Port LED Indications ................................................................. 47
RJ-45 Ethernet Access Unit (EC-4A) .................................................48
RJ-45 Port LED Indications .............................................................. 48
T1/E1 Unit (T1E1-4A) ...........................................................................50
T1/E1 Port LED Indications ............................................................... 50
CBUS Unit (CBUS-4A) .........................................................................52
CBUS Port LED Indications .............................................................. 52
CBUS Connection to a JungleMUX/TN1U Expansion Shelf .......... 53
CBUS Connection to a TN1Ue Expansion Shelf ............................. 55

10. TDM DATA PACKETIZING .............................. 56

TDM Port Mapping ..............................................................................56
Bundles ................................................................................................57
TDMoP Delays .....................................................................................59
Bundle Hairpinning .............................................................................60

11. PROTECTION SWITCHING ............................. 61

“1+1” vs. “1:1” Path Protection Schemes .........................................61
Types of Access Ports ........................................................................64
Access Port Switching (1+1) ..............................................................65
Pseudowire Switching (1:1)................................................................68
1:1 Protection Switching for Pseudowires Carrying VPWS Services
............................................................................................................. 68
Protection Switching for Pseudowires Carrying VPLS Services .. 71
Hardware Redundancy .......................................................................74
Protection Switching in Various Network Topologies .....................74

12. FREQUENCY SYNCHRONIZATION................ 75

Synchronization Status Messaging ...................................................76
JunglePAX Network Synchronization Engineering Rules ...............78
Sync Engineering Examples ..............................................................79
Example 1: Dual-homed rings .......................................................... 79
Example 2: Added “tie” connection between dual-homed rings . 81
Example 3: Two rings with parallel tie links .................................. 81
Example 4: Meshed network with spurs and parallel links ........... 82
Synchronization of Main Loop with Single Headend Node .............83
Timing of a Main Loop with Two Headend Nodes ............................86

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 7

13. SPECIFICATIONS ............................................ 88

14. ORDERING INFORMATION ............................ 93

APPENDIX A .......................................................... 94
TDMoIP .................................................................................................94
TDMoIP Format ....................................................................................94
Delay ....................................................................................................95
Timing Recovery .................................................................................96
Packet Loss .........................................................................................96

APPENDIX B .......................................................... 98
List of Figures .....................................................................................98
List of Tables ......................................................................................100

APPENDIX C ......................................................... 101

List of Acronyms ................................................................................101

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 8

1. INTRODUCTION

JunglePAX is a purpose-built fiber-optic transport solution for high-performance

industrial communication networks serving mission-critical and time-sensitive
services within harsh utility environments.

The platform ensures private, secure and reliable communication between

access sites and guarantees performance over backhaul networks for protection
and/or control.

The JunglePAX has been designed based on MPLS-TP standard for superior
packet delivery performance within utility-specific operational and environmental
conditions thus addressing their communication challenges and meeting their
future business needs.

Customer inquiries for information contained in this manual should be directed to

JunglePAX Product Line Management. GE Multilin appreciates notification of
any possible errors or omissions contained herein.

This manual provides the overview of JunglePAX hardware, its features and
operation. It also briefly describes the basic concepts of the underlying
technology.

Handling and Packing

Equipment with Electrostatic Discharge Sensitive (ESDS) devices or components

must be shipped in protective containers and necessary handling precautions
observed otherwise all warranties, expressed or implied, will be considered null
and void.

The following Electronic Industries Association (EIA) attention label appears on

all GE Multilin EAS schematics and should be attached on all containers used for
ESDS items to alert personnel that the contents requires special handling.

ATTENTION
OBSERVE PRECAUTIONS
FOR HANDLING HANDLE & ASSEMBLE
ELECTROSTATIC PER 562-48043-01
SENSITIVE
DEVICES
THIS UNIT CONTAINS STATIC SENSITIVE DEVICES

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 9

Earthing

The JunglePAX shelf must be connected to protective earth (ground) at

all times. Connect one of the earth terminals provided on the top rear
corners of the shelf (marked with the symbol shown here) to the rack
frame or nearest available protective earthing terminal using an earth
wire or braid. The diameter of the copper conductor used for grounding must not
be smaller than 2.05 mm (12 AWG, 3.31 mm2). Use TE Connectivity 170785-2
(http://www.te.com/usa-en/product-170785-2.html) to connect the ground
wire/braid to the earth terminal.

Class A Compliance

This equipment has been tested and found to comply with the limits for
a Class A digital device pursuant to Part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will
be required to correct the interference at his own expense.

Revision History

Issue No. Issue Date Details of Change

Draft 1 Jan 2016 Document created. Preliminary release.
Draft 2 April 2016 Added regulatory statements.
Draft 3 Aug 2016 Document updated. Added sections 11, 12 & 13.
Draft 4 Jan 2018 Document updated. Added AC Power Unit.
Configuration moved into separate manual.
Issue 1 Feb 2018 Minor corrections.
Issue 1.1 Aug 2019 Updated specifications

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 10

2. MPLS

What is MPLS?

Multiprotocol Label Switching (MPLS) is a mechanism in high-performance

packet-based telecommunications networks that quickly and efficiently directs
data from one network node to the next based on short path labels. MPLS was
designed to provide a unified data-carrying service for both circuit-based and
packet-switching clients.

The labels assigned to data packets identify virtual links (paths) between ingress
and egress nodes in an MPLS network. Packet-forwarding decisions are made
solely on the contents of this label, without the need to examine the packet itself.

MPLS operates at a layer that is generally considered to lie between traditional

definitions of layer 2 (data link layer) and layer 3 (network layer). Therefore, it is
often referred to as a "layer 2.5" protocol.

MPLS Operation

MPLS works by prefixing packets with an MPLS header, containing one or more
labels. This is called a label stack. Each label in the label stack has 4 bytes and
contains the following four fields:
- A 20-bit label value.1
- A 3-bit Traffic Class field for QoS (Quality of Service) priority.2
- A 1-bit Bottom of Stack flag. (If this bit is set, this label is the last in the
label stack.)
- An 8-bit TTL (time to live) field.

In the case of MPLS encapsulation of an Ethernet frame, the preamble and

Frame Check Sequence (FCS) are stripped. A new preamble and FCS are
added for the resulting MPLS frame. The presence of MPLS label is indicated
through the use of EtherType values 0x8847 and 0x8848 for unicast and
multicast connections, respectively.

1 A label with the value of 1 represents the router alert label.

2 May also carry ECN (Explicit Congestion Notification).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 11

Figure 1: Unicast MPLS packet format (shown without preamble and FCS)

MPLS Routers

There are two types of MPLS routers.

A Label Edge Router (LER) or Provider Edge (PE) router is a router that
operates at the edge of an MPLS network and acts as an entry/exit point to/from
the MPLS network. LERs push an MPLS label onto each packet that enters the
MPLS network and pop it off each packet that leaves it.

An MPLS router that performs routing based only on the label is called a Label
Switching Router (LSR), a transit router or Provider (P) router. This is a type of
router located in the middle of an MPLS network. It is responsible for switching
the labels used to route packets.

When an LSR receives a packet, it uses the label included in the packet header
as an index to determine the next hop on the label-switched path (LSP) and a
corresponding label for the packet from a lookup table. The old label is then
removed from the header and replaced with the new label before the packet is
forwarded. This action is called label swap.

Inbound Label Outbound Label Outbound Interface

172 651 1
104 738 2
64 916 1
212 361 2

Figure 2: Example of label lookup table at LSR

Label-Switched Paths

A Label-Switched Path (LSPs) is a path through an MPLS network that

interconnects two LERs.1 LSPs are established by the network operator and
they can be set either statically or dynamically by a signaling protocol.

1 Although most LSPs are point-to-point (P2P), there are also LSPs that are point-to-multipoint
(P2MP), which are mainly used for multicasting purposes.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 12

Note that LSPs are unidirectional. As bidirectional communication is typically

desired, signaling protocols are capable of automatically setting up an LSP in the
other direction. The two associated LSPs carrying traffic in opposite directions
are usually referred to as a bidirectional LSP or an MPLS tunnel.

Figure 3: Example of a label-switched path

Routing

When an unlabeled packet enters the ingress router and needs to be passed on
to an MPLS tunnel, the router first determines the forwarding equivalence class
(FEC) for the packet based on the packet’s QoS and then inserts (pushes) one or
more labels in the packet's newly created MPLS header. The packet is then
passed on to the next hop router along this tunnel.

When a labeled packet is received by an MPLS router, the topmost label is

examined. Based on the contents of the label, a swap, push or pop operation is
performed on the packet's label stack. Routers usually have prebuilt lookup
tables that tell them what kind of operation to do based on the topmost label of
the incoming packet so they can process the packet very quickly.
- In a swap operation the label is swapped with a new label, and the packet is
forwarded along the path associated with the new label.
- In a push operation a new label is pushed on top of the existing label,
effectively "encapsulating" the packet in another layer of MPLS. This allows
hierarchical routing of MPLS packets i.e. tunneling MPLS packets through
external MPLS infrastructures (“carrier-of-carriers” model), by creating MPLS
VPNs.
- In a pop operation the label is removed from the packet, which may reveal an
inner label below. This process is called "decapsulation". If the popped label
was the last on the label stack, the packet "leaves" the MPLS tunnel.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 13

During these operations, the contents of the packet below the MPLS label stack
are not examined. MPLS transit routers (LSRs) typically need only to examine
the topmost label on the stack. Forwarding of the packet is done based only on
the contents of the labels.

At the egress router, when the last label has been popped, only the payload
packet remains. The egress router must therefore have routing information for
the packet's payload, since it must forward it without the help of label lookup
tables. An MPLS transit router has no such requirement.

LSP Protection

To achieve protection of P2P LSP paths, primary (working) and secondary

(protect) LSP paths are created.

Figure 4: Working and Protect LSP

The alternate path can be pre-configured (pre-signaled), in which case the

switchover is fast but the reserved bandwidth is unavailable for other LSPs
during normal conditions. On the other hand, for a signaled alternate path, there
is a delay associated with source-notification and LSP construction, which makes
the switchover longer.

Pseudowires

Pseudowire (PW) is a mechanism that emulates the essential attributes of a

point-to-point service while it is being transported over a packet-switched network
(PSN). PWs are usually bidirectional.

An MPLS tunnel is established to provide a direct forwarding path for the PW

between the communicating LERs. As such, the PW traffic is invisible to the
packet-switched network (PSN) nodes, and consequently, the PSN is invisible to
the communicating CEs.

For PW transport over MPLS, the tunnel label is known as the "outer" label, while
the PW label is known as the "inner" label.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 14

Pseudowires can be used to deliver two types of services to end users: virtual
private wire service (VPWS) and virtual private LAN service (VPLS).

VPWS

Virtual Private Wire Service (VPWS)1 is a way to provide Ethernet-based point-

to-point communication over MPLS networks. With VPWS, the provider delivers
the virtual equivalent of a leased line.

VPLS

Virtual Private LAN Service (VPLS) is a way to provide Ethernet-based

multipoint-to-multipoint communication over MPLS networks. With VPLS,
different sites can share an Ethernet broadcast domain through the use of
pseudowires.

VPLS allows any-to-any (multipoint) Layer 2 connectivity. It is essentially

designed for applications that require multipoint or broadcast access.

In a VPLS, the local area network (LAN) at each site is extended to the edge of
the provider network. The provider network then emulates a switch or bridge to
connect all of the customer LANs to create a single bridged LAN. Since VPLS
emulates a LAN, full mesh connectivity is often required.2

PEs participating in a VPLS-based VPN must appear as an Ethernet bridge to

connected customer edge (CE) devices.

When a PE receives a frame from a CE, it inspects the frame and learns the CE's
MAC address, storing it locally along with LSP routing information. It then checks
the frame's destination MAC address. If it is a broadcast frame, or the MAC
address is not known to the PE, it floods the frame to all PEs in the mesh.

Loop avoidance is arranged by ensuring that PE never forwards a frame received

from a PE to another PE.

In case of failure, traffic is automatically routed along available backup paths in

the service provider's network.

1Also referred to as Virtual Leased Line (VLL).

2For some VPLS applications, full mesh is not required. In SCADA networks, bridging between
RTUs is not needed.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 15

MPLS-TP

Transport networks have been traditionally built using Time Division Multiplexed
(TDM) SONET/SDH devices. These are becoming ineffective and costly in
today's packet-oriented world, which is driving service providers to deploy more
packet-based equipment in their transport networks.

Packet technology, however, did not offer the resilience, reliability, manageability
and operational simplicity of SONET/SDH that carriers demand. These include:
- In-band OAM functions to detect and isolate faults
- Fast (<50 ms) protection and restoration, to minimize traffic loss due to faults
- End-to-end QoS.
- Data Plane non-reliant on Control Plane.

MPLS-TP (Multiprotocol Label Switching - Transport Profile) addresses these

deficiencies, providing the same QoS, protection and restoration, and OAM
inherent to SONET/SDH in a way that has a familiar look and feel for network
operators.

In short, MPLS-TP is a variant of the MPLS protocol designed for transport

networks and it is based on the same architectural principles of layered
networking used in trusted transport network technologies like SONET, SDH and
OTN. Table 1 summarizes the characteristics of MPLS-TP.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 16

MPLS MPLS-TP
Control Plane Dependency No Control Plane required
- Fast re-convergence and no dependencies
- Forwarding is independent of IP to avoid
complex routing and control protocols
- Physical separation of the control and
management planes from the data plane
(packet forwarding continues in the absence
of the control plane)
- MPLS-TP data plane is a subset of MPLS
data plane as defined by IETF
- Can interoperate with existing IETF MPLS
and IETF PWE3 control and data planes
without requiring a gateway
- Data plane must support 1+1 protection
switching, revertive and non-revertive
Unidirectional paths Supports unidirectional, co-routed bidirectional,
and associated bidirectional point-to-point
transport paths. (Co-routed bidirectional paths
ensure path symmetry.)
Ring support not mandated Explicit support of ring topologies to reduce
(Protection switching is network complexity.
dependent on Interior - Supports 1+1 and 1:1 protection.
Gateway Routing Protocol) - Switching time must be within 50 ms from the
moment of fault detection in a 16-node ring
with less than 1200 km of fiber.
Connectionless Connection-oriented with traffic engineering
capabilities.
- Must support traffic-engineered point-to-point
(P2P) and point-to-multipoint (P2MP)
transport paths.
- Must support static provisioning
Out-of-Band OAM In-band OAM (“fate sharing”)
- OAM-triggered protection switching
- Mandated use of BFD (Bidirectional
Forwarding Detection) protocol.

Table 1: MPLS vs MPLS-TP

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 17

3. PRODUCT OVERVIEW
JunglePAX is a utility-grade MPLS-TP device designed specifically for network
operations requiring mission-critical and time-sensitive communications within
harsh substation environments. It uses an optimized version of MPLS-TP that
provides determinism for secure and dependable packet transport.

JunglePAX is a transport-quality multiplexer that converges PDH/TDM, Ethernet

and IP-based traffic over a connection-oriented next-generation MPLS-TP fiber-
optic network. It is a simple “one-box multiplexer solution” combining MPLS-TP
packet transport with emulated TDM T1/E1 access and 64 kb/s primary access
circuits. The functionality normally provided by a T1/E1 primary access
multiplexer has been included in JunglePAX thus providing an integrated
solution. This unique approach allows the user to support legacy interfaces
alongside native packet services reliably from a single platform.

JunglePAX features low power consumption requiring no active cooling and

extended temperature operating range (-20ºC to +60ºC) make it ideal for
applications in uncontrolled environments normally found in transportation,
mining, oil & gas and power substation environments. JunglePAX is designed for
continuous operation with minimum or no maintenance in those harsh
environments. The remote monitoring functionality through its network
management system (NMS) allows the operator to remotely monitor the alarm
status and performance conditions of all nodes.

Features and Benefits

Use of MPLS-TP Technology

A connection-oriented Layer 2.5 packet transport technology derived from the

MPLS standard. TP shares the label-based forward classes, but without the
associated complexity of requiring Layer 3 routing tables or control protocols and
without the dependency of any management or control plane. The SONET/SDH-
like OAM (Operations, Administration and Maintenance) within band
(accompanying the operational traffic) ensures that MPLS-TP OAM shares the
same fate as the traffic to quickly detect and initiate recovery triggers within 50
ms. In addition to supporting point-to-multipoint label switched paths, MPLS-TP
offers transmit and receive path association (co-routing) to ensure symmetry is
maintained, which is essential for applications that can be sensitive to
asymmetrical delays such as operational protection and control.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 18

Enhanced MPLS-TP Features

Purpose-built for high-performance industrial communication networks requiring

mission-critical and time-sensitive communications within harsh utility
environments. JunglePAX represents an optimized version of MPLS-TP that
provides determinism for secure and dependable utility applications. Inclusion of
fully redundant custom hardware offers 1+1 protection for fast line protection
switching (<10 ms).

Synchronous Ethernet for Tight Jitter Control

Layer 1 clock signaling is extended across the entire MPLS-TP infrastructure

utilizing built-in SyncE and IEEE 1588 capabilities. SyncE is fundamental to
carrying latency sensitive TDM traffic over a packet network. Hardware
additions within the JunglePAX that control jitter in both working and protect
paths are essential, not optional. The JPAX solution provides less than 30
microseconds delay for intra-nodal traffic and less than 4 milliseconds edge-to-
edge delay for TDM services. Precision timing is offered with less than 1
microsecond accuracy.

Integrated MPLS-TP Converged Platform

JunglePAX supports high bandwidth differentiated IT services over a packet-

switched network like video and reliably transports TDM and 64 kb/s for voice,
serial data and specific relay interfaces like ITU G.703 (64kb/s), IEEE C37.94,
RS-232 Mirrored Bit and Direct Transfer Trip (DTT) for tele-protection
applications.

Operation in Harsh Environment

JunglePAX has been designed for utility applications and is designed to meet
SWC (Surge Withstand Capability), Fast Transient, RFI (Radio Frequency
Interference) and Zone 4 Earthquake specifications that are applicable to all
power utilities.

The product has been built to work in remote locations, which required additional
measures to prevent local wildlife liquid and solid droppings from penetrating the
chassis.

Extended Operating Temperature Range

JunglePAX does not require a forced cooled environment or fans for it to operate.
The temperature range is -20°C to +60°. Fans in substation environments can

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 19

be very troublesome due to fine airborne particulates found in field substation

environments. Fans filters require routine maintenance and can become easily
clogged, which could result in overheating of the equipment. Fans have been
ruled out in the latest IEEE specification 1613, "Standard Environmental and
Testing Requirements for Communications Networking Devices in Electric Power
Substations."

Wide Range of Applications

JunglePAX with its wide range of interface units has the ability to transport voice,
data, IP, teleprotection and video traffic with guaranteed security and
dependability.

Flexible Network Architecture

JunglePAX can be deployed in a number of network topologies – linear networks,

ring networks, mesh and multiple ring networks.

Interoperation with MPLS Network Elements

JunglePAX complies with the MPLS-TP specifications and can be deployed as

part of a network that has pre-existing packet transport equipment. Private
MPLS-TP solutions, however, provide utility-grade network performance edge-to-
edge.

Interoperation with JungleMUX DS0 / 64 kbps Level Interface Units

JunglePAX can interface directly with JungleMUX/TN1U/TN1Ue channel buses

(CBUS) to allow connectivity with legacy DS0/64kbps level interface units. It is
likely that many of these units have been operating for some time and are
designed with a typical 20+ year MTBF. These field proven units are cabled,
engineered, documented and the technical staff are trained already on this
equipment. Retaining these channel units and cabling the CBUS signal to a
JunglePAX node instead of a JIF-Share, CMUX or CDAX unit is a simple
migration path for such services.

Comprehensive OAM

Full OAM support for both underlying infrastructure and service-based

performance and availability management is offered.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 20

Integrated Network Management

The JunglePAX Network Management System provides network visibility,

information collection, real-time event responses and provisioning capabilities
from optic level down to the DS0/64kbps level tributary units at every node,
minimizing maintenance time and expenses. Hardware design has been
optimized to enhance embedded management functions.

Scalability

JunglePAX is scalable and supports easy growth. Future traffic requirements

can be met by adding additional access modules or adding additional WAN ports.
This helps in minimizing and protecting initial investment.

Flexible Bandwidth Utilization

TDM pseudowires supported by JunglePAX include CESoPSN (circuit emulation

over packet-switched network) and SAToP (structure-agnostic TDM-over-packet;
future) modes. Where the structure of the TDM is agnostic, the channelized
structure of the TDM is completely disregarded (good for transfer-delay-sensitive
applications, whereas structure-aware TDM transport protects the TDM structure.
The latter is useful for individual DS0/64kbps services that need to be managed
with finer granularity, providing performance and quality over efficiency, like a
fractional DS1 service, where framing bits and unused channels are stripped,
and the used channels transported over the network.

L2VPN (layer-2 virtual private network) and VPLS (virtual private LAN service)
instances can be created over the JunglePAX infrastructure to enable point-to-
point and point-to-multipoint connections, respectively.

Hot Swappable Units

All units in the JunglePAX system are hot swappable. This allows continuous
operation during troubleshooting or expansion of the network.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 21

4. PRODUCT STRUCTURE

JunglePAX is modular in design, which makes it flexible and adaptable to various

application needs and allows for simple additions of new features to existing
systems.

A JunglePAX system comprises the following module types:

1. Equipment Shelf
2. Core Units
3. Timing Unit (presently not available)
4. Power Supply Units
5. Ethernet LAN access units
6. TDM access units (T1/E1, CBUS and DS0/64kbps level units)

The Equipment shelf occupies 2 RU in a 19” rack. It can accommodate two Core
Units, Timing unit, two Power Supply units and various access units. The Core
and Timing units are installed from the front, while the Power Supply and access
units are installed from the rear. Customer connections to individual units are
provided on their faceplates.

All modules are hot swappable. They are equipped with special ejection handles
that allow reduced insertion/ejection force and ensure safe locking for
Earthquake Risk Zone 4 compliance.

Figure 5: JunglePAX Shelf Front View (both Core Units equipped)

On its faceplate, the Core Unit provides six optical WAN ports, two NMS ports,
two serial ports for console/modem access, and ports for clock & time reference
inputs & outputs. Through the backplane, the Core Unit interfaces the

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 22

companion Core Unit, the Timing Unit and access units, which may include
Ethernet LAN units, T1/E1 Units, CBUS Units (for access to legacy JungleMUX
64kb/s level units1) and JPAX 64kb/s level access units (also referred to as iDS0
level units – internal DS0/64kbps level units). The Core Unit also provides NMS
functionality. When two (left and right) Core Units are installed, redundancy is
provided for all the aforementioned functions. In unprotected applications (e.g.
terminal node in a linear system), only one Core Unit is installed.

The Timing unit is needed only if external BITS/SSU or GPS timing needs to be
fed into the node. Hardware protection/redundancy is provided at the system
level by establishing connections to external synchronization/timing sources at
two or more JunglePAX nodes equipped with Timing units. The Timing unit
provides GPS antenna input as well BITS/SSU timing inputs.

Figure 6: JunglePAX Shelf Rear View

The Power Supply Units are installed into the shelf’s leftmost and rightmost rear
slot positions. Two units are needed for redundancy. The DC Power Supply Unit
supports 36-140 VDC. The future AC Power Supply Unit will support 85-265
VAC (50/60Hz).

Access units (Ethernet LAN, T1/E1, CBUS and iDS0 level units) are installed into
the slots between Power Supply Units. There are 16 shelf slots available for
access units.

1 If used, legacy DS0-level interface units are installed in a JungleMUX shelf.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 23

5. EQUIPMENT SHELF

The JunglePAX Equipment Shelf (P/N 90001-01) occupies 2 RUs in a 19” rack.

The shelf is equipped with two side brackets. These could be mounted in ten
different positions to support recessed (-1.5”), flush (-0.25”) and protruded
mounts with 7 different depths (1”, 2.25”, 3.5”, 4.75”, 5”, 6.25”, 7.5”, 8.75, 10”).
The shelf dimensions provided in the figure below are shown for when the
brackets are positioned for the recessed mount (-1.5”).

Figure 7: Shelf dimensions

JunglePAX has been designed to operate over extended ambient temperature

range of -20 to +60 ºC (-4 to +140 ºF) and it does not require active cooling. To
ensure enough airflow for efficient passive cooling through the convection
chimneys, one RU above and below the shelf must be left unequipped. This
means that if two JunglePAX shelfs are installed one above the other, 2 RU
spacing between them is required.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 24

As the product was expected to work in remote, often unmanned locations, the
convection chimneys have been designed to prevent liquid and solid wildlife
droppings from penetrating into the shelf. They also prevent penetration of
industrial contaminants into the shelf.

Figure 8: Shelf design prevents penetration of industrial contaminants and

wildlife droppings

The shelf design meets Radio Frequency Immunity (RFI) and Electromagnetic
Compatibility (EMC) according to ANSI/IEEE C37.90.2, IEC61850-3 and IEEE
1613.

Backplane

The JunglePAX shelf backplane provides connections between Core

Units, Timing Unit, Power Units and access units. Figure 9 shows the actual
position of the backplane.

The rear side of the backplane (Figure 10) has 18 slots. The two outside slots
are reserved for Power Supply Units, while the remaining 16 slots (numbered 1
to 16) are reserved for access units. These 16 slots are divided into two zones;
Ethernet Zone (slots 1-6) and Flex Zone (slots 7-16). The capacities and
possible uses of individual slots in these zones are shown in Table 2.

Note: The backplane provides independent tracing from individual access units
to each Core Unit to ensure full 1+1 hardware protection. It also allows the Core
Units to automatically detect all installed access units.

The backplane has no active components. Both front and rear backplane
connectors allow for self-aligned low-force insertion/ejection of units.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 25

Rear Side

Backplane

Left Right
Core Core

Timing Card
Front Side (optional)
Figure 9: JunglePAX Shelf Top View (shown with top cover removed)

FLEX ZONE ETHERNET ZONE

<Slot 16 ……..………………………………………...… Slot 7> <Slot 6 ………………..… Slot 1>

Power 1 x 1 GigE: Slots

Slots 7,
7, 13,
9, 13,
15 15 4 x 1 GigE: Slots 1, 3, 5 Power
Supply 4 x T1/E1: Slots 13,
13, 14
14 1 x 1 GigE: Slots 2,
2, 4,
4, 66 Supply
Unit 4 x CBUS: Slots
Slots 15, 16 Unit
(Left)
(Slot 17) 64k Channel: Slots
Slots 7-16 (Right)
(Slot 0)

Figure 10: Backplane Access Unit Zones (Rear View)

The example in Figure 11 shows the shelf’s rear view with redundant Power
Supply, two Ethernet LAN interface units (installed in slots 1 and 4) and one
CBUS Unit (installed in slot 15).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 26

Zone Slot Capacity Function 1 Function 2 Function 3 Function 4

# (see NOTE 1) (future) (future)
Ethernet 1 4 Gb/s 4 x 1 GigE See NOTE 2
2 1 Gb/s 1 x 1 GigE See NOTE 2
3 4 Gb/s 4 x 1 GigE See NOTE 2
4 1 Gb/s 1 x 1 GigE See NOTE 2
5 4 Gb/s 4 x 1 GigE See NOTE 2
6 1 Gb/s 1 x 1 GigE See NOTE 2
Flex 7 1 Gb/s 1 x 1 GigE 64 kb/s level (NG) See NOTE 2
8 1 Gb/s 64 kb/s level (NG) See NOTE 2
9 1 Gb/s 64 kb/s level (NG) See NOTE 2
10 1 Gb/s 64 kb/s level (NG) See NOTE 2
11 1 Gb/s 64 kb/s level (NG) See NOTE 2
12 1 Gb/s 64 kb/s level (NG) See NOTE 2
13 1 Gb/s 1 x 1 GigE 4 x T1/E1 64 kb/s level (NG) See NOTE 2
14 4 x T1/E1 64 kb/s level (NG) See NOTE 2
15 1 Gb/s 1 x 1 GigE 4 x CBUS 64 kb/s level (NG) See NOTE 2
16 4 x CBUS 64 kb/s level (NG) See NOTE 2

NOTE 1: Presently, only the module with 4 x 1 GigE optical ports (SFP) and the module with 4 x
10/100/1000 Mbps RJ-45 ports are available. When either module is installed in slot 2, 4, 6, 7, 13
or 15, only Port #4 can be used.
NOTE 2: One of the following future dual-slot units can be alternatively installed into any two
adjacent slots between slots 1 and 8 and between slots 13 and 16:
a) 8 x 10/100/1000 Mb/s Ethernet
b) 16 T1/E1 unit (supports only bulk T1/E1 tunneling)

Table 2: Use of Backplane Access Slots

Figure 11: Shelf Rear View with Power Supply, 2 Ethernet and 1 CBUS Unit

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 27

6. CORE UNIT
The Core Unit (P/N 90010-01) acts as the multiplexing unit for the JunglePAX
system. It multiplexes data from various access interfaces into any of the 6 fiber-
optic WAN interfaces located on the faceplate of the Core Unit. The unit also
provides NMS functions for the JunglePAX node.

The Core Unit has the following key functions:

- Provides interface to Ethernet WAN ports (optical), companion Core Unit,
Timing Unit and various access units
- Operates as a 24 Gbps Ethernet switch
- Extends proper synchronization and precision time across the WAN
- Ensures secure NMS access and data encryption on WAN ports
- Ensures real time control of traffic and NMS functions through separate data
and management planes

Figure 12: Core Unit

The key functional components of a Core Unit are the 24 Gbps switch/router,
TDM packetizer and a dual-core processor. The processor’s core #1 provides a
high-speed / real-time control of the fiber network data plane. The core #2
provides embedded management plane functionality (NMS). Full separation of
Management and Data planes is ensured.

The JunglePAX shelf is normally equipped with two Core Units to support ring
applications and provide hardware redundancy. At any given point of time, one
of the two Core Units is actively managing the node while the other one operates
as a hot standby for that function.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 28

2 x Local Ports 2x Clock IO

2 x 10 Gigabit Ports Status LEDs

4 x 1 Gigabit Ports Latches

2x NMS Ports SD Card Slot

Figure 13: Core Unit Face Plate

Interfaces

Fiber-Optic WAN Ports

Each Core Unit is equipped with 6 WAN ports (Figure 14).

WAN ports 1 & 2 can be equipped with 10G, 2.5G or 1G SFP+/SFP transceivers.
WAN ports 3, 4, 5 & 6 can be equipped only with 1G SFP transceivers.

Note: Bolded options are available in Release 1.

Figure 14: WAN port connectors: (a) with no SFPs installed; (b) with WAN 1 and
WAN 3 SFPs in place (WAN 1 port is disabled so its LEDs are off)

On an installed SFP transceiver in the upper row (WAN ports 1, 3 and 5), the
laser source is the left connector, while the PINFET receiver is the right

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 29

connector. This is reversed for the SFP transceivers in the lower row (WAN
ports 2, 4, 6).

The dust covers for unequipped SFP cages must be kept in place to prevent dust
contamination. Additionally, the dust covers for SFP transceiver connectors
should be in place when the transceiver is installed but not in operation or when
the unit with installed transceivers is stowed away for future use.

WARNING
The laser radiation is infrared and invisible.
Do not attempt to look into the laser.
Use only laser-safe SFP modules (per IEC 60825-1 and IEC 60950-1).

NOTE
Do not insert alcohol swabs into optical connectors.

All fiber patch cord connectors should be properly cleaned before insertion into
the unit. Compressed air can be used if it is necessary to remove dust from the
unit's optical connectors.

Note: Each WAN port that needs to be activated requires an activation license.
Please contact GE Lentronics for more information.

Note: A JunglePAX node operating in a single ring topology has one WAN port
provisioned on each Core Unit. Similarly, a JunglePAX node acting as a
gateway between two rings has two WAN ports provisioned on each Core Unit.
Meshed network topologies are also supported.

Data on WAN ports is encrypted. Additionally, the Ethernet frames on WAN

ports are carried within a WAN frame called WIS (WAN Interface Sublayer). This
SONET/SDH-like frame provides overhead Information required for network
maintenance and fast switching. In the future firmware releases, the user will be
able to disable WIS encapsulation for WAN ports 2, 4 and 6, to make those ports
compatible with remote non-JunglePAX MPLS equipment.

Note: In the event of a single fibre failure, the Core Unit’s switch automatically
kills the traffic in the opposite direction. Note, however, that the WIS overhead is
not killed so the RDI (Remote Defect Indication) is still received at the transmit
end of the faulty fibre link.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 30

NMS Ports

Two stacked Ethernet RJ-45 ports denoted NMS (Figure 13) provide two NMS
access points to the unit. Two connections allow the user to dedicate one port
for a permanent NMS link and the second for local maintenance access.

Note: Presently, only NMS port #1 is operational.

Serial Craft Interface Port

The modular 8P8C (RJ45) jack denoted “RS232” is for factory use only. The
pinouts for this connector are available in Table 3.

Pin Number Name Direction Description

1 RTS Out Request To Send
2 N/C
3 TXD Out Transceiver Data
4 GND
5 GND
6 RXD In Receiver Data
7 N/C
8 CTS In Clear To Send

Table 3: RS232 connector pinout

USB Port

A standard USB Type B female connector is used for local eMS access
(alternative to the NMS connectors). Its use is mandatory for the unit IP address
allocation.

Pin Number Name Description

1 VCC +5 Vdc (500mA max)
2 D- Data -
3 D+ Data +
4 GND Ground

Table 4: USB Connector pinout

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 31

Timing Connections

Core Unit provides four SMB connectors (1PPS-in, 1PPS-out, CLK-in, CLK-out)
for passing timing signals to/from the unit. 1PPS signals are used for precision
timing, while the CLK signals are used for frequency synchronization.

The CLK port signals do not carry embedded NMS and can be configured for
three different reference frequencies. One of them is the 2 kHz sync signal,
commonly used for passing clock between JungleMUX networks. This allows for
the reference clock to be passed from a legacy JungleMUX node to a collocated
JunglePAX node.

Micro SD Card Socket

A Micro SD card socket allows for insertion of externally accessible data storage.

LED Indications

Unit/System Status LEDs

There are 3 Unit/System Status LEDs located on the Core Unit. They provide
summary status of the shelf. The indications are as follows:

Steady Red – Major alarm in the data plane.

Flashing Red – Major alarm in the management plane. Suppressed if a Major
alarm in the data plane exists.

Steady Yellow – Minor alarm in the data plane.

Flashing Yellow – Minor alarm in the management plane. Suppressed if a Minor
alarm in the management plane exists.

Steady Green – Denotes normal node operation.

All LEDs Off – No power

WAN Port Status LEDs

There are 2 bicolored LEDs associated on each WAN port. They are positioned
between the upper and lower WAN ports as shown in Figure 15.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 32

Upper WAN Port’s LED B

(green/red)

Upper WAN Port’s LED A

(green/amber)

Lower WAN Port’s LED B

(green/red)

Lower WAN Port’s LED A

(green/amber)

Figure 15: WAN port LED indications

The indications are as follows:

Steady Red – SFP alarm (LOS, Transmit Fault, Temperature, SFP missing, etc.)
Flashing Red – presently not used

Steady Amber – Link is down and port enabled, or RDI and port enabled.
Flashing Amber – Port is receiving bad packets (CRC, illegal length, etc).

Steady Green – Link is up and idle (no traffic).

Flashing Green (LED A) – Port is sending data.
Flashing Green (LED B) – Port is receiving data.
Off Green - No link or no traffic (port not sending or receiving data).

Core Unit Insertion

1. Ensure that the ejection/insertion handles located at the left and right side of
the Core Unit are in the disengaged position.
2. While loosely holding both ejection/insertion handles, gently push the unit into
the shelf until you reach the point of resistance.
3. Once the handles have cleared the raised edge of the chassis, push the
handles simultaneously. When the handles have locked into position, the unit
is fully inserted.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 33

Figure 16: Core Unit ejection/insertion handle

Figure 17: Core Units ejected (with ejection/insertion handles in disengaged

position)

Core Unit Ejection

1. Pull the lock clip located immediately above each ejection/insertion handle up
to unlock the respective ejection/insertion handle.
2. Pull the ejection/insertion handle to eject the unit.
3. Slide the unit out of the chassis.

WARNING
The SFP cage, heat sink and heat spreader may be very hot!

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 34

7. DC POWER SUPPLY UNIT

Overview

The 90110-01 DC Power

Supply Unit (DC PSU)
accepts a DC source
ranging from 40 to 140 VDC
and efficiently provides
isolated and regulated 12V
and 3.3V outputs to the
JunglePAX system. The
unit also reports its status to
the Core Units so it can be
monitored through eMS.

The module’s input has

inrush limiting as well as
Figure 18: DC Power Supply Unit shown with
transient, overcurrent and
and without mating terminal block connectors
reverse polarity protection.
installed
Its outputs incorporate
current limiting, short circuit protection, overvoltage protection (OVP) and ESD
transient limiting.

Each JunglePAX node requires two PSUs (DC, AC or one of each) to operate
normally. The module has been designed to reliably share the load with a
paralleled PSU thus providing redundant power to all other installed units. If
either PSU fails, the remaining PSU takes over the entire load without
interruptions on the output voltage rail.

The monitoring circuit provides information on the module’s output voltages,

output current, operating temperature, serial number, part number and hardware
revision.

The unit has been approved by CSA

(Canada Safety Administration) and the
corresponding label on the inside of the unit
shows the relevant registration number
(Figure 19).

Figure 19: DC PSU’s label with

CSA certification and ratings

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 35

Faceplate LED

The unit provides a single bicolor LED to report the unit’s state.
Green indicates that the unit is powered and operating normally.
Red indicates that either the 3 VDC output or both 12 VDC and 3 VDC outputs
have failed.
The LED turned off indicates that the unit’s power input is not connected to a
voltage source or the unit has failed.

Faceplate Connections

The unit uses a two-piece 5.08 mm terminal block for input power connection.
Use TE P/N 796859-3 (or similar) as a mating connector. The pin assignments
for the power input connector are shown in Table 5.

WARNING
Exercise extreme caution when connecting power supply inputs to
voltages higher than 60 V.

The unit uses a two-piece 3.5 mm terminal block for Major/Minor alarm
connections. Use TE P/N: 284510-3 (or similar) as a mating connector. The pin
assignments for the Major/Minor alarm connectors are shown in Table 6.

Pin Number Signal Description Label

1 CG Chassis ground
2 P-VINP Battery Positive +
terminal (+)
3 P-VINM Battery Negative -
terminal (-)
Table 5: Power input connector pin assignments

Pin Number Signal Description Label

1 Major/Minor NO Form C Normally NO
Open terminal
2 Major/Minor COM Form C Common COM
terminal
3 Major/Minor NC Form C Normally NC
Closed Terminal
Table 6: Major/Minor alarm connector pin assignments

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 36

The mating connectors for power input and both alarm contacts are supplied with
the unit.

The Major/Minor alarm outputs are connected to galvanically isolated Form C

Solid State Relay (SSR) with guaranteed 3kV isolation.

DC Power Supply Unit Insertion

1. Prior to Power Supply Unit insertion, ensure that the shelf is properly
grounded (see Earthing section on page 9).
2. Make sure there is no power input connections made to the Power Supply
unit before insertion.
3. A protective device such as a molded case circuit breaker or fused disconnect
switch must be installed on both sources of incoming power for circuit
protection and as a disconnection device.
4. Make sure the unit’s heat sink is facing outside of the chassis before inserting
the unit.
Note: The unit in the right-hand side position is installed rotated by 180 with
respect to the one installed in the left-hand side position (Figure 20).
5. Ensure that the ejection/insertion handle is in the disengaged position (Figure
21).
6. Gently push the unit into the shelf until you reach the point of resistance.
7. Engage the handle (i.e. lift it up if the unit is in the left position, or pull it down
if the unit is in the right position). When the handles have locked into position,
the unit is fully inserted.
8. Prior to establishing input power connections to the unit, ensure that the
external fuse rating does not exceed the specified value (5A at 48VDC, 1.5A
at 130VDC). A protective device such as a molded case circuit breaker or
fused disconnect switch must be installed on both sources of incoming power
for circuit protection and as a disconnection device.
9. Establish the input power connections. Use 12 AWG conductors Green LED
will indicate proper Power Supply Unit operation.

DC Power Supply Unit Ejection

1. Disconnect the power input from the unit.

2. Pull the lock clip on the ejection/insertion handle towards the tip of the handle
to unlock the handle (Figure 20).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 37

3. Pull the ejection/insertion handle to eject the unit.

4. Slide the unit out of the chassis.

WARNING
The heat sink and heat spreader may be very hot!

Ejection/Insertion
Handle

Lock Clip

a) b)

Figure 20: DC PSU installed in left position (a) and right position (b)

Figure 21: Left DC PSU ejected (with handle in disengaged position)

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 38

8. AC POWER SUPPLY UNIT

Overview

The 90100-01 AC Power Supply Unit (AC PSU)

accepts an AC source ranging from 115 to 240 VAC
(50-60 Hz) and efficiently provides isolated and
regulated 12V and 3.3V outputs to the JunglePAX
system. The unit also reports its status to the Core
Units so it can be monitored through eMS.

The module’s input has inrush limiting as well as

transient, overcurrent thermal protection. Its outputs
incorporate overcurrent restart (hiccup mode), short
circuit protection, overvoltage protection (OVP) and
ESD transient limiting.

Each JunglePAX node requires two PSUs (DC, AC

or one of each) to operate normally. The unit has
Figure 22: AC Power
been designed to reliably share the load with a
Supply Unit
paralleled PSU thus providing redundant power to all
other installed units. If either PSU fails, the remaining PSU takes over the entire
load without interruptions on the output voltage rail.

The monitoring circuit provides information on the module’s output voltages,

output current, operating temperature, serial number, part number and hardware
revision.

The unit has been certified according to

IEC60950-1 IECEE CB Scheme
(international system for mutual acceptance
of test reports and certificates dealing with
the safety of electrical and electronic
components, equipment and products) and
the corresponding label on the inside of the
unit shows the relevant registration number. Figure 23: AC PSU’s label with
CSA certification and ratings

Faceplate LED

The unit provides a single bicolor LED to report the unit’s state.
Green indicates that the unit is powered and operating normally.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 39

Red indicates that either the 3 VDC output or both 12 VDC and 3 VDC outputs
have failed.
The LED turned off indicates that the unit’s power input is not connected to a
voltage source or the unit has failed.

Faceplate Connections

The unit has an integrated 18” AC power “pigtail” cord terminated with the
universal female AC power connector IEC 320 C14 (Figure 24). Supplied with
the unit is an AC main power cable equipped with the universal male AC power
connector (IEC 320 C13) at one end and the adequate power plug at the other.
The most commonly used main power cables and their codes are shown in Table
7.

Figure 24: Universal female connector (connects to supplied main power cable)

Code Main Power Cable’s Plug Type

B NEMA 5-15p (North America)
E CEE7/7 (most of Europe)
G BS1363 (UK and Middle East)
I Australia and New Zealand
NOTE: More codes will be added as needed. Please contact GE if desired plug type is not listed.
Table 7: Codes for commonly used plug types on the main power cable

Part Number Description

90100-01/<code> AC PSU with a desired main power cable included
90100-01 AC PSU unit without the main power cable
90100/<code> Main power cable (code indicates the type of plug)
Figure 25: Part Number format for AC PSU and associated main power cable

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 40

The unit uses a two-piece 3.5 mm terminal block for Major/Minor alarm
connections. Use TE P/N: 284510-3 (or similar) as a mating connector. The pin
assignments for the Major/Minor alarm connectors are shown in Table 6.

The mating connectors for both alarm contacts are supplied with the unit.

The Major/Minor alarm outputs are connected to galvanically isolated Form C

Solid State Relay (SSR) with guaranteed 3kV isolation.

AC Power Supply Unit Insertion

1. Prior to AC Power Supply Unit insertion, ensure that the shelf is properly
grounded (see Earthing section on page 9).
2. Make sure the power cord is disconnected from the power source before
insertion.
3. A protective device such as a molded case circuit breaker or fused disconnect
switch must be installed on both sources of incoming power for circuit
protection and as a disconnection device.
4. Make sure the unit’s heat sink is facing outside of the chassis before inserting
the unit.
Note: The unit in the right-hand side position is installed rotated by 180 with
respect to the one installed in the left-hand side position (Figure 26).
5. Gently push the unit into the shelf. The unit is fully inserted when the upper
and lower screw tabs are touching the back of the shelf. Note that a fully
inserted unit is partially protruded.
6. Secure the unit in position using the retaining screw (type 4-40) supplied with
the unit.
7. Prior to establishing input power connections to the unit, ensure that the
external fuse rating does not exceed the specified value (2A @ 115VAC or 1A
@ 240VAC). A protective device such as a molded case circuit breaker or
fused disconnect switch must be installed on both sources of incoming power
for circuit protection and as a disconnection device.
8. Connect the supplied main power cord to the universal adapter at the end of
the integrated power pigtail cord. Ensure they are fully mated.
9. Connect the other end of the main power cord to the power source (115-
240VAC 50-60Hz). Green LED will indicate proper Power Supply Unit
operation.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 41

AC Power Supply Unit Ejection

1. Disconnect the power input from the unit.

2. Undo the retaining screw.
3. Firmly grip the top and bottom protruding surfaces of the unit and pull the card
straight out of the chassis. Do not attempt to extract the unit by pulling the
power cord.
WARNING
The heat sink and heat spreader may be very hot!

Screw tab

a) b)
Figure 26: AC PSU installed in left position (a) and right position (b)

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 42

9. ACCESS UNITS

Access units are installed at the back of the JunglePAX shelf, between the Power
Supply Units. There are sixteen slots available for access unit installation;
however, not all the slots are available for all unit types (refer to Table 2 on page
26 for more information). The presently available access units are listed in Table
8. These units provide connections to the customer drop equipment except for
the CBUS-4A unit, which provides access to the Expansion Shelf with
JungleMUX DS0 level units.

Part Number Name Description

90200-01 EF-4A Ethernet Access Unit (4G), 4 x 1G, SFP
90201-01 EC-4A Ethernet Access Unit (4G), 4 x 10/100/1000 Mbps,
RJ-45
90300-01 T1E1-4A TDM Access Unit, 4 x T1/E1, RJ-48c
90301-01 CBUS-4A TDM Access Unit, 4 x CBUS, RJ-45
Table 8: Presently available JunglePAX access units

General Information

This sub-section provides the information applicable to all access unit types. The
information applicable to individual access unit types is provided later in this
section.

Access Unit LED Indications

There are two types of visual indicators on every access unit panel:

1. Unit status LEDs

These include 3 LEDs (Figure 27):
• The uppermost two LEDs (green and red) indicate the summary status of
the unit.
• The blue LED in the bottom right corner indicates the initialization status of
the unit.
More details on the operation on the conditions indicated by the Unit Status
LEDs is provided in Table 9.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 43

Unit Condition “OK” LED - Green “ALM” LED - Red “ON” LED - Blue
Uninitialized OFF OFF ON
Normal operation ON OFF OFF
Board level alarm OFF ON OFF
Initialization failure OFF ON ON
Traffic test on one or X X Blinking twice per
more ports second
Unit is booting OFF OFF Blinking once per
second
EEPROM X X ON
programing
(factory use)

Table 9: Operation of Unit Status LEDs

2. Port status LEDs

Multiple, interface-specific LEDs provide functional summary status for
individual access ports. These LEDs, when available, are embedded into the
access port connectors themselves and provide interface-specific status.
More information on Port Status LED conditions for individual access module
types is provided later in this section.

Unit Status - Red

Unit Status - Green

Initialization Status - Blue

Figure 27: Access Unit Status LEDs

Access Unit Insertion

1. Before insertion, make sure that the correct access unit type and the correct
slot position have been selected.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 44

2. Make sure the unit is properly oriented (its thumb screw should be on the top;
see Figure 29a).
3. Align the unit into the red rail at the bottom of the chassis and into the green
rail at the top of the chassis (Figure 28).
4. Slide the access unit into the slot and push the handle in to lock the unit.
Shortly after the handle has been placed in the locked position, the blue LED
on the unit’s faceplate will turn off.
5. Secure the thumb screw on the top of the unit.
6. Ensure the lock handle is pushed in.

Figure 28: Proper alignment of access unit before insertion

Figure 29: Access unit: (a) ejected; (b) unlocked; (c) locked

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 45

Access Unit Ejection

1. Release the thumb screw on top of the unit.

2. Pull the lock handle at the bottom of the unit.
Note: Pulling the lock handle out will reset the unit (Blue LED will light up).
3. Continue pulling the handle to slide the unit out of the chassis.

Access Unit Reset

1. Pull the lock handle at the bottom of the unit half way out. Blue LED will light
up.
2. Push the lock handle back in. Blue LED will start flashing.
3. Once the unit is up and running, the blue LED turns off.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 46

SFP Ethernet Access Unit (EF-4A)

The Quad SFP Ethernet Access Unit (EF-4A, P/N
90200-01) provides four optical 1GigE interfaces
to the JunglePAX node and it occupies a single
access slot on the JunglePAX backplane. The
unit is normally installed in access slots 1, 3 and
5. It can also be installed in slots 2, 4, 6, 7, 13
and 15 if only one port needs to be used (Port 4).
Each used port requires a 1 Gbps SFP transceiver
installed. Only SFP transceivers with Diagnostic
Monitoring Interface (DMI) feature are supported.
The part numbers for the 1 Gbps SFP
transceivers presently available through GE
Multilin are provided in Table 20 (page 93).

The lower connector on each installed dual-fiber

SFP transceiver is the laser source, while the
upper connector is the PINFET receiver.

Figure 30: EF-4A Unit The dust covers for unequipped SFP cages must
with SFP transceiver be kept in place to prevent dust contamination.
installed for Port 2 Additionally, the dust covers for SFP transceiver
connectors should be in place when the
transceiver is installed but not in operation or when the unit with installed
transceivers is stowed away for future use.

All fiber patch cord connectors should be properly cleaned before insertion into
the unit. Compressed air can be used if it is necessary to remove dust from SFP
connectors.

WARNING
The laser radiation is infrared and invisible.
Do not attempt to look into the laser.
Use only laser-safe SFP modules (per IEC 60825-1 and IEC 60950-1).

NOTE
Do not insert alcohol swabs into optical connectors.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 47

SFP Port LED Indications

As shown in Figure 31, each SFP port has two bi-colored LEDs: the upper one
(Port Status LED) and lower one (Traffic Status LED). Table 10 provides the
details on the conditions indicated by these LEDs.

Port Status LED

(red/yellow)

Traffic Status LED

(green/yellow)

Figure 31: SFP Port LED Indications

Port Condition Upper LED (Port Status) Lower LED (Traffic

Status)
Disabled OFF OFF
Bad SFP RED X
(suppresses Link Down Alarm)
Link Down Alarm (loss of Yellow OFF
incoming optical signal)
Link Up Idle Traffic X Green
(incoming optical signal is
OK but no traffic received)
Traffic present (on link up) X Green randomly blinking
Traffic errors (on link up) X Yellow randomly blinking

Table 10: SFP Ethernet Access Unit Port Status LED Indications

Additionally, the blue LED located at the bottom of the faceplate will blink twice
per second if there is a traffic test in progress on one or more SFP ports.

For Unit Status LED indications refer to the Access Unit LED Indications section
(Page 42).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 48

RJ-45 Ethernet Access Unit (EC-4A)

The Quad RJ-45 (PHY) Ethernet Access Unit (EC-4A, P/N

90201-01) provides four RJ-45 10/100/1000 Mb/s interfaces to
the JunglePAX node and it occupies a single access slot on
the JunglePAX backplane. The unit is normally installed in
access slots 1, 3 and 5. It can also be installed in slots 2, 4, 6,
7, 13 and 15 if only one port needs to be used (Port 4).

Each RJ-45 port can be set to auto-negotiate the maximum

data transfer speed (10, 100 or 1000 Mb/s) and mode (half or
full duplex) with the device connected to the port. Alternatively,
the user can disable auto-negotiation and configure the mode
and speed as desired.

Note: When the connected device does not support auto-

negotiation and the unit’s auto-negotiation for the port is
enabled, the unit uses the incoming signal's speed and half-
duplex mode.

Each RJ-45 port can also be set for MDI, MDIX or MDI/MDIX
auto-detect mode.

Figure 32:
EC-4A Unit

RJ-45 Port LED Indications

As shown in Figure 31, each SFP port has two LEDs: the upper one
(green/yellow) and lower one (green). Table 10 provides the details on the
conditions indicated by these LEDs.

Speed
(green/yellow)

Link/Activity Status LED

(green)

Figure 33: RJ-45 Port LED Indications

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 49

Port Condition Upper LED (Speed) Lower LED (Link/Activity)

Disabled OFF OFF
Link Down Alarm (loss of OFF OFF
incoming signal)
Link Up, 10 Mb/s OFF Green
Idle traffic 100 Mb/s Green Green
1000 Mb/s Yellow Green
Link Up, 10 Mb/s OFF Green randomly blinking
Traffic 100 Mb/s Green Green randomly blinking
1000 Mb/s Yellow Green randomly blinking

Table 11: RJ-45 Ethernet Access Unit Port Status LED Indications

Additionally, the blue LED located at the bottom of the faceplate will blink twice
per second if there is a traffic test in progress on one or more RJ-45 ports.

For Unit Status LED indications refer to the Access Unit LED Indications section
(Page 42).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 50

T1/E1 Unit (T1E1-4A)

The T1/E1 Unit (T1E1-4A, P/N 90300-01) provides four
channelized T1 (1544 kbps) or E1 (2048 kbps) interfaces to the
JunglePAX node. The unit occupies a single access slot on the
JunglePAX backplane and it can be installed in either slot 13 or
14. Customer connections are made through RJ-45c connectors
whose pinouts are shown in Table 12. The connectors are
shielded and include panel ground springs for EMI containment.
The T1/E1 multiplex signal on each provisioned port can be split
into individual DS0/64kbps channels (or groups of DS0 channels)
for individual transport to their respective designated far-end
T1/E1/CBUS ports.

Pin # Description Format Direction with respect

to T1/E1 Unit
1 Data+ In (Tx) T1/E1 Input
2 Data- In (Tx) T1/E1 Input
3 Not Connected - -
Figure 34: 4 Data+ Out (Rx) T1/E1 Output
5 Data- Out (Rx) T1/E1 Output
T1E1-4A Unit
6 Not Connected - -
7 Not Connected - -
8 Not Connected - -

Table 12: RJ-48c Connector Pinouts

The unit deploys a passive 1+1 protection scheme where two T1/E1 LIUs (one
for the left and one for the right Core Unit) are used for each T1/E1 port.

T1/E1 Port LED Indications

As shown in Figure 35, each T1/E1 port has two LEDs: the upper one (Port
Status LED) and lower one (RAI LED). Table 13 provides the details on the
conditions indicated by these LEDs.

Port Status LED

(green/yellow)

RAI LED (yellow)

Figure 35: T1/E1 Port LEDs

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 51

Port Condition Upper LED (Port Status) Lower LED (RAI)

Disabled OFF OFF
OK Green X
T1/E1 Signal Alarm Yellow OFF
(LOS, LOF or AIS)
RAI (bad T1/E1 X Yellow
received at remote end)

Table 13: T1/E1 Port Status LED Indications

Additionally, the blue LED located at the bottom of the faceplate will blink twice
per second if there is a traffic test in progress on one or more RJ-45 ports.

For Unit Status LED indications refer to the Access Unit LED Indications section
(Page 42).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 52

CBUS Unit (CBUS-4A)

The CBUS Unit (CBUS-4A, P/N 90301-01) provides four
proprietary CBUS interfaces to a JungleMUX Expansion Shelf
equipped with DS0 level units. The unit occupies a single
access slot on the JunglePAX backplane and it can be installed
in either slot 15 or 16. Customer connections are made through
a modular RJ-45 connector whose pinouts are shown in Table
12. The connectors are shielded and include panel ground
springs for EMI containment. The CBUS multiplex signal on
each provisioned port can be split into individual DS0/64kbps
channels (or groups of DS0 channels) for individual transport to
their respective designated far-end CBUS/T1/E1 ports. The
unit’s part number is provided in Table 20 (page 93).

Pin # Description Format Direction with respect

to CBUS Unit
1 Data+ In (Tx) RS-422 Input
2 Data− In (Tx) RS-422 Input
3 Ground
Figure 36:
4 Data+ Out (Rx) RS-422 Output
CBUS-4A Unit
5 Data− Out (Rx) RS-422 Output
6 Ground
7 Clock+ RS-422 Output
8 Clock− RS-422 Output
Table 14: CBUS (RJ45) Connector Pinouts

CBUS Port LED Indications

As shown in Figure 37, each CBUS port has two bi-colored LEDs: the upper one
(Port Status LED) and lower one (Traffic Status LED). Table 15 provides the
details on the conditions indicated by these LEDs.

Port Status LED

(green/yellow)

Traffic Status LED

(yellow)

Figure 37: CBUS Port LEDs

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 53

Port Condition Upper LED (Port Status) Lower LED (Traffic Status)
Disabled OFF OFF
OK Green X
Loss of CBUS Yellow OFF
link

Table 15: CBUS Port Status LED Indications

For Unit Status LED indications refer to the Access Unit LED Indications section
(Page 42).

CBUS Connection to a JungleMUX/TN1U Expansion Shelf

A CBUS cable (P/N 90902-01, Figure 38) connects a CBUS RJ45 connector to a
header connector on the JungleMUX/TN1U Expansion Shelf (B86430-0X/-1X/-
3X). To establish such a connection, do the following:

1. Connect the RJ45 end of the cable to the selected CBUS access unit’s port
Figure 39a).
2. Connect the header connector to the lower pinout connector to the left of the
leftmost end of the CBUS established on a JungleMUX/TN1U Expansion
Shelf while making sure the red side of the ribbon cable is aligned with pin 1
on the shelf’s connector. Cover the installed header with a blank jumper
board and secure it in place with the plastic screw provided with the blank
jumper board (Figure 39b).
3. Connect the spade terminal to the ground connector on the JungleMUX/TN1U
Expansion Shelf.
4. If more than one DS0/64kb/s channel unit is installed on the same CBUS,
make sure the CBUS jumper assemblies (P/N 087-86430-90, Figure 40) are
installed along the CBUS (Figure 39b).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 54

Figure 38: CBUS cable

Figure 39: CBUS cable connection: (a) Expansion Shelf side; (b) CBUS Unit
side

087-86430-90
J1

J2

Figure 40: CBUS Jumper Assembly

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 55

CBUS Connection to a TN1Ue Expansion Shelf

The CBUS DB9-to-RJ45 Adapter (P/N 90902-02) and a shielded straight-through

RJ45 cable are used to connect a CBUS-4A Unit’s RJ45 connector to a male
DB9 connector on a TN1Ue Expansion Shelf (B86430-22/-42). To establish such
a connection, do the following:

1. Connect the adapter to the selected CBUS (male DB9) connector on the
TN1Ue Expansion Shelf (Figure 41) and secure it using the two integral
thumb screws.
2. Using a shielded RJ45 cable of appropriate length (customer provided),
connect the adapter’s female RJ45 connector to the desired CBUS port on
the CBUS-4A Unit.
3. If more than one 64kb/s level unit is installed on the same CBUS, make sure
the CBUS jumper assemblies (P/N 087-86430-90, Figure 40) are installed
along the CBUS (Figure 41).
CBUS CONNECTOR TRACED TO SLOT 14 CBUS CONNECTOR TRACED TO SLOT 7

CBUS TIF IN TIF IN TIF IN TIF IN TIF IN TIF IN

[14] [14] R [12] R [10] R [7] R [5] R [3] R
CBUS
[7]
TIF IN TIF IN TIF IN TIF IN +5V TIF IN TIF IN
+5V
[13] L [11] L [9] L [8] L [4] L [2] L

TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT
[14] R [12] R +5V +5V [5] R [3] R
[10] R [7] R
CBUS CBUS
[8] [1]

TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT
TIF EXT
[13] L [11] L [6] L [4] L [2] L
[9] L

CBUS JUMPER ASSEMBLY CBUS CONNECTOR TRACED TO SLOT 8 CBUS CONNECTOR TRACED TO SLOT 2

Figure 41: TN1Ue Expansion Shelf Backplane

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 56

10. TDM DATA PACKETIZING

TDM interfaces include T1/E1 and CBUS ports available on respective access
units. These units provide physical T1/E1 and CBUS interfaces to the Core
Unit’s TDM packetizer.

Note: At the factory, the packetizer is configured for either T1 or E1 mode

depending on the region the unit is to be used in (North America or the rest of the
world). The packetizer in T1 mode cannot support E1 ports and vice versa.

CBUS is a JungleMUX-proprietary bidirectional channel bus with 24 DS0/64kbps

channel capacity. It carries both TDM and NMS data. This interface provides
access to Lentronics DS0/64kbps level interface units installed in a JungleMUX
Expansion Shelf. It also provides a means for migrating JungleMUX SONET and
TN1U/TN1Ue SDH networks towards a JunglePAX packet-switched network.

TDM Port Mapping

TDM data from up to eight T1/E1 or CBUS ports can be packetized and
forwarded to the Ethernet WAN. Figure 42 shows the port mapping.

Note: Two physical ports connected to the same packetizer port cannot be
simultaneously used. For example, if CBUS port 15-1 is used, the T1/E1 port
13-1 cannot be used and vice versa.

CBUS T1/E1
Slot: 16 15 14 13

5 16-1 1 15-1 5 14-1 1 13-1 Use example:

6 16-2 2 15-2 6 14-2 2 13-2 5 16-1 1 15-1 5 14-1 1 13-1

6 16-2 2 15-2 6 14-2 2 13-2

7 16-3 3 15-3 7 14-3 3 13-3
7 16-3 3 15-3 7 14-3 3 13-3

8 16-4 4 15-4 8 14-4 4 13-4

8 16-4 4 15-4 8 14-4 4 13-4

Packetizer’s TDMoP ports

Figure 42: TDM port mapping

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 57

Bundles

Packetized TDM data is transported in bundles. Note the following:

• A maximum of 64 bundles per node can be created.
• One or multiple bundles can be assigned to a TDM port.
• A bundle cannot be assigned to multiple TDM ports.
• A bundle can accommodate any selection of up to 24 timeslots for a
T1/CBUS interface or up to 30 timeslots for an E1 interface.
o Bulk T1/E1 transport is presently not supported.
o All timeslots in the bundle share the same QoS (5 or 7).
o If at least one circuit in the selected timeslots generates signaling
data, the bundle’s signaling channel needs to be enabled.
• Multiple bundles can be assigned to the same TDM port.
• Near-end and far-end bundle IDs need to match.
o Presently, the range is 1-64, but will be expanded to 1-64K.
• A bundle can be forwarded to any remote TDM port or any local TDM port
(hairpinning functionality).
• The number of timeslots must match at the two ends
o The actual timeslot numbers allocated to the given bundle at the
two ends do not need to match as long as their count is the same.
o The timeslots are matched in ascending order (e.g. if the near end
is set for timeslots 1 and 5 while the far end is set for timeslots 20
and 21, timeslot 1 will connect to timeslot 20 while timeslot 5 will
connect to timeslot 21).

Note: Each set of DS0/64kbps circuits from a CBUS or T1/E1 port destined for
any specific far-end port can be placed into the same bundle (service) if the
same QoS is needed for all of them. Separate bundles/services are created if
different QoS is needed.

Caution: Adding a timeslot to a bundle in service takes the whole bundle out of
service until the new timeslot is added at both ends. If this is unacceptable (and
the added timeslot is a new circuit rather than bandwidth expansion of an existing
circuit), a new bundle needs to be used for this timeslot.

Note: By default, bundles are including signaling data for all associated
DS0/64kbps circuits. If none of the DS0/64kbps circuits in the bundle are using
signaling, this feature should be disabled.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 58

CBUS Interface SDRAM interface

T1/E1 Interface
MII Interface
TDMoP Block

LIU Transmitter TX Formatter

Clock
Recovery

Ethernet
MAC 10/
TDM Cross- 100
Connect Payload Type
Machine
(CESoPSN)
LIU Receiver RX Framer

CBUS Interface

Figure 43: TDM packetizer block diagram

Figure 44: Encapsulating TDM data into a bundle (example)

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 59

TDMoP Delays

End-to-end TDMoP circuit delay depends on four major factors:

1. Packet creation time (depends on the number of TDM frames per packet)
2. Propagation delay (fixed, depends on the selected tunnel path)
3. Allocated buffering time for the compensation of packet delay variation
4. Circuit processing time (fixed)

Factors 1 and 4 can be controlled by the user.

The packet creation time (or packetization delay) can be reduced by decreasing
the number of TDM frames (125μs) per packet (minimum is 3 frames, or 4
frames if signaling channel is enabled); which in turn reduces the bandwidth
utilization as packets (with potentially unfilled payload) are sent more frequently.

Propagation delay consists of two components: fiber propagation delay (5

μs/km) and node through delay (10-20 μs per node).

Jitter buffer time (also called dejitter buffer time) is the parameter that sets the
size of the buffer for incoming packets. The longer the buffering time, the more
tolerance for the variations in packet arrival rate is provided. The objective is to
minimize this time while ensuring that the buffer will not get emptied during
normal network operation.

Circuit processing time includes the circuit processing time at both ends of the
circuit and it varies depending on the of type of TDM circuit. For example, for a
4W VF circuit, this time is approximately 600 μs, while for a DTT circuit it is
typically 1.5 ms (max 3 ms).

Note: Reducing the buffering time below certain limit reduces its ability to
efficiently compensate for network packet jitter, which may result in data loss.

Maximum bandwidth utilization for a T1/CBUS-originated bundle with 24

timeslots is achieved with 60 frames per packet (packet creation time = 7.5 µs).

Maximum bandwidth utilization for an E1-originated bundle with 31 timeslots is

achieved with 46 frames per packet (packet creation time = 5.75 µs).

Note: Higher latency is a tradeoff for achieving high bandwidth utilization.

Note: A typical latency of an optimized TDM circuit over a JunglePAX network is

lower than 3 ms.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 60

Bundle Hairpinning

Figure 45 and Figure 46 are showing two typical TDM data hairpinning scenarios
Note that bundle hairpinning requires use of two bundles.

Figure 45: Hairpinning DS0/64kbps channels between two T1/E1 ports

Jmux DS0 Unit

Scenario #2
T1: Bundle #1 = {TS#10, 11, 12} Port 3
CBUS: Bundle #6 = {TS#10, 11, 12}

CBUS
Bundle #6 Interface

T1/E1
10/100 Ethernet
Interface

Bundle #1
Ethernet
Port 1
MAC

Octal T1/E1
Transceiver TDM Cross Connection

Figure 46: Hairpinning DS0/64kbps channels from a T1/E1 to CBUS port

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 61

11. PROTECTION SWITCHING

As pointed out earlier in this manual, LSPs are unidirectional in nature. Two co-
routed LSPs carrying traffic in opposite directions are configured simultaneously
to create a tunnel1.

A service/pseudowire can be transported to the far end in either protected or

unprotected fashion. For protected transport, two tunnels between the same pair
of end nodes need to be created. For full path redundancy, these tunnels should
be routed over different network paths.

“1+1” vs. “1:1” Path Protection Schemes

In a 1+1 path protection scheme, each protected service is simultaneously sent

over two paths (Figure 47). At the far end, one of the two paths is designated as
the priority path for the received service. If the priority path fails, the protection
switching takes place and the non-priority path goes online. In a JunglePAX
system, 1+1 protection switching is revertive and is carried out at the access port
level. The access port associated with service(s) requiring 1+1 path protection
must be configured for ‘Bulk’ mode and its Rx Priority setting (Left or Right)
determines which of the two Core Units (and, ultimately, which of the two paths)
is online under normal conditions. Note that the Rx Priorities at the two ends
must be carefully set to avoid asymmetric delay (Figure 48).
In a 1:1 path protection scheme, each protected service/pseudowire is sent to
the far end over one (working) path only. If the working path fails, the
pseudowire is switched to the protection path at both transmit and receive ends.
In JunglePAX system, 1:1 protection switching is revertive and is carried out at
the pseudowire level. The tunnels carrying 1:1 protected pseudowires must
originate and terminate on the Left Core unit (Figure 49). Each 1:1 protected
pseudowire has a designated primary (working) tunnel for Tx traffic. The tunnel
designated as the secondary tunnel acts as a protect tunnel for the given
pseudowire. Note that the same primary tunnel needs to be selected at both
ends to avoid asymmetric delay (Figure 50).
Note: In both 1+1 and 1:1 protection schemes, an LSP that is ‘working’ (normally
online) for one protected service could be ‘protect’ (normally offline) for another.
Note: Protection switching in both 1+1 and 1:1 protection schemes is triggered
when the LSP associated with the working path for the given service/pseudowire
is declared unhealthy.

1 Tunnels are sometimes referred to as bidirectional LSPs.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 62

NOTE: Traffic is sent simultaneously

in both directions. Highlighted lines
indicate online paths. Dotted lines
indicate no traffic presence.

L R L R

Rx Pri=L Rx Pri=L

Protected Protected Protected Protected

Tunnel Tunnel Tunnel Tunnel
A B A B

Rx Pri=R Rx Pri=R
R L R L

NOTE: On unidirectional failure,

loss of Rx BFDs causes near-
end receive failover. Near end
LSP
also stops sending BFDs, which
Service/Pseudowire causes far-end receive failover.

Figure 47: 1+1 protection switching for a path set with no asymmetrical delay

NOTE: Traffic is sent simultaneously

in both directions. Highlighted lines
indicate online paths. Dotted lines
L indicate no traffic presence. L R

L R L R

Rx Pri=L Rx Pri=L

Protected Protected Protected Protected

Tunnel Tunnel Tunnel Tunnel
A B A B

Rx Pri=L Rx Pri=L
R L R L

R L R L
NOTE: On unidirectional failure,
loss of Rx BFDs causes near-
end receive failover. Near end
LSP
also stops sending BFDs, which
Service/Pseudowire causes far-end receive failover.

Figure 48: 1+1 protection switching for a path set with asymmetrical delay

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 63

NOTE: Traffic is sent by the left unit

in one direction only. Highlighted
lines indicate online paths. Dotted
L R lines indicate no traffic presence. L R

Left Core Left Core

Tx Pri=Tunnel A Tx Pri=Tunnel A

Protected Protected Protected Protected

Tunnel Tunnel Tunnel Tunnel
A B A B

Tx Pri=Tunnel A Tx Pri=Tunnel A
Left Core Left Core

R R
L NOTE: On unidirectional failure, L
loss of Rx BFDs causes near-
end transmit failover. Near end
LSP
also stops sending BFDs, which
Service/Pseudowire causes far-end transmit failover.

Figure 49: 1:1 protection switching for a path set with no asymmetrical delay

NOTE: Traffic is sent by the left unit

in one direction only. Highlighted
lines indicate online paths. Dotted
L R lines indicate no traffic presence. L R

Left Core Left Core

Tx Pri=Tunnel B Tx Pri=Tunnel B

Protected Protected Protected Protected

Tunnel Tunnel Tunnel Tunnel
A B A B

Tx Pri=Tunnel A Tx Pri=Tunnel A
Left Core Left Core

R R
L NOTE: On unidirectional failure, L
loss of Rx BFDs causes near-
end transmit failover. Near end
LSP
also stops sending BFDs, which
Service/Pseudowire causes far-end transmit failover.

Figure 50: 1:1 protection switching for a path set with asymmetrical delay

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 64

Note: Use of 1:1 protection scheme results in slightly longer protection switching
time than 1+1 scheme, but it allows services originated on the same access port
to be destined for different far-end nodes.

Types of Access Ports

Each access port must be configured for either Bulk or Shared mode of
operation. Table 16 details the differences between the two modes.

Bulk mode: All services must be placed into the same tunnel (i.e. they must all be
destined for the same far-end node). A mix of protected and unprotected VPWS
services is allowed. Must not include VPLS services. In protected applications,
either the left or right unit is set as ‘working’ for the receive direction. (This is
achieved by setting Rx Priority to either Left or Right on both units). Protection
switching is executed at the access port level.

Shared mode: Services may be placed in the same or different tunnels. A mix of
protected/unprotected VPWS and VPLS services is allowed. The left unit is
‘online’, while the right unit is ‘offline’ for the port. (Note that Rx Priority is neither
configurable nor exposed).

Bulk Shared
Placement of services Same tunnel Same or different tunnels

Allowed mix of services VPWS protected VPWS protected

VPWS unprotected1 VPWS unprotected1
VPLS protected2
VPLS unprotected1,2
Designated Online Core Left or Right (user Left (not configurable)
Unit for RX traffic configurable)
Protection switching Access port level, 1+1 Pseudowire level, 1:1
execution (on tunnel loss)
Hairpinning No Yes

HW redundancy Yes Yes

(excluding access units)
1
Applicable to working (normally online) ports only
2
Applicable to Ethernet access ports only

Table 16: Types of Access Ports

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 65

Note the following:

• The near and far-end ports associated with a given service must be
configured for the same mode (not applicable to future iDS0 access ports).
• A future iDS0 access port at the near end can connect to either an iDS0 port
of the matching type or a CBUS/T1/E1 port (Bulk or Shared) at the far end.
• Hairpin circuits (n/a to LAN ports) can be established only between two
Shared ports, or between a Share port and iDS0 port configured with Rx
Priority=Left.

Access Port Switching (1+1)

Protection switching for services associated with ports in “Bulk” mode is always
1+1. If multiple services are present on the port, they must be connected to the
same tunnel. Use of left and right Core Units at both LER nodes is mandatory.

For each access port in “bulk” mode, one Core Unit (e.g. left for access ports 15-
1 and 1-2 in Figure 51) is normally online for traffic received from the far end.
This is determined by the Rx Priority setting for the port. Both Left and Right
Core Units are configured with the same Rx Priority setting (either Left or Right).
The Rx Priority is usually set based on the minimum end-to-end delay from the
far end. Note that, if multiple access ports are connected to the same tunnel,
they are usually configured with the same Rx Priority.

Note: If no path and hardware redundancy is required for a service on a Bulk

port, only the Core Unit that is normally online for the port is provisioned for that
service (i.e. the normally offline side is not configured).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 66

Figure 51: Access Port Switching – Normal State

If the working receive tunnel path for the given service is deemed unhealthy (due
to near-end WAN link failure or loss of BFD connectivity), protection switching
takes place. As shown in Figure 52, the affected access ports (port 15-1 in this
example) will start receiving traffic via the companion unit after the switchover.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 67

Figure 52: Access Port Switching – Tunnel Failure

In a situation where one of the two Core Units becomes unavailable, the other
Core Unit becomes online for all 1+1 protected services destined for this node
(Figure 53).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 68

Figure 53: Access Port Switching – Left Core Failure

Pseudowire Switching (1:1)

If an access port has services destined for multiple far-end sites, the port must be
configured for “Shared” mode of operation. For protected services originating on
access ports in Shared mode, use of 1:1 path protection switching mechanism
(executed at the pseudowire level) is mandatory.

The left Core Unit is automatically designated ‘working’ for all access ports in
Shared mode. If present, the right Core Unit is automatically designated
‘protection’ for these access ports. Note that it acts as a protection unit only for
those services whose one path (either normally online or normally offline) is
routed through the right Core Unit.

1:1 Protection Switching for Pseudowires Carrying VPWS Services

An example of a node terminating several VPWS services on access ports in

Shared mode is shown in Figure 54. Tunnels 4’ and 4” are destined for the same
far-end node. Similarly, tunnels 5’ and 5” are destined to the same far-end node

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 69

(but different from the tunnel pair 4’/4”). In the transmit (add) direction, traffic is
presented to both Core Units. The Left Core Unit sends traffic associated with
each service into only one of the two tunnels associated with the desired far-end
node. This designation is made by setting the Primary and Secondary tunnel for
each service and decision is usually made based on the minimal end-to-end
delay to the respecive far-end node. In the example in Figure 54, Tunnel 4’ is the
designated primary tunnel for the “purple” service on Port 15-2 and for the
“orange” service on Port 14-3, while Tunnel 5” is the designated primary tunnel
for the “red” service on Port 15-2 and the “blue” service on Port 15-3.

In the receive direction, the traffic for the given service is “collected” from both
the primary and the secondary tunnel (of course, traffic is present in only one of
them).

If the primary tunnel for the given pseudowire is deemed unhealthy (due to near-
end WAN link failure or loss of BFD connectivity), protection switching takes
place at the transmit end of each affected pseudowire (see Figure 55).

Figure 54: Pseudowire Switching (VPWS) – Normal State

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 70

Note that 1:1 protection switching is executed in the Left Core Unit regardless of
which of the two tunnels is designated primary. Observe that the Left Core Unit
remains online for all access ports in Shared mode regardless of the status of
individual tunnels. This means that the presence of Right Core Unit at LER
nodes is irrelevant for those 1:1-protected services whose both primary and
secondary tunnels are routed through the Left Core Unit’s WAN ports, which
makes use of Shared ports and 1:1 switching mechanism suitable in
implementations with single (left only) Core Units.

Figure 55: Pseudowire Switching (VPWS) – Tunnel Failure

The right-hand Core Unit will go online for ports in Share mode only if the Left
Core Unit fails (Figure 56). Note that hardware redundancy for a
service/pseudowire can be provided only if either the primary or the secondary
tunnel is routed through the Right Core Unit.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 71

Figure 56: Pseudowire Switching (VPWS) – Left Core Unit Failure

Protection Switching for Pseudowires Carrying VPLS Services

An example of a node terminating two VPLS services each with two pseudowires
is shown in Figure 57. The operation is the same as the one for tunnels carrying
VPWS services except that all traffic is forwarded through a switch ensuring that
all known unicast frames are sent to only one pseudowire.

If the primary tunnel for the given pseudowire is deemed unhealthy (due to near-
end WAN link failure or loss of BFD connectivity), protection switching takes
place at the transmit end of each affected pseudowire (Figure 58).

The right-hand Core Unit will go online for the receive traffic only if the Left Core
Unit fails (Figure 59).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 72

Figure 57: Pseudowire Switching (VPLS) – Normal State

Figure 58: Pseudowire Switching (VPLS) – Tunnel Failure

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 73

Figure 59: Pseudowire Switching (VPLS) – Left Core Unit Failure

Note: The BFD (Bidirectional Forwarding Detection) protocol must be enabled at

both ends of the tunnel to monitor its continuity. An LSP is declared unhealthy
upon loss of three consecutive BFD packets, which are sent every 3.3 ms1 This
event also causes the unit to stop sending BFD packets in the opposite direction
of the tunnel, triggering the same behavior at the far end. BFD initialization
packets will be sent once per second thereafter.

Note: A WAN link failure initiates fast protection switching of all services carried
in the working LSPs terminated by the Core Units interfacing the failed WAN link
regardless of whether BFD is enabled for their respective tunnels or not.

Note: Although it is strongly recommended to have the BFD protocol enabled for
all tunnels, if the Core Unit’s limit of 256 locally terminated tunnels with BFD
enabled has been reached (or is likely to be reached), the user may choose to
have BFD disabled for tunnels that meet one of the following two criteria:
- Tunnel is exclusively used for carrying unprotected traffic.

1The stated period is applicable to hardware-assisted BFDs. There are 256 HW-assisted BFDs
available per Core Unit. Firmware-assisted BFDs are planned for the future and their transmit
period is expected to be approximately 50 ms. Use of HW-assisted BFDs is mandatory for
applications where fast protection switching is required.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 74

- Tunnel is not traversing multiple hops (no LSR nodes) and not extended (from
Right to Left Core) at either LER node.

Hardware Redundancy

In 1+1 path protection schemes, hardware redundancy is implemented by means

of complete physical separation of the two paths between the near and far-end
access units. Note that both left and right Core Units must be used at each LER
node implementing 1+1 path protection switching scheme for at least one access
port.

In 1:1 path protection schemes, hardware redundancy is optional. Use of left

Core Unit is mandatory at each LER node. Hardware redundancy is provided if
one path is routed through a left and the other path through a right WAN port at
each LER node. When the left Core Unit fails, the right Core unit intercepts the
path established through the right WAN port and goes online for all locally
terminated 1:1 protected services.

Note: JunglePAX cannot provide hardware redundancy for services that are not
path protected.

Protection Switching in Various Network Topologies

1+1 protection switching mechanism can be used for services established over
ring, multiple ring, protected linear, and meshed network topologies as long as
both left and right Core Units are equipped at the near and far end nodes.

1:1 protection switching mechanism can be used for services established over
ring, multiple ring, protected linear, and meshed network topologies regardless of
whether one (left only) or both Core Units are installed at either end.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 75

12. FREQUENCY SYNCHRONIZATION

All nodes in a JunglePAX system should be referenced to a single clock source.

Frequency synchronization of the network is achieved through the physical layer
using line timing and clock recovery, i.e. the same way as SONET/SDH
networks. In network topologies providing path redundancy, proper reference
clock distribution must be maintained in the case of any WAN link or node failure.

Line timing implies that there is a node designated as a "headend node" which
provides the reference clock for the entire system. At the headend node, the
reference clock is either generated by the node itself (i.e. by one of its Core
Units) or introduced externally. Presently, the external reference clock can be a
2 kHz, 1.544 MHz, 10 MHz or 1 PPS signal. Solutions with primary and
secondary headend nodes are used when the system needs to remain
referenced to a highly accurate external clock even if the primary headend
becomes unavailable. These configurations are detailed later in this section.

The Core Unit unit has a user-configurable parameter called Node Type. The
Node Type can be set to Normal, HEI (Headend Internal), or HEE (Headend
External). Use of these synchronization modes is explained below. Note that at
any given node the Node Type parameter must be configured identically at both
left and right Core Units.

Another user-configurable synchronization parameter is “Sync Priority”. It takes

effect only if both Core Units are equipped at the node. It is set the same on both
units and it is normally kept defaulted (Left) at every node in the network.

A JunglePAX node configured as HEI generates its own clock. One of the two
Core Units provides the reference clock (i.e. it is internally timed) while the other
one is companion-timed; however, if the unit which is normally internally timed
fails (or is being replaced for maintenance), the normally-companion-timed unit
takes over the clock generation task. This clock is used to time the unit's
outgoing WAN port signals, the companion unit and its outgoing WAN port
signals, and all access units.

A "Normal" node derives the reference clock from the received line signal.
Normally, one of the two Core Units is "line-timed" while the other one is
"companion-timed". Which of the two Core Units (left or right) will be "line-timed"
is determined by comparing the SSM values in the received optical WAN port
signals provisioned for timing. In the case when all WAN port signals provisioned

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 76

for timing are carrying the same SSM value, the "Sync Priority" setting
determines the one used for timing.

A JunglePAX node is configured as HEE when it is timed through an external

reference frequency input on the Core Unit’s faceplate (2kHz, 1.544 MHz, 10
MHz, 1 PPS) or through the future Timing Unit installed between the two Core
Units. The Timing unit will allow for obtaining the reference clock from an all-
ones or traffic-carrying T1/E1 signal or from a GPS signal. The Core Unit whose
front frequency input is used for timing passes the reference clock to the
companion Core Unit. If the Timing unit is used to bring the external clock
reference into the node, both Core Units are timed directly from the Timing Unit.

Synchronization Status Messaging

Both left and right Core Units receive and transmit SSM messages. The SSM
message is a four-bit message contained in bits 5-8 of the S1 byte of the WIS1
overhead or in the Ethernet Synchronization Message Channel (ESMC) protocol
data unit as described in ITU-T G.8264. These messages provide an indication
of the quality level of the synchronization source of the aggregate optical signal.

JunglePAX supports both Option I (SDH) and Option II (SONET) SSM message
sets. The SSM values used for both options are provided in the tables below.

SSM Value S1 bits (b5-b8) Description

0 0000 Quality unknown (QU)
2 0010 Traceable to G.811 (PRC)
4 0100 G.812 Transit Clock (SSU-A)
8 1000 G.812 Local Clock (SSU-B)
11 1011 Traceable to G.813 Clock (SEC)
15 1111 Do not use for synchronization (DNU)

Table 17: Option I (SDH) SSM Message Set

1 WAN Interface Sublayer (WIS) is a framing standard described in IEEE 802.3ae that allows
Ethernet frames to be mapped into a SONET/SDH-like signal thus facilitating the SONET/SDH
Layer 1 fault management (LOS/LOF/AIS/RDI/BIP/REI). By default, WIS functionality is enabled
on all provisioned JunglePAX 10G, 1G and future 2.5 WAN ports. Future Core Unit firmware
versions will allow the user to turn the WIS functionality off on selected ports to allow
interoperability with foreign MPLS-TP products.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 77

SSM S1 bits
Quality Level Description
Value (b5-b8)
QL1 1 0001 Traceable to Stratum 1 (ST1)
QL2 0 0000 Synchronized – traceability/quality
unknown (STU)
QL3 7 0111 Traceable to Stratum 2 (ST2)
QL4 4 0100 Traceable to transit node clock (TNC)
QL5 13 1101 Traceable to Stratum 3E (ST3E)
QL6 A (10) 1010 Traceable to Stratum 3 (ST3)
QL7 C (12) 1100 Traceable to 20 ppm clock (SMC)
QL8 E (14) 1110 Reserved for network synchronization
QL9 F (15) 1111 Do not use for synchronization (DUS)

Table 18: Option II (SONET) SSM Message Set

Node Type Behavior

HEI • Sync Priority Unit is normally internally timed.
• Non-Sync Priority Unit takes over if the Sync Priority Unit dies.
• All WAN outputs send SSM=10 (or 8)1 unless Force TX SSM is
used.
HEE • Times from best timing source (Timing Unit, Core Unit Front Freq
Input, WAN ports) across both units based on SSM (actual or
forced), Port Sync Priority2, and Unit Sync Priority.
• All WAN outputs send SSM of the selected source, except the one
being used for timing (sends DUS/DNU).
• If no sources are available, times internally and outputs the Holdover
SSM=14 (11)1 on all WAN ports.
Normal • Times from best timing source (WAN port) across both units based
on SSM (actual or forced), Port Sync Priority, and Unit Sync Priority.
• All WAN outputs send SSM of the selected source, except the one
being used for timing (sends DUS/DNU).
• If no sources are available, times internally and outputs SSM=14
(11)1 on all WAN ports.

Table 19: Sync behavior of JunglePAX nodes

1 The actual value depends on whether SONET or SDH SSM message set is used. This info is
embedded in the license file.
2 Port Sync Priority determines which of the two or more local Core Unit’s WAN ports receiving
the same best SSM at the node level will be selected for timing. Factory preset to match the
WAN port numbers. This feature is not use for standard JunglePAX synchronization schemes.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 78

JunglePAX Network Synchronization Engineering Rules

To ensure proper frequency synchronization, the following rules shall be followed

when engineering a standalone JunglePAX network regardless of its topology
(ring, mesh, linear, or a mix of these).

1. Choose the reference clock source.

a. Internal or external
b. If external:
i. One or two headend nodes
ii. Type of external reference clock at each headend node (GPS
feed, 2kHz, 1.544 MHz, 10 MHz, 1 PPS)
2. Select the headend site(s).
3. Select the main synchronization loop. This could be any closed loop within
the JunglePAX network topology that satisfies the following rules:
a. It must include the headend node(s). If two headend nodes are used,
both of them must be included in the loop.
b. It must include one WAN port on the left Core Unit and one WAN port
on the right Core Unit at any node included in the loop. In other words,
the loop must go through the bypass link of every node included in the
loop.
c. Ensure left-to-right WAN port connectivity along the loop.1
d. If possible, ensure that there are no overlapped WAN links in the loop.
e. If two or more parallel WAN port links are running between any two
adjacent nodes in the main loop, include only one of them in the main
loop. For the remaining ones, set the Force Rx SSM parameter to
DUS/DNU at both ends.
4. Select the first open loop attached to the main loop.
a. An open loop may include any number of nodes, or it may include no
nodes at all.
b. Both ends of an open loop must be attached to the main loop,
preferably at different nodes.
i. The only exception are spurs (point-to-point or linear system
attached to the network at one end) or situations where WAN
link redundancy between two parts of the network cannot be
established.

1 For main synchronization loops established in JunglePAX networks whose individual nodes are
equipped with only one (left) Core Unit, it must be ensured that a lower-to-higher WAN port
number connectivity is established along the loop in either clockwise or counterclockwise
direction (e.g. L1-L2 in the clockwise direction).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 79

ii. If connecting both ends of an open loop to the same node

cannot be avoided, they must not be connected to the same
Core Unit.
c. An open loop must include one WAN port on the left Core Unit and one
WAN port on the right Core Unit at any node within the loop.
d. Ensure left-to-right WAN port connectivity between the nodes within
the loop (applicable if the loop contains two or more nodes).1
e. Set the Force Rx SSM parameter to DUS/DNU at both connecting
WAN ports in the main loop (towards the main loop itself).
i. For spurs, this can be done at only one connecting WAN port.
5. If there are any nodes or WAN links not included in the main or first open
loop, select another open loop following the rules 4a to 4f. Note that this and
any subsequent open loops may be attached to any two nodes belonging to
either the main loop or any of the previously established open loops with both
end points connected. The Force Rx SSM parameter would be set to
DUS/DNU at the respective end points, whether they belong to the main loop
or any previously established open loop.
NOTE: If possible, avoid connecting any new open loops to spurs (see
points 4bi and 4ei).
6. Repeat step 5 until all nodes and WAN port links in the network are covered.

Sync Engineering Examples

Example 1: Dual-homed rings

Note that the “tie” connections between rings are also WAN links.
HEE

Ring 1 Ring 2

HEE

Figure 60: Dual-homed rings

1 For open loops established in JunglePAX networks whose individual nodes are equipped with
only one (left) Core Unit, it must be ensured that a lower-to-higher WAN port number connectivity
is established along the open loop (e.g. L1-L2).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 80

Some of the possible timing solutions for the above network are shown below.
The main loop is green, the first open loop is yellow and the second open loop is
blue.
DUS DUS
HEE

Ring 1 Ring 2

DUS DUS
HEE

Figure 61: Dual-homed rings – Sync Solution 1

DUS
HEE

DUS

Ring 1 Ring 2

DUS DUS

HEE

Figure 62: Dual-homed rings – Sync Solution 2

HEE

DUS DUS

Ring 1 Ring 2

DUS DUS

HEE

Figure 63: Dual-homed rings – Sync Solution 3

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 81

Example 2: Added “tie” connection between dual-homed rings

HEE

DUS DUS

DUS DUS
Ring 1 Ring 2
Added 3rd Tie

DUS DUS

HEE

Figure 64: Dual-homed rings with 3rd Tie added

Example 3: Two rings with parallel tie links

HEE

Ring 1 Ring 2

HEE

Figure 65: Two rings with parallel tie links

In the sync solution below, note that the main loop (green) is selected to coincide
with Ring 1. The first open loop is pink while the second open loop is blue. Also
note that the pink loop is closed through the tie node in Ring 2 and attached to
the two Core Units at the Ring 1 tie node.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 82

HEE

DUS DUS
Ring 1 Ring 2
DUS DUS

HEE

Figure 66: Two rings with parallel tie links – Sync Solution

Example 4: Meshed network with spurs and parallel links

Below is an example of a meshed network including two parallel WAN links, an

attached linear system with 1+1 protected links, and two attached unprotected
spurs.

In both sync solutions 1 and 2 (Figure 68 and Figure 69), the main sync loop is
colored dark green. The two solutions differ by the selection of nodes for the
open loops in the lower left quadrant of the network.

HEE

HEE

Figure 67: Meshed network with spurs and parallel links

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 83

HEE
DUS
DUS DUS
DUS DUS
DUS
DUS DUS
DUS
DUS HEE DUS
DUS DUS
DUS DUS

DUS
DUS
DUS
DUS
DUS

Figure 68: Meshed network with spurs and parallel links – Sync Solution 1

HEE
DUS
DUS DUS
DUS DUS
DUS
DUS DUS
DUS
DUS HEE DUS
DUS
DUS
DUS DUS

DUS
DUS
DUS DUS
DUS

Figure 69: Meshed network with spurs and parallel links – Sync Solution 2

Synchronization of Main Loop with Single Headend Node

Figure 70 shows a JunglePAX main loop timed from an external sync source.
Node A is the headend node (Node Type = HEE) with redundant external

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 84

reference clock feeds established either to the Timing Unit or to the Core Unit’s
Front Frequency Inputs. One of the two external inputs is selected based on
their health, incoming or assigned SSM, and port/unit priority setting. The
selected reference is used to supply the node with the clock. The SSM
associated with the selected reference input will be forwarded to both left and
right Core Units and asserted into the outgoing WAN port signals.

Node A distributes the clock to other nodes in the loop, typically one way around
it (default setting). The Core Units at all other nodes in the loop have their Node
Type set to Normal. At each Normal node, one of the two Core Units is normally
line-timed while the other unit is companion-timed.

Prim
A C
Sec

Figure 70: Application with single headend node (Normal State)

If the primary clock source at Node A becomes unavailable, the secondary

source will be selected (Figure 71).

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 85

Prim
A C
Sec

Figure 71: Application with single headend node (loss of primary sync input)

If both external sources at Node A become unavailable (Figure 72), the Timing
Unit (if used) or the Sync Priority Core Unit will go into Holdover mode and will
continue to supply the node with the clock. In this mode, the SSM=14 (Option II)
or 11 (Option I) will be outputted on all provisioned headend node’s WAN ports.
If the Sync Priority unit fails, its companion will become the new sync leader.

Prim
HOLD
C
OVER
Sec

Figure 72: Application with single headend node (holdover)

If the headend node were to time internally, its Core Units would have their Node
Type parameter configured for HEI mode. The Sync Priority unit (left by default)
would generate the reference clock for the entire system. In the networks using
the Option I (SDH) SSM message set, the SSM outputted on the headend node’s

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 86

WAN port would be 8, while in the networks with Option II (SONET) SSM
message set, the WAN ports would output SSM=10.

Timing of a Main Loop with Two Headend Nodes

Some applications require an alternate (backup) headend node i.e. presence of

another site with access to external sync references. The main and backup
headend nodes may be located in the same main loop. Although connected to
valid external clock references, the backup headend node would normally be line
timed. To ensure this, the SSMs associated with the backup headend node’s
external sync references must be greater (lower sync quality designation) than
those at the main headend node during normal operation, but not greater than 10
(SONET) / 8 (SDH). This can be achieved by utilizing the Force Rx SSM feature.
For example, if the main headend node’s external sync references have their
SSM set to 1 (SONET) / 2 (SDH), the backup headend node should have its
external sync references’ SSMs set to 7 (SONET) / 4 (SDH).

Figure 73 shows the normal condition for the application with both main and
backup sync nodes residing in the same ring.

Main
Headend
Node
Prim Prim
A C
Sec Sec
Backup
Headend
Site

Figure 73: Main and backup headend nodes in same ring (normal operation)

In the case when both external sync references at the main headend node are
lost, its master External Sync Unit goes into Holdover mode and asserts SSM=14
(SONET) / 11 (SDH) into all outgoing WAN port signals. Since this SSM is now
greater than the SSM associated with external references available at the backup
headend node, the primary reference at the backup headend node will be
selected for local timing and its SSM will be asserted in the outgoing WAN port

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 87

signals. The master External Sync Unit at the main headend node will observe
that the new (lower than 14/11) SSM is received on one of the local aggregate
inputs and will perform a sync switch from holdover to line timing (Figure 74).

Main
Headend
Node
Prim Prim
A C
Sec Sec
Backup
Headend
Node

Figure 74: Main and backup headend nodes in same ring (loss of sync inputs at
main headend node)

Once at least one of the two external sync references at the main headend node
is valid again, the node will switch back to it. Shortly, the backup sync node will
become line-timed again.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 88

13. SPECIFICATIONS

WAN Ports Total Capacity 24 Gbps

Total Number of Optical WAN ports 6
Number of 10G WAN Ports 2, SFP+
Number of 1G WAN ports 4, SFP
CORE Hardware protection 1+1
Transport Protocol MPLS-TP, RFC 3031, RFC 3032, RFC
3985, RFC 5654
Encapsulation WAN-Interface Sublayer (WIS), IEEE
802.3ae
Bypass link capacity 20G
Switching capacity 66G
Number of terminated tunnels with 256 with H/W-assisted BFDs
individual fault detection (per Core 1792 with F/W-assisted BFDs *
Unit)
Processor Type Dual Core; one core for data plane
and one core for management plane
Client Services TDM (T1/E1/CBUS/64kb/s) and VPWS, VPLS, Emulated TDM over
Ethernet PSN (static)
Packetizer T1/E1/CBUS/iCBUS TDM ports 8
Number of TDM bundles 64
Circuit Emulation CESoPSN, SAToP
Synchronization WAN Synchronization method SyncE with SSM, G.8261, G.8262
Supported Clock Sources External, Internal, Line (WAN ports)
Internal Clock Accuracy 4.6 ppm (Stratum 3)
External Frequency Sync Interfaces 2kHz, 10MHz, 1.544MHz, 1PPS,
GPS*
2kHz/10MHz/1.544MHz/1PPS IN:
LVTTL/TTL, LVCMOS/CMOS
VIH: 2.0V (min), 5.0V (max)
VIL: 0V (min), 0.5V (max)
Cable Length: 3m (max), local only
2kHz/10MHz/1.544MHz/1PPS OUT:
LVTTL/TTL, LVCMOS/CMOS
VOH: 2.4V (min), 3.3V (max)
VOL: 0V (min), 0.4V (max)
Cable Length: 3m (max), local only
Quality Messaging SSM, ESMC, G.8264
Timing Timing Protocols NTP, IEEE 1588v2 (telecom and
power)*
Accuracy 1 µs, Grandmaster (1588 v2) *

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 89

OAM Continuity Check (BFD), Loss of RFC 5860, RFC 5880

Continuity, Link Down Indication,
Remote Defect Indication,
Loopback, Link Traceroute, Loss
Measurement, Delay Measurement
(round trip)
Performance Quality of Service IEEE 802.1p/Q with priority queues
and priority scheduling
Node through delay < 30 µs
Fault Detection Time 9.9 ms (for H/W-assisted BFDs)
150 ms (for F/W-assisted BFDs) *
Protection switching (failover) time 1+1: <3 ms (on fiber break)
(triggered by LDI and H/W-assisted ~0 ms (on Core card extraction)
BFD) 1:1: <16 ms (on fiber break)
<50 ms (on Core card extraction)
Management Device management model embedded Management System
(eMS)
Network management model embedded Management System
(eMS), Advanced NMS (Telenium)
Redundancy 1+1 protected (if both Core Units are
installed)
Interfaces CLI, WebUI (HTTPS), SNMP v3 *,
NetConf
Security EtherWAN encryption engine 6 independent encryption engines,
Optionally enabled on each WAN port
*
Encryption AES 256 *
Authentication SHA 256
Key distribution Public/Private, user-configurable key
rolling frequency *
Access Control Role-based
User Authentication RADIUS
Accounting Syslog (local)
Federal Information Processing 140-2
Standard
Hardening Compliance IEEE 1613 (no cooling fans), SWC,
EMI, RFI & ESD
IEC 61850-3, IEC 61000
Safety UL, CSA, IEC, TUV Compliance UL 60950-1-2014
CAN/CSA-C22.2 No 60950-1-07 +Am
1:2011+Am 2:2014
IEC 60950-1:2005, IEC 60950-
1:2005/AMD1:2009, IEC 60950-
1:2005/AMD2:2013
Additionally evaluated to EN 60950-
1:2006+A11:2009+A1:2010
+A12:2011 +A2:2013
CSA File Number: 215286
TUV SUD Certificate: U8 16 11 95680 002

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 90

Emissions Conducted and radiated emissions FCC Title 47 CFR Part 15 Class A
ICES-003 Issue 6
ETSI EN 300 386V1.6.1
EN 55022:2010/AC:2011
EN 55032:2012/AC:2013
EN 61000-3-2:2014
EN 61000-3-3:2013
Immunity IEEE 1613-2009+A1-2011 (Sections
4-8)
ETSI EN 300 386 V1.6.1
EN 55024:2010
• IEC 61000-4-2:2008
• IEC 61000-4-3:2006
+AMD1:2007+AMD2:2010
• IEC 61000-4-4:2012
• IEC 61000-4-5:2014
• IEC 61000-4-6:2013
• IEC 61000-4-8:2009
• IEC 61000-4-11:2004
Environmental Operating Temperature -20C (-4F) to + 60C (140F)
IEEE 1613-2019+A1-2011 Section 3
Storage Temperature -40C (-40F) to +70C (158F)
IEC 60068-2
IEEE 1613-2019+A1-2011 Section 3
Humidity, %RH 5 - 95%, non-condensing
IEEE 1613-2019+A1-2011 Section 3
Operating Altitude 2000 m
Penetration of small objects and At least IP32 (Protected against
liquids ingress of solid foreign objects
>2.5mm and dripping water (15
angled)
Earthquake NEBS ITL GR-63-CORE-TCG Issue 4,
April 2012 Section 4.4
Vibration/Shock
10mm/s 1-150Hz
100mm fall test
IEEE 1613-2019+A1-2011 Section 9
RoHS RoHS / WEEE
Reliability JunglePAX node in redundant 21 years
configuration
Shelf Size 19” (48.26cm) W
16.32” (41.45 cm) L
3.49" (8.86cm) H
Spacing 1 RU above and below for air
circulation
Backplane Type Passive
Hot swappable units Yes
Core Unit slots 2
Power Unit slots 2

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 91

Timing Unit slots 1

Access Unit slots (total) 16
4G (4x1GigE) Access Unit slots 3
1G (1 GigE) slots 7, using EF-4A or EC-4A* units
T1/E1 Unit slots 2
CBUS Unit slots 2
iDS0 level unit slots 10
Power 48/130VDC 40-140VDC
115/240VAC 100-264VAC, 45-66Hz
Redundancy Yes (with load sharing)
Consumption 160W (with overcurrent protection at
180W per Power Supply Unit)
Protection Reversed polarity, overcurrent,
overvoltage, transients, short circuit
External fuse rating for DC (max) 5A at 48VDC, 1.5A at 130VDC
External fuse rating for AC (max) 2A at 115VAC, 1A at 240VAC
Internal Fuse AC Unit
Input Fuse (Reference Designator
F100) – Solder-in 5x20 Ceramic,
Time-delay Fuse 250VAC, 6.3A
DC Unit
Self-clearing electronic breaker 5A
Alarm Contacts Major/Minor on DC PSU up to 140 VDC
Major/Minor on AC PSU up to 280 VDC
Access Unit EF-4A 4 x 1G Fiber ports, SFP (normally
interfaces installed in 4G slots), IEEE 802.3u,
802.3z, 802.1p, 802.1Q, 1000Base-
SX, 1000Base-LX, 1000Base-EX,
1000Base-ZX, 1000Base-EZX
EC-4A 4 x 1G Copper ports, RJ-45 (normally
installed in 1G slots), IEEE 802.3,
802.3u, 802.3x, 802.3ab, 802.1p,
802.1Q
T1E1-4A 4 x T1/E1 ports, RJ-48c, framed or
unframed, G.703, G.704, G.706,
G.826
CBUS-4A 4x CBUS ports, RJ-45
DR-4A 4x RS-232/V.24/V.28 (up to 38.4 kb/s)
or 3x RS-232/V.24/V.28 (up to 38.4
kb/s) plus 1x ITU G.703 64kb/s codir.
data
DR-1A 1x RS-232/V.24/V.28 (up to 38.4 kb/s)
or 1x ITU G.703 64kb/s data with
alarm contacts
G703D-4A 1x ITU G.703 64k codirectional data
C3794-4A 4x IEEE C37.94 n*64kb/s (n≤12) data

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 92

C3794-1A 1x IEEE C37.94 n*64kb/s (n≤12)data

with alarm contacts
Old-generation Direct Transfer Trip (DTT) 4 x DTT Tx/Rx, or 2 x DTT Tx+Rx
access units Data-LS 4 x 9.6 kb/s or 2 x 19.2 kb/s, or 1 x
compatible with 38.4 kb/s data signal plus 4 x 300 b/s
JunglePAX via control lines; RS-232/V.24
CBUS ** Data-Nx64 One N x 64 kb/s (N=1 to 12);
V.35 with local control lines or
RS-422/V.11 with no control lines
Data-Nx64F IEEE C37.94, mmf or smf interface
Data-G703 ITU-T G.703, 64 kbps (codirectional)
Data-56 56 kb/s async/sync plus one control
line; V.35 or RS-422/V.11
OCUDP 56 or 64 kb/s synchronous 4-wire
Digital Data Service (DDS) signal
4W VF E&M 4-wire VF, with optional E&M signaling
2W VF E&M 2-wire VF, with optional E&M signaling
2W VF FXO 2-wire; FXO loop-start or FXO ground-
start signaling
2W VF FXS 2-wire; FXS loop-start, FXS ground-start
or PLAR signaling
Contact IO Allows up to 16 external (foreign)
contacts (open/closed) to be replicated
from one note to another; configurable
for inputs only, outputs only or mix of
inputs and outputs.

* near future release

** Installed in legacy JungleMUX Expansion Shelf

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 93

14. ORDERING INFORMATION

This section covers the ordering information for JunglePAX units and is not
intended to replace standard engineering documentation or drawings. Please
contact the Account Manager for your area regarding ordering the
JunglePAX units and their accessories.

Type Part Number Description

Shelf 90001-01 JunglePAX Equipment Shelf, 2RU
Core-WAN 90010-01 Core Unit, MPLS-TP Multiplexer, 2 x 10 GigE WAN ports, 4 x
1 GigE WAN ports, Unlicensed. Two required for each shelf
operating in a protected configuration.
90010/10G 10 GigE WAN port RTU license
90010/G 1 GigE WAN port RTU license
90010/A, /B, /C SFP+, 10 GigE, LC, SMF, 10 km / 40 km / 80 km **
90010/AA, /BB, SFP, 1 GigE, LC, SMF, 10 km / 40 km / 80 km / 120 km **
/CC, /EE
Timing 90080-01* Timing Module, GPS & BITS
Power 90100-01 AC Power Unit, 115-240VAC, 50-60Hz
90110-01 DC Power Unit, 48/130 VDC
Access 90200-01 Ethernet Access Unit (4G), 4 x 1 GigE, SFP
90200/AA SFP, 1 GigE, LC, 1310 nm, SMF, 10 km
90200/DD SFP, 1 GigE, LC, 850 nm, MMF, 300 m
86418/AA SFP, 100M, LC, 1310nm, SMF, 30km
86418/DD SFP, 100M, LC, 850nm, MMF, 2km
90201-01 Ethernet Access Unit (4G), 4 x 10/100/1000 Mbps, RJ-45
90300-01 TDM Access Unit, 4 x T1/E1, RJ-48c
90301-01 TDM Access Module, 4 x CBUS, RJ-45
90360-01 IEEE C37.94, 1 port (SMF or MMF), LC, Form C
90360-02 IEEE C37.94, 4 ports (SMF or MMF), LC
90360/AA SFP for C37.94, SMF, 1310 nm, 15 km
90360/DD SFP for C37.94, MMF, 850 nm, 2 km
90350-01 1 x RS-232/V.24/V.28, or 1 x G.703 64kpbs, RJ-45
90350-02 4 x RS-232/V.24/V.28, or 3 x RS-232/V.24/V.28 and 1 x
G.703 64kpbs, RJ-45
90366-01 4 x G.703 64kbps, RJ-45
Cables 90900-01 Serial Cable, USB
90901-01 Ethernet Cable, RJ45-to-RJ45, CAT-5e, UTP, 3 m
90902-01 CBUS Cable, RJ45 to IDC Socket (JMUX & TN1U), 2 m
90902-02 CBUS Adapter, RJ45-to-DB9 (TN1Ue)
Software 90000-02 Embedded Manager (eMS), Network, per node RTU license
* Future release
** Other distances and CWDM/DWDM SFPs are available upon request

Table 20: Part Numbers

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 94

APPENDIX A

TDMoIP

Communications service providers and enterprise customers are interested in

deployment of voice and leased line services over efficient Ethernet, IP and
MPLS infrastructures. While Voice over IP (VoIP) is maturing, its deployment
requires an investment in new network infrastructure and customer premises
equipment. TDM over IP (TDMoIP) presents a migration path, through which
modern packet switched networks can be used for transport, while the end-user
equipment does not need to be immediately replaced.

TDMoIP is the emulation of time-division multiplexing (TDM) over a packet

switched network (PSN). TDM refers to a 64kbps, N x 64kbps, T1, E1, T3 or E3
signal, while the PSN is based either on IP or MPLS or on raw Ethernet.

TDMoIP is a type of pseudowire (PW). However, unlike pseudowires carrying

traffic types that are packet-based in nature (e.g. ATM, Frame Relay and
Ethernet), the pseudowires carring TDM traffic are carrying real-time bit streams.
In addition, TDMoIP circuits need to have features that allow them to carry voice-
grade telephony channels.

One critical issue in implementing TDM PWs is clock recovery. In contrast to

native TDM networks where the physical layer carries highly accurate timing
information along with the TDM data, PSNs carrying TDM data implement
innovative mechanisms to adaptively reproduce TDM timing.

Another issue that must be addressed is TDMoIP packet loss concealment

(PLC). Since TDM data is delivered at a constant rate over a dedicated channel,
the native service may have bit errors but data is never lost in transit. All PSNs
suffer to some degree from packet loss and this must be compensated when
delivering TDM over a PSN.

TDMoIP Format

TDMoIP operates by segmenting, adapting and encapsulating the TDM traffic at

PSN ingress and performing the inverse operations at PSN egress. Adaptation
denotes mechanisms that modify the payload to enable its proper restoration at
the PSN egress. By using proper adaptation, the TDM signaling and timing can

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 95

be recovered, and a certain amount of packet loss can be accommodated.

Encapsulation signifies placing the adapted payload into packets of the format
required by the underlying PSN technology. For the MPLS case, ITU-T
Recommendation Y.1413 contains a complete description of the packet format.

In all cases a TDMoIP packet commences with PSN headers. First comes the
20-byte header of UDP/IP, or the label-stack of MPLS. This is followed by the
"PW label", a four-byte MPLS-like label that is used to demultiplex different TDM
PWs. After the PSN header comes the four-byte TDMoIP "control word". The
control word contains a 16-bit packet sequence number (needed to detect packet
re-ordering and packet loss), payload length, and flags indicating defect
conditions.

After the control word comes the TDMoIP payload. For structure-agnostic
transport (SAToP), this is simply a predetermined number of TDM octets, while
for the structure-locked format the payload is an integer number of TDM frames.
For structure-indication and structure-reassembly TDMoIP draws on proven
adaptation mechanisms originally developed for ATM.

Delay

The telephony network severely constrains end-to-end delays. ITU-T

G.114/G.131 states that one-way transmission times of up to 150 ms are
universally acceptable, assuming adequate echo control is provided. These
constraints are not problematic for TDM networks, where the major component of
the end-to-end delay is propagation time. By contrast, IP-based systems
typically add various forms of delay, one of which is based on the time it takes to
form packets (packetization delay), which is proportional to the packet size
divided by the data rate. Packet sizes cannot be made too small or the packet
header overhead will become overwhelming. The other form of delay introduced
by IP systems is the playout delay, which needs to be added at the recipient to
buffer packet delay variation and ensure a smooth playout. VoIP systems that try
to be very bandwidth efficient may also add tens of milliseconds of algorithmic
delay in the voice codec.

TDMoIP maps TDM octets directly into the payload with no voice compression
algorithms and no resultant algorithmic delay. The packetization latency added
by TDMoIP depends on the number of TDM frames (or timeslots) per packet.
Both TDMoIP and VoIP work best on paths with controlled packet delay variation
(strong overprovisioning or "QoS").

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 96

Timing Recovery

Native TDM networks normally rely on hierarchical distribution of timing.

Somewhere in the network there is at least one extremely accurate primary
reference clock with a long-term accuracy of 1 x 10-11. This node, which offers
Stratum 1 accuracy, provides the reference clock to secondary nodes with
Stratum 2 accuracy. The secondary nodes then provide a time reference to
Stratum 3 nodes. This hierarchy of time synchronization is essential for the
proper functioning of the network as a whole.

Packets in the PSN reach their destination with delay that has a random
component, known as packet delay variation (PDV). When emulating TDM
transport on such a network, this randomness may be overcome by placing the
TDM packets into a jitter buffer from which data can be read out at a constant
rate for delivery to TDM end-user equipment. The problem is that the TDM
source time reference is no longer available and the precise rate at which the
data are to be "clocked out" of the jitter buffer is unknown.

When the TDM equipment at both ends of the PW is independently traceable to a

common clock source or they are traceable to independent but highly accurate
clock source, the timing at each end of the PW can be derived from the
respective TDM equipment. Sometimes, however, the only alternative is to
attempt to recover the clock based exclusively on the TDMoIP traffic, a
technology known as "adaptive clock recovery". This is possible since the
source TDM device is producing bits at a constant rate determined by its clock,
although this rate is hidden by the PDV. The task of clock recovery is thus an
"averaging" process that negates the effect of the random PDV and captures the
average rate of transmission of the original bit stream.

Packet Loss

While proper application of traffic engineering and quality-of-service (QoS) is

expected to minimize packet loss, packets will at times arrive at the egress out of
order. They may also have been dropped altogether within the PSN. The
TDMoIP control word described above includes a 16-bit sequence number for
detecting and handling lost and mis-ordered packets. In the case of lost packets,
TDMoIP requires insertion of interpolation packets to maintain TDM timing. Mis-
ordered packets may be either reordered or dropped and interpolated.

While the insertion of arbitrary packets may be sufficient to maintain the TDM
timing, in voice applications packet loss can cause gaps or errors that result in
choppy, annoying, or even incomprehensible speech. The precise effect of

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 97

packet loss on voice quality and the development of packet loss concealment
algorithms have been the subject of detailed study in the VoIP community, but
their results are not directly applicable to the TDMoIP case. This is because
VoIP packets typically contain between 80 samples (10 ms) and 240 samples (30
ms) of the speech signal, while TDMoIP packets may contain only a small
number of samples. Since TDMoIP packets are so small, it is acceptable to
simply insert a constant value in place of any lost speech samples. Assuming
that the input signal is zero-mean (i.e. contains no DC component), minimal
distortion is attained when this constant is set to zero. Alternatively, more
sophisticated approaches call for optimally predicting the values of missing
samples.

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 98

APPENDIX B

LIST OF ILLUSTRATIONS

List of Figures

FIGURE DESCRIPTION PAGE

Figure 1: Unicast MPLS packet format (shown without preamble and FCS) ......................... 11
Figure 2: Example of label lookup table at LSR ..................................................................... 11
Figure 3: Example of a label-switched path............................................................................ 12
Figure 4: Working and Protect LSP ........................................................................................ 13
Figure 5: JunglePAX Shelf Front View (both Core Units equipped) ....................................... 21
Figure 6: JunglePAX Shelf Rear View .................................................................................... 22
Figure 7: Shelf dimensions ..................................................................................................... 23
Figure 8: Shelf design prevents penetration of industrial contaminants and wildlife
droppings ................................................................................................................ 24
Figure 9: JunglePAX Shelf Top View (shown with top cover removed) ................................. 25
Figure 10: Backplane Access Unit Zones (Rear View) .......................................................... 25
Figure 11: Shelf Rear View with Power Supply, 2 Ethernet and 1 CBUS Unit....................... 26
Figure 12: Core Unit ............................................................................................................... 27
Figure 13: Core Unit Face Plate ............................................................................................. 28
Figure 14: WAN port connectors ............................................................................................ 28
Figure 15: WAN port LED indications ..................................................................................... 32
Figure 16: Core Unit ejection/insertion handle ....................................................................... 33
Figure 17: Core Units ejected (with ejection/insertion handles in disengaged position) ........ 33
Figure 18: DC Power Supply Unit shown with and without mating terminal block
connectors installed .............................................................................................. 34
Figure 19: DC PSU’s label with CSA certification and ratings................................................ 34
Figure 20: DC PSU installed in left position (a) and right position (b) .................................... 37
Figure 21: Left DC PSU ejected (with handle in disengaged position) .................................. 37
Figure 22: AC Power Supply Unit ........................................................................................... 38
Figure 23: AC PSU’s label with CSA certification and ratings ................................................ 38
Figure 24: Universal female connector (connects to supplied main power cable) ................. 39
Figure 25: Part Number format for AC PSU and associated main power cable .................... 39
Figure 26: AC PSU installed in left position (a) and right position (b) .................................... 41
Figure 27: Access Unit Status LEDs ...................................................................................... 43
Figure 28: Proper alignment of access unit before insertion .................................................. 44
Figure 29: Access unit: (a) ejected; (b) unlocked; (c) locked ................................................. 44
Figure 30: EF-4A Unit with SFP transceiver installed for Port 2............................................. 46
Figure 31: SFP Port LED Indications ...................................................................................... 47
Figure 32: EC-4A Unit............................................................................................................ 48
Figure 33: RJ-45 Port LED Indications ................................................................................... 48
Figure 34: T1E1-4A Unit ......................................................................................................... 50
Figure 35: T1/E1 Port LEDs.................................................................................................... 50
Figure 36: CBUS-4A Unit........................................................................................................ 52

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 99

List of Figures (Continued)

FIGURE DESCRIPTION PAGE

Figure 37: CBUS Port LEDs ................................................................................................... 52

Figure 38: CBUS cable ........................................................................................................... 54
Figure 39: CBUS cable connection: (a) Expansion Shelf side; (b) CBUS Unit side............... 54
Figure 40: CBUS Jumper Assembly ....................................................................................... 54
Figure 41: TN1Ue Expansion Shelf Backplane ...................................................................... 55
Figure 42: TDM port mapping ................................................................................................. 56
Figure 43: TDM packetizer block diagram .............................................................................. 58
Figure 44: Encapsulating TDM data into a bundle (example) ................................................ 58
Figure 45: Hairpinning DS0/64kbps channels between two T1/E1 ports ............................... 60
Figure 46: Hairpinning DS0/64kbps channels from a T1/E1 to CBUS port ............................ 60
Figure 47: 1+1 protection switching for a path set with no asymmetrical delay ..................... 62
Figure 48: 1+1 protection switching for a path set with asymmetrical delay .......................... 62
Figure 49: 1:1 protection switching for a path set with no asymmetrical delay ...................... 63
Figure 50: 1:1 protection switching for a path set with asymmetrical delay ........................... 63
Figure 51: Access Port Switching – Normal State .................................................................. 66
Figure 52: Access Port Switching – Tunnel Failure ................................................................ 67
Figure 53: Access Port Switching – Left Core Failure ............................................................ 68
Figure 54: Pseudowire Switching (VPWS) – Normal State .................................................... 69
Figure 55: Pseudowire Switching (VPWS) – Tunnel Failure .................................................. 70
Figure 56: Pseudowire Switching (VPWS) – Left Core Unit Failure ....................................... 71
Figure 57: Pseudowire Switching (VPLS) – Normal State ..................................................... 72
Figure 58: Pseudowire Switching (VPLS) – Tunnel Failure ................................................... 72
Figure 59: Pseudowire Switching (VPLS) – Left Core Unit Failure ........................................ 73
Figure 60: Dual-homed rings .................................................................................................. 79
Figure 61: Dual-homed rings – Sync Solution 1 ..................................................................... 80
Figure 62: Dual-homed rings – Sync Solution 2 ..................................................................... 80
Figure 63: Dual-homed rings – Sync Solution 3 ..................................................................... 80
Figure 64: Dual-homed rings with 3rd Tie added .................................................................... 81
Figure 65: Two rings with parallel tie links .............................................................................. 81
Figure 66: Two rings with parallel tie links – Sync Solution.................................................... 82
Figure 67: Meshed network with spurs and parallel links ....................................................... 82
Figure 68: Meshed network with spurs and parallel links – Sync Solution 1.......................... 83
Figure 69: Meshed network with spurs and parallel links – Sync Solution 2.......................... 83
Figure 70: Application with single headend node (Normal State) .......................................... 84
Figure 71: Application with single headend node (loss of primary sync input)....................... 85
Figure 72: Application with single headend node (holdover).................................................. 85
Figure 73: Main and backup headend nodes in same ring (normal operation) ...................... 86
Figure 74: Main and backup headend nodes in same ring (loss of sync inputs at main
headend node) ...................................................................................................... 87

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 100

List of Tables

TABLE DESCRIPTION PAGE

Table 1: MPLS vs MPLS-TP ................................................................................................... 16

Table 2: Use of Backplane Access Slots ................................................................................ 26
Table 3: RS232 connector pinout ........................................................................................... 30
Table 4: USB Connector pinout .............................................................................................. 30
Table 5: Power input connector pin assignments................................................................... 35
Table 6: Major/Minor alarm connector pin assignments......................................................... 35
Table 7: Codes for commonly used plug types on the main power cable .............................. 39
Table 8: Presently available JunglePAX access units............................................................ 42
Table 9: Operation of Unit Status LEDs ................................................................................. 43
Table 10: SFP Ethernet Access Unit Port Status LED Indications ......................................... 47
Table 11: RJ-45 Ethernet Access Unit Port Status LED Indications ...................................... 49
Table 12: RJ-48c Connector Pinouts...................................................................................... 50
Table 13: T1/E1 Port Status LED Indications ......................................................................... 51
Table 14: CBUS (RJ45) Connector Pinouts ........................................................................... 52
Table 15: CBUS Port Status LED Indications ........................................................................ 53
Table 16: Types of Access Ports ............................................................................................ 64
Table 17: Option I (SDH) SSM Message Set ......................................................................... 76
Table 18: Option II (SONET) SSM Message Set ................................................................... 77
Table 19: Sync behavior of JunglePAX nodes ....................................................................... 77
Table 20: Part Numbers ......................................................................................................... 93

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 101

APPENDIX C

LIST OF ACRONYMS

• 2W 2-wire
• 4W 4-wire
• AC Alternating Current
• AES Advanced Encryption Standard
• AIS Alarm Indication Signal
• AMI Alternate Mark Inversion
• ANSI American National Standards Institute
• ATM Asynchronous Transfer Mode
• B8ZS Bipolar with 8-Zero Substitution
• BFD Bidirectional Forwarding Detection
• BER Bit Error Rate
• BITS Building Integrated Timing Supply
• BPV Bipolar Violations
• CBUS Channel Bus
• CDAX Compact Digital Access Cross-Connect
• CE Customer Edge
• CEoP Circuit Emulation over Packet
• CESoP Circuit Emulation Service over Packet
• CESoPSN Circuit Emulation over Packet-Switched Network
• CISPR Comité International Spécial des Perturbations Radioélectriques
(International Special Committee on Radio Interference)
• CLI Command Line Interface
• CMUX Channel Multiplexer
• CRC Cyclic Redundancy Check
• CSA Canada Safety Administration
• DA Destination Address
• DACS Digital Access and Cross-connect System
• DC Direct Current

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 102

• DDS Digital Data Service

• DHCP Dynamic Host Configuration Protocol
• DMI Diagnostic Monitoring Interface
• DNU Do Not Use (for Synchronization)
• DP Data Plane
• DS0 Digital Signal level 0 (64 kb/s)
• DSL Digital Subscriber Line
• DTT Direct Transfer Trip
• DUS Don’t Use for Synchronization
• E1 European Primary Multiplex Signal (2,048 kb/s)
• E3 European PDH Multiplex Signal Level 3 (34,368 kbit/s)
• ECN Explicit Congestion Notification
• EEPROM Electrically Erasable Programmable Read-Only Memory
• EIA Electronic Industries Association
• eLER Extended LER
• ELR Extra Long Reach
• EMC Electromagnetic Compatibility
• EMI Electromagnetic Interference
• eMS Embedded Management System
• ER Engineering Release
• ESDS Electrostatic Discharge Sensitive
• ESF Extended Superframe
• ESMC Ethernet Synchronization Message Channel
• ETSI European Telecommunications Standards Institute
• EXZ Excessive Zeros
• FAS Frame Alignment Signal
• FCC Federal Communications Commission
• FCS Frame Check Sequence
• FEC Forwarding Equivalent Class
• F/W Firmware
• FPGA Field Programmable Logic Gate Array
• FR Frame Relay
• FXO Foreign Exchange Office
• FXS Foreign Exchange Subscriber

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 103

• GMT Greenwich Mean Time

• GPS Geo-Positioning Satellite
• H/W Hardware
• HDB3 High-Density Bipolar Order 3
• HEE Headend External (headend with external timing)
• HEI Headend – Internal (headend with internal timing)
• HTTP Hypertext Transfer Protocol
• HTTPS HTTP Secure
• iCBUS Internal Channel Bus
• ID Identification Data (Identifier)
• IEC International Electrotechnical Commission
• IECEE CB International Electrotechnical Commission for Electrical
Equipment – Certification Body
• IEEE Institute of Electrical and Electronics Engineers
• IETF Internet Engineering Task Force
• IP Internet Protocol
• IR Intermediate Reach
• ITL Independent Testing Laboratory
• ITU-T International Telecommunication Union – Telecommunications
Sector
• JIF JungleMUX Intermediate Format
• JMUX JungleMUX
• JPAX JunglePAX
• LAN Local Area Network
• LBO Line Build-Out
• LDI Link Down Indication
• LED Light Emitting Diode
• LER Label Edge Router
• LIU Line Interface Unit
• LOS Loss Of Signal
• LSP Label Switched Path
• LSR Label Switching Router
• LR Long Reach
• LS Low Speed

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 104

• MAC Media Access Control

• MDI Media Dependent Interface
• MP Management Plane
• MP2MP Multipoint-to-Multipoint
• MPLS Multiprotocol Label Switching
• MPLS-TP Multiprotocol Label Switching – Transport Profile
• MTBF Mean Time Between Failures
• NAD Node Assignment Drawing
• NEBS Network Equipment-Building System
• NMS Network Management System
• NTP Network Timing Protocol
• OAM Operations, Administration and Maintenance
• OOF Out Of Frame
• OTN Optical Transport Network
• P Provider
• P/N Part Number
• P2P Point to Point
• P2MP Point to Multipoint
• PC Personal Computer
• PCM Pulse Code Modulation
• PDH Plesiochronous Digital Hierarchy
• PDV Packet Delay Variation
• PE Provider Edge
• PHY Physical layer of the OSI model
• PINFET p-intrinsic-n Field Effect Transistor
• PLC Packet Loss Concealment
• PLL Phase Locked Loop
• P/N Part Number
• PPS Pulse Per Second
• PRBS Pseudo-Random Binary Sequence
• PRC Primary Reference Clock
• PSN Packet Switched Network
• PSU Power Supply Unit
• PTM Point-To-Multipoint

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 105

• PW Pseudowire
• PWE3 Pseudowire Emulation Edge-to-Edge
• QoS Quality of Service
• QRSS Quasi-Random Signal Sequence
• QU Quality Unknown
• RADIUS Remote Authentication Dial-In User Service
• RAI Remote Alarm Indication
• RCV Receive
• RDI Remote Defect Indication
• RFI Radio Frequency Interference
• RoHS Restriction of Hazardous Substances
• RTC Real-Time Clock
• RU Rack Unit
• RX Receive
• SA Source Address
• SAToP Structure-Agnostic TDM over Packet
• SD Secure Digital (memory card)
• SDH Synchronous Digital Hierarchy
• SEC Synchronous Equipment Clock
• SHA Secure Hash Algorithm
• SF Superframe
• SFP Small Form-Factor Pluggable
• SMC SONET Minimum Clock
• SN Serial Number
• SNMP Simple Network Management Protocol
• SONET Synchronous Optical Network
• SR Short Reach
• SSH Secure Socket Shell
• SSM Synchronization Status Messaging
• SSR Solid State Relay
• SSU Synchronization Supply Unit
• ST1 Stratum 1
• ST2 Stratum 2
• ST3 Stratum 3

Copyright © GE Multilin Inc. 2016-2019

 342-90001-PS
Issue 1.1
August 2019
Page 106

• ST3E Stratum 3E
• STU Synchronized, Traceability Unknown
• S/W Software
• SWC Surge Withstand Capability
• T1 Digital Signal level 1 (1,544 kb/s)
• T3 Digital Signal level 3 (44,736 kbit/s)
• T1MX T1 Multiplexer (a member of Lentronics Multiplexers’ family)
• TCP Transmission Control Protocol
• TDM Time Division Multiplexing
• TDMoIP TDM over IP
• TDMoP TDM over Packet
• TE Traffic Engineering
• TNC Transit Node Clock
• TP Transport Profile
• TPIM Technical Practice and Installation Manual
• TTL Time to Live
• TX Transmit
• UDP User Datagram Protocol
• UI User Interface
• UTC Coordinated Universal Time
• VLAN Virtual LAN
• VLL Virtual Leased Line
• VoIP Voice over IP
• VPN Virtual Private Network
• VPLS Virtual Private LAN Service
• VPWS Virtual Private Wire Service
• VRF Virtual Routing and Forwarding
• VF Voice Frequency
• WAN Wide Area Network
• WEEE Waste Electrical and Electronic Equipment
• WIS WAN Interface Sublayer
• XMT Transmit

Copyright © GE Multilin Inc. 2016-2019