0% found this document useful (0 votes)
305 views117 pages

JPAX - eMS User Manual

JPAX MPLS NODE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
305 views117 pages

JPAX - eMS User Manual

JPAX MPLS NODE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

342-90001-PS2

Draft 1
January 2018

JunglePAX Embedded
Management Software (eMS)

User’s Guide

Copyright © GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 2

JunglePAX Embedded
Management Software (eMS)

User’s Guide

Copyright  GE Multilin Inc. 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. 2018


342-90001-PS2
Draft 1
January 2018
Page 3

TABLE OF CONTENTS
SECTION PAGE
1. INTRODUCTION .................................................. 6 
Revision History ...................................................................................7 

2. GETTING STARTED ........................................... 8 


Configuring Core Unit IP Address ......................................................8 
Normal Configuration Dialog (example) ........................................... 8 
Configuration Dialog with Warnings (example) ............................... 9 

3. WEB UI ............................................................... 10 


WebUI Header ......................................................................................12 
Action Buttons ................................................................................... 12 
Breadcrumb ....................................................................................... 13 
Username ........................................................................................... 14 
General Information ............................................................................14 
Accordions ......................................................................................... 14 
Eyeglasses and Open Box Symbols ................................................ 15 
Mandatory Entry Fields ..................................................................... 15 
Configuration Change Indication ..................................................... 15 
Tables ................................................................................................. 16 
Network > Node List Tab ....................................................................17 
Network > Tunnel Builder Tab............................................................19 
Node > eMS Tab ..................................................................................19 
NMS Port 1 ......................................................................................... 21 
Run Command ................................................................................... 23 
Node > Inventory Tab..........................................................................24 
Chassis ............................................................................................... 24 
Core Units .......................................................................................... 25 
Access Units ...................................................................................... 25 
Power Units ........................................................................................ 27 
Expansion Shelf................................................................................. 28 

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 4

SECTION PAGE
Node > Interfaces Tab .........................................................................29 
WAN Ports – Status Tab ................................................................... 29 
WAN Ports – Config Tab ................................................................... 30 
LAN Interfaces – Status Tab ............................................................. 32 
LAN Interfaces – Config Tab ............................................................ 34 
TDMoP Interfaces – Status Tab ........................................................ 37 
TDMoP Interfaces – Config Tab ....................................................... 39 
Node > Tunnels Tab ............................................................................42 
Introduction........................................................................................ 42 
LSR ..................................................................................................... 45 
LER ..................................................................................................... 48 
eLER (n/a to Left Core Units) ........................................................... 50 
Node > Services Tab ...........................................................................52 
Introduction........................................................................................ 52 
VPWS .................................................................................................. 53 
VPLS ................................................................................................... 60 
Node > Frequency Sync Tab ..............................................................64 
General ............................................................................................... 64 
Reference Frequency Inputs – Status Tab ...................................... 65 
Reference Frequency Inputs – Config Tab ..................................... 66 
Reference Frequency Outputs ......................................................... 68 
Node > Time Sync Tab ........................................................................68 
Introduction [To be moved to TPIM] ............................................... 68 
Time Sync........................................................................................... 68 
Alarms > Current Alarms Tab ............................................................71 
Alarms ................................................................................................ 71 
Alarms > Alarm Log Tab .....................................................................72 
Log ...................................................................................................... 72 
Alarms > Alarm Settings Tab .............................................................73 
Maintenance > Diagnostics Tab .........................................................73 
WAN Ports .......................................................................................... 76 
Bypass Ports...................................................................................... 76 
NMS Link ............................................................................................ 76 
LAN Ports ........................................................................................... 77 
TDMoP Trunk ..................................................................................... 77 
TDMoP Trunk Downlink .................................................................... 77 
TDMoP Trunk Uplink ......................................................................... 78 
TDMoP Ports ...................................................................................... 78 
Maintenance > Reports Tab ...............................................................80 
Maintenance > Firmware Tab .............................................................80 
Maintenance > Utilities Tab ................................................................80 
System Admin > User Management Tab ...........................................80 
Authorization Roles ........................................................................... 81 

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 5

SECTION PAGE
Local Users ........................................................................................ 84 
RADIUS Users .................................................................................... 85 
User Authentication Settings ........................................................... 86 
System Admin > Security Tab ............................................................87 
Operation............................................................................................ 87 
RADIUS Configuration ...................................................................... 88 
Distribution ........................................................................................ 90 

4. COMMAND LINE INTERFACE .......................... 92 


Accessing JunglePAX CLI..................................................................92 
Operation Mode Commands ..............................................................93 
“Show All” and “Show” Command Examples ................................ 94 
Core Unit Reboot ............................................................................... 94 
Reboot eMS (Management Plane) Only ........................................... 94 
Configuration Mode ............................................................................95 
“Set” Command Examples ............................................................... 96 
Configuration Scripts (example for a 2-node system) .................. 101 

APPENDIX A ......................................................... 109 


TCP/UDP Ports Used by JunglePAX ................................................109 

APPENDIX B ......................................................... 110 


List of Figures ....................................................................................110 
List of Tables ......................................................................................111 

APPENDIX C ......................................................... 112 


List of Acronyms ................................................................................112 

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 6

1. INTRODUCTION

JunglePAX Embedded Management Software (eMS) is a network management


program (p/n 90000-02) running inside every JunglePAX Core Unit. JunglePAX
nodes equipped with both left and right Core Units are thus equipped with
redundant network management functions for guaranteed high NMS availability
and reliability.

eMS runs on a microprocessor core dedicated for management plane functions.


The second microprocessor core is reserved for the JunglePAX data plane, thus
ensuring complete separation of traffic forwarding and network management
functions.

eMS enables automatic equipment discovery, facilitates configuring and


monitoring of network infrastructure and services, provides alarm and event
logging, enables effortless module additions and replacements, and facilitates
firmware upgrades while ensuring network security through user authentication
and authorization.

JunglePAX users can access eMS through the WebUI, CLI, or an external NMS
platform supporting NETCONF interface.1

WebUI is a user-friendly graphical user interface provided by the Core Unit’s


internal web server. It allows for configuring and monitoring the entire
JunglePAX network through the NMS interface of any Core Unit in the network
using a PC running an ordinary web-browser application such as Google
Chrome.

CLI is a command-line based user interface provided by the CLI interpreter


running on the Core Unit. The user interacts with the Core Unit by issuing
commands in the form of successive lines of text (command lines) from a PC
connected to the Core Unit’s NMS port. Use of CLI is not mandatory, but it is
convenient for running scripts (collection of commands) for fast node configuring.

External NMS software offers enhanced NMS functions such as graphical


network representation, centralized alarm collection and end-to-end tunnel and
service building functions. Use of external network management system (NMS)
is not considered necessary for small to medium sized JunglePAX networks.

1 Support for SNMP alarm traps will be added soon.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 7

This manual provides a detailed description of the JunglePAX WebUI and an


overview of the JunglePAX CLI commands as applicable to JunglePAX firmware
version 1.11. This document should be used in conjunction with the JunglePAX
Technical Practice and Installation Manual (TPIM).

Customer inquiries for information contained in this document should be directed


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

Revision History

Issue No. Issue Date Details of Change


Draft 1 Jan 2018 Document created. Preliminary release. Reflects
features of JunglePAX firmware version 1.11.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 8

2. GETTING STARTED

To establish a connection to a Core Unit via its NMS port, the user should know
its IP address.

Configuring Core Unit IP Address

Core Units are shipped from the factory with the following IP settings:
Default IP Address: [Link]
Default Subnet Mask: [Link]
Default Gateway Address: [Link]

The Core Unit’s IP settings can be changed by connecting physically to its front
USB port and running a serial console application such as PuTTY.

Normal Configuration Dialog (example)

Welcome to GE Lentronics JunglePAX


[Link] login: ipadmin

Current NMS port configuration:


IP/prefix is [Link]/16; (netmask = [Link])
Gateway IP is [Link]
Enter NMS port IP address/prefix, e.g. [Link]/24
[Link]/24
Enter gateway IP address for NMS port, e.g. [Link]
If you don't want to configure the gateway enter [Link]
[Link]
Press 'y' to proceed, 'n' to re-enter data, 'q' to quit
y
Suggested NMS port configuration:
IP/prefix is [Link]/24; (netmask = [Link])
Gateway IP is [Link]
Press 'y' to proceed with configuration, 'n' to re-enter data, 'q' to
quit
y
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

Bring NMS port down


Delete NMS port IP address
Set new NMS port IP address/netmask
Bring NMS port up
PHY: 0:00 - Link is Up - 100/Full
Set default route on NMS port

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 9

Welcome to GE Lentronics JunglePAX


[Link] login:  Note that the IP address in the login prompt has not
changed. This is a problem with the prompt. The
actual IP address has been changed.

Configuration Dialog with Warnings (example)

Welcome to GE Lentronics JunglePAX


[Link] login: ipadmin
Current NMS port configuration:
IP/prefix is [Link]/24; (netmask = [Link])
Gateway IP is [Link]
Enter NMS port IP address/prefix, e.g. [Link]/24
[Link]/24
Enter gateway IP address for NMS port, e.g. [Link]
If you don't want to configure the gateway enter [Link]
[Link]  Gateway IP address is outside the interface subnet.
Press 'y' to proceed, 'n' to re-enter data, 'q' to quit
Suggested NMS port configuration:
IP/prefix is [Link]/24; (netmask = [Link])
Gateway IP is [Link]
y
WARNING !!! IP/prefix and gateway IP mismatch

Press 'y' to proceed with configuration, 'n' to re-enter data, 'q' to


quit
y
Welcome to GE Lentronics JunglePAX
[Link] login:

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 10

3. WEB UI

WebUI is a user-friendly graphical user interface that allows for configuring and
monitoring the entire JunglePAX network from any Core Unit.

To start a WebUI session, do the following:


1. Obtain the NMS port’s IP address. Refer to section “Getting Started” for
information on how to configure a static IP address of the NMS port.
2. Connect a PC to the unit’s NMS port or make sure the unit’s NMS port is
reachable from your PC through the IP network.
3. Start a web browser and enter <Core Unit’s NMS Port IP Address> into its
address field. Press Enter.
Note: Use the latest version of a major web browser (Chrome is
recommended).
4. If connection to the unit exists, the view shown in Figure 1 will be displayed.
5. Enter your username and password. The main administrator’s username is
“Administrator” and his factory default password is “Administrator1”. The
administrator should change the password as soon as the unit is received
from GE (see User Management tab).
NOTE
JunglePAX administrator should change the default WebUI password as
soon as the unit is received from GE.
6. Upon successful login, the Network tab and its Node List subtab (Figure 2)
will be selected and displayed. The selected tab and subtab are highlighted
(dark blue). More information on the Node List
Note: The Core Unit the user has logged into is referred to as the gateway
Core Unit.
Note: By default, after three consecutive unsuccessful attempts, the user will
be forced to delay any new login attempts. Refer to User Authentication
Settings in the User Management Tab for more information.
Note: To store a configuration change to the unit, click on the Configure
button in the header.
Note: To update the information displayed, reload the current WebUI page.
The information provided below is for the WebUI associated with the firmware
package version 1.11.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 11

Figure 1: WebUI – Login View (appearance prior to user login)

Figure 2: Node List View

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 12

WebUI Header

The WebUI header has the same content regardless of the selected tab.

Figure 3: WebUI Header

Action Buttons

The WebUI header information includes the following action buttons:

Configure
Saves (commits) configuration changes to the unit. The button is greyed
out if no configuration changes have been made.

Note: Configuration changes made in the eMS and Interface subtabs are
saved on both left and right Core Units regardless of whether the change
is executed from the left or right Core Unit’s WebUI.

Note: Clicking on the Configure button initiates automatic validation of


configuration changes prior to saving them. See the Validate Changes
description below.

When the Configure button is active, the button can be expanded into a
command menu with the following alternative actions (Figure 4):

Figure 4: Configure button’s action menu

View Changes
Allows the user to view the configuration changes that would be saved if
the Configure button were clicked.

Validate Changes
Triggers validation of configuration changes prior to saving them. Any
illegal configuration changes (e.g. delete a tunnel with at least one

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 13

associated service, or configure something that the user is not authorized


for) will be listed.

Cancel Changes
Cancels all the changes prior to having them saved.

View Companion
Displays the same tab on the companion unit.

CLI
Opens a window that allows for directly entering commands (or pasting
scrips) for execution on the gateway Core Unit.

Logout
Logs the user out. After logout, the Login View (Figure 1) is displayed.

GE Logo
Clicking on the GE logo opens the Node List subtab.

Notifications Button
Click on the notifications symbol (exclamation mark) to open the panel
with a list of most recent notifications that are generated on various user
actions in the WebUI. Each notification category is displayed in a distinct
color. The number that appears to the bottom right of the notifications
symbol indicates the number of unread notifications.
To close the panel click on the notifications symbol again.

Figure 5: Notifications button with and without unread notifications

Breadcrumb

To the right of the notifications button is the “breadcrumb”, i.e. the WebUI path
indicator. It indicates the path to the opened page. The following format is used:

JPAX > <Local or Remote> > <Node Name>(N<Node#>) > <Side> > <Tab> <Subtab>

Local indicates that the page belongs to the local (gateway) Core Unit.
Remote indicates that the page belongs to a Core Unit that is not the gateway.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 14

Node Name displays the node name alias defined in the Node>eMS subtab. If
Node Name is not defined, the Node ID is displayed instead. For more
information on Node Name and Node ID refer to the Node>eMS subtab
description.
Node Number is a user-defined number (1-4096) associated with this node. If
not defined (default is 0), it is omitted along with the preceding letter N and
parenthesis.
Side indicates whether the page belongs to a left or right Core Unit residing at
the given node.
Tab and Subtab indicate the location of the opened page in the WebUI.

Username

Displayed in the bottom right corner of the header is the username of the person
that logged into the WebUI.

General Information

Accordions

Each tab in the WebUI includes one or more expandable and collapsible sections
(“accordions”). Click on the ‘right arrow’ to expand the accordion (Figure 6).
Click on the ‘down arrow’ to collapse the accordion.

Figure 6: Expanding and collapsing “accordions”

When a tab is opened, its first accordion is expanded automatically.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 15

Eyeglasses and Open Box Symbols

Some tables include fields with the eyeglasses symbols ( ). Click on the
eyeglasses to display a panel providing more information about the field the
eyeglasses symbol is residing in (Figure 7).

When the panel is open, the eyeglasses symbol is replaced with an open box
symbol ( ). Click on either the open box symbol or the Finish button in the
bottom right corner of the panel to close the panel.

Figure 7: Opening and closing panels associated with eyeglasses symbols

Mandatory Entry Fields

Configurable fields whose default value is ‘blank’ and require a valid entry or
option selection in order for the respective provisioning process to be completed
are indicated with an asterisk in the label.

Figure 8: Mandatory entry field

Configuration Change Indication

A configurable field whose value has been changed (but not yet committed) will
be colored in green along with its label unless the field is a combo box whose
selection triggers changes in the page content. The field will stay colored in
green until the change is either cancelled or committed (by clicking the Configure
button in the header).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 16

Figure 9: Configuration change indication (prior to committing)

Tables

Table’s content can be sorted alphabetically by the content of any of its columns.
Click on the background of the respective column’s header and toggle between
the following states: ‘sort in ascending order’, ‘sort in descending order’, and
‘don’t sort by this column’s content’.

Located immediately above the top right corner of each table are the following
action buttons:

Selects the maximum number of table entries displayed on the page.


The options available are 10, 50 (default), 100 and 500.

Refreshes the table’s content.

Allows for shortlisting the entries to only those whose specific


parameters are reporting (or are set to) specific values. After clicking
this button, a search panel shows up. Click on “Add a condition”.
Then click on the first displayed parameter and select the desired
one from the pop-up menu. Enter the first condition (search
criterion). Note that the condition must fully match the parameter’s
reading/setting. The search is case sensitive. Checkbox states are
entered as true or false. For additional conditions that should be
combined (logically ANDed) with the first one, click ‘Add a condition’
or click on the ‘+’ button on the right side of the panel. To add a new
condition group (to be logically ORed with previously defined
condition groups) click on the “+{}” button. Use the corresponding ‘x’
button to remove a condition or a condition group. Click Search to
display the matching entries. Click ‘Clear’ to remove all existing
search conditions. Note that the button is colored in green if there
are any active conditions applied to the table. Click on the button to
modify or add current search conditions.

Located immediately above the top left corner of each table is the search action
field. As an alphanumeric string is being entered into the field, the mismatched
entries are automatically filtered out. Filtering is case-sensitive. Delete the
entered string to remove filtering.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 17

Centered above the tables whose entries can be added and deleted are “Add…”
and “Delete” buttons. Click “Add…” to add a new entry. To delete an entry,
select it by clicking on its first column cell, click “Delete” and confirm the action.

If the number of table entries displayed on the page is lower than the total
number of entries in the table, the page selection panel appears immediately
below the table (Figure 10).

Figure 10: Page navigation panel

Network > Node List Tab

This tab (Figure 2) displays the Core Units visible from the gateway Core Unit
and their status. It also allows for determining the WAN port connectivity across
the networks as well as selecting individual Core Units for remote monitoring and
configuration.

Node #
Indicates the Node # configured in the Node>eMS tab of the
respective Core Units. This setting is synchronized between the
companion units, i.e. configuring either Core Unit will also configure
its companion (if present). If the two Core Units are not configured
the same for this parameter, both left and right Core Unit’s Node#
are displayed separated by a forward slash and colored in red.
Note: Node # presently acts only as a numeric alias for the node;
however, its function will be expanded in future firmware versions.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 18

Node Name
Indicates the Node Name (alphanumeric user-configured alias with
up to 22 characters) for the node as configured in the respective
Core Units’ eMS tab. This setting is synchronized between the
companion units, i.e. configuring either Core Unit will also configure
its companion (if present). If this parameter is left unconfigured
(blank), the shelf’s Node ID (consisting of the shelf option and serial
number) will be displayed instead (Figure 11). If the Node Name
on the two Core Units is not the same, the one configured on the
left unit will be displayed and colored in red.

Figure 11: Node IDs as default Node Names

Left/Right Buttons
Displayed to the left and right of the Node Name / Node ID are the
Core Unit selection buttons. Use these buttons to select the Core
Unit that needs to be monitored or configured.
The gateway Core Unit is colored in green. All other Core Units are
colored in blue. The button associated with the presently selected
Core Unit is bolded (dark blue or dark green).

DP Status
Indicates the alarm severity status of the respective Core Unit’s
Data Plane. It also reflects the status of the Power Units and
access units at the given node. May be Major, Minor, Warning or
OK. Click on the associated eyeglasses symbol to open the panel
indicating the Core Unit data plane layers in alarm. Click on the
open box symbol or click Finish to close the panel.

Figure 12: DP Alarm Status Panel

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 19

Note: Both Core Units are simultaneously driving the Form C alarm
contacts available on the Power Units’ faceplates in a logical OR
fashion. For example, if the Left Core is in Minor Alarm while the
Right Core is in Major Alarm, both Major and Minor Form C
contacts on both Power Units will be in alarm. Note that alarms
designated as Warnings, will not drive any alarm contacts.

MP Status
Indicates the alarm severity status of the respective Core Unit’s
Management Plane. May be Major, Minor, Warning or OK. Click
on the associated eyeglasses symbol to open the panel indicating
the Core Unit management plane layers in alarm. Click on the
open box symbol or click Finish to close the panel.
Note: MP alarms are not reflected on the Form C contacts.

WAN
The WAN eyeglasses symbol opens the WAN port connectivity
panel (Figure 13). It indicates the far-end node and WAN port to
which the selected near-end WAN port is connected to. Click on
the open box symbol or click Finish to close the panel.

Figure 13: WAN port connectivity panel

Network > Tunnel Builder Tab

Presently not operational.

Node > eMS Tab

The eMS tab is shown in Figure 14.

The presently selected Core Unit is framed on the JunglePAX node picture. The
user can select the companion unit by clicking on it on the picture.

Note: The settings in this tab are synchronized between the companion units, i.e.
configuring either Core Unit will also configure its companion (if present).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 20

Figure 14: eMS tab

Node Number
Allows the user to configure the Node Number (1-4096) that will be
associated with this node.
Note: This parameter should be configured the same on both Core
Units. Its use is presently optional as it currently acts only as a
numeric alias for the node. Its function will be expanded in the
future firmware versions.

Node Name
Allows the user to configure the node name (up to 22 alphanumeric
characters). If not configured, the shelf’s Node ID (see below) will
be displayed instead.
Note: This parameter should be configured the same on both Core
Units.

DP Status
Indicates the alarm severity status of the selected Core Unit’s Data
Plane. It also reflects the status of the local Power Units and
access units. May be Major, Minor, Warning or OK.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 21

Note: Both Core Units are simultaneously driving the Form C alarm
contacts available on the Power Units’ faceplates in a logical OR
fashion. Only Major and Minor alarms are driving Form C contacts.

MP Status
Indicates the alarm severity status of the respective Core Unit’s
Management Plane. May be Major, Minor, Warning or OK.
Note: These alarms are not reflected on the Form C contacts.

NMS Port 1

The Status tab (Figure 14) indicates the status of the faceplate NMS port. The
Config tab (Figure 15) allows for setting the NMS port’s DHCP mode and static
IP parameters when DHCP is set to ‘Disabled’.

Figure 15: NMS Port 1 – Config Tab

Note: Presently, NMS ports 1 and 2 are treated as a single port (NMS port 1).
Only one of them can be used at a time.

Link Status (applicable to Status tab only)


Indicates the status of the NMS port’s link.

DHCP
Information displayed in the Status tab indicates the DHCP mode
configured in the Config tab.
Disabled (Default) The port’s network parameters are assigned
manually. The Local IP, Subnet Mask and Gateway
IP fields in the Config tab are user-configurable.
Client An external DHCP server is present in the network
and this port’s IP address is assigned automatically.
The respective Subnet Mask and Gateway IP are also
provided by the external DHCP server and are not
user-configurable.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 22

Server The port is to be connected directly to a PC whose IP


address will be assigned automatically. The port’s
DHCP server function is enabled and it assigns an IP
address to the port itself and to the connected PC.
The respective Subnet Mask is also provided by the
internal DHCP server.

WARNING
If the NMS port is connected to an IP network with a DHCP
server and the port’s DHCP Server function is enabled, the IP
network operation may be seriously impacted!

Local IP
When the DHCP field is set to ‘Disabled’, the information displayed
in the Status tab indicates the Local IP configured in the Config tab.
When the port’s DHCP field is configured for either the Client or
Server mode, the port's IP address is assigned automatically.
Otherwise, a valid static IP address for the port must be entered in
the Config tab.
Note: If the port’s DHCP field is set to ‘Disabled’, the user should
manually enter the port’s static IP address, Subnet Mask and
Gateway IP (if applicable) in the Status tab.
Note: If the NMS port’s DHCP field is set to ‘Server’, its IP address
([Link]) will be automatically assigned as soon as an external
Ethernet device is connected to the port.
Note: If the port is set for the Client mode and an external DHCP
server is not available, the port’s Local IP field will display [Link].
The same is displayed for a disconnected NMS port whose Server
function is enabled.

Subnet Mask
A subnet is a segment of a network that shares a common address.
A subnet mask is used within networks to simplify the routing tables
of gateway routers used to manage IP traffic, to add security and
improve network performance.
When DHCP is set to ‘Disabled’, the information displayed in the
Status tab indicates the Subnet Mask configured in the Config tab.
Note: When the DHCP field is set to ‘Client’ and the port is
connected to a network with DHCP server available, the subnet

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 23

mask is not user-configurable. The mask displayed in the Status


tab (if any) is provided by the external DHCP server.
Note: When the NMS port’s DHCP field is set to ‘Server’, the
subnet mask [Link] is applied to allow for only two hosts
in the subnet. In this mode, the IP addresses [Link] and
[Link] will be assigned to the NMS port and the connected
device, respectively.

Gateway IP
LAN’s are typically managed by devices that limit the MAC domains
to improve the dependability and efficiency of the LAN. Gateway
routers provide this functionality and therefore must be assigned an
IP address. All hosts on a LAN (including the NMS port) must
establish a connection with this gateway to communicate with
devices external to the LAN.
When DHCP is set to ‘Disabled’, the information displayed in the
Status tab indicates the Gateway IP configured in the Config tab.
Note: When the DHCP field is set to ‘Client’ and the port is
connected to a network with DHCP server available, the Gateway
IP is not user-configurable. The Gateway IP displayed in the Status
tab (if any) is provided by the external DHCP server.
Note: When the NMS port’s DHCP field is set to ‘Server’, the
Gateway IP is neither user-configurable nor automatically assigned.

MAC Address
Displays the port’s MAC address.

Run Command

Allows for executing a specific command (as instructed by GE).

WARNING: Do not attempt to arbitrarily enter any commands in this field.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 24

Node > Inventory Tab

The Inventory tab’s Chassis and Core Unit accordions are shown in Figure 16.
The Access Unit accordion is shown in Figure 17 while the Power Units and
Expansion Shelf accordions are shown in Figure 18.

Chassis

Type ID
Indicates the shelf’s part number.

Serial ID
Indicates the shelf’s serial number.

HW Version
Indicates the shelf’s hardware version.

Figure 16: Inventory tab’s Chassis and Core Units accordions

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 25

Core Units

Slot
Indicates the slot (left or right) that the selected Core Unit is residing
in.

Type ID
Indicates the Core Unit’s part number.

Description
Describes the WAN ports the Core Unit is equipped with.

HW Version
Indicates the Core Unit’s hardware version.

Serial #
Indicates the Core Unit’s serial number.

Firmware
Click on the eyeglasses to display the Core Unit’s firmware
information. The Core Unit’s firmware package includes four
components: the management plane (MP) firmware, data plane
operating system (DP-OS) firmware, data plane field programmable
gate array (DP-FPGA) firmware, and bootloader firmware.

SFPs
Click on the eyeglasses to display the information on equipped
WAN port SFP transceivers. The table displays the summary of
most important parameters. Click on the port number to open a
sub-panel with more SFP details.
Note: The table provides a selection of parameters provided in the
sub-panel.

Access Units

Provides the list of access units residing in this JunglePAX shelf.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 26

Figure 17: Inventory tab’s Access Units accordion

Slot
Indicates the slot (1 - 16) that the given access unit is residing in.

Type ID
Indicates the serial number of this access unit.

Description
Provides the description of this access unit.

HW Version
Indicates the access unit’s hardware version.

Serial #
Indicates the serial number of this access unit.

Firmware
Indicates the firmware version of this access unit.

SFPs
Click on the eyeglasses to display the information on equipped
access port SFP transceivers. Applicable only to 90200-01 SFP
access units. The table displays the summary of most important

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 27

SFP parameters. Click on the port number to open a sub-panel


with more SFP details.
Note: The table provides a selection of parameters provided in the
sub-panel.

Power Units

Slot
Indicates the slot (0 or 17) the Power Unit is residing in.

Type ID
Indicates the Power Unit’s part number.

HW Version
Indicates the Power Unit’s hardware version.

Serial #
Indicates the Power Unit’s serial number.

Figure 18: Inventory tab’s Power Unit’s and Expansion Shelf accordions

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 28

Expansion Shelf

Provides the list of legacy DS0 access units residing in Expansion shelf/shelves.

CBUS Slot
Indicates the slot (15 or 16) that the CBUS unit feeding the given
legacy DS0 access unit is residing in.

CBUS Port
Indicates the port (1, 2, 3 or 4) on the CBUS unit that feeds the
channel bus on which the given legacy DS0 access unit is residing.

Rack#, Shelf#, Slot#


Indicates the rack, shelf and slot in which the given legacy DS0
access unit is residing (as programmed in the legacy DS0 access
unit itself).

Unit Type
Indicates the type of this legacy DS0 access unit.

Serial #
Indicates the serial number of this legacy DS0 access unit.

Firmware
Indicates the firmware version of this legacy DS0 access unit.

Part Number
Indicates the part number of this legacy DS0 access unit.

Allocated Channels
Indicates the DS0 channel(s) assigned to this legacy DS0 access
unit (as programmed in the legacy DS0 access unit itself).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 29

Node > Interfaces Tab

WAN Ports – Status Tab

The Status tab info for the Interfaces tab’s WAN Ports accordion is shown in
Figure 19.

Figure 19: Interfaces tab’s WAN Ports accordion – Status tab

This tab provides the list of WAN ports on the selected Core Unit (the first
character indicates the side, while the second character indicates the port
number). Click on the desired port to display a panel with more information for
the port.

Port Enable
True indicates that the port is enabled (per the respective setting in
the Config tab).

Interface Type
Indicates 10G for ports 1 and 2. 1G for ports 3-6.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 30

Near-End MAC (hidden for disabled ports)


Indicates the MAC address associated with the given local WAN
port.

Far-End MAC (hidden for disabled ports)


Indicates the MAC address of the presently connected far-end WAN
port.

Expected Far-End MAC (hidden for disabled ports) (N/A to version 1.11+)
Indicates the MAC address expected at the far end. Not displayed
if the Far-End MAC is matching the expected one.
Note: If the far-end WAN port’s MAC address is changed (e.g. due
to accidental fiber misconnection or Core Unit replacement), the
Expected Far-End MAC is displayed. The user needs to click on
the Accept button (appears in this panel) at both ends of the WAN
link to reestablish traffic on this link. In the firmware version 1.11,
the WAN port MAC address change notification and respective
traffic blocking are disabled. Traffic blocking on MAC mismatch will
be made an optional feature in future firmware releases.

B1 BER (hidden for disabled ports)


Indicates the current bit error rate for the WAN port section layer.
B1 refers to the respective WIS overhead byte.

B3 BER (hidden for disabled ports)


Indicates the current bit error rate for the WAN port path layer. B3
refers to the respective WIS overhead byte.

WAN Ports – Config Tab

The Config tab info for the Interfaces tab’s WAN Ports accordion is shown in
Figure 20.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 31

Figure 20: Interfaces tab’s WAN Ports accordion – Config tab

Provides the list of WAN ports on the selected Core Unit (the first character
indicates the side, while the second character indicates the port number). Click
on the desired port to display a panel with more information for the port. Note
that WAN ports on both Core Units can be configured from either Core Unit.
Note: The settings in this tab are synchronized between the companion units, i.e.
configuring either Core Unit will also configure its companion (if present).

Port Enable
Check the box to enable the port.

Port Alias
Enter an optional name alias for the port. Up to 32 characters.

B1 BER Threshold (hidden for disabled ports)


Allows the user to configure the B1 BER threshold. When
exceeded, an alarm will be raised and port traffic will be disabled.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 32

B3 BER Threshold (hidden for disabled ports)


Allows the user to configure the B3 BER threshold. When
exceeded, an alarm will be raised and port traffic will be disabled.

LAN Interfaces – Status Tab

The Status tab info for the LAN Interfaces accordion is shown in Figure 21. It
provides the list of LAN interfaces (LAN ports) in this shelf. Click on the desired
port to display a panel with more information for the port.

Figure 21: Interfaces tab’s LAN Interfaces accordion – Status tab

Slot
Indicates the slot (1-7, 13, 15) that can accommodate a LAN
interface unit (SFP or PHY).

Port
Indicates the port number (1, 2, 3 or 4 for slots 1, 3 and 5. 4 for
slots 2, 4, 6, 7, 13 and 15).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 33

Unit Type
Indicates the type of interface unit installed in this slot. ‘Slot Empty’
indicates that the slot is unequipped.

Port Enable
True indicates that the port is enabled (as configured in the Config
tab).

Output
Indicates whether the port is online or offline for the receive traffic
(i.e. for the traffic outputted from this port).

Link Status
Indicates the status of the Ethernet link established to the port (as
perceived by the local Core Unit). May read “Up” (link is up and
running) or “Down” (link is down).

Port Frame Max


Indicates the maximum Ethernet frame length that will be allowed to
ingress the port. Factory preset to 2200.

Rx Priority
Indicates the Core Unit (left or right) that should be normally online
for the traffic received from the far end. Applicable only to ports in
Bulk mode (see Config tab).

Port Speed
Indicates the port’s speed configured in the Config tab.

Rate Ingress
Indicates ingress rate limiting applied (as configured in the Config
tab). No Limit (default) indicates no rate limiting applied.

Rate Egress
Indicates ingress rate limiting applied (as configured in the Config
tab). No Limit (default) indicates no rate limiting applied.

Rate in Use (not applicable to SFP ports)


Indicates the present port speed (may be autonegotiated or forced,
as configured in the Config tab). ‘Link Down’ indicates that the port
is disconnected or the link is inactive.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 34

LAN Interfaces – Config Tab

The Config tab info for the LAN Interfaces accordion is shown in Figure 22 (with
an SFP panel expanded) and Figure 23 (with a PHY panel expanded). Click on
the desired port to expose all configurable parameters for the port.
Note: A LAN interface port can be preconfigured prior to having the matching
interface unit installed.
Note: Whenever an access unit has been added, replaced or reseated, go to the
Interface tab, or, if you are already in the Interface tab, refresh the page (F5) in
order for the preconfigured settings to take effect.
Note: The settings in this tab are synchronized between the companion units, i.e.
configuring either Core Unit will also configure its companion (if present).

Figure 22: Interfaces tab’s LAN Interfaces accordion – Config tab (SFP panel)

Slot
Indicates the slot (1-7, 13, 15) that can accommodate a LAN
interface unit (SFP or PHY).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 35

Figure 23: Interfaces tab’s LAN Interfaces accordion – Config tab (PHY panel)

Port
Indicates the port number (1, 2, 3 or 4 for slots 1, 3 and 5. 4 for
slots 2, 4, 6, 7, 13 and 15).

Port Alias
Enter an optional name alias for the port. Up to 32 characters.
Note that the port alias cannot be changed if at least one service is
associated with the port.

Unit Type
Select the unit type (SFP or PHY) that needs to be installed in the
slot associated with this port. If a mismatched unit is installed (as
indicated in the Status tab), the configuration settings for this port
will not take effect.

Port Enable
Check the box to enable the port.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 36

Mode
May be set to Bulk or Shared (default). See the Protection
Switching section for more information on the port mode selection.

Rx Priority (n/a to ports in Shared Mode)


Sets the Core Unit (left or right) that should be normally online for
the traffic received from the far end. Applicable only to ports in Bulk
mode. See the Protection Switching section for more information.

Default Priority
Sets the default priority that will be applied to untagged ingress
frames. Note that tagged frames are prioritized based on their
802.1p priority except that frames with 802.1p priority set to 7 are
treated as priority 6 frames. (This is because priority 7 is reserved
for critical TDMoP traffic.) The valid range for Default Priority
should be 0 – 6 although the presently allowed range is 0 – 7.

Port Speed
Sets the port speed on the unit’s switch. The possible settings are:
Default (1G), 100M or 10M (n/a to SFP). This field will be
eventually merged with Rate Allowed below.

Rate Ingress
Sets the ingress rate limiting. Possible selections are: No Limit
(default), 128 kbps, 256 kbps, 512 kbps, 1 Mbps, 10 Mbps, 50
Mbps, 100 Mbps, 200 Mbps, 400 Mbps, 800 Mbps.

Rate Egress
Sets the egress rate limiting. Possible selections are: No Limit
(default), 128 kbps, 256 kbps, 512 kbps, 1 Mbps, 10 Mbps, 50
Mbps, 100 Mbps, 200 Mbps, 400 Mbps, 800 Mbps.

Rate Allowed (n/a to SFP ports)


May be configured for one of the following::
- auto Autonegotiation is enabled (default)
- 1000fdx Force 1000 Mpbs, Full Duplex
- 1000hdx Force 1000 Mpbs, Half Duplex
- 100fdx Force 100 Mpbs, Full Duplex
- 100hdx Force 100 Mpbs, Half Duplex
- 10fdx Force 10 Mpbs, Full Duplex
- 10hdx Force 10 Mpbs, Half Duplex
WARNING: Presently, having autonegotiation enabled for a PHY port in
Bulk mode may cause permanent Down Link alarm reported by the port’s

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 37

non-priority (protect) Core Unit. In that case, either reboot the port’s
priority Core Unit, or cycle the port’s Rx Priority setting. Note that keeping
the port’s non-priority Core Unit in permanent Link Down alarm will cause
an extended protection switching time because the protect port will need
to autonegotiate rate and duplex mode prior to taking the traffic over.

Crossover (n/a to SFP ports)


May be configured for one of the following::
- auto Autosensing enabled (default)
- mdi Straight-through mode
- mdix Crossover mode

TDMoP Interfaces – Status Tab

The Status tab info for the TDMoP Interfaces accordion is shown in Figure 24.

Figure 24: Interfaces tab’s TDMoP Interfaces accordion – Status tab

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 38

Packetizer Mode
Indicates the mode the packetizer is set for. May be T1 or E1. The
packetizer mode is presently not configurable through the WebUI.
Normally, the units shipped to North-American customers are
factory preset for T1 mode while the ones shipped to overseas
customers are preset for E1 mode. Please contact GE Lentronics if
the packetizer mode needs to be changed.

The table’s Status tab displays the 8 TDMoP ports available on the Core Units’
packetizer. Click on a desired port to display a panel with more information on
the port.

Port Type
Indicates the type of interface this port is configured for (see the
Config tab’s Port Type field). Note the following:
- T1 is displayed if the configured Port Type is T1/E1 and the
Packetizer Mode is T1.
- E1 is displayed if the configured Port Type is T1/E1 and
Packetizer Mode is E1.
- CBUS is displayed if the configured Port Type is CBUS.

Port Enable
True indicates that the port is enabled (as configured in the Config
tab).

Output
Indicates whether the port is online or offline for the receive traffic
(i.e. for the traffic outputted on this port).

Access Card Port


Indicates the access unit’s port# associated with the type of unit
selected in the Config tab’s Port Type field for this TDMoP port.
Refer to TDM Port Mapping in the TDM Data Packetizing section of
the JunglePAX Technical Practice and Installation Manual.

Access Card Slot


Indicates the shelf slot number associated with the type of unit
selected in the Config tab’s Port Type field for this TDMoP port.
Refer to TDM Port Mapping in the TDM Data Packetizing section of
the JunglePAX Technical Practice and Installation Manual.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 39

Access Card Unit Type


Indicates the type of interface unit presently installed in the slot
indicated in the Access Card Slot field above. ‘Slot Empty’
indicates that the slot is unequipped.

Rx Priority
Indicates the Core Unit (left or right) that should be normally online
for the traffic received from the far end. Applicable only to ports in
Bulk mode (see Config tab).

Rx Gain Limit (applicable only to T1/E1 ports)


Always indicates Short Haul (max cable length of 655ft/200m).

Output Clock Mode (applicable only to T1/E1 ports)


Reflects the respective setting in the Config tab. Indicates the clock
source for the outputted T1/E1 signal. May read SyncE (JunglePAX
system clock), Adaptive Recovery (future use; will be used only if
the service is SAToP – Bulk T1/E1), or LIU Loopback (clock derived
from the locally inputted T1/E1 signal).

Framing (applicable only to T1 ports)


Reflects the respective setting in the Config tab. For T1 it may read
ESF or SF. For E1 ports, PCM30-CRC is assumed.

Line Code (applicable only to T1 ports)


Reflects the respective setting in the Config tab. It may read B8ZS
or AMI. For E1 ports, HDB3 is assumed.

TDMoP Interfaces – Config Tab

The Config tab info for the TDMoP Interfaces accordion is shown in Figure 25
(with a T1 panel expanded) and Figure 26 (with a CBUS panel expanded). Click
on the desired port to expose all configurable parameters for the port.
Note: A TDMoP interface port can be preconfigured prior to having the matching
interface unit installed.
Note: Whenever an access unit has been added, replaced or reseated, open the
Interface tab, or, if you are already in the Interface tab, refresh the page (F5) in
order for the preconfigured settings to take effect.
Note: The settings in this tab are synchronized between the companion units, i.e.
configuring either Core Unit will also configure its companion (if present).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 40

Figure 25: Interfaces tab’s TDMoP Interfaces accordion – Config tab (T1/E1
panel)

Port Type
Select the unit type (T1/E1 or CBUS) that needs to be installed in
the slot associated with this port. If a mismatched unit is installed
(as indicated in the Status tab’s Access Card Unit Type field), the
configuration settings for this port will not take effect.

Port Alias
Enter an optional name alias for the port. Up to 32 characters.
Note that the port alias cannot be changed if at least one service is
associated with the port.

Port Enable
Check the box to enable the port.
Note: Port Enable cannot be committed prior to committing the Port
Type.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 41

Mode
May be set to Bulk or Shared (default). See the Protection
Switching section for more information on the port mode selection.
Note: This setting cannot be changed if the port has at least one
service assigned to it.

Figure 26: Interfaces tab’s TDMoP Interfaces accordion – Config tab (CBUS
panel)

Rx Priority (n/a to ports in Shared Mode)


Sets the Core Unit (left or right) that should be normally online for
the traffic received from the far end. Applicable only to ports in Bulk
mode. See the Protection Switching section for more information.

Output Clock Mode (applicable only to T1/E1 ports)


Sets the clock source for the outputted T1/E1 signal. The options
available are: SyncE (JunglePAX system clock; default). Adaptive
Recovery (future use; will be used only if the service is SAToP –
Bulk T1/E1), or LIU Loopback (clock derived from the locally
inputted T1/E1 signal).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 42

Framing (applicable only to T1 ports)


Sets the T1 framing for either ESF (default) or SF.
Note: In firmware version 1.11, E1 ports are using PCM30-CRC
framing regardless of the selection made in this field. Additionally,
version 1.11 does not support E1 CAS, so voice circuits with
associated signaling cannot be properly packetized.

Line Code (applicable only to T1 ports)


Sets the T1 line code for B8ZS (default) or AMI.

Node > Tunnels Tab

Introduction

Each tunnel has its near and far-end LER Core Unit and, optionally, one or more
LSR (pass-through Core Units). Additionally, the tunnels terminated on a Left
Core Unit and passed on to it through the Right Core Unit are designated as
eLER (extended LER) tunnels on the Right Core. The Right Core normally acts
as an LSR for such tunnel, but it also acts as an LER when the Left Core
becomes unavailable.

In the example in Figure 27, the Right Core at Node A and the Left Core at Node
F are acting as LER for Tunnel 1, while the Left Core at Node A and the Right
Core at Node F are acting as LER for Tunnel 2.

In the example in Figure 28, the Left Core units at nodes A and F are acting as
LER for Tunnel 3, while the right Cores at nodes A and F are acting as eLER for
this tunnel.

Note: eLER tunnels are applicable only to Right Core units. Each eLER on the
Right Core has its associated LER on the Left Core. However, not every LER on
the Left Core has its associated eLER on the Right Core.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 43

Figure 27: Examples of tunnels without eLERs

Figure 28: Example of a tunnel with eLER (Tunnel 3)

An example of a network without redundant Core Units is shown in Figure 29.


Only the Left Core Unit is installed at every node. Note that eLER tunnels are
not applicable and only 1:1 path protection may be used.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 44

Figure 29: Examples of tunnels in a network without redundant Core Unit

Examples of LSR, LER and eLER tunnels in various linear network solutions are
shown in Figure 30.

LER LSR LSR LSR LSR LER


Linear network with no redundancy
(upgradable to a ring with 1+1/ 1:1 L R L R L R L
protection and hardware redundancy) LER LSR LSR LER

Linear network with no redundancy LER LSR LSR LER


(upgradable to a ring with 1:1 path L L L L
protection and no hardware
redundancy) LER LSR LER

LER LSR LSR LER


1:1 path protection over a linear
network with path redundancy and no L L L L
hardware redundancy LER LSR LSR LER

LER LSR LSR LER


1+1 path protection over a linear
L L L L
network with path and hardware R R
R R
redundancy LER LSR LSR LER

1:1 path protection over a linear LER LSR LSR LER


L L
network with path and hardware L L
R R R R
redundancy (needed for VPLS
services) eLER LSR LSR eLER

Figure 30: LSR, LER and eLER tunnels in various linear network solutions

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 45

Examples of LSR, LER and eLER tunnels in a ring network with attached spur
are shown in Figure 31.

R L

LSR LSR
1:1 protection over a L R
LSR LER
“ring+spur” topology LER LSR L L
LER LSR
R L LSR LER
LSR LSR LSR

L R

R L

LSR LSR
1+1 protection over a L R LSR LSR LER
“ring+spur” topology LER LSR R L R L
LER LSR
R L LSR LSR LSR LSR LER
LSR LSR

L R

R L

1:1 protection over a LSR LSR


L R
“ring+spur” topology LSR LSR eLER LER
LER LSR R L R L
(needed for VPLS services)
eLER LSR
where 1+1 protected
R L LSR LSR LSR LSR LER
services are also needed LSR LSR

L R

Figure 31: Examples of LSR, LER and eLER tunnels on a spur

The Tunnels tab consists of 3 accordions: LSR, LER and eLER. Note that the
eLER accordion is not applicable to the Left Core unit.

LSR

The LSR accordion is shown in Figure 33. It displays the provisioned LSR (pass-
through) tunnels on the local Core Unit and allows for adding new LSR tunnels.

From the local node’s perspective, there are two types or LSR tunnels:
- those whose entry and exit ports are on different Core Units (see node G for
Tunnel 1 and nodes B, C and E for Tunnel 2 in Figure 27)
- those whose both entry and exit ports are on the same Core Unit (Left Core at
node D for Tunnel 1, and Right Core at node D for Tunnel 2 in Figure 27).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 46

The former are bypassed through either Bypass 1 or Bypass 2 port (see Figure
32) and need to be provisioned in both Left and Right Core units, while the latter
are provisioned in only one Core Unit.

Byp1 Byp1
R1 L1
Byp2
or R1
Byp2
L1

Figure 32: LSR tunnels bypassed between Core Units

To view or edit an existing LSR tunnel, click on the tunnel’s Local ID. This
opens a panel with the tunnel’s present settings. Note that the parameters
provided in the table are a selection of parameters in the panel.

To add a new LSR tunnel, click on the ‘Add…’ button above the table, enter an
unused Local ID (typically, the next available Local ID is entered) and click ‘Add’.
Select or enter the desired values for all parameters and click ‘Finish’. Click on
the ‘Configure’ button in the header.

To delete an LSR tunnel, click on the background of the Local ID cell associated
with the LSR tunnel to be deleted and click on the Delete button above the table.
Confirm the action and click ‘Configure’ in the header to save changes to the unit.

Figure 33: Tunnel tab’s LSR accordion

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 47

Local ID
The local ID associated with the given LSR tunnel. Must be in the
1-2048 range. Defined at the time the tunnel is created and cannot
be edited afterwards.

Name
Enter tunnel name. Up to 32 characters.

Port A*
Select the WAN port (or first of the two WAN ports) associated with
this LSR tunnel.

Port B*
Select the bypass port (or second of the two WAN ports) associated
with this LSR tunnel.

Label out A*
Enter the tunnel’s outgoing LSP label on Port A. The allowed range
is 255-1048575.

Label in A*
Enter the tunnel’s incoming LSP label on Port A. The allowed
range is 255-1048575.
Note: For each Core Unit, each “In” label must be unique across all
configured local LSR/LER/eLER tunnels.
Note: It is recommended that ‘In’ and ‘Out’ labels for a given tunnel
are different. This is mandatory for the LSR tunnels that are passed
through only one Core Unit, and for eLER tunnels. Typically, one
label is used for one direction of the entire tunnel, while another
label is used for its other direction, with a different pair of labels
used for eLER’s bypass port (if applicable).

Label out B*
Enter the tunnel’s outgoing LSP label on Port B. The allowed range
is 255-1048575.

Label in B*
Enter the tunnel’s incoming LSP label on Port B. The allowed
range is 255-1048575.
Note: For each Core Unit, each “In” label must be unique across all
configured LSR/LER/eLR tunnels.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 48

Note: It is recommended that ‘In’ and ‘Out’ labels for a given tunnel
are different. This is mandatory for LSR nodes where tunnel is
passed through one Core Unit only. Typically, one label is used
along the entire tunnel for one direction, and another label is used
along the entire tunnel for the other direction.

LER

The LER accordion’s Config tab is shown in Figure 34. It displays the
provisioned LER tunnels on the local Core Unit and allows for adding new LER
tunnels.

Figure 34: Tunnel tab’s LER accordion (Config tab)

To view or edit the settings for an existing LER tunnel, locate the tunnel in
the Config tab and click on its Local ID. This opens a panel with the tunnel’s
present settings. Note that the parameters provided in the table are a selection
of parameters in the panel.

To add a new LER tunnel, click on the ‘Add…’ button located above the Config
tab’s table, enter an unused Local ID (typically, the next available Local ID is
entered) and click ‘Add’. Select or enter the desired values for all parameters
and click ‘Finish’. Click on the ‘Configure’ button in the header.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 49

To delete an LER tunnel, click on the background of the Local ID cell associated
with the LER tunnel to be deleted and click on the Delete button above the table.
Confirm the action and click ‘Configure’ in the header to save changes to the unit.
Note: Only LER tunnels with no services assigned to them can be deleted.

Local ID
The local ID associated with the given LER tunnel. Must be in the
1-2048 range. Defined at the time the tunnel is created and cannot
be edited afterwards.

Name
Enter tunnel name. Up to 32 characters.

Port*
Select the WAN port associated with this LER tunnel.

Label Out*
Enter the tunnel’s outgoing LSP label. The allowed range is 255-
1048575.

Label In*
Enter the tunnel’s incoming LSP label. The allowed range is 255-
1048575.
Note: For each Core Unit, each “In” label must be unique across all
configured local LSR/LER/eLER tunnels.
Note: It is recommended that ‘In’ and ‘Out’ labels for a given tunnel
are different. This is mandatory for LSR tunnels passed through
only one Core Unit, and for eLER tunnels. Typically, one label is
used for one direction of the entire tunnel, while another label is
used for its other direction, with a different pair of labels used for
eLER’s bypass port (if applicable).

BFD
Set the BFD to ‘on’ (default) or ‘off’. It is strongly recommended
that BFD be enabled for all provisioned tunnels because, otherwise,
tunnel continuity cannot be monitored.
Note: BFD must be enabled for tunnels carrying protected services.
The Core Unit can support a maximum of 256 LER/eLER tunnels
with BFD enabled.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 50

The LER accordion’s Status tab is shown in Figure 35. It displays the BFD status
(up or down) for each provisioned tunnel with BFD enabled as detected at the
time the page was loaded or refreshed last time.
Note: Refresh the page (F5 button) to update the BFD status info.

Figure 35: Tunnel tab’s LER accordion (Status Tab)

eLER (n/a to Left Core Units)

The eLER accordion’s Config tab is shown in Figure 36. It displays the
provisioned eLER tunnels on the local Core Unit and allows for adding new eLER
tunnels.

Figure 36: Tunnel tab’s eLER accordion (n/a to Left Core)

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 51

To view or edit the settings for an existing eLER tunnel, locate the tunnel in
the Config tab and click on its Local ID. This opens a panel with the tunnel’s
present settings. Note that the parameters provided in the table are a selection
of parameters in the panel.

To add a new eLER tunnel, click on the ‘Add…’ button located above the Config
tab’s table, enter an unused Local ID (typically, the next available Local ID is
entered) and click ‘Add’. Select or enter the desired values for all parameters
and click ‘Finish’. Click on the ‘Configure’ button in the header.

To delete an eLER tunnel, click on the background of the Local ID cell


associated with the eLER tunnel to be deleted and click on the Delete button
above the table. Confirm the action and click ‘Configure’ in the header to save
changes to the unit.
Note: Only eLER tunnels with no services assigned to them can be deleted.

Local ID
The local ID associated with the given eLER tunnel. Must be in the
1-2048 range. Defined at the time the tunnel is created and cannot
be edited afterwards.

Name
Enter tunnel name. Up to 32 characters.

Port A*
Select the local WAN port associated with this eLER tunnel.

Label out A*
Enter the tunnel’s outgoing LSP label on Port A. The allowed range
is 255-1048575.

Label in A*
Enter the tunnel’s incoming LSP label on Port A. The allowed
range is 255-1048575.
Note: For each Core Unit, each “In” label must be unique across all
configured local LSR/LER/eLER tunnels.
Note: For eLER tunnels, the labels used on the Bypass port must
be different from the ones used on the WAN port.

Port B*
Select the Bypass port (byp1 or byp2) associated with this eLER
tunnel.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 52

Label out B*
Enter the tunnel’s outgoing LSP label on Port B. The allowed range
is 255-1048575.

Label in B*
Enter the tunnel’s incoming LSP label on Port B. The allowed
range is 255-1048575.
Note: For each Core Unit, each “In” label must be unique across all
configured local LSR/LER/eLER tunnels.
Note: For eLER tunnels, the labels used on the Bypass port must
be different from the ones used on the WAN port.

BFD
Set the BFD to ‘on’ (default) or ‘off’. It is strongly recommended
that BFD be enabled for all provisioned tunnels because, otherwise,
tunnel continuity cannot be monitored.
Note: BFD must be enabled for tunnels carrying protected services.
The Core Unit can support a maximum of 256 LER/eLER tunnels
with BFD enabled. If there is a concern that this limit is likely to be
reached, the user may choose to disable BFD for tunnels with no
intermediate nodes (no LSRs).

The eLER accordion’s Status tab is similar to the LER one shown in Figure 35. It
displays the BFD status (admin down, up or down) for each provisioned tunnel
with BFD enabled as detected at the time the page was loaded or refreshed last
time. ‘Admin down’ is displayed as long as the Left Core is operational.
Note: Refresh the page (F5 button) to update the BFD status info.

Node > Services Tab

Introduction

There are two basic categories of services: VPWS (point-to-point) and VPLS
(point-to-multipoint [hub-and-spoke] or multipoint-to-multipoint [any-to-any]).1
Note the following:
- VPWS service can be either Ethernet (E-Line) or TDMoP.

1 Point-to-point Ethernet services are often referred to as E-Line. Point-to-multipoint and


multipoint-to-multipoint Ethernet services are also referred to as E-Tree and E-LAN, respectively.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 53

- VPLS service can only be Ethernet (E-Tree or E-LAN).


- VPWS service uses only one pseudowire.
- VPLS service uses multiple pseudowires.
o In point-to-multipoint (hub-and-spoke) applications, the outer end of
each spoke is associated with only one pseudowire.
- VPWS services are associated with only one access port at each end.
- VPLS services may be associated with multiple access ports at each end.
(This feature is not operational in firmware versions up to 1.11).
- Each TDMoP service is associated with a bundle that may include one or
multiple DS0/64kbps channels on the given port.
o The bundle IDs at the two ends must match.
o The number of channels at each end must match.
o The lowest channel number at the near end is matched with the
lowest channel at the far end. All other channels are matched in
the ascending order.
- Ethernet services can be defined either as “per port” (the entire port traffic is
forwarded) or “per port and VLAN” (only the selected VLAN traffic is
forwarded).
- Services associated with access ports in Bulk mode can implement only 1+1
path protection switching.
- Services associated with access ports in Shared mode can implement only
1:1 path protection switching.
- VPLS services require use of Shared access ports and can therefore
implement only 1:1 path protection switching.

The Services tab consists of two accordions: VPWS and VPLS.

VPWS

Figure 37 shows the VPWS accordion with a panel opened for a TDM service
implementing 1:1 path protection. Figure 38 shows the same accordion with a
panel opened for a new Ethernet service configured for 1+1 path protection.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 54

Figure 37: VPWS accordion with a TDM service panel opened

To view or edit the settings for an existing VPWS service, locate the service
in the table and click on its Local ID. This opens a panel with the service’s
present settings. Note that the parameters provided in the table are a selection
of parameters in the panel.

To add a new service, click on the ‘Add…’ button located above the table, enter
an unused Local ID (typically, the next available Local ID is entered) and click
‘Add’. Select or enter the desired values for all parameters and click ‘Finish’.
Click on the ‘Configure’ button in the header.

Note: After making any changes to the Packetizing Mode or Signaling Channel
fields, click Finish and reopen the panel prior to making any changes to the
Frame Count field.

Note: In Firmware version 1.11, some configuration changes may require unit
reboot to take effect. This will be corrected in the next version of the firmware.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 55

Figure 38: VPWS accordion with an add service panel for Ethernet service
implementing 1+1 path protection

To delete a service, click on the background of the Local ID cell associated with
the service to be deleted and click on the Delete button above the table. Confirm
the action and click ‘Configure’ in the header to save changes to the unit.
Local ID
The local ID associated with the given VPWS service. Must be in
the 1-2048 range. Defined at the time the service is created and
cannot be edited afterwards.

Name
Enter service name. Up to 32 characters.

Label Out*
Enter the service’s outgoing pseudowire label. The allowed range
is 255-1048575.

Label In*
Enter the service’s incoming pseudowire label. The allowed range
is 255-1048575.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 56

Note: It is recommended that ‘In’ and ‘Out’ labels for a given


pseudowire are different. Typically, each pseudowire uses a
globally (customer-network-wide) unique pair of labels.

Category*
Select the service category (‘tdm’ or ‘ethernet’).

Port*
Select the local access port associated with this service. If the
selected category is ‘tdm’, the selected port must be a TDM port. If
the selected category is ‘ethernet’, the selected port must be an
Ethernet port.
Note: Only enabled TDM ports can be assigned to a TDM service.
An attempt to assign a disabled TDM port will produce an error
message immediately after the Configure button is clicked. This
restriction does not apply to Ethernet ports.

Protection Path*
Select path protection type (1+1 or 1:1). If the selected port is in
Bulk mode, select 1+1. If the selected port is in Shared mode,
select 1:1.

Tunnel* (applicable to 1+1 path protection only)


Select an LER tunnel terminated through a local WAN port and
destined for the desired far-end node.

Primary Tunnel* (applicable to 1:1 path protection, Left Unit only)


Select an LER tunnel destined for the desired far-end node that
should be used as the working path for this pseudowire.

Secondary Tunnel* (applicable to 1:1 path protection, Left Core Unit only)
Select an LER tunnel destined for the desired far-end node that
should be used as the protection path for this pseudowire.

E Tunnel* (applicable to 1+1 path protection, Right Core Unit only)


Select the eLER tunnel destined for the desired far-end node and
extended to the companion unit where it is designated as either the
primary or secondary LER tunnel for this service.

TDM Specific Parameters

Bundle ID*
Select the Bundle ID (1-64). It must match the Bundle ID selected
at the far end.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 57

Timeslots*
Allows for selecting timeslots (DS0/64kbps channels) that need to
be included in the bundle.
To add a channel to the bundle, click “Add an entry…”, select either
a specific timeslot or ‘all channels’ from the pull-down menu and
click ‘Add’. Repeat the process to add additional channels.
To remove a timeslot from the bundle, click on ‘x’ to the right of the
timeslot.
WARNING: The number of timeslots assigned to a bundle at the
two ends of a TDMoP service must match in order for the bundle to
be operational. Having a timeslot assigned/unassigned at one end
of a TDMoP service will cause loss of traffic for the entire bundle
until the respective timeslot is assigned/unassigned at the far end.

Priority
Select QoS (802.1p priority) for the service. The options are 5
(default) or 7. Select 7 (the highest priority) only for mission critical
services.

Signaling Channel
Select ‘yes’ if at least one of the timeslots in the bundle is used by
either a voice application with associated signaling (E&M, FXO,
FXS), or a data application where signaling channel is used to carry
circuit addressing. Otherwise, keep the default selection (‘no’).
Note: In firmware versions up to 1.11, VF signaling is not supported
for bundles associated with E1 ports. Additionally, the signaling
channel can be used for Circuit Addressing1 only for bundles
associated with the CBUS ports driven by the packetizers preset for
T1 mode (see Table 1).
Packetizer in T1 mode Packetizer in E1 mode
Application
CBUS T1 CBUS E1
VF Signaling Yes Yes Yes No
Circuit Addressing Yes No No No
Table 1: Use of Signaling Channel in firmware versions ≤1.11
Note: If you changed the Signaling Channel setting from ‘no’ to
‘yes’ while the Packetizing Model was set to ‘custom’, click Finish
and reopen the panel prior to selecting the Frame Count value.

1 Circuit Addressing is the feature available on Lentronics DS0/64kbps data units.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 58

Packetizing Model
Select one of the following 3 options:
- high-bw-utilization (default) This option will maximize
bandwidth utilization at the expense of increased end-to-end
delay. It will preset the Jitter Buffer Delay to 1ms and Frame
Count as follows:
 For bundles associated with CBUS and T1 ports:
o 60 (if Signaling Channel is set to “no”)
o 24 (if Signaling Channel is set to “yes”)
 For bundles associated with E1 ports:
o 471 (if Signaling Channel is set to “no”).
o 162 (if Signaling Channel is set to “yes”).
Use this option for bundles carrying non-delay sensitive
applications.
- low-latency This option will minimize end-to-end delay at
the expense of bandwidth utilization. It will preset the Jitter
Buffer Delay to 1ms and Frame Count to 4. Use this option for
teleprotection services.
- custom This option will allow the user to set the Jitter Buffer
Delay and Frame Count as desired within the range applicable
to the given port.
Note: If Custom is selected, click Finish and reopen the panel prior
to selecting the Jitter Buffer Delay and Frame Count values.

Jitter Buffer Delay [Non Custom]*


If the selected packetizing model is either high-bw-utilization or low-
latency, the field is not configurable and is preset to 1ms. Note that
the field’s name is displayed as “Jitter Buffer Delay Non Custom”.
If the selected packetizing model is ‘custom’, the options available
are: 100us, 150us, 200us, 250us, 300us, 400us, 500us, 600us,
700us, 800us, 900us, 1ms, 2ms, 3ms, 5ms, 7ms, 10ms, 20ms,
50ms, 70ms, 100ms, 200ms, 300ms and 500ms.
Note: Refrain from selecting values higher than 100ms.

[Data] Frame Count [Low Latency] [High Bw Utilization]*


Depending on the selection made in the Packetizing Model and
Signaling Channel fields, this field is either configurable or non-

1 Note that in firmware version 1.11, the WebUI mistakenly displays 60 instead of 47 frames.
2 Note that in firmware version 1.11, the WebUI mistakenly displays 24 instead of 16 frames.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 59

configurable. Refer to the table below for the available options.


Note that the field’s name is displayed differently depending on the
Packetizing Model and Signaling Channel selections.

Packetizing Frame Count Signaling Valid Selections Valid Selections


Model Field Name Channel for Frame Count for Frame Count
enabled (CBUS1, T1) (CBUS2, E1)
high-bw- Frame Count yes3 24 164
utilization High Bw no 60 475
Utilization
low-latency Frame Count yes6 4 4
Low Latency no 4 4
custom Frame Count yes7 4, 6, 8, 12, 248 4, 8, 169
Data Frame no 3 to 60 3 to 4710
Count

Table 2: Selectable Frame Count Values


Note: After making any changes to the Packetizing Mode or
Signaling Channel fields, click Finish and reopen the panel prior to
making any changes to the Frame Count field.

Ethernet Specific Parameters

Bridging Criteria*11
Select one of the following two options:
By Port All traffic ingressing the port will be forwarded
to the far end.
By Port and VLAN Only the selected 802.1Q VLAN specified in
the VLAN field below will be forwarded to the
far end.

1 For packetizers in T1 mode.


2 For packetizers in E1 mode.
3 In firmware version 1.11, this is not a valid selection for E1 port bundles.
4 In firmware version 1.11, the WebUI mistakenly displays 24 instead of 16.
5 In firmware version 1.11, the WebUI mistakenly displays 60 instead of 47.
6 In firmware version 1.11, this is not a valid selection for E1 port bundles.
7 In firmware version 1.11, this is not a valid selection for E1 port bundles.
8 In firmware version 1.11, option 3 is also selectable, but should not be used.
9 In firmware version 1.11, options 3, 6, 12 and 24 are also selectable, but should not be used. 16
will be added in the next firmware version.
10 In firmware version 1.11, options 48-60 are also selectable, but should not be used.
11 Will be renamed to “Traffic Selection” in firmware version 1.12.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 60

VLAN*
Enter the 802.1Q VLAN ID. The allowed range is 1-4000.
Note: This field is not applicable if Bridging Criteria is set to “By
Port”.

VPLS

By definition, each VPLS service comprises multiple pseudowires.

Figure 39 shows the VPLS accordion with a panel opened for one of the local
VPLS services.

Figure 39: VPLS accordion with a service panel opened

To view or edit the settings for an existing VPLS service, locate the service
in the table and click on its Local ID. This opens a panel displaying all the
configurations associated with the service. Note that the Pseudowire and Local
Endpoint eyeglasses can be used to open the respective table individually (both
tables are displayed when the service panel is opened). Edit the parameters as
needed. When finished, click ‘Finish’. Click ‘Configure’ in the header to save
changes to the unit.

To add a new service, click on the ‘Add…’ button located above the services
table, enter an unused Local ID (typically, the next available Local ID is entered)

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 61

and click ‘Add’. Select or enter the desired values for all parameters including
pseudowires and local endpoints (refer to the following two paragraphs). When
finished, click on the service panel’s ‘Finish’ button. Click ‘Configure’ in the
header to save changes to the unit.

To add a pseudowire to a new or existing service, click on the “Add…” button


located above the pseudowire table associated with the respective service.
Enter an unused Local ID (typically, the next available Local ID is entered) and
click ‘Add’. This opens the add pseudowire sub-panel (see Figure 40). Select or
enter the desired values for all parameters. Click on the sub-panel’s ‘Finish’
button. If needed, repeat this process to add more pseudowires to the service.
When finished, if no local endpoints are to be added, click on the
service/pseudowire panel’s ‘Finish’ button. Click ‘Configure’ in the header to
save changes to the unit.

Figure 40: Pseudowires table with add pseudowire sub-panel open

To add a local endpoint (port) to a new or existing service, click on the “Add…”
button located above the Local Endpoints table. This opens the add port sub-
panel (see Figure 41). Click on the Port field and select a LAN port from the
menu. Click ‘Add’. Repeat this process to add more local endpoints to the
service. When finished, click on the sub-panel’s ‘Finish’ button. Click on the
service/local-endpoints panel’s ‘Finish’ button. Click ‘Configure’ in the header to
save changes to the unit.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 62

Figure 41: Local Endpoints table with add port sub-panel open

To delete a pseudowire, a local endpoint allocation, or the entire service, click on


the background of the respective Local ID cell and click on the Delete button
above the table. Confirm the action and click ‘Configure’ in the header to save
changes to the unit.

Local ID
The local ID associated with the given VPLS service. Must be in
the 1-2048 range. Defined at the time the service is created and
cannot be edited afterwards.

Name
Enter service name. Up to 32 characters.

Bridging Criteria*
Select one of the following two options:
By Port All traffic ingressing the ports associated with
this service will be forwarded to the far end
(based on their destination MAC address).
By Port and VLAN Only the selected 802.1Q VLAN specified in
the VLAN field below will be forwarded to the
far end (based on their destination MAC
address).

VLAN*
Enter the 802.1Q VLAN ID. The allowed range is 1-4000.
Note: This field is not applicable if Bridging Criteria is set to “By
Port”.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 63

Pseudowires

ID
The local ID associated with the given pseudowire. Must be in the
1-2048 range. Defined at the time the pseudowire is created and
cannot be edited afterwards.

Primary Tunnel* (applicable to the Left Core Unit only)


Select an LER tunnel destined for the desired far-end node that
should be used as the working path for this pseudowire.

Secondary Tunnel* (applicable to the Left Core Unit only)


Select an LER tunnel destined for the desired far-end node that
should be used as the protection path for this pseudowire.

E Tunnel* (applicable to the Right Core Unit only)


Select the eLER tunnel destined for the desired far-end node and
extended to the companion unit where it is designated as either the
primary or secondary LER tunnel for this service.

Label Out*
Enter the outgoing pseudowire label. The allowed range is 255-
1048575.

Label In*
Enter the incoming pseudowire label. The allowed range is 255-
1048575.
Note: It is recommended that ‘In’ and ‘Out’ labels for a given
pseudowire are different. Typically, each pseudowire uses a
globally (customer-network-wide) unique pair of labels.

Local Endpoints

Port*
Local LAN port(s) associated with this VPLS service. The selected
ports must be in Shared mode.
Note: For firmware package versions ≤1.11, a VPLS service can be
associated with only one local LAN port.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 64

Node > Frequency Sync Tab

The Frequency Sync Tab is shown in Figure 42.

Figure 42: Freq Sync Tab with Reference Sync Inputs’ Status tab selected

General

Node Type
May be set to one of the following: HEI (Headend Internal), HEE
(Headend External) or Normal. It is critical that this field be set in
accordance to the adopted network frequency synchronization
solution. Refer to the Frequency Synchronization section in
JunglePAX Technical Practice and Installation Manual for more
details.
Note: This parameter must be configured the same on the
companion Core Unit.
Warning: Changing this parameter to a value that is not in
accordance to the network synchronization solution, may cause
loss of all TDMoP traffic in the network!

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 65

Clock Source
Displays the frequency timing source presently used by this unit.
May be the internal (free-running), companion unit, or any one of
the local ports listed in the Reference Frequency Inputs Config tab
(see Figure 43).

Priority Unit
Preset to left (presently not user-configurable). At an HEI node, it
determines which of the two Core Units will be internally timed. At a
Normal node (and HEE nodes with no valid external references and
WAN ports provisioned for timing on both Core Units), it determines
which of the two Core Units will be line timed if the node’s best SSM
is received on both Core Unit’s WAN ports.

PLL State
Indicates the state of the Phase Locked Loop on the unit. The
possible readings are:
- Locked The unit is locked to the selected sync reference.
- Locking The unit is in the process of locking to the selected
sync reference.
- Holdover No valid clock reference is available and the unit is
trying to preserve the clock based on the last valid
clock reference received.
- Freerun The unit is internally timed.

Front Frequency Input (applicable to HEE nodes only)


It determines the frequency of the timing signal expected on the
front frequency input provided that the port is provisioned (i.e.
added to the Reference Frequency Inputs Config tab’s table). May
be set to one of the following: External 2 kHz, External 1.544 MHz,
or External 10 MHz.

Reference Frequency Inputs – Status Tab

Displays a table with a list of reference frequency inputs whose SSMs are being
monitored. The list includes the companion unit plus the WAN ports enabled in
the Node>Interfaces tab. At an HEE node, the list may include the front
frequency input (if the input is provisioned, i.e. added to the Reference
Frequency Inputs Config tab’s table).

Ref Freq Input


Shows the ports whose Rx SSM are being monitored.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 66

Rx SSM [SDH/SONET]
Indicates the SSM received on the respective input at the time the
page was loaded or refreshed last time. If the unit is factory-preset
for use in North America, the label is displayed as Rx SSM SONET
and the Option II (SONET) SSM message set is used (refer to the
Frequency Synchronization section in JunglePAX Technical
Practice and Installation Manual). If the unit is preset for use
outside North America, the label is displayed as Rx SSM SDH and
the Option I (SDH) SSM set is used.
Note: All units with package versions ≤1.11 are preset for Option I
(SDH) SSM set.
Note: For HEI nodes, the displayed Rx SSM value is always 15.
Note: Refresh the page (F5) to update the Rx SSM readings.

Reference Frequency Inputs – Config Tab

Allows the user to set/change the receive SSM setting on selected input ports
based on the network frequency synchronization solution. Those ports need to
be added to the table because the table is blank by default. At Normal and HEE
nodes, all enabled WAN ports should be added to the list. At HEE nodes, the
front frequency input port should also be added if used for synchronization. For
HEI nodes, this function is not applicable because the HEI nodes are always
internally timed.

By default, all WAN ports at Normal and HEE nodes are set with Force Rx SSM
= 15 (Don’t Use for Sync).

At Normal nodes equipped with two Core Units, one WAN port on each Core Unit
needs to have its Force Rx SSM disabled (set to ‘none’) while all other WAN
ports should be kept with their default Force Rx SSM settings (15). This should
be done in accordance to the network sync solution.

Presently, the HEE mode is used only if one or both Core Units at the node are
having their local front frequency input used for timing. Those units will need to
have this input forced to a desired SSM value in accordance to the network
synchronization solution. In applications with redundant HEE nodes, the
selected WAN port(s) also need to have their Force Rx SSM disabled following
the principles described in the previous paragraph.

To add a port to the table, click on the “Add…” button above the table. The
Add Reference Frequency Input panel appears. Select the port from the pull-
down menu and click “Add”. Set the Force Rx SSM value as desired (or leave it

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 67

defaulted). Click “Finish”. Repeat this procedure if more ports need to be added
to the table. When finished, click on the “Configure” button in the header.

To remove a port from the table, click on the background of the respective Ref
Freq Input cell and click on the Delete button above the table. Confirm the action
and click ‘Configure’ in the header.

Ref Freq Input


Shows the ports that have been added to the table in order for their
Force Rx SSM value to be set or exposed for setting validation.

Force Rx SSM [SDH/SONET]


Allows the user to Force the Rx SSM value on the respective Ref
Freq Input to a desired value. This should be done in accordance
to the network synchronization solution.
Warning: Changing this parameter to a value that is not in
accordance to the network synchronization solution, may cause
loss of network synchronization, which would in turn cause loss of
TDMoP circuits established between the nodes that are not
synchronized.

Figure 43: Freq Sync Tab with Reference Sync Inputs’ Config tab selected

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 68

Reference Frequency Outputs

The Reference Frequency Outputs accordion is shown in Figure 42. It displays


the SSM transmitted out of all local ports that may be used for reference
frequency distribution and are capable of carrying SSM.

Ref Freq Output


Shows the output ports capable of carrying SSM.

Tx SSM [SDH/SONET]
Indicates the SSM transmitted on the respective output at the time
the page was loaded or refreshed last time.
Note: Refresh the page (F5) to update the Rx SSM readings.

Node > Time Sync Tab

Introduction [To be moved to TPIM]

Date and time information is distributed across the JunglePAX network using a
master-slave model. Normally, two master Core Units (designated as Primary
Secondary masters) are configured for redundancy. All other Core Units are
configured as clients (slaves). The secondary master behaves as a client as
long as the primary master is active.

Masters can be configured to time either from an NTP source, or from the
internal RTC (real time clock). When configured for NTP timing, up to two
external NTP server IP addresses can be entered for redundancy. When
configured for RTC timing, the date and time are user-configurable.

Clients are timed from the active master as long as updates from the active
master are received. If both masters become unavailable, clients will time based
on their local RTCs independently. The date and time at client RTCs are user-
configurable, but these settings will be overridden by the next update received
from the active master (if available).

Time Sync

The Time Sync tab layout at a master Core Unit is shown in Figure 44. The
layout at a client Core Unit is shown in Figure 45.

Note: For users with no time management privilege, only the “Current Date and
Time” and “Active Time Source” are displayed.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 69

Figure 44: Time Sync tab layout when Primary/Secondary Master is selected

Figure 45: Time Sync tab layout when Client is selected

Current Date and Time


Indicates the current date and time on this Core Unit.
Note: Refresh the page (F5) to update the reading.

Active Time Source


Displays the presently used source for Date and Time sync. The
possible readings are: Local RTC, Primary (master’s) RTC, Primary
(master’s) NTP, Secondary (master’s) RTC, Secondary (master’s)
NTP.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 70

Note: Refresh the page (F5) to update the reading.

Time Sync Role


Sets the Core Unit for Primary Master, Secondary Master or Client
mode.

Time Source (n/a to client Core Units unless no masters are available)
For a master Core Unit, this parameter sets the time source when
the unit is operating as an active master. Configurable to NTP or
RTC. RTC should be used only if no access to remote NTP servers
is available.
For a client Core Unit, it is invalid to select NTP as the timing
source (cannot be committed although selectable). Note that this
setting is irrelevant at client Core Units operating in a network with
provisioned master Core Units.

Client Update Period (sec) (n/a to client Core Units)


Determines how often will this master update the clients when
operating as an active master.

Set Date and Time


Sets the date and time (applicable at units configured as RTC).
Note: In a normally configured network, this setting will take effect
only at the active master Core Unit because at all other Core Units
it would be overridden by the next update received from the active
master.

Configure NTP (applicable only at masters whose Time Source is set to NTP)

NTP Server 1 Address


Sets the IP address of the remote NTP Server #1. N/A to clients.

NTP Server 1 Enable


Enables polling of NTP Server #1.

NTP Server 2 Address


Sets the IP address of the remote NTP Server #2. N/A to clients.

NTP Server 2 Enable


Enables polling of NTP Server #2. This will happen only if Server#1
is unavailable (not responding to polls).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 71

Polling Interval
Sets how often the NTP server is polled for sync.

Alarms > Current Alarms Tab

Alarms

The Current Alarms tab (Figure 46) shows the list of presently active alarms.

Note: By default, the most recent alarms are shown at the bottom of the list. Use
the sorting, filtering and search tools described in the section ‘Tables’ on page
16.

Figure 46: Current Alarms Tab

Time Stamp
Time stamp is displayed in the following format:
<Year>-<Month>-<Date>T<Hours>:<Minutes>:<Seconds>+<Time Zone>
 Hours are displayed in the 24-hour format.
 Seconds are displayed with microsecond accuracy.
 Time zone is indicated as the current shift with respect to GMT.
Presently, all timestamps are shown as GMT.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 72

Name
Displays the alarm name.

Source
Displays the source of alarm.

Severity
Displays the alarm severity (Major, Minor or Warning).
Note: Major and Minor alarms are reflected on the respective
faceplate LED. They are also driving the respective Form C contact
on both left and right Power Unit faceplates.

Status
Presently unused.

Note: For DS0 level units installed in JungleMUX/TN1U/TN1Ue shelves and


connected through CBUS-4A units:
 Alarms are, by default, reported as minor alarms.
 Alerts (e.g. DTT trip conditions) are, by default, reported as warnings.
These severities can be changed through the software (presently through CLI
only).

Alarms > Alarm Log Tab

Log

The Alarm Log tab (Figure 47) shows the list of both presently active and historic
alarms. Each historic alarm is represented with two entries: a set entry and a
clear entry. Current alarms have no respective clear entries.

Note: By default, the most recent entries are shown at the bottom of the list. Use
the sorting, filtering and search tools described in the section ‘Tables’ on page
16.

The table includes all the columns available in the Current Alarms tab plus the
State column.

State
May indicate ‘set’ or ‘clear’. A set event indicates when the specific
alarm was detected. A cleared event indicates when the respective
alarm cleared. Each cleared event has the matching set entry.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 73

Refer to the Current Alarms section (page 71) for the description of other
columns available in the Alarm Log table.

Note: The unit can store tens of thousands of alarm entries in the log. When the
designated memory is full, the oldest alarm entries are cleared first.

Figure 47: Alarm Log Tab

Alarms > Alarm Settings Tab

Presently not used.

Maintenance > Diagnostics Tab

The Diagnostics tab displays BER for WAN ports as well as various frame
statistics for:
 Individual WAN, LAN and TDMoP ports
 Bypass ports

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 74

 Internal link between the switch and microprocessor


 TDMoP trunk (the link between the switch and packetizer from both the
switch side (Downlink) and packetizer side (uplink)

This tab also allows for resetting counters on both individual and group basis as
well as enabling loopbacks on various ports.

To reset counters, check the relevant checkbox and click Configure. Note that
the position of the Reset Counters checkbox determines which counters will be
reset. For example, checking a Reset Counters checkbox inside the WAN Ports
table will clear the WAN port counters for the respective WAN port, while clicking
on the Reset Counters checkbox at the top of the view (outside any accordions)
will clear all counters on the Core Unit.

For each port on the internal switch device (including WAN ports, Bypass ports,
LAN ports, and NMS link to the microprocessor), the following frame statistics
parameters are monitored:

Figure 48: Input and Output Frame Statistics

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 75

The Loopback Mode field indicates the present loopback mode for the selected
port (if applicable). To change the loopback mode for the port, use the Set
Loopback Mode action widget. By default, all loopbacks are disabled. Figure 50
shows the presently selectable loopbacks.

Figure 49: Set loopback mode options for a 10G WAN port

Note: Selecting any Loopback mode other than ‘disabled’ will impact customer
traffic on the port.

Remote (PHY) (22)


SFP 22
SFP PHY 23 T1/ E1 CBUS
Unit Unit Access Units Unit Unit
12 12 Local (PHY) (23)

Remote (MAC) (12) Remote (MAC) (12)


Core
Packetizer

SGMII SGMII Local (LIU) (2) LIU


Remote 2
(14) Local (Switch) (14) Local (Switch) (14) Remote (LIU) (1)
1 Unit
14 14 Jitter Attntr T1/E1
Add
Local (SGMII) (7) Remote (GMII) (5)
XAUI 3
BYP1

14 Remote (Framer) (3)


Converter Framer
Local (Framer) (4)
Switch 4
SGMII GMII
TDMoP
SGMII

XAUI
GMII
PCS
BYP2

14 7 6 5 Cross-Conn.

Add 14 14

Remote ( TDMoP Trunk


XAUI (10G) SGMII (1G) Local (13)
(14) Remote (Switch) (14) Local (PCS) (6)

9 Remote (XAUI) (9) 13


XAUI SGMII CBUSConversion
10 10 Remote (WIS/PCS) (10)
WIS/ PCS WIS/ PCS

PMA PMA
11 11 Local (PMA) (11) FPGA
10G SFP 1G SFP

GMII Gigabit Media Independent Interface


PCS Physical Coding Sublayer
PMA Physical Medium Attachment (sublayer)
SGMII Serial GMII
10G WAN 1G WAN XAUI 10 Mbps Attachment Unit Interface
(WAN Ports 1/ 2) (WAN Ports 3/ 4/ 5/ 6) WIS WAN Interface Sublayer

Figure 50: JunglePAX loopbacks

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 76

WAN Ports

Opening the WAN Port accordion exposes a table that lists the provisioned WAN
ports. Click on a desired WAN port to display the port’s diagnostics information
including the input and output frame statistics (Figure 48), loopback mode
selection (Figure 49) as well as B1 and B3 BER readings (indicating the
performance of the WIS layer) and their threshold settings.

Figure 51: WAN ports diagnostics table

Bypass Ports

The Bypass Ports accordion provides the performance information on the two
10G bypass ports and allows for resetting the performance counters. Click on
the port number to display the panel with frame statistics and expose the
loopback mode selection widget.

NMS Link

Open the NMS Link accordion to check the performance of the internal NMS link
between the switch and microprocessor. The reset counters button is provided.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 77

Figure 52: WAN port diagnostics panel

LAN Ports

The LAN port accordion allows for checking the performance of all provisioned
LAN (Ethernet access) ports. The user can reset their counters individually or all
at once. Click on a LAN port number to display the panel with respective input
and output frame statistics.

TDMoP Trunk

This accordion includes a widget for setting the loopback mode of the TDMoP
trunk (the link between the switch and TDM packetizer).

TDMoP Trunk Downlink

The TDMoP Trunk Downlink accordion provides the input and output frame
statistics for the TDMoP trunk as seen from the switch’s side. The Reset
Counters button is provided.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 78

TDMoP Trunk Uplink

The TDMoP Trunk Uplink accordion provides the packetizer’s Ethernet interface
performance counters i.e. the frame statistics for the TDMoP trunk as seen from
the paketizer’s side. The Reset Counters button is provided. Note that Input
Frame Statistics on the TDMoP packetizer side, corresponds to the Output
Frame Statistics on the Switch’s side and vice versa.

Figure 53: TDMoP Trunk Uplink panel

TDMoP Ports

This accordion provides a table with all 8 packetizer ports. Click on a port to
open a panel with port’s performance information. The content of the panel
depends on the mode the selected packetizer port is set for.

For a CBUS port (Figure 54), the panel includes the Type field (=CBUS), physical
slot and port numbers, whether the CBUS signal is received (LOS=0) or not
(LOS=1) as well as the widget for setting the loopback mode for the port. Also
included is the performance information for each individual bundle associated
with the port.

For a T1/E1 port, the panel includes the Type field (T1 or E1), physical slot and
port numbers, a widget for setting the loopback mode for the port and a selection
of parameters (counters and alarm indicators) as shown in Figure 55. Also
included is the performance information for each individual bundle associated
with the port.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 79

Figure 54: Performance information for a CBUS port

Figure 55: Performance information for a T1 port

Click on a Bundle ID to open a panel for the respective bundle. The bundle
panel presently includes the information shown in Figure 56.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 80

Figure 56: Bundle performance information

Maintenance > Reports Tab

Presently not used.

Maintenance > Firmware Tab

Presently not used.

Maintenance > Utilities Tab

Presently not used.

System Admin > User Management Tab

This tab allows for managing the unit’s access control list.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 81

Note: Only roles with User Management privilege can view and configure
parameters in this subtab.

Note: All changes made in the ‘User Management’ subtab are automatically
synchronized to all other Core Units with matching Network Passwords. For
more information see Security subtab section.

The User Management subtab consists of four accordions: Authorization Roles,


Local Users, RADIUS Users, User Authentication Settings.

Authorization Roles

The Authorization Roles accordion is shown in Figure 57.

Figure 57: User Management subtab with Administration Roles accordion open

Each entry in the Authorization Roles table represents a user group whose
members are sharing the same authorizations. There are two predefined roles:
 Administrators (can do everything), and
 Operators (can only monitor non-security sensitive information)
New roles with customized privileges and restrictions can be added. To define a
new role, click the “Add…” button above the table, enter a role name. It must be
minimum 6 characters long and may contain letters, numbers, underscores and
periods. Click the Add button below. A panel for the new role appears. If the
members for the new role are supposed to have one or more of the security
sensitive privileges that are normally reserved for Administrators (user, security
and time management), check the checkboxes against the desired privileges.
The privileges/restrictions associated with each of the 3 checkboxes are provided
in Table 3.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 82

Security Sensitive Function Privileges when enabled Restrictions when disabled


Allow User Management User Management tab No visibility of User Management
view and configure tab
Allow Security Management Security tab - view and No visibility of Security tab
configure
Allow Time Management Time Management tab – No visibility of Time Management
view and configure tab except for the “Current Date
and Time” and “Active Time
Source” parameters (see Time
Sync tab).

Table 3: Security sensitive functions

The functionalities that can be added to the list of privileges/restrictions are listed
in Table 4:

Functionality Target subtab in WebUI & equivalent CLI structure


All All tabs and subtabs listed below
Node List Network > Node List subtab
eMS Node > eMS subtab
Inventory Node > Inventory subtab
Interfaces Node > Interfaces subtab
Tunnels Node > Tunnels subtab
Services Node > Services subtab
Frequency Sync Node > Freq Sync subtab
Current Alarms Alarms > Current Alarms subtab
Alarm Log Alarms > Alarm Log subtab
Alarm Settings Alarms > Alarm Settings subtab (future)
Diagnostics Maintenance > Diagnostics subtab
Table 4: Functionalities addable to lists of privileges and restrictions

For each functionality added to the list of privileges, the administrator needs to
select the actions allowed for the selected functionality. The selectable actions
are:
 Read
 Read Update
 Read Create Update Delete

For each functionality added to the list of restrictions, the administrator needs to
select the actions denied for the selected functionality. The selectable actions
are:
 Read Create Update Delete
 Create Update Delete
 Delete

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 83

When defining user privileges for a role (other than the 3 security critical ones
listed in Table 3), there are two basic approaches:
a) Define only specific privileges. This approach is useful if the role has more
restrictions than privileges.
b) Define only specific restrictions. This approach is useful if the role has
more privileges than restrictions. The process typically starts with defining
only one privilege: Functionality: All; Allow: Read Create Update Delete.

Note: If the same functionality (e.g. Services Delete) is both allowed and denied,
the functionality will be denied.

To add a privilege/restriction, click the “Add…” button above the respective table,
select the functionality, click the “Add” button below and select the desired option
from the Allow/Deny menu. Click Configure.

To add or edit privileges/restrictions for a previously added role, click on the


role’s name in the Authorization Roles table to open the role’s panel and edit the
settings as desired. Note that deletions of individual privileges/restrictions are
presently not possible.

Figure 58: Authorization Role panel

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 84

To delete a role, select it and click Delete button above the table. Note that the
Administrators and Operators roles cannot be deleted. Also, any roles with at
least one Local or RADIUS user assign to it cannot be deleted.

Local Users

This accordion, along with the RADIUS Users accordion, allows the administrator
to manage the unit’s access control list. Only the users entered into the Local
Users table (Figure 59) and/or RADIUS User table (Figure 60) will be allowed to
log into this Core Unit’s CLI and WebUI.

The Local User list takes effect in one of the following two situations:
 Authentication Order (see Security tab) is set to ‘Local Only
 Authentication Order is set to ‘RADIUS else Local’ and RADIUS
configurations are either not properly set, or the RADIUS server cannot
be reached during the user authentication process.

There are two predefined Local Users:


 Administrator (a member of the Administrators role), and
 Operator (a member of the Operators role)

The Administrator’s default password is Administrator1, while the Operator’s


default password is Operator1.

For security reasons, it is strongly recommended that the default passwords be


changed at the time the network is commissioned.

To add a new user, click the “Add…” button above the table and enter the user
name. It must be minimum 6 characters long and may contain letters, numbers,
underscores and periods. Select the desired role for the user and click the Add
button below.

Figure 59: User Management subtab with Local Users accordion opened

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 85

A user can be reallocated to a different role, but this change can be carried out
only by entering the user’s current password into the Password and Confirm
Password fields. Password can also be changed (but not along with the role
change).

Checking the Locked Out box will make the user inactive. Use this option if the
user’s CLI and WebUI access need to be temporarily disabled.

To delete a user, select it and click Delete button above the table. Predefined
users (Administrator and Operator) cannot be deleted.

RADIUS Users

The RADIUS Users tab (Figure 60) allows for entering RADIUS users to the
access control list. The RADIUS Users list takes affect if:
 Authentication Order (Security tab) is set to ‘RADIUS else Local’, and
 RADIUS configurations are properly set, and
 RADIUS server can be reached during the user authentication process.
Otherwise, the Local Users list applies.

Figure 60: User Management subtab with RADIUS Users and User
Authentication accordions open

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 86

To add a new user, click the “Add…” button above the table and enter the user
name. The name must match the respective username in the active directory
accessed by the RADIUS server. Select the desired role for the user and click
the Add button below.

Note: The entries with usernames that are not exactly matching those in the
active directory accessed by the RADIUS server will not take any effect.

A user can be reallocated to a different role, but this change can be carried out
only by entering the user’s current password into the Password and Confirm
Password fields. Password can also be changed (but not along with the role
change).

Checking the Locked Out box will make the user inactive. Use this option if the
user’s CLI and WebUI access need to be temporarily disabled.

To delete a user, select it and click Delete button above the table.

User Authentication Settings

Session Idle Timeout (min)


Sets the inactivity timeout period for both WebUI and CLI sessions.
Default is 30 minutes.

User Login Attempts


Sets the allowed number of consecutive failed login attempts.
Default is 3.

Failed Login Lockout Time


Sets the login lockout time (in seconds) that will be applied after the
specified number of unsuccessful login attempts (as set in the field
above).

Local Password Minimum Values

Length
Sets the minimal number of characters in the password.

Lower Case Letters


Sets the minimal number of lower case letters in the password.

Upper Case Letters


Sets the minimal number of upper case letters in the password.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 87

Numbers
Sets the minimal number of numbers in the password.

Non Alphanumeric
Sets the minimal number of non-alphanumeric characters in the
password.

System Admin > Security Tab

Note: Only roles with Security Management privilege can view this subtab.

The Security subtab consists of three accordions: Operation, RADIUS


Configuration, and Distribution. The RADIUS Configuration accordion is not
displayed if the Security Role parameter (see Operation tab) is set to Client,
while the Distribution accordion is displayed only for Core Units whose Security
Role is ‘Primary Gateway’.

Operation

The content of the Operations accordion is shown in Figure 61.

Figure 61: Security subtab with Operations accordion open

Security Role
May be set for ‘Client’ (default), ‘Primary Gateway’, or ‘Secondary
Gateway’.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 88

One Core Unit in a JunglePAX network needs to be configured as


Primary Gateway, while another Core Unit (preferably at a different
site) needs to be configured as Secondary Gateway. All other
Cores should remain configured as Clients.
If RADIUS authentication of JunglePAX users is required, the two
Gateway Core Units must be connected to the IP network where
the RADIUS server(s) reside, which typically determines the actual
site(s) chosen for the primary and secondary gateway functions.

Network Password
All Core Units in the network must be set with the same Network
Password in order for the access control list and other security
settings to synchronize across the network. The network password
can be a string of any length and any combination of characters. A
blank/empty string (default) is also allowed. It is strongly
recommended that the Network Password be configured at each
Core Unit at the time the unit is installed.
Note: Any configuration changes made in the User Management
and Security subtabs (except for the Security Role and Network
Password) will be automatically distributed to all remote Core Units
set with the matching Network Password.1

Primary/Secondary Gateway
Provides the location (Node Name and side) and security sync
status (Active/Standby/Down) of the Primary and Secondary
Gateway Core Units.

RADIUS Configuration

The RADIUS Configuration accordion (Figure 62) is displayed only for Primary
and Secondary Gateway Core Units.

1 A watchdog mechanism indicating whether or not any Core Units are “out-of-sync” for the
security settings will soon be implemented.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 89

Figure 62: RADIUS Configurations accordion

Authentication Order
May be set for ‘Local Only’ (default), or ‘RADIUS else Local’.
If set to ‘Local Only’, RADIUS authentication is disabled.
If set to ‘RADIUS else Local’, RADIUS authentication is attempted
first. Failing that, the user is authenticated based on his/her
credentials defined in the Local User list.

Timeout
Sets the timeout for each RADIUS connection attempt (in seconds).
Default is 15 sec.

Connection Attempts
Sets the maximum number of connection attempts to the RADIUS
server. Default is 3.
Indicates how long the Gateway will wait for the RADIUS server to
respond to a user’s authentication request before it declares the
RADIUS server unavailable. The default is 15 sec.
Note: If an authentication request to the Primary RADIUS server is
timed out, the authentication request will be sent to the Secondary
RADIUS Server (if provisioned). If this request is also timed out, an
attempt will be made to log the user in locally, i.e. the entered
credentials will be matched against the Local Users control list.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 90

RADIUS Server 1/2

IP Address
Enter the respective RADIUS Server IP address.

RADIUS Port
Enter the listening port for RADIUS authentication traffic.

Shared Secret
Enter the shared secret used by the respective RADIUS server for
authentication traffic.

Distribution

The Distribution accordion (Figure 63) is displayed only for the Primary Gateway
Core Unit.

Figure 63: Distribution accordion

Distribution Begin Button


Click this button to distribute the Master Gateway Core Unit’s
security settings to remote Cores with matching Network Password.

As mentioned earlier, any configuration changes made in the User


Management and Security subtabs (except for the Security Role
and Network Password) will be automatically distributed to all
remote Core Units set with the matching Network Password.
Consequently, any remote Core Units whose Network Password
was mismatched when auto-distribution took place, as well as the
Core Units residing at nodes installed after the last distribution, will
be “out-of-sync”. To get those units synchronized, set their
Network Password to match the one at the Master Gateway unit,

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 91

open the Master Gateway’s Distribution accordion and click the


‘Distribution Begin’ button.

Distribution Status Button


Presently not operational.

Distribution Cancel Button


Click this button to stop the ongoing distribution of security settings.
Given that the distribution process is very fast, typically, all remote
Core Units will get updated shortly after the Distribution button is
clicked (i.e. before the user manages to click the Distribution
Cancel button).

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 92

4. COMMAND LINE INTERFACE

CLI is a command-line based user interface provided by the CLI interpreter


running on the Core Unit. Use of CLI is not mandatory, but it is convenient for
running scripts (collection of commands) for fast node configuring.

Accessing JunglePAX CLI

JunglePAX CLI can be accessed through an SSH client application such as


PuTTY on the standard SSH port 22 or through the WebUI. The advantage of
using the SSH client is better window size flexibility and ability to copy and paste
scripts from text files.

If an SSH client application is used, do the following:


1. Connect the PC to the desired Core Unit NMS port.
2. Start the SSH client application.
3. Enter the NMS port’s IP address and open the session.
4. Log into Linux as admin.
5. Log into CLI as Administrator using default password Administrator1.

Below is a CLI login dialog example when an external SSH client application
is used.
login as: admin
Welcome to GE Lentronics JunglePAX
login to cli as: Administrator
password: Administrator1
local CLI (y/n): y

Administrator connected from [Link] using console on [Link]


Administrator@[Link]>

If the WebUI is used1, do the following:


1. Click on the CLI button in the WebUI’s header to open the CLI window.
2. Hit Enter.

The CLI entry message and prompt will appear in the following format:
Administrator connected from [Link] using console on [Link]
Administrator@[Link] [Link]>

1The information on how to access the Core Unit and log into it using WebUI is provided in the
WebUI section of this manual.

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 93

The CLI starts in Operational mode (note the prompt ending with “>”). In this
mode, the user can view system status, performance parameters and current
configuration, but cannot change configuration.

Note: Entering commands in CLI is case sensitive.

Operation Mode Commands

Press the "Tab" key to display the available commands. The “Tab” key also
autocompletes any unfinished commands or provides the list of possible
completions.

Administrator@[Link] [Link]> <Tab>


Possible completions:
compare - Compare running configuration to another configuration or a file
configure - Manipulate software configuration information
describe - Display transparent command information
exit - Exit the management session
file - Perform file operations
help - Provide help information
id - Show user id information
quit - Exit the management session (same as exit)
request - Make system-level requests
script - Script actions
set - Set CLI properties
set-path - Set relative show path
show - Show information about the system
source - File to source
top - Exit to top level and optionally run command
up - Exit one level of configuration

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 94

“Show All” and “Show” Command Examples

“Show” allows for showing only status parameters, while “Show All” also allows
for showing current configurations. Use of “Show All” is therefore recommended.

Display Node Type:


…> show all ems frequency frequency-config node-type
node-type normal;
[ok][ 2017-08-17 [Link]
Administrator@[Link] [Link]>

Note that the following two commands would have the same effect:
…> set-path ems frequency frequency-config node-type
[ok][ 2017-08-17 [Link]

[path ems Frequency Node_Type]


Administrator@[Link] [Link]> show all
node-type normal;
[ok][ 2017-08-17 [Link]

[path ems frequency frequency-config node-type]


Administrator@[Link] [Link]>

Show active time source and current time:


show ems time-state
Show chassis ID, type ID, serial ID and hardware version:
show ems properties
Show inventory:
show ems inventory <press Tab to see options>
Show used tunnels (Tunnel IDs) and their BFD status:
show ems tunnels
Show tunnel configurations:
show all ems tunnels <press Tab to see options>
Show service configurations:
show all ems services <press Tab to see options>

Core Unit Reboot

request ems firmware reboot-core-card

Reboot eMS (Management Plane) Only

request ems firmware reboot-mp-only

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 95

Configuration Mode

To enter Configuration mode, type configure. The following entry message and
prompt will appear (note the % character at the end of the prompt in
Configuration mode):

Administrator@[Link] [Link]> configure


Entering configuration mode private
Current configuration users:
auth tcp (maapi from [Link]) on since 2017-08-17 [Link] private mode
[ok][2017-08-17 [Link]

[edit]
Administrator@[Link] [Link]%

Press the "Tab" key to display the available configuration commands. The “Tab”
key also provides possible completions for any unfinished commands.

Administrator@[Link] [Link]% <Tab>


Possible completions:
commit - Commit current set of changes
compare - Show configuration differences
copy - Copy a list entry
delete - Delete a data element
describe - Display transparent command information
edit - Edit a sub-element
exit - Exit from this level
help - Provide help information
insert - Insert a parameter
load - Load configuration from an ASCII file
move - Move a parameter
quit - Exit from this level (same as exit)
rename - Rename an identifier
request - Make system-level requests
resolved - Conflicts have been resolved
revert - Copy configuration from running
rollback - Roll back database to last committed version
run - Run an operational-mode command
save - Save configuration to an ASCII file
set - Set a parameter
show - Show a parameter
status - Display users currently editing the configuration
top - Exit to top level and optionally run command
up - Exit one level of configuration
validate - Validate current configuration

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 96

The most frequently used configuration commands are set and commit. The set
command sets a new value for a parameter. The modification will take effect
once the commit command is issued. Note that multiple set commands may be
entered prior to the commit command.

Example:

…% set ems frequency frequency-config node-type HEI


[ok][ 2016-08-17 [Link]

[edit]
Administrator@[Link] [Link]% commit
Commit complete.
[ok][ 2016-08-17 [Link]

[edit]
Administrator@[Link] [Link]%

To exit Configuration mode, type exit.

Administrator@[Link] [Link]% exit


[ok][2016-08-17 [Link]
Administrator@[Link] [Link]>

“Set” Command Examples

eMS Settings

Set Node Name


set ems settings node-name <string>
commit

Set Node Number


set ems settings node-number <1-4096> [presently 1-65535]
commit

Time Settings

Set time source to RTC (Default)


set ems time time-source RTC
commit

Set time source to NTP


set ems time time-source NTP

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 97

commit

Frequency Settings

Set Node Type to NORMAL (Default)


set ems frequency frequency-config node-type normal
commit

Set Node Type to “Headend Internal”


set ems frequency frequency-config node-type hei
commit

Set Node Type to “Headend External” and set the front frequency input mode as needed
set ems frequency frequency-config node-type hee front-frequency-input <press Tab
for options>
commit

Set Force Rx SSM for a WAN port (wan1-wan6)


set ems frequency frequency-config reference-frequency-inputs <port> force-rx-ssm-
sdh <press Tab for options>
commit

Interface Settings

WAN Ports (WAN port number: L1-L6, R1-R6):

Activate WAN port


set ems interface wan-config wan <WAN port number> activate-port true
commit

Set WAN port name alias


set ems interface wan-config wan <WAN port number> name <string>
commit

LAN Ports (slot 1-7,13,15 port 1-4):

Set LAN port name alias


set ems interface lan-config lan <slot> <port> name <string>
commit

Set Unit Type (sfp or phy)


set ems interface lan-config lan <slot> <port> unit-type <sfp/phy>
commit

Activate LAN Port


set ems interface lan-config lan <slot> <port> activate-port true
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 98

Set Mode (bulk or shared)


set ems interface lan-config lan <slot> <port> mode <bulk/shared>
commit

Set Rx Priority (left or right)


set ems interface lan-config lan <slot> <port> rx-priority <left/right>
commit

Set Port Speed (for SFP: 1gbps or 100mbps; for PHY: none)
set ems interface lan-config lan <slot> <port> port-speed <1gbps/100mbps/none>
commit

Set Default Priority (0…6)


set ems interface lan-config lan <slot> <port> default-piority <0…6>
commit

Set Ingress/Egress Rate Limit


set ems interface lan-config lan <slot> <port> rate-ingress <press Tab for options>
set ems interface lan-config lan <slot> <port> rate-egress <press Tab for options>
commit

Set Rate Allowed (for PHY only: auto, 1000fdx, 1000hdx, 100fdx, 100hdx, 10fdx, 10hdx)
set ems interface lan-config lan <slot> <port> rj-45 rate-allowed <press Tab for options>
commit

Set Crossover (for PHY only: auto, mdi or mdix)


set ems interface lan-config lan <slot> <port> rj-45 crossover <auto/mdi/mdix>

TDM Ports (port 1-8)

Set Port Type (cbus or t1-e1)


set ems interface tdmop-config tdmop <port> port-type <cbus or t1-e1>
commit

Activate TDM Port


set ems interface tdmop-config tdmop <port> activate-port true
commit

Set Mode (bulk or shared)


set ems interface lan-config lan <slot> <port> mode <bulk/shared>
commit

Set Rx Priority (left or right)


set ems interface tdmop-config tdmop <port> rx-priority <left/right>
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 99

Tunnels Settings - WAN port number (1-6)

NOTE: The associated WAN port should be enabled through interfaces.

Left Core Unit

LER (port: wan1-wan6, byp1-byp2)


set ems tunnels ler-config ler <tunnel ID> name <tunnel name> port <port> label-out
<label-out #> label-in <label-in #> bfd <on/off>
commit

LSR (port-a: wan1-wan6; port-b: wan1-wan6, byp1-byp2)


set ems tunnels lsr-config lsr <tunnel ID> name <tunnel name> port-a <port-a> port-
b <port-b> label-out-a <label-out-a> label-in-a <label-in-a> label-out-b <label-out-b>
label-in-b <label-in-b>
commit

Right Core Unit

LER (port: wan1-wan6, byp1-byp2)


set ems tunnels ler-config ler <tunnel ID> name <tunnel name> port <port> label-out
<label-out> label-in <label-in> bfd <on/off>
commit

eLER (port-a: wan1-wan6; port-b: wan1-wan6, byp1-byp2)


set ems tunnels eler-config eler <tunnel ID> name <tunnel name> port-a <port-a>
port-b <port-b> label-out-a <label-out-a> label-in-a <label-in-a> label-out-b <label-
out-b> label-in-b <label-in-b>
commit

LSR (port-a: wan1-wan6; port-b: wan1-wan6, byp1-byp2)


set ems tunnels lsr-config lsr <tunnel ID> name <tunnel name> port-a <port-a> port-
b <port-b> label-out-a <label-out-a> label-in-a <label-in-a> label-out-b <label-out-b>
label-in-b <label-in-b>
commit

Services Settings

NOTE: The associated tunnel(s) should be created and the Access (LAN/TDM) interface
port should be set for the proper unit type and enabled.

VPWS, Ethernet, 1+1 protection, Left or Right Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category ethernet lan port <LAN port alias>
bridging-criteria <by-port or by-port-and-vlan> [vlan <VLAN #>] protection-path 1+1
tunnel <LER tunnel ID>

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 100

commit

VPWS, Ethernet, 1:1 protection, Left Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category ethernet lan port <LAN port alias>
bridging-criteria <by-port or by-port-and-vlan> [vlan <VLAN #>] protection-path 1:1
primary-tunnel <LER tunnel ID> secondary-tunnel <LER tunnel ID>
commit

VPWS, Ethernet, 1:1 protection, Right Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category ethernet lan port <LAN port alias>
bridging-criteria <by-port or by-port-and-vlan> [vlan <VLAN #>] protection-path 1:1 e-
tunnel <eLER tunnel ID>
commit

VPLS (Ethernet), 1:1 protection, Left Core Unit

set ems services vpls-config vpls <service ID> name <service name> bridging-
criteria <by-port or by-port-and-vlan> [vlan <VLAN #>]
set ems services vpls-config vpls <service ID> local-endpoints <LAN port alias>
set ems services vpls-config vpls <service ID> pseudowires <PW ID> primary-tunnel
<LER tunnel ID> secondary-tunnel <LER tunnel ID> label-out <PW label out> label-
in <PW label in>
commit

VPLS (Ethernet), 1:1 protection, Right Core Unit

set ems services vpls-config vpls <service ID> name <service name> bridging-
criteria <by-port or by-port-and-vlan> [vlan <VLAN #>]
set ems services vpls-config vpls <service ID> local-endpoints <LAN port alias>
set ems services vpls-config vpls <service ID> pseudowires <PW ID> e-tunnel
<eLER tunnel ID> label-out <PW label out> label-in <PW label in>
commit

VPWS, TDM, 1+1 protection, Left or Right Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category tdm tdmop port <TDMoP port#>
bundle-id <bundle ID> timeslots <timeslot# or all-timeslots > priority <5 or 7>
signaling-channel <yes or no> packetizing model <high-bw-utilization, low-latency,
custom> [jitter-buffer-delay <press Tab for options>] [frame-count <press Tab for
options>] protection-path 1+1 tunnel <LER tunnel ID>
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 101

VPWS, TDM, 1:1 protection, Left Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category tdm tdmop port <TDMoP port#>
bundle-id <bundle ID> timeslots <timeslot# or all-timeslots > priority <5 or 7>
signaling-channel <yes or no> packetizing model <high-bw-utilization, low-latency,
custom> [jitter-buffer-delay <press Tab for options>] [frame-count <press Tab for
options>] protection-path 1:1 primary-tunnel <LER tunnel ID> secondary-tunnel
<LER tunnel ID>
commit

VPWS, TDM, 1:1 protection, Right Core Unit

set ems services vpws-config vpws <service ID> name <service name> label-out
<PW label out> label-in <PW label in> category tdm tdmop port <TDMoP port#>
bundle-id <bundle ID> timeslots <timeslot# or all-timeslots> priority <5 or 7>
signaling-channel <yes or no> packetizing model <high-bw-utilization, low-latency,
custom> [jitter-buffer-delay <press Tab for options>] [frame-count <press Tab for
options>] protection-path 1:1 e-tunnel <eLER tunnel ID>
commit

NOTE: For E1, use "bundle-timeslots" instead of "timeslots".

Configuration Scripts (example for a 2-node system)

Node 1 - Left Core Unit (Headend Internal)

set ems settings node-name Node1


commit

set ems interface wan-config wan L1 activate-port true


commit
set ems interface wan-config wan L3 activate-port true
commit
set ems interface lan-config lan 1 1 unit-type sfp mode shared
commit
set ems interface lan-config lan 1 1 activate-port true
commit
set ems interface lan-config lan 1 2 unit-type sfp mode shared
commit
set ems interface lan-config lan 1 2 activate-port true
commit

set ems interface tdmop-config tdmop 5 mode bulk rx-priority left port-type CBUS
commit
set ems interface tdmop-config tdmop 5 activate-port true
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 102

set ems interface tdmop-config tdmop 6 mode bulk rx-priority left port-type CBUS
commit
set ems interface tdmop-config tdmop 6 activate-port true
commit

set ems tunnels ler-config ler 1 name 10G-VPLS-Primary port wan1 label-out 1000 label-in 1000
bfd on
commit
set ems tunnels ler-config ler 2 name 10G-VPLS-Secondary port byp1 label-out 1001 label-in
1002 bfd on
commit
set ems tunnels ler-config ler 3 name 1G-VPLS-Primary port wan3 label-out 1003 label-in 1003
bfd on
commit
set ems tunnels ler-config ler 4 name 1G-VPLS-Secondary port byp2 label-out 1004 label-in 1005
bfd on
commit
set ems tunnels ler-config ler 5 name 10G-VPWS-Primary port wan1 label-out 1006 label-in 1006
bfd on
commit
set ems tunnels ler-config ler 6 name 1G-VPWS-Primary port wan3 label-out 1007 label-in 1007
bfd on
commit

set ems services vpws-config vpws 3 name 10G-VPWS-CBUS-Primary label-out 1010 label-in
1010 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 3 timeslots all-timeslots protection-path 1+1 tunnel 5 port 5
commit
set ems services vpws-config vpws 4 name 1G-VPWS-CBUS-Primary label-out 1011 label-in
1011 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 4 timeslots all-timeslots protection-path 1+1 tunnel 6 port 6
commit

set ems services vpls-config vpls 1 name 10G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-1
set ems services vpls-config vpls 1 pseudowires 1 label-out 1014 label-in 1014 primary-tunnel 1
secondary-tunnel 2
commit
set ems services vpls-config vpls 2 name 1G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-2
set ems services vpls-config vpls 2 pseudowires 1 label-out 1015 label-in 1015 primary-tunnel 3
secondary-tunnel 4
commit

set ems frequency frequency-config node-type HEI


commit

Node 1 - Right Core Unit (Headend Internal)


set ems settings node-name Node1

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 103

commit

set ems interface wan-config wan R1 activate-port true


commit
set ems interface wan-config wan R3 activate-port true
commit
set ems interface lan-config lan 1 1 unit-type phy mode shared
commit
set ems interface lan-config lan 1 1 activate-port true
commit
set ems interface lan-config lan 1 2 unit-type phy mode shared
commit
set ems interface lan-config lan 1 2 activate-port true
commit
set ems interface lan-config lan 3 1 unit-type sfp mode bulk rx-priority left
commit
set ems interface lan-config lan 3 1 activate-port true
commit
set ems interface lan-config lan 3 2 unit-type sfp mode bulk rx-priority left
commit
set ems interface lan-config lan 3 2 activate-port true
commit
set ems interface tdmop-config tdmop 1 mode bulk rx-priority left port-type t1-e1
commit
set ems interface tdmop-config tdmop 1 activate-port true
commit
set ems interface tdmop-config tdmop 2 mode bulk rx-priority left port-type t1-e1
commit
set ems interface tdmop-config tdmop 2 activate-port true
commit
set ems interface tdmop-config tdmop 5 mode bulk rx-priority left port-type CBUS
commit
set ems interface tdmop-config tdmop 5 activate-port true
commit
set ems interface tdmop-config tdmop 6 mode bulk rx-priority left port-type CBUS
commit
set ems interface tdmop-config tdmop 6 activate-port true
commit

set ems tunnels eler-config eler 1 name 10G-VPLS-Secondary port-a wan1 label-out-a 1000
label-in-a 1000 port-b byp1 label-out-b 1002 label-in-b 1001 bfd on
commit
set ems tunnels eler-config eler 2 name 1G-VPLS-Secondary port-a wan3 label-out-a 1003 label-
in-a 1003 port-b byp2 label-out-b 1005 label-in-b 1004 bfd on
commit
set ems tunnels ler-config ler 1 name 10G-VPWS-Secondary port wan1 label-out 1006 label-in
1006 bfd on
commit
set ems tunnels ler-config ler 2 name 1G-VPWS-Secondary port wan3 label-out 1007 label-in
1007 bfd on
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 104

set ems services vpws-config vpws 1 name 10G-VPWS-T1-Secondary label-out 1008 label-in
1008 category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id
1 timeslots all-timeslots protection-path 1+1 tunnel 1 port 1
commit
set ems services vpws-config vpws 2 name 1G-VPWS-T1-Secondary label-out 1009 label-in
1009 category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id
2 timeslots all-timeslots protection-path 1+1 tunnel 2 port 2
commit
set ems services vpws-config vpws 3 name 10G-VPWS-CBUS-Secondary label-out 1010 label-in
1010 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 3 timeslots all-timeslots protection-path 1+1 tunnel 1 port 5
commit
set ems services vpws-config vpws 4 name 1G-VPWS-CBUS-Secondary label-out 1011 label-in
1011 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 4 timeslots all-timeslots protection-path 1+1 tunnel 2 port 6
commit
set ems services vpws-config vpws 5 name 10G-VPWS-LAN-Secondary label-out 1012 label-in
1012 category ethernet lan port lan-3-1 bridging-criteria by-port protection-path 1+1 tunnel 1
commit
set ems services vpws-config vpws 6 name 1G-VPWS-LAN-Secondary label-out 1013 label-in
1013 category ethernet lan port lan-3-2 bridging-criteria by-port protection-path 1+1 tunnel 2
commit

set ems services vpls-config vpls 1 name 10G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-1
set ems services vpls-config vpls 1 pseudowires 1 label-out 1014 label-in 1014 e-tunnel 1
commit
set ems services vpls-config vpls 2 name 1G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-2
set ems services vpls-config vpls 2 pseudowires 1 label-out 1015 label-in 1015 e-tunnel 2
commit

set ems frequency frequency-config node-type HEI


commit

Node 2 - Left Core Unit (Normal)


set ems settings node-name Node2
commit

set ems interface wan-config wan L1 activate-port true


commit
set ems interface wan-config wan L3 activate-port true
commit
set ems interface lan-config lan 1 1 unit-type phy mode shared
commit
set ems interface lan-config lan 1 1 activate-port true
commit
set ems interface lan-config lan 1 2 unit-type phy mode shared
commit
set ems interface lan-config lan 1 2 activate-port true
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 105

set ems interface lan-config lan 1 3 unit-type phy mode shared


commit
set ems interface lan-config lan 1 3 activate-port true
commit
set ems interface lan-config lan 1 4 unit-type phy mode shared
commit
set ems interface lan-config lan 1 4 activate-port true
commit
set ems interface lan-config lan 3 1 unit-type sfp mode bulk rx-priority right
commit
set ems interface lan-config lan 3 1 activate-port true
commit
set ems interface lan-config lan 3 2 unit-type sfp mode bulk rx-priority right
commit
set ems interface lan-config lan 3 2 activate-port true
commit
set ems interface tdmop-config tdmop 1 mode bulk rx-priority right port-type t1-e1
commit
set ems interface tdmop-config tdmop 1 activate-port true
commit
set ems interface tdmop-config tdmop 2 mode bulk rx-priority right port-type t1-e1
commit
set ems interface tdmop-config tdmop 2 activate-port true
commit
set ems interface tdmop-config tdmop 5 mode bulk rx-priority right port-type CBUS
commit
set ems interface tdmop-config tdmop 5 activate-port true
commit
set ems interface tdmop-config tdmop 6 mode bulk rx-priority right port-type CBUS
commit
set ems interface tdmop-config tdmop 6 activate-port true
commit

set ems tunnels ler-config ler 1 name 10G-VPLS-Secondary port wan1 label-out 1000 label-in
1000 bfd on
commit
set ems tunnels ler-config ler 2 name 10G-VPLS-Primary port byp1 label-out 1001 label-in 1002
bfd on
commit
set ems tunnels ler-config ler 3 name 1G-VPLS-Secondary port wan3 label-out 1003 label-in
1003 bfd on
commit
set ems tunnels ler-config ler 4 name 1G-VPLS-Primary port byp2 label-out 1004 label-in 1005
bfd on
commit
set ems tunnels ler-config ler 5 name 10G-VPWS-Secondary port wan1 label-out 1006 label-in
1006 bfd on
commit
set ems tunnels ler-config ler 6 name 1G-VPWS-Secondary port wan3 label-out 1007 label-in
1007 bfd on
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 106

set ems services vpws-config vpws 1 name 10G-VPWS-T1-Secondary label-out 1008 label-in
1008 category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id
1 timeslots all-timeslots protection-path 1+1 tunnel 5 port 1
commit
set ems services vpws-config vpws 2 name 1G-VPWS-T1-Secondary label-out 1009 label-in
1009 category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id
2 timeslots all-timeslots protection-path 1+1 tunnel 6 port 2
commit
set ems services vpws-config vpws 3 name 10G-VPWS-CBUS-Secondary label-out 1010 label-in
1010 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 3 timeslots all-timeslots protection-path 1+1 tunnel 5 port 5
commit
set ems services vpws-config vpws 4 name 1G-VPWS-CBUS-Secondary label-out 1011 label-in
1011 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 4 timeslots all-timeslots protection-path 1+1 tunnel 6 port 6
commit
set ems services vpws-config vpws 5 name 10G-VPWS-LAN-Secondary label-out 1012 label-in
1012 category ethernet lan port lan-3-1 bridging-criteria by-port protection-path 1+1 tunnel 5
commit
set ems services vpws-config vpws 6 name 1G-VPWS-LAN-Secondary label-out 1013 label-in
1013 category ethernet lan port lan-3-2 bridging-criteria by-port protection-path 1+1 tunnel 6
commit

set ems services vpls-config vpls 1 name 10G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-1
set ems services vpls-config vpls 1 local-endpoints lan-1-2
set ems services vpls-config vpls 1 pseudowires 1 label-out 1014 label-in 1014 primary-tunnel 2
secondary-tunnel 1
commit
set ems services vpls-config vpls 2 name 1G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-3
set ems services vpls-config vpls 2 local-endpoints lan-1-4
set ems services vpls-config vpls 2 pseudowires 1 label-out 1015 label-in 1015 primary-tunnel 4
secondary-tunnel 3
commit

set ems frequency frequency-config node-type normal reference-frequency-inputs wan-1 force-rx-


ssm-sdh none
commit
set ems frequency frequency-config node-type normal reference-frequency-inputs wan-3 force-rx-
ssm-sdh none
commit

Node 2 - Right Core Unit (Normal)


set ems settings node-name Node2
commit

set ems interface wan-config wan R1 activate-port true


commit
set ems interface wan-config wan R3 activate-port true
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 107

set ems interface lan-config lan 1 1 unit-type phy mode shared


commit
set ems interface lan-config lan 1 1 activate-port true
commit
set ems interface lan-config lan 1 2 unit-type phy mode shared
commit
set ems interface lan-config lan 1 2 activate-port true
commit
set ems interface lan-config lan 1 3 unit-type phy mode shared
commit
set ems interface lan-config lan 1 3 activate-port true
commit
set ems interface lan-config lan 1 4 unit-type phy mode shared
commit
set ems interface lan-config lan 1 4 activate-port true
commit
set ems interface lan-config lan 3 1 unit-type sfp mode bulk rx-priority right
commit
set ems interface lan-config lan 3 1 activate-port true
commit
set ems interface lan-config lan 3 2 unit-type sfp mode bulk rx-priority right
commit
set ems interface lan-config lan 3 2 activate-port true
commit
set ems interface tdmop-config tdmop 1 mode bulk rx-priority right port-type t1-e1
commit
set ems interface tdmop-config tdmop 1 activate-port true
commit
set ems interface tdmop-config tdmop 2 mode bulk rx-priority right port-type t1-e1
commit
set ems interface tdmop-config tdmop 2 activate-port true
commit
set ems interface tdmop-config tdmop 5 mode bulk rx-priority right port-type CBUS
commit
set ems interface tdmop-config tdmop 5 activate-port true
commit
set ems interface tdmop-config tdmop 6 mode bulk rx-priority right port-type CBUS
commit
set ems interface tdmop-config tdmop 6 activate-port true
commit

set ems tunnels eler-config eler 1 name 10G-VPLS-Primary port-a wan1 label-out-a 1000 label-
in-a 1000 port-b byp1 label-out-b 1002 label-in-b 1001 bfd on
commit
set ems tunnels eler-config eler 2 name 1G-VPLS-Primary port-a wan3 label-out-a 1003 label-in-
a 1003 port-b byp2 label-out-b 1005 label-in-b 1004 bfd on
commit
set ems tunnels ler-config ler 1 name 10G-VPWS-Primary port wan1 label-out 1006 label-in 1006
bfd on
commit
set ems tunnels ler-config ler 2 name 1G-VPWS-Primary port wan3 label-out 1007 label-in 1007
bfd on

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 108

commit

set ems services vpws-config vpws 1 name 10G-VPWS-T1-Primary label-out 1008 label-in 1008
category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id 1
timeslots all-timeslots protection-path 1+1 tunnel 1 port 1
commit
set ems services vpws-config vpws 2 name 1G-VPWS-T1-Primary label-out 1009 label-in 1009
category tdm tdmop priority 7 signaling-channel no packetizing-model low-latency bundle-id 2
timeslots all-timeslots protection-path 1+1 tunnel 2 port 2
commit
set ems services vpws-config vpws 3 name 10G-VPWS-CBUS-Primary label-out 1010 label-in
1010 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 3 timeslots all-timeslots protection-path 1+1 tunnel 1 port 5
commit
set ems services vpws-config vpws 4 name 1G-VPWS-CBUS-Primary label-out 1011 label-in
1011 category tdm tdmop priority 7 signaling-channel yes packetizing-model low-latency bundle-
id 4 timeslots all-timeslots protection-path 1+1 tunnel 2 port 6
commit
set ems services vpws-config vpws 5 name 10G-VPWS-LAN-Primary label-out 1012 label-in
1012 category ethernet lan port lan-3-1 bridging-criteria by-port protection-path 1+1 tunnel 1
commit
set ems services vpws-config vpws 6 name 1G-VPWS-LAN-Primary label-out 1013 label-in 1013
category ethernet lan port lan-3-2 bridging-criteria by-port protection-path 1+1 tunnel 2
commit

set ems services vpls-config vpls 1 name 10G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-1
set ems services vpls-config vpls 1 local-endpoints lan-1-2
set ems services vpls-config vpls 1 pseudowires 1 label-out 1014 label-in 1014 e-tunnel 1
commit
set ems services vpls-config vpls 2 name 1G-VPLS-LAN bridging-criteria by-port local-endpoints
lan-1-3
set ems services vpls-config vpls 2 local-endpoints lan-1-4
set ems services vpls-config vpls 2 pseudowires 1 label-out 1015 label-in 1015 e-tunnel 2
commit

set ems frequency frequency-config node-type normal reference-frequency-inputs wan-1 force-rx-


ssm-sdh none
commit
set ems frequency frequency-config node-type normal reference-frequency-inputs wan-3 force-rx-
ssm-sdh none
commit

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 109

APPENDIX A

TCP/UDP PORTS USED


BY JUNGLEPAX

TCP 80 HTTP
TCP 443 HTTPS
TCP 830 NETCONF
TCP 22 SSH
UDP 123 NTP – outgoing only
UDP 161 SNMP (future)
UDP 162 SNMP traps (future) – outgoing only

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 110

APPENDIX B

LIST OF ILLUSTRATIONS

List of Figures

FIGURE DESCRIPTION PAGE

Figure 1: WebUI – Login View (appearance prior to user login) ............................................ 11 
Figure 2: Node List View......................................................................................................... 11 
Figure 3: WebUI Header ......................................................................................................... 12 
Figure 4: Configure button’s action menu............................................................................... 12 
Figure 5: Notifications button with and without unread notifications ...................................... 13 
Figure 6: Expanding and collapsing “accordions” .................................................................. 14 
Figure 7: Opening and closing panels associated with eyeglasses symbols ......................... 15 
Figure 8: Mandatory entry field ............................................................................................... 15 
Figure 9: Configuration change indication (prior to committing) ............................................. 16 
Figure 10: Page navigation panel ........................................................................................... 17 
Figure 11: Node IDs as default Node Names ......................................................................... 18 
Figure 12: DP Alarm Status Panel .......................................................................................... 18 
Figure 13: WAN port connectivity panel ................................................................................. 19 
Figure 14: eMS tab ................................................................................................................. 20 
Figure 15: NMS Port 1 – Config Tab ...................................................................................... 21 
Figure 16: Inventory tab’s Chassis and Core Units accordions.............................................. 24 
Figure 17: Inventory tab’s Access Units accordion ................................................................ 26 
Figure 18: Inventory tab’s Power Unit’s and Expansion Shelf accordions ............................. 27 
Figure 19: Interfaces tab’s WAN Ports accordion – Status tab .............................................. 29 
Figure 20: Interfaces tab’s WAN Ports accordion – Config tab .............................................. 31 
Figure 21: Interfaces tab’s LAN Interfaces accordion – Status tab ........................................ 32 
Figure 22: Interfaces tab’s LAN Interfaces accordion – Config tab (SFP panel).................... 34 
Figure 23: Interfaces tab’s LAN Interfaces accordion – Config tab (PHY panel) ................... 35 
Figure 24: Interfaces tab’s TDMoP Interfaces accordion – Status tab ................................... 37 
Figure 25: Interfaces tab’s TDMoP Interfaces accordion – Config tab (T1/E1 panel) ............ 40 
Figure 26: Interfaces tab’s TDMoP Interfaces accordion – Config tab (CBUS panel) ........... 41 
Figure 27: Examples of tunnels without eLERs ...................................................................... 43 
Figure 28: Example of a tunnel with eLER (Tunnel 3) ............................................................ 43 
Figure 29: Examples of tunnels in a network without redundant Core Unit ........................... 44 
Figure 30: LSR, LER and eLER tunnels in various linear network solutions ......................... 44 
Figure 31: Examples of LSR, LER and eLER tunnels on a spur ............................................ 45 
Figure 32: LSR tunnels bypassed between Core Units.......................................................... 46 
Figure 33: Tunnel tab’s LSR accordion .................................................................................. 46 
Figure 34: Tunnel tab’s LER accordion (Config tab) .............................................................. 48 
Figure 35: Tunnel tab’s LER accordion (Status Tab) ............................................................. 50 
Figure 36: Tunnel tab’s eLER accordion (n/a to Left Core) .................................................... 50 
Figure 37: VPWS accordion with a TDM service panel opened............................................. 54 

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 111

List of Figures (Continued)

FIGURE DESCRIPTION PAGE


 
Figure 38: VPWS accordion with an add service panel for Ethernet service implementing
1+1 path protection ................................................................................................ 55 
Figure 39: VPLS accordion with a service panel opened ....................................................... 60 
Figure 40: Pseudowires table with add pseudowire sub-panel open ..................................... 61 
Figure 41: Local Endpoints table with add port sub-panel open ............................................ 62 
Figure 42: Freq Sync Tab with Reference Sync Inputs’ Status tab selected ......................... 64 
Figure 43: Freq Sync Tab with Reference Sync Inputs’ Config tab selected ......................... 67 
Figure 44: Time Sync tab layout when Primary/Secondary Master is selected ..................... 69 
Figure 45: Time Sync tab layout when Client is selected ....................................................... 69 
Figure 46: Current Alarms Tab ............................................................................................... 71 
Figure 47: Alarm Log Tab ....................................................................................................... 73 
Figure 48: Input and Output Frame Statistics ......................................................................... 74 
Figure 49: Set loopback mode options for a 10G WAN port .................................................. 75 
Figure 50: JunglePAX loopbacks ........................................................................................... 75 
Figure 51: WAN ports diagnostics table ................................................................................. 76 
Figure 52: WAN port diagnostics panel .................................................................................. 77 
Figure 53: TDMoP Trunk Uplink panel ................................................................................... 78 
Figure 54: Performance information for a CBUS port ............................................................ 79 
Figure 55: Performance information for a T1 port .................................................................. 79 
Figure 56: Bundle performance information ........................................................................... 80 
Figure 57: User Management subtab with Administration Roles accordion open.................. 81 
Figure 58: Authorization Role panel ....................................................................................... 83 
Figure 59: User Management subtab with Local Users accordion opened ............................ 84 
Figure 60: User Management subtab with RADIUS Users and User Authentication
accordions open .................................................................................................... 85 
Figure 61: Security subtab with Operations accordion open .................................................. 87 
Figure 62: RADIUS Configurations accordion ........................................................................ 89 
Figure 63: Distribution accordion ............................................................................................ 90 

List of Tables

TABLE DESCRIPTION PAGE

Table 1: Use of Signaling Channel in firmware versions ≤1.11 .............................................. 57 


Table 2: Selectable Frame Count Values ............................................................................... 59 
Table 3: Security sensitive functions ...................................................................................... 82 
Table 4: Functionalities addable to lists of privileges and restrictions.................................... 82 

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 112

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
 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
 CC Core Card, Cross-Connect
 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. 2018


342-90001-PS2
Draft 1
January 2018
Page 113

 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)
 DTT Direct Transfer Trip
 DUS Don’t Use for Synchronization
 E1 European Primary Multiplex Signal (2,048 kb/s)
 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
 GMT Greenwich Mean Time
 GPS Geo-Positioning Satellite
 H/W Hardware

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 114

 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
 MAC Media Access Control
 MDI Media Dependent Interface
 MP Management Plane

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 115

 MP2MP Multipoint-to-Multipoint
 MPLS Multiprotocol Label Switching
 MPLS-TP Multiprotocol Label Switching – Transport Profile
 MTBF Mean Time Between Failures
 NEBS Network Equipment-Building System
 NMS Network Management System
 NTP Network Timing Protocol
 OAM Operations, Administration and Maintenance
 OOF Out Of Frame
 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
 PW Pseudowire
 QoS Quality of Service
 QU Quality Unknown
 RADIUS Remote Authentication Dial-In User Service
 RAI Remote Alarm Indication

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 116

 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
 ST3E Stratum 3E
 STU Synchronized, Traceability Unknown
 S/W Software
 SWC Surge Withstand Capability
 T1 Digital Signal level 1 (1,544 kb/s)
 T1MX T1 Multiplexer (a member of Lentronics Multiplexers’ family)
 TCP Transmission Control Protocol

Copyright  GE Multilin Inc. 2018


342-90001-PS2
Draft 1
January 2018
Page 117

 TDM Time Division Multiplexing


 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
 VF Voice Frequency
 WAN Wide Area Network
 WebUI Web User Interface
 WEEE Waste Electrical and Electronic Equipment
 WIS WAN Interface Sublayer
 XMT Transmit

Copyright  GE Multilin Inc. 2018

You might also like