Adva FSP150
Adva FSP150
All rights reserved. Hardware and software mentioned in this document includes software developed by ADVA
Optical Networking SE ("ADVA Optical Networking"), the Apache Software Foundation
([Link] Teodor Danciu ([Link] and/or other open source
software. Some software was created using ORBacus for Java by Object-Oriented Concepts, Inc.
Trademarks
The terms ADVATM, FSP 3000®, EtherjackTM and the EtherjackTM logo are trademarks or registered
trademarks of ADVA Optical Networking in the United States, Germany and/or other countries. All other
company products or services mentioned in this document may be trademarks or service marks of ADVA
Optical Networking or their respective owner.
Patents
The content described in this document may be covered by patents or pending patent applications of ADVA
Optical Networking. The furnishing of this document does not give you any license to these patents.
Disclaimers
Nothing in this document shall be construed as granting any license or rights with respect to its content or the
patents and trademarks mentioned above. The content of this document may include technical inaccuracies or
typographical errors, and is subject to change at any time without notice. Reliance on this content is at the
relying party's sole risk and will not create any liability or obligation for ADVA Optical Networking. Any
references in this document to publications and/or Internet sites that are not from ADVA Optical Networking are
provided for convenience only and do not in any manner serve as an endorsement of those publications and/or
Internet sites. The materials within those publications and/or Internet sites are not part of the materials for any
ADVA Optical Networking information, product, or service, and use of those publications and/or Internet sites is
at your own risk.
THE CONTENT OF THIS DOCUMENT IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL ADVA OPTICAL NETWORKING, ITS AFFILIATES, EMPLOYEES, OFFICERS OR ITS SUPPLIERS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND BASED ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE SAME APPLIES FOR ANY HARDWARE OR SOFTWARE COVERED BY THIS DOCUMENT,
UNLESS A SIGNED AGREEMENT WITH ADVA OPTICAL NETWORKING OR THE APPLICABLE
PRODUCT LIABILITY LAW EXPRESSLY STATES OTHERWISE.
Introduction 55
Minimum System Requirements 59
Logging On and Off 60
Logging On 60
Logging Off 67
User Session Timeout 68
Getting Familiar with the Web-based GUI 69
About the Workspace 70
Title Bar 70
Menu Bar 70
Tool Bar 71
Selection Tree 73
Details Pane 74
Operations and Provisioning Field Types 75
Command Buttons 75
Alarms Pane 76
Keyboard Navigation 77
Web-based GUI Applications 78
Configuration View 79
Maintenance View 83
Viewing Entities in Maintenance View 87
Editing Alarm Attributes 88
Loopbacks 89
Etherjack® Diagnostics 90
Performance Monitoring View 91
ESA and CFM 91
Precision Time Protocol 91
Sync Jack 91
Service Activation Test 91
Two-Way Active Measurement Protocol 91
Open Flow 91
ConnectGuard 91
IPFIX 91
Introduction 93
Upgrade Software 94
Provisioning the GE11xPro 103
Recommended Sequence of Steps for Initial Turn Up of a GE11xPro 104
Provision System Options 106
Configure System 106
Configure Logs 108
Configure ACL 110
Configure LLDP 111
Edit the Security Banner 112
Edit Time Zone 113
Edit System Time of Day 114
Configure Data Export 118
Provision NE-1 Common Units 120
Configure NE-1 120
Configure NTE11xPRO 122
Configure PSUs - GE112Pro (H)/GE114Pro (SH)/GE114Pro (CSH)/GE114Pro (HE) 123
Provision PSE 125
Configure PSE Group 125
Configure PSE Port 126
Provision Secure Access 127
Configure Security Keys 127
Configure Security Policy 130
Configure Local Non-Crypto Users 131
Configure Local Crypto User - GE114Pro (C)/GE114Pro (CSH) 135
Configure Remote Authentication 141
Provision SNMP Access 143
Enable Software License 144
Configure Flexible Port (Ethernet Port II) 147
Provision Access Port Services 148
Ethernet Private Line Service Provisioning 149
Ethernet Virtual Private Line Service Provisioning 164
Provision Network Ports 181
Provision Network Ports without LAG or Protection Group 182
Provision Network Ports in a Protection Group 187
Provision Ports in a LAG Group 191
Provision Ports in a Split Horizon Group (SHG) 196
Provision Network Ports in an Ethernet Ring Protection Group 198
Provision Ethernet over Multiprotocol Label Switching (EoMPLS) 208
Provision GRE 217
Provision GRE IP Interface 217
Provision GRE Tunnel 218
Port Mirroring Provisioning 220
Provision ELP 233
Create ELP 233
Eidt ELP 234
Provision ConnectGuard - GE114Pro (C)/GE114Pro (CSH) 236
Provision Secure Traffic 237
Provision Crypto User’s Authorizations 256
Introduction 515
Loopbacks 516
Performing Loopbacks Using the Web-based GUI 517
Etherjack® Diagnostics 519
Transmission Media Analysis 519
Ethernet Fault Isolation and Diagnostics 520
Cable Length Benchmarks 522
Manually Entering / Editing Cable Length Benchmarks 523
Performance Monitoring 525
Overview 525
Etherjack® PM Features 526
Performance Parameters 527
Performance Parameter Attributes 528
Performance Parameter Counters 529
Bins and Bin Periods 529
Rollover Counter 529
Performance Parameter Thresholding 530
Optical Performance Parameter Thresholding 530
Threshold Crossing Alert Messages 531
Viewing PM Counts and Threshold Values 532
Viewing PMs for Network Port, Access Port, Flow or LAG 532
Viewing PMs for ESA Probes 542
Initializing PM and Distribution Registers 544
Initializing Network Port, Access Port, Flow and LAG Registers 544
Initializing ESA Probe PM Registers 545
Initializing ESA Probe Distribution Registers 546
Editing PM Thresholds 548
Edit Network Port, Access Port, Flow or LAG PM Thresholds 548
Edit ESA Probe PM Registers 549
ESA Provisioning and Operation 551
Provision a Layer-3 Probe 551
Provision a Y.1731 Probe 555
Provision a Reflector 561
Provision an ESA Schedule 564
CFM Provisioning and Operation 572
Optimized for wireless backhaul, the FSP 150GE11xPro enables delivery of Ethernet
services as well as highly accurate synchronization over a fiber-based access network in
a temperature-hardened platform ideal for remote cabinets.
The FSP 150GE11xPro is convection cooled (no fans or filters) and is designed for use in
a desktop or communications closet environment. A selection of wall-mount / rack-mount
kits may be ordered separately (see FSP 150-GE11xPro System Description document
for mounting kit details).
Multiple units may be stacked up to 4 rows high, depending on the operating environment.
(Refer to FSP 150GE11xPro R9.2 Installation and Commissioning Manual document for
air flow requirement details.) A detailed list of system features is provided in FSP
150GE11xPro R9.2 System Description document.
The GE101Pro product is 24.5mm high, 13.5mm wide, 113.5mm deep, which are
equipped with a back mounted barrel connectors for 12V AC/DC power adapters.
The GO102Pro(S) and GO102Pro(SP), 66 mm high, 160mm wide, 240mm deep, which
are equipped with either a single AC or -48VDC integrated power supply.
The GE112Pro (m) product is a 34.2 mm high (including heat sink), 144.8 mm wide
(including mounting bracket) and 152 mm deep chassis, which are equipped with two
back mounted barrel connectors for 12V AC/DC power adapters.
Etherjack®
ADVA Optical Networking’s patent-pending Etherjack technology allows a carrier to
deploy profitable Ethernet services by providing an intelligent Ethernet demarcation point
that includes an 802.1ag, Y.1731 and 802.3ah compliant Network Interface Device (NID)
for OAM functionality, plus a Metro Ethernet Forum (MEF) certified User Network
Interface (UNI) for providing advanced services definition. In addition to Y.1731, the
Network Interface Device (NID) supports Etherjack Service Assurance (ESA) for in-
service SLA monitoring critical for carrier-class Ethernet services. The Etherjack service
UNI provides service intelligence necessary for defining Committed Information Rate
(CIR), Excess Information Rate (EIR) and burst size of individual port flow, priorities or
VLANs. ADVA Optical Networking’s unique demarcation function enables carriers to
provide differentiated, profitable Ethernet services.
ConnectGuardTM
ConnectGuardTM is ADVA Optical Networking’s Trade Mark functionality that is
developed based on the Media Access Control (MAC) Security standard defined in IEEE
802.1AE-2006 and IEEE 802.1AEbn-2011. It allows authorized systems that attach to
and interconnect LANs in a network to maintain confidentiality of transmitted data and to
take measures against frames transmitted or modified by unauthorized devices.
With the advantage of ConnectGuard, the GE11xPro products which support this feature
can broaden the application range and benefit both the Customer Premise Equipment
(CPE) and the Service Provider.
• CPE based encryption: The traffic may be secured at the customer CPE with the Inner
VLAN encrypted and Outer VLAN tagged at the NID.
• Management service encryption: The encryption starts from the NID owned by the
Service Provider. The NID is able to filter the traffic based on the incoming VLAN ID
and entry the traffic based on the policy that is to be defined by the end user.
• The smaller overhead of implementing MAC security in an end to end manner makes
ConnectGuard - MAC encryption a good solution for Layer-2 based backhaul.
More information on ConnectGuard and the current implementation can be found in FSP
150-GE11xPro System Description.
GE101Pro
The GE101Pro has the following main features:
With two Ethernet copper/fiber combination ports, the GE101Pro device is capable of
supporting single customers or service configurations over a GbE or 100FX optical
connection. The Ethernet combination ports that may be configured for copper
(10/100/1000BASE-T) or optical (100BASE-FX/1000BASE-X). Port one is fixed and
always designated as a Network port. Port two is an Access ports. The GE101Pro is a
version of the product that does not include Synchronous Ethernet (Sync-E) capability
and ConnectGuard functionality. See Figure 1 for the front view of the GE101Pro.
GO102Pro(S)
The GO102Pro has the following main features:
GO102Pro(SP)
The GO102Pro(SP) has all features supported by GO102Pro(S) while also supporting
Power over Ethernet(POE).
GE112Pro
The GE112Pro has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via a Small Form factor Pluggable (SFP) transceiver or electrical
(10/100/1000BaseT) via RJ45 connector. Using both ports provides 1+1 protection.
Port 1 is dedicated as a Network port. Port 2 may be configured as either the Network
protection port or an Access port.
l Two Access interfaces (Three Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
With four Ethernet copper/fiber combination ports, the GE112Pro device is capable of
supporting multiple customers or service configurations over an optional protected GbE
or 100FX optical connection. The GE112Pro supports four Ethernet combination ports
that may be configured for copper (10/100/1000BASE-T) or optical (100BASE-
FX/1000BASE-X). Port 1 is fixed and always designated as a Network port. Port 2 (a
flexible port) may be configured for LAG or 1+1 Network protection, or as an Access port.
Ports 3 and 4 are dedicated Access ports. The GE112Pro is a version of the product that
does not include Synchronous Ethernet (Sync-E) capability and ConnectGuard
functionality. See Figure 6 for a front view of the GE112Pro -48VDC variant.
GE112Pro (H)
The GE112Pro (H) has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via a Small Form factor Pluggable (SFP) transceiver or electrical
(10/100/1000BaseT) via RJ45 connector. Using both ports provides 1+1 protection.
Port 1 is dedicated as a Network port. Port 2 may be configured as either the Network
protection port or an Access port.
l Two Access interfaces (Three Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
With four Ethernet copper/fiber combination ports, the GE112Pro (H) device is capable of
supporting multiple customers or service configurations over an optional protected GbE
or 100FX optical connection. The GE112Pro (H) supports four Ethernet combination ports
that may be configured for copper (10/100/1000BASE-T) or optical (100BASE-
FX/1000BASE-X). Port 1 is fixed and always designated as a Network port. Port 2 (a
flexible port) may be configured for LAG or 1+1 Network protection, or as an Access port.
Ports 3 and 4 are dedicated Access ports.
The GE112Pro (H) is similar to the GE112Pro, except that it is a version of the product
that includes dual (redundant) pluggable Power Supply Units and is full width. The
GE112Pro (H) is a version of the product that does not include Synchronous Ethernet
(Sync-E) capability and ConnectGuard functionality.
The GE112Pro (H) product is a 1U high (44 mm), full-width (443 mm), and 218 mm deep
chassis, which may be supplied with dual AC, or -48VDC power supplies. See Figure 7
for a front view of the GE112Pro (H).
GE112Pro (m)
The GE112Pro (m) has the following main features:
l One (Protected) Network interface that operates in optical mode only (100BaseFX or
1000BaseX) via a Small Form factor Pluggable (SFP) transceiver. Using both ports
provides 1+1 protection. Port 1 is dedicated as a Network port. Port 2 may be
configured as either the Network protection port or an Access port.
l Two Access interfaces (Three Optional - if Network protection is not
provisioned) where Port 3 can be configured only as optical (100BaseFX or
1000BaseX) via an SFP transceiver and Port 4 can be configured as either electrical
(10/100/1000BaseT) via RJ45 connector or optical (100BaseFX or 1000BaseX) via an
SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
With four Ethernet fiber ports and one copper port, the GE112Pro (m) device is capable of
supporting multiple customers or service configurations over an optional protected GbE
or 100FX optical connection. The GE112Pro (m) supports four Ethernet ports that may be
configured for optical (100BASE-FX/1000BASE-X) and one Ethernet Port that may be
configured for copper (10/100/1000BASE-T) or optical (100BASE-FX/1000BASE-X). Port
1 is fixed and always designated as a Network port. Port 2 (a flexible port) may be
configured for LAG or 1+1 Network protection, or as an Access port. Ports 3 and 4 are
dedicated Access ports. The GE112Pro (m) is a version of the product that does not
include Synchronous Ethernet (Sync-E) capability and ConnectGuard functionality. See
Figure 8 for a front view of the GE112Pro (m).
GE114Pro
The GE114Pro has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via an SFP transceiver or electrical (10/100/1000BaseT) via RJ45
connector. Using both ports provides 1+1 protection. Port 1 is dedicated as a Network
port. Port 2 may be configured as either the Network protection port or an Access port.
l Four Access interfaces (Five Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
With six Ethernet copper/fiber combination ports, the GE114Pro device is capable of
supporting multiple customers or service configurations over an optional protected GbE
or 100FX optical connection. The GE114Pro supports six Ethernet combination ports that
may be configured for copper (10/100/1000BASE-T) or optical (100BASE-FX/1000BASE-
X). Port 1 is fixed and always designated as a Network port. Port 2 (a flexible port) may
be configured for LAG or 1+1 Network protection, or as an Access port. Ports 3 through 6
are dedicated Access ports. The GE114Pro is a version of the product that does not
include Sync-E capability or ConnectGuard functionality. See the following figure for a
front view of the GE114Pro.
GE114Pro (C)
The GE114Pro (C) has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via an SFP transceiver or electrical (10/100/1000BaseT) via RJ45
connector. Using both ports provides 1+1 protection. Port 1 is dedicated as a Network
port. Port 2 may be configured as either the Network protection port or an Access port.
l Four Access interfaces (Five Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
l ConnectGuard Functionality
GE114Pro (C) is similar to GE114Pro, except that it is a version of the product that also
supports ConnectGuard functionality. However, GE114Pro (C) is not a version of the
product that supports Sync-E capability. See the following figure for a front view of the
GE114Pro (C). Note that the front panel of GE114Pro (C) is very similar to GE114Pro,
except that there is a “blue key” symbol placed horizontally which is the logo of
ConnectGuard functionality.
GE114Pro (SH)
The GE114Pro (SH) has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via an SFP transceiver or electrical (10/100/1000BaseT) via RJ45
connector. Using both ports provides 1+1 protection. Port 1 is dedicated as a Network
port. Port 2 may be configured as either the Network protection port or an Access port.
l Four Access interfaces (Five Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Precision Time Protocol (PTP)
l SyncJack (SJ)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
The GE114Pro (SH) is similar to the GE114Pro, except that it is a version of the product
that includes dual (redundant) pluggable Power Supply Units (PSUs), and is full width.
The GE114Pro (SH) is a version of the product that supports Sync-E functionality and
has BITS IN and BITS OUT interfaces via a RJ48c connector for T1/E1 timing input and
output, one TOD interface via RJ45 connector, two Mini-SMB connectors for PPS IN and
PPS (Input/Output) respectively, one Mini-SMB connector for external 10MHz Clock
frequency output (CLK) and one additional front mounted SMA connector for external
GPS signal receiving. GE114Pro (SH) does not support ConnectGuard functionality. See
the following figure for a front view of the GE114Pro (SH).
The GE114Pro (SH) product is a 1U high (44 mm), full-width (443 mm), and 218 mm deep
chassis, which may be supplied with dual AC, or -48VDC power supplies.
GE114Pro (CSH)
The GE114Pro (CSH) has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via an SFP transceiver or electrical (10/100/1000BaseT) via RJ45
connector. Using both ports provides 1+1 protection. Port 1 is dedicated as a Network
port. Port 2 may be configured as either the Network protection port or an Access port.
l Four Access interfaces (Five Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Precision Time Protocol (PTP)
l SyncJack (SJ)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
l ConnectGuard Functionality
The GE114Pro (CSH) is similar to GE114Pro (SH), besides all the interfaces and
features supported in GE114Pro (SH), it is a version of the product that also supports
ConnectGuard functionality. See the following figure for a front view of the GE114Pro
(CSH).
The GE114Pro (CSH) product is a 1U high (44 mm), full-width (443 mm), and 218 mm
deep chassis, which may be supplied with dual AC or -48VDC power supplies.
GE114Pro (HE)
The GE114Pro (HE) has the following main features:
l One (Protected) Network interface that operates in optical mode (100BaseFX or
1000BaseX) via an SFP transceiver or electrical (10/100/1000BaseT) via RJ45
connector. Using both ports provides 1+1 protection. Port 1 is dedicated as a Network
port. Port 2 may be configured as either the Network protection port or an Access port.
l Four Access interfaces (Five Optional - if Network protection is not
provisioned), configured as either electrical (10/100/1000BaseT) via RJ45 connector
or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
l 802.1ad Provider Bridge C-Tag / S-Tag Mapping
l Layer-3 Services Forwarding and ACL Filtering
l Etherjack Service Assurance (ESA) and Connectivity Fault Management (CFM)
l G.8032 Ethernet Ring Protection (ERP)
l Y.1564 Service Activation Testing (SAT)
l Two-Way Active Measurement Protocol (TWAMP)
l Open Flow (OF)
The GE114Pro (HE) is similar to the GE114Pro (SH), except that it is a version of the
product that does not supports PTP related functions, Sync-E or SyncJack and does not
provide PTP related interfaces. GE114Pro (HE) supports Environmental Alarm inputs by
providing a Dry Contact RJ-45 connector in the front panel. Dual pluggable power supply
AC/-48VDC 24 Watts are supported. The front connectors are arranged differently.
The GE114Pro (HE) product is a 1U high (44 mm), full-width (443 mm), and 218 mm deep
chassis, which may be supplied with dual AC / DC power supplies. See the following
figure for a front view of the GE114Pro (HE).
Document Overview
This manual is provided to help you install, configure and operate the FSP 150GE11xPro.
This manual provides an introduction to the FSP 150GE11xPro, a description of its
operation, and a step by step walk-through of the provisioning process.
This version of the FSP 150GE11xPro Provisioning and Operations Manual is applicable
to the FSP 150GE11xPro software release 9.2. For defect resolution and functional
additions please refer to the Release Notes.
Although this document focuses primarily on using the web-based Element Management
System (EMS) Graphical User Interface (GUI) for configuring and monitoring the FSP
150GE11xPro, equivalent CLI or SNMP commands may be used. For more information
regarding the CLI command structure, refer to the FSP 150GE11xPro Command Line
Interface Reference Guide. For more information regarding the SNMP command
structure, refer to the FSP 150GE11xPro SNMP User Guide.
Before installing and provisioning the FSP 150GE11xPro, familiarize yourself with the
FSP 150GE11xPro equipment, its functions and requirements. The following chapters
support the installation and operation of the FSP 150GE11xPro:
Chapter 1, Overview of the FSP 150GE11xPro contains a brief overview of the FSP 150-
GE11xPro equipment, this document and supporting documents in the document suite,
and how to obtain technical assistance.
Chapter 6, Alarms, Events and Probable Causes contains listing of all alarms and events
generated by the system and includes the probable cause of each.
Application Notes for specific features. For CLI option settings and rules, refer to the FSP
150GE11xPro Command Line Interface Reference Guide.
Audience
The reader must have sufficient knowledge of the following when using this document:
Related Documentation
Refer to the following documents for additional information about the FSP 150GE11xPro:
Documentation Feedback
We want our manuals to be as helpful as possible. Feedback regarding the manuals are
therefore always welcome. You can e-mail your comments/suggestions to:
global-techdocu@[Link]
To contact ADVA Optical Networking’s Technical Services by email, use the fol- lowing
address:
support@[Link]
l 24 X 7 telephone support
l Web-based support tools
l On-site support
l Technical training, both on-site and at company facilities in Germany, the UK and the
USA
l Expedited repair service
l Extended hardware warranty service
Customer Login ADVA Optical Networking’s customer login provides a suite of interactive, net- working
services that provide immediate access to information and resources at any time, from
anywhere in the world. This highly integrated Internet application is a powerful, easy-to-
use tool for doing business with us.
The customer login’s broad range of features and services help customers to streamline
business processes and improve productivity. Through your cus- tomer login, you will
find information tailored especially for you, including net- working solutions, services, and
programs. In addition, you can resolve technical issues with Online support services,
download and test software pack- ages, and order training materials.
Contact your local sales office for information on obtaining a customer login. Access your
customer login via the home page at [Link]
Management Interfaces
The FSP 150 family of Ethernet access products support the following Management
Interfaces.
NETCONF/YANG Interface
Although this document focuses on using the web-based EMS GUI for configuring and
monitoring the FSP 150GE11xPro, equivalent NETCONF commands may be used. The
NETCON/YANG models provide a text-based system for local configuration and
management of FSP 150GE11xPro functions. NETCONF access may be attained via
telnet / ssh session. For more information regarding the CLI command structure, refer to
the FSP 150GE11xPro R9.2 NETCONF/YANG Reference Guide.
In the Alarms Pane, all alarms are color coded by severity: red (Critical), orange (Major)
and yellow (Minor).
For further information on the Alarms Pane, see Chapter 2 Web-based Element
Management System.
Management Features
Web access to the onboard Element Manager is via HTTP or HTTPS. Telnet, SSH,
HTTP, HTTPS, FTP, SFTP and SCP protocols may be enabled or disabled individually.
Serial port access may also be disabled. The serial port automatically logs the user off on
disconnect (provisionable).
A user account is locked for a period of 5 minutes after 3 unsuccessful login attempts (not
applicable when RADIUS authentication is used). The number of unsuccessful login
attempts are displayed in the user profile. The lockout period is not configurable.
“NetConf” users can only be created/deleted via the web-based Element Management
System (EMS) Graphical User Interface (GUI) and the Command Line Interface (CLI) by
a user with the “Superuser” privilege level. “NetConf” users have the provisioning
permission only in the NETCONF Interface. “NetConf” users may only be created or
deleted and cannot be edited or migrate to other privilege users. For complete information
regarding the provisioning and operations by “NetConf” users in NETCONF Interface,
refer to the FSP 150-GE11xPro NETCONF User Guide.
Four preconfigured SNMP user accounts are provided as default: “ADMIN,” “MONITOR”,
“OPERATOR” and “PROVISION”. The “CRYPTO” user account is only available in
GE114Pro (C)/GE114Pro (CSH).
ACL Management
Up to 10 system level ACL entries can be made, and each entry can be individually
enabled or disabled. Enabling ACL filtering will “permit” the corresponding management
traffic. Disabling the ACL filtering will “deny” the corresponding management traffic.
Enabled entries apply to all management interfaces and may be provisioned for specific
IP addresses, or an IP address range (subnetwork).
Security Banner
The security banner feature allows an operator to define a custom security banner which
is displayed whenever a user logs onto the system. This banner is displayed on CLI and
web browser logins. The system is shipped with a default security banner.
RADIUS or TACACS+
Up to three RADIUS or TACACS+ servers may be configured for remote authentication.
Both support accounting.
Provisioning
The GE11xPro provides provisioning options for the various NE functions. The following
provides a brief overview of provisioning options supported by the GE11xPro. For
detailed provisioning information, see Operations and Provisioning andProvisioning
Rules .
Communications Provisioning
The GE11xPro provides facilities to set up a management communication configuration
for a particular site or specific network configuration and supports several management
configurations and options.
Operations Provisioning
Provisioning System Options
Facilities are provided to provision system options, including:
o IP connectivity
o time
o access
o SNMP traps
l information logs, including Security, Alarm, Audit and System Logs
l system security, such as the configuration of users, Access Control List (ACL) and
the login security banner (see Facilities are provided to edit PM threshold levels and
initialize PM registers as a precursor to monitoring performance (see Performance
Monitoring).)
l the System Time of Day
l the Time Zone
l the LLLDP configurations
l data export
Provisioning Protection
Facilities are provided to provision protection by adding a protection group for 1+1, Dual
Active Receive).
Facilities are provided to provision protection by adding a LAG group for 1:1 protection
(Network or Access interfaces).
l SNMP details
l Users, including:
o Adding/Editing/Deleting Users
o Editing Passwords
o Editing GUI Login Time-outs
l Remote Authentication
Provisioning Alarms
Facilities are provided to modify alarm notification codes for given alarm condition types,
displayed in the Alarms Pane. The options available for notification codes are: Critical,
Major, Minor, Not Alarmed or Not Reported. For further information on Alarm Monitoring
see Alarm Generation and Monitoring.
following can be configured: Alarm Type, Notification Code, Alarm Description and Alarm
Input Mode (which indicates if the alarm input is enabled and if the monitored condition is
active when the contact is open or closed).
l Barrel Connector for Power Adapter - Output voltage: 12 - 13.5V; output current:
larger than 2A; 2.1mm * 5.5 mm, 7 - 11 mm length. Two back mounted barrel
connectors for GE112Pro (m). One back mounted barrel connector for GE112Pro.
l GE112Pro - Three variants available: two variants with a single integrated Power
Supply Unit (AC or -48VDC), and a third variant (PD) which can be powered by a
Power Sourcing Equipment (PSE, e.g. FSP 150CC-GE114PH) via Port 3 copper. All
the three variants may also be powered via an external adapter (+12V, AC or -48VDC,
ordered separately) connecting to the back mounted barrel connector.
l GE112Pro (m) - Two back mounted barrel connectors are equipped. GE112Pro (m)
may only be powered via the barrel connector by an AC/DC power adapter.
l GE114Pro/GE114Pro (C) - A single integrated Power Supply Unit (AC or -48VDC
variant) with integral Cable Tie support
l GE112Pro (H)/GE114Pro (SH)/GE114 (CSH)/GE114Pro (HE) - Two (redundant)
Power Supply Units (PSUs) with integral Cable Tie support (ordered separately). PSU
Blank Plates are not provided.
l GE114Pro (HE) - Environmental Alarm Input connector - front mounted RJ45
connector
l GE114Pro (SH)/GE114Pro (CSH) - BITS IN/BITS OUT Port - front mounted RJ-48c
T1/E1 timing input/output connector; TOD Port output connector - front mounted RJ45
connector, PPS IN /PPS (input/output) connectors- front mounted Mini-SMB
connectors, one CLK output connector - front mounted Mini-SMB connector
l GE114Pro (SH)/GE114Pro (CSH) - one front mounted SMA GPS connector
l Serial Console Adapter, RJ-45 to DB9, used to connect to a DB-9 RS-232 port on the
PC or Laptop.
l Rack/Wall Mounting Brackets (ordered separately)
Refer to Alarm Attributes, Probable Cause and Trouble Clearing for a description of the
alarm condition, probable cause, suggested trouble clearing procedures, and associated
LED indication. To clear alarm conditions, it is suggested that you start by using the
trouble clearing procedure in Recommended Steps for Trouble Clearing, using the
associated web-based EMS GUI alarm condition.
l USB Port - high speed USB 3.0 port with type A receptacle supporting 3G/4G/LTE
management using a USB wireless adapter. This Port is not available on GO102Pro(S)
or GO102Pro(SP).
l A single integrated Power Supply Unit (AC or -48VDC variant) with integral Cable Tie
support for GO102Pro(S)/GO102Pro(SP)/GE112Pro/GE114Pro/GE114Pro (C)
l Dual (redundant) pluggable Power Supply Unit (PSU) with integral Cable Tie support
(ordered separately) for GE112Pro (H)/GE114Pro (SH)/GE114 (CSH)/GE114Pro (HE).
One PSU Blank Plate is provided.
Single fiber (bi-directional) and dual fiber and copper Small Form factor Pluggable (SFP)
transceivers are supported. ADVA Optical Networking strongly
encourages the use of ADVA Optical Networking sourced SFPs. For more information on
SFPs, see FSP 150-GE11xPro System Description document.
For information on connectors and LED descriptions, see Connector and LED
Descriptions. For details on connector pin assignments, see “Connection Pin
Assignments” in FSP 150-GE11xPro Installation and Commissioning Manual document.
Chassis
Dimensions The dimensions of the chassis are:
Cable Tie
Support
(Integral) Cable handling for the FSP 150GE11xPro is provided by means of an integral Cable Tie
Support. This is located on the mounting brackets which provides a means to tie down all
cables.
Mounting
Brackets The chassis may be positioned as a standalone unit or it may be rack mounted or wall
mounted. Adaptation to rack mounting is possible by using mounting brackets, which
may be ordered separately. Mounting kits are available for a variety of mounting
environments (see Equipment Part Number in FSP 150-GE11xPro System Description
document):
l Wall mounting (GE112Pro (m) provides an integrated mounting bracket on the outside
of the Left-Hand (LH) side panel)
l Standard 19-inch, 23-inch rack or ETSI mounting for a single unit or dual
GE112Pro/GE114Pro/GE114Pro (C) units, or for a single GE112Pro (H)/
GE114Pro (SH)/GE114Pro (CSH)/GE114Pro (HE)
l 19-inch, 23-inch rack or ETSI Extended (recessed) mounting in order to ensure that
optical fiber bend radius is maintained when installed in some cabinets with doors.
Bracket configurations are provided for mounting for a single unit or dual
GE112Pro/GE114Pro/GE114Pro (C) units, or for a single GE112Pro (H)/GE114Pro
(SH)/GE114Pro (CSH)/GE114Pro (HE).
All brackets are designed to be screwed to the sides of the chassis and the screws
supplied have ETSI compatible threads.
System LEDs
The names and functions of each general system LED are described in the following
table.
Each optical Ethernet port provides one LED (Link / Facility) as defined in the following
table.
Each RJ-45 electrical Ethernet port has two LEDs associated with the connector. The
definitions of the LEDs are shown in the following table. Connectors are rotated for the
upper electrical ports (Link/Facility on the left and Rate on the right).
In addition to one earth terminal point, the GE112Pro (m) rear panel also includes two
barrel connectors for AC/DC power adapters, one RS-232 (RJ-45) connector for serial
connection, one MGMT LAN (RJ-45) connector for local management LAN connection.
See Figure 26 on p. 51.
Barrel
Micro USB Power
Port Connector
Earth
Point
Besides the earth terminal points, the GE112Pro (including AC/DC/PD variants) rear
panel also includes one barrel connector for AC/DC power adapter. See Figure 28 on
p. 52.
For all GE11xPro products, the earth terminal point connection is required.
Except for GE112Pro (m), all the other GE11xPro products provide two earth
terminal points at the rear panel and thus user may choose to connect to
either one earth terminal point or two.
Introduction
The web-based Element Management System (EMS) management tool provides a
Graphical User Interface (GUI) for Operation, Administration and Maintenance (OAM)
functions. The web-based EMS GUI provides comprehensive support for fault,
configuration, performance and security functions from a web browser (see Minimum
System Requirements) on a computer connected to Data Communication Network
(DCN) port (see Figure 1).
This chapter describes the web-based EMS GUI and the features it provides to manage
the GE11xPro equipment. The chapter provides the following information:
To access the web-based EMS GUI, the GE11xPro must first be configured with an
Internet Protocol (IP) address and subnet mask. Details on how to do this are provided in
Provision Communications.
The web-based EMS GUI provides the user with the following major applications:
Alarms Pane
The Alarms Pane provides quick visibility and access to current alarms. Alarms are color-
coded based on severity. The Alarms Pane is always displayed no matter what
application is currently selected, thereby providing continuous alarm monitoring.
Configuration
Maintenance
This provides the user with a single view from which to perform all testing and
maintenance related operations, such as:
Users and associated security levels can be viewed, entered and modified by the
Superuser, except that Crypto user account settings cannot be modified and are read-
only. Other users can view and modify their own user accounts. For more information,
see Configure Local Non-Crypto Users and Configure Local Crypto User - GE114Pro
(C)/GE114Pro (CSH).
Software Upgrade
Software may be easily updated to the current release level using the Browser
Management Tool provided by the GUI interface. For more information, see Upgrade
Software.
Feature management provides feature control where a feature can be enabled or disabled
irrespective of the presence of a license for a [Link] operations on feature specific
objects are denied when the feature is disabled. For more information, see Enable
Software License.
Performance Monitoring
l Configure PM interval
l Obtain Performance Monitoring (PM) reports and chart them
l View and configure Performance Parameter threshold values
The Etherjack Service Assurance (ESA) feature is a real-time monitoring tool to allow
Ethernet services to be subjectively measured for the basis of service level agreements
(SLA). ESA may be implemented when GE11xPro equipment is at both ends for round-
trip reporting via Probe and Reflector, or may be implemented with only one GE11xPro for
one-way trip reporting via Probe only. Up to 10 layer-3 Probes and 6 Reflectors are
supported and up to 32(GE112Pro series)/64 (GE114Pro series) layer-2 Probes are
supported. The user is allowed to “Delete All Port Related ESA Entities” at the NTE level
when the corresponding schedules have been deleted.
Standard reporting includes Round Trip Delay and Round Trip Packet Loss. Enhanced
reporting includes round trip and one-way packet delay, one-way packet loss, out-of-
sequence and late arrival packets, and inter-packet delay variation. In addition to
performing an ESA measurement on demand, ESAs may be scheduled for periodic
monitoring. For more information, see ESA Provisioning and Operation.
The Connectivity Fault Management (CFM) feature provides the ability to detect, verify,
isolate and report connectivity faults on a service instance. For more information, see
CFM Provisioning and Operation.
The Precision Time Protocol (PTP) feature provides the ability to create and monitor End-
to-End (E2E) Transparent Clock (TC) functionality and Telecom Slave (TS) functionality
for use in high accuracy time and frequency synchronization applications. See Provision
Precision Time Protocol (PTP) - GE114Pro (SH)/GE114Pro (CSH).
Sync Jack
Supported in all FSP 150-GE11xPro products, the Service Activation Testing (SAT) is an
Ethernet service activation test methodology which is the only standard test
methodology that allows for complete validation of Ethernet service-level-agreements
(SLAs) in a single test. This methodology is built around two key sub-tests: the service
configuration test and the service performance test, which are performed in order. For
more information, see Service Activation Testing.
Open Flow
ConnectGuard
This feature includes two major functions that must be performed by the crypto user. For
more information, see Provision ConnectGuard - GE114Pro (C)/GE114Pro (CSH).
l 200Mhz processor
l supported Operating System (OS) versions: Microsoft Windows XP/Vista/7
l A browser, such as Internet Explorer(IE 11 recommended) or an up-to-date version of
Firefox or Chrome. Other browsers may suffice, but no specific browser is certified by
ADVA Optical Networking.
l 128 Mb of Random Access Memory (RAM)
l Adobe Acrobat Reader 5.0 or greater
l Recommended display: 1024 x 768 with 16+ color bits.
Logging On
Use the following procedure to log on to the GE11xPro web-based EMS GUI
management tool.
This procedure assumes that HTTP and HTTPS access are enabled (factory defaults).
1. Ensure that a DCN connection to the GE11xPro has been established, or the PC is
connected to the DCN port, as required.
3. Open up the appropriate Internet Browser and enter the following address if the login
user is non-crypto user:
[Link]
To ensure the secure connection and authentication between the nodes that
support ConnectGuard, the local user, with crypto privilege or non-crypto
privilege, must use HTTPS in the Internet Browser to access a GE114Pro
(C)/GE114Pro (CSH), i.e. [Link] where
[Link] is the IP address of the DCN that the GE114Pro
(C)/GE114Pro (CSH) is connected to.
4. Enter a valid User ID and Password (default is root and ChgMeNOW, respectively).
See Provision Secure Access for additional login information.
5. Select Login.
6. Select Continue.
8. Open up the appropriate Internet Browser and enter the following address if the login
user is the crypto user:
[Link]
To ensure the secure connection and authentication between the nodes that
support ConnectGuard, the local user, with Crypto privilege or non-crypto
privilege, must use HTTPS in the Internet Browser to access a GE114Pro
(C)/GE114Pro (CSH), i.e. [Link] where
[Link] is the IP address of the DCN that the GE114Pro
(C)/GE114Pro (CSH) is connected to.
The Internet Browser page indicates that website to visit has security
certificate problem
Different Internet Browsers may have different caution pages for the
HTTPS access. The differences will not be mentioned in detail in this
procedure.
9. Click on the option to trust the website to visit and continue with the connection.
10. Enter the Crypto User ID and Password (default login password is ChegMeNOW).
See Provision Secure Access for additional login information.
Click on Login.
The user with Superuser privilege can change the login password of
the crypto user, which can cause the crypto user’s crypto password to
be cleared, so that the crypto user must reset new crypto password at
next login (See 12).
For more information about configuring the crypto user, see Configure
Local Crypto User - GE114Pro (C)/GE114Pro (CSH).
For a crypto user account, if it is the first-time login or the first-time re-
login after restoring DB or factory defaults or a tamper event reboot, it
is required that the crypto user reset the crypto password on the login
Fo page (See 12).
The “first-time login” mentioned in this procedure refers to the very first time
to use the web-based GUI or the first login after restoring factory defaults or
after a tamper event reboot.
If the entered new crypto password does not meet the crypto
password requirement, an error message will pop up indicating that the
user has no sufficient privilege to log on.
Logging Off
To log out of the GE11xPro web-based EMS GUI management tool:
When this occurs, simply select here from the Authentication Failed screen to go to the
GE11xPro login screen, and continue with the logon sequence (see 4 of Logging On).
The Details Pane provides a different set of viewing and editing options depending on the
application and entity selected. The Alarms pane provides continuous alarm monitoring
regardless of the application currently selected.
The Configuration Application displays when you first open the web-based GUI. The
GE11xPro system view (located in the Details Pane) provides a physical representation
of the GE11xPro, its current provisioning configuration and alarm status.
Alarm details are displayed in the Alarms Pane. Refer to Figure 12 for an example of a
system entity selected in Configuration view and each component of the web browser
window.
Title Bar
The Title Bar displays the current application that has been selected from the Menu Bar,
Application menu or the Tool Bar.
Menu Bar
Each item on the Menu Bar provides a pull-down menu which contain the menu options
available in web-based GUI. Menu options are selected by pointing and clicking with the
mouse in the File or Application drop down menu and then clicking the mouse on the
desired option.
o Maintenance
o Performance Monitoring
o ESA
o CFM
o PTP (GE114Pro (SH)/GE114Pro (CSH) only)
o Sync Jack (GE114Pro (SH)/GE114Pro (CSH) only)
o SAT
o TWAMP
o OpenFlow
o ConnectGuard (GE114Pro (C)/GE114Pro (CSH) only)
o IPFIX
Tool Bar
The Tool Bar contains a set of tool buttons that can be selected for quick access to Web-
based GUI applications. The tool buttons available are:
Sync Jack (SJ) provides the means to monitor and measure the per-
formance and accuracy of Clock, PTP Clock and PTP Network by cal-
culating the relevant metrics and allows a high level of sync assurance.
This feature is only applicable in GE114Pro (SH)/GE114Pro (CSH)
products.
The applications available on the Tool Bar, may also be selected from the
Application pull-down menu on the Menu Bar. See Menu Bar.
Selection Tree
The Selection Tree (located at the left of the screen) enables the user to select an entity
in order to:
l display a status pane related to that entity (shown in the Details Pane to the right)
l select menu options related to that entity
The Selection Tree provides a hierarchical tree of the entities that make up an GE11xPro
system and the entities related to that system. Each Selection Tree entity is
representative of a specific entity type (NE, PSU, Network Port, Access Port, protection
group, communications, SNMP, administration, etc.).
Entities are arranged in hierarchical order, e.g., to gain access to an Access Port, the
System, NE-1 and GE11xPro menus must first be opened. Selection Tree nested items
are opened or closed by clicking on the + or - symbol next to the entity, respectively.
Once an entity is opened, the entity item is expanded, displaying nested items.
A “pointing hand” cursor (displayed when hovering the cursor over an entity within the
selection tree) indicates there are menu selectable items available for that entity, and if a
right mouse click is entered on that entity, applicable menu selectable items appear. See
Figure 13 for an example of a Selection Tree with menu selected. Menu selectable items
are bold and non-selectable items are grey. If an I-beam cursor is displayed, it indicates
there are no menu selectable items for that entity within the currently selected
application.
When an entity is selected within the Selection Tree, the corresponding entity status is
displayed in the Details Pane. The status displayed in the Details Pane is dependent
upon which application is currently selected. For example, if Configuration application is
selected, and a Access Port facility is selected in the Selection Tree, facility status
information such as assigned state, operational state and EVC mode status will be
displayed. If the same Access Port facility is selected in the Selection Tree while in
Maintenance view, the Details Pane will display Etherjack® diagnostics results and
alarm attributes.
Details Pane
When an item is selected from the Selection Tree with the left mouse button (see
Selection Tree), a status view related to that item is displayed in the Details Pane (to the
right of the Selection Tree). The details displayed are dependent upon the Application
currently selected.
If details are provided by more than one status pane, tabs are provided to toggle between
each pane. See Figure 14 for an example of tab selections in the Details Pane.
Figure 14: Tab Selections and Scroll Bars in the Details Pane
If data is too large to fit in the current Details Pane size, the browser window can be
resized or maximized to view a larger area, you can use the window resizing bars to open
the viewing area, or you can use the scroll bars located in the Details Pane to view the
remaining data (see Figure 14).
Right clicking on an entity in the Selection Tree Pane opens a window of available edits
for that entity selecting one of these yields an edit view in the Details Pane. See Figure
15 for an example of an Edit Access Port pane. Note that all valid provisioning options are
displayed in white and options that are not provisionable are grayed out (Media Type).
The operations and provisioning options in a Details Pane are displayed in a series of
fields. The information provided in the Details Pane enables the user to gain information
on the operation of the GE11xPro and to input and/or select data that is required for the
desired operation.
l Display only fields, which are provided to display status information. These fields are
grey and cannot be selected or changed.
l Provisionable fields, which have a white background, are used to indicate:
o a field that can be edited by direct data input
Command Buttons
Actions are selected via command buttons that are available at the bottom of the Details
Pane. The common Command Buttons available on a Details Pane are:
l OK, which accepts the information in a status pane and closes the pane.
l Cancel, which cancels any changes that have been made to the information in the
status pane and closes the pane.
l Refresh, which reads and displays the latest values of the fields in the status pane.
l Apply, which applies any changes made to the information in the status pane, without
closing the pane.
l Next>, which opens the next page (screen) of data.
l <Back, which opens the previous page (screen) of data.
Alarms Pane
The Alarms Pane provides quick visibility and access to current alarms.
l red; Critical
l orange; Major
l yellow; Minor
Each alarm is listed as a separate line item, with the following details:
l Interface type
l Notification Code
l Description
l Date/Time stamp
Keyboard Navigation
It is usual for the mouse to be used to navigate the Workspace and select menu options.
However, a number of keys on the PC keyboard can be used to navigate around the
Menu Bar, the Selection Tree Pane and the Details Pane as outlined in the table below.
Key Function
In the Web-based GUI Workspace:
Move through Workspace areas. This key enables the user to
Tab move through the Menu Bar, the Tool Bar, the Selection Tree Pane
and the Details Pane.
In the Menu Bar:
Select. This key enables the user to display a pull down menu and
Return
select a menu option.
Right arrow Move. These keys enable the user to move through the options on
Left arrow the Menu Bar to highlight the one required.
Up arrow Move. These keys enable the user to move up and down (scroll)
through menu options on a pull down menu to highlight the one
Down arrow required.
In the Selection Tree Pane:
Select. This key enables the user to select a highlighted item or
Return
menu option and open the appropriate pane in the Details Pane.
Up arrow
Move. These keys enable the user to move up and down (scroll)
Down arrow
through items and menu options to highlight the one required.
Tab
Open. This key enables the user to view nested items. If nested
Right arrow items are available it is indicated by a plus sign (+) to the left of that
item.
Close. This key enables the user to close a nest of items. A minus
Left arrow sign (-) to the left of an item indicates that the item’s nested items
are open.
In the Details Pane:
Select. This key enables the user to select a highlighted field for
Return
information input or a highlighted command button.
Right arrow Move through status pane tabs. This key enables the user to nav-
Left arrow igate through tabs at the top of the Details Pane.
Move through editable fields. This key enables the user to move
Tab down through the editable fields and the command buttons on a
status pane.
Up arrow Move through the options of a drop down list. This key enables
Down Arrow the user to move up or down through the items of a drop down list.
l Configuration
l Maintenance
l Performance Monitoring
l Etherjack Service Assurance
l Connectivity Fault Management
l PTP (GE114Pro (SH)/GE114Pro (CSH) only)
l Sync Jack (GE114Pro (SH)/GE114Pro (CSH) only)
l SAT
l TWAMP
l OpenFlow
l ConnectGuard (GE114Pro (C)/GE114Pro (CSH) only)
Each of the Applications can be selected from the Menu Bar (see Menu Bar) or the Tool
Bar (see Tool Bar). The Title Bar displays the latest application that has been selected
(see Title Bar).
Configuration View
Configuration view allows you to perform provisioning functions, and view provisioning
attributes of the entity that is selected in the Selection Tree or the entity Details Pane.
Left clicking an item in the Selection Tree displays current status and configuration in the
Details Pane. Right clicking an item in the Selection Tree displays a selection window for
editing configuration items for the selected entity. Selecting an editing option brings up an
edit view in the Details Pane. Alarm status is displayed in the Alarms Pane located at the
bottom of the screen, providing constant visibility and access to current alarms. Options
available are dependent upon the user access permission level and the current entity
status.
The following configuration changes can be applied and current status can be viewed
within Configuration View:
System
System level settings can be viewed by selecting the System entity in the selection tree.
Additional system level settings may be viewed by selecting one of the following tabs:
Identification, Security Log, Alarm Log, Audit Log, Syslog, ACL (Access Control List),
LLDP (Link Layer Discovery Protocol), Banner, Time Zone, System Time of Day or Data
Export. You can edit system options by entering a right click on the System entity and
selecting the desired menu option. System Defaults may also be restored at this menu
level.
NE level settings can be viewed by selecting the NE-1 entity in the selection tree.
Expanding the NE-1 entity reveals all equipment associated with the NE and the
provisionable features, i.e., VRF, DHCP Delay Agent, EoMPLS PW and BFD.
By expanding the NE-1 entity under the System entity, selecting the NTE11xPRO entity
and then selecting the Resources tab of the NTE11xPRO entity, all allocated and
available system traffic resources are displayed (see Figure 16).
Network Port, Access Port, DCN and PSU provisioning may be performed within the
NE-1 hierarchy in the selection tree.
PT Flows
By expanding the Protection Groups entity and selecting the Flow entity, the
configuration of a specific PT flow can be viewed on the Details Pane by double-clicking
on the row where it locates in the PT flow entity list. Entering a right click allows editing,
deleting and viewing configuration as well.
Protection Groups
By expanding the Protection Groups entity, the NE-1 entity and selecting the NTE11x
entity, the protection group configuration can be viewed, and entering a right click allows
adding, editing and deleting of a protection group.
Alternatively, by selecting the ERP entity under the NE-1 entity, the ERP instance
configuration can be viewed, and entering a right click allows editing, deleting of an
instance or clearing the statistics of an instance.
LAG
By expanding the LAG entity, entering a right click on the NE-1 entity allows LAG
creation. By expanding the LAG and NE-1 entities, and selecting the LAG entity identifier,
port configuration and aggregation port statistics can be viewed. Entering a right click on
the LAG entity allows editing LAG, LAG port, PCP, Priority Mapping configurations,
clearing statistics or LAG deletion selections.
By expanding the LAG, NE-1, LAG entity identifier and Members entities, and selecting a
LAG Member entity, the Member configuration, statistics and LACP debug information
can be viewed - and entering a right click allows editing of LAG member port configuration
or clearing LACP statistics.
SHG
By expanding the SHG entity and selecting the NE-1 entity, the configuration of a
specific SHG entity can be viewed, and entering a right click allows editing, deleting,
viewing configuration, flushing FDB and viewing FDB entities.
By expanding the Synchronization entity, NE-1 entity, NTE114S entity and selecting the
SYNC-1-1-1-1/TIME CLOCK-1-1-1-1 entity, the configuration and status of the system
sync entity can be viewed. Entering a right click allows editing, adding/editing/deleting
sync reference. Expanding BITS-1 entity and selecting BITS-IN/BITS-OUT allows
viewing configuration; Entering a right click on either entity allows editing configuration.
Likewise, selecting CLK, PPS, TOD and GPS entities allows viewing configuration and
entering a right click on each entity allows editing configuration.
Profiles
By expanding Profiles and Priority Mapping Profile, a default priority mapping profile
PRIORITY MAP PROFILE-1 appears on the details pane. Entering a right click on the
map profile to view, edit or delete it. The system supports up to eight profiles. To add a
new profile, enter a right click on Priority Mapping Profile in the selection tree and select
Add Profile.
Communications
Static Routes, Static ARP Entries, IPv6 Static Routes, IPv6 Static Neighbor Entries,
IPv6 Static ProxyND Entries and Source Address Configuration are viewed by selecting
the Communications entity and selecting the associated tab. Static Routes, Static ARP,
IPv6 Static Routes, IPv6 Static Neighbor Entries and IPv6 Static ProxyND Entries may
be added or deleted, and Source Address Configuration may be edited by entering a right
click on the Communications entity.
SNMP
Administration
Users, Remote Authentication, Security Policy and Key Generation are viewed by
expanding the Administration entity and selecting the entity in the selection tree. These
entities are provisioned by expanding the Administration entity, entering a right click on
the desired entity in the selection tree and selecting the applicable menu option.
Maintenance View
Maintenance View allows performing maintenance functions, such as diagnostics,
loopbacks, setting up and running ECPA tests, raising and clearing test alarms, setting
and retrieving alarm attributes, rebooting, upgrading software, database backup and
restore, configuration file management, licensable software feature management,
operating and releasing ERP protection switch, and operating reference switch on sync
entity and clock.
When entering a right click on an entity in the Selection Tree, maintenance options are
available in menu form. The options available are dependent upon the user access
permission level and current entity status. Alarm status is displayed in the Alarms Pane
at the bottom of the screen, providing constant visibility and access to current alarms.
The current status is viewed and maintenance operations performed within Maintenance
View:
System
Selecting the System entity allows viewing of System Identification, Conditions List and
ECPA Streams. Entering a right click provides menu options for editing ECPA Streams.
Selecting the NE entity allows viewing of the conditions list associated with the NE.
Expanding the NE entity reveals all equipment associated with the NE. Entering a right
click on the NE-1 entity provides a menu option for performing a lamp test. The following
maintenance functions may be viewed/performed for the following entities when the NE
is expanded in the selection tree:
l NTE11xPRO
o NTE11xPRO - displays ECPA results and first frame data. Entering a right click
provides menu options for configuring and running ECPA tests, raising and clearing
test alarm, and rebooting the NTE11xPRO.
o Network ports - view operations status, diagnostic results and cable benchmarks.
Entering a right click provides menu options for performing Etherjack® Diagnostic
Tests, editing Cable Length Benchmarks, performing Loopbacks and
raising/clearing a test alarm.
o Access port - view operations status, diagnostic results and cable benchmarks.
Entering a right click provides menu options for performing Etherjack® Diagnostic
Tests, editing Cable Length Benchmarks, raising and clearing test alarm, and
performing Loopbacks.
Protection Groups
By expanding the Protection Groups entity, the NE-1 entity and selecting the
NTE11xPRO entity, the protection group configuration and current status is displayed. If
a protection group is configured, entering a right click on the entity allows protection
switch operation and release functions. The operations available are:
By selecting the ERP entities, the configuration is displayed. Entering a right click on an
ERP entity allows protection switch operation and release functions. The operations
available are:
l Forced
l Manual
l Ring Port 0
l Ring Port 1
LAG
By expanding the LAG entity and selecting the desired LAG entity identifier, the
operations status is displayed. If a LAG is configured, entering a right click on the entity
allows loopback operation and release functions.
Synchronization
By expanding the Synchronization entity, the NE-1 entity and selecting the SYNC entity,
the Configuration and Status tabs for SYNC are displayed. Entering a right click on the
entity allows switching Sync references. The operations available are:
l Forced Switch
l Manual Switch
l Lock Out
l Clear Wait To Restore
l Clear Lock Out
l Clear Switch
Communications
Selecting the Communications entity allows viewing of the Routing Table, ARP Table,
IPv6 Routing Table, IPv6 NDP Table, the results of the last ping command, and the
results of the last trace route command. Ping, Trace Route, Flush ARP Cache and Flush
NDP Cache options are available when a right click is entered on the Communications
entity.
By expanding the Environmental Alarms entity, four dry contact environmental alarm
inputs may be viewed by selecting the desired entity or provisioned by entering a right
click on the environmental alarm entity and selecting Edit. The dry contact alarm inputs
are programmable to specify the monitored condition and whether the alarm shall be
raised on contact close or open.
Alarm Attributes
By expanding the Alarm Attributes and selecting a listed entity the current alarm attribute
settings for that entity are displayed. Entering a right click on the entity allows editing the
alarm severity of each listed condition. The NE entities available are:
l Traffic IP Interface
l WIFI DONGLE
l VXLAN Tunnel End Point
l VXLAN Segment
Administration
Expanding the Administration entity reveals the Software, Database and Configuration
Files entities. The following maintenance functions are available:
A Conditions List is also present for the NE-1 entity (see Figure 19).
l Critical (CR)
l Major (MJ)
l Minor (MN)
l Not Alarmed (NA)
l Not Reported (NR)
Loopbacks
Entering a right click on a Network Port or Access Port under the NTE11xPRO entity, or
LAG entity under the LAG/NE-1 entity and selecting Loopbacks provides a Loopback
view. From this view, the Network Port, Access Port or LAG entity can be placed in the
Maintenance state, and a loopback can be performed.
See Figure 21 for an example of a loopback view. For loopback procedures, see Chapter
5, Etherjack/Syncjack Test Procedures and Performance Monitoring .
When using web-based GUI, to remove a loopback, click on the drop-down list for
Loopback Configuration and select “None”, then click on “OK”.
Etherjack® Diagnostics
Etherjack® Diagnostics enable the user to perform tests on the Ethernet facility and the
attached cable for a copper (non-SFP) port, in order to detect and isolate faults on:
This feature is accessed by right clicking on a copper Access Port under the
NTE11xPRO entity and selecting “Diagnostic Test”.
See Figure 22 for an example of an Etherjack® Diagnostic Test Result view. For
Etherjack® diagnostic procedures, see Chapter 5,Etherjack/Syncjack Test Procedures
and Performance Monitoring .
The capabilities of the Ethernet Cable Test (performed as part of Etherjack® Diagnostics)
can be enhanced by using Cable Length Benchmarking. See Cable Length Benchmarks).
Sync Jack
See SyncJack Testing - GE114Pro (SH)/GE114Pro (CSH).
Open Flow
See Provision OpenFlow.
ConnectGuard
See Provision ConnectGuard - GE114Pro (C)/GE114Pro (CSH).
IPFIX
See Provision IPFIX.
Introduction
This chapter contains system provisioning details for the FSP 150GE11xPro and
provides a recommended work flow for new installations. The procedures can also be
used for incorporating provisioning changes to existing systems. Additionally, this
chapter includes links to technical information and procedures elsewhere in the document
that are needed or helpful in successfully completing the installation and original
provisioning process.
Upgrade Software
Upgrading or changing the system software is a multi-step process:
l If the user wants to perform the individual actions on deployed systems at different
times, the three-step operation is the best choice because it allows a network upgrade
to be staged before taking effect.
l If the user's goal is to have the system running a new software load, the one-step
operation is the solution that combines transfer, installation and activation in one
operation.
Activation causes the NE to reset, which temporarily interrupts traffic and cancels all
active user sessions.
During the software upgrade process, it is desirable to know the status of the
upgrade. The GE11xPro provides standing conditions to supply this need. By
default, these conditions are set with a Notification Code of Not Reported
and thus are only visible by selecting the Maintenance Application System
view and selecting the Conditions List tab in the Details Pane.
If the user wants to see the status conditions dynamically while using the
Upgrade or Database detail views, edit the Notification Codes for SWDL and
Data Base Condition Types to Not Alarmed. This causes the conditions to
display in the Alarm Pane at the bottom of the GUI window (See Figure 3).
See for Software Download (SWDL) condition types.
The upgrade operation data is kept as local events in the Audit Log, which is
viewable from the System Details Pane in the Configuration View. Below is a
sample of these messages - this example indicates the activation is
scheduled for January 17, 2012 at 12:10, with the validation timer set for 1
hour.
The following procedure includes steps for performing the software upgrade process
using the web-based Element Management System (EMS). It is also possible to perform
this process using CLI. See the FSP 150GE11xPro Command Line Interface Reference
Guide for details. The following procedure also assumes that the user has configured the
NE with an IP address and connected the NE to a DCN or LAN. (See "Set Up the
GE11xPro DCN (eth0) Port Using the Serial Port " on page 461.)
1. Click on the Maintenance icon, or select “Maintenance” from the application drop-
down list.
4. Determine the File Transfer Method and enter the corresponding file transfer options
as required to access the proper image file (Web) or the file server (FTP/SCP/SFTP).
Then, select the activation mode (Activate Immediately or Schedule Activation). If
Schedule Activation is selected, enter the date and time activation should occur.
Enable Validation Timer and set the Time Out option if desired (see the same note and
warning below 14). See below figure.
Click on OK.
User may change the activation schedule settings by canceling the previous
scheduled activation first.
However, immediate activation is not allowed to be canceled and must be
completed with no interruption.
8. Enter the path to the proper image file (.img file extension) or use the “browse” button
to search for the file location and select it, then select “OK”.
The file transfer will begin, and a screen similar to Figure 6 displays.
9. Go to 12.
10. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
following figure. (The figure shows the SCP view, the FTP and SFTP file
transfer view is identical.)
11. Enter the data required in the screen to access the FTP or SCP server and begin the
file transfer process, and click on OK.
It is assumed that the user knows the IPv4/IPv6 address of the FTP, SFTP
or SCP server, has a valid user ID and password and knows the path and file
name of the software file to transfer.
The file transfer will begin and a screen similar to the following displays
12. When the “Status” changes from “In progress” to “Success”, right click on “Upgrade” in
the selection tree pane and select “Install”. The following screen displays:
Click OK, and the screen shows a progress bar similar to Figure 6.
13. When the install completes (when the “Status” changes from “In progress” to
“Success”), right click on “Upgrade” in the selection tree pane, then select “Activate”.
An Activate Upgrade screen displays, as shown in the following figure:
If Schedule Activation is selected, enter the date and time activation should
occur.
Enable and set the validation timer time out option if desired (see the following
note and warning).
While the Schedule Activation timer is running, users are not allowed to
perform any saving, creating, downloading or transferring operations
regarding Database, Configuration Files, Logs, Diagnostics Files, etc. Users
must perform “Cancel Previous Scheduled Activation” and then do desired
file or database related operations.
Failure to use the validation timer option can result in loss of contact with the
NE and interruption of customer traffic should the software or database
become corrupted during the upgrade process. The validation timer option
permits the NE to “roll back” to the previous software and database without
user intervention.
After selecting and setting the desired activation and validation settings, select
OK.
15. When activation occurs (now or when scheduled) the NE resets, and the web-based
GUI session is interrupted. After a few seconds the STA LED will begin to flash.
Wait for 2 or 3 minutes (or when the STA LED has finished flashing and
becomes solid green), then reconnect to the NE. Once logged back in, verify
that the NE is behaving normally.
If unable to login, the validation timer will eventually time out and the NE will
revert to the previous load, and after that NE reset, reconnection should be
possible. If the validation timer was not used, contact technical support.
The display is the Validate Upgrade view, shown in the following figure:
18. To accept the upgrade, ensure the radio button next to “Accept Upgrade” is selected.
To cancel the upgrade, ensure the radio button next to “Cancel Upgrade” is
selected.
Click on OK.
19. Click on “Upgrade” in the selection tree pane, then select “Activate”. An Activate
Upgrade screen displays, as shown in the following figure.
20. Select the “Cancel Previous Scheduled Activation” radio button and Click on OK.
21. Click on “Upgrade” in the selection tree pane, then select “Activate”. An Activate
Upgrade screen displays
22. Select Enable Validation Timer and set Time Out time. Click on OK.
l Serial Connection
l Set Up the GE11xPro DCN (eth0) Port Using the Serial Port or Set Up the USB
Modem Using the Serial Port (if no DCN) or Set up WiFi Connection via the Wifi
Dongle (if no DCN)
l Browser-based IP Connection
l Configure USB Modem Using the Web-based GUI
l Upgrade Software
l Provision System Options
l Provision NE-1 Common Units
l Provision Secure Access
l Provision SNMP Access
l Enable Software License
l Configure Flexible Port (Ethernet Port II)
l Provision Access Port Services
o Ethernet Private Line Service Provisioning
o Etherjack® Diagnostics
o Cable Length Benchmarks
Configure System
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Right click on “System” in the selection tree pane and select Edit System and the
following screen displays:
2. The user can change the system level CLI prompt prefix, set Provisioning Mode,
Management Traffic Bridging, Management Traffic Bridging Security, Proxy ARP,
Proxy NDP, IPv6 Forwarding, Date, Time, FTP, HTTP, HTTPS, SSL Cipher
Strength, SCP, Serial Port, Serial Port Auto Log Off, SFTP, SSH, Telnet,
Authentication Traps, CLI Security Prompt, DSCP, DSCP Value, Long IF Alias
Control, Reset Button and SNMP Engine ID. For information on these system options
see System Configuration.
The System identity information that is not available for editing on this screen
(Name, Description, Location, Contact), is the same identity information that
displays in the NE-1 view and is editable on the NE-1 “Edit Configuration”
display.
3. Check that the information entered in 2is what is desired and click on OK. The display
will change to reflect the entered data.
Configure Logs
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Right click on “System” in the selection tree pane and select Edit Security Log and the
following screen displays:
2. Select “Enabled” to include Security Log messages in the Syslog or “Disabled” to not
include Security Log messages in the Syslog and click on OK.
3. Right click on “System” in the selection tree pane and select Edit Alarm Log and the
following screen displays:
4. For Syslog, select “Enabled” to include Alarm Log messages in the Syslog or
“Disabled” to not include Alarm Log messages in the Syslog; for Local Logging, select
“Enabled” or “Disabled” to Enable or Disable sending Alarm messages to the local log
(Alarm Log tab) and click on OK.
5. Right click on “System” in the selection tree pane and select Edit Audit Log and the
following screen displays:
6. For Syslog, select “Enabled” to include Audit Log messages in the Syslog or
“Disabled” to not include Audit Log messages in the Syslog; for Local Logging, select
“Enabled” or “Disabled” to Enable or Disable sending Alarm messages to the local log
(Alarm Log tab) and click on OK.
7. Right click on “System” in the selection tree pane and select Edit Syslog and the
following screen displays:
9. Enter Syslog Server information (IPv4/IPv6 Address and Port) for up to 3 servers (the
default port number is 514) if Log Server Method is User Defined.
Click on OK.
Configure ACL
The Access Control List (ACL) allows the user to limit access to the NE via the DCN or
management tunnels to specific IP addresses or IP address ranges (subnetworks). Up to
ten entries can be made, and each entry can be individually enabled or disabled.
Enabling ACL filtering will “permit” the corresponding management traffic. Disabling the
ACL filtering will “deny” the corresponding management traffic. Enabled entries apply to
all management interfaces and may be provisioned for specific IP addresses, or an IP
address range (subnetwork).
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Right click on “System” in the selection tree pane and select Edit ACL and the
following screen displays:
2. The Access Control List contains 10 entries. Each entry consists of IP version and
corresponding IP data options; an IPv4 Address and network Mask are configurable if
IP Version is IPv4; an IPv6 address and Prefix are configurable if IP Version is IPv6.
Edit the Control status to Enable/Disable each entry.
3. Click on OK. The display will change to reflect the entered data.
Configure LLDP
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Right click on “System” in the selection tree pane and select Edit LLDP and the
following screen displays:
2. Enter the following data to configure system LLDP options (see Table 97 on p. 945 for
options and rules details):
1. Right click on “System” in the selection tree pane and select Edit Banner and the
following screen displays:
2. The Banner is displayed for each CLI or GUI login. The banner can be edited to contain
a customized message of up to 1024 characters. The default banner message is “This
is a private system. Unauthorized access or use may lead to prosecution.”
Edit the Banner, then click on OK and the screen will update to display the edited
banner message.
1. Right click on “System” in the selection tree pane and select Edit Time Zone.
Click on OK
1. Right click on “System” in the selection tree pane and select Edit System Time of
Day.
4. Select the drop down calendar for the Date and select the appropriate year, month and
day.
6. Select the System Time Of Day tab to view the local entry.
a) The Polling Interval can be set to 16, 32, 64, 128, 256, 512 or 1024
seconds. The default is 16 seconds.
Select OK.
2. Right click on System on the selection tree pane, select Data Export and Edit.
5. Right click on System on the selection tree pane, select Data Export and Clear
Statistics.
Configure NE-1
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Expand the System entity, right click on “NE-1” in the selection tree pane and select
Edit Configuration. The following screen displays:
After editing the NE information, click on OK. The display will update to show
the edited information.
Click on OK.
Configure NTE11xPRO
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application menu. Expand the system and NE-1 by clicking the “+” sign next to each
entity.
2. Right click on “NTE11xPRO” in the selection tree pane and select Edit Configuration.
After editing the NTE11x information, click on OK. The display will update to
show the edited information.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application menu. Expand the system and NE-1 by clicking the “+” sign next to each
entity.
2. Right click on “PSU-1” in the selection tree pane and select Edit Configuration
After editing the PSU information, click on OK. The display updates.
Provision PSE
Refer to the following for provisioning a PSE service on a GO102Pro (SP). Power-
Supplying Equipment (PSE) feature is configured on Group level and port level. The DC
variant of GO102Pro (S) can work as a PD device.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System in the selection tree pane, by clicking on the “+”
signs next to it to expand the view.
2. Under System Right Click the PSE Node in the Selection tree, and select Edit
Configuration from the pop-up menu.
5. Select from the drop-down menu to Enable or Disable the Non-Standard Powered
Devices (PD).
1. Make sure the Access Port is in Copper mode. For more information about media
type, see Ethernet Private Line Service Provisioning.
2. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu.
3. Expand System and PSE in the selection tree pane, by clicking on the “+” signs next
to it to expand the view.
4. Under PSE, right Click the desired Port in the tree and select Edit Configuration from
the pop-up menu.
7. (Optional) Enter a description in the PSE Port Type text box. Usually, it is used to
indicate the type of Powered Device connected to this port.
8. Select an Power Level form on the Available Power Level Drop-down Menu.
Changing the security keys may interrupt any current secure sessions that
have used the existing keys for authentication.
1. Left click on “Key Generation” in the selection tree pane and the following screen
displays to show the current SSL Certificate and SSH Key information:
2. To regenerate the SSL Certificate or SSH Key, right click on “Key Generation” in the
selection tree pane and select Regenerate Keys and the following screen displays
(see Figure 34):
3. To regenerate the SSL Certificate, select the “Regenerate SSL Certificate radio
button, click OK for the message pop-up and the following screen displays (see Figure
34):
When an SSL Certificate is generated, the HTTP server will be restarted and
web access will be unavailable during this time (approximately 15 seconds).
5. To regenerate the SSH Key, select the radio button next to “Regenerate SSH Key”,
click OK on the message pop-up and the following screen displays:
When an SSH Key is generated, all SSH users will be logged off.
6. Click on OK.
1. Right click on “Security Policy” in the selection tree pane and select Edit Policy, and
the following screen displays to show the current Policy Strength setting and a
description of the policy rules:
2. To change the Policy Strength, select the desired setting from the Strength drop-down
list, then click on OK.
1. Select Configuration icon or select Configuration from the Applications menu, then
expand the System, Administration, Users and Local entities, by clicking on the “+”
signs next to each entity.
Entering a new user can only be done by a user with superuser privilege.
3. Right click on “Local” in the selection tree pane and select Add User and the following
screen displays:
4. Enter the required data to establish a new user. Details on the function and rules for
each data entry is located at Administration.
After editing the user information, click on OK. The display will update to show
the edited information.
Editing non-crypto user data other than the user’s own password can only be
done by a user with superuser privilege.
5. Right click on the user name to be edited in the selection tree pane and select Edit
User and the following screen displays:
6. Edit the required data for this user. Details on the function and rules for each data entry
is located at Administration.
After editing the user information, click on OK. The display will update to show
the edited information.
Editing the user password can be done by the user or a user with superuser
privilege.
7. Right click on the user name to be edited in the selection tree pane and select Edit
Password and the following screen displays:
8. Edit the password for this user. Details on the function and rules for each data entry is
located at Administration.
After editing the password, click on OK. The display will update to show the
edited information.
9. Right click on the User Name to be deleted, select Delete User, and the following
screen displays:
10. Verify that the selected user is the one to be deleted. Click on OK. The display will
update to show the deleted information.
11. Right click on the User Name that is locked, select Remove Lock, and the following
screen displays:
12. Verify that the selected user is the one from whom the lock-out is to be removed. Click
on OK. The display updates.
The following procedure applies to the configuration of the local crypto user
who is the user with Crypto privilege and is only available in GE114Pro
(C)/GE114Pro (CSH). Currently, only one crypto user is supported per
system.
For more provisioning privilege information of the crypto user, see Provision
ConnectGuard - GE114Pro (C)/GE114Pro (CSH).
1. Select Configuration icon or select Configuration from the Applications menu, then
expand the System, Administration, Users and Local entities, by clicking on the “+”
signs next to each entity.
Editing the crypto user data and login password can be done by a user with
either Superuser privilege or Crypto privilege.
The user logged on with the Crypto privilege can only see one local user
“crypto” (see on p. 136).
The crypto user can edit user information, login password and crypto
password.
Crypto user’s crypto password can only be edited by the crypto user.
3. Right click on “crypto” in the selection tree pane and select Edit User.
4. Edit the required data for the crypto user. Details on function and rules for each data
entry is located at Administration.
After editing the user information, click on OK. The display will update to show
the edited information.
5. Right click on “crypto” in the selection tree pane and select Edit Password.
Figure 44: Edit Crypto User’s Password (Login with Superuser Privilege)
The user with Superuser privilege can change the login password of the
crypto user, which can cause the crypto user’s crypto password to be
cleared, so that the crypto user must reset new crypto password at next
login.
For more information about crypto user login, see Logging On.
Figure 45: Edit Crypto User’s Password (Login with Crypto Privilege)
6. Enter the old password and new password as required. Details on the function and
rules for each data entry is located at Administration.
If the login user is the crypto user, it is also required to enter the old login
password besides the new login password.
7. Right click on “crypto” in the selection tree pane and select Edit Crypto Password.
The crypto user’s crypto password conform to the security policy of High
strength (see Configure Security Policy).
The crypto password is stored in SRAM. Every time after the provisioning
operation which must only be performed by the crypto user, the crypto user is
required to enter the crypto password to verify if the password input is the
same as the one stored in SRAM.
The crypto password input is required in ConnecGuard provisioning (see
Provision ConnectGuard - GE114Pro (C)/GE114Pro (CSH)).
The crypto password can be set at first-time login (see Logging On).
Crypto user’s crypto password can only be edited by the crypto user.
If the user is using Internet Explorer 10, an “eye” icon will show by the crypto
password entry allowing the user to click to display the password details.
9. Click on OK.
10. Enter the new crypto password that was just set and click on OK.
Instead of hiding the crypto password using black dots, user may click on the
“Show password” checkbox as an option to make the password components
visible, e.g., gui_12345678#ADVA.
11. Right click on “crypto” in selection tree pane and select “Remove Lock”.
Only the use with Superuser privilege can remove the lock for any user
account.
1. Expand the System and Administration entities in the selection tree pane, by clicking
on the “+” signs next to each entity to expand each view.
2. Right click on “Remote Authentication” in the selection tree pane and select Edit
Remote Authentication and the following screen displays:
3. Enter the required data for the Remote Authentication Protocol System Level
Configuration including Authentication Protocol, Authentication Type, TACACS
Privilege Control, TACACS Default Privilege, NAS IP Address (RADIUS only),
Accounting, and Access Order. Details on the function and rules for each entry is
located at Administration and User Management and Security and in FSP 150-
GE11xPro System Description document.
4. Enter the required data for each Remote Authentication Server (1, 2 and 3) including
Server Status, Priority, IP Address, Server Secret, Port, Accounting Port, Timeout
and Retries. Details on the function and rules for each entry is located at
Administration and User Management and Security and in FSP 150-GE11xPro
System Description document.
References for SNMP configuration settings may be found in SNMP and SNMP Support
in FSP 150-GE11xPro System Description document.
Vxlan, supported in all GE11xPro products, GE101Pro and GO102Pro, enable or disable
the Virtual eXtensible Local Area Network (VXLAN) feature. By default, this license is
Disabled.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application Menu. Expand the System, Administration and Software Licensing
entities in the selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
3. Select Enabled from the Status drop-down list associated with the desired feature.
o Protection group
o LAG
o Management tunnel
o Flow (When the port is in EVPL mode)
o ERP
o SHG
1. Ensure that no other entities are associated with Port 2 (1+1 protection, LAG,
management tunnel, flow, etc.), otherwise, delete them first.
2. Select Configuration view. Expand the System, NE-1, NTE entities in the Selection
Tree, by clicking on the “+” signs next to each entity.
3. Enter a right click on the Port 2 (E1000-N-2 or E1000-A-2) entity and select “Switch to
ACC” (or “Switch to NET”).
4. Select OK.
5. Select OK.
6. After approximately 2 minutes a login screen appears. Log back onto the system.
GE112Pro (m) - Two Fiber Access interfaces that may be configured for optical,
wherein Port 3 is optical only and Port 4 has separate interfaces for copper and
[Link] GE112Pro (m) is a version of the product that does not include Sync-E
capability, PTP, SyncJackTM and ConnectGuardTM functionalities.
Refer to Access Port Configuration Options and Rules to determine the default values,
value ranges and rules for each option in the following procedure. For Control Data
Protocol provisioning, see CPD Filters Options and Rules.
1. Observe the current Service Type. The status will be used in the following steps.
2. Right click on the Access Port facility and select Edit Configuration.
4. If not already in the unassigned state, set the Administrative State to Unassigned and
click on Apply.
Click on OK.
5. Enter a right click on the Access Port facility and select Edit Configuration.
Identification
8. Enter a right click on the Flow EID and select Edit Configuration.
Figure 56: Select Edit Configuration from Flow Entity Configuration List
9. Enter the EPL Flow facility changes: (see Access Port Configuration Options and
Rules for details and rules).
Connection
Learning Attributes
l) Set the Interface Learning Control, Protected Learning Control and Max
Forwarding Table Entries for Network Port and Access Port respectively.
s) The following A2N Policer Settings are editable: CIR, EIR, CBS, EBS,
CM, CF. Information regarding each item (full name and entry type) is
available by placing the cursor on the item heading. Edit the desired items
by clicking in the box under the item name.
t) Enter A2N Shaper Settings: BS, SOAM-CIR and SOAM-EIR. If Port-
based A2N shaping is used, it is entered in the A2N Shaper page of the
selected Network Port. If Flow-based A2N shaping is used, it is entered in
the A2N Setting box of the flow. Enter A2N Shaper SOAM-CIR and
SOAM-EIR to allocate bandwidth resource to the SOAM service on this
flow. Enter the MIN Threshold %, MAX Threshold %, Maximum Drop
Probability % for WRED In-Profile and WRED Out of Profile traffic for the
Shaper.
u) If Independent N2A Rating Limiting is enabled, enter N2A Policer settings
(CIR, EIR, CBS, EBS, CM, CF) and N2A Shaper settings (BS).
When a flow is added or the CBS is increased, the system will ensure
that the N2A and A2N queue BS is at least as large as the sum of
CBSs for all flows’ policers towards that queue by automatically
adjusting the BS to the sum of CBS.
However, when a flow is deleted or the CBS is decreased, the system
will not decrease the BS value accordingly.
Click on OK.
10. Enter a right click on the Flow EID and select Add Forwarding Table Entry.
a) Specify the Destination Address and select a Destination Port from the
drop-down list.
b) Select the desired Learning Action.
Click on OK.
c) Enter a right click on the Flow EID and select View FDB Entries to view
the existing Forwarding Table Entries.
d) Enter a right click on one FDB entry and select the desired operations
from the menu: View Configuration, Edit Configuration or Delete FDB
Entry.
11. Enter a right click on the EPL Flow EID and select the desired operations from the
menu: Flush FDB, or Clear Blocked State.
12. Enter a right click on the EPL Flow EID and select Create A2N ACL Rule.
Figure 61: Create A2N ACL Rule for Access Port Flow
13. Enter or select the following data to configure the ACL Rule:
Identification
e) Select relevant check boxes for Src Addr and/or Dest Addr, and if
selected, enter the corresponding Address and Mask.
If Rule Action is set to Accept, the system will forbid the user to edit
the Destination Address.
EtherType
f) Select the check box for EtherType Control and if selected enter the
EtherType.
Outer VLAN Tag
g) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
h) Select the check box for DEI and enter the DEI value.
Inner VLAN Tag
i) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
IP
j) Select the Src Addr check box, and if selected, select the Dynamic check
box as desired or directly enter IP addresses for Low Limit and High Limit.
k) Similarly, select the relevant check boxes for Dest Addr and Priority, and
if selected, enter Low Limit and High Limit.
Protocol
l) Select the check box for Control and the Protocol Number will change to
align with the selected Protocol type. If CUSTOM is selected, enter a
custom number.
m) Select the relevant check boxes for Src Port and/or Dst Port, and if
selected, enter Low Limit and High Limit.
n) Select the check box for TCP Flags Control, and if selected, enter TCP
Flags.
Click on OK.
14. Enter a right click on the EPL Flow EID and select Create N2A ACL Rule. The
provisioning options are same as “Create A2N ACL Rule”. Refer to 13.
15. Enter a right click on the EPL Flow EID and select View A2N ACL Rule or View N2A
ACL Rule.
16. Enter a right click on the Access Port facility and select Edit CPD Filters.
Only the ten L2PT function protocols ([Link], STP(BPDU), CDP, VTP,
UDLD, DTP, PVSTP+, LACP, LAMP and PAgP) support “Pass Thru L2PT”
disposition on Access Port CPD. Network Port, logical port and flows do not
support L2PT CPD.(See Layer 2 Protocol Tunneling in FSP 150-GE11xPro
System Description document.)
If LAG is used for the Network Ports, the Bridge Group LACP and LACP
Marker protocols for all Access Ports must be set to Discard. The default is
Pass Thru.
c) Click on OK.
18. Enter a right click on the Access Port facility and select Edit EFM-OAM.
Click on OK.
20. Enter a right click on the Access Port facility and select Edit N2A Shapers.
21. Edit the N2A Shaper QID BS, SOAM-CIR, SOAM-EIR setting as desired.
When a flow is added or the CBS is increased, the system will ensure
that the N2A and A2N queue BS is at least as large as the sum of
CBSs for all flows’ policers towards that queue by automatically
adjusting the BS to the sum of CBS.
However, when a flow is deleted or the CBS is decreased, the system
will not decrease the BS value accordingly.
Click on OK.
22. Enter a right click on the Access Port facility and select Edit E-LMI.
23. Edit the State and Configuration options as desired and select OK.
24. Select the E-LMI lab to view E-LMI configuration details and status.
If ELMI is enabled and working, the Messages and Statistics data should
indicate messages have been received and sent, and the EVC Status
should indicate that it is in the Active State
25. Enter a right click on the Access Port facility and select Edit Configuration.
Click on OK.
27. For PCP, PTP, Sync-E, LLDP, LAG and/or SHG provisioning, refer to the following
notes:
The GE11xPro supports SHG on Access Ports. SHG and LAG cannot
both be provisioned on the same Access Ports. Use the above steps
to provision the other Access Ports to be present on the SHG. For
SHG provisioning procedure, see Provision Ports in a Split Horizon
Group (SHG).
28. Repeat the above steps for EPL services on other Ethernet Ports on the system. Also
repeat these steps for creating the appropriate flow(s) supporting a Transparent Clock
or Telecom Slave, as required.
29. Configure all intermediate devices appropriately for carrying traffic from this GE11xPro
to the far end GE11xPro.
30. Repeat above steps for each EPL service to be created at the far end GE11xPro.
It is recommended that you pre-determine the provisioning details and ensure that they
meet the GE11xPro’s provisioning rules prior to making changes to an existing service or
placing an additional Access Port into service. Ensure that CIR, EIR and C-Tag/S-Tag
VLAN ID-Priority values will not conflict with another Access Port/Flow that is in the
Assigned state.
Refer to Access Port Configuration Options and Rules to determine the default values,
value ranges and rules for each option in the following procedure. For Control Data
Protocol provisioning, see CPD Filters Options and Rules.
1. Observe the current Service Type. The status will be used in the following steps.
2. Enter a right click on the Access Port facility and select Edit Configuration.
4. If not already in the unassigned state, set the Administrative State to Unassigned and
click on Apply.
Click on OK.
5. Enter a right click on the Access Port facility and select Edit Configuration.
Identification
aa) Select the desired destination MAC address types. By default, the
Nearest Bridge is selected. System will create a separate tab in the Edit
LLDP Details Pane for the port.
Click on OK.
7. Enter a right click on the Access Port facility and select Edit CPD Filters.
8. Change the default Tunnel MAC as desired. Select Discard, Pass Thru, Pass Thru
L2PT or Use MAC Setting for each protocol or group as desired.
Only the ten L2PT function protocols (i.e. LLDP, STP(BPDU), CDP,
VTP, UDLD, DTP, PVSTP+, LACP, LAMP and PAgP) support “Pass
Thru L2PT” disposition on Access Port CPD. Network Port, logical
port and flows do not support L2PT CPD.(See Layer 2 Protocol
Tunneling in FSP 150-GE11xPro System Description document)
If LAG is used for the Network Ports, the Bridge Group LACP and
LACP Marker protocols must be set to Discard for all Access Ports.
The default is Pass Thru.
Click on OK.
9. Enter a right click on the Access Port facility and select Edit EFM-OAM.
Click on OK.
A Flow entity configuration list displays, showing a list of the existing flows
12. Right click on the Flow entity under the Access Port and select Create Flow.
13. Enter the EVPL Flow attributes: (see EVPL Service Provisioning Rules for details and
rules)
Identification
v) Set the Interface Learning Control, Protected Learning Control and Max
Forwarding Table Entries for Network Port and Access Port respectively.
ae) If Multi-COS is Disabled: The following A2N Policer Settings are editable:
CIR, EIR, CBS, EBS, AlGO,CM, CF, Envelope. Information regarding
each item (full name and entry type) is available by placing the cursor on
the item heading. Edit the desired items by clicking in the box under the
item name.
af) If Multi-COS is Enabled (see Figure 74): There are Policer and Shaper
entries for each COS. Select the COS values desired by clicking in the
“Active” box. For each box selected, the following A2N Policer Settings
are editable: CIR, EIR, CBS, EBS, CM, CF, Envelope, and QID.
Information regarding each item (full name and entry type) is available by
placing the cursor on the item heading. Edit the desired items by clicking
in the box under the item name.
ag) If Flow-based A2N Shaping, enter A2N Shaper settings: BS, SOAM-CIR,
SOAM-EIR. If A2N Shaping is set to Port-Based, these entires are
entered in the A2N Shaper page of the selected Network Port. If A2N
Shaping is set to Flow-Based, these entires are entered in the A2N
Setting box of the EVC. If Multi-COS is Enabled, the Shapers whose
QIDs match to the Active Policers are editable. Enter A2N Shaper SOAM-
CIR and SOAM-EIR to allocate bandwidth resource to the SOAM service
on this flow. Enter the MIN Threshold%, MAX Threshold%, Maximum
Drop Probability% for WRED In-Profile and WRED Out of Profile traffic
for Shaper. If Multi COS is Enabled, edit the above entries for each
desired COS and select/deselect the check box for Hierarchical COS
Settings. If Hierarchical COS Settings are selected, enter the Guaranteed
Bandwidth and Maximum Bandwidth.
A2N Shaper QID BS settings are editable if the QID of the associated
Policer ID is changed.
N2A Settings
ah) Enter N2A Policer settings (CIR, EIR, CBS, EBS, CM, CF) if N2A Rate
Limiting is Enabled. If Multi-COS is Enabled, select the desired Policers
ai) Enter a desired VLAN ID (or range) and Priority, then click on “Add”.
Repeat for each additional VLAN entry.
Click on OK.
The Administrative State of a flow can only be changed when the port
is not in the Unassigned state.
14. Expand the Access Port facility entity and select the newly created flow to verify the
entry.
16. Enter a right click on an EVPL flow facility and select Add Forwarding Table Entry.
a) Specify the Destination Address and select a Destination Port from the
drop-down list.
b) Select the desired Learning Action.
Click on OK.
c) Select the FDB tab to view the existing Forwarding Table Entries.
d) Enter a right click on one FDB entry and select the desired operations
from the menu: View Configuration, Edit Configuration or Delete FDB
Entry.
17. Enter a right click on the EVPL flow facility and select the desired operations from the
menu: Flush FDB, or Clear Blocked State.
18. Enter a right click on the EVPL Flow EID and select Create A2N ACL Rule.
Figure 78: Create A2N ACL Rule for Access Port Flow
19. Enter or select the following data to configure the ACL Rule:
Identification
e) Select relevant check boxes for Src Addr and/or Dest Addr, and if
selected, enter the corresponding Address and Mask.
If Rule Action is set to Accept, the system will forbid the user to edit
the Destination Address.
EtherType
f)Select the check box for EtherType Control and if selected enter the
EtherType.
Outer VLAN Tag
g) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
h) Select the check box for DEI and enter the DEI value.
Inner VLAN Tag
i) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
IP
j)Select the Src Addr check box, and if selected, select the Dynamic check
box as desired or directly enter IP addresses for Low Limit and High Limit.
k) Similarly, select the relevant check boxes for Dest Addr and Priority, and
if selected, enter Low Limit and High Limit.
Protocol
l) Select the check box for Control and the Protocol Number will change to
align with the selected Protocol type. If CUSTOM is selected, enter a
custom number.
m) Select the relevant check boxes for Src Port and/or Dst Port, and if
selected, enter Low Limit and High Limit.
n) Select the check box for TCP Flags Control, and if selected, enter TCP
Flags.
Click on OK.
20. Enter a right click on the EPL Flow EID and select Create N2A ACL Rule. The
provisioning options are same as “Create A2N ACL Rule”. Refer to 13.
21. Enter a right click on the EPL Flow EID and select View A2N ACL Rule or View N2A
ACL Rule.
22. Enter a right click on the Access Port facility and select Edit N2A Shapers.
23. Edit each N2A Shaper QID BS, SOAM-CIR, SOAM-EIR setting as desired.
When a flow is added or the CBS is increased, the system will ensure
that the N2A and A2N queue BS is at least as large as the sum of
CBSs for all flows’ policers towards that queue by automatically
adjusting the BS to the sum of CBS.
However, when a flow is deleted or the CBS is decreased, the system
will not decrease the BS value accordingly.
Click on OK.
24. Enter a right click on the Access Port facility and select Edit E-LMI.
25. Edit the State and Configuration options as desired and select OK.
26. Select the E-LMI lab to view E-LMI configuration details and status.
If ELMI is enabled and working, the Messages and Statistics data should
indicate messages have been received and sent, and the EVC Status
should indicate that it is in the Active State
27. Enter a right click on the Access Port facility and select Edit Configuration.
Click on OK.
29. For PCP, PTP, Sync-E, LLDP, LAG and/or SHG provisioning, refer to the following
notes:
The GE11xPro supports SHG on Access Ports. SHG and LAG cannot
both be provisioned on the same Access Ports. Use the above steps
to provision the other Access Ports to be present on the SHG. For
SHG provisioning procedure, see Provision Ports in a Split Horizon
Group (SHG).
30. Repeat the above steps for EVPL services on other Ethernet Ports on the system.
Also repeat these steps for creating the appropriate flow(s) supporting a Transparent
Clock or Telecom Slave, as required.
31. Configure all intermediate devices appropriately for carrying traffic from this GE11xPro
to the far end GE11xPro.
32. Repeat above steps for each EVPL service to be created at the far end GE11xPro.
It is also assumed that the user is logged on to the web-based GUI with the proper
privilege level for provisioning (see User Authorization Privilege Levels) and is in the
configuration view.
Use one of the following procedures for configuring the Network Port(s). A port cannot be
configured for both LAG and Protection Group.
2. If a “+” sign appears next to NE-1 in the selection tree pane under “System”, click on it
to expand the NE view, then click on the “+” sign next to NTE11x to expand it.
3. Right click on E1000-N-1 interface in the selection tree pane and select Edit
Configuration and the following screen displays:
Various Port, Service and LLF data can be edited. For details on each editable
item see Network Port Configuration Options and Rules.
After editing the interface information, click on OK. The display will update to
show the edited information.
5. Right click on the E1000-N-1 interface and select “Edit EFM OAM” and the details
pane displays:
6. The OAM State and Local Configuration Mode can be edited. After selecting the
desired settings, click on OK.
7. Right click on E1000-N-1 interface in the selection tree pane and select Edit CPD
Filters and the following screen displays:
8. If LAG is (or will be) also configured on Access Ports, then Bridge Group Protocols
“LACP” and “LACP Marker” must be set to “Discard” on the Network Port.
Click on OK.
9. Enter a right click on the Network Port facility and select Edit E-LMI.
10. Edit the State and Configuration options as desired and select OK.
11. Select the E-LMI lab to view E-LMI configuration details and status.
If ELMI is enabled and working, the Messages and Statistics data should
indicate messages have been received and sent, and the EVC Status
should indicate that it is in the Active State
12. For PCP, PTP, Sync-E, LLDP, LAG and/or SHG provisioning, refer to the following
notes:
2. Scroll down the selection tree to “Protection Groups” and click on the “+” sign next to it
to expand it.
4. Right click on NTE11x and select “Add Protection Group” and the following screen
displays:
Click on OK.
The E1000-N-2 interface is placed in service (IS) - the LK and RT LEDs indicate
activity if the fiber is connected. (See Entity State Descriptions).l
6. If a “+” sign appears next to NE-1 in the selection tree pane under “System”, click on it
to expand the NE view, then click on the “+” sign next to NTE11x to expand it.
7. Right click on E1000-N-1 interface in the selection tree pane and select Edit
Configuration and the following screen displays:
Various Port, Service and LLF data can be edited. For details on each editable
item, see Network Port Configuration Options and Rules.
After editing the interface information, click on OK. The display will update to
show the edited information.
9. Right click on the E1000-N-1 interface and select “Edit EFM OAM” and the details
pane displays:
10. The OAM State and Local Configuration Mode can be edited. After selecting the
desired settings, click on OK.
11. If 1+1 or Dual Active Receive protection has been configured, repeat 7 through 10 for
E1000-N-2.
12. Right click on E1000-N-1 interface in the selection tree pane and select Edit CPD
Filters and the following screen displays:
If LAG is (or will be) configured on Access Ports, then Bridge Group Protocols
“LACP” and “LACP Marker” must be set to “Discard” on the Network Port. All
other CPD Filter setting should be set as desired.
Click on OK.
4. Right click on E1000-N-1 (or first Access Port) interface in the selection tree pane and
select Edit Configuration and the following screen displays:
Click on OK.
6. Right click on the E1000-N-1 (or first Access Port) interface and select “Edit EFM
OAM” and the details pane displays:
7. The OAM State and Local Configuration Mode can be edited. After selecting the
desired settings, click on OK.
8. Right click on E1000-N-1 (or an Access Port) interface in the selection tree pane and
select Edit CPD Filters and the following screen displays:
For Access Ports: If LAG is (or will be) also configured on Access Ports, then
Bridge Group Protocols “LACP” and “LACP Marker” must be set to “Discard” on
the Network Port. All other CPD Filter setting should be set as desired.
Click on OK.
10. Select LAG and click on the “+” sign to expand it.
11. Right click on NE-1 and select “Create LAG” and the following screen is displayed.
If the Frame Dist Algorithm is Field Hash, Select Fields to be used in Hash
calculation.
Select “NETWORK PORT-1-1-1-1” (or first Access Port) for Members Entry and
click on “Add” (the first entry in the Network Port Members list must be Network
Port 1)
Select “NETWORK PORT-1-1-1-2” (or second Access Port) for Members Entry
and click on “Add”
Click on “OK”
LAG includes support for Link Aggregation Control Protocol (LACP) that
is a control protocol that automatically detects links between two LACP-
enabled devices and configures the links into a LAG.
Group. Refer to the table content SHG to determine the default values, value ranges and
rules for each option in the following procedure.
2. Enter a right click on NE-1 and select Create SHG and the following screen displays:
3. Select the desired SHG index and enter the desired Alias.
4. Select the first Port Member entry and select Add. Repeat for other ports on the SHG.
(To delete a member from the list, select the entity in the Members list and select
Delete.)
Click on OK.
5. The new SHG appears in the SHG Configuration entity list of the Details Pane.
6. Enter a right click on the new SHG entity in the details pane and select View
Configuration to verify provisioning entry.
7. To edit an SHG, enter a right click on a desired SHG entity in the Details Pane and
select Edit Configuration. To delete an existing SHG, enter a right click on the desired
SHG entity in the Details Pane and select Delete.
9. Verify end-to-end connectivity for the SHG services. To view Forwarding Database
entries, enter a right click on the desired SHG entity in the Details Pane and select
View FDB Entries. To flush all the FDB entries, enter a right click on the desired SHG
entity in the Details Pane and select Flush FDB.
1. Expand System in the Selection Tree, scroll down the selection tree to “Protection
Grps” and click on the “+” sign next to it to expand it.
3. Right click on NE-1 and select “Create ERP” and the following screen displays:
There can be only one RPL owner in a ring. A ring node configured
as the RPL-Owner link in a G.8032 Ring should be configured with
the largest Node ID of all the nodes in the ring. A non-owner node
configured as the highest priority ring node may result in
temporary ring segmentation for cases of simultaneous reboots of
multiple ring nodes. In this case, temporary ring segmentation
time is limited to the configured value of the RPL Owner Wait-to-
Restore.
i) Click on OK.
The ERP configuration displays
5. Select the Configuration tab to verify ERP configuration details. If changes are
required, enter a right click on the ERP entity in the Selection Tree Pane and select
Edit.
7. Expand the PT Flows entity in the Selection Tree Pane, enter a right click on Flow and
select Create Flow.
8. Enter the Pass-through Flow details: (see Pass-Through Flow Configuration Options
and Rules for details and rules)
Identification
l) Enter the desired Auto CIR Bandwidth Percentage (if Auto Bandwidth is
enabled)
m) If Multi COS is Disabled: the following N2N Policer Settings are editable:
CIR, EIR, CBS, EBS, CM and CF; BS is editable for N2N Shaper
Settings (if Shaping Type is Flow Based). Information regarding each item
(full name and entry type) is available by placing the cursor on the item
heading. Edit the desired item by clicking in the box under the item name.
n) If Multi COS is Enabled: There are Policer and Shaper entries for each
COS. Select the desired COS by clicking in the Active box. For each box
selected, the following N2N Policer Settings are editable: CIR, EIR, CBS,
EBS, CM, TF and QID. Information regarding each item (full name and
entry type) is available by placing the cursor on the item heading. Edit the
desired items by clicking in the box under the item name.
p) Enter a desired VLAN ID (or range) and Priority; then click on Add. Repeat
for each additional VLAN entry.
Click on OK.
10. Right click on the pass-through flow entity ID and select View Configuration.
11. Verify the Pass-through flow entry. If changes are required, select the configuration
tab, enter a right click on the Pass-through Flow Entity ID and click Edit Configuration.
12. Repeat 7 through 11 for each additional Pass-through Flow for this node.
14. Enter a right click on the ERP entity in the Selection Tree Pane and select Edit. The
following screen displays.
15. Select the desired MEP for Ring Port 0 and Ring Port1. Then click on OK.
17. Expand the System, Protection Groups, NE-1 entities in the Selection Tree.
18. Select the ERP entity and the RAPS Status tab to view the RAPS status:
19. Observe the Node State. Refer to the following table describing the three Node
States.
20. If the Node State is not the expected result, troubleshoot and rectify the trouble
accordingly. Select the Statistics Tab to view ERP Statistics to observe transmission
and receive statistics. See the following figure and table:
22. Select the Maintenance application. Expand the Protection Groups and NE-1 entities
in the Selection Tree Pane. Enter a right click on the ERP entity and select Operate
Protection Switch.
23. Select Protection Switch Action of Manual and select the desired Blocking Ring Port.
Then select OK.
24. Verify that the protection switch action did not introduce any unwanted results.
25. Enter a right click on the ERP entity and select Release Protection Switch.
Prior to provisioning EoMPLS, the software license for EoMPLS must be enabled so the
GE11xPro system may support the following number of EoMPLS PWs:
More information and specifications on EoMPLS and the current implementation can be
found in FSP 150-GE11xPro System Description.
More information on EoMPLS use case details can be found in FSP 150-GE11xPro Quick
Start Guide.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
The following procedure also assumes that services have been configured at
local end with flows to support MPLS encapsulated traffic and a connection exists
between the local end and the remote end. See Provision Access Port Services on p.
149.
Refer to EoMPLS Configuration Options and Rules to determine the default values, value
ranges and rules for each option in the following procedure.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application menu. Expand the System, Administration and Software Licensing
entities in the selection tree pane, by clicking the “+” sign next to each entity.
4. Select the Configuration Application on the tool bar or select Configuration from the
Application menu. Expand System and NE-1 entities in the selection tree pane by
clicking the “+” sign next to each entity.
6. Enter or select the following data to configure the EoMPLS PW (see Create/Edit
EoMPLS PW for options and rules):
Identification
a) PW ID - automatically indexed
AdminState
Configuration
7. To view an EoMPLS PW, select EoMPLS PW entity in the selection tree under
Configuration View to display the list of configured EoMPLS PW entities in the details
pane.
9. To close the EoMPLS PW view, click the “x” on the facility tab.
10. To edit an EoMPLS PW, select EoMPLS PW entity in the selection tree under
Configuration View to display the list of configured EoMPLS PW entities in the details
pane.
11. Enter a right click on the desired EoMPLS PW entity and select Edit EoMPLS PW.
c) Change the settings of Outer S-Tag Priority Control, Outer Label EXP
Control, Inner Label EXP Control, Egress Interface, Outer Stag Vlan, Rx
VC Label, Tx VC Label, Rx MPLS Label and Tx MPLS Label as desired.
Click on OK.
13. To delete an EoMPLS PW, select EoMPLS PW entity in the selection tree under
Configuration View to display the list of configured EoMPLS PW entities in the details
pane.
14. Enter a right click on the desired EoMPLS PW and select Delete EoMPLS PW.
16. Select the Configuration icon in the tool bar or select Configuration from the
Application menu, then expand the System, NE-1, NTE entities in the selection tree,
by clicking the “+” sign next to each entity.
17. Enter a right click on the desired Network Port and select Edit Configuration.
18. EoMPLS Source IP Address - enter a desired IPv4 Address in Network Port
Configuration.
Click on OK.
mapping should also take MPLS labels into consideration (see Default Priority
Mapping Profile Tables and Priority Mapping Profile (Create/Edit Priority Mapping Profile)
for more information on EoMPLS priority mapping).
20. Select Configuration icon or select Configuration from the Application menu, then
expand the System, NE-1, NTE and Access Port entities in the selection tree, by
clicking on the “+” sign next to each entity.
21. Select the Flow entity under Configuration view to display the list of configured Flows
in the facility configuration pane.
22. Enter a right click on the desired Flow and select Edit Configuration.
Figure 105: Configure EoMPLS Related Settings on Flow (EVPL Flow, Multi COS Enabled)
23. Select the following data to configure EoMPLS settings on the flow:
Connection
If the TTL in any of the encapsulation labels equals to 0, the associated packets
will be dropped. The system supports a statistic counter for such dropped
packets.
24. Select Performance icon or select Performance from the Application menu, then
expand the System, NE-1 and NTE entities in the selection tree, by clicking on the “+”
sign next to each entity.
25. Select EoMPLS PW entity under Performance View to display the PM summery in the
details pane.
Provision GRE
The Generic Routing Encapsulation (GRE) is supported in A2N direction on Network port
(physical and logical) in all GE112Pro series products
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1 and GRE in the selection tree pane, by
clicking on the “+” signs next to it to expand the view.
2. Right-click GRE IP Interface and select Create GRE IP Interface in the Shortcut
Menu.
3. Accept the GRE IP Interface ID. It must be 1 (Only one GRE IP Interface can be
created).
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1 and GRE in the selection tree pane, by
clicking on the “+” signs next to it to expand the view.
2. Right-click GRE Tunnel and select Create GRE Tunnel in the Shortcut Menu.
3. Accept the GRE Tunnel ID. It must be 1 (Only one GRE IP Interface can be created).
The Port Mirror feature on the system has 2 Mirror Sessions on that can mirror frames
from a Source Port to a Monitor Entity. A single mirror session is required for each Source
Port and direction being mirrored. Multiple filters can be added for a Mirror Session to limit
the number of frames mirrored to the Monitor Port. Truncation and time-stamping can also
be enabled for each Mirror Session. Monitor Entity can be one traffic port, or one egress
Monitor Flow point. When egress Monitor Flow point is used, additional packet
procession can be applied, for example: Tag Push, bandwidth Control, tunnel and etc.
Mirror Resource concept is not applicable for has enough port resources
in FPGA. So user does not need specify Mirror Resource when creating
Mirror Session.
If port is being configured as a Mirror Port, set other physical port settings
as required for interfacing with the external device.
a) Select Enabled for Monitor Port if port is to be used to transport mirrored
frames
Otherwise go to 1
7. To change a port having Monitor Port from enabled to a disabled condition, the port
cannot be assigned to a Mirror Session. If it is assigned to a Mirror Session and it is
desired to change the port to an Unassigned state, the Mirror Session must first be
deleted (see 1 and follow the link for ‘Configure Mirror Sessions’).
If the port is not a participant in a Mirror Session, follow the directions in 4 and 5, then
select ‘Disabled’ for Monitor Port.
8. Click on OK
9. Go to 1
To edit settings for a Monitor Port , follow the directions in 4 and 5, then edit the desired
settings (limited to: Alias, Media Type, MTU, Configured Speed and Buffer Size.
10. Click on OK
11. Go to 1
14. The EID automatically indexes to the next available ID and does not normally require a
selection by the user.
16. Go to 12
18. Go to 12
24. Go to 12
26. Go to 12
c) Click OK.
28. Go to 12
31. The EID automatically indexes to the next available ID and does not normally require a
selection by the user, but a drop-down box of available EIDs is provided.
Select the desired Source Port from the drop-down box. This is the port being
mirrored.
Select the desired Monitor Port from the drop-down box. One or more Access
Ports must already have been configured as a Monitor Port to appear in the drop-
down list.
To close the view, click on the ‘X’ in the tab for the session.
35. Go to 29
37. ACL Miss Action, Timestamp Control, Truncation Control and Truncation Length can
be edited.
Click OK.
38. Go to 29
c) Click OK
40. To clear statistics for a Port Mirror Session:
c) Click on OK
41. Go to 29
c) Right Click on the desired Mirror Session in the Details Pane and select
Create ACL Rule.
An Create ACL Rule window appears
44. Enter or select the following data for the Mirror ACL Rule:
a) Identification
Index - Edit the Index number. By default, it is automatically indexed.
Enter a desire Alias.
b) State
Select the Administrative State.
c) Rule Configuration
Select the desired Action type.
Enter the desired Rule Priority.
d) MAC Address
Select relevant check boxes for Src Addr and/or Dest Addr, and if
selected, enter the corresponding Address and Mask.
e) EtherType
Select the check box for EtherType Control and if selected enter the
EtherType.
f) Outer VLAN Tag
Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
Select the check box for DEI and enter the DEI value.
i) Protocol
Select or unselect Control and Protocol. The Protocol Number updates
according to the selected Protocol type.
Select or unselect Src Port and/or Dst Port, and if selected, enter Low
Limit and High Limit.
Select or unselect TCP Flags Control, and if selected, enter TCP Flags.
j) Click on OK.
45. Go to 42.
d) Right click the desired ACL rule and select View Configuration.
An View ACL Rule window appears
47. Go to 42.
Provision ELP
The Ethernet Linear Protection (ELP) behavior and Automatic Protection Switching
(APS) protocol are specified in ITU-T Recommendation G.8031. The ELP functionality is
used to provide Ethernet network protection for end-to-end services over any topology.
The protection mechanism uses 2 point-to-point network connections; with 1 connection
providing a primary (working) path and the other providing a secondary (protect) path.
Create ELP
A Ethernet Linear Protection Group (ELP) is created on the Network ports.
1. Select the Configuration Application on the tool bar or select Configuration in the
Application Menu. Expand System, Protection Groups and NE-1 in the selection tree
pane, by clicking on the “+” signs next to them to expand the view.
2. Under NE-1, right-click ELP and select Create ELP in the shortcut menu.
Identification,
AdminState,
Configuration
Eidt ELP
A Ethernet Linear Protection Group (ELP) is created on the Network ports.
1. Select the Configuration Application on the tool bar or select Configuration in the
Application Menu. Expand System, Protection Groups and NE-1 in the selection tree
pane, by clicking on the “+” signs next to them to expand the view.
2. Under NE-1, click ELP and select Create ELP in the shortcut menu.
3. In the ELP list, right-click the ELP to be edited, and select Edit ELP in the shortcut
menu.
Identification,
AdminState,
Configuration
l CPE based encryption: The traffic may be secured at the customer CPE with the Inner
VLAN encrypted and Outer VLAN tagged at the NID.
l Management service encryption: The encryption starts from the NID owned by the
Service Provider. The NID is able to filter the traffic based on the incoming VLAN ID
and entry the traffic based on the policy that is to be defined by the end user.
l The smaller overhead of implementing MAC security in an end to end manner makes
ConnectGuard - MAC encryption a good solution for Layer-2 based backhaul.
More information on ConnectGuard and the current implementation can be found in FSP
150-GE11xPro System Description.
More information on ConnectGuard use case details can be found in FSP 150-GE11xPro
Quick Start Guide.
The following procedure assumes that the user has configured the NE with an
IP address and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN
(eth0) Port Using the Serial Port with at least a Provisioning level user permission and
then is logged on with a Crypto level user permission using the web-based GUI (See
User Authorization Privilege Levels).
To ensure the secure connection and authentication between the nodes that
support ConnectGuard, the local user, with crypto privilege or non-crypto
privilege, must use HTTPS in the Internet Browser to access a GE114Pro
(C)/GE114Pro (CSH), i.e. [Link] where
[Link] is the IP address of the DCN that the GE114Pro
(C)/GE114Pro (CSH) is connected to.
The following procedure also assumes that services have been configured at
both ends with flows to support encrypted P2P traffic and a connection exists between
the two sides. See Provision Access Port Services.
1. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System and Profiles entities in the Selection Tree, by clicking the “+”
signs next to each entity.
2. To create a Key Exchange Profile, right click on the Key Exchange entity and select
Add Key Exchange Profile.
3. Enter or select the following data to configure the key exchange profile (See
Create/Edit Key Exchange Profile for options and rules):
Identification
a) Key Exchange Profile EID - select a desired profile entity identifier from
the drop-down list
b) Name - enter a desired name for this profile (optional)
Parameters
c) Diffie Hellman Length - select the desired keypair length for Diffie Hellman
mode
d) Authentication Password - enter a string of up to 10 - 32 alphanumeric and
special characters as the authentication password for Diffie Hellman
mode
e) Retype Authentication Password
User must make sure that the Key Exchange Profile settings on both ends of
the traffic for encryption and decryption match each other and the
Authentication Password must be same on both ends.
Click on OK.
4. Enter the crypto password that was last set (See Logging On and Configure Local
Crypto User - GE114Pro (C)/GE114Pro (CSH) for information on crypto password
setting.)
Instead of hiding the crypto password using black dots, user may click on the
“Show password” checkbox as an option to make the password components
visible, e.g., gui_12345678#ADVA.
Click on OK.
Every time after the provisioning operation, the crypto user is required to
enter the crypto password to verify if the password input is the same as the
crypto password stored in the SRAM.
It is required that the crypto password of the crypto user conform to the
security policy of High strength (see Configure Security Policy).
It
If the entered crypto password is different from the one stored in SRAM, an
error message will pop up indicating that the operation performed with
insufficient privilege level will be denied. (See Figure 127 on p. 240)
5. To View an Key Exchange Profile, select Key Exchange entity under ConnectGuard
view to display the list of configured Key Exchange Profile entities in the details pane.
Figure 128: ConnectGuard Key Exchange Profile List and Operation Menu
6. Enter a right click on the desired Key Exchange Profile entity and select View
Configuration.
7. To close the Key Exchange Profile view, click the “x” on the facility tab.
8. To edit an Key Exchange Profile, select Key Exchange entity under ConnectGuard
view to display the list of configured Key Exchange Profile entities in the details pane.
9. Enter a right click on the desired Key Exchange Profile entity and select Edit.
10. Edit the following data to configure the Key Exchange Profile:
12. To delete an Key Exchange Profile, select Key Exchange entity under ConnectGuard
view to display the list of configured Key Exchange Profile entities in the details pane.
13. Enter a right click on the desired Key Exchange Profile and select Delete.
Click on OK.
15. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System, NE-1, NTE114PRO CSH and Secure Flows entities in the
Selection Tree, by clicking the “+” signs next to each entity.
16. Enter a right click on the Flow entity and select Add Secure Flow.
17. Enter or select the following data to configure the Secure Flow (See Create/Edit
Secure Flow for options and rules):
Identification
c) Egress Interface - select the desired egress interface for encrypted traffic.
d) Cipher Suite - select the desired cipher suite from the drop-down list.
e) Tags In Clear - select the desired number of frame tags to bypass the
security tag.
f) Replay Protection - enable/disable the replay protection for received
packets.
g) Replay Protection Window - enter the desired replay protection window
size when replay protection has been enabled.
Key Exchange Setting
h) Key Exchange Profile - select the desired Key Exchange Profile that has
been provisioned.
i) Key Exchange Tag Mode - select the desired key exchange frame’s tag
mode. Only “Manual” is supported in current release.
j) Key Exchange Interval - enter a desired Key Exchange Interval.
k) Remote MAC Address Enabled - enable/disable the Remote MAC
Address entry for a unicast MAC address.
l) Remote MAC Address - enter a desired unicast MAC address as the DA
when Remote MAC Address Enabled option has been enabled.
Key Exchange Tag Setting
m) Select the checkbox by Outer VLAN to enable Outer VLAN entry and
enter the Outer VLAN Tag, as desired.
n) Select the checkbox by Inner VLAN1 to enable Inner VLAN1 entry and
enter the Inner VLAN1 Tag, as desired.
Click on OK.
19. To View a Secure Flow, select the Flow entity under Secure Flows in ConnectGuard
view to display the list of configured Secure Flow entities in the details pane.
20. Enter a right click on the desired Secure Flow and select View Configuration.
The Secure Flow configuration view window not only displays the
configuration settings, but also shows the instantaneous state of Secure
Channel (SC) and Security Association (SA).
Two SA are supported within each SC for the purpose of key exchange
without traffic interruption.
The SC state provides a brief performance statistic view. For more detailed
SC statistics, see View Secure Flow Statistics on Both Ends.
If no mistakes were made in the Secure Flow configurations at both ends, the
key exchange process will succeed; otherwise a “Key Exchange Failed”
alarm associated with the secure flow will be raised.
21. To close the Secure Flow configuration view, click the “x” on the facility tab.
22. To edit a Secure Flow, select the Flow entity under Secure Flows in ConnectGuard
view to display the list of configured Secure Flow entities in the details pane.
23. Enter a right click on the desired Secure Flow and select Edit.
AdminState
b) Cipher Suite - select the desired cipher suite from the drop-down list.
c) Tags In Clear - select the desired number of frame tags to bypass the
security tag.
d) Replay Protection - enable/disable the replay protection for received
packets.
e) Replay Protection Window - enter the desired replay protection window
size when replay protection has been enabled.
Key Exchange Setting
f) Key Exchange Profile - select the desired Key Exchange Profile that has
been provisioned.
g) Key Exchange Tag Mode - select the desired key exchange frame’s tag
mode. Only “Manual” is supported in current release.
h) Key Exchange Interval - enter a desired Key Exchange Interval.
i) Remote MAC Address Enabled - enable/disable the Remote MAC
Address entry for a unicast MAC address.
j) Remote MAC Address - enter a desired unicast MAC address as the DA
when Remote MAC Address Enabled option has been enabled.
Key Exchange Tag Setting
k) Select the checkbox by Outer VLAN to enable Outer VLAN entry and
enter the Outer VLAN Tag, as desired.
l) Select the checkbox by Inner VLAN to enable Inner VLAN entry and enter
the Inner VLAN Tag, as desired.
Click on OK.
If key exchange process failed, it keeps trying restart key exchange process
until three consecutive failures, where the third key exchange will be delayed
for a period of “Key Exchange Interval” after the second failure.
After three consecutive key exchange failures, the crypto user may perform
“Restart Key Exchange” (see 26) operation after making appropriate changes
on the Secure Flow settings of both ends.
26. To restart key exchange for a Secure Flow, select the Flow entity under Secure Flows
in ConnectGuard view to display the list of configured Secure Flow entities in the
details pane.
27. Enter a right click on the desired Secure Flow and select Restart Key Exchange.
30. To delete a Secure Flow, select the Flow entity under Secure Flows in ConnectGuard
view to display the list of configured Secure Flow entities in the details pane.
31. Enter a right click on the desired Secure Flow and select Delete.
To realize traffic encryption and decryption between the two ends, the
provisioned Access Flow s on both ends must be associated with a Secure Flow
and the Secure Flow settings on both ends must be the same.
By associating an Access Flow with a Secure Flow, the Access Flow will be
able to encrypt the outgoing traffic and decrypt the incoming traffic. To view
the Statistics of encrypted and decrypted packets on both ends, see View
Secure Flow Statistics on Both Ends.
The procedure below assumes that layer-2 services have been configured at
both ends with flows to support the ConnectGuard secure traffic frames
between the two ends for key exchange and a connection exists between the
two sides.
The procedure below also assumes that at least one Secure Flow has been
provisioned and the Key Exchange Frame Tag Setting in Manual mode (see
Create/Edit Secure Flow) matches the tags of the Flow that is to be
associated with the Secure Flow.
34. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System, NE-1, NTE114PRO CSH and Secure Flows entities in the
Selection Tree, by clicking the “+” signs next to each entity.
35. Expand a desired Access Port entity in the selection tree and select the Flow entity
under the Access Port to display the list of configured flows in the details pane.
36. Enter a right click on the desired flow and select Edit Configuration.
37. Configure the following data to associate the Flow with an existing Secure Flow:
Connection
a) Secure Flow - select a desired Secure Flow from the drop-down list.
b) Secure Block - select Enabled or Disabled.
Before the editing the Secure Flow List, the user must set the Secure
Block to enabled and change the list to empty.
The Access Flow attributes “Secure Flow” and “Secure Block” are editable
only for the crypto user in ConnectGuard View and are ready-only for non-
crypto users.
Thus, the two attributes are not editable while a user with at least a
provisioning privilege level provisions Access Port Services (see Provision
Access Port Services).
The user has to make a conscious decision doing this because security
can be undermined.
In this state, the crypto user can only provision the following two settings for the
Unsecure Normal Access Flow :
l Secure Block
l Secure Flow
TheAccess Flow /Nework L3 Flowpoint is not associated with a Secure Flow and
Secure Block is Enabled.
In this state, the crypto user can provision the following settings for the Access Flow :
l Secure Block
l Secure Flow
Unsecure Blocked
l VLAN Members
l Tag Management
l Untagged Frame control
In this state, a user with at least the Provisioning privilege level can provision all the
settings in the Access Flow .
The Access Flow /Nework L3 Flowpoint is associated with a Secure Flow and the
Secure Flow has an active key to encrypt/decrypt packets.
In this state, the crypto user can provision the following settings for the Access Flow :
l Secure Block
l Secure Flow
Secure Normal
l VLAN Members
l Tag Management
l Untagged Frames control
In this state, a user with at least the Provisioning privilege level can provision the
settings other than above in the Access Flow .
In this state, the crypto user can provision the following settings for the Access Flow :
l Secure Block
l Secure Flow;
Secure Blocked
l VLAN Members
l Tag Management
l Untagged Frames control
In this state, a user with at least the Provisioning privilege level can provision the
settings other than above in the Access Flow .
Click on OK.
The procedure below also assumes that at least one Secure Flow has been
provisioned and the Key Exchange Frame Tag Setting in Manual mode (see
Create/Edit Secure Flow) matches the tags of the Flowpoint that is to be
associated with the Secure Flow.
39. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System, NE-1, NTE and the desired Network Port in the Selection
Tree, by clicking the “+” signs next to each entity.
40. Under the Network Port, click L3 Flow Point. And a list of L3 Flow Point existing on
the Network Port is displayed.
41. Right-click the desired L3 Flow Point and select Edit Configuration.
43. Enter Secure Flow Attibute for the L3 Flow Point as desired.
When a flow point associates with a secure flow, the Secure Block must
be disabled.
To change the Secure Flow, the user must set the Secure Block to
enabled and change the list to empty first.
If Key Exchange process is successful, the user can view the secure flow
statistics to monitor the performance of traffic encryption and decryption.
If the “Key Exchange Failed” alarm is raised, the SA and SC will not show
valid data.
44. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System, NE-1, NTE114PRO CSH and Statistics entities in the
Selection Tree, by clicking the “+” signs next to each entity.
45. Click on Flow and select a desired Secure Flow in the details pane.
46. Alternatively, expand the System, NE-1, NTE114PRO CSH and Secure Flows
entities in the Selection Tree pane in ConnectGuard View. Select Flows entity to
display the list of configured Secure Flows.
47. Double click on the desired Secure Flow, or enter a right click on the desired Secure
Flow and select View Configuration.
48. Scroll down the Secure Flow configuration page to observe SC State and SA State.
49. While under the Statistics, enter a right click on the desired Secure Flow and select
the desired action from the menu: Init Registers, Edit Thresholds, Generate PM Data
File (see Figure 142 on p. 255).
l Software Install
l Software Version
l Restore Factory Defaults
l Restore Database
l Load Config File
The following procedure assumes that the user has configured the NE with an
IP address and connected the NE to a DCN or LAN (see Set Up the GE11xPro
DCN (eth0) Port Using the Serial Port on p. 322) with at least a Provisioning level user
permission and then is logged on with a Crypto level user permission using the web-
based GUI (See User Authorization Privilege Levels).
1. Select the ConnectGuard icon or select ConnectGuard from the Applications menu,
then expand the System and Administration entities in the Selection Tree, by clicking
the “+” signs next to each entity.
3. To approve software installation, set Software Install to Enabled and enter the
Software Version (e.g. 7.1.1-365). To approve the operations of Restore Factory
Defaults, Restore Database and/or Load Config File, select Enabled from the
corresponding drop-down list.
Click on OK.
For information on how to set/edit the Crypto Password, see Configure Local
Crypto User - GE114Pro (C)/GE114Pro (CSH) and Logging On.
The GE11xPro family products support Layer-3 services (i.e. IP service forwarding)
functionalities, including:
l Create DHCP Relay Agent to include desired Traffic IP Interfaces for dynamic routing
learning
In current system, the layer-3 probes (See Provision a Layer-3 Probe) do not
support the test of the layer-3 services provisioned under the NE.
However, TWAMP can support the test of the layer-3 services provisioned
under the NE.
Refer to Layer-3 Services Configuration Options and Rules to determine the default
values, value ranges and rules for each option in the following procedure.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application menu. Expand the System, Administration and Software Licensing
entities in the selection tree pane, by clicking the “+” sign next to each entity.
4. To create an L3 Flow Point, select the Configuration Application on the tool bar or
select Configuration from the Application menu. Expand System, NE-1 and NTE
entities in the selection tree by clicking on the “+” sign next to each entity to expand
each view.
5. Expand the desired Network Port facility, Access Port facility or LAG in the selection
tree by clicking the “+” sign next to it.
6. Enter a right click on L3 Flow Point and select Create L3 Flow Point.
7. Enter the following L3 Flow Point options (See Create/Edit L3 Flow Point for options
and rules):
Identification
h) Edit CIR, EIR, CBS, EBS, CM and CF for Policer. Edit CIR, EIR, BS,
and MIN Threshold %, MAX Threshold %, Maximum Drop Probability %
for WRED In-Profile and WRED Out of Profile traffic for Shaper. If Multi
COS is Enabled, edit the above entries for each desired COS and
select/deselect the check box for Hierarchical COS Settings. If
Hierarchical COS Settings are selected, enter the Guaranteed Bandwidth
and Maximum Bandwidth.
Click on OK.
8. To edit an L3 Flow Point, select the L3 Flow Point entity in the selection tree to display
the list of configured L3 Flow Points in the facility configuration pane. Enter a right
click on the desired L3 Flow Point and select Edit L3 Flow Point.
Identification
d) Edit CIR, EIR, CBS, EBS, CM and CF for Policer. Edit CIR, EIR, BS,
and MIN Threshold %, MAX Threshold %, Maximum Drop Probability %
for WRED In-Profile and WRED Out of Profile for Shaper. If Multi COS is
Enabled, edit the above entries for each desired COS and select/deselect
the check box for HierarchicalCOS Settings. If Hierarchical COS Settings
are selected, enter the Guaranteed Bandwidth and Maximum Bandwidth
Click on OK.
10. To view an L3 Flow Point, select the L3 Flow Point entity in selection tree to display
the list of configured L3 Flow Points. Enter a right click on the desired L3 Flow Point
and select View Configuration, or double click on the desired L3 Flow Point directly.
11. To close the L3 Flow Point Configuration view, click the “x” on the facility tab.
12. To delete an L3 Flow Point, select the L3 Flow Point entity in selection tree to display
the list of configured L3 Flow Points. Enter a right click on the desired L3 Flow Point
and select Delete L3 Flow Point.
Click on OK.
13. To create an ACL rule for an L3 Flow Point, select the L3 Flow Point entity in selection
tree to display the list of configured L3 Flow Points. Enter a right click on the desired
L3 Flow Point and select Create ACL Rule.
14. Enter or select the following data to configure the ACL Rule (see Create/Edit ACL
Rule for options and rules):
Identification
COS Override takes effect only on “Multi COS” enabled L3 Flow Point.
See 7 for more details on L3 Flow Point configurations.
e) Select relevant check boxes for Src Addr and/or Dest Addr, and if
selected, enter the corresponding Address and Mask.
If Rule Action is set to Accept, the system will forbid the user to edit
the Destination Address.
EtherType
f) Select the check box for EtherType Control and if selected enter the
EtherType.
Outer VLAN Tag
g) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
h) Select the check box for DEI and enter the DEI value.
Inner VLAN Tag
i) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
IP
j) Select the Src Addr check box, and if selected, select the Dynamic check
box as desired or directly enter IP addresses for Low Limit and High Limit.
k) Similarly, select the relevant check boxes for Dest Addr and Priority, and
if selected, enter Low Limit and High Limit.
Protocol
l) Select the check box for Control and the Protocol Number will change to
align with the selected Protocol type. If CUSTOM is selected, enter a
custom number.
m) Select the relevant check boxes for Src Port and/or Dst Port, and if
selected, enter Low Limit and High Limit.
Src Port and Dst Port cannot be enabled if Protocol Control is not
enabled.
n) Select the check box for TCP Flags Control, and if selected, enter TCP
Flags.
Click on OK.
15. To view an ACL Rule, select the L3 Flow Point entity in selection tree to display the
list of configured L3 Flow Points. Enter a right click on the desired L3 Flow Point and
select View ACL Rules.
16. To view the Configuration of a specific ACL Rule, enter a right click on the desired L3
ACL Rule in the list and select View Configuration.
17. To close the ACL Rule configuration view, click the “x” on the facility tab.
18. To edit an ACL Rule configuration, enter a right click on the desired L3 ACL Rule in the
list and select Edit Configuration.
Identification
e) Select relevant check boxes for Src Addr and/or Dest Addr, and if
selected, enter the corresponding Address and Mask.
If Rule Action is set to Accept, the system will forbid the user to edit
the Destination Address and will only allow the MAC Address of the
traffic port associated with the L3 Flow Point.
EtherType
f) Select the check box for EtherType Control and if selected enter the
EtherType.
Outer VLAN Tag
g) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
h) Select the check box for DEI and enter the DEI value.
Inner VLAN Tag
i) Select the relevant check boxes for VLAN ID and/or PCP, and if selected,
enter the corresponding Low Limit and High Limit.
IP
j) Select the Src Addr check box, and if selected, select the Dynamic check
box as desired or directly enter IP addresses for Low Limit and High Limit.
k) Similarly, select the relevant check boxes for Dest Addr and Priority, and
if selected, enter Low Limit and High Limit.
Protocol
l) Select the check box for Control and the Protocol Number will change to
align with the selected Protocol type. If CUSTOM is selected, enter a
custom number.
m) Select the relevant check boxes for Src Port and/or Dst Port, and if
selected, enter Low Limit and High Limit.
n) Select the check box for TCP Flags Control, and if selected, enter TCP
Flags.
Click on OK.
20. To edit the priority of an ACL Rule, enter a right click on the desired L3 ACL Rule in the
list and select Edit Rule Priority.
21. Edit the Rule Priority. The priority is 0 by default. (see Edit ACL Rule Priority for
options and rules)
Click on OK
22. The updated Rule Priority will be displayed in the ACL Rule List (see the figure below).
23. To delete an ACL Rule, enter a right click on the desired ACL Rule and select Delete.
25. To add a new L3 ACL Rule, enter a right click on the L3 ACL Rule list and select Insert
ACL Rule.
27. To create a Traffic IP Interface, select the Configuration Application on the tool bar or
select Configuration from the Application menu. Expand System, NE-1 and NTE
entities in the selection tree by clicking on the “+” sign next to each entity to expand
each view.
28. Expand the desired Network Port facility or Access Port facility in the selection tree by
clicking the “+” sign next to it.
29. Select the L3 Flow Point entity in selection tree to display the list of configured L3
Flow Points. Enter a right click on the desired L3 Flow Point and select Create IP
Interface.
30. Enter the following data to configure the Traffic IP Interface (see Create/Edit Traffic IP
Interface for options and rules):
Identification
DHCP Configuration
31. To edit a Traffic IP Interface, select the Traffic IP Interface entity in selection tree to
display the list of configured Traffic IP Interface in the configuration pane. Enter a right
click on the desired Traffic IP Interface and select Edit IP Interface.
Identification
Click on OK.
33. To view a Traffic IP Interface, expand L3 Flow Point entity by clicking the “+” sign and
select the Traffic IP Interface entity in the selection tree to display the list of
configured Traffic IP Interface.
34. Enter a right click on the desired Traffic IP Interface and select View Configuration, or
double click on the desired Traffic IP Interface directly.
35. To close the Traffic IP Interface view, click the “x” sign on the facility tab.
36. To delete a Traffic IP Interface, select the Traffic IP Interface entity in selection tree to
display the list of configured Traffic IP Interface in the configuration pane. Enter a right
click on the desired Traffic IP Interface and select Delete IP Interface.
38. To add a Static ARP Entry to a Traffic IP Interface, select the Traffic IP Interface
entity in selection tree to display the list of configured Traffic IP Interface in the
configuration pane. Enter a right click on the desired Traffic IP Interface and select
Add Static ARP Entry.
39. Enter the following data to configure the Static ARP entry:
When the system level alarm “Traffic ARP Table Full” is raised against
the Interface Route, user should not create more Interface Route
related static ARP entries, otherwise layer-3 traffic will be affect.
40. To view a Static ARP Entry, select the Traffic IP Interface entity in selection tree to
display the list of configured Traffic IP Interface in the configuration pane. Enter a right
click on the desired Traffic IP Interface and select View ARP Entry.
41. To close the ARP Entry Table view, click the “x” on the facility tab.
42. To delete a Static ARP Entry, select the Traffic IP Interface entity in selection tree to
display the list of configured Traffic IP Interface in the configuration pane. Enter a right
click on the desired Traffic IP Interface and select Delete Static ARP Entry.
43. Select the radio button for the desired ARP Entry to delete, then the button displayed
is changed, select OK. (see the following figure)
Provision VRF
44. To create a VRF, select the Configuration Application on the tool bar or select
Configuration from the Application menu. Expand System and NE-1 entities in the
selection tree by clicking on the “+” sign next to each entity to expand each view.
46. Enter or select the following options to configure a VRF (see Create/Edit VRF for
options and rules):
Identification
Traffic IP Interfaces
e) Select the check boxes for the desired Traffic IP Interfaces to include in
the VRF.
The system does not allow removing a Traffic IP Interface from a VRF
if the VRF contains one or more Static Routes associated with this
Traffic IP Interface.
47. To Edit a VRF, expand System and NE-1 entities in the selection tree by clicking on
the “+” sign next to each entity to expand each view. Select VRF entity in the selection
tree to display the list of configured VRFs in the configuration pane.
48. Enter a right click on the desired VRF and select Edit VRF.
Identification
The system does not allow Traffic IP Interface removal from the
Traffic IP Interface List if there is one or more static routes associated
with this Traffic IP Interface.
Click on OK.
50. To delete a VRF, expand System and NE-1 entities in the selection tree by clicking on
the “+” sign next to each entity to expand each view. Select VRF entity in the selection
tree to display the list of configured VRFs in the configuration pane.
51. Enter right click on the desired VRF and select Delete VRF.
The system will forbid the VRF deletion if the VRF to delete is in In-
Service state.
Once a VRF is deleted, all the routes of this VRF will also be deleted
automatically by the system.
53. To view a VRF, expand System and NE-1 entities in the selection tree by clicking on
the “+” sign next to each entity to expand each view. Select VRF entity in the selection
tree to display the list of configured VRFs in the configuration pane.
55. To add a static route to the VRF, select the Configuration Application on the tool bar or
select Configuration from the Application menu. Expand System and NE-1 entities in
the selection tree by clicking on the “+” sign next to each entity to expand each view.
56. Select the VRF entity in the selection tree to display the list of configured VRFs in the
configuration pane.
57. Enter a right click on the desired VRF and select Add Static Route.
58. Enter the following options to configure a static route (see Create/Edit Static Route for
VRF for options and rules):
59. To edit a static route, select the VRF entity in the selection tree to display the list of
configured VRFs in the configuration pane.
60. Enter a right click on the desired VRF and select Edit Static Route.
61. Select the radio buttons ahead of the desired Static Route and edit the corresponding
Metric and Forward options as desired. Click on OK. (see the figure below)
62. To delete a static route, select the VRF entity in the selection tree to display the list of
configured VRFs in the configuration pane.
63. Enter a right click on the desired VRF and select Delete Static Route.
64. Select the radio button ahead of the desired Static Route and select OK.
The system will automatically delete all the routes of a VRF if the VRF
is deleted by the user.
The system does not allow removing a Traffic IP Interface from a VRF
if the VRF contains one or more Static Routes associated with this
Traffic IP Interface.
65. To view the available Traffic Routes in a VRF, select the VRF entity in the selection
tree to display the list of configured VRFs in the configuration pane.
66. Enter a right click on the desired VRF and select View Traffic Routes.
67. To close the traffic routes view, click the “x” on the facility tab.
68. To ping a destination IP address using the VRF, select the Configuration Application
on the tool bar or select Configuration from the Application menu. Expand System and
NE-1 entities in the selection tree by clicking on the “+” sign next to each entity to
expand each view.
69. Select the VRF entity in the selection tree to display the list of configured VRFs in the
configuration pane.
70. Enter a right click on the desired VRF and select Ping.
Click on OK.
72. To view the Ping status and statistics, enter a right click on the desired VRF that is
performing Ping and select View Last Ping.
73. Click the Last Ping facility tab to update the Last Ping status until the windows shows
the Ping result. (see the figure below)
74. To close the Last Ping view, click the “x” on the facility tab.
75. To trace route a destination IP address using the VRF, select the Configuration
Application on the tool bar or select Configuration from the Application menu. Expand
System and NE-1 entities in the selection tree by clicking on the “+” sign next to each
entity to expand each view.
76. Select the VRF entity in the selection tree to display the list of configured VRFs in the
configuration pane.
77. Enter a right click on the desired VRF and select Trace Route.
78. Enter the desired IPv4 Address ad the destination to execute Trace Route.
Click on OK.
79. To view the Trace Route status and statistics, enter a right click on the desired VRF
that is performing Trace Route and select View Last Trace Route.
80. Click the Last Trace Route facility tab to update the Last Trace Route status until the
windows shows the Trace Route result. (see the figure below)
81. To close the Last Ping view, click the “x” on the facility tab.
82. To create a DHCP Relay Agent, select the Configuration Application on the tool bar or
select Configuration from the Application menu. Expand System and NE-1 entities in
the selection tree by clicking on the “+” sign next to each entity to expand each view.
83. Enter a right click on the DHCP Relay Agent entity in the selection tree and select
Create DHCP Relay Agent.
84. Enter or select the following options to configure a DHCP Relay Agent (see
Create/Edit DHCP Relay Agent for options and rules):
Identification
d) Select the check boxes for the desired Traffic IP Interfaces to include in
the DHCP Relay Agent.
85. To edit a DHCP Relay Agent, select the DHCP Relay Agent entity in the selection
tree to display the list of configured DHCP Relay Agents in the configuration pane.
86. Enter a right click on the desired DHCP Relay Agent and select Edit DHCP Relay
Agent.
Identification
Click on OK.
88. To delete a DHCP Relay Agent, select the DHCP Relay Agent entity in the selection
tree to display the list of configured DHCP Relay Agents in the configuration pane.
89. Enter a right click on the desired DHCP Relay Agent and select Delete DHCP Relay
Agent.
Once a DHCP Relay Agent is deleted, all the dynamic routes learned
by the DHCP Relay Agent will be deleted automatically by the
system.
In GE11xPro, BFD functions on the Traffic IP Interfaces of Network Ports. When BFD in
N1 Port detects the link failure and BFD in N2 Port detects a successful link, layer-3
traffic going through layer-3 routing table will be forwarded to the IP Interface on N2 Port
via default route; vice versa. Thus, BFD is a trigger to layer-3 routing table update and
protects layer-3 services in the meanwhile.
When BFD protection for layer-3 services is needed, user can create the association
between BFD session and Traffic IP Interface. For more information, see the procedure
below.
l Provision necessary layer-3 services (L3 Flow Point, ACL, Traffic IP Interface, VRF,
Static Routes, etc), making sure all layer-3 routes between two ends are reachable
and resolvable (See Provision Layer-3 Services for more information on the procedure
and see FSP 150-GE11xPro Quick Start Guide for specific use case)
l Create/Edit BFD Session Entity
More information and specifications on BFD and the current implementation can be found
in FSP 150-GE11xPro System Description.
More information on BFD use case details can be found in FSP 150-GE11xPro Quick
Start Guide.
The following procedure assumes that the user has configured the NE with an IP Address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
The following procedure also assumes that layer-3 services ((See Provision Layer-3
Services) have been configured at both ends and two link connections exist between the
two ends via network ports.
Refer to BFD Configuration Options and Rules to determine the default values, value
ranges and rules for each option in the following procedure.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System and NE-1 entities in the selection tree by clicking
the “+” sign next to each entity.
Identification
4. To view a BFD Session, select BFD entity in the selection tree under Configuration
View to display the list of configured BFD entities in the details pane.
6. To close the BFD Session view, click the “x” on the facility tab.
7. To edit a BFD Session, select BFD entity in the selection tree under Configuration
View to display the list of configured BFD entities in the details pane.
8. Enter a right click on the desired BFD Session entity and select Edit BFD.
Identification
10. To delete a BFD Session, select BFD entity in the selection tree under Configuration
View to display the list of configured BFD entities in the details pane.
11. Enter a right click on the desired BFD Session entity and select Delete BFD.
12. Change the Administrative state to non-IS state and click on OK.
13. To view BFD Session Status, select BFD entity in the selection tree under
Configuration View to display the list of configured BFD entities in the details pane.
14. Enter a right click on the desired BFD Session entity and select View Status.
16. To verify if BFD protects layer-3 links when detecting link fault, manually set BFD
Session Control to “Admin Down”, then observe the corresponding BFD Session
Status and the layer-3 route status again.
17. To clear BFD Session performance statistics, select BFD entity in the selection tree
under Configuration View to display the list of configured BFD entities in the details
pane.
18. Enter a right click on the desired BFD Session entity and select Clear Stats.
Click on OK.
Provision VXLAN
Provisioning of VXLAN is a multi-step process, which involves doing the following.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application Menu. Expand System, Administration and Software Licensing entities in
the selection tree pane, by clicking the “+” signs next to each entity to expand each
view.
2. Right click Feature Management and select Edit Feature in the Shortcut Menu.
Configure VTEP
VXLAN Tunnel End Point (VTEP) has to be created at first. See options and rules ).
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1 and VXLAN in the selection tree pane, by
clicking on the “+” signs next to it to expand the view.
a) Identification
Accept the VTEP ID, whic is 1 (Only one VTEP can be created).
Enter a desirable Alias for the VTEP.
b) AdminState
Select a proper AdminState (IS or Management)
c) Configuration
Select or unselect Outer VLAN. If selected, enter appropriate EtherType
and VLAN.
Select or unselect Inner VLAN. If selected, enter appropriate EtherType
and VLAN.
Enter DSCP
Enter Destination UDP Port.
4. Click OK.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1, VXLAN and VTEP in the selection tree
pane, by clicking on the “+” signs next to it to expand the view.
2. In the Detail Panel, Right-click the VTEP instance and select Create VTEP IP
Interface.
a) Identification
Enter VTEP IP IF ID, which can be 1 or 2.
Enter a desirable Name for the VTEP IP Interface.
b) AdminState
Select a proper AdminState (IS or Management)
c) Configuration
Select Unnumbered Control status (The first VTEP IP Interface must be
Numbered and the second one must be unnumbered).
For Numbered VTEP IP Interface, the Borrowed Interface filed is grayed
out; for Unnumbered VTEP IP Interface, the Borrowed Interface filed is
populated by the Interface name of the Numbered VTEP IP Interface.
Select to enable or disable DHCP control, if enabled, also enter IPv4
Address and IPv4 Mask
Select a Network Port from the drop-down list for the VTEP IP Interface to
associate with (A Network Port can only associated with one VTEP IP
Interface).
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1, VXLAN and VTEP in the selection tree
pane, by clicking on the “+” signs next to it to expand the view.
2. In the Detail Panel, Right-click the VTEP instance and select Create VXLAN
Segment.
a) Identification
Enter VXLAN Segment ID.
Enter a desirable Alias for the VXLAN Segment.
b) AdminState
Select a proper AdminState (IS or Management)
c) Configuration
Enter VNI
Select to enable or disable Outer Tag Priority Control.
Select to enable or disable Inner Tag Priority Control.
Selet to enable or disable DSCP Control.
Enter Max DMAC2DIP Entry
Enter DMAC2DIP Table Aging Time
Select DMAC2DIP Table Full Action
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1, VXLAN and VTEP in the selection tree
pane, by clicking on the “+” signs next to it to expand the view.
2. In the Detail Panel, Right-click the VTEP instance and select Create VTEP IPv4
Route.
a) Gateway
b) Metric
c) Interface
d) BED, if the VXLAN is work with a B
Provision IPFIX
Provisioning of lP Flow Information Export (IPFIX) is a multi-step process, which
involves doing the following.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application Menu. Expand System, Administration and Software Licensing in the
selection tree pane, by clicking the “+” signs next to each entity to expand each view.
2. Right click Feature Management and select Edit Feature in the Shortcut Menu.
1. Select the IPFIX Application on the tool bar or select IPFIX from the Application Menu.
Expand System, NE-1, IPFIX in the selection tree pane, by clicking on the “+” signs
next to it to expand the view.
2. In the Selection Tree Pane, right-click Exporter under IPFIX and select Create IPFIX
Exporter
a) Identification
Enter IPFIX Exporter ID, which must be 1 (There can be one Exporter at
most.)
Optionally, enter an Alias for the IPFIX Exporter.
b) Configuration
Select the IP Version to reach Collector 1 and enter the IP address of the
Collector 1.
Enter the UDP port, where Collector 1 listens for IPFIX exporting.
Select the IP Version to reach Collector 2 and enter the IP address of the
Collector 2.
Enter the UDP port, where Collector 2 listens for IPFIX exporting.
4. Click OK.
1. Select the IPFIX Application on the tool bar or select IPFIX from the Application Menu.
Expand System, NE-1, IPFIX in the selection tree pane, by clicking on the “+” signs
next to it to expand the view.
2. In the Selection Tree Pane, right-click Template and select Create IPFIX Template
a) Identification
Enter IPFIX Exporter ID (Up to 32 IPFIX Templates can be supported.)
Optionally, enter an Alias for the IPFIX Exporter.
b) Configuration
Enter a Template Number,
Configure how the Traffic is matched. GE11xPro allows matching
monitored traffic with VID, SIP, SIP Prefix, DIP, DIP Prefix, Protocol,
TOS, TOS Range, TCP Flag, SrcPort, SrcPort Range, DstPort or DstPort
Range.
Configure the data to be collected by IPFIX, the data type can be enabled
or disabled including, Flow Start System Time, Flow End System Time,
Octet Delta Count Control, Packet Delta Count Control, Min TTL, Max
TTL, Min IP Total Length, Max IP Total.
4. Click OK.
1. Select the IPFIX Application on the tool bar or select IPFIX from the Application Menu.
Expand System, NE-1, IPFIX in the selection tree pane, by clicking on the “+” signs
next to it to expand the view.
2. In the Selection Tree Pane, right-click Meter Process under IPFIX and select Create
IPFIX Meter Process
a) Identification
Enter IPFIX Exporter ID (Up to 2 IPFIX Metering Processes can be
supported.)
Optionally, enter an Alias for the IPFIX Metering Process.
b) Configuration
Select an IPFIX Template to be used for the Metering Process.
Select an IPFIX Exporter to be used for the Metering Process.
Enter a desired Active Timeout.
Enter a desired Inactive Timeout.
c) Sampling Configuration
Select Algorithm
Enter Size
Enter Population
4. Click OK.
1. Select the IPFIX Application on the tool bar or select IPFIX from the Application Menu.
Expand System, NE-1, IPFIX in the selection tree pane, by clicking on the “+” signs
next to it to expand the view.
2. In the Selection Tree Pane, right-click Domain under IPFIX and select Create IPFIX
Observation Domain
a) Identification
Enter IPFIX Exporter ID (Up to 32 IPFIX Observation Domains can be
supported.)
Optionally, enter an Alias for the IPFIX Observation Domain.
b) Configuration
Enter an ID for the Observation Domain.
Select a Domain Type for the Observation Domain.
4. Click OK.
1. Select the IPFIX Application on the tool bar or select IPFIX from the Application Menu.
Expand System, NE-1, IPFIX in the selection tree pane, by clicking on the “+” signs
next to it to expand the view.
3. In the Detail Panel, right-click the desired Observation Domain and select Create
IPFIX Observation Point.
a) Identification
Enter IPFIX Observation Point ID (Up to 128 IPFIX Observation Points
can be created in each Domain.)
Optionally, enter an Alias for the IPFIX Observation Point.
b) Configuration
Enter Observation Point ID
Select and Traffic Interface to associate with the Observation Point
(Select a Flow in Flow-based domain, an Access Port or Network Port in
Port-based Domain).
(For flow-based Observation Domain only), select a direction in which the
traffic is monitored.
Select a Meter Process to use.
5. Click OK.
Provision OpenFlow
Provisioning of OpenFlow is a multi-step process, which involves doing the following.
When there are redundant OpenFlow Controllers, roles can be configured. If they are
configured as Master / Slave, only the Master Controller can be used to configure the
OpenFlow Switches. The Slave Controller is used for monitoring purposes. If both
Controllers are configured as Equal, the user can modify OpenFlow Switch from either
one.
By default, the Master or Equal role controller receives Packet In messages, Port-Status
change and Flow-Remove messages. The Slave role only receives Port - status change
messages by default.
On EG-X, configure two Management Tunnels. Management Tunnel one to connect with
GE11xPro One and Management Tunnel two to connect with GE11xPro Two. This is to
enable the user (with the PC) and the SDN Controller to communicate to both GE11xPro
devices in a network as shown in Figure 192 on p. 314.
After Management Tunnel is successfully configured, verify that the GE11xPro devices
can be reached from the PC.
1. Select the Maintenance Application on the tool bar or select Maintenance from the
Application Menu. Expand System, Administration and Software Licensing entities in
the selection tree pane, by clicking the “+” signs next to each entity to expand each
view.
2. Right click Feature Management and select Edit Feature in the Shortcut Menu.
3. Select Enabled from the Status drop-down list associated with the OpenFlow feature.
1. Select the OpenFlow Application on the tool bar or select OpenFlow in the Application
Menu. Expand System entity in the selection tree pane, by clicking on the “+” signs
next to each Note to expand the view.
3. Select OK.
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1 entities in the selection tree pane, by
clicking on the “+” signs next to each node to expand the views.
2. Enter a right click on OF Capable Switch-1 and select Create OF Logical Switch.
5. Select OK.
OpenFlow can be enabled on Ethernet Port 2, either when it is a Network Port or Access
Port. However, OpenFlow must be disabled to switch this Port from a Network port to an
Access port or in the other way around.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand System, NE-1, NTE entities in the selection tree pane, by
clicking on the “+” signs next to each entity to expand each view.
2. Enter a right click on an proper Network or Access port and select Edit Configuration.
3. (On an Access Port), make sure that the Port is in EVPL Mode.
4. (On an Access Port), make sure that A2N Push Port VID is disabled.
7. Select OK.
OpenFlow is enabled
8. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch entities in the selection
tree pane, by clicking on the “+” signs next to each entity to expand each view.
The OF Port doe not show in the Selection Tree Pane until the OpenFlow
Logical Switch is appropriately configured.
There are some attributes significant and have an impact on the OpenFlow
Queues.
l OF Port Number; a number derived from the Physical port number. In
GE11xPro, Network Port one always gets OF Port Number 0x1, Port two
(No matter it is an Network port or access port) always gets OF Port
Number 0x2. Access Port three gets OF Port Number 0x3. So on and So
forth. In Figure 193, This port is listed in the selection tree as OF port-1 in
the Selection tree while the OF Port Number is shown as 0x5. The
OpenFlow Controller uses OF Port Number to identify OF ports.
l Current Rate, the Bandwidth on the physical port which is currently
available for services. It is measured in kbps.
l Maximum Rate, the Maximum Rate the port can offer. It is derived from
the maximum rate the physical speed. It is also measured in kbps. In
GE11xPro, the Maximum rate is fixed to 1,000,000 kbps.
See Figure 193 on p. 321 for more details about the attributes mentioned
above
When the user enables OpenFlow on an Ethernet port, a default OpenFlow Queue is
automatically created and attached to the Port. The default Queue can be shared by all
OpenFlow service on the port when it is the only Queue on the port. To achieve an
improved performance, it is recommended to create additional Queues when in an
environment with multiple services.
See OpenFlow options and rules OpenFlow Configuration Options and Rules).
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1 entities in the selection tree pane, by
clicking on the “+” signs next to each node to expand the views.
4. Enter the Minimum Rate and Maximum Rate (allocated in 1/1000 of Current Rate of
the OpenFlow Port).
The overall allocated Minimum Rate of queues must not exceed the Current
Rate of the OF Port.
It is OK for the overall allocated Maximum Rate to exceed the Maximum
Rate of the OF Port.
5. Enter a Buffersize.
8. Select OK.
See OpenFlow options and rules OpenFlow Configuration Options and Rules).
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch entities in the selection
tree pane, by clicking on the “+” signs next to each node to expand the views.
4. Enter the IPv4 Unicast address and Port number on the OF controller, where the
service is available. In the case, [Link] is entered and the Controller Transport
Port is configured to 6633.
8. Select OK.
9. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch and OF Logical Switch
entities in the selection tree pane, by clicking on the “+” signs next to each node to
expand the views.
l The OpenFlow Protocol V1.3 is active. The GE11xPro series supports only the V1.3 of
the OpenFlow Protocol.
l Packet-in message are appropriately configured. The information that is reported to the
SDN Controller as Packet-in message must be configured, including where they
should be sent. For each packet-in type, the user can configure sending it to either the
Master Controller, Slave controller or Equal. For different Controller roles, see
Configure OpenFlow Controller. There are three classes of Packet in message
supported: No-match, Action, Invalid TTL. By default, No-Match and Action packet-in
messages are sent to Master or Equal SDN Controller. Packet-in messages ARE
NOT sent to the Controller playing a Slave role by default.
l Switch Configuration has been retrieved to the Controller. This allow the Controller to
know the necessary information to configure flow, namely,
o Tables the switch supports
The user needs to do the following on the SDN Controller to create OpenFlow services -
each one needs to be configured for priority, timeout, match rules, instruction, Queue,
Meter, Overlapping Control and Byte Count Control.
OpenFlows are also modified and deleted with the OpenFlow Controller.
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch-1, OF Logical Switch-
1, and OF Main Flow Table in the selection tree pane, by clicking on the “+” signs next
to each node to expand the views.
4. In the lower-right part of the detail pane, find the ACL Rule Eid entry and Service
Eid attribute.
l If corresponding Entity Identifiers are displayed, the Flow is active (See Figure 1 on
p. 328).
l Otherwise, the Flow is not active and the configuration may need modification (See
Figure 2 on p. 329).
The ACL Rule Eid and Service Eid are only shown in the Main
Flow Table.
For Table Miss Flow in the Main Table, the Service Eid is
available when it is active but not the ACL Rule Eid.
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch-1, OF Logical Switch-
1, and OF Main Flow Table or OF VLAN Flow Table in the selection tree pane, by
clicking on the “+” signs next to each node to expand the views.
2. Click OF Flow under the OF VLAN Flow Table or OF Main Flow Table as Selected in
1.
3. Right click the desired Flow and Select View Status in the shortcut menu.
1. Select the OpenFlow Application on the tool bar or select OpenFlow from the
Application Menu. Expand System, NE-1, OF Capable Switch-1 and OF Logical
Switch-1 in the selection tree pane, by clicking on the “+” signs next to each node to
expand the views.
3. Right-Click the desired OF Queue and Select View Status in the shortcut menu.
If Low Touch Provisioning (LTP) is not used, delete the default LTP
management tunnel.
Use the following procedure if using AMP to provision a node as an AMP Server and the
required nodes as AMP Clients. Otherwise, skip this procedure.
1. Ensure that the AMP Server node’s communications network is provisioned properly
for your network configuration, including System IP address, Gateway IP address,
Proxy ARP setting, static route, management tunnel, etc. Also ensure that EFM-OAM
is enabled on the AMP Server Port management tunnel.
2. Expand the Communications entity in the Selection Tree Pane. Enter a right click on
AMP Configuration and select Create Server. The Create AMP Configuration screen
displays:
5. Enter a right click on the AMP Server entity in the details pane and select View to
verify configuration entry.
When the Client node has been installed and configured as an AMP
Client, and when connectivity is sound (and EFM-OAM is enabled to
deliver AMP protocols at each node), the AMP Server node will
provision the remote configuration as entered above.
6. Perform the following for a Network Port if it is used for AMP protocols. Otherwise,
skip this step.
Go to Provision Network Ports to provision the AMP Client flow and set the port
to the In-Service state. Edit EFM-OAM to enable OAM Control.
7. Perform the following for an Access Port if it is used for AMP protocols. Otherwise,
skip this step.
Go to Provision Access Port Services to provision the AMP Client flow and set it
to the In-Service state. (Ensure to edit EFM-OAM to enable OAM Control.)
8. Expand Communications in the selection tree pane. Right click on AMP Configuration
and select Create Client. The following screen displays:
9. Select the desired AMP ID and Port EID. Set Control to Enabled.
10. Select the AMP Configuration entity in the selection tree pane.
11. Enter a right click on the AMP Client entity and select View.
Observe the AMP Statistics - “Last Status Received” should indicate Provision,
and “Last Status Transmitted” should indicate Config Success (see following
figure).
13. Verify that a management tunnel associated with the AMP Client has been
automatically created, by expanding the Management Tunnels and NE-1 entities in the
selection tree pane, and selecting the management tunnel entity.
14. At the AMP Server node, enter a right click on the AMP Server entity in the Details
pane and select View to observe AMP Statistics.
15. At the AMP Server node, expand the Communications entity and select the AMP
Configuration entity in the Selection Tree Pane. Then enter a right click on the AMP
Server entity in the detail pane and select View.
16. Repeat above steps for each AMP Server (and AMP Client node) as required.
Remaining Client node provisioning may be performed by local practices via Network
Manager.
Refer to the following provisioning order on how to provision the PTP configurations for
your site.
The TS, once provisioned and Locked (the OCS Port State changes to Slave state),
may be:
o selected as a sync reference to the System Sync Domain (SYNC-1-1-1-1)
l Create a G.8265 Mini Grand Master Clock -- using Time Clock as Timing Source
o Create a Master Clock Interface
(Optional)
For more information on the scalability of PTP entities, see Enable Software License.
The provisioning steps described in this section are performed using the PTP application
(located on the tool bar or selected via the Application menu) once the licenses of this
feature has been turned on.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
2. Enter a right click on the Ethernet Port entity associated with the PTP Flow Point and
select Edit.
3. Enter the desired Delay Asymmetry value in nanoseconds and select OK.
4. Go to 1.
Prior to creating a Transparent Clock, the appropriate flow(s) for the Clock
source(s) must already have been created and In Service, and the Master
Clock device has been provisioned and tested.
1. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System and NE-1 entities in the selection tree pane, by clicking on the “+”
signs next to each entity to expand each view.
2. Enter a right click on the NE-1 entity and select Create Transparent Clock.
3. Enter the following Transparent Clock options (see Create / Edit a Transparent Clock
for details and rules):
Note that user need ensure that the PTP packets do not have more than two
layers of tags after transmitting out of the egress port, otherwise the PTP
packets will not be processed and the TC performance will be impacted.
e) Select the desired Delay Mechanism and enter the desired Access and
Network PTP Flow Point IDs.
Select OK.
4. Expand the newly created TC entity and select the TC entity and each TC port to view
configuration details and associated LAG, Network and/or Access port Flow Point
EIDs.
5. Expand the associated LAG, Ethernet Access and/or Network ports in the selection
tree pane.
A TC entity appears under the associated ports in the selection tree pane
Figure 208: Network and Access Port PTP Flow Point in Selection Tree Pane
6. Select the Configuration tab in the associated Transparent Clock Ports and PTP flow
points to view configuration details.
7. Select the Statistics and Summary tabs for the associated PTP flow points.
Current PTP statistics are displayed (see the next two figures)
9. Go to 1.
10. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System, NE-1 and TC entities in the selection tree pane, by clicking on
the “+” signs next to each entity to expand each view.
11. Enter a right click on the TC-1-x entity and select Delete.
13. Go to 1.
Prior to creating a Telecom Slave, the appropriate flow(s) for the Clock
source(s) must already have been created and In Service, and the
Master Clock device has been provisioned and tested.
1. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System and NE-1 entities in the selection tree pane, by clicking on the “+”
signs next to each entity to expand each view.
2. Enter a right click on the NE-1 entity and select Create Telecom Slave.
3. Enter the following Telecom Slave options (see Create / Edit a Telecom Slave for
details and rules):
Select OK.
A TS entity appears under the Ethernet Ports in the selection tree pane
5. Enter a right click on the Telecom Slave (TS-1-1) entity and select Create SOOC.
6. Enter the following SOOC options (see Create / Edit a Slave Only Ordinary Clock
(SOOC) for details and rules):
An SOOC entity appears below the Telecom Slave entity in the selection
tree pane
8. Enter a right click on the Ethernet Port associated with the Flow for the clock source
and select Create PTPFP.
9. Enter/Select the following PTP Flow Point options (see Create / Edit a PTP Flow
Point for details and rules):
A PTP FLOW PT entity appears below the associated Ethernet Port entity
in the selection tree pane
10. Select the PTP FLOW PT entity and the Configuration tab to view configuration
details.
11. Enter a right click on the SOOC entity and select Create OCS Port.
An OCS PORT entity appears below the associated SOOC entity in the
selection tree pane
13. Select the OCS PORT entity to view configuration details and Port State.
The OC-S recovered clock will achieve lock to the selected Master
Clock within 25 minutes. If no messages have been received, the Port
State is Listening. Once messages have been received from the
Master Clock the Port State changes to Uncalibrated. When the
system determines it is able to calibrate time, then the Port State
changes to Slave (Locked).
14. Select the PTP Flow Point entity and Statistics tab to view PM data. Ensure that
messages are being received, otherwise troubleshoot accordingly.
15. Select the SOOC entity and Statistics tab to view PM data. If required, select the Raw
PTP Messages tab to view raw PTP messages. See the next two figures.
16. Select the OCS PORT entity to view configuration details and Port State. Wait until
the Port Status changes to Slave (Locked) if it is in Uncalibrated state.
17. Go to 1.
When the Telecom Slave has been provisioned and is Locked to the Master Clock (the
OCS Port Status changes to Slave), then it can be associated with the 10 MHz Clock
Output.
18. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand the System, NE-1, Synchronization, NE-1 and NTE114Sx
entities in the selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
19. Enter a right click on the CLK-1-1-1-1 entity and select Edit Configuration.
a) Enter the desired Alias and select the desired Administrative state
b) Select the desired Frequency Source EID
c) Select the desired Squelch Control and Squelch QL options
d) Select OK
21. Select the CLK-1-1-1-1 entity to view configuration details.
22. Go to 1.
When the Telecom Slave has been provisioned and is Locked to the Master Clock (the
OCS Port Status changes to Slave), then it can be associated with the PPS Output.
23. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand the System, NE-1, Synchronization, NE-1 and NTE20x
entities in the selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
24. Enter a right click on the PPS-1-1-1-1 entity and select Edit Configuration.
a) Enter the desired Alias and select the desired Administrative state
b) Enter the desired Cable Delay Compensation
c) Select the desired Time of Day Source EID
d) Select the desired Squelch Control and Squelch QL options
e) Select OK
PPS-1-1-1-2 can only be used for SyncJack input (see Figure 223).
See SyncJack Testing - GE114Pro (SH)/GE114Pro (CSH) for details.
27. Go to 1.
When the Telecom Slave has been provisioned and is Locked to the Master Clock (the
OCS Port Status changes to Slave), then it can be associated with the TOD Clock
Output.
28. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand the System, NE-1, Synchronization, NE-1 and NTE114Sx
entities in the selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
29. Enter a right click on the TOD-1-1-1-1 entity and select Edit Configuration.
a) Enter the desired Alias and select the desired Administrative state
b) Select the desired Time of Day Source EID
c) Select the desired Squelch Control and Squelch QL options
d) Select OK
32. Go to 1.
When the Telecom Slave has been provisioned and is Locked to the Master Clock (the
OCS Port Status changes to Slave), then it can be associated with the System TOD.
33. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu.
34. Enter a right click on the System entity and select Edit System Time of Day.
37. Go to 1.
Refer to the following example configuration for the provisioning procedure in this section.
Figure 226: Example Boundary Clock and Dynamic Remote Slave in G.8265 Topology
Prior to creating a Boundary Clock, ensure that the following has been
completed:
a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to the
Ethernet port associated with the remote slave.
1. Enable the PTP-MC/BC feature by performing Enable Software Licensing for PTP-
MC/BC.
2. Edit the Network Port and Access Port (associated with the PTP Flow Point for
Master Virtual Port and for OCS Port) and place them In Service. See Provision
Access Port Services and Provision Network Ports.
3. Edit an Ethernet Port’s (associated with the PTP Flow Point for Master Virtual Port)
Delay Asymmetry Setting by performing Associate the Telecom Slave to the 10 MHz
Clock Output.
5. Select PTP in the tool bar or select PTP from the application menu.
6. Expand the System entity and enter a right click on NE-1 entity, then select Create
Boundary Clock.
9. Enter a right click on the PTP BC-1-1 entity and select Edit to modify the configuration
of the BC as appropriate.
10. Enter a right click on the Boundary Clock entity and select Create Master Clock
Interface (MCI).
12. Select the Master Clock Interface entity to verify entry details.
13. Enter a right click on the PTP MCI-1-1-1 entity and select Edit to modify the
configuration of the Master Clock Interface as necessary.
14. Expand the NTE114PRO CSH/SH entity. Enter a right click on the Network or
Access Port associated with the PTP Flow Point for the Master Clock Interface and
select Create PTPFP.
16. Select the PTP FLOW PT entity and Configuration tab to view configuration details.
17. Enter a right click on the PTP MCI-1-1-1 entity and select Create Master Virtual Port.
19. Select the MASTER VIRTUAL PORT entity to view configuration details. Enter a right
click and select Edit to change the Alias as needed.
20. To provision the remote slave, perform one of the following procedures:
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand the System, Synchronization, NE-1 and NTE114SH
entities in the selection tree pane by clicking on the “+” signs next to each entity to
expand each view.
2. Enter a right click on the Time Clock entity and select Edit Time Clock.
1. Select the Configuration Application on the tool bar or select Configuration from the
Application Menu. Expand the System, Synchronization, NE-1 and NTE114PRO
CSH/SH entities in the selection tree pane by clicking on the “+” signs next to each
entity to expand each view.
2. Enter a right click on the Time Clock entity and select Add Time Clock Reference.
a) Select the desired TimeREF Index number and enter the desired Alias
b) Select the desired Priority of this Time Clock Reference
c) Select the desired Time Clock Reference Source
d) Click on OK
4. Add a second Time Clock Reference, if required, by repeating 2 and 3.
5. Select the Time Clock entity and select the Status tab to verify reference configuration
and status. Wait a few minutes for alarms to clear and the Clock Mode changes to
“Locked”. Select the Time Clock entity again to observe progress. See the following
Note and figure.
The Clock Mode should indicate Locked and the Source Status should
indicate Reference OK
The Time Clock will achieve lock to the reference within 5 minutes to
15 minutes, depending on visibility / conditions. When establishing
sync with the reference, the Clock Mode is Tracking. When the
system determines it is able to synchronize, then the Clock Mode
changes to Locked. If this does not occur, verify the above
provisioning steps and Time Clock interconnectivity to the selected
reference.
6. Go to 1.
2. Select the desired Request and Target for switch. Then click on OK.
3. Select the Status tab in the Detail pane to check the state associated with the Time
Ref Eid which is just switched.
4. Go to 1
Figure 237: Example Mini GM Clock and Dynamic Remote Slave in G.8265 Topology
GE114Pro (SH)/GE114Pro (CSH) are the products in GE11xPro family that support
Master Clock (MC) in PTP. Perform the following steps for creating a Master Clock.
Prior to creating a Master Clock, ensure that the following has been
completed:
l the Network Port or Access Port associated with the PTP Flow
Port (for Master Virtual Port) is provisioned and In Service
l a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to
the Ethernet port associated with the remote slave.
1. Enable the PTP-MC/BC feature by performing Enable Software Licensing for PTP-
MC/BC.
2. Edit an Ethernet Port’s (associated with the PTP Flow Point for Master Virtual Port)
Delay Asymmetry Setting by performing Edit an Ethernet Port’s Delay Asymmetry
Setting.
4. Edit the Time Clock and add GPS as the first priority reference by performing Edit the
Time Clock and Add Time Clock Reference.
5. Select PTP Application on the tool bar or select PTP from the application menu.
Expand the System entity, enter a right click on NE-1 entity and select Create Master
Clock.
f) Select OK.
A PTP Master Clock entity displays below the NE entity in the Selection
Tree Pane
8. Enter a right click on the Master Clock entity and select Create Master Clock
Interface.
p) Enter Remote Slave Aging Timeout (Only entered if the Profile is IEEE
1588 2008, and Transport method is Ethernet).
10. Expand the Master Clock entity in the selection tree.
11. Select the Master Clock Interface entity to verify entry details.
12. Enter a right click on the Network or Access Port associated with the PTP Flow Point
for the Master Clock Interface source and select Create PTPFP.
14. Select the PTP FLOW PT entity and Configuration tab to view configuration details.
15. Enter a right click on the Master Clock Interface entity and select Create Master
Virtual Port.
17. Select the Master Virtual Port entity to view configuration details.
19. To provision the remote slave, perform one of the following procedures:
If a Dynamic Slave node has been provisioned, expand Dynamic Slaves and
select the Dynamic Slave entity in the selection tree pane to view
configuration details.
If the following have been provisioned correctly, then the Dynamic Slave
entity should be present:
l The Remote Slave unit has been provisioned with Unicast Message
Negotiation Enabled (Dynamic Slave)
l The Master Clock Interface has been provisioned with the correct
number of Master Slaves Supported to accept the Dynamic Slave
(Maximum Slaves Supported = the maximum number of Dynamic Slaves
+ the maximum number of Static Slaves)
l The Master Clock Interface has been provisioned for the correct MAX
PTP rates (Max Announce Message Rate, Max Sync Message Rate and
Max Delay Response Message Rate)
l The Master Clock Interface has been provisioned for the correct IP
address and PTP domain number
To create a remote slave as a Static Remote Slave, perform the following steps at the
GE114Pro (SH)/GE114Pro (CSH) remote slave location. If the remote slave has ready
been provisioned, go to 1 to provision the GE114Pro (SH)/GE114Pro (CSH) Master
Clock / Boundary Clock node to accept the Static Remote Slave.
Perform the following steps at the GE114Pro (SH)/GE114Pro (CSH) Remote Slave site:
1. Ensure that the Ethernet port associated with the PTP Flow Point (for OCS Port) is
provisioned and In Service.
2. Ensure that a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to the
Ethernet port associated with the Master Clock / Boundary Clock node.
3. Edit the Ethernet Port (associated with the PTP Flow Point) Delay Asymmetry
setting. Perform Edit an Ethernet Port’s Delay Asymmetry Setting.
4. Create a Telecom Slave (ensure that the Slave Only Ordinary Clock [SOOC] is
provisioned for Unicast Message Negotiation: Disabled). Perform Create a Telecom
Slave.
Prior to performing the following steps, ensure that the Boundary Clock /
Master Clock node has been provisioned to accept this Static Remote Slave.
Refer to Create a Boundary Clock or Create a G.8265 Mini Grand Master
Clock.
1. Enter a right click on the Static Slaves entity in the Selection tree and select Create
Static Slave.
A Static Slave entity appears below the Static Slaves entity in the selection
tree pane
4. Select the Static Slave entity and select the Configuration tab to view configuration
details and status.
5. Select the Static Slave Statistics tab to view Receive and Transmit statistics.
6. If statistics are not indicating message receive and transmit statistics as expected,
troubleshoot connectivity and provisioning.
7. At the GE114Pro (SH)/GE114Pro (CSH) remote node, select the PTP Application on
the tool bar or select PTP from the Application menu. Expand the System and NE-1
entities in the selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
8. Select the OCS PORT entity to view configuration details and Port State. Wait until
the Port Status changes to Slave (Locked).
9. Select the SOOC entity and the Statistics tab to view the Receive Statistics.
10. If statistics are not indicating message receive statistics as expected, troubleshoot
connectivity and provisioning.
11. Go to 1.
To create a remote slave as a Dynamic Remote Slave, perform the following steps at the
GE114Pro (SH)/GE114Pro (CSH) remote slave location. If the remote slave has already
been provisioned, go to
If the Remote Slave is another type of unit (such as an OSA 541x), it must
already have a Telecom Slave provisioned. Go to 1 to verity the Dynamic
Remote Slave.
Perform the following steps at the GE114Pro (SH)/GE114Pro (CSH) Remote Slave site:
1. Ensure that the Ethernet port associated with the PTP Flow Point (for OCS Port) is
provisioned and In Service.
2. Ensure that a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to the
Ethernet port associated with the Master Clock / Boundary Clock node.
3. Edit the Ethernet Port (associated with the PTP Flow Point) Delay Asymmetry
setting. Perform Edit an Ethernet Port’s Delay Asymmetry Setting.
2. Select the Dynamic Slave entity and select the Configuration tab to view configuration
details and status. See the following figure.
If the remote node is provisioned and connected correctly, the Dynamic Remote
Slave entity is present and Status results are displayed. If the Dynamic Slave
entity is not present as expected, troubleshoot connectivity and provisioning.
3. Enter a right click on the Dynamic Slave entity and select Edit.
5. Select the Dynamic Slave Configuration tab to view the Administrative State changed
to IS.
6. Select the Dynamic Slave Statistics tab to view Receive and Transmit statistics.
7. If the Dynamic Slave entity is not present or statistics are not indicating message
receive and transmit statistics as expected, troubleshoot connectivity and
provisioning.
8. At the remote slave node, select the PTP Application on the tool bar or select PTP
from the Application Menu. Expand the System and NE-1 entities in the selection tree
pane, by clicking on the “+” signs next to each entity to expand each view.
9. Select the OCS PORT entity to view configuration details and Port State. Wait until
the Port Status changes to Slave (Locked).
10. Select the SOOC entity and the Statistics tab to view the Receive Statistics.
11. If statistics are not indicating message receive statistics as expected, troubleshoot
connectivity and provisioning.
12. Go to 1.
Figure 253: Example Mini GM Clock and Dynamic Remote Slave in G. 8275 Topology - No Backup
Prior to creating a PTP Clock, ensure that the following has been
completed:
l the Network Port or Access Port associated with the PTP Flow
Point (for PTP Port) is provisioned and In Service
l a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to
the Ethernet port(s) associated with the remote unit (Master Clock
or Remote Slave).
l the GPS/GNSS has been installed and cabled to the GE114Pro
(SH)/GE114Pro (CSH)
1. Enable the PTP-MC/BC feature by performing Enable Software Licensing for PTP-
MC/BC.
2. Edit an Ethernet Port’s (associated with the PTP Flow Point for PTP Port) Delay
Asymmetry Setting by performing Edit an Ethernet Port’s Delay Asymmetry Setting.
4. Edit the Time Clock and add GPS as the first priority reference by performing Edit the
Time Clockand Add Time Clock Reference.
5. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System and NE-1 entities in the selection tree pane, by clicking on the “+”
signs next to each entity to expand each view.
6. Enter a right click on the NE-1 entity and select Create PTP Clock.
9. Expand the NTE114PRO CSH/SH entity in the selection tree pane. Enter a right click
on the Ethernet Port (associated with the PTP Flow point for the PTP Clock Interface
source) and select Create PTPFP.
11. Select the PTP FLOW PT entity and Configuration tab to view configuration details.
12. Enter a right click on the PTP Clock entity and select Create PTP Port.
14. Expand the PTP Clock entity. Select the PTP Port entity to view configuration details.
15. A second PTP Port may be added to the PTP Clock. To do so, repeat 9through 14to
add the second PTP Port.
16. Go to 1.
To create a G.8275 Remote Slave, perform the following steps at the GE114Pro
(SH)/GE114Pro (CSH) remote slave location. If the remote slave has already been
provisioned, go to Verify a G.8275 Remote Slave Connectivity.
Perform the following steps at the GE114Pro (SH)/GE114Pro (CSH) Remote Slave site:
1. Enable the PTP-MC/BC feature by performing Enable Software Licensing for PTP-
MC/BC.
2. Ensure that the Ethernet port associated with the PTP Flow Point (for PTP Port) is
provisioned and In Service.
3. Ensure that a cable has been run from the GE114Pro (SH)/GE114Pro (CSH) to the
Ethernet port associated with the Master Clock node.
4. Edit the Ethernet Ports (associated with the PTP Flow Points) Delay Asymmetry
setting. Perform Edit an Ethernet Port’s Delay Asymmetry Setting.
5. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System and NE-1 entities in the selection tree pane, by clicking on the “+”
signs next to each entity to expand each view.
6. Enter a right click on the NE-1 entity and select Create PTP Clock.
9. Expand the NTE114PRO CSH/SH entity in the selection tree pane. Enter a right click
on the Ethernet Port (associated with the PTP Flow point for the PTP Clock Interface
source) and select Create PTPFP.
11. Select the PTP FLOW PT entity and Configuration tab to view configuration details.
12. Enter a right click on the PTP Clock entity and select Create PTP Port.
14. Expand the PTP Clock entity. Select the PTP Port entity to view configuration details.
15. A second PTP Port may be added to the PTP Clock. To do so, repeat 18through 14 to
add the second PTP Port.
16. Expand the PTP Clock entity. Select the PTP Port entity to display the list of
configured PTP Ports. Enter a right click on the desired PTP Port and select View
Configuration to view configuration details and Port State. Wait a few minutes for
alarms to clear and the Port State changes to “Slave”. Select the Time Clock entity
again to observe progress. See the following Note and figure.
The PTP Port recovered clock will achieve lock to the selected Master
Clock within 5 minutes to 60 minutes, depending on network
conditions. If no messages have been received, the Port State is
Listening. Once messages have been received from the Master
Clock the Port State changes to Uncalibrated. When the system
determines it is able to calibrate time, then the Port State changes to
Slave when the PTP Port is locked to the Master (Locked). If this does
not occur, verify the above provisioning steps and interconnectivity to
the Master Clock node.
18. Select the PTP Flow Point entity and the Statistics tab to observe statistics data.
Prior to performing the following steps, ensure that the Master Clock
node has been provisioned to accept this Remote Slave. Refer to
Create a G.8275 Mini Grand Master Clock for G.8275 Master Clock
provisioning steps.
1. Select the PTP Application on the tool bar or select PTP from the Application Menu.
Expand the System, NE-1 and PTP Clock entity. Select the PTP Port entity to display
the list of configured PTP Ports. Enter a right click on the desired PTP Port and select
View [Link] the Configuration tab.
2. If the Port State is not indicating Master as expected, troubleshoot connectivity and
provisioning.
3. To view PTP Port statistics, select the PTP Port entity to display the list of configured
PTP Ports. Enter a right click on the desired PTP Port and select View Statistics.
4. If the PTP Port statistics are not indicating statistics as expected, troubleshoot
connectivity and provisioning.
5. Go to 1.
The unit supports both SDH (Option 1) and SONET (Option 2) synchronization capability.
The default is SDH (Option1). For both SDH and SONET, the BITS interfaces support
T1, E1 and 2048 kHz options. For Synchronization provisioning rules, see
Synchronization
While the BITS-IN and BITS-OUT interfaces can be individually enabled and configured,
they share basic configuration settings, so that changing the line type or code of one
simultaneously changes the same settings on the other.
When the Telecom Slave has been provided and is Locked to the Master Clock (the OCS
Port Status changes to Slave), then it can be associated with a Sync Reference.
Sync-E is enabled on a per Ethernet Port basis. The Sync-E mode attribute supports the
values of enabled or disabled (default for all ports is disabled). If a port working at a
specific Configured Speed and Media Type has Sync-E mode enabled, then it can be
selected as a reference source for the System Clock. If Sync-E mode is disabled for that
port, it is not shown in the drop-down list for the System Clock references.
The following procedure assumes that the user has configured the NE with an IP address
and configured the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permissions
using the web-based GUI.
All steps in the following procedure are performed in the Configuration Application based
on a GE114S product, which also applies to GE114Pro (SH) / GE114Pro (CSH).
Refer to Synchronization to determine the default values, value ranges and rules for each
option in the following procedure.
The Network Port or Access Port must be provisioned prior to using this
procedure. See Provision Access Port Services or Provision Network Ports.
1. Expand the System, Synchronization, NE-1 and NTE114S and BITS-1 entities in the
Selection Tree Pane, by clicking on the “+” sign next to each entity to expand each
view.
Changing the Network Clock Type changes the options available for
Sync-E functions on BITS-IN, BITS-OUT, Access Ports and Network
Ports. If any of these interfaces were previously configured for Sync-E
functions, the Assumed QL, Expected QL and Squelch QL settings
revert to default values and have to be reconfigured.
d) Select OK
3. Go to 1.
Edit BITS-IN
1. Right click on BITS-IN and select Edit Configuration. The following screen display.
Line type, line code, frame format and SA bit settings for BITS-IN and
BITS-OUT are shared. Changing one changes the other.
For SDH (Option-1), if QL Mode is Disabled, Assumed QL must be set
to a value other than None.
BITS will not show up as a potential synchronization reference if the
administration state is set to Unassigned
d) Click OK
3. Select the BITS-IN entity to view configuration details.
4. Go to 1.
Edit BITS-OUT
1. Right click on BITS-OUT and select Edit Configuration. The following screen
displays:
Line type, line code, frame format and SA bit settings for BITS-IN and
BITS-OUT are shared. Changing one changes the other.
Squelch QL setting means if the reference clock drops below this
setting, the BITS-OUT output will be suppressed.
Line Build Out is editable only when the Line Type is T1.
As part of the Ethernet port Sync-E reference set up, the
Administration State should not be set to Unassigned.
d) Click OK
3. Select the BITS-OUT entity to view configuration details.
4. Go to 1.
4. Go to 1.
4. Go to 1.
4. Go to 1.
4. Go to 1.
2. Select the desired Configuration settings for Sync-E Mode, QL Mode, Assumed QL
and Expected QL.
3. Click on OK
4. Go to 1.
To associate Network Ports / Access Ports, Telecom Slave, BITS-IN with sync
reference source: Right click on the System Sync Domain (SYNC-1-1-1-1) and
select Add Sync Reference. The following screen displays:
Click on OK
4. For Network Ports / Access Ports, Telecom Slave, BITS-IN: Select the System Sync
Domain entity (SYNC-1-1-1-1) and the Status tab.
5. Go to 1.
Right click on the System Sync Domain (SYNC-1-1-1-1) and select Edit Sync
Reference. The following screen displays:
2. Select the radio button for the sync source to edit, then select the desired Priority from
the drop-down list and enter an Alias if desired.
Click on OK
3. Go to 1.
Right click on the System Sync Domain (SYNC-1-1-1-1) and select Delete Sync
Reference. The following screen displays:
Click on OK.
3. Go to 1.
4. Select the Maintenance application. Expand the System, Synchronization, NE-1 and
NTE114S/NET114SH entities in the Selection Tree pane. Enter a right click on the
SYNC-1-1-1-1 entity and select Operate Reference Switch.
5. Select the desired Request and Target for switch. Then click on OK.
6. Select the Status tab in the Detail pane to check the state associated with the Sync
Ref Eid which is just switched.
l Provision System LLDP, including LLDP frame settings, Max Neighbors Action and
Destination Address Configuration
l Provision LLDP on Traffic Ports (Network Ports/Access Ports/LAG member ports),
including port LLDP control and SNMP notification control, LLDP frame TLV options
and Management Address configuration
Refer to LLDP Configuration Settings to determine the default values, value ranges and
rules for each option in the following procedure.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
1. Select the Configuration Application on the tool bar or select Configuration via the
application menu.
3. Expand System, NE-1 and NTE11x entities in the selection tree pane, by clicking the
“+” signs next to each entity to expand each view.
4. Enter a right click on the desired Ethernet port and select Edit LLDP.
5. Enter a right click on the Access Port facility and select Edit LLDP.
6. Enter/Select the following data to configure LLDP settings for this port:
Edit LLDP
The LLDP Admin Action on NE level will unify the LLDP Admin Status
on port level. However, it’s still allowed that user customize the LLDP
Admin Status on specific port (see Provision NE-1 Common Units for
LLDP Admin Action on NE level).
Enter a right click under the Management ADDR table title and select the
desired operation from the selection menu. (see Figure 280 on p. 411)
d) If add is selected, an ADD LLDP ACC PORT CONFIG tab will appear
next to the Management ADDR tab (see Figure 281 on p. 411)
• Select the desired Management Interface and Enable/Disable the
Control to transmit the select management address in LLDP frame.
• Click on OK.
e) Right click on an existing Management Address and select Edit from the
selection menu. An Edit LLDP ACC PORT CONFIT tab will appear (see
Figure 281 on p. 411)
• Edit the Control option as desired.
• Click OK.
8. Select the Ethernet Port in the selection tree pane, then in the Details Pane select
LLDP tab. Switch between Destination MAC tabs and corresponding data sub-tabs
below to view Port Configuration, Local Data, Remote System Data, Remote
Management Address, Remote Organizationally Defined TLVs and Remote Unknown
TLVs.
The following procedure assumes that the user has completed the physical installation
procedures in “Physical Installation” in FSP 150-GE11xPro Installation and
Commissioning Manual document, including installation of the Environmental Alarm
cable to the appropriate relays in the GE114Pro (HE) environment. It is also assumed
that the external equipment these Environmental Alarm input pins are connected to are
provisioned and operating as expected. It is also assumed that the user is logged on to
the web-based GUI with the proper privilege level for provisioning (see User Authorization
Privilege Levels).
1. Select Maintenance View. Expand the System and Environmental Alarms entities in
the Selection Tree pane.
2. Enter a right click on the desired Environmental Alarm input entity and select Edit. The
following screen displays.
3. Select the desired options for: Alarm Type, Notification Code, Alarm Input Mode and
Alarm Hold Off
4. Select OK
l "ICF Configuration Files" below (binary) via the web-based GUI, SNMP and CLI
l "CLI Configuration Files" on page 432 (text based) via SNMP, CLI and the web-based
GUI
These two types of files can be used in a complimentary fashion, or they can be used
independently. Each type of file and its use is described under the headings "ICF
Configuration Files" below and "CLI Configuration Files" on page 432.
There is a third type of Database File supported by the GE11xPro called the Default
Settings File. This is an XML based file that changes the default settings applied when a
new entity (such as an EVPL Flow) is created. This file is downloaded and applied to the
unit if the factory default values are determined to be not applicable or unacceptable to
the user’s application. See Default Settings Value File.
As provisioning occurs, the current running configuration database is updated with each
change entered. At some point, the user may determine that the current copy should be
the default database for this unit, at which time the user should perform the "Set a
System Default Database" below procedure. Then, if required the database can be
restored to these settings by performing the "Restore System Defaults" on page 429
procedure.
The Factory Default Database never changes, and as a last resort troubleshooting tool,
or upon decommissioning, the current database can be reset to factory defaults by
performing the "Restore Factory Defaults" on page 430 procedure. The Default Database
can also be reset to Factory Defaults using the “New” option in the "Set a System Default
Database" below procedure. From a user’s perspective, there are some major
differences:
l Restore Factory Defaults delete all Configuration files; “New” option in the Set a
Default Database procedure doesn’t.
l Restore Factory Defaults deletes any Default-Value file created by the user. “New”
option in the Set a Default Database procedure doesn’t.
l Restore Factory Defaults erases all Log informations; “New” option in the Set a
Default Database procedure doesn’t.
l Restore Factory Defaults reset system time. “New” option in the Set a Default
Database procedure doesn’t.
l Restore Factory Defaults reset the data-structures in the database.
The GE11xPro permits the user to designate the current configuration as the Default
Database or to reset the Default Database to factory defaults using this procedure.
The following procedure includes steps for setting a Default Database using the web-
based GUI. It is also possible to perform this process using CLI. See the FSP
150GE11xPro Command Line Interface Reference Guide for details. The following
procedure also assumes that the user has configured the NE with an IP address and
connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port Using
the Serial Port ) and is logged on using the web-based GUI.
1. Click on the Maintenance icon, or select “Maintenance” from the application drop-
down list.
The display is the Save Configuration to System Defaults view, shown in the
figure below.
4. Click OK.
The display is the Copy To Remote, File Transmit Method view, shown in the
following figure.
7. Click on “OK”, then click on the underlined “here” for HTTP File Transfer.
You are prompted to open or save the file. Select the save option to save the file.
The options presented for file saving are dependent on the browser
being used and the options the user has selected for browser
operation. For example, MS Internet Explorer will prompt for file name
and where the file should be saved, Firefox will save the file with the
default file name ([Link]) to the user’s download folder.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully
downloaded to the system. With this configuration, the system logs
may indicate successful file download, when the browser has not
properly saved the file. The file may be successfully downloaded and
saved by either disabling configuration of File Download Prompting or
disabling pop-up blocking; or using the browser’s pop-up override
capability to allow the file save to complete.
8. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
following figure. (The figure shows the SCP view, the FTP and SFTP views are
identical.)
9. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or SCP
server, has a valid user ID and password and knows the path and file name
of the software file to transfer.
The file transfer will begin, and show a screen similar to the following displays.
When the “Status” changes from “Progress” to “Success”, the file has been
transferred.
10. Expand “Administration”, right click on “Database” and select “Copy from Remote”
The display is the Copy From Remote view, shown in the following figure:
12. Enter the path to the file to restore, or browse to the file location, then click on “OK”.
The file will be copied from the source location and the Detail Pane will indicate
when the file transfer is 100% complete.
13. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
following figure: (The figure shows the SCP view, the FTP and SFTP views are
identical.)
14. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or
SCP server, has a valid user ID and password and knows the path
and file name of the database file to transfer.
The file transfer will begin, and show a screen similar to the following.
The file will be copied from the source location and the Detail Pane will indicate
when the file transfer is 100% complete.
15. Expand “Administration”, right click on “Default Database” and select “New”.
The display is the Save Configuration to System Defaults view, shown in the
figure below.
Resetting the database to factory defaults will drop all traffic and erase
all communications and user settings, including the loss of the web-
based GUI connection to the NE. When using the “New” option
selection, any user uploaded “Default Settings” will be erased. This
operation should not be performed lightly. It may be advisable to
backup the current database so that it can be restored later.
The System resets the Default Database and Active Database to Factory
Defaults.
The following procedure includes steps for performing the database backup process
using the web-based GUI. It is also possible to perform this process using CLI. See the
FSP 150GE11xPro Command Line Interface Reference Guide for details. The following
procedure also assumes that the user has configured the NE with an IP address and
connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port Using
the Serial Port ) and is logged on using the web-based GUI.
1. Click on the maintenance icon, or select “Maintenance” from the application drop-
down list.
The display is the Backup Database view, shown in the figure below.
3. Click on OK, wait a few seconds, then click on “Database” in the selection tree pane
and the Details Pane will show the results of the Back Up operation. See the following
figure:
The display is the Copy to Remote, File Transmit Method view, shown in the
figure below.
6. Click on “OK”, then click on the underlined “here” for HTTP File Transfer.
You are prompted to open or save the file. Select the save option to save the file.
The options presented for file saving are dependent on the browser
being used and the options the user has selected for browser
operation. For example, MS Internet Explorer will prompt for file name
and where the file should be saved, Firefox will save the file with the
default file name ([Link]) to the computer desktop.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully
downloaded to the system. With this configuration, the system logs
may indicate successful file download, when the browser has not
properly saved the file. The file may be successfully downloaded and
saved by either disabling configuration of File Download Prompting or
disabling pop-up blocking; or using the browser’s pop-up override
capability to allow the file save to complete.
7. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
figure below. (The figure shows the SCP view, the FTP and SFTP views are
identical.)
8. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or
SCP server, has a valid user ID and password and knows the path and
file name of the software file to transfer.
The file transfer will begin, and show a screen similar to the following displays.
9. When the “Status” changes from “In progress” to “Success”, the file has been
transferred.
Restore Database
Restoring the database is a multi-step process:
l First, the database file has to be transferred from an external repository to a temporary
location on the NE. The NE supports transfer via HTTP (Web), FTP, SFTP and SCP
protocols.
l Second, the database file must be transferred to standby memory on the NE.
l Third, the database is activated, which causes the NE to reset and temporarily
interrupt traffic and cancel active user sessions.
The following procedure includes steps for performing the database restore process using
the web-based GUI. It is also possible to perform this process using CLI. See the FSP
150GE11xPro Command Line Interface Reference Guide for details. The following
procedure also assumes that the user has configured the NE with an IP address and
connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port Using
the Serial Port ) and is logged on using the web-based GUI.
1. Click on the Maintenance icon, or select “Maintenance” from the application drop-
down list.
2. Expand “Administration”, right click on “Database” and select “Copy from Remote”.
The display is the Copy From Remote view, shown in the following figure:
4. Enter the path to the file to restore, or browse to the file location, then click on “OK”.
The file will be copied from the source location and the Detail Pane will indicate
when the file transfer is 100% complete.
5. Go to 8.
6. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
following figure. (The figure shows the SCP view, the FTP and SFTP views are
identical.)
7. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or SCP
server, has a valid user ID and password and knows the path and file name
of the database file to transfer.
The file transfer will begin, and show a screen similar to the following.
8. When the “Status” changes from “Progress” to “Success”, right click on “Database” in
the selection tree pane and select “Restore Database”. The following screen displays:
9. Click OK, and the screen shows a progress bar. When the restore completes, right
click on “Database” in the selection tree pane, then select “Activate Database”. An
Activate Standby Database” screen displays, as shown in the following figure:
Restore System Defaults may result in the loss of all Provisioning Data Base
settings including DCN, SNMP, Remote Access and User data. This is
normally done only when a system is decommissioned and moved to a new
location or when the software or database is corrupted. It is advisable to
backup the database before performing this procedure.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI in Configuration view.
1. Click on the Maintenance icon, or select “Maintenance” from the application drop-
down list. Right click on “Administration” in the selection tree pane and select “Restore
System Defaults” and the following screen displays:
Resetting the database to system defaults may drop all traffic and erase all
communications and user settings, including the loss of the web-based GUI
connection to the NE. This operation should not be performed lightly. It may
be advisable to backup the current database so that it can be restored later.
Restore Factory Defaults results in the loss of all Provisioning Data Base
settings including DCN, SNMP, Remote Access and User data. This is
normally done only when a system is decommissioned and moved to a new
location or when the software or database is corrupted. It is advisable to
backup the database before performing this procedure.
On GE101Pro and GO102Pro, the user can restore factory default by a long-
press (5 second or longer) of the Reset button, if the button is enabled.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI in Configuration view.
1. Click on the Maintenance icon, or select “Maintenance” from the application drop-
down list. Right click on “Administration” in the selection tree pane and select “Restore
Factory Defaults” and the following screen displays:
Resetting the database to factory defaults will drop all traffic and erase all
communications and user settings, including the loss of the web-based GUI
connection to the NE. This operation should not be performed lightly. It may
be advisable to backup the current database so that it can be restored later.
A “Restore Factory Defaults” deletes all configurations file along with all user
configurations.
The CLI Configuration File contain most configurations, but there some exceptions.
l Loopback Configurations
l Local user and SNMP USM user Configurations
l ESA Schedule Configurations
l Secret information for the Remote Authentication Server
CLI configuration files, when executed (Load function), modify the active database one
line item at a time. These files are managed using CLI commands, web-based GUI or
SNMP. These, or edited versions of these files on an external server, are used to
configure newly installed systems to transition from an installation network to the traffic-
carrying network or to reprovision a system following a database reset to System or
Factory Defaults. The CLI commands for managing configuration files are:
l "Description" on page 436
l "List" on page 434
l "Load" on page 435
l "Remove" on page 436
l "Restart-with-configfile" on page 434
l Save
l "Show" on page 435
l "Transfer File" on page 434
then imported back onto the system. A file can be created, marked for execution upon
system reset, and files can be displayed and deleted.
The CLI Configuration files are kept in persistent memory and survive software upgrades
and ICF database file resets and restorals.
The following give some examples of and uses for the CLI configuration files. The full
syntax for each related CLI command can be found in the FSP 150GE11xPro Command
Line Interface Reference Guide. Included here is a procedure for dealing with CLI
configuration files: CLI Configuration File Procedure.
Below is a sample configuration file. The configuration file parser looks for the first
“remarks” line (lines starting with #) to identify that this is a configuration file and this line
should never be edited, or the file will not be run.
#
#CLI:ESA PROBE-1-1-1-1 Create
#
home
network-element ne-1
configure nte nte114-1-1-1
configure esa
add probe esa_probe-1-1-1-1 "probe1" icmp-echo
access-1-1-1-5 [Link] [Link] [Link]
10min 15 15min 24
configure probe esa_probe-1-1-1-1
vlan-control enabled
vlan-tag 3-4
priority-map dscp
priority 3
packet-per-sample 200
dead-interval 60
response-timeout 10
#
#CLI:ESA REFLECTOR-1-1-1-1 Create
#
home
network-element ne-1
configure nte nte114-1-1-1
configure esa
add reflector esa_reflector-1-1-1-1 "ref1"
access-1-1-1-5 [Link] [Link] dscp 1
#
#CLI:ESA REFLECTOR-1-1-1-2 Create
#
home
network-element ne-1
configure nte nte114-1-1-1
configure esa
#end
home
admin config-file
ADVA:config-file-->
Transfer File
To export or import a configuration file, use the “transfer-file” command:
From the highest level prompt, all configuration file commands are accessed by entering
“admin config-file”. The configuration file “transfer-file” command under “config-file” is:
This command uses the selected file transfer protocol to move a configuration file to (put)
or from (get) a remote server.
List
To list all configuration files, use the “list” command, as in:
ADVA:config-file--> list
|File Name |Description
|--------------------------------|----------------|
|configfile2 |psu and root
|configfile3 |
|configfile4 |
ADVA:config-file-->
The command response shows the filename and the description for the file. The
description can be edited using the “description” command.
Restart-with-configfile
The “restart-with-configfile” command is used to force an immediate system reset, then
execute the designated configfile against the system Default. The basic command is:
Load
To run a configuration file now, use the “load” command, as in:
Show
To view the contents of a configuration file, use the “show ConfigFile” command, as in:
#
#CLI:ACCESS PORT-1-1-1-6 Edit
#
home
network-element ne-1
configure nte NTE114-1-1-1
configure access-port access-1-1-1-6
service-type evpl
#
#CLI:FLOW-1-1-1-6-1 Create
#
home
network-element ne-1
configure nte NTE114-1-1-1
configure access-port access-1-1-1-6
add flow flow-1-1-1-6-1 "testing123" regular-evc
disabled disabled disabled 0 disabled push 1-0 enabled
push 1-0 "2001-*" 1024000
0
#end
home
admin config-file
ADVA:config-file-->
Description
To enter or edit the description of a configuration file, use the “description” command, as
in:
The description can be up to 128 characters long, ASCII with no spaces (unless in
quotes) or question marks. Example:
Remove
To delete a configuration file, use the “remove” command, as in:
remove <configfile-name>
Example:
To support Fiber Service Platform Network Manager (FSPNM), GE11xPro also allows to
manage Configuration File with SNMP. For more information about manging
Configuration File, see FSP 150GE11xPro SNMP User Guide.
save <configfile-name>
The configfile will contain the delta between the default database and the current
active database.
save <configfile-name>
The configfile will contain the delta between the default database and the current
active database and will overwrite the existing file.
list
This command uses the selected file transfer protocol to move a configuration
file to (put) or from (get) a remote server. The IP address of the server, a valid
username, password, and configfile-name are required for either get or put
operations.
load <configfile-name>
ADVA:connectguard:authorizations--> load-configfile
enabled
show <configfile-name>
remove <configfile-name>
20. If configuration changes were implemented using this procedure, verify the changes,
then save the configuration using the Create a Database Backup procedure.
2. Right click on “Configuration Files” and select “Create”. The following screen displays:
The configuration file will contain the delta between the default database and the
current active database.
4. Go to 1.
5. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
6. Select “Save”.
The configfile is updated and contains the delta between the default database
and the current active database and overwrites the existing file.
7. Go to 1.
The details pane shows a table of the existing configuration files including the
file name and description (if any).
9. Go to 1.
10. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
A text editing window opens. Enter the desired description, up to 127 ASCII
characters and click on OK.
12. Go to 1.
13. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
15. Go to 1.
16. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
A Configuration File load status window appears and the load may take a while.
When the loading is completed, the NID will not restart.
18. Right click on “Configuration Files” and select “Copy From Remote”. The following
screen displays:
19. Select the desired protocol and enter the configuration file name:
The selected file transfer protocol is used to move a configuration file from (get)
a remote server. The IP address of the server, a valid username, password, and
configfile-name are required if using FTP, SFTP or SCP protocols.
20. Go to 1.
21. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
Follow the instructions in the detail pane to move the selected configuration file
to the remote location using the selected transfer protocol.
23. Go to 1.
24. Select “Configuration Files” then right click on the menu icon beside the desired
configuration file name in the table inside the details pane. The following screen
displays:
26. Go to 1.
27. If configuration changes were implemented using this procedure, verify the changes,
then save the configuration using the procedure Create a Database Backup.
Installing a Default Settings Value File changes the settings applied when a
new entity or object is created. The Factory Default settings were carefully
vetted to avoid potential serious conflicts in these settings. Changing them
may result in corruption of the database or inability to work with certain
created objects. This procedure should only be done by properly trained
personnel with a file that was tested in a lab to ensure proper operation.
Restore Factory Defaults will erase any user defined Default Settings file.
The following procedure includes steps for performing applying a new Default Settings
file using the web-based GUI. It is also possible to perform this process using CLI. See
the FSP 150GE11xPro Command Line Interface Reference Guide for details. The
following procedure also assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Click on the maintenance icon, or select “Maintenance” from the application drop-
down list.
The display is the Copy System Default Settings From Remote view, shown in
the following figure:
Figure 313: Copy System Default Settings From Remote - Web View
4. Enter the path to the file to copy, or browse to the file location, then click on “OK”.
The file is copied from the source location and the Detail Pane indicates when
the file transfer is 100% complete.
5. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
following figure: (The figure shows the SCP view, the FTP and SFTP views are
identical.)
Figure 314: Copy System Default Settings From Remote - SCP View
6. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or SCP
server, has a valid user ID and password and knows the path and file name
of the database file to transfer.
The file transfer begins, and show a screen similar to the following displays:
The following procedure includes steps for performing the bulk file transfer process using
the web-based GUI. It is also possible to perform this process using CLI. See the FSP
150GE11xPro Command Line Interface Reference Guide for details. The following
procedure also assumes that the user has configured the NE with an IP address and
connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port Using
the Serial Port ) and is logged on using the web-based GUI.
1. Click on the maintenance icon, or select “Maintenance” from the application drop-
down list.
2. Expand “Administration”, right click on “Transfer Log” and select the desired log file to
Transfer (Alarm Log, Audit Log, Security Log).
The display is the Transfer Log view, shown in the figure below. The examples
use the Alarm Log, all others are similar.
4. Click on “OK”.
You are prompted to open or save the file. Select the save option to save the file.
The options presented for file saving are dependent on the browser being
used and the options the user has selected for browser operation. For
example, MS Internet Explorer will prompt for file name and where the file
should be saved, Firefox will save the file with the default file name to the
computer desktop.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully downloaded to the
system. With this configuration, the system logs may indicate successful file
download, when the browser has not properly saved the file. The file may be
successfully downloaded and saved by either disabling configuration of File
Download Prompting or disabling pop-up blocking; or using the browser’s
pop-up override capability to allow the file save to complete.
5. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
figure below. (The figure shows the SCP view, the FTP and SFTP views are
identical.)
6. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or SCP
server, has a valid user ID and password and knows the path and file name
of the software file to transfer.
The file transfer will begin, and show a screen similar to the following displays.
7. When the “Status” changes from “In Progress” to “Success”, the file has been
transferred.
Diagnostics Files
The diagnostics files, including all system inventory information, all system Field
Replaceable Units (including Power Supply Units), current versions of software,
hardware, FPGA and CPLD, running config file output, current database, current alarms
and conditions, alarm log, audit log and security log generated or preserved since system
initialization, can be saved as a ZIP file and copied to a remote repository. The NE
supports transferring the diagnostics files via HTTPS (Web), FTP, SFTP and SCP
protocols. Transferring the diagnostics files requires the user to have Superuser access.
The following procedure includes steps for performing saving the diagnostics files at a
specific time stamp and copying the saved diagnostics file to a remote repository using
the web-based GUI. It is also possible to perform this process using CLI. See the FSP
150GE11xPro Command Line Interface Reference Guide for details. The following
procedure also assumes that the user has configured the NE with an IP address and
connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port Using
the Serial Port ) and is logged on using the web-based GUI.
1. Click on the maintenance icon, or select Maintenance from the application drop-down
list.
2. Expand Administration, right click on Diagnostics Files and select Save in the
Selection Tree pane.
3. Click on OK.
5. Click Diagnostics Files in Selection Tree pane to view the Status and Date of Existing
Diagnostics Files in the Detail pane.
6. Enter a right click on Diagnostics Files in Selection Tree pane and select Copy to
Remote.
8. Click on “OK”.
You are prompted to open or save the file. Select the save option to save the file.
The options presented for file saving are dependent on the browser
being used and the options the user has selected for browser
operation. For example, MS Internet Explorer will prompt for file name
and where the file should be saved, Firefox will save the file with the
default file name to the computer desktop.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully
downloaded to the system. With this configuration, the system logs
may indicate successful file download, when the browser has not
properly saved the file. The file may be successfully downloaded and
saved by either disabling configuration of File Download Prompting or
disabling pop-up blocking; or using the browser’s pop-up override
capability to allow the file save to complete.
9. For “File Transfer Method” select FTP, SFTP or SCP from the drop-down list.
The display changes to the FTP, SFTP or SCP file transfer view, shown in the
figure below. (The figure shows the SCP view, the FTP and SFTP views are
identical.)
10. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process (See the following figure on how the required data for
SCP transfer are correctly provisioned.), and click on OK.
11. When the “Status” changes from “In Progress” to “Success”, the file has been
transferred.
This Chapter contains communications provisioning information and procedures for the
FSP 150GE11xPro. An example scenario of GNE to SNE communications is provided
along with provisioning details. This section contains the following communications
procedures:
l Serial Connection
l Set Up the GE11xPro DCN (eth0) Port Using the Serial Port
l Set Up the USB Modem Using the Serial Port
l Set up WiFi Connection via the Wifi Dongle
l Browser-based IP Connection
l Edit DCN (eth0) Configuration
l Configure Management Tunnel
l Configure IPv6 over IPv4 Tunnel
l Configure Source Address
l Add/Delete Static Route
l Add/Delete Static ARP Entry
l Add/Delete IPv6 Static Route
l Add/Delete IPv6 Static Neighbor Entry
l Add/Delete IPv6 Static Proxy ND Entry
l Configure Access Control List
l Configure USB Modem Using the Web-based GUI
l Sample Network - GNE to SNE over Management Tunnel
Provision Communications
The GE11xPro supports several management configurations and options. This section
does not provide typical deployment scenarios of the GE11xPro in common IP network
configurations as there are simply too many different network configurations in common
use as to be practical.
Additionally, most entities deploying the product have network administrators who either
do the provisioning or provide work orders with provisioning details. This section also
does not provide a comprehensive explanation of IP networking concepts.
The factory default settings for the GE11xPro provide for connecting the MGMT LAN
(DCN) RJ45 connector to the local/remote DCN. This interface (eth0) is preconfigured by
factory defaults with DHCP in client mode and the DHCP disabled.
The user can ascertain quickly the status of the DCN by using the RS-232 serial port to
query the NE for the DCN settings. This same interface can be used to enable DHCP or
set the IP address of the eth0 interface if DHCP is not used on the DCN.
The user has the option of deploying the unit with settings other than the factory defaults
and/or establishing a system default database (see Database and Configuration Files)
with user specified DCN settings or configuring a management tunnel on one or more
Network or Access Ports.
The system also supports Management Traffic Bridging, which implements an Ethernet
Bridge between the Management LAN (eth0) and all configured Management Tunnels.
This allows having only a single IP address for all management interfaces on the system
and eliminates the need for static routes, routing protocols or proxy ARP in an SNE/GNE
configuration. The Ethernet Bridge functionality supports MAC learning and flooding of
un-learned MAC addresses. If Management Traffic Bridging is Enabled (see Table 56 on
p. 788), management tunnels do not support provisioning for IP Address, Subnet Mask,
DHCP or RIP. Another system level option, Management Traffic Bridging Security, limits
acceptance of DCN packets to those with source MACs containing an ADVA Optical
Networking OUI. Management Traffic Bridging also facilitates the use of a Hot Sparing
configuration.
A valid IP address for the Management LAN Interface is required when connecting via the
DCN. Although the GE11xPro is shipped with a default IP address loaded ([Link] /
24), the default is the same for each unit. To ensure a reliable connection to the
GE11xPro, the IP address of the Management LAN Interface should first be configured to
a unique address compatible with the network it is on. This is usually performed
automatically by using DHCP or manually by making a serial connection to the
GE11xPro and performing IP Configuration during installation. See Serial Connection for
further details.
The use of a PC or Laptop running Microsoft (MS) Windows and the terminal
emulation program detailed in this section are used as illustrations only.
Other terminal emulation programs, run on a preferred platform may be used
instead. For more information contact ADVA Optical Networking Technical
Support using the contact details given in the Preface, Technical Support.
It is outside of the scope of this document to describe the use of any com-
puter operating system, terminal emulation program or Internet browser,
either recommended or otherwise. If further details are required on the use of
a particular program, please refer to the documentation supplied with it.
When using the local password file for user authentication a login account is
locked for a period of 5 minutes after 3 unsuccessful login attempts.
Serial Connection
Information on using CLI commands utilizing the serial port are found in the FSP
150GE11xPro Command Line Interface Reference Guide.
1. Ensure that a physical serial connection from a PC or Laptop to the GE11xPro RS-232
connector (For GE101Pro and GO102Pro, the micro USB Port) has been established
(see “Serial Console Port Connection” in FSP 150GE11xPro Installation and
Commissioning Manual document).
2. Start a serial terminal emulation program (e.g. Tera Term Web) to establish a
connection.
4. Set the communication settings of the terminal emulation program to the following:
l 9600 baud
l 8 data bits
l no parity bit
l 1 stop bit
l No flow control
Login:
ADVA-->
Perform the following procedure to set up the GE11xPro DCN (eth0) port (MGMT LAN)
using the RS-232 Serial Port on the GE11xPro (RS 232) and the CLI command structure.
(For more information on the CLI command structure, see the FSP 150GE11xPro
Command Line Interface Reference Guide.)
The default DHCP setting for the GE11xPro DCN port is disabled and as a DHCP
client.
This procedure is offered as the best way to set up the GE11xPro IP address using the
CLI command structure by connecting to the RS-232 Serial Console Port (RS 232 on the
GE11x) and your PC. If a DHCP server is not available for the DCN port, then DHCP
must be disabled. Note that by default, DHCP is disabled on the DCN, and as a DHCP
client.
The IP addresses and Subnet Masks entries shown in these procedures are for example
purposes only. The information you enter should be determined from local sources.
1. Connect a serial cable between the GE11xPro RS-232 Serial Port and a PC and logon
using procedure: Serial Connection.
2. Enter the show ip-interface eth0 command to view the current DHCP setting for the
DCN interface on the GE11xPro. See the following example:
4. Enter the configure communication command. A next level prompt appears. Then
enter configure eth0 dhcp-control enabled or dhcp-control disabled to set the
desired DHCP state. For example:
7. Enter the configure communication command. A next level prompt will appear. For
example:
8. Enter configure eth0 followed by a valid IP address, network mask and default
gateway for the DCN network the NE will be connected to. For example:
11. Enter the show system command and verify that HTTP and HTTPS are enabled.
13. Enter the following highlighted CLI commands to enable both HTTP and HTTPS.
ADVA:comms--> home
ADVA--> configure system
ADVA:system--> http enabled
ADVA:system--> https enabled
14. Go to 11
15. Use an Ethernet cable to connect the MGMT LAN RJ-45 connector to the network
DCN.
16. Open a browser window and use the configured IP address to access the NE.
18. Enter a valid login User ID and Password. The default login and password are ‘root’
and ‘ChgMeNOW,’ respectively. The security banner will then be displayed.
19. Click on the “Continue” button, and a display similar to the following will appear.
20. From the “File” menu, select “Logout”, and verify that the browser shows the Login
screen.
21. Return to the serial port session and logoff by entering quit. See the following example
ADVA:comms--> quit
Logged Out
Login:
22. Disconnect the serial cable from the RS 232 connector on the GE11xPro.
23. Use an Ethernet cable to connect the MGMT LAN RJ-45 connector to the network
DCN.
24. Enter the show ip-interface eth0 command to view the current DHCP setting for the
DCN interface on the GE11xPro. See the following example:
26. Enter the show system command and verify that HTTP and HTTPS are enabled.
28. Enter the following highlighted CLI commands to enable both HTTP and HTTPS.
ADVA:comms--> home
ADVA--> configure system
ADVA:system--> http enabled
ADVA:system--> https enabled
29. Go to 26
30. Open a browser window and use the configured IP address to access the NE.
32. Enter a valid login User ID and Password. The default login and password are ‘root’
and ‘ChgMeNOW,’ respectively. The warning banner will then be displayed.
33. Click on the “Continue” button, and a display similar to Figure 1 appears.
34. From the “File” menu, select “Logout”, and verify that the browser shows the Login
screen.
35. Return to the serial port session and logoff by entering quit. See the following example
ADVA:comms--> quit
Logged Out
login:
36. Disconnect the serial cable from the RS 232 connector on the GE11xPro.
Perform the following procedure to set up the USB modem port using the RS-232 Serial
Port on the GE11xPro and the CLI command structure. (For more information on the CLI
command structure, see the FSP 150GE11xPro Command Line Interface Reference
Guide.)
The default DHCP setting for the GE11xPro DCN port is disabled and as a DHCP
client.
The CLI entries shown in these procedures are for example purposes only. The
information you enter should be determined from local sources. At the finish of the
procedure, the USB modem gets into in-service state and connects itself to the local
wireless network with the credential provided. Please consult the FSP 150GE11xPro
Command Line Interface Reference Guide for the details for running each command.
1. Connect a serial cable between the GE11xPro RS-232 Serial Port and a PC and log in
using procedure: Serial Connection.
ADVA-NE-1:usb_dcn-1-1-1-1-->
6. Run user-name command to enter the user name for wireless connection.
ADVA-NE-1:usb_dcn-1-1-1-1-->password ***********
ADVA-NE-1:usb_dcn-1-1-1-1-->
9. Navigate to the Communication level and run show usb-dcn command. If the USB
DCN port has obtained an IP address, the wireless connection is ready.
ADVA-NE-1:usb_dcn-1-1-1-1--> home
ADVA--> configure communication
ADVA:comms--> configure usb-dcn
ADVA:comms:usb-modem--> show usb-dcn
MTU : 1500
IP Address : [Link]
Subnet Mask : [Link]
Primary DNS : [Link]
Secondary DNS : [Link]
10. Connect to the device with the IP address on CLI, SNMP or GUI.
11. Go to 3.
12. Run enable-pin command to enable PIN Authentication. Once PIN Authentication
is enabled, user needs to run pin-aunthenticaion command to get the
authentication to access the USB Modem.
13. Go to 3.
14. Run disable-pin command to disable pin authentication. Once PIN authentication
is disabled, the user doesn’t need to run pin-aunthenticaion to access the USB
Modem.
15. Go to 3.
16. Run unlock-pin command to unlock the SIM and set a New PIN. This command
should only be run in the case where the PIN has been incorrectly entered 3 times.
17. Go to 3.
The following procedure assumes that the WiFi Dongle has been installed, either directly
into the USB port or through a USB cable (if required). (Use this procedure for DCN
connection backup purpose when the DCN (eth0) port is disabled or the DCN connection
is unavailable, and when the system is not working in management traffic bridging mode.)
WiFi Dongle IP Interface can coexist with the DCN (eth0) IP Interface. When
they are both in assigned state, their IP Addresses cannot be in the same
subnetwork.
Perform the following procedure to set up the WiFi Connection using the RS-232 Serial
Port on the GE11xPro and the CLI command structure. (For more information on the CLI
command structure, see the FSP 150GE11xPro Command Line Interface Reference
Guide.)
The default DHCP setting for the GE11xPro DCN port is disabled and as a DHCP
Client.
The CLI entries shown in these procedures are for example purposes only. The
information you enter should be determined from local sources. At the finish of the
procedure, the WiFi Dongle gets into in-service state and allows PC to connect to itself
via the free WiFi network with the credential provided. Please consult the FSP
150GE11xPro Command Line Interface Reference Guide for the details for running each
command.
1. Connect a serial cable between the GE11xPro RS-232 Serial Port and a PC and logon
using procedure Serial Connection.
3. Enter the delete mobile-modem command to delete the default mobile modem
entity.
Since the WiFi Dongle has been plugged in the USB Port and a default
Mobile Modem entity exists under USB Port, a “Modem Mismatch” alarm will
be raised. The “Modem Mismatch” alarm can be cleared by deleting the
default Mobile Modem entity.
6. Edit the WiFi Dongle settings and set the admin-state to In-Service as desired.
ADVA-NE-1:nte112pro_h-1-1-1:wifi_dongle-1-1-1-1-->
admin-state in-service
If the WiFi Dongle is plugged out when the Administrative State has
been provisioned to In-Service, a “Modem Removed” alarm will be
raised. This alarm can be cleared by plugging the WiFi Dongle back
into the USB Port or changing the WiFi Dongle’s Administrative State
to Unassigned.
7. Enter the show wifi-dongle command to view the current settings for the WiFi
Dongle.
Name : wlan0
Alias :
Admin State : in-service
Operational State : normal
Secondary States : act
SSID : iron's wifi
dongleioioioijju216
Encryption method : wpa-wpa2-psk
Password : ChgMeNOW
9. Edit the WiFi Dongle settings as desired and enter the show wifi-dongle
command to view the settings.
Name : wlan0
IP Address : [Link]
Subnet Mask : [Link]
DHCP Role : dhcp-server
Allocated IP Address Start : [Link]
Allocated IP Address End : [Link]
Accessed Users : [Link]
[Link]*[Link] [Link]
11. Proceed to connect to the Wifi network by entering the Security Key as required.
12. Open a browser window and use the IP Address configured above to access the
GE11xPro.
Browser-based IP Connection
This procedure details the steps used to access a web-accessible GE11xPro (HTTP
and/or HTTPS enabled) using a web browser on a PC with connectivity to the DCN or
USB modem the GE11xPro is connected to.
To make an Ethernet DCN connection to the GE11xPro, perform the following steps:
1. Ensure that a unique IP address has been configured for the GE11xPro’s Management
Interface or USB modem, See Set Up the GE11xPro DCN (eth0) Port Using the Serial
Port or Set Up the USB Modem Using the Serial Port.
2. Ensure that a physical Ethernet connection from the DCN PC to the GE11xPro has
been established or the USB modem/Wifi Dongle is provisioned and operational.
3. Verify the user’s PC IP address and netmask match the values provided by the
Network Administrator, so that it has access to the network the GE11xPro is on.
a) Open up the appropriate Internet browser and enter the following address:
[Link]
or
[Link]
where [Link] is the IP address of the GE11xPro to be
connected to. This will be the IP address that has been assigned to the
GE11xPro during initial IP configuration (if none has been set, the default
address is [Link]).
The Web Interface will open and the Login Screen will be displayed.
b) Login with the following details:
• Account name - root (or as appropriate, see "Provision Secure
Access" on page 127).
• Password - ChgMeNOW (or as appropriate).
Security details will also be displayed on the screen.
c) Press Continue.
The Web Interface GE11xPro Main Menu will be displayed, as described
in Chapter 3, Web-based Element Management System.
The factory default settings are with the DHCP (v4 & v6) disabled in the client role with
RIPv2/RIPng disabled.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI. For more information
on the configuration settings and rules, see DCN (eth0) (Edit Configuration).
1. Right click on “DCN (eth0)” and select Edit Configuration. The following “Edit DCN
(eth0)” screen displays.
Enable/Disable RIPv2
Click on OK
In order for the new IP Address and DHCP server function (IP Address
range) to become active, DHCP Control must be cycled.
Enable/Disable RIPng
Select the checkbox next to Edit System Default and Enter the Gateway IPv6
Address
Click on OK
6. Go to 3
Enable/Disable RIPv2
Select/Enter the following DHCP options that are only applicable in IPv4 mode:
Enable/Disable RIPng
Select the Edit System Default checkbox if desired, and enter the desired
Gateway IPv6 Address
Click on OK
9. Go to 3
Enable/Disable RIPv2
Select the Edit System Default Gateway checkbox if desired, and enter the
desired Gateway IPv4 Address
Enter the desired IPv6 Unicast Address if Stateless Address Auto Configuration
is Disabled
Enable/Disable RIPng
Enter a desired IPv6 RA Prefix (only editable when Stateless Address Auto
Configuration is Disabled)
Select the Edit System Default Gateway checkbox if desired, and enter the
desired Gateway IPv6 Address
Click on OK
12. Go to 3
Click on OK
14. Go to 3
Click on OK
16. Go to 3
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
From the Configuration view with the Communications and Management Tunnels entities
expanded:
3. Right click on “NE-1” in the selection tree pane under “Management Tunnels”, select
Create Tunnel and the following screen displays:
(see Management Tunnel Configuration Options and Rules for details on each
item.)
Identification
Associated Port - select from drop-down list - only one tunnel per port
Interface
IPv4 Networking
Edit (if desired) DHCP Client ID if the selected DHCP Client ID Type is User
Defined (only available if DHCP Client ID Control is Enabled) (not applicable for
PPP)
Select a desired DHCP Host Name Type (not applicable for PPP)
Edit (if desired) DHCP Host Name if the selected DHCP Host Name Type is
User Defined.
Select a desired DHCP Vendor Information Type (not applicable for PPP)
Edit (if desired) DHCP Vendor Information if the selected DHCP Vendor
Information Type is User Defined.
IP Address - valid IPV4 address if IP Mode is IPv4 Only or IPv4 and IPv6 and
when DHCP is Disabled (not applicable for PPP)
Subnet Mask - valid IPV4 mask if IP Mode is IPv4 Only or IPv4 and IPv6 and
when DHCP is Disabled (not applicable for PPP)
Select the checkbox next to Edit System Default Gateway if DHCP is disabled.
IPv6 Networking
Enter a desired IPv6 Unicast Address when DHCPv6 and Stateless Address
Auto Configuration are both Disabled (not applicable for PPP)
Enter a desired IPv6 RA Prefix for IPv6 Route Advertise when IPv6 RA Prefix
Enabled is Enabled (not applicable for PPP)
Select the checkbox next to Edit System Default Gateway when either or both
of DHCPv6 and Stateless Address Auto Configuration is Disabled
Layer 2 Configuration
IPv4 RIP
IPv6 RIP
Bandwidth
CIR - 64000 to 8000000 bps - default is 256000 bps (Max of 8 Mbps for all
management tunnels combined)
COS - 0 to 7 - default is 7
Click on OK
5. Expand the NE-1 entity under Management Tunnels, left click on the management
tunnel ID and verify the data entered. (see Figure 7 on p. 483)
Click on OK.
7. Go to Step 1.
8. To delete a management tunnel, right click on the management tunnel ID and select
Delete (see the following figure).
Click on OK.
10. Right click on “NE-1” in the selection tree pane under “Management Tunnels”, select
Create Tunnel and the following screen displays:
(see Management Tunnel Configuration Options and Rules for details on each
item.)
Identification
Associated Port - select from drop-down list - only one tunnel per port
Interface
Layer 2 Configuration
Bandwidth
CIR - 64000 to 8000000 bps - default is 256000 bps (Max of 8 Mbps for all
management tunnels combined)
COS - 0 to 7 - default is 7
Click on OK
12. Expand the NE-1 entity under Management Tunnels, left click on the management
tunnel ID and verify the data entered. (see figure below)
13. If anything in the Configuration data requires modification, right click on the
management tunnel ID and select Edit Configuration (see the following figure):
Click on OK.
14. Go to Step 1.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN, (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
From the Configuration view with the Communications and IPv6 over Tunnels entities
expanded:
2. Right click on “NE-1” in the selection tree pane under IPv6 over IPv4 Tunnels, select
“Create Tunnel” and the following screen displays:
3. Enter/Select the following data to configure the IPv6 over IPv4 tunnel:
(see IPv6 over IPv4 Tunnel Configuration Options and Rules for details on each
item.)
Identification
Associated IPv4 Interface - select from drown-down list - one IPv4 management
interface
Tunnel
Mode - select a desired tunnel mode - Configured, Auto 6o4, IPv4 Compatible, or
ISATAP
Click on OK.
5. Go to 1.
6. Expand the NE-1 entity under IPv6 over IPv4 Tunnels, click on the IPv6 over IPv4
Tunnel ID and verify the data entered.
7. To delete an IPv6 over IPv4 Tunnel, right click on the tunnel ID and select Delete.
Click on OK.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN, (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
1. Right click on “Communications” in the selection tree pane, select Edit Source
Address Config and the following screen displays (see the following figure):
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
2. Right click on “Communications” in the selection tree pane and select Add Static
Route and the following screen displays (see the following figure):
Interface Name - Select desired Interface Name from the drop-down list.
Metric - 0 to 65535
Click on OK
4. Go to Step 1
5. Left click on “Communications” and select the “Static Routes” tab. (see Figure 18)
6. Go to Step1
7. To delete a Static Route, right click on Communications and select “Delete Static
Route” (see the following figure):
Click the radio button in the “Delete” column for each route to be deleted.
Click on OK.
8. Go to Step 1.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
2. Right click on “Communications” in the selection tree pane and select Add Static
Route and the following screen displays (see the following figure):
MAC Address
Interface Name - Select desired Interface Name from the drop-down list.
Click on OK.
4. Go to Step 1.
5. Left click on “Communications” and select the “Static ARP Entry” tab. (see the
following figure)
6. Go to Step 1.
7. To delete a Static ARP Entry, right click on Communications and select “Delete Static
ARP Entry” (see the following figure):
Click the radio button in the “Delete” column for each ARP entry to be deleted.
Click on OK.
8. Go to Step 1.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
2. Right click on “Communications” in the selection tree pane and select Add IPv6 Static
Route and the following screen displays (see the following figure):
3. Enter/select the following data to create a static route: (see IPv6 Static Route (Add
IPv6 Static Route) for details on each item.)
Interface Name - Select desired Interface Name from the drop-down list, by
default the management interface in IPv6 mode will automatically appear for
selection.
Click on OK
4. Go to Step 1
5. Left click on “Communications” and select the “IPv6 Static Routes” tab. (see Figure
24)
6. Go to Step1
7. To delete an IPv6 Static Route, right click on Communications and select “Delete
IPv6 Static Route” (see the following figure):
Click the radio button in the “Delete” column for each IPv6 route to be deleted.
Click on OK.
8. Go to Step 1.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
2. Right click on “Communications” in the selection tree pane and select Add IPv6 Static
Neighbor Entry and the following screen displays (see the following figure):
3. Enter/select the following data to create an IPv6 Static Neighbor Entry: (seeIPv6
Static Neighbor Entry (Add IPv6 Static Neighbor Entry) for details on each item.)
MAC Address
Interface Name - Select desired Interface Name from the drop-down list. By
default, a management tunnel configured with IPv6 address will appear for
selection.
Click on OK.
4. Go to Step 1.
5. Left click on “Communications” and select the “IPv6 Static Neighbor Entry” tab. (see
the following figure)
6. Go to Step 1.
7. To delete an IPv6 Static Neighbor Entry, right click on Communications and select
“Delete IPv6 Static Neighbor Entry” (see the following figure):
Click the radio button in the “Delete” column for each IPv6 static neighbor entry
to be deleted.
Click on OK.
8. Go to Step 1.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN. (See Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on using the web-based GUI.
2. Right click on “Communications” in the selection tree pane and select Add IPv6 Static
ProxyND Entry and the following screen displays (see the following figure):
3. Enter/select the following data to create an IPv6 Static Proxy ND Entry: (see IPv6
Static Proxy ND Entry (Add IPv6 Static Proxy ND Entry) for details on each item.)
Interface Name - Select desired Interface Name from the drop-down list. By
default, a management tunnel configured with IPv6 address will appear for
selection.
Click on OK.
4. Go to Step 1.
5. Left click on “Communications” and select the “IPv6 Static ProxyND Entry” tab. (see
the following figure)
6. Go to Step 1.
7. To delete an IPv6 Static Proxy ND Entry, right click on Communications and select
“Delete IPv6 Static ProxyND Entry” (see the following figure):
Click the radio button in the “Delete” column for each IPv6 static proxy ND entry
to be deleted.
Click on OK.
8. Go to Step 1.
When the primary management connection is in service and working, and SNMP is
provisioned, GE11x reports its public IP address acquired from the 3G/4G/LTE service
provider to a Network manager via the primary management connection (DCN). If the
primary management connection fails, management communications may be made to
the GE11x via a public 3G/4G/LTE network.
The following is a procedure for provisioning a USB modem to enable the wireless
connection to a GE11x using the web-based GUI. If there is no DCN connected and only
a USB DCN is provided for this GE11x, refer to Set Up the USB Modem Using the Serial
Port to provision the USB DCN port using CLI commands.
Note that the terms “USB DCN” and “USB modem” will be used in the following
provisioning procedures, instead of repeatedly emphasizing the specific wireless network
type.
1. Select Configuration view. Expand the System Name, NE-1 and NTE11x entities in
the Selection Tree.
3. Right click on the USB Modem entity and select Edit Configuration. The following
screen displays.
4. Fill in the Alias as appropriate. Select “IS” for Administrative State. The Modem
information and Physical Configuration information will display automatically once the
USB modem is plugged in. Enter the Dial-Up Configuration. Click on OK.
5. Left click on “USB Modem” under NTE11x. Verify the data entered and observe the
SIM status by selecting the corresponding tab (see the following two figures). Refer to
Table 10 for SIM status result descriptions. The SIM status will be used in the next
step.
6. Use the SIM status information from the previous step to determine the next step.
7. To enable USB Modem PIN, right click on the USB Modem entity and select “Enable
PIN”. The following screen displays.
When the PIN is Enabled, if the USB Modem is unplugged or the system
reboots, the USB Modem SIM must be unlocked by entering the PIN upon
each occurrence.
9. Go to 5 to observe the current configuration and SIM status to determine the next step.
10. To disable USB Modem PIN, right click on the USB Modem entity and select “Disable
PIN”. The following screen displays.
USB Modem SIM will not be locked if the PIN is disabled. Once the
PIN is disabled, the operations such as Change PIN, PIN
Authentication, Unlock with PUK are disabled.
12. Go to 5 to observe the current configuration and SIM status to determine the next step.
13. To change the USB Modem PIN, right click on the USB Modem entity and select
“Change PIN”. The following screen displays.
14. Enter the current PIN and the new PIN; then repeat the new PIN to confirm the input.
Click OK.
The new PIN setting takes effect at the next time when the user is required to
enter the PIN.
15. Go to 5 to observe the current configuration and SIM status to determine the next step.
16. To unlock the SIM by PIN authentication, right click on the USB Modem entity and
select “PIN Authentication”. The following screen displays. Note the number of
remaining (failed) attempts indicated.
If PIN is Enabled and the USB Modem is unplugged or the system reboots,
the USB Modem will be locked and the user will need to re-enter PIN
authentication. If the PIN input fails after three attempts to authenticate PIN,
the USB Modem SIM will still be locked - and the SIM will need to be
unlocked by entering PUK and a new PIN (19).
18. Go to 5 to observe the current configuration and SIM status to determine the next step.
19. If a user fails to unlock the SIM via PIN after three failed attempts, the SIM needs to
be unlocked with PUK. Enter a right click on the USB Modem entity and select
“Unlock with PUK”. The following screen displays.
20. Input PUK and the New PIN; then repeat the new PIN to confirm the input. Click OK.
If PUK input fails to unlock SIM after 10 attempts, contact the wireless ISP
to unlock the SIM.
21. Observe the cellular networking information by expanding the Communications entity
under System and selecting “USB DCN”.
22. To verify connection to the GE11x via the cellular networking IP address, continue
with the next step. Otherwise, go to 5 to observe the current configuration and SIM
status to determine the next step.
23. To verify the connection to the GE11x via the cellular Networking IP address, open a
new web browser window, enter the IP address in the address bar of your Web
browser and log onto the GE11x.
The Figure below shows an example of back-to-back GE11xPros where the the web-
based GUI workstation, Gateway NE (GNE) and Subtending NE (SNE) are on the same
subnet, and WAN connectivity between GE11xPros is via a management tunnel.
GE11xPro #1 and the Workstation reside on LAN Segment A. GE11xPro #2 has no
management LAN connection, and has a WAN management tunnel connection to
GE11xPro #1.
You should currently be logged onto the GE11xPro #2’s RS232 (serial port)
using CLI.
2. Provision the eth0 (system) IP address using the following CLI command entry
4. To edit the management tunnel to enable RIPv2 packets, enter the following CLI
command.
5. Set the Management LAN Port’s (eth0) Admin state to unassigned using the following
CLI command.
ADVA:comms:mgmt_tnl-1--> home
ADVA-NE-1:dcn-1-1-1-1--> home
6. Add a static route to point to the management tunnel on GE11xPro #1 using the
following CLI command
7. Enter a “show system” and verify that Proxy ARP is disabled. If Proxy ARP is
enabled, enter the following command, otherwise continue to the next step
ADVA:comms--> home
Ensure that the Proxy ARP option is set correctly for the GE11xPro. If
two or more ADVA Optical Networking NEs or GE11xPros are
connected via SDCC or Management Tunnel as well as connected to
the same LAN segment, then only one of the them should have the
Proxy ARP option enabled. Otherwise, there will be multiple ARP
responses for a single ARP request for a remote reachable IP address
from each NE/GE11xPro in the same LAN that has Proxy ARP
enabled.
8. Logoff the CLI session and remove any commissioning cables (Ethernet cable and/or
console cable) from the GE11xPro front panel connectors, as required.
9. Connect the optical cables to the GE11xPro Network Port front panel connectors if
they are not already connected.
You should currently be logged onto the GE11xPro #1’s RS232 (serial
port) using CLI.
13. Provision the eth0 (system) IP address using the following CLI command entry
ADVA:comms:mgmt_tnl-1--> home
.ADVA:comms--> home
Ensure that the Proxy ARP option is set correctly for the GE11xPro. If
two or more ADVA Optical Networking NEs or GE11xPros are
connected via SDCC or Management Tunnel as well as connected to
the same LAN segment, then only one of the them should have the
Proxy ARP option enabled. Otherwise, there will be multiple ARP
responses for a single ARP request for a remote reachable IP address
from each NE/GE11xPro in the same LAN that has Proxy ARP
enabled.
15. Logoff the CLI session and remove any commissioning cables (Ethernet cable and/or
console cable) from the GE11xPro front panel connectors, as required.
16. Ensure the DCN connection for LAN Segment A is connected to the MGMT LAN
(eth0) port.
17. Connect the optical cables to the GE11xPro Network Port front panel connectors if
they are not already connected.
18. Observe the Network Port Net and Act LEDs on the front panel. They should be lit
green. If the LEDs are not lit green, then troubleshoot the connections between
GE11xPro #1 and GE11xPro #2.
19. Depending on your configuration, either set the web-based GUI workstation default
gateway to point to the GNE GE11xPro’s Management LAN port IP address, or create
a static route on the PC to communicate to the SNE (e.g., from Windows command
20. Verify connectivity to GE11xPro #1 and GE11xPro #2 from the web-based GUI
Workstation. Open a web browser window (Internet Explorer(IE 11 recommended) or
an up-to-date version of Firefox or Chrome) and enter the IP address of GE11xPro #1
to access the GE11xPro web-based Element Management System. Logon using a
valid user name and password. The default login and password are ‘root’ and
‘ChgMeNOW,’ respectively. Repeat for GE11xPro #2.)
Introduction
This chapter contains information and procedures for the following Etherjack® and
Syncjack® testing features.
l Loopbacks
l Etherjack® Diagnostics
l Cable Length Benchmarks
l Performance Monitoring
l ESA Provisioning and Operation
l CFM Provisioning and Operation
l Etherjack® Connection Performance Analyzer
l Service Activation Testing
l SyncJack Testing - GE114Pro (SH)/GE114Pro (CSH)
l Two-Way Active Measurement Protocol
Loopbacks
To assist with Ethernet service fault isolation and to support Service Level Agreement
(SLA) conformance verification, the system supports Port, VLAN, and EFM-OAM
message loopback modes on all Ethernet traffic carrying ports (see Note). The
Loopbacks allow the user to setup an Ethernet test set at a central location to inject traffic
into the network.
As shown in the example in following figure, traffic is looped back into the network and
back to the test-set. The test-set can look for any anomalies such as frame loss or out-of-
sequence frames. The loopback eliminates the need to connect a test-set in the field or at
the customer premise to verify round-trip service.
CO Based
Test Head
Loopback Loopback
Test Pattern 2 Test Pattern 1
Four basic types of loopback are available: Port, VLAN, and Ethernet First Mile (EFM)-
Operation, Administration and Maintenance (OAM). The following loopback functions are
available:
l EFM-OAM Remote
l EFM-OAM Remote Timed
l Facility Port
l Facility Port Timed
l Facility VLAN
l Terminal Port
l Terminal Port Timed
l Terminal VLAN
From this view, the Network Port or Access Port facility can be placed in the
Maintenance state and a loopback or timed loopback can be performed at the terminal or
facility. If performing a terminal or facility VLAN loopback, up to three VLAN Loopbacks
may be created per entity. Port Loopbacks ignore traffic shaping, allowing use of the full
port bandwidth, while VLAN Loopbacks conform to configured shaping profiles.
MAC Address matching for Loopback extends existing port and VLAN loopbacks to
loopback only service frames from a specified source and/or with specified destination
MAC address. The existing loopback types will continue to be supported, and the MAC
Address filter option is only available for terminal loopback types on the GE11x
[Link] prevent service frames from interfering with loopback testing, service frames
matching the port/vlan of the loopback should be dropped (i.e., Blocked) or optionally
allowed to pass. As with Loopback attributes, the MAC Address Match configuration
cannot be modified on an active loopback.
Selecting the Swap SADA [Swapping the Source Address (SA) with the Destination
Address (DA)] option during the loopback directs the GE11xPro to look up the MAC
address of frames being received and swap out the Source Address with the Destination
Address, allowing the Layer 2 cloud to forward the frames.
A blocking mechanism is provided to prevent service frames from being forwarded, when
the service frame matches the signature of the loopback frames. This functionality will
continue to be provided as a configurable option: block or no-block.
Only one Terminal/Facility loopback may be performed per system, and multiple EFM-
OAM Loopbacks may be performed meanwhile for different remote terminals. Once a
VLAN and/or Swap SADA loopback has been operated, a second Swap SADA loopback
may not be performed on another entity.
If Facility Port Timed or Terminal Port Timed is selected, the Timer is set by the user for
10 to 300 seconds (the duration of the loopback).
See the following figure for an example of a loopback view. For a description of the web-
based Element Management System GUI functions, see Chapter 2, Web-based Element
Management System. For a list of loopback setting options, rules, and associated default
settings, see Loopback Settings.
To remove a loopback, click on the drop-down list for Loopback Configuration and select
“None”, then click on “OK”.
For more information regarding loopback operation overview, see FSP 150-GE11xPro
System Description document.
Etherjack® Diagnostics
On a terminated cable, the energy of the signal pulse is absorbed by the terminating
device. Little or no energy is reflected back to the originating transceiver. This means the
length of a terminated cable cannot be determined.
However, if the cable is not terminated, when the signal pulse is transmitted the energy is
reflected back towards the transmitter from the point of the open circuit. By measuring
the phase variation between the transmitted and reflected pulses, the system can
determine the distance from the transmitter to the open circuit fault to within 1 meter.
Similarly, a short circuit between any of the wires in a loop can be detected. In this case,
it is also possible to measure the distance from the transmitter to the short circuit fault to
within 1 meter by analyzing phase delay characteristics.
Before starting Diagnostic Test at one end of a link, make sure Auto
Diagnostic is disabled at the other end. Otherwise the test results are
incorrect.
Tests are started automatically on detection of a link fault, but they can also be started
manually using the web-based GUI. Refer to the following figure for an example
Etherjack® Diagnostic Test result using the web-based GUI.
1. Ethernet Cable Test. Cable faults can be isolated to within +/- 1 meter resolution
along the cables length, for each cable pair. The test can detect the presence of:
o open circuits
o short circuits
o impedance mismatches
The capabilities of the Ethernet Cable Test can be enhanced by using Cable
Length Benchmarking. See Cable Length Benchmarks.
2. Ethernet Auto-Negotiation Test. During this phase, the speed and duplicity of the
Ethernet link is negotiated. This test also performs auto-MDIX for crossover detection
and adaptation.
3. Ethernet EFM Loopback Test. On this phase the far-end is placed on EFM loopback
mode to perform traffic testing over the link. As with the Ethernet Port loopback, test
packets are injected into the Tx data path and are monitored at the receiver. Missing or
faulty packets detected at the Rx monitor point, indicates a failure at the Tx output
driver or the receiver input.
l The user can select the port on which to run the tests. Tests are only valid for copper
media type Ethernet ports. A selected port must be assigned and removed from
service (i.e., placed in a ‘Maintenance’ state) before non-automatic tests can be
performed.
l The user may select to run all Ethernet tests or select individual tests manually.
l Manual diagnostics are not possible when automatic diagnostics are running.
l By default, Etherjack® diagnostics are automatically triggered when a fault has been
detected on an Ethernet port.
l Only the Ethernet cable Test and Ethernet Auto-negotiation is performed during
automatic diagnosis.
l By default, the EFM loopback test:
o is not performed when the user has selected to run all tests. The user must select
l Ethernet Port - Device FAIL. Through internal loopback testing, the Ethernet port has
been found to be faulty. This is an equipment fault.
l Ethernet Port - Device PASS. Through internal loopback testing, the Ethernet port
has been found to be good.
l No Cable Detected. A cable has not been detected on the Ethernet port.
l Un-Terminated Cable Detected Length: <n> meters. An open circuit condition was
detected on the cable at a distance of n meters from the physical port.
l Cable Short Circuit at <n> meters. a short circuit condition was detected on the
cable at a distance of n meters from the physical port.
l Impedance Mismatch. The terminating impedance is higher or lower than the line
impedance, causing a reflected signal that does not match either the open or shorted
conditions.
l EFM Communication Failure. EFM packets sent were not returned.
l Cable OK. A valid termination was detected on the cable.
The capabilities of the Ethernet Cable Test (performed as part of Etherjack® Diagnostics)
can be enhanced by using Cable Length Benchmarking. See the following figure.
Points at various distances along the Ethernet cable can be given a name. Each cable
point can represent known locations on the Ethernet link, such as the location of a patch
panel connection, a wire closet or the end of the cable.
When an Ethernet Cable Test is run on a shorted, cut or unplugged cable, it gives the
distance from the port to the location of the open/short circuit. However, the results may
also be correlated to the nearest saved cable point or points, thus, providing more
accurate fault location.
The location of each cable point can be specified in terms of distance from the port and by
a user defined description.
The first benchmark is created with only one span of cable, then the second cable is
connected and another cable test is run to determine the combined length of the cables.
This continues until finally the last span of cable (up to five total) is added to the total
distance of the cable.
By entering a right click on the Access Port and selecting Cable Benchmarks, an Edit
Cable Length Benchmarks pane appears (see the following figure). In the following figure,
three cable points have been defined at various locations along the Ethernet cable. If the
cable at Point 1 has been unplugged, in addition to reporting an open circuit at a distance
from the local port to Point 1, the Ethernet Cable Test result will also show that the
nearest named cable port is ‘1st floor cabinet’.
l When specifying a cable length, the maximum cable length allowed is 1000 meters.
l When labeling cable termination points, the string is limited to 64 ASCII characters.
l Cable benchmark termination points are displayed to the user as provisioned (i.e., they
are not sorted by cable length).
1. Enter or edit the cable benchmarks for the desired copper interface.
Web-based GUI
Select Maintenance view
Enter the cable length (in meters) for each enabled Point, and a description name
for each enabled cable segment (up to 64 characters) in the Description field
Select Apply
Select OK
Performance Monitoring
Overview
The Performance Monitoring (PM) feature enables in-service, non-intrusive system
monitoring to aid in diagnosing and isolating issues that may occur during operation. PM
enables users to detect and react to potential failures prior to a customer outage. In
addition to providing traditional SNMP MIB Etherstats, Etherjack® provides Performance
Parameters (PPs) and features similar to those found in traditional services. This allows
Etherjack Service Assurance to be integrated into a carrier’s existing service assurance
infrastructure.
Performance Monitoring view allows you to view performance monitoring counts and
view PM thresholds. Performance monitoring thresholds can be edited, and registers can
be initialized (for users with proper user access permission level).
For PM commands using CLI, refer to the FSP 150GE11xPro Command Line Interface
Reference Guide.
Etherjack® PM Features
The following features are provided:
l retrievable performance data for each managed entity, so the user can determine past
and current system operation. PM data collection is performed via a polling
mechanism, were primitives are gathered into accumulated counts. After a defined
interval, (e.g., 15 minutes or 1 day), the counts are binned and stored in a database.
l the checking of PM counts against a threshold to see if the threshold has been
crossed. If so, a Threshold Crossing Alert (TCA) is reported, so that corrective actions
can be taken.
Etherjack® PM supports:
Performance Parameters
There are several categories of Performance Parameters (PPs) that are collected, as
follows:
l equipment presence and type [e.g., Small Form Factor Pluggable (SFP) Interface type
and presence, module type and presence]
l physical Layer monitoring (e.g., optical power, temperature)
l Ethernet Statistics (e.g., the number of Ethernet packets received/transmitted)
l Protocol Statistics (e.g., the number of protocol dependent packets
received/transmitted)
The following entities are monitored for performance data which is accumulated into PPs:
(1) The 32 Historical 15-Minute Bins provide the most recent 8 hours of per-
formance data.
(2) The Historical 1-Day Bin provides the performance data from the previous
day starting from 12:00am (i.e., midnight, 00:00).
Rollover
Counter For Ethernet managed entities only, a Rollover Counter is provided. This gives the
current performance data since monitoring began. The counter accumulates until it
reaches its maximum size (64 bits). When this happens the counter will ‘roll over’ to zero
and begin again.
Unlike Bins, the Rollover Counter is not related to the time of day, but to system uptime.
Each Network Port, Access Port, Flow and ESA Probe entity type has default thresholds
for its PPs, which are used when an entity is provisioned. The default thresholds are
configurable.
A TCA is only reported once during a bins time period unless it is initialized and then is
crossed again.
For the PPs Optical Power Transmit (OPT) and Optical Power Receive (OPR), a TCA is
raised if the PP count varies by the provisioned Optical Power Transmit Variance (OPT-
VAR) and Optical Power Received Variance (OPR-VAR) (higher or lower). The target
value and the acceptable variance is configurable by the user.
In other words, Optical Power Received / Transmit Variance (+/- dBm) represents the
variance from the configured OPR / OPT thresholds where the measured value will not
result in the generation of a TCA. For example: with an OPR threshold of -80 and an
OPR-VAR of 4, no TCA is generated if the measured OPR is -76 to -84.
Refer to "Performance Monitoring Settings" on page 953 for monitored types and default
Threshold Crossing Alert (TCA) settings.
l Summary, which displays a summary of both transmit and receive statistics. See
Figure 14 for an example view of an Access Port summary.
l 15 Minute/5 Minute, which displays the PM counts in the current 15 Minute/5 Minute
performance bin. To select 15 Minute or 5 Minute as the PM interval, right click on NE-
1 and select Edit; Select the desired PM Interval and click on Apply/OK. See Figure 17
for an example view of a Network Port 15 Minute PM counters. If the History checkbox
is selected the previous 32 periods are also displayed.
l 1 Day, which displays the PM counts in the current 1 Day performance bin. If the
History checkbox is selected the previous period is also displayed.
l Thresholds, which displays the details and the thresholds that have been set for each
PP. See for an example view of a Network Port Threshold values.
1. Select the Performance Monitoring icon or select Performance Monitoring from the
Applications menu, then expand the System entity in the Selection Tree.
2. Expand the Network Element and NTE entities. To view Flow PM counts, also
expand the Access Port entity in the Selection Tree. To view LAG entity counts,
expand the LAG and Network Element entities.
4. elect the desired PM Interval for the Network Element. Default is 15 Minutes. Click on
Apply or OK to save the setting.
5. Enter a right click on the Network Element and select Generate PM Data File.
The PM data files for Network Ports, Access Ports, PT Flows and LAGs can
also be saved by entering a right click on the desired entity and selecting
Generate PM Data File (See Figure 8).
The PM Data Files saving progress will begin, showing a screen as below.
When the “status” changes from “In progress” to “Success”, the PM Data Files
have been saved successfully.
7. Expand the Administration entity, right click on PM Data Export and select Copy to
Remote.
9. Click on OK and you’ll be prompted to open or save the file. Select Save and Open.
10. For “File Transfer Method” selecting FTP, SFTP or SCP from the drop-down list, the
display changes to the FTP, SFTP or SCP file transfer view, shown in the following
figure. (The figure shows the SCP view. The FTP and SFTP views are identical.)
11. Enter the data required in the screen to access the FTP, SFTP or SCP server and
begin the file transfer process, and click on OK.
It is assumed that the user knows the IP address of the FTP, SFTP or SCP
server, has a valid user ID and password and knows the path and file name
of the software file to transfer.
The file transfer will begin, showing a screen as the following figure
When the “Status” changes from “In progress” to “Success”, the PM Data file
has been transferred.
12. Select the desired Network Port, Access Port, LAG, Flow or Probe ID in the Selection
Tree.
Figure 16: Summary PM Counts View of an Access Port Flow (Flow-Based A2N Shaping)
Figure 17: 15 Minute PM Counts View of an Access Port Flow (Flow-Based A2N Shaping)
13. Select the desired tab to view Summary, 15 Minute counters, 1 Day counters or
Threshold levels.
Summary tab: To refresh the data, enter the number of seconds and select the
Automatic Refresh Every box.
15 Minute/5 Minute tab, 1 Day tab: Move, resize windows or use sliding bars
to view data, as required. Windows may be filtered (See Figure 19) to display
only selected data by selecting the Filter button and selecting/de-selecting
individual Monitored Type, or by selecting the Select All or Deselect All buttons.
Then select OK. History data may be hidden or displayed by de-
selecting/selecting the History option. An asterisk in the Time column indicates
data that is suspect.
14. If desired, 15 Minute/5 Minute and 1 Day counts can be exported to an Excel
spreadsheet by selecting the Export button.
15. Choose the desired application to open, or select the Save option (Save options vary
on different Web browsers). A filename associated with the entity and date is created
in the selected application (Excel is the default application - see Figure 21). Edit or
save the exported file as desired.
1. Select the ESA icon or select ESA from the Applications menu, then expand the
System, Network Element, NTE and Probes entities in the Selection Tree.
Current intervals are indicated as “current” and older periods are assigned incremental
numbers. The index allows a user to identify the current, previous (Bin Index=1) or one of
the historical bins (Bin Index = 2 to 32), with 32 being the oldest bin.
1. Select the Performance Monitoring icon or select Performance Monitoring from the
Applications menu, then expand the System selection tree.
2. Expand the Network Element entity form the selection tree, then expand the NTE
entity. To access Flow PM counts, also expand the Access entity in the selection
tree. To access LAG entity counts, also expand the LAG and its Network Element
entity.
3. Enter a right click on the desired Network Port, Access Port, LAG or Flow in the
selection tree and select Init Registers.
4. Select the desired Entity, Interval and Bin Index. Select OK.
1. Select the ESA icon or select ESA from the Applications menu, then expand the
System, Network Element, NTE and Probes entities in the Selection Tree.
2. Enter a right click on the desired Probe ID and select Init. PM Registers.
4. For a layer-2 probe, select the desired Destinations and CoS(s), Select All or Deselect
All.
5. Select OK.
1. Select the ESA icon or select ESA from the Applications menu, then expand the
System, Network Element, NTE and Probes entities in the Selection Tree.
2. Enter a right click on the desired Probe ID and select Init. Dist. Registers.
3. Select the desired history distribution register: All History Data, or specific history
data.
4. For a layer-2 probe, select the desired Destinations and CoS(s), Select All or Deselect
All.
5. Select OK.
Editing PM Thresholds
Each Network Port, Access Port, Flow, LAG and ESA Probe entity type has default
thresholds for its PPs. These thresholds are provisionable. The following procedures are
provided for the following entities/applications:
1. Select the Performance Monitoring icon or select Performance Monitoring from the
Applications menu.
2. Expand the System, Network Element and NTE entities in the Selection Tree. To
access Flow PM counts, also expand the Access entity in the selection tree. To
access LAG entity counts, expand the LAG and the Network Element entity.
3. Enter a right click on the desired Network Port, Access Port, LAG or Flow in the
selection tree and select Edit Thresholds. Select the desired entity and select OK.
4. Edit the desired thresholds for the desired Monitored Type. Select OK.
1. Select the ESA icon or select ESA from the Applications menu, then expand the
System, Network Element, NTE and Probes entities in the Selection Tree.
2. Enter a right click on the desired Probe ID and select Edit Thresholds.
3. Select the desired history distribution register: All History Data, or specific history
data.
4. Edit the desired thresholds for the desired Monitored Type. Select OK.
5. Select OK.
Creating Reflectors and Probes are performed by entering a right click on one of the
entities and selecting Create Probe/Create Reflector. There are 2 types of Probes; Layer-
3 Probes and Layer-2(Y.1731) Probes. Up to 10 Layer-3 Probes, 6 Reflectors and up to
32 (for GE112Pro series)/64 (for GE114Pro series) Layer-2 Probes are supported. Once a
Layer-2 Probe or a Layer-3 Probe / Reflector Pair has been created, an ESA scheduled
activity may be initiated to control the activity (see Provision an ESA Schedule).
The Service End Points and History Configuration items cannot be edited. If
they require modification, the probe must be deleted and re-entered.
To delete an existing Probe, enter a right click on the desired Probe entity and select
Delete Probe.
In current system, the layer-3 probes do no support the test of the layer-3
services provisioned under the NE. For more information on the layer-3
services provisioning, see Provision Layer-3 Services.
T
Refer to ESA Options and Rules to determine the default values, value ranges and rules
for each option in the following procedure.
1. Select the ESA icon on the Tool Bar or select ESA from the Applications menu and
expand the System, NE-1 and NTE11x entities in the Selection Tree.
2. Ensure that services are created and In-Service for the Access Port that is targeted to
create the Layer-3 Probe.
3. Enter a right click on the Probes entity and select Create Probe.
Identification
a) Probe Index – unique EID for the probe. Options available are 1 to 255.
b) Probe Name – a text identifier (up to 15 characters, no spaces and must
contain only alpha-numeric characters) for the probe (required).
c) Alias - enter the desired alias.
Probe Information
d) Protocol – the type of protocol to use (UDP Echo or ICMP Echo for
General and Round Trip Delay count reporting, ICMP Timestamp for
General, Round Trip Delay, One-Way Delay and Jitter count reporting.
e) Source Port – select the Access Port this probe is assigned to from the
drop-down list.
Service End Points
f) Probe IP Address and Mask – the IP address and subnet mask of the
probe to which echo replies will be sent.
The IP address must not overlap with any non-ESA related subnet
provisioned within the GE11xPro.
If more than one Probe IP address resides on the same subnet, they must all
be associated with the same flow.
Traffic Parameters
History Configuration
u) Round Trip Delay - set the minimum and maximum values and the
number of bins assigned.
v) One Way TX Delay - set the minimum and maximum values and the
number of bins assigned.
w) One Way RX Delay - set the minimum and maximum values and the
number of bins assigned.
x) One Way TX Jitter - set the minimum and maximum values and the
number of bins assigned.
y) One Way RX Jitter - set the minimum and maximum values and the
number of bins assigned.
5. Select OK.
6. Expand the Probes entity in the Selection Tree. Select the Probe Identifier and
Configuration and StatsConfig tabs to verify the entry.
7. To view / edit Probe Thresholds, see Viewing PM Counts and Threshold Values or
Editing PM Thresholds, respectively.
Every GE11xPro product supports two types of Y.1731 probes which are
MEF 35/36 compliant.
To edit an existing Probe, enter a right click on the desired Probe entity and select Edit
Probe.
The Service End Points and History Configuration items cannot be edited. If
they require modification, the probe must be deleted and re-entered.
To delete an existing Probe, enter a right click on the desired Probe entity and select
Delete Probe.
Refer to ESA Options and Rules to determine the default values, value ranges and rules
for each option in the following procedure.
1. Ensure that services are created and In-Service for the Access Ports that are targeted
for Layer-2 ESA testing.
2. Create a CFM MD, MANET, MACOMP and MEP for the desired ports at both NEs
(see CFM Provisioning and Operation).
3. Select the ESA icon on the Tool Bar or select ESA from the Applications menu and
expand the System, NE-1 and NTE11x entities in the Selection Tree.
4. Enter a right click on the Probes entity and select Create Probe.
5. Select Protocol type Y.1731 LM/DM or Y.1731 SLM/DMM from the drop down list.
Y.1731 uses CFM MEPs as the end points and thus does not require a
reflector. This also means that the related MD, MANET, MACOMP and
MEPs must already exist on the same interface as this probe in CFM to
create a Y.1731 protocol probe. Additionally, since Y.1731 LM/DM only
supports point-to-point connections, the CFM MA MEP list can only have
two entries or an error message displays.
6. Enter/select the following Probe options (refer to ESA Probe Configuration Settings for
details and rules):
Identification
a) Probe Index – Unique EID for the probe. Options available are 1 to 255.
b) Probe Name – a text identifier (up to 15 characters, no spaces and must
contain only alpha-numeric characters) for the probe (required).
c) Alias - a customized name for this probe
Probe Information
If the two Network ports are configured “1+1” or “Dual Active Receive” PPG
and are provisioned with different speeds, the port configured with larger port
speed will output random larger SLM/DMM frames against the configuration.
Thus, it is recommended that the network ports be provisioned with same
speed. As such, for auto-negotiated speed, both ports are recommended to
be provisioned the same auto-negotiated speed, e.g. Auto 1000 Full;
however, “auto” is not recommended.
Destination MEP List (only available for Y.1731 SLM/DMM probe when
Multicast MAC is disabled and Destination Type is set to Point to Multipoint.)
Figure 30: Multiple Destination MEP Members for Y.1731 SLM/DMM Service End Point
Service Parameters
History Configuration
x) History Bins – the number of bins of history results to keep. The default
is 8.
y) History Interval – drop-down list - the number of minutes in a single
interval. The default is 15 minutes.
z) History Distribution Bins – the number of distribution history bins to
keep. The default is 8.
aa) History Distribution Interval – drop-down list - the number of minutes in
a distribution history bin. The default is 15 minutes.
ab) Round Trip Delay - set the minimum and maximum values and the
number of bins assigned
ac) One Way TX Delay - set the minimum and maximum values and the
number of bins assigned
ad) One Way RX Delay - set the minimum and maximum values and the
number of bins assigned
ae) One Way TX Jitter - set the minimum and maximum values and the
number of bins assigned
af) One Way RX Jitter - set the minimum and maximum values and the
number of bins assigned
Select OK.
7. Expand the Probes entity in the Selection Tree. Select the Probe Identifier and
Configuration and StatsConfig tabs to verify the entry (see Figure 31 and Figure 32).
8. To view / edit Probe Thresholds, see Viewing PM Counts and Threshold Values or
Editing PM Thresholds, respectively.
Provision a Reflector
The next step in creating a Layer-3 ESA test is to establish a reflector at one GE11xPro.
To edit an existing Reflector, enter a right click on the desired Reflector entity and select
Edit Reflector. To delete an existing Reflector, enter a right click on the desired Reflector
entity and select Suspend Reflector, then enter a right click and select Delete Reflector.
Once a Reflector has been created, the Reflector identifier appears under the Reflector
identifier in the selection tree. You can view Reflector details and status by selecting the
specific Reflector entity.
Entering a right click on an existing Reflector identifier will provide menu selections for
the specific Reflector. Menu selections available for Reflector identifiers are:
l Edit Reflector - (only Priority Map Mode and Priority are editable)
l Delete Reflector - To delete a reflector.
Refer to ESA Options and Rules to determine the default values, value ranges and rules
for each option in the following procedure.
1. Select the ESA icon on the Tool Bar or select ESA from the Applications menu.
Expand the System, NE-1 and NTE11x entities in the Selection Tree.
2. Ensure that services are created and In-Service for the Access Port that is targeted to
create the Reflector.
3. Enter a right click on the Reflectors entity and select Create Reflector.
Identification
a) Reflector Index – Unique EID for the probe. Options available are 1 to
255.
b) Reflector ID – a text identifier (up to 15 characters, no spaces and must
contain only alpha-numeric characters) for the reflector (required).
IP Information
c) Source Port - the port on which the reflector operates - select from drop-
down list
Reflector Information
5. Select OK.
6. Expand the Reflector entity in the Selection Tree. Select the Reflector Identifier and
Configuration tab to verify the entry.
One or more Probes may be scheduled using the same Entity ID and Activity ID, and
multiple Scheduled ESA activities may be created. Refer to ESA Options and Rules for
detailed information on Scheduled ESA configuration options and rules.
Once a Scheduled ESA has been created, options available when entering a right click on
the Activity ID in the Selection Tree are: Delete, Suspend, Resume and Edit. To
edit/delete a Scheduled ESA, you must first Suspend the activity. For the schedules in
Active status, user is allowed to edit the schedules by adding or removing probes. To
view the ESA Schedule status, expand the System, NE-1, NTE11x and Schedules
entities in the Selection Tree and select the desired Entity ID.
1. Select the ESA icon on the Tool Bar or select ESA from the Applications menu.
2. Expand the System, NE-1 and NTE11x entities in the Selection Tree. Enter a right
click on Schedules and select Create Schedule.
Identification
a) Schedule Index – Unique EID for the ESA Schedule. Options available
are 1 to 255.
b) Activity ID – a text identifier (up to 15 characters, no spaces and must
contain only alpha-numeric characters) for the ESA Schedule (required).
Schedule Parameters
Schedule Probes
i) Select the checkbox next to the desired probes this schedule is assigned
to.
4. Select OK.
5. Expand the Schedules entity and select the Schedule identifier to verify entry.
6. To edit a Schedule entity, enter a right click on the desired entity and select Edit
Schedule.
7. Select/Deselect the checkboxes by the probes you want to associate with this
schedule. Click on OK.
Only the schedules in “Active” status are allowed to be edited. The schedules
in “Completed” or “Initial” Status cannot be edited any more.
8. Once a scheduled ESA has been activated, status results may be displayed: If
required, expand the Probe entity in the Selection Tree. To display ESA test results,
select the desired active Probe and select the Statistics tab.
Counts available are dependant upon which Protocol type has been entered
when creating the Probe and which report Group has been selected from the
Groups selection list (see Table 13).
9. Select the desired display type of Table or Chart. See Figure 37 for an example of ESA
counts displayed in tabular format, and see Figure 38 and Figure 39 for examples of
ESA counts displayed in chart format.
10. Select the desired Counters to be displayed: General, Distribution, Delay or Jitter. If
Distribution is selected, also select the desired Distribution Type to be displayed.
Counters may also be filtered by selecting the Filter button (see Figure 40).
Select or de-select individual counter or click the Select All or Deselect All
button in respective counter types to filter the displayed [Link] click on the
Filter: OK button to confirm the selection.
Results may be refreshed by selecting the Statistics tab. History data may be
hidden or displayed by de-selecting/selecting the History option.
11. If desired, Statistics results can be exported to an Excel spreadsheet by selecting the
Export button.
12. Choose the desired application to open, or select the Save File option. A filename
associated with the entity and date is created in the selected application (Excel is the
default application - see Figure 42). Edit or save the exported file as desired.
13. If desired, edit ESA Probe thresholds or initialize PM/Distribution registers. To edit
ESA Probe thresholds, see Editing PM Thresholds. To initialize PM or Distribution
registers, see Initializing PM and Distribution Registers.
Figure 39: ESA Round Trip Delay Distributed Statistics Results in Chart Format
The following procedure describes the CFM feature provisioning and operation process
for each node. Refer to CFM Configuration Options and Rules to determine the default
values, value ranges and rules for each option in the following procedure.
1. Determine the CFM node locations to be provisioned, including their MAC addresses
and other associated options. Common elements for each end point include Primary
VLAN IDs, Maintenance End Point IDs and Continuity Check Message interval.
2. Select CFM from the Applications menu, expand the System and Maintenance
Domain entities in the selection tree.
3. Right click on the System entity in the selection tree and select Edit System Default
MD Level.
5. Select OK.
6. Right click on the System entity in the selection tree and select Edit CFM Control.
7. Select the desired Signal Fail Trigger by ticking the corresponding checkbox.
8. Select OK.
9. Right click on the Maintenance Domain entity in the selection tree and select Create
MD.
10. Enter/select the following MD options (refer to Configure Maintenance Domain for
details and rules):
11. Select OK
MIPs are not created explicitly via the web-based GUI. For information on
MIP rules see FSP 150-GE11xPro System Description document.
13. Select the new Maintenance Domain ID and verify the entry.
15. Right click on a Maintenance Domain ID in the selection tree and select Create
MANET.
16. Enter/select the following MANET options (see Configure Maintenance Association
Network for details and rules):
Enter the Maintenance Association MEP list by entering the first ID number and
select Add. Enter additional ID members and select Add, as required. To delete
an ID member, select the ID member to be removed, and then select Delete.
17. Select OK
20. If additional MANETs are required for the same Maintenance Domain ID, repeat 15
through 17.
22. Expand the MD entity in the selection tree, right click on the associated MANET entity
in the selection tree and select Create MACOMP.
24. Select OK
25. Expand the NE-1 and NTE entities in the selection tree.
26. Right click on the interface port identified by itself or its associated flow in the
MACOMP and select Create MEP.
If the MACOMP Component ID is an Access Port Flow, the flow EID will
appear as the Associated Port for the MEP to create.
27. Enter/select the following MEP options (refer to Configure Maintenance End Point for
details and rules):
Identification
Although the MEP Index appears above the MANET ID in the GUI display,
the MANET ID determines what MEP Indexes are available, so the MANET
ID must be selected first.
State
Configuration (General)
The system currently only supports Up Direction if the MEP associated port
is an Access Port Flow.
CFM LLF triggers only work if the ports associated with the MEP are
configured to support LLF. If using RDI as a trigger, ensure the Remote
MEP’s fault priority is set higher than MAC STATUS (default value) or the
port may not recover from an RDI triggered deactivation without intervention.
Configuration (AIS)
Configuration (ESA)
Select the desired LM and DM settings for LM In-Profile Only, LM TX Count All
Priorities, Dual-ended Count All Priorities, LM RX Count All Priorities
Configuration (SAT)
Select OK
28. Expand the associated Maintenance End Point entity interface in the selection tree.
32. Right click on the desired access/network port and select Create VLAN Entry.
33. Enter the following VLAN Entry options (see Configure CFM VLAN Table for details
and rules):
Enter the VID Members List by entering the first VID ID number and select Add.
Enter additional VID ID members and select Add, as required. To delete a VID
ID member, select the VID ID member to be removed, and then select Delete.
35. Select the access port associated with the VLAN entry in the selection tree.
37. If additional MEPs are required for another Maintenance Association ID, repeat 25
through 36.
38. If additional Maintenance Domains, and their associated MD IDs and MEPs are
required, repeat 9 through 37.
39. Select the maintenance application, expand the tree to see the selections under the
Alarm Attributes tab. select CFM MEP and determine if Notification Code changes are
required. If Alarm notification code changes are required, enter a right click on a CFM
MEP and select Edit Alarm Attributes, select the desired Notification Code(s) and
then select OK. Repeat for CFM QOS Shaper.
40. Repeat 1 through 39 for each node to be set up for Connectivity Fault Management.
42. Expand the Maintenance End Point entity in the selection tree.
43. Right click on the associated MEP interface in the selection tree and select Loopback.
44. Enter/select the following options (refer to Initiate Loopback Message for details and
rules):
Before running Loopback, ensure that the Administrative State of the MEP is
IS.
46. Go to 41
47. Expand the Maintenance End Point entity in the selection tree.
48. Right click on the associated MEP interface in the selection tree and select Linktrace
Before running Linktrace, ensure that the Administrative State of the MEP is
IS.
51. Select the MEP Configuration tab and verify the status
For LTM, click on the LTR Database tab to view the Link Trace Reply database.
ECPA upstream injection (e.g., network port as the source port and injecting
in the N2A direction) with the source port of a LAG Member Port is not
expected to function properly when injecting untagged frames and LAG
protocols enabled. The injection of untagged frames blocks LACP (because
they are untagged) and causes the removal of the port from the LAG function.
The removal of the port from the LAG also blocks all non-LACP frames from
being forwarded on that port.
From the Maintenance application, entering a right click on “System” in the selection tree
and selecting Edit ECPA Streams allows you to edit ECPA test stream details prior to
advancing through the ECPA test process. See the following figure.
ECPA setup and execution options are available by entering a right click on the NTE
entity and selecting Run ECPA. An ECPA test setup window walks you through the
steps for selecting ECPA setup and execution options, and performing ECPA
diagnostics. You can place a facility in the maintenance state, select the desired tests to
perform, execute diagnostics, view test results, and restore the facility from this window.
See Figure 55 for the ECPA test setup window provided after the facility has been placed
in the maintenance state.
The desired Source Port, Injector and Monitor direction, Test Type (and Duration or
Frames as appropriate) and ECPA test stream assignments are also selected and edited
from this window.
The next step in the ECPA Test Process is running the test, which is invoked by
selecting the Run button from the ECPA test setup window. The ECPA test results
window will appear, displaying the current ECPA test status and results. If multiple test
streams are run, scroll down to review each ECPA test stream. The screen refreshes
itself when the test completes or is stopped. The test can be canceled by selecting the
Stop Test button.
The first ECPA test frame can be viewed by selecting the ECPA First Frame buttons
located at the top of the ECPA view. See Figure 56 for the location of the ECPA First
Frame buttons. See Figure 57 for an example of ECPA First Frame results.
The ECPA First Frame windows provide first frame result details, including frame header,
packet details and raw frame content for each ECPA test stream. If more than one ECPA
test stream was run, use the tabs to view the ECPA First Frame for the desired ECPA
test stream. To toggle back to the ECPA Test Results window, select the ECPA Results
button located at the top of the ECPA First Frame results view. See Figure 57.
1. Create a remote loopback at the far end of the facility to be tested or create a local
loopback if internal testing is desired.
2. Select Maintenance view, right click on “System” in the selection tree and select Edit
ECPA Streams.
An Edit ECPA Streams window appears
Name
Configuration
VLAN Configuration
4. Select OK
The maintenance status window appears
7. Right click on the NTE entity (NTE11x) in the selection tree and select Run ECPA.
An ECPA Status window appears
Select the desired Test Stream for Test Stream A (Stream-1 was configured in
step 2)
10. Select OK
11. Verify the Administrative State of the facility is in the Maintenance state.
12. Select the “Start Test” button to start the ECPA test.
ECPA Test Status changes to “In Progress”
14. Select Stop Test when desired, or wait until the test has completed.
16. Select “Set Configuration” and select “IS” for the Administrative State.
Select Apply
The Administrative State changes to IS
19. If desired, retrieve the first frame received by selecting the desired ECPA First Frame
tab
1. Create a remote loopback at the far end of the facility to be tested or create a local
loopback if internal testing is desired.
2. For Flow VLAN facility, create the appropriate VLAN member(s) that will be used
when creating ECPA test streams in the next step. (Defaults for all 12 streams are:
Outer VLAN, Inner VLAN1 and Inner VLAN2: EtherType = 8100 (hex), Tag = 4094-1)
3. Select Maintenance view, right click on “System” in the selection tree and select Edit
ECPA Streams.
4. Select the desired ECPA Stream and enter/select the following configuration options:
Name
Configuration
The rate should not exceed the facility/path rate, including overhead bytes.
VLAN Configuration
Select the desired VLAN Configuration options (Outer VLAN, InnerVLAN1, Inner
VLAN2) and edit the Ethertype and Tag information as needed.
5. Select OK.
6. Select the ECPA Streams tab and stream number tab to verify ECPA Stream entry.
8. Right click on the NTE entity (NTE11x) in the selection tree and select Run ECPA.
Select the desired Test Stream number (or “None”) for each Test Stream
11. Select OK
12. Verify the Administrative State of the facility is in the Maintenance state. Select Start
Test.
14. Select Stop when desired (if TestType is Continuous), or wait until the test has
completed.
16. Select Set Configuration and select “IS” for the Administrative State.
The following procedure assumes that the user has configured the NE with an IP address
and connected the NE to a DCN or LAN (see Set Up the GE11xPro DCN (eth0) Port
Using the Serial Port ) and is logged on with at least a Provisioning level user permission
using the web-based GUI.
The procedure also assumes that services have been configured at both ends with flows
and up/down MEPs to support SAT testing and that a connection exists between the two
sites. See Provision Access Port Services and ESA Provisioning and Operation.
The screenshots in the following procedure are presented for reference and do not reflect
the actual User Interface of a GE11xPro product.
Refer to SAT Configuration Options and Rules to determine the default values, value
ranges and rules for each option in the following procedure.
The SAT Test Stream will use local MEP’s MAC address as its source MAC
address. The local MEP is used to negotiate with the remote SAT Responder
and run delay measurement.
Make sure that the CFM settings at Site A and Site B match each other and
the Up/Down MEPs at two sites form a pair.
The destination MEP at Site B is created for the test stream and is
used to negotiate with the local MEP and run delay measurement.
1. Select the Service Activation Testing Application on the tool bar or select Service
Activation Testing from the Application menu. Expand the System and NE-1 entities
in the selection tree pane by clicking the “+” sign.
When SAT Control works in “One Way” mode, the SAT Responder Control
option must be Enabled (see Configure Maintenance End Point) on
destination MEP, so that the SAT Responder End is capable of exchanging
the control Protocol Data Unit (PDU) with the SAT Control End.
4. Expand the SAT Control entity in the Selection Tree and select the Configuration tab
in the Detail Pane to view the SAT Control settings.
5. From the SAT application, expand the System and SAC Profile entities.
9. Enter a right click on SAT Control and select Create Test Stream.
10. Enter/Select the following SAT Test Stream options (see Create/Edit SAT Test
Stream for option rules):
Identification
SAT Test Stream supports service based Up MEP. If a SAT Test Stream is
associated with a service based Up MEP, the “FLPDU Tag Override” option
in associated SAT Control must be Enabled. The system only supports
customized VLAN tag (or untagged) on SAT Test Stream for service based
Up MEP.
The system allows running SAT tests on MEPs that are associated with
probes without having to delete the probes, given that the probes are not
included in any schedule (see Provision an ESA Schedule for how to edit an
ESA schedule).
Only Forward direction is supported when SAT Control works in “Two Way”
Test Mode.
FLPDU
m) Select the desired Mac Address Type for test stream’s FLPDU
n) Enter the Destination MAC Address if Mac Address Type is Multicast
o) Select desired Payload Type
p) Enter Custom Payload if Payload Type is CUSTOM
q) Enter desired Frame Size List or click on EMIX or EMIX Default to use a
fixed frame size list
Service
11. Go to 17.
12. Enter a right click on SAT Control and select Create SAT Test Stream Wizard.
The wizard will automatically check and fill out the configuration settings if
valid associated settings have been provisioned.
The wizard does not support to create SAT Test Stream in Down direction.
13. Observe the settings wizard automatically provisions and make changes if needed,
then click on Next to proceed.
14. Likewise, the wizard automatically provisions the settings in step 2. Click on Prev to
modify the settings in previous step, otherwise make changes as needed and click on
Next to proceed.
The FINISH pane appears, showing SAT Test Streams are created
successfully
16. Expand the selection tree and click on the newly created SAT test stream under SAT
Control.
17. Select the Configuration tab to verify Test Stream configuration details. If changes are
required, enter a right click on the test stream entity and select Edit.
The source port and local MEP settings cannot be edited after the creation of
a SAT Test Stream.
System supports up to four Test Streams running at the same time and the
running test streams may belong to different flows under a same port or
different COS (depending on VID and Priority) under a same flow.
One Local MEP and one Destination MEP can apply to all the four Test
Streams.
19. Initiate a Terminal Port/VLAN loopback on the port on Site B (SAT Responder End) if
SAT Control works in “Two Way” Test Mode.
For down direction test streams, initiate a facility Port/VLAN loopback on the
responder port if SAT Control works in “Two Way” Test Mode.
Before running SAT tests, make sure that the SAT Control End and the SAT
Responder end are synchronized (see Edit System Time of Day ), otherwise
test result will record the occurrences of out of synchronization error; if time
is not synchronized, FDV will be calculated as normal, but Min/Max/Avg
FTD will be counted only for valid samples (DMM).
If the transmitted FLPDU Priority at one end is different from the received
FLPDU priority at the other end, the SAT test will fail.
21. Enter a right click on the SAT Control entity and select Run to start the tests of all
available streams.
When SAT Control works in “One Way” Test Mode, a “Remote Initiated SAT”
alarm will be raised at the Responder End after the test starts. This alarm
indicates a SAT Responder Session has been negotiated successfully and is
running on the Responder End.
This alarm will be cleared when user deletes the Responder Session or when
it is released by the remote SAT Control End.
The Run SAT Control screen displays the general test status, progress
and overall result of each test stream
24. Go to 28.
25. Right click on the SAT Test Stream ID and select Run to start the test of a single test
stream.
26. Scroll down the page and click on Start Test to run the test stream, or click on Set
Configuration to change the test stream settings.
The Status / SAT Test Result in Run SAT Test Stream screen display the
test progress, details and result associated with the test stream (see Figure
71)
28. When the test is completed, scroll down to the bottom of page in Run SAT Test
Stream screen to view the SAT Test Result of a single test stream (see Figure 72).
29. Alternatively, click on the test stream in selection tree and select the Test Result tab
in the Detail Pane (see Figure 73)
The SAT Test Result Tab not only displays the test result details, but
also presents Test Procedure and Pass Criteria in a cellular form so
user can adjust test stream configuration settings based on the
measurement and criteria.
Only the test result of green packets will be compared against Service
Acceptance Criteria (SAC) parameters.
Frame Loss Ratio (FLR), Max Frame Transmission Delay (Max FTD) and
Max Frame Delay Variance (Max FDV) will be compared against the FLR,
FTD and FDV set in SAC Profile. If any one of these parameters do not
match with SAC criteria, the test fails.
30. If a test fails, troubleshoot the parameter settings in flows, test streams and CFM
entities or change the SAC parameters as appropriate.
It is possible that the FLR and FL Count for yellow packets show minus
values in EIR or Policing test result when Color Mode is set to Color Aware.
This is because the Responder end received more yellow packets than what
the Control end sent. User can troubleshoot this problem by balancing the
CIR settings in the test stream and the associated flow.
31. Expand the selection tree and select SAT Control, select the Configuration tab to view
SAT Control Configuration, SAT Control Status and SAT Stream Status. (see Figure
74)
The Test Result tab displays SAT Test Results based on user’s selection.
33. Scroll down to the bottom of the Test Result page, click on Export to save the test
result of a single test stream or all test streams as a .csv file to a specified directory.
The FTP and SFTP transfer methods require identical File Transfer settings
as SCP (see Figure 77).
Figure 78: SAT Test Result Upload Progress - SCP Transfer Method
35. When the upload is completed, access the server to check the exported SAT test
result. If saving the result via Web, save the file to a specified directory (see Figure
79).
Selecting the NE-1 entity in the Selection Tree provides the SyncJack Global Dashboard
View (see Figure 80). The Global status reflects a composite of 3 status meters: Clock
Accuracy, Clock Analysis and PTP Network Analysis. For the indicator bar, a horizontal
line indicates N/A, green indicates normal operation, yellow indicates some issue exists,
red indicates a significant problem.
Probing Feature
Clock Accuracy
l Up to 2 Clock Probes:
o Calculate MTIE between physical source and reference signals
Only one Clock Probe can be created if Time Clock is configured with GPS
as Time Reference.
Clock Analysis
l Up to 4 PTP Clock Probes (all PTP Clock Probes must use the same reference)
o Calculate packet MTIE between physical reference signals and packet flow
MTIE Comparison
l Compare up to four MTIE results
the last 100K seconds is displayed. In addition, MTIE is calculated over the entire
measurement.
In case additional analysis is required (e.g., Time Deviation (TDEV)) or longer TE/TIE
measurements are needed, the TE/TIE raw data can be collected by the device and sent
to an external server.
The amount of raw data which can be stored on the device (e.g., GE114Pro
(SH)/GE114Pro (CSH)) is limited; therefore the data is collected and sent every 5
minutes to the configured server.
The data can then be concatenated in the server (by NMS or any other user SW) and
imported to the relevant software tool for analysis.
and
MTIE: Constant difference between the clocks is rejected, so only the frequency
differences matter.
The following procedure for performing Clock Accuracy testing assumes that GE114Pro
(SH) is properly connected to the clock inputs to be measured and the appropriate
GE114Pro (SH) interfaces have been configured. See Provisioning the GE11xPro
The screenshots in the following procedure are presented for reference and do not reflect
the actual User Interface of a GE114Pro (SH)/GE114Pro (CSH) product.
Refer to Clock Accuracy Parameters to determine the default values, value ranges and
rules for each option in the following procedure.
1. Select the SyncJack icon or select SyncJack from the Applications drop-down list,
then expend the System folder in the selection tree.
2. Expand the Network Element entity from the selection tree, then expand the Clock
Accuracy entity.
3. Enter a right click on Clock Probes in the selection tree and select Create Clock
Probe.
a) Clock Probe Index -- EID for the probe. Enter a number from 1 to 2.
b) Name - a text identifier (up to 15 characters, no spaces or special
characters) for the probe. (Required entry)
c) Reference - the signal reference for this Clock Probe. The available
references are populated in a drop-down list.
d) Reference Expected QL - clock quality level of the selected reference.
The available QLs are provided in a drop-down list.
e) Source - select the desired source (clock under test) from the drop-down
list.
f) Source Type - select either Frequency or Phase from the drop-down list.
g) MTIE Mask - select the desired MTIE Mask from the drop-down list.
h) Mask Margin - enter the desired Mask Margin as a percentage from 0 to 99
i) Raw Data Collection - If Raw Data Collection Server has been
provisioned: enable or disable raw data to be sent to a remote raw data
collection server.
j) Measurement Type - select the measurement type (Frequency or Phase)
Select OK.
6. Select the Clock Probe entity and Status tab to verify entry and connection status
(See Figure 82 on p. 614). If any Failures are indicated, troubleshoot and clear the
failure as necessary.
A Clock Probe can be edited after creation by right clicking on the entity
name and selecting ‘Edit Clock Probe’. All fields except the Clock Probe
Index can be edited. Once a probe is scheduled it cannot be modified or
deleted.
7. Enter a right click on SyncJack Schedules in the Selection Tree and select Create
Schedule.
a) Schedule Index - EID for the schedule. Enter a number from 1 to 255.
b) Activity ID - a text identifier (up to 15 characters, no spaces or special
characters) for the probe.
c) Schedule Type - Select the desired type from the drop-down list (Only
“One Shot” is currently supported)
d) Duration - Select either the “Forever” or “Fixed” radio button. If “Fixed” is
selected, enter the desired duration in seconds.
e) Start Time - Select “Now” or “Future” radio button. If “Future” is selected,
enter the date and time for the test to start.
f) Schedule SJ Test Items - Select the desired Clock Probe(s) for this test
from the list provided by clicking the related check box(es).
Select OK.
11. Select the desired Clock Probe entity/entities in the Selection Tree and select the
Status tab to observe the SyncJack Schedule State and test process (State indicates
whether the test is Not Scheduled, Failed, Waiting [Scheduled - Future], Running or
Completed).
12. Click on the Clock Probe entity again to observe continued progress while the test is
running. Observe the Actual Test Duration (s) status to determine how long the test
has been running / how much time is left before completion (if a Fixed Duration was
scheduled).
13. Click on the Clock Probe entity again to observe when the test is completed (see the
following figure).
14. Observe test result details by interval by viewing the Test Result table or hovering the
mouse over the interval marker in the graph (see the following figure).
15. Test results may be exported to Microsoft Excel or other program by selecting the
Export button (see the next two figures).
16. After the test is completed, select the Tests tab to view test results in tabular format.
Scroll over to determine if any thresholds have been crossed.
Figure 91: Example Clock Probe TIE/TE Graph with Failed Region
18. If the test duration is longer than 2000 seconds, select the Recent TIE/TE Graph tab
to view the last 2000 seconds of test results (see the following figure).
The TIE/TE Graph may present the last 100,000 seconds of the
measurement since the start of Probe; while the Recent TIE/TE Graph may
present the last 2000 seconds of the measurements.
19. After the test is completed, a subset of the Clock Probe Status tab data are available
in a history entity. To view history results, expand the History Results entity under the
Clock Probe entity and select the desired Clock Probe Result(s) to view.
20. History test results may be exported to Microsoft Excel or other program by selecting
the Export button.
21. Select the Clock Accuracy entity in the Selection Tree to view the Clock Accuracy
results via Dashboard meter. If two Clock Probes have been scheduled (as shown
below), the results of both Clock Probes are displayed.
The Clock Accuracy meter will display test results only if the associated
SyncJack schedule is present. Each probe is associated with a color coded
radio button according to its test result (green, yellow or red). If gray, this
indicates the SyncJack schedule has been deleted.
Figure 94: View Clock Accuracy Result Meter (Two Clock Probes)
22. Select the Network Element entity in the Selection Tree to view the Clock Accuracy
and Global results via Dashboard meter.
23. To set up Raw Data Collection, perform the procedure Raw Data Collection.
24. To delete a SyncJack Schedule, right click on the desired schedule under “Syncjack
Schedules” and select Delete Schedule.
Select OK.
25. To delete a Clock Probe History Result, right click on the desired result under “History
Results” and select Delete History Result.
Select OK.
26. To edit a Clock Probe History Result, right click on the desired result under “History
Results” and select “Edit History Result”.
28. To edit a SyncJack Clock Probe, right click on the desired clock probe under “Clock
Accuracy” and select Edit Clock Probe.
29. Edit the data as appropriate if the Clock Probe is not associated with a present
SyncJack Schedule. Select OK to save the changes.
30. To delete a SyncJack Clock Probe, right click on the desired clock probe under “Clock
Accuracy” and select Delete Clock Probe.
Select OK.
Refer to Clock Analysis Parameters to determine the default values, value ranges and
rules for each option in the following procedure.
1. Select the SyncJack icon or select SyncJack from the Applications menu, then
expand the System folder in the selection tree.
2. Expand the Network Element entity from the selection tree, then expand the Clock
Analysis entity.
3. Enter a right click on PTP Clock Probes in the Selection Tree and select Create Clock
Probe.
a) PTP Clock Probe Index - EID for the PTP Clock Probe. Enter a number
from 1 to 4. (Create only)
b) Name - a text identifier (up to 15 characters, no spaces or special
characters) for the probe. (Required entry)
c) PTP Flowpoint - select the PTP Flowpoint from the drop-down list.
d) IP Version - select the desired IP version from the drop-down list. (Only
IPv4 is supported for the current release.)
e) Master IP Address - enter the IP address of the master clock (if the PTP
Flow Point Type is set to OC Slave, then the Slave IP Address must be
configured the same as the SOOC.)
f) Slave IP Address - enter the IP address of the slave clock (if the PTP
Flow Point Type is set to OC Slave, then the Slave IP Address must be
configured the same as the SOOC.)
g) Direction - select the desired Direction (Slave to Master or Master to
Slave). If the Flow Point Type of the associated PTP Flow Point is set to
OC Slave, then Slave to Master or Master to Slave may be selected. If the
Flow Point Type of the associated PTP Flow Point is set to OC Master,
then only Slave to Master selection is allowed.
h) Reference - the signal reference for this PTP Clock Probe. The available
references are populated in a drop-down list.
i) Reference Expected QL - clock quality level of the selected reference.
The available QLs are provided in a drop-down list.
j) MTIE Mask - select the desired MTIE Mask from the drop-down list.
k) Mask Margin - enter the desired Mask Margin as a percentage from 1 to 99
l) Raw Data Collection - If Raw Data Collection Server has been
provisioned: enable or disable raw data to be sent to a remote raw data
collection server.
m) Measurement Type - select the measurement type.
Select OK.
6. Select the newly created PTP Clock Probe entity to verify entry and connection status
(see Figure 99 on p. 627). If any failures are indicated, troubleshoot and clear the
failure as necessary.
The Telecom Slave cannot be used in different PTP Clock Probes for
separate Frequency and Phase measurement under the same NE. The
“SJTEST Reference Fail” alarm will be raised if the user intends to create a
PTP Clock Probe using telecom slave for Frequency measurement while
another PTP Clock Probe using the same Telecom Slave for Phase
measurement already exists, and vice versa.
A PTP Clock Probe can be edited after creation by right clicking on the entity
name and selecting Edit PTP Clock Probe. All fields except the PTP Clock
Probe Index can be edited. Once a probe is scheduled, it cannot be modified
or deleted.
7. Enter a right click on SyncJack Schedules in the Selection Tree and select Create
Schedule.
a) Schedule Index - EID for the schedule. Enter a number from 1 to 255.
11. Select the desired PTP Clock Probe entity in the Selection Tree to observe the
SyncJack Schedule State and test progress (State indicates whether the test is Not
Scheduled, Failed, Waiting [Scheduled - Future], Running or Completed).
12. Click on the PTP Clock Probe entity again to observe continued progress while the
test is running. Observe the Actual Test Duration (s) status to determine how long the
test has been running / how much time is left before completion (if a Fixed Duration
was scheduled).
13. Click on the PTP Clock Probe entity again to observe when the test is completed (see
the following figure).
14. Observe test result details by interval by viewing the Test Result table or hovering the
mouse over the interval marker in the graph (see the following figure).
15. Test results may be exported to Microsoft Excel or other program by selecting the
Export button (see the following figure).
16. After the test is completed, select the Tests tab to view test results in tabular format.
Scroll over to determine if any thresholds have been crossed.
18. If the test duration is longer than 2000 seconds, select the Recent TIE Graph tab to
view the last 2000 seconds of test results.
The TIE/TE Graph may present the last 100,000 seconds of the
measurement since the start of Probe; while the Recent TIE/TE Graph
may present the last 2000 seconds of the measurements.
19. After the test is completed, a subset of the PTP Clock Probe Status Tab data are
available in a history entity. To view history results, expand the History Estimations
entity under the PTP Clock Probe entity and select the desired PTP Clock Probe
Result(s) to view.
20. Test results may be exported to Microsoft Excel or other program by selecting the
Export button.
21. Select the Clock Analysis entity in the Selection Tree to view the Clock Analysis
results via Dashboard meter. If four PTP Clock Probes have been scheduled, the
results of the four probes are displayed.
The Clock Analysis meter will display test results only if the
associated SyncJack schedule is present. Each result is associated
with a color coded radio button according to its Probe Score (green,
yellow or red). If gray, this indicates the SyncJack schedule has been
deleted or no score results are present.
22. Select the Network Element entity in the Selection Tree to view the Clock Analysis
and Global results via Dashboard meter.
23. To set up Raw Data Collection, perform the procedure Raw Data Collection.
24. To delete a SyncJack Schedule, right click on the desired schedule under SyncJack
Schedules and select Delete Schedule.
Select OK.
25. To delete a PTP Clock Probe History Result, right click on the desired result under
History Estimations and select Delete History Estimation.
Select OK.
26. To delete a SyncJack PTP Clock Probe, right click on the desired probe and select
Delete PTP Clock Probe.
Select OK.
This scoring is used to estimate the frequency and phase recovery of the internal
GE114Pro (SH)/GE114Pro (CSH) telecom slave. Unlike Network Usability, this is the
quality of the slave clock, not the network. The input is PTP packets, the output is a
frequency accuracy and a phase accuracy score of 3, 4 or 5 for each as PM.
The Telecom Slave current configuration and statistics can be viewed by selecting the
Telecom Slave (TS-1-1) under Clock Analysis. See Figure 108 on p. 635 for configuration
view and Figure 109 on p. 636 for statistics summary view.
The Telecom Slave score target values for frequency and phase can be configured by
right clicking on the Telecom Slave (TS-1-1) under Clock Analysis and selecting Edit
Telecom Slave Analysis, then selecting the desired values for Frequency Recovery
Target and Phase Recovery Target in the details pane and clicking on OK. See Figure
110 on p. 636.
To initialize the Telecom Slave PM registers, right click on the Telecom Slave (TS-1-1)
under Clock Analysis and select Edit Thresholds and follow the procedure in Initializing
PM and Distribution Registers.
To edit the Telecom Slave PM Thresholds, right click on the Telecom Slave (TS-1-1)
under Clock Analysis and select Edit Thresholds and follow the procedure in Editing PM
Thresholds.
The procedure for performing PTP Network Analysis assumes that GE114Pro
(SH)/GE114Pro (CSH) is properly connected to the clock inputs to be measured and the
appropriate GE114Pro (SH)/GE114Pro (CSH) interfaces have been configured. See
Provisioning the GE11xPro.
Refer to PTP Network Analysis Parameters to determine the default values, value
ranges and rules for each option in the following procedure.
1. Select the SyncJack icon or select SyncJack from the Applications menu, then
expand the System Selection Tree.
2. Expand the Network Element entity from the Selection Tree, then expand the PTP
Network Analysis entity.
3. Enter a right click on PTP Network Probes in the Selection Tree and select Create
PTP Network Probe.
a) PTP Network Probe Index - EID for the probe. Enter a number from 1 to 2.
(Create only)
b) Name - a text identifier (up to 15 characters, no spaces or special
characters) for the probe. (Required entry)
c) PTP Flowpoint - select the desired PTP Flowpoint from the drop-down list.
The PTP Flow Point used for monitoring by PTP Network Probe must
be able to receive packets from two directions. If the PTP Flow Point
type is OC-Slave, the associated Telecom Slave must have Two-Way
Recovery Mode.
d) IP Version - select the desired IP version from the drop-down list. (Only
IPv4 is supported version for the current release.)
e) Master IP Address - enter the IP address of the master clock (for parallel
mode must be as configured for the PTP SOOC)
f) Slave IP Address - enter the IP address of the slave clock (for parallel
mode must be as configured for the PTP SOOC)
g) Reference - the signal reference for this probe. The available references
are populated in a drop-down list.
h) Reference Expected QL - clock quality level of the selected reference.
The available QLs are provided in a drop-down list.
i) RPDV fw Low (ns) - enter the desired Residual Path Delay Variation
(RPDV) forward, low in nanoseconds
j) RPDV fw Medium (ns) - enter the desired RPDV forward, medium in
nanoseconds
k) RPDV fw High (ns) - enter the desired RPDV forward, high in
nanoseconds
l) RPDV rev Low (ns) - enter the desired RPDV reverse, low in
nanoseconds
m) RPDV rev Medium (ns) - enter the desired RPDV reverse, medium in
nanoseconds
n) RPDV rev High (ns) - enter the desired RPDV reverse, high in
nanoseconds
o) PDV Cluster Range - Assured (ns) - enter the desired value in
nanoseconds
p) PDV Cluster Range - Satisfied (ns) - enter the desired value in
nanoseconds
Select OK.
6. Select the newly created PTP Network Probe entity to verify entry.
7. Enter a right click on SyncJack Schedules in the Selection Tree and select Create
Schedule.
a) Schedule Index - EID for the schedule. Enter a number from 1 to 255.
b) Activity ID - a text identifier (up to 15 characters, no spaces or special
characters) for the probe.
c) Schedule Type - Select the desired type from the drop-down list (Only
“One Shot” is currently supported)
d) Duration - Select either the “Forever” or “Fixed” radio button. If “Fixed” is
selected, enter the desired duration in seconds.
e) Start Time - Select “Now” or “Future” radio button. If “Future” is selected,
enter the date and time for the test to start.
f) Schedule SJ Test Items - Select the desired PTP Network Probe(s) for
this test from the list provided by clicking the related check box(es).
Select OK.
9. Select the PTP Network Probe entity and Configuration tab to view the SyncJack
Schedule State and test progress (State indicates whether the test is Failed, Waiting
(Scheduled), Running or Completed).
10. Click on the PTP Network Probe entity again to observe when the test is completed.
11. During or after the test is completed, the results are available by selecting the desired
PTP Network Probe and selecting the Statistics tab.
Figure 114: View SyncJack PTP Network Probe Statistics (Summary Data)
Figure 115: View SyncJack PTP Network Probe Statistics (15-Minute PM Data)
12. Select the PTP Network Analysis entity in the Selection Tree to view the PTP
Network Analysis results via Dashboard meter (see Figure 116 on p. 642).
13. Select the Network Element entity in the Selection Tree and View the PTP Network
Analysis and Global results via Dashboard meter.
The PTP Network Analysis meter will display test results only if the
associated SyncJack schedule is running and the current Forward
Score and Reverse Scores have been calculated. Each result is
associated with a color coded radio button according to its
Probe/Score (green, yellow or red). If grey, this indicates the
SyncJack schedule running has been completed or no score results
have been calculated.
14. To initialize the PM registers, right click on the PTP Network Probe and select Init
Register and follow the procedure in Initializing PM and Distribution Registers.
15. To edit the PM Thresholds, right click on the PTP Network Probe and select Edit
Thresholds and follow the procedure in Editing PM Thresholds.
16. To delete a SyncJack Schedule, right click on the desired schedule under SyncJack
Schedules and select Delete Schedule.
Select OK.
17. To delete a SyncJack PTP Network Probe, right click on the desired probe and select
Delete PTP Network Probe.
Select OK.
18. Select the SyncJack icon or select SyncJack from the Applications menu, then
expand the System selection tree.
19. Expand the Network Element entity from the selection tree, then expand the Result
Analysis entity.
20. Enter a right click on the MTIE Comparison in the selection tree and select Configure.
1. Ensure that the relevant file transfer protocol is enabled. See Provision System
Options.
2. Select the SyncJack icon or select SyncJack from the Applications menu, then
expand the System folder in the selection tree.
3. Enter a right click on Raw Data Collection in the selection tree and select Edit Raw
Data Server.
6. Expand the Network Element entity from the selection tree, then expand the Clock
Accuracy / Clock Analysis entity.
7. Enter a right click on the relevant Clock Probe or PTP Clock Probe in the selection
tree and select Edit Clock Probe / Edit PTP Clock Probe.
9. Schedule the Probe (See Performing Clock Accuracy Testing or Performing Clock
Analysis).
10. Concatenate the relevant files on the server: e.g., the following script can be used in
Linux:
#!/bin/bash
out_file=$1
shift
header_lines=11
temp_file=[Link]
rm -f $temp_file
rm -f $out_file
echo processing $1
head -n -1 $out_file > $temp_file
gzip -dc $1 | tail -n +$header_lines >> $temp_file
mv $temp_file $out_file
shift
done
E.g., the following command will concatenate all files with CLOCK_PROBE-1-1
string to CLOCK_PROBE_ALL.txt output file:
#Type: Phase
#Frequency: 10
#TimeMultiplier: 1
#Multiplier: 1
#Title: ClockProbe1
#Adva Source: TS
#Adva Direction: NA
Example:
2.3950001938E+03, 4.0000000000E-09
2.3951001938E+03, 4.0000000000E-09
2.3952001938E+03, 8.0000000000E-09
2.3953001938E+03, 4.0000000000E-09
2.3954001938E+03, 4.0000000000E-09
2.3955001938E+03, 4.0000000000E-09
2.3956001938E+03, 4.0000000000E-09
2.3957001938E+03, 4.0000000000E-09
l Path asymmetry
l Symmetric paths performance characteristics in each direction could be significantly
different due to asymmetric queuing and asymmetric OoS.
l Performance of a particular application may depend on one-way performance
TWAMP supports setting timestamps at the reflector end to enable greater accuracy of
two-way delay. This is intended to allow measurement of round-trip network delay by
accounting for the processing time at the reflector. The same timestamps at the reflector
end can be used for one-way measurements. If clocks are synchronized delay and delay
variation can be supported. If clocks are not synchronized, one-way cannot be supported
but one-way delay variation can still be supported. The intention is to support one-way
and two-way measurements using TWAMP.
Simple protocols like ICMP Echo (two-way), UDP Echo (two-way) and ICMP Timestamp
(two-way and one-way) may be used as supported by L3 ESA (Etherjack Service
Assurance). But because of some of the reasons these protocols may not work:
l ICMP Echo and UDP Echo cannot be used for one-way measurements
l ICMP is a protocol that is used to identify problems in IP networks like routing loops
(IP TTL reaching zero), used by higher layer protocols like TCP for various reasons like
destination-unreachability, etc. Even though ICMP as a protocol is necessary in IP
networks, use of ICMP for performance measurements may not work for the following
reasons:
o Certain types of ICMP messages like Echo, Timestamp etc could be blocked by
Refer to the following provisioning order on how to provision the TWAMP configurations
for your sites:
More information on TWAMP and the current implementation can be found in the FSP
150-GE11xPro System Description.
The TWAMP testing can support the test of the layer-3 services
provisioned under the NE. For more information on provisioning the
layer-3 services, see Provision Layer-3 Services and Provision
TWAMP on Traffic IP Interface.
Refer to TWAMP Configuration Options and Rules to determine the default values, value
ranges and rules for each option in the following procedure.
1. Select the TWAMP icon or select TWAMP from the Applications menu, then expand
the System, NE-1 and Communications entities in the Selection Tree, by clicking on
the “+” signs next to each entity.
2. To create a TWAMP IP Interface, right click on the TWAMP IP Interfaces entity and
select Create TWAMP IP Interface.
b) Select the desired Associated Port from the drop-down list of available
ports
c) Enter the desired IPv4 Address and IPv4 Mask
d) Enter the desired MTU size
Click on OK
4. Likewise, repeat the steps above to create a TWAMP IP Interface at the Reflector
end.
5. To view the TWAMP IP Interface, select TWAMP IP Interfaces entity under TWAMP
view to display the list of configured IP Interfaces in the facility configuration pane.
6. Enter a right click on the desired IP Interface and select View Configuration.
7. To close the IP Interface Configuration view, click the “x” on the facility tab.
9. Enter a right click on the desired IP Interface and select Edit Configuration.
Click on OK.
11. To delete a TWAMP IP Interface, select TWAMP IP Interfaces entity under TWAMP
view to display the list of configured IP Interfaces in the facility configuration pane.
12. Enter a right click on the desired IP Interface and select Delete TWAMP IP Interface.
14. Likewise, perform the desired operations as above on the TWAMP IP Interface of the
Reflector end as necessary.
15. To create a Control Client, expand System and NE-1 entities under TWAMP
application view. Enter a right click on Control Clients and select Create Control
Client.
16. Enter or Select the following data to configure the Control Client:
17. To view a Control Client, select the Control Clients entity to display the list of
configured Control Clients in the facility configuration pane.
18. Right click on the desired Control Client and select View Configuration.
19. To close the Control Client view, click the “x” on the facility tab.
20. To edit a Control Client, select Control Clients to display the list of configured Control
Clients in the facility configuration pane.
21. Enter a right click on the desired Control Client and select Edit Configuration.
Click on OK.
23. To delete a Control Client, select the Control Clients entity to display the list of
configured Control Clients in the facility configuration pane.
24. Right click on the desired Control Client and select Delete Control Client.
26. To create a Session Sender, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
27. Right click on the Session Sender entity and select Create Session Sender.
Identification
n) Select the relevant check boxes for Outer and/or Inner VLAN, and if
selected, enter the Ethertype and VLAN Tag information.
History Configuration
p) Edit the Two Way Delay Min, Max and Bins as required
q) Edit the One Way S2R and R2S Delay settings as required
r) Edit the One Way S2R and R2S PDV settings as required
Click on OK.
29. To view a Session Sender Configuration, expand System and NE-1 entities by
clicking on the “+” signs next to each entity under TWAMP application view.
30. Right click on the desired Session Sender and select View Configuration.
31. To close the Session Sender Configuration view, click the “x” on the facility tab.
32. To view a Session Sender Configuration Statistics, expand System and NE-1 entities
by clicking on the “+” signs next to each entity under TWAMP application view.
33. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
View Config Statistics.
34. To close the Session Sender Statistics Configuration view, click the “x” on the facility
tab.
35. To view Session Sender Thresholds, expand System and NE-1 entities by clicking on
the “+” signs next to each entity under TWAMP application view.
36. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
View Thresholds.
37. To close the Session Sender Thresholds view, click the “x” on the facility tab.
38. To edit a Session Sender, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
39. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
Edit Configuration.
Identification
m) Select the relevant check boxes for Outer and/or Inner VLAN, and if
selected, enter the Ethertype and VLAN Tag information.
History Configuration
o) Edit the Two Way Delay Min, Max and Bins as required
p) Edit the One Way S2R and R2S Delay settings as required
q) Edit the One Way S2R and R2S PDV settings as required
Click on OK.
41. To Edit Session Sender Thresholds, expand System and NE-1 entities by clicking on
the “+” signs next to each entity under TWAMP application view.
42. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
Edit Thresholds.
Click on OK.
44. To delete a Session Sender, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
45. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
Delete Session Sender.
47. To add a Session Sender, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
48. Select the Control Clients entity to display the list of configured Control Clients in the
facility configuration pane. Right click on the desired Control Client and select Add a
Session Sender.
Click on OK.
50. To remove a Session Sender, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
51. Select the Control Clients entity to display the list of configured Control Clients in the
facility configuration pane. Right click on the desired Control Client and select
Remove a Session Sender.
Click on OK.
53. To create a server, expand System and NE-1 entities by clicking on the “+” signs next
to each entity under TWAMP application view.
54. Right click on the Servers entity in the selection tree and select Create Server.
56. To view a Server, expand System and NE-1 entities by clicking on the “+” signs next
to each entity under TWAMP application view.
57. Select the Servers entity to display the list of configured Servers in the facility
configuration pane. Right click on the desired Server and select View Configuration.
58. To close the Server Configuration view, click the “x” on the facility tab.
59. To edit a Server, expand System and NE-1 entities by clicking on the “+” signs next to
each entity under TWAMP application view.
60. Select the Servers entity to display the list of configured Servers in the facility
configuration pane. Right click on the desired Server and select Edit Configuration.
Click on OK.
62. To delete a Server, expand System and NE-1 entities by clicking on the “+” signs next
to each entity under TWAMP application view.
63. Select the Servers entity to display the list of configured Servers in the facility
configuration pane. Right click on the desired Server and select Delete Server.
64. To create Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
65. Right click on the Session Reflector entity and select Create Reflector.
Select the desired Associated IP Interface name from the drop-down list of
available names
The UDP Port number at Session Reflector end should match the
UDP Port at the Session Sender end.
Click on OK
67. To view a Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
68. Select the Session Reflectors entity to display the list of configured Session
Reflectors in the facility configuration pane. Right click on the desired Reflector and
select View Configuration.
69. To close the Session Reflector Configuration view, click the ‘X’ on the facility tab.
70. To edit a Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
71. Select the Session Reflectors entity to display the list of configured Session
Reflectors in the facility configuration pane. Right click on the desired Reflector and
select Edit Configuration.
Select the desired Associated IP Interface name from the drop-down list of
available names
Click on OK.
73. To delete a Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
74. Select the Session Reflectors entity to display the list of configured Session
Reflectors in the facility configuration pane. Right click on the desired Reflector and
select Delete Reflector.
75. To add Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
76. Select the Servers entity to display the list of configured Servers in the facility
configuration pane. Right click on the desired Server and select Add Session
Reflector.
Click on OK.
78. To remove Session Reflector, expand System and NE-1 entities by clicking on the “+”
signs next to each entity under TWAMP application view.
79. Select the Servers entity to display the list of configured Servers in the facility
configuration pane. Right click on the desired Server and select Remove Session
Reflector.
Click on OK.
Start Session
81. To Start a Session, expand System and NE-1 entities by clicking on the “+” signs next
to each entity under TWAMP application view.
82. Select the Control Clients entity to display the list of configured Control Clients in the
facility configuration pane. Right click on the desired Control Client and select Start
Sessions.
84. To view Session Sender Statistics, expand System and NE-1 entities by clicking on
the “+” signs next to each entity under TWAMP application view.
85. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
View Statistics.
86. Click the Stats facility tab to update the statistic data shown in the table while the
TWAMP sessions are in progress.
88. To close the Session Sender Statistics view, click the “x” on the facility tab.
Stop Session
89. To stop a session, expand System and NE-1 entities by clicking on the “+” signs next
to each entity under TWAMP application view.
90. Select the Control Clients entity to display the list of configured Control Clients in the
facility configuration pane. Right click on the desired Control Client and select Stop
Sessions.
Clear PM Registers
92. To clear Session Sender PM registers, expand System and NE-1 entities by clicking
on the “+” signs next to each entity under TWAMP application view.
93. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
Clear PM Registers.
Click on OK.
95. To clear Session Sender distribution registers, expand System and NE-1 entities by
clicking on the “+” signs next to each entity under TWAMP application view.
96. Select the Session Sender entity to display the list of configured Session Sender in
the facility configuration pane. Right click on the desired Session Sender and select
Clear Dist. Registers.
Click on OK.
99. Go to 1.
1. After all necessary layer-3 provisioning is done, proceed with Session Sender, Control
Client, Session Reflector and Server provisioning. Go to 15 to 98.
2. Go to 1.
This chapter contains information supporting alarms and events generated by the
system, their meaning and suggested trouble clearing methods. This chapter contains
the following information:
The following procedure lists the steps to identify, isolate, and correct conditions that
cause alarms reported in the web-based GUI Alarm Window.
1. Ensure that an interface device, such as a craft interface, is connected to the network
and is operating correctly before continuing.
2. Establish a communication connection to the FSP 150CC(s) and log on. See Logging
On and Off.
3. Observe the Alarms Pane to view all current alarms, and record the alarm severity.
See Getting Familiar with the Web-based GUI for an overview of the web-based GUI
components and the location of the Alarm Window.
4. Determine which current alarm has the greatest service effect, and record the alarm.
Service-affecting (SA) critical alarms should be cleared first, followed by Major SA
alarms, and then Minor SA alarms. Then any remaining non-service-affecting (NSA)
major alarms should be cleared, followed by any minor alarms.
6. Refer to Alarm Attributes, Probable Cause and Trouble Clearing for identifying,
interpreting, and troubleshooting alarms.
7. Refer to Connector and LED Descriptions for descriptions of connectors and front-
panel LED indications.
8. After performing suggested trouble clearing actions, did the alarm or status condition
clear?
a) If YES:
Record the time the alarm was cleared, and continue with the next step.
b) If NO:
Obtain ADVA Optical Networking technical assistance (see below).
10. Observe the Alarms Pane to view all current alarms. Have all alarm conditions been
cleared?
a) If YES:
Go to the next step.
b) If NO:
Obtain ADVA Optical Networking technical assistance (see below).
l System
l Network Element
o BFD Session
o DCN Port
o EoMPLS PW
o L3 VRF
o NTE11xPro Shelf
o NTE11xPro Card
o Power Supply (PSU) - GE112Pro (H)/GE114Pro (SH)/GE114Pro (CSH)/GE114Pro
(HE)
o Traffic IP Interface
o Mobile Modem (Not Apply to GO102(S) or GO102(SP))
l Synchronization - GE114Pro (SH)/GE114Pro (CSH)
o 10MHz (CLK) Port/Pulse Per Second (PPS) Port/Time Of Day (TOD) Port
o BITS In Port
o BITS Out Port
o GPS
o SYNC-1-1-1-1
l Time Clock
l PTP Alarms - GE114Pro (SH)/GE114Pro (CSH)
o PTP Clock
o PTP Port
o SOOC
o Telecom Slave
l Network Port and Access Port Alarms
l CFM Maintenance End Point Alarms
l CFM QoS Shaper Alarms
l LAG Alarms
l SAT Responder Session Alarms
l ERP Alarms
l SyncJack Alarms - GE114Pro (SH)/GE114Pro (CSH)
l Open Flow Alarms
l Secure Flow Alarms - GE114Pro (C)/GE114Pro (CSH)
System
1) Verify that the IP address can be reached (respond to
Backup NTP Server Attempt to connect to the pings) by performing both a ping and a trace route from the
Failed Backup NTP Server failed. management tunnel’s IP address.
{Superscript}
2) Verify management communication configuration. Minor N/A N/A
a) Target IP address connectivity
a) Repair IP address connectivity or routing problem.
or routing problem.
b) No NTP server / NTP server
b) Switch to Primary NTP Server. Repair NTP server.
down.
Data Base - File Trans- Database file transfer is in pro-
No action required. Not Reported N/A N/A
fer In Progress gress.
1) Verify that the IP address can be reached (respond to
pings) by performing both a ping and a trace route from the
DataExport FTP Fail The Data Export via FTP failed. DCN IP address Minor N/A N/A
2) Very that the User Name, Password and Export Path
are correct.
Database Downgrade - imple- 1) Verify that this database contains the desired data.
DB Downgrade mentation of a database file 2) If required, obtain latest database file, otherwise - No Not Reported N/A N/A
below the current release level. Action Required.
File Transfer In Pro-
File transfer is in progress. No action required. Not Reported N/A N/A
gress
IP Address Conflict (declared
IP Address Conflict when a DHCP assigned address Verify management communication configuration. N/A CR N/A
overlaps with an existing subnet)
1When using Ethernet encapsulated management tunnels, the source IP address of the ping used to validate reachability of the trap host is the IP address assigned to the
management tunnel, and not the system IP address.
The ARP Table is full for Inter- Delete old useless ARP entries or wait for ARP Entry to
Traffic ARP Table Full Minor N/A N/A
face Route. age out to clear this alarm, or no action required.
Network Element
BFD Session
1. Check physical connection.
BFD session is down mainly 2. Check the settings on nodes.
because the local node cannot
BFD Session Down receive BFD control packets for 3. Enlarge the local packet detection time and shorten the N/A Minor N/A
negotiating transmission interval local transmission interval for BFD control packets.
and packet detection time.
4. Switch Session Control from Admin Down to None or
set the administrative state to IS/Management.
DCN Port
Check physical cabling, MDIX is not supported on DCN
Cable disconnected, cable fault,
Link Down port. Check settings on system to match DCN network N/A Not Alarmed N/A
improper configuration.
requirements.
EoMPLS PW
The destination of EoMPLS tun-
nel cannot be resolved, i.e., the
remote MAC address cannot be
discovered because the local When ARP response is received, the MAC address entry
Destination Unre- node hasn’t begun to send ARP will be updated and the alarm will be cleared. The soaking
N/A Major N/A
solved request to or get ARP response time for this alarm is 2.5 seconds and the clear soaking
from the remote node for des- time is 10 seconds.
tination MAC address, or ARP
request is failed or because the
MAC entry is aged out.
L3 VRF
Maximum number of VRF routes
supported by VRF has been Delete the existing route to add a new route or add the
No Route Resources N/A Major N/A
reached and new routes cannot route to another VRF.
be installed.
Mobile Modem (Not Apply to GO102(S) or GO102(SP))
Link Down is generated when a Perform an Etherjack Diagnostic test. Repair the port
Link Down physical connection is lost on the using test results. NA N/A N/A
port.
Unplug the USB modem, insert the SIM card into the
No SIM Card No SIM card is detected. NA N/A N/A
modem, and re-insert the USB modem into the USB port.
The modem is not qualified by Install an ADVA Optical Networking qualified USB
Modem is not qualified NA N/A N/A
ADVA Optical Networking. modem.
Modem is removed from the USB Re-insert ADVA Optical Networking qualified USB
Modem Removed NA N/A N/A
port. modem.
NTE11xPro Shelf
Check ambient temperature and adjust. Verify that airflow
Equipment has exceeded the
Over Temperature requirements are met. See Air Flow Requirement in FSP Minor N/A Status Red
temperature limit (>= 90 C).
150-GE11xPro System Description document.
System temperature has dropped
below the minimum temperature
Under Temperature Check ambient temperature and adjust. Minor N/A Status Red
threshold
(<= -50 C).
NTE11xPro Card
Communication Fail-
Communication Failure Equipment is malfunctioning. Repair or replace unit. Minor N/A N/A
ure
Alarm Indication Signal BITS Alarm Indication Signal. Not Reported N/A N/A
If a T1 is the desired BITS Line Type, then Network Clock
Type should be set to "Option 2".
PTP Clock
PTP Clock in Frequency Freerun. The recovered clock
PTP Clock in Fre- Verify and troubleshoot clock and ref-
is the same as the internal oscillator and the PTP Not Reported N/A N/A
quency Freerun erence and provisioning.
Clock is in freerun.
PTP Clock in Fre- Verify and troubleshoot clock and ref-
PTP Clock Frequency recovery is in Holdover. Not Reported N/A N/A
quency Holdover erence and provisioning.
PTP Clock in Time
PTP Clock is not locked to TOD. N/A Not Reported N/A N/A
Freerun
PTP Clock in Time
PTP Clock time recovery in Holdover. N/A Not Reported N/A N/A
Holdover
PTP Clock Fre-
Verify and troubleshoot clock and ref-
quency Not Trace- PTP Clock Frequency Not Traceable. Minor N/A N/A
erence and provisioning.
able
PTP Clock Time Not Verify and troubleshoot clock and ref-
PTP Clock Time Not Traceable. Major N/A N/A
Traceable erence and provisioning.
switch.
A Sync Reference has been locked out. Test the Locked Out Sync
Sync Reference
Usually due to failure, configuration changes planned Reference and remove lock
Locked Out Minor N/A N/A
or maintenance out when reference is fully
(for future)
operations. functional again.
Sync Reference A manual switch operation has been Evaluate reason for the
Manual Switch Minor N/A N/A
(for future) performed on a Sync Reference. manual switch operation.
Sync Reference Wait
A Sync Reference has been restored and is
To Restore No Action Required. Minor N/A N/A
in WTR timing.
(for future)
the Expected QL. The PTP Clock's QL Verify and troubleshoot clock
Sync QL Mismatch Minor N/A N/A
Mode attribute must be configured as reference.
Multiple Peers - alarm is asserted if PTP Port received for 50 -70 sec
Multiple Peers Port received one Announce messages Announce messages from single PTP N/A Major N/A
Port. Verify and troubleshoot network
from more than one PTP Port. and
provisioning.
All Slave-Only Ordinary Clocks (SOOC) failed. The Verify and troubleshoot clock ref-
All SOOCs Failed OC-S Virtual Port in a Faulty state or a PTSF Alarm erence. N/A Critical N/A
exists on the SOOC.
Sync Reference Wait A Sync Reference has been restored and is in WTR
No Action Required. Minor N/A N/A
To Restore timing.
Telecom Slave in Freerun. The recovered clock is the Verify and troubleshoot clock reference
Telecom Slave in
same as the internal oscillator and the Telecom Slave and provisioning. Not Reported N/A N/A
Freerun
is in freerun.
Telecom Slave in Holdover. The recovered clock is in Verify and troubleshoot clock reference
Telecom Slave in Hol- and provisioning.
holdover as there is no valid SOOC to support clock Not Reported N/A N/A
dover
recovery.
After sending provisioning when it fails either Verify provisioning and adjust accord-
AMP Provisioning Fail because it receives a message from the client Minor N/A N/A
ingly.
that it failed to apply provisioning or a timeout has
occurred waiting for a client to respond to a pro-
visioning message.
Bandwidth Exceeds
Verify provisioning and adjust accord-
Negotiated Speed Bandwidth Exceeds Negotiated Speed. Minor Major Facility Red
ingly.
(Access Port only)
1SFP (PN: 1061705878-01 SFP/DPI/GBE/850I/MM/LC/TIN) and SFP (PN: 1061705879-01 SFP/DPI/GBE/1310S/SM/LC/TIN) cannot be used as sync reference, or a
Frequency Offset alarm is raised for a sync reference when clock selector detects a frequency offset greater than +/- 4.6ppm. This specific behavior is an outcome of the
SFP doing a store and forward and using a low accuracy oscillator to generate signals.
1If the Network Port RFI alarm notification code is set to Not Reported or Not Alarmed, then the Link Loss Forwarding feature will not activate for that alarm attribute.
Erroneous CCM 3. CCM interval does not match the interval configured N/A Minor N/A
for the receiving MEP’s MA.
2) All MEPs on the same interface are reporting that Verify the Remote MEP LAN interface
the port is blocked (i.e., all remote MEPs’ Bridge Ports connection and configuration.
are not forwarding data).
Some MAC Status Troubleshoot and repair the Remote N/A Minor N/A
The problem lies at the starting point of the service MEP interface connection or recon-
instance (the Remote MEP) and probably not any- figure the interface.
where in the network used by the MA. In FSP
150GE11xPro CCMs generated do not have Port
Status or Interface Status TLVs, but the TLVs are
handled if CCMs are received containing them.
At least one of the Remote MEPs is sending CCMs
Observe MEP alarm conditions at the
with Remote Defect Indication (RDI) set.
remote node.
Some RDI RDI is present in the CCMs transmitted when any of N/A Minor N/A
Perform appropriate steps in this table
the other MEP alarm conditions (above) exist for a
to clear the condition at the far end.
Remote MEP.
MEP alarm attributes are editable in CFM mode (by selecting Applications and then CFM or selecting the CFM icon).
LAG Alarms
Refer to the following table for LAG alarm conditions and their associated probable cause, default notification code and suggested trouble clearing
procedure.
ELP Alrams
Refer to the following table for ELP alarm conditions and their associated probable cause, default notification code and suggested trouble clearing
procedure.
ERP Alarms
Refer to the following table for Ethernet Ring Protection (ERP) alarm conditions and their associated probable cause, default notification code and
suggested trouble clearing procedure.
Clock Probe
SJTEST Reference Probe Reference signal failed. May be caused by sig- For case of external signal, check
Minor N/A N/A
Fail nal loss or signal accuracy degradation detected. cable connection.
Probe source signal failed. May be caused by signal For case of external signal, check
SJTEST Source Fail Minor N/A N/A
loss or signal accuracy degradation detected. cable connection.
PTP Clock Probe
Validate PTP Clock Probe con-
SJTEST No Mes- PTP Clock Probe does not receive PTP event mes-
figuration, check connectivity to the Minor N/A N/A
sages sages from the clock under test.
clock under test.
SJTEST No PTP Clock Probe does not receive valid timestamps in Make sure PTP Clock under test event
Minor N/A N/A
Timestamp the PTP event messages. messages comprise valid timestamps.
SJTEST Reference Probe Reference signal failed. May be caused by sig- For case of external signal, check
Minor N/A N/A
Fail nal loss or signal accuracy degradation detected. cable connection.
PTP Network Probe
Validate PTP Network Probe con-
SJTEST No Mes- PTP Clock Probe does not receive PTP event mes-
figuration, check connectivity to the Minor N/A N/A
sages sages from the clock under test.
PTP network under test.
SJTEST Reference Probe Reference signal failed. May be caused by sig- For case of external signal, check
Minor N/A N/A
Fail nal loss or signal accuracy degradation detected. cable connection.
Alarm Masking
Refer to the following tables for alarm masking, where certain alarms or conditions may
mask the raising of an underlying condition, and until the “masking” alarms are cleared,
the underlying alarms may not be seen.
or efmfail
1EFM OAM - Remote Loopback Failed alarm's provisionable severity levels are not declared. EFM OAM - Remote Loopback
Failed alarm only occurs when a port is in the Maintenance state, and the Maintenance state forces alarms to NR regardless of
the provisioned severity level.
9 Athentication failed
Invalid password
ENTITY CONDITIONS
256 Entity does not exist.
257 Entity already exists.
258 Next child entity does not exist.
259 Set operation is not supported.
260 Create operation is not supported.
261 Delete operation is not supported.
262 _actiontype_ operation is not supported.
263 Get variable objects operation is not supported.
264 Maximum (_maxnum_) number of _entityname_ entities has been reached.
265 Total _rsrc_ resource amount of _totalval_ exceeds max limit of _maxval_
Invalid EID: _why_
Id cannot be 0
267 Protection Group Id must be 1
Traffic IP Interface number in Traffic IP Interface’s Eid should not exceed the maximum
number of Traffic IP Interface (xxx).
Operation denied: _why_
Object is transient
(EID) MD name causes MA ID length to exceed limit (xxx MIN... yyy MAX)
(xxx) does not have enough tags for ConnectGuard Secure Flow
(xxx) is in the Synchronization Reference List, a port in the reference selector list cannot be
unassigned
(xxx) is not applicable for N2A COS Priority when ITAG control is not (yyy)
A member in the VID list (xxx) matches the primary vid of vlan entry [eid]
An Ethernet port with speed configured as (xxx) cannot be added to the reference selector list
271 - 275 An Ethernet port with SyncE mode disabled cannot be added to the reference selector list
(Continued) AIS client MD level (xxx) must be greater than MEP MD level of (yyy)
A port can only be added to the reference selector list if its signal direction is input
ARP Entries for interfaces other than eth0 exist in the system
Cannot have both Primary and Backup server's IP addresses set to zero
Cannot modify A2N shaping type if the flow is not in UNASSIGNED state
Changing Service Type and Admin State is not allowed in one operation. Admin
Cannot unassign a port if the port is provisioned as Ring Port 0 ""or Ring Port 1 of an ERP
instance
If PPS is output state and source id is PTP Clock, it’s not allowed to delete the PTP Clock
If TOD Source id is PTP Clock, it’s not allowed to delete the PTP Clock
(Continued) Inner VLAN Tag enabled without Outer VLAN Tag enabled
Interface (name) cannot be set to (dhcprole) role when Management Traffic Bridging is enabled
Invalid primary vid - must be 0, component primary vid or must be from the vlan table
Ipv6 Forward can’t be set when Stateless Address Auto Configuration is enabled on any
interface
(loopbacktype) is not available when a Management Tunnel is on (xxx) whose working path is
(yyy) and Management Traffic Bridging is enabled
271 - 275
ITAG is not allowed when JDSU loopback is enabled on (xxx)
(Continued)
ITAG is not allowed when Access Interface Learning Confront is enabled
Loopback is active on (xxx), both member ports of protection group cannot change media type
Management port (portid) (name) cannot be in (xx) state when Management Traffic Bridging is
enabled
Management prot (portid) (name) cannot have Fixed Speed and Half-Duplex mode (portspeed)
when Management Traffic Bridging Security is enabled
MA Name format cannot be set to (xxx) when MD Name format is set to (yyy)
Management Tunnel cannot be created when Terminal Loopback is on the port and
Management Traffic Bridging is enabled
Master IP Address must not be MCI’s Master IP Address when PTP FlowPoint is Monitoring
Members List and Tag Control cannot be modified when EVC is associated with PTP Flow
Point, Transparent Clock or SOOC
system
MD Name format cannot be set to (xxx) when (eid) Name format is set to ICC format
Not allowed to enabled OpenFlow if the port is configured with EPL mode
Not allowed to enable OpenFlow if there is MAC based management tunnel associated with
this port
Not allowed to disable Open Flow if any OFFlow is associated with this port as Ingress port or
Egress port
Not allowed to modify the Configured Speed when this port is OpenFlow enabled
Not allowed to configure the Configured Speed as Auto when this port is OpenFlow enabled
NE already accepted
Number of Max Static Slave supported is higher than number of total slaves
Not allowed to remove member port when JDSU Loopback is enabled on the LAG
Only fully provisioned Telecom Slave can be “Reference for SyncJack Probe”
Only fully provisioned Telecom Slave can be “Source for SyncJack Probe”
Only fully provisioned Telecom Slave can be “System Time Of Day PTP Clock”
Only fully provisioned Telecom Slave can be System Time of Day PTP Clock
Port based Down MEP with more than 1 remote MEP is not supported
Port Level Up MEP and VID level Up MEP cannot exist together on the same port
Primary VID MANET name is not same as MACOMP primary VID (xxx)
Probe is single-COS
PTP Clock Eid must be set as Telecom Slave when “System Time Of Day” is PTP CLOCK
PTP CLOCK Eid must be set as Time Clock when “System Time Of Day” Type is TIME
CLOCK
PTP Access Flow Point’s parent port must be the same as Service Flow’s parent
PTP Clock Eid must be set when System Time of Day is PTP Clock
(271-275) Reference must be the same for all PTP Clock Probes
Should not modify CTag/ITag/STag Control when the flow is associated with CFM MACOMP
Slave IP Address must not be SOOC’s Slave IP Address when PTP Flow Point is Monitoring
SOAM frame interval and DMM frame interval are both required to be set.
SOAM frame size and DMM frame size are both required to be set.
Source MEP (yyy) does not belong to the Source Port (xxx)
instance
SAT Test does not support the Port based Down MEP
(271-275) SAT Responder cannot be enabled when the MEP is associated with the probe
Slave IP Address must not be SOOC’s Slave IP Address when PTP Flow Point is Monitoring
Telecom Slave cannot be the system TOD Source if the clock recovery mode is one-way
The combination tags of Outer VLAN Tags and Inner VLAN Tags are not unique
The port should not be the source port of the ECPA Test
The file name must be 1-32 characters long, must have only a-z, A-Z, 0-9, (.), - and _, but can
not be (.) or (..)
The mep is enabled for SAT responder, thus, cannot be referred by probe
The port should not be provisioned as Ring Port 0 or Ring Port 1 of an ERP
The combination of Outer Vlan Tags and Inner Vlan Tags is not unique
The File description is invalid, length of string is 0-127 and can't contains double quotation
marks “ “, semicolon(;) and pound (#)
The PTP Flowpoint creation on the Network Port 2 is denied if it is not an independent
Network Port
Two vlan entries cannot have the same VID list for the same port
When A2N PBB Frames is enabled, th combination of CTAG control and STAG control are
just allowed (NONE, NONE) and (PUSH, PUSH)
(271-275)
When A2N PBB Frames is enabled, the Untagged Frames must be enabled.
When ITAG control is set, ITAG ID must be provisioned with a non-zero value.
When the Flow has pushed S-Tag, the Outer Vlan Ethertype must be 0x88a8When the Flow
has pushed C-Tag, the Outer Vlan Ethertype must be ox8100
Two vlan entries cannot have the same VID list for the same port
VID list size exceeds the maximum of [MaxVlanMbrs] including the Primary VID
276 Attribute values are inconsistent
277 _entityname_ does not exist
An Ethernet port with SyncE mode disabled cannot be added to the reference selector list
(xxx) C-Tag Control option is not applicable when service type is (yyy)
(xxx) doesn’t have one of the following valid tag control configurations: 1.
STagControl=PUSH, CTagControl=NONE;[Link]=NONE, CTagControl=PUSH;
[Link]=NONE, CTagControl=PUSHVID (yyy)
(xxx) flow with UNTAGGED support need to have different COS level support
(xxx) is in a lag
An Access Port cannot have a combination of Access Port UP MEP and Service UP MEP.
An Ethernet port with SyncE mode disabled cannot be added to the reference selector list
A port can only be added to the reference selector list if its signal direction is input
Cannot be empty
Cannot enable QL Mode because the port configuration does not support SSM
Crypto password accept alphabetic and numeric characters only, and case insensitive
Data TLV exceeds the allowed maximum of (xxx MIN... yyy MAX)
Empty string
Filename is empty
ID must be 1
Invalid character
Invalid IP Address
Invalid port
It is not allowed that both corresponding flow entries under vlan table and main table are
configured as VLAN ID disabled
It is not allowed to create more than one flow table with the same table id
It is not allowed that OF port is associated to the other physical port except Network port and
Access port
512 It is not allowed that more than two Pop actions in the Action List
(continued) It is not allowed that there are two Pop actions in the Action List under main table apply-action
instruction except single connection
It is not allowed that there is one Pop action in the Action List under Vlan table write-action
instruction
It is not allowed that the specified vlan pcp of flow entry under main table is not equal to
corresponding flow entry under vlan table and the vlan table flow entry does not have specified
pop action but specified vlan pcp
It is not allowed to create unidirectional flow when the in-port between the flow entries under
vlan table and main table are different
Name must be 1- (xxx) characters long and contain only alphanumeric characters
Negative number
NTP is disabled
Only multicos flow can provision flow based priority mapping profile
Option 82 Sub 1 must be Disabled if the interface side of the traffic IP interface is configured
as server
Option 82 Sub 2 must be Disabled if the interface side of the traffic IP interface is configured
as server
Pathname is empty
ROLLOVER
Selected MEP destination type does not allow to specify MAC address
Source Type = Frequency is not valid with Telecom Slave as SourceEid (xxx)
SyncE Mode cannot be disabled because this port is used in the reference selector list
SysLog is disabled
TACACS Default Privilege Level can be: retrieve, maintenance, provisioning, superuser.
The maximum is 32
The next table of VLAN table only allows going to main table
The number of Destination MEPs cannot exceed the number of Remote MEPs
The Queue number (xxx) is reserved for all queues in the port
The vid of the outer tag of (xxx) is different from the primary vid of the MACOMP
in MANET
The output port id is not equal to the port id of the Queue associated to the OF Flow
Total provisioned CIR (xxx) bps exceeds port speed (yyy) bps
Traffic IP Interface (xxx) is the second server configured over (yyy). Only single server is
allowed
TS phase signal configuration should be allowed only if TS is configured with Clock recovery
mode set to Two Way
512 Tunnel already exists on (xxx)
(continued) Tunnel index must be from 1 to 255
Unknown interval
Unknown/unsupported
Vendor Class ID/opt60 must be Disabled if the interface side of the traffic IP
When the Secure State is (xxx), the flow must be associated with a Secure Flow
Login failed
8192 Invalid message received
8193 Invalid user
8194 Unable to update profile
8195 Internal error
8196 Internal error
8197 Internal error - IPC
8198 Internal error
8199 Internal error - EP
8200 Invalid user name received
8201 insufficient privilege level
SNMP SPECIFIC
20480 Attribute is deprecated
20481 VLAN ID is not specified
20482 Invalid Data for Cable Length Benchmark, Required format [Link]
Administration State
There are a number of rules related to the behavior of the Administrative state as it relates
to the parent/child relationship of objects. For example, there are certain states for a child
that are 'invalid' if the parent state is not already in that state. The administrative state
model consists of the following states:
l IS (in-service) - this is the 'normal' state for an entity that is configured to be fully
operational.
l Management - this is referred to as the “Out of Service” state. In this state, all alarms
for the entity will be squelched. Any Standing Alarm will be cleared and re-raised as a
non-alarmed (NA) condition. The intended use of this state is to squelch alarms that
the user is not interested in. In addition, for any 'traffic affecting' provisioning change,
the entity should be put into this state (although there is no enforcement of this
requirement). The additional characteristics associated with this state are that the user
data and management traffic will continue to flow.
l Maintenance - this is ALSO an “Out of Service” state (i.e., it inherits the properties
described above). The additional characteristic associated with this state is that
'maintenance' operations are allowed to be performed against an entity in this state
which may affect user data or management data. Maintenance state operations
include things like Loopback, Etherjack diagnostic, etc.
l Disabled - this is ALSO an “Out of Service” state (i.e., it inherits the properties
described above). The additional characteristic associated with an entity in this state
is that no user data traffic will pass. The intended use of this state is to allow the user
traffic to be 'disabled' while still preserving management connectivity with the entity.
l Unassigned - this state is essentially equivalent to an entity being 'deleted'. An entity
in this state is not factored into any of the rules checking and will not be alarmed or
carry traffic. The Administrative State must first be set to Unassigned state prior to
changing the Service Type of a Network Port or Access Port.
l The equipment Administrative state model will only utilize the In-service and
Management states
l When in the Management or Maintenance state, all alarms against that entity will be
suppressed. The entity will otherwise function as normal.
l When in the Disabled state, user data traffic is suppressed.
l In order to perform maintenance actions on an entity (e.g., Loopback, Diagnostics,
etc.) the entity must first be put into the Maintenance state.
l An entity in the Disabled state will not pass user data traffic. Management traffic (i.e.
Management Tunnel traffic and EFM OAM) will continue to pass in this state.
o Outage
l The facility Administrative state model will utilize all states described above. The
exception to this is the following: The Disabled State only applies to Access Ports.
Network Ports do not support the Disabled state. In regards to Network Ports, the
Unassigned State does not apply to the working Network port. The working Network
port cannot be Unassigned.
l The DCN facility Administrative state model is limited to the following states:
o In-service
o Management
o Unassigned
l EVC (Flows), Policers and Shapers support the following states:
o In-service
o Management
o Disabled
o Unassigned
EVC (Flows) - Admin state control between In-service and Management is supported.
Disabled and Unassigned is derived from the parent port. Policers and Shapers - Admin
state is read-only. State is ALWAYS derived from parent EVC.
Users may edit the state of the Equipment, Port and EVC (Flow). The Policer and Shaper
states are derived directly from the EVC (Flow) state. Editing the EVC state is allowed
according to the rules outlined below. It should be noted that the state of the individual
EVC can be overwritten by a subsequent edit of the parent Port object (see behavior rules
defined below).
l If an Equipment entity is In-service, its child entities Port entities can be in any state
(supported by that entity).
l If an Equipment entity is Management, its child entities can be in any “Out of Service”
state or Unassigned.
l If an Equipment entity is Unassigned, its child entities must be unassigned.
l If a Port Entity is in In-Service state, its child entities (EVCs) can be in In-Service,
Management or Unassigned state.
l If a Port Entity is in Management, Maintenance or Disabled state, its child entities can
be in Management or Unassigned state
l If a Port Entity is in Unassigned state, its child entities must be in Unassigned state.
Parent/Child rules for EVC (Flow) entities. Note that child entities of EVCs are not user
editable.
l If an EVC Entity is in In-Service state, its child entities (policers, shapers) will be in In-
Service.
l If an EVC Entity is in Management state, its child entities will be in Management.
l If an EVC Entity is in Unassigned state, its child entities will be in Unassigned state.
Changing the Equipment entity state from In-Service to Management will have the side-
effect of changing the Port state from In-Service to Management. Any Port that was
already in an OOS state (i.e. Management, Maintenance or Disabled) will stay in that
state. Any Port that was already in the Unassigned state will stay in the Unassigned
state.
Changing an Equipment entity from Management to In-service will NOT have any side-
effect on the Port state. The Port state will remain as it was.
Due to the many-to-one relationship between Port entities and EVCs (Flows), the
following behaviors will be implemented:
This effect will also occur as a result of an edit of the Port's parent
entity. For example, if the Equipment entity state is edited in such a
way that it affects the Port's Administration state, the above rules will
apply such that the effect is propagated to the Port's child entities
also.
Due to the many-to-one relationship between Port entities and EVCs (Flows), the
following behaviors will be implemented:
This effect will also occur as a result of an edit of the EVC's parent
entity. For example, if the Port entity state is edited in such a way that
it affects the EVC's Admin state, the above rules will apply such that
the effect is propagated to the EVC's child entities also.
Operational State
This attribute contains the current actual state of the entity. It is based on the provisioned
state plus the actual physical state of the entity.
Secondary State
This attribute refines or provides added information regarding the Operational State of the
entity.
Refer to the following table for state values and their definitions.
1The Crypto privilege level is only available in GE114Pro (C) and GE114Pro (CSH) which support
ConnectGuard [Link] user with Crypto privilege is crypto user. By comparison, the other user privileges
are non-crypto and the corresponding users are non-crypto users.
2The NetConf privilege level is only applicable in NetConf/YANG interface. The user with NetConf privilege
can only be created on GUI/CLI by a user with Superuser privilege. Up to 3 simultaneous NetConf user
sessions are supported.
The following configuration options and rules tables provide high level option descriptions
and valid entries using the web-based Element Management System (EMS) GUI. The
high level option descriptions provided here assume a good working knowledge of the use
of each option, and are intended to be used as a guide to operate, configure and maintain
the system. Additional information for each option description can be found in the FSP
150GE11xPro Command Line Interface Reference Guide and Application Notes for
specific features. For more information regarding navigating and using the web-based
GUI, see Web-based Element Management System.
Refer to the following table for factory default configuration settings and correlation from
SNMP parameters to FSP 150CC Web-based Browser GUI operation.
E1000-A-3=3
Link Loss Forwarding
cmEthernetAccPortLinkLossFwdLocalLinkId E1000-A-4=4
Local Link ID
E1000-A-5=5
E1000-A-6=6
Link Loss Forwarding
cmEthernetAccPortLinkLossFwdTriggerTypes None selected (Empty)
Trigger Events
Remote Link IDs cmEthernetAccPortLinkLossFwdRemoteLinkIds None selected (Empty)
Monitor Entity f3PortMirrorAccPortExtMonitorEnabled False(2)
Buffer Size f3PortMirrorAccPortExtBufferSize 128 KB
CPD Filters
Bridge Group 01-80-C2-
cmEthernetAccPortCpdV2Mac00DispType pass-thru(3)
00-00-00
pass-thru(3) (EPL)
Bridge Group BPDU cmEthernetAccPortCpdV2BPDUDispType
useMacSetting(8) (EVPL)
Bridge Group Cus- pass-thru(3) (EPL)
cmEthernetAccPortCpdV2CustomerLLDPDispType
tomerLLDP useMacSetting(8) (EVPL)
Bridge Group 01-80-C2-
cmEthernetAccPortCpdV2Mac01DispType pass-thru(3)
00-00-01
Bridge Group pass-thru(3) (EPL)
cmEthernetAccPortCpdV2PauseDispType
Pause useMacSetting(8) (EVPL)
Bridge Group
cmEthernetAccPortCpdV2Mac02DispType pass-thru(3)
01-80-C2-00-00-02
pass-thru(3) (EPL)
Bridge Group EFM-OAM cmEthernetAccPortCpdV2EfmOamDispType
discard(1) (EVPL)
Bridge Group pass-thru(3) (EPL)
cmEthernetAccPortCpdV2LACPDispType
LACP useMacSetting(8) (EVPL)
Bridge Group pass-thru(3) (EPL)
cmEthernetAccPortCpdV2LACPMarkerDispType
LACP Marker useMacSetting(8) (EVPL)
pass-thru(3) (EPL)
Bridge Group SSM cmEthernetAccPortCpdV2SSMDispType
discard(1) (EVPL)
Bridge Group
cmEthernetAccPortCpdV2Mac03DispType pass-thru(3)
01-80-C2-00-00-03
Power Usage
pethMainPseUsageThreshold 99
Threshold
PSE Group Notification Con-
pethNotificationControlEnable False (2)
(cmFacilityMIB) trol
Nonstandard PD
pethMainPseExtNonStandardPD Disabled (2)
Allowed
Administrative
pethPsePortAdminEnable False (2)
State
PSE Port Power Pairs pethPsePortPowerPairs Signal (1)
(ieee8023powerEthernetMIB) PSE Port Type pethPsePortType (zero-length)
Available Power
pethPsePortExtAvailablePowerLevel class4 (4)
Level
Maximum Bandwidth
Table 55: Maximum Network Port/Access Port Bandwidth
Associated EID Port Type Max. CIR Max. EIR
NETWORK PORT-1-1-1-1,
E1000 (Fiber SFP or Copper): 1000000000 (bps) No Limit.
NETWORK PORT-1-1-1-2
ACCESS PORT-1-1-1-3
ACCESS PORT-1-1-1-4
E1000 (Fiber SFP or Copper): 1000000000 (bps) No Limit.
ACCESS PORT-1-1-1-5
ACCESS PORT-1-1-1-6
All maximum values shown in the above table are indicative of a port without
a management tunnel, which utilizes a configurable amount of bandwidth. At
default configuration, a Low Touch Provisioning (LTP) management tunnel is
provisioned.
System configuration options and rules consist of the following entities, which are
provided in Table 56:
l System Configuration
l Network Element (NE-1) Configuration
l NTE11x Configuration
l PT Flows
l Protection Groups (NE-1)
l LAG
l SHG
l Synchronization
l Profiles
l Communications
l SNMP
l Administration
Enabled
********************************************************-
*****
CLI Security
This is a private system. Unauthorized access or
Prompt
use may lead to prosecution.
********************************************************-
***** Disabled
[Link]
Set the NTP polling interval in seconds. Allowed
Polling Inter- settings are from 16 to 1024 seconds as powers
16
val of 2 (16, 32, 64, 128, 256, 512, 1024). Default is
16.
If both Primary and Backup Server IP Addresses Primary
Active Server are configured, the user may switch between
them using this setting. Backup
If System Time of Day is set to PTP Clock , the PTP Licensable Feature must have been Enabled and a
Telecom Slave has been fully provisioned: (GE114Pro (SH)/GE114Pro (CSH))
Selects the source TOD Clock (TS-1-1 or PTP
Clock if provisioned).
Source TOD (drop down list of available Telecom Slave
Clock entities)
NE-1 (Edit)
This is a text string containing a meaningful
description of the NE. The NE Name must start
with a letter, end with a letter or digit, and have as up to 256 characters
Name
interior characters only letters, digits, and (e.g. FSP 150-GE114Pro (CSH))
hyphens. Maximum length is 256 characters.
Upper and lower case characters are allowed.
GE11xPro (Edit)
A text and/or number string the user enters to
up to 64 characters
Alias uniquely identify this entity. This string can be up
(blank)
to 64 printable ASCII characters long.
Admin- Defines the GE11xPro administrative state. IS is IS
istrative In Service and is the default value. See Entity
State State Descriptions. Management
Flow
Note: To delete an existing Protection Group, enter a right click on the NTE11x entity and select Delete. A Pro-
tection Group with a Network Port in Loopback cannot be deleted. Deleting a protection group will not neces-
sarily be hitless.
User Label associated with the Facility Protection up to 64 characters
User Label
Group. Up to 64 characters are allowed. (blank)
Note 2: To Flush all forwarding table entries, enter a right click on the desired SHG EID in the Details Pane and
select Flush FDB. To view forwarding table entries, enter a right click on the desired SHG EID in the Details
Pane and select View FDB Entries.
Note 3: All members of an SHG must have the same value of Service Type.
Note 4: All members of an SHG must have the same value of C-Tags and S-Tags.
SHG Index
1. A valid Sync Reference source must first be configured and In Service prior to adding a Sync Reference.
2. The GPS input must first be configured and In Service prior to adding to a Sync Reference.
Antenna 0 - 100
Select the proper cable length attached to the
Cable
antenna. 5
Length, m
GPS Only
GNSS Sys-
Select the type of GNSS system used. GLONASS Only
tem
GPS And GLONASS
Installation Full Sky View
Defines the GNSS antenna type.
Type Limited Sky View
QL-SSU-A
Profiles
Priority Mapping Profile (Create/Edit Priority Mapping Profile)
Priority Mapping Profile identifier. The system
Priority Map
provides a default 802.1p mode priority mapping
Profile 1-8
profile as default. The system allows up to 8 pro-
(Create only)
files.
Enter an alias for this profile using 1 - 64 char-
acters. The profile name will show up in the EVPL
Name (blank)
port/flow Priority Mapping Profile drop-down list.
This option is mandatory.
802.1p
Priority Map Defines the Priority Map mode. It identifies the
IP-TOS
Mode lookup criteria for the priority mapping table.
IP-DSCP
Select the COS Mapping mode:
Ethernet
l if COS mapping is for Ethernet frames, only
COS Map Outer/Inner Tag Priority can be specified;
Mode
l if COS mapping is for EoMPLS packets, only
EoMPLS Outer Tag, Outer EXP and Inner EoMPLS
EXP can be specified.
Priority Map Index Selection. The following 0 to 7
ranges of Indexes are: 0...7 if Priority Map Mode (802.1p or IP-TOS)
In Priority
is set to 802.1p or IP-TOS; 0...63 if Priority Map
Mode is set to IP-DSCP. 0 to 63 (IP-DSCP)
X-Tag Priority Control. This parameter controls
the behavior of the Priority portion of the frame. If None
Priority Con- NONE is selected, the incoming priority bits are
trol left unchanged. If SWAP is selected, the incom-
ing priority bits are changed by the value specified Swap
in the X-Tag Priority parameter.
This parameter defines the new priority bits to be
New Priority 0 to 7
used. Valid only if Priority Control is set to Swap.
packets.
Whether to Advertise prefix to link in router mode.
Disabled
This is only applicable when IPv6 Forwarding is
IPv6 RA Pre- enabled on System level. This option and State-
fix Enabled less Address Auto Configuration are mutually
exclusive; they cannot be both Enabled at the Enabled
same time.
[Link]
IPv6 RA Pre- The IPv6 Prefix to be dispatched to link in Router 000
fix mode.
/0
Edit System
Selecting the checkbox allows editing the Gate-
Default Gate- (checkbox unselected)
way IPv6 Address.
way
Gateway Enter a Gateway IPv6 Address if the “Edit Sys-
(grayed out)
IPv6 Address tem Default Gateway” checkbox is selected.
USB DCN - Edit WiFi Dongle Inet Interface (Not apply to GO102Pro(S) or GO102Pro(SP))
Configure the IP Address for the WiFi Dongle
IP Address [Link]
(WiFi interface).
Network Configure the subnetwork mask for the WiFi
[Link]
Mask Dongle.
IP Address Configure the start IP address in the same subnet
(blank)
Pool From for the clients.
IP Address Configure the end IP address in the same subnet
(blank)
Pool To for the clients.
AMP Configuration
Note 2: EFM-OAM must be enabled on the AMP Client management tunnel interface in order to send and
receive AMP protocol messages.
AMP Id Automatic Management Provisioning (AMP)
AMP-1 through AMP-255
(Create Only) entity identifier.
Note 2: EMF-OAM must be enabled on the AMP Server management tunnel interface in order to send and
receive AMP protocol messages.
AMP Id Automatic Management Provisioning (AMP)
AMP-1 through AMP-255
(Create only) entity identifier.
EID of the port this instance is associated with.
Network Ports in LAG or 1+1 protection group are
Port EID (dropdown list of provisioned Network ports
treated as a single logical port. Access Ports in
(Create only) and Access Ports)
LAG or protection group are denied for this con-
figuration.
Enable or disable Server Automatic Management Disabled
Control
Provisioning. Enabled
Remote Sys- Remote system name, a string of 1 - 255 char-
(empty)
tem Name acters.
Remote Sys-
tem IP Remote system’s IPv4 Address. [Link]
Address
Remote Sys-
Remote system IP Mask. [Link]
tem IP Mask
Remote Sys-
tem Def Gate- Remote system default gateway. [Link]
way
Remote Tun-
Remote Tunnel Index. 1 - 255
nel Index
Remote Tun- Alphanumeric tunnel interface name of 1 - 15 char-
(empty)
nel Name acters.
Remote Tun- Identify whether the tunnel is VLAN based or VLAN Based
nel Type MAC based. MAC Based
Remote Tun-
nel IP Remote tunnel IP Address. 0.0,0.0
Address
Remote Tun-
Remote tunnel IP Mask. [Link]
nel IP Mask
Remote Tun-
Remote tunnel VLAN ID. 1 - 4095
nel VLAN ID
[Link] USM User “crypto” available in GE114Pro (C)/GE114Pro (CSH) cannot be deleted.
3. After every provisioning operations, the crypto user will be required to enter the crypto password.
High:
Low:
Regenerate
(unselected)
SSH Key
When an SSH Key is generated, all SSH users
are logged off.
Country Edit SSL Certificate Data - Country US
State Edit SSL Certificate Data - State Texas
Locality Edit SSL Certificate Data - Locality Richardson
Organization Edit SSL Certificate Data - Organization ADVA Optical Networking
Organization
Edit SSL Certificate Data - Organization Unit Ethernet Access
Unit
Name Edit SSL Certificate Data - Name ADVA
Email Edit SSL Certificate Data - Email support@[Link]
Valid Until Edit SSL Certificate Data - Valid Until (varies)
The flow is point-to-point and 2 Port attributes define the ingress and egress points of the
Flow. The Membership, Bandwidth Profile and Traffic Management provisioning
attributes are in effect for service frame forwarding from Port1-to-Port2 and Port2-to-Port1
(i.e., Provisioning is applied bidirectionally between ports).
PT Flows
Flow (Create/Edit Flow)
Passthrough Flow PT FLOW-1-1
EID The EID of this flow instance. through
(Create only) PT FLOW-1-128
Defines a circuit identifier for the Flow. Up to 256 characters up to 256 characters
Circuit Name
are allowed. (blank)
IS
Enables or disables the Pass-through Flow. IS is In Service
Administrative State Management
and is the default value. See Entity State Descriptions.
Disabled
Defines the EVC type.
Regular EVC
If Default EVC: N2N Flow Membership based on a frame
EVC Type received on a Network Port that does not match any other
flow membership (only 1 default flow is allowed per System).
If Regular EVC: N2N Flow Membership based on VLAN Default EVC
Member list.
Control of N2N policing function.
If Enabled: the Bandwidth Profile values for this flow are Enabled
N2N Auto Band- determined dynamically and are read-only.
width If Disabled: the Bandwidth Profile of the flow is manually con-
trolled. Disabled
Not applicable when Multi COS = Enabled.
Percentage of available CIR on the Network ports assigned to
this flow. The flow guaranteed bandwidth is set to available
bandwidth multiplied by this value.
N2N Auto CIR Band-
0-100
width Percent The sum of N2N auto CIR bandwidth Percentage value for all
flows with N2N Auto Bandwidth = Enabled must be <= 100%.
If the Priority value is not specified, all the priority values for
that VLAN ID belongs to the FID. A maximum of 64 members
can be defined for a given FID. If no value is supplied, this
FID becomes the default FID for the port, i.e., all the VLAN
IDs that don’t belong to any other FID on the port belongs to
this FID.
VLAN Members
(Regular EVC only) Regarding the use of the “wildcard” value * - The normal des-
ignation of a VLAN Member is X-Y, where X is the VLAN ID
and Y is the Priority. Supported wildcard forms are: X-*, where
* represents any priority value, i.e., flow is priority agnostic
and *-Y where * represents any VLAN ID, i.e., flow is VLAN
agnostic. The rules are: *-Y members can coexist with X-Y
members (same priority) within the same flow as well as
across all flows within the same access port, with the X-Y
member match taking precedence; Default flows (*-*) can
coexist with *-Y member flows with the *-Y member match Priority portion of
taking precedence; *-Y members cannot coexist with X-* VLAN ID-Priority:
members.
0 to 7, or *
l For LAG descriptions and attributes, see Link Aggregation Group in FSP 150-
GE11xPro System Description document.
l For LAG configuration procedure, see Provision Ports in a LAG Group. Table 60 shows
the LAG Configuration Rules applying to GE11xPro. The attributes are arranged in the
same order as on the web-based GUI. Default settings are identified in bold.
Note 4: When adding the first port to LAG, the Admin State must be INSERVICE, MAINTENANCE or
MANAGEMENT. The second port must have an Admin State of Unassigned.
Note 5: Deleting a LAG is denied if more than one port is in the Member Port List.
Note 6: The first Member Port added can have active loopback, but active loop on the second Member port is
not allowed.
Note 7: Deleting a LAG is denied if there is active loopback on the LAG or any member port.
Note 8: If the LAG is to be created with Network Ports. Network One must be added, and other Network ports
must be in Unassigned states.
Note 9: At the time a LAG is deleted, or the last member port is removed, the following entities existing on the
LAG are migrated to the member port which is deleted the last.
o Flow
o CFM entities (MIP, MEP, Server MEP)
o Management tunnel
o ESA entities
Note 11: Regarding the Access LAG, the Service Mode of A LAG can be EVP of EVPL, this is dictated by the
Service Mode of the first Member Port added to the LAG. The Service Mode of the second port is automatically
converted to align to the first Port. Once the LAG is created, the Service Mode is not editable.
Note 12: If creating a LAG group on Access Ports: The Network Port Bridge Group Protocols “LACP” and
“LACP Marker” must be set to “Discard”. All other CPD Filter setting may be set as desired.
Create/Edit LAG Configuration
Unique LAG identifier,
LAG ID
o GE112Prox: LAG-1, LAG-2 LAG-1
(Create LAG only)
o GE114xProx: LAG-1. LAG-2, LAG-3
A text and/or number string the user enters to identify a LAG up to 255 characters
Alias entity. This string can be up to 255 printable ASCII characters (blank)
long. Unique strings across the NE are recommended.
LAG mode of Active-Standby creates 1:1 link protection.
Load Sharing
An Active-Stdby Protection mode means only 2 member ports
Mode are allowed in this LAG, one member is in Working role and the
other one is in Protect role.
Active-Standby
In a LoadSharing LAG , all member ports share the traffic load.
Defines the LAG facility administrative state. The admin-
istrative state controls the generation of alarms and event IS
Administrative State reports. When an entity is in the In-Service state, it is fully oper-
ational. For more information on Administrative States, see Management
Entity State Descriptions.
Option is used to enable LAG protocols. Disabled
LAG Protocols
See Footnote 1. Enabled
Option is used to enable LACP Control for the LAG entity. Disabled
LACP Control
See Footnote 1. Enabled
The algorithm used to distribute traffic load among the LAG Filed Hash
Frame Dist Algorithm
member ports. Service Assignment
The filed (factor) to be used in the Hash Algorithm. One or
Hashing Combination some of the following fileds can be selected:
Outer Vid
Field Inner Vid Src Mac Dest Mac Src Ip Dest Ip Ip Protocol Src
Port Dest Port
Option used to enable the use of CFM CCM to detect defects
Disabled
on the LAG entity. If CCM Defect Detection is desired, a
CCM Defect Detection
Down MEP with proper provisioning must preexist on the LAG
Enabled
Port.
Defines the LACP Actor System Priority. Minimum is 0; Max- 0 - 65535
System Priority
imum is 65535. 32768
Rx DEI Outer Tag • Stag – DEI is used for color identification only if the outer tag
is S-Tag
• Ctag Or Stag – DEI is used for color identification if outer tag Stag
is C-Tag or S-Tag
Transmit DEI Action. Set to Zero
Tx DEI Action • Set to Zero - implies the DEI is always set to 0 Mark Color
• Mark Color - implies the declared color is set in the DEI
• No Change - implies the outer tag DEI is not modified No Change
Transmit DEI Outer Tag Type. Applies only if the Tx DEI
Action is “Set to Zero” and “Mark Color”. Ctag Or Stag
Tx DEI Outer Tag
• Stag – DEI is modified only if the outer tag is S-Tag Stag
• Ctag Or Stag – DEI is modified if outer tag is C-Tag or S-Tag
This option is only available in Network Port LAG. See Specify
EoMPLS Source IP
an IP Address for Network Port (Physical or Logical) for more [Link]
Address IP Address
information.
Traffic type allowed on the LAG. This parameter is only avail- AFP All
able in Access Port LAG - Port configurations. See Acceptable
AFP AFP tagged
Frame Policy in FSP 150-GE11xPro System Description
document. AFP Untagged
1 TheLACP-Control parameter allows the selection process to be independent of the LACP protocol for
applications that require a conversion from unprotected port to an active-standby LAG. For configurations
where LACP-Control is disabled, the LACP protocol information may not align with the actual selection state
of the active-standby LAG. Collecting & distributing information is derived from the LACP protocol.
Active/Standby status is derived from the port selection process.
0
Active-standby LAG is expected to be a bidirectional protection mechanism and relies on the LACP protocol
for coordinating the active link determination between 2 partner systems. For configurations where LACP-
Control is disabled, the 2 partner systems could experience a mismatch of active and standby ports causing
traffic outage.
The GE11xPro supports all LACP & LAMP interaction in software. A warm reboot of the system stops all LACP
processing (transmit and receive) and causes a LAG with ‘LAG Protocols enabled’ to initiate a link down,
affecting all service frames on the LAG logical port. For warm reboot during maintenance activity on back-to-
back ADVA Optical Networking systems, the LACP Control setting may be used to disable the link selection
based on LACP (i.e., LACP Control disabled) for the duration of the warm reboot.
Network Port 2 (if not associated with another entity) may be switched to operate as an
Access Port by entering a right click on Network Port 2, selecting “Switch to ACC” and
selecting OK. The associated entities that must not exist when switching from a Network
Port to an Access Port are:
l LAG group
l 1+1 Network protection
l MEPs
l MACOMPs
l ERP instance
l SHG group
Conversely, Access Port 2 (if not associated with another entity) may be switched back
to become Network Port 2 by entering a right click on Access Port 2, selecting “Switch to
NET” and selecting OK. The associated entities that must not exist when switching from
an Access Port to a Network Port are:
l LAG group
l Management tunnel
l MEPs
l MACOMPs
l SHG group
l ESA probes or reflectors
l Running ECPA test
l PTP related configurations - GE114Pro (SH)/GE114Pro (CSH)
After the port type changes, the new port is in the unassigned state and all the attributes
use the system default values.
Edit Configuration
A text and/or number string the user enters to uniquely identify this up to 255
Alias Network Port. This string can be up to 64 printable ASCII characters characters
long. (blank)
Defines the Network Port facility administrative state. The admin-
istrative state controls the generation of alarms and event reports. IS
When an entity is in the In Service state, it is fully operational. The
Administrative State must be set to Maintenance prior to initiating a Management
Administrative
loopback or an Etherjack Diagnostic. When a protection group is con-
State
figured, and Network Port 2 is placed in service. Administrative Maintenance
State and Remote Link ID options are the only editable options on
Network Port 2. For more information on Administrative States, see
Unassigned
Entity State Descriptions.
Fiber
Media Type Defines the port media type.
Copper
Defines the Maximum Transmission Unit size in bytes. Minimum
MTU 1518-9638
MTU is 1518; Maximum is 9638.
Auto 1000
Configured Speed Sets the configured speed for the network interface. The user can Full
(Fiber) select auto negotiation or manual configuration. 1000 Full
100 Full
Auto
Auto 1000 Full
Auto 1000 Full
Master
Configured Speed Sets the configured speed for the network interface. The user can Auto 1000 Full
(Copper) select auto negotiation or manual configuration. Slave
Auto 100 Full
Auto 10 Full
100 Full
10 Full
Auto
If Media Type is Copper, MDIX can be edited. If Media Type is Fiber,
MDIX Crossed
MDIX is not applicable.
Uncrossed
Rx DEI Outer Tag l Stag – DEI is used for color identification only if the outer tag is
S-Tag
l Ctag Or Stag – DEI is used for color identification if outer tag is Stag
C-Tag or S-Tag
Transmit DEI Action. Set to Zero
Tx DEI Action l Set to Zero - implies the DEI is always set to 0 Mark Color
l Mark Color - implies the declared color is set in the DEI
l No Change - implies the outer tag DEI is not modified No Change
See Default Priority Mapping Profile Tables for default Priority Map
settings.
Whether to enable configuring Bandwidth for Port Shaper
independently. Enabled
Independent Port When Independent Shaper Bandwidth is disabled, the port Shaper
Shaper BW CIR is a sum of Corresponding Policers.
N/A for
E1000-N-2
Edit PCP Configuration (Network Port 1 Only)
Standardized modes for editing PCP encoding are 7P1D, 6P2D and
5P3D which allow the user to edit 1, 2 or 3 PCP pairs respectively. None
Also provided is a ‘Custom’ mode that allows the user to edit the
PCP Encoding and Decoding Tables directly and ignore the normal
7P1D
rules regarding priority reuse and hierarchy. Any use of PCP
Encoding may affect existing traffic. The Custom mode has the
PCP DE Encoding potential for causing unexpected and unintended disruption of normal
Mode traffic. 6P2D
The following Access Port settings are shown in order, as seen when using the web-
based GUI in Configuration mode.
To observe the current allocated and available traffic resources, expand the NE-1 entity
under the System entity, select the NTE11x entity and then select the Resources tab.
Network Port 2 (if not associated with another entity) may be switched to operate as an
Access Port by entering a right click on Network Port 2, selecting “Switch to ACC” and
selecting OK. The associated entities that must not exist when switching from a Network
Port to an Access Port are:
l LAG group
l 1+1 Network protection
l MEPs
l MACOMPs
l ERP instance
l SHG group
Conversely, Access Port 2 (if not associated with another entity) may be switched back
to become Network Port 2 by entering a right click on Access Port 2, selecting “Switch to
NET” and selecting OK. The associated entities that must not exist when switching from
an Access Port to a Network Port are:
l LAG group
l Management tunnel
l MEPs
l MACOMPs
l SHG group
l ESA probes or reflectors
l Running ECPA test
l PTP related configurations - GE114Pro (SH)/GE114Pro (CSH)
After the port type changes, the new port is in the unassigned state and all the attributes
use the system default values.
Changing the Service Type on a port will drop all traffic on the
port, including Management Tunnel connectivity and
Maintenance End Points.
OpenFlow EPL
o Not allowed not add this port to a LAG
o Not allowed to set the port Configured Speed to “Auto”
o Port-2 (flexible port) is not allowed to switched to
Network Port
o Not allowed to change the setting if at least one OF Enabled
Flow is associated with this port as part of Flow match
or as Output action
o It’s allowed to change the setting even if an OF
Capable Switch exists.
Auto
Auto 1000 Full
Auto 1000 Full Master
Configured Speed Sets the configured speed for the access interface. The user Auto 1000 Full Slave
(Copper) can select auto negotiation or manual configuration. Auto 100 Full
Auto 10 Full
100 Full
10 Full
Auto 1000 Full
Configured Speed Sets the configured speed for the access interface. The user
1000 Full
(Fiber) can select auto negotiation or manual configuration.
100 Full
Auto Diagnostic (cop- Enables or disables the automatic Cable Diagnostic tests Enabled
per) when the cable is removed from the port. Disabled
Receive DEI Action.
Use
Rx DEI Action l Ignore - does not use DEI for color identification
l Use - uses DEI for color identification Ignore
Receive DEI Outer Tag Type. Applies only if the Receive DEI
Action is USE Ctag Or Stag
Rx DEI Outer Tag l Stag – DEI is used for color identification only if the outer
tag is S-Tag
l Ctag Or Stag – DEI is used for color identification if outer Stag
tag is C-Tag or S-Tag
Tx DEI Action l Set to Zero - implies the DEI is always set to 0 Mark Color
l Mark Color - implies the declared color is set in the DEI
l No Change - implies the outer tag DEI is not modified No Change
Transmit DEI Outer Tag Type. Applies only if the Tx DEI
Action is “Set to Zero” and “Mark Color”. Ctag Or Stag
Tx DEI Outer Tag l Stag – DEI is modified only if the outer tag is S-Tag
l Ctag Or Stag – DEI is modified if outer tag is C-Tag or S- Stag
Tag
Defines the service type for this Access port - either Ethernet
Private Line (EPL) or Ethernet Virtual Private Line (EVPL). The EPL
Access Port Administrative State must first be set to
Service Type
Unassigned state prior to changing the Service Type. When
changing from Access Port Service Type EVPL to EPL, a new EVPL
Flow is automatically created in the Unassigned state.
AFP Tagged
Defines the Acceptable Frame Policy. See Acceptable Frame
AFP AFP Untagged
Policy in FSP 150-GE11xPro System Description document.
AFP All
Defines the Stacked Ethertype to be used to inter-operate with
Q in Q Ethertype Queue-in-Queue frames with other vendors. Only editable if Q 0 (hex)
in Q EtherType Override is enabled.
Q in Q EtherType Enabled
Enables or disables editing the Q in Q EtherType.
Override Disabled
Enabled
802.3 Pause RX Defines the receive flow control for the facility.
Disabled
Enabled
802.3 Pause TX Defines the transmit flow control for the facility.
Disabled
Enables or Disables Access Port Shaping. Port shaping limits
Enabled
the output traffic rate to a value below the pro-
Port Shaping
visioned/negotiated physical port speed. Shaping is useful to
Disabled
limit the burst size of the traffic being offered to the client.
Defines the maximum bandwidth on the Access Port (in bps).
Port Shaped Speed 0 to 1,000,000,000 (bps)
Applicable when Port Shaping is Enabled.
Controls whether the selected (if any) LLF Trigger Events will Disabled
Link Loss Forwarding
work. If no LLF Trigger Events are selected, it’s equivalent to
Port LLF Status Enabled
setting LLF to Disabled.
Sets the Link Loss Enable Delay, in seconds, from the time
Link Loss Forwarding Link Loss is detected before Link Loss Forwarding takes
0 -3600 (sec.)
Delay effect. If the loss clears during delay time, it is not propagated.
Only effective if LLF Status is Enabled.
Sets Link Loss Forwarding Transmit Signal Type. A facility No Action
Link Loss Forwarding port takes TX Action only after the other end of its associated
EFM Signal
TX Action flow get LLF events triggered. This option is not controlled by
Port LLF Status. Link Down
0
(allocated resource from
port shaper plus shaper
SOAM-EIR
Define the shaper EIR size for the SOAM service on this flow. CIR cannot exceed
1Gbps)
0
Shaper WRED In-Pro-
The minimum drop threshold for in-profile traffic. 0 - 100
file MIN Threshold %
Note 2: Reset PCP Defaults option is used to reset the PCP Encoding and Decoding Tables back to default val-
ues.
Standardized modes for editing PCP encoding are 7P1D,
6P2D and 5P3D which allow the user to edit 1, 2 or 3 PCP None
pairs respectively.
(Edit Configuration)
Connection
Defines a circuit identifier for the Flow. Up to 256 characters up to 256 characters
Circuit Name
are allowed. (blank)
Select the Network Interface for this flow. Candidates include:
NETWORK PORT-1-
Network port, Network LAG, Network PPG (including 1+1,
1-1-1
Dual-Active, RP entity with network ring port,), and SHG
Network Interface
entity with network member port. Note that PPG, SHG and
NETWORK PORT-1-1-
LAG can not coexist; if any one type exists, the other two can-
1-2
not exist.
Select the Access Interface for this flow. Candidates include:
Access Interface the current Access port, LAG (if any) with current port as mem- Current Access Port
ber, and SHG (if any) entity with current port as member.
Enable/Disable the selected Policing Control. When the poli- Enabled
Policing cing is Disabled, the policer in the corresponding direction will
not work. Disabled
A2N_N2A
Policing Control Specify the policing direction of the flow. A2N
N2A
If Flow Based is selected, system will assign 8 independent
queues for this flow for A2N shaping; If Port Based is selec- Flow Based
A2N Shaping
ted, system will schedule this flow to use the queues of the
specified Network Interface according to the COS specified Port Based
for this flow.
EoMPLS Encap- Select the checkbox to associate the access port flow (checkbox
sulation (EPL/EVPL) with an EoMPLS PW. unselected)
Select a desired EoMPLS PW to associate with from the drop
EoMPLS PW (none by default)
down list.
Specify the COS (Class of Service) value for the Traffic Flow.
It identifies the internal COS applied to the all A2N frames
COS 0 to 7
received on the parent Access Port that match the Flow’s A2N
membership.
Independent N2A Rate Manages N2A rate limiting, independent of A2N rate limiting. Disabled
Limiting When not enabled, N2A specification is the same as A2N. Enabled
Note that each P2P flow will decrease the Max Forwarding 0 - 2048
Table Entries per system (2048 for GE112Pro series, 4096 for (GE112Pro series)
Max Network For- GE114Pro series) by 2, on condition of the following pre- or
warding Table Entries requisites:
0 - 4096
1) Network Interface Learning Control set to None
(GE114Pro series)
2) Access Interface Learning Control set to None
Aging Timer The aging time of the MAC address learned. 10 - 1,000,000
300
Tag Management
Defines whether the C (Customer) Tag VLAN ID / VLAN Pri-
ority should be PUSHed or no action taken.
Push
If more than one Access port is to be used in the system, Push
C-Tag Control must be selected. If C-Tag Control is set to None, only one
LAN port may be used in the system.
None
If C-Tag Control is set to None, then C-Tag VLAN ID and C-
Tag VLAN Priority cannot be entered.
1 to 4095
Defines the C-Tag VLAN ID that will be PUSHed. This option E1000-A-2 (if
is only available if C-Tag Control is set to Push. provisioned)
default is 2
All C-Tag and S-Tag VLAN ID-Priority values must not conflict
on the Network port. (For example: A service with C-Tag E1000-A-3
PUSH 100-0, S-Tag PUSH 100-0 will conflict with another ser- default is 3
vice with the same C-Tag and S-Tag. A service with C-Tag E1000-A-4
PUSH 100-0, S-Tag None will conflict with another service default is 4
C-Tag
with C-Tag None, S-Tag PUSH 100-0. An EPL service with C- E1000-A-5
Tag PUSH 100-0, S-Tag NONE will conflict with a Flow with default is 5
VLAN Member 100-0, C-Tag NONE and S-Tag NONE.) E1000-A-6
default is 6
Defines the C-Tag VLAN Priority that will be PUSHed. This
option is only allowed if C-Tag Control is set to Push.
0 to 7
All C-Tag and S-Tag VLAN ID-Priority values must not conflict
on the Network port (see C-Tag VLAN ID).
Defines whether the S (Service) Tag VLAN ID / VLAN Priority
should be PUSHed or no action taken. Push
S-Tag Control
If S-Tag Control is set to None, S-Tag VLAN ID and C-Tag None
VLAN Priority cannot be entered.
0
(allocated resource from
port shaper plus shaper
SOAM-EIR
Define the shaper EIR size for the SOAM service on this flow. CIR cannot exceed
1Gbps)
0
Shaper WRED In-Pro-
The minimum drop threshold for in-profile traffic. 0 - 100
file MIN Threshold %
Shaper WRED In-Pro-
The maximum drop threshold for in-profile traffic. 0 - 100
file MAX Threshold %
Shaper WRED In-Pro-
file Maximum Drop The maximum drop probability for in-profile traffic. 0 - 100
Probability
Shaper WRED Out-of 0 - 100
Profile MIN Threshold The minimum drop threshold for out-of profile traffic.
% 75
Shaper WRED Out-of 0 - 100
Profile MAX Threshold The maximum drop threshold for out-of profile traffic.
% 75
Changing Service Type on a port will drop all traffic on the port,
including Management Tunnel connectivity and Maintenance
End Points.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Auto 1000 Full
Configured Speed Sets the configured speed for the access interface. The user
1000 Full
(Fiber) can select auto negotiation or manual configuration.
100 Full
Enable/Disable the support of Open Flow on this port.
Rx DEI Outer Tag l Stag – DEI is used for color identification only if the outer
tag is S-Tag
l Ctag Or Stag – DEI is used for color identification if outer Stag
tag is C-Tag or S-Tag
Transmit DEI Action. Set to Zero
Tx DEI Action l Set to Zero - implies the DEI is always set to 0 Mark Color
l Mark Color - implies the declared color is set in the DEI
l No Change - implies the outer tag DEI is not modified No Change
Transmit DEI Outer Tag Type. Applies only if the Tx DEI
Action is “Set to Zero” and “Mark Color”. Ctag Or Stag
Tx DEI Outer Tag l Stag – DEI is modified only if the outer tag is S-Tag
l Ctag Or Stag – DEI is modified if outer tag is C-Tag or S- Stag
Tag
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the service type for this Access port - either Ethernet
EPL
Private Line (EPL) or Ethernet Virtual Private Line (EVPL). The
Service Type
Administrative State must first be set to Unassigned state prior
EVPL
to changing the Service Type.
AFP Tagged
Defines the Acceptable Frame Policy. See Acceptable Frame
AFP AFP Untagged
Policy in FSP 150-GE11xPro System Description document.
AFP All
Defines the Stacked Ethertype to be used to inter-operate with
Queue-in-Queue frames with other vendors. Only editable if Q
Q in Q Ethertype in Q EtherType Override is enabled. 0 (hex)
Q in Q EtherType Enabled
Enables or disables editing the Q in Q EtherType.
Override Disabled
1 to 4095-[0 to 7]
E1000-A-2 (if
provisioned)
VID default is 2
Defines the Port VLAN ID. The format is VID-PRIO. The valid
E1000-A-3
values for VID are 1 to 4095 and valid values for PRIO are 0 to
Port VID default is 3
7. If only the VID portion is entered, PRIO will default to 0. If
VLAN ID E1000-A-4
the VID portion is not entered, PRIO also cannot be specified.
VID default is 4
This option is only valid when Service Type is set to EVPL.
E1000-A-5
VID default is 5
E1000-A-6
VID default is 6
Selects a Priority Mapping Profile Identifier for Access Port
A2N ingress P-bit mapping while port Service Type is set to None
EVPL. If a specific profile is selected, the port-based priority
mapping will be based on the selected profile setting. The sys- Drop-down list of
Priority Mapping Profile tem supports up to 8/64 Ingress Priority Mapping Profile entit- available Priority
ies. Mapping Profile entity
See Default Priority Mapping Profile Tables for default Priority names
Map settings. This option is only valid when Service Type is
set to EVPL.
Enable/Disable swapping VID number in A2N direction using
the VID specified as the Swap Priority VID only when the Enabled
A2N Swap Priority VID incoming Outer VID equals 0. Used to change the A2N VID
without altering the priority of a tagged frame. This option is Disabled
only valid when Service Type is set to EVPL.
Enable/Disable swapping VID number in N2A direction to 0
only when the incoming Outer VID equals the VID specified as Enabled
N2A Swap Priority VID the Swap Priority VID. Used to change the N2A VID without
altering the priority of a tagged frame. This option is only valid Disabled
when Service Type is set to EVPL.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
VID to be used for A2N and/or N2A Swap Priority VID when
Swap Priority VID either or both are enabled. This option is only valid when 1 - 4095
Service Type is set to EVPL.
Enabled
802.3 Pause RX Defines the receive flow control for the facility.
Disabled
Enabled
802.3 Pause TX Defines the transmit flow control for the facility.
Disabled
Enables or Disables Access Port Shaping. Port shaping limits
Enabled
the output traffic rate to a value below the pro-
Port Shaping
visioned/negotiated physical port speed. Shaping is useful to
Disabled
limit the burst size of the traffic being offered to the client.
Defines the maximum bandwidth on the Access Port (in bps) 0 to 1,000,000,000
Port Shaped Speed
toward the client. Applicable when Port Shaping is Enabled. (bps)
Whether to enable configuring Bandwidth for Port Shaper
independently.
Enabled
When Independent Shaper Bandwidth is disabled, the port
Independent Port
Shaper CIR is a sum of Corresponding Policers.
Shaper BW
When Independent Shaper Bandwidth is enabled, the user can
Disabled
manually enter CIR and EIR setting for the port Shapers
setting.
Enables or disables the Network to Access VLAN trunking on
Enabled
the Ethernet Access port. Disabling VLAN trunking removes all
N2A VLAN Trunking
VLAN tags before transmitting traffic out of the access port.
Disabled
This option is only valid when Service Type is set to EVPL.
Sets Push port VLAN ID in the Access to Network direction.
When Enabled, the Port VLAN ID is PUSHed onto the frame. Enabled
A2N Push Port VID When Disabled, no tags are PUSHEed onto the frame (i.e., it
stays untagged). This option is only valid when Service Type is Disabled
set to EVPL.
Sets Pop port VLAN ID on N2A frames. If Ingress PUSH Port
Enabled
VLAN ID is Enabled, it may be desired that the PVID may be
N2A Pop Port VID
POPed. This option is only valid when Service Type is set to
Disabled
EVPL.
Controls whether the selected (if any) LLF Trigger Events will Disabled
Link Loss Forwarding
work. If no LLF Trigger Events are selected, it’s equivalent to
Port LLF Status Enabled
setting LLF to Disabled.
Sets the Link Loss Enable Delay, in seconds, from the time
Link Loss Forwarding Link Loss is detected before Link Loss Forwarding takes effect.
0-3600 (sec.)
Delay If the loss clears during delay time, it is not propagated. Only
effective if LLF Status is Enabled.
Sets Link Loss Forwarding Transmit Signal Type. A facility port No Action
Link Loss Forwarding takes TX Action only after the other end of its associated flow
EFM Signal
TX Action get LLF events triggered. This option is not controlled by Port
LLF Status. Link Down
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Check boxes to select trigger events to generate the Link Loss EFM
Link Loss Forwarding
Forwarding signal. Either EFM or Link Down may be selected,
Trigger Events Link Down
or both. In default, none are selected.
Defines the Local Link ID for the Access port to indicate which 1 to 6
Link Loss Forwarding port is faulted. Applicable entries are 1 through 6. Default is the
Local Link ID current Access Port ID. Local Link ID is only used for EFM Sig- (current Access Port
nal TX Action. ID)
Allows selection of the Remote Link ID(s) to be used for match-
Link Loss Forwarding ing against the Link ID in the EFM RLD (Remote Link Down) 1 to 6
Remote Link IDs message. The same Remote Link ID number may be set for N/A
multiple Network ports, if desired. Default is no ports selected.
If selected, the LLDP frame propagation scope will include a
Nearest Bridge single LAN which limits the propagation of LLDP frames across Selected
([Link]) a link, and the MAC Address [Link] will be used as /Unselected
the destination address in LLDP frames.
If selected, the LLDP frame propagation scope will include the Selected
Nearest non-TPMR transmission of LLDP frames through Two-Port MAC Relays
Bridge (TPMR) between two C-VLAN/S-VLAN components or 802.1d /Unselected
([Link]) bridges. and the MAC Address [Link] will be used
as the destination address in LLDP frames,
If selected, the LLDP frame propagation scope will include the Selected
Nearest Customer transmission of LLDP frames through TPMRs and S-VLAN
Edge components between C-VLAN components or 802.1d bridges, /Unselected
([Link]) and the MAC Address [Link] will be used as the
destination address in LLDP frames.
If port is to be used for mirroring another port, the port must be in
unassigned state, not in a LAG or ERP group, have no MEPs
Port Mirror Monitor Port Disabled / Enabled
present and no ECPA test stream assigned. Actual mirror
assignment is done in Maintenance View.
10 -15360KB
Port Mirror Buffer Size Specify the buffer size for the Port Mirror.
128
Edit CPD Filters - see CPD Filters Options and Rules.
Edit EFM-OAM
State Disabled
Manages the EFM OAM on the Ethernet Network Port.
OAM Control Enabled
Local Configuration Configures the OAM sub-layer entity in either Active or Passive OAM Active
Mode mode. OAM Passive
Edit Sync-E - GE114Pro (SH)/GE114Pro (CSH)
Determines whether the Ethernet port operates in SyncE Disabled
Sync-E Mode Mode. Disabled means the port operates in non-Sync mode.
Enabled means the port operates in sync mode. Enabled
Determines whether the Ethernet port operates in Quality Level
Disabled
(QL) Mode. The QL Mode for an Ethernet port cannot be set to
QL Mode
Enabled unless the SyncE Mode attribute is also set to
Enabled
Enabled.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Specifies the assumed Quality Level (QL) on the
QL-NONE
Ethernet Port. Assumed QL is a QL value that is forced at a
receiving interface.
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A. QL- QL-EEC1
SSU-B, QL-EEC1. Default is QL-EEC1.
Valid entry for SONET Network Clock: QL-STU. QL-STU
Set the Expected QL for the Ethernet port. When the Received QL-NONE
QL value is lower than the Expected QL value, the interface is QL-PRC
declared as failed and a Sync QL Mismatch alarm is declared QL-SSU-A
against the [Link] Expected QL only has meaning when QL-SSU-B
the QL Mode attribute is set to Enabled. QL-EEC1
QL-NONE
QL-PRS
Expected QL
QL-STU
Valid entry for SONET Network Clock: QL-NONE, QL-PRS, QL-ST2
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, QL-TNC
QL-PROV. QL-ST3E
QL-EEC2
QL-SMC
QL-PROV
Port N2A Shapers (Edit N2A Shapers)
10 to 15,360 (KB)
Buffer Size Represents the Buffer Size of the Shaper. Entered in kilobytes.
0 (KB)
(allocated resource
1Gbps)
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
(allocated resource
1Gbps)
0
Edit PCP Configuration
Note 1: Update Table option is used to update the PCP Encoding and Decoding Tables after editing PCP Pairs
1, 2 and/or 3.
Note 2: Reset PCP Defaults option is used to reset the PCP Encoding and Decoding Tables back to default val-
ues.
Standardized modes for editing PCP encoding are 7P1D, 6P2D
and 5P3D which allow the user to edit 1, 2 or 3 PCP pairs None
respectively.
Note: To delete a Flow, enter a right click on the desired flow and select Delete Flow. Then select OK.
Identification
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
The flow identifier which is automatically indexed by default.
User may select the desired ID from the drop-down list. For FID-1 to FID-32 for
GE112Pro (m)/GE112Pro/GE112Pro (H), 32 flows are sup- GE112Prox
Flow ID
ported per system; For GE114Pro/GE114Pro (C)/GE114Pro FID-1 to FID-64 for
(SH)/GE114Pro (CSH)/GE114Pro (HE), 64 flows are sup- GE114Prox
ported per system.
Connection
Assigns a circuit name to the flow. Up to 256 characters are up to 256 characters
Circuit Name
allowed. (blank)
Defines the flow type. If Default EVC is selected, no VLAN
Member value may be supplied, and this FID becomes the
Default FID for the port, i.e., all the VLAN IDs that don’t belong Default EVC
to any other FID on the port belongs to this FID. If Regular EVC
is selected, then individual VLAN Members may be added to
EVC Type the flow.
(Create Flow only)
Flow Type cannot be edited once a flow is created. To change Regular EVC
the Flow Type, the FID must be deleted and then re-created
with the new Flow Type.
Select the Network Interface for this flow. Candidates include:
Network port, Network LAG, Network PPG (including 1+1,
Dual-Active, RP entity with network ring port,), and SHG entity Select from Drop-
Network Interface with network member port, VXLAN Segment. Down list
Note that PPG, SHG and LAG can not coexist; if any one type
exists, the other two cannot exist.
ACCESS PORT-1-1-
Select the Access Interface for this flow. Candidates include: 1-N
Access Interface the current Access port, LAG (if any) with current port as mem- (N = 2 to 6
ber, and SHG (if any) entity with current port as member. respectively for
E1000-A-N)
Enable/Disable the selected Policing Control. When the poli- Enabled
Policing cing is Disabled, the policer in the corresponding direction will
not work. Disabled
A2N_N2A
Policing Control Specify the policing direction of the flow. A2N
N2A
Specifies the COS (Class of Service) value for the Traffic
Flow. This value is used at flow creation time to identify the
COS COS level of the A2N and N2A shaper. If MULTI COS is 0 to 7
Enabled, this option is not applicable when multiple policer-
s/shapers exist on the flow.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Enables or Disables Multi Class Of Service (COS). If set to the
Disabled, one N2A Policer and one A2N Policer are pro-
visionable. If set to the Enabled state, up to 8 N2A Policers and Enabled
8 A2N Policers may be provisioned. Multi COS can only be set
Multi COS to the Enabled state if Priority Map Mode is set to anything
other than None for the facility.
(Create Flow only)
This option is only available during Flow creation and cannot be Disabled
edited. If it is desired to edit an existing Flow, the Flow must be
deleted and then re-created with the Multi COS change.
Outer VLAN Tag
Inner VLAN Tag
Specifies what the flow uses for determining the COS (Class of N2A Priority Mapping
N2A COS Priority Service) in the N2A direction. This option is only applicable if VC Label
Multi COS is Enabled. MPLS Label
Encapsulation Outer
VLAN Tag
Enabled
Untagged Frames Specifies whether untagged traffic is supported on this flow.
Disabled
Whether to enable Independent Shaper Bandwidth in A2N
direciton.
Enabled
When Independent Shaper Bandwidth is disabled, the Shapers
Independent A2N
automatically inherit the CIR and EIR setting from the
Shaper BW
corresponding Policer.
Disabled
When Independent Shaper Bandwidth is enabled, the user can
manually configure CIR and EIR for the Shaper.
Default Priority
Selects a Priority Mapping Profile Identifier for EVPL flow A2N
A2N Priority Mapping ingress P-bit mapping while Multi COS is enabled. Slecting Mapping Profile
Profile (Drop-down list of
None to disable flow-based priority mapping; if a specific profile
available Priority
is selected for this flow, the flow-based priority mapping will
Mapping Profile entity
override related port-based setting.
names)
Selects a Priority Mapping Profile Identifier for EVPL flow N2A None
ingress P-bit mapping while Multi COS is enabled. Default is (Drop-down list of
N2A Priority Mapping
None which means flow-based priority mapping is disabled; if a available Priority
Profile
specific profile is selected for this flow, the flow-based priority Mapping Profile entity
mapping will override related port-based setting. names)
Select the checkbox to associate the access port flow (checkbox
EoMPLS Encapsulation
(EPL/EVPL) with an EoMPLS PW. unselected)
Select a desired EoMPLS PW to associate with from the drop
EoMPLS PW (none by default)
down list.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Specifies whether the flow participates in inner-tag priority
swap. The Priority Mapping Profile - COS Mapping Table Enabled
Inner Tag Priority Con-
allows the A2N inner-tag priority to be specified based on
trol
incoming priority at Access Port (based on priority mapping Disabled
mode - 802.1p, IP-TOS, IP-DSCP).
Specifies whether the flow participates in outer-tag priority
swap. The Priority Mapping Table - COS Mapping Table allows Enabled
Outer Tag Priority Con-
the A2N outer-tag priority to be specified based on incoming pri-
trol
ority at Access Port (based on priority mapping mode - 802.1p, Disabled
IP-TOS, IP-DSCP).
Manages N2A rate limiting, independent of A2N rate limiting. Enabled
Independent N2A Rate
When not enabled, N2A specification is the same as A2N. This
Limiting Disabled
option is only applicable if Multi COS is Disabled.
Frame Loss Threshold 1-100%
A threshold for a flow to be considered as serious frame loss.
Ratio 30%
Shaping method used on A2N direction.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
This option must be configured by a crypto user or by a
Disabled
Superuser. But the Superuser can only configure this option in
Secure Block
flow creation process. See Configure Secure Flow Attributes
Enabled
for details.
Learning Attributes
If set to None, the specified Network Interface will not learn the
None
Network Interface Source MAC Address of received frames; If set to MAC
Learning Control Based, the Network Interface will learn the Source MAC
MAC Based
Address of receiving frames.
Defines the Protected Network Learning Control.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the Protected Access Learning Control.
All flows that begin discarding frames due to this control Block
Aging Timer The aging time of the MAC address learned. 10 - 1,000,000
300
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Tag Management
Defines whether the C (Customer) Tag VLAN ID / VLAN Pri-
ority should be Pushed, Swapped, Popped or no action taken.
Push
l If Push: A2N Push C-TAG containing C-Tag VLAN ID and
C-Tag VLAN Priority. If Push is selected, N2A Outer Tag
Priority Control cannot be selected.
l If Push VID: only the VLAN ID (12 bits) is PUSHed - the
Priority is copied from the incoming tag’s Priority. If Push Swap VID
VID is selected, C-Tag VLAN Priority cannot be entered,
Preserve S-Tag Properties cannot be selected and N2A
Outer Tag Priority Control cannot be selected.
C-Tag Control l If Swap VID: only the VLAN ID (12 bits) are swapped with Push VID
the specified C-Tag VLAN ID. If Swap VID is selected, C-
Tag VLAN Priority cannot be entered, Preserve S-Tag
Properties cannot be selected and N2A Outer Tag Priority
Control cannot be selected.
l If None: This selection provides no tag control action. If None
None is selected, C-Tag VLAN ID/Priority cannot be
entered, Preserve S-Tag Properties cannot be selected and
N2A Outer Tag Priority Control cannot be selected.
l If Pop: A2N Pop C-TAG containing the C-Tag VLAN ID. If Pop
Pop is selected, Preserve S-Tag Properties cannot be
selected and S-Tag Control is set to None.
Defines the C-Tag VLAN ID. If C-Tag Control is set to None,
then C-Tag VLAN ID cannot be entered.
All C-Tag and S-Tag VLAN ID-Priority values must not conflict
on the Network port. (For example: A service with C-Tag
PUSH 100-0, S-Tag PUSH 100-0 will conflict with another ser-
vice with the same C-Tag and S-Tag combination. A service 1 to 4095
with C-Tag PUSH 100-0, S-Tag None will conflict with another
C-Tag service with C-Tag None, S-Tag PUSH 100-0. A EPL service
with C-Tag PUSH 100-0, S-Tag NONE will conflict with an
EVPL service Flow with VLAN Member 100-0, C-Tag NONE
and S-Tag NONE.)
Defines the C-Tag VLAN Priority. If C-Tag Control is set to
None or Push VID, C-Tag VLAN Priority cannot be entered. All
0 to 7
C-Tag and S-Tag VLAN ID-Priority values must not conflict on
the Network port (see above).
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines whether the S (Service) Tag VLAN ID / VLAN Priority
should be PUSHed, Swapped or no action taken.
Push
l If None, S-Tag VLAN ID and S-Tag VLAN Priority cannot
be entered.
l If Push, A2N Push S-TAG containing S-Tag VLAN ID and
S-Tag VLAN Priority. If Push is selected, Preserve S-Tag
S-Tag Control Properties cannot be selected and N2A Outer Tag Priority None
Control cannot be selected.
l If Swap VID, it is only available if C-Tag Control is set to
“None”. If Swap VID is selected, S-Tag VLAN Priority
cannot be entered, Preserve S-Tag Properties can be
selected and N2A Outer Tag Priority Control cannot be Swap VID
selected.
Defines the Transport VLAN ID. If S-Tag Control is set to
None, S-Tag VLAN ID cannot be entered. All C-Tag and S-Tag
VLAN ID-Priority values must not conflict on the Network port.
(For example: A service with C-Tag PUSH 100-0, S-Tag
PUSH 100-0 will conflict with another service with the same C-
1 to 4095
Tag and S-Tag combination. A service with C-Tag PUSH 100-
0, S-Tag None will conflict with another service with C-Tag
S-Tag None, S-Tag PUSH 100-0. An EPL service with C-Tag PUSH
100-0, S-Tag NONE will conflict with an EVPL service Flow
with VLAN Member 100-0, C-Tag NONE and S-Tag NONE.)
Defines the S-Tag VLAN Priority. If S-Tag Control is set to
None, S-Tag VLAN Priority cannot be entered.
0 to 7
All C-Tag and S-Tag VLAN ID-Priority values must not conflict
on the Network port (see above).
Preserve S-Tag Prop- Disabled
Preserve the S-Tag properties.
erties Enabled
Disabled
N2A Outer Tag Priority Enable/Disable N2A Outer Tag priority.
Enabled
A2N Settings
Whether to use Hierarchical COS Settings.
Hierarchical COS Set- Hierarchical COS Settings can be used by selecting the check-
tings box. Hierarchical COS settings allows managing bandwidth
profiles of schedule entities by bounding a group of traffic
classes (Multi COS group). The user can set values for the Enabled
guaranteed and maximum flow bandwidths bounding the whole
multi COS group.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Guaranteed bandwidth for the flow.
By default, GFB is set to the sum of all CIRs for the Multi COS
Guaranteed Flow Band- Group, and can not be set to a lower number. If set to a higher 0 to 1 Gbps
width number, the difference is termed “excess CIR” for the flow. N/A
Unused CIR and excess CIR from other COS levels within the
group are distributed based on the priority levels within the flow
first. Any unused CIR is then shared by other flows in the sys-
tem.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Supports the Hierarchical Class of Service (HCOS) feature.
This option is only available if Multi COS is enabled and
the Hierarchical COS Settings is selected. This is the peak
limit of a flow. Maximum Flow Bandwidth (MFB) must be
greater than or equal to PIR (Peak Information Rate) = CIR +
EIR. The sum of a Flow's A2N Shaper PIR values must be
less than or equal to the oversubscribed Maximum Flow Band-
width value. Note: The oversubscribed Maximum Flow Band-
width value is equal to 8 times the Maximum Flow Bandwidth
value.
By default, MFB is set the greater of: the maximum PIR, or the
GFB for the Multi COS group.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the A2N Policer Committed Information Rate (CIR) for
this Policer, in bps. If Policer EIR is set to 0, then a Policer CIR
value of 64,000 bps or greater must be entered. Policer CIR
and Policer EIR cannot both be set to 0. A2N Policer values are
compared against the Network Port speed. CIR entry must not
exceed the speed of the Network Port. PIR (Peak Information
Rate) = CIR + EIR; must be less than or equal to the Maximum
Flow Bandwidth. The sum of a Flow's A2N Shaper PIR values
must be less than or equal to the oversubscribed Maximum
Flow Bandwidth value. Note: The oversubscribed Maximum
Flow Bandwidth value is equal to 8 times the Maximum Flow
Bandwidth value.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the A2N Policer Excess Information Rate (EIR) for this
port, in bps. If Policer CIR is set to 0, then a Policer EIR value
of 64,000 bps or greater must be entered. Policer CIR and
Policer EIR cannot both be set to 0. A2N Policer values are
compared against the Network Port speed. PIR (Peak Inform-
ation Rate) = CIR + EIR; must be less than or equal to the Max-
imum Flow Bandwidth. The sum of a Flow's A2N Shaper PIR
values must be less than or equal to the oversubscribed Max-
imum Flow Bandwidth value. Note: The oversubscribed Max-
imum Flow Bandwidth value is equal to 8 times the Maximum
Flow Bandwidth value.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Specifies the A2N Policer Coupling Flag. When coupling is
enabled, tokens that would normally be added to the C-bucket
are passed to the E-bucket only once the CIR bucket has
reached its CBS level. Therefore under this condition the E-
Enabled
bucket is being filled at the rate of CIR + EIR. Normally the
long term average of frames declared ˜yellow” is bounded by
the EIR. Coupling is a function to allow the long term average
Policer Color Coupling of frames declared ˜yellow” to be bounded by CIR + EIR. This
Flag allows a higher volume of yellow frames to be delivered/re-
ceived if the arrival of green marked frames is low. Tokens from
the E-bucket do NOT get passed to the C-bucket once the EBS
level has been reached. Enabling coupling in combination with
Disabled
a provisioned EIR of 0 allows for a single rate three color mark-
ing (srTCM) algorithm to be established. In this situation the E-
bucket is filled at the CIR rate in the case the C-bucket is filled
to its CBS level.
Specifies the A2N Shaper Queue Identifier associated with this
Shaper Queue ID Policer. This option is only available if Multi COS is 0-7
enabled.
0-32(GE112Pro series)
The Policer Token-Sharing Envelop to be assigned to the
Envelope
Policer. Tokens are allocated among Policers in an Envelope. 0-64 (GE114Pro
series)
Priority assigned to a Policer when the Policer is in a Token-
Sharing Envelop. A larger number indicates a higher priority.
0
(allocated resource
from port shaper plus
SOAM-EIR
Define the shaper EIR size for the SOAM service on this flow. shaper CIR cannot
exceed 1Gbps)
0
Shaper WRED In-Pro-
The minimum drop threshold for in-profile traffic. 0 - 100
file MIN Threshold %
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Shaper WRED In-Pro-
The maximum drop threshold for in-profile traffic. 0 - 100
file MAX Threshold %
Shaper WRED In-Pro-
file Maximum Drop The maximum drop probability for in-profile traffic. 0 - 100
Probability
Shaper WRED Out-of 0 - 100
Profile MIN Threshold The minimum drop threshold for out-of profile traffic.
% 75
Shaper WRED Out-of 0 - 100
Profile MAX Threshold The maximum drop threshold for out-of profile traffic.
% 75
Shaper WRED Out-of 0 - 100
Profile Maximum Drop The maximum drop probability for out-of profile traffic.
Probability 75
N2A Settings
Checkbox for selecting the desired Active N2A Policers. This
Policer Active Check- option is only available if Multi COS is enabled. Box selec- Check boxes for
box tion must be made before Policer entry is allowed. At least one Policers 0-7
N2A Policer must exist on a Flow.
Defines the N2A Policer Committed Information Rate (CIR) for
this port, in bps. If Policer EIR is set to 0, then a Policer CIR
value of 64,000 bps or greater must be entered. An entry of 0
cannot be entered for both N2A Policer CIR and N2A Policer
EIR. N2A value is compared against the Access Port speed.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the Policer Excess Information Rate (EIR) for this port,
in bps. If Policer CIR is set to 0, then a Policer EIR value of
64,000 bps or greater must be entered. An entry of 0 cannot be
entered for both N2A Policer CIR and N2A Policer EIR. N2A
value is compared against the Access Port speed.
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Defines the frames that belong to the flow. Frames are clas-
sified based on the VLAN tag and the membership is specified
as a list of VLAN IDs. The VLAN member format is VLAN ID-*,
VLAN ID (range)-* or *-Priority. The valid values for VLAN ID
are 0 to 4095. Valid values for Priority are * or 0 to 7. A VLAN ID
range is a contiguous block of VID values delineated by a first
member and a last member, inclusive (e.g., Range 100 - 199
shall consist of all frames with VID values {100, 101..... 198,
199}) including all PRI values for those VIDs, and is entered
using a colon, for example: 100:199. Range must list lower VLAN ID portion of
value on left and larger value on the right. Up to 16 VLAN ID VLAN ID-Priority:
range entries are allowed per flow. 2 VLAN ID range entries are
allowed per flow on average. 0 to 4095, or *
If the Priority value is not specified, all the priority values for
that VLAN ID belongs to the FID. A maximum of 64 members
can be defined for a given FID. If no value is supplied, this FID
becomes the default FID for the port, i.e., all the VLAN IDs that
don’t belong to any other FID on the port belongs to this FID.
VLAN Members
(Regular EVC only) Regarding the use of the “wildcard” value * - The normal des-
ignation of a VLAN Member is X-Y, where X is the VLAN ID
and Y is the Priority. Supported wildcard forms are: X-*, where *
represents any priority value, i.e., flow is priority agnostic and *-
Y where * represents any VLAN ID, i.e., flow is VLAN
agnostic. The rules are: *-Y members can coexist with X-Y
members (same priority) within the same flow as well as
across all flows within the same access port, with the X-Y
member match taking precedence; Default flows (*-*) can coex- Priority portion of
ist with *-Y member flows with the *-Y member match taking VLAN ID-Priority:
precedence; *-Y members cannot coexist with X-* members.
0 to 7, or *
Table 63: Configuration Settings for Ethernet Virtual Private Line Service
Description / Option Settings /
Parameter
Applicable Rules Defaults
Add a specified static destination MAC address to the
Destination Address (blank)
Forwarding table for this flow.
Access Interface of
Select the destination port where the input Destination Address this flow
Destination Port
is learned. Network Interface of
this flow
Select the action to take when this Destination Address is
learned. If set to Block, the learned address will be discarded Block
Learning Action and this flow will block the learning of this MAC address again;
if set to Forward, this flow will forward this learned Destination Forward
Address.
The Priority Mapping Table defines how the A2N/N2A ingress outer tag P-bit (Priority)
swapping and COS mapping will be implemented.
Table 66 and Table 67 identify the default Priority Mapping Tables for 802.1P, IP-TOS
and IP-DSCP.
The COS Mapping Table defines how Tag Priority mapping will be implemented for each
COS.
Table 68 identifies the default COS Mapping Tables for 802.1P, IP-TOS and IP-DSCP in
Ethernet Mode.
Table 69 identifies the default COS Mapping Tables for 802.1P, IP-TOS and IP-DSCP in
EoMPLS Mode.
Refer to the following tables for EoMPLS configuration settings. Default settings are
identified in bold. For details on EoMPLS provisioning, see Provision Ethernet over
Multiprotocol Label Switching (EoMPLS).
Create/Edit EoMPLS PW
Table 70: Create/Edit EoMPLS PW
Description / Option Settings /
Parameter
Applicable Rules Defaults
The entity ID of the EoMPLS Pseudo Wire (PW). The ID range varies 1 - 34
PW ID with GE112Pro series and GE114Pro series. The association between
PW and EVC is 1 to 1 mapping. For GE112Pro series, the system sup- or
(Create only) ports up to 32 PWs; for GE114Pro series, the system supports up to
64 PWs. 1 - 66
Administrative IS
The Administrative State of the EoMPLS Pseudo Wire (PW).
State Mangement
In Raw mode, for EPL flow, there is no operation performed on incom-
ing tags; for EVPL flow, only single membership is allowed and this Tagged
membership VID will be popped in A2N direction and pushed in N2A
Mode direction; untagged is also taken as a VID member.
In Tagged mode, for EPL flow, an inner Stag/Ctag must be applied; for Raw
EVPL flow, there is no operation performed on incoming tags.
Encapsulation Ethernet
The Encapsulation method for the EoMPLS to use
Type GRE
none
Encapsulation The entity employed for Encapsulation. This is configured only when
GRE Tunnels from
Entity the Encapsulation Type is set to GRE.
drop down list
Enabled
Service Delimiting Whether to enable Service Delimiting
Disabled
l Create/Edit Key Exchange Profile (up to 16 Key Exchange Profiles per system)
l Create/Edit Secure Flow
l Associate an Access Flow with a Secure Flow
l Configure crypto user’s authorizations for system operations
If the crypto password is cleared, the crypto user must reset the
crypto password immediately.
Note:Due to PHY limitation, the key exchange frame only supports up to 2 layers of tags.
Select the checkbox by Outer VLAN to enable Key
Outer VLAN (checkbox unselected)
Exchange frame’s Outer VLAN.
Enter the Outer VLAN Tag in the format of “VID - Pri-
Outer VLAN Tag 0-0
ority”. VID = 1- 4095, Priority = 0 - 7.
Select the checkbox by Inner VLAN to enable Key
Inner VLAN1 (checkbox unselected)
Exchange frame’s Inner VLAN.
Enter the Inner VLAN Tag in the format of “VID = Pri-
Inner VLAN1 Tag 0-0
ority”. VID = 1 - 4095, Priority = 0 - 7.
To configure Secure Flow attributes, the crypto user a right-click the desired Access
Flow or Network Layer 3 Flowpoint in ConnectGuard View and select Edit Configuration.
The following system operations must be approved or specified by the crypto user before
the user with appropriate privilege performs the operations.
l Software Install
l Software Version
l Restore Factory Defaults
l Restore Database
l Load Config File
The GE11xPro family products support Layer-3 services (i.e. IP service forwarding)
functionalities, including:
l Create DHCP Relay Agent to include desired Traffic IP Interfaces for dynamic routing
learning
Policers. This option is only available if Multi check boxes for Policer 0 -
Policer Active Checkbox
COS is enabled. To activate Policer entry, select 7
the desired Policer (0 to 7).
Defines the Policer Committed Information Rate 0 - 1 Gbps
(CIR) for this Policer, in bps. If Policer EIR is set
Policer CIR to 0, then a Policer CIR value of 64,000 bps or N/A
greater must be entered. Policer CIR and Policer
EIR cannot both be set to 0.
Defines the Policer Excess Information Rate
Policer EIR (EIR) for this port, in bps. If Policer CIR is set to 0 - 1 Gbps
0, then a Policer EIR value of 64,000 bps or
greater must be entered. Policer CIR and Policer N/A
EIR cannot both be set to 0.
Name.
When the system level alarm “Traffic ARP Table Full” is raised against the
Interface Route, user should not create more Interface Route related static
ARP entries, otherwise layer-3 traffic will be affect.
The system supports up to 128/1024 ARP Entries for Traffic Interface
Routes per GE112Pro/GE114Pro.
Create/Edit VRF
Table 85: Create/Edit VRF
Option Settings /
Parameter Description / Application Rules
Defaults
Identification
1 - 4 for GE112Prox1
VRF Index The Virtual Routing and Forwarding (VRF) entity
index number. This number is automatically or
(Create Only) indexed by the system.
1 - 8 for GE114Prox2
Enter a text and/or number string to uniquely
Alias identify this VRF. This string can be 255 char- (blank)
acters.
State
The administrative state of the VRF. The NE will Management
Administrative
forbid the deletion of a VRF while its state is IS. IS
Configuration
When DHCP Route Control is Enabled, the
dynamic routes learned by a Traffic IP Interface Disabled
based on DHCP Relay Agent can also be used
DHCP Route Control
by the VRF if the Traffic IP Interface is also
included in the VRF. When Disabled, the Enabled
dynamic routes learned cannot be used by VRF.
Traffic IP Interfaces
Select the check boxes by the Traffic IP Interface
EIDs to add the interfaces to the VRF. Note that
Traffic IP Interfaces cannot be shared by different
TRAFFIC IP VRFs. The Traffic IP Interfaces that have been
(a list of available Traffic
INTERFACE List Check selected in the Traffic IP Interface List of another
IP Interface EIDs)
Boxes VRF will not show up here. During editing, remov-
ing a Traffic IP Interface is not allowed if there is
one or more static routes associated with this IP
Interface.
Default is Disabled.
l Provision necessary layer-3 services (L3 Flow Point, ACL, Traffic IP Interface, VRF,
Static Routes, etc), making sure all layer-3 routes between two ends are reachable
and resolvable (See Layer-3 Services Configuration Options and Rules for more
information on options and rules, see Provision Layer-3 Services for more information
on the procedure and see FSP 150-GE11xPro Quick Start Guide for specific use case)
l Create/Edit BFD Session
Refer to the following table for BFD configuration settings. Default settings are identified
in bold. For details on BFD provisioning, see Provision Bidirectional Fault Detection
(BFD).
Note 2: Select the checkboxes by the desired Traffic IP Interfaces created on Associated Port to asso-
ciate them with the BFD Session.
Note 3: The Traffic IP Interfaces which have been associated with BFD Sessions will not appear.
0-255 characters
Alias A string to help identify this VTEP IP Interface.
blank
0-1677215
VNI VXLAN Network Identifier (VNI).
1
Outer Tag Priority Con- Whether to enable Encapsulation Outer Tag Priority for the Disabled
trol Segment. Enabled
Internal ClassWhether to enable Encapsulation Outer Tag Disabled
Inner Tag Priority Control
Priority for the Segment. Enabled
Disabled
DSCP Control Whether to enable DSCP for the Segment.
Enabled
1-4096
Max DMAC2DIP Entry Max DMAC2DIP Entry
1000
DMAC2DIP Table Aging 0, 10-10000 (Seconds)
The aging time for the entries in the DMAC to DIP.
Time 300
When there is Load-Sharing LAG existing on Network Ports, it is up to the user to provision
the VTEP IP interface and VXLAN Flow with the same LAG member port. Traffic can be
blocked otherwise.
Disabled
Match VLAN ID Whether to enable or disable matching traffic with VID
Enabled
Match Source IP Disabled
Whether to enable or disable matching traffic with SIP
Address Enabled
Disabled
Match Source IP Prefix Whether to enable or disable matching traffic with SIP Prefix
Enabled
Source IP Prefix The target SIP Prefix, when SIP Prefix matching is enabled. 1-32
Match Destination IP Disabled
Whether to enable or disable matching traffic with DIP
Address Enabled
Match Destination IP Disabled
Whether to enable or disable matching traffic with DIPPrefix
Prefix Enabled
Destination IP Prefix The target DIP Prefix, when DIP Prefix matching is enabled. 1-32
Disabled
Match Protocol Whether to enable or disable matching traffic with Protocol.
Enabled
Disabled
Match TOS Whether to enable or disable matching traffic with TOS.
Enabled
Disabled
Match TOS Range Whether to enable or disable matching traffic with a TOS Range
Enabled
Min TOS The lower limit of the target TOS range. 0-7
Max TOS The higher limit of the target TOS range. 0-7
To delete an existing management tunnel, enter a right click on the desired management
tunnel and select Delete and then select OK. A Management Tunnel cannot be deleted if
the it has been selected as the agent-address value for Static Route, Static ARP Entry
or Source Address Config.
The following management tunnel provisioning options and rules are described for each
option setting available:
l When no LAG group is established, all Network ports and all Access ports are
available for creating management tunnels.
l When LAG groups are established, the Network or Access Ports used as members
are no longer available - the management tunnel is assigned to the LAG instead.
CAUTION:
When there is a MAC-based Management Tunnel, PTPoUDP and
TWAMP do not work properly on the same port. Also, Y.1731 Lose
Measurement (LM) on the same port cannot count the received ARP
packets for other application ( for instance, EoMPLS) correctly.
1If RIP is enabled on an interface and you are changing the IP address, it may take minutes for RIP to
advertise the new IP address. If RIP is enabled on an interface, it is recommended that you perform a FSP
150 reboot after changing the IP address. This will force RIP to advertise the address immediately. Note that
this operation should be performed locally, or a static route must be created to the remote in order to make
the changes remotely.
IPv6 RA Prefix The IPv6 Prefix to be dispatched to link in Router mode. [Link]
/0
Edit System Selecting the checkbox allows editing the Gateway IPv6
(checkbox unselected)
Default Gateway Address.
Gateway IPv6 Enter a Gateway IPv6 Address if the “Edit System Default
(grayed out)
Address Gateway” checkbox is selected.
VLAN Based
Tunnel Mode Defines the management tunnel mode.
MAC Based
Enable or Disable C-Tag VLAN ID entry. This option is not
Enabled
available when Tunnel Mode is set to MAC Based, and can-
C-Tag VLAN
not be enabled with S-Tag VLAN at the same time when Tun-
Disabled
nel Mode is set to ITAG Based.
Define the C-Tag Management VLAN ID. It is used to
C-Tag VLAN ID identify management traffic on the port. This option is only 1 to 4095
editable when C-Tag VLAN is enabled.
Enable or Disable S-Tag VLAN ID entry. This option is not
Enabled
available when Tunnel Mode is set to MAC Based and can-
S-Tag VLAN
not be enabled with C-Tag VLAN at the same time when Tun-
Disabled
nel Mode is set to ITAG Based.
Define the S-Tag Management VLAN ID. It is used to identify
S-Tag VLAN ID management traffic on the port. This option is only available 1 to 4095
when S-Tag Vlan is enabled.
Committed Information Rate for the management tunnel. Min-
CIR imum setting is 0 bps, maximum setting is Network Port 256000
bandwidth. Default is 256000 bps.
Excess Information Rate for the management tunnel. Min-
EIR imum setting is 0 bps, maximum is Network Port bandwidth. 768000
Default is 768000 bps.
Denotes the amount of memory in KB devoted to buffering
Buffer Size management tunnel packets. Minimum is 32, maximum is 32 - 33554
33554. Default is 32.
To delete an existing IPv6 over IPv4 tunnel, enter a right click on the IPv6 over IPv4
tunnel and select Delete and then select OK. An IPv6 over IPv4 tunnel cannot be deleted
if it has been selected as the Interface Name value for IPv6 Static Route, IPv6 Static
Neighbor Entry or IPv6 Static ProxyND Entry.
Table 96 summarizes the list of relevant Layer 2 control protocols and Cisco proprietary
protocols that are the subject of this feature.
01-80-C2-00-00-2F
Loopback Settings
Refer to Table 100 for Network and Access Port loopback option settings. To set
loopback options, select Maintenance view, enter a right click on the desired entity in the
Selection Tree and select Loopback. The Administrative State must be set to
Maintenance prior to initiating a loopback. For Network interfaces when a Dual Active
Receive Protection Group is present, only a Network-1 or Network-2 loopback may be
applied at a time. Independent loopbacks may be applied simultaneously on Network-1
and Network-2 if a 1+1 Protection Group exists. Default settings are identified in bold.
The following loopback provisioning options and rules are described for each option
setting available:
When using the web-based GUI “None” is used to remove a Terminal Port
loopback.
Terminal Port Timed
The following provisioning options and rules are described for each option setting
available. Default settings are identified in bold.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsABRRx ABR-RX Average Bit Rate Received. The Receive Near End 0 0
average bit rate received over the
specific interval in the ingress dir-
ection. If there is link down during
the interval, the bin is not access-
ible. This counter is based on
RMON etherStatsOctets.
cmEthernetNetPortStatsABRTx ABR-TX Average Bit Rate Transmitted. The Receive Near End 0 0
average bit rate transmitted over a
specific interval in the egress dir-
ection, based on Bytes Sent. If
there is link down during the inter-
val, the bin is not accessible.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortAclDropNotMatch AclDropNotMatch AclRule Drop Not Match Receive Near End 0 0
cmEthernetNetPortAclFwd2Cpu AclFwd2Cpu AclRule Forward To CPU Receive Near End 0 0
cmEthernetNetPortDhcpDropNoAssocIf DhcpDropNoAssocIf Drop DHCP Packets Due To No Receive Near End 0 0
Associated Traffic IP Interface
cmEthernetNetPortStatsESBF ESBF EtherStats Broadcast Frames. The Receive Near End 0 0
Broadcast Frames Sent in the
egress direction If there is link
down during the interval, the bin is
not accessible.
cmEthernetNetPortStatsESBP ESBP EtherStats Broadcast Packets Receive Near End 0 0
Received. The total number of good
packets received that were directed
to the broadcast address. Note that
this does not include multicast
packets.
cmEthernetNetPortStatsESBS ESBS EtherStats Bytes Sent. The Bytes Transmit Near End 0 0
Sent in the egress direction If there
is link down during the interval, the
bin is not accessible.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESC ESC EtherStats Collisions. The best Receive Near End 0 0
estimate of the total number of col-
lisions on this Ethernet segment.
The value returned will depend on
the location of the RMON probe.
Section [Link] (10BASE-5) and
section [Link] (10BASE-2) of
IEEE standard 802.3 states that a
station must detect a collision, in
the receive mode, if three or more
stations are transmitting sim-
ultaneously. A repeater port must
detect a collision when two or more
stations are transmitting sim-
ultaneously.
cmEthernetNetPortStatsESCAE ESCAE EtherStats CRC (Cyclic Redund- Receive Near End 37055 3557280
ancy Check) Aligned Errors. The
total number of packets received
that had a length (excluding framing
bits, but including FCS octets) of
between 64 and 1518 octets, inclus-
ive, but had either a bad Frame
Check Sequence (FCS) with an
integral number of octets (FCS
Error) or a bad FCS with a non-
integral number of octets (Align-
ment Error).
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESDE ESDE EtherStats Drop Events. The total Receive Near End 37055 3557280
number of events in which packets
were dropped due to lack of
resources. Note that this number is
not necessarily the number of pack-
ets dropped; it is just the number of
times this condition has been detec-
ted.
cmEthernetNetPortStatsESF ESF EtherStats Fragments. The total Receive Near End 37055 3557280
number of packets received that
were less than 64 octets in length
(excluding framing bits but includ-
ing FCS octets) and had either a
bad Frame Check Sequence (FCS)
with an integral number of octets
(FCS Error) or a bad FCS with a
non-integral number of octets (Align-
ment Error). Note that it is entirely
normal for etherStatsFragments to
increment. This is because it
counts both runts (which are normal
occurrences due to collisions) and
noise hits.
cmEthernetNetPortStatsESFS ESFS EtherStats Frames Sent. The Receive Near End 0 0
Frames Sent in the egress direction
If there is link down during the inter-
val, the bin is not accessible.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESJ ESJ EtherStats Jabbers. The total num- Receive Near End 0 0
ber of packets received that were
longer than 1518 octets (excluding
framing bits, but including FCS oct-
ets), and had either a bad Frame
Check Sequence (FCS) with an
integral number of octets (FCS
Error) or a bad FCS with a non-
integral number of octets (Align-
ment Error).
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESMP ESMP EtherStats Multicast Packets Receive Near End 0 0
Received. EtherStats Multicast
Packets Received. The total num-
ber of good packets received that
were directed to a multicast
address. Note that this number
does not include packets directed
to the broadcast address.
cmEthernetNetPortStatsESO ESO EtherStats Octets Received. The Receive Near End 0 0
total number of octets of data
(including those in bad packets)
received on the network (excluding
framing bits but including FCS oct-
ets).
cmEthernetNetPortStatsESOF ESOF EtherStats Oversize Frames. The Transmit Near End 0 0
total number of frames received
that were oversized.
cmEthernetNetPortStatsESOP ESOP EtherStats Oversize Packets. The Receive Near End 37055 3557280
total number of packets received
that were longer than 1518 octets
(excluding framing bits, but includ-
ing FCS octets) and were oth-
erwise well formed.
cmEthernetNetPortStatsESP ESP EtherStats Packets Received. Receive Near End 0 0
EtherStats Packets Received. The
total number of packets (including
bad packets, broadcast packets,
and multicast packets) received.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESP1024 ESP1024 EtherStats Packets - 1024 to 1518 Receive Near End 0 0
Octets Frames. The total number of
packets (including bad packets)
received that were between 1024
and 1518 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
cmEthernetNetPortStatsESP128 ESP128 EtherStats Packets - 128 to 255 Receive Near End 0 0
Octets Frames. The total number of
packets (including bad packets)
received that were between 128
and 255 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
cmEthernetNetPortStatsESP1519 ESP1519 EtherStats Packets - 1519 to 1536 Receive Near End 0 0
Octets Frames. The total number of
packets (including bad packets)
received that were between 1519
and 1536 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
cmEthernetNetPortStatsESP256 ESP256 EtherStats Packets - 256 to 511 Receive Near End 0 0
Octet Packets. The total number of
packets (including bad packets)
received that were between 256
and 511 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESP512 ESP512 EtherStats Packets - 512 to 1023 Receive Near End 0 0
Octets Frames. The total number of
packets (including bad packets)
received that were between 512
and 1023 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
cmEthernetNetPortStatsESP64 ESP64 EtherStats Packets - 0 to 64 Octets Receive Near End 0 0
Frames. The total number of pack-
ets (including bad packets)
received that were 64 octets in
length (excluding framing bits but
including FCS octets).
cmEthernetNetPortStatsESP65 ESP65 EtherStats Packets - 65 to 127 Oct- Receive Near End 0 0
ets Frames. The total number of
packets (including bad packets)
received that were between 65 and
127 octets in length inclusive
(excluding framing bits but includ-
ing FCS octets).
cmEthernetNetPortStatsESUF ESUF EtherStats Unicast Frames. The Transmit Near End 0 0
Unicast Frames Sent in the egress
direction If there is link down during
the interval, the bin is not access-
ible.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsESUP ESUP EtherStats Undersize Packets. Receive Near End 37055 3557280
The total number of packets
received that were less than 64 oct-
ets long (excluding framing bits, but
including FCS octets) and were oth-
erwise well formed.
cmEthernetNetPortStatsIBR-RX IBR-RX Instantaneous Bit Rate Received Receive Near End 0 0
cmEthernetNetPortStatsIBR-TX IBR-TX Instantaneous Bit Rate Trans- Transmit Near End 0 0
mitted
cmEthernetNetPortStatsIBRMAX-RX IBRMAX-RX Instantaneous Bit Rate Maximum Receive Near End 0 0
Received
cmEthernetNetPortStatsIBRMAX-TX IBRMAX-TX Instantaneous Bit Rate Maximum Transmit Near End 0 0
Transmitted
cmEthernetNetPortStatsIBRMIN-RX IBRMIN-RX Instantaneous Bit Rate Minimum Receive Near End 0 0
Received
cmEthernetNetPortStatsIBRMIN-TX IBRMIN-TX Instantaneous Bit Rate Minimum Transmit Near End 0 0
Transmitted
cmEthernetNetPortStatsL2CPFD L2CPFD Layer 2 Control Protocol Frames Receive Near End 0 0
Discarded. Number of Layer 2 Con-
trol Protocol Frames discarded on
the interface.
cmEthernetNetPortStatsL2CPFP L2CPFP Layer 2 Control Protocol Frames Receive Near End 0 0
Processed. Number of Layer 2 Con-
trol Protocol Frames processed on
the interface.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsL2PTTxFramesDecap L2PTFD Number of transmitted Layer 2 Pro- Transmit Near End 0 0
tocol Tunneling Frames Decap-
sulated.
cmEthernetNetPortStatsL2PTRxFramesEncap L2PTFE Number of received Layer 2 Pro- Receive Near End 0 0
tocol Tunneling Frames Encap-
sulated.
cmEthernetNetPortStatsLBC LBC1 Laser Bias Current retrieved from Receive Near End 0 0
the SFP. Applicable only if the
media type is Fiber.
cmEthernetNetPortThresholdVarOprVariance OPR-VAR1 Variance in the Optical Power Transmit Near End 4 4
received (in dbM), beyond which
threshold crossing alert will be gen-
erated.
cmEthernetNetPortStatsOPR OPR1 Optical Power Receive (in dBm) for Receive Near End -80 -80
the physical layer. This is applic-
able only if the media type for the
Network Port is fiber.
cmEthernetNetPortThresholdVarOptVariance OPT-VAR1 Variance in the Optical Power trans- Transmit Near End 4 4
mitted (in dbM), beyond which
threshold crossing alert will be gen-
erated.
cmEthernetNetPortStatsOPT OPT1 Optical Power Transmit (in dBm) Receive Near End -80 -80
for the physical layer. This is applic-
able only if the media type for the
Network Port is fiber.
cmEthernetNetPortStatsOPR PSC Protection Switch Count Receive Near End 0 0
1Valid only when the port is configured to use the fiber interfaces.
Table 103: Ethernet Network Port Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Description Direction Location 1 Day
5Min.
cmEthernetNetPortStatsTemp TEMP1 Temperature for the physical layer None Near End 0 0
(expressed in Celsius). Applicable
only if the media type is Fiber.
cmEthernetNetPortStatsUAS UAS Unavailable Seconds - counted if Receive Near End 0 0
one or more of following exists in
that second: Link down, link deac-
tivated (triggered by LLF), SFP
faults, EFM-OAM discovery failure,
and EFM-OAM local loopback.
Also, any one of the following port
based MEP conditions: cross con-
nect defect (unexpected MD level
or MAID Mismatch), Error CCM
Defect (Unexpected MEP or unex-
pected period), RMEP CCM Defect
(Loss of Connectivity), and RDI
Defect (unidirectional failure makes
the port based service unavailable).
When the Access port is configured in EPL mode, a single service (Flow) is also configured which has counters associated with it.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmAccPortQosShaperStatsABRRL ABR-RX Average Bit Rate Received. The average bit rate Receive Near End 0 0
received over the specific interval in the ingress dir-
ection. This counter is based on RMON eth-
erStatsOctets.
cmEthernetAccPortStatsABRTx ABR-TX Average Bit Rate Transmitted. The average bit rate Transmit Near End 0 0
transmitted over a specific interval in the egress dir-
ection, based on Bytes Sent.
cmEthernetAccPortAclDropNotMatch AclDropNotMatch AclRule Drop Not Match Receive Near End 0 0
cmEthernetAccPortAclFwd2Cpu AclFwd2Cpu AclRule Forward To CPU Receive Near End 0 0
cmEthernetAccPortStatsAPFD APFD AFP Priority-tagged Frames Dropped. Priority-tagged Receive Near End 0 0
frames dropped due to AFP setting. AFP Priority-tagged
Frames Dropped. Priority-tagged frames dropped due to
AFP setting.
cmEthernetAccPortStatsAUFD AUFD AFP Untagged Frames Dropped. Untagged frames Receive Near End 0 0
dropped due to AFP setting.
cmEthernetAccPortDhcpDropNoAssocIf DhcpDropNoAssocIf Drop DHCP Packets Due To No Associated Traffic IP Receive Near End 0 0
Interface
cmEthernetAccPortStatsESBF ESBF EtherStats Broadcast Frames. If there is link down dur- Receive Near End 0 0
ing the interval, the bin is not accessible.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsESBP ESBP EtherStats Broadcast Packets Received (in the A2N dir- Receive Near End 0 0
ection). The total number of good packets received that
were directed to the broadcast address. Note that this
does not include multicast packets.
cmEthernetAccPortStatsESBS ESBS EtherStats Bytes Sent. Transmit Near End 0 0
cmEthernetAccPortStatsESC ESC EtherStats Collisions. The best estimate of the total Receive Near End 0 0
number of collisions on this Ethernet segment. The
value returned will depend on the location of the RMON
probe. Section [Link] (10BASE-5) and section [Link]
(10BASE-2) of IEEE standard 802.3 states that a station
must detect a collision, in the receive mode, if three or
more stations are transmitting simultaneously. A
repeater port must detect a collision when two or more
stations are transmitting simultaneously.
cmEthernetAccPortStatsESCAE ESCAE EtherStats CRC (Cyclic Redundancy Check) Aligned Receive Near End 37055 3557280
Errors. The total number of packets received that had a
length (excluding framing bits, but including FCS octets)
of between 64 and 1518 octets, inclusive, but had either
a bad Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with a non-
integral number of octets (Alignment Error).
cmEthernetAccPortStatsESDE ESDE EtherStats Drop Events. The total number of events in Receive Near End 37055 3557280
which packets were dropped due to lack of resources.
Note that this number is not necessarily the number of
packets dropped; it is just the number of times this con-
dition has been detected.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsESF ESF EtherStats Fragments. The total number of packets Receive Near End 37055 3557280
received that were less than 64 octets in length (exclud-
ing framing bits but including FCS octets) and had either
a bad Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with a non-
integral number of octets (Alignment Error). Note that it
is entirely normal for etherStatsFragments to increment.
This is because it counts both runts (which are normal
occurrences due to collisions) and noise hits.
cmEthernetAccPortStatsESFS ESFS EtherStats Frames Sent. The Frames Sent in the egress Transmit Near End 0 0
direction.
cmEthernetAccPortStatsESJ ESJ EtherStats Jabbers. The total number of packets Receive Near End 0 0
received that were longer than 1518 octets (excluding
framing bits, but including FCS octets), and had either a
bad Frame Check Sequence (FCS) with an integral num-
ber of octets (FCS Error) or a bad FCS with a non-integ-
ral number of octets (Alignment Error).
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsESMP ESMP EtherStats Multicast Packets Received. EtherStats Receive Near End 0 0
Multicast Packets Received. The total number of good
packets received that were directed to a multicast
address. Note that this number does not include packets
directed to the broadcast address.
cmEthernetAccPortStatsESO ESO EtherStats Octets Received. The total number of octets Receive Near End 0 0
of data (including those in bad packets) received on the
network (excluding framing bits but including FCS oct-
ets).
cmEthernetAccPortStatsESOF ESOF EtherStats Oversize Frames. The total number of Transmit Near End 0 0
frames transmitted that were oversized.
cmEthernetAccPortStatsESOP ESOP EtherStats Oversize Packets. The total number of pack- Receive Near End 37055 3557280
ets received that were longer than 1518 octets (exclud-
ing framing bits, but including FCS octets) and were
otherwise well formed.
cmEthernetAccPortStatsESP ESP EtherStats Packets Received. The total number of pack- Receive Near End 0 0
ets (including bad packets, broadcast packets, and mul-
ticast packets) received.
cmEthernetAccPortStatsESP1024 ESP1024 EtherStats Packets - 1024 to 1518 Octets Frames. The Receive Near End 0 0
total number of packets (including bad packets) received
that were between 1024 and 1518 octets in length inclus-
ive (excluding framing bits but including FCS octets).
cmEthernetAccPortStatsESP128 ESP128 EtherStats Packets - 128 to 255 Octets Frames. The Receive Near End 0 0
total number of packets (including bad packets) received
that were between 128 and 255 octets in length inclusive
(excluding framing bits but including FCS octets).
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsESP1519 ESP1519 EtherStats Packets - 1519 to 1536 Octets Frames. The Receive Near End 0 0
total number of packets (including bad packets) received
that were between 1519 and 1536 octets in length inclus-
ive (excluding framing bits but including FCS octets).
cmEthernetAccPortStatsESP256 ESP256 EtherStats Packets - 256 to 511 Octet Packets. The Receive Near End 0 0
total number of packets (including bad packets) received
that were between 256 and 511 octets in length inclusive
(excluding framing bits but including FCS octets).
cmEthernetAccPortStatsESP512 ESP512 EtherStats Packets - 512 to 1023 Octets Frames. The Receive Near End 0 0
total number of packets (including bad packets) received
that were between 512 and 1023 octets in length inclus-
ive (excluding framing bits but including FCS octets).
cmEthernetAccPortStatsESP64 ESP64 EtherStats Packets - 0 to 64 Octets Frames. The total Receive Near End 0 0
number of packets (including bad packets) received that
were 64 octets in length (excluding framing bits but
including FCS octets).
cmEthernetAccPortStatsESP65 ESP65 EtherStats Packets - 65 to 127 Octets Frames. The total Receive Near End 0 0
number of packets (including bad packets) received that
were between 65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets).
cmEthernetAccPortStatsESUF ESUF EtherStats Unicast Frames sent. If there is link down Transmit Near End 0 0
during the interval, the bin is not accessible.
cmEthernetAccPortStatsESUP ESUP EtherStats Undersize Packets received. The total num- Receive Near End 37055 3557280
ber of packets received that were less than 64 octets
long (excluding framing bits, but including FCS octets)
and were otherwise well formed.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsIBR-RX IBR-RX Instantaneous Bit Rate Received Receive Near End 0 0
cmEthernetAccPortStatsIBR-TX IBR-TX Instantaneous Bit Rate Transmitted Transmit Near End 0 0
cmEthernetAccPortStatsIBRMAX-RX IBRMAX-RX Instantaneous Bit Rate Maximum Received Receive Near End 0 0
cmEthernetAccPortStatsIBRMAX- IBRMAX-TX Instantaneous Bit Rate Maximum Transmitted Transmit Near End 0 0
TX
cmEthernetAccPortStatsIBRMIN- IBRMIN-RX Instantaneous Bit Rate Minimum Received Receive Near End 0 0
RX
cmEthernetAccPortStatsIBRMIN- IBRMIN-TX Instantaneous Bit Rate Minimum Transmitted Transmit Near End 0 0
TX
cmEthernetAccPortStatsL2CPFD L2CPFD Layer 2 Control Protocol Frames Discarded. Number of Receive Near End 0 0
Layer 2 Control Protocol Frames discarded on the inter-
face.
cmEthernetAccPortStatsL2CPFP L2CPFP Layer 2 Control Protocol Frames Processed. Number of Receive Near End 0 0
Layer 2 Control Protocol Frames processed on the inter-
face.
cmEthernetAccPortStatsL2PTTxFramesDecap L2PTFD Number of transmitted Layer 2 Protocol Tunneling Transmit Near End 0 0
Frames Decapsulated.
cmEthernetAccPortStatsL2PTRxFramesEncap L2PTFE Number of received Layer 2 Protocol Tunneling Frames Receive Near End 0 0
Encapsulated.
cmEthernetAccPortStatsLBC LBC1 Laser Bias Current retrieved from the SFP. Applicable Receive Near End 0 0
only if the media type is Fiber.
1Valid only when the port is configured to use the fiber interfaces.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortThresholdVarOprVariance OPR-VAR1 Variance in the Optical Power received (in dbM), beyond Transmit Near End 4 4
which threshold crossing alert will be generated.
cmEthernetAccPortStatsOPR OPR1 Optical Power Receive (in dBm) for the physical layer. Receive Near End -80 -80
This is applicable only if the media type for the Access
Port is fiber.
cmEthernetAccPortThresholdVarOptVariance OPT-VAR1 Variance in the Optical Power transmitted (in dbM), bey- Transmit Near End 4 4
ond which threshold crossing alert will be generated.
cmEthernetAccPortStatsOPT OPT1 Optical Power Transmit (in dBm) for the physical layer. Receive Near End -80 -80
This is applicable only if the media type for the Access
Port is fiber.
cmEthernetAccPortStatsTemp TEMP1 Temperature for the physical layer (expressed in None Near End 0 0
Celsius). Applicable only if the media type is Fiber.
Table 104: Ethernet Access Port Monitored Types and Default TCA Settings
15
SNMP statsEntry Monitored Type Description Direction Location Min./ 1 Day
5Min.
cmEthernetAccPortStatsPSC UAS1 Unavailable Seconds. Used by Network/Service Man- Receive Near End 0 0
agement Systems to compute port-based service un-
availability. Counted if one or more of following exists in
that second:
l Link down
l link deactivated (triggered by LLF)
l SFP faults
l EFM-OAM discovery failure
l EFM-OAM loopback.
1Any second that is deemed UAS for the port will also be UAS for all the EVCs on that port.
Table 105: Ethernet Access Port QoS Shaper/LAG N2A Shaper Monitored Types and Default TCA Settings
Monitored 15 Min./
SNMP statsEntry Definition Direction Location 1 Day
Type 5Min.
cmAccPortQosShaperStatsABRRL ABRRL Average Bit Rate - Rate Limited for QoS queue n1. Receive Near End 0 0
cmAccPortQosShaperStatsBREDD BREDD Bytes Random Early Discard Dropped Transmit Near End 0 0
cmAccPortQosShaperStatsBT BT Bytes Transmitted by QoS queue n1 Receive Near End 0 0
cmAccPortQosShaperStatsBTD BTD Bytes Tail Dropped from this QoS queue n1 (in the Receive Near End 0 0
N2A direction).
cmAccPortQosShaperStatsFD FD Frames Dequeued by QoS queue n1 Receive Near End 0 0
cmAccPortQosShaperStatsFREDD FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
cmAccPortQosShaperStatsFTD FTD Frames Tail Dropped by QoS queue n1 Receive Near End 0 0
Table 106: Ethernet Network Port A2N Shaper and LAG A2N Shaper Monitored Types and Default TCA Settings
Monitored 15 Min./
SNMP statsEntry Definition Direction Location 1 Day
Type 5Min.
f3NetPortQosShaperStatsABRRL ABRRL Average Bit Rate - Rate Limited for QoS queue n1 Receive Near End 0 0
f3NetPortShaperStatsBREDD BREDD Bytes Random Early Discard Dropped Transmit Near End 0 0
f3NetPortQosShaperStatsBT BT Bytes Transmitted by QoS queue n 1 Receive Near End 0 0
f3NetPortQosShaperStatsBTD BTD Bytes Tail Dropped from this QoS queue n 1(in the Receive Near End 0 0
N2A direction).
f3NetPortQosShaperStatsFD FD Frames Dequeued by QoS queue n 1 Receive Near End 0 0
f3NetPortShaperStatsFREDD FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
f3NetPortQosShaperStatsFTD FTD Frames Tail Dropped by QoS queue n 1 Receive Near End 0 0
All Flow-based Shapers, for Service Flow or Pass-through Flow, share the same Monitor types. In SNMP the Monitor types are tracked in the same
table.
Table 107: Ethernet Network Port Flow A2N and Pass-through Flow N2N Shaper Monitored Types and Default TCA Settings
Monitored 15 Min./
SNMP statsEntry Definition Direction Location 1 Day
Type 5Min.
cmQosShaperStatsABRRL ABRRL Average Bit Rate - Rate Limited for QoS queue n1. Receive Near End 0 0
cmQosShaperStatsBREDD BREDD Bytes Random Early Discard Dropped Transmit Near End 0 0
cmQosShaperStatsBT BT Bytes Transmitted by QoS queue n Receive Near End 0 0
cmQosShaperStatsBTD BTD Bytes Tail Dropped from this QoS queue n (N2A) . Receive Near End 0 0
cmQosShaperStatsFD FD Frames Dequeued by QoS queue n Receive Near End 0 0
cmQosShaperStatsFREDD FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
cmQosShaperStatsFTD FTD Frames Tail Dropped by QoS queue n Receive Near End 0 0
1Up to 8 based on how many policers/queues are being used by the Flow
Table 109: QOS Flow Policer Monitored Types and Default TCA Settings
Monitored 15 Min./
SNMP statsEntry Definition Direction Location 1 Day
Type 5Min.
cmQosFlowPolicerStatsABR ABR Average Bit Rate - for Policer n1 . Receive Near End 0 0
cmQosFlowPolicerStatsBytesIn BYTESIN Number of bytes received by the Policer. Receive Near End 0 0
cmQosFlowPolicerStatsBytesOut BYTESOUT Number of bytes transmitted by the Policer. Receive Near End 0 0
cmQosFlowPolicerStatsFMG FMG Frames Marked Green and Passed for Policer Receive Near End 0 0
n.
cmQosFlowPolicerStatsFMRD FMRD Frames Marked Red and Discarded for Policer Receive Near End 0 0
n.
cmQosFlowPolicerStatsFMY FMY Frames Marked Yellow and Passed for Policer Receive Near End 0 0
n.
Table 110: Layer-three QOS Policer Monitored Types and Default TCA Settings
Monitored 15 Min./
SNMP statsEntry Definition Direction Location 1 Day
Type 5Min.
f3L3QosPolicerStatsABR ABR Average Bit Rate Receive Near End 0 0
f3L3QosPolicerStatsBytesIn BYTESIN Total Bytes In Receive Near End 0 0
f3L3QosPolicerStatsBytesOut BYTESOUT Total Bytes Out Receive Near End 0 0
f3L3QosPolicerStatsFMG FMG Frames Marked Green and Passed Receive Near End 0 0
f3L3QosPolicerStatsFMRD FMRD Frames Marked Red and Discarded Receive Near End 0 0
f3L3QosPolicerStatsFMY FMY Frames Marked Yellow and Passed Receive Near End 0 0
Table 111: layer-three QOS Shaper Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Definition Direction Location 15 Min./ 1 Day
Type 5Min.
f3L3QosShaperStatsABRRL ABRRL Average Bit Rate - Rate Limited Receive Near End 0 0
f3L3QosShaperStatsBREDD BREDD Bytes Random Early Discard Dropped Transmit Near End 0 0
f3L3QosShaperStatsBT BT Bytes Dequeued (Transmitted) Receive Near End 0 0
f3L3QosShaperStatsBTD BTD Bytes Tail Dropped Receive Near End 0 0
f3L3QosShaperStatsFD FD Frames Dequeued Receive Near End 0 0
f3L3QosShaperStatsFREDD FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
f3L3QosShaperStatsFTD FTD Frames Tail Dropped Receive Near End 0 0
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
f3EsaProbeStatsSoamPmExtAvgAbsRTJitter AVG-ABSRTJITTER Average Absolute Round Trip Jitter (µsec) 0
f3EsaProbeStatsSoamPmExtAvgP2RFDR AVG-P2R-FDR Average Probe to Reflector Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtAvgR2PFDR AVG-R2P-FDR Average Reflector to Probe Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtAvgRTFDR AVG-RT-FDR Average Round Trip Frame Delay Range (µsec) 0
esaProbeStatsAvgRoundTripDelay AVG-RTDELAY The average round-trip delay (in µsec) across all packets 0
received in the current interval. The reflector's pro-
cessing time is excluded from the value.
esaProbeStatsLostPkts LOST-FRAMES The total number of Lost Packets in the current interval. 0
Packets which are not received from the reflector end
beyond the configured timeout value are termed as lost.
NOTE: This is not applicable for Y.1731 probes.
f3EsaProbeStatsSoamPmExtMaxAbsRTJitter MAX-ABSRTJITTER Max Absolute Round Trip Jitter (µsec) 0
f3EsaProbeStatsSoamPmExtMaxP2RFDR MAX-P2R-FDR Max Probe to Reflector Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtMaxR2PFDR MAX-R2P-FDR Max Reflector to Probe Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtMaxRTFDR MAX-RT-FDR Max Round Trip Frame Delay Range (µsec) 0
esaProbeStatsMaxRoundTripDelay MAX-RTDELAY The maximum round-trip delay (in µsec) across all pack- 0
ets received in the current interval. The reflector's pro-
cessing time is excluded from the value.
f3EsaProbeStatsSoamPmExtMinAbsRTJitter MIN-ABSRTJITTER Min Absolute Round Trip Jitter (µsec) 0
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsMinRoundTripDelay MIN-RTDELAY The minimum round-trip delay (in µsec) across all pack- 0
ets received in the current interval. The reflector's pro-
cessing time is excluded from the value.
f3EsaProbeStatsSoamPmExtNumAbsRTJitter NUM-ABSRTJITTER Number of Absolute Round Trip Jitter 0
f3EsaProbeStatsSoamPmExtNumP2RFDR NUM-P2R-FDR Number Probe to Reflector Frame Delay Range 0
f3EsaProbeStatsSoamPmExtNumR2PFDR NUM-R2P-FDR Number Reflector to Probe Frame Delay Range 0
f3EsaProbeStatsSoamPmExtNumRTFDR NUM-RT-FDR Number Round Trip Frame Delay Range 0
esaProbeStatsOutOfSeqErrs OUTOFSEQ-ERRS1 Out of Sequence Errors. The total number of out of 0
sequence errors across all packets received in the cur-
rent interval. If (Received Sequence Number) is less
than or equal to (Last Received Sequence Number) it is
termed as out of sequence error. NOTE: This is not
applicable for Y.1731 probes.
f3EsaProbeStatsSoamPmExtP2rAvailableDeltaTs P2R-AVAIL-DELTA-TS Probe to Reflector Available Delta TS (µsec) 0
f3EsaProbeStatsSoamPmExtP2rAvailableTime P2R-AVAIL-TIME Probe to Reflector Available Time (µsec) 0
f3EsaProbeStatsSoamPmExtAvgP2RFlr P2R-AVG-FLR Probe to Reflector Average FLR (m%) 0
esaProbeStatsAvgOnewayP2RDelay P2R-AVG-OWDELAY Probe to Reflector Average Oneway Delay. The average 0
one-way source to destination delay (in µsec) across all
packets received in the current interval.
esaProbeStatsAvgAbsP2RJitter P2R-AVGABSJITTER Probe to Reflector Average Absolute Jitter (µsec). 0
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsY1731P2RFrames P2R-DATA-FRAMES1 This attribute is only applicable to Y.1731 probes. This is 0
the number of data frames counted by the Source MEP
(Probe) that are transmitted towards the Destination
MEP (Reflector). Based on the configuration the MEP
counts the data frames with:
1 The P2R-Data Frames counter stops counting in case the Link is lost, and resumes when the Link is restored.
2 There are several Performance Monitoring data types which appear for all probes but only valid to layer-three probes, namely, P2R-Err-Frames, R2P-Err-Frames, Seq-
Gaps and [Link] related statistics must be ignored for layer-two (Y.1731) probes.
3 There are several Performance Monitoring data types which appear for all probes but only valid to layer-three probes, namely, P2R-Err-Frames, R2P-Err-Frames, Seq-
Gaps and [Link] related statistics must be ignored for layer-two (Y.1731) probes.
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsP2RPkts P2R-FRAMES1 Probe to Reflector Packets. The total number of Trans- 0
mitted Packets in the current interval. In the case of
Y.1731 probes, this reflects the number of DMRs (Delay
Measurement Replies) received and this is always be
the same as the esaProbeStatsR2PPkts.
esaProbeStatsP2RLostPkts P2R-LOST-FRAMES The number of Lost Packets from probe to reflector in 0
the current interval. For Y.1731 probes, these are the
actual data frames lost.
f3EsaProbeStatsSoamPmExtMaxP2RFlr P2R-MAX-FLR Probe to Reflector Max FLR (m%) 0
esaProbeStatsMaxOnewayP2RDelay P2R-MAX-OWDELAY Probe to Reflector Maximum Oneway Delay. The max- 0
imum one-way source to destination delay (in µsec)
across all packets received in the current interval.
esaProbeStatsMaxAbsP2RJitter P2R-MAXABSJITTER Probe to Reflector Maximum Absolute Jitter (µsec). 0
esaProbeStatsMaxNegP2RJitter P2R-MAXNEGJITTER Probe to Reflector Maximum Negative Jitters. The max- 0
imum negative one-way jitter from source to destination
in the current interval.
esaProbeStatsMaxPosP2RJitter P2R-MAXPOSJITTER Probe to Reflector Maximum Positive Jitters. The max- 0
imum positive one-way jitter from source to destination
in the current interval.
f3EsaProbeStatsSoamPmExtMinP2RFlr P2R-MIN-FLR Probe to Reflector Min FLR (m%) 0
esaProbeStatsMinOnewayP2RDelay P2R-MIN-OWDELAY Probe to Reflector Minimum Oneway Delay. The min- 0
imum one-way source to destination delay (in µsec)
across all packets received in the current interval.
1 The P2R-Frames counter stops counting in case the Link is lost, and resumes when the Link is restored.
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsMinAbsP2RJitter P2R-MINABSJITTER Probe to Reflector Minimum Absolute Jitter (µsec). 0
esaProbeStatsMinNegP2RJitter P2R-MINNEGJITTER Probe to Reflector Minimum Negative Jitters. The min- 0
imum negative one-way jitter from source to destination
in the current interval.
esaProbeStatsMinPosP2RJitter P2R-MINPOSJITTER Probe to Reflector Minimum Positive Jitters. The min- 0
imum positive one-way jitter from source to destination
in the current interval.
esaProbeStatsY1731P2RNegLossOccurrences P2R-NEG-LOSSES This attribute is only applicable to Y.1731 probes. This is 0
the number of occurrences of negative frame loss from
Source MEP (Probe) to Destination MEP (Reflector). If
these counts are non-zero, then there can be some kind
of provisioning mismatch between the Probe MEP and
Reflector MEP. Here are some scenarios where this can
happen:
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsNumNegP2RJitter P2R-NUMNEGJITTER Probe to Reflector Number of Negative Jitters. The total 0
number of negative one-way jitters from source to des-
tination in the current interval.
esaProbeStatsNumPosP2RJitter P2R-NUMPOSJITTER Probe to Reflector Number of Positive Jitters. The total 0
number of positive one-way jitters from source to des-
tination in the current interval.
f3EsaProbeStatsSoamPmExtP2rSeverelyErroredDeltaTs P2R-SE-DELTA-TS Probe to Reflector Severely Errored Delta TS 0
esaProbeStatsSumOnewayP2RDelay P2R-SUM-OWDELAY Probe to Reflector Sum of Oneway Delays. The total 0
sum of one-way delay from source to destination in the
current interval.
esaProbeStatsSumOfSqOnewayP2RDelay P2R-SUM-SQ- Probe to Reflector Sum of Square of Oneway Delays. 0
OWDELAY The sum of square of one-way delay from source to des-
tination in the current interval.
esaProbeStatsSumAbsP2RJitter P2R-SUMABSJITTER Probe to Reflector Sum of Absolute Jitter (µsec). 0
esaProbeStatsSumNegP2RJitter P2R-SUMNEGJITTER Probe to Reflector Sum of Negative Jitters. The total 0
sum of negative one-way jitters from source to des-
tination in the current interval.
esaProbeStatsSumPosP2RJitter P2R-SUMPOSJITTER Probe to Reflector Sum of Positive Jitters. The total sum 0
of positive one-way jitters from source to destination in
the current interval.
esaProbeStatsSumOfSqAbsP2RJitter P2R- Probe to Reflector Sum of Square of Absolute Jitter 0
SUMSQABSJITTER (µsec).
esaProbeStatsSumOfSqNegP2RJitter P2R- Probe to Reflector Sum of Square of Negative Jitters. 0
SUMSQNEGJITTER The sum of square of negative one-way jitters from
source to destination in the current interval.
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsSumOfSqPosP2RJitter P2R- Probe to Reflector Sum of Square of Positive Jitters. 0
SUMSQPOSJITTER The sum of square of positive one-way jitters from
source to destination in the current interval.
esaProbeStatsP2RSyncErrs P2R-SYNC-ERRS The number of (time) Synchronization Errors from probe 0
to reflector in the current interval.
f3EsaProbeStatsSoamPmExtP2rUnavailableDeltaTs P2R-UNAVAIL- Probe to Reflector Unavailable Delta TS (µsec) 0
DELTA-TS
f3EsaProbeStatsSoamPmExtP2rUnavailableTime P2R-UNAVAIL-TIME Probe to Reflector Unavailable Time (µsec) 0
f3EsaProbeStatsSoamPmExtR2pAvailableDeltaTs R2P-AVAIL-DELTA-TS Reflector to Probe Available Delta TS (µsec) 0
f3EsaProbeStatsSoamPmExtR2PAvailableTime R2P-AVAIL-TIME Reflector to Probe Available Time (µsec) 0
f3EsaProbeStatsSoamPmExtAvgR2PFlr R2P-AVG-FLR Reflector to Probe Average FLR (m%) 0
esaProbeStatsAvgOnewayR2PDelay R2P-AVG-OWDELAY Reflector to Probe Average Oneway Delay. The average 0
one-way destination to source delay (in µsec) across all
packets received in the current interval.
esaProbeStatsAvgAbsR2PJitter R2P-AVGABSJITTER Reflector to Probe Average Absolute Jitter (µsec). 0
esaProbeStatsY1731R2PFrames R2P-DATA-FRAMES This attribute is only applicable to Y.1731 probes. This is 0
the number of data frames counted by the Destination
MEP (Reflector) that are transmitted towards the Source
MEP (Probe). Based on the configuration the MEP
counts the data frames with:
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsR2PErredPkts R2P-ERR-FRAMES1 Reflector to Probe Errored Packets. The total number of 0
Received Packets in the current interval, which had
errors such as length of received packet is less than the
protocol header length, packet was received after it was
marked as lost (i.e., beyond timeout). NOTE: This is not
applicable for Y.1731 probes.
esaProbeStatsR2PPkts R2P-FRAMES Reflector to Probe Packets. The total number of 0
Received Packets in the current interval. In the case of
Y.1731 probes, this reflects the number of DMRs (Delay
Measurement Replies) received and this is always be
the same as the esaProbeStatsP2RPkts.
esaProbeStatsR2PLostPkts R2P-LOST-FRAMES Reflector to Probe Lost Packets. The number of Lost 0
Packets from reflector to probe in the current interval.
For Y.1731 probes, these are the actual data frames
lost.
f3EsaProbeStatsSoamPmExtMaxR2PFlr R2P-MAX-FLR Reflector to Probe Max FLR (m%) 0
esaProbeStatsMaxOnewayR2PDelay R2P-MAX-OWDELAY Reflector to Probe Maximum Oneway Delay. The max- 0
imum one-way destination to source delay (in µsec)
across all packets received in the current interval.
esaProbeStatsMaxAbsR2PJitter R2P-MAXABSJITTER Reflector to Probe Maximum Absolute Jitter (µsec). 0
esaProbeStatsMaxNegR2PJitter R2P-MAXNEGJITTER Reflector to Probe Maximum Negative Jitters. The max- 0
imum negative one-way jitter from destination to source
in the current interval.
esaProbeStatsMaxPosR2PJitter R2P-MAXPOSJITTER Reflector to Probe Maximum Positive Jitters. The max- 0
imum positive one-way jitter from destination to source
in the current interval.
f3EsaProbeStatsSoamPmExtMinR2PFlr R2P-MIN-FLR Reflector to Probe Min FLR (m%) 0
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsMinOnewayR2PDelay R2P-MIN-OWDELAY Reflector to Probe Minimum Oneway Delay. The min- 0
imum one-way destination to source delay (in µsec)
across all packets received in the current interval.
esaProbeStatsMinAbsR2PJitter R2P-MINABSJITTER Reflector to Probe Minimum Absolute Jitter (µsec). 0
esaProbeStatsMinNegR2PJitter R2P-MINNEGJITTER Reflector to Probe Minimum Negative Jitters. The min- 0
imum negative one-way jitter from destination to source
in the current interval.
esaProbeStatsMinPosR2PJitter R2P-MINPOSJITTER Reflector to Probe Minimum Positive Jitters. The min- 0
imum positive one-way jitter from destination to source
in the current interval.
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsY1731R2PNegLossOccurrences R2P-NEG-LOSSES This attribute is only applicable to Y.1731 probes. This is 0
the number of occurrences of negative frame loss from
to Destination MEP (Reflector) to Source MEP (Probe).
If these counts are non-zero, then there can be some
kind of provisioning mismatch between the Probe MEP
and Reflector MEP. Here are some scenarios where this
can happen:
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
esaProbeStatsSumOnewayR2PDelay R2P-SUM-OWDELAY Reflector to Probe Sum of Oneway Delay. The total sum 0
of one-way delay from destination to source in the cur-
rent interval.
esaProbeStatsSumOfSqOnewayR2PDelay R2P-SUM-SQ- Reflector to Probe Sum of Square of Oneway Delay. 0
OWDELAY The sum of square of one-way delay from destination to
source in the current interval.
esaProbeStatsSumAbsR2PJitter R2P-SUMABSJITTER Reflector to Probe Sum of Absolute Jitter (µsec). 0
esaProbeStatsSumNegR2PJitter R2P-SUMNEGJITTER Reflector to Probe Sum of Negative Jitters. The total 0
sum of negative one-way jitters from destination to
source in the current interval.
esaProbeStatsSumPosR2PJitter R2P-SUMPOSJITTER Reflector to Probe Sum of Positive Jitters. The total sum 0
of positive one-way jitters from destination to source in
the current interval.
esaProbeStatsSumOfSqAbsR2PJitter R2P- Reflector to Probe Sum of Square of Absolute Jitter 0
SUMSQABSJITTER (µsec).
esaProbeStatsSumOfSqNegR2PJitter R2P- Reflector to Probe Sum of Square of Negative Jitters. 0
SUMSQNEGJITTER The sum of square of negative one-way jitters from des-
tination to source in the current interval.
esaProbeStatsSumOfSqPosR2PJitter R2P- Reflector to Probe Sum of Square of Positive Jitters. 0
SUMSQPOSJITTER The sum of square of positive one-way jitters from des-
tination to source in the current interval.
esaProbeStatsR2PSyncErrs R2P-SYNC-ERRS Reflector to Probe Sync Errors. The number of (time) 0
Synchronization Errors from reflector to probe in the cur-
rent interval.
f3EsaProbeStatsSoamPmExtR2pUnavailableDeltaTs R2P-UNAVAIL- Reflector to Probe Unavailable Delta TS (µsec) 0
DELTA-TS
Table 112: ESA Probe Monitored Types and Default TCA Settings
Default
SNMP statsEntry Monitored Type Definition
Threshold
f3EsaProbeStatsSoamPmExtR2PUnavailableTime R2P-UNAVAIL-TIME Reflector to Probe Unavailable Time (µsec) 0
esaProbeStatsSeqGaps SEQ-GAPS1 The total number of sequence gaps across all packets 0
received in the current interval. If (Received Sequence
Number) is greater than or equal to (Last Received
Sequence Number + 2)) it is termed as a sequence gap.
NOTE: This is not applicable for Y.1731 probes.
f3EsaProbeStatsSoamPmExtSumAbsRTJitter SUM-ABSRTJITTER Sum of Absolute Round Trip Jitter (µsec) 0
f3EsaProbeStatsSoamPmExtSumP2RFDR SUM-P2R-FDR Sum of Probe to Reflector Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtSumR2PFDR SUM-R2P-FDR Sum of Reflector to Probe Frame Delay Range (µsec) 0
f3EsaProbeStatsSoamPmExtSumRTFDR SUM-RT-FDR Sum of Squares of Round Trip Delays 0
esaProbeStatsSumRoundTripDelay SUM-RTDELAY The total sum of round trip delay (in milliseconds) in the 0
current interval. The reflector's processing time is
excluded from the value.
esaProbeStatsSumOfSqRoundTripDelay SUM-SQ-RTDELAY The sum of square of round trip delays in the current inter- 0
val.
f3EsaProbeStatsSoamPmExtSumOfSqAbsRTJitter SUMOFSQ- Sum of Squares of Absolute Round Trip Jitter (µsec²) 0
ABSRTJITTER
f3EsaProbeStatsSoamPmExtSumOfSqP2RFDR SUMOFSQ-P2R-FDR Sum of Squares of Probe to Reflector Frame Delay 0
Range (µsec²)
f3EsaProbeStatsSoamPmExtSumOfSqR2PFDR SUMOFSQ-R2P-FDR Sum of Squares of Reflector to Probe Frame Delay 0
Range (µsec²)
f3EsaProbeStatsSoamPmExtSumOfSqRTFDR SUMOFSQ-RT-FDR Sum of Squares Round Trip Frame Delay Range (µsec²) 0
Table 113: GRE IP Interface Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3GreIpInterfaceStats FragFramesRx Rx Fragment Frames Receive Near End 0 0
FragmentsReceivedFrames
f3GreIpInterfaceStats FragBytesRx Rx Fragment Bytes Receive Near End 0 0
FragmentsReceivedBytes
f3GreIpInterfaceStats FragFramesTx Tx Fragment Frames Transmit Near End 0 0
FragmentsTransmitsFrames
f3GreIpInterfaceStats FragBytesTx Tx Fragment Bytes Transmit Near End 0 0
FragmentsTransmitsBytes
f3GreIpInterfaceStats FragFramesDrop Fragment Frames Drop Receive Near End 0 0
FragmentsDroppedFrames
f3GreIpInterfaceStats FragBytesDrop Fragment Bytes Drop Receive Near End 0 0
FragmentsDroppedBytes
f3GreIpInterfaceStats PktReassembledFrames Packet Reassembled Receive Near End 0 0
PacketsReassembledFrames Frames
f3GreIpInterfaceStats PktReassembledBytes Packet Reassembled Receive Near End 0 0
PacketsReassembledBytes Bytes
f3GreIpInterfaceStats PreFragFramesTx Pre Tx Fragment Transmit Near End 0 0
PreFragmentsTransmitsFrames Frames
f3GreIpInterfaceStats PreFragBytesTx Pre Tx Fragment Bytes Transmit Near End 0 0
PreFragmentsTransmitsBytes
Table 114: GRE Tunnel Monitored Types and Default TCA Settings
Monitored
SNMP statsEntry Definition Direction Location 15 Min./ 5Min. 1 Day
Type
f3GreTunnelStats TTLD TTL Equal 0 Receive Near End 0 0
TtlEqual0Drop Drop
f3GreTunnelStatsDest DUD Dest Transmit Near End 0 0
UnreachableDrop Unreachable
Drop
f3GreTunnelStats DIMD Dest IP Receive Near End 0 0
DestIpMismatchDrop Mismatch
Drop
f3GreTunnelStats GVMD GRE Receive Near End 0 0
GreVerMismatchDrop Version
Mismatch
Drop
Table 115: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpAcc1PortFlowPointStatsAnnouncesRx ANNOUNCESRX Number of PTP Announce mes- Receive Near End 0 0
sages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsAnnouncesTx ANNOUNCESTX Number of Announce Mes- Transmit Near End 0 0
sages transmitted on the PTP
Flow Point. This object is applic-
able for transparent clocks.
f3PtpAccPortFlowPointStatsDelayReqsRx DELAYREQSRX Number of Delay Request Mes- Receive Near End 0 0
sages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsDelayReqsTx DELAYREQSTX Number of Delay Request Mes- Transmit Near End 0 0
sages transmitted on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsDelayRspsRx DELAYRSPSRX Number of Delay Response Receive Near End 0 0
Messages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsDelayRspsTx DELAYRSPSTX Number of Delay Response Transmit Near End 0 0
Messages transmitted on the
PTP Flow Point.
1The “Acc” in all the SNMP StatsEntries should be replaced by “Net” for Network Port PTP Flow Point Monitor Types.
Table 115: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpAccPortFlowPointStatsFollowupsRx FOLLOWUPSRX Number of Follow up Messages Receive Near End 0 0
received on the PTP Flow
Point.
f3PtpAccPortFlowPointStatsFollowupsTx FOLLOWUPSTX Number of Follow up Messages Transmit Near End 0 0
transmitted on the PTP Flow
Point.
f3PtpAccPortFlowPointStatsMgmtFramesRx MGMTFRAMESRX Number of PTP Management Receive Near End 0 0
Frames received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsMgmtFramesTx MGMTFRAMESTX Number of PTP Management Transmit Near End 0 0
Frames Messages transmitted
on the PTP Flow Point.
f3PtpAccPortFlowPointStatsPDelayReqsRx PDELAYREQSRX Number of Peer Delay Request Receive Near End 0 0
Messages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsPDelayReqsTx PDELAYREQSTX Number of Peer Delay Request Transmit Near End 0 0
Messages transmitted on the
PTP Flow Point.
f3PtpAccPortFlowPointStatsPDelayRspsRx PDELAYRSPSRX Number of Peer Delay Receive Near End 0 0
Response Messages received
on the PTP Flow Point.
f3PtpAccPortFlowPointStatsPDelayRspsTx PDELAYRSPSTX Number of Peer Delay Transmit Near End 0 0
Response Messages trans-
mitted on the PTP Flow Point
Table 115: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpAccPortFlowPointStatsPDelayRspFollowupsRx PDELAYRSPFOLUPSRX Number of Peer Delay Receive Near End 0 0
Response Followup Messages
received on the PTP Flow
Point.
f3PtpAccPortFlowPointStatsPDelayRspFollowupsTx PDELAYRSPFOLUPSTX Number of Peer Delay Transmit Near End 0 0
Response Followup Messages
transmitted on the PTP Flow
Point.
f3PtpAccPortFlowPointStatsPtpUnknownsRx PTPUNKNOWNSRX Number of Unknown PTP Mes- Receive Near End 0 0
sages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsPtpUnknownsTx PTPUNKNOWNSTX Number of Unknown PTP Mes- Transmit Near End 0 0
sages transmitted on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsSignalingRx SIGNALINGRX Number of PTP Signaling Mes- Receive Near End 0 0
sages received on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsSignalingTx SIGNALINGTX Number of PTP Signaling Mes- Transmit Near End 0 0
sages transmitted on the PTP
Flow Point.
f3PtpAccPortFlowPointStatsSyncsRx SYNCSRX PTP Sync Messages Received Receive Near End 0 0
f3PtpAccPortFlowPointStatsSyncsTx SYNCSTX PTP Sync Messages Trans- Transmit Near End 0 0
mitted
f3PtpAccPortFlowPointStatsAvgSyncResTime AVGSYNCRESTIME The average residence time for Receive Near End 0 0
PTP Sync messages.
Table 115: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpAccPortFlowPointStatsMinSyncResTime MINSYNCRESTIME The minimum residence time Receive Near End 0 0
for PTP Sync messages.
f3PtpAccPortFlowPointStatsAvgDelayReqResTime AVGDELAYREQRESTIME The average residence time for Receive Near End 0 0
PTP Delay Request messages.
Table 115: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpAccPortFlowPointStatsMinPDelayRspResTime MINPDELAYRSPRESTIME The minimum residence time Receive Near End 0 0
for PTP Peer Delay Response
messages.
f3PtpAccPortFlowPointStatsMaxPDelayRspResTime MAXPDELAYRSPRESTIME The maximum residence time Receive Near End 0 0
for PTP Peer Delay Response
messages.
Table 116: Master Clock Interface Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3PtpMCIStatsPtpDiscards MCI_PTPDISCARDS PTP Message Receive Near End 0 0
Discards
f3PtpMCIStatsAnnounceDeniedEvents MCI_ANNOUNCEDENEVTS Announce Ser- Receive Near End 0 0
vice Denied
Events
f3PtpMCIStatsSyncDeniedEvents MCI_SYNCDENEVTS Sync Service Receive Near End 0 0
Denied Events
f3PtpMCIStatsDelayRspDeniedEvents MCI_DELAYRESPDENEVTS Delay Response Receive Near End 0 0
Service Denied
Events
f3PtpMCIStatsAnnounceCancelledEvents MCI_ANNCANCELEVTS Announce Ser- Receive Near End 0 0
vice Canceled
Events
f3PtpMCIStatsSyncCancelledEvents MCI_SYNCCANCELLEVTS Sync Service Receive Near End 0 0
Canceled Events
f3PtpMCIStatsDelayRspCancelledEvents MCI_ Delay Response Receive Near End 0 0
DELAYRESPCANCELEVTS Service Canceled
Events
f3PtpMCIStatsDynamicSlavesLearnt MCI_ Dynamic Slaves Receive Near End 0 0
DYNSLAVESLEARNCOUNTS Learned Count
f3PtpMCIStatsDynamicSlavesDropped MCI_DYNSLAVESDROPPED Dynamic Slaves Receive Near End 0 0
Service Dropped
Table 117: PTP Remote Slave Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpRemoteSlaveStatsAnnounceMsgsGen RS_ANNOUNCEMSGSGEN Announce Mes- Transmit Near End 0 0
sages Generated
f3PtpRemoteSlaveStatsSyncMsgsGen RS_SYNCMSGSGEN Sync Messages Transmit Near End 0 0
Generated
f3PtpRemoteSlaveStatsDelayRspMsgsGen RS_DELAYRESPMSGSGEN DelayResp mes- Transmit Near End 0 0
sages generated
f3PtpRemoteSlaveStatsSignallingMsgsGen RS_SIGNALMSGSGEN Signaling Mes- Transmit Near End 0 0
sages generated
f3PtpRemoteSlaveStatsSignallingMsgsRx RS_SIGNALMSGSRX Signaling Mes- Receive Near End 0 0
sages Received
f3PtpRemoteSlaveStatsDelayReqMsgsRx RS_DELAYREQMSGSRX Delay Req Mes- Receive Near End 0 0
sages Received
f3PtpRemoteSlaveStatsDelayReqMsgsDropped RS_ Delay Req Mes- Receive Near End 0 0
DELAYREQMSGSDROPPED sages Dropped
f3PtpRemoteSlaveStatsInvalidTLVLenDiscards RS_INVTLVLENDISCARDS PTP messages Receive Near End 0 0
with invalid PTP
TLV length
f3PtpRemoteSlaveStatsInvalidTLVTypeDiscards RS_INVTLVTYPEDISCARDS PTP messages Receive Near End 0 0
with unknown
PTP TLV type
Table 117: PTP Remote Slave Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpRemoteSlaveStatsTimesAnnounceLeaseExp RS_ Times Announce Receive Near End 0 0
TIMESANNOUNCELEASEEXP lease duration
expired
f3PtpRemoteSlaveStatsTimesSyncLeaseExp RS_TIMESSYNCLEASEEXP Times Sync Receive Near End 0 0
lease duration
expired
f3PtpRemoteSlaveStatsTimesDelayRspLeaseExp RS_TIMESDELAYRESPEXP Times Delay_ Receive Near End 0 0
Resp lease dur-
ation expired
Table 118: Slave Only Ordinary Clock Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpSOOCStats MgmtMsgsDiscarded PTPMGMTMSGSD PTP Management Receive Near End
Message Discards
f3PtpSOOCStats InvalidMsgLenDiscards PTPINVMSGLEND PTP Invalid Mes- Receive Near End
sage Length Dis-
cards
f3PtpSOOCStats UnknownMasterDiscards PTPUNKMASTERD PTP Unknown Receive Near End
Master Discards
f3PtpSOOCStatsUnknownDomainDiscards PTPUNKDOMAIND PTP Unknown Receive Near End
Domain Discards
f3PtpSOOCStatsMulticastAnnounceDiscards PTPMULTIANNOUNCED PTP Multicast Receive Near End
Announce Mes-
sage Discards
f3PtpSOOCStats OutOfSeqAnnounceMsgs PTPOOSANNOUNCES PTP Out Of Receive Near End
Sequence
Announce Mes-
sages
f3PtpSOOCStats MulticastSyncDiscards PTPMULTISYNCD PTP Multicast Receive Near End
Sync Message Dis-
cards
f3PtpSOOC StatsTwoStepSyncDiscards PTPTWOSTEPSYNCD PTP Two Step Receive Near End
Sync Message Dis-
cards
Table 118: Slave Only Ordinary Clock Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpSOOCStats FollowupDiscards PTPFOLLOWUPSD PTP Follow-up Receive Near End
Message Discards
f3PtpSOOCStats DelayReqDiscards PTPDELAYREQSD PTP Delay_Req Receive Near End
Message Discards
f3PtpSOOCStats PDelayReqDiscards PTPPDELAYREQSD PTP PDelay_Req Receive Near End
Message Discards
f3PtpSOOCStats PDelayRspDiscards PTPPDELAYRSPSD PTP PDelay_Resp Receive Near End
Message Discards
f3PtpSOOCStats PDelayFollowupDiscards PTPPDELAYFOLLOWUPSD PTP PDelay Fol- Receive Near End
low-up Message
Discards
f3PtpSOOCStats InvalidTLVLenDiscards PTPINVTLVLENSD PTP Invalid TLV Receive Near End
Length Discards
f3PtpSOOCStats InvalidTLVTypeDiscards PTPINVTLVTYPESD PTP Invalid TLV Receive Near End
Type Discards
f3PtpSOOCStats AvgSyncPathDelay AVGSYNCPD Average Sync Path Receive Near End
Delay (nsec)
f3PtpSOOCStatsMinSyncPathDelay MINSYNCPD Minimum Sync Receive Near End
Path Delay (nsec)
f3PtpSOOCStats MaxSyncPathDelay MAXSYNCPD Maximum Sync Receive Near End
Path Delay (nsec)
f3PtpSOOCStats AvgSyncPDV AVGSYNCPDV Average Sync PDV Receive Near End
(nsec)
f3PtpSOOCStats MinSyncPDV MINSYNCPDV Minimum Sync Receive Near End
PDV (nsec)
Table 118: Slave Only Ordinary Clock Monitored Types and Default TCA Settings
15 Min./
SNMP statsEntry Monitored Type Definition Direction Location 1 Day
5Min.
f3PtpSOOCStats MaxSyncPDV MAXSYNCPDV Maximum Sync Receive Near End
PDV (nsec)
f3PtpSOOCStats AvgMeanPathDelay AVGMEANPATHDELAY Average Mean Path Receive Near End
Delay (nsec)
f3PtpSOOCStats MinMeanPathDelay MINMEANPATHDELAY Minimum Mean Receive Near End
Path Delay (nsec)
f3PtpSOOCStats MaxMeanPathDelay MAXMEANPATHDELAY Maximum Mean Receive Near End
Path Delay (nsec)
f3PtpSOOCStats AvgOffsetFromMaster AVGOFM Average Offset Receive Near End
from Master (nsec)
f3PtpSOOCStats MinOffsetFromMaster MINOFM Minimum Offset Receive Near End
from Master (nsec)
f3PtpSOOCStats MaxOffsetFromMaster MAXOFM Maximum Offset Receive Near End
from Master (nsec)
Table 119: PTP Clock Monitored Types and Default TCA Settings
15 Min./
Monitored Type SNMP statsEntry Definition Direction Location 1 Day
5 Min.
AVGSYNCPD f3PtpPTPClockStats Average Sync Path Receive Near End 0 0
AvgSyncPathDelay Delay (nsec)
MINSYNCPD f3PtpPTPClockStats Minimum Sync Path Receive Near End 0 0
MinSyncPathDelay Delay (nsec)
MAXSYNCPD f3PtpPTPClockStats Maximum Sync Path Receive Near End 0 0
MaxSyncPathDelay Delay (nsec)
AVGMEANPATHDELAY f3PtpPTPClockStats Average Mean Path Receive Near End 0 0
AvgMeanPathDelay Delay (nsec)
MINMEANPATHDELAY f3PtpPTPClockStats Minimum Mean Path Receive Near End 0 0
MinMeanPathDelay Delay (nsec)
MAXMEANPATHDELAY f3PtpPTPClockStats Maximum Mean Receive Near End 0 0
MaxMeanPathDelay Path Delay (nsec)
AVGOFM f3PtpPTPClockStats Average Offset From Receive Near End 0 0
AvgOffsetFromMaster Master (nsec)
MINOFM f3PtpPTPClockStats Minimum Offset Receive Near End 0 0
MinOffsetFromMaster From Master (nsec)
MAXOFM f3PtpPTPClockStats Maximum Offset Receive Near End 0 0
MaxOffsetFromMaster From Master (nsec)
Table 120: PTP Port Monitored Types and Default TCA Settings
15 Min./
Monitored Type SNMP statsEntry Definition Direction Location 1 Day
5 Min.
AVGANNOUNCERATE f3PtpPTPPortStats PTP Port Average Receive Near End 0 0
AVGANNOUNCERATE Announce Rate
AVGSYNCRATE f3PtpPTPPortStats AVGSYNCRATE PTP Port Average Receive Near End 0 0
Sync Rate
AVGDELAYREQRATE f3PtpPTPPortStats PTP Port Average Receive Near End 0 0
AVGDELAYREQRATE Delay Req Rate
AVGDELAYRESPRATE f3PtpPTPPortStats PTP Port Average Receive Near End 0 0
AVGDELAYRESPRATE Delay Resp Rate
PTPUNKDOMAIND f3PtpPTPPortStats PTP Port Mis- Receive Near End 0 0
PTPUNKDOMAIND match Domain Dis-
cards
MSGWRONGTYPE f3PtpPTPPortStatsMSGWRONGTYPE PTP Port Mes- Receive Near End 0 0
DSCRD DSCRD sage Wrong Type
Discards
PTPINVMSGLEND f3PtpPTPPortStats PTPINVMSGLEND PTP Port Mes- Receive Near End 0 0
sages Wrong
Length Discards
UNKNOWNMASTER f3PtpPTPPortStats PTP Port Receive Near End 0 0
DISCARDS UNKNOWNMASTER DISCARDS Unknown Master
Discards
Table 120: PTP Port Monitored Types and Default TCA Settings
15 Min./
Monitored Type SNMP statsEntry Definition Direction Location 1 Day
5 Min.
MESSAGEMISC f3PtpPTPPortStats MESSAGEMISC Packets Dis- Receive Near End 0 0
DISCARDS DISCARDS carded By Mis-
cellaneous
Reason
Table 122: Layer-three Flow Point Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3L3FlowPointStatsFMG FMG Frames Marked Receive Near End 0 0
Green
f3L3FlowPointStatsFMY FMY Frame Makeed Yel- Receive Near End 0 0
low
f3L3FlowPointStatsFMRD FTD Frames Tail Dropped Transmit Near End 0 0
f3L3FlowPointStatsFTD FMRD Frames Marked Red Receive Near End 0 0
f3L3FlowPointStatsFragmentedDropAcl FRD Fragments Dropped Receive Near End 0 0
f3L3FlowPointStatsAclRuleDrop FDACL Frames Dropped by Receive Near End 0 0
ACL Rule
f3L3FlowPointStatsTtlEqual1Drop TTLD Packets Dropped, Receive Near End 0 0
Invalid TTL
f3L3FlowPointStatsFrameTx FrameTx Frames Tx Transmit Near End 0 0
f3L3FlowPointStatsFrameRx FrameRx Frames Rx Receive Near End 0 0
f3L3FlowPointStatsNoRouteDrop NoRouteDrop Packets Dropped, no Receive Near End 0 0
Active Route
Table 123: Traffic IP Interface Monitored Types and Default TCA Settings
Monitored
SNMP statsEntry Definition Direction Location 15 Min./ 5Min. 1 Day
Type
f3L3TrafficIpInterfaceStatsDhcpTx DHCPTX DHCP Tx Transmit Near End 0 0
f3L3TrafficIpInterfaceStatsDhcpRx DHCPRX DHCP Rx Receive Near End 0 0
f3L3TrafficIpInterfaceStatsIcmpTx ICMPTX ICMP Tx Transmit Near End 0 0
f3L3TrafficIpInterfaceStatsIcmpRx ICMPRX ICMP Rx Receive Near End 0 0
f3L3TrafficIpInterfaceStatsArpReqTx ARQTX ARP Request Tx Transmit Near End 0 0
f3L3TrafficIpInterfaceStatsArpReqRx ARQRX ARP Request Rx Receive Near End 0 0
f3L3TrafficIpInterfaceStatsArpReplyTx ARPTX ARP Reply Tx Transmit Near End 0 0
f3L3TrafficIpInterfaceStatsArpReplyRx ARPRX ARP Relay Rx Receive Near End 0 0
Table 124: layer-two and layer-three Traffic ACL Rule Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3L3AclRuleStatsRuleMatch RuleMatch ACL Rule Match Receive Near End 0 0
Also see layer-two and layer-three Traffic ACL Rule stats definitions in F3L3MIB
Table 125: Layer-two A2N ACL Rule Monitored Types and Default TCA Settings
1
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min.
Day
f3L2A2NAclRuleStatsRuleMatch RuleMatch ACL Rule Match Receive Near End 0 0
Also see layer-two and layer-three Traffic ACL Rule stats definitions in F3L3MIB.
Table 126: Layer-two N2A ACL Rule Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3L2N2AAclRuleStatsRuleMatch RuleMatch ACL Rule Match Receive Near End 0 0
Also see layer-two and layer-three Mirror ACL Rule stats definitions in f3PortMirrorMIB.
Table 127: Layer-two N2A ACL Rule Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3PortMirrorAclRuleStatsRuleMatch RuleMatch ACL Rule Match Receive Near End 0 0
Table 128: Secure Flow Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3ConnectGuardFlowStats TxUntaggedPkt OUTPKTSUNTAGGED Out Packets Transmit Near End 0 0
Untagged
f3ConnectGuardFlowStats TxTooLongPkts OUTPKTSTOOLONG Out Packets Too Transmit Near End 0 0
Long
f3ConnectGuardFlowStats RxUntaggedPkts INPKTSUNTAGGED In Packets Receive Near End 0 0
Untagged
f3ConnectGuardFlowStats RxNotagPkts INPKTSNOTAG In Packets No Tag Receive Near End 0 0
f3ConnectGuardFlowStats RxBadtagPkts INPKTSBADTAG In Packets Bad Receive Near End 0 0
Tag
f3ConnectGuardFlowStats INPKTSUNKNOWNSCI In Packets Receive Near End 0 0
RxUnknownSCIPkts Unknown SCI
f3ConnectGuardFlow StatsRxNoSCIPkts INPKTSNOSCI In Packets No SCI Receive Near End 0 0
f3ConnectGuardFlow StatsRxNoSCIPkts INPKTSOVERRUN In Packets Over Receive Near End 0 0
Run
Table 129: TX Secure Channel Monitored Types and Default TCA Settings
Monitored Type SNMP statsEntry Definition Direction Location 15 Min./ 5Min. 1 Day
f3ConnectGuardTxSCStats OUTPKTSPROTECTED Out Packets Pro- Transmit Near End 0 0
TxProtectedPkts tected
f3ConnectGuardTxSCStats OUTPKTSENCRYPTED Out Packets Encryp- Transmit Near End 0 0
TxEncryptedPkts ted
f3ConnectGuardTxSCStats OUTOCTETSPROTECTED Out Octets Pro- Transmit Near End 0 0
TxOctetsProtected tected
f3ConnectGuardTxSCStats OUTOCTETSENCRYPTED Out Octets Encryp- Transmit Near End 0 0
TxOctetsEncrypted ted
Table 130: RX Secure Channel Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3ConnectGuardRxSCStats INPKTSUNUSEDSA In Packets Receive Near End 0 0
RxUnusedSAPkts Unused SA
f3ConnectGuardRxSCStats INPKTSNOUSINGSA In Packets No Receive Near End 0 0
RxNoUsingSAPkts Using SA
f3ConnectGuardRxSCStats RxLatePkts INPKTSLATE In Packets Late Receive Near End 0 0
f3ConnectGuardRxSCStats RxNotVal- INPKTSNOTVALID In Packets Not Receive Near End 0 0
idPkts Valid
f3ConnectGuardRxSCStats RxIn- INPKTSINVALID In Packets Invalid Receive Near End 0 0
validPkts
f3ConnectGuardRxSCStats INPKTSDELAYED In Packets Receive Near End 0 0
RxDelayedPkts Delayed
f3ConnectGuardRxSCStats INPKTSUNCHECKED In Packets Receive Near End 0 0
RxUncheckedPkts Unchecked
f3ConnectGuardRxSCStats RxOKPkts INPKTSOK In Packets OK Receive Near End 0 0
f3ConnectGuardRxSCStats RxOc- INOCTETSVALIDATED In Octets Val- Receive Near End 0 0
tetsValidated idated
f3ConnectGuardRxSCStats RxOc- INOCTETSDECRYPTED In Octets Decryp- Receive Near End 0 0
tetsDecrypted ted
Table 131: TX Secure Association Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3ConnectGuardTxSAStats OutPktsProtected Out Packets Pro- Transmit Near End N/A N/A
ProtectedPkts. tected
f3ConnectGuardTxSAStats OutPktsEncrypted Out Packets Encryp- Transmit Near End N/A N/A
EncryptedPkts. ted
Table 132: RX Secure Association Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3ConnectGuardRxSAStats InPktsUnusedSA In Packets Unused Receive Near End N/A N/A
UnusedSAPkts SA
f3ConnectGuardRxSAStats InPktsNotUsingSA In Packets Not Using Receive Near End N/A N/A
NoUsingSAPkts SA
f3ConnectGuardRxSAStats InPktsNotValid In Packets Not Valid Receive Near End N/A N/A
NotValidPkts
f3ConnectGuardRxSAStats InPktsInvalid In Packets Invalid Receive Near End N/A N/A
InvalidPkts
f3ConnectGuardRxSAStats InPktsOK In Packets OK Receive Near End N/A N/A
OKPkts
Table 133: TWAMP Session Sender Monitored Types and Default TCA Settings
Performance Default
SNMP statsEntry Definition
Parameter Threshold
f3TwampStatsAvgOneWayR2SAbsPDV AVG-ONEWAY- Average One Way 0
R2S-ABSPDV Reflector to Session
Sender Absolute Packet
Delay Variation
f3TwampStatsAvgOneWayR2SNegPDV AVG-ONEWAY- Average One Way 0
R2S-NEGPDV Reflector to Session
Sender Negative Packet
Delay Variation
f3TwampStatsAvgOneWayR2SPosPDV AVG-ONEWAY- Average One Way 0
R2S-POSPDV Reflector to Session
Sender Positive Packet
Delay Variation
f3TwampStatsAvgOneWayR2SPD AVG-ONEWAY- Average One Way 0
R2SPD Reflector to Session
Sender Packet Delay
f3TwampStatsAvgOneWayS2RAbsPDV AVG-ONEWAY- Average One Way Ses- 0
S2R-ABSPDV sion Sender to Reflector
Absolute Packet Delay
Variation
f3TwampStatsAvgOneWayS2RNegPDV AVG-ONEWAY- Average One Way Ses- 0
S2R-NEGPDV sion Sender to Reflector
Negative Packet Delay
Variation
f3TwampStatsAvgOneWayS2RPosPDV AVG-ONEWAY- Average One Way Ses- 0
S2R-POSPDV sion Sender to Reflector
Positive Packet Delay
Variation
f3TwampStatsAvgOneWayS2RPD AVG-ONEWAY- Average One Way Ses- 0
S2RPD sion Sender to Reflector
Packet Delay
f3TwampStatsAvgTwoWayPD AVG-TWOWAY- Average Two Way 0
PD Packet Delay
Table 133: TWAMP Session Sender Monitored Types and Default TCA Settings
Performance Default
SNMP statsEntry Definition
Parameter Threshold
f3TwampStatsMaxOneWayR2SAbsPDV MAX-ONEWAY- Maximum One Way 0
R2S-ABSPDV Reflector to Session
Sender Absolute Packet
Delay Variation
f3TwampStatsMaxOneWayR2SNegPDV MAX-ONEWAY- Maximum One Way 0
R2S-NEGPDV Reflector to Session
Sender Negative Packet
Delay Variation
f3TwampStatsMaxOneWayR2SPosPDV MAX-ONEWAY- Maximum One Way 0
R2S-POSPDV Reflector to Session
Sender Positive Packet
Delay Variation
f3TwampStatsMaxOneWayR2SPD MAX-ONEWAY- Maximum One Way 0
R2SPD Reflector to Session
Sender Packet Delay
f3TwampStatsMaxOneWayS2RAbsPDV MAX-ONEWAY- Maximum One Way Ses- 0
S2R-ABSPDV sion Sender to Reflector
Absolute Packet Delay
Variation
f3TwampStatsMaxOneWayS2RNegPDV MAX-ONEWAY- Maximum One Way Ses- 0
S2R-NEGPDV sion Sender to Reflector
Negative Packet Delay
Variation
f3TwampStatsMaxOneWayS2RPosPDV MAX-ONEWAY- Maximum One Way Ses- 0
S2R-POSPDV sion Sender to Reflector
Positive Packet Delay
Variation
f3TwampStatsMaxOneWayS2RPD MAX-ONEWAY- Maximum One Way Ses- 0
S2RPD sion Sender to Reflector
Packet Delay
f3TwampStatsMaxTwoWayPD MAX-TWOWAY- Maximum Two Way 0
PD Packet Delay
f3TwampStatsMinOneWayR2SAbsPDV MIN-ONEWAY- Minimum One Way 0
R2S-ABSPDV Reflector to Session
Sender Absolute Packet
Delay Variation
f3TwampStatsMinOneWayR2SNegPDV MIN-ONEWAY- Minimum One Way 0
R2S-NEGPDV Reflector to Session
Sender Negative Packet
Delay Variation
f3TwampStatsMinOneWayR2SPosPDV MIN-ONEWAY- Minimum One Way 0
R2S-POSPDV Reflector to Session
Sender Positive Packet
Delay Variation
Table 133: TWAMP Session Sender Monitored Types and Default TCA Settings
Performance Default
SNMP statsEntry Definition
Parameter Threshold
f3TwampStatsMinOneWayR2SPD MIN-ONEWAY- Minimum One Way 0
R2SPD Reflector to Session
Sender Packet Delay
f3TwampStatsMinOneWayS2RAbsPDV MIN-ONEWAY- Minimum One Way Ses- 0
S2R-ABSPDV sion Sender to Reflector
Absolute Packet Delay
Variation
f3TwampStatsMinOneWayS2RNegPDV MIN-ONEWAY- Minimum One Way Ses- 0
S2R-NEGPDV sion Sender to Reflector
Negative Packet Delay
Variation
f3TwampStatsMinOneWayS2RPosPDV MIN-ONEWAY- Minimum One Way Ses- 0
S2R-POSPDV sion Sender to Reflector
Positive Packet Delay
Variation
f3TwampStatsMinOneWayS2RPD MIN-ONEWAY- Minimum One Way Ses- 0
S2RPD sion Sender to Reflector
Packet Delay
f3TwampStatsMinTwoWayPD MIN-TWOWAY- Minimum Two Way 0
PD Packet Delay
f3TwampStatsNumOneWayR2SAbsPDV NUM-ONEWAY- Number of One Way 0
R2S-ABSPDV Reflector to Session
Sender Absolute Packet
Delay Variation
f3TwampStatsNumOneWayR2SNegPDV NUM-ONEWAY- Number of One Way 0
R2S-NEGPDV Reflector to Session
Sender Negative Packet
Delay Variation
f3TwampStatsNumOneWayR2SPosPDV NUM-ONEWAY- Number of One Way 0
R2S-POSPDV Reflector to Session
Sender Positive Packet
Delay Variation
f3TwampStatsNumOneWayS2RAbsPDV NUM-ONEWAY- Number of One Way Ses- 0
S2R-ABSPDV sion Sender to Reflector
Absolute Packet Delay
Variation
f3TwampStatsNumOneWayS2RNegPDV NUM-ONEWAY- Number of One Way Ses- 0
S2R-NEGPDV sion Sender to Reflector
Negative Packet Delay
Variation
f3TwampStatsNumOneWayS2RPosPDV NUM-ONEWAY- Number of One Way Ses- 0
S2R-POSPDV sion Sender to Reflector
Positive Packet Delay
Variation
Table 133: TWAMP Session Sender Monitored Types and Default TCA Settings
Performance Default
SNMP statsEntry Definition
Parameter Threshold
f3TwampStatsOutOfSeqErrs OUTOFSEQ- Out of Sequence Errors 0
ERRS
f3TwampStatsR2SLostPkts R2S-LOST-PKTS Reflector to Session 0
Sender Lost Packets
f3TwampStatsR2SPkts R2S-PKTS Reflector to Session 0
Sender Packets
f3TwampStatsR2SSyncErrs R2S-SYNC- Reflector to Session 0
ERRORS Sender Sync Errors
f3TwampStatsS2RLostPkts S2R-LOST-PKTS Session Sender to 0
Reflector Lost Packets
f3TwampStatsS2RPkts S2R-PKTS Session Sender to 0
Reflector Packets
f3TwampStatsS2RSyncErrs S2R-SYNC- Session Sender to 0
ERRORS Reflector Sync Errors
f3TwampStatsSeqGaps SEQ-GAPS Number of Gaps in 0
Sequence Numbers
f3TwampStatsSumOneWayR2SAbsPDV SUM-ONEWAY- Sum of One Way 0
R2S-ABSPDV Reflector to Session
Sender Absolute Packet
Delay Variation
f3TwampStatsSumOneWayR2SNegPDV SUM-ONEWAY- Sum of One Way 0
R2S-NEGPDV Reflector to Session
Sender Negative Packet
Delay Variation
f3TwampStatsSumOneWayR2SPosPDV SUM-ONEWAY- Sum of One Way 0
R2S-POSPDV Reflector to Session
Sender Positive Packet
Delay Variation
f3TwampStatsSumOneWayR2SPD SUM-ONEWAY- Sum of One Way 0
R2SPD Reflector to Session
Sender Packet Delay
f3TwampStatsSumOneWayS2RAbsPDV SUM-ONEWAY- Sum of One Way Ses- 0
S2R-ABSPDV sion Sender to Reflector
Absolute Packet Delay
Variation
f3TwampStatsSumOneWayS2RNegPDV SUM-ONEWAY- Sum of One Way Ses- 0
S2R-NEGPDV sion Sender to Reflector
Negative Packet Delay
Variation
f3TwampStatsSumOneWayS2RPosPDV SUM-ONEWAY- Sum of One Way Ses- 0
S2R-POSPDV sion Sender to Reflector
Positive Packet Delay
Variation
Table 133: TWAMP Session Sender Monitored Types and Default TCA Settings
Performance Default
SNMP statsEntry Definition
Parameter Threshold
f3TwampStatsSumOneWayS2RPD SUM-ONEWAY- Sum of One Way Ses- 0
S2RPD sion Sender to Reflector
Packet Delay
f3TwampStatsSumOfSqOneWayR2SAbsPDV SUM-SQ- Sum of Squares One 0
ONEWAY-R2S- Way Reflector to Ses-
ABSPDV sion Sender Absolute
Packet Delay Variation
f3TwampStatsSumOfSqOneWayR2SNegPDV SUM-SQ- Sum of Squares of One 0
ONEWAY-R2S- Way Reflector to Ses-
NEGPDV sion Sender Negative
Packet Delay Variation
f3TwampStatsSumOfSqOneWayR2SPosPDV SUM-SQ- Sum of Squares of One 0
ONEWAY-R2S- Way Reflector to Ses-
POSPDV sion Sender Positive
Packet Delay Variation
f3TwampStatsSumOfSqOneWayR2SPD SUM-SQ- Sum of Squares of One 0
ONEWAY-R2SPD Way Reflector to Ses-
sion Sender Packet
Delay
f3TwampStatsSumOfSqOneWayS2RAbsPDV SUM-SQ- Sum of Squares of One 0
ONEWAY-S2R- Way Session Sender to
ABSPDV Reflector Absolute
Packet Delay Variation
f3TwampStatsSumOfSqOneWayS2RNegPDV SUM-SQ- Sum of Squares of One 0
ONEWAY-S2R- Way Session Sender to
NEGPDV Reflector Negative
Packet Delay Variation
f3TwampStatsSumOfSqOneWayS2RPosPDV SUM-SQ- Sum of Squares of One 0
ONEWAY-S2R- Way Session Sender to
POSPDV Reflector Positive
Packet Delay Variation
f3TwampStatsSumOfSqOneWayS2RPD SUM-SQ- Sum of Squares of One 0
ONEWAY-S2RPD Way Session Sender to
Reflector Packet Delay
f3TwampStatsSumOfSqTwoWayPD SUM-SQ- Sum of Squares of Two 0
TWOWAY-PD Way Packet Delay
f3TwampStatsSumTwoWayPD SUM-TWOWAY- Sum of Two Way Packet 0
PD Delay
Table 134: VXLAN Segment Monitored Types and Default TCA Settings
SNMP statsEntry Monitored Type Definition Direction Location 15 Min./ 5Min. 1 Day
f3VXLANSegmentStats
TTLD TTL Equal 0 Drop Receive Near End 1 0
TtlEqual0Drop
f3VXLANSegmentStats
NRD No Route Drop Transmit Near End 2 0
NoRouteDrop
f3VXLANSegmentStats
TD Tagged Drop Receive Near End 3 0
TaggedDrop
f3VXLANSegmentStats
DIMD Destination IP Mismatch Drop Receive Near End 4 0
DestIpMismatchDrop
f3VXLANSegmentStats
FD Fragmented Drop Receive Near End 5 0
FragmentedDrop
f3VXLANSegmentStats
DMAC2DIPTFD DMAC2DIP Table Full Drop Receive Near End 6 0
Dmac2DipTableFullDrop
Action l When the action is Accept, traffic meets criteria in the ACL
rule is passed through.
l When the action is Deny, traffic meets criteria in the ACL Deny
rule is dropped.
Whether to enable filtering frames by its Outer VLAN Drop Eli- checkbox
DEI Control
gibility Indicator (DEI) attribute. cleared
DEI The Drop Eligible Indicator in the Outer VLAN. 0, 1
Inner VLAN Tag
checkbox
VLAN ID Control Whether to enable filtering frames by its Inner VLAN VID
cleared
The low end of the VID segment for filtering. This parameter is
VLAN ID Low Limit 0-4095
entered only when Inner VLAN VID filtering is enabled.
The high end of the VID segment for filtering. This parameter is
VLAN ID High Limit 0-4095
entered only when Inner VLAN VID filtering is enabled.
checkbox
PCP Control Whether to enable filtering frames by its Inner VLAN PCP
cleared
The low end of the PCP segment for filtering. This parameter is
PCP Low Limit 0-7
entered only when Inner VLAN PCP filtering is enabled.
The high end of the PCP segment for filtering. This parameter is
PCP High Limit 0-7
entered only when Inner VLAN PCP filtering is enabled.
See Table 136 and Table 137 for ESA Reflector and Probe configuration settings,
respectively. See Table 138 for ESA Schedule configuration settings. Default settings
are identified in bold.
Identification
Reflector Index An Identifier value used to uniquely identify this ESA
1-255
(Create Reflector only) Reflector.
Reflector identifier (1 to 15 characters - no spaces, and
Reflector ID must contain only alpha-numeric characters). This is a 1 to 15 characters
(Create Reflector only) user specified unique identifier associated with a (blank)
Reflector and must be provided.
Reflector Identification
Source Port Reflector source port. Points to the Port to which the
(drop-down list of
ESA Reflector is attached, i.e., on which the service to
(Create Reflector only) available ports)
be monitored resides.
IP Information
Reflector IP address. This is a user specified IP
Reflector IP Address address, uniquely associated with an ESA Reflector
instance. The IP address must not overlap with any [Link]
(Create Reflector only) non-ESA related subnets provisioned within the
GE11xPro. (See Note.)
Mask
Reflector Subnet mask. [Link]
(Create Reflector only)
None
Priority Map Mode Priority Map Mode. TOS
DSCP
Specifies the Priority Value for ESA Reflector Priority N/A
Priority Map Mode. Only applicable if Priority Map Mode is set 0-7 (TOS)
to TOS or DSCP. 0-63 (DSCP)
Identification
Probe Index An Identifier value used to uniquely identify this ESA
1-255
(Create Probe only) Probe.
Probe identifier (1 to 15 characters - no spaces, and must
Probe Name contain only alpha-numeric characters). This is a user 1 to 15 characters
(Create Probe only) specified unique identifier associated with a Probe and (blank)
must be provided.
Enter an alias for this probe as a customized name. This 0-128 characters
Alias parameter is not mandatory in probe creation. User can
edit it after probe creation. (blank)
Probe Identification
Protocol. UDP Echo and ICMP Echo measure the round-
UDP Echo
trip delay. ICMP Timestamp measures the round-trip
delay and one-way delay as well as one-way jitter. ICMP Echo
Protocol Y.1731 links ESA to CFM MEPs for facilitating ETH-LM
Frame Loss Measurements and ETH-DM Delay Meas- ICMP Timestamp
(Create Probe only) urements, as well as ETH-SLM Frame Synthetic Loss
Measurement and Delay Measurement Message. Select- Y.1731 LM/DM
ing a Y.1731 protocol changes the create options. (See
Y.1731 only options below.) Y.1731 SLM/DMM
(drop-down list of
Source Port Probe source port. Points to the Port to which the ESA available ports)
Probe is attached, i.e., on which the service to be mon-
(Create Probe only) itored resides. ACCESS PORT-1-
1-1-3
Service End Points
Source (Probe) IP address. This is a user specified IP
address, uniquely associated with an ESA Probe
Probe IP Address instance. This is the IP address to be used in UDP Echo,
ICMP Echo or ICMP Timestamp request. The IP address [Link]
(Create Probe only)1 must not overlap with any non-ESA related subnet pro-
visioned within GE11xPro. Not available if protocol is
Y.1731.
1If the IP address assigned to the Probe collides with an IP address used by the customer traffic, all packets
destined for that IP address are routed up to the Network Processor.
1Oneway options are only available if ICMP timestamp is set for protocol type. A Probe that is assigned to an
active schedule cannot be edited.
N/A
Set the packet size (in bytes) of the Service Assurance 64-1518 (Untagged)
Packets. The L3 packet size is up to 1500 Bytes, thus, if
Packet Type is Untagged, the maximum Service Assur- 104
Packet Size{Superscript}
ance Packet size is 1518 Bytes; if Packet Type is VLAN
Tagged (one tag pushed), the maximum Service Assur- 68 - 1522 (VLAN
ance Packet size is 1522 Bytes. Tagged)
(Create Probe only) This is the amount of time between history bins. 8
History Distribution Bins Number of History Distribution Bins (up to a maximum of 1 to 32
Once a Scheduled ESA has been created, options available when entering a right click on
the ESA Entity ID in the Selection Tree are: Delete Schedule, Suspend Schedule,
Resume Schedule and Edit Schedule. To delete an activity, you must first Suspend the
activity. To edit an activity, you must ensure that the activity is in “Active” status.
Identification
Schedule Index An Identifier value used to uniquely identify this
ESA [Link] is automatically indexed, 1 - 255
(Create Schedule only) but is user editable.
Activity identifier (1 to 15 ASCII characters). This
up to 15 characters
Activity ID is a user specified unique identifier associated
(blank)
with a Probe, and is not a mandatory entry.
Schedule Parameters
Define schedule type as a one time or periodic One Shot
Schedule Type
execution. Periodic
Activate either an immediate ESA or future Now
Start Time Buttons
(scheduled) ESA. Future
Specifies the interval between subsequent runs
Periodic Interval (secs) (in seconds). This option is only available if Sched- 1 - 4,294,967,295 (sec)
ule Type of Periodic is selected.
Define the duration as continuous or a fixed time Forever
Duration Buttons (in seconds). Only applicable if Schedule Type of
One Shot is selected. Fixed
Define the duration in seconds. Valid entries are 0
through 9,999,999,999 (seconds). However, when 1 - 9,999,999,999 (sec)
Duration (secs) the entered value is equal to or larger than
4,294,967,295, the system will automatically (blank)
Entry Window
save the duration to “Forever”.
In addition to configuring CFM options, alarm attributes are editable when the CFM
application is selected (see CFM Maintenance End Point Alarms).
Configuration
System Default MD System or specified Maintenance
Level 0 to 7
Level Domain default MD level.
MIP Creation Control. If Default is None
selected, the parameters set in the
System MIP MIP Creation Con-
Default Maintenance Domain will be Default
Creation Control trol
used for MD Level, MIP Creation Con-
trol and Default Sender ID Control. Explicit
The following MEP provisioning options and rules are described for each option setting
available for:
Identification
Server MEP Index
(Create Sever MEP Index number assigned to a specific Server MEP entity. 1 to 255
Only)
Associated Port
Drop-down list of associated interfaces. LAG entities are only lis- (drop-down list of
(Create Sever MEP ted if one or more LAG groups have been provisioned. available ports)
Only)
Configuration
Enabled
AIS Generation Enable or disable generation of AIS by a Server MEP.
Disabled
AIS Client MD Level Set the client MD level of a Server MEP 0 -7
AIS Transmission Set the interval for AIS transmission. Only effective if AIS Gen- 1 Second
Interval eration is Enabled. 1 Minute
AIS Priority Set the AIS priority level. 0 -7
To edit an existing CFM VLAN Table entry, enter a right click on the Access Port entity
and select Edit VLAN Entry, then select the Edit radio button for the VLAN entity to edit,
then modify the VID entries by adding new ones and/or deleting existing ones.
To delete and VLAN entry, in the selection tree enter a right click on the Access Port
entity and selecting Delete VLAN Entry, then select the Delete radio button for the
VLAN entity to delete, then click on OK.
To remove an MD, expand the Maintenance Domain entity, enter a right click on the
desired MD and select Delete. Then select OK.
In order to delete an MD, all subordinate entities (MAs and MEPs) must first
be deleted.
See the following table for Maintenance Domain configuration settings. Default settings
are identified in bold.
Identification
1 - 64 for GE112Pro
MD Index series
Maintenance Domain identifier.
(Create MD Only) 1 - 128 for GE114Pro
series
Configuration
String
MAC - Integer
Format Type Selectable Name Entry type.
DNS Name
No Name
Maintenance Domain name identified by string (if Format Type
String is selected) or by DNS Name (if Format Type DNS
Name is selected) or by MAC address (if Format Type MAC- Text string
Integer is selected). If Format Type String or DNS Name is
MAC address or DNS
MD Name selected, ASCII characters are allowed. If Format Type MAC-
name
Integer is selected, the entry must be Hexadecimal char-
[Link] that it is not allowed to use system reserved names (blank)
(i.e. ltp, cfm, efm, elmi, erppdu, eth0, eth1,jdsu, lagpdu, lldppdu,
lo, ptpsyncjack, ptpts, sat, ssm, etc) to name CFM entities.
Level
Maintenance Domain level. 0 to 7
(Create MD Only)
MIP Creation Control. If Default is selected, the parameters set None
MIP Creation Con-
in the Default Maintenance Domain is used for MD Level, MIP Default
trol
Creation Control and Default Sender ID Control. Explicit
To edit a MANET, expand the Maintenance Domain entity, expand the Maintenance
Domain ID, enter a right click on the desired MANET and select Edit Configuration. The
Entity ID cannot be edited. To edit this parameter, the MA must be deleted and then re-
entered.
To delete a MANET, expand the Maintenance Domain entity, expand the Maintenance
Domain ID, enter a right click on the desired MANET and select Delete. (All subordinate
MACOMPs must be deleted prior to deleting the MANET.) Then select OK.
See the following table for MANET configuration settings. Default settings are identified
in bold.
Identification
MANET Index
To edit a MACOMP, expand the Maintenance Domain entity, expand the Maintenance
Domain ID and MANET entities, enter a right click on the desired MACOMP entity and
select Edit Configuration. The following parameters cannot be edited: Entity ID,
Associated Port or Primary VID. To edit these parameters, the MA must be deleted and
then re-entered with the new desired parameters.
To delete a MACOMP, expand the Maintenance Domain entity, expand the Maintenance
Domain ID and MANET entities, enter a right click on the desired MANET and select
Delete. Then select OK.
The following MA provisioning options and rules are described for each option setting
available for:
See the following table for MACOMP configuration settings. Default settings are
identified in bold.
Identification
MACOMP Index
Maintenance Association Component identifier. 1
(not editable)
Configuration
Drop-down list of associated interfaces and flows.
Component ID l LAG entities are only listed if one or more LAG groups
have been provisioned. (drop-down list of
(Create Only) available ports and
l Access Port Flow entities are only applicable when the
flows)
flows have a single Push or PushVID Tag Control
operation; A flow with no tag push or double tags push
cannot be identified as a MA Component ID.
Primary VLAN Identifier. For an Access Port Flow configured
as a MACOMP Component ID, the
Primary VID MACOMP Primary VID must be unique for the N2A mem- 0 to 4095
(Create only) bership of all Access Port Flows in the system and must be (1)
equal to the VLAN ID of the single Push/PushVID Tag for the
Access Port Flow.
MIP Creation Control. If Default is selected, the parameters None
MIP Creation Con- set in the Default Maintenance Domain will be used for MD
Level, MIP Creation Control and Default Sender ID Control. If Default
trol
MACOMP Component ID is an Access Port Flow, the MIP Explicit
Creation Control must be set to None; Otherwise, the system
will deny the MACOMP creation or editing. Defer
To remove an existing Maintenance End Point, expand the desired Access Port, Network
Port or LAG entity, enter a right click on the desired MEP and select Delete. Then select
OK. To edit an existing Maintenance End Point, select Edit Configuration.
See the following table for Maintenance Association configuration settings. Default
settings are identified in bold.
Identification
Maintenance End Point (MEP) identifier. MEP IDs are cre-
MEP Index ated when provisioning a MEP list during MA creation/edit.
Existing MEP IDs are listed in numerical order according to 1 to 8191
(Create Only) the selected MANET ID. The appropriate MANET ID must
be selected prior to selecting the MEP ID.
Maintenance Association - Network identifier associated
MANET ID with this MEP. The MANET must first be created prior to Available CFM
selecting this MANET ID. The MANET ID must be selected MANET IDs from
(Create Only) first, then the MEP Index, because it determines which option list
MEP Index is available.
State
Disabled
Administrative MEP state setting. When disabled, the MEP is inactive. IS
Management
Configuration (General)
Direction Selects the MEP direction. Only UP direction MEP is cur- Up
rently supported if the Associated Port is an Access Port
(Create Only) Flow. Down
Enable or disable Continuity Check Message (CCM) gen- Disabled
CCM Generation
eration. Enabled
VLAN Priority VLAN priority. 0 to 7
Check boxes to select triggers for Link Loss Forwarding.
AIS Defect
The check boxes are for Ethernet Alarm Indication Signal
Defect, Interface Status, Remote Defect Indication and
Interface Status
Remote MEP Continuity Check Message Interface Status.
LLF Trigger l If a Down MEP is configured on a port, it is the other end RDI
of this port's associated flow that will take LLF TX
Remote MEP CCM
action.
Failure
l If an UP MEP is configured on a port, it is this port that
will take LLF TX action. (non-selected)
VLAN Ethertype Ethertype for MEP VLAN Tag for the MEPs. 8100 (hex)
See the following table for Initiate Loop Back Message configuration settings. Default
settings are identified in bold.
The MEP must be set to the In Service State for the Loop Back
Message to be initiated.
See the following table for Initiate Link Trace Message configuration settings. Default
settings are identified in bold.
The MEP must be set to the In Service State for the Link Trace
Message to be initiated.
In addition to configuring PTP options, alarm attributes are editable when the PTP
application is selected (see PTP Alarms - GE114Pro (SH)/GE114Pro (CSH)).
PTP configuration options are created in the following order for Master Clock:
l Ensure that the Port associated with the PTP Flow Point is provisioned and In Service
l Edit Ethernet Port’s Delay Asymmetry
l Create / Edit a Telecom Slave
o Create / Edit a Slave Only Ordinary Clock (SOOC)
To edit a Transparent Clock, enter a right click on the Transparent Clock entity (TC-1-1)
and select Edit.
To delete a Transparent Clock, enter a right click on the Transparent Clock entity (TC-1-
1) and select Delete, then place the TC in Management state and select OK.
To edit a Telecom Slave, enter a right click on the Telecom Slave entity (TS-1-1) and
select Edit.
To delete a Telecom Slave, enter a right click on the Telecom Slave entity and select
Delete.
-port shall terminate and discard any SSM slow protocol Enabled
PDUs
QL-EEC1
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A,
QL-SSU-B, QL-EEC1. Default is QL-EEC1.
Valid entry for SONET Network Clock: QL-STU. QL-STU
Specifies the expected Quality Level (QL) when the Ethernet
Network Port is enabled for QL Mode. This object is only
applicable for Synchronous Ethernet capable ports, when QL-NONE
QL Mode is Enabled. This option allows the user to set a min-
imum expected received Quality Level on the port. The valid
values depend upon the SYNC entity’s Network Clock
Type. A value of None represents that a minimum Quality QL-PRC
Level is not expected.
QL-EEC1
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A,
QL-SSU-B, QL-EEC1, QL-NONE. Default is QL-NONE.
To edit an SOOC, enter a right click on the SOOC entity (SOOC-1-1-1-1-1) and select
Edit.
To delete an SOOC, enter a right click on the SOOC entity and select Delete. The SOOC
cannot be deleted if the TS is associated with a Sync Reference.
To edit a PTP Flow Point, enter a right click on the PTP Flow Point entity (e.g., ACC PTP
FLOW PT-1-1-1-1-1) and select Edit.
To delete a PTPFP, enter a right click on the PTPFP entity and select Delete.
To edit an OCS Port, enter a right click on the OCS Port entity (OCS PORT-1-1-1-1) and
select Edit.
To delete an OCS Port, enter a right click on the OCS Port entity and select Delete.
A Boundary Clock and Master Clock cannot co-exist. Only one or the other may be
provisioned and In Service at a time.
To delete a Boundary Clock, enter a right click on the Boundary Clock entity and select
Delete.
A Boundary Clock and Master Clock cannot co-exist. Only one or the other may be
provisioned and In Service at a time.
To delete a Master Clock, enter a right click on the Master Clock entity and select Delete.
To delete a Master Clock Interface, enter a right click on the Master Clock Interface
entity and select Delete.
Max Sync Message When Message Rate is 128 PPS, up to 4 remote slaves are 8 Packets Per Second
Rate (Create only) supported. 16 Packets Per Second
When Message Rate is 64 PPS, up to 8 remote slaves are sup- 32 Packets Per Second
ported.
64 Packets Per Second
When Message Rate is 32 PPS or lower, up to 16 remote
slaves are supported. 128 Packets Per Second
Maximum Delay Response Message Rate. 1 Packet Per Second
Even when the licensing PTP-MC/BC and PTP-Extended-
2 Packets Per Second
Remote-Slaves are both enabled, the maximum number of
slaves are still dependent of the PTP Packet Rate. 4 Packets Per Second
Max Delay When Message Rate is 128 PPS, up to 4 remote slaves are
8 Packets Per Second
Response Message supported.
Rate (Create only) When Message Rate is 64 PPS, up to 8 remote slaves are sup- 16 Packets Per Second
ported.
32 Packets Per Second
When Message Rate is 32 PPS or lower, up to 16 remote
slaves are supported. 64 Packets Per Second
To delete a Master Virtual Port, enter a right click on the Master Virtual Port entity and
select Delete.
The number of Static Slaves that may be created is dependent on the Max Slaves
Supported and Max Static Slaves Supported entries made when creating the Master
Clock [Link] enabling the licensing PTP - MC/BC, up to 5 remote slaves are
supported.
To edit a Static Slave, enter a right click on the Static Slave entity (e.g., STATIC SLAVE-
1-1-1-1) and select Edit.
To delete a Static Slave, enter a right click on the Static Slave entity and select Delete.
The number of Static Slaves that may be created is dependent on the Max Slaves
Supported and Max Static Slaves Supported entries made when creating the Master
Clock [Link] enabling the licensing PTP - MC/BC, up to 5 remote slaves are
supported.
To edit a Dynamic Slave, enter a right click on the Dynamic Slave entity (e.g., DYNAMIC
SLAVE-1-1-1-1) and select Edit.
To delete a Dynamic Slave, enter a right click on the Dynamic Slave entity and select
Delete.
To edit a PTP Clock, enter a right click on the PTP Clock entity (e.g., PTP CLOCK-1-1)
and select Edit.
To delete a PTP Clock, enter a right click on the PTP Clock entity and select Delete.
l When PTP Clock Type is set to Master Only, the PTP Boundary Clock
Clock will work in T-GM mode, and all the associated
PTP Clock Type ports should be configured with NotSlave = True.
l When PTP Clock Type is set to Boundary Clock, the PTP
Clock will work in T-BC mode, and the associated PTP Master Only
Port mode may be dynamically changed between Master,
Slave or Passive.
PTP Domain Number This PTP domain number is used in the domain number field
24 - 43
(Create only) of the PTP header in the PTP packet.
Priority 1 Priority 1 (based on IEEE 1588v2). 128
0 - 255
Priority 2 Priority 2 (based on IEEE 1588v2).
128
0 - 255
Local Priority Defines the local priority.
128
Expected QL QL-SSU-A
Choices available depend on the Network Clock Type
QL-EEC1
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A,
QL-SSU-B, QL-EEC1, QL-NONE. Default is QL-NONE.
QL-PRS
QL-STU
Expected QL Valid entry for SONET Network Clock: QL-PRS, QL-ST2
QL-TNC
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2,
QL-ST3E
(Continued) QL-SMC, QL-PROV, QL-NONE. Default is QL-NONE. QL-EEC2
QL-SMC
QL-PROV
To edit a PTP Port, enter a right click on the PTP Port entity (PTP PORT-1-1-1) and
select Edit.
To delete a PTP Port, enter a right click on the PTP Port entity and select Delete.
In addition to configuring SyncJack options, TIE history stats are available in the
SyncJack application.
To delete a Clock Probe, enter a right click on the Clock Probe entity (CLOCK PROBE-1-
1) and select Delete, then select OK.
To delete a PTP Clock Probe, enter a right click on the PTP Clock Probe entity (PTP
CLOCK PROBE-1-1) and select Delete, then select OK.
l If the Flow Point Type of the associated PTP Flow Point Slave to Master
is set to OC Slave, then Slave to Master or Master to
Direction Slave may be selected.
l If the Flow Point Type of the associated PTP Flow Point
is set to OC Master, then only Slave to Master selection Master to Slave
is allowed.
To edit thresholds, enter a right click on the Telecom Slave entity (TS-1-1) AND select
Edit Thresholds.
To delete a PTP Network Probe, enter a right click on the PTP Network Probe entity
(PTP NETWORK PROBE-1-1) and select Delete, then select OK.
RPDV rev Medium Residual Packet Delay Variation, reverse, medium (in
nanoseconds). Must be higher than the RPDV rev 1 - 4294967295
(ns)
Low setting and lower than the RPDV rev High set- 500
ting.
RPDV rev High Residual Packet Delay Variation, reverse, high (in
1 - 4294967295
(ns) nanoseconds).
2000
FPP Cluster 1 - 4294967295
Range - Assured Packet Delay Variation Assured (in nanoseconds)
(ns) 25000
FPP Cluster 1 - 4294967295
Range - Satisfied Packet Delay Variation Satisfied (in nanoseconds)
(ns) 150000
Identification
Schedule Index An Identifier value used to uniquely identify this
1-255
(Create Schedule only) SyncJack Schedule.
Result Analysis
Configure MTIE Comparison Parameters
Result Analysis may be configured by selecting the SyncJack icon on the Tool Bar or
selecting SyncJack from the Applications menu, expanding System, NE-1 and Result
Analysis in the Selection Tree, entering a right click on the MTIE Comparison entity and
selecting Configure.
A SAT Test Stream is created by entering a right click on the SAT Control entity and
selecting Create SAT Test Stream. To edit an existing SAT test stream, expanding the
SAT Control entity, entering a right click on the desired test stream and selecting Edit. To
delete a SAT test stream, enter a right click on the desired test stream and selecting
delete.
o Green PCP and Yellow PCP are not applicable Color Blind
o Outer VLAN Tag specifies the outer VLAN ID of
FLPDU (same as the flow’s VLAN member) and its
priority will be used by SAT control PDU,
DMM/DMR and FLPDU.
Enable/Disable the Drop Eligibility Indicator.
Use DEI
o if DEI is disabled:
n GTF will set DEI to 0 for both green and
yellow frames; CTF distinguishes color only
by priority.
l In Color Blind mode:
Enabled
o DEI can only be disabled.
Current implementation:
Identification
Session Sender ID Drop down list of available IDs. The list automatically
indexes to the next available number, but the user can 1 to 10
(Create Only) change it to any available number.
Alias A text and/or number string the user enters to uniquely
up to 64 characters
identify this Reflector. This string can be up to 64 print-
(blank)
able ASCII characters long.
Configuration
User selects a configured TWAMP IP Interface name Drop down list of
IP Interface from a drop down list. Each IP interface is associated selectable IP interface
with a port. names
User enters a UDP port to use for this Session Sender.
The default value of 0 is not a valid UDP port assign-
ment. It is recommended that user be cautious while 1 to 65535
UDP Port
choosing the well known UDP Port inclusively between 1 0
and 1023 in case of possible service conflicts and drop
the port range from 0xA000 to 0xDFFF.
Session Reflector IPv4 User enters the IPv4 address associated with the Ses- valid IPv4 address
Address sion Reflector to use with this Session Sender. [Link]
User enters the UDP port assigned to the Session 1 to 65535
Session Reflector UDP Port
Reflector. 0
Differentiated Services Code Point associated with this
DSCP Value 0 to 63
Session Sender
1 to 4294967295
Number of Packets The number of packets included in each transmission.
0
87 to 1526
Packet Size Size in bytes of each packet.
0
10 to 3600000 (msec)
Packet Interval Time in milliseconds between packet transmissions.
100
Response timeout in seconds for a response from the 2 to 10 (sec)
Response Timeout
Session Reflector. 5
Schedule Information
Start time type for a session. Immediate starts when a Immediate
Start Time Type Start Sessions command is executed on the associated
Control Client. Relative is a value in [Link] and Relative
requires a ‘Time’ entry. Fixed requires the user to des-
ignate both a ‘Date’ and ‘Time’ for the session to start. Fixed
Date Only valid if Start Time Type is Fixed. yyyy-mm-dd
Time Only valid if Start Time Type is Fixed or Relative. hh:mm:ss
VLAN Configuration
Identification
Session Reflector ID
Drop down list of available IDs. 1 to 10
(Create Only)
Alias A text and/or number string the user enters to uniquely
up to 64 characters
identify this Reflector. This string can be up to 64 print-
(blank)
able ASCII characters long.
Configuration
User selects a configured TWAMP IP Interface name Drop down list of
IP Interface from a drop down list. Each IP interface is associated selectable IP
with a port. interface names
User enters a UDP port to use for this Session
Reflector. The default value of 0 is not a valid UDP port
assignment. The UDP Port at Session Reflector end
should match the UDP Port at Session Sender end. It 1 to 65535
UDP Port
is recommended that user be cautious while choosing 0
the well known UDP Port inclusively between 1 and
1023 in case of possible service conflicts and drop the
port range from 0xA000 to 0xDFFF.
Use Sender Sequence Enable/Disable using the Sender Session’s sequence Disabled
Number number. Enabled
Delete Reflector
To delete a Reflector, select it from the Configuration tab and then click on OK. A Reflector can not be
deleted if it is associated with a Server.
Independent N2A rate limiting can be applied in the FSP 150GE11xPro system by enabling the feature in the flow configuration settings. When enabled, it allows for separate N2A rate settings to be configured, distinct from the A2N settings. However, constraints include ensuring that the system's set Frame Loss Threshold and Frame Loss Threshold Ratio do not inadvertently degrade service quality when independent rate limiting is configured. Proper configuration considers these threshold settings to maintain network performance standards .
Addressing an alarm indicating a synchronization reference failure involves verifying the synchronization network and its provisioning settings. Initially, one should ensure that all connections are intact and that no physical disruption exists in the synchronization signal path. Reviewing the network's configuration to confirm all reference settings are correct and operational is essential. Any identified hardware issues should be repaired or replaced to restore synchronization capabilities .
The system handles provisioning failures such as "ampProvFail" by raising an alert indicating that a client provisioning request was unsuccessful, either due to a client’s inability to apply the provisioning or a timeout awaiting a client response. The recommended corrective actions include verifying the accuracy and completeness of provisioning settings. If the error results from a timeout, ensuring optimal network conditions and reviewing the client communication pathways for interruptions or rule misconfigurations can help in resolving the issue .
The provisioning of a Master Clock in the PTP context for the GE114Pro involves several key elements: enabling the PTP-MC/BC feature through software licensing, ensuring the Network Port or Access Port is provisioned and in service, and configuring the associated Ethernet Port's Delay Asymmetry Setting. The setup also requires the integration of GPS for time reference, managed through editing the GPS port and setting it as the first priority reference. The steps further involve selecting system entities through the PTP application menu to formally create and configure the Master Clock. This comprehensive setup ensures precise timing and synchronization across the network .
The Synchronization Quality Level (QL) is significant in maintaining network integrity because it dictates the synchronization accuracy and stability across network devices. When the system receives SSM messages with a specified Quality Level lower than expected, it could indicate potential issues with synchronization accuracy. Such a mismatch can lead to degraded network performance or timing discrepancies. Configuring the QL settings correctly ensures that all devices use reliable references, thereby maintaining accurate time synchronization throughout the network .
Resetting the database to factory defaults on the FSP 150GE11xPro system will drop all traffic and erase all communications and user settings. This operation also results in the loss of the web-based GUI connection to the Network Element (NE), thereby disconnecting users from the system. Because of these significant consequences, the operation should not be performed casually. It is advisable to backup the current database to ensure the ability to restore settings if needed .
The recommended approach for setting up an Ethernet Port's Delay Asymmetry in the context of Precision Time Protocol (PTP) configuration on the GE114Pro involves performing the Edit Delay Asymmetry Setting procedure. This involves specifying the delay differences to calibrate timing accuracy between master and slave clocks within the network. Conducting these configurations accurately ensures that timing discrepancies are minimized, thus optimizing the precision of time synchronization across the network .
VLAN management in the FSP 150GE11xPro system involves entering desired VLAN IDs and priorities, which are crucial for organizing network traffic based on logical segmentation. Configuring VLAN IDs allows administrators to manage traffic flow and enhance network efficiency by ensuring packets are forwarded across relevant network segments. Priority settings further ensure that critical traffic is prioritized, reducing latency and enhancing the overall quality of service (QoS) in the network .
Link Loss Forwarding (LLF) is a feature that deactivates the Link Aggregation Group (LAG) if a corresponding remote port experiences a failure, effectively preventing data transmission over faulty links. When triggered, LLF causes the deactivation of a LAG, highlighting that the port is down due to Link Loss Forwarding, ensuring that the proper failed unit is addressed. This mechanism helps in maintaining network stability by preventing faulty communication paths and necessitates checking related network port alarms to identify the root cause and resolve the issue .
If the statistics tab for the Slave SOOC entity does not indicate expected message reception, the first step is to troubleshoot connectivity issues and verify the provisioning settings. This involves checking the network connections from the NE to the associated equipment to ensure cables are correctly installed and that there are no disruptions or misconfigurations affecting message flow. Any discrepancies in statistical data could hint at a failure in communication pathways or incorrect system configurations that may need correction .









