FSP 150CC-GE11X R6.1 Installation and Operations Manual

FSP 150CC-GE11x
Fiber Service Platform 150CC-

GE112/GE114/GE114S/GE114H/
GE114SH/GE114PH
Installation and Operations

Manual
Product Release 6.1

Document Issue: A (December 2013)
Copyright © 2001-2013 ADVA Optical Networking SE
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
(http://www.apache.org), Teodor Danciu (http://jasperreports.sourceforge.net), 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 pat-
ents.
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 Opti-
cal 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 MERCHANT-
ABILITY 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 CONSE-
QUENTIAL 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 DOC-
UMENT, UNLESS A SIGNED AGREEMENT WITH ADVA OPTICAL NETWORKING OR THE APPLI-
CABLE PRODUCT LIABILITY LAW EXPRESSLY STATES OTHERWISE.
ADVA Optical Networking SE
5755 Peachtree Industrial Blvd
Norcross, Georgia 30092
USA
Phone +1 678 728 8600
Fax +1 678 728 8788
http://www.advaoptical.com
Table of Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
List of Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 1 FSP 150CC-GE11x Overview . . . . . . . . . . 27

Common OAM Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Etherjack® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
GE112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
GE114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
GE114S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
GE114H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
GE114SH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
GE114PH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
FSP 150CC-GE11x R6.1 80000026494 Issue: A, © 2013 ADVA Optical Networking SE - Confidential
Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Obtaining Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
FSP 150CC-GE11x User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
eVision Web Browser Management Tool . . . . . . . . . . . . . . . . . . . . . . 35
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . 36
Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Service Applications and System Resources . . . . . . . . . . . . . . . . . . . . . . . . 38
Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Connection-Oriented UNI-EVC Mapping. . . . . . . . . . . . . . . . . . . . . . . . . 39
Provider Backbone Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Backbone Source Address and Destination Address . . . . . . . . . . . . . . 40
Network Port Traffic Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1+1 Network Port Protection Switching . . . . . . . . . . . . . . . . . . . . . . 41
Network Port Dual Active Receive . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Link Aggregation Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Layer 2 Protocol Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
L2PT Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
L2PT Protocols, Addresses and Signatures . . . . . . . . . . . . . . . . . . . . 43
Link Layer Discovery Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
LLDP Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Installation and Operations Manual 3

LLDP Frame Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
LLDP Frame Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Independent EVC Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
System Resource Rules and Limitations . . . . . . . . . . . . . . . . . . . . . . . . 46
Power over Ethernet - GE114PH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Split Horizon Group (GE114x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Ethernet-Link Management Interface (E-LMI) . . . . . . . . . . . . . . . . . . . . 50
Timing and Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Synchronous Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
System Clock Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Precision Timing Protocol (PTP) - GE114S/GE114SH . . . . . . . . . . . . . 53
ADVA’s Etherjack® Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Etherjack® Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 61
Etherjack® Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Cable Length Benchmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Etherjack® Service Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Ethernet Connectivity Fault Management . . . . . . . . . . . . . . . . . . . . . 71
Etherjack® Connection Performance Analyzer. . . . . . . . . . . . . . . . . . 83
Port, VLAN, EFM-OAM and I-Tag Loopback . . . . . . . . . . . . . . . . . . . . 87
Fault Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
EFM-OAM Dying Gasp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
SNMP Dying Gasp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
EFM-OAM Dying Gasp and SNMP Dying Gasp Inter-Operation . . . . . . . 95
Environmental Alarm Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Management and Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Management Traffic Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . 98
eVision Web Browser Management Tool . . . . . . . . . . . . . . . . . . . . . . 98
Breadcrumb. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
User Management and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Operations Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Low Touch Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
LTP Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Boot Configuration File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Alarm Generation and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
FSP 150CC-GE11x Hardware Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 111
Integrated Power Supplies - GE112/GE114/GE114S . . . . . . . . . . . . . . . 113
4 Installation and Operations Manual

Power Supply Units - GE114H/GE114SH/GE114PH . . . . . . . . . . . . . . . . 113
Power Supply External Fuse Rating and Cabling . . . . . . . . . . . . . . . . . . 114
Connector and LED Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Front Panel Connector Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 114
System LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Local Management Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Ethernet Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 2 Physical Installation . . . . . . . . . . . . . . . 123

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Physical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Preparing for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Verifying Site Readiness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Unpack and Inspect the FSP 150CC Equipment . . . . . . . . . . . . . . . . . . 130
Returning Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Install the FSP 150CC-GE11x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Mounting the GE112/GE114/GE114S . . . . . . . . . . . . . . . . . . . . . . . . . 135
GE112/GE114/GE114S Mounting Kits. . . . . . . . . . . . . . . . . . . . . . . 135
Mounting a Single GE112/GE114/GE114S via a Standard or Extended 19”
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Mounting a Single GE112/GE114/GE114S via a 23” Standard or Extended
/ ETSI Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 137
Mounting Dual FSP GE112/GE114/GE114S via a 19” Standard or Extended
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Mounting Dual FSP GE112/GE114/GE114S via a 23” Standard or Extended
/ ETSI Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 141
Mounting the GE112/GE114/GE114S to a Wall . . . . . . . . . . . . . . . . 143
Installing a GE112/GE114/GE114S Standalone Chassis . . . . . . . . . . 145
Mounting the GE114H/GE114SH/GE114PH . . . . . . . . . . . . . . . . . . . . . 146
Installing a Rack Mounted Chassis . . . . . . . . . . . . . . . . . . . . . . . . . 146
Mounting the GE114H/GE114SH/GE114PH to a Wall. . . . . . . . . . . . . . . 148
Installing a GE114H/GE114SH/GE114PH Standalone Chassis. . . . . . . . . 150
Connect Optional Earth Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Install GE114H/GE114SH/GE114PH PSU . . . . . . . . . . . . . . . . . . . . . . . . . 153
Install or Remove GE114H/GE114SH/GE114PH Blank Plates . . . . . . . . . . . 155
Route and Connect Copper Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Access / Network Interface Copper Cables . . . . . . . . . . . . . . . . . . . . . 157
Ethernet DCN Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Serial Console Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
USB Port Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Environmental Alarm Connections (GE114H/GE114PH) . . . . . . . . . . . . . 159
BITS IN and BITS OUT Cables (GE114S/GE114SH) . . . . . . . . . . . . . . . 160
Time of Day Cable (GE114S/GE114SH). . . . . . . . . . . . . . . . . . . . . . . . 160
Pulse Per Second Cable (GE114S/GE114SH) . . . . . . . . . . . . . . . . . . . . 161
External (10MHz) Frequency Reference Cable (GE114S/GE114SH). . . . . 161
GPS Cable (GE114SH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Install SFPs and Route Optical Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Install SFP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Route Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Connect Power Cables and Apply Power. . . . . . . . . . . . . . . . . . . . . . . . . . 167
Connect AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Connect -48 VDC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Connect +24 VDC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Start-Up LED Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
LED Start-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Power On Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Measure Optical Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Optical Attenuation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Clean Fiber Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Precautions When Connecting Fiber Optic Cables . . . . . . . . . . . . . . . . . 179
Connect Fiber Cables to Access Port or Network Port . . . . . . . . . . . . . . 180
To Power Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Power Supply Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . 181
LAN Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Serial Console Port Connector Pin Assignments . . . . . . . . . . . . . . . . . . 184
Environmental Alarm Connector Pin Description and Assignments -
GE114H/GE114PH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
RJ-48c BITS Connector Pin Description and Assignment - GE114S/GE114SH
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Time of Day (TOD) Connector Pin Assignments - GE114S/GE114SH . . . . 186
PPS/CLK Connector Pin Assignment - GE114S/GE114SH . . . . . . . . . . . . 186
GPS Connector Pin Assignment - GE114SH . . . . . . . . . . . . . . . . . . . . . 187
Changing Fan Air Filter Pad - GE114PH . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Chapter 3 eVision Web Browser Management Tool

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Logging On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Logging On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Logging Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
User Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Getting Familiar with eVision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
About the Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Selection Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Details Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Alarms Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Keyboard Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
eVision Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Maintenance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Viewing Entities in Maintenance View . . . . . . . . . . . . . . . . . . . . . . . . . 213
Editing Alarm Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Etherjack® Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Performance Monitoring View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
ESA and CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Precision Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Service Activation Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Chapter 4 Operations Provisioning . . . . . . . . . . . . 219

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 219
Provisioning the GE11x . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 219
Recommended Sequence of Steps for Initial Turn Up of a GE11x . . . . . . 219
Upgrade Software Version . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 220
Provision System Options . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 228
Configure System. . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 228
Configure Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 229
Configure ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 231
Configure LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 233
Edit the Security Banner . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 234
Edit System Time of Day . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 235
Provision NE-1 Common Units . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 239
Configure NE-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 239
Configure NTE11x . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... . . . . . 240

Configure PSUs - GE114H/GE114SH/GE114PH. . . . . . . . . . . . . . . . . . . 241
Provision Secure Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Configure Security Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Configure Security Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Configure Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Configure Remote Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Provision SNMP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Enable Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configure Flexible Port (Ethernet Port II) . . . . . . . . . . . . . . . . . . . . . . . . . 254
Provision Access Port Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
For GE112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
For GE114x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Ethernet Private Line Service Provisioning . . . . . . . . . . . . . . . . . . . . . . 256
Ethernet Virtual Private Line Service Provisioning. . . . . . . . . . . . . . . . . 267
Power Over Ethernet Service Provisioning . . . . . . . . . . . . . . . . . . . . . . 283
Provision Network Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Provision Network Ports without LAG or Protection Group . . . . . . . . . . . 285
Provision Network Ports in a Protection Group . . . . . . . . . . . . . . . . . . . 289
Provision Ports in a LAG Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Provision Ports in a Split Horizon Group (SHG) . . . . . . . . . . . . . . . . . . 297
Provision Network Ports in an Ethernet Ring Protection Group . . . . . . . . 299
Provision Management Tunnel(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Provision Precision Time Protocol (PTP) (GE114S/GE114SH) . . . . . . . . . . . 310
Provision Synchronous Ethernet (Sync-E) (GE114S/GE114SH) . . . . . . . . . . 337
Edit System Sync Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Edit BITS-IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Edit BITS-OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Edit CLK Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Edit PPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Edit TOD Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Edit GPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Edit Sync-E on a Network Port or Access Port . . . . . . . . . . . . . . . . . . . 345
Add a Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Edit a Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Delete a Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Provision Link Layer Discovery Protocol (LLDP). . . . . . . . . . . . . . . . . . . . . 351
Provision Environmental Alarms (GE114H/GE114PH) . . . . . . . . . . . . . . . . 355
Provision Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Database and Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
ICF Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Determine Database Configuration Status . . . . . . . . . . . . . . . . . . . 357

Set a System Default Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Create a Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Restore Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Restore System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
CLI Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
CLI Configuration File Management . . . . . . . . . . . . . . . . . . . . . . . . 376
Configuration File Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Default Settings Value File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Bulk Log Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Diagnostics Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Test the FSP 150CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Chapter 5 Communications Provisioning . . . . . . . 399

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Provision Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Management Communication to the FSP 150CC . . . . . . . . . . . . . . . . . . 400
Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Set Up the FSP 150CC DCN (eth0) Port Using the Serial Port . . . . . . 402
Set Up the 3G Modem Using the Serial Port . . . . . . . . . . . . . . . . . . 408
Browser-based IP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Edit DCN (eth0) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Configure Management Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Configure IPv6 over IPv4 Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Configure Source Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Add/Delete Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Add/Delete Static ARP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Add/Delete IPv6 Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Add/Delete IPv6 Static Neighbor Entry . . . . . . . . . . . . . . . . . . . . . . 439
Add/Delete IPv6 Static Proxy ND Entry. . . . . . . . . . . . . . . . . . . . . . 442
Configure Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Configure 3G Modem Using eVision . . . . . . . . . . . . . . . . . . . . . . . . 444
Sample Network - GNE to SNE over Management Tunnel . . . . . . . . . 454
Chapter 6 Etherjack Test Procedures and Performance

Monitoring. . . . . . . . . . . . . . . . . . . . . . . 459
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Performing Loopbacks Using eVision . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Etherjack® Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

Transmission Media Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Ethernet Fault Isolation and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . 463
Cable Length Benchmarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Manually Entering / Editing Cable Length Benchmarks . . . . . . . . . . . 468
Performance Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Etherjack® PM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Performance Parameter Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Performance Parameter Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Performance Parameter Thresholding . . . . . . . . . . . . . . . . . . . . . . . . . 472
Optical Performance Parameter Thresholding. . . . . . . . . . . . . . . . . . . . 472
Threshold Crossing Alert Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Viewing PM Counts and Threshold Values . . . . . . . . . . . . . . . . . . . . . . 473
Viewing PMs for Network Port, Access Port, Flow or LAG. . . . . . . . . . 473
Viewing PMs for ESA Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Initializing PM and Distribution Registers. . . . . . . . . . . . . . . . . . . . . . . 478
Initializing Network Port, Access Port, Flow and LAG Registers . . . . . 478
Initializing ESA Probe PM Registers . . . . . . . . . . . . . . . . . . . . . . . . 479
Initializing ESA Probe Distribution Registers . . . . . . . . . . . . . . . . . . 480
Editing PM Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Edit Network Port, Access Port, Flow or LAG PM Registers . . . . . . . . 481
Edit ESA Probe PM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
ESA Provisioning and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Provision a Layer-3 Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Provision a Y.1731 LM/DM Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Provision a Reflector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Provision an ESA Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
CFM Provisioning and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Etherjack® Connection Performance Analyzer . . . . . . . . . . . . . . . . . . . . . 514
Run Untagged ECPA Test on an Access Facility . . . . . . . . . . . . . . . . 517
Run VLAN ECPA Test on an Access Facility . . . . . . . . . . . . . . . . . . . 519
Service Activation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Chapter 7 Alarms, Events and Probable Causes, Error

Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Recommended Steps for Trouble Clearing . . . . . . . . . . . . . . . . . . . . . . . . 535
Obtaining Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Alarm Attributes, Probable Cause and Trouble Clearing . . . . . . . . . . . . . . . 537

Alarm Profile Notification Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Precision Time Protocol (PTP) Alarms (GE114S/GE114SH). . . . . . . . . . . 551
Network Port and Access Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 554
CFM Maintenance End Point Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 562
CFM QoS Shaper Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
LAG Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
SAT Responder Session Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
ERP Alarms (GE114x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Alarm Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Error Codes and System Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Chapter 8 Provisioning Rules . . . . . . . . . . . . . . . . 599

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Entity State Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Administration State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Administration State Model Details . . . . . . . . . . . . . . . . . . . . . . . . 600
Operational State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Secondary State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

User Authorization Privilege Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Configuration Settings, Rules and Dependencies. . . . . . . . . . . . . . . . . . . . 605
Factory Default Parameters and Maximum Bandwidth. . . . . . . . . . . . . . 606
System Configuration Options and Rules . . . . . . . . . . . . . . . . . . . . . . . 618
Pass-Through Flow Configuration Options and Rules . . . . . . . . . . . . . . . 652
LAG Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Network Port Configuration Options and Rules . . . . . . . . . . . . . . . . . . . 661
Access Port Configuration Options and Rules . . . . . . . . . . . . . . . . . . . . 666
Edit Access Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Default Priority Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Management Tunnel Configuration Options and Rules. . . . . . . . . . . . . . 701
IPv6 over IPv4 Tunnel Configuration Options and Rules . . . . . . . . . . . . 707
CPD Filters Options and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
LLDP Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Loopback Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Environmental Alarms Settings - GE114H/GE114PH . . . . . . . . . . . . . . . 717
Performance Monitoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Ethernet Network Port Monitored Types . . . . . . . . . . . . . . . . . . . . . 718
Ethernet Access Port Monitored Types . . . . . . . . . . . . . . . . . . . . . . 723
Ethernet Access Port N2A and LAG A2N Shaper Monitored Types. . . . 728
Flow Monitored Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Flow A2N Shaper Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . 732

Flow Policer Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
ESA Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Ethernet (Network/Access) Port PTP Flow Point Monitored Types . . . . 739
PTP MCI Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
PTP Remote Slave Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . 742
SOOC Monitored Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
PT Flow Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
PT Flow Shaper (QoS Queues) Monitored Types . . . . . . . . . . . . . . . 745
PT Flow Policer Monitored Types . . . . . . . . . . . . . . . . . . . . . . . . . . 745
ESA Options and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Scheduled ESA Activity Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
CFM Configuration Options and Rules . . . . . . . . . . . . . . . . . . . . . . . . . 752
Configure System Default MD Parameters . . . . . . . . . . . . . . . . . . . 752
Configure Server MEP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 753
Configure CFM VLAN Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Configure Maintenance Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Configure Maintenance Association Network . . . . . . . . . . . . . . . . . . 755
Configure Maintenance Association Component . . . . . . . . . . . . . . . . 757
Configure Maintenance End Point. . . . . . . . . . . . . . . . . . . . . . . . . . 758
Initiate Loopback Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Initiate Link Trace Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
PTP Configuration Options and Rules (GE114S/GE114SH) . . . . . . . . . . . 763
Transparent Clock Provisioning Order. . . . . . . . . . . . . . . . . . . . . . . 763
Telecom Slave Provisioning Order . . . . . . . . . . . . . . . . . . . . . . . . . 763
Boundary Clock Provisioning Order . . . . . . . . . . . . . . . . . . . . . . . . 763
Master Clock Provisioning Order (GE114SH Only) . . . . . . . . . . . . . . 764
Transparent Clock Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Edit Ethernet Port’s Delay Asymmetry . . . . . . . . . . . . . . . . . . . . . . 766
Telecom Slave Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Create / Edit a Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Create / Edit a Master Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
Create / Edit a Master Clock Interface . . . . . . . . . . . . . . . . . . . . . . 777
Create / Edit a Master Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . 779
Create / Edit a Static Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Edit / Delete a Dynamic Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
SAT Configuration Options and Rules . . . . . . . . . . . . . . . . . . . . . . . . . 783
Edit SAT System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Create/Edit SAT Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Create/Edit SAT Test Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
Edit SAC Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

List of Figures
Figure 1: FSP 150CC-GE112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 2: FSP 150CC-GE114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 3: FSP 150CC-GE114S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 4: FSP 150CC-GE114H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 5: FSP 150CC-GE114SH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 6: FSP 150CC-GE114PH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 7: eVision Web Browser Management Tool . . . . . . . . . . . . . . . . . 35
Figure 8: FSP 150CC-GE11x in a Cellular Backhaul Application . . . . . . . . 36
Figure 9: FSP 150CC-GE11x Management via 3G DCN port . . . . . . . . . . 37
Figure 10: FSP 150CC-GE114x in a G.8032 Ring Application . . . . . . . . . . . 38

Figure 11: Connection-Oriented UNI-EVC Mapping (Static Mapping). . . . . . 39
Figure 12: L2PT General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 13: Scope of Group MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 14: NTE11x Resources Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 15: PoE Application Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 16: Split Horizon Group Application Example . . . . . . . . . . . . . . . . . 50
Figure 17: E-LMI Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 18: Frequency Distribution via BITS Out Port and Sync-E Interface . 53
Figure 19: BITS Output Port Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 20: OC-Master, OC-Slave with TC Interconnect . . . . . . . . . . . . . . . 56
Figure 21: PTP Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 22: Clock Interface Functions and Interconnections . . . . . . . . . . . . 59
Figure 23: Demarcation for Traditional T1 Services . . . . . . . . . . . . . . . . . 60
Figure 24: Etherjack Demarcation for Ethernet Services . . . . . . . . . . . . . . 61
Figure 25: Performance Monitoring Summary View . . . . . . . . . . . . . . . . . 62
Figure 26: Etherjack® Diagnostic Results Using eVision . . . . . . . . . . . . . . 63
Figure 27: Faulty Segment Identified Using Cable Length Benchmark . . . . 64
Figure 28: ESA Test Results in Chart Format . . . . . . . . . . . . . . . . . . . . . . 65
Figure 29: End-to-End SLA Verification . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 30: ESA Probes and Reflectors . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 31: ESA One-Way Measurements . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 32: ESA Probe - Injector Operation . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 33: ESA Probe - Monitor Operation. . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 34: ESA Reflector Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Figure 35: Provider-Subscriber Relationship . . . . . . . . . . . . . . . . . . . . . . 72
Figure 36: Maintenance Domain Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 37: Maintenance Points Example . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 38: CCM Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 39: Link Trace Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 40: Loopback Message Example. . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 41: End-to-End EVC Circuit Testing Using ECPA . . . . . . . . . . . . . . . 83
Figure 42: ECPA Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 43: ECPA Point to Point EVC Example . . . . . . . . . . . . . . . . . . . . . . 85
Figure 44: ECPA Test Results Window. . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 45: CO Based Testing Using Ethernet Loopback . . . . . . . . . . . . . . . 87
Figure 46: Terminal Loopback (without Swap SA/DA). . . . . . . . . . . . . . . . 88
Figure 47: Facility Loopback (without Swap SA/DA) . . . . . . . . . . . . . . . . . 88
Figure 48: Access Port Terminal Loopback (without Swap SA/DA) . . . . . . . 89
Figure 49: Access Port Terminal Loopback (with Swap SA/DA) . . . . . . . . . 89
Figure 50: Access Port Terminal VLAN Loopback . . . . . . . . . . . . . . . . . . . 90
Figure 51: Network Port I-Tag based Terminal Loopback . . . . . . . . . . . . . 91
Figure 52: EFM-OAM Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 53: Network to Access Link Loss Forwarding . . . . . . . . . . . . . . . . . 92
Figure 54: Access to Access Link Loss Forwarding . . . . . . . . . . . . . . . . . . 92
Figure 55: EFM-OAM Dying Gasp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 56: SNMP Dying Gasp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 57: Single Level Management Bridging . . . . . . . . . . . . . . . . . . . . . 97
Figure 58: Dual Level Management Bridging . . . . . . . . . . . . . . . . . . . . . . 97
Figure 59: eVision Web Browser Management Tool . . . . . . . . . . . . . . . . . 99
Figure 60: GE112 Front Panel Connectors and LEDs (AC Variant) . . . . . . 116
Figure 61: GE114 Front Panel Connectors and LEDs (-48 VDC Variant). . . 116
Figure 62: GE114S Front Panel Connectors and LEDs (-48 VDC Variant). . 116
Figure 63: GE114H Front Panel Connectors and LEDs . . . . . . . . . . . . . . . 116
Figure 64: GE114SH Front Panel Connectors and LEDs . . . . . . . . . . . . . . 117
Figure 65: GE114PH Front Panel Connectors and LEDs . . . . . . . . . . . . . . 117
Figure 66: GE112/GE114/GE114S Rear Panel Frame Ground Point. . . . . . 121
Figure 67: GE114H/GE114SH/GE114PH Rear Panel Frame Ground Point. . 121
Figure 68: Install Half-width Units in Standard Rack in I-Temp Environment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 69: Install Half-width Units in Standard Rack in C-Temp Environment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

List of Figures
Figure 70: Install Full-width Units in Standard Rack in I-Temp Environment

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 71: Install Full-width Units in Standard Rack in C-Temp Environment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 72: Mounting a Single GE112/GE114/GE114S via EXT 19” Configuration
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 73: Mounting a Single GE112/GE114/GE114S via EXT 23” / ETSI
Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 74: Mounting Dual GE112/GE114/GE114S via EXT 19” Configuration
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 75: Mounting Dual GE112/GE114/GE114S via EXT 23” / ETSI
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 76: Installing GE112/GE114/GE114S Wall Mounting Brackets . . . . 144
Figure 77: Installing Mounting Brackets for GE114H/GE114SH/GE114PH Rack
Mounted Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 78: Mounting the GE114H/GE114SH/GE114PH into a Rack . . . . . . 148
Figure 79: Installing GE114H/GE114SH/GE114PH Wall Mounting Brackets
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 80: GE112/GE114/GE114S Rear Panel Frame Ground Point. . . . . . 151
Figure 81: GE114H/GE114SH/GE114PH Rear Panel Frame Ground Point. . 151

Figure 82: Grounding Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 83: GE114H/GE114SH -48 VDC PSU Locking Mechanism . . . . . . . 154
Figure 84: GE114H/GE114SH 120-240 VAC PSU Locking Mechanism (24W)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 85: GE114PH 120-240 VAC/95W DC PSU Locking Mechanism
(180W/95W/60W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 86: GE112/GE114/GE114S -48 VDC PSU Connector . . . . . . . . . . . 170
Figure 87: GE114H/GE114SH/GE114PH -48 VDC Power Supply Connector 170
Figure 88: GE112/GE114/GE114S +24 VDC PSU Connector . . . . . . . . . . 173
Figure 89: LED Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 90: GE112/GE114/GE114S -48 VDC Power Supply Connector . . . . 181
Figure 91: GE114H/GE114SH/GE114PH -48 VDC PSU Connector . . . . . . . 181
Figure 92: GE112/GE114/GE114S +24 VDC Power Supply Connector. . . . 182
Figure 93: eVision Web Browser Management Tool . . . . . . . . . . . . . . . . 190
Figure 94: System Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 95: Login Continue Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 96: Successful Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 97: Authentication Failure Screen. . . . . . . . . . . . . . . . . . . . . . . . 197
Figure 98: eVision Web Browser Management Tool Components . . . . . . . 198
Figure 99: Selection Tree with Menu Selected . . . . . . . . . . . . . . . . . . . . 202
Figure 100: Tab Selections and Scroll Bars in the Details Pane . . . . . . . . . 202

Figure 101: Edit Access Port Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 102: NTE11x Resources Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 103: Edit Network Port Configuration View . . . . . . . . . . . . . . . . . . 207
Figure 104: Alarm Attributes View of a Network Port . . . . . . . . . . . . . . . . 213
Figure 105: Conditions List View of the NE-1 Entity . . . . . . . . . . . . . . . . . 214
Figure 106: Edit Alarm Attributes Pane. . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 107: Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 108: Etherjack® Diagnostic Test Results View. . . . . . . . . . . . . . . . 217
Figure 109: Transfer Upgrade - Web View . . . . . . . . . . . . . . . . . . . . . . . 223
Figure 110: Transfer Upgrade - SCP View . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 111: File Transfer Progress Screen. . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 112: Software Install Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 113: Software Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 114: Validate Upgrade View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 115: Software Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 116: Edit System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 117: Edit Security Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 118: Edit Alarm Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 119: Edit Audit Log View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 120: Edit Syslog View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 121: Edit ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 122: Edit LLDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 123: Edit Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Figure 124: Edit System Time Of Day. . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 125: Edit System Time Of Day - Local Method . . . . . . . . . . . . . . . . 236
Figure 126: Edit System Time Of Day - NTP Method. . . . . . . . . . . . . . . . . 237
Figure 127: Edit System Time Of Day - PTP Method . . . . . . . . . . . . . . . . . 238
Figure 128: Edit NE-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 129: Edit NTE11x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Figure 130: Edit PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 131: Display SSL Certificate and SSH Key. . . . . . . . . . . . . . . . . . . 243
Figure 132: Regenerate Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 133: Regenerate SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . 244
Figure 134: Regenerate SSH Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 135: Edit Policy Strength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 136: Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 137: Edit User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Figure 138: Edit User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 139: Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

List of Figures
Figure 140: Remove Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Figure 141: Edit Remote Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 251
Figure 142: Edit Feature Management . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 143: License Warning Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 144: Feature Management Status View . . . . . . . . . . . . . . . . . . . . 254
Figure 145: Edit Access Port EPL Configuration View . . . . . . . . . . . . . . . . 257
Figure 147: Edit Access Port EPL Flow Configuration View. . . . . . . . . . . . . 259
Figure 148: Add Forwarding Table Entry . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 149: View FDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 150: FDB Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 151: Edit Access Port CPD Filters View . . . . . . . . . . . . . . . . . . . . . 263
Figure 152: Edit Access Port EFM-OAM View . . . . . . . . . . . . . . . . . . . . . . 264
Figure 153: Edit Access Port N2A Shapers View. . . . . . . . . . . . . . . . . . . . 264
Figure 155: Edit Access Port (EVPL) Configuration View . . . . . . . . . . . . . . 268
Figure 156: Edit Access Port EVPL Configuration View . . . . . . . . . . . . . . . 269
Figure 157: Edit Access Port CPD Filters View . . . . . . . . . . . . . . . . . . . . . 271
Figure 158: Edit Access Port EFM-OAM View . . . . . . . . . . . . . . . . . . . . . . 272

Figure 159: Edit Access Port Priority Mapping View . . . . . . . . . . . . . . . . . 273
Figure 160: Create Access Port EVPL Flow View. . . . . . . . . . . . . . . . . . . . 274
Figure 161: Create EVPL Multi-COS Flow Options. . . . . . . . . . . . . . . . . . . 277
Figure 162: Add Forwarding Table Entry . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 163: View FDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 164: FDB Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 165: Edit Access Port N2A Shapers View. . . . . . . . . . . . . . . . . . . . 279
Figure 166: Edit Access Port EVPL Configuration View . . . . . . . . . . . . . . . 280
Figure 167: Edit Global Power-Supplying Equipment (PSE) Configuration . . 284
Figure 168: Edit Port PSE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 284
Figure 169: Edit Network Interface 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 170: Edit OAM-EFM Network Interface 1 . . . . . . . . . . . . . . . . . . . . 287
Figure 171: Edit Network Port CPD Filters . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 172: Create Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Figure 175: Edit CPD Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 178: Edit Network Port CPD Filters . . . . . . . . . . . . . . . . . . . . . . . . 294

Figure 179: Create LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Figure 180: Create SHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 181: SHG Entity Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Figure 182: Create Ethernet Ring Protection Group . . . . . . . . . . . . . . . . . 299
Figure 183: View ERP Configuration Details . . . . . . . . . . . . . . . . . . . . . . 300
Figure 184: Pass-through Flow Configuration . . . . . . . . . . . . . . . . . . . . . 301
Figure 185: Create Pass-through Flow (Multi COS Enabled) . . . . . . . . . . . 302
Figure 186: Menu Selection to View Pass-through Flow . . . . . . . . . . . . . . 303
Figure 187: View Pass-through Flow Configuration Details . . . . . . . . . . . . 304
Figure 188: Edit ERP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 189: View ERP Configuration Details . . . . . . . . . . . . . . . . . . . . . . 305
Figure 190: ERP RAPS Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 191: ERP Statistics View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 192: Operate ERP Protection Switch . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 193: Release ERP Protection Switch . . . . . . . . . . . . . . . . . . . . . . . 309
Figure 194: Edit Feature Management . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Figure 195: Create Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 196: Network and Access Port PTP Flow Point in Selection Tree Pane
............................................ 314
Figure 197: Network Port PTP Flow Point Statistics . . . . . . . . . . . . . . . . . 315
Figure 198: Access Port PTP Flow Point Statistics. . . . . . . . . . . . . . . . . . . 315
Figure 199: Delete Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Figure 200: Create Telecom Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Figure 201: Create Slave Only Ordinary Clock . . . . . . . . . . . . . . . . . . . . . 318
Figure 202: Create PTP Flow Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Figure 203: Create Ordinary Clock Slave Port . . . . . . . . . . . . . . . . . . . . . 320
Figure 204: OCS Port Configuration - Port State (Slave) . . . . . . . . . . . . . . 321
Figure 205: PTP Flow Point Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Figure 206: SOOC Statistics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 207: SOOC Raw PTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 208: OCS Port Configuration Status (Slave) . . . . . . . . . . . . . . . . . 323
Figure 209: Edit PTP Access Port Delay Asymmetry . . . . . . . . . . . . . . . . . 323
Figure 210: Edit CLK Interface Configuration. . . . . . . . . . . . . . . . . . . . . . 324
Figure 211: Edit PPS Interface Configuration. . . . . . . . . . . . . . . . . . . . . . 325
Figure 212: Edit Time of Day Interface Configuration . . . . . . . . . . . . . . . . 326
Figure 213: Edit System Time of Day (PTP Clock Method). . . . . . . . . . . . . 327
Figure 214: Create Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Figure 215: Boundary Clock Configuration . . . . . . . . . . . . . . . . . . . . . . . 328
Figure 216: Create Master Clock Interface . . . . . . . . . . . . . . . . . . . . . . . 329

List of Figures
Figure 217: Create Master Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Figure 218: Dynamic Slave Configuration and Selection Menu. . . . . . . . . . 331
Figure 219: Dynamic Slave Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Figure 220: Edit Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Figure 221: Add a Time Clock Reference . . . . . . . . . . . . . . . . . . . . . . . . 334
Figure 222: Time Clock Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Figure 223: Operate Reference Switch on Time Clock Entity . . . . . . . . . . . 335
Figure 224: Time Reference State after Switch . . . . . . . . . . . . . . . . . . . . 335
Figure 225: Create Master Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 226: Edit System Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Figure 227: Edit BITS-IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Figure 228: Edit BITS-OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 229: Edit CLK Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 230: Edit PPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Figure 231: Edit TOD Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Figure 232: Edit GPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Figure 233: Edit Sync-E on Ethernet Port (Access Port) . . . . . . . . . . . . . . 345
Figure 234: Add Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Figure 235: Sync Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Figure 236: Edit a Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 237: Delete a Sync Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 238: Operate Reference Switch on System Sync Entity. . . . . . . . . . 349
Figure 239: Sync Reference State after Switch . . . . . . . . . . . . . . . . . . . . 350
Figure 240: Edit Access Port LLDP View . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 241: Provision Access Port LLDP Management Address View . . . . . . 353
Figure 242: Edit Access Port LLDP Management Address . . . . . . . . . . . . . 353
Figure 243: Port LLDP Configuration View . . . . . . . . . . . . . . . . . . . . . . . . 354
Figure 244: Edit Environmental Alarm Input . . . . . . . . . . . . . . . . . . . . . . 355
Figure 245: Database Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 246: Save Configuration to System Defaults View . . . . . . . . . . . . . 359
Figure 247: Copy System Default Database To Remote - Web View . . . . . . 359
Figure 248: Copy Database To Remote - SCP View . . . . . . . . . . . . . . . . . 360
Figure 249: Transfer Progress Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure 250: Copy Database From Remote - Web View . . . . . . . . . . . . . . . 362
Figure 251: Copy Database From Remote - SCP View . . . . . . . . . . . . . . . 363
Figure 253: New System Defaults View . . . . . . . . . . . . . . . . . . . . . . . . . 364
Figure 254: Backup Database View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Figure 255: Database Back Up Status View. . . . . . . . . . . . . . . . . . . . . . . 365

Figure 256: Copy Database To Remote - Web View . . . . . . . . . . . . . . . . . 366
Figure 257: Copy Database to Remote - SCP View . . . . . . . . . . . . . . . . . . 367
Figure 259: Copy Database From Remote - Web View . . . . . . . . . . . . . . . 369
Figure 260: Copy Database From Remote - SCP View . . . . . . . . . . . . . . . 370
Figure 262: Restore Database Query . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Figure 263: Activate Standby Database View . . . . . . . . . . . . . . . . . . . . . 371
Figure 264: Restore System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Figure 265: Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Figure 266: Configuration Files - Create . . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 267: Configuration Files - Update. . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 268: Configuration Files - Display Status . . . . . . . . . . . . . . . . . . . 384
Figure 269: Configuration Files - Edit Description . . . . . . . . . . . . . . . . . . 384
Figure 270: Configuration Files - Restart . . . . . . . . . . . . . . . . . . . . . . . . 385
Figure 271: Configuration Files - Import . . . . . . . . . . . . . . . . . . . . . . . . . 385
Figure 272: Configuration Files - Export . . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 273: Configuration Files - Remove . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 274: Copy System Default Settings From Remote - Web View . . . . . 388
Figure 275: Copy System Default Settings From Remote - SCP View . . . . . 389
Figure 277: Transfer Log View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Figure 278: Bulk Log Transfer - SCP View . . . . . . . . . . . . . . . . . . . . . . . . 391
Figure 280: Save Diagnostics File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Figure 281: Diagnostics File Save in Progress . . . . . . . . . . . . . . . . . . . . . 394
Figure 282: Diagnostics File Save Success . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 283: View Diagnostics Files Status and Time Stamp . . . . . . . . . . . . 395
Figure 284: Copy Diagnostics Files to Remote . . . . . . . . . . . . . . . . . . . . . 395
Figure 285: Diagnostics File Transfer - SCP View . . . . . . . . . . . . . . . . . . . 396
Figure 286: Diagnostics File Transfer - SCP Option Filled . . . . . . . . . . . . . 397
Figure 287: Diagnostics File Transfer Progress Screen . . . . . . . . . . . . . . . 397
Figure 288: eVision System View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 289: Edit DCN (eth0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Figure 290: Edit DCN - DHCP Enabled Client Role . . . . . . . . . . . . . . . . . . 416
Figure 291: Create Management Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 419
Figure 292: Display Management Tunnel Configuration . . . . . . . . . . . . . . 422
Figure 293: Edit Management Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Figure 294: Delete Management Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 423

List of Figures
Figure 295: Create Management Tunnel - Bridging Enabled . . . . . . . . . . . 424

Figure 296: Display Management Tunnel Configuration - Bridging . . . . . . . 426
Figure 297: Edit Management Tunnel - Bridging . . . . . . . . . . . . . . . . . . . 426
Figure 298: Create IPv6 over IPv4 Tunnel . . . . . . . . . . . . . . . . . . . . . . . 427
Figure 299: Display IPv6 over IPv4 Tunnel . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 300: Delete an IPv6 over IPv4 Tunnel . . . . . . . . . . . . . . . . . . . . . 429
Figure 301: Edit Source Address Config . . . . . . . . . . . . . . . . . . . . . . . . . 430
Figure 302: Add Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Figure 303: Display Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Figure 304: Delete Static Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Figure 305: Add Static ARP Entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Figure 306: Display Static ARP Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Figure 307: Delete Static ARP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Figure 308: Add IPv6 Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Figure 309: Display IPv6 Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Figure 310: Delete IPv6 Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Figure 311: Add IPv6 Static Neighbor Entry . . . . . . . . . . . . . . . . . . . . . . 439
Figure 312: Display IPv6 Static Neighbor Entries . . . . . . . . . . . . . . . . . . . 440
Figure 313: Delete IPv6 Static Neighbor Entry. . . . . . . . . . . . . . . . . . . . . 441

Figure 314: Add IPv6 Static Proxy ND Entry . . . . . . . . . . . . . . . . . . . . . . 442
Figure 315: Display IPv6 Static Proxy ND Entries. . . . . . . . . . . . . . . . . . . 443
Figure 316: Delete IPv6 Static Proxy ND Entry . . . . . . . . . . . . . . . . . . . . 444
Figure 317: Edit 3G Modem Configuration. . . . . . . . . . . . . . . . . . . . . . . . 446
Figure 318: 3G Modem Configuration Information . . . . . . . . . . . . . . . . . . 447
Figure 319: 3G Modem SIM Card Status . . . . . . . . . . . . . . . . . . . . . . . . 447
Figure 320: Enable 3G Modem PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Figure 321: Disable 3G Modem PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 322: Change 3G Modem PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 323: 3G Modem PIN Authentication . . . . . . . . . . . . . . . . . . . . . . . 451
Figure 324: Unlock 3G Modem with PUK . . . . . . . . . . . . . . . . . . . . . . . . . 452
Figure 325: 3G Networking Information . . . . . . . . . . . . . . . . . . . . . . . . . 452
Figure 326: Workstation / GNE / SNE on Same Subnet . . . . . . . . . . . . . . 454
Figure 327: CO Based Testing Using Ethernet Loopback . . . . . . . . . . . . . . 460
Figure 328: Loopback View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Figure 329: Etherjack® Diagnostic Test Results View. . . . . . . . . . . . . . . . 464
Figure 330: Faulty Segment Identified Using Cable Length Benchmark . . . 466
Figure 331: Edit Cable Length Benchmarks . . . . . . . . . . . . . . . . . . . . . . . 467
Figure 332: Summary PM Counts View of an Access Port Flow . . . . . . . . . 475
Figure 333: 15 Minute PM Counts View of an Access Port Flow . . . . . . . . . 475

Figure 334: Current PM Threshold View of a Network Port . . . . . . . . . . . . 476
Figure 335: Exporting 15 Minute PM Counts to Excel . . . . . . . . . . . . . . . . 476
Figure 336: 15 Minute PM Counts Exported to Excel. . . . . . . . . . . . . . . . . 477
Figure 337: Thresholds View of an ESA Probe . . . . . . . . . . . . . . . . . . . . . 478
Figure 338: Initialize PM Registers Pane . . . . . . . . . . . . . . . . . . . . . . . . . 479
Figure 339: Initialize ESA Probe PM Registers . . . . . . . . . . . . . . . . . . . . . 480
Figure 340: Initialize ESA Probe Distribution Registers . . . . . . . . . . . . . . . 481
Figure 341: Edit PM Threshold View of an Access Port Flow. . . . . . . . . . . . 482
Figure 342: Edit PM Threshold View of an ESA Probe . . . . . . . . . . . . . . . . 483
Figure 343: Create Probe View (ICMP Timestamp) . . . . . . . . . . . . . . . . . 485
Figure 344: Create Probe View (Y.1731 LM/DM) . . . . . . . . . . . . . . . . . . . 491
Figure 345: Viewing a Probe Configuration Tab . . . . . . . . . . . . . . . . . . . . 491
Figure 346: Viewing a Probe Distribution Statistics . . . . . . . . . . . . . . . . . 492
Figure 347: Viewing a Probe Thresholds Tab . . . . . . . . . . . . . . . . . . . . . . 492
Figure 348: Create Reflector View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Figure 349: Create Schedule View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Figure 350: ESA Test Results in Tabular Format . . . . . . . . . . . . . . . . . . . 499
Figure 351: ESA Statistics Results in Chart Format . . . . . . . . . . . . . . . . . 499
Figure 352: ESA Round Trip Delay Distributed Statistics Results in Chart Format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Figure 353: Filtering ESA Probe Statistics . . . . . . . . . . . . . . . . . . . . . . . . 500
Figure 354: Exporting ESA Probe Statistics to Excel . . . . . . . . . . . . . . . . . 500
Figure 355: ESA Probe Statistics Exported to Excel . . . . . . . . . . . . . . . . . 501
Figure 356: Create Maintenance Association Window . . . . . . . . . . . . . . . . 504
Figure 357: Create Maintenance Association - Component . . . . . . . . . . . . 505
Figure 358: Create MEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Figure 359: Create VLAN Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Figure 360: Configure Loop Back Message . . . . . . . . . . . . . . . . . . . . . . . 511
Figure 361: Configure Link Trace Message . . . . . . . . . . . . . . . . . . . . . . . 512
Figure 362: MEP Display Configuration Window . . . . . . . . . . . . . . . . . . . . 513
Figure 363: Edit ECPA Test Streams Window. . . . . . . . . . . . . . . . . . . . . . 515
Figure 364: ECPA Set Configuration Window (Flow VLAN). . . . . . . . . . . . . 516
Figure 365: ECPA Test Results Window. . . . . . . . . . . . . . . . . . . . . . . . . . 516
Figure 366: ECPA First Frame from ECPA Results Window. . . . . . . . . . . . . 517
Figure 367: Provision EVPL Flow for Testing . . . . . . . . . . . . . . . . . . . . . . 523
Figure 368: Up MEP on Associated Port . . . . . . . . . . . . . . . . . . . . . . . . . 524
Figure 369: Create SAT Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Figure 370: SAT Control Configuration View . . . . . . . . . . . . . . . . . . . . . . 526
Figure 371: Edit SAC Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526

List of Figures
Figure 372: Create SAT Test Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

Figure 373: SAT Test Stream View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Figure 374: Run SAT Test Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Figure 375: Run SAT Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Figure 376: SAT Test Status (Run SAT Test Stream) . . . . . . . . . . . . . . . . 530
Figure 377: SAT Test Status (Run SAT Control). . . . . . . . . . . . . . . . . . . . 531
Figure 378: SAT Test Result View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Figure 379: Export SAT Test Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Figure 380: Edit Ethernet Port’s Delay Asymmetry Parameter . . . . . . . . . . 766

24
Installation and Operations Manual
List of Tables
Table 1: System Resource Rules and Limitations . . . . . . . . . . . . . . . . . 46
Table 2: Front Panel Connectors (Left to Right) . . . . . . . . . . . . . . . . . 117
Table 3: System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 4: Local Management Port LEDs . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 5: Network Optical Ethernet Link and Rate LEDs . . . . . . . . . . . . 120
Table 6: RJ-45 Electrical Port Connector LED Definitions . . . . . . . . . . . 121
Table 7: FSP 150CC-GE11x Mounting Procedures . . . . . . . . . . . . . . . . 135
Table 8: Copper Cable Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 9: –48 VDC PSU Cable Wire Assignments . . . . . . . . . . . . . . . . . 181
Table 10: +24 VDC PSU Cable Wire Assignments . . . . . . . . . . . . . . . . . 182

Table 11: 10/100 Base-T LAN Port (RJ-45 Connector) . . . . . . . . . . . . . . 183
Table 12: 1000 Base-T LAN Port (RJ-45 Connector) . . . . . . . . . . . . . . . 183
Table 13: RJ-45 (RS-232 Serial Console Port) and DB9 Adapter Pin
Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Table 14: RJ-45, Environmental Alarm Input Connector . . . . . . . . . . . . 184
Table 15: RJ-48c, BITS IN Input Connector . . . . . . . . . . . . . . . . . . . . . 185
Table 16: RJ-48c, BITS OUT Output Connector . . . . . . . . . . . . . . . . . . . 185
Table 17: TOD RJ-45 RS422 Connector and Pin Assignments . . . . . . . . . 186
Table 18: PPS/CLK SMB Connector and Pin Assignments . . . . . . . . . . . . 186
Table 19: GPS SMA Connector and Pin Assignments . . . . . . . . . . . . . . . 187
Table 20: Software Download Condition Types . . . . . . . . . . . . . . . . . . . 222
Table 21: RAPS Status (Node State) Descriptions . . . . . . . . . . . . . . . . . 306
Table 22: ERP Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Table 23: SIM Card Status Description . . . . . . . . . . . . . . . . . . . . . . . . 448
Table 24: Performance Parameter Attributes . . . . . . . . . . . . . . . . . . . . 470
Table 25: Threshold Crossing Alert Attributes. . . . . . . . . . . . . . . . . . . . 472
Table 26: ESA Counts/Thresholds By Protocol Type and Report Group . . 497
Table 27: Alarm Profile Notification Codes . . . . . . . . . . . . . . . . . . . . . . 538
Table 28: System Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . 539
Table 29: PTP Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Table 30: Network Port and Access Port Alarms . . . . . . . . . . . . . . . . . . 554

Table 31: Maintenance End Point Alarms . . . . . . . . . . . . . . . . . . . . . . . 562
Table 32: Qos Shaper Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Table 33: LAG Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Table 34: SAT Responder Session Alarms . . . . . . . . . . . . . . . . . . . . . . 567
Table 35: ERP Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Table 36: Alarm Masking Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Table 37: Error Codes and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 579
Table 38: State Codes and Descriptions. . . . . . . . . . . . . . . . . . . . . . . . 603
Table 39: User Authorization Privilege Levels . . . . . . . . . . . . . . . . . . . . 605
Table 40: Factory Default Configuration Settings . . . . . . . . . . . . . . . . . 607
Table 41: Maximum Network Port/Access Port Bandwidth . . . . . . . . . . . 618
Table 42: System Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . 619
Table 43: Configuration Settings for Pass-Through Flows. . . . . . . . . . . . 652
Table 44: LAG Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Table 45: Network Port Configuration Settings (Edit Configuration) . . . . 662
Table 46: Configuration Settings for Ethernet Private Line Service . . . . . 668
Table 47: Configuration Settings for Ethernet Virtual Private Line Service
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Table 49: Recommended CBS / EBS Entry - Depending on CIR / EIR Range
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Table 48: Minimum CBS / EBS Entry - Depending on CIR / EIR Range . . 699
Table 50: 8021P or IP-TOS Default Priority Mapping Table . . . . . . . . . . . 700
Table 51: IP-DSCP Default Priority Mapping Table. . . . . . . . . . . . . . . . . 700
Table 52: Management Tunnel Configuration Settings . . . . . . . . . . . . . . 701
Table 53: IPv6 over IPv4 Tunnel Configuration Settings . . . . . . . . . . . . 707
Table 54: Control Data Protocol Configuration Options and Rules . . . . . . 709
Table 55: Layer 2 Control Protocol Summary . . . . . . . . . . . . . . . . . . . . 710
Table 56: System LLDP Configuration Settings . . . . . . . . . . . . . . . . . . . 713
Table 57: Physical Ethernet Port LLDP Configuration Settings. . . . . . . . . 714
Table 58: Loopback Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Table 59: Environmental Alarms Settings . . . . . . . . . . . . . . . . . . . . . . 717
Table 60: Ethernet Network Port Monitored Types and Default TCA Settings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Table 61: Ethernet Access Port Monitored Types and Default TCA Settings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Table 62: Ethernet Access Port/LAG QoS Queues Monitored Types and Default
TCA Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Table 63: Flow Monitored Types and Default TCA Settings . . . . . . . . . . . 729
Table 64: Ethernet Network Port QoS Queues Monitored Types and Default TCA
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732

List of Tables
Table 65: Flow Policer Monitored Types and Default TCA Settings . . . . . . 732
Table 66: ESA Monitored Types and Default TCA Settings . . . . . . . . . . . 733
Table 67: Ethernet Port PTP Flow Point Monitored Types and Default TCA
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Table 68: Master Clock Interface Monitored Types and Default TCA Settings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Table 69: PTP Remote Slave Monitored Types and Default TCA Settings . 742
Table 70: SOOC Monitored Types and Default TCA Settings . . . . . . . 743
Table 71: PT Flow Monitored Types and Default TCA Settings. . . . . . . . . 744
Table 72: PT Flow QoS Shaper Monitored Types and Default TCA Settings
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Table 73: PT Flow Policer Monitored Types and Default TCA Settings . . . 745
Table 74: ESA Reflector Configuration Settings. . . . . . . . . . . . . . . . . . . 746
Table 75: ESA Probe Configuration Settings . . . . . . . . . . . . . . . . . . . . . 747
Table 76: Scheduled ESA Configuration Settings . . . . . . . . . . . . . . . . . 750
Table 77: Configure Default MD Parameters Settings . . . . . . . . . . . . . . 752
Table 78: Configure Server MEP Parameters Settings . . . . . . . . . . . . . . 753
Table 79: CFM VLAN Table Configuration Settings. . . . . . . . . . . . . . . . . 754
Table 80: Maintenance Domain Configuration Settings . . . . . . . . . . . . . 754

Table 81: Maintenance Association Network Configuration Settings . . . . 756
Table 82: Maintenance Association Component Configuration Settings . . 757
Table 83: Maintenance End Point Configuration Settings . . . . . . . . . . . . 758
Table 84: Initiate Loopback Message Settings . . . . . . . . . . . . . . . . . . . 760
Table 85: Initiate Link Trace Message Settings . . . . . . . . . . . . . . . . . . . 761
Table 86: Create/Edit Transparent Clock Parameter Settings . . . . . . . . . 765
Table 87: Create/Edit Telecom Slave Parameter Settings. . . . . . . . . . . . 767
Table 88: Create/Edit SOOC Parameter Settings. . . . . . . . . . . . . . . . . . 770
Table 89: Create/Edit PTP Flow Point Parameter Settings. . . . . . . . . . . . 772
Table 90: Create/Edit OCS Port Parameter Settings . . . . . . . . . . . . . . . 774
Table 91: Create/Edit Boundary Clock Parameter Settings . . . . . . . . . . . 775
Table 92: Create/Edit Master Clock Parameter Settings . . . . . . . . . . . . . 776
Table 93: Create/Edit Master Clock Interface Parameter Settings . . . . . . 777
Table 94: Create/Edit Master Virtual Port Parameter Settings. . . . . . . . . 779
Table 95: Create/Edit Static Slave Parameter Settings . . . . . . . . . . . . . 780
Table 96: Create/Edit Dynamic Slave Parameter Settings . . . . . . . . . . . 782
Table 97:\ Edit SAT System Parameter Settings . . . . . . . . . . . . . . . . . . 783
Table 98: Create/Edit SAT Control Parameter Settings . . . . . . . . . . . . . 783
Table 99: Create/Edit SAT Test Stream Parameter Settings . . . . . . . . . . 784
Table 100: Create/Edit SAC Profile Parameter Settings . . . . . . . . . . . . . . 787

28
Chapter 1
FSP 150CC-GE11x Overview

The ADVA Optical Networking FSP 150 family of Ethernet access products pro-
vides devices for Ethernet demarcation, extension and aggregation to support
delivery of intelligent Ethernet services both in-region and out-of-region.
Optimized for wireless backhaul, the Fiber Service Platform 150CC-
GE112/GE114/GE114S/GE114H/GE114SH/GE114PH (FSP 150CC-GE11x)
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 150CC-GE11x 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 Entity State
Descriptions on p. 599 for mounting kit details).
Multiple units may be stacked up to 4 rows high, depending on the operating
environment. (Refer to FSP 150CC GE11x R6.1 Installation and Operations
Manual document for air flow requirement details.) A detailed list of system fea-
tures is provided in FSP 150CC GE11x Technical Descriptions document.
The GE112/GE114/GE114S product is a 1U high, half-width chassis, which may
be ordered equipped with either a single AC, -48VDC or +24VDC integrated
power supply.
The GE114H/GE114SH/GE114PH product is a 1U high, full-width chassis, with
redundant modular Power Supply Unit (PSU) slots (AC and/or DC).
Common OAM Capabilities

A rich set of remote OAM capabilities ensure that the equipment can be
installed and the services can be turned on without any on-site provisioning.
Optional Network port protection and temperature hardening ensure high ser-
vice availability for mission critical applications, while Service Level Agreement
(SLA) verification can be ensured via integrated SLA monitoring. Small Form-
factor Pluggable (SFP) optical devices address a wide range of optical fibers,
reaches and wavelengths.

Etherjack®
ADVA Optical Networking’s patent-pending Etherjack technology allows a car-
rier to deploy profitable Ethernet services by providing an intelligent Ethernet
demarcation point that includes an 802.1ag, Y.1731 and 802.3ah compliant Net-
work 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 car-
rier-class Ethernet services. The Etherjack service UNI provides service intelli-
gence 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.
GE112
The FSP 150CC-GE112 has the following main features:
• One (Protected) Network interface that operates in optical mode
(100BaseFX or 1000BaseX) via a Small Form factor Pluggable (SFP) trans-
ceiver 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.
• Two Access interfaces (Three Optional - if Network protection is not provi-
sioned), configured as either electrical (10/100/1000BaseT) via RJ45 con-
nector or optical (100BaseFX or 1000BaseX) via an SFP transceiver.
• 802.1ad Provider Bridge C-Tag / S-Tag Mapping
• Etherjack Service Assurance (ESA) and Connectivity Fault Management
(CFM)
• Y.1564 Service Activation Testing (SAT)
With four Ethernet copper/fiber combination ports, the FSP 150CC-GE112
device is capable of supporting multiple customers or service configurations
over an optional protected GbE or 100FX optical connection. The GE112 sup-
ports 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 config-
ured for LAG or 1+1 Network protection, or as an Access port. Ports 3 and 4 are
dedicated Access ports. The FSP 150CC-GE112 is a version of the product that
does not include Synchronous Ethernet (Sync-E) capability. See Figure 1 for a
front view of the FSP 150CC-GE112.

Chapter 1 FSP 150CC-GE11x Overview
Figure 1: FSP 150CC-GE112
GE114
The FSP 150CC-GE114 has the following main features:
(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.
• Four Access interfaces (Five Optional - if Network protection is not provi-

(CFM)
• G.8032 Ethernet Ring Protection (ERP)
With six Ethernet copper/fiber combination ports, the FSP 150CC-GE114
device is capable of supporting multiple customers or service configurations
over an optional protected GbE or 100FX optical connection. The GE114 sup-
ports six Ethernet combination ports that may be configured for copper
(10/100/1000BASE-T) or optical (100BASE-FX/1000BASE-X). Port 1 is fixed
ured for LAG or 1+1 Network protection, or as an Access port. Ports 3 through 6
are dedicated Access ports. The FSP 150CC-GE114 is a version of the product
that does not include Sync-E capability. See the following figure for a front view
of the FSP 150CC-GE114.
Figure 2: FSP 150CC-GE114

GE114S
The FSP 150CC-GE114S has the following main features:
(CFM)
• G.8261 Synchronous Ethernet (Sync-E)
• IEEE 1588v2 Precision Time Protocol (PTP)
The FSP 150CC-GE114S is similar to GE114, except that it is a version of the
product that supports Sync-E functionality and has BITS IN and BITS OUT inter-
faces via a RJ48c connector for T1/E1 timing input and output, one TOD inter-
face via RJ45 connector, two Mini-SMB connectors for PPS IN (for future use)
and PPS Out respectively, and one more Mini-SMB connector for exter-
nal10MHz Clock frequency output (CLK). See the following figure for a front
view of the FSP 150CC-GE114S.
Figure 3: FSP 150CC-GE114S
GE114H
The FSP 150CC-GE114H has the following main features:


(CFM)
The FSP 150CC-GE114H is similar to the GE114, except that it is a version of
the product that includes dual (redundant) pluggable Power Supply Units
(PSUs), dry contact Environmental Alarm input connector and is full width. See
the following figure for a front view of the FSP 150CC-GE114H.
The GE114H 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.
Figure 4: FSP 150CC-GE114H

GE114SH
The FSP 150CC-GE114SH is similar to GE114S, besides all the interfaces and
features supported in GE114S, it is a version of the product that include dual
(redundant) pluggable Power Supply Units (PSUs) and one additional front
mounted SMA connector for external GPS signal receiving. See the following
figure for a front view of the FSP 150CC-GE114SH.
The GE114SH 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.
Figure 5: FSP 150CC-GE114SH
GE114PH
The FSP 150CC-GE114PH is similar to the GE114H, except that it is a version
of the product that also supports Power over Ethernet (PoE), dual (redundant)
pluggable (180 Watts, 60Watts or 95Watts) AC or 95 Watts DC Power Supply
Units (PSUs) - and the front connectors are arranged differently. See the follow-
ing figure for a front view of the FSP 150CC-GE114PH.

Document Overview
Figure 6: FSP 150CC-GE114PH
The GE114PH 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.
Document Overview
This manual is provided to help you install, configure and operate the FSP
150CC-GE11x. This manual provides an introduction to the FSP
150CC-GE11x, a description of its operation, and a step by step walk-through of
the installation process.
This version of the FSP 150CC-GE11x Installation and Operations Guide is
applicable to the FSP 150CC-GE11x software release 6.1. For defect resolution
and functional additions please refer to the Release Notes.
Although this document focuses primarily on using the eVision web browser for
configuring and monitoring the FSP 150CC-GE11x, equivalent CLI or SNMP
commands may be used. For more information regarding the CLI command
structure, refer to the FSP 150CC-GE11x Command Line Interface Reference
Guide. For more information regarding the SNMP command structure, refer to
the FSP 150CC-GE11x SNMP Reference Manual.
Before installing and provisioning the FSP 150CC-GE11x, familiarize yourself
with the FSP 150CC-GE11x equipment, its functions and requirements. The fol-
lowing chapters support the installation and operation of the FSP
150CC-GE11x:
Chapter 1, Overview of the FSP 150CC-GE11x contains product overview infor-
mation and feature descriptions.
Chapter 2, Physical Installation contains procedures to physically install the
FSP 150CC-GE11x and contains a recommended work flow sequence for new
installations, including support for software upgrades.
Chapter 3, eVision Web Browser Management Tool contains an overview of the
eVision web browser management tool workspace and contains procedures for
logging in and logging off.
Chapter 4, Operations Provisioning contains step by step operations and provi-
sioning procedures for the FSP 150CC-GE11x system. It is organized in the rec-
ommended workflow for new installations and can be applied to existing
systems.
Chapter 5, Communications Provisioning contains step by step procedures for
provisioning the FSP 150CC-GE11x communications interfaces. It is organized
in the recommended workflow for new installations and can be applied to exist-
ing systems.
Chapter 6, Etherjack® Testing Procedures and Performance Monitoring con-
tains information on service loopbacks and step by step procedures for perform-

ing IP connection tests (e.g., ping), Etherjack® Diagnostics, Cable Length

Benchmarks, and executing Etherjack Service Assurance and Connectivity
Fault Management tests. This chapter also contains step by step procedures for
viewing PM counters, setting thresholds and initializing counters.
Chapter 7, Alarms, Events and Probable Causes contains listing of all alarms
and events generated by the system and includes the probable cause of each.
Chapter 8, Provisioning Rules contains configuration option setting information
to be used as a guide to plan, operate, configure and maintain the FSP
150CC-GE11x. It contains system default settings, configuration options and
provisioning rules using the eVision web browser management tool. High level
descriptions and provisioning rules are provided for each eVision configuration
option. Additional information for each option description can be found in the
Technical Descriptions document and Application Notes for specific features.
For CLI option settings and rules, refer to the FSP 150CC-GE11x Command
Line Interface Reference Guide.
Audience
The reader must have sufficient knowledge of the following when using this doc-
ument:
• IP addressing
• Network port facility provisioning requirements

• Access port EVC provisioning requirements
• Fiber handling and cleaning procedures (if connecting fiber cables)
• Power handling and connection procedures (if connecting DC power)
Related Documentation
Refer to the following documents for additional information about the FSP
150CC-GE11x:
• FSP 150CC-GE11x 6.1 Technical Descriptions
• FSP 150CC-GE11x 6.1 Command Line Interface Reference Guide
• FSP 150CC-GE11x 6.1 Quick Start Guide
• FSP 150CC-GE11x 6.1 SNMP User Guide
• Safety Guide
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/sug-
gestions to:
global-techdocu@advaoptical.com
To submit your comments/suggestions by mail, use the following address:
ADVA Optical Networking SE
Technical Documentation

Document Overview
Märzenquelle 1-3
98617 Meiningen-Dreissigacker
Germany
We appreciate and value your comments/suggestions to improve the quality of
our manuals.
Obtaining Technical Assistance

Product Maintenance Agreements and other customer assistance agreements
are available for our products through your ADVA distribution channel. Techni-
cal support is available to warranty or maintenance contract customers who
need technical assistance with a product that is under warranty or covered by a
maintenance contract.
To display ADVA’s Technical Support web site that includes all contact informa-
tion, go to the home page at http://www.advaoptical.com and select
“Customer Login”.
ADVA’s service options include:
• 24 X 7 telephone support
• Web-based support tools
• On-site support
• Technical training, both on-site and at company facilities in Germany, the
UK and the USA
• Expedited repair service
• Extended hardware warranty service
Customer Login ADVA’s customer login provides a suite of interactive, networking services that
provide immediate access to information and resources at any time, from any-
where 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
http://www.advaoptical.com

FSP 150CC-GE11x User Interfaces

The FSP 150 family of Ethernet access products support the following User
Interfaces.
eVision Web Browser Management Tool

The FSP 150CC-GE11x supports an eVision web browser management tool to
provide a web based Graphical User Interface (GUI) for Operation, Administra-
tion and Maintenance (OA&M) functions. For more information on eVision web
browser management tool operation, see Chapter 3: eVision Web Browser
Management Tool.
Figure 7: eVision Web Browser Management Tool

Command Line Interface

Although this document focuses on using the eVision web browser for configur-
ing and monitoring the FSP 150CC-GE11x, equivalent CLI commands may be
used. The CLI command structure provides a text-based system for local config-
uration and management of FSP 150CC-GE11x functions. CLI access may be
attained via RS-232 Serial Console Port direct connection, or telnet / ssh ses-
sion. For more information regarding the CLI command structure, refer to the
FSP 150CC-GE11x Command Line Interface Reference Guide.

Network Topology
Simple Network Management Protocol

Although this document focuses on using the eVision web browser for configur-
ing and monitoring the FSP 150CC-GE11x, equivalent SNMP commands may
be used. The FSP 150CC-GE11x SNMP MIB provides a system for remote con-
figuration and management of FSP 150CC-GE11x functions. For more informa-
tion regarding the SNMP command structure, refer to the FSP 150CC-GE11x
SNMP Reference Manual.
Network Topology
The FSP 150CC-GE11x is a next generation Ethernet demarcation unit with an
extended temperature range (-40C to +65C) which is suited for use in a remote
terminal cabinet.
The FSP 150CC-GE11x may be deployed in a stand-alone configuration con-
nected to a third party switch. Management can be direct to the DCN interface
on the front of the unit or via in-band IP-based management tunnel. The service
topology in this application could take the form of either a hub or spoke configu-
ration. In the spoke scenario, the system will need to support a few EVCs. In the
hub scenario, a much larger number of EVCs would be required.
In a simple point-to-point application, systems may be connected back-to-back
via direct fiber connection (or via some optical path network). Management is
only available at the end-points for the circuit and one end of the link may act as
a management proxy for the remote system with communication via an embed-
ded management tunnel.
Figure 8: FSP 150CC-GE11x in a Cellular Backhaul Application
E th ern et
E th ern et R ad io N etw o rk
U p lin k
C o n troller
P acket S T M 1 /O C 3
Sw itch (E 1 /T 1 )
N etw ork
F S P 1 5 0 C C -G E 11 x
G atew a y
B ase S ta tio n
C on tro ller
A 3G DCN port (cellular port) provides a wireless management port that can be
accessed via 3G network so that user can connect to the FSP 150CC-GE11x
without cable connections, or it can work as a backup management port when
the DCN LAN port is disconnected (see the figure below). However, the 3G
DCN port cannot work as the DCN port backup when the system is in manage-
ment bridging mode.

When the primary management connection is working with no trouble, FSP

150CC-GE11x will report its public IP address acquired from 3G service pro-
vider to a Network manager via the primary management connection. If the pri-
mary management connection fails, the user can use a PC/laptop to connect to
the FSP 150CC-GE11x via a public 3G network.
Figure 9: FSP 150CC-GE11x Management via 3G DCN port
The FSP 150CC-GE114/GE114S/GE114H/GE114SH/GE114PH (GE114x)

support Ethernet Ring Protection (ERP) as follows (see Figure 10 on p. 38):
• R-APS and ERP Control

• Up to two 2-Port Ring instances (Major Ring) on the Network Port pair
• User Actions of Forced Switch, Manual Switch and Clear
• User Ability to Configure Revertive and Non-Revertive modes
• FDB support for MAC Learning
• EPL and EVPL service support
The Ethernet Ring Protection (ERP) feature provides a mechanism for Ethernet
service recovery utilizing redundant paths configured in a logical ring topology, a
loop avoidance protocol and learning/forwarding/flooding of Ethernet frames.
A Major Ring consists of multiple Ring Nodes connected together in a ring topol-
ogy. Loop avoidance on a non-failed ring is achieved by blocking service frames
on one of the links in the ring – the Ring Protection Link (RPL). One of the Ring
Nodes is designated as the RPL Owner and this node performs the blocking of
service frames to or from the RPL.
An optional RPL Neighbor Node can be configured to allow better bandwidth uti-
lization for multiple rings and for certain flush optimization scenarios. The RPL
Neighbor Node also blocks service frames to or from the RPL when the RPL is
blocked by the RPL Owner.

Service Applications and System Resources
Figure 10: FSP 150CC-GE114x in a G.8032 Ring Application
RPL Owner
RPL BLock
Ring Protection Link

(RPL)
RPL Neighbor
MAJOR
RING
Ring Node
For more details regarding ERP functionality, see the FSP 150CC-GE11x R6.1
Technical Descriptions document.

Software Licensing
FSP 150CC-GE11x provides optional functions in different GE11x variants.
ADVA offers these function with a 60-day free trail, but to use this function
legally after the trial period, the user must purchase a separate Software
License.
• Provider Backbone Bridge (PBB), available in GE112, GE114, GE114H,
and GE114PH, see Provider Backbone Bridge on p. 40 for its function
description
• Precision Time Protocol (PTP), available in GE114S and GE114SH, see
Precision Timing Protocol (PTP) - GE114S/GE114SH on p. 53 for its func-
tion
• PTP-Master Clock (MC)/Boundary Clock (BC), available in GE114S and
GE114SH, wherein MC is only supported in GE114SH

Within 60 days of enabling this feature, you must purchase and obtain
a valid license key corresponding to the feature being enabled. If you
do not comply with the above terms, continuing to use this feature is a
violation of your End User License Agreement and may result in legal
actions being taken against you. ADVA reserves the right to ensure
entitlement and compliance through auditing.
Connection-Oriented UNI-EVC Mapping

In Connection-oriented UNI-EVC mapping, client Ethernet frames from a UNI
are statically mapped to a network EVC based on the client port, client VLAN,
frame priority, or some combination thereof. Connection-oriented mode sup-
ports E-LINE service types providing Ethernet Private Line (EPL) and Ethernet
Virtual Private Line (EVPL) service offerings.
A Connection-oriented UNI which maps all client frames to a single EVC oper-
ates in EPL service type, as is the case for UNI-1 in the following figure. UNI-2
maps some frames to one EVC and other frames to another EVC. In the exam-
ple, UNI-2 uses a single VLAN tag to determine which EVC to address. Such a
service is referred to as a single-tagged multiple-service offering. UNI-3, in con-
trast, maps frames with a single VLAN 404 to an EVC. This type of offering is
referred to as single-tagged single-service.
Figure 11: Connection-Oriented UNI-EVC Mapping (Static Mapping)
Network EVCs
UNI <–> EVC
Mapping
UNI-1 All frames
UNI-1
UNI-2 VLAN 56
UNI-2 Network Port
UNI-2 VLAN 405
UNI-1 VLAN 404

UNI-3
UNI-3

Provider Backbone Bridge

The Provider Backbone Bridge (PBB, also known as Mac-in-Mac) encapsulates
an Ethernet Frames inside a new Ethernet header with a new Backbone DA
MAC (BDA) and new Backbone SA MAC (BSA). With the customer MAC
address hidden, PBB significantly reduces the number of MAC address for the
provider equipment to learn. PBB makes use of Backbone Service Instance Tag
(I-Tag), which is similar to C-Tag and S-Tag. The I-Tag includes a 24-bit I SID,
allowing 224 (or 16, 777, 215) unique service identifiers. The PBB standard also
defines an optional Backbone VLAN Tag (B-Tag), which is ignored by FSP
150CC-GE11x.
Each Network Port supports the configuration of a B-MAC. It is used as the
Source MAC address of the PBB Frames sent out from this Network Port. By
default, the B-MAC is the same as the Network Port’s MAC address.
A Flow can be configured independently to push either an I-Tag (the I-SID and
the PCP bits) or just the I-SID, which results in the P-bits from the received
X-tag being populated in the PCP bits (P-bit) of the I-Tag. The Backbone DA
MAC address (BDA) is configured per EVC allowing each EVC to be routed to a
unique Route.
A frame is recognized as a PBB frame if:
• The outer tag is an I-Tag (EtherType: 0x88E7)
• The outer tag is a Backbone VLAN Tag (B-Tag, indicated by EtherType:
0x88A8) and the inner tag is an I-Tag (EtherType: 0x88E7).
The PBB frame arrive at network port is accepted only when its B-DA matches
system B-MAC or default B-MAC multicast group address.For the on incoming
traffic received on Network Port:
• PBB frames lookup is done with (Backbone Service Instance ID) I-SID.
• Non-PBB Frame lookup is done with C-TAG or S-TAG.
Backbone Source Address and Destination

Address
In FSP 150CC-GE11x, The outgoing Network BMAC is used as Backbone
Source Address (BSA) of PBB encapsulation.
When there is a LAG existing on the Network Port, the BMAC of LAG port is
used as BSA of PBB encapsulation. And it is copied from Network Port 1, and
when LAG is deleted, the BMAC value of Network Port 1 will be copied from
LAG port. The PBB frame arrive at network port is accepted only when its B-DA
matches system B-MAC or default B-MAC multicast group address.
For FSP 150CC-GE11x Management Tunnel. BSA is the system’s B-MAC. And
the BDA is assigned by user. I-TAG is assigned by user.
Network Port Traffic Protection

The FSP 150CC-GE11x supports three types of Network Port traffic protection:
• 1+1 protection switching

• Dual-active receive
• 1:1 protection switching via Link Aggregation Group (LAG)
1+1 Network Port Protection Switching

If Network traffic protection is desired, the system supports configuring 1+1
switching protection of Network traffic. The switching function normally uses
loss of signal, signal degrade, switch request (forced, lockout or manual), EFM
failure or lack of discovery, and can use CCM defect detection as default (see
Protection in FSP 150CC GE11x R6.1 Installation and Operations Manual docu-
ment). Protection switching occurs within 50 mSec following detection of switch-
ing criteria.
When CCM defect is used as a trigger for protection switching,

PS
performing a loopback on port can cause undesired protection

switching.
Note
Network Port Dual Active Receive

An option provided to users of the FSP 150CC-GE11x is to configure the Net-
work Ports so that both receivers are active at the same time. This option is pro-
vided primarily to support upstream equipment provisioned to handle different
VLAN traffic on each Network Port. Normally, in 1+1 protection, both transmit-
ters are active and transmit the same information, but only one receiver is
active. By setting both receivers to active, different packets on each Network
Port will still all get to their respective Access Port. However, it is possible to
receive duplicate packets and send them both to the Access Port. It is also pos-
sible for the receive traffic to exceed the effective bandwidth of the FSP
150CC-GE11x. Because of these potential problems, unless the user’s network
topology requires both receivers to be active at the same time, the user should
refrain from using this option.
Link Aggregation Group

The system supports configuring 1:1 switching protection of traffic by establish-
ing a LAG group in conformance to IEEE 802.3-2005. The LAG switching func-
tion normally uses LACP, but can be configured to use CCM defect detection if
desired. When FSP 150CC’s are connected back-to-back using LACP, protec-
tion switching occurs within 50 mSec. Slower switching may be experienced
when inter-operating with other vendor’s equipment due to issues related to
LAG/LACP protocol characteristics. The FSP 150CC-GE11x supports LAG on
the Network Ports and/or the Access Ports. Up to 1 (for GE112) or 2 (for
GE114x) LAG groups are supported on Access Ports.
The FSP 150CC-GE11x 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 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.
Layer 2 Protocol Tunneling

The Layer 2 Protocol Tunneling (L2PT) function is used to tunnel customer LAN
bridge control frames (notably LLDP, STP(BPDU), CDP, and VTP PDUs) trans-
parently across metro Ethernet networks which might otherwise terminate them.
One key application of L2PT is tunneling a customer’s STP domain across the
provider’s network, providing a single transparent STP domain across the cus-
tomer’s network. Without L2PT tunneling, the provider edge switches might at
best isolate segments of the customer’s network into separate STP domains,
and at worst join the customer’s STP domain with the provider’s STP domain.
L2PT works by re-writing the DA MAC of a received frame with a multicast MAC
address that is treated as a regular user address by intermediate switches in the
metro Ethernet network. On transmit a tunnel endpoint recognizes tunneled
frames and restores their original DA MAC. The L2PT protocol is not formally
standardized; it is industry prevalent and most major metro switch vendors
implement some form of it.
The L2PT function, whose purpose is to tunnel control frames through the data
stream using the L2PT protocol, should not be confused with the L2PT CPD fil-
ter, whose purpose is to filter L2PT protocol frames (e.g. encapsulated frames)
out of the data stream. L2PT should not be confused with the similarly named
Layer 2 Tunneling Protocol (L2TP).
L2PT has local significance at the UNI Access ports. Its operation is transparent
to the Metro Ethernet Network and the Customer Equipment (see Figure 12).
Figure 12: L2PT General Overview
L2PT Implementation
• L2PT is configured on a per port and per protocol basis

• It is bi-directional – operating on both receive and transmit frames on the

port.
• Only IEEE LLDP, 802.1D STP (BPDU) and Cisco CDP/VTP are supported
as protocols that may be tunneled in R5.4.1.
• L2PT includes the following procedures:
o
L2PT RX encapsulation: match protocol specific MAC DA and protocol
signature in the frame. Overwrite the MAC DA with L2PT Tunnel MAC.
o
L2PT TX decapsulation: match L2PT Tunnel MAC DA and protocol sig-
nature. Overwrite DA MAC with protocol’s inferred MAC DA.
• L2PT function procedures maintain statistics for encapsulated and decap-
sulated frames. Statistics are presented to the GUI as part of port PM his-
tory.
L2PT Protocols, Addresses and Signatures

• IEEE Protocol STP
o Protocol DA 01:80:C2:00:00:00, Bridge Group.
o Protocol signature: LLC STP specific DSAP/SSAP. Protocol ID field is
STP.
• Cisco Protocols (CDP and VTP)
o
Protocol DA 01:00:0C:CC:CC:CC, Cisco multicast
o
Protocol signature: LLC+SNAP, SNAP OUI (Cisco’s) and SNAP Type
o
CDP and VTP have different SNAP Types
• The LLDP
o
Protocol DA 01:80:C2:00:00:0E.
o
Protocol signature: Ethernet Type Field = 0x88CC
For each protocol (BPDU, LLDP, CDP, VTP) that the user wishes to tunnel, the
CPD disposition for that feature is set to “Pass Thru L2PT”. The default L2PT
tunnel MAC address is 01:00:0c:cd:cd:d0 and is user editable. The same L2PT
MAC Tunnel is used for all tunneled protocols.
Link Layer Discovery Protocol

Link Layer Discovery Protocol (LLDP) is a link layer protocol that operates
above the MAC layer. FSP 150CC-GE11x supports LLDP on physical ports.
This protocol facilitates a device on an 802 LAN to advertise the following infor-
mation about itself to its neighbors:
• Major capabilities provided by the device
• IEEE 802 LAN connection endpoint information
• Management address(es) which can be used to manage the advertised
device capabilities

PS
LLDP does not solicit information from the neighboring node.
Note
The above information advertised by a device is stored by the neighbors and

made available via management interfaces. The standard also supports a
SNMP MIB for a management system to configure/retrieve local and remote
system LLDP information.
• LLDP functionality includes:
o
LLDP frame transmission generating LLDP frames with supported TLVs
o
LLDP frame reception that involves frame recognition, frame validation
and frame processing
• LLDP management includes:
o
Configuration of LLDP local system information for LLDP frame trans-
mission
o
Retrieval of LLDP remote system information which is updated based
on LLDP frames received
LLDP Frame Format
LLDP frame is an Ethernet frame with destination MAC address, source MAC
address, Ethertype and LLDPDU.
Destination MAC address can be one of three standard IEEE 802.1 group MAC
addresses shown below:
• Nearest Bridge Group MAC Address: 01-80-C2-00-00-0E
• Nearest Non-TPMR Group MAC Address: 01-80-C2-00-00-03
• Nearest Customer Bridge Group MAC Address: 01-80-C2-00-00-00
Destination address used in generated LLDP frames depends on the scope of
propagation of the frames. The Nearest Bridge group MAC address is used if
the scope is limited to a single LAN which is limited to propagation of LLDP
frames across a link. The Nearest non-TPMR Bridge group MAC address is
used if the scope involves transmission of LLDP frames through Two-port MAC
Relays (TPMR) between two C-VLAN components, S-VLAN component or
802.1D Bridges. The Nearest Customer Bridge group MAC address is used if
the scope involves transmission of LLDP frames through TPMRs and S-VLAN
components between C-VLAN components or 802.1D Bridges. See the figure
below.

Figure 13: Scope of Group MAC Address
Nearest Customer Bridge
Customer Nearest Non-TPMR Customer

Nearest Nearest
Bridge
Bridge non- non-
S-VLAN S-VLAN Bridge
TPMR TPMR
Bridge Bridge TPMR
Bridge Bridge
Bridge
Nearest Nearest Nearest Nearest

Bridge Bridge Bridge Bridge
If LLDP transmit and/or receive is enabled on a port at least one group MAC
address and up to three allowed group MAC addresses can be configured.
These MAC addresses are used to transmit one or more LLDP frames each of
the configured MAC address. Also only the LLDP frames with configured group
MAC addresses are filtered.
Source MAC address shall be the sending port’s individual MAC address. LLDP
Ethertype is 0x88CC. LLDPDU is the payload of the LLDP frame which contains
the ordered list of mandatory TLVs followed by optional TLVs ending with End of
LLDPDU TLV.
LLDP Frame Transmission

LLDP transmission can be initiated in the following two ways:
• LLDP frame is initiated periodically based on user configurable interval
• LLDP frame is initiated when LLDP local system information changes
requiring a new value to be sent in the TLV
Typically LLDP transmission interval is multiple of the TTL. This prevents a sys-
tem’s information in the remote systems database from aging even if a few
LLDP frames are lost.
Anytime there are a series of changes in local system information, multiple
LLDP frames can be transmitted. The number of LLDP frame that can be sent
within an interval can be configured.
If LLDP frame transmission is enabled for a port, the LLDP group MAC
addresses used in transmitted LLDP frames can be configured.
LLDP Frame Reception

LLDP frame reception involves the following:
• LLDP frame filtering
• LLDP frame validation
• Updating the LLDP Remote System database

LLDP frame filtering is done in the FPGA the LLDP frames are filtered and for-
ward to the processor for frame validation and processing. LLDP is added to list
of L2CP filters supported. LLDP will behave like EFM-OAM from the L2CP per-
spective. There is an LLDP application level control per port which indicates
whether LLDP needs to be received and processed, so that the L2CP filter for
LLDP is set to PEER and if the application level control is not setup to receive
and process LLDP frames then the L2CP filter could be configured via the L2CP
interface to DISCARD or PASS-THRU. When PASS-THRU is provisioned the
EVC level L2CP filter decides if LLDP frames need to pass through the service
or discarded for the service.
Independent EVC Mapping

FSP 150CC-GE11x allows a flow to be associated with either Network Port One
or Network Port Two.To use this function, the Network Ports must be in non-pro-
tection mode (there is no Protection Group or LAG on the Network Ports). Set-
ting the Admin State of Network Port two to In-Service enables Independent
EVC Mapping.
When Independent EVC Mapping is enabled:
• The sum of CIR allocated on Network Port One and Two cannot exceed 1
Gbps.
• Network Port 2 supports:
o
VID-based up/down MEPs, Port-based down MEPs
o
ESA Reflectors
o
Management tunnels
o
ECPA/Loopbacks
o
Link Loss Forwarding (LLF).
o
Priority Mapping
o
PCP Encoding/Decoding
System Resource Rules and Limitations

Refer to the following table for rules and limitations when provisioning FSP
150CC-GE11x resources. Available traffic resources may be viewed by select-
ing the Resources tab of the NTE11x entity (see Figure 14).
Table 1: System Resource Rules and Limitations

Product
Resource
GE112 GE114x
Traffic
Network Port Interfaces 2 2
Access Port Interfaces 2 4
(3 if Network (5 if Network
Protection / LAG is Protection / LAG is
not used) not used)
LAG Groups 2 3

Table 1: System Resource Rules and Limitations (Continued)

Product
Resource
GE112 GE114x
Bandwidth configuration
64 kbps 64 kbps
increment
Maximum members per flow 64 64
Maximum ranges per flow 16 16
Total ranges per system 32 64
EVCs 16 32
Policers 128 255
Maximum number of queues
108 104
dedicated to user traffic
Total buffer space for traffic
32102 KByte 32102 KByte
queues
Queue configuration increment 1 kB 1 kB
ESA
Layer 2 Probes 16 32
Layer 3 Probes 10 10
Reflectors 6 6
CFM and Y.1731
MDs 44 70
MAs 44 70
Local MEPs 28 38
Remote MEPs 128 128
Concurrent LBM loopbacks
10 10
initiated
Outstanding LBMs 50 50
Management
Simultaneous Web sessions 5 5
Simultaneous telnet/SSH
3 3
sessions
Local User IDs 10 10
Remote TACACS+/RADIUS
3 3
servers
NTP servers 2 2
Management Tunnels 2 2
System ACL Entries 10 10

Figure 14: NTE11x Resources Tab
Power over Ethernet - GE114PH
Power over Ethernet (PoE) technology describes a system to pass electrical
power safely, along with data, on Ethernet cabling. The IEEE standard for PoE
requires category 5 cable or higher for high power levels, but can operate with
category 3 cable if less power is required. Power is supplied in common mode
over two or more of the differential pairs of wires found in the Ethernet cables.
PoE technology has helped increase the number of devices that can be con-
nected to network, i.e., CCTV cameras, Wireless LAN Access Points, and IP
Phones with advanced video conferencing features. Standard Ethernet distance
rules apply. The maximum cable length is 100 meters, or 333 feet (or twice the
distance if using a PoE repeater).
Figure 15: PoE Application Overview
Wireless LAN
VoIP Phone Network Camera
Access Point

Power over Ethernet (PoE) technology has two different methodologies:

• Power-Supplying Equipment (PSE)
• Powered devices (PDs)
The GE114PH works as an Endpoint PSE with 4 client ports supporting power
sourcing.
From a power perspective, IEEE 802.3at defines two types of PSEs:
• Type 1 (over two pairs) – The PSE can supply a maximum of 15.4W over a
voltage range of 44 to 57 VDC using Category 3 cabling or better. The PD
operation for Type 1 is a maximum of 13.0W over a voltage range between
37 to 57 VDC. This type provides support for legacy installations.
• Type 2 – The PSE can supply 30W (over two pairs) or 60W (over all four
pairs) over a voltage range of 50 to 57 VDC using Category 5 or better
cabling. The PD operation for Type 2 is a maximum of 25.5W over two pairs
or 51W over four pairs, both with a voltage range between 37 to 57 VDC.
The standard supports two alternatives for power injection:
• Alternative A, where power is transmitted (super-imposed) over data trans-
mission pairs 1/2 and 3/6.
• Alternative B, where power is transmitted over spare pairs 4/5 and 7/8.
The PD must be capable of receiving power regardless of which powering
scheme is used.
The PD negotiates a power class during the time of initial connection. To pre-
vent damage to non-PoE devices, all PDs must include a 25 kΩ resistor across
powered pairs to allow for detection by the PSE. This scheme also allows the
PSE to detect when a PD is disconnected from the network. The detection sig-
nature is visible by both Alternative A and Alternative B PSEs.
During link power-up, after detect a PD requesting power, the PSE must deter-
mine the power classification of the PD (basically how much power must be sup-
plied to the PD). The standard provides two mechanisms for managing power
supplied to the PD: physical layer or data link-layer classification. In release
R5.4, the GE114PH supports Physical Layer Classification. Physical layer clas-
sification uses the link’s cable and PD electrical characteristics to determine
which power class to assign the PD (see IEEE 802.3at-2009 33.2 for details).
The total power output over PSE varies with the PSU type:
• 120W power output is supported with the 180W PSUs inserted.
• 31W power output is supported with the 60W PSU inserted.
Split Horizon Group (GE114x)

The Split Horizon Group (SHG) feature allows multi-point connectivity to Access
Flows or Network Flows utilizing MAC learning, MAC forwarding and flushing of
the Forwarding/Filtering Database (FDB).
Multi-point connectivity defined for a Network Interface can be an SHG, ERP or
both. Configuring an Access Flow with a SHG or ERP Network Interface creates
frame forwarding capability between the Access Interface and both Network
Ports. This duplicates certain physical entities in the system that are necessary

to identify membership, tag translation, Bandwidth Profile (BWP), N2A policers,

A2N shapers independently for each network port. The configuration informa-
tion is duplicated for each network port entity; and separate PM stats are main-
tained for each Network Port entity (e.g., a Flow provisioned with a ERP
Network Interface will have separate PM stats for Network Port 1 shapers and
Network Port 2 shapers).
Multi-point connectivity defined for an Access Interface can be an SHG. Config-
uring an Access Flow with an SHG Access Interface allows for multiple Access
Flows to be grouped in a single MAC forwarding domain. The split-horizon func-
tionality is maintained so frame forwarding cannot occur between Access Ports.
But the frames from multiple ports can share the same membership and tagging
treatment while be forwarded to different ports based on MAC learning.
See the following figure.
Figure 16: Split Horizon Group Application Example
RNC
RNC
RNC
RNC
Split
Horizon
Group VPLS over IP/MPLS
Core Network w/
Full mesh connectivity
For more details regarding SHG functionality, see the FSP 150CC-GE11x Tech-
nical Descriptions document.
Ethernet-Link Management Interface (E-LMI)

The E-LMI protocol is specified in MEF 16. The protocol is based on ITU-T
Q.933, X.36 and FR-LMI implementation agreement document. The E-LMI pro-
tocol and procedures can be used for enabling auto configuration of the CE
device and providing UNI and EVC status information to the CE device. The
E-LMI protocol has a local significance at the UNI between the Metro Ethernet
Network (MEN) and the CE.
Figure 17: E-LMI Protocol

The E-LMI includes the following procedures:

• Notification to the CE of the addition of an EVC
• Notification to the CE of the deletion of an EVC
• Notification to the CE of the availability state of a configured EVC
o
Active
o
Not Active
o
Partially Active (applicable for Multipoint-to-Multipoint EVCs)
• Communication of UNI and EVC attributes to the CE
The GE11x products may be deployed with either an Access Port facing the CE,
or a Network Port facing the CE; therefore the feature is required for both port
types.
E-LMI feature content overview:
• MEF16 UNI-N functions are supported for ELMI; UNI-C functions are not
supported
• E-LMI can be configured on Network or Access ports
• ELMI is not supported on LAG logical ports or physical ports within a LAG
• E-LMI is not supported on Network Ports in a protection group (1+1 or
Dual-Active Receive)
• The ELMI EVC status for a flow is determined by the defects detected by a
VID-based UP MEP with a primary VID that matches the flow (linkage
between flow and MEP is the same as Unavailable Seconds)
• DOWN MEP (untagged or VID) do not contribute to ELMI EVC status.
• E-LMI is included in L2CPD as a separate protocol
• ELMI stats are rollover counts and not binned
• All ELMI Mandatory Information Elements are supported, except for the
Bandwidth Profile (for both UNI and EVC)
Timing and Synchronization

The GE114S/GE114SH are equipped with internal clocks with an accuracy of
+/-4ppm and the performance in hold-over mode meets the requirements identi-
fied in ITU-T G.8262 Option 1.
Synchronous Ethernet
The GE114S/GE114SH supports Synchronous Ethernet according to ITU-T
G.8261 for frequency distribution over Ethernet networks, and can use any Net-
work or Access Port, or an E1 or T1 BITS clock.
Ethernet interfaces can be configured in synchronous operation mode or
non-synchronous operation mode. Synchronous operation mode can be
enabled or disabled on a per port basis. Default is non-synchronous operation
mode.
In synchronous operation mode, in the receive direction, the port is able to
recover the clock from the incoming signal. This recovered clock provides the

stable reference to the system clock from which the transmit clock for ports is
derived. Ports can be enabled to process the Ethernet Synchronization Messag-
ing Channel (ESMC) and extract the encoded Synchronization Status Message
Quality Level (SSM-QL) value. In the transmit direction, ports are locked to a
common clock derived from the system clock and can be enabled to insert the
ESMC channel with the appropriate SSM-QL value.
In non-synchronous operation mode, in the receive direction, the port’s recov-
ered clock is not used by the system clock and the port does not terminate the
ESMC channel. In the transmit direction, the port may be locked to the system
clock (which is either synchronized to another reference clock or is free running)
but does not generate an ESMC channel.
System Clock Reference

The system clock on the GE114S/GE114SH can be synchronized to one of sev-
eral timing references:
• the recovered clock of an Ethernet port operating in Synchronous Ethernet
mode
• a PTP Telecom Slave Clock with Sync-E mode enabled, using the Telecom
Slave as a Sync Reference
• an external clock provided on the Building Integrated Timing Service (BITS)
input port
• an internal crystal oscillator
The GE114S/GE114SH feature BITS IN and BITS OUT ports. The BITS ports
are presented via RJ48 connectors.
Synchronous Ethernet interfaces and the BITS IN port can be selected as syn-
chronization sources and can be assigned an expected SSM-QL value.
If the selected synchronization input(s) fails, the GE114S/GE114SH product
automatically switches either to holdover or free-running. Holdover is used if the
internal clock was locked to the reference. The accuracy of the internal clock is
+/-4ppm and the performance in hold-over mode meets the requirements identi-
fied in ITU-T G.8262 Option 1. Free-running is used if the internal clock was not
locked to the selected reference. The switchover can occur as soon as the fault
condition is detected or after a configurable hold-over timer has elapsed. Syn-
chronization source switchover can be triggered by physical link defects (LoS)
or changes in the received quality level (SSM-QL).
The BITS output port can feed legacy devices or synchronization equipment
such as SSUs or SASEs. The BITS OUT port can be assigned a SSM-QL.
In the diagram below a GE114SH distributes the frequency reference to a leg-
acy base station via BITS output port and to a new generation base station via a
Sync-E interface.

Figure 18: Frequency Distribution via BITS Out Port and Sync-E Interface
Packet Based Network
Sync-E T1/E1
Office A
3G 2G
If the synchronization quality of the BITS output port falls below the configured
SSM-QL value, the port can be switched off (squelched).
Figure 19: BITS Output Port Off
Packet Based Network
3G 2G
Precision Timing Protocol (PTP) -

GE114S/GE114SH
Generic synchronization distribution consists of the recovery and distribution of
timing to and from a variety of network elements and interface types.
Historically, networks are synchronized by distributing frequency over the

physical layer of the transport media (e.g. fiber optic cable for SDH, SONET,
and SyncE, or twisted pair copper cable for DS1/E1). However, as mobile
networks and services grow in sophistication and complexity, the ability to
distribute precise time (also referred to as phase) through the network is
required. NTP provides time distribution; however, it does not satisfy the time
accuracy and precision requirements for next generation mobile networks.
IEEE 1588-2008 (1588v2) defines the Precision Time Protocol (PTP) which is
intended for use in high accuracy time and frequency synchronization
applications. PTP is a layer 5 protocol which can be transported over a variety of
lower-layer packet technologies (e.g. PTP/UDP/IPv4/ENET,
PTP/UDP/IPv6/ENET, PTP/ENET, etc.). It supports both unicast and multicast
messaging, and provides message formats for synchronization distribution,
delay estimation, signaling, and management purposes.
The PTP protocol enables accurate time transfer between two entities (clocks)
by transporting 80-bit timestamps in time-critical packets. Each timestamp rep-
resents the time at which the packet was sent and has a 1 nanosecond granu-
larity. Through the use of the CorrectionField in the PTP header, each
timestamp can support sub-nanosecond granularity. The periodic transmission
of messages is the basis for frequency recovery, while the distribution of the
timestamp values allows for accurate phase/time recovery.
Precision Time Protocol (PTP) is a packet based method dedicated to the distri-
bution of time and/or frequency over packet switched networks (PSNs). It is
based on a master-slave relationship between the time sources and their time
recipients. A time source (herein referred to as a master, Grand Master, master
clock, or Ordinary Clock-Master (OC-M)), distributes its time and frequency to
downstream nodes (referred to as slaves, slave clocks, Slave-Only Ordinary
Clocks (SOOC) via PTP messages. Since the transport mechanism is
packet-based, each intermediate node (e.g. router, switch, aggregation NE,
etc.) between the master and slave clocks introduces packet delay variation
(PDV) in the transport of the PTP messages. This creates uncertainty and error
in a slave clock’s recovered time and frequency.
The Grandmaster is the primary time reference source in the packet-based syn-
chronization network. It is equivalent to a PRC/PRS clock in a traditional fre-
quency-based synchronization network. For redundancy, more than one
Grandmaster exists within the same network time domain. An SOOC is the
recipient of the timing information and synchronizes to the Grandmaster to
within a specified accuracy/tolerance. For current mobile backhaul applications,
Slave Clock accuracy is currently required to be within ±1.5µs; however, ±1.0µs
has been accepted as the industry requirement with a future target of ±200ns for
MIMO applications.
To minimize the effects of PDV, 1588v2 defines two additional clock types, a
Boundary Clock, and a Transparent Clock, to account for the variable packet
delay incurred by PTP messages while in transit from the master to the slave.
A Boundary Clock is typically a multi-port device residing between an upstream
master and one or more Slave Clocks. A Boundary Clock is similar to an SSU or
SEC in SDH, and provides a timing boundary, or partition, between the master
and slave clocks. A Boundary Clock terminates the PTP messages received
from an upstream master clock, recovers the time and/or frequency based on
the received PTP messages, and generates new PTP message flows to down-

stream slave clocks based on its recovered version of the upstream master
time/frequency.
A Transparent Clock does not participate in the master/slave hierarchy, but
instead, measures the residence time for each PTP event message; i.e. it mea-
sures the time a PTP event message spends in transit through the Transparent
Clock, or more specifically, the time between the ingress point and the egress
point in the node. A Slave Clock uses the residence times to account for the
variable delay (i.e. queuing delay) incurred by a PTP event message while in
transit through the network.
1588v2 defines the Precision Time Protocol (PTP) for use in applications requir-
ing highly accurate time/phase synchronization. The PTP protocol involves the
transmission of messages containing accurate timestamps, with each time-
stamp representing the time at which the message was sent. The repeated
transmission of messages provides the means for frequency recovery, and
when combined with the timestamps embedded within the messages, accurate
time/phase is also recovered.
The performance achievable by the PTP protocol is dependent on the network
environment in which it is operating and the use and performance of the various
clock types (e.g. OC, BC, TC) within the network. 1588v2 doesn’t define the per-
formance criteria for recovering the clock (time and frequency) from a received
PTP message flow; however, ITU-T is working on such requirements for tele-
communications applications.
To support the accurate transport and recovery of time across a network,

1588v2 defines the following clock types to be used to transport time/phase:
• Ordinary Clock
• Boundary Clock
• Master Clock
• Transparent Clock
While the standard defines these as “clocks”, they are actually logical functions
that recover, distribute, and/or support synchronization.
PTP supports both unicast and multicast operation, and also defines support for
two clock modes: one-step clock mode and two-step clock mode.
The one-step mode involves embedding the timestamp associated with a mes-
sage within the message itself, while the two-step mode requires the transmis-
sion of an additional message for transporting the timestamp of the original
message.The implementation in the GE114S/GE114SH products is the
one-step mode.
Because of their logical (versus physical) nature, the FSP150CC products asso-
ciate each E2E TC function with a specific service flow. The associated service
flow may or may not be transporting user traffic along with PTP messages. As a
result, each GE114S/GE114SH product may support many simultaneous E2E
TC functions.
The following figure shows an example application involving an End-to-End
(E2E) Transparent Clock (TC).

Figure 20: OC-Master, OC-Slave with TC Interconnect
Synchronous networks rely on accurate distribution of frequency in order to opti-

mize transmission and TDM cross-connection. In contrast, packet based net-
works and services are highly buffered and do not require accurate timing for
their operation. If packet based networks are used to support circuit emulation
services, stable frequency is needed at both ends of the service. Stable fre-
quency from one end has to be transported on the packet network and be recov-
ered on the other side. Other applications include wireless access technologies
like LTE, WIMAX etc., where the air interfaces have stringent synchronization
requirements. Synchronous Ethernet was developed by ITU-T for physical layer
frequency distribution. But Synchronous Ethernet may not be a viable option in
all cases as it requires transceivers that are capable of extracting accurate fre-
quency from the received signal and hence requires different hardware. This
also adds cost to the network devices.
1588v2 defines mechanisms to accurately transfer time between two clocks. A
1588v2 slave computes the time based on a precise timestamp from the master
and the delay between master and slave. The accuracy of the time at the slave
depends on the accuracy of delay measurement between master and slave.
The delay is calculated by halving the round trip time between the master and
slave. To increase accuracy, the PTP protocol separates the link level delay
which is symmetric and if needed adjusts for fixed asymmetry and variable
delay which is mostly within the devices. To improve the accuracy of at the slave
all the timestamps in PTP event messages are recorded as close as possible to
the physical interface in ingress and egress directions. To minimize delay asym-
metry between Ordinary Clock Master (OC-M) and Ordinary Clock Slave
(OC-S), each device between the OC-M and OC-S should provide either a
Transparent Clock (TC) if fan-out of timing is not required or a Boundary Clock
(BC) if fan-out is required. TC calculations eliminate inaccuracy due to delay
asymmetry in a device in either direction by calculating residence time in the
device and record it in the PTP messages. BC involves at least one slave port
and one or more master ports where PTP messages are terminated and time-
stamp data is recovered by the slave function and the master ports generate
new streams of PTP messages using the time recovered by the slave function.

ITU-T developed G.8265 and G.8265.1 to specify transport of frequency over a

packet network using packet-based mechanisms without physical layer timing.
Repeated transmission of PTP packets allows recovery of frequency.
The initial version of PTP as defined in IEEE 1588-2002 (1588v1) was devel-
oped for industrial automation. The second version, IEEE 1588-2008 was
extended to be applicable to other applications such as telecom. 1588v2 defines
the concept of PTP profiles including required options, prohibited options and
ranges/defaults of configurable attributes.
ITU-T G.8265.1 defines a PTP profile for telecom applications for ordinary
clocks using PTP over UDP in a unicast environment. ITU-T G.8265.1 only
defines recovery of frequency and does not cover phase or time-of-day align-
ment. For accurate frequency recovery it is ideal to receive the PTP packets
with precise time stamps with minimum packet delay variation (PDV). It is not
practical in a packet network to expect PTP packets without PDV and this PDV
introduces inaccuracy in recovered frequency. The use of a recovery algorithm
minimizes the impact of PDV on the recovered frequency.
G.8265 and G.8265.1 also define protection schemes for synchronization in
telecom networks. Synchronization in telecom networks is designed and config-
ured in a fixed arrangement. Protection is based on selection between multiple
master clocks based on received QL and priority.
In 1588v2 each PTP port in each ordinary clock and boundary clock runs an
independent state machine. Using the Best Master Clock Algorithm (BMCA),
contents of all Announce messages received on the port and the data sets of the
OC or BC clock data sets are analyzed to determine the state of each port of the
clock. This approach makes the timing network dynamic where it is reconfigur-
ing itself by electing a master depending on factors like clock class, clock accu-
racy and priority of the available timing sources. This is not suitable for telecom
networks.
To support selection between multiple master clocks, ITU-T G.8265.1 defines
Telecom Slave which is the entity that recovers frequency based on timestamps
from the selected master clock. An entity called the Slave Only Ordinary Clock
(SOOC) is a 1588v2 OC-S that gets its PTP packets from a Grand Master (GM).
For protection, more than one SOOC is defined, each receiving timing from a
different GM. Based on the clock class in Announce messages (QL), priority and
Packet Timing Signal Fail (PTSF) a master is selected. PTSF is based on
PTSF-lossSync, PTSF-lossAnnounce or PTSF-unusable. PTSF-unusable is
undefined in G.8265.1 and this could be used to indicate conditions such as the
high PDV that could result in inaccurate clock recovery. Today G.8265.1 defines
selection only based on the quality of the GM, priority and lack of PTP mes-
sages required for clock recovery and does not base selection on network qual-
ity between GM and SOOC. This is an area for future improvement.
The object model for various PTP entities is shown as below:

Figure 21: PTP Object Model
Terminologies and definitions:
• Timing Domain: It is a source of timing that provides frequency and/or
phase.
• SYNC Timing Domain: It provides only frequency and it involves clock qual-
ification and clock selection. For now all the devices shall support one
SYNC Timing Domain which is the System SYNC Timing Domain. SYNC
Timing Domain generally involves selection from multiple SYNC references.
These SYNC references can be Sync-E from Ethernet ports, other forms of
frequency inputs like 10MHz, BITS or PTP recovered frequency.
• PTP Timing Domain: involves a Telecom Slave that selects a PTP stream
from one or more Slave Only Ordinary Clocks (SOOC) and recovers fre-
quency and phase from it.
• Currently the system supports only a System SYNC Timing Domain and
one PTP Timing Domain. In the future some devices will support up to 4
PTP Timing Domains.
• System Clock: the frequency output by the System SYNC Timing Domain
which is one of the SYNC references of SYNC Entity.
• SYNC Entity/Object: an abstraction of the System SYNC Timing Domain
and is used interchangeably with System SYNC Timing Domain.
The GE114S/GE114SH implementation follows IEEE 1588v2 and ITU
G.8265.1. 1588v1 is not supported.
The following figure shows various clock interface functions and interconnec-
tions.

Figure 22: Clock Interface Functions and Interconnections
Ethernet Port Ethernet Port

(Net/Acc) Rx (Net/Acc) Tx
Reference Selector
SYNC-1-1-1-1
BITS-IN BITS-OUT
Source Selector CLK-1-1-1-1

Telecom Slave
PPS-1-1-1-1
TOD-1-1-1-1
Source Selector
Reference Selector
GPS TIME
CLOCK-1-1-1-1
System
NTP Time of Day
Local

ADVA’s Etherjack® Technology

Most carriers are delivering Ethernet based services to their small to medium
business customers. Ethernet has been the physical medium of choice for
decades in the enterprise environment, and forward looking carriers are offering
Ethernet services as a way to simplify their customer’s networking challenges.
Unfortunately, Ethernet was designed as a Local Area Network (LAN) solution
and is not well suited for carrier’s Wide Area Network (WAN) environment.
While traditional data services such as frame relay and private line T1/T3s offer
many levels of performance monitoring and fault isolation, Ethernet has a lim-
ited set of parameters for these tasks. In addition, traditional carrier services
have well-defined hand-off specifications and demarcation points which do not
exist in the Ethernet world. ADVA Optical Networking’s FSP 150CC adds Ether-
net capability to first generation transport systems and can also add Virtual LAN
(VLAN) support to second generation systems.
In addition to providing Ethernet access and Ethernet media conversion, ADVA
Optical Networking’s Etherjack® technology provides carriers with an intelligent
Ethernet demarcation device that is aligned with emerging Ethernet OAM stan-
dards for transport, connectivity and services from IEEE, MEF and ITU stan-
dards bodies.
ADVA Optical Networking's patented Etherjack® technology allows carriers to
deploy profitable Ethernet services by providing carrier grade remote monitoring
and diagnosis for Ethernet based services. This capability is analogous to the
Smartjack™ capability used as a demarcation point for traditional T1 services.
Figure 23: Demarcation for Traditional T1 Services
Carrier Network Customer Network
T1 V.35
ADM or Smartjack or Switch/Router
Modem CSU/DSU
While early data services were delivered blind, without demarcation capability,
carriers quickly determined that remote management was critical to providing
value-added services to their customers while reducing truck rolls and the
expense of diagnosing an Ethernet service problem.
ADVA Optical Networking’s Etherjack® technology includes performance moni-
toring, remote failure indications (e.g., dying gasp), remote loopbacks, cable
integrity testing and Etherjack Service Assurance (ESA) and Connectivity Fault
Management (CFM) to provide diagnostics through the carrier network and on
both sides of the demarcation point (see the following figure).

Figure 24: Etherjack Demarcation for Ethernet Services
Carrier Network Customer Network

PSU1 PS U2 MG MT F S P 15 0 C C
LA N BITS IN
LK R T LK R T L KRT Etherjack ®
1
N ET AC T
A CC
STA 2 1 GE201
2
R S - 2 32 B ITS O U T ACCES S 1 N E T W O RK 2
100/1000BT 10/100/1000BT
ADM, FSP 150CC Switch/Router
Modem or
Media converter
Using Etherjack® technology, the FSP 150CC monitors the performance of

Ethernet services and provides carriers with advance visibility of performance
degradation (RMON Etherstats) before an outage occurs. The Ethernet perfor-
mance data is presented in 15 minute bins just like traditional T1 performance
data, and can provide indication of whether a fault is a one time event, or an
on-going problem.
When a fault occurs, the FSP 150CC-GE11x provides fault isolation and diag-
nosis of both the carrier network as well as the final Cat5 connection to the cus-
tomer premise equipment (CPE). It enables a carrier to diagnose Ethernet cable
faults to determine if the customer's Cat5 cable is open-circuit, short-circuit or
properly terminated.
When Etherjack® locates a cable fault; it will provide the distance from an FSP
150CC-GE11x Ethernet port to the cable fault to the nearest meter. In addition,
the FSP 150CC-GE11x can detect if an Ethernet cross-over cable has been
improperly installed on the LAN port, and re-configure its port to compensate for
the improper wiring. These unique isolation and diagnosis capabilities can dra-
matically reduce the quantity and duration of truck rolls necessary to maintain
Ethernet services.
Etherjack® Performance Monitoring

Etherjack® Performance Monitoring allows carriers to detect and react to poten-
tial failures prior to a customer outage. In addition to providing traditional SNMP
MIB Etherstats, Etherjack provides GR-253/GR-820 style PM parameters and
features similar to those found on traditional SONET and T1 services. This
allows Etherjack Service Assurance to be integrated into a carrier’s existing Ser-
vice Assurance infrastructure. Etherjack Performance Monitoring supports
threshold setting and automatic TCA message/trap generation. Current and his-
tory PM bins provide a continuous record of service performance, allowing for
accurate SLA conformance statements. See the following figure for an example
of a summary view of PM counts displayed for an Access Port in ADVA Optical
Networking’s on-board eVision Web Browser Management Tool.
For additional information on Etherjack® Performance Monitoring using eVision,
see Etherjack Test Procedures and Performance Monitoring on p. 459. Refer to
Performance Monitoring Settings on p. 717 for monitored types and default
Threshold Crossing Alert (TCA) settings.

Figure 25: Performance Monitoring Summary View
Etherjack® Diagnostics
Etherjack® diagnostics provide a suite of tests to isolate faults between carrier
equipment, customer equipment and Ethernet cables:
• Ethernet EFM loopback to test the traffic from a far-end over the link
• Ethernet LAN cable diagnostics to detect open-circuit, short-circuit condi-
tions
• Manual restart of Ethernet auto-negotiation sequences (to detect one-way
failures and MDIX conditions)
The FSP 150CC-GE11x can monitor the status of a physical Ethernet link to
determine whether the link is properly terminated, improperly terminated,
open-circuit or short-circuit. See Figure 26 for an example of Etherjack diagnos-
tics results using the eVision Web Browser Management Tool. For additional
information on Etherjack Diagnostics using eVision, see Etherjack® Diagnostics
on p. 462.

Figure 26: Etherjack® Diagnostic Results Using eVision

Cable Length Benchmark

An addition to Etherjack® diagnostics results is the cable length benchmark fea-
ture. This feature provides a means to store up to 5 cable segment lengths
during the installation process. Each cable segment can be named with a text
string to describe the physical location of each segment. If a subsequent Ether-
jack diagnostic detects an open circuit at one of the stored segments, eVision
will highlight the location name of the faulty segment, and the test operator can
quickly determine if the fault is located at a particular patch panel, possibly pre-
venting the need to dispatch repair personnel.
See Figure 27 for an example of Etherjack diagnostics results highlighting the
open segment location. For additional information on Cable Length Benchmark
using eVision, see Cable Length Benchmarks on p. 466.

Figure 27: Faulty Segment Identified Using Cable Length Benchmark
Etherjack® Service Assurance
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 implements standards-based approaches that
are currently in progress.
SLA monitoring is a key success factor for carriers offering premium Ethernet
services. Sophisticated enterprise customers demand SLA guarantees in their
service contracts. Carriers must monitor the performance of a connection to
determine if the agreement is being satisfied.
The FSP 150CC offers built-in SLA monitoring via the ESA feature set. The ESA
feature provides Ethernet service providers with the ability to monitor individual
customer SLAs without the need to install any extra monitoring and reporting
equipment. ESA test results are displayed in tabular or chart format using the
eVision Web Browser Management Tool. See Figure 28 for an example of ESA
test results in chart form.

Figure 28: ESA Test Results in Chart Format
Network Performance
Network performance is measured and reported in terms of the experience a
packet encounters as it traverses a network. This performance is typically
expressed in terms of the following four parameters:
• Delay
• Delay Variation (Jitter)
• Packet Loss
• Network Availability
A Service Level Agreement for a service hosted on a network defines the perfor-
mance expectations of the network in terms of these four parameters.
Delay Delay, often referred to as latency, is the time delay experienced by a packet in
traversing the network from the source to the destination.
Controlling congestion points is just one means of ensuring consistent network
throughput and predictable network delay. Delay can cause significant QoS
issues for sensitive services such as voice and video. Voice and video over IP
can compensate for minor delays across a network, but once a threshold is
exceeded, the quality of the service degrades exponentially. Network delays are
typically caused by queueing points in the network. The more queues which a
packet encounters, the greater is the potential for delay. The key to low latency
QoS is to minimize the amount of queueing which a packet encounters when
transiting the network.
Delay Variation Jitter is the variation in the delay of transmission of packets from source to des-
tination. Some applications are more sensitive to jitter than others. Voice and
video applications, for instance, cannot tolerate excessive jitter. The same tech-
niques and mechanisms employed to manage delay are employed to bound the
jitter across a network. With small queue sizes and committed bandwidths, the
maximum amount of jitter which a service will experience can be computed and
bounded. With appropriate tuning, a network can easily be engineered to meet
the strict jitter tolerances of jitter-sensitive traffic.

Packet Loss Packet loss refers to the number of packets of a particular class which are
received by the network but are never delivered to the intended destination.
Traffic loss is often expressed as a ratio of: (#packets not delivered at destina-
tion) / (total #packets received at source).
Packet loss can occur due to physical errors on network links, hardware faults in
network equipment, and network congestion. Traffic loss can also be experi-
enced if a service transmits more bandwidth into the network than its SLA con-
tract specifies. Rate limiting discards packets which exceed the guaranteed
bandwidth or burst size for a service. Congestion management mechanisms,
such as Random Early Discard (RED), can be employed to reduce congestion
within a network. Such algorithms randomly discard packets once the network
nears congestion. This practice effectively limits the size of traffic bursts pre-
sented to the network.
An application’s response to packet loss is dependent on the application type.
Certain applications respond by ignoring lost packets. VoIP and video applica-
tions, for instance, recover from a single lost packet by re-using the last packet
received. Other applications, such as E-mail, file transfer and web applications
are intolerant to packet loss. Such applications often rely on transport layer pro-
tocols, such as TCP/IP, to retransmit lost packets. Application layer protocols
may also guard against packet loss using retry methods.
Network Network availability refers to the percentage of time that a network is capable of
Availability transporting packets between a source port and destination port. While a net-
work may be capable of physically transporting packets presented to it, it may
not always meet the QoS specifications for all traffic classes. Thus, we extend
the definition of network availability as the percentage of time that a network is
able to transport packets while meeting the QoS requirements for each traffic
class supported by the network.
Failures which completely inhibit the transmission of packets are easy to detect
and quantify with simple metrics, but partial failures or service degrades which
impact different traffic types in different ways require QoS specific network
probes and metrics.
End-to-End Performance Monitoring

ESA enables true end-to-end performance monitoring (see Figure 29). In con-
trast, some Ethernet service providers monitor the performance of the core net-
work only and use those results to prepare customer reports and to monitor
SLAs.
By deploying the FSP 150CC at the customer premise, true end-to-end service
monitoring is enabled. This capability is particularly critical if the last mile links to
the customer premise are sub-Ethernet rate, such as DS3 (43 Mbps).
End-to-end monitoring provides the most accurate monitoring of Ethernet con-
nection performance.

Figure 29: End-to-End SLA Verification

Customer Premise Customer Premise
10/100BT
10/100BT
IP Network
Demarcation Device Demarcation Device
Link Trunk Link
Etherjack Service Assurance

End to End SLA Verification
ESA Operation
The Etherjack Service Assurance (ESA) feature provides real-time monitoring of
the four major network performance metrics (delay, delay variation, packet loss
and network availability) for an Ethernet circuit.
ESA operates by injecting test traffic into a live Ethernet connection and moni-
toring the delay, jitter and loss of the test traffic as it transits the connection. Net-
work availability is then computed from the measured parameters.
ESA uses a special Probe object to inject test traffic into an Ethernet connec-
tion. This test traffic is targeted to another object called a Reflector. See the fol-
lowing figure. There are two types of Reflectors. The first Reflector type is a
simple Reflector which simply “echoes” the test traffic back to the Probe. The
Probe object then calculates round-trip delay, jitter and loss. The second type of
Reflector recognizes the injected test traffic and inserts timestamps into the test
traffic before reflecting it back to the Probe. This allows the Probe to compute
one-way delay and jitter.
Figure 30: ESA Probes and Reflectors
Responder
Responder Probe
10/100BT 10/100BT
IP Network
IP Network
FSP 150CC FSP 150CC
Customer Customer
Premise Premise
Optionally, when defining a Probe the user can specify the probe protocol as
Y.1731 LM/DM and use previously defined CFM MEPs (see Ethernet Connec-
tivity Fault Management on p. 71) in which case a Reflector is not required since
MEPs respond to LMMs (Loss Measurement Messages) and DMMs (Delay
Measurement Messages) by definition.
A Probe can support up to 10 active monitoring sessions each. A Reflector can
terminate up to 30 sessions. ESA utilizes IP layer frames to conduct perfor-
mance monitoring. Probes and Reflectors are assigned individual IP addresses

to enable service monitoring across layer 2 and 3 networks. The FSP

150CC-GE11x supports up to 6 layer 3 probes and reflectors and up to 16
(GE112) /32 (GE114x) layer 2 probes.
Standard and Enhanced Reporting

Both UDP Echo and ICMP Echo packets are employed to measure connection
performance. Because of this standard IP layer implementation, a Reflector can
in fact be any network device that has an IP address and supports UDP echo.
UDP echo provides support for standard reporting. The following round-trip
measurements are available for Standard Reporting:
• Round trip delay
The ICMP echo packet enables enhanced reporting which includes one-way
measurements. The UDP echo packet allows for a custom packet payload. By
placing timestamp data in the packet payload, a Probe / Reflector pair can
determine one-way performance. In addition to standard reporting measure-
ments, Enhanced Reporting also includes the following parameters:
• One way delay
• One way jitter
To perform the one-way measurement, the Probe inserts a timestamp into the
ICMP echo packet as it sends the packet. When the Reflector receives the
packet, it places a second timestamp in the packet indicating when the packet
was received. When the Reflector sends the packet back toward the Probe, it
inserts a third timestamp indicating time of transmission. When the Probe
receives the original packet, it again timestamps the packet as it is received.
The Probe then uses the four timestamps to calculate the one-way transmission
time in both directions (Probe to Reflector and Reflector to Probe). This opera-
tion is shown in Figure 31.

Figure 31: ESA One-Way Measurements

A critical aspect of one-way measurements requires that the system clocks of

the Reflector and the Probe units be synchronized to a common source. The
FSP 150CC utilizes the Simple Network Time Protocol (SNTP) to synchronize
the clocks of Probes and Reflectors. NTP/SNTP timing distribution protocols
provide timing accuracy of about 1 msec. More accurate timing distribution
mechanisms are also being investigated.
ESA Probe - Injector Operation

The ESA Packet Generator builds the ESA frame based on user configurable
information such as: packet size, destination IP, VLAN tag. Prior to injecting the
frame into the service flow, it inserts a timestamp. From the system perspective,
the frame will appear to be coming from the customer service port, hence ESA
frames will receive the same frame processing as customer frames. This
ensures true end-to-end monitoring of performance and yields the most accu-
rate results. This operation is shown in Figure 32.

Figure 32: ESA Probe - Injector Operation
ESA Probe - Monitor Operation

The ESA packets will follow the same traffic path through the device as the cus-
tomer traffic. Just prior to being sent out the customer port, the ESA filter will
determine if the packet belongs to one of the active ESA sessions and diverts
the packet to the Network Processor queue. Once received by the ESA Packet
Processor, the receive timestamp will be inserted. The ESA Packet Processor
will then process the packet and update the appropriate metrics based on the
information in the packet. This operation is shown in the following figure.
Figure 33: ESA Probe - Monitor Operation
Reflector Operation
The ESA packets follow the same traffic path through the device as customer
traffic. Just prior to being sent to the customer port, if the packet matches the
ESA Filter criteria, it is diverted to the ESA Packet Processor. At the ESA

Packet Processor, if the packet is an ICMP timestamp request, the Receive

timestamp is inserted. The echo/timestamp request packet is then processed
into an echo/timestamp reply. Just prior to leaving the ESA Packet Processor,
the Send Timestamp is inserted.
Figure 34: ESA Reflector Operation

ESA Test Configuration and Scheduling

An operator can choose to continuously monitor an Ethernet connection by
scheduling ESA tests to run automatically at fixed intervals. Test results are
then collected in monitoring bins and can be retrieved asynchronously. Addition-
ally, an operator can configure the system to autonomously report ESA perfor-
mance violations in “real time” through the use of performance thresholds. For
ESA operation using eVision, see ESA Provisioning and Operation on p. 484.
Ethernet Connectivity Fault Management

The expansion of Ethernet technology into the domain of service providers pro-
vides an additional challenge to maintaining link uptime, where timeliness in iso-
lating and responding to failures is crucial to daily operation.
Customers contract with service providers for end-to-end Ethernet service, and
service providers may sub-contract with operators to provide equipment and
networks (see Figure 35). These constituent networks belong to distinct organi-
zations or departments, which are substantially larger, are more complex, and
have a wider user base compared to enterprise networks.
Ethernet Connectivity Fault Management (CFM) is an emerging set of standards
(ITU-T Y.1731, IEEE 802.1ag) aimed at enhancing Ethernet Service Operation,
Administration and Management (OAM) capabilities by providing proactive
end-to-end connectivity monitoring, fault verification and fault isolation for large
Ethernet MANs and WANs.

Figure 35: Provider-Subscriber Relationship
MEP
MIP
The CFM features included in this release of the FSP 150CC are:
• Configure Maintenance Domains (MD)
• Configure Maintenance Association Networks (MANET)
• Configure and manage Maintenance Association Component assignments
(MACOMP)
• Configure and manage Maintenance End Points (MEP)
• Configure and manage Maintenance Intermediate Points (MIP)
• Transmit and receive Continuity Check Messages (CCM)
• Initiate transmission of and receive responses for Link Trace Messages and
Loopback Messages (LTM, LBM)
• Fault Monitoring (ETH-AIS)
• Detect and raise CFM related alarms
• Performance Monitoring
o
Loss Measurement (LM)
o
Delay Measurement (DM)
o
Delay Variance Measurement
CFM Overview
The managed network in the context of CFM consists of Maintenance Domains
(MDs), Maintenance Domain levels, Maintenance Association Networks
(MANETs), and Maintenance Association Component assignments
(MACOMPs). An MANET consists of a set of Maintenance End Points (MEPs)
and Maintenance Intermediate Points (MIPs) that have the same MA ID and MD
level.
CFM exchanges messages and performs operations on a per-domain basis. A
Maintenance Domain is a bridged network (or network of bridged networks)
maintained by an operator. Multiple domains at different levels create a hierar-
chy of Maintenance Domains. Each maintenance domain is assigned a Mainte-
nance Domain level between 0 and 7. Suggested Maintenance Domain level
allocation is: Customer Domain (5-7), Service Provider Domain (3-4), Operator
Domain (0-2). An example of a Maintenance Domain hierarchy is shown in the
following figure.

Figure 36: Maintenance Domain Hierarchy

CPE Operator A Provider Bridges Operator B Provider Bridges CPE
Customer Domain
MD Level = 5
Service Provider Domain
MD Level = 3
Operator Domain Operator Domain
MD Level = 2
Up MEP Down MEP MIP MANET
A Maintenance Domain at a higher level is a subscriber of the services of a

lower level domain. As shown in the figure above, the MD at level 5 (Customer
Domain) uses the service provided by the MD at level 3 (Service Provider
Domain). Similarly, the Service Provider Domain at MD level 3 uses the services
of Operators A and B at MD level 2.
The Maintenance Domain level restricts visibility upward and downward in the
hierarchy. The network topology of the Service Provider is not visible to the Cus-
tomer Domain. Similarly, the Service Provider cannot see the Operator
Domain’s topology. A higher level domain can only see what the lower level
domain allows it to see.
A Maintenance Association Network represents the service instance being mon-
itored and consists of MEPs which define the edge or boundary of the Mainte-
nance Association Network. Even though only one MEP is created on each
bridge for a Maintenance Domain, the MEP IDs of all MEPs in the MANET must
be configured at each bridge.
Maintenance Points (MPs)

A maintenance point is a demarcation point on an interface that participates in
CFM within a Maintenance Domain. Maintenance points can be associated with
a port, an EVC, or a VLAN ID and can be created as an end point (MEP) or an
intermediate point (MIP). MEPs define the boundary of a maintenance associa-
tion. A MEP can be configured as an up MEP or a down MEP. Up MEPs trans-
mit and receive CFM messages in the direction of the bridge relay. Down MEPs
are just the opposite - CFM messages are transmitted/ received in the direction
facing away from the bridge relay. Maintenance Intermediate Points (MIPs) are
intermediate hops on the path between MEPs and are useful in fault isolation
applications. MIPs are often MEPs for maintenance domains at a lower MD
level. See Figure 36.
The following figure illustrates the possible locations of the maintenance end
points. Port based MEPs are associated with the entire physical port. These are

typically down MEPs created to monitor the link between the local port and the
far end port.
Figure 37: Maintenance Points Example

Client/LAN Ports (UNIs) Network/WAN Port
Egress Ingress
Port Mapped EVC
EVC w/Multi VLAN IDs
VLAN based MEPs
Flow Mapped EVCs
Port based MEPs
EVC based MEPs Up MEP

Down MEP
VLAN based MEPs are associated with specific VIDs. These are typically up or
down MEPs monitoring an X tag. EVC based MEPs monitor the service
instance over the network interface. These MEPs are usually associated with C
and S tags. The total number of MEPs supported by the system is limited to
28(GE112)/ 38(GE114x).
Server MEPs
A Server MEP is used when it is desired to monitor a port and create an
ETH-AIS condition when the port goes down. The Server MEP does not partici-
pate in sending or receiving CCM messages and no other CFM related configu-
ration is required on the port or the services on that port to support the Server
MEP.
Creating and Deleting MIPs

Since MDs, MANETs, MACOMPs and MEPs are explicitly created and deleted
by user intervention (command or GUI) the remainder of this section will discuss
the details of those components of CFM hierarchy. MIP creation and deletion
however, is much more complex and are not explicitly created and deleted via
command or GUI option selection, therefore the following provides an explana-
tion of MIP creation and deletion scenarios.
MIP creation is only supported on Access ports. MIP creation evaluation is
always performed for a primary VID on a specific port, and are implicitly created
or deleted based on the result of the MIP evaluation.
Upon a MIP trigger condition (discussed later), the primary VID and port (com-
ponent ID) is checked for MIP creation according to 22.2.3 of the IEEE 802.1ag
specification, which follows these steps:

Creation of an Active MD Level list which includes MAs and a default MD entry
with matching primary VID and component ID, and meet the following condi-
tions:
• MD levels of the MAs that have MEPs configured
• MD levels of the MAs that have No MEPs configured
• MD level of the default MD entry
Exactly one object in the list is used for MIP evaluation. It is the object with the
lowest MD level that does not have a MEP configured. If it meets the following
criteria, then:
• If there is no such object, then no MIP change will occur.
• If the chosen object is an MANET, and Maintenance Intermediate Point Half
Function (MHF) creation control is Not Defer, then the MHF creation control
is taken from the MANET.
• If the chosen object is an MANET, and MHF creation control is Defer, then
the MHF creation control is taken from the MD object for the MANET.
• If the chosen object is a default MD entry and MHF creation control is Not
Defer, then the MHF creation control for the default MD entry is used.
• If the chosen object is a default MD entry and MHF creation control is Defer,
then the MHF creation control is taken from the default MD level object.
For each possible value of MHF creation control, the results are:
• None - No MIP is created.
• Default - A MIP is created at the chosen MD level for the primary VID and
component ID if it does not currently exist.
• Explicit - A MIP is created if there is a MEP at the next lower Active MD
level.
If the output of the evaluation result is a MIP should be created,
then a MIP is created if it does not exist. If the output of the
PS
evaluation result is a MIP should NOT be created, then if a MIP

Note currently exists, it is deleted.
Continuity Check Message

Fundamentally, the CFM standard defines a set of CFM messages, along with
supporting protocols and procedures, used for monitoring and managing the
connectivity between the maintenance points that comprise a Maintenance
Association.
Continuity Check Messages are periodic multicast messages used for detecting
loss of continuity between maintenance end points within a maintenance asso-
ciation network. Each MEP transmits CCMs to all other MEPs in the mainte-
nance association network at a specified interval. This message maintains a
heartbeat between the MEPs. If the heartbeat from any one MEP is not detected
for 3 consecutive intervals, a loss of continuity defect is declared. The loss of
continuity defect must persist for 3 consecutive seconds for the “Some Remote
MEP CCM” alarm to be declared. Since all MEPs in the same maintenance

association network must transmit at the same interval, the CCM interval is also
used as the receive interval for loss of continuity detection.
Figure 38: CCM Example

C
B
Operator B
Operator A
A D
M EP
CCM MIP
CCM Multicast from MEP A forwarded to MEP B, C and D
CCMs can also be used to detect misconfigurations. These defects include:
• Unexpected MD Level
• MANET ID Mismatch/Service cross-connect
• Missing or Unexpected MEP ID
• CCM Interval Mismatch
• Duplicate MEP ID
• Duplicate Sequence Number
The CCM carries information about the sender such as the source MAC
address, maintenance association network ID, source MEP ID, MD Level, etc.
Each MEP receiving a CCM from a peer MEP must catalog this information into
a local CCM MEP database. An entry should be created in the database for
each MEP in the MANET. The CCM interval ranges from 3.3 ms to 10 minutes.
The 3.3 ms CCM interval is intended for protection applications. An interval of 1
second is recommended for fault detection. CCMs are drop ineligible.
Finally, CCM Defect Detection can be used by the FSP 150CC to control 1+1
protection switching on the Network port if so configured (see Protection in FSP
150CC GE11x R6.1 Installation and Operations Manual document).
Link Trace Message

Link Trace Message (LTM) is used for path discovery and fault isolation. LTM
messages are multicast frames that a MEP transmits, at user request, to track
the path (hop-by-hop) to destination MEP. At each MIP along the path to the tar-
get, the LTM is forwarded to the next hop and a Link Trace Response message
(LTR) is sent back to the originating MEP. This process is repeated until the
LTM reaches the intended target, or the LTM can no longer be forwarded.

Based on the information in the LTRs received, the originating MEP can deter-
mine the path to the target if the Link Trace was successful, or the location of the
fault in the event of a failure.
Figure 39: Link Trace Example

LTM Ignored
C
Operator B
Operator A
A D

LTM MEP
LTR M IP
LTM from MEP A forwarded to MEP B, C and D

Loopback Message
Loopback Messages (LBMs) are Unicast messages that a MEP transmits, at
user request, to verify connectivity to a particular maintenance point. LBMs may
also contain additional data in the payload to measure performance characteris-
tics of the service. At the destination maintenance point, a Loopback Reply Mes-
sage (LBR) is transmitted back to the originating MEP. A reply to a loopback
message indicates whether a destination is reachable but does not contain
hop-by-hop discovery of the path.

Figure 40: Loopback Message Example

C
Operator A Operator B
A D

LBM MEP
LBR MIP
LBM from MEP A forwarded to MEP B, LBR from MEP B forwarded to MEP A
CFM & Y.1731
Y.1731 defines the fault and performance monitoring functions to operate and
maintain the Ethernet-based network and services. From a high level the func-
tions are:
• Fault Monitoring
• AIS
• Loss Measurement (LM)
• Delay Measurement (DM)
• Delay Variance Measurement
ETH-AIS
Ethernet AIS as defined in Y.1731 facilitates suppressing of alarms in higher
level MEPs, when they are due to defects in lower level MEPs. The idea is to
reduce the clutter of extraneous alarms, so the technician can home-in on the
actual failure. At the lowest level the defects on a port-based MEP (typically MD
Level = 0) can suppress alarms on one or more higher level MEPs.
Additionally, Ethernet AIS is used for Link Loss Forwarding (LLF). When a link
goes down, link loss is forwarded using the Interface Status TLV in the CCM.
TLV is sent in all the subsequent CCMs until the link down ceases to exist. On
the receiving end the Access port up MEPs can be configured to perform LLF
functionality by reacting to either CCM with an Interface Status TLV (isDown) or
ETH-AIS. ETH-AIS is a non-standard mechanism but is provided as a value-add
for situations where another vendor's equipment uses this mechanism for LLF.
This is implemented using the same ETH-AIS frame defined in Y.1731 without
any modifications in such a way as to not cause any interoperability issues.

MEPs running Continuity Check Protocol can be configured for one or more of
the following MEP defects to trigger ETH-AIS:
• Mismerge or Cross-connect defect
• Loss Of Connectivity (LOC) or Remote MEP CCM defect
• Unexpected or Error CCM defect
• AIS defect
Each MEP has a provisioned client MD level. If there is a MEP at the client MD
level then the AIS defect is set for that MEP and the AIS defect cascades up the
MEPs until a MEP is detected where there are no higher level MEPs or a MIP is
detected for that VID. If the highest level MP is a MEP, an ETH-AIS frame is
generated for a VID at client MD level of the MEP. If the highest level MP is a
MIP then an ETH-AIS frame is generated for a VID at the MIP MD level.
ETH-AIS frames are generated in the network-to-access direction for Network
port down MEPs and Access port up MEPs.
As per Y.1731 there are situations where a MEP could trigger ETH-AIS frames
for up to 4094 VIDs. This is not practical, so various criteria are used to limit the
number of ETH-AIS frames generated in the event of a qualifying defect on a
MEP.
For Access port up MEPs ETH-AIS frame is sent to the VLAN identified by the
MEP's primary VID and priority with ETH-AIS MD level set to the provisioned cli-
ent MD level.
For Network port-based down MEPs the ETH-AIS frames are sent to each
VLAN identified by Access port up MEP's primary VID and priority only for the
Access port up MEPs at the Network port MEP's client MD level.
For Network port VID-based down MEPs the ETH-AIS frames are sent to each
VLAN identified by Access port up MEP's primary VID and priority only for the
Access port up MEPs at the Network port MEP's client MD level. Additionally
Access port up MEPs should also have the Network port MEP's primary VID and
priority as the S-TAG of the service for which the Access port up MEP is
defined.
To keep it simple, MEPs were used above to identify the VLANs
to which ETH-AIS frames need to be sent. In all the above cases
PS
it is conceivable that MIPs dictate the ETH-AIS frames sent if a

MIP is present for the corresponding VID at the MEP's client MD
Note
level.
When an AIS frame is received and terminated by a Access port up MEP, the
MEP can be configured to either send an ETH-AIS frame or turn off the Access
port according to it’s Link Loss Forwarding configuration. If the Access port has
multiple MEPs that receive the ETH-AIS, each of which is configured to turn off
the Access port, then any single MEP can turn the port off but the port is turned
back on only if AIS defects are cleared on all the MEPs.
On AIS reception the AIS is defect is set immediately and if an ETH-AIS frame is
not received for 3.5 times the AIS transmission period the AIS defect is cleared.
Upon detecting an AIS defect the MEP can be configured to raise an AIS alarm.

Y.1731 Performance Monitoring

The user interface to affect and view the Y.1731 performance monitoring uses
the existing Etherjack Service Assurance (ESA) interface. ESA provides
on-demand layer-3 service assurance capabilities which are enhanced to pro-
vide the Y.1731 layer-2 service assurance.
For layer-2 service assurance the probes are loosely coupled to the MEPs. The
user creates the MEPs independently and then in the process of creating ESA
layer-2 probes associates a probe to the MEP by selecting one of the already
created MEPs. Typically in ESA a probe is created with a protocol (such as UDP
ECHO) and other items such as packet size, inter-packet interval etc. is config-
ured. The configuration is common to loss, delay and jitter (delay variance). This
remains the same for Y.1731 probes.
The transmission intervals supported for Delay Measurement (DM) are 10
msec., 100 msec., 1 sec., 10 sec. and 1 min. The Loss Measurement (LM)
transmission interval is always 1 sec. It is worth noting that Y.1731 loss mea-
surement is not done by counting the synthesized frames but instead is based
on the counters that are carried in the synthesized loss measurement frames.
These counters count the in-profile data frames. So it is not critical to generate
the loss measurement frames as frequently as the delay measurement frames
where the delay is calculated based on the synthesized frames.
Y.1731 Loss Measurement (LM)
Loss Measurement capability is supported as defined in Y.1731. The exception
is that dual-ended LM is only partially supported. The device supports transmis-
sion of the LM counters in the CCMs that are sent out but not near-end or
far-end loss measurements based on the LM counters of the received CCMs.
This capability is provided to facilitate the peer MEP to support the near-end and
far-end loss measurements.
The single-ended on-demand LM is fully supported. The on-demand LM is con-
figured and scheduled by the user using the ESA interface. The MEP allows the
following configurable parameters for supporting the LM functionality:
• Transmission Period: 1 second. This is the frequency at which the Loss
Measurement Messages (LMMs) are transmitted.
• Priority: The priority used in the LMMs. If not specified the MEP's CCM pri-
ority is used.
• Ignore Priority: This flag indicates that the LM counts are combined for all
the priorities. This is a vendor extension and should be used only if the peer
device is an ADVA Optical Networking device.
For Access port up MEPs the MEP's primary VID and the LMM/CCM priority
make up the X-Tag of the LMM. For Network port down MEPs the MEP's pri-
mary VID and the LMM/CCM priority make up the S-TAG of the LMM. Port-level
Network port down MEPs cannot be used for loss or delay measurements.
The LMMs are drop-ineligible. Within the NID the policer passes the
LMMs/LMRs irrespective of the available bandwidth. But for the LMMs gener-
ated by the NID for the Network port down MEPs, it sets the DEI bit in the
S-TAG to 0 to indicate the drop eligibility as false.

If the ignore priority flag is enabled, the local counter values sent in the LMM are
aggregate values for all priorities. If the ignore priority flag is disabled then the
LM counters are maintained for each priority class. In this case the local counter
values sent in the LMM are the counters for configured LMM priority.
When it comes to LMM reception and LMR generation there is no limitation, an
LMR is generated for each LMM received.
There is a concern with loss measurements where receiving end receives more
frames than the transmitting end has sent resulting in negative frame loss. Even
though the chance of this happening is remote, it is possible. This happens if
data frames sent after the LMM on the transmitting end reach the receiving end
before the LMM. This implies that there will be a positive frame loss some time
after the negative frame loss. Software counts the occurrences of negative
frame loss so the user can correlate that a positive frame loss was not really a
frame loss but was potentially caused due to the negative frame loss occur-
rences in the past within this bin period.
There is also a situation where the receiving end is configured to perform some
CFM functions but potentially does not support or is not configured to perform
Y.1731 performance monitoring functions. This means that the transmitting end
will not receive any LMRs. This will show zero loss of frames and it should be
differentiated from genuine zero frame loss resulting from processing LMRs
(either due to lack of traffic or no frame loss with traffic). The user has a flag that
indicates that the bin period did not have any loss measurement samples (no
LMRs received).
Y.1731 Delay Measurement (DM)

Delay Measurement capability is supported as defined in Y.1731 with the
exception of handling 1DM frames for one-way delay measurement. The 1DM
frames if received are ignored. Y.1731 suggests that the Delay Measurement
Message/Delay Measurement Reply (DMM/DMR) frames are used for two-way
delay measurements. The receiving end can add receive and transmit time
stamps to account for the processing time in the two-way delay measurements.
We can use these time stamps also for one-way delay measurement which is a
bit of deviation from Y.1731 which defines a separate 1DM frame for one-way
delay measurement. If the receiving equipment is ADVA Optical Networking
equipment then these time stamps are added.
As adding these time stamps is not mandatory as per Y.1731, if some
non-ADVA Optical Networking equipment does not add these timestamps then
the processing times cannot be accounted for two-way delay and one-way
delays cannot be measured. The DMM/DMR approach is used as it is more suit-
able for on-demand and fits better with the ESA model and also as suggested
above can be used for both one-way and two-way delay measurements. For
one-way delay measurements the clocks on both ends need to be synchro-
nized.
The on-demand DM is configured and scheduled by the user using the updated
ESA interface. The Y.1731 ESA Probe allows the following DM configuration
parameters:
• Transmission Period: The supported values can be between 10 millisec-
onds, 100 milliseconds, 1 second, 10 seconds and 1 minute and the default

is 100 milliseconds. This is the frequency at which the DMMs are transmit-
ted.
• Packet Size: This is the size of the frame. The frame size can expand from
the minimum size using a Data TLV padded with all zeros. Changing the
packet size may create interoperability implications since the DMM as per
Y.1731 is a fixed length frame without TLVs.
• DM Priority: The priority used in the DMMs. This setting is done on the MEP.
For Access port up MEPs the MEP's primary VID and the DMM/CCM priority
make up the X-Tag of the DMM. For Network port down MEPs the MEP's pri-
mary VID and the DMM/CCM priority make up the S-TAG of the DMM.
Port-level Network port down MEPs cannot be used for loss or delay measure-
ments.
The DMMs are drop-ineligible. The policer passes the DMMs/DMRs irrespective
of the available bandwidth. But for the DMMs generated by the NID for the Net-
work port down MEPs, it sets the DEI bit in the S-TAG to 0 to indicate the drop
eligibility as false.
For time stamps, software periodically updates an internal timing source based
on updates from SNTP. It uses this to timestamp the DMM and DMR frames.
The timing scheme accounts for the inaccuracies in the timing specifically for a
DMM which is sent before an NTP timing update and a DMR received after the
update by adding or subtracting the drift in the timing source.
There is also a situation where the receiving end is configured to perform some
CFM functions but potentially does not support or is not configured to perform
Y.1731 performance monitoring functions. This means that the transmitting end
will not receive any DMRs. The user has a flag that indicates that the bin period
did not have any delay measurement samples (no DMRs received).
Y.1731 Delay Variation (Jitter) Measurement

Delay variation or jitter is calculated fully by software based on the delay mea-
surement timestamps gathered from delay measurement computations. It is the
variation in delay between two consecutive measurements.
Component ID (MACOMP)
According to the 802.1ag standard MIB, the component ID is introduced to sup-
port 802.1ah where there could be multiple bridge-like components in a bridge
device. It can also be used to support multiple CFM components in a device
such as our NID that supports multiple C-VLAN and S-VLAN components. With-
out the component IDs, service definitions (VLAN membership) are identical on
all VLAN ports. It does not match well with our EVC service definition which is
port specific. The new model with component ID solves this problem. Essen-
tially, we assign a component ID to each of the access ports. Another flexibility
afforded by the component ID is that the MIP creation control and sender ID
control are also port specific.
CFM VLAN Table

The entries in the CFM VLAN table are organized by {ComponentID, EntityID,
PrimaryVid, VID} in the VLAN table. This means that instead of one VLAN table

for the system there are multiple VLAN tables - one for each component in the
bridge.
Protection Switch Using CCM

This feature uses CCM loss of continuity (dLOC) and ETH-CC Remote Defect
Indication (RDI) on Network port down MEPs as protection triggers. This
requires configuring down MEPs on the Network ports with 3.3 msec (300 Hz)
CCM interval setting for the MANET.
Upon loss of ETH-CC messages, as defined by 802.1ag, the MEP raises the
dLOC condition locally, and immediately transmits an ETH-CC message toward
the peer MEP with the RDI indication set.
This action provides not only for local protection switch triggers, but also covers
the case of a uni-directional failure. The remote MEP, on receiving the RDI indi-
cation knows that a uni-directional failure has occurred and sends an RDI fault
indication to the protection algorithm on its local end to initiate a protection
switch.

PS

switching.
Note
Etherjack® Connection Performance Analyzer

While port and VLAN loopback functions provide a means to manually test
end-to-end EVC circuits, multiple test suites are required, and the result of the
tests performed will estimate end-to-end throughput, latency, jitter, etc. ADVA
Optical Networking’s Etherjack Connection Performance Analyzer (ECPA) pro-
vides a means to test end-to-end EVC circuits, and provides a measurement of
actual customer throughput, latency, jitter, etc. (see Figure 41).
Figure 41: End-to-End EVC Circuit Testing Using ECPA
Loopback
Test Pattern
ECPA
FSP 150CC FSP 150CC
Customer Premise Central Office Customer Premise
The Etherjack® Connection Performance Analyzer (ECPA) provides a subset of

Ethernet test equipment functions embedded directly into the port cards so that
each individual Ethernet port can act as its own “test equipment.” This provides
a means to test EVC connectivity and verify service conformance from a remote
location without the need for external test equipment.

The ECPA feature can be controlled remotely from a Network Management ter-
minal anywhere in the network. Together with port and VLAN loopback func-
tions on each ECPA port, ECPA allows in-service end-to-end EVC traffic
testing.
Etherjack™ Connection Performance Analyzer:
• Provides a subset of Ethernet test equipment functions embedded directly
into the Provider Equipment so that each individual Ethernet port can act as
its own test equipment.
• Provides a management feature which allows the FSP 150CC to be con-
trolled remotely from a Network Management terminal anywhere in the net-
work.
• Allows service verification for new point-to-point EVCs on a multi-point
Ethernet port without disrupting other “live” connections on the same port.
• Provides a port loopback on each Ethernet port which loops egress traffic
back to the ingress path. This allows end-to-end traffic testing.
• Provides a VLAN loopback capability to allow only selected VLANs (up to 3)
to be looped back at a port
ECPA functionality is implemented by a combination of hardware and software

components. The hardware component is used to insert Ethernet test frames
into an EVC connection and to monitor test frames received from an EVC con-
nection.
The FrameInjector and FrameMonitor blocks lie in the data-path on each ser-
vice card. The Input of the FrameMonitor can be connected to the ingress or
egress data path on the card so that frames can be monitored in either direction.
The output of the FrameInjector can be connected to either ingress or egress
data path. In addition, a VLAN loopback function can select egress frames with
a specific VLAN ID to be looped back into the ingress traffic path. This allows for
in-service testing of connections without disrupting normal EVC traffic.
A port loopback can also be selected which loops all traffic from the egress
direction back to the ingress data path. This is an out-of-service disruptive loop-
back.
Refer to Figure 42 for a block diagram of the data path of a service interface
card which contains the FrameInjector and FrameMonitor blocks.

Figure 42: ECPA Block Diagram
WAN CLIENT
ETHERNET ETHERNET
PORT INGRESS PORT
FRAME
PROCESSING
INTERFACE
INTERFACE
MEDIA
FRAME FRAME
WAN
MONITOR INJECT
EGRESS
FRAME
PROCESSING
PORT
LOOPBACK
(All frames)
VLAN
LOOPBACK
(Only selected EVC frames)
By injecting test traffic into an EVC connection, then looping the test traffic at the
far end of the EVC, and monitoring the “echoed” traffic, ECPA can verify net-
work connectivity along with several performance parameters. An example of
this is shown in Figure 43.
Figure 43: ECPA Point to Point EVC Example
EGRESS INGRESS
FRAME FRAME
PROCESSING PROCESSING
INTERFACE
INTERFACE
INTERFACE
INTERFACE
MEDIA
MEDIA
FRAME FRAME FRAME FRAME
NETWORK
WAN
WAN
MONITOR INJECT MONITOR INJECT
INGRESS EGRESS
FRAME FRAME
PROCESSING PROCESSING
ECPA Operation
Under normal circumstances, the FrameInjector allows traffic from the MAC
block to pass-thru to the Ingress Frame Processing block. Similarly, the Frame-
Monitor, in normal operation, passes frames transparently in the egress direc-
tion from the egress frame processing block to the MAC block.
When placed in test mode, the FrameInjector can inject test traffic in the ingress
or egress data path. This test traffic emulates the flow of traffic from a UNI or
EVC and allows various characteristics of the traffic to be simulated to ensure
that the EVC connection performs correctly all the way through the network.
The FrameMonitor, when enabled, sniffs the ingress or egress traffic path for
EVC test frames and traps them. The FrameMonitor can perform various perfor-
mance calculations on the test traffic to analyze the EVC operation.
The FrameMonitor and FrameInjector also implement a flow loopback path
which allows egress traffic frames trapped in the FrameMonitor to be “looped”
back to the FrameInjector for transmission back into the network. This flow loop-

back enables a single EVC test traffic flow to be looped back without affecting
normal EVC traffic. This capability is critical to performing multi-service port test-
ing.
Each FrameInjector block is capable of sourcing three independent traffic flows,
each with a different set of characteristics. Thus, it is possible to test EVC per-
formance for multiple classes of traffic (for instance, with different priority levels)
to ensure that different traffic classes receive correct QoS treatment. Similarly,
each FrameMonitor is capable of monitoring and analyzing three independent
data flows.
An ECPA test setup window via eVision walks you though 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, exe-
cute diagnostics, view test results, and restore the facility from this window.
Refer to Figure 44 for an example of an ECPA test in progress using eVision.
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.
For more information on the ECPA operation, see Etherjack® Connection Per-
formance Analyzer on p. 514.
Figure 44: ECPA Test Results Window

Port, VLAN, EFM-OAM and I-Tag Loopback

To assist with Ethernet service fault isolation and to support Service Level
Agreement (SLA) conformance verification, ADVA Optical Networking’s family
of FSP 150CCs support port, VLAN and EFM-OAM message loopback modes
on all Access and Network ports. This feature allows the operator to set up an
Ethernet test-set at a central location to inject traffic into the network.
Figure 45: CO Based Testing Using Ethernet Loopback
CO Based
Test Head
Loopback Loopback
Test Pattern 2 Test Pattern 1
FSP 150CC FSP 150CC
As shown in the example in the figure above, traffic is looped back into the net-
work 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 con-
nect a test-set in the field or at the customer premise to verify round-trip service.
Three basic types of loopback are available: Port, VLAN and EFM-OAM. The
following loopback functions are available:
• Terminal Loopback
• Terminal Timed Loopback
• Facility Loopback
• Facility Timed Loopback
• Terminal VLAN Loopback
• Facility VLAN Loopback
• Remote EFM-OAM Loopback
• Timed Remote EFM-OAM Loopback
• Facility I-TAG Loopback (Network Port only)
• Terminal I-TAG Loopback (Network Port only)
When using eVision, to remove a loopback, click on the drop-down list for Loop-
back Configuration and select “None”, then click on “OK”.

Port Loopback
Port loopbacks consist of Terminal and Facility loopbacks, which may be
applied in a constant or timed manner. A terminal loopback connects all traffic
frames about to be transmitted from the port to the associated, incoming
receiver (see Figure 46). This operation also enables testing of internal receiv-
ers and transmitters. Placing a port in facility loopback mode connects all traffic
frames received from the port to the associated transmitter (see Figure 47).
Both terminal and facility loopbacks will loop back all traffic frames (excluding
EFM-OAM messages), resulting in a disruption of service. Selecting the timed
loopback option can minimize the amount of time service is disrupted while
allowing a specified duration of testing. Port loopbacks ignore any traffic shap-
ing and allow testing at the full port bandwidth.
Figure 46: Terminal Loopback (without Swap SA/DA)
Access Terminal Loopback Network Terminal Loopback
RX TX RX TX
Access TX RX Network Access TX RX Network
FSP 150CC FSP 150CC
All traffic is looped back, excluding EFM-OAM messages
Figure 47: Facility Loopback (without Swap SA/DA)
Access Facility Loopback Network Facility Loopback
RX TX RX TX
TX RX TX RX
Access Network Access Network
FSP 150CC FSP 150CC
All traffic is looped back, excluding EFM-OAM messages
A simple terminal or facility loopback is sufficient for back-to-back FSP 150CC

configurations with no Layer 2 cloud between them. However, if a Layer 2 cloud
does exist between each FSP 150CC, traffic will not reach its intended destina-
tion (see Figure 48). Within each Ethernet frame is a MAC address from which
the frames are sent (Source Address) and the MAC address of the intended
recipient of those frames (Destination Address). A Layer 2 cloud looks at the
Destination Address to determine where to send the frames, and if the Destina-

tion Address is the same address from where the frames are received, the Layer
2 cloud will discard the frames.
Selecting the Swap SA/DA [Swapping the Source Address (SA) with the Desti-
nation Address (DA)] option during the loopback directs the FSP 150CC 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 (see Figure 49). This function is performed by the Media Controller Con-
verter (MCC). Only one Swap SA/DA loopback may be performed per system.
Once a Swap SA/DA loopback has been operated, a second Swap SA/DA loop-
back may not be performed on another entity.
Although the following examples show Access port loopbacks, the same applies
to Network port loopbacks.
Figure 48: Access Port Terminal Loopback (without Swap SA/DA)
FSP 150CC FSP 150CC

(MAC Address: 00:0B:90:02:8A:31) (MAC Address: 00:0B:90:00:08:32)
FRAMES:
SA MAC: 00:0B:90:00:08:32
DA MAC: 00:0B:90:02:8A:31
RX TX RX TX
Access Network
X Layer 2 Cloud Network Access
TX Media RX TX RX
FRAMES:
Converter
Controller SA MAC: 00:0B:90:00:08:32
DA MAC: 00:0B:90:02:8A:31
Figure 49: Access Port Terminal Loopback (with Swap SA/DA)
FSP 150CC FSP 150CC

(MAC Address: 00:0B:90:02:8A:31) (MAC Address: 00:0B:90:00:08:32)
FRAMES:
SA MAC: 00:0B:90:02:8A:31
DA MAC: 00:0B:90:00:08:32
RX TX RX TX
Access Network
Layer 2 Cloud Network Access
TX Media RX TX RX
FRAMES:
Converter
Controller: SA MAC: 00:0B:90:00:08:32
Swap SA/DA DA MAC: 00:0B:90:02:8A:31
VLAN Loopback
Both terminal and facility loopbacks send all traffic frames, and therefore result
in an out-of-service disruption of service for the time the loopback is applied.
The VLAN loopback function can select egress frames with a specific VLAN ID
to be looped back without disrupting normal EVC traffic. During a VLAN loop-
back, only the specified VLAN traffic is looped back. All other traffic is for-

warded, preventing any disruption of service. Only one VLAN loopback may be
performed per system. Once a VLAN loopback has been operated, a second
VLAN loopback may not be performed on another entity. For Network, selection
and entry of Inner Tag and/or Outer Tag VLAN IDs are possible. VLAN loop-
backs conform to any configured traffic shaping profiles.
Figure 50: Access Port Terminal VLAN Loopback

FSP 150CC FSP 150CC
All Other Traffic

RX TX RX TX
Access Network Network Access
TX Media RX TX RX
Converter
Controller VLAN ID = 4094-0
Selected VLAN(s) are looped back,
all other frames are forwarded
I-Tag Based Loopbacks

FSP 150CC-GE11x also supports Backbone Service Instance Tag (I-Tag)
based loopbacks on the Network Ports. It is similar to VLAN-base loopbacks,
but the I-Tag is also used. FSP 150CC-GE11x ignores the Backbone VLAN Tag
(B-TAG) in the PBB frames. There are two types of I-Tag Based Loopbacks:
• Facility I-TAG Loopbacks
• Terminal I-TAG Loopbacks
Either types of I-TAG Loopbacks can be based on:
• {I-SID, I-PCP} or {I-SID, *} up to 3 pairs
• {I-SID, I-PCP} + inner {VID, PRI} or {VID.*} up to 3 pairs
• {I-SID, *} + inner {VID, PRI} or {VID.*} up to 3 pairs
In the list above, PCP means Priority Code Point (P-bits).
As for I-Tag based loopbacks, if the SwapSADA attribute is set to “Swap SADA”
the following are swapped:
• B-DA MAC and B-SA MAC
• C-DA MAC and C-SA MAC
If SwapSADA is set to “Swap DA Overrides SA” the following are swapped:
• B-SA MAC and local SA MAC
• C-DA MAC and C-SA MAC

Figure 51: Network Port I-Tag based Terminal Loopback

FSP 150CC FSP 150CC
All Other Traffic

RX TX RX TX
Network Access Access Network
TX Media RX TX RX
Converter
Controller I-Tag = 16777214-7
Selected I-Tag & VLAN(s) are looped back, VLAN ID = 4094-7
all other frames are forwarded
EFM-OAM Loopback
IEEE compliance requires EFM-OAM frame integrity when a loopback is in
place. The EFM-OAM loopback (which is similar to a facility loopback) performs
this function by processing all EFM-OAM frames while looping back all other
traffic. The EFM-OAM loopback function is performed by the Media Controller
Converter (MCC). See the following figure. Note that the Remote EFM-OAM
loopback includes management traffic, therefore management traffic is dropped
while the Remote EFM-OAM loopback is active. Since all EFM-OAM frames are
still processed, when the loopback is released, management connectivity will
also be restored.
Figure 52: EFM-OAM Loopback

FSP 150CC FSP 150CC
All EFM-OAM
Messages Processed EFM-OAM CPD set to Peer
RX TX RX TX
TX Media RX TX RX
Converter
Controller
All Other Traffic
EFM-OAM messages are processed, Remote EFM-OAM Loopback
all other frames are looped back command sent from this FSP 150CC
Fault Propagation
The FSP 150CC supports two types of fault propagation:
• Network to Access Fault Propagation
• Access to Access Link Loss Forwarding
Network to Access fault propagation can be the simple link loss forwarding
across the system (i.e., between network and client ports) or the propagation of
a fault condition from the network to the access by means of Ethernet OAM
messages.

Figure 53: Network to Access Link Loss Forwarding
Link
Disable
®
MGMT
LA
N
STA 123LKL
FSP 150CC
Node B
Network to Access fault propagation triggers include:

• Link Down detection
• Detection of loss of continuity (dLOC)
• Reception of Remote Defect Indication
• Reception of Ethernet Alarm Information Signal
Fault conditions can be propagated from network to access in two ways:
• by physically disabling the access port
• by transmitting frames with ETH-AIS information.
It is also often desired to propagate link faults across an intermediate network.
Access to Access Link Loss Forwarding (LLF) allows a failure detected on one
UNI to be propagated to the remote UNI across the EVC. This type of Link Loss
Forwarding requires the use of control messages between the FSP 150CC
products.
Figure 54: Access to Access Link Loss Forwarding
L in k D is a b le
C lie n t
S w itc h
FSP 150CC
Link Fault
FSP 150CC
C lie n t
S w itc h
The control messages to implement Access to Access LLF are based on the fol-
lowing standard Ethernet OAM protocols:
• IEEE 802.3ah EFM OAM

• IEEE 802.1ag Connectivity Fault Management

IEEE 802.3ah EFM OAM can be used when signalling Access to Access LLF
across a point to point link, while IEEE 802.1ag can be adopted for signalling
Access to Access LLF across an intermediate network.
Access to Access LLF across a point to point link is via Remote Link Down that
is based on Vendor Specific EFM OAMPDU.
Conversely, Access to Access LLF across an intermediate network is signalled
by encoding “Link Down” in the Interface Status TLV of CC messages as per
IEEE 802.1ag. The Interface Status TLV indicates the status of the interface on
which the MEP transmitting the CC message is configured.
Link failures are caused by physical layer failures or other conditions such as an
interface being placed into loopback. Link failures are detected by monitoring
the physical hardware or by management actions.
Access to Access Link loss forwarding triggers include:
• Link Down detection
• Receipt of Remote Fault condition from remote link partner.
• Placing the port in facility loopback mode.
Link failures on one link/port are propagated to a link partner (across the device
or to a remote end of the service) by physically disabling the port. This is accom-
plished by one of the following actions:
• by turning the laser off on the optical transceiver (SFP)

• by turning the electrical port off for copper media (no link)
EFM-OAM Dying Gasp

The FSP 150CC transmits a single EFM-OAM Dying Gasp message out each
EFM-OAM enabled port when a power failure occurs. This message is specified
in the IEEE standard 802.3ah - Annex 43B. A receiving peer entity capable of
processing this message raises an alarm when the Dying Gasp is detected (see
the following figure). If EFM-OAM Dying Gasp and SNMP Dying Gasp are both
enabled, and an SNMP Trap Dying Gasp Interface is resolved, then SNMP
Dying Gasp takes priority on that interface.
Figure 55: EFM-OAM Dying Gasp

FSP 150CC FSP 150CC
EFM-OAM CPD set to Peer
RX TX RX TX
TX Media RX TX Media RX
Converter
EFM-OAM Dying Gasp sent
Converter
Controller to all EFM-OAM enabled interfaces Controller

SNMP Dying Gasp

Unfortunately, not all peers attached to the FSP 150CC can process EFM-OAM
Dying Gasp messages. The SNMP Dying Gasp feature may be used as an
alternative to EFM-OAM Dying Gasp to enable these peers to receive power
failure notification as an SNMP trap. When SNMP Dying Gasp is enabled,
Ethernet frame particulars such as VLAN and source MAC address are obtained
from each interface’s provisioned MAC- or VLAN-based management tunnel,
and a Dying Gasp message is prepared for transmission to the first reachable
SNMP target address, should a power failure occur. See the following figure for
details.
Figure 56: SNMP Dying Gasp

Third Party System FSP 150CC
RX TX RX TX
TX RX TX RX
SNMP Dying Gasp sent
to resolved SNMP Target Address
The SNMP Dying Gasp feature is best utilized when connected to a device that
is not EFM-OAM compliant. Note that SNMP Dying Gasp, which is intended to
supplant EFM-OAM Dying Gasp, only functions on traffic carrying ports (i.e., not
the Management LAN port).
To set up the SNMP Dying Gasp feature, first create the appropriate Ethernet
encapsulated VLAN-based management tunnel (the SNMP Dying Gasp feature
only applies to Network and Access interfaces and are not applicable to the
Management LAN or Serial Port). Then configure SNMP Target addresses on
the FSP 150CC. Then enable SNMP Dying Gasp at the system level. Once an
SNMP target address is configured and resolved, the SNMP Trap Dying Gasp
Interface displays, indicating that the SNMP Dying Gasp feature is operational.
Resolving Target Addresses

The list of SNMP target addresses, as displayed, is polled every 5 minutes to
resolve target addresses and verify reachability. It may take up to 10 minutes for
a target address to be resolved. Upon reboot, a resolved SNMP target address
is not displayed until a second 5 minute cycle has completed. Outside of a
reboot, changes are reflected after each 5 minute poll cycle.
Resolving target addresses entails using trace route to determine the appropri-
ate interface. It does not guarantee that the target address can be reached over
that interface. Reachability uses ping (ICMP Echo) in an attempt to reach the
target address. If the Ping fails, an “SNMP Dying Gasp Trap Host Unreachable
Via Ping” alarm is raised. Note that reaching the IP address does not equate to
an SNMP trap receiver running at that IP address. It is also possible that the
ping could fail (e.g., be filtered by the network even though an SNMP trap would
get through).

If an SNMP target address is unresolved, the SNMP Dying Gasp trap cannot be
transmitted for that SNMP target address. Each interface may have one target
address resolved for it. This means that a device that has two management tun-
nels, with a resolved target address on each tunnel, will send out two SNMP
Dying Gasp traps - one for each interface.
The first target address per interface that is resolved is considered as the
“resolved” one for that interface. Other target addresses that would be reach-
able on that same interface are listed as unresolved.
EFM-OAM Dying Gasp and SNMP Dying Gasp

Inter-Operation
If EFM-OAM Dying Gasp and SNMP Dying Gasp are both enabled, and an
SNMP Trap Dying Gasp Interface is resolved, then SNMP Dying Gasp takes pri-
ority on that interface. (Note that it may take up to 10 minutes for a target
address to be resolved on an interface once it is added. During that time period,
the EFM-OAM Dying Gasp message will be sent if the system loses power.)
Environmental Alarm Input

The GE114H/GE114PH provide 4 dry contact alarm inputs. These dry contact
alarm inputs are accessed via a RJ45 connector in the front of the unit. Up to 4
monitored devices can be connected to the 4 dry contact alarm inputs. The dry
contact alarm inputs are programmable to specify the monitored condition and
whether the alarm shall be raised on contact closed or open.
Management and Control

The following describes the general management communications architecture
and the management features supported in the FSP 150CC.
The FSP 150CC supports the following management interface connectors:
• Local Area Network (MGMT LAN) port (10/100 BaseT with RJ45 connector)
for connection to a management DCN or a local Personal Computer (PC).
• Serial Port (RS232 with RJ45 connector) to enable access to the Command
Line Interface (CLI) from a local PC.
• VLAN based management tunnels. The FSP 150CC supports one manage-
ment tunnel on each Network and Access Port.
• The FSP 150CC supports a Management Traffic Bridging feature which
implements an Ethernet bridge with eth0 (DCN) and all management tun-
nels as attached interfaces.
The Management and Control architecture of the FSP 150CC not only supports
local shelf management and controls - it also supports inter-operability with
other FSP 150CC products via IP/Ethernet over VLAN based Management Tun-
nels.
Management tunnels are the means by which the provider will be able to man-
age the chassis from a remote location. Local management interface and DCN

interfaces can also be used to connect and manage other FSP 150CC and FSP
150CP products. In order to support the management tunnels, each interface
supports an IP interface by reserving some provisionable bandwidth for trans-
porting management traffic. Basic ARP and IP routing functionality is provided in
the case where the DCN works like a router.
The DCN also supports an Access Control List (ACL) to limit management
access to the shelf. 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).
The system also provides a means for the user to control the availability of ser-
vices such as FTP, Telnet etc. The system supports broadcast storm suppres-
sion so as to prevent DOS attack.
Management Traffic Bridging

The Management Traffic Bridging feature implements an Ethernet bridge with
eth0 (DCN) and all management tunnels as attached interfaces. The main
advantage of this feature is that the system can be assigned only a single IP
address and the user will be able to connect to the system using this single
address - either from eth0 (DCN) or any management tunnel.
Management Traffic Bridging is enabled or disabled at the system level (Edit
System) where default is no bridging (Disabled).
The following figures show provisioning examples and the respective connectiv-
ity between the FSP 150CC-GE11x and a FSP 150CC-GE206 using the bridg-
ing feature via two scenarios: Single Level Bridging and Dual Level Bridging.

Figure 57: Single Level Management Bridging
eVision Workstation
IP Address =
192.168.190.105
Subnet Mask =
255.255.255.0
Default Gateway =
192.168.190.1
eVision Workstation
IP Address =
192.168.192.50
Subnet Mask =
DCN
255.255.255.0
IP Address = 192.168.192.51
Default Gateway =
Subnet Mask = 255.255.255.0
192.168.192.1
Default Router = 192.168.192.1
GE11x DHCP = enabled
Management Traffic Bridging =
Enabled
port1 port2
GE11x port1 GE206 Net
Mgmttnl Mgmttnl
VLAN Based, VLAN ID = 100 VLAN Based, VLAN ID = 100
Encapsulation Type = Ethernet Encapsulation Type = Ethernet

DHCP = enabled DHCP = enabled
RIP V2 Packets =disabled RIP V2 Packets =disabled
Figure 58: Dual Level Management Bridging

eVision Workstation
IP Address =
192.168.190.105
Subnet Mask =
255.255.255.0
Default Gateway =
192.168.190.1
eVision Workstation
IP Address =
192.168.192.50
Subnet Mask =
255.255.255.0 DCN
Default Gateway = IP Address = 192.168.192.51
192.168.192.1 Subnet Mask = 255.255.255.0
Default Router = 192.168.192.1
GE11x DHCP = enabled
Management Traffic Bridging =
Enabled
port1 port2
DCN
DCN IP Address = 192.168.192.53
IP Address = 192.168.192.52 Subnet Mask = 255.255.255.0
Subnet Mask = 255.255.255.0 Default Router = 192.168.192.1
Default Router = 192.168.192.1 GE11x port1 GE206 DHCP = disabled
Net
DHCP = disabled Management Traffic Bridging = Enabled
Management Traffic Bridging = Enabled Add static default route:
Add static default route: 0.0.0.0 0.0.0.0 192.168.192.1 eth0
0.0.0.0 0.0.0.0 192.168.192.1 eth0
Mgmttnl Mgmttnl
VLAN Based, VLAN ID = 100 VLAN Based, VLAN ID = 100
Encapsulation Type = Ethernet Encapsulation Type = Ethernet

Management Interfaces
Management interfaces consist of a eVision Web Browser Management Tool
interface, a Command Line Interface and a Simple Network Management Proto-
col interface.
Command Line Interface

This document assumes the use of eVision for configuring and monitoring the
FSP 150CC. However, a CLI is also available. The CLI command structure pro-
vides a text-based system for local configuration and management of FSP
150CC functions. For further information regarding the CLI and the command
structure refer to the FSP 150CC-GE11x Command Line Interface Reference
Guide.
Simple Network Management Protocol

The FSP 150CC provides seamless integration between Simple Network Man-
agement Protocol (SNMP) and EFM environments to ensure seamless network
level views via the FSP 150 enterprise Management Information Base (MIB).
For further information regarding management via SNMP refer to the FSP
150CC-GE11x SNMP Reference Guide.
eVision Web Browser Management Tool

The FSP 150CC supports an eVision Web Browser Management Tool to pro-
vide a web based Graphical User Interface (GUI) for OAM functions. For further
details on the eVision Web Browser Management Tool, refer to Chapter 2, eVi-
sion Web Browser Management Tool on p. 189.


Breadcrumb
Breadcrumbs are used by Fiber Service Platform Network Manager (FSPNM) to
store information. Information is packed into unstructured name-value pairs
(ESM-nvpair). Being unstructured allows Breadcrumbs to store any information
including that relevant to higher layer management systems such as Operations
support systems (OSSs).
The Breadcrumb can be manipulated on CLI or SNMP but not GUI. What nota-
ble is, when the user delete an entity (for example, a LAG or a Flow) on any
interface (CLI, SNMP or GUI), the Breadcrumb entities associated with it, are
automatically removed.
Management Features
User Management and Security

Security features include: user access security levels, Secure Sockets Layer
(SSL) support for security of Secure Hypertext Transfer Protocol (HTTPS),
Secure Shell (SSH) management protocols, RADIUS support, TACACS+,
SNMP support, post login security banner, and Access Control List (ACL) man-
agement.
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 dis-
abled individually. Serial port access may also be disabled. The serial port auto-
matically logs the user off on disconnect (provisionable).

Local User Profile Management

Up to 10 local user accounts are supported. A login inactivity time-out security
feature provides a provisionable login time-out for each user ID regardless of
access type. Four privilege levels are supported: Superuser, Provisioning, Main-
tenance and Retrieve. (See User Authorization Privilege Levels on p. 605)
Three preconfigured user accounts are provided as default: “root” (Superuser
level), “netadmin” (Provisioning level), and “user” (Maintenance level). Default
passwords for preconfigured user accounts is “ChgMeNOW.” Default login time-
out is 15 minutes for each preconfigured user account.
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.
SNMP User Management

SNMP MD5/SHA1 authentication protocols and AES/DES privilege protocols
are supported.
Four preconfigured SNMP user accounts are provided as default: “ADMIN,”
“MONITOR”, “OPERATOR” and “PROVISION”.
ACL Management
Up to 10 system level ACL entries can be made, and each entry can be individ-
ually 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 (subnet-
work).
Security Banner
The security banner feature allows an operator to define a custom security ban-
ner 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 FSP 150CC provides provisioning options for the various NE functions. The
following provides a brief overview of provisioning options supported by the FSP
150CC. For detailed provisioning information, see Operations Provisioning on
p. 219 and Provisioning Rules on p. 599.
Communications Provisioning
The FSP 150CC provides facilities to set up a management communication
configuration for a particular site or specific network configuration and supports
several management configurations and options.
Typical deployment scenarios are in common IP network configurations and
within an IP environment the FSP 150CC can be connected in many different
ways, e.g.:
• connected to a LAN through direct connections, a router, or an Ethernet
switch
• static routes can be created to enable connections between a workstation
and an FSP 150CC
• different IP functions can be used to achieve specific network goals, e.g.,
Proxy Address Resolution Protocol (ARP) enables one LAN-connected FSP
150CC to serve as a gateway for other equipment that is not connected to
the LAN
Operations Provisioning
Provisioning System Options
Facilities are provided to provision system options, including:
• common system options, such as:
o
System identity
o
IP connectivity
o
time
o
access
o
SNMP traps
• information logs, including Security, Alarm, Audit and System Logs
• system security, such as the configuration of users, Access Control List
(ACL) and the login security banner (see Management Features on p. 99)
• the Network Time Protocol (NTP)
Provisioning Network Elements

Facilities are provided to provision NEs, including the following:
• a Network Element Identity
• Configuring Network/Access Interfaces, including:
o configuring Port Services (including Link Loss Forwarding)
o configuring an Access Port EVC (e.g., in EPL and EVPL modes)
o configuring Port EFM-OAM

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 pro-
tection (Network or Access interfaces).
Provisioning Secure Access

Facilities are provided to ensure that access to the FSP 150CC-GE11x man-
agement system is secure. This could entail configuring:
• SNMP details
• Users, including:
o
Adding/Editing/Deleting Users
o
Editing Passwords
o
Editing GUI Login Time-outs
• Remote Authentication
Provisioning Alarms
Facilities are provided to modify alarm notification codes for given alarm condi-
tion types, displayed in the Alarms Pane. The options available for notification
codes are: Critical, Major, Minor, Not Alarmed or Not Reported. For further infor-
mation on Alarm Monitoring see Alarm Generation and Monitoring on p. 110.
Provision Environmental Alarm Inputs -

GE114H/GE114PH
The GE114H/GE114PH provide 4 dry contact environmental alarm inputs which
are accessed via an RJ45 connector in the front of the unit. For each environ-
mental input the 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).
Provisioning Cable Length Benchmarks

Cable length benchmarks (up to 5 per Access Port) can be entered so that when
future Etherjack® Diagnostics are performed (see Etherjack® Diagnostics on
p. 62), a test operator can quickly refine the fault location to a particular seg-
ment.
Provisioning Performance Monitoring

Facilities are provided to edit PM threshold levels and initialize PM registers as
a precursor to monitoring performance (see Etherjack® Performance Monitoring
on p. 61).

Low Touch Provisioning

The Low-Touch Provisioning (LTP) feature provides a method for automatically
configuring a device with a default, customer-defined service configuration. This
feature can work in a wide variety of provider (or client) network configurations.
LTP minimizes the manual interventions required. The FSP 150CC-GE11x LTP
can:
• Install specified Software Image from a remote server,
• Download a Config file from a remote server, reset the NE to System
Defaults database, and restart apply the Config-File against the System
default settings.
LTP communicates with an installation DHCP server to retrieve the information
of system software and the configuration files. The FSP 150CC-GE11x is
designed to support LTP on the Network Ports, Access Ports and DCN Port.
LTP interacts with the following functions and features to do its jobs:
• DHCP/BOOTP Client
• TFTP, SCP, SFTP or FTP Clients
• Software Download/Upgrade
• CLI command file download and processing
LTP requires DHCP to work. DHCP can be enabled on:
• A Management Tunnel on Network Port.

• A Management Tunnel on Network Port or Access Port.
• The Management DCN Port.
In FSP 150CC-GE11x, a Management Tunnel with DHCP enabled on the Net-
work Port one is configured as factory default.
The management tunnel provisioned in factory default is the support

for LTP since FSP 150CC-GE11x release 5.4.
PS
In the case an NE is upgraded from 5.2 or 5.3 to 5.4 or above, there

could be no qualified management tunnel existing. The user may
Note
have to manually create one.
The DHCP server for the Installation Network has to be properly configured to
support the LTP function. The FSP 150CC-GE11x expects to receive not only
an IP address, but looks for a boot configuration file name and a server address
from which to retrieve the file. Since this boot configuration file is usually specific
for each NE, the DHCP server has to be able to identify the specific NE. If the
NE does not receive the “file name” and “next server” information, LTP is not
invoked.
After getting a valid IP address on the installation network, the FSP
150CC-GE11x accesses the “Next Server” to downloads the “Filename”
(BOOTP configuration file) via Trivial File Transfer Protocol (TFTP). Once a
BOOTP configuration file is downloaded and validated. The BOOTP configura-
tion file causes the FSP 150CC-GE11x to check the software version and install

the system software if necessary, and then download a CLI Configuration files
to perform in-depth provisioning.
The FSP 150CC-GE11x can reboot while running the Boot Configuration file,
(e.g., after installing the system software) but the BOOTP file isn’t in persistent
memory. This means the NE repeats all LTP actions including the authentica-
tion step, accessing the installation DHCP server and the “next server” to get the
BOOTP Config file again and re-examining each directive. When it gets to the
end of the BOOTP Config file, the FSP 150CC-GE11x should be properly provi-
sioned to access the traffic-carrying network.
LTP Process
LTP is always on. Every time when the Device is initialized or reinitialized, it
tries to communicate with the installation DHCP server.
Step 1 LTP starts at system boot.
Step 2 If an Management interface with DHCP enabled is detected. LTP per-
forms a DHCP Exchange to determine the Boot Configuration File-
name and Next Server.
FSP 150CC-GE11x supports a Boot Configuration Filename up to 64
PS
characters long. A Boot Configuration File with a name longer than

that cannot be downloaded successfully.A LTP failure alarm is raised.
Note
Step 3 Download Boot Configuration File from the Next Server.

Step 4 Verify the version number of the Boot Configuration File.
Step 5 If the Boot Configuration File matches, compare the software version
specified by the software directives. If the same, proceed to Step 9.
Step 6 If the software version doesn’t match, download the designated soft-
ware from the specified server.
Step 7 Install downloaded software image.
Step 8 Activate the newly installed software image and reboot. The reboot
cause the LTP process to be restarted from Step 2.
Step 9 Download the CLI Config file as specified by the Restart Config direc-
tive.
Step 10 Restore NE to System Default Database and reboot.
Step 11 Load the CLI Config file downloaded in Step 9. If a failure occurs
during the application of the CLI command file, the system discontin-
ues processing the CLI Configuration file and then continue normal
initialization. An LTP Failure condition/alarm is not raised. Additional
diagnostic information can be retrieved with the system's config-
file-status command.
Step 12 The LTP process is terminated by commands in the CLI Config file.
System works normally.

The NE could reboot once or twice when the LTP is progress:

• The NE reboot once, if only either software upgrading or con-
fig-file load is required.
PS
• The NE reboot twice, if both software upgrading and config-file
Note
load are required.
• The NE doesn’t reboot, if neither software upgrading and con-
fig-file load are required.
Boot Configuration File Format

As part of Low Touch Provisioning (LTP), the installation network DHCP
server’s offer to the FSP 150CC-GE11x includes a BOOTP file name and next
server address. The LTP BOOTP file is a text based boot configuration file.
Upon successful completion of the DHCP process, the boot configuration file is
downloaded from the specified server using TFTP. For a successful download-
ing, the Boot Configuration File must has a filename not longer than 64 charac-
ters.
FSP 150CC-GE11x supports a Boot Configuration Filename up to 64

PS
characters long. A Boot Configuration File with a name longer than

that cannot be downloaded successfully.A LTP failure alarm is raised.

Note
The boot configuration file generally contains the following:

• Version Directive - the version of the boot configuration file. If LTP cannot
identify or does not support the version, it raises an “LTP Failure” condi-
tion/alarm and stops processing the boot configuration file.
• Verify Software Directive - compares the current active software revision
level to the software revision called out in the directive. If the software revi-
sion matches, no action occurs and LTP proceeds to the next directive. If
the revision levels do not match, LTP downloads via TFTP, SCP, SFTP or
SCP and installs the specified software image, then reboots the NE. After
the reboot completes, LTP restarts from the beginning and passes this step
without performing a software download.
It recommended to download the software image with SCP, SFTP or

PS
SCP protocol but not TFTP. Using TFTP can take longer than
acceptable. TFTP was designed as a slow protocol.
Note
• Download Restart Config Directive - downloads a text-based CLI command

configuration file via TFTP, SCP, SFTP or SCP and applies it to the running
configuration. For information on the creation of CLI configuration files, see
CLI Configuration Files on p. 375.
• Comments - A “#” (hash mark or pound sign) is used to identify a comment,
and the parser ignores all characters from this character to the next carriage
return. Comments are used to clarify the information contained in the boot

configuration file to human readers of the file. Blank lines are also ignored
by the parser.
Among the Boot Configuration File components:

• Version Directive is mandatory. A mismatch or absence of this
part results in LTP failure.
PS • Verify Software Directive is optional.
Note • Download Restart Config Directive is optional.
• Comments are Optional.
Version Directive Syntax

The FSP 150CC-GE11x only accepts a Boot Configuration File with version
number:
version F3-01.00
Example of Version Directive:

# "version" directive
#
# Syntax:
#
# version <major>.<minor>
#
# where:
#
# <major> - a two-digit "major" number
# <minor> - a two-digit "minor" number
#
# NOTE: A "version" directive MUST be the first directive in a boot
# configuration file.
#
# There SHOULD be at least ONE "version" directive in a boot
# configuration file. There SHOULD be ONLY one "version" directive
# in a boot configuration file. ALL "version" directives are
# processed and ALL are validated.
#
# If NO "version" directive is found, then no other
# directives can be processed.
#
# Special Case: If no directives are specified, then LTP
# will succeed. (do nothing)
#
# Example:
#
# version F3-01.00
#
version F3-01.00
Verify Software Directive Syntax

This directive should be placed in the boot configuration file before any "down-
load config" directives.
For example:
# "verify-software" directive
#
# Syntax:
#
# verify-software <version> tftp <serverIpAddr> <filepath/filename>
# verify-software <version> scp <serverIpAddr> <username> <filepath/filename>
#

# where:
#
# <version> - a version in the following format "xxx.yyy.zzz"
# where "xxx", "yyy" and "zzz" specify the software
# image release version "major.minor.build".
# <serverIpAddr> - a decimal dotted notation IPv4 address
# <username> - a username to use for the SCP client. This
# username must exist on the 825.
# <filepath/filename> - a file path and name with standard characters
#
# NOTE: The TOTAL directive length must not exceed 512 characters!
#
# There MUST be at most ONE "verify-software" directive in a boot
# configuration file. There MAY be NO "verify-software" directives
# in a boot configuration file.
#
# Example:
#
# verify-software 2.1.329 tftp 10.10.32.10 FSP825_2.1.329.img
# verify-software 2.1.329 scp 10.10.32.10 user1 FSP825_2.1.329.img
#
verify-software 5.4.1-249 sftp 172.23.191.253 zeno 123456
/home/zeno/fsp150cc-ge114.5.4.1-249.img
If the software upgrade fails, the system is in an unusable state and requires
manual intervention. There is no mechanism to limit the number of LTP attempts
to perform the software upgrade.
Downloading software image with TFTP is not recommended, which

PS
can take time longer than acceptable. This is because TFTP was
designed as a slow protocol.
Note
Download Restart Config Directive Syntax

One “Download Restart Config” directive can be specified in the boot configura-
tion file.
Only one “Download Restart Config” directive can be specified in the

PS
boot configuration file.

A second “Download Restart Config” directive is never executed.
Note
For example:
# "download-config" directive
#
# Syntax:
#
# download-config tftp <serverIpAddr> <filepath/filename>
# download-config scp <serverIpAddr> <username> <filepath/filename>
#
# where:
#
# username must exist on the 825.
#
#
# There MAY be no, one, or more "download-config" directives
# in the boot configuration file.
#

# Example:
#
# download-config tftp 10.10.32.10 configfiles/CLIconfig1
#
download-config tftp 10.10.32.10 configfiles/ConfigFile2
#
#
# <end>
In the example above, the CLI files are downloaded using the TFTP client.
If a failure occurs during the application of the CLI command file, the system dis-
continues processing the CLI Configuration file and then continue normal initial-
ization. An LTP Failure condition/alarm is not raised. Additional diagnostic
information can be retrieved with the system's configfile-status command.
In the CLI configuration File downloaded, the user must include commands to
ensure that the LTP process is appropriately terminated. Usually, this is
achieved by preventing the NE to communicate with the Installation DHCP
again. In order of this, the user can:
• Disabled DHCP on the Management Interface (Management Tunnel, DCN).
• Delete it the Management Interface (only applies if the Management Inter-
face is a Management tunnel).
• Disable the management interface (only applies if the is DCN).
In the cases where LTP download a CLI Configuration
File, but the Configuration file includes no commands to
disable DHCP on the Management tunnel or delete the
Management tunnel, the NE falls into an endless LTP
loop.
NOTICE This is because LTP reboot the NE to apply the CLI
Configuration file. With a DHCP-enabled management
Tunnel existing, LTP will continue to download the same
Boot Configuration File and CLI Configuration file again,
which will cause another reboot.
Comments Syntax
#
# Low-Touch Provisioning Boot Configuration File
#
# ADVA Optical Networking NA, Inc.
#
# Date : Tue Sep 16 09:14:40 CDT 2008
# Author : Jack B. Nimble (jnibble@advaoptical.com)
#
#
# Comments are denoted with the "#" symbol and are ignored during processing.
Complete Sample Boot Configuration File

#
# Low-Touch Provisioning Boot Configuration File
#
# ADVA Optical Networking NA, Inc.
#
# Date : Tue Sep 16 09:14:40 CDT 2008
# Author : Steven W. Riggle (sriggle@advaoptical.com)
#

#
# Comments are denoted with the "#" symbol and are ignored during processing.
#
# "version" directive
#
# Syntax:
#
# version <major>.<minor>
#
# where:
#
# <major> - a two-digit "major" number
# <minor> - a two-digit "minor" number
#
# NOTE: A "version" directive MUST be the first directive in a boot
# configuration file.
#
# There SHOULD be at least ONE "version" directive in a boot
# configuration file. There SHOULD be ONLY one "version" directive
# in a boot configuration file. ALL "version" directives are
# processed and ALL are validated.
#
# If NO "version" directive is found, then no other
# directives can be processed.
#
# Special Case: If no directives are specified, then LTP
# will succeed. (do nothing)
#
# Example:
#
# version F3-01.00
#
version F3-01.00
# "verify-software" directive
#
# Syntax:
#
# verify-software <version> tftp <serverIpAddr> <filepath/filename>
# verify-software <version> scp <serverIpAddr> <username> <filepath/filename>
#
# where:
#
# <version> - a version in the following format "xxx.yyy.zzz"
# where "xxx", "yyy" and "zzz" specify the software
# image release version "major.minor.build".
# username must exist on the system.
#
#
# There MUST be at most ONE "verify-software" directive in a boot
# configuration file. There MAY be NO "verify-software" directives
# in a boot configuration file. (The first "verify-software"
# directive shall be processed and completed before checking
# for other "verify-software" directives.)
#
# Example:
#
# verify-software 2.1.139 tftp 10.10.32.10 FSPNNN_2.1.139.img
# verify-software 2.1.139 scp 10.10.32.10 user1 FSPNNN_2.1.139.img
#
verify-software 5.4.1-249 sftp 172.23.191.253 zeno 123456
/home/zeno/fsp150cc-ge114.5.4.1-249.img
#
# "download-config" directive
#
# Syntax:
#
# download-config tftp <serverIpAddr> <filepath/filename>
# download-config scp <serverIpAddr> <username> <filepath/filename>
#
# where:
#


# username must exist on the system.
#
#
# There MAY be no, one, or more "download-config" directives
# in the boot configuration file.
#
# Example:
#
# download-config tftp 10.10.32.10 configfiles/CLIconfig1
#
download-restart-config tftp 172.23.5.104 LTP_114H.log
#download-restart-config tftp 172.23.5.104 clifile1
#
#
# <end>
Alarm Generation and Monitoring

Alarm status is displayed in the Alarms Pane located at the bottom of the eVi-
sion screen. This provides constant visibility and access to current alarms,
enabling continuous alarm monitoring no matter what application is currently
selected.
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 3: eVision Web
Browser Management Tool.

FSP 150CC-GE11x Hardware Descriptions

The FSP 150CC-GE11x is a 1U Chassis system that comprises the following
main components:
• GE11x - Two Network interfaces that may be configured for copper
(10/100/1000BASE-T) or optical (100BASE-FX /1000BASE-X). Using both
ports provides 1+1 protection. Port 1 is fixed and always designated as a
Network port. Port 2 may be configured for LAG or 1+1 Network protection,
or as an Access port.
• GE112 - Two Access interfaces that may be configured for copper
(10/100/1000BASE-T) or optical (100BASE-FX/1000BASE-X). Ports 3 and
4 are Access ports. Port 2 may be configured as an Access port if Network
protection is not provisioned. The GE112 is a version of the product that
does not include Sync-E capability.
• GE114/GE114S/GE114H/GE114SH/GE114PH - Four Access interfaces
that may be configured for copper (10/100/1000BASE-T) or optical
(100BASE-FX/ 1000BASE-X). Ports 3 through 6 are Access ports. Port 2
may be configured as an Access port if Network protection is not provi-
sioned. The GE114/GE114H/GE114PH are versions of the product that do
not include Sync-E capability. The GE114S/GE114SH are versions of the
product that support Sync-E (ITU G.8262) and Precision Time Protocol
(IEEE 1588 v2). In addition to data traffic, the GE114PH supports Power
over Ethernet (PoE) and functions as Power-Supplying Equipment (PSE) to
devices that are IEEE 802.3at compatible.
• Local Management LAN Port (labeled MGMT LAN) - front mounted RJ-45
connector
• Local Serial Port (labeled RS-232) - front mounted RJ-45 connector
• USB Port - high speed USB 2.0 port with type A receptacle for wireless
management using a USB wireless adapter
• GE112/GE114/GE114S - A single integrated Power Supply Unit (AC,
-48VDC or +24VDC variant) with integral Cable Tie support
• GE114H/GE114SH/GE114PH - Two (redundant) Power Supply Units
(PSUs) with integral Cable Tie support (ordered separately). PSU Blank
Plates are not provided.
• GE114H/GE114PH - Environmental Alarm Input connector - front mounted
RJ45 connector
• GE114S/GE114SH - 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 (for future use)/PPS output connectors- front
mounted Mini-SMB connectors, one CLK output connector - front mounted
Mini-SMB connector
• GE114SH - one front mounted SMA GPS connector
• Serial Console Adapter, RJ-45 to DB9, used to connect to a DB-9 RS-232
port on the PC or Laptop.

• Rack/Wall Mounting Brackets (ordered separately)
For effective environmental protection from external objects of any

kind, the FSP 150CC-GE11x is intended to be protected from dust
and particles with all covers complete. To ensure that all components
PS
are adequately protected, do not operate the FSP 150CC-GE11x for
Note extended periods without supplying plugs for vacant electrical and
optical ports.
Single fiber (bi-directional), dual fiber and copper Small Form factor Pluggable
(SFP) transceivers are supported. ADVA Optical Networking strongly encour-
ages the use of ADVA Optical Networking sourced SFPs. No support is pro-
vided for systems that use SFPs other than those sourced by ADVA Optical
Networking. The SFP contains a software key that is checked by the FSP
150CC-GE11x prior to initialization. This check is performed to ensure that only
ADVA Optical Networking approved SFP units are used. SFP units are individu-
ally qualified by ADVA Optical Networking to ensure the quality of the optical
output and conformance to the MultiSource Agreement (MSA).
If the SFP transceiver and rate do not match the configured application, an SFP
mismatch alarm is raised. The port is then configured to prevent traffic from
passing. If SFP cannot pass ADVA check criteria, but the SFP transceiver and
rate do match the configured application, a “SFP is not qualified” standing condi-
tion is raised, and traffic is allowed. For more information on SFPs, see Sup-
ported SFP Interface in FSP 150CC GE11x R6.1 Technical Descriptions
document.
For information on connectors and LED descriptions, see Connector and LED
Descriptions on p. 114. For details on connector pin assignments, see Connec-
tor Pin Assignments on p. 181.
Chassis The dimensions of the chassis are:

Dimensions • GE112/GE114/GE114S width, without mounting brackets: 220 mm
• GE114H/GE114SH/GE114PHwidth, without mounting brackets: 443 mm
• Height, 1U: 44 mm
• Depth, without International Electrotechnical Commission (IEC) and optical
connectors: 218 mm. The depth allows the chassis to fit into a 300 mm
(11.81 in) deep European Telecommunication Standardization Institute
(ETSI) cabinet.
Cable Tie Cable handling for the FSP 150CC-GE11x is provided by means of an integral
Support Cable Tie Support. This is located on the mounting brackets which provides a
(Integral) means to tie down all cables.
Mounting The chassis may be positioned as a standalone unit or it may be rack mounted
Brackets 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 150CC
GE11x R6.1 Technical Descriptions document):
• Wall mounting

• Standard 19-inch, 23-inch rack or ETSI mounting for a single unit or dual
GE112/GE114/GE114S units, or for a single GE114H/GE114SH/GE114PH
• 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 GE112/GE114 units, or for a single GE114H/GE114PH.
All brackets are designed to be screwed to the sides of the chassis and the
screws supplied have ETSI compatible threads.
Integrated Power Supplies - GE112/GE114/GE114S

Power is supplied to the GE112/GE114/GE114S by a single integrated power
supply. Each GE112/GE114/GE114S variant may be ordered as Alternating
Current (AC), -48V or +24V Direct Current (DC) variants. The cable connector is
located on the far left side of the GE112/GE114/GE114S product.
In the event of a complete system power failure, the system maintains inte-
grated voltages for a period that is sufficient to allow a dying gasp alarm to be
raised via the in-band management channels (SNMP trap or 802.3ah EFM
“Dying Gasp” messages).
For more detailed specification information, see Power in FSP 150CC GE11x
R6.1 Technical Descriptions document.
Power Supply Units - GE114H/GE114SH/GE114PH

Power is supplied to the GE114H/GE114SH by two (optionally) redundant 24W
PSU modules. They mount in slots on the far left side of the unit. One variant of
Alternating Current (AC) and one variant of Direct Current (DC) PSUs are avail-
able. The 24W DC PSU is only for Central Office -48 VDC.
180 Watts, 60Watts or 95Watts AC and 95Watts DC (-48 VDC) power supplies
may be used for the GE114PH.The software can detected the PSU type
inserted. If two PSUs are equipped, and one PSU module fails or its input
source fails, the remaining module continues to power the system without inter-
ruption to system function.
The PSUs operate in Hot Standby (current sharing) mode. For
GE114H/GE114SH/GE114PH, cross-powering is supported (i.e., one AC and
one DC PSU can be used simultaneously), as long as both PSUs are on the
same power level. The GE114x may also be powered by a single PSU. If two
PSUs are equipped and one PSU module fails or its input source fails, the
remaining module continues to power the system without interruption to system
function.
In the event of a complete system power failure, the system maintains internal
voltages for a period that is sufficient to allow a dying gasp alarm to be raised
via the in-band management channels (SNMP trap or 802.3ah EFM “Dying
Gasp” messages).

Power Supply External Fuse Rating and Cabling

External Fuse The AC PSU external fuse should be rated as following with slow blow fuse:
Rating o 4 A for GE112/GE114/GE114S.
o 5 A for GE114H/GE114SH.
o 5 A for GE114PH.
The -48VDC PSU external fuse should be rated as following with slow blow
fuse:
o
4 A for GE112/GE114/GE114S.
o
5 A for GE114H/GE114SH/GE114PH.
The +24VDC PSU external fuse should be rated as following with slow blow
fuse:
o
20A for GE112/GE114/GE114S.
Power Cabling With the exception of the -48 VDC PSU for European applications, which comes
with an EU power cable, all PSU power cords must be ordered separately. The
AC power cord is 6 feet long and each DC power cord is 10 feet long, each wire
is 16 Gauge, stranded. For more detailed specification information, see Power
in FSP 150CC GE11x R6.1 Technical Descriptions document.
Connector and LED Descriptions
Refer to the following for FSP 150CC-GE11x connectors and LED descriptions
when performing the following procedures. They may be used as supporting
technical information for troubleshooting faults as well as connector and LED
location/identification. For connector pin designations, refer to Connector Pin
Assignments on p. 181.
Refer to Alarm Attributes, Probable Cause and Trouble Clearing on p. 537 for a
description of the alarm condition, probable cause, suggested trouble clearing
procedures, and associated LED indication. To clear alarm conditions, it is sug-
gested that you start by using the trouble clearing procedure in Recommended
Steps for Trouble Clearing on p. 535, using the associated eVision alarm condi-
tion.
Front Panel Connector Descriptions

All interface connections including power connectors are located at the FSP
150CC-GE11x front panel. The front panel of the GE112 is shown in Figure 60,
the front panel of the GE114 is shown in Figure 61. The font panel of the
GE114S is shown in Figure 62. The front panel of the GE114H is shown in
Figure 63. The front panel of the GE114SH is shown in Figure 64. The front
panel of the GE114PH is shown in Figure 65.
The following connectors are provided on the front panel of the FSP 150CC-
GE112/GE114x:
GE112
Four configurable 1GbE optical or 10/100/1000 Base-T copper LAN ports
(RJ45) - labeled 1 though 4:

• Port 1 is fixed and always designated as a Network port. Port 2 may be con-
figured for LAG or 1+1 Network protection, or as an Access port. The optical
Network port interfaces use single or dual SFP optical transceivers (SMF or
MMF) that support 1000 Base SX/LX/ZX. Optionally, the Network ports may
be configured as 100/1000 Base-T copper LAN ports.
• Ports 3 and 4 are Access ports and may be configured for optical or copper,
or copper SFP. (In addition, Port 2 may be provisioned as an Access port, if
Network protection is not used.) The optical LAN interfaces use an SFP
optical transceiver (SMF or MMF) that supports (1000 BaseLX10 or 1000
BaseLH) or single fiber (1000 Base BX10). Optionally, the Access ports
may be configured as 10/100 Base-T copper LAN ports (RJ45).
GE114x
Six configurable 1GbE optical or 10/100/1000 Base-T copper LAN ports (RJ45)
- labeled 1 though 6:
• Port 1 is fixed and always designated as a Network port. Port 2 may be con-
figured for LAG or 1+1 Network protection, or as an Access port. The optical
Network port interfaces use single or dual SFP optical transceivers (SMF or
MMF) that support 1000 Base SX/LX/ZX. Optionally, the Network ports may
be configured as 100/1000 Base-T copper LAN ports.
• Ports 3 through 6 are Access ports and may be configured for optical or
copper, or copper SFP. (In addition, Port 2 may be provisioned as an

Access port, if Network protection is not used.) The optical LAN interfaces
use an SFP optical transceiver (SMF or MMF) that supports (1000
BaseLX10 or 1000 BaseLH) or single fiber (1000 Base BX10). Optionally,
the Access ports may be configured as 10/100/1000 Base-T copper LAN
ports (RJ45).
Common to FSP 150CC-GE11x

• 10/100/1000 Base-T Management LAN port (RJ-45)
• RS-232 Serial Console (maintenance) port (RJ-45)
• USB port for management back-up or DCN access using a USB wireless
adapter
• AC, -48 VDC or +24 VDC power connector (variant / PSU specific for the
GE11x products)
• One (non-redundant) Power Supply Unit (PSU) for GE112/GE114/GE114S
• Dual (redundant) pluggable Power Supply Unit (PSU) for
GE114H/GE114SH/GE14PH
Clock Specific Connectors

• T1/E1 External Clock Input connector (labeled BITS IN) and T1/E1 External
Clock Output connector (labeled BITS OUT) are both front mounted RJ-48c
connectors (balanced 120 Ohm impedance)
• Time of Day input connector (labeled TOD) - front mounted RJ-45 RS-422
output only

• Pulse Per Second input (labeled PPS IN) (for future use) and a Pulse Per
Second output connector (labeled PPS) - both are front mounted Mini-SMB
- TTL (75 Ohm)
• External (10MHz) Frequency Reference output (labeled CLK) - front
mounted Mini-SMB (75 Ohm)
• Ground Position Satellite connector (labeled GPS) - front mounted SMA (50
Ohm)
Figure 60: GE112 Front Panel Connectors and LEDs (AC Variant)
Figure 61: GE114 Front Panel Connectors and LEDs (-48 VDC Variant)
Figure 62: GE114S Front Panel Connectors and LEDs (-48 VDC Variant)
Figure 63: GE114H Front Panel Connectors and LEDs

Figure 64: GE114SH Front Panel Connectors and LEDs
Figure 65: GE114PH Front Panel Connectors and LEDs
Table 2: Front Panel Connectors (Left to Right)

Section Connectors Description
AC power AC power connector on AC power
variant
DC power +24 VDC or -48 VDC power
PSU
connector on DC power variant.
Connectors are labeled +, - and

GND.
RS-232 RJ-45 RS-232 Serial Console
(maintenance) port
Management LAN RJ-45 10/100 Base-T
Management LAN port supports
auto-MDIX capabilities
USB USB 2.0 port with type A
receptacle supporting 3G/LTE
USB
interface for backup or DCN
access
Copper Ethernet 1-4 10/100/1000 Base-T copper LAN
Ports - GE112 ports (RJ45)
Optical Ethernet 1-4 SFP optics
Ports - GE112
Copper Ethernet 1-6 10/100/1000 Base-T copper LAN
Ports - GE114x ports (RJ45)
Optical Ethernet 1-6 SFP optics
Ports - GE114x
Environmental ALARM Provides 4 dry contact environmen-
Alarm Input Port - tal alarm inputs which are ac-
GE114H/ cessed via an RJ45 connector in
GE114PH the front of the unit.

Table 2: Front Panel Connectors (Left to Right) (Continued)

Section Connectors Description
BITS IN and T1/E1 External Clock Input and
BITS OUT Output, RJ-48c connectors
(balanced 120 Ohm impedance)
TOD Time Of Day, RJ-45 connector
Synchronization - PPS IN (for future Pulse Per Second connector
GE114S use) (input)
/GE114SH PPS Pulse Per Second connector
(output)
CLK Clock (10MHz) connector (output
only)
GPS (GE114SH) GPS Antenna connector
System LEDs
The names and functions of each general system LED are described in the fol-
lowing table.
Table 3: System LEDs
LED Name Color Definition
PSU-n Off No input power detected
Status Input power present and PSU operating
(GE114H Green
with normal limits
/GE114SH PSU fail or input power out of spec
/ GE114PH) Red

Table 3: System LEDs (Continued)

LED Name Color Definition
Off No Power detected
Green Normal operation
Equipment Initializing. The card is out of
the boot loader and into the kernel.
Software image validation is taking place
Flashing-Green
and boot kernel, system kernel, system
initialization, and system applications are
all being started.
Equipment initializing. After power rails are
within tolerance, the hardware sets this
Yellow
LED to solid yellow and it stays yellow
while the processor is initializing.
STA Equipment initializing.
• The card is in the boot loader stage.
Either MTPS is being loaded and the
self-diagnosis is running or the KDI is
Flashing Yellow
validated and loaded.
• It also can indicate that software down-
load or database backup/restore oper-
ations are in progress.

Equipment Failure. Also, during boot-up,
the Status LED is momentarily lit Red until
Red
all card power rails are up and within toler-
ance.
Flashing Red Equipment doesn't match provisioning.

Local Management Port LEDs

The names and functions of each local management LAN port LED are
described in the following table.
Table 4: Local Management Port LEDs

Connector LED Color Definition
RJ-45 (LAN) Off No link
Link/Activity Link/ Green Link
Activity Flashing- Activity
Rate Green
Off No link
Rate Yellow 10 Mbps operation
Green 100 Mbps operation
Ethernet Port LEDs

Port 1 is fixed as a Network port and Port 2 may be provisioned for Network pro-
tection, or as an Access port - if protection is not used. Ports 3 through 6 are
Access ports.
Each optical Ethernet port provides one LED (Link / Facility) as defined in the
following table.
Table 5: Network Optical Ethernet Link and Rate LEDs

SFP Off Unassigned
Green Working (Link detected)
Link/ Flashing Green Traffic (TX or RX)
Facility Flashing Yellow Loopback
(LK/FAC)
Yellow Remote Fault / Degraded
Red Link Fault / No Link
Each RJ-45 electrical Ethernet port has two LEDs associated with the connec-
tor. 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).

Table 6: RJ-45 Electrical Port Connector LED Definitions

RJ-45 • Off
Off
• 10 Mbps
Rate
Yellow 100 Mbps
Rate Green 1000 Mbps
Off Unassigned
Link / Facility
Green Link Detected
Flashing Green Activity
Link /
Flashing Yellow Loopback
Facility
Yellow Remote Fault /
Degraded
Red Link Fault / No Link
Rear Panel Connector Description

The rear panel of the FSP 150CC-GE11x includes an earth terminal (frame
ground) point located on the rear of the unit.
Figure 66: GE112/GE114/GE114S Rear Panel Frame Ground Point

Earth terminal point

(optional connection)
Figure 67: GE114H/GE114SH/GE114PH Rear Panel Frame Ground Point


122

Chapter 2
Physical Installation
Introduction
This Chapter deals with the physical installation of the FSP 150CC-GE11x,
PSUs, and the external cabling for power, management and traffic to and from
the chassis. Additionally, this chapter includes references to technical informa-
tion and procedures elsewhere in the document that are needed or helpful in
successfully completing the installation process.
This section provides the information required to successfully install an FSP
150CC-GE11x system. Installation consists of:
• The physical installation of hardware, which includes:
o
Preparing for installation
o
Mount the FSP 150CC
o
Connect optional earth (frame ground) cable
o
Install PSUs (GE114H/GE114SH/GE114PH)
• Connect cables and power up the equipment
Only suitably qualified personnel may install FSP 150CC equipment.

It is recommended that personnel installing the FSP 150CC be
trained and authorized by ADVA Optical Networking. The training
necessary to install, operate and service the FSP 150CC includes the
following as a minimum:
PS
• background information on optical fiber communication systems

Note
• safety information concerning the laser classification system and
the hazard levels of the FSP 150CC
• guidance on the safe use of the FSP 150CC equipment.

To successfully install and commission a FSP 150CC, the following sections

and the steps must be followed in the order that they are given. Observe the fol-
lowing precautions when performing the installation tasks in this chapter.
Invisible Laser Radiation
(1) The FSP 150CC is a class 1 laser product when equipped with
Small Form Factor Pluggable (SFP) modules, approved by ADVA
Optical Networking.
(2) Do NOT stare into the beam of any optical (e.g., SFP) Interface or
CAUTION
view directly with optical instruments.
(3) SFP Interfaces contain laser emitters on the front of the unit oper-
ating at a wavelength of 850/1310/1550/1610nm (and various ranges
in between), Class 1 AEL.
Do not touch the backplane under any circumstances when power is

applied.
WARNING
This product contains Electro-Static Sensitive Devices.

Appropriate anti-static handling precautions should be followed (i.e.,
IEC 61340-5-1:1998).
Preparing for Installation

Before physically installing the FSP 150CC the following tasks must be com-
pleted:
• Verify site readiness. See Verifying Site Readiness.
• Ensure that all cables, tools and equipment required for installation, are
readily available. See Requirements on p. 126.
• Unpack and inspect the FSP 150CC equipment. See Unpack and Inspect
the FSP 150CC Equipment on p. 130.
Verifying Site Readiness

Before installation ensure that the site is suitable.
Check the items listed below. If any check fails, rectify the problem before con-
tinuing.
If the FSP 150CC is to be mounted in a rack:
• Is a rack available and is there sufficient space in it?
Height 44 mm
GE112/GE114/
Width 220 mm (without brackets)
GE114S
Depth 218 mm
Height 44 mm
GE114H/GE114
Width 443 mm (without brackets)
SH/GE114PH
Depth 218 mm

Chapter 2 Physical Installation
The chassis is designed for passive (fanless) air cooling. The number
of units that can be stacked are determined by the environment the
unit will be installed in, not the unit type that will be installed. The
following are requirements for maintaining internal temperatures
within design limits:
When units are installed in an I-Temp (Industrial) environment, units
can be stacked 1 high and must be mounted as a single unit only.
Dual unit mounting in an I-Temp environment should not be
implemented. When units are installed in a C-Temp (Commercial)
PS
environment, units can be stacked 4 high.

Note If it is necessary to install a single FSP 150CC-GE11x unit in an
I-Temp environment or 4 rows of FSP 150CC-GE11xs in a C-Temp
environment above other heat producing components, it is
recommended that a heat deflector is installed below the FSP
150CC-GE11x(s). If it is necessary to install heat sensitive equipment
above a single FSP 150CC-GE11x unit in an I-Temp environment or
4 rows of FSP 150CC-GE11xs in a C-Temp environment, it is
recommended that a heat deflector is installed above the FSP
150CC-GE11x(s).
• Has the rack been correctly leveled and secured to the floor?
• If appropriate, has the rack been grounded by a Safety Ground Cable

according to local office policy?
• Are the appropriate rack / wall mounting kit(s) at hand?
If the FSP 150CC is to be mounted on a wall:
• Is there sufficient clearance on either side of the chassis so that the air
vents are not obscured when the chassis is positioned?
• Is there sufficient clearance between the unit along the wall to perform the
necessary work?
If the FSP 150CC is to be provisioned locally, is AC power available for a main-
tenance PC?
Is AC or –48 VDC or +24VDC power available for the FSP 150CC?
Are the following AC and/or DC power input specifications met?
AC Voltage 120 / 240 VAC nominal, 50-60Hz

nominal, external fuse should be rated
at 4 Amp for GE112/GE114/GE114S, 5
Amp for GE114H/GE114SH/GE114PH.
–48 VDC Voltage (Central Office –48 / –60 VDC nominal (external fuse: 4
Type) Amp rating for GE112/GE114/GE114S
or 5 Amp rating for GE114H/GE114SH
/GE114PH).
+24 VDC Voltage (Mobile +24 VDC nominal (external fuse: 20
Backhaul) Amp rating for GE112/GE114/GE114S)

Max Power Consumption, DC/AC 16.8W for GE112

power
24W for
GE114/GE114S/GE114H//GE114SH
64W for GE114PH with 60W AC PSU
176W for GE114PH with 180W AC PSU
102W for GE114PH with 95W AC/DC
PSU
Connectors IEC-60320/C14 AC socket / DC input,
Terminal block
Are the following operating temperature specifications met?
Operating Temperature –40C to +65C

Max Relative Humidity Max. 95% (non-condensing)
Requirements
In order to install the FSP 150CC, several types of cables, tools, equipment and
software applications are needed. The requirements are described in the follow-
ing sections.
Cables
Ensure that the cable types under the following headings are readily available,
as appropriate, for installation.
Power Cables Alternating Current

Straight connection International Electrotechnical Commission (IEC) lead with
Central European, UK, US plug. One is required for each AC power supply vari-
ant, with external fuse rated at 4 Amp for GE112/GE114/GE114S, 5 Amp for
GE114H/GE114SH/GE114PH.
Direct Current--48V
For connecting the FSP 150CC to a fuse panel use a Direct Current (DC) power
cable (Power wires AWG 16) and 4 Amp rating for GE112/GE114/GE114S or 5
Amp rating for GE114H/GE114SH/GE114PH. DC power cables are not sup-
plied with FSP 150CC equipment and must be ordered separately. See Equip-
ment Accessories in FSP 150CC GE11x R6.1 Technical Descriptions
document.
Direct Current- +24V

For connecting the FSP 150CC to a fuse panel use a Direct Current (DC) power
cable (Power wires AWG 16) and 20 Amp rating for GE112/GE114/ GE114H
slow blow fuses. DC power cables are not supplied with FSP 150CC equipment
and must be ordered separately. +24V power cannot be applied to
GE114H/GE114SH/GE114PH. See Equipment Accessories in FSP 150CC
GE11x R6.1 Technical Descriptions document.

Frame Ground An optional Earth (Frame Ground) connection may be attached to the Earth ter-
Cable minal point, located at the rear of the unit. Each FSP 150CC unit is supplied with
an Earth Terminal Kit and a 10 foot, 16 gauge grounding cable, terminated with
a round connector at one end and a slotted connector at the other end. During
installation, the ground cable is terminated at the rear of the unit at one end and
terminated at a site designated frame mounting point or ground bar at the other
end. A terminal tab is provided in the Earth Terminal Kit for optional push-on
connection to the Earth terminal point.
Fiber-optic Use fiber-optic cables that support distances up to the maximum drive distance.
Cables Both single mode (9/125µm) and multi-mode (50/125µm and 62.5/125µm) are
supported. (Note that the fiber type (SM/MM) must match the SFP module type.)
Do fiber optic cables have correct connectors?
Are the appropriate Small Form Factor Plugables (SFPs) identified and supplied
for each applicable Network/Access interface? The “FSP 150 Ethernet Access
Compatibility Matrix” document contains up-to-date information on which SFPs
are certified for each product. This document may be obtained through ADVA
Technical Support or via the product support site on www.advaoptical.com.
Is there fiber for each applicable Network/Access interface?
Copper Cables Observe the following precaution for copper cables:

The intra-building port(s) of the equipment or subassembly is suitable
for connection to intra-building or unexposed wiring or cabling only.

The intra-building port(s) of the equipment or subassembly MUST
NOT be metallically connected to interfaces that connect to the
Outside Plant (OSP) or its wiring. These interfaces are designed for
use as intra-building interfaces only (Type 2 or Type 4 ports as
WARNING
described in GR-1089) and require isolation from the exposed OSP
cabling. The addition of Primary Protectors is not sufficient protection
in order to connect these interfaces metallically to OSP wiring.
In order to achieve EMC conformance, shielded intra-building cabling

that is grounded at both ends is required for the following interfaces:
GE114H/GE114SH/GE114PH- Environmental Alarm Input (RJ45
WARNING interface).
Obtain and verify the following for copper cables:

Do all LAN port copper/electrical cables have RJ45 connectors?
Access Port Copper Connections

For EMI Class A required sites, a Category 5 cable terminated with RJ-45 con-
nectors may be used. The cable should be no longer than 100m and should be
compliant with the Institute of Electrical and Electronics Engineers (IEEE)
802.3:1998 Ethernet standard. See LAN Connector Pin Assignments on p. 182.
Local Serial Console Port Connection

For provisioning the FSP 150CC via the serial management port:

An adapter to the PC serial port (F, DB9) is required. See Serial Console Port
Connector Pin Assignments on p. 184. (The Serial Console Adapter is shipped
with the unit in the Accessory Kit, and may also be ordered separately; Part
Number 1036904035.)
Local Management LAN Port Connection

See LAN Connector Pin Assignments on p. 182.
3G DCN Port Connection

Insert the 3G modem into the USB port. Available ADVA Optical Networking
qualified 3G modems are as below:
• ZTEMT 119
• HW E1750
If cable extension is required, an ADVA Optical Networking qualified cable must
be used.
Environmental Alarm Port Connection - GE114H/GE114PH

For EMI Class B required sites, a Category 6 or 7 cable terminated with an
RJ-45 connector is required for all metallic interface connections. For EMI Class
A required sites, a Category 5 cable terminated with an RJ-45 connector may be
used for connection to the Environmental Alarm port. A customer-provided
cable shall consist of an RJ-45 connector on one end and wire connections at
the opposite end as required for the connecting equipment. Maximum length of
wire supported on alarm inputs: 100m (328 ft.) at 24 AWG. See Environmental
Alarm Connector Pin Description and Assignments - GE114H/GE114PH on
p. 184.
BITS IN and BITS OUT Port Connections

For EMI Class B required sites, a Category 6 or 7 cable terminated with RJ-48c
connectors is required for all metallic interface connections. For EMI Class A
required sites, a Category 5 cable terminated with RJ-48c connectors may be
used for connection to BITS IN and BITS OUT ports. See RJ-48c BITS Connec-
tor Pin Description and Assignment - GE114S/GE114SH on p. 185.
Time of Day (TOD) Port Connection

For EMI Class B required sites, a Category 6 or 7 cable terminated with RJ-45
connectors is required for all metallic interface connections. See Time of Day
(TOD) Connector Pin Assignments - GE114S/GE114SH on p. 186.
10 MHz Reference Clock (CLK) Port Connection

A cable terminated with mini-coax connector is required for connection to the
10MHz ports.
Pulse Per Second (PPS) Port Connection

PPS (out) port.

Ground Position Satellite (GPS) Port Connection

GPS port.
Tools
The tools described below are required for installation.
Screwdrivers
The following screwdrivers may be required during installation:
• a No.1 Pozi or Phillips screwdriver to attach DC power cables
• a No.2 Pozi or Phillips screwdriver to attach chassis rack mounting brackets
• a flat blade screwdriver to lock PSUs into chassis
ESD Protection
As the FSP 150CC contains electro-static sensitive devices, a grounded
anti-static wrist or heel strap is required when handling the unit to reduce elec-
tro-static charges.
Compressed Air
Canned, dry, oil-free compressed air for removing dust or debris is required.
DC Power Cabling
For connecting DC powered FSP 150CC power supply units, you need the fol-
lowing items:
• Screwdriver
• Wire wrap tool
• Wire cutters
• Wire strippers
• Volt meter
• Fuse panel
• Other power related tools and supplies as required by local practices
Optical Equipment
The following optical equipment is required during installation:
• signal/protocol generator or Bit Error Rate Tester (BERT)
• variable or fixed attenuators in the range 3dB to 11dB or fiber spools provid-
ing equivalent attenuation
• an optical power meter calibrated for the required wavelength(s)
• Optical fiber cleaning materials

Personal Computer
When provisioning the FSP 150CC, a personal computer or laptop with telnet or
SSH is required, with an RJ-45 Ethernet patch cable (cross-over or
straight-through) and an RJ-45 to F, DB9 adapter (The Serial Console Adapter
is shipped with the unit in the Accessory Kit, and may also be ordered sepa-
rately; Part Number 1036904035.)
Use a PC or Laptop running the OS MS Windows version XP, Vista or Windows
7 with:
• an unused serial RS-232 port
• a VT100 or ANSI compatible terminal emulation program (e.g., Tera Term
Pro Web 3.1.3) loaded.
Unpack and Inspect the FSP 150CC Equipment

Depending on the order, a FSP 150CC shipment may consist of a number of
equipment packs.
This product contains electro-static sensitive devices.
IEC 61340-5-1:1998).
Further details on equipment packs and part numbers are given in
PS
FSP 150CC GE11x R6.1 Technical Descriptions document.

Note
Verify the contents of the shipment and the condition of the equipment as soon
as it arrives. Use the following procedure for unpacking and inspecting the
equipment.
Procedure
Step 1 Remove the FSP 150CC equipment from its shipping cartons.
Step 2 Compare the equipment in each carton with the equipment lists in this
section. If there are discrepancies, notify ADVA Optical Networking
immediately with details of the discrepancies (see Obtaining Techni-
cal Assistance on p. 34).
Step 3 Check all components. If shipping damage is discovered notify ADVA
Optical Networking immediately (see Obtaining Technical Assistance
on p. 34). Please have the following information available:
• Part number of the equipment pack
• Serial and version number of the damaged unit
• Description of the damage
• How the damage may prevent successful installation
Step 4 If any FSP 150CC equipment is to be returned to ADVA Optical Net-
working, re-pack the equipment in the original carton. For details on
returning FSP 150CC equipment refer to Returning Equipment on
p. 131.

Step 5 Unless the equipment is to be installed immediately, put all equipment

back in the packaging, otherwise proceed with the installation.
End of Procedure
Returning Equipment
If you need to return equipment, use the following procedure.
IEC 61340-5-1:1998).
If returning equipment to ADVA Optical Networking for repair or

replacement, use the original packaging material for optimum equip-
PS
ment protection.
Note
Procedure
Step 1 Repack the FSP 150CC equipment in the original packaging for opti-
mum equipment protection.
Step 2 Contact ADVA Optical Networking for assistance. See Obtaining
Technical Assistance on p. 34 for contact details.
End of Procedure

Install the FSP 150CC-GE11x

This section details the installation procedures for individual FSP 150CC Base
Unit. A full description of the FSP 150CC components covered can be found in
FSP 150CC-GE11x Overview on p. 27. Component part numbers and technical
specifications can be found in FSP 150CC GE11x R6.1 Technical Descriptions
document.
The chassis is designed for passive (fanless) air cooling. See following note.
of units that can be stacked are determined by the environment the
unit will be installed in, not the unit type that will be installed. The
following are requirements for maintaining internal temperatures
within design limits:
When units are installed in an I-Temp (Industrial) environment, units
can be stacked 1 high and must be mounted as a single unit only.
Dual unit mounting in an I-Temp environment should not be
implemented. When units are installed in a C-Temp (Commercial)
PS
environment, units can be stacked 4 high.

Note If it is necessary to install a single FSP 150CC-GE11x unit in an
I-Temp environment or 4 rows of FSP 150CC-GE11xs in a C-Temp
environment above other heat producing components, it is
recommended that a heat deflector is installed below the FSP
150CC-GE11x(s). If it is necessary to install heat sensitive equipment
above a single FSP 150CC-GE11x unit in an I-Temp environment or
4 rows of FSP 150CC-GE11xs in a C-Temp environment, it is
recommended that a heat deflector is installed above the FSP
150CC-GE11x(s).
See the figures below to have a more intuitive understanding of the installation
of different units in different environments.
Figure 68: Install Half-width Units in Standard Rack in I-Temp Environment

Figure 69: Install Half-width Units in Standard Rack in C-Temp Environment
Figure 70: Install Full-width Units in Standard Rack in I-Temp Environment


Figure 71: Install Full-width Units in Standard Rack in C-Temp Environment
Before installing FSP 150CC, refer to Preparing for Installation on p. 124, for
details on site verification, the tools and equipment required for installation and
procedures for installing the FSP 150CC.
To avoid eye injury from debris, always wear safety
WARNING glasses when working with canned compressed air.

IEC 61340-5-1:1998).
There are two procedures for mounting the FSP 150CC-GE11x, depending on
the product type. Refer one of the following procedures for the particular product
being installed:
• Mounting the GE112/GE114/GE114S on p. 135
• Mounting the GE114H/GE114SH/GE114PH on p. 146
For GE114H/GE114SH/GE114PH, power supply units (PSUs) are also
required:
• Install GE114H/GE114SH/GE114PH PSU on p. 153

Mounting the GE112/GE114/GE114S

The following section contains details for mounting a single or dual
GE112/GE114/GE114S into a rack, wall or as a stand alone unit.
GE112/GE114/GE114S Mounting Kits

Four rack mounting kits are available for mounting the GE112/GE114/GE114S:
o GE112/GE114/GE114S Single Rack Mounting Brackets (part number
1013904010)
o GE112/GE114/GE114S Dual Rack Mounting Brackets (part number
1013904011)
o GE112/GE114/GE114S Extended Rack Mounting Brackets (part num-
ber 1013904012)
o GE112/GE114/GE114S Wall Mounting Brackets (part number
1013904013)
For certain applications, multiple kits are required. See Equipment Accessories
in FSP 150CC GE11x R6.1 Technical Descriptions document for kit compo-
nents and refer to the following mounting options for details on which kits are
required for your application.
Mounting Options
The chassis may be rack mounted, wall mounted or placed as a standalone unit.
Use one of the following procedures to mount the FSP 150CC:
Table 7: FSP 150CC-GE11x Mounting Procedures
Single Dual
GE112/G GE112/ Mounting Kit(s)
Mounting Type Procedure
E114/GE GE114/ Required
114S GE114S
X 19” Standard or 1013904010 Mounting a Single
Extended GE112/GE114/GE114S via a
Standard or Extended 19”
Configuration on p. 136
X 23” Standard or 1013904010 and Mounting a Single
Extended 1013904012 GE112/GE114/GE114S via a 23”
X ETSI Extended 1013904010 and Standard or Extended / ETSI
1013904012 Extended Configuration on p. 137
X 19” Standard or 1013904011 Mounting Dual FSP
Extended GE112/GE114/GE114S via a 19”
Standard or Extended
Configuration on p. 139
X 23” Standard or 1013904011 and Mounting Dual FSP
Extended 1013904012 GE112/GE114/GE114S via a 23”
X ETSI Extended 1013904011 and Standard or Extended / ETSI
1013904012 Extended Configuration on p. 141

Table 7: FSP 150CC-GE11x Mounting Procedures

Single Dual
GE112/G GE112/ Mounting Kit(s)
Mounting Type Procedure
E114/GE GE114/ Required
114S GE114S
X Wall Mounted 1013904013 Mounting the
GE112/GE114/GE114S to a Wall
on p. 143
X Cabinet or Desk N/A Installing a GE112/GE114/GE114S
Standalone Chassis on p. 145
Mounting a Single GE112/GE114/GE114S via a

Standard or Extended 19” Configuration
Prior to mounting the GE112/GE114/GE114S, please check the mounting pack-
age contents carefully. One mounting kit is required: The
GE112/GE114/GE114S Single Rack Mounting Brackets kit (part number
1013904010).
The following components will be used in this procedure:
o
One 19” mounting bracket (short)
o
One 19” mounting bracket (long)
o
Four M3x5 CSK POZI screws
o
Four 12-24 x 0.5 phillips screws - or - Four M6x20 screws and four M6
nuts
(1) MECHANICAL LOADING. When mounting the equipment in a

rack ensure that a hazardous condition is not created by uneven
mechanical loading.
(2) Ensure that reliable grounding of the rack mounted equipment is
WARNING maintained. Particular attention should be given to supply
connections other than direct connections to the branch circuit.
Use the following procedure to install a single GE112/GE114/GE114S via a

Standard or Extended 19” configuration.
Procedure
The steps for fitting the appropriate mounting brackets are as follows:
Step 1 Take the chassis out of its packaging and put it on an anti-static sur-
face. If necessary, use canned compressed air to blow off any dust
particles.
Step 2 Secure the 19” mounting bracket (short) and 19” mounting bracket
(long) to the GE112/GE114/GE114S using four M3X5 CSK POZI
screws. If installing in a Standard configuration, set the brackets flush
with the GE112/GE114/GE114S. If installing in an Extended configu-
ration line up the rear set of bracket holes to the

GE112/GE114/GE114S so that the GE112/GE114/GE114S is

recessed from the front of the bracket. See Figure 72.
Step 3 Mount the GE112/GE114/GE114S to the 19” rack with four 12-24 x
0.5 phillips screws or four M6x20 screws and four M6 nuts.
Figure 72: Mounting a Single GE112/GE114/GE114S via EXT 19” Configuration

End of Procedure
Mounting a Single GE112/GE114/GE114S via a

23” Standard or Extended / ETSI Extended
Configuration
age contents carefully. Two mounting kits are required:
• GE112/GE114/GE114S 19” Single Rack Mounting Brackets kit (part num-
ber 1013904010)
• GE112/GE114/GE114S Extended Rack Mounting Brackets kit (part number
1013904012)


o One 19” mounting bracket (short)
o One 19” mounting bracket (long)
o Four M3x5 CSK POZI screws
o Two adapter brackets (extender tabs): 1U 19” to 23” or 1U 19” to ETSI
o Four 10-32 x 0.375 screws
o Four 12-24 x 0.5 phillips screws - or - Four M6x20 screws and four M6
nuts

mechanical loading.
Use the following procedure to install a single GE112/GE114/GE114S via a

Standard or Extended 23” / ETSI Extended configuration.
Procedure
particles.
Step 2 Secure the 19” mounting bracket (short) and 19” mounting bracket
(long) to the GE112/GE114/GE114S using four M3x5 CSK POZI
screws.
For 23” rack installation: attach one 1U 19” to 23” extender bracket to
each 19” mounting ear (short and long) using four 10-32 x 0.375
screws. For ETSI rack installation: attach one 1U 19” to ETSI
extender bracket to each 19” mounting ear (short and long) using four
10-32 x 0.375 screws See Figure 73.
If installing in a Standard configuration, set the brackets flush with the
GE112/GE114/GE114S. If installing in an Extended configuration,
line up the rear set of bracket holes to the GE112/GE114/GE114S so
that the GE112/GE114/GE114S is recessed from the front of the
bracket.
Step 3 Mount the GE112/GE114/GE114S to the 23” rack or ETSI rack with
four 12-24 x 0.5 phillips screws or four M6x20 screws and four M6
nuts.
End of Procedure

Figure 73: Mounting a Single GE112/GE114/GE114S via EXT 23” / ETSI Extended Configura-
tion
Mounting Dual FSP GE112/GE114/GE114S via a

19” Standard or Extended Configuration
age contents carefully. One mounting kit is required: the
GE112/GE114/GE114S Dual Rack Mounting Brackets Kit (part number
1013904011).
o Two 19” short rack mounting brackets
o Two dual mounting brackets
o Six M2x6 Phillips A2 screws
o Eight M3x5 CSK POZI A2 screws
o Four 12-24 x 0.5 phillips screws - or - Four M6x20 POZI screws and four
M6 nuts


mechanical loading.
Use the following procedure to install dual GE112/GE114/GE114Ss via a Stan-

dard or Extended 19” configuration.
Procedure
particles.
Step 2 If necessary, determine which GE112/GE114/GE114S will reside on
the left and which will reside on the right. Install one of the dual
mounting brackets to the right side of the left GE112/GE114/GE114S
using two M3x5 CSK POZI screws. Mount the other dual mounting
bracket to the left side of the right GE112/GE114/GE114S using two
M3x5 CSK POZI screws. Ensure that the dual mounting brackets are
“flipped” from one another (oriented so they will mate correctly when
they are attached in the next step). See Figure 74.
Step 3 Secure the dual mounting brackets to each other using six M2x6 Phil-
lips A2 screws (three on the top and three on the bottom). See
Figure 74.
Step 4 Secure a 19” (short) mounting bracket to the left unit using two M3X5
CSK POZI screws and secure the remaining 19” (short) mounting
bracket to the right unit using two M3x5 CSK POZI screws. See
Figure 74.
GE112/GE114/GE114S. If installing in an Extended configuration line
up the rear set of bracket holes to the GE112/GE114/GE114S so that
the GE112/GE114/GE114S is recessed from the front of the bracket.
Step 5 Mount the GE112/GE114/GE114S to the 23” rack or ETSI rack with
four 12-24 x 0.5 phillips screws or four M6x20 screws and four M6
nuts.
End of Procedure

Figure 74: Mounting Dual GE112/GE114/GE114S via EXT 19” Configuration

Mounting Dual FSP GE112/GE114/GE114S via a

23” Standard or Extended / ETSI Extended
Configuration
age contents carefully. Two mounting kits are required:
• GE112/GE114/GE114S Dual Rack Mounting Brackets Kit (part number
1013904011)
• GE112/GE114/GE114S Extended Rack Mounting Brackets kit (part number
1013904012)


o two 19” short rack mounting brackets
o two dual mounting brackets
o six M2x6 Phillips A2 screws
o eight M3x5 CSK POZI A2 screws
o Two adapter brackets (extender tabs): 1U 19” to 23” or 1U 19” to ETSI
o Four 10-32 x 0.375 screws
o Four 12-24 x 0.5 phillips screws - or - Four M6x20 POZI screws and four
M6 nuts

mechanical loading.
Use the following procedure to install dual GE112/GE114/GE114Ss via a Stan-

dard or Extended 23” / ETSI Extended configuration.
Procedure
Step 1 Perform all the steps in the following procedure: Mounting Dual FSP
GE112/GE114/GE114S via a 19” Standard or Extended Configura-
tion on p. 139.
Step 2 Attach the extension brackets to each end unit:
For 23” rack installation: attach one 1U 19” to 23” extender bracket to
each (left and right unit) 19” mounting ear using four 10-32 x 0.375
screws. For ETSI rack installation: attach one 1U 19” to ETSI
extender bracket to each (left and right unit) 19” mounting ear using
four 10-32 x 0.375 screws. See Figure 75.
GE112/GE114/GE114S. If installing in an Extended configuration,
line up the rear set of bracket holes to the GE112/GE114/GE114S so
that the GE112/GE114/GE114S is recessed from the front of the
bracket.
Step 3 Mount the dual-mated GE112/GE114/GE114S to the 23” rack or ETSI
rack with four 12-24 x 0.5 phillips screws or four M6x20 screws and
four M6 nuts.
End of Procedure

Figure 75: Mounting Dual GE112/GE114/GE114S via EXT 23” / ETSI Configuration
Mounting the GE112/GE114/GE114S to a Wall

Use the following procedure to install a single chassis on a wall.
The GE112/GE114/GE114S single rack/wall mounting kit (part number
1013904013) supports wall mounting applications, and contains the following
components:
o
two wall mounting brackets
o
four M3x5 CSK POZI A2 screws
Wall anchoring components are supplied by the installer, depending on the
mounting surface.
Procedure
Step 1 Select a suitable location to install the GE112/GE114/GE114S. The

wall material and mounting screws should be of sufficient strength to
bear the load of the GE112/GE114/GE114S (approx. 10 lbs).
particles.

Step 3 Secure the GE112/GE114/GE114S wall mounting brackets to the

FSP 150CC-GE11x using two M3x5 CSK POZI A2 screws each. See
Figure 76.
Step 4 Use the wall mounting brackets as a template for marking holes. Drill
mounting holes and insert wall anchors, as required.
Step 5 Attach the GE112/GE114/GE114S mounting bracket to the wall using
wall anchors and screws. See Figure 76.
End of Procedure
Figure 76: Installing GE112/GE114/GE114S Wall Mounting Brackets

Installing a GE112/GE114/GE114S Standalone

Chassis
Use the following procedure to install a chassis in a cabinet or on a desk. The
GE112/GE114/GE114S is cooled by radiating heat from the chassis. If the
GE112/GE114/GE114S is to be placed on a desktop or in a communications
closet environment, it is recommended that nothing be placed on top of the unit
or within 3 inches (7 cm.) of either side.
Procedure
particles.
Step 2 Mount four rubber feet to the bottom of the unit near each corner.
(Four white rubber feet are included in the Accessory Kit, which is
shipped with each unit.)
Step 3 Place the chassis on a secure flat surface, making sure that it is within
reach of the necessary connections.
End of Procedure

Mounting the GE114H/GE114SH/GE114PH

The following section contains details for mounting a single
GE114H/GE114SH/GE114PH into a rack, wall or as a stand alone unit.
Installing a Rack Mounted Chassis

The chassis is rack mounted using a mounting bracket pair. The currently avail-
able rack mounting brackets enable the chassis to be inserted into 19” ETSI or
23” standard size racks.
The mounting brackets are mounted on the GE114H/GE114SH/GE114PH on
the outside of the Left Hand (LH) and Right Hand (RH) side panels. The mount-
ing brackets are either mounted so that the chassis is flush with the rack, or
recessed in the rack to allow doors to be used.


mechanical loading.
Use the following procedure to install a rack mounted chassis.
Procedure
particles.
Step 2 Select the correct mounting bracket type from the
GE114H/GE114SH/GE114PH Rack Mounting Kit.
Step 3 Place one mounting bracket on one side of the
GE114H/GE114SH/GE114PH in the correct position, so that the four
screw holes on the chassis side panel and the mounting bracket are
lined up (one bracket for each side). The mounting bracket can be
used in the middle or the front of the side panels. See Figure 77.
Step 4 Align the shelf to the assigned frame location and insert two
counter-sunk M4 Pozihead Screws through the mounting holes (as
supplied in the Rack Mounting Kit) and tighten with a No.2 Pozi or
Phillips screwdriver. See Figure 78.
Step 5 Repeat Steps 3 and 4 for the opposite side of the chassis.

Step 6 Insert the chassis into the rack and secure each mounting bracket to
the rack using M5 (or M6) Pozihead Screws.
The following air flow rules apply:
of units that can be stacked are determined by the environment, not
the unit type installed. When units are mounted vertically in an I-Temp
(Industrial) environment, they require 1 RU of space above and below
each unit to maintain internal temperatures within design limits. When
installed in a C-Temp (Commercial) environment, units can be
stacked 4 high without providing space between units.
PS
If it is necessary to install 3 rows of GE114H/GE114SH/GE114PHs in

Note an I-Temp environment or 5 rows of GE114H/GE114SH/GE114PHs
in a C-Temp environment above other heat producing components, it
is recommended that a heat deflector is installed below the
GE114H/GE114SH/GE114PHs. If it is necessary to install heat sensi-
tive equipment above 3 rows of GE114H/GE114SH/GE114PHs in an
I-Temp environment or 5 rows of GE114H/GE114SH/GE114PHs in a
C-Temp environment, it is recommended that a heat deflector is
installed above the GE114H/GE114SH/GE114PHs.
End of Procedure
Figure 77: Installing Mounting Brackets for GE114H/GE114SH/GE114PH Rack Mounted Appli-
cations
23” STD Mount Bracket
19” STD Bracket 19” Extension Bracket
Wall Mount Bracket

STD ETSI Mount
ETSI Extension Bracket

Figure 78: Mounting the GE114H/GE114SH/GE114PH into a Rack
23” STD Mount Bracket on Rack
Mounting the GE114H/GE114SH/GE114PH to a Wall
Use the following procedure to mount a GE114H/GE114SH/GE114PH chassis
to a wall.
Procedure
Step 1 Select a suitable location to install the GE114H/GE114SH/GE114PH.

The wall material and mounting screws should be of sufficient
strength to bear the load of the GE114H/GE114SH/GE114PH
(approx. 10 lbs).
particles.
Step 3 Secure the GE114H/GE114SH/GE114PH wall mounting brackets to
the center screw holes on the unit using four screws each. See
Figure 76.
Step 4 Use the wall mounting brackets as a template for marking holes. Drill
mounting holes and insert wall anchors, as required.
Step 5 Attach the GE114H/GE114SH/GE114PH mounting bracket to the
wall using wall anchors and screws. See Figure 76.
Step 6 Connect a ground wire to one of the screws and connect the other
end to a suitable building (earth) ground.
End of Procedure

Figure 79: Installing GE114H/GE114SH/GE114PH Wall Mounting Brackets
Wall Mount Bracket


Connect Optional Earth Cable
Installing a GE114H/GE114SH/GE114PH Standalone

Chassis
Use the following procedure to install a chassis in a cabinet or on a desk.
Procedure
particles.
Step 2 Mount four rubber feet to the bottom of the unit near each corner.
(Four white rubber feet are included in the Accessory Kit, which is
shipped with each unit.)
Step 3 Place the chassis on a secure flat surface, making sure that it is within
reach of the necessary connections.
End of Procedure
An optional Earth (Frame Ground) connection may be attached to the Earth ter-
minal point, located at the rear of the unit. Each FSP 150CC-GE11x unit is sup-
plied with an Earth Terminal Kit and a 10 foot, 16 gauge grounding cable, to
facilitate this connection.
A terminal tab is provided within the Earth Terminal Kit for optional
push-on connection to the Earth terminal point, which is not the
PS
method described in the following procedure. The following procedure

Note connects to a frame ground point using the provided ground cable:
Procedure
Step 1 Using the M4x6 RAIS Pozi screw and one lock washer provided with
the Earth Terminal Kit, attach the 10 foot, 16 gauge grounding cable
to the Earth terminal point located at the rear of the FSP
150CC-GE11x unit. See Figure 80 through Figure 82.
Step 2 Connect the other end of the cable to the site designated grounding
location (frame connecting point or ground bar location). See
Figure 82.
Step 3 Dress the cable, as required.
End of Procedure

Figure 80: GE112/GE114/GE114S Rear Panel Frame Ground Point

Figure 81: GE114H/GE114SH/GE114PH Rear Panel Frame Ground Point


Figure 82: Grounding Detail
Optional
Terminal tab
Earth Terminal Kit and Ground Cable (for optional grounding)

Install GE114H/GE114SH/GE114PH PSU

Two slots are available in the GE114H/GE114SH/GE114PH for the installation
of two Power Supply Units (PSUs). These are the two left most rectangular slots
as viewed from the front of the chassis and stenciled PSU1 and PSU2 on the
cable tray.
Each PSU is equipped with a mechanical lock for locking the PSU into the
GE114H/GE114SH/GE114PH. The mechanical lock must be in the disengaged
position when inserting and removing a PSU into/out of the
GE114H/GE114SH/GE114PH.
Use the following precautions when installing PSUs:
The PSUs contain electro-static sensitive devices.

IEC 61340-5-1:1998).
Ensure that the correct PSU is installed in the corresponding unit. The
GE114H/GE114SH uses 24 Watts AC/DC PSUs whereas the
GE114PH requires 180 Watts, 95 Watts or 60 Watts AC and 95 Watts

PS
DC PSUs. To install a GE114PH with Power Redundancy, make sure

the power capacity of both PSU is the same. For associated part
Note
numbers, see Equipment Accessories in FSP 150CC GE11x R6.1
Technical Descriptions document.
The PSUs are hot swappable. The power to the

PS
GE114H/GE114SH/GE114PH does not need to be switched off

during the installation of a unit.
Note
Use the following procedure to install the GE114H/GE114SH/GE114PH Power

Supply Units.
Procedure
Step 1 Take the PSU out of its packaging and put it on an anti-static surface.
If necessary, use canned compressed air to blow off any dust parti-
cles.
Step 2 Insert the PSU into the appropriate chassis slot with the thumbscrew
oriented to the right.
Step 3 Push the PSU firmly until its connector engages with the backplane
connector inside the chassis.

Install GE114H/GE114SH/GE114PH PSU
Step 4 Hold the PSU in position and tighten the thumbscrew on the front
panel of the unit to secure it in place. See Figure 83 through Figure 85
for an example of the PSU variants.
End of Procedure
Figure 83: GE114H/GE114SH -48 VDC PSU Locking Mechanism
Status
-48 to -60V DC
- Gnd +
Detail
Figure 84: GE114H/GE114SH 120-240 VAC PSU Locking Mechanism
(24W)
Status
100 -
240V AC
Detail

Figure 85: GE114PH 120-240 VAC/95W DC PSU Locking Mechanism

(180W/95W/60W)
100 - 240V AC
Status
Detail
Install or Remove
GE114H/GE114SH/GE114PH Blank Plates
ADVA strongly recommended Redundant Power Supply Units for FSP 150CC-
GE114H/GE114SH/GE114PH. There are no Blank Plates provided.

Route and Connect Copper Cables

Observe the following precautions for routing and connecting copper cables:
The intra-building port(s) of the equipment or subassembly is suitable
for connection to intra-building or unexposed wiring or cabling only.
The intra-building port(s) of the equipment or subassembly MUST
NOT be metallically connected to interfaces that connect to the
Outside Plant (OSP) or its wiring. These interfaces are designed for
use as intra-building interfaces only (Type 2 or Type 4 ports as
WARNING described in GR-1089-CORE, Issue 5) and require isolation from the
exposed OSP cabling. The addition of Primary Protectors is not
sufficient protection in order to connect these interfaces metallically to
OSP wiring.
In order to achieve EMC conformance, shielded intra-building cabling

that is grounded at both ends is required for the following interfaces:
GE114H/GE114PH- Environmental Alarm Input (RJ45 interface).
WARNING
Use the following for connecting copper cables:
Table 8: Copper Cable Connections
Product Connection Type
Network and Access Ports
GE112 Four Ethernet combination ports that may be configured for copper
(10/100/1000 BaseT) or optical (100BaseFX/1000BaseX):
• 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.
GE114/GE114S Six Ethernet combination ports that may be configured for copper
GE114H/GE114SH/GE1 (10/100/1000 BaseT) or optical (100BaseFX/1000BaseX):
14PH
• 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.
Other Electrical Connections
All Ethernet DCN connection (labeled MGMT LAN).
All Local Serial port (labeled RS-232).
All USB port for ADVA Optical Networking qualified 3G modem
connection
All Optional earth ground cable.
GE114H/GE114PH Environmental Alarm Input, RJ-45 connector.

Table 8: Copper Cable Connections (Continued)

Product Connection Type
GE114S/GE114SH BITS IN - T1/E1 timing input connector, RJ-48c
BITS OUT - T1/E1 timing output connector - RJ48c
TOD - Time of Day input/output, RJ-45 RS-422/RS-232
PPS - front mounted min-SMB JACK connector, 75 Ohm
CLK - front mounted mini-SMB JACK connector, 75 Ohm
GE114SH GPS - front mounted SMA JACK connector, 50 Ohm

IEC 61340-5-1:1998).
For Class B EMI required sites, a Category 6 or 7 cable terminated

with RJ-45 / RJ-48c connectors is required for all metallic interface
PS
connections. For Class A EMI required sites, a Category 5 cable

Note terminated with RJ-45 / RJ-48c connectors may be used.
Access / Network Interface Copper Cables

For EMI Class A required sites, a Category 5 cable terminated with RJ-45 con-
nectors may be used. The cable should be no longer than 100m and should be
compliant with the Institute of Electrical and Electronics Engineers (IEEE)
802.3:1998 Ethernet standard. See LAN Connector Pin Assignments on p. 182.
PS

optical ports.
The copper connection has Auto MDIX enabled, which allows

PS
straight-through or cross-over cables to be used.

Note
Procedure
Step 1 Route the Access / Network interface cable(s) from the FSP
150CC-GE11x to the appropriate location. Repeat for each additional
port as needed.
Step 2 Connect one end of the Ethernet cable to the Access / Network Inter-
face port on the front panel of the FSP 150CC-GE11x. Repeat for
each additional port as needed.

Step 3 Connect the other end of the Ethernet cable to the Customer Equip-
ment. Repeat for each additional Access / Network Port copper cable.
Step 4 Dress cables, as required.
End of Procedure
Ethernet DCN Connections

See LAN Connector Pin Assignments on p. 182.
Procedure
Connect an Ethernet cable from a PC or Laptop to the DCN connection, as fol-

lows:
Step 1 Route the DCN Ethernet cable from the FSP 150CC-GE11x to the
appropriate location.
Step 2 Connect one end of the Ethernet cable to the 10/100BASE-T Ethernet
port of the DCN PC or Laptop.
Step 3 Connect the other end of the Ethernet cable to the RJ-45 Ethernet
port (labeled Management LAN) on the front panel of the FSP
150CC-GE11x.
End of Procedure
Serial Console Port Connection

This connection is used for provisioning the FSP 150CC via the serial manage-
ment port. An adapter to the PC serial port (F, DB9) is required. See Serial Con-
sole Port Connector Pin Assignments on p. 184. (The Serial Console Adapter is
shipped with the unit in the Accessory Kit, and may also be ordered separately;
Part Number 1036904035.)
This connection may be made prior to provisioning the FSP

PS
150CC-GE11x (see Operations Provisioning on p. 219).

Note
Procedure
Connect a cable for serial interface from a PC or Laptop to the FSP

150CC-GE11x RS-232 port, as follows:
Step 1 Route the serial console port cable from the FSP 150CC-GE11x to
the appropriate location.
Step 2 Connect one end of the cable to an unused DB-9 RS-232 port on the
PC or Laptop using the RJ-45 to F, DB9 adapter (ADVA Optical Net-

working PN 2036904035-01 or 1036904035, see Serial Console Port

Connector Pin Assignments on p. 184).
Step 3 Connect the other end of the cable to the RJ45 connector labeled
RS-232 on the front panel of the FSP 150CC-GE11x.
End of Procedure
USB Port Connections

Insert the 3G modem into the USB port. Available ADVA Optical Networking
qualified 3G modems are as below:
• ZTEMT 119
• HW E1750
If cable extension is required, an ADVA Optical Networking qualified cable must
be used.
Environmental Alarm Connections

(GE114H/GE114PH)
Up to 4 monitored devices can be connected to the GE114H/GE114PH’s 4 dry

contact alarm inputs. The dry contact alarm inputs are programmable to specify
the monitored condition and whether the alarm shall be raised on contact closed
or open.
required sites, a Category 5 cable terminated with RJ-45 connectors may be
used for connection to external equipment sourcing a relay contact for desired
alarms.
A customer-provided cable shall consist of an RJ-45 connector on one end and
wire connections at the opposite end as required for the connecting equipment.
Maximum length of wire supported on alarm inputs: 100m (328 ft.) at 24 AWG.
See Connector Pin Assignments on p. 181.
Procedure
Connect an Ethernet cable from a PC or Laptop to the DCN connection, as fol-

lows:
Step 1 Prepare a customer-provided cable with RJ-45 connector at one end
and wire connections at the opposite end as required for the connect-
ing equipment. Route the Environmental Alarm cable from the
GE114H/GE114PH to the appropriate location.
Step 2 Connect one end of the Environmental Alarm cable to the appropriate
location of the equipment sourcing the alarm relays or cross-connect
panel.

Step 3 Connect the other end of the Environmental Alarm to the Environmen-
tal Alarm connector (labeled ALARM) on the front panel of the
GE114H/GE114PH.
End of Procedure
BITS IN and BITS OUT Cables (GE114S/GE114SH)

For EMI Class B required sites, a Category 6 or 7 cable terminated with RJ-48c
required sites, a Category 5 cable terminated with RJ-48c connectors may be
used for connection to BITS IN and BITS OUT ports. See RJ-48c BITS Connec-
tor Pin Description and Assignment - GE114S/GE114SH on p. 185.
Procedure
Step 1 Route the BITS IN and BITS OUT cable(s) from the
GE114S/GE114SH to the appropriate location.
Step 2 Connect the one end of the BITS cables to the appropriate location of
the clocking device or cross-connect panel.
Step 3 Connect the BITS IN and BITS OUT cables to the appropriate con-
nectors on the front panel of the GE114S/GE114SH.
End of Procedure
Time of Day Cable (GE114S/GE114SH)

required sites, a Category 5 cable terminated with RJ-45 connectors may be
used. for connection to a TOD port. See Time of Day (TOD) Connector Pin
Assignments - GE114S/GE114SH on p. 186.
Procedure
Step 1 Route the TOD cable from the GE114S/GE114SH to the appropriate
location. Dress cables, as required.
Step 2 Connect the one end of the TOD cable to the appropriate location of
the clocking device or cross-connect panel.
Step 3 Connect the TOD cable to the TOD connector on the front panel of
the GE114S/GE114SH.
End of Procedure

Pulse Per Second Cable (GE114S/GE114SH)

A cable terminated with Mini-SMB (75 Ohm) plug connector is required for con-
nection to the PPS port.
Procedure
Step 1 Route the PPS cable from the GE114S/GE114SH to the appropriate
Step 2 Connect the one end of the PPS cable to the appropriate location of
the external device or cross-connect panel.
Step 3 Connect the PPS cable to the PPS connector on the front panel of the
GE114S/GE114SH.
End of Procedure
External (10MHz) Frequency Reference Cable

(GE114S/GE114SH)
A cable terminated with Mini-SMB (75 Ohm) plug connector is required for con-
nection to the CLK port.
Procedure
Step 1 Route the CLK cable from the GE114S/GE114SH to the appropriate
Step 2 Connect the one end of the CLK cable to the appropriate location of
the external device or cross-connect panel.
Step 3 Connect the CLK cable to the CLK connector on the front panel of the
GE114S/GE114SH.
End of Procedure
GPS Cable (GE114SH)

A cable terminated with SMA (50 Ohm) plug connector is required for connec-
tion to the GPS port.
Procedure
Step 1 Route the GPS cable from the GE114SH to the appropriate location.
Dress cables, as required.
Step 2 Connect the one end of the GPS cable to GPS antenna cable.

Step 3 Connect the other end the GPS cable to the GPS connector on the
front panel of the GE114SH.
End of Procedure

Install SFPs and Route Optical Cables

Use the following information and procedures to install SFP interfaces, and con-
nect optical cables to the Network Ports and Access Ports, as required.
Install SFP Interfaces

Each optical port of a FSP 150CC-GE11x Service Module accepts a SFP Inter-
face, depending on customer requirements. The interfaces are inserted into the
appropriate ports on the front panel of each Service Module.
ADVA Optical Networking strongly encourages the use of ADVA Optical Net-
working sourced SFPs. No support will be provided for systems that use SFPs
other than those sourced by ADVA Optical Networking. The SFP contains a
software key that is checked by the GE11x service module base unit prior to ini-
tialization. This check is performed to ensure that only ADVA Optical Network-
ing approved SFP units are used. SFP units are individually qualified by ADVA
Optical Networking to ensure the quality of the optical output and conformance
to the Multiuser Agreement (MSA).
If the SFP transceiver and rate do not match the configured application, an SFP
mismatch alarm is raised. The port is then configured to prevent traffic to pass. If
SFP cannot pass ADVA Optical Networking check criteria, but SFP transceiver
and rate do match the configured application, a “NON qualified SFP” standing
condition is raised.
Copper SFPs are supported. See FSP 150CC GE11x R6.1 Technical Descrip-
tions document for more information on SFPs. The “FSP 150 Ethernet Access
Compatibility Matrix” document contains up-to-date information on which SFPs
are certified for each product. This document may be obtained through ADVA
Technical Support or via the product support site on www.advaoptical.com.
(1) The insertion of SFP Interfaces other than those

approved by ADVA Optical Networking, even those
approved for other ADVA Optical Networking products,
will result in exceeding safety certification for the FSP
150CC.
WARNING (2) NEVER insert metal objects, such as a screwdriver or
a finger with jewelry, into open SFP Interface slots when
the FSP 150CC is powered on.
(3) To avoid eye injury from debris, always wear safety
glasses when working with canned compressed air.

PS

optical ports.

Invisible Laser Radiation

(1) Laser equipment should only be installed by personnel competent
in laser technology.
(2) SFP Interfaces, approved by ADVA Optical Networking are Class
1 laser devices, when inserted into the FSP 150CC-GE11x.
(3) Do not stare into the beam of any SFP Interface or view directly
with optical instruments.
(4) Output ports of the SFP Interfaces emit laser radiation which is
CAUTION
invisible to the naked eye. The equipment uses laser diodes as
fiber-optic transmitter sources which are inherently safe unless mis-
handled. Mishandling and misuse can result in severe eye injury.
(5) Do NOT look directly into an optical fiber connector or an un-termi-
nated receptacle with a magnifier, unless it is absolutely certain that
no laser radiation is being emitted from the receptacle or the fiber.

IEC 61340-5-1:1998).
(1) When handling SFP Interfaces DO NOT touch any connections
inside the device.
PS
(2) Keep all ports and connectors free from dust. When not in use, fit
Note both connector plugs and sockets with protective caps.
SFP Interfaces are hot swappable. The power to the FSP 150CC
PS
does not need to be switched off during the installation of an interface.

Note
Use the following procedure for installing an SFP Interface. Repeat the proce-
dure for each SFP to be installed.
Procedure
Step 1 If so equipped, remove the protective cap from the appropriate port on
the front panel of the Access Port or Network Port.
Step 2 Take the SFP Interface out of its packaging and put it on an anti-static
surface. If necessary, use canned compressed air to blow off any dust
particles.

Step 3 Orient the SFP Interface until the duplex LC, simplex SC or RJ45 con-
nector is facing you and the manufacturer’s label is toward the Access
Port or Network Port port interface’s LEDs.
Electrical Connector Label Latching Mechanism

(not visible)
LC Connectors Protective Plug

The latching mechanism may differ between SFP Interfaces supplied

by ADVA Optical Networking.
(1) SFP Interfaces can only be properly inserted one way. If the inter-
PS
face does not click when inserted, remove it, turn it over and reinsert.
Note (2) Force should not be required to insert a SFP Interface. If an
interface does not insert easily, remove and inspect it, and if it is not
damaged, reinsert.
Step 4 Holding the SFP Interface by its sides, gently slide it into the port slot
until it clicks into place, or until it cannot be inserted any further.
End of Procedure

Route Fiber Optic Cables

Refer to the following procedure when running fiber optic cables.
Follow local safety procedures regarding fiber optic cables. Never
look at the end of a fiber optic cable. Permanent eye damage or
blindness can occur. All optical connectors are shipped with
protective caps. Ensure that protective caps are firmly in place before
CAUTION
running any fiber optic cables.
Never handle exposed fiber optic cables with bare hands or touch it to
your body. A fiber fragment could enter the skin and be very difficult to
detect and remove.
CAUTION
Prevent damage to fiber optic cables. Do not bend fiber

NOTICE optic cables to a radius less than 50 mm.
To avoid damage to optical receivers, do not connect any

NOTICE fibers until instructed to do so. Always check optical
levels before connecting fiber optic cables.
Procedure
Step 1 Route all fiber optic cables from the GE11x to the appropriate loca-
tion. Do not connect the cables to the GE11x connectors at this time.
They will be connected later.
Step 2 Dress all fiber optic cables. Use local practices for protecting all
cables and connectors.
End of Procedure

Connect Power Cables and Apply Power

For GE112/GE114/GE114S: The system is powered by either an integrated AC
and/or DC Power Supply.
For GE114H/GE114SH: The system is powered by dual 24 Watts AC and/or DC
Power Supply Units (PSUs). The shelf may be equipped with two AC modules,
two DC modules, one of each or even a single PSU (operation without redun-
dancy is not recommended). The PSUs are load sharing and hot-swappable.
They are physically accessed at the front of the unit and source connections are
located on the front of each PSU module. If one PSU module fails - or its input
source fails, the remaining module continues to power the system without inter-
rupting system function. DC PSUs have an input polarity guard. If the power is
connected with the polarity reversed, the unit does not power up.
AC PSUs available for GE114H/GE114SH:
o
24W Variant: Takes 120/240 VAC input.
DC PSUs available for GE114H/GE114SH:
o 24W Variant: Takes -48 VDC input.
For GE114PH: The system is powered by dual 180 Watts or 60 Watts AC and
95 Watts AC/DC Power Supply Units (PSUs). The shelf may be equipped with
one or two AC modules (operation without redundancy is not recommended).
The PSUs are load sharing and hot-swappable. They are physically accessed at
the front of the unit and source connections are located on the front of each PSU
module. If one PSU module fails - or its input source fails, the remaining module
continues to power the system without interrupting system function.
There are three variants of AC and one variant of DC PSUs available for
GE114PH. The software will detect the PSU type inserted.
o 180W Variant: Takes 120/240 VAC input.
o 60W Variant: Takes 120/240 VAC input.
o 95W Variant: Takes 120/240 VAC input
o
95W Variant: Takes -48 VDC input
Ensure that the correct PSU is installed in the corresponding unit. The
GE114H/GE114SH use 24 Watts AC/DC PSUs, whereas the
PS
GE114PH requires 180 Watts, 60 Watts or 95 Watts AC or 95 Watts

DC PSUs. For associated part numbers, see Equipment Accessories
Note
in FSP 150CC GE11x R6.1 Technical Descriptions document.
When connecting power to a PSU, make sure that the office supply is
PS
correct according to the rating label of the GE11x. The rating label
can be found on the back of the GE11x.
Note

Use the following precautions when connecting power cables and applying
power to the GE11x.
(1) ALWAYS remove power from supply leads when connecting or

disconnecting DC power cables, and always ensure that the protec-
tive earth terminal is grounded, otherwise there is a risk of severe
electrical shock and personal injury.
(2) ALWAYS connect the accessory 3-pin power cord to a 3-pin
grounded power outlet when supplying AC power to the GE11x. If
power is supplied without the protective earth grounded, there is a
risk of severe electrical shock and personal injury.
(3) Two GE11x DC variants are available. The -48 VDC (nominal)
variant and a +24 VDC (nominal) variant. Each is designed for use
with a telecommunications DC supply. As such, this should only be
installed in a restricted access location by trained personnel.
WARNING (4) When connecting to a 240v AC supply, the unit should be con-
nected using a 3 Amp double pole branch circuit breaker.
(5) Circuit Overloading - Consideration should be made when con-
necting the equipment to the supply circuit. Consider the effect over-
loading the circuits might have on current protection and supply
wiring. Appropriate consideration of the equipment current rating
should be taken when addressing this concern.
(6) For AC variants, the power inlet connector is the disconnect
device. For DC variants, a readily accessible disconnect device
should be incorporated in the building / RT installation wiring.
Connect AC Power
The GE11x AC PSU operates with an AC source, with a voltage range of 120 /
240 VAC nominal, 50-60Hz nominal. The system operates with an AC source
with the voltage range specified in ANSI specification C84.1-1989, Voltage Rat-
ings (60 Hz) for Electric Power Systems Equipment, Range B. The equipment
shall tolerate any frequency within the range of 60 (+/-3) Hz. UK/EU Power
requirements: EN50160 defines voltage characteristics in public distribution
systems. Public low voltage is: 230 VAC +/-10% i.e., 207-253 VAC, 50Hz
-6%/+4% (47- 52 Hz).
Use the following procedure to connect AC power to each of the AC power
PSUs, as required.
Procedure
Step 1 Use an AC tester to verify the integrity of the AC outlet. Rectify any
grounding, isolation, etc., issues identified.
Step 2 Route the AC power cable(s) from the GE11x to the designated
power outlet, externally fused at 4 Amps for GE112/GE114/GE114S,
5 Amps for GE114H/GE114SH/GE114PH.

Step 3 Connect the AC power cable(s) to the GE11x power connector.

For GE114H/GE114SH/GE114PH:
Repeat Step 3 for a second source AC power supply, if applicable.
• AC variant of GE112/GE114/GE114S: Use a right-angled or a

straight connector.
PS
• AC variant PSU of GE114H/GE114SH : Use a left-angled con-
nector or a straight one.
Note
• AC variant of PSU GE114PH: Use a straight connector.
Step 4 Do Not Insert the power plug(s) into the power receptacle(s) at this
time. They will be inserted later during the procedure.
Step 5 For GE112/GE114/GE114S: skip this step. For
GE114H/GE114SH/GE114PH: Determine the next step.
Desired Activity Then

Will a -48 VDC PSU also be installed? Continue to Connect
-48 VDC Power on
p. 170.
Are no more PSUs to be installed? Continue with the next

step.
Step 6 Dress cables as required.

Step 7 Insert AC Power cable(s) into AC receptacle(s). The Status LED on
the PSU should be illuminated Green. Observe the system STA LED
after applying power: See Start-Up LED Sequence on p. 175.
End of Procedure

Connect -48 VDC Power

Use the following procedure to connect –48 VDC power to a
GE112/GE114/GE114S/GE114H/GE114SH/GE114PH -48 VDC PSU, as
required. Refer to Power Supply Connector Pin Assignments on p. 181 for con-
nector pin assignment information.
Avoid the risk of electrical shock. Follow local procedures for working
with electrical power. High voltage may be present in the following
tasks. Shut off the power from the power source or turn off the circuit
breakers before proceeding. Use properly insulated tools when
WARNING working with power connections. Do not allow any metal objects to
connect across power terminals.
Figure 86: GE112/GE114/GE114S -48 VDC PSU Connector
Position Connector Release Tab
- Gnd + at top of power connector
3 2 1
Figure 87: GE114H/GE114SH/GE114PH -48 VDC Power Supply Connector

at top of power connector Status
Power Input -48 to -60V DC
- Gnd +
- Gnd +
3 2 1

Procedure
Step 1 Verify that the office DC power supply is set up to deliver the correct
operating voltage to the GE11x (-48 or -60 VDC nominal). Verify that
the correct fuse or breaker (4 Amp rating for GE112/GE114/GE114S
or 5 Amp rating for GE114H/GE114SH/GE114PH) is installed at the
power supply source and that power is turned off. For
GE114H/GE114SH/GE114PH: Repeat Step 1 for a second -48 VDC
power supply source, if applicable.
Step 2 Using a volt meter, measure the voltages at the source power supply
terminals. Verify that no voltage is present.
Step 3 Run the DC power cable(s) from the GE11x to the designated office
battery terminals. Dress cables as required.
When performing the following step, ensure that the proper polarity of
the DC power is observed as miswiring could result in damage to the
GE11x.
The GE11x detects polarity reversal and does not power up when the
WARNING
polarity is reversed.
Step 4 Remove the cover from the source power terminal strip. Connect the
following wires to the source DC power supply terminals. Verify that

all power terminal connections are tight and that no strands of wire
are shorting terminals together. Wire size is 16 AWG for GE11x.
• North American application
• Black Battery Return wire to the + terminal
• Green/yellow Ground wire to the GND terminal
• Red -48V Office Battery wire to the - terminal
• European application (With Power Cable 1036904053)
• Blue Battery Return wire to the + terminal
• Grey -48V Office Battery wire to the - terminal
• European application (With Power Cable 1036904054)
• Black Battery Return wire to the + terminal
• Blue Office Battery wire to the - terminal
For GE114H/GE114SH/GE114PH: Repeat Step 4 for a second
source -48 VDC power supply, if applicable.
Step 5 Route the wire harness to the appropriate PSU connector. Do Not
insert the power connectors at the GE11x (see Figure 86). They will
be inserted later during the power up procedure.
For GE114H/GE114SH/GE114PH: Repeat Step 5 for a second -48
VDC power supply, if applicable.
Step 6 Reconnect the office power source (reinstall fuses, reset breakers or
turn on power supply).
Step 7 Use a volt meter to verify the power and ground at the source DC
power supply terminals. Connect the positive voltmeter lead to the -
terminal and the negative voltmeter lead to the + terminal. Ensure that

the voltage between + and - terminals measures between -36 and -72
VDC.
Step 8 Using a volt meter, measure the voltage between + and GND termi-
nals. Verify that 2 VDC or less is present. Replace the cover to the
source power terminal strip.
Step 10 Insert the -48 VDC power connector(s) (For GE114H/GE114SH: Also
insert AC Power cable into AC receptacle, if present).The Status LED
on the PSU(s) should be illuminated Green. Observe the system STA
LED after applying power: See Start-Up LED Sequence on p. 175.
End of Procedure

Connect +24 VDC Power

Use the following procedure to connect +24 VDC power to a
GE112/GE114/GE114S +24 VDC PSU, as required. Refer to Power Supply
Connector Pin Assignments on p. 181 for connector pin assignment information.
GE112/GE114/GE114S, work with +24 VDC and GE114H/GE114SH/GE114PH
don’t.
Avoid the risk of electrical shock. Follow local procedures for working
with electrical power. High voltage may be present in the following
tasks. Shut off the power from the power source or turn off the circuit
breakers before proceeding. Use properly insulated tools when
WARNING working with power connections. Do not allow any metal objects to
connect across power terminals.
Figure 88: GE112/GE114/GE114S +24 VDC PSU Connector

- Position connectors under

set screws of power connector
Gnd
+
Step 1 Verify that the source +24 VDC power supply is set up to deliver the
correct operating voltage to the GE11x (+24 VDC nominal). Verify
that the correct fuse or breaker (20 A rating) is installed at the power
supply source and that power is turned off.
Step 2 Using a volt meter, measure the voltages at the source power supply
terminals. Verify that no voltage is present.

Step 3 Run the DC power cable(s) from the GE11x to the designated battery
terminals. Dress cable(s) as required.
When performing the following step, ensure that the proper polarity of
the DC power is observed as miswiring could result in damage to the
GE11x.
The GE11x detects polarity reversal and does not power up when the
WARNING
polarity is reversed.
Step 4 Remove the cover from the source power terminal strip. Connect the
following wires to the source DC power supply terminals. Verify that
all power terminal connections are tight and that no strands of wire
are shorting terminals together.
• Black Battery Return wire to the – terminal
• Green/yellow Ground wire to the Gnd terminal
• Red +24V wire to the + terminal
• European application
• Blue Battery Return wire to the – terminal
• Grey +24V wire to the + terminal
Step 5 Route the wire harness to the GE11x. Connect the following wires to
the DC power supply terminals at the GE11x (see Figure 88). Verify
that all power terminal connections are tight and that no strands of
wire are shorting terminals together.
• Black Battery Return wire to the – terminal
• Red +24V wire to the + terminal
• European application
• Blue Battery Return wire to the – terminal
• Grey +24V wire to the + terminal
Step 6 Reconnect the power source (reinstall fuses, reset breakers or turn on
power supply).
Step 7 Use a volt meter to verify the power and ground at the GE11x power
terminals. Connect the positive voltmeter lead to the + terminal and
the negative voltmeter lead to the - terminal. Ensure that the voltage
between + and - terminals measures between +18 and +30 VDC.
Step 8 Using a volt meter, measure the voltage between + and GND termi-
nals. Verify that 2 VDC or less is present. Replace the cover to the
source power terminal strip.
Step 10 Insert the +24 VDC power connector(s). The Status LED on the
PSU(s) should be illuminated Green. Observe the system STA LED
after applying power: See Start-Up LED Sequence on p. 175.
End of Procedure

Start-Up LED Sequence

Following Power On the modules in the GE11x will take several seconds to boot
up/start up. During this time, the Status Indicators will indicate where in the boot
up and start up sequence that module is. The LED function is used for signaling
local operators within visible range the current status of shelves, cards, and
interfaces on ADVA Optical Networking devices.
A start-up condition takes place when a device initially powers up or when the
device is set to do a hard reset when triggered by the backplane reset signal.
The guidelines in this section are implementation specific as cards may support
different types of boot sequences depending upon the technology used.
Figure 89 illustrates the LED transitions for a typical device during start-up.

Figure 89: LED Flow Diagram

Power
Applied
Stage Time LED All LEDs

12 Volts N
Available? Off
Y
COLD
Hardware Ctrl
N Slot 200 ms
All Off/Red
All Board Red

N Status
Supplies Within COLD
Tolerances? LED
Power Up Reset Yellow

Delay Board Yellow
Status
(Slot #) 200ms CPLD, FPGA, CPU Status
LED
LED
Flashing Y Valid
Flashing Yellow
Processor Init Yellow

300 misc. max
WARM Cold Boot?

Status MTPS
LED Y
BOOTLDR
Flashing
Load Y Valid Load
Green
BKDI BKDI U-Boot
Status
LED
STOP
Card Perform U-Boot

Lamp Test HW Test
Monitor
Lamp test/Red
Y
2 Sec Min
Red
MTPS
N
HW Test Status STOP
Pass? LED
N
Y “reset”
Cmd
User
Break
Detected
Force
Software WARM
N /HRESET
RUN HW Init COMMs

Flashing Green/Green/All Off
Image SW Init Verified Software

Software
Software Running
Upgrade
Upgrade
Lifetime
N N
All LEDs Force Cold WARM
Provisioned? Reset?
Off
Y Y
COLD
Green
Status
LED

LED Start-Up
Use the following procedure shows the sequence of LEDs during start-up.
Please note that the following steps can complete so quickly that you may not
see a particular LED transition.
Procedure
Step 1 Power up the GE11x by applying power to the GE11x while observing
the following start-up sequence:
• Insert the power plug into the AC power receptacle(s)
• Insert the power connectors at the GE11x -48 VDC / +24 VDC
PSU(s)
Step 2 Red - Between power up of the power controller on the card and the
other power supplies being enabled and before they are all within
acceptable tolerance of nominal, the Status LED is red; all other LEDs
are off during initialization.
Step 3 Yellow - The Status LED transitions from red to yellow after the volt-
age rails have come up and while the card is configuring hardware or
performing hardware tests (i.e., configuration of FPGA, CPLD, and
CPU).
Step 4 Once the hardware devices have been configured the Status LED will
be begin to flash Yellow with a frequency of 1Hz +/- 0.5Hz.

Step 5 After the U-Boot software has loaded, a power on lamp test is exe-
cuted where all LEDs are lit for two seconds. See LED Start-Up on
p. 177.
Step 6 Next, hardware tests are performed. If there are no failures, the
sequence continues. If there is a hardware failure, the Status LED is
red and the sequence stops.
Step 7 WARM Start: If the card has been WARM started, the sequence
begins here. If this is a cold start sequence then the previous steps
are executed and a forced warm restart is performed. Once the CPU
has been initialized the Status LED will begin to flash Yellow with a
frequency of 1Hz +/- 0.5Hz.
Step 8 Now, the image is validated. If the image is bad, the sequence stops
and the Status LED will continue to flash Yellow. If the image is good,
the Status LED will begin to flash Green with a frequency of 1Hz +/-
0.5Hz.
Step 9 The status LED then reverts to normal behavior (either Green – provi-
sioned, or Flashing Red- equipment mismatch).
Step 10 If, during the boot sequence or during normal operation, a fault is
detected on the card in Hardware, Firmware, or Software, the Status
LED will be lit red indefinitely. This indicates that the card cannot
recover.
End of Procedure

Measure Optical Power
Power On Lamp Test

The GE11x performs a Power On Lamp Test. This lamp test occurs during the
module start up sequence (see LED Start-Up on p. 177).
During the test, all module indicators illuminate for two seconds and then the
indicators return to normal operation (dual color LEDs will light a mix of colors,
i.e., Red + Green will be Orange).
Measure Optical Power

Using an optical power meter calibrated for the appropriate wavelength, check
the power budgets and the transmit levels of optical Access and Network Inter-
face connections by performing the following procedure for each.
Procedure
Step 1 Take optical power measurements for:

• the Tx port
• the Rx fiber before insertion
Step 2 Compare the optical power measurements made, and add attenua-
tion if necessary (see Optical Attenuation on p. 178).
End of Procedure
Optical Attenuation
When making optical power measurements the following guidelines generally
apply:
For Access Interface connections:
• the power measured at the Rx input should be within the range of the
Access ports Rx level
• the power measured at the input to the customer equipment should be
within the range of the customer equipment’s Rx level.
For Network Interface connections:
• the Rx input should be within the range of the Network ports Rx level
In some cases it is necessary to attenuate the optical signal power to meet the
specification of the GE11x or the specifications of customer equipment.
Variable or fixed attenuators in the range of -3dB to -11dB can be placed, as
appropriate, at the:
• Rx and Tx Access Interface connectors
• Rx and Tx Network Interface connectors
Install an optical attenuator by plugging the appropriate fiber-optic cable into the
attenuator and installing the cable/attenuator combination at the appropriate
connector socket.

Clean Fiber Connections

Clean all fiber connections prior to connecting fiber optic cables.
Isopropyl alcohol can cause eye irritation. Follow the pre-
cautions given by the optical fiber cable manufacturer.
WARNING Working with compressed air can cause debris to fly into
your eyes. To avoid injury, wear safety glasses when you
work with isopropyl alcohol and compressed air.
Fiber-optic end surfaces must be smooth and clean before

PS
connection.
Note
To ensure that all fiber connectors are clean, thoroughly clean the connectors
using a lint free, non abrasive wipe or pad.
Precautions When Connecting Fiber Optic Cables

Refer to the following precautions when connecting fiber optic cables.
NEVER insert metal objects, such as a screwdriver or a finger with

jewelry, into open SFP Interface slots when the GE11x is powered on.
WARNING
Fiber-optic cables can be damaged if they are handled or

NOTICE routed improperly. Do not bend fiber optic cables to a
radius less than 50 mm.
Keep all ports and connectors free from dust. When not in
NOTICE use, fit both connector plugs and sockets with protective
caps.
When cabling SFP Interface optics, note that Rx ports are on the right
PS
(bottom) and Tx ports are on the left (top).

Note

To Power Off
Connect Fiber Cables to Access Port or Network Port

Use the following procedure to connect fiber optic cables to the Access Port or
Network Port Interfaces.
Procedure
Step 1 Remove the protective caps from both connector plugs and sockets.
Step 2 Connect the fiber cables depending upon the deployment scenario:
For direct connection to another FSP 150CC:
• the near end Tx port is connected to the far end Rx port
• the near end Rx port is connected to the far end Tx port.
For connection via a core active network:
• the Tx port is connected to the Rx port of the Switch or Router
• the Rx port is connected to the Tx port of the Switch or Router
End of Procedure
To Power Off
For maintenance or transport purposes, it may be necessary to power down the
GE11x. In which case, use the following procedure to do so.
ALWAYS remove power from the PSU to ensure that the GE11x is
electrically inert.
WARNING
To power off the GE11x, use the following procedure.
Procedure
Step 1 Turn off the -48 VDC and/or +24 VDC power supply to the PSU con-
nector(s).
Step 2 Remove the power cables from the AC outlet (for PSU 1 and/or PSU
2).

Connector Pin Assignments

Power Supply Connector Pin Assignments
Refer to the following for -48 VDC and +24 VDC PSU connector pin designa-
tions and cable wire assignments.
Figure 90: GE112/GE114/GE114S -48 VDC Power Supply Connector

- Gnd + at top of power connector
3 2 1
Figure 91: GE114H/GE114SH/GE114PH -48 VDC PSU Connector

at top of power connector Status
Power Input -48 to -60V DC
- Gnd +
- Gnd +
3 2 1
Table 9: –48 VDC PSU Cable Wire Assignments

Pin PSU European Wire North American
Connector Description
Number Connection Color Wire Color
1 + Return for battery source Blue Black

Table 9: –48 VDC PSU Cable Wire Assignments

Pin PSU European Wire North American
Connector Description
Number Connection Color Wire Color
2 Gnd Ground Yellow / Green Yellow / Green
3 — –48 VDC, 5A Battery Grey Red
Figure 92: GE112/GE114/GE114S +24 VDC Power Supply Connector
- Position connectors under

set screws of power connector
Gnd
+
Table 10: +24 VDC PSU Cable Wire Assignments

European Wire North American
PSU Connection Connector Description
Color Wire Color
+ +24 VDC, 5A Battery Grey Red
Gnd Ground Yellow / Green Yellow / Green
– Return for battery source Blue Black
LAN Connector Pin Assignments

Refer to Table 11 for the RJ-45 10/100 Base-T connector pin assignments and
refer to Table 12 for 1000 Base-T LAN port connector pin assignments.
For GE114PH: Two alternatives are also provided for power injection:

• Alternative A, where power is transmitted (super-imposed) over data trans-

mission pairs 1/2 and 3/6.
• Alternative B, where power is transmitted over spare pairs 4/5 and 7/8.
Table 11: 10/100 Base-T LAN Port (RJ-45 Connector)
MDI MDI-X 10/100 Base-T Signal Name
1 3 TX+
2 6 TX-
3 1 RX+
4 7 —
5 8 —
6 2 RX-
7 4 —
8 5 —
Table 12: 1000 Base-T LAN Port (RJ-45 Connector)

MDI MDI-X 1000 Base-T Signal Name
1 3 BI D1+
2 6 BI D1-
3 1 BI D2+
4 7 BI D3+
5 8 BI D3-
6 2 BI D2-
7 4 BI D4+
8 5 BI D4-
BI D = Bi-directional Data

Serial Console Port Connector Pin Assignments

The GE11X is a DCE device, refer to the following table for the RJ-45 (RS-232
Serial Console port) connector pin assignments, which follows the
EIA/TIA-232-F standard. The installation kit also provides an RJ-45 to DB9 con-
version adapter (pin assignments are shown in the following table).
Table 13: RJ-45 (RS-232 Serial Console Port) and DB9 Adapter Pin
Assignments
Signal Name Description RJ-45 DB9
— Not used 1 —
DSR Data Set Ready 2 6
DTR Data Terminal Ready 3 4
SG Signal Ground 4 5
RXD Receive Data 5 2
TXD Transmit Data 6 3
CTS Clear To Send 7 8
RTS Request To Send 8 7
Environmental Alarm Connector Pin Description and
Assignments - GE114H/GE114PH
The Environmental Alarm input connector (labeled ALARM) is a front mounted
RJ-45 connector. Up to 4 monitored devices can be connected to the 4 dry con-
tact alarm inputs. The dry contact alarm inputs are programmable to specify the
monitored condition, and whether the alarm shall be raised on contact close or
open. Refer to the following table for the Environmental Alarm connector pin
assignments.
Table 14: RJ-45, Environmental Alarm Input Connector
Pin Number Signal Description
1 GND Ground (Alarm 1)

2 ALM1 Alarm 1
4 ALM2 Alarm 2
6 ALM3 Alarm 3
8 ALM4 Alarm 4

RJ-48c BITS Connector Pin Description and

Assignment - GE114S/GE114SH
T1/E1 External Clock Input connector (labeled BITS IN) and T1/E1 External
Clock Output connector (labeled BITS OUT) are both front mounted RJ-48c bal-
anced 120 Ohm connectors.
Refer to the following tables for the BITS IN and BITS OUT connector pin
assignments.
Table 15: RJ-48c, BITS IN Input Connector
B1 RRING Receive Ring

B2 RTIP Receive Tip
B3 GND Ground
B4 — —
B5 — —
B6 GND Ground
B7 GND Ground
B8 GND Ground
Table 16: RJ-48c, BITS OUT Output Connector
B1 — —
B2 — —
B3 GND Ground
B4 TRING Transmit Ring
B5 TTIP Transmit Tip
B6 GND Ground
B7 GND Ground
B8 GND Ground

Time of Day (TOD) Connector Pin Assignments -

GE114S/GE114SH
The Time of Day connector (labeled TOD) is a front mounted RJ-45 connector,
with an output function. The system supports a TOD output with synchronized
phase signal sourced from the Time Clock or a Telecom Slave.
Refer to the following table for detailed pin assignments.
Table 17: TOD RJ-45 RS422 Connector and Pin Assignments
T1 — —
T2 — —
T3 PPS_IN -/PPS_OUT - Receive/Transmit 1PPS negative
T4 GND Ground
T5 GND Ground
T6 PPS_IN +/PPS_OUT + Receive/Transmit 1PPS positive
T7 TOD_RX -/TOD_TX - Receive/Transmit TOD time
message negative
T8 TOD_RX +/TOD_TX + Receive/Transmit TOD time
message positive
PPS/CLK Connector Pin Assignment -

GE114S/GE114SH
The Pulse Per Second (labeled PPS) and the CLK (labeled CLK) are both front
mounted Mini-SMB JACK (75 Ohm) connectors. The system supports a PPS
synchronous phase output sourced from a telecom slave or the Time Clock. The
system supports a CLK synchronous frequency output sourced from a telecom
salve.
Table 18: PPS/CLK SMB Connector and Pin Assignments
Center Sync Phase or 1PPS, 10Mhz signal, TTL

Frequency Signal
Shield Ground Ground

GPS Connector Pin Assignment - GE114SH

The Ground Position Satellite (labeled GPS) is a front mounted SMA JACK (50
Ohm) connector. The system supports a GPS output as the time reference to
the Time Clock.
Table 19: GPS SMA Connector and Pin Assignments
Center GPS Signal GPS Signal

Shield Ground Ground
Changing Fan Air Filter Pad - GE114PH

A dirty air filter pad negatively influences cooling efficiency. Taking air pollution
into consideration, replace dirty air filter pads at least once a year. ADVA Optical
Networking strongly recommends replacing the air filter pad every 90 days. A
set of 50 air filter replacement pads may be ordered (part number
1078904649-01). Ensure that the local air filter change schedule is entered
appropriately for the site.
Use the following procedure to change the air filter pad on the FSP
150CC-GE114 PH 180 Watts PSU.
Procedure
Step 1 Loosen the Thumbscrew on left hand-side, until the front panel of
PSU is removed from the PSU. The air filter becomes accessible.
Step 2 Remove the air filter and replace it with a new one.
Step 3 Restore the front panel of PSU back to the PSU.
Step 4 Fasten the Thumbscrew on left hand-side until the front panel is firmly
fixed.
Step 5 Dispose of the dirty air filter as designated by local practices.
End of Procedure

188
Changing Fan Air Filter Pad - GE114PH

Chapter 3
eVision Web Browser

Management Tool
Introduction
The eVision web browser management tool provides a Graphical User Interface
(GUI) for Operation, Administration and Maintenance (OAM) functions. The eVi-
sion provides comprehensive support for fault, configuration, performance and
security functions from a web browser (see Minimum System Requirements on
p. 193) on a computer connected to Data Communication Network (DCN) port
(see Figure 93).
This chapter describes eVision and the features it provides to manage the FSP
150CC equipment. The chapter provides the following information:
• logging on and off
• getting familiar with eVision
• eVision Applications descriptions

Introduction
To access eVision, the FSP 150CC must first be configured with an Internet
Protocol (IP) address and subnet mask. Details on how to do this are provided
in Provision Communications on p. 400.
eVision 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
This provides the user with the ability to:
• view the current status of the FSP 150CC system
• view the current configuration of the FSP 150CC system
• provision the FSP 150CC for operation.
See Configuration View on p. 206 for further details.
Maintenance
This provides the user with a single view from which to perform all testing and
maintenance related operations, such as:

• Etherjack Connection Performance Analysis (ECPA) Test Stream configu-

ration and test execution
• Etherjack® Diagnostics
• Cable Length Benchmarking
• Loopbacks
• Enable/Disable JDSU loopbacks response
• Protection Groups switch operation
• Sync reference switch
• Time Clock reference switch
• Ping, trace route, flush Address Routing Protocol (ARP) cache, flush Neigh-
bor Discovery Protocol (NDP) cache
• Edit alarm attributes
• Environment Alarm input configuration
• Restore to factory defaults or system defaults
• Software upgrade
• Database management
• CLI configuration file management
• Alarm/Audit/Security log transfer

• Diagnostic files management
• Software licensed feature management
See Maintenance View on p. 209 for further details.
Performance Monitoring
This provides the user with the ability to:
• Configure PM interval
• Obtain Performance Monitoring (PM) reports and chart them
• View and configure Performance Parameter threshold values
See Performance Monitoring View on p. 217 for further details.
Etherjack® Service Assurance

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 FSP 150CC equip-
ment is at both ends for round-trip reporting via Probe and Reflector, or may be
implemented with only one FSP 150CC for one-way trip reporting via Probe
only. Up to 10 layer-3 Probes and 6 Reflectors are supported and up to 16
(GE112)/32 (GE114x) 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

Introduction
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 Provi-
sioning and Operation on p. 484.
Connectivity Fault Management

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 on p. 502.
Users and Security

Users and associated security levels can be viewed, entered and modified by
the Superuser. Other users can view and modify their own user accounts. For
more information, see Configure Local Users on p. 247.
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 Version on p. 220.
Database Configuration Management
Operations available for managing configuration data are: determining database
configuration status, restore system defaults, backup database and restore
database, modify the system default database, reset to system defaults, reset to
factory defaults and change the default value file. For more information, see
Database and Configuration Files on p. 356, Restore Database on p. 368 or
Restore System Defaults on p. 372.
Software Licensable Feature Management

Feature management provides feature control where a feature can be enabled
or disabled irrespective of the presence of a license for a feature.The operations
on feature specific objects are denied when the feature is disabled.
Precision Time Protocol

The Precision Time Protocol (PTP) is only included in FSP 150CC
GE114S/GE114SH products. The GE114S/GE114SH products support the
applicable criteria defined in IEEE 1588-2008 (version 2), including the support
for E2E Transparent Clock, Telecom Slave, Boundary Clock and Master Clock.
For more information, see Provision Precision Time Protocol (PTP)
(GE114S/GE114SH) on p. 310.
Service Activation Testing

Supported in all FSP150CC GE11x products, the Service Activation Testing
(SAT) is an Ethernet service activation test methodology which is the only stan-
dard test methodology that allows for complete validation of Ethernet ser-
vice-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 on p. 522.
Minimum System Requirements

Prior to running eVision, ensure that the management system Personal Com-
puter (PC) meets the following minimum system requirements:
• 200Mhz processor
• supported Operating System (OS) versions: Microsoft Windows XP/Vista/7
• A browser, such as Internet Explorer 5.0 or greater (IE 8.0 recommended)
or Firefox 2.0 or greater (Firefox 3.6 recommended). Other browsers may
suffice, but no specific browser is certified by ADVA Optical Networking.
• 128 Mb of Random Access Memory (RAM)
• Adobe Acrobat Reader 5.0 or greater (6.0 is included)
• Recommended display: 1024 x 768 with 16+ color bits.
If using Internet Explorer 8, in order to view certain eVision elements

correctly (namely data provided in Maintenance View - e.g., Restore
factory defaults, Restore system defaults, Restore database, New
PS
System Defaults File), enable Compatibility View in IE by selecting

Note Tools, Compatibility View Settings and adding the FSP 150CC IP
address to the list of websites data field.

Logging On and Off
Logging On and Off

Logging On
Use the following procedure to log on to the FSP 150CC eVision web browser
management tool.
This procedure assumes that HTTP and HTTPS access is enabled (factory
defaults).
Procedure
Step 1 Ensure that a DCN connection to the FSP 150CC has been estab-
lished, or the PC is connected to the DCN port, as required.
Step 2 Open up the appropriate Internet Browser and enter the following
address:
http://xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the DCN that the FSP
150CC is connected to. This will be the IP address that has been
assigned to the DCN port (eth0) during initial IP configuration, or if
none has been set, the default address of 192.168.0.2.
eVision opens and the Login Screen is displayed, as shown below:
Figure 94: System Login Screen

Step 3 Enter a valid User ID and Password (default is root and ChgMeNOW,
respectively). See Provision Secure Access on p. 242 for additional
login information.
Step 4 Select Login.
The security banner displays, as shown below.
Figure 95: Login Continue Screen

A login account will be locked for a period of 5 minutes after 3

PS
unsuccessful login attempts.

Note
Step 5 Select Continue.

eVision displays, as shown below.

Logging On and Off
Figure 96: Successful Login Screen
Step 6 Resize the screen for viewing, as desired.
End of Procedure
Logging Off
To log out of the FSP 150CC eVision web browser management tool:
Procedure
Step 1 Select File, Exit from the Menu Bar.

Step 2 Close the Internet browser.
End of Procedure

User Session Timeout

Each user is provisioned with a user inactivity timeout of 0 minutes (to disable
timeout) to 99 minutes. Default is 15 minutes. Only a Superuser (see Table 39
User Authorization Privilege Levels on p. 605) may edit a user GUI login timeout
value. When a user session is inactive for the amount of time provisioned in the
GUI timeout, the user session is automatically logged off to ensure system
security. Once the user timeout has occurred and the user attempts to operate
or view the eVision GUI, an Authentication Failed screen is displayed.
Figure 97: Authentication Failure Screen

When this occurs, simply select here from the Authentication Failed screen to
go to the FSP 150CC login screen, and continue with the logon sequence (see
Step 3 of Logging On on p. 194).
Getting Familiar with eVision

The eVision web browser management tool provides a web based Graphical
User Interface (GUI) for Operation, Administration and Maintenance (OAM)
functions. The eVision Web Browser Management Tool workspace is arranged
to allow you to focus on the task you wish to perform while continually displaying
alarm information. The Menu Bar, Tool Bar and Selection Tree provide easy
access to the desired workflow, e.g., provisioning an entity or performing main-
tenance functions.

The Details Pane provides a different set of viewing and editing options depend-
ing 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 eVision. The FSP
150CC system view (located in the Details Pane) provides a physical represen-
tation of the FSP 150CC, its current provisioning configuration and alarm status.
Figure 98: eVision Web Browser Management Tool Components
Menu Bar Tool Bar

Title Bar
System
Name
Selection
Tree Pane
View Tabs
Details
Pane
User Name Alarms Pane
Alarm details are displayed in the Alarms Pane. Refer to Figure 98 for an exam-
ple of a system entity selected in Configuration view and each component of the
web browser window.
About the Workspace

The eVision workspace consists of the following components.
• Title Bar, on Page 3-199.
• Menu Bar, on Page 3-199.
• Tool Bar, on Page 3-200.
• Selection Tree Pane, on Page 3-201.

• Details Pane, on Page 3-202.

• Alarms Pane, on Page 3-204.
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 eVision. 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.
The menus available on the Menu Bar are:
• File, which provides the following options:
o
Logout
• Application, which provides the following options:
o Configuration
o Maintenance
o Performance Monitoring
o ESA
o CFM
o PTP (GE114S/GE114SH only)
o SAT
The selections available on the Application pull-down menu may also

PS
be selected from the Tool Bar. See Tool Bar on p. 200.

Note

Tool Bar
The Tool Bar contains a set of tool buttons that can be selected for quick access
to eVision applications. The tool buttons available are:
Configuration, which accesses the Configuration
application. It allows you to perform provisioning functions,
such as editing system, equipment, facilities or users.
Various views are provided when Configuration is
selected, depending on what entity is selected in the
Selection Tree. When entering a right click on a folder or
entity from the Selection Tree, provisioning options
become available in menu form. Options available to the
user are dependent upon the user access permission
level.
Maintenance, which accesses the Maintenance
application. It allows you to perform maintenance
functions, such as loopbacks, diagnostics, software
upgrade, database backup and restore. When entering a
right click on a folder or entity from the Selection Tree,
maintenance options become available in menu form.
Various views are provided, depending upon what folder
or entity is selected in the Selection Tree. Options
available to the user are dependent upon the user access
permission level.
Performance Monitoring, which accesses the
Performance Monitoring application. It allows you to
retrieve performance monitoring counts in columnar or
chart format. Performance monitoring thresholds can be
edited or displayed, and registers can be initialized
(depending on the user access permission level).
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.
Connectivity Fault Management (CFM) provides the ability
to detect, verify, isolate and report connectivity faults on a
service instance.
Precision Time Protocol (PTP) provides the provisioning

and management for transparent clock, telecom slave,
boundary clock and master clock which are used as clock
synchronization precision standard. This feature is only
applicable in GE114S/GE114SH products.
Service Activation Testing (SAT) provides the standard

Ethernet service test methodology that allows for complete
validation of Ethernet service-level-agreements (SLAs) by
two sub-tests: service configuration test and service
performance test.

The applications available on the Tool Bar, may also be selected from
PS
the Application pull-down menu on the Menu Bar. See Menu Bar on
p. 199.
Note
Selection Tree
The Selection Tree (located at the left of the screen) enables the user to select
an entity in order to:
• display a status pane related to that entity (shown in the Details Pane to the
right)
• select menu options related to that entity
The Selection Tree provides a hierarchical tree of the entities that make up an
FSP 150CC 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 FSP 150CC 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 99 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 Con-
figuration 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.

Figure 99: Selection Tree with Menu Selected
Details Pane
When an item is selected from the Selection Tree with the left mouse button
(see Selection Tree on p. 201), 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 100 for an example of tab selections in the
Details Pane.
Figure 100: Tab Selections and Scroll Bars in the Details Pane
Tab
Scroll
Bars
Window
Resizing
Bars

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 100).
Right clicking on an entity in the Selection Tree Pane opens a window of avail-
able edits for that entity selecting one of these yields an edit view in the Details
Pane. See Figure 101 for an example of an Edit Access Port pane. Note that all
valid provisioning options are displayed in white and options that are not provi-
sionable are grayed out (Media Type).
Figure 101: Edit Access Port Pane

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 FSP 150CC and to input and/or select
data that is required for the desired operation.
Operations and Provisioning Field Types

The field types that may appear on a Details Pane are:
• Display only fields, which are provided to display status information. These
fields are grey and cannot be selected or changed.

• Provisionable fields, which have a white background, are used to indicate:

o a field that can be edited by direct data input
o a selectable drop down menu which provides context sensitive provi-
sioning options
o a check box (or toggle button)
o a right-click menu of options (configuration files only)
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:
• OK, which accepts the information in a status pane and closes the pane.
• Cancel, which cancels any changes that have been made to the information
in the status pane and closes the pane.
• Refresh, which reads and displays the latest values of the fields in the sta-
tus pane.
• Apply, which applies any changes made to the information in the status
pane, without closing the pane.
• Next>, which opens the next page (screen) of data.
• <Back, which opens the previous page (screen) of data.
Alarms Pane
The Alarms Pane provides quick visibility and access to current alarms.
All alarms are color coded by severity:
• red; Critical
• orange; Major
• yellow; Minor
Each alarm is listed as a separate line item, with the following details:
• Interface type
• Notification Code
• Description
• 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 eVision Workspace:
Tab Move through Workspace areas. This key enables the
user to move through the Menu Bar, the Tool Bar, the
Selection Tree Pane and the Details Pane.
In the Menu Bar:
Return Select. This key enables the user to display a pull down
menu and select a menu option.
Right arrow Move. These keys enable the user to move through the
Left arrow options on the Menu Bar to highlight the one required.
Up arrow Move. These keys enable the user to move up and
Down arrow down (scroll) through menu options on a pull down
menu to highlight the one required.
In the Selection Tree Pane:
Return Select. This key enables the user to select a highlighted
item or menu option and open the appropriate pane in
the Details Pane.
Up arrow Move. These keys enable the user to move up and
Down arrow down (scroll) through items and menu options to
Tab highlight the one required.
Right arrow Open. This key enables the user to view nested items. If
nested items are available it is indicated by a plus sign
(+) to the left of that item.
Left arrow Close. This key enables the user to close a nest of
items. A minus sign (-) to the left of an item indicates
that the item’s nested items are open.
In the Details Pane:
Return Select. This key enables the user to select a highlighted
field for information input or a highlighted command
button.
Right arrow Move through status pane tabs. This key enables the
Left arrow user to navigate through tabs at the top of the Details
Pane.
Tab Move through editable fields. This key enables the user
to move 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
Down Arrow enables the user to move up or down through the items
of a drop down list.
eVision Applications
The eVision web browser management tool provides the user with the following
major applications:

Configuration View
• Configuration
• Maintenance
• Etherjack Service Assurance
• Connectivity Fault Management
• Precision Time Protocol (GE114S/GE114SH)
• Service Activation Testing
Each of the Applications can be selected from the Menu Bar (see Menu Bar on
p. 199) or the Tool Bar (see Tool Bar on p. 200). The Title Bar displays the latest
application that has been selected (see Title Bar on p. 199).
Configuration View
Configuration view allows you to perform provisioning functions, and view provi-
sioning 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 avail-
able are dependent upon the user access permission level and the current entity
status.
For procedures regarding provisioning of specific entities, refer to Chapter 4,
Operations Provisioning on p. 219.
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 selec-
tion 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), Banner or NTP (Network Time Protocol). 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.
Network Element (NE)

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.
By expanding the NE-1 entity under the System entity, selecting the NTE11x
entity and then selecting the Resources tab of the NTE11x entity, all allocated
and available system traffic resources are displayed (see Figure 102).
Network Port, Access Port, DCN and PSU provisioning may be performed within
the NE-1 hierarchy in the selection tree.

See Figure 103 for an example of an Edit Network Port Configuration view.
Figure 102: NTE11x Resources Tab

Figure 103: Edit Network Port Configuration View

Configuration View
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 dou-
ble-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, Pri-
ority 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.
Synchronization (GE114S/GE114SH)
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 edit-
ing, adding/editing/deleting sync reference. Expanding BITS-1 entity and select-
ing 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.
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.

The DCN entity is accessed by expanding the Communications entity, manage-

ment tunnels are accessed by expanding the Management Tunnels and NE-1
entities, and IPv6 over IPv4 Tunnels are accessed by expanding the IPv6 over
IPv4 Tunnels and NE-1 entities. These entities are provisioned by expanding
the Communications entity, entering a right click on the desired entity in the
selection tree and selecting the applicable menu option.
SNMP
Simple Network Management Protocol (SNMP) Communities, Target
Addresses, Target Parameters, USM User entries and SNMP Dying Gasp are
viewed by selecting the SNMP entity and selecting the associated tab in the
Details Pane. These entities are provisioned by entering a right click on SNMP
in the selection tree and selecting the applicable menu option.
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 diagnos-

tics, 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 soft-
ware 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 dis-
played in the Alarms Pane at the bottom of the screen, providing constant visi-
bility and access to current alarms.
For more information on Maintenance operations, refer to Chapter 4, Operations
Provisioning on p. 219 and Chapter 6, Etherjack Test Procedures and Perfor-
mance Monitoring on p. 459.
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.

Maintenance View
Network Element (NE-1)

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:
• NTE11x
o
NTE11x - 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 NTE11x.
o
Network ports - view operations status, diagnostic results and cable
benchmarks. Entering a right click provides menu options for perform-
ing 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 perform-
ing 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
NTE11x entity, the protection group configuration and current status is dis-
played. If a protection group is configured, entering a right click on the entity
allows protection switch operation and release functions. The operations avail-
able are:
• Manual From Working
• Forced From Working
• Manual From Protect
• Forced From Protect
• Lockout From Protect
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:
• Forced
• Manual
• Ring Port 0
• 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.

By expanding the Synchronization, NE-1 and NTE114S/NTE114SH entities and
selecting SYNC/TIME CLOCK entity, the configuration and status are displayed
in separate tabs for the corresponding entity; Entering a right click on either
entity allows Reference Switch operations functions. The operations available
are:
• Forced Switch
• Manual Switch
• Lock Out
• Clear Wait To Restore
• Clear Lock Out
• 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 com-
mand, 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.
Environmental Alarms (GE114H/GE114PH)

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 avail-
able are:
• 10MHz (CLK) Port
• 3G USB Modem
• Access Port
• BITS In Port
• BITS Out Port
• CFM MEP
• CFM QOS Shaper
• DCN Port
• ERP Group
• GPS Port
• LAG

Maintenance View
• NTE11x Card
• NTE11x Shelf
• Network Port
• Pulse Per Second (PPS) Port
• PSE Group
• PSE Port
• Power Supply
• SOOC
• Synchronization
• System
• Telecom Slave
• Time Of Day (TOD) Port
Administration
Expanding the Administration entity reveals the Software, Database and Config-
uration Files entities. The following maintenance functions are available:
• Administration - Right clicking on the Administration entity allows selection
of Restore System Defaults or Restore Factory Defaults. See Restore Sys-
tem Defaults on p. 372 and Restore Factory Defaults on p. 374 for explana-
tions of these operations and the difference between them.
• Upgrade - Selecting the Upgrade entity displays the current Active and
Standby software versions along with the File Services mode and status
and the Validation Timer status. Entering a right click on the Upgrade entity
allows selection of Transfer, Install, Activate and Validate options.
• Database - Selecting the Database entity displays the current Active and
Standby database versions along with the File Services mode and status.
Entering a right click on the Database entity allows selection of database
backup and restore functions: Backup Database, Copy to Remote, Copy
from Remote, Restore Database and Activate Database.
• Default Database - Entering a right click on the Default Database entity
allows selection of the Save (create a new default database), Copy to
Remote, Copy from Remote, and New (revert the default database back to
factory defaults).
• Default Settings - Selecting the Default Settings entity allows the copying of
a remote default value file to the FSP 150CC via Web, FTP, SCP or SFTP.
• Configuration Files - Selecting the Configuration Files entity displays the
current list and status of the configuration files resident on the unit. Entering
a right click on the Configuration File entity allows the user to Create a new
configuration file, or Copy from Remote. Entering a right click on a configu-
ration file in the table in the details pane yields a list of configuration file
options including: Save, Edit Description, Copy to Remote, Restart with File
and Remove.
• Last Reset Cause - Selecting the Last Reset Cause entity displays the Last
Reset Type and Last Reset Cause information along with identifiers for up

to three debug files if any exist. Entering a right click on the Last Reset
Cause entity allows the user to Copy to Remote the debug file(s).
• Transfer Log - Entering a right click on the Transfer Log entity allows the
user to select the desired log (Alarm, Audit or Security) to transfer.
• Diagnostic Files - Selecting the Diagnostic Files entity displays the status
and Mode of diagnostic files
Viewing Entities in Maintenance View

When selecting an entity in Maintenance View, Alarm Attributes views are avail-
able by selecting the associated entity in the view area under the Alarm Attri-
butes heading. Selecting the entity displays the current Notification Code (NC)
assigned to each Alarm Attribute/Condition Type (see Figure 104).
Figure 104: Alarm Attributes View of a Network Port

A Conditions List is also present for the NE-1 entity (see Figure 105).

Maintenance View
Figure 105: Conditions List View of the NE-1 Entity
Editing Alarm Attributes
An Edit Alarm Attributes pane is accessed in Maintenance view by entering a
right click on an entity under Alarms Attributes and selecting Edit Alarm Attri-
butes (see Figure 106). Notification Codes can be edited for a given Condition
Type by selecting the desired Notification Code in the drop down menu, select-
ing the desired Notification Code, then selecting Apply or OK.
Notification Codes available for selection are:
• Critical (CR)
• Major (MJ)
• Minor (MN)
• Not Alarmed (NA)
• Not Reported (NR)

Figure 106: Edit Alarm Attributes Pane

Loopbacks
Entering a right click on a Network Port or Access Port under the NTE11x 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 107 for an example of a loopback view. For loopback procedures,
see Chapter 6, Etherjack Test Procedures and Performance Monitoring on
p. 459.
When using eVision, to remove a loopback, click on the drop-down list for Loop-
back Configuration and select “None”, then click on “OK”.

Maintenance View
Figure 107: Loopback View
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 iso-
late faults on:
• the Ethernet port
• the connecting cable
• the far-end equipment
This feature is accessed by right clicking on a copper Access Port under the
NTE11x entity and selecting “Diagnostic Test”.
See Figure 108 for an example of an Etherjack® Diagnostic Test Result view.
For Etherjack® diagnostic procedures, see Chapter 6,Etherjack Test Proce-
dures and Performance Monitoring on p. 459.

Figure 108: Etherjack® Diagnostic Test Results View

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 on p. 466).
Performance Monitoring View

See Etherjack Test Procedures and Performance Monitoring on p. 459.
ESA and CFM

See ESA Provisioning and Operation on p. 484 and CFM Provisioning and
Operation on p. 502.
Precision Time Protocol

See Provision Precision Time Protocol (PTP) (GE114S/GE114SH) on p. 310.
Service Activation Test

see Service Activation Testing on p. 522.

218
Service Activation Test

Chapter 4
Operations Provisioning
Introduction
This chapter contains system provisioning details for the FSP 150CC-GE11x
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.
Provisioning the GE11x

Once the chassis has been installed, cabled and powered (see Physical Instal-
lation on p. 123), it requires provisioning and testing prior to carrying customer
traffic. The procedures to accomplish this are listed below in the suggested
order that they be performed. The following sections can also be used for incor-
porating provisioning changes to existing systems.
Recommended Sequence of Steps for Initial Turn Up

of a GE11x
The following sections in this chapter provide supporting information and proce-
dures for provisioning the GE11x:
• Serial Connection on p. 402
• Set Up the FSP 150CC DCN (eth0) Port Using the Serial Port on p. 402 or
Set Up the 3G Modem Using the Serial Port on p. 408 (if no DCN)
• Browser-based IP Connection on p. 411
• Configure 3G Modem Using eVision on p. 444
• Upgrade Software Version on p. 220
• Provision System Options on p. 228

Upgrade Software Version
• Provision NE-1 Common Units on p. 239

• Provision Secure Access on p. 242
• Provision SNMP Access on p. 252
• Enable Software Licensing on p. 252
• Configure Flexible Port (Ethernet Port II) on p. 254
• Provision Access Port Services on p. 255
• Provision Network Ports on p. 285
o Provision Network Ports without LAG or Protection Group on p. 285
o Provision Network Ports in a Protection Group on p. 289
o Provision Ports in a LAG Group on p. 292
o Provision Ports in a Split Horizon Group (SHG) on p. 297
o Provision Network Ports in an Ethernet Ring Protection Group on p. 299
• Provision Management Tunnel(s) on p. 309
• Provision Precision Time Protocol (PTP) (GE114S/GE114SH) on p. 310
• Provision Synchronous Ethernet (Sync-E) (GE114S/GE114SH) on p. 337
• Provision Link Layer Discovery Protocol (LLDP) on p. 351
• Provision Environmental Alarms (GE114H/GE114PH) on p. 355
• Provision Performance Monitoring on p. 356
• Clear all alarms (see Recommended Steps for Trouble Clearing on p. 535)
• Database and Configuration Files on p. 356
• Test the FSP 150CC on p. 397:
o
Loopbacks
o
o
Cable Length Benchmarks
o
Etherjack Test Procedures and Performance Monitoring
o
ESA Provisioning and Operation
o
CFM Provisioning and Operation
o

Upgrading or changing the system software is a multi-step process:
• First, the new software is transferred from an external repository to a tempo-
rary location on the NE. The NE supports transfer via HTTP (Web), HTTPS
(Web), FTP, SFTP and SCP protocols.
• Second, the new system software is installed, that is transferred to the
standby side of the NE.
• Third, the new software is activated, that is switched from standby to active.
The FSP 150CC-GE11x supports immediate or scheduled activation and
can use a validation timer, which allows the NE to revert to the previous

Chapter 4 Operations Provisioning
software version if problems are encountered during the software upgrade

process.
o If scheduled activation is chosen, it is possible to cancel the activation
any time before the activation occurs.
o If validation timing is set, the user must accept the new load by the time
set, or the NE automatically reverts to the previous load.
Due to changed design, FSP 150CC-GE11x 6.1 only

allows total buffer space 32102K. It is smaller than that of
5.2.
Before upgrade a FSP 150CC-GE11x software from
NOTICE version 5.2 to 6.1, make sure the total buffer space for
traffic queues is SMALLER than 32102K.
Otherwise the upgrade can fail and connection to the NE
can be lost.
It is recommended to perform a refresh of the browser after every SW

PS
upgrade. Any resource that is cached by the browser may have to be

refreshed if that resource is different from one release to another.
Note
Activation causes the NE to reset, which temporarily interrupts traffic and can-
cels all active user sessions.
. During the software upgrade process, it is desirable to know the

status of the upgrade. The GE11x 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
PS
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
Note window. See Table 20.
Also, eVision does not show the settings for Scheduled Activation or
Validation Timer once these settings are made. However, the data is
included 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.
2012-01-16 00:00:00:root:EVT:2012-01-17 12:10:Software

Activate timer set
2012-01-16 00:00:00:root:EVT:2012-01-17 13:10:Software
Validate timer set

Table 20: Software Download Condition Types
Condition Type Description
SWDL - File Transfer In Progress Software is being copied from a

remote source to temporary
memory
SWDL - Installation In Progress Software is being written from
temporary memory to Standby
SWDL - Activation In Progress Software is being activated or is
scheduled for future activation
SWDL - Validation In Progress Software has been activated
and the validation timer was set
and is running
The following procedure includes steps for performing the software upgrade
process using the eVision tool. It is also possible to perform this process using
CLI. See the FSP 150CC-GE11x 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
FSP 150CC DCN (eth0) Port Using the Serial Port, on Page 5-402.)
Procedure
Step 1 Click on the maintenance icon, or select “maintenance” from the

application drop-down list.
Step 2 Determine the next step.

Perform Software Upgrade? Continue with the next
step.
Cancel scheduled activation? Go to Step 16.
Accept or reject upgrade during validation period? Go to Step 14.
Step 3 Expand “System”, “Administration”, right click on “Upgrade” and

select “Transfer”.
The default display is the Web file transfer view, shown below:

Figure 109: Transfer Upgrade - Web View

Use Web Browser (HTTP) to transfer software? Continue with the next
step.
Use FTP, SFTP or SCP to transfer software? Go to Step 7
Step 5 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 111 dis-
plays.
Step 6 Go to Step 9.
Step 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 following figure. (The figure shows the SCP view, the
FTP and SFTP file transfer view is identical.)

Figure 110: Transfer Upgrade - SCP View
Step 8 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 IP address of the FTP, SFTP or
PS
SCP server, has a valid user ID and password and knows the path
and file name of the software file to transfer.
Note
The file transfer will begin, and a screen similar to the following dis-
plays:
Figure 111: File Transfer Progress Screen
Step 9 When the “Status” changes from “In progress” to “Success”, right click
on “Upgrade” in the selection tree pane and select “Install”. The fol-
lowing screen displays:

Figure 112: Software Install Query
Step 10 Click OK, and the screen shows a progress bar similar to Figure 111.
When the install completes (when the “Status” changes from “In prog-
ress” 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:
Figure 113: Software Activate
Step 11 Select the activation mode (Activate Now or Schedule Activation).

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

Activation can be done immediately (Activate Now) or scheduled for

some date/time in the future (Schedule Activation). Either way, setting
the validation timer causes an automatic switch-back to the previous
PS
load if the timer should expire. The validation timer should be set for a
long enough period to allow reconnection to the NE and verification
Note
that it is functioning properly. Once this “sanity test” is done, the user
accepts or cancels the upgrade (see Step 15).
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
CAUTION
software and database without user intervention.
After selecting and setting the desired activation and validation set-
tings, select OK.
Step 12 When activation occurs (now or when scheduled) the NE resets, and
the eVision 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,
PS
reconnection should be possible. If the validation timer was not used,

Note contact technical support.

Accept or reject upgrade during validation period? Go to Step 14.
Cancel scheduled activation? Go to Step 16.
Validation timer not set? End of Procedure.
Step 14 Expand “Administration”, right click on “Upgrade” and select “Vali-

date”.
The display is the Validate Upgrade view, shown in the following fig-
ure:

Figure 114: Validate Upgrade View
Step 15 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.
End of Procedure
Step 16 Click on “Upgrade” in the selection tree pane, then select “Activate”.
An Activate Upgrade screen displays, as shown in the following fig-
ure.
Figure 115: Software Activate
Step 17 Select the “Cancel Previous Scheduled Activation” radio button and
Click OK.
End of Procedure

Provision System Options

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 FSP 150CC
DCN (eth0) Port Using the Serial Port on p. 402) and is logged on using eVision.
Procedure
Step 1 Right click on “System” in the selection tree pane and select Edit Sys-
tem and the following screen displays:
Figure 116: Edit System
Step 2 The user can change the system level CLI prompt prefix, set Provi- FSP 150CC-GE11x R6.1 80000026494 Issue: A, © 2013 ADVA Optical Networking SE - Confidential
sioning 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 and SNMP Engine ID. For information on these
system options see System Configuration on p. 619.

The System identity information that is not available for editing on this
screen (Name, Description, Location, Contact), is the same identity
PS
information that displays in the NE-1 view and is editable on the NE-1
Note “Edit Configuration” display.
Step 3 Check that the information entered in Step 2 is what is desired and
click on OK. The display will change to reflect the entered data.
End of Procedure
Configure Logs
Procedure
Step 1 Right click on “System” in the selection tree pane and select Edit
Security Log and the following screen displays:
Figure 117: Edit Security Log View
Step 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.
Alarm Log and the following screen displays:

Figure 118: Edit Alarm Log View
Step 4 For Syslog, select “Enabled” to include Alarm Log messages in the
Syslog or “Disabled” to not include Alarm Log messages in the Sys-
log; 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.
Audit Log and the following screen displays:
Figure 119: Edit Audit Log View
Step 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.
log and the following screen displays:

Figure 120: Edit Syslog View
Step 8 Select the desired Log Server Method - User Defined, or DHCP.
Step 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.
End of Procedure
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 individu-
ally enabled or disabled.
Enabling ACL filtering will “permit” the corresponding management traffic. Dis-
abling 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).

Procedure
Step 1 Right click on “System” in the selection tree pane and select Edit ACL
and the following screen displays:
Figure 121: Edit ACL
Step 2 The Access Control List contains 10 entries. Each entry consists of IP
version and corresponding IP data options; an IPv4 Address and net-
work 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.
Step 3 Click on OK. The display will change to reflect the entered data.
End of Procedure

Configure LLDP
Procedure
LLDP and the following screen displays:
Figure 122: Edit LLDP

Step 2 Enter the following data to configure system LLDP options (see
Table 56 on p. 713 for options and rules details):
Transmission Interval - 5 - 3600 seconds, default as 30
Hold Time Multiplier - 2 - 10, default as 4
Re-initialization Delay - 1 - 10 seconds, default as 2
Notification Interval - 5 - 3600 seconds, default as 30
Maximum Tx Credit - 1 - 100, default as 5
Message Fast Tx - 1 - 3600 seconds, default as 1
Tx Fast Init - 1 - 8, default as 4

Maximum Neighbors Action - automatically set to “Discard NEW”

Click on OK to save the settings.
End of Procedure
Edit the Security Banner

Procedure
Step 1 Right click on “System” in the selection tree pane and select Edit Ban-
ner and the following screen displays:
Figure 123: Edit Banner
Step 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. Unautho-

rized access or use may lead to prosecution.”
Edit the Banner, then click on OK and the screen will update to dis-
play the edited banner message.
End of Procedure
Edit System Time of Day

The following procedure provides instructions for editing the System Time of
Day using Local, NTP or PTP configuration. It assumes that the user has config-
ured the NE with an IP address and connected the NE to a DCN or LAN (see
Set Up the FSP 150CC DCN (eth0) Port Using the Serial Port on p. 402) and is
logged on using eVision.
Procedure
tem Time of Day.
The Edit System Time Of Day screen displays
Figure 124: Edit System Time Of Day
Current Status Then

Edit System Time Of Day via local entry? Continue with the next
step.
Edit System Time Of Day via NTP? Go to Step 7.
Edit System Time Of Day via PTP Clock? Go to Step 9

Step 3 For System Time Of Day, select Local.

Local Time Of Day entry fields appear
Step 4 Select the drop down calendar for the Date and select the appropriate
year, month and day.
Three years are displayed at a time. To progress through the years

PS
beyond the displayed years, continue to click on the right most years
until the desired year is displayed. Then select the desired year. Then
select the desired month from the drop down list. Then select the
Note
desired date.
Figure 125: Edit System Time Of Day - Local Method
Step 5 Enter the appropriate time in (hh:mm:ss) and select OK.
Step 6 Select the System Time Of Day tab to view the local entry.
End of Procedure
Step 7 For System Time Of Day, select NTP.

NTP entry fields appear

Figure 126: Edit System Time Of Day - NTP Method
Step 8 Select/enter the desired NTP options.

The Polling Interval can be set to 16, 32, 64, 128, 256, 512 or 1024
seconds. The default is 16 seconds.
Select the desired NTP Server Method - User Defined or DHCP
Select the IP version and enter the corresponding IP address for Pri-
mary Server and, if applicable, the Backup Server if NTP Server
Method is User Defined
If both a Primary and Backup Server are configured, either one can
be made Active by selecting the desired Active server.
Select OK.
The display updates to show the edited information
End of Procedure
Step 9 For System Time Of Day, select PTP.

PTP entry fields appear

Figure 127: Edit System Time Of Day - PTP Method
Step 10 Select the desired Source TOD Clock.

Select OK.
The display updates to show the edited information
End of Procedure

Provision NE-1 Common Units

Configure NE-1
Procedure
Step 1 Expand the System entity, right click on “NE-1” in the selection tree
pane and select Edit Configuration. The following screen displays:
Figure 128: Edit NE-1

Step 2 The Administrative State can be changed between IS (default value)

and Management. (See Entity State Descriptions on p. 599).
NE Identity information can also be changed or entered; Name, Loca-
tion, Contact, CLI Prefix and MEF BWP.
After editing the NE information, click on OK. The display will update
to show the edited information.
The NE-1 identity information that is available for editing on this
screen except for CLI Prefix and MEF BWP, is the same identity
PS
information that displays in the System view and is editable on the

Note “Edit System” display.

Provision NE-1 Common Units
End of Procedure
Configure NTE11x
Procedure
Step 1 If a “+” sign appears next to NE-1 in the selection tree pane, click on it
to expand the NE view, then click on the “+” sign next to NTE11x to
expand it.
Right click on “NTE11x” in the selection tree pane and select Edit
Configuration and the following screen displays:
Figure 129: Edit NTE11x


and Management. (See Entity State Descriptions on p. 599)
An alias can be entered to permit easy identification of this particular
NTE11x.
SNMP Dying Gasp can be Enabled. Default is Disabled.
After editing the NTE11x information, click on OK. The display will
update to show the edited information.
End of Procedure
Configure PSUs - GE114H/GE114SH/GE114PH

The GE114H/GE114SH can be powered with 24W PSU(s) and either
slot may be populated with AC, or -48 PSUs.
For GE114PH: only 180W (or 60 Watts) AC power supplies can be
used.
If 24W PSU(s) are installed in a GE114PH, the system will prevent it
from initializing and no alarm is raised.

PS
If both a 180W (or 60W) and 24W PSU are installed in the same
Note system, the 24W PSU is disabled automatically.
To verify whether a particular PSU is a 24W or 180W (or 60 Watts)
unit, the part number is printed on the PSU label and is retrievable via
all user interfaces. Part numbers and descriptions are found in
Equipment Part Numbers in FSP 150CC GE11x R6.1 Technical
Descriptions document.
Procedure
Step 1 If a “+” sign appears next to NE-1 in the selection tree pane, click on it
to expand the NE view. Right click on “PSU-1” in the selection tree
pane and select Edit Configuration and the Edit PSU screen displays.
See Figure 130 Edit PSU.
and Management. (See Entity State Descriptions on p. 599.)
An alias can be entered to permit easy identification of the PSU.
After editing the PSU information, click on OK. The display updates.
Step 3 Repeat Step 1 and Step 2 for PSU-2.
End of Procedure

Provision Secure Access
Figure 130: Edit PSU
Secure Access involves several different aspects:
• The FSP 150CC accommodates various methods of access to the system
including serial port, telnet, SSH, HTTP, HTTPS, FTP, SFTP and SCP.
These are viewable and editable from the System and Edit System view
respectively (see Configure System on p. 228).
• Access via SSH and SSL based protocols, uses certificates and keys that
are user configurable. (see Configure Security Keys on p. 243).
• The local user access security policy can be configured for low, medium or
high security levels. (see Configure Security Policy on p. 246).
• Access can be restricted by using the Access Control List (ACL) where only
designated IP addresses or subnetworks are permitted to access the sys-
tem (see Configure ACL on p. 231).
• Access to the system can be limited by use of locally defined users includ-
ing user ID, password and access level (superuser, provisioning, mainte-
nance or monitoring). See Configure Local Users on p. 247.
• Access to the system can be restricted by using remote authentication with
an externally defined and controlled user set. See Configure Remote
Authentication on p. 251.

Configure Security Keys

DCN (eth0) Port Using the Serial Port on p. 402) and is logged on as a supe-
ruser using eVision.
PS
Changing the security keys may interrupt any current secure sessions
that have used the existing keys for authentication.
Note
From the Configuration view with the Administration tree expanded:
Procedure
Step 1 Left click on “Key Generation” in the selection tree pane and the fol-
lowing screen displays to show the current SSL Certificate and SSH
Key information:
Figure 131: Display SSL Certificate and SSH Key

Step 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 133):

Figure 132: Regenerate Keys
Step 3 To regenerate the SSL Certificate, select the “Regenerate SSL Certif-
icate radio button, click OK for the message pop-up and the following
screen displays (see Figure 133):
When an SSL Certificate is generated, the HTTP server will be
restarted and web access will be unavailable during this time (approx-
PS
imately 15 seconds).
Note
Figure 133: Regenerate SSL Certificate
Step 4 Edit the Certificate Data, then click on OK.

Step 5 To regenerate the SSH Key, select the radio button next to “Regener-
ate 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.
PS
Note
Figure 134: Regenerate SSH Key

Step 6 Click on OK.
End of Procedure

Configure Security Policy

DCN (eth0) Port Using the Serial Port on p. 402) and is logged on as a supe-
ruser using eVision.
From the Configuration view with the Administration tree expanded:
Procedure
Step 1 Right click on “Security Policy” in the selection tree pane and select
Edit Policy, and the following screen displays to show the current Pol-
icy Strength setting and a description of the policy rules:
Figure 135: Edit Policy Strength
Step 2 To change the Policy Strength, select the desired setting from the
Strength drop-down list, then click on OK.
End of Procedure

Configure Local Users

Procedure
Step 1 Expand the System, Administration, Users and Local entities in the
selection tree pane, by clicking on the “+” signs next to each entity to
expand each view.
Current Status Then

Entering a new user? Continue with the next
step.
Editing data other than the password for an Go to Step 5.
existing user?
Editing just the password for an existing user? Go to Step 7.
Deleting a user? Go to Step 9.
Remove a login lock-out? Go to Step 11.
Entering a new user can only be done by a user with superuser

PS
privilege.
Note
Step 3 Right click on “Local” in the selection tree pane and select Add User
and the following screen displays:
Figure 136: Add User

Step 4 Enter the required data to establish a new user. Details on the func-
tion and rules for each data entry is located at Administration on
p. 646.
After editing the user information, click on OK. The display will update
End of Procedure
Editing user data other than the user’s own password can only be
PS
done by a user with superuser privilege.

Note
Step 5 Right click on the user name to be edited in the selection tree pane
and select Edit User and the following screen displays:
Figure 137: Edit User
Step 6 Edit the required data for this user. Details on the function and rules
for each data entry is located at Administration on p. 646.
After editing the user information, click on OK. The display will update
End of Procedure
Editing the user password can be done by the user or a user with
PS
superuser privilege.
Note
Step 7 Right click on the user name to be edited in the selection tree pane
and select Edit Password and the following screen displays:

Figure 138: Edit User Password
Step 8 Edit the password for this user. Details on the function and rules for
each data entry is located at Administration on p. 646.
After editing the password, click on OK. The display will update to
show the edited information.
End of Procedure
PS
Deleting a user requires superuser privilege.

Note
Step 9 Right click on the User Name to be deleted, select Delete User, and
the following screen displays:

Figure 139: Delete User
Step 10 Verify that the selected user is the one to be deleted. Click on OK.
The display will update to show the deleted information.
End of Procedure
PS
Removing a lock-out from a user requires superuser privilege.

Note
Step 11 Right click on the User Name that is locked, select Remove Lock, and
the following screen displays:
Figure 140: Remove Lock
Step 12 Verify that the selected user is the one from whom the lock-out is to
be removed. Click on OK. The display updates.
End of Procedure

Configure Remote Authentication

Procedure
Step 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.
Step 2 Right click on “Remote Authentication” in the selection tree pane and
select Edit Remote Authentication and the following screen displays:
Figure 141: Edit Remote Authentication

Step 3 Enter the required data for the Remote Authentication Protocol Sys-
tem Level Configuration including Authentication Protocol, Authenti-
cation 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 Adminis-
tration on p. 646 and User Management and Security in FSP 150CC
GE11x R6.1 Installation and Operations Manual document.
Step 4 Enter the required data for each Remote Authentication Server (1, 2
and 3) including Server Status, Priority, IP Address, Server Secret,

Provision SNMP Access
Port, Accounting Port, Timeout and Retries. Details on the function

and rules for each entry is located at Administration on p. 646 and
User Management and Security in FSP 150CC GE11x R6.1 Installa-
tion and Operations Manual document.
If Remote Authentication is activated, local access will be

authenticated based on the selected Access Order. If Access Order is
PS
Local, the system will perform the authentication in local first, then in
the remote server if a user does not exist in local; if Access Order is
Remote, vice versa. For details, see User Management and Security
Note
in FSP 150CC GE11x R6.1 Installation and Operations Manual
document.
Step 5 Verify that all data is entered properly, then click on OK.
End of Procedure
Provision SNMP Access
SNMP information is contained in the FSP 150CC-GE11x SNMP Reference
Guide.
Data on setting for SNMP settings are located at SNMP on p. 643 and SNMP
Support in FSP 150CC GE11x R6.1 Installation and Operations Manual docu-
ment.
Enable Software Licensing

The following software licensing options are available:
Provider Backbone Bridge (PBB), supported in GE112,GE114,GE114H and
GE114PH, when enabled, supports the provisioning of ITAG Based manage-
ment tunnel, enabling PBB Frames on services and configuring ITAG Push on
services.
Precision Time Protocol (PTP), supported in GE114S and GE114SH,
enables/disables Transparent Clock and Telecom Slave functionalities.
PTP - MC/BC, supported in GE114S and GE114SH, enables/disables Master
Clock/Boundary Clock functionalities for up to 4 remote slaves at the maximum
PTP message rate, wherein, the Master Clock is only supported in GE114SH
and cannot coexist with a Boundary Clock.

Procedure
Step 1 Select the Maintenance Application on the tool bar or select Mainte-
nance 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.
Step 2 Enter a right click on Feature Management and select Edit Feature.
An Edit Feature Management screen displays
Figure 142: Edit Feature Management

Step 3 Select Enabled from the Status dropdown list associated with the
desired feature.
A License Warning window appears
Figure 143: License Warning Window
Step 4 Select OK to close the warning window.

Configure Flexible Port (Ethernet Port II)
Step 5 Select OK to confirm enabling the feature.

The Feature Management Status is displayed and indicates it is in the
Enabled state
Figure 144: Feature Management Status View
Step 6 Repeat Step 2 through Step 5 for each additional desired feature.
End of Procedure
Configure Flexible Port (Ethernet Port II)

The Flexible Port (Ethernet Port two) can function as either a Network Port or an
Access Port. When switching from one to another, the port must not be associ-
ated with any of the entities below:
o Protection group
o LAG
o Management tunnel
o EVC Flow (When the port is in EVPL mode)
o ERP
o SHG
Switching Network Port 2 to function as an Access Port

(or switching back) will cause the system to reboot,
WARNING dropping communications and traffic, and the traffic on
other ports may be influenced.

Procedure
Step 1 Ensure that no other entities are associated with Port 2 (1+1 protec-
tion, LAG, management tunnel, flow, etc.), otherwise, delete them
first.
Step 2 Select Configuration view. Expand the System, NE-1, NTE entities in
the Selection Tree, by clicking on the “+” signs next to each entity.
Step 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”).
Step 4 Select OK.
A confirmation window appears
Step 5 Select OK.
A system warm reboot occurs
Step 6 After approximately 2 minutes a login screen appears. Log back onto
the system.
End of Procedure
Provision Access Port Services

Refer to the following procedures for provisioning and editing Access Port Ser-
vices:
• Ethernet Private Line Service Provisioning on p. 256
• Ethernet Virtual Private Line Service Provisioning on p. 267
In addition to traffic services, Access Ports may be provisioned for PoE services
on the GE114PH. See Power Over Ethernet Service Provisioning on p. 283
For GE112
The GE112 supports four Ethernet combination ports that may be configured for
copper (10/100/1000 BaseT) or optical (100BaseFX/1000BaseX). Port 1 is fixed
ured for LAG or 1+1 Network protection, or as an Access port. Ports 3 and 4 are
dedicated Access ports. The FSP 150CC-GE112 is a version of the product that
does not include Sync-E capability.
For GE114x
The GE114/GE114S/GE114H/GE114SH/GE114PH support six Ethernet combi-
nation ports that may be configured for copper (10/100/1000 BaseT) or optical
(100BaseFX/1000BaseX). 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 protec-
tion, or as an Access port. Ports 3 through 6 are dedicated Access ports.

Ethernet Private Line Service Provisioning

Refer to the following for provisioning a port in Ethernet Private Line (EPL)
Mode. It is recommended that you pre-determine the provisioning details and
ensure that they meet the FSP 150CC’s provisioning rules prior to making
changes to an existing service or placing an additional Access Port into service.
Ensure that CIR, EIR, CBS, EBS settings are compatible 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 on p. 666 to determine
the default values, value ranges and rules for each option in the following proce-
dure. For Control Data Protocol provisioning, see CPD Filters Options and
Rules on p. 709.
Procedure
Step 1 Observe the current Service Type. The status will be used in the fol-
lowing steps.
a) Select Configuration view.
b) Expand the System, NE-1 and NTE entities in the Selection Tree,
by clicking on the “+” signs next to each entity.
c) Select the desired Access Port facility in the Selection Tree.
The Access Port facility status window is displayed and the Con-
figuration Tab is selected
d) Observe the current Service Type.
Changing Service Type on a facility will drop all traffic on

WARNING the port, including Management Tunnel connectivity and
Maintenance End Points.
Step 2 Right click on the Access Port facility and select Edit Configuration.
An Edit Configuration window appears

Figure 145: Edit Access Port EPL Configuration View


Current Status Then
Is the current Service Type set to EPL? Go to Step 6.
Is the Service Type set to EVPL? Continue with the next
step.
Step 4 If not already in the unassigned state, set the Administrative State to
Unassigned and click on Apply.
The screen will update
Set the Service Type to EPL

Click on OK.
Step 5 Enter a right click on the Access Port facility and select Edit Configu-
ration.

Step 6 Enter the Access Port facility changes:
Identification
a) Enter an Alias, as required
State
b) Leave the Administrative State “Unassigned”
Port
c) Select the desired Media Type (GE112 Ports 3-4, GE114x Ports
3-6). Port 2 is available if not used as a Network Protection port.
d) Enter the desired MTU size
e) Select the Configured Speed option
f) Select the Port MDIX option (copper ports)
g) Enable/Disable Auto Diagnostic
h) Enable/Disable Drop Eligibility Indicator
Service
i) Select the desired AFP option
j) Enable/Disable Q in Q EtherType Override

k) Edit the Q in Q Ethertype setting if desired (if Q in Q Override is

set to Enabled)
l) Enable/Disable 802.3 RX Pause
m) Enable/Disable 802.3 TX Pause
n) Enable/Disable Port Shaping
o) Enter the desired Port Shaped Speed (Setting can not be lower
than the CIR setting for the flow) if Port Shaping is Enabled.
Link Loss Forwarding
p) Enable/Disable Port LLF Status
q) Enter the desired Delay value
r) Select the desired TX Action
s) Enter the desired Local Link ID
t) Select the desired Trigger Events
u) Select the desired Remote Link IDs
LLDP Destination MAC Address
v) 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.
Step 7 Expand the Access Port entity and right click on Flow-1 under the
Access Port and select Edit Configuration.
Figure 147: Edit Access Port EPL Flow Configuration View

Step 8 Enter the EPL Flow facility changes: (see Access Port Configuration
Options and Rules on p. 666 for details and rules).
Connection
a) Edit the Circuit Name.
b) Select a Network Port Interface and an Access Interface.
c) Set Policing to Enabled or Disabled; if enabled, select the desired
Policing Control mode.
d) Select the desired COS (Class Of Service).
e) Enable/Disable Provider Backbone Bridging (PBB) Frames.
When enabled, incoming PBB frames are allowed to enter the
Access Port, they are dropped otherwise.
PBB frame related functionalities are not supported in

PS
GE114S/GE114SH.
Note
f) Set a desired mode of A2N shaping (Flow-based or Port-based).

g) Set the desired Frame Loss Threshold Ratio percentage.
h) Set the desired Frame Loss Threshold.
i) Enable/Disable Independent N2A Rate Limiting (if Enabled is
selected, N2A Settings appear below the A2N Settings).
Learning Attributes
j) Set the Interface Learning Control, Protected Learning Control
and Max Forwarding Table Entries for Network Port and Access
Port respectively.
If the Network Interface and Access Interface of a flow are both

common Ethernet ports rather than ERP or SHG, enabling MAC
PS
Based Interface Learning may cause traffic congestion due to

Note insufficient buffer size for broadcasting frames.
k) Set the desired MAC Table Full Action.

l) Set the Aging Time for the dynamic forwarding table entries.
Tag Management
m) Select the C-Tag Control.
n) Enter the C-Tag (if C-Tag Control is Push).
o) Select the S-Tag Control.
p) Enter the S-Tag (if S-Tag Control is Push).
q) Select the I-Tag Control (To push an I-Tag, both C-Tag and
S-Tag Control must be set to none).
r) Enter the I-Tag (if I-Tag Control is Push).

s) Select the Destination Backbone MAC Control (To enable Desti-

nation Backbone MAC, I-Tag Control must be set to Push).
t) Enter the Destination Backbone MAC Address (if Destination
Backbone MAC is enabled).
A2N Settings
u) The following A2N Policer Settings are editable: CIR, EIR, CBS,
EBS, CM, TCM, 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.
v) Enter A2N Shaper settings (BS). If Port-based A2N shaping is
used, it is entered in the A2N Shaper page of the selected Net-
work Port. If Flow-based A2N shaping is used, it is entered in the
A2N Setting box of the EVC.
w) If Independent N2A Rating Limiting is enabled, enter N2A Policer
settings (CIR, EIR, CBS, EBS, CM, CF) if N2A Rate Limiting is
Enabled.
x) Enter N2A Shaper settings (BS).
Click on OK.
Step 9 Enter a right click on the EPL flow facility and select Add Forwarding
Table Entry.
An Add Forwarding Table Entry window appears
Figure 148: 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.

Figure 149: View FDB
d) Enter a right click on one FDB entry and select the desired opera-
tions from the menu: View Configuration, Edit Configuration or
Delete FDB Entry.
Figure 150: FDB Selection Menu
Step 10 Enter a right click on the EPL flow facility and select the desired oper-
ations from the menu: Flush FDB, or Clear Blocked State.
Step 11 Enter a right click on the Access Port facility and select Edit CPD Fil-
ters.
An Edit CPD Filters window appears

Figure 151: Edit Access Port CPD Filters View
Step 12 Enter the desired CPD settings:

a) Set the desired L2PT Tunnel MAC address as required.

b) Select Discard or Pass Thru for each protocol or group as
desired.
CPD settings can be done by individual protocol or by group. If the

Group setting is changed (Bridge Group, GARP Group, Cisco, LAN
Bridges) all sub-group protocols have a setting for “Use Group Set-
ting” that forces the use of the Group setting. Otherwise the CPD
function is independent for each protocol (see CPD options and rules
PS
CPD Filters Options and Rules on p. 709).

Note
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.
Step 13 Enter a right click on the Access Port facility and select Edit
EFM-OAM.
An Edit EFM-OAM window appears

Figure 152: Edit Access Port EFM-OAM View
Step 14 Enable or Disable EFM-OAM as required.
If Enabled, select the desired Local Configuration Mode.
Click on OK.
Step 15 Enter a right click on the Access Port facility and select Edit N2A
Shapers.
An Edit N2A Shapers window appears
Figure 153: Edit Access Port N2A Shapers View
Step 16 Edit the N2A Shaper QID BS setting as desired.

Click on OK.

ration.

Step 18 Select “IS” for the Administrative State.

Click on OK.
When setting the Service State to IS (In Service) and an error mes-
sage appears, the most likely problem is that the flow settings are
incompatible with each other, the port settings, or there is a conflict
PS
with C-Tags or S-Tags assigned to other flows on other Access Ports.

Compare settings to the details and rules (see Ethernet Private Line
Note
(EPL) Service Provisioning on p. 667), resolve these issues, and
repeat Step 18.
Step 19 For PCP, PTP, Sync-E, LLDP, LAG and/or SHG provisioning, refer to
the following notes:
For configuration of PCP functionality, see Edit PCP Configuration on

PS
p. 660. For a description of PCP functionality, see the FSP

150CC-GE11x R6.1 Technical Descriptions document.
Note

For configuration of PTP functionality, see Provision Precision Time

Protocol (PTP) (GE114S/GE114SH) on p. 310. For a description of
PTP functionality, see the FSP 150CC-GE11x R6.1 Technical
For configuration of Sync-E functionality, see Provision Synchronous
Ethernet (Sync-E) (GE114S/GE114SH) on p. 337. For a description
PS of Synchronous Ethernet, see the FSP 150CC-GE11x R6.1 Technical
Note Descriptions document.
For configuration of LLDP functionality, see Provision Link Layer
Discovery Protocol (LLDP) on p. 351. For a description of LLDP
functionality, see the FSP 150CC-GE11x R6.1 Technical Descriptions
document.
The GE11x supports LAG on Network Ports and Access Ports. Up to

3 LAG Groups can be configured, including two Access Port LAG
PS
Groups and one Network Port LAG Group. (The GE112 supports one
Access Port LAG Group.) For LAG Provisioning procedure on Access
Note
Port, see Provision Ports in a LAG Group on p. 292.
The GE11x supports SHG on Access Ports. SHG and LAG cannot
both be provisioned on the same Access Ports. Use the above steps
PS
to provision the other Access Ports to be present on the SHG. For

SHG provisioning procedure, see Provision Ports in a Split Horizon
Note
Group (SHG) on p. 297.
Step 20 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.
Step 21 Configure all intermediate devices appropriately for carrying traffic
from this FSP 150CC to the far end FSP 150CC.
Step 22 Repeat above steps for each EPL service to be created at the far end
FSP 150CC.
End of Procedure

Ethernet Virtual Private Line Service Provisioning

Refer to the following for provisioning a Ethernet Virtual Private Line (EVPL) ser-
vice.
It is recommended that you pre-determine the provisioning details and ensure
that they meet the FSP 150CC’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.
dure. For Control Data Protocol provisioning, see CPD Filters Options and
Rules on p. 709.
Procedure
Step 1 Observe the current Service Type. The status will be used in the fol-
lowing steps.
a) Select Configuration view
b) Expand the System, NE-1, NTE and desired Access Port facility
entities in the Selection Tree.
The Access Port facility status window is displayed and the Con-
figuration Tab is selected
c) Observe the current Service Type.

ration.

Figure 155: Edit Access Port (EVPL) Configuration View
Current Status Then
Is the current Service Type set to Go to Step 5.
EVPL?
Is the Service Type set to EPL? Continue with the next
step.
Step 4 If not already in the unassigned state, set the Administrative State to
Unassigned and click on Apply.
The screen will update
Set the Service Type to EVPL.

Click on OK.
ration.

Figure 156: Edit Access Port EVPL Configuration View

Step 6 Enter the Access Port facility changes.

Identification
a) Enter an Alias, as required
State
b) Leave the Administrative State as “Unassigned” for now
Port
c) Select the desired Media Type (GE112 Ports 3-4, GE114x Ports
3-6). Port 2 is available if not used as a Network Protection port.

d) Enter the desired MTU size

e) Select the Port Configured Speed option
f) Select the Port MDIX option (copper ports)
g) Enable/Disable Auto Diagnostic
h) Enable/Disable Drop Eligibility Indicator
Service
i) Select the desired AFP option
j) Edit the Q in Q Ethertype if desired (if Q in Q EtherType Override
is Enabled)
k) Enable/Disable Q in Q EtherType Override
l) Edit the Port VLAN ID if required
m) Select the desired Priority Map Mode
n) Enable/Disable Port Shaping
o) Enter the desired Port Shaped Speed (if Port Shaping is Enabled)
p) Enable/Disable N2A VLAN Trunking
q) Enable/Disable A2N Push Port VID
r) Enable/Disable N2A Pop Port VID
Link Loss Forwarding
s) Enable/Disable Port LLF Status
t) Enter the desired Delay value
u) Select the desired TX Action
v) Enter the desired Local Link ID
w) Select the desired Trigger Events
x) Select the desired Remote Link IDs
LLDP Destination MAC Address
y) 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.
Step 7 Enter a right click on the Access Port facility and select Edit CPD Fil-
ters.
An Edit CPD Filters window appears

Figure 157: Edit Access Port CPD Filters View
Step 8 Select Discard, Pass Thru or Use Group Setting for each protocol or
group as desired.
CPD settings can be done by individual protocol or by group. If the

Group setting is changed (Bridge Group, GARP Group, Cisco, LAN
Bridges) all sub-group protocols have a setting for “Use Group Set-
ting” that will force the use of the Group setting. Otherwise the CPD
function is independent for each protocol (see CPD options and rules
PS
CPD Filters Options and Rules on p. 709).

Note
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.
Step 9 Enter a right click on the Access Port facility and select Edit
EFM-OAM.
An Edit EFM-OAM window appears

Figure 158: Edit Access Port EFM-OAM View
Step 10 Enable or Disable EFM-OAM as required.
If Enabled, select the desired Local Configuration Mode.
Click on OK.
Current Status Then
Is Priority Map Mode set to None or are Go to Step 14.
the default priorities acceptable?
Does the priority mapping require Continue with the next
editing? step.
Step 12 Enter a right click on the Access Port facility and select Edit Priority
Mapping.
An Edit Priority Mapping window appears

Figure 159: Edit Access Port Priority Mapping View
Step 13 For each In Priority edit.:

a) Priority Control
b) New Priority (if Priority Control = Swap)
c) COS
d) Inner Tag Priority

e) Outer Tag Priority
For 802.1P and IP-TOS, there are 8 priority levels, but IP-DSCP has
PS
64 levels.
Note
Click on OK.
Step 14 Right click on the Access Port facility and select Create Flow.
A Create Flow window appears

Figure 160: Create Access Port EVPL Flow View
Step 15 Enter the EVPL Flow attributes: (see Ethernet Virtual Private Line
(EVPL) Service Provisioning on p. 679 for details and rules)
Identification
a) Select the desired Flow ID from the drop-down list
Connection
b) Enter a Circuit Name
c) Select the EVC Type (Regular or Default)
d) Select desired Network Interface and Access Interface
e) Enable/Disable Policing and Set Policing Control if Policing is
enabled
f) Select the desired COS (Class Of Service)
g) Enable/Disable Multi-COS (if Enabled is selected, the display
changes - see Figure 161
h) Select the N2A COS Priority (if Multi-COS = Enabled)
i) Enable/Disable Untagged Frames

j) Enable/Disable Provider Backbone Bridging (PBB) Frames.

When enabled, incoming PBB frames are allowed to enter the
Access Port, they are dropped otherwise.
PBB frames and related functionalities are not supported in

PS
GE114S/GE114SH.
Note
k) Enable/Disable Inner Tag Priority Control

l) Enable/Disable Outer Tag Priority Control
m) Enable/Disable Independent N2A Rate Limiting (Default as
Enabled if Multi COS is Enabled. If Enabled is selected, N2A
CIR/EIR appear below the A2N Settings)
n) Set the desired Frame Loss Threshold Ratio
o) Set the desired Frame Loss Threshold
p) Select a desired A2N Shaping mode.
A2N Shaping and N2A Shaping are automatically set to Port Based
PS
as default for GE114S and GE114SH.

Note
q) Enable/Disable N2N Forwarding.

Learning Attributes
r) Set the Interface Learning Control, Protected Learning Control
and Max Forwarding Table Entries for Network Port and Access
Port respectively.
If the Network Interface and Access Interface of a flow are both

common Ethernet ports rather than ERP or SHG, enabling MAC
PS
Based Interface Learning may cause traffic congestion due to

Note insufficient buffer size for broadcasting frames.
s) Set the desired MAC Table Full Action.

t) Set the Aging Time for the dynamic forwarding table entries.
Tag Management
u) Select the C-Tag Control
v) Enter the C-Tag (if C-Tag Control = Push, Pop, Push VID or Swap
VID)
w) Select the S-Tag Control
x) Enter the S-Tag (if S-Tag Control = Push or Swap ID)

y) Enable/Disable Preserve S-Tag Properties (if S-Tag Control =

Swap VID)
z) Enable/Disable N2A Outer Tag Priority (if C-Tag Control = Pop)
aa) Select the I-Tag Control (To push an I-Tag or VID, both C-Tag
and S-Tag Control must be set to none).
ab) Enter the I-Tag (if I-Tag Control is Push).
ac) Select the Destination Backbone MAC Control (To enable Desti-
nation Backbone MAC, I-Tag Control must be set to Push or Push
IS ID).
ad) Enter the Destination Backbone MAC Address (if Destination
Backbone MAC is enabled).
A2N Settings
ae) If Multi-COS is Disabled: 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.
af) If Multi-COS is Enabled (see Figure 161): 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
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) Enter A2N Shaper settings (BS). If Port-based A2N shaping is
used, it is entered in the A2N Shaper page of the selected Net-
work Port. If Flow-based A2N shaping is used, it is 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.
A2N Shaper QID BS settings are editable if the QID for a given
PS
Policer ID is changed.
Note
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 by clicking the appropriate “active” boxes. Only
“active” Policers are editable. (N2A Shaper(s) are edited else-
where and are covered later in this procedure)
VLAN Members
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 if the port is
PS
not in the Unassigned state.
Note
Figure 161: Create EVPL Multi-COS Flow Options

Step 16 Expand the Access Port facility entity and select the newly created
flow to verify the entry.
Step 17 To enter additional Flows, repeat Step 14 to Step 16.

Step 18 Enter a right click on an EVPL flow facility and select Add Forwarding
Table Entry.
An Add Forwarding Table Entry window appears
Figure 162: Add Forwarding Table Entry
a) Specify the Destination Address and select a Destination Port

b) Select the desired Learning Action.
Click on OK.
c) Select the FDB tab to view the existing Forwarding Table Entries.
Figure 163: View FDB
d) Enter a right click on one FDB entry and select the desired opera-
tions from the menu: View Configuration, Edit Configuration or
Delete FDB Entry.

Figure 164: FDB Selection Menu
Step 19 Enter a right click on the EPL flow facility and select the desired oper-
ations from the menu: Flush FDB, or Clear Blocked State.
Step 20 Enter a right click on the Access Port facility and select Edit N2A
Shapers.
An Edit N2A Shapers window appears
Figure 165: Edit Access Port N2A Shapers View

Step 21 Edit each N2A Shaper QID BS setting as desired.

Click on OK.
ration.

Figure 166: Edit Access Port EVPL Configuration View
Step 23 Select “IS” for the Administrative State.

Click on OK.

When setting the Service State to IS (In Service) and an error mes-
sage appears, the most likely problem is that the flow settings are
incompatible with each other, the port settings, or there is a conflict
PS
with C-Tags or S-Tags assigned to other flows on other Access Ports.
Compare settings to the details and rules (see Ethernet Virtual Private
Note
Line (EVPL) Service Provisioning on p. 679), resolve these issues,
and repeat Step 18
PS
p. 660. For a description of PCP functionality, See the GE11x

Technical Descriptions.
Note

Protocol (PTP) (GE114S/GE114SH) on p. 310
PS
Ethernet (Sync-E) (GE114S/GE114SH) on p. 337

Note For configuration of LLDP functionality, see Provision Link Layer

Discovery Protocol (LLDP) on p. 351

PS
Access Port LAG Group.) For LAG Provisioning procedure on Access
Note
Port, see Provision Ports in a LAG Group on p. 292.
The GE11x supports SHG on Access Ports. SHG and LAG cannot
both be provisioned on the same Access Ports. Use the above steps
PS
to provision the other Access Ports to be present on the SHG. For

SHG provisioning procedure, see Provision Ports in a Split Horizon
Note
Group (SHG) on p. 297.
Step 25 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.
Step 26 Configure all intermediate devices appropriately for carrying traffic
from this FSP 150CC to the far end FSP 150CC.

Step 27 Repeat above steps for each EPL service to be created at the far end
FSP 150CC.
End of Procedure

Power Over Ethernet Service Provisioning

Refer to the following for provisioning a PoE service on a GE114PH.
dure.
Power-Supplying Equipment (PSE) feature is configured on Group level and
port level.
Procedure
Step 1 Make sure the Configuration Panel is open.

Step 2 Make sure the Access Port is in Copper mode. For more information
about media type, see Ethernet Private Line Service Provisioning on
p. 256
Step 3 Right click the PSE Node in the Selection tree, and select Edit Config-
uration from the pop-up menu. The Configuration Screen is displayed.
See Figure 167 on p. 284
Step 4 Enter Power Usage Threshold.
Step 5 Select from the drop-down menu to Enable or Disable the Notification.
Step 6 Select from the drop-down menu to Enable or Disable the Non-Stan-
dard Powered Devices (PD).
Step 7 Click the “+” to open the PSE.
Step 8 Right Click a Port entity in the tree and select Edit Configuration from
the pop-up menu. An Edit Configuration screen is displayed.See
Figure 168 on p. 284.
Step 9 Enter Administrative state for the Port.
Step 10 Enter Power Pair configuration for the Port.
Step 11 (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.
Step 12 Select an Power Level form on the Available Power Level
Drop-down Menu.
End of Procedure

Figure 167: Edit Global Power-Supplying Equipment (PSE) Configuration
Figure 168: Edit Port PSE Configuration

Provision Network Ports

The following procedures assume that the user has completed the physical
installation procedures in Physical Installation on p. 123, including installation of
SFPs and connecting fiber cables to the Network Ports. It is also assumed that
the user has configured the NID with an IP address and connected the NID to a
DCN or LAN (see Set Up the FSP 150CC DCN (eth0) Port Using the Serial Port
on p. 402) and has provisioned the Flexible Port for the desired operation (see
Configure Flexible Port (Ethernet Port II) on p. 254).
It is also assumed that the user is logged on to eVision with the proper privilege
level for provisioning (see User Authorization Privilege Levels on p. 605) 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.
Provision Network Ports without LAG or Protection Group on p. 285
Provision Network Ports in a Protection Group on p. 289
Provision Ports in a LAG Group on p. 292
Provision Ports in a Split Horizon Group (SHG) on p. 297
Provision Network Ports in an Ethernet Ring Protection Group on p. 299
Provision Network Ports without LAG or Protection

Group
Procedure
Step 1 Expand the System Name entity in the Selection Tree.

Step 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.
Step 3 Right click on E1000-N-1 interface in the selection tree pane and
select Edit Configuration and the following screen displays:

Figure 169: Edit Network Interface 1
Step 4 An alias can be entered to permit easy identification of this particular
interface.
The Administrative State can be changed between IS (default value)
Maintenance, Management and Unassigned. See Entity State
Descriptions on p. 599 for details.
Various Port, Service and LLF data can be edited. For details on each
editable item see Network Port Configuration Options and Rules on
p. 661.
After editing the interface information, click on OK. The display will
Step 5 Right click on the E1000-N-1 interface and select “Edit EFM OAM”
and the details pane displays:

Figure 170: Edit OAM-EFM Network Interface 1

Step 6 The OAM State and Local Configuration Mode can be edited. After
selecting the desired settings, click on OK.
select Edit CPD Filters and the following screen displays:
Figure 171: Edit Network Port CPD Filters

Step 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.
All other CPD Filter setting should be set as desired.
Click on OK.

PS

Note
.
PS

Note
Protocol (PTP) (GE114S/GE114SH) on p. 310. For a description of
PTP functionality, see the FSP 150CC-GE11x R6.1 Technical
Ethernet (Sync-E) (GE114S/GE114SH) on p. 337. For a description
PS
of Synchronous Ethernet, see the FSP 150CC-GE11x R6.1 Technical

Note Descriptions document.
For configuration of LLDP functionality, see Provision Link Layer
Discovery Protocol (LLDP) on p. 351. For a description of LLDP
functionality, see the FSP 150CC-GE11x R6.1 Technical Descriptions
document.

PS
Access Port LAG Group.) For LAG Provisioning procedure on
Note
Network Port, see Provision Ports in a LAG Group on p. 292.
The GE11x supports SHG on Network Ports. SHG and LAG cannot
both be provisioned on the same Network Ports. Use the above steps
PS
to provision the Network Ports which are not in a LAG to be present

on the SHG. For SHG provisioning procedure, see Provision Ports in
Note
a Split Horizon Group (SHG) on p. 297.

Provision Network Ports in a Protection Group

Procedure

Step 2 Scroll down the selection tree to “Protection Groups” and click on the
“+” sign next to it to expand it.
Step 3 Select NE-1 and click on the “+” sign to expand it.
Step 4 Right click on NTE11x and select “Add Protection Group” and the fol-
lowing screen displays:
Figure 172: Create Protection Group

Step 5 Enter a User Label if desired or required.

Select the desired Protection Mode: 1+1 or Dual Active Receive.
Dual Active Receive is a special setting that requires an external
device that provides discrimination to present well behaved traffic
PS
to the network ports. It does not permit doubling the Network

Note Port’s maximum bandwidth.
Click on OK.
The NE display will update.
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 on p. 599).l
Step 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.
select Edit Configuration and the following screen displays:

Step 8 An alias can be entered to permit easy identification of this particular
interface.
The Administrative State can be changed between IS (default value)
Maintenance, Management and Unassigned. See Entity State
Descriptions on p. 599 for details.
Various Port, Service and LLF data can be edited. For details on each
editable item, see Network Port Configuration Options and Rules on
p. 661.
It is recommended that Link Loss Forwarding Delay be provisioned

PS
with a non-zero value on the protection group member ports, in case

of LLF vibration during the protection switching process.
Note
After editing the interface information, click on OK. The display will
Step 9 Right click on the E1000-N-1 interface and select “Edit EFM OAM”
and the details pane displays:


Step 11 If 1+1 or Dual Active Receive protection has been configured, repeat
Step 7 through Step 10 for E1000-N-2.
select Edit CPD Filters and the following screen displays:
Figure 175: Edit CPD Filters

Step 13 Set the desired CPD filter options.

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.

PS p. 660. For a description of PCP functionality, see the FSP
Note
End of Procedure
a
Provision Ports in a LAG Group

Use the following procedure for configuring Network or Access Ports in a LAG
Group. Refer to LAG Configuration Rules on p. 656 to determine the default val-
ues, value ranges and rules for each option in the following procedure.
3 LAG Groups can be configured using any 2 Access Ports in each
PS
group, with each Access Port being used only once. (The GE112
Note supports one Access Port LAG Group.)
Procedure

Step 3 Select NTE11x and click on the “+” sign to expand it.
Step 4 Right click on E1000-N-1 (or first Access Port) interface in the selec-
tion tree pane and select Edit Configuration and the following screen
displays:


Step 5 For successful LAG configuration:

Administrative State must be IS, Management or Maintenance
Configured Speed can not be “Auto” (any other option is acceptable)
Auto Diagnostic must be “Disabled”
All other options should be set as desired.
Click on OK.
Step 6 Right click on the E1000-N-1 (or first Access Port) interface and
select “Edit EFM OAM” and the details pane displays:

LAG traffic will be impacted on warm restart if EFM OAM

WARNING is enabled, therefore it is recommended to disable EFM
OAM on LAG ports.
Step 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 dis-
plays:
Figure 178: Edit Network Port CPD Filters

Step 9 Set the desired CPD filter options.

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.
Step 10 Select LAG and click on the “+” sign to expand it.
Step 11 Right click on NE-1 and select “Create LAG” and the following screen
is displayed.
Figure 179: Create LAG

Step 12 Enter an Alias if desired

Select the desired Administrative State (should be “IS”)
Enable/Disable LAG Protocols (see note and warning)
Enable/Disable LACP Control (see note and warning)
Enable/Disable CCM Defect Detection (Enable is denied if a properly
configured MEP does not exist on the port)
Edit System Priority if desired
Edit Collector Max Delay if desired
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 Mem-

bers 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.
Enabled – systems determine Master and Slave assignment
between two LAG partners. Active link selection is controlled by
PS
LAG Master based on provisionable priorities of LAG Member

Note ports and status of Signal Fail on a link.
Disabled – both LAG devices determine an active link inde-
pendently based on the highest priority port that does not detect a
Signal Fail. LAG partner systems must have port priorities provi-
sioned identically
The LACP-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
WARNING is derived from the port selection process.
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.
End of Procedure

Provision Ports in a Split Horizon Group (SHG)

Use the following procedure for configuring Network or Access Ports in a SHG
Group. Refer to the table content SHG on p. 629 to determine the default val-
ues, value ranges and rules for each option in the following procedure.
Procedure
Step 1 Expand the System and SHG entities in the Selection Tree.
Step 2 Enter a right click on NE-1 and select Create SHG and the following
screen displays:
Figure 180: Create SHG

Step 3 Select the desired SHG index and enter the desired Alias.
Step 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.
Step 5 The new SHG appears in the SHG Configuration entity list of the
Details Pane.
Step 6 Enter a right click on the new SHG entity in the details pane and
select View Configuration to verify provisioning entry.

Figure 181: SHG Entity Menu Options
Step 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.
Step 8 Repeat above steps at the far end node.
Step 9 Very end-to-end connectivity for the SHG services. To view Forward-
ing 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.
End of Procedure

Provision Network Ports in an Ethernet Ring

Protection Group
Refer to the table ERP-1--n - (GE114x) (Create/Edit) on p. 626 to determine the
default values, value ranges and rules for each option in the following proce-
dure.
Procedure
Perform the following at Site A:

Step 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.
Step 3 Right click on NE-1 and select “Create ERP” and the following screen
displays:
Figure 182: Create Ethernet Ring Protection Group

Step 4 Enter the ERP configuration details:

a) Enter the ERP Index and ERP Label.
b) Select the desired Administrative State.
c) Enter the ERP Group RAPS Node ID, RAPS Ring Id, RAPS
VLAN Tag, RAPS Tag Ethertype, RAPS MD Level, Guard Time,
Wait-to-Restore Time and Hold-off Time.
d) Enable/Disable Revertive option.
e) Enable/Disable Management Tunnel Protection.
f) Enalbe/Disable Sub-Ring without Virtual Channel.

g) Select Network Port for Ring Port 0 and Ring Port 1.

h) Select the Ring Port 0/1 RPL Role and MEP options, if MEPs
have already been created (they will be created later in this pro-
cedure). If no MEPs have been created, then leave the option set
to None.
There can be only one RPL owner in a ring. A ring node config-
ured as the RPL-Owner link in a G.8032 Ring should be config-
ured with the largest Node ID of all the nodes in the ring. A
non-owner node configured as the highest priority ring node may
PS
result in temporary ring segmentation for cases of simultaneous

Note reboots of multiple ring nodes. In this case, temporary ring seg-
mentation time is limited to the configured value of the RPL
Owner Wait-to-Restore.
Configuring CFM MEPs is optional, although recommended, for

PS
fast failure detection and CFM monitoring in a ring environment.

Note
i) Click on OK.
The ERP configuration displays
Figure 183: View ERP Configuration Details

Step 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.
Step 6 Repeat the above steps for a second ERP instance, if required.
Configure Pass-Through flow(s) to allow ring management VLAN traffic:
Step 7 Expand the PT Flows entity in the Selection Tree Pane, enter a right
click on Flow and select Create Flow.
A Pass-through Flow Configuration screen appears
Figure 184: Pass-through Flow Configuration

Step 8 Enter the Pass-through Flow details: (see Pass-Through Flow Config-
uration Options and Rules on p. 652 for details and rules)
Identification
a) Select a desired Passthrough Flow EID from the drop-down list
b) Enter a Circuit Name
AdminState
c) Select the desired Administrative State
Connection
d) Select the desired EVC Type
e) Enable/disable Policing

f) Enable/disable Multi COS. (If enabled is selected, the display

changes, see Figure 185 on p. 302)
g) Select the COS (if Multi COS is disabled)
h) Enable/disable Untagged Frames
i) Select the desired Loop Avoidance (ERP instance for this
pass-through flow)
j) Select the desired Shaping Type
GE114S/GE114SH do not support Flow Based Shaping Type for

PS
pass-through flows.
Note
N2N Settings
k) Enable/disable Auto Bandwidth (if Multi COS is disabled)
l) Enter the desired Auto CIR Bandwidth Percentage (if Auto Band-
width 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.
Figure 185: Create Pass-through Flow (Multi COS Enabled)

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.
o) Enter N2N Shaper settings (BS). If Multi-COS is Enabled, the
Shapers whose QIDs match to the Active Policers are editable.
VLAN Members
p) Enter a desired VLAN ID (or range) and Priority; then click on
Add. Repeat for each additional VLAN entry.
Click on OK.
Step 9 Select the Flows entity (under PT Flow) in the Selection Tree.
The newly created Pass-through flow Entity ID appears in the Details
Pane.
Step 10 Right click on the pass-through flow entity ID and select View Config-
uration.
Figure 186: Menu Selection to View Pass-through Flow

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

Figure 187: View Pass-through Flow Configuration Details
Step 12 Repeat Step 7 through Step 11 for each additional Pass-through Flow
for this node.
Step 13 Configure Ethernet Connectivity Fault Management (CFM) mainte-
nance endpoints (MEPs). Perform the procedure CFM Provisioning
and Operation on p. 502.
Configuring CFM MEPs for is optional, though recommended, for fast

failure detection and CFM monitoring in a ring environment. Set a ring
PS
port to be Down MEP facing the neighbor unit. This way the CFM
Note connectivity is established by pairs of MEPs facing each other.
Connectivity Fault Management (CFM) and line status messages

are used to detect ring link and node failure. During the recovery
phase, when the failed link is restored, the nodes adjacent to the
restored link send Ring Automatic Protection Switching (R-APS)
No Request (RAPS NR) messages. On obtaining this message,
PS
the ring protection link (RPL) owner blocks the RPL port and
sends R-APS NR and R-APS RPL (R-APS NR, RB) messages.
Note
These messages cause all other nodes, other than the RPL
owner in the ring, to unblock all blocked ports. The Ethernet Ring
Protection (ERP) protocol works for both unidirectional failure and
multiple link failure scenarios in a ring topology.

Step 14 Enter a right click on the ERP entity in the Selection Tree Pane and
select Edit. The following screen displays.
Figure 188: Edit ERP Configuration

Step 15 Select the desired MEP for Ring Port 0 and Ring Port1. Then click on
OK.
The ERP configuration changes are displayed in the Details Pane.
Figure 189: View ERP Configuration Details

Perform the following at Sites B, C, etc.

Step 16 Repeat the above steps at Sites B, C, etc.
Perform the following at Sites A, B, C, etc.
Step 17 Expand the System, Protection Groups, NE-1 entities in the Selection
Tree.
Step 18 Select the ERP entity and the RAPS Status tab to view the RAPS sta-
tus:
Figure 190: ERP RAPS Status View
Step 19 Observe the Node State. Refer to the following table describing the
three Node States.
The Node State should indicate Idle
Table 21: RAPS Status (Node State) Descriptions

Node State Definition
Protection A failure occurred on the ring. For normal node, traffic is blocked on the ring port that
connects to the failing link and unblocked on working ring ports. For the RPL owner,
traffic is unblocked on both ring ports if they connect to non-failure links. Node with
link failure should show Rx/Tx stats.
Idle No failure on the ring, the node is performing normally. For normal node, traffic is
unblocked on both ring ports. For the RPL owner or neighbor, traffic is blocked on the
ring port that connects to the RPL and unblocked on the other ring port.
Pending Not a participant of a specific ring. Nodes with link recovery should show Rx/Tx stats.

Step 20 If the Node State is not the expected result, troubleshoot and rectify
the trouble accordingly. Select the Statistics Tab to view ERP Statis-
tics to observe transmission and receive statistics. See the following
figure and table:
Figure 191: ERP Statistics View

Table 22: ERP Statistics

Node Role RAPS PDUs Comment
RPL Owner Always Transmitting, should not receive any Only One Owner is allowed
PDUs (When neighbor is configured). If RPL in a Ring
Neighbor does not exist then RAPS PDUs will
be received back and both Rx/Tx statistics will
indicate the number of PDUs.
RPL Neighbor Receives RAPS PDUs but does not forward to Adjacent link port of RPL
(Optional) Owner. Owner port.
Other Ring Always Receiving and a copy will be forwarded. Stats will only show received
Nodes PDUs.
Perform the following at each node location:

Step 21 Verify traffic connectivity between node sites.

Step 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.
An Operate Protection Switch window is displayed
Figure 192: Operate ERP Protection Switch
Step 23 Select Protection Switch Action of Manual and select the desired
Blocking Ring Port. Then select OK.
Step 24 Verify that the protection switch action did not introduce any
unwanted results.
Step 25 Enter a right click on the ERP entity and select Release Protection
Switch.
A Release Protection Switch window is displayed

Figure 193: Release ERP Protection Switch
Step 26 Select OK.
End of Procedure
Provision Management Tunnel(s)

Configure management tunnels on desired Access and/or Network ports by per-
forming Configure Management Tunnel on p. 418, as required.
If Low Touch Provisioning (LTP) is not used, delete the default LTP
PS
management tunnel.
Note

Provision Precision Time Protocol (PTP) (GE114S/GE114SH)
Provision Precision Time Protocol (PTP)

(GE114S/GE114SH)
The GE114S/GE114SH support PTP functionalities, including:
• Transparent Clock (TC)
• Telecom Slave (TS)
• Time Clock and add a Time Clock Reference
• Master Clock (MC) (only available in GE114SH)
• Boundary Clock (BC)
• Remote Slave (Static Slave or Dynamic Slave)
Up to 32 Transparent Clocks may be provisioned and one Telecom Slave may

be provisioned per system. Transparent Clocks are created in the following
order:
• Enable Software Licensing for PTP
• Create a flow on the associated port (must be in-service)
• Create a Transparent Clock
• Edit an Ethernet Port’s Delay Asymmetry setting
A single Telecom Slave may be created for the system. The Telecom Slave and
associated timing functions are created in the following order:
• Create a Telecom Slave
o
Create/Edit a Slave Only Ordinary Clock (SOOC)
o
Create/Edit a PTP Flow Point (PTP FP)
o
Create/Edit an Ordinary Clock Slave (OCS) Port
• Edit an Ethernet Port’s Delay Asymmetry setting
The TS, once provisioned and locked (the OCS Port State changes to Slave
state), may be:
• selected as a sync reference to the System Sync Domain (SYNC-1-1-1-1)
• selected as the Timing Source of Boundary Clock (These entities should be
disabled until the OC-S has achieved lock [OCS Port State=Slave].)
• selected as an output reference for the 10MHz Clock (CLK-1-1-1-1), PPS
(PPS-1-1-1-1), or Time of Day (TOD-1-1-1-1) output ports. (These outputs
should be disabled until the OC-S has achieved lock. The output should be
disabled if the OC-S state is not LOCKED or HOLD-OVER.)
• selected as the Source TOD Clock of System Time of Day (ToD)

A Master Clock and a Boundary Clock cannot co-exist. Either a single Master
Clock or a single Boundary Clock may be provisioned per system, wherein the
Master Clock feature is only available in GE114SH. The Boundary clock is cre-
ated in the following order:
• Enable Software Licensing for PTP and PTP-MC/BC
• Created a fully provisioned TS
• Create a Boundary Clock -- using TS as Timing Source
• Create/Edit a Master Clock Interface
• Create/Edit a PTP Flow Point (PTPFP)
• Create/Edit a Master Virtual Port
• Create/Edit a Static Slave or Edit/Delete a Dynamic Slave
The Master Clock is created in the following order:

• Enable Software Licensing for PTP-MC/BC
• Create a Master Clock -- using Time Clock as Timing Source
• Create/Edit a Master Clock Interface
• Create/Edit a PTP Flow Point (PTPFP)
• Create/Edit a Master Virtual Port

• Create/Edit a Static Slave or Edit/Delete a Dynamic Slave
The provisioning steps described in this section are performed using the PTP
application (located in the tool bar or selected via the Application menu) once
the licenses of this feature has been turned on.
Refer to PTP Configuration Options and Rules (GE114S/GE114SH) on p. 763
to determine the default values, value ranges and rules for each option in the
following procedure.
Procedure
DCN (eth0) Port Using the Serial Port on p. 402) and is logged on with at least a
Provisioning level user permission using eVision.
Enable Software Licensing for PTP and PTP-MC/BC

Step 1 Select the Maintenance Application on the tool bar or select Mainte-
nance 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.
Step 2 Enter a right click on Feature Management and select Edit Feature.
An Edit Feature Management screen displays

Figure 194: Edit Feature Management
Step 3 Select Enable Status by PTP and PTP-MC/BC and select OK.
The Feature Management Status is displayed and indicates they are
in Enabled state
Step 4 Determine the next step
Desired Function Then
Create a Transparent Clock? Go to Step 5.
Delete a Transparent Clock? Go to Step 14.
Create a Telecom Slave? Go to Step 18.
Edit Ethernet Port’s Delay Asymmetry? Go to Step 35
Add a Telecom Slave to a Sync Reference? See Add a Sync Reference
on p. 346.
Associate the Telecom Slave to the Clock Go to Step 39.
Output?
Associate the Telecom Slave to the PPS Go to Step 44.
Output?
Associate the Telecom Slave to the ToD Go to Step 49.
Output?
Associate the Telecom Slave to the System Go to Step 54.
ToD?
Create a Boundary Clock? Go to Step 59
Edit the Time Clock? Go to Step 76
Add a Time Clock Reference? Go to Step 81
Operate Reference Switch on Time Clock? Go to Step 86
Create a Master Clock? Go to Step 90
All PTP provisioning is completed? End of Procedure

Create a Transparent Clock

Prior to creating a Transparent Clock, the appropriate flow(s) for the
PS
Clock source(s) must already have been created and In Service, and
the Master Clock device has been provisioned and tested.
Note
Step 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 selec-
tion tree pane, by clicking on the “+” signs next to each entity to
expand each view.
Step 6 Enter a right click on the NE-1 entity and select Create Transparent
Clock.
A Create Transparent Clock window displays
Figure 195: Create Transparent Clock

Step 7 Enter the following Transparent Clock options:

a) Enter a unique TC ID and the desired Alias
b) Select the desired Administrative State
c) Enter the desired Clock Entity
d) Select the Flow Identifier associated with the clock source
e) Select the desired Delay Mechanism and enter the desired
Access and Network PTP Flow Point IDs.
f) Select OK.

Step 8 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.
Step 9 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 196: Network and Access Port PTP Flow Point in Selection Tree Pane
Step 10 Select the Configuration tab in the associated Transparent Clock
Ports and PTP flow points to view configuration details.
Step 11 Select the Statistics and Summary tabs for the associated PTP flow
points.
Current PTP statistics are displayed (see the next two figures)

Figure 197: Network Port PTP Flow Point Statistics
Figure 198: Access Port PTP Flow Point Statistics

Step 12 Repeat Step 5 through Step 11 for each Transparent Clock to be cre-
ated
Delete a Transparent Clock

Application Menu. Expand the System, NE-1 and TC entities in the

expand each view.
Step 15 Enter a right click on the TC-1-x entity and select Delete.
A Delete Transparent Clock window displays
Figure 199: Delete Transparent Clock
Step 16 Set the Administrative State to Management and select OK.
Create a Telecom Slave

Prior to creating a Telecom Slave, the appropriate flow(s) for the
PS
Clock source(s) must already have been created and In Service, and
the Master Clock device has been provisioned and tested.
Note
Application Menu. Expand the System and NE-1 entities in the selec-
tion tree pane, by clicking on the “+” signs next to each entity to
expand each view.
Step 19 Enter a right click on the NE-1 entity and select Create Telecom
Slave.
A Create Telecom Slave window displays

Figure 200: Create Telecom Slave

Step 20 Enter the following Telecom Slave options:

a) Enter the desired Alias and Clock Identity
c) Select the desired PTP Domain Number and Clock Recovery
Mode
d) Select the desired Time Holdover Accuracy
e) Select the desired Sync Reference control (If set to Enabled, the
TS port is available as a possible reference for the system Sync
object. If set to Disabled, the TS port is not available as a possible
reference for the system Sync object (SYNC-1-1-1-1). The sys-
tem Sync object may be used to drive PTP if this option is dis-
abled AND SYNC-1-1-1-1 is selected in the Sync ID option.)
f) Select the desired QL Mode, Sync ID, Assumed QL and Expected
QL options
g) Select OK.
A TS entity appears under the Ethernet Ports in the selection tree
pane
Step 21 Select the TS entity to view configuration details.
Create a Slave Only Ordinary Clock

Step 22 Enter a right click on the Telecom Slave (TS-1-1) entity and select
Create SOOC.
A Create Slave Only Ordinary Clock window displays

Figure 201: Create Slave Only Ordinary Clock
Step 23 Enter the following SOOC options:
a) Enter the desired Alias
c) Select the Identifier of the flow used for receiving PTP frames
d) Enter the Slave IP address and subnet mask
e) Enter an Interface Name (mandatory)
f) Enable/disable Unicast Message Negotiation
g) Enter the desired Unicast Timeout and Unicast Restart Timer
h) Select the desired Priority Mode and enter the desired Priority
i) Select the Master Delay Mechanism
j) Enter the Master Priority
k) Select the Master Protocol type and enter the Master Clock IP
Address
l) Select the desired Master Clock Message Rates/Duration options
m) Select OK.
An SOOC entity appears below the Telecom Slave entity in the selec-
tion tree pane
Step 24 Select the SOOC entity to view configuration details.

Create a PTP Flow Point

Step 25 Enter a right click on the Ethernet Port associated with the Flow for
the clock source and select Create PTPFP.
A Create PTP Flow Point screen displays
PTPFP cannot be created unless the Flow on the associated port is

PS
created and in In-service state. The Flow ID must be the same Flow
ID that was entered when creating a Slave Only Ordinary Clock.
Note
Figure 202: Create PTP Flow Point

Step 26 Enter the following PTP Flow Point options:

a) Enter the desired PTPFP ID and Alias
c) Select the desired PTP FlowPoint Type
d) Select the Flow Identifier associated with the clock source
e) Deselect the Untagged frame check box if Inner and/or Outer
VLAN tags need to be entered. Select the desired Inner/Outer
VLAN tag check box(es) to allow tag entry, then enter the desired
EtherType and VLAN Tag(s)
f) Select OK.
A PTP FLOW PT entity appears below the associated Ethernet Port
entity in the selection tree pane
Step 27 Select the PTP FLOW PT entity and the Configuration tab to view
configuration details.

Create an Ordinary Clock Slave Clock

Step 28 Enter a right click on the SOOC entity and select Create OCS Port.
A Create Ordinary Clock Slave Port screen displays
Figure 203: Create Ordinary Clock Slave Port
Step 29 Enter the following OCS Port options:

b) Select the PTP Flow Point associated with the clock source
c) Select OK.
An OCS PORT entity appears below the associated SOOC entity in
the selection tree pane
Step 30 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 Mas-
PS
ter Clock the Port State changes to Uncalibrated. When the system
Note determines it is able to calibrate time, then the Port State changes to
Slave (Locked).

Figure 204: OCS Port Configuration - Port State (Slave)
Step 31 Select the PTP Flow Point entity and Statistics tab to view PM data.
Ensure that messages are being received, otherwise troubleshoot
accordingly.
Figure 205: PTP Flow Point Statistics

Step 32 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.

Figure 206: SOOC Statistics Tab
Figure 207: SOOC Raw PTP Messages
Step 33 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.

Figure 208: OCS Port Configuration Status (Slave)
Edit an Ethernet Port’s Delay Asymmetry Setting

Application Menu. Expand the system, NE-1 and NTE entities in the
expand each view.

Step 36 Enter a right click on the Ethernet Port entity associated with the PTP
Flow Point and select Edit.
An Edit PTP Network or Access Port screen displays
Figure 209: Edit PTP Access Port Delay Asymmetry
Step 37 Enter the desired Delay Asymmetry value in nanoseconds and select
OK.

Associate the Telecom Slave to the 10 MHz Clock Output

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.
Step 39 Select the Configuration Application on the tool bar or select Configu-
ration from the Application Menu. Expand the System, NE-1, Syn-
chronization, NE-1 and NTE114Sx entities in the selection tree pane,
by clicking on the “+” signs next to each entity to expand each view.
Step 40 Enter a right click on the CLK-1-1-1-1 entity and select Edit Configura-
tion.
An Edit CLK-1-1-1-1 window displays
Figure 210: Edit CLK Interface Configuration
Step 41 Enter the following 10MHz Clock options:
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
Step 42 Select the CLK-1-1-1-1 entity to view configuration details.
Associate the Telecom Slave to the Pulse Per Second Output

the PPS Output.

chronization, NE-1 and NTE20x entities in the selection tree pane, by

clicking on the “+” signs next to each entity to expand each view.
Step 45 Enter a right click on the PPS-1-1-1-1 entity and select Edit Configu-
ration.
An Edit PPS-1-1-1-1 window displays
Figure 211: Edit PPS Interface Configuration

Step 46 Enter the following PPS options:

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
Step 47 Select the PPS-1-1-1-1 entity to view configuration details.
Associate the Telecom Slave to the TOD Clock Output

the TOD Clock Output.
chronization, NE-1 and NTE114Sx entities in the selection tree pane,
by clicking on the “+” signs next to each entity to expand each view.
Step 50 Enter a right click on the TOD-1-1-1-1 entity and select Edit Configu-
ration.
An Edit TOD-1-1-1-1 window displays

Figure 212: Edit Time of Day Interface Configuration
Step 51 Enter the following TOD options:

state
b) Select the desired Time of Day Source EID
c) Select the desired Squelch Control and Squelch QL options
d) Select OK
The Time-of-Day (TOD) output signal is capable of being sourced

from an active Telecom Slave’s recovered ToD. While the Telecom
PS
Slave is working in one-way recovery mode, the accuracy of ToD

Note timing cannot be guaranteed.
Step 52 Select the TOD-1-1-1-1 entity to view configuration details.

Associate the Telecom Slave to the System TOD

the System TOD.
ration from the Application Menu.
Step 55 Enter a right click on the System entity and select Edit System Time of
Day.
An Edit System Time of Day window displays

Figure 213: Edit System Time of Day (PTP Clock Method)
Step 56 Enter the following System TOD options:

a) Select PTP Clock for System Time of Day
b) Select TS-1-1 for the Source Time of Day Clock
c) Select OK
Step 57 Select the System Time of Day tab to view configuration details.
Select the Identification tab to view Date and Time.
Create a Boundary Clock

Clock (the OCS Port Status changes to Slave), it can serve as the timing source
of the Boundary Clock (BC).
Step 59 Select PTP in the tool bar or select PTP from the application menu.
Step 60 Expand the System entity and right click on NE-1 entity, then select
Create Boundary Clock.
The Create Boundary Clock screen appears
Figure 214: Create Boundary Clock

Step 61 Enter/Select the following Boundary Clock configuration options:

a) Enter the desired Boundary Clock Index and Alias
b) Select/Unselect the checkbox by Use Selected Telecom Slave
Clock Identity
c) Edit the Clock Identity as required if Use Selected Telecom Slave
Clock Entity is not selected
d) Selected the desired Administrative state
e) Selected the desired TS Identifier as Timing Source
f) Enter the desired PTP Domain Number
g) Click on OK
A PTP BC entity appears below the NTE entity in the Selection Tree
Pane
Step 62 Select the PTP BC-1-1 entity below NTE114x to view the BC configu-
ration.
Figure 215: Boundary Clock Configuration
Step 63 Enter a right click on the PTP BC-1-1 entity and select Edit to modify
the configuration of the BC as appropriate.
Create a Master Clock Interface

Step 64 Enter a right click on the PTP BC-1-1 entity and select Create Master
Clock Interface (MCI).
A Create Master Clock Interface screen appears

Figure 216: Create Master Clock Interface
Step 65 Enter/Select the following Master Clock Interface configuration

options:
a) Enter a desired Alias for the Master Clock Interface

b) Select the desired Administrative state
c) Select the IP Protocol and enter the corresponding IP Address,
Subnet Mask
d) Enter a desired Interface Name
e) Select a desired Priority Mode
f) Enter a desired Priority
g) Select the desired Clock Type (Only the popular one-step can be
selected)
h) Select the desired Delay Mechanism
i) Enter the desired number of Max Slaves Supported
j) Enter the desired number of Max Static Slaves Supported
k) Select the desired Rate for PTP frames and enter the Max Lease
Duration
l) Click on OK
A PTP MCI-1-1-1 entity followed by Static Slaves and Dynamic
Slaves entities below appears under the PTP BC-1-1 entity in the
Selection Tree Pane
Step 66 Enter a right click on the PTP MCI-1-1-1 entity and select Edit to mod-
ify the configuration of the Master Clock Interface below BC.

Create a Master Virtual Port

Step 67 Enter a right click on the PTP MCI-1-1-1 entity and select Create Mas-
ter Virtual Port.
A Create Master Virtual Port screen displays
Figure 217: Create Master Virtual Port
Step 68 Enter the following Master Virtual Port options:
a) Enter a desired Master Virtual Port Index and Alias
b) Select the desired PTP Flow Point
c) Select OK
A MASTER VIRTUAL PORT entity appears below the associated
MCI entity in the Selection Tree Pane
Step 69 Select the MASTER VIRTUAL PORT entity to view configuration
details. Enter a right click and select Edit to change the Alias as
needed.
Create/Edit a Static Slave

Step 70 Right click on Static Slaves to Create Static Slave if Max Static Slave
Supported is set to a value larger than 0 in MCI configuration (see
Step 65).
Step 71 Enter/select the following Static Remote Slave options:
a) Enter a desired Static Remote Slave Index and Alias
c) Enter the IP Address and select the desired control option for Uni-
cast Message Negotiation (if set to Enabled, the Message Rates
are not configurable; if set to Disabled, the Message Rates are
editable.)

d) Select the desired Rates for Announce Message, Sync Message

and Relay Response Message, if Unicast Message Negotiation is
set to Disabled.
e) Select OK.
A STATIC SLAVE entity appears below Static Slaves in the Selection
Tree Pane.
Step 72 Enter a right click on the static slave entity and select the desired
action from the menu: Edit, Delete, Init Registers, Edit Thresholds.
Edit/Delete a Dynamic Slave

Step 73 The learned DYNAMIC SLAVE entities, if any, will appear below the
Dynamic Slaves entity.
Step 74 Enter a right click on the DYNAMIC SLAVE entity and select the
desired operation from the menu.
Figure 218: Dynamic Slave Configuration and Selection Menu

Step 75 Click the Dynamic Slave entity and Statistics tab to view PM data.
Ensure the messages are being transmitted and received, otherwise
troubleshoot accordingly.

Figure 219: Dynamic Slave Statistics
Edit the Time Clock
Prior to creating a Master Clock, a Time Clock must first be

provisioned and In Service. The Time Clock is used to acquire an
PS
active time reference from the GPS signal input. Thus, it is required
that the Time Clock has GPS provisioned (see Edit GPS Port on
Note
p. 344) before all other associated provisioning.
ration from the Application Menu. Expand the System, Synchroniza-
tion, NE-1 and NTE114SH entities in the selection tree pane by
Step 77 Enter a right click on the Time Clock entity and select Edit Time
Clock.
An Edit Time Clock window appears

Figure 220: Edit Time Clock
Step 78 Enter/Select the following Time Clock options:


b) Set the Administrative state to IS
c) Enter the desired WTR Time
d) Select the desired Selection Mode, Time Holdover Performance,
Sync Reference Candidate and Expected QL options
e) Click on OK
Step 79 Select the Time Clock entity and select the Configuration tab to verify
the configuration entry.
Step 80 Continue with next step to add a Time Clock reference. Otherwise, go
to Step 4.
Add Time Clock Reference

ration from the Application Menu. Expand the System, Synchroniza-
tion, NE-1 and NTE114SH entities in the selection tree pane by
Step 82 Enter a right click on the Time Clock entity and select Add Time Clock
Reference.
An Add Time Clock Reference window appears

Figure 221: Add a Time Clock Reference
Step 83 Enter/Select the following Time Clock Reference options:

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
Step 84 Select the Time Clock entity and select the Status tab to verify refer-
ence configuration and status.
Figure 222: Time Clock Status

Operate Time Clock Reference Switch

Step 86 Select the Maintenance application. Expand the System, Synchroni-
zation, NE-1 and NTE114S/NET114SH entities in the Selection Tree
pane. Enter a right click on the TIME CLOCK-1-1-1-1 entity and select
Operate Reference Switch.
An Operate Reference Switch screen displays
Figure 223: Operate Reference Switch on Time Clock Entity

Step 87 Select the desired Request and Target for switch. Then click on OK.
Step 88 Select the Status tab in the Detail pane to check the state associated
with the Time Ref Eid which is just switched.
Figure 224: Time Reference State after Switch
Step 89 Go to Step 4

Create a Master Clock

GE114SH is the only product that supports Master Clock (MC) in PTP. The
steps to create a Master Clock are same as the steps to create a Boundary
Clock, except the different configuration options in Master Clock entity.
Step 90 Select PTP in the tool bar or select PTP from the application menu.
Step 91 Expand the System entity and right click on NE-1 entity, then select
Create Master Clock
The Create Master Clock screen appears
Figure 225: Create Master Clock
Step 92 Enter/select the following Master Clock options:
a) Enter a desired Master Clock Index and Alias.
b) Change Clock Identify as required.
c) Select the desired Administrative State.
d) Enter the desired PTP Domain Number, Priority 1 and Priority 2,
and select a desired Timing Clock Eid.
e) Select OK.
A PTP Master Clock entity appears below the NTE entity in the Selec-
tion Tree Pane
Step 93 Select the PTP MASTER CLOCK-1-1 entity to view the configuration.
Step 94 For the next provisioning steps, refer to Step 63 to Step 75.
End of Procedure

Provision Synchronous Ethernet (Sync-E)

(GE114S/GE114SH)
The GE114S/GE114SH support Sync-E functionality, including the Network
Ports, Access Ports and BITS IN/OUT. The following procedure provides the
steps necessary to configure Sync-E on the GE114S/GE114SH.
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 provision-
ing rules, see Synchronization (GE114S/GE114SH) on p. 630
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.
Steps in provisioning Sync-E and PTP:

• Edit System Sync Domain
• Provision BITS-IN/OUT
• Provision Telecom Slave

• Provision and Enable Sync-E on associated Ethernet Ports
• Provision CLK, PPS, TOD and GPS
• Provision and associate Time Domain on associated facilities
• Associate Sync Reference Sources (Sync-E Enabled Network Ports/Access
Ports, Telecom Slave and/or BITS-IN) to System Sync Domain
(SYNC-1-1-1-1) - Up to three per system
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 sup-
ports 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.
SFP (PN: 1061705878-01 SFP/DPI/GBE/850I/MM/LC/TIN) and SFP

PS
(PN: 1061705879-01 SFP/DPI/GBE/1310S/SM/LC/TIN) do not

support Sync-E functionality.
Note

Provision Synchronous Ethernet (Sync-E) (GE114S/GE114SH)
IP address and configured the NE to a DCN or LAN (see Set Up the FSP 150CC
Provisioning level user permissions using eVision.
All steps in the following procedure are performed in the Configuration Applica-
tion based on a GE114S product, which are also applicable to GE114SH.
Refer to Synchronization (GE114S/GE114SH) on p. 630 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

PS
this procedure. See Provision Access Port Services on p. 255 or Pro-

vision Network Ports on p. 285.
Note
Procedure
Step 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.

Configure System Sync Domain? Continue with the next step
Configure BITS-IN? Go to Step 6.
Configure BITS-OUT? Go to Step 10.
Configure the 10MHz Clock Port? Go to Step 14
Configure the PPS Port? Go to Step 18
Configure the TOD Port? Go to Step 22
Configure the GPS Port? Go to Step 26
Configure Sync-E for Network/Access Ports? Go to Step 30.
Add a Sync Reference? Go to Step 34.
Edit a Sync Reference? Go to Step 39.
Delete a Sync Reference? Go to Step 42.
Operate Reference Switch on System Sync Go to Step 45
Domain?
All Synchronization provisioning is completed? End of Procedure

Edit System Sync Domain

Step 3 Right click on SYNC-1-1-1-1 and select “Edit Sync”. The following
screen displays:
Figure 226: Edit System Sync

Step 4 Enter/select the following options for system sync:

a) Edit the Alias as desired
c) Select the desired Network Clock Type, enter desired WTR Time,
and select desired Selection Mode
Changing the Network Clock Type changes the options available for
Sync-E functions on BITS-IN, BITS-OUT, Access Ports and Network
PS
Ports. If any of these interfaces were previously configured for Sync-E

functions, the Assumed QL, Expected QL and Squelch QL settings
Note
revert to default values and have to be reconfigured.
d) Select OK
Edit BITS-IN
Step 6 Right click on BITS-IN and select Edit Configuration. The following
screen display.

Figure 227: Edit BITS-IN
Step 7 Enter/select the following BITS-IN options:
a) Enter a desired Alias
c) Select the desired configuration setting, starting from Line Type,
as the Line Type option changes Line Code, Frame Formate, SA
Bit and QL mode.
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
PS
set to a value other than None.

Note BITS will not show up as a potential synchronization reference if the
administration state is set to Unassigned
d) Click OK
Step 8 Select the BITS-IN entity to view configuration details.
Edit BITS-OUT
Step 10 Right click on BITS-OUT and select Edit Configuration. The following
screen displays:

Figure 228: Edit BITS-OUT
Step 11 Enter/select the following BITS-IN options:

a) Enter an Alias if desired.

b) Select the desired Administrative State.
c) Select the desired Configuration settings, starting with Line Type,
as the Line Type selection changes the options available for Line
Code, Frame Format, SA Bit, QL Mode and Line Build Out.
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
PS
setting, the BITS-OUT output will be suppressed.

Line Build Out is editable only when the Line Type is T1.
Note
As part of the Ethernet port Sync-E reference set up, the
Administration State should not be set to Unassigned.
d) Click OK
Step 12 Select the BITS-OUT entity to view configuration details.
Edit CLK Port

Step 14 Right click on CLK and select Edit Configuration. The following
screen displays.

Figure 229: Edit CLK Port
Step 15 Enter or select the following CLK options:

c) Select Signal Direction (Output only), Frequency Source Eid,
Squelch Control and Squelch QL (if Squelch QL is selected)
d) Click on OK
Step 16 Select the CLK-1-1-1-1 entity to view configuration details.
Edit PPS Port

Step 18 Enter a right click on the PPS port and select Edit Configuration. The
following screen displays.

Figure 230: Edit PPS Port
Step 19 Enter or select the following PPS options:

c) Select Signal Direction (Output only), Source Eid, Squelch Con-

trol, Squelch QL (if Squelch QL is selected), and enter Cable
Delay Compensation
d) Click on OK
Step 20 Select the PPS-1-1-1-1 entity to view configuration details.
Edit TOD Port

Step 22 Enter a right click on TOD port and select Edit Configuration. The fol-
lowing screen displays.

Figure 231: Edit TOD Port
Step 23 Enter or Select the following TOD options:

c) Select the desired Time of Day Source Eid, Squelch Control and
Squelch QL (if Squelch QL is selected)
d) Click on OK
Edit GPS Port

Step 26 Right click on GPS port and select Edit Configuration. The following
screen displays.
Figure 232: Edit GPS Port

Step 27 Enter or select the following GPS port options:

c) Select PPS generation condition and Antenna Cable Length
d) Click on OK
Edit Sync-E on a Network Port or Access Port

Step 30 Expand the NTE114S entity in the selection tree pane by clicking the
“+” next to it. Right click on the desired Network or Access Port and
select Edit Sync-E. The following screen displays:
Figure 233: Edit Sync-E on Ethernet Port (Access Port)

Step 31 Select the desired Configuration settings for Sync-E Mode, QL Mode,
Assumed QL and Expected QL.
If using SDH (Option-1), and QL Mode is disabled, an Assumed QL

PS
other than None must be selected.

Note
SFP (PN: 0061705890 SFP/GBE/ELECTRICAL/RJ45) connector

PS
resident Ethernet ports do not support Sync-E functionality.

Note
Step 32 Click on OK

Add a Sync Reference

Step 34 Expand the System, Synchronization, NE-1 and NTE114S entities in
the selection tree pane, by clicking on the “+” signs next to each entity
to expand each view.
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:
Figure 234: Add Sync Reference
Step 35 Enter/select the following options for sync reference:
a) Enter an Alias, if desired
b) Select the desired Priority value from the drop-down list.
c) Select the desired Sync Reference Source identifier from the
drop-down list
For Network and Access Ports to appear in the Sync Reference

Sources list they must be configured specific Configured Speed
corresponding to each Media Type. Sync-E cannot be enabled on
Copper 10 Full Mbps ports.
PS
Management Ports cannot be used as Timing reference.

Note For any interface to appear in the Sync Reference Sources list, it
must have Sync-E Mode enabled and the interface must not be
Unassigned.

SFP (PN: 1061705878-01 SFP/DPI/GBE/850I/MM/LC/TIN) and SFP
PS
(PN: 1061705879-01 SFP/DPI/GBE/1310S/SM/LC/TIN) cannot be
used as sync reference, or a Frequency Offset alarm will be raised.
Note
Click on OK
Step 36 Repeat Step 34 and Step 35 for each additional Sync entity.
Step 37 For Network Ports / Access Ports, Telecom Slave, BITS-IN: Select
the System Sync Domain entity (SYNC-1-1-1-1) and the Status tab.
The Synchronization Reference List appears, showing the status of
each Sync Reference Eid
Figure 235: Sync Reference List

Edit a Sync Reference

Right click on the System Sync Domain (SYNC-1-1-1-1) and select
Edit Sync Reference. The following screen displays:

Figure 236: Edit a Sync Reference
Step 40 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
Delete a Sync Reference

Right click on the System Sync Domain (SYNC-1-1-1-1) and select
Delete Sync Reference. The following screen displays:

Figure 237: Delete a Sync Reference
Step 43 Select the Radio Button for the Source to delete.

Click on OK.
Step 45 Select the Maintenance application. Expand the System, Synchroni-
zation, 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 Oper-
ate Reference Switch.
An Operate Reference Switch screen displays
Figure 238: Operate Reference Switch on System Sync Entity
Step 46 Select the desired Request and Target for switch. Then click on OK.
Step 47 Select the Status tab in the Detail pane to check the state associated
with the Sync Ref Eid which is just switched.

Figure 239: Sync Reference State after Switch
End of Procedure

Provision Link Layer Discovery Protocol

(LLDP)
LLDP is supported in all the GE11x products and the provisioning includes:
• Provision System LLDP, including LLDP frame settings, Max Neighbors
Action and Destination Address Configuration
• 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 on p. 713 to determine the default values,
value ranges and rules for each option in the following procedure.
Procedure
Provisioning level user permission using eVision.
ration via the application menu.
Provision System LLDP

Step 2 See Configure LLDP on p. 233
Once the system LLDP configuration is provisioned, go on next steps
to provision LLDP on traffic ports.
Provision Ethernet Port LLDP

Step 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.
Step 4 Enter a right click on the desired Ethernet port and select Edit LLDP.
Step 5 Enter a right click on the Access Port facility and select Edit LLDP.
An Edit LLDP window appears

Provision Link Layer Discovery Protocol (LLDP)
Figure 240: Edit Access Port LLDP View
The number of tabs displayed in the Details Pane is depended on the
Destination MAC Address types selected in Port configuration
provisioning. If more than one LLDP Destination MAC Address types
PS
have been selected, switching between different Destination MAC

Note tabs allows corresponding LLDP editing. The configuration options in
different tabs are same.
Step 6 Enter/Select the following data to configure LLDP settings for this
port:
Edit LLDP
a) Select the desired LLDP Admin Status for this port
b) Enable/Disable SNMP Notification
c) Select desired Basic Optional TLVs
Management Address Transmitted
Enter a right click under the Management ADDR table title and select
the desired operation from the selection menu. (see Figure 241 on
p. 353)
d) If add is selected, an ADD LLDP ACC PORT CONFIG tab will
appear next to the Management ADDR tab (see Figure 242 on
p. 353)
• Select the desired Management Interface and Enable/Dis-
able 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 242 on p. 353)
• Edit the Control option as desired.
• Click OK.
Figure 241: Provision Access Port LLDP Management Address View

Figure 242: Edit Access Port LLDP Management Address
f) To delete an existing management address, enter a right click on

it and Select Delete. Click on OK.

Provision Link Layer Discovery Protocol (LLDP)
Click on OK to save the LLDP configuration for this Destination MAC

Address.
Step 7 Repeat Step 6 to configure the LLDP for more Destination Addresses.
Step 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.
Figure 243: Port LLDP Configuration View
End of Procedure

Provision Environmental Alarms

(GE114H/GE114PH)
The GE114H/GE114PH provide 4 dry contact alarm inputs. These dry contact
alarm inputs are accessed via a RJ45 connector in the front of the unit. Up to 4
monitored devices can be connected to the 4 dry contact alarm inputs. The dry
contact alarm inputs are programmable to specify the monitored condition and
whether the alarm shall be raised on contact closed or open.
The following procedure assumes that the user has completed the physical
installation procedures in Physical Installation on p. 123, including installation of
the Environmental Alarm cable to the appropriate relays in the
GE114H/GE114PH 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 eVision
with the proper privilege level for provisioning (see User Authorization Privilege
Levels on p. 605).
Refer to Configuration Settings, Rules and Dependencies on p. 605 to deter-
mine the default values, value ranges and rules for each option in the following
procedure.
Procedure
Step 1 Select Maintenance View. Expand the System and Environmental

Alarms entities in the Selection Tree pane.
Step 2 Enter a right click on the desired Environmental Alarm input entity and
select Edit. The following screen displays.
Figure 244: Edit Environmental Alarm Input
Step 3 Select the desired options for: Alarm Type, Notification Code, Alarm
Input Mode and Alarm Hold Off
Enter the desired Alarm Description

Provision Performance Monitoring
Step 4 Select OK
End of Procedure
Provision Performance Monitoring

Database and Configuration Files

There are two different ways to manage database files on the FSP 150CC:
• ICF Configuration Files (binary) via eVision, SNMP and CLI
• CLI Configuration Files (text based) via SNMP, CLI and eVision
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 head-
ings ICF Configuration Files and CLI Configuration Files.
There is a third type of Database File supported by the FSP 150CC 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 down-
loaded 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 on p. 387.
If using Internet Explorer 8, in order to view certain eVision elements

correctly (namely data provided in Maintenance View - e.g., Restore
factory defaults, Restore system defaults, Restore database, New
PS
System Defaults File), enable Compatibility View in IE by selecting

Note Tools, Compatibility View Settings and adding the FSP 150CC IP
address to the list of websites data field.
ICF Configuration Files

The ICF (Implementation Configuration File) database files are binary copies of
the complete database and are not user editable. While the binary database
files can be managed using CLI or SNMP commands, the FSP 150CC provides
an easy means to manage the binary database files using the following configu-
ration database management functions via the eVision Web Browser:
• Create a Database Backup
• Restore Database
• Set a System Default Database
• Restore System Defaults
• Restore Factory Defaults

Determine Database Configuration Status

When the database of the FSP 150CC is modified, it stores the changes in
non-volatile memory. If a power loss / system reboot occurs, all configuration
data is retained. There are three versions of the database always resident on
the system, plus a “standby” copy of the current database. The three versions
are the current running configuration, a System Default that may be modified
and saved by a user, and a Factory Default that may not be modified. When first
commissioned, these three database copies are identical.
As provisioning occurs, the current running configuration database is updated
with each change entered. At some point, the user may determine that the cur-
rent copy should be the default database for this unit, at which time the user
should perform the Set a System Default Database procedure. Then, if required
the database can be restored to these settings by performing the Restore Sys-
tem Defaults procedure.
The Factory Default Database never changes, and as a last resort troubleshoot-
ing tool, or upon decommissioning, the current database can be reset to factory
defaults by performing the Restore Factory Defaults procedure. The Default
Database can also be reset to Factory Defaults using the “New” option in the Set
a System Default Database procedure. From a user’s perspective, there are
some major differences:
• Restore Factory Defaults delete all Configuration files; “New” option in the
Set a Default Database procedure doesn’t.

• Restore Factory Defaults deletes any Default-Value file created by the user.
“New” option in the Set a Default Database procedure doesn’t.
• Restore Factory Defaults erases all Log informations; “New” option in the
Set a Default Database procedure doesn’t.
• Restore Factory Defaults reset system time. “New” option in the Set a
Default Database procedure doesn’t.
• Restore Factory Defaults reset the data-structures in the database.
To view the configuration database information in eVision, select Maintenance
view, expand the Administration entity, and then select the Database entity (see
Figure 245 for an example of a default database configuration). The display
shows the current database version for both the active and standby partitions as
well as the status.
Figure 245: Database Status Display

Set a System Default Database

At the original commissioning of the unit, the Default Database and the Factory
Default Database are identical. At some point, it may be desirable to reset the
current database to something other than the Factory Defaults, especially if a
specific and complex management communications and/or remote access con-
figuration has been provisioned.
The FSP 150CC 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
eVision tool. It is also possible to perform this process using CLI. See the FSP
150CC-GE11x Command Line Interface Reference Guide for details. The fol-
lowing 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 FSP 150CC
Procedure
Step 1 Click on the Maintenance icon, or select “Maintenance” from the

Set the current database as the System Default Continue with the next
Database? step.
Copy the System Default Database to a remote Go to Step 5.
site?
Copy a Default Database from a remote site? Go to Step 10.
Reset the Default Database to Factory Go to Step 15.
Defaults?
Step 3 Expand “Administration”, right click on “Default Database” and select

“Save”.
The display is the Save Configuration to System Defaults view, shown
in the figure below.

Figure 246: Save Configuration to System Defaults View
Step 4 Click OK.
End of Procedure

“Copy To Remote”.
The display is the Copy To Remote, File Transmit Method view,
shown in the following figure.
Figure 247: Copy System Default Database To Remote - Web View
Desired File Transfer Method Then

Web (HTTP)? Continue with the next
step.
FTP, SFTP or SCP? Go to Step 8.

Step 7 Click on “OK”, then click on the underlined “here” for HTTP File Trans-
fer.
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 (backupdb.bin) to the user’s download folder.
A browser with File Download Prompting enabled and pop-up
PS
blocking enabled may not allow a transferred file to be successfully

downloaded to the system. With this configuration, the system logs
Note
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.
End of Procedure
drop-down list.
FTP and SFTP views are identical.)
Figure 248: Copy Database To Remote - SCP View
Step 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.

PS
Note
The file transfer will begin, and show a screen similar to the following
displays.
Figure 249: Transfer Progress Screen

When the “Status” changes from “Progress” to “Success”, the file has been
transferred.
End of Procedure
Step 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:

Figure 250: Copy Database From Remote - Web View

step.
Step 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.
End of Procedure
drop-down list.
shown in the following figure: (The figure shows the SCP view, the

Figure 251: Copy Database From Remote - SCP View
PS
and file name of the database file to transfer.
Note
The file transfer will begin, and show a screen similar to the following.
End of Procedure

“New”.
The display is the Save Configuration to System Defaults view, shown

Figure 253: New System Defaults View
Resetting the database to factory defaults will drop all traffic and
erase all communications and user settings, including the loss of the
eVision connection to the NE. When using the “New” option selection,
any user uploaded “Default Settings” will be erased. This operation
CAUTION should not be performed lightly. It may be advisable to backup the
current database so that it can be restored later.
Step 16 Click OK.

The System resets the Default Database and Active Database to Fac-
tory Defaults.
End of Procedure
Create a Database Backup

Backing up the system database is a two step process:
• First, the database has to be created at a temporary location on the NE.
• Second, the database file is transferred to a remote repository. The NE sup-
ports transfer via HTTPS (Web), FTP, SFTP and SCP protocols.
The following procedure includes steps for performing the database backup pro-
cess using the eVision tool. It is also possible to perform this process using CLI.
See the FSP 150CC-GE11x Command Line Interface Reference Guide for
NE with an IP address and connected the NE to a DCN or LAN (see Set Up the
FSP 150CC DCN (eth0) Port Using the Serial Port on p. 402) and is logged on
using eVision.

Procedure
Step 1 Click on the maintenance icon, or select “Maintenance” from the

Step 2 Expand “Administration”, right click on “Database” and select “Backup
Database”.
The display is the Backup Database view, shown in the figure below.
Figure 254: Backup Database View

Step 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:
Figure 255: Database Back Up Status View

Step 4 Right click on “Database” and select “Copy to Remote”.

The display is the Copy to Remote, File Transmit Method view, shown
Figure 256: Copy Database To Remote - Web View

step.
Step 6 Click on “OK”, then click on the underlined “here” for HTTP File Trans-
fer.
save the file.

default file name (backupdb.bin) to the computer desktop.
PS blocking enabled may not allow a transferred file to be successfully
Note
End of Procedure
drop-down list.
shown in the figure below. (The figure shows the SCP view, the FTP
and SFTP views are identical.)
Figure 257: Copy Database to Remote - SCP View
PS
Note

displays.
Step 9 When the “Status” changes from “In progress” to “Success”, the file
has been transferred.
End of Procedure
Restore Database
Restoring the database is a multi-step process:
• 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.
• Second, the database file must be transferred to standby memory on the
NE.
• Third, the database is activated, which causes the NE to reset and tempo-
rarily interrupt traffic and cancel active user sessions.
The following procedure includes steps for performing the database restore pro-
using eVision.

Procedure

Step 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:
Figure 259: Copy Database From Remote - Web View


step.
Step 4 Enter the path to the file to restore, or browse to the file location, then
click on “OK”.
drop-down list.

Figure 260: Copy Database From Remote - SCP View
PS
Note
The file transfer will begin, and show a screen similar to the following.
Step 8 When the “Status” changes from “Progress” to “Success”, right click
on “Database” in the selection tree pane and select “Restore Data-
base”. The following screen displays:

Figure 262: Restore Database Query
Step 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:
Figure 263: Activate Standby Database View

Step 10 To accept the restored database, click on OK.

Step 11 The NE will reboot.

If restoring a database taken from a different unit, (e.g. if replacing a

failed unit with another unit and restoring a database backup from the
first unit) the original unit’s SNMP engine ID (snmpEngineId) is
PS
preserved so the configured USM auth and priv keys remain valid. If
Note the snmpEngineId is edited, the USM auth and priv keys
automatically reset to “ChgMeNOW’ and need to be edited.
End of Procedure
Restore System Defaults

There are two types of database resets available on the FSP 150CC, Restore
System Defaults and Restore Factory Defaults. The difference between System
Defaults and Factory Defaults is explained in Determine Database Configura-
tion Status on p. 357.
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 only done only when a system is decommis-
sioned and moved to a new location or when the software or data-
base is corrupted. It is advisable to backup the database before
CAUTION performing this procedure.
This procedure is NOT part of original Provisioning procedures.
DCN (eth0) Port Using the Serial Port on p. 402) and is logged on using eVision
in Configuration view.
Procedure

application drop-down list. Right click on “Administration” in the selec-
tion tree pane and select “Restore System Defaults” and the following
screen displays:

Figure 264: Restore System Defaults
Resetting the database to system defaults may drop all traffic and
eVision connection to the NE. This operation should not be performed
lightly. It may be advisable to backup the current database so that it
CAUTION
can be restored later.
Step 2 To reset the current database to the system defaults, select OK.
A system warm reboot occurs.
End of Procedure

Restore Factory Defaults

There are two types of database resets available on the FSP 150CC, Restore
System Defaults and Restore Factory Defaults. The difference between System
Defaults and Factory Defaults is explained in Determine Database Configura-
tion Status on p. 357.
Restore Factory Defaults results in the loss of all Provisioning Data
Base settings including DCN, SNMP, Remote Access and User data.
This is normally only done only when a system is decommissioned
and moved to a new location or when the software or database is cor-
rupted. It is advisable to backup the database before performing this
procedure.
CAUTION
in Configuration view.
Procedure
application drop-down list. Right click on “Administration” in the selec-
tion tree pane and select “Restore Factory Defaults” and the following
screen displays:
Figure 265: Restore Factory Defaults
Resetting the database to factory defaults will drop all traffic and
eVision connection to the NE. This operation should not be performed
lightly. It may be advisable to backup the current database so that it
CAUTION
can be restored later.

Step 2 To reset the current database to the factory defaults, select OK.
End of Procedure
CLI Configuration Files

In addition to the ICF database files (see Database and Configuration Files on
p. 356), the system also supports text based configuration files based on the
output from the CLI command “show running config” (see FSP 150CC-GE11x
6.1 Command Line Interface Reference Guide and CLI Configuration File Man-
agement on p. 376). Since they are text based, they can be viewed and edited.
The system supports keeping up to four CLI configuration files in persistent
memory. These files can be created, deleted, loaded, marked for execution after
rebooting the system or copied to and/or from a remote server using FTP, SFTP
or SCP (file transfer protocols). They are mentioned here because they persist
in memory after a “Restore System Defaults”.
A “Restore Factory Defaults” deletes all configurations file along with

PS
all user configurations.

Note
The CLI Configuration File contain most configurations, but there some excep-
tions.
• Loopback Configurations
• Local user and SNMP USM user Configurations
• ESA Schedule Configurations
• Secret information for the Remote Authentication Server
CLI configuration files, when executed (Load function), modify the active data-
base one line item at a time. These files are managed using CLI commands,
eVision 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:
• Description
• List
• Load
• Remove
• Restart-with-configfile
• Save
• Show
• Transfer File

These commands are detailed at CLI Configuration File Management on p. 376.
CLI Configuration File Management

CLI configuration files are text files based on the CLI command “show run-
ning-config”. These files reflect the delta between the system default and active
database at the time they are created, and can be used to reconfigure the sys-
tem by running them manually or load them upon system resets. The user can
create and store up to four files on the system. While these files can not be
edited on the system, they can be exported, edited, 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
150CC-GE11x 6.1 Command Line Interface Reference Guide. Included here is
a procedure for dealing with CLI configuration files: CLI Configuration File Pro-
cedure on p. 380.
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.
ADVA:config-file--> show configfile configfile4
File Name : configfile4
Description :
Context : below
# DO NOT EDIT THIS LINE. FILE_TYPE=CONFIGURATION_FILE
#
#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 12.112.12.3 255.255.255.0 12.112.12.5 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
configure esa
add reflector esa_reflector-1-1-1-1 "ref1" access-1-1-1-5
121.12.0.5 255.255.255.0 dscp 1
#
#CLI:ESA REFLECTOR-1-1-1-2 Create
#
home
configure esa
add reflector esa_reflector-1-1-1-2 "ref2" access-1-1-1-4
123.12.12.12 255.255.255.0 tos 4
#
#CLI:CFM N2A PORT SHAPER-1-1-1-4-1 Edit
#
home
configure cfm
configure cfm-n2a-port-shaper access-1-1-1-4
cfm_n2a_port_shaper-1-1-1-4-1
cir 320000
buffersize 1
#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:
ADVA:config-file--> transfer-file <ftp,scp,sftp>
<get,put> <user-name> <password> <ipaddr>
<filename>
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:
ADVA:config-file--> restart-with-configfile
configfile4 yes
ADVA:config-file-->
U-Boot 2009.03-14408 (Jan 27 2012 - 14:21:19)

MPC83XX
The Restart-with-configfile command are similar to Load command

but they are different in the following aspects:
• The Restart-with-configfile command causes an NE reboot.The
Load command doesn’t.
PS
• The Restart-with-configfile command restores the NE to system
Note
default database. The Load command doesn’t.
• The Restart-with-configfile command applies the configuration
against system-default setting. The Load command applies con-
figuration against current setting.
Load
To run a configuration file now, use the “load” command, as in:
ADVA:config-file--> load configfile4
ADVA:config-file-->
Show
To view the contents of a configuration file, use the “show ConfigFile” command,
as in:
ADVA:config-file--> show configfile configfile4
File Name : configfile4
Description :
Context : below
# DO NOT EDIT THIS LINE.

FILE_TYPE=CONFIGURATION_FILE
#
#CLI:ACCESS PORT-1-1-1-6 Edit
#
home

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
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” com-
mand, as in:
description <configfile-name> <description>
The description can be up to 128 characters long, ASCII with no spaces (unless
in quotes) or question marks. Example:
ADVA:config-file--> description configfile4 "set access6 to EVPL
and create a flow"
|-------------------------|----------------------------------|
|configfile2 |psu and root
|configfile3 |
|configfile4 |set access6 to EVPL and create a flow
ADVA:config-file-->
Remove
To delete a configuration file, use the “remove” command, as in:
remove <configfile-name>
Example:
ADVA:config-file--> remove configfile2
|-------------------------|----------------------------------|
|configfile3 |
|configfile4 |set access6 to EVPL and create a flow
ADVA:config-file-->

Configuration File Procedures

Below are two procedures for working with Configuration Files. The first is
based on using CLI commands, which is the basis for Configuration Files. The
second details how to perform the same operations using eVision.
To support Fiber Service Platform Network Manager (FSPNM), GE11x also
allows to manage Configuration File with SNMP. For more information about
manging Configuration File, see FSP 150CC-GE11x 6.1 SNMP User Guide.
CLI Configuration File Procedure

The user should be logged on to a CLI session as a superuser, then have
entered “admin config-file” at the user prompt. See FSP 150CC-GE11x 6.1
Command Line Interface Reference Guide for details on CLI interface operation
and commands. Descriptions and examples of the commands referenced in this
procedure are given in CLI Configuration File Management on p. 376.
Procedure
Desired Operation Then
Create a new configuration file Continue with the next step.
Update an existing configuration file Go to Step 4.
List/check status of the configuration files Go to Step 6.
Reboot the system and execute a configuration file Go to Step 8.
Import/export a configuration file Go to Step 10.
Run (Load) a configuration file now Go to Step 12.
View the contents of a configuration file Go to Step 14.
Edit the description of a configuration file Go to Step 16.
Delete a configuration file Go to Step 18.
Done working with configuration files Go to Step 20.
Step 2 Enter the following command:

save <configfile-name>
Where “configfile-name” is 1 to 32 characters, no spaces or slashes
(/).
The configfile will contain the delta between the default database and
the current active database.

save <configfile-name>
Where “configfile-name” is an existing configfile.
The configfile will contain the delta between the default database and
the current active database and will overwrite the existing file.
list
restart-with-configfile <configfile-name> yes
Where “configfile-name” is the an existing configfile.
This will result in an immediate reboot of the system followed by an
execution of the designated configfile.
transfer-file <ftp,scp,sftp> <get,put> <user-name>
<password> <ipaddr> <filename>
This command uses the selected file transfer protocol to move a con-
figuration 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>
Where “configfile-name” is the an existing configfile.
show <configfile-name>
description <configfile-name> <description>
Where “configfile-name” is an existing configfile. The description can
be up to 128 characters long, ASCII with no spaces or question marks
(unless the text string is in quotes).
remove <configfile-name>

Step 20 If configuration changes were implemented using this procedure, ver-

ify the changes, then save the configuration using the Create a Data-
base Backup on p. 364 procedure.
End of Procedure
Configuration File Procedure - Using eVision

in Maintenance view.
Procedure
Create a new configuration file Continue with the next step.

Update an existing configuration file Go to Step 5.
List/check status of the configuration files Go to Step 8.
Edit the description of a configuration file Go to Step 10.
Reboot the system and execute a configuration file Go to Step 13.
Import a configuration file Go to Step 15.
Export a configuration file Go to Step 18.
Delete a configuration file Go to Step 21.
Done working with configuration files Go to Step 24.
Step 2 Right click on “Configuration Files” and select “Create”. The following
screen displays:

Figure 266: Configuration Files - Create
Step 3 Enter the desired File Name, 1 to 32 characters, no spaces or slashes

(/).
The configuration file will contain the delta between the default data-
base and the current active database.
Step 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:
Figure 267: Configuration Files - Update
Step 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.
Step 8 Select “Configuration Files”. The following screen displays:

Figure 268: Configuration Files - Display Status
The details pane shows a table of the existing configuration files

including the file name and description (if any).
Figure 269: Configuration Files - Edit Description
Step 11 Select “Edit Description”.

A text editing window opens. Enter the desired description, up to 127
ASCII characters and click on OK.

Figure 270: Configuration Files - Restart
Step 14 Select “Restart with File”.

The NID is rebooted, then the selected configfile is run.
End of Procedure
Step 15 Right click on “Configuration Files” and select “Copy From Remote”.
Figure 271: Configuration Files - Import
Step 16 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 user-
name, password, and configfile-name are required if using FTP,
SFTP or SCP protocols.

Figure 272: Configuration Files - Export
Step 19 Select “Copy to Remote”.
Follow the instructions in the detail pane to move the selected config-
uration file to the remote location using the selected transfer protocol.
Figure 273: Configuration Files - Remove
Step 22 Select “Remove”.

The selected configuration file is deleted.

Step 24 If configuration changes were implemented using this procedure, ver-
ify the changes, then save the configuration using the procedure Cre-
ate a Database Backup on p. 364.
End of Procedure
Default Settings Value File

If the user has determined that the default value settings applied when a new
entity is created are not applicable or unacceptable, an XML file containing
alternate settings can be downloaded and applied to the FSP 150CC using the
following procedure.
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 set-
tings. 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
CAUTION
erase any user defined Default Settings file.
The following procedure includes steps for performing applying a new Default
Settings file using the eVision tool. It is also possible to perform this process
using CLI. See the FSP 150CC-GE11x Command Line Interface Reference
Guide for details. The following procedure also assumes that the user has con-
figured the NE with an IP address and connected the NE to a DCN or LAN (see
Procedure

Step 2 Expand “Administration” and select “Default Settings”
The display is the Copy System Default Settings From Remote view,
shown in the following figure:

Figure 274: Copy System Default Settings From Remote - Web View

step.
Step 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 indi-
cates when the file transfer is 100% complete.
End of Procedure
drop-down list.
shown in the following figure: (The figure shows the SCP view, the

Figure 275: Copy System Default Settings From Remote - SCP View
PS
Note
The file transfer begins, and show a screen similar to the following
displays:
Step 7 When the “Status” changes from “Progress” to “Success”.
End of Procedure

Bulk Log Transfer

The Audit Log, Alarm Log and Security Log can be bulk transferred to a remote
repository. The NE supports transfer via HTTPS (Web), FTP, SFTP and SCP
protocols. Transferring the Security Log requires the user to have Superuser
access.
The following procedure includes steps for performing the bulk file transfer pro-
using eVision.
Procedure

Step 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.
Figure 277: Transfer Log View

step.
Step 4 Click on “OK”.

save the file.

default file name to the computer desktop.
PS blocking enabled may not allow a transferred file to be successfully
Note
End of Procedure
drop-down list.
Figure 278: Bulk Log Transfer - SCP View

PS
Note
displays.
Step 7 When the “Status” changes from “In Progress” to “Success”, the file
End of Procedure

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, cur-
rent 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 eVision tool. It is also possible to perform this process using
CLI. See the FSP 150CC-GE11x R6.1 Command Line Interface Reference
Guide for details. The following procedure also assumes that the user has con-
figured the NE with an IP address and connected the NE to a DCN or LAN (see
Procedure
Step 1 Click on the maintenance icon, or select Maintenance from the appli-
cation drop-down list.
Step 2 Expand Administration, right click on Diagnostics Files and select

Save in the Selection Tree pane.
A Save Diagnostics Files screen displays
Figure 280: Save Diagnostics File
Step 3 Click on OK.

A Transfer Diagnostics Files Progress screen displays, showing the
System Diagnostics File Save status

Figure 281: Diagnostics File Save in Progress
Step 4 When the Diagnostics File is saved successfully (see Figure 4),
Figure 282: Diagnostics File Save Success
Step 5 Click Diagnostics Files in Selection Tree pane to view the Status and
Date of Existing Diagnostics Files in the Detail pane.

Figure 283: View Diagnostics Files Status and Time Stamp
Step 6 Enter a right click on Diagnostics Files in Selection Tree pane and
select Copy to Remote.
A Transfer Diagnostics Files screen displays
Figure 284: Copy Diagnostics Files to Remote

step.

Step 8 Click on “OK”.

save the file.
default file name to the computer desktop.
PS
blocking enabled may not allow a transferred file to be successfully

Note
End of Procedure
drop-down list.
Figure 285: Diagnostics File Transfer - SCP View
SCP server and begin the file transfer process (See the following fig-
ure on how the required data for SCP transfer are correctly provi-
sioned.), and click on OK.

Figure 286: Diagnostics File Transfer - SCP Option Filled
The file transfer will begin, and show a screen as below
Figure 287: Diagnostics File Transfer Progress Screen

Step 11 When the “Status” changes from “In Progress” to “Success”, the file
End of Procedure
Test the FSP 150CC


398
Test the FSP 150CC

Chapter 5
Communications Provisioning
Introduction
This Chapter contains communications provisioning information and procedures
for the FSP 150CC-GE11x. An example scenario of GNE to SNE communica-
tions is provided along with provisioning details. This section contains the fol-
lowing communications procedures:

• Serial Connection on p. 402
• Set Up the FSP 150CC DCN (eth0) Port Using the Serial Port on p. 402
• Set Up the 3G Modem Using the Serial Port on p. 408
• Browser-based IP Connection on p. 411
• Edit DCN (eth0) Configuration on p. 412
• Configure Management Tunnel on p. 418
• Configure IPv6 over IPv4 Tunnel on p. 427
• Configure Source Address on p. 429
• Add/Delete Static Route on p. 431
• Add/Delete Static ARP Entry on p. 434
• Add/Delete IPv6 Static Route on p. 436
• Add/Delete IPv6 Static Neighbor Entry on p. 439
• Add/Delete IPv6 Static Proxy ND Entry on p. 442
• Configure Access Control List on p. 444
• Configure 3G Modem Using eVision on p. 444
• Sample Network - GNE to SNE over Management Tunnel on p. 454

Provision Communications
The FSP 150CC supports several management configurations and options.
This section does not provide typical deployment scenarios of the FSP 150CC
in common IP network configurations as there are simply too many different net-
work 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 network-
ing concepts.
The factory default settings for the FSP 150CC 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 Con-
figuration Files on p. 356) 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 Man-
agement Tunnels. This allows having only a single IP address for all manage-
ment 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 42 System Configuration
Settings on p. 619), management tunnels do not support provisioning for IP
Address, Subnet Mask, DHCP or RIP. Another system level option, Manage-
ment 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.
When bridging is disabled, existing http/https/telnet/ssh sessions are

unresponsive for up to 3 seconds
PS
When bridging is enabled, existing http/https/telnet/ssh sessions are

Note unresponsive for up to 10 seconds
Management Communication to the FSP 150CC

A connection can be made between a PC or laptop and the FSP 150CC man-
agement interface using Command Line Interface (CLI) on a direct local serial
link. However, to connect to the FSP 150CC from a remote DCN, connection
can also be made via a DCN network.
A valid IP address for the Management LAN Interface is required when connect-
ing via the DCN. Although the FSP 150CC is shipped with a default IP address

Chapter 5 Communications Provisioning
loaded (192.168.0.2 / 24), the default is the same for each unit. To ensure a reli-
able connection to the FSP 150CC, the IP address of the Management LAN
Interface should first be configured to a unique address compatible with the net-
work it is on. This is usually performed automatically by using DHCP or manu-
ally by making a serial connection to the FSP 150CC and performing IP
Configuration during installation. See Serial Connection on p. 402 for further
details.
Regarding examples shown:

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
PS
given in the Preface, Technical Support.

Note
It is outside of the scope of this document to describe the use of any
computer 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.
Regarding login user names and passwords:

The default password for access to the management interface is
ChgMeNOW. This password is used on first access to:
(a) the root, netadmin or user account
(b) an account which has been changed by an administrator
When logging in using the default password, a password change is
enforced. This minimizes possible exposure, restricts access to the
PS
system and thereby increases system security. See Configure Local

Note Users, on Page 4-247 for details on changing a password.
All account names and passwords are case sensitive.
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
150CC-GE11x Command Line Interface Reference Guide.
Procedure
To make a serial connection to the FSP 150CC, perform the following steps:
Step 1 Ensure that a physical serial connection from a PC or Laptop to the
FSP 150CC RS-232 connector has been established (see Serial Con-
sole Port Connection on p. 158).
Step 2 Start a serial terminal emulation program (e.g. Tera Term Web) to
establish a connection.
Step 3 Select the outgoing communication port.
Step 4 Set the communication settings of the terminal emulation program to
the following:
• 9600 baud
• 8 data bits
• no parity bit
• 1 stop bit
• No flow control
Step 5 Save these settings for future use.
The following Login prompt should be displayed:
Login:
Step 6 Login with the following details:
• Account name - root (or as appropriate, see Provision Secure
Access on p. 242)
• Password - ChgMeNOW (or as appropriate).
A Security Banner displays on the screen.
Step 7 Enter “Y” to continue.
The following prompt is displayed:
ADVA-->
End of Procedure
Set Up the FSP 150CC DCN (eth0) Port Using the

Serial Port
The following procedure assumes that the Ethernet cable connecting MGMT
LAN to the DCN network has not been installed yet. (If there is no DCN con-
nected and only a 3G DCN will be provided for this GE11x, refer to Set Up the
3G Modem Using the Serial Port on p. 408 to provision the 3G DCN USB port
using CLI commands.)
Perform the following procedure to set up the FSP 150CC DCN (eth0) port
(MGMT LAN) using the RS-232 Serial Port on the FSP 150CC (RS 232) and the

CLI command structure. (For more information on the CLI command structure,
see the FSP 150CC-GE11x Command Line Interface Reference Guide.)
You will need the following items for this procedure:
• PC with a serial communications port (e.g., COM1 or COM2)
• 2 Category 5 LAN Cables (with RJ-45 connectors)
• DB-9 to RJ-45 converter (ADVA Optical Networking PN 2036904035-01 or
1036904035, see Table 13 RJ-45 (RS-232 Serial Console Port) and DB9
Adapter Pin Assignments on p. 184)
• A communications program, like TeraTerm Pro Web (a free software termi-
nal emulator for MS-Windows)
• An Internet browser [e.g. Internet Explorer 5.0 or greater (IE 8.0 recom-
mended) or Firefox 2.0 or greater (Firefox 3.6 recommended), etc.] This
procedure is intended to be used during the commissioning process or used
as a stand-alone procedure.
This procedure is intended to be used during the commissioning process or
used as a stand-alone procedure.
The default DHCP setting for the FSP 150CC DCN port is disabled and as a
DHCP client.
This procedure is offered as the best way to set up the FSP 150CC 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 dis-
abled 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.
Procedure
Step 1 Connect a serial cable between the FSP 150CC RS-232 Serial Port
and a PC and logon using procedure: Serial Connection on p. 402.
Step 2 Enter the show ip-interface eth0 command to view the current DHCP
setting for the DCN interface on the FSP 150CC. See the following
example:
ADVA--> show ip-interface eth0
Name : eth0
IP Address : 0.0.0.0
Netmask : 255.255.255.255
DHCP Role : dhcp-client
DHCP : enabled
DHCP Client ID : FSP150CC-GE114
RIPv2 : disabled
MTU (bytes) : 1500
MAC Address : 00:80:ea:02:62:01
System Default Gateway : 0.0.0.0

Current Status Then

Is the eth0 port DHCP status set to the desired Go to Step 7.
state of Disabled?
state of Enabled?
Does the eth0 port DHCP setting need to be Continue with the next
changed? step.
Step 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:
ADVA--> configure communication
ADVA:comms--> configure eth0 dhcp-control enabled
ADVA:comms-->
Step 5 Enter the show eth0 command to verify the changes.
Current Status Then

state of Disabled?
state of Enabled?
Step 7 Enter the configure communication command. A next level prompt

will appear. For example:
ADVA:comms-->
Usually, the IP address and network mask information is supplied by

PS
the network administrator.

Note
Step 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:
ADVA:comms--> configure eth0 ip-address
172.17.11.33 255.255.255.0 172.17.11.1
ADVA:comms-->
Step 9 Enter the show eth0 command to view the current IP address and net-
work mask setting for the DCN interface on the GE11x. See the fol-
lowing example:
ADVA:comms--> show eth0
Name : eth0
IP Address : 172.17.11.33
Netmask : 255.255.255.0


DHCP : disabled
RIPv2 : disabled
MTU (bytes) : 1500
Physical Address : 00:80:ea:02:62:01
Current Status Then

Is the IP address and mask wrong? Go to Step 8.
Is the IP address and mask correct? Proceed to the next step.
Step 11 Enter the show system command and verify that HTTP and HTTPS
are enabled.
Current Status Then

Are both HTTP and HTTPS enabled? Go to Step 15.
Is HTTP and/or HTTPS disabled? Proceed to the next step.
Step 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
Step 15 Use an Ethernet cable to connect the MGMT LAN RJ-45 connector to
the network DCN.
Step 16 Open a browser window and use the configured IP address to access
the NE.
Current Status Then

Did a login screen display? Proceed to the next step.
Did the connection to the NE fail? Check that you entered the IP
address correctly, that the PC
is connected to the network
DCN and has a valid IP
address itself, that the NE is
connected to the network DCN
and that the NE’s IP address is
set correctly. If necessary,
return to Step 2.

Step 18 Enter a valid login User ID and Password. The default login and pass-
word are ‘root’ and ‘ChgMeNOW,’ respectively. The security banner
will then be displayed.
Step 19 Click on the “Continue” button, and a display similar to the following
will appear.
Figure 288: eVision System View
Step 20 From the “File” menu, select “Logout”, and verify that the browser
shows the Login screen.
Step 21 Return to the serial port session and logoff by entering quit. See the
following example
ADVA:comms--> quit
Logged Out
Login:
Step 22 Disconnect the serial cable from the RS 232 connector on the FSP
150CC.
End of Procedure
Step 23 Use an Ethernet cable to connect the MGMT LAN RJ-45 connector to
the network DCN.
Step 24 Enter the show ip-interface eth0 command to view the current DHCP
setting for the DCN interface on the FSP 150CC. See the following
example:
ADVA--> show eth0
Name : eth0
IP Address : 172.17.11.33

Netmask : 255.255.255.0
DHCP : enabled
RIPv2 : disabled
MTU (bytes) : 1500
Physical Address : 00:80:ea:02:62:01
Current Status Then

Is the IP address something other than Proceed to the next step.
0.0.0.0?
Is the IP address still 0.0.0.0? Wait a one minute, then retry Step
24. If after 4 attempts, the IP
address still does not appear,
contact your System
Administrator. When an IP
address other than 0.0.0.0 is
present, proceed to the next step.
Step 26 Enter the show system command and verify that HTTP and HTTPS
are enabled.
Current Status Then

Are both HTTP and HTTPS enabled? Go to Step 30.
Is HTTP and/or HTTPS disabled? Proceed to the next step.
Step 28 Enter the following highlighted CLI commands to enable both HTTP
and HTTPS.
ADVA:comms--> home
ADVA:system--> http enabled
ADVA:system--> https enabled
Step 30 Open a browser window and use the configured IP address to access
the NE.

Current Status Then

Did a login screen display? Proceed to the next step.
Did the connection to the NE fail? Check that you entered the IP
address correctly, that the PC is
connected to the network DCN
and has a valid IP address itself,
that the NE is connected to the
network DCN and that the NE’s IP
address is correct. If necessary,
return to Step 24.
Step 32 Enter a valid login User ID and Password. The default login and pass-
word are ‘root’ and ‘ChgMeNOW,’ respectively. The warning banner
will then be displayed.
Step 33 Click on the “Continue” button, and a display similar to Figure 288
appears.
Step 34 From the “File” menu, select “Logout”, and verify that the browser
shows the Login screen.
Step 35 Return to the serial port session and logoff by entering quit. See the
following example
ADVA:comms--> quit
Logged Out
login:
Step 36 Disconnect the serial cable from the RS 232 connector on the FSP
150CC.
End of Procedure
Set Up the 3G Modem Using the Serial Port

The following procedure assumes that the 3G modem has been installed, either
directly into the USB port or through a USB cable (if required). (Use this proce-
dure 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.)
Perform the following procedure to set up the 3G modem port using the RS-232
Serial Port on the FSP 150CC (RS 232) and the CLI command structure. (For
more information on the CLI command structure, see the FSP 150CC-GE11x
Command Line Interface Reference Guide.)
You will need the following items for this procedure:
• PC with a serial communications port (e.g., COM1 or COM2)
• 2 Category 5 LAN Cables (with RJ-45 connectors)

• DB-9 to RJ-45 converter (ADVA Optical Networking PN 2036904035-01 or

1036904035, see Table 13 RJ-45 (RS-232 Serial Console Port) and DB9
Adapter Pin Assignments on p. 184)
• A communications program, like TeraTerm Pro Web (a free software termi-
nal emulator for MS-Windows)
• An Internet browser [e.g. Internet Explorer 5.0 or greater (IE 8.0 recom-
mended) or Firefox 2.0 or greater (Firefox 3.6 recommended), etc.] This
procedure is intended to be used during the commissioning process or used
as a stand-alone procedure.
• An ADVA Optical Networking qualified 3G modem, ZTEMT 119 or HW
E1750
This procedure is intended to be used during the commissioning process or
used as a stand-alone procedure.
The default DHCP setting for the FSP 150CC 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 3G modem gets into in-service state and connects itself to
the local 3G wireless network with the credential provided. Please consult the
FSP 150CC-GE11x Command Line Interface Reference Guide for the details
for running each command.
Procedure
Step 1 Connect a serial cable between the FSP 150CC RS-232 Serial Port
and a PC and logon using procedure: Serial Connection on p. 402.
Step 2 Navigated to the 3G Modem Command Level.
ADVA--> network-element ne-1
ADVA-NE-1--> configure nte nte114-1-1-1
ADVA-NE-1:nte114-1-1-1--> configure usb
ADVA-NE-1:3g_dcn-1-1-1-1-->
Set a wireless connection with a PIN-authentication enabled Continue with the next step.
3G Modem
Set a wireless connection with a PIN-authentication disabled Go to Step 5.
3G Modem.
Disable Pin Authentication Go to Step 14.
Unlock the SIM card Go to Step 16.
Change the PIN Go to Step 18.
Step 4 Run pin-authenticaition command to get authenticated.

ADVA-NE-1:3g_dcn-1-1-1-1--> pin-authentication ****

Step 5 Run dial-number command to enter the Wireless Access Number.

ADVA-NE-1:3g_dcn-1-1-1-1--> dial-number
(650)2222222
ADVA-NE-1:3g_dcn-1-1-1-1-->
Step 6 Run user-name command to enter the user name for wireless con-
nection.
ADVA-NE-1:3g_dcn-1-1-1-1--> user-name "tommy J"
ADVA-NE-1:3g_dcn-1-1-1-1-->
Step 7 Run password command to enter the password for wireless connec-
tion.
ADVA-NE-1:3g_dcn-1-1-1-1-->password ***********
ADVA-NE-1:3g_dcn-1-1-1-1-->
Step 8 Run admin-state command to transfer the 3G Modem to in-service
state.
ADVA-NE-1:3g_dcn-1-1-1-1--> admin-state in-service
ADVA-NE-1:3g_dcn-1-1-1-1-->
Step 9 Navigated to the Communication level and ran show 3g-dcn com-
mand. If the 3G port has obtained an IP address, the wireless connec-
tion is ready.
ADVA-NE-1:3g_dcn-1-1-1-1--> home
ADVA:comms--> configure 3g-dcn
ADVA:comms:3g-dcn--> show 3g-dcn
MTU : 1500
IP Address : 172.21.66.94
Subnet Mask : 255.255.255.255
Primary DNS : 210.21.196.6
Secondary DNS : 221.5.88.88
Step 10 Connect to the device with the IP address on CLI, SNMP or GUI.
Step 12 Run enable-pin command to enable pin authentication. once pin
authentication is enabled, user has to run pin-aunthenticaion to
access the 3G Modem.
ADVA-NE-1:3g_dcn-1-1-1-1--> enable-pin ****
Step 14 Run disable-pin command to disable pin authentication. once pin
authentication is disabled, the user doesn’t have to run
pin-aunthenticaion to access the 3G Modem.
ADVA-NE-1:3g_dcn-1-1-1-1--> enable-pin ****
Step 16 Run unlock-pin command to unlock the SIM and set a New PIN. This
command must be ran in the cases where the PIN has been mistak-
enly entered 3 times.
ADVA-NE-1:3g_dcn-1-1-1-1--> unlock-pin ******* ****
****

ADVA-NE-1:3g_dcn-1-1-1-1-->
Step 18 Change the PIN
ADVA-NE-1:3g_dcn-1-1-1-1--> change-pin **** ****
****
End of Procedure
Browser-based IP Connection
This procedure details the steps used to access a web-accessible FSP 150CC
(HTTP and/or HTTPS enabled) using a web browser on a PC with connectivity
to the DCN or 3G modem the FSP 150CC is connected to.
To ensure a reliable connection to a FSP 150CC over an Ethernet

DCN network, the IP address of the FSP 150CC’s Management
PS
Interface should be configured to a unique address compatible with

Note the network it is to be present on.
Procedure
To make an Ethernet DCN connection to the FSP 150CC, perform the following
steps:
Step 1 Ensure that a unique IP address has been configured for the FSP
150CC’s Management Interface or 3G modem, See Set Up the FSP
150CC DCN (eth0) Port Using the Serial Port on p. 402 or Set Up the
3G Modem Using the Serial Port on p. 408.
Step 2 Ensure that a physical Ethernet connection from the DCN PC to the
FSP 150CC has been established or the 3G modem is provisioned
and operational.
Step 3 Verify the user’s PC IP address and netmask match the values pro-
vided by the Network Administrator, so that it has access to the net-
work the FSP 150CC is on.
Step 4 Establish a connection to the FSP 150CC Management Interface or
3G modem via an Internet browser (Internet Explorer 5.0 or greater

(IE 8.0 recommended) or Firefox 2.0 or greater (Firefox 3.6 recom-

mended) by performing the following:
a) Open up the appropriate Internet browser and enter the following
address:
http://xxx.xxx.xxx.xxx
or
https://xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the FSP 150CC
to be connected to. This will be the IP address that has been
assigned to the FSP 150CC during initial IP configuration (if none
has been set, the default address is 192.168.0.2).
The Web Interface will open and the Login Screen will be dis-
played.
b) Login with the following details:
• Account name - root (or as appropriate, see Provision
Secure Access, on Page 4-242).
• Password - ChgMeNOW (or as appropriate).
Security details will also be displayed on the screen.
c) Press Continue.
The Web Interface FSP 150CC Main Menu will be displayed, as
described in Chapter 3, eVision Web Browser Management Tool
on p. 189.
Commands from the Internet browser are authenticated by a ‘per-ses-

sion cookie’ (i.e., a cookie that is not stored permanently). If a login to
PS
the Web Interface is not possible, check that the INTERNET browser
Note is configured to accept such cookies.
End of Procedure
Edit DCN (eth0) Configuration

The Management LAN Interface, with IPv4 and IPv6 modes both supported, can
be configured as a DHCP Server, as a DHCP Client, or have DHCP functionality
disabled in either IP mode. If DHCP Client mode is not used, the IP Address and
Netmask can be edited. Additionally, RIPv2/RIPng functionality can be enabled
or disabled. This procedure covers editing the DCN options.
The factory default settings are with the DHCP (v4 & v6) disabled in the client
role with RIPv2/RIPng disabled.

IP address and connected the NE to a DCN or LAN. (See Set Up the FSP
150CC DCN (eth0) Port Using the Serial Port on p. 402) and is logged on using
eVision. For more information on the configuration settings and rules, see DCN
(eth0) (Edit Configuration) on p. 640.
From the Configuration view with the Communications tree expanded:
Procedure
Step 1 Right click on “DCN (eth0)” and select Edit Configuration. The follow-
ing “Edit DCN (eth0)” screen displays.
Figure 289: Edit DCN (eth0)

Step 2 Select IP Mode - IPv4 only, IPv6 only or IPv4 and IPv6.

Set up DCN as a DHCP Server? Continue with the next
step.
Configure DCN as a DHCP Client? Go to Step 7.
Disable DHCP functionality? Go to Step 10.
Configure RIPv2/RIPng? Go to Step 13.
Manually Configure IP Address and Netmask? Go to Step 15.
Provisioning complete? End of Procedure

Step 4 Perform the following settings if IPv4 is a selected IP Mode:

Select DHCP - Enabled
Select DHCP Role - DHCP Server
Enter the desired IP Address
Enter the desired Netmask
The range of the Netmask entered determines the number of IP

PS
Addresses available for this server to assign.

Note
Enable/Disable RIPv2
Click on OK
In order for the new IP Address and DHCP server function (IP
PS
Address range) to become active, DHCP Control must be cycled.

Note
Select DHCPv6 - Enabled
Select DHCPv6 Role - DHCP Server
Enter the desired IPv6 Unicast Address
Enable/Disable RIPng
Enable/Disable IPv6 RA Prefix Enabled
Enter the desired IPv6 RA Prefix if IPv6 RA Prefix Enabled is Enabled
Select the checkbox next to Edit System Default and Enter the Gate-
way IPv6 Address
Click on OK
Step 6 Go to Step 3
End of Procedure

Select DHCP - Enabled
Select DHCP Role - DHCP Client
Select/Enter the following DHCP options that are only applicable in
IPv4 mode:
a) Enable/Disable DHCP Client ID Control
b) Select (if desired) DHCP Client ID Type (only available if DHCP
Client ID Control is Enabled)

c) Edit (if desired) DHCP Client ID (only available if DHCP Client ID

Control is Enabled and User Defined is selected as DHCP Client
ID Type)
d) Enable/Disable DHCP Class ID Control
e) Enable/Disable DHCP Host Name Control
f) Select (if desired) DHCP Host Name Type (only available if
DHCP Host Name Control is Enabled)
g) Edit (if desired) DHCP Host Name (only available if DHCP Host
Name Control is Enabled)
h) Enable/Disable DHCP Log Server Control
i) Enable/Disable NTP Server Control
Select DHCPv6 - Enabled
Select DHCPv6 Role - DHCP Client
Enable/Disable Stateless Address Auto Configuration
Enable/Disable IPv6 RA Prefix (RA Prefix cannot be enabled while
Select the Edit System Default checkbox if desired, and enter the
desired Gateway IPv6 Address

Click on OK

Figure 290: Edit DCN - DHCP Enabled Client Role
Step 9 Go to Step 3
End of Procedure
Step 10 Select/Enter the following options if IPv4 is a selected IP Mode:

Select DHCP - Disabled
Enter the desired IPv4 Address
Enter the desired Netmask
Select the Edit System Default Gateway checkbox if desired, and
enter the desired Gateway IPv4 Address

Step 11 Select/Enter the following options if IPv6 is a selected IP mode:

Select DHCPv6 - Disabled
Enter the desired IPv6 Unicast Address if Stateless Address Auto
Configuration is Disabled
Enable/Disable IPv6 RA Prefix Enabled (System will automatically set
it to Disabled if Stateless Address Auto Configuration is Enabled).
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
End of Procedure
Step 13 Select the desired RIPv2/RIPng setting

Click on OK
End of Procedure
Step 15 Select DHCP - Disabled

Enter the desired IP Address for selected IP mode
Enter the desired Netmask if IPv4 is included in selected IP mode
Prior to entering an IPv6 Unicast Address, Stateless Address Auto

PS
Configuration and DHCPv6 should both be Disabled.

Note
Select the desired RIPv2/RIPng setting

Click on OK
End of Procedure

Configure Management Tunnel

The FSP 150CC supports the configuration of a single management tunnel on
each Network or Access interface port or LAG group, and up to 2 management
tunnels are supported at one time. The tunnel mode supported includes VLAN
Based, MAC Based and ITag Based, wherein ITAG Based mode is not applica-
ble to GE114S/GE114SH, and is only supported on Network Port management
tunnel. The FSP 150CC supports management tunnels that use Ethernet or
PPP encapsulation. PPP can only be used with ADVA Optical Networking NIDs
that are directly connected and not using Management Traffic Bridging (imple-
ments an Ethernet Bridge between the eth0 and all configured Management
Tunnels, allowing a single IP address for all management interfaces on the sys-
tem and eliminates the need for static routes, routing protocols or proxy ARP in
an SNE/GNE configuration and supports MAC learning and flooding of
un-learned MAC addresses).
eVision.
From the Configuration view with the Communications and Management Tun-
nels entities expanded:
Procedure
Management Traffic Bridging Enabled? Then

No Continue with the next
step.
Yes Go to Step 9.
If Management Traffic Bridging is desired, it must first be enabled at

PS
the System level. See Configure System on p. 228.

Note

Create a management tunnel? Continue with the next
step.
Display a management tunnel? Go to Step 5.
Edit a management tunnel? Go to Step 293.
Delete a management tunnel? Go to Step 8.
Provisioning complete? End of Procedure.

Step 3 Right click on “NE-1” in the selection tree pane under “Management
Tunnels”, select Create Tunnel and the following screen displays:
Figure 291: Create Management Tunnel

Step 4 Enter/select the following data to configure the management tunnel:

(see Management Tunnel Configuration Options and Rules on p. 701
for details on each item.)
Identification
Management Tunnel Index - integer from 1 to 255
Management Tunnel Name - 1 to 15 alphanumeric characters
Associated Port - select from drop-down list - only one tunnel per port
Interface
Encapsulation Type - Ethernet or PPP
IP Mode - IPv4 Only, IPv6 Only or IPv4 and IPv6
IPv4 Networking
DHCP - Enabled/Disabled - default is Disabled (not applicable for
PPP)
Enable/Disable DHCP Client ID Control (not applicable for PPP)
Select a desired Client ID Type (only available if DHCP Client ID Con-
trol is Enabled) (not applicable for PPP)
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)

Enable/Disable DHCP Class ID Control (not applicable for PPP)

Enable/Disable DHCP Host Name Control (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.
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)
IPv4 System Default Gateway (not applicable for PPP)
Select the checkbox next to Edit System Default Gateway if DHCP is
disabled.
Enter a desired Gateway IPv4 Address if Edit System Default Gate-
way is checked.
IPv6 Networking
DHCPv6 - Enabled/Disabled - default is Disabled (not applicable for
PPP)
Enable/Disable Stateless Address Auto Configuration (not applicable
for PPP)
Enable/Disable IPv6 RA Prefix Enabled (not applicable for PPP)
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)
IPv6 System Default Gateway (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 Dis-
abled
Enter a desired Gateway IPv6 Address if Edit System Default Gate-
way is checked.
Layer 2 Configuration
Tunnel Mode - Select from VLAN Based, Mac-based, and
I-Tag-based. (I-Tag-based is only supported on Network Port)
C-TAG VLAN Enabled/Disabled
C-TAG VLAN Id - 1 to 4095 - default is 4095
I-TAG - Enabled/Disabled (only applicable when the Tunnel Mode is
set to I-Tag-based)
I-SID - 256 - 16777214. (only applicable when the Tunnel Mode is set
to I-Tag-based)
S-Tag VLAN - Enabled/Disabled - default is Disabled

S-Tag VLAN Id - 1 to 4095 - default is 4095 (only applicable if S-Tag

VLAN is Enabled)
Destination Backbone MAC- Enabled/Disabled (only applicable when
the Tunnel Mode is set to I-Tag-based)
Backbone MAC Destination Address. A valid MAC address. (only
applicable when the Tunnel Mode is set to I-Tag-based)
IPv4 RIP
RIPv2 - Enabled/Disabled - default is Disabled (not applicable for
PPP)
IPv6 RIP
RIPng - Enabled/Disabled - default is Disabled (not applicable for
PPP)
Bandwidth
CIR - 64000 to 8000000 bps - default is 256000 bps (Max of 8 Mbps
for all management tunnels combined)
EIR - 0 to 80000000 bps - default is 768000 bps
Buffer Size - 32 to 15000 KB - default is 32 KB
COS - 0 to 7 - default is 7
Click on OK
Step 5 Expand the NE-1 entity under Management Tunnels, left click on the
management tunnel ID and verify the data entered. (see Figure 292
on p. 422)
Step 6 If anything in the Configuration, RIP or Bandwidth data requires modi-
fication, right click on the management tunnel ID and select Edit Con-
figuration (see Figure 293 on p. 423)
Edit the data as appropriate.
Click on OK.

Figure 292: Display Management Tunnel Configuration

Figure 293: Edit Management Tunnel

Step 8 To delete a management tunnel, right click on the management tun-

nel ID and select Delete (see the following figure).
Click on OK.
Figure 294: Delete Management Tunnel
End of Procedure


Create a management tunnel? Continue with the next
step.
Display a management tunnel? Go to Step 12.
Edit a management tunnel? Go to Step 13.
Delete a management tunnel? Go to Step 8.
Step 10 Right click on “NE-1” in the selection tree pane under “Management
Tunnels”, select Create Tunnel and the following screen displays:
Figure 295: Create Management Tunnel - Bridging Enabled

Step 11 Enter/select the following data to configure the management tunnel:

(see Management Tunnel Configuration Options and Rules on p. 701
for details on each item.)
Identification
Management Tunnel Index - integer from 1 to 255
Management Tunnel Name - 1 to 15 alphanumeric characters
Associated Port - select from drop-down list - only one tunnel per port
Interface
Encapsulation Type - Ethernet
Layer 2 Configuration
Tunnel Mode - VLAN Based and I-Tag-based. (I-Tag-based is only
supported on Network Port)
C-TAG VLAN Enabled/Disabled
C-TAG VLAN ID - 1 to 4095 - default is 4095
I-TAG - Enabled/Disabled (only applicable when the Tunnel Mode is
set to I-Tag-based)
I-SID - 256 - 16777214. (only applicable when the Tunnel Mode is set
to I-Tag-based)
VLAN Id - 1 to 4095 - default is 4095
S-Tag VLAN - Enabled/Disabled - default is Disabled

S-Tag VLAN Id - 1 to 4095 - default is 4095 (only applicable if S-Tag
VLAN is Enabled)
Destination Backbone MAC- Enabled/Disabled (only applicable when
the Tunnel Mode is set to I-Tag-based)
Backbone MAC Destination Address. A valid MAC address. (only
applicable when the Tunnel Mode is set to I-Tag-based)
Bandwidth
CIR - 64000 to 8000000 bps - default is 256000 bps (Max of 8 Mbps
for all management tunnels combined)
EIR - 0 to 80000000 bps - default is 768000 bps
Buffer Size - 32 to 15000 KB - default is 32 KB
COS - 0 to 7 - default is 7
Click on OK
Step 12 Expand the NE-1 entity under Management Tunnels, left click on the
management tunnel ID and verify the data entered. (see figure below)

Figure 296: Display Management Tunnel Configuration - Bridging
Step 13 If anything in the Configuration data requires modification, right click

on the management tunnel ID and select Edit Configuration (see the
following figure):
Figure 297: Edit Management Tunnel - Bridging
Edit the appropriate data.

Click on OK.
End of Procedure

Configure IPv6 over IPv4 Tunnel

The GE11x supports the configuration of one IPv6 over IPv4 tunnel per system.
With an IPv4 management interface as the tunnel entrance and with a specified
destination IPv4 address as the tunnel exit, the IPv6 packets encapsulated in
IPv4 packets can be delivered across an IPv4 infrastructure. At the exit, the IPv6
packets are decapsulated and forwarded to an IPv6 unicast address destina-
tion. By using the IPv6 over IPv4 tunnel, IPv6 hosts can access GE11x products
in an IPv6 network without upgrading the IPv4 infrastructure between them.
IP address and connected the NE to a DCN or LAN, (See Set Up the FSP
eVision.
From the Configuration view with the Communications and IPv6 over Tunnels
entities expanded:
Procedure
Step 1 Determine the next step:

Create an IPv6 over IPv4 tunnel? Continue with the next
step.
Display an IPv6 over IPv4 tunnel? Go to Step 6.
Delete an IPv6 over IPv4 tunnel? Go to Step 7
Step 2 Right click on “NE-1” in the selection tree pane under IPv6 over IPv4
Tunnels, select “Create Tunnel” and the following screen displays:
Figure 298: Create IPv6 over IPv4 Tunnel

Step 3 Enter/Select the following data to configure the IPv6 over IPv4 tunnel:
(see IPv6 over IPv4 Tunnel Configuration Options and Rules on
p. 707 for details on each item.)
Identification
IPv6 over v4 Tunnel Index - 1, default and unique value.
IPv6 over v4 Tunnel Name - a string up to15 alphanumeric characters
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
Tunnel Address (options vary according to different Tunnel Mode)
Destination IPv4 Address - valid IPv4 destination address (applicable
to Configured Mode)
IPv4 Unicast Address - valid IPv6 unicast address (applicable to Con-
figured Tunnel Mode)
Step 4 Potential Router - valid IPv4 address (applicable to ISATAP Tunnel
Mode)
Click on OK.
Step 6 Expand the NE-1 entity under IPv6 over IPv4 Tunnels, click on the
IPv6 over IPv4 Tunnel ID and verify the data entered.
Figure 299: Display IPv6 over IPv4 Tunnel
Step 7 To delete an IPv6 over IPv4 Tunnel, right click on the tunnel ID and
select Delete.
Click on OK.

Figure 300: Delete an IPv6 over IPv4 Tunnel
End of Procedure
Configure Source Address

The FSP 150CC can have multiple IP addresses assigned when using manage-
ment tunnels in addition to or in place of the Management LAN interface (Sys-
tem IP Address). When management conditions or messages are sent over
another interface, it is often desirable or even necessary that the message be

traceable to the Management LAN IP address rather than the address of the
interface carrying the message. Setting the Source Address ensures that this
address will be used for all management functions for the unit. For details on the
settings and options for Source Address, see Source Address Config (Edit
Source Address Config) on p. 640
The FSP 150CC supports the configuration of a single management tunnel on
each Network/Access interface or LAG. Up to 2 management tunnels can be
supported at one time.
IP address and connected the NE to a DCN or LAN, (See Set Up the FSP
eVision.

Procedure
Step 1 Right click on “Communications” in the selection tree pane, select

Edit Source Address Config and the following screen displays (see
the following figure):
Figure 301: Edit Source Address Config
Step 2 Enter/select the following data to configure Source Address:
Address Type - Select “System IP Address” or “Outgoing Interface IP”
Source Address Interface Name:
If Address Type is “System IP Address”, select the desired
Source Address Interface Name from the drop-down list.
If Address Type is “Outgoing Interface IP”, Source Address Inter-
face Name is fixed as “eth0” (Management LAN)
SNMP v1 Interface Name:
Select the desired interface name from the drop-down list.
Click on OK
Any management interface or tunnel interface configured with IPv4

address could be the candidates for Snmp v1 Interface Name, and
PS
Source Address Interface Name. (for System IP Address Access

Note Type)
End of Procedure

Add/Delete Static Route

Static Routes may be displayed, created or deleted. To edit an existing static
route, delete it and add a new static route.
eVision.
Procedure

Add a Static Route? Continue with the next
step.
Display Static Routes? Go to Step 5.
Delete Static Route? Go to Step 7.
Step 2 Right click on “Communications” in the selection tree pane and select
Add Static Route and the following screen displays (see the following
figure):
Figure 302: Add Static Route

Step 3 Enter/select the following data to create a static route:

Destination IP Address - valid IPV4 address
Subnet Mask - valid IPV4 mask
Gateway IP Address - valid IPV4 address of Gateway
Interface Name - Select desired Interface Name from the drop-down
list.
Metric - 0 to 65535
Advertise Route - select “Disabled or Enabled”
Click on OK
If Management Traffic Bridging is enabled, only eth0 is allowed for

PS
Interface Name. To enable Management Traffic Bridging, refer to

Table 42: System Configuration Settings on p. 619.
Note
Step 4 Go to Step 1
Step 5 Left click on “Communications” and select the “Static Routes” tab.
(see Figure 303)
Figure 303: Display Static Routes
Step 6 Go to Step1
Step 7 To delete a Static Route, right click on Communications and select
“Delete Static Route” (see the following figure):

Figure 304: Delete Static Route
Click the radio button in the “Delete” column for each route to be
deleted.
Click on OK.
End of Procedure

Add/Delete Static ARP Entry

Static ARP Entries may be displayed, created or deleted. To edit an existing
static ARP entry, delete it and add a new static ARP entry.
eVision.
Procedure

Add a Static ARP Entry? Continue with the next
step.
Display Static ARP Entries? Go to Step 5.
Delete Static ARP Entry? Go to Step 7.
Add Static Route and the following screen displays (see the following
figure):
Figure 305: Add Static ARP Entry
Step 3 Enter/select the following data to create a Static ARP Entry:

IP Address - valid IPV4 address
MAC Address
list.
Click on OK.

If Management Traffic Bridging is enabled, only eth0 is allowed for
PS
Interface Name. To enable Management Traffic Bridging, refer to
Table 42 System Configuration Settings on p. 619.
Note
Step 5 Left click on “Communications” and select the “Static ARP Entry” tab.
(see the following figure)
Figure 306: Display Static ARP Entries

Step 7 To delete a Static ARP Entry, right click on Communications and
select “Delete Static ARP Entry” (see the following figure):
Figure 307: Delete Static ARP Entry
Click the radio button in the “Delete” column for each ARP entry to be
deleted.
Click on OK.

End of Procedure
Add/Delete IPv6 Static Route

IPv6 Static Routes may be displayed, created or deleted. To edit an existing
IPv6 static route, delete it and add a new static route.
eVision.
Procedure

Add IPv6 Static Route? Continue with the next
step.
Display IPv6 Static Routes? Go to Step 5.
Delete IPv6 Static Routes? Go to Step 7.
Add IPv6 Static Route and the following screen displays (see the fol-
lowing figure):
Figure 308: Add IPv6 Static Route

Step 3 Enter/select the following data to create a static route: (see IPv6
Static Route (Add IPv6 Static Route) on p. 639 for details on each
item.)
Destination IPv6 Address - valid IPv6 unicast address
Gateway IP Address - valid IPv6 address of Gateway
list, by default the management interface in IPv6 mode will automati-
cally appear for selection.
Metric - 0 to 65535, default is 1
Advertise Route - select “Disabled or Enabled”
Click on OK
If Management Traffic Bridging is enabled, only eth0 configured with

IPv6 unicast address is allowed for Interface Name. To enable
PS
Management Traffic Bridging, refer to Table 42: System Configuration

Note Settings on p. 619.
Step 4 Go to Step 1
Step 5 Left click on “Communications” and select the “IPv6 Static Routes”
tab. (see Figure 309)
Figure 309: Display IPv6 Static Routes
Step 6 Go to Step1
Step 7 To delete an IPv6 Static Route, right click on Communications and
select “Delete IPv6 Static Route” (see the following figure):

Figure 310: Delete IPv6 Static Route
Click the radio button in the “Delete” column for each IPv6 route to be
deleted.
Click on OK.
End of Procedure

Add/Delete IPv6 Static Neighbor Entry

IPv6 Static Neighbor Entries may be displayed, created or deleted. To edit an
existing IPv6 static neighbor entry, delete it and add a new IPv6 static neighbor
entry.
eVision.
Procedure

Add an IPv6 Static Neighbor Entry? Continue with the next
step.
Display IPv6 Static Neighbor Entries? Go to Step 5.
Delete an IPv6 Static Neighbor Entry? Go to Step 7.
Add IPv6 Static Neighbor Entry and the following screen displays (see
Figure 311: Add IPv6 Static Neighbor Entry

Step 3 Enter/select the following data to create an IPv6 Static Neighbor

Entry: (seeIPv6 Static Neighbor Entry (Add IPv6 Static Neighbor
Entry) on p. 639 for details on each item.)
IP Address - valid IPv6 unicast address
MAC Address
list. By default, a management tunnel configured with IPv6 address
will appear for selection.
Click on OK.
If Management Traffic Bridging is enabled, only eth0 if configured with

PS
Management Traffic Bridging, refer to Table 42 System Configuration

Step 5 Left click on “Communications” and select the “IPv6 Static Neighbor
Entry” tab. (see the following figure)
Figure 312: Display IPv6 Static Neighbor Entries
Step 6 Go to Step 1. FSP 150CC-GE11x R6.1 80000026494 Issue: A, © 2013 ADVA Optical Networking SE - Confidential
Step 7 To delete an IPv6 Static Neighbor Entry, right click on Communica-

tions and select “Delete IPv6 Static Neighbor Entry” (see the following
figure):

Figure 313: Delete IPv6 Static Neighbor Entry
Click the radio button in the “Delete” column for each IPv6 static
neighbor entry to be deleted.
Click on OK.
End of Procedure

Add/Delete IPv6 Static Proxy ND Entry

IPv6 Static Proxy ND Entries may be displayed, created or deleted. To edit an
existing IPv6 static Proxy ND entry, delete it and add a new IPv6 static proxy ND
entry.
eVision.
Procedure

Add an IPv6 Static Proxy ND Entry? Continue with the next
step.
Display IPv6 Static Proxy ND Entries? Go to Step 5.
Delete an IPv6 Static Proxy ND Entry? Go to Step 7.
Add IPv6 Static ProxyND Entry and the following screen displays (see
Figure 314: Add IPv6 Static Proxy ND Entry

Step 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) on p. 640 for details on each item.)
IP Address - valid IPv6 unicast address
list. By default, a management tunnel configured with IPv6 address
will appear for selection.
Click on OK.
If Management Traffic Bridging is enabled, only eth0 if configured with

PS
Management Traffic Bridging, refer to Table 42 System Configuration

Step 5 Left click on “Communications” and select the “IPv6 Static ProxyND
Entry” tab. (see the following figure)
Figure 315: Display IPv6 Static Proxy ND Entries

Step 7 To delete an IPv6 Static Proxy ND Entry, right click on Communica-
tions and select “Delete IPv6 Static ProxyND Entry” (see the following
figure):

Figure 316: Delete IPv6 Static Proxy ND Entry
Click the radio button in the “Delete” column for each IPv6 static proxy
ND entry to be deleted.
Click on OK.
End of Procedure
Configure Access Control List

See Configure ACL on p. 231.
Configure 3G Modem Using eVision

The 3G DCN USB port provides a wireless management port that can be
accessed via a 3G network, so that the user can connect to the GE11x without
local DCN cable connections, or it can work as a back-up management port
when the DCN LAN port is disconnected or inoperable.
When the primary management connection is in service and working, and
SNMP is provisioned, GE11x reports its public IP address acquired from the 3G
service provider to a Network manager via the primary management connection
(DCN). If the primary management connection fails, management communica-
tions may be made to the GE11x via a public 3G network.
The following is a procedure for provisioning a 3G modem to enable the wire-
less connection to a GE11x using eVision. If there is no DCN connected and
only a 3G DCN will be provided for this GE11x, refer to Set Up the 3G Modem
Using the Serial Port on p. 408 to provision the 3G DCN USB port using CLI

commands.
Procedure
Step 1 Select Configuration view. Expand the System Name, NE-1 and
NTE11x entities in the Selection Tree.
Desired Function Description Then
Edit 3G modem Provision or edit 3G Modem Configuration. Continue with the
configuration next step.
Observe current 3G Observe current 3G modem configuration and Go to Step 5.
modem configuration SIM status to determine appropriate action
and SIM status
Enable PIN Requires entry using a PIN. (Can be applied if Go to Step 7.
PIN/PUK status = Disabled.) When the PIN is
Enabled, if the 3G Modem is unplugged or the
system reboots, the 3G Modem SIM must be
unlocked by entering the PIN.
Disable PIN Allows access without entering a PIN. (Can be Go to Step 10.
applied if PIN/PUK status = OK.)
Change PIN Change existing PIN. (Can be applied if Go to Step 13.
PIN/PUK status = OK.)

PIN authentication Enter the PIN. (Can be applied if PIN/PUK Go to Step 16.
status = Input PIN.)
Unlock with PUK If the PIN input fails for three times during PIN Go to Step 19.
Authentication, the 3G Modem SIM will be
locked; therefore, the SIM needs to be unlocked
by entering the PUK and new PIN. (Can be
applied if PIN/PUK status = Input PUK.)
Observe 3G Network Observe the 3G modem network information Go to Step 21.
information and IP address
Verify 3G Network Verify the 3G network connection by logging Go to Step 23.
Connection onto the GE11x via the IP address acquired
from the 3G service provider
Provisioning Complete All desired provisioning options are completed End of Procedure
and current 3G status has been verified
Step 3 Right click on the 3G Modem entity and select Edit Configuration. The
following screen displays.

Figure 317: Edit 3G Modem Configuration
Step 4 Fill in the Alias as appropriate. Select “IS” for Administrative State.
The Modem information and Physical Configuration information will
display automatically once the 3G modem is plugged in. Enter the 3G
Dial-Up Configuration. Click on OK.
Step 5 Left click on “3G 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 23 for SIM status result descrip-
tions. The SIM status will be used in the next step.

Figure 318: 3G Modem Configuration Information

Figure 319: 3G Modem SIM Card Status

Table 23: SIM Card Status Description

SIM Status Type Result Description
SIM Status OK Unlocked status
Network reject Invalid SIM
Not inserted SIM not inserted
PIN/PUK Status Disabled PIN protection is disabled
OK PIN protection is enabled and PIN
code is correct.
Input PIN PIN authentication is required to
unlock SIM
Input PUK Pin protection is enabled and the PIN
code is locked: 3 failed attempts to
input PIN has occurred. Unlock with
PUK is required.
Locked SIM is locked, contact SIM provider
IMSI IMSI code International Mobile Subscriber
Identity of the SIM card.
Not Available SIM is removed
Current RSSI High, Medium Current Received Signal Strength
or Low Indicator. This value changes
automatically according to the actual
signal strength.
Not Available SIM is removed
Step 6 Use the SIM status information from the previous step to determine
the next step.
Enable PIN? Continue with the next
(Can be applied if PIN/PUK status = Disabled.) step.
When the PIN is Enabled, if the 3G Modem is
unplugged or the system reboots, the 3G
Modem SIM must be unlocked by entering the
PIN.
Disable PIN? Allows access without entering Go to Step 10.
PIN authentication. Once the PIN is disabled,
operations such as Change PIN, PIN
Authentication, Unlock with PUK are disabled.
(Can be applied if PIN/PUK status = OK.)
PIN authentication required (PIN/PUK status = Go to Step 16.
input PIN)?
Unlock with PUK required (PIN/PUK status = Go to Step 19.
Input PUK)?
Provisioning is complete - Verify 3G Go to Step 21.
Networking Connection?

Step 7 To enable 3G Modem PIN, right click on the 3G Modem entity and
select “Enable PIN”. The following screen displays.
Figure 320: Enable 3G Modem PIN
Step 8 Enter the PIN provided by wireless ISP. Click OK.

When the PIN is Enabled, if the 3G Modem is unplugged or the

PS
system reboots, the 3G Modem SIM must be unlocked by entering the

PIN upon each occurrence.
Note
Step 9 Go to Step 5 to observe the current configuration and SIM status to

determine the next step.
Step 10 To disable 3G Modem PIN, right click on the 3G Modem entity and
select “Disable PIN”. The following screen displays.

Figure 321: Disable 3G Modem PIN
Step 11 Input PIN and click OK.
3G Modem SIM will not be locked if the PIN is disabled. Once the PIN
PS
is disabled, the operations such as Change PIN, PIN Authentication,
Unlock with PUK are disabled.
Note

Step 13 To change the 3G Modem PIN, right click on the 3G Modem entity
and select “Change PIN”. The following screen displays.
Figure 322: Change 3G Modem PIN

Step 14 Enter the current PIN and the new PIN; then repeat the new PIN to
confirm the input. Click OK.
The new PIN will take effect in the next time when PIN input is
PS
required.
Note

Step 16 To unlock the SIM by PIN authentication, right click on the 3G Modem
entity and select “PIN Authentication”. The following screen displays.
Note the number of remaining (failed) attempts indicated.
Figure 323: 3G Modem PIN Authentication

Step 17 Input PIN and click OK.
If PIN is Enabled and the 3G Modem is unplugged or the system

reboots, the 3G Modem will be locked and the user will need to
re-enter PIN authentication. If the PIN input fails after three attempts
PS
to authenticate PIN, the 3G Modem SIM will still be locked - and the
SIM will need to be unlocked by entering PUK and a new PIN
Note (Step 19).


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 3G
Modem entity and select “Unlock with PUK”. The following screen dis-
plays.
Figure 324: Unlock 3G Modem with PUK
Step 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
PS
ISP to unlock the SIM.

Note
Step 21 Observe the 3G Networking information by expanding the Communi-

cations entity under System and selecting “3G DCN”.
Figure 325: 3G Networking Information

Step 22 To verify connection to the GE11x via the 3G networking IP address,

continue with the next step. Otherwise, go to Step 5 to observe the
current configuration and SIM status to determine the next step.
Step 23 To verify the connection to the GE11x via the 3G 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.
End of Procedure

Sample Network - GNE to SNE over Management

Tunnel
This is an example of setting up communications between two FSP 150CC’s
using a management tunnel in a laboratory or back-to-back small network con-
figuration.
The Figure below shows an example of back-to-back FSP 150CCs where the
eVision workstation, Gateway NE (GNE) and Subtending NE (SNE) are on the
same subnet, and WAN connectivity between FSP 150CCs is via a manage-
ment tunnel. FSP 150CC #1 and the Workstation reside on LAN Segment A.
FSP 150CC #2 has no management LAN connection, and has a WAN manage-
ment tunnel connection to FSP 150CC #1.
Figure 326: Workstation / GNE / SNE on Same Subnet
GNE
FSP 150CC #1
Network Port
Management Tunnel
MGMT LAN Port VLAN Based, VLAN ID = 100
Layer 2 Protocol = Ethernet
IP Address = 192.168.2.2
DHCP = disabled
Netmask = 255.255.255.0
RIP V2 Packets = enabled
DHCP = disabled
IP Address = 10.10.10.4
RIPv2 = disabled
Subnet Mask = 255.255.255.0
Proxy ARP = enabled
Default Router = 192.168.2.1 Network Port
Static Route Not Required
Management Tunnel
LAN Segment A VLAN Based, VLAN ID = 100
Layer 2 Protocol = Ethernet
DHCP = disabled
RIP V2 Packets = enabled
IP Address = 10.10.10.5 SNE
Subnet Mask = 255.255.255.0 FSP 150CC #2
eVision Workstation MGMT LAN Port

IP Address = 192.168.2.4 IP Address = 192.168.2.3
Subnet Mask = 255.255.255.0 Netmask = 255.255.255.0
Default Gateway = 192.168.2.2 DHCP = disabled
RIPv2 = enabled
Note 1: If a DHCP server is available on LAN Segment A, then enable Proxy ARP = disabled
DHCP on the MGMT LAN Port of FSP 150CC #1. If DHCP is enabled, Default Router = N/A
then the IP Address, Subnet Mask and Default Router are assigned by the Admin State = unassigned
DHCP server. Static Route Required
Note 2: User must create a static route on the eVision Workstation PC to

reach the SNE OR set the PC’s Default Gateway to the GNE’s IP Address.
If there is difficulty logging on to the SNE after initial setup, the ARP cache
on the Workstation should be flushed.

For management tunnels where RIP is enabled, under a Denial of

Service attack scenario, RIP PDUs will likely be discarded, resulting
PS
in all RIP learned routes being withdrawn from the routing table. On
Note the GNE, this will have the affect of losing the route to the SNE.
Procedure
Perform the following steps at FSP 150CC #2 (SNE):

Step 1 At FSP 150CC #2, perform the procedures Connect Power Cables
and Apply Power on p. 167 and Serial Connection on p. 402.
You should currently be logged onto the FSP 150CC #2’s RS232
PS
(serial port) using CLI.

Note
Step 2 Provision the eth0 (system) IP address using the following CLI com-
mand entry
ADVA:comms--> configure eth0 ip-address 192.168.2.3
255.255.255.0
ADVA:comms-->
Step 3 Provision the management tunnel using the following CLI command.
ADVA:comms--> add mgmttnl 1 phoenix1 ethernet
vlan-based 100 disabled 10.10.10.5 255.255.255.0
network-1-1-1-1
According to the example in Figure 326, the FSP 150CC #2’s man-
agement tunnel should be set to Ethernet Layer 2 Protocol, VLAN
PS
based with the VLAN ID set to 100, DHCP disabled, the IP address
should be set to 10.10.10.5 with a Subnet Mask of 255.255.255.0,
Note
and RIPv2 should be set to enabled.
Step 4 To edit the management tunnel to enable RIPv2 packets, enter the
following CLI command.
ADVA:comms--> configure mgmttnl mgmt_tnl-1
ADVA:comms:mgmt_tnl-1--> rip2Pkts-control enabled

Step 5 Set the Management LAN Port’s (eth0) Admin state to unassigned
using the following CLI command.
ADVA:comms:mgmt_tnl-1--> home
ADVA--> network-element ne-1
ADVA-NE-1--> configure nte nte114-1-1-1
ADVA-NE-1:NTE114-1-1-1--> configure dcn
ADVA-NE-1:dcn-1-1-1-1--> admin-state unassigned
ADVA-NE-1:dcn-1-1-1-1--> home
Step 6 Add a static route to point to the management tunnel on FSP 150CC
#1 using the following CLI command
ADVA:comms--> add ip-route nexthop 0.0.0.0 0.0.0.0
10.10.10.4 phoenix1 1 disabled
Step 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
ADVA:system--> proxy-arp disabled
Ensure that the Proxy ARP option is set correctly for the FSP 150CC.
If two or more ADVA Optical Networking NEs or FSP 150CCs 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
CAUTION responses for a single ARP request for a remote reachable IP
address from each NE/FSP 150CC in the same LAN that has Proxy
ARP enabled.
Step 8 Logoff the CLI session and remove any commissioning cables (Ether-
net cable and/or console cable) from the FSP 150CC front panel con-
nectors, as required.
Step 9 Connect the optical cables to the FSP 150CC Network Port front
panel connectors if they are not already connected.
Perform the following at FSP 150CC #1 (GNE):
Step 10 At FSP 150CC #1, perform the procedures Connect Power Cables
and Apply Power on p. 167 and Serial Connection on p. 402.
You should currently be logged onto the FSP 150CC #1’s RS232
PS
(serial port) using CLI.

Note
Step 11 Provision a management tunnel using the following CLI command.


ADVA:comms--> add mgmttnl 1 phoenix1 ethernet
vlan-based 100 disabled 10.10.10.4 255.255.255.0
network-1-1-1-1
According to the example in Figure 326, the FSP 150CC #1’s man-
agement tunnel should be set to Ethernet Layer 2 Protocol, VLAN
PS
based with the VLAN ID set to 100, DHCP disabled, the IP address
should be set to 10.10.10.4 with a Subnet Mask of 255.255.255.0,
Note
and RIPv2 should be set to enabled.
Step 12 Edit the management tunnel to enable RIPv2 packets.

ADVA:comms--> configure mgmttnl mgmt_tnl-1
ADVA:comms:mgmt_tnl-1--> rip2Pkts-control enabled
Step 13 Provision the eth0 (system) IP address using the following CLI com-
mand entry
ADVA:comms:mgmt_tnl-1--> home
ADVA:comms--> configure eth0 ip-address 192.168.2.2
255.255.255.0
ADVA:comms-->home
Step 14 Enable Proxy ARP by entering the following CLI command.
.ADVA:comms--> home
ADVA:system--> proxy-arp enabled
Ensure that the Proxy ARP option is set correctly for the FSP 150CC.
If two or more ADVA Optical Networking NEs or FSP 150CCs 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
CAUTION responses for a single ARP request for a remote reachable IP
address from each NE/FSP 150CC in the same LAN that has Proxy
ARP enabled.
Step 15 Logoff the CLI session and remove any commissioning cables (Ether-
net cable and/or console cable) from the FSP 150CC front panel con-
nectors, as required.
Step 16 Ensure the DCN connection for LAN Segment A is connected to the
MGMT LAN (eth0) port.
Step 17 Connect the optical cables to the FSP 150CC Network Port front
panel connectors if they are not already connected.
Step 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 FSP 150CC #1 and FSP 150CC #2.

Step 19 Depending on your configuration, either set the eVision workstation

default gateway to point to the GNE FSP 150CC’s Management LAN
port IP address, or create a static route on the PC to communicate to
the SNE (e.g., from Windows command prompt, enter route add
192.168.2.3 mask 255.255.255.255 192.168.2.2 according to the
example in Figure 326:, on Page 5-454). This will allow you to con-
nect to the SNE.
Step 20 Verify connectivity to FSP 150CC #1 and FSP 150CC #2 from the
eVision Workstation. Open a web browser window [Internet Explorer
5.0 or greater (IE 8.0 recommended) or Firefox 2.0 or greater (Firefox
3.6 recommended)] and enter the IP address of FSP 150CC #1 to
access the FSP 150CC eVision Web Browser Management Tool.
Logon using a valid user name and password. The default login and
password are ‘root’ and ‘ChgMeNOW,’ respectively. Repeat for FSP
150CC #2.)
End of Procedure

Chapter 6
Etherjack Test Procedures and

Introduction
This chapter contains information and procedures for the following Etherjack®
testing features.
• Loopbacks
• Etherjack® Diagnostics
• Cable Length Benchmarks
• ESA Provisioning and Operation
• CFM Provisioning and Operation
• Etherjack® Connection Performance Analyzer
• Service Activation Testing
Loopbacks
To assist with Ethernet service fault isolation and to support Service Level
Agreement (SLA) conformance verification, the system supports Port, VLAN,
ITAG (not applicable in GE114S/GE114SH) 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 net-
work.

Loopbacks
PS
switching.
Note
As shown in the example in following figure, traffic is looped back into the net-
work 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 con-
nect a test-set in the field or at the customer premise to verify round-trip service.
Figure 327: CO Based Testing Using Ethernet Loopback
CO Based
Test Head
Loopback Loopback
Test Pattern 2 Test Pattern 1
FSP 150CC FSP 150CC
Four basic types of loopback are available: Port, VLAN, I-Tag, and Ethernet
First Mile (EFM)-Operation, Administration and Maintenance (OAM). The follow-
ing loopback functions are available:
• EFM-OAM Remote
• EFM-OAM Remote Timed
• Facility Port
• Facility Port Timed
• Facility VLAN
• Terminal Port
• Terminal Port Timed
• Terminal VLAN
• Facility I-Tag Port (not applicable to GE114S/GE114SH)
• Terminal I-Tag (not applicable to GE114S/GE114SH)
As a sub-function, JDSU loopback responder function is supported and man-
aged on a per-port basis, wherein the device only reacts and responds to a
JDSU loopback control request frame. There is no support for initializing request
messages. Fore more information on JDSU loopback, see FSP1500CC GE11x
R6.1 Technical Descriptions document.

Chapter 6 Etherjack Test Procedures and Performance Monitoring
Performing Loopbacks Using eVision

From the Maintenance application, entering a right click on a Network Port or
Access Port and selecting Loopbacks provides a Loopback view. From this view,
the Network Port or Access Port can be placed in the Maintenance state, and a
loopback can be performed.
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 shap-
ing, allowing use of the full port bandwidth, while VLAN Loopbacks conform to
configured shaping profiles.
Selecting the Swap SADA [Swapping the Source Address (SA) with the Desti-
nation Address (DA)] option during the loopback directs the FSP 150CC 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.
Only one Terminal/Facility loopback may be performed per system, and multiple
EFM-OAM Loopbacks may be performed meanwhile for different remote termi-
nals. 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).

Another option available is performing a Remote EFM-OAM loopback.
See the following figure for an example of a loopback view. For a description of
the eVision web browser management tool functions, see Chapter 3, eVision
Web Browser Management Tool on p. 189. For a list of loopback setting
options, rules, and associated default settings, see Loopback Settings on
p. 714.
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 Port, VLAN,
EFM-OAM and I-Tag Loopback on p. 87.

Figure 328: Loopback View
Transmission Media Analysis
This diagnostics feature provides a means of monitoring and diagnosing copper
link conditions using Time Domain Reflectometry (TDR) technology. TDR tech-
nology operates by sending individual signal pulses down the transmission
medium and analyzing the return energy.
On a terminated cable, the energy of the signal pulse is absorbed by the termi-
nating 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 cir-
cuit. 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
PS
Diagnostic is disabled at the other end. Otherwise the test results
are incorrect.
Note
PS
This test is not run on copper SFP interfaces.

Note
Ethernet Fault Isolation and Diagnostics

Etherjack® Diagnostics enable the user to perform tests on the Ethernet facility
and the attached cable, in order to detect and isolate faults on:
• the Ethernet port
• the connecting cable
• the far-end equipment
Tests are started automatically on detection of a link fault, but they can also be
started manually using the eVision web browser management tool. Refer to the
following figure for an example Etherjack® Diagnostic Test result using eVision.

Figure 329: Etherjack® Diagnostic Test Results View
The diagnostic operation consists of the following phases:
1 Ethernet Cable Test. Cable faults can be isolated to within +/- 1 meter reso-
lution 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
PS
Cable Length Benchmarking. See Cable Length Benchmarks on

p. 466.
Note
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 moni-
tored 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.

The Etherjack® Diagnostics facility has the following capabilities:

• 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.
• The user may select to run all Ethernet tests or select individual tests manu-
ally.
• Manual diagnostics are not possible when automatic diagnostics are run-
ning.
• By default, Etherjack® diagnostics are automatically triggered when a fault
has been detected on an Ethernet port.
• Only the Ethernet cable Test and Ethernet Auto-negotiation is performed
during automatic diagnosis.
• By default, the EFM loopback test:
o is not performed when the user has selected to run all tests. The user
must select this test separately.
o is not included as part of the automatic tests performed when a link is
down.
o is not performed if the far-end is not EFM capable
• If the cable tests do not pass, the auto-negotiation test is not performed.
Auto-negotiation test is not done unless the port is configured for auto-nego-
tiation.
• Etherjack® Diagnostics are service affecting. This includes management
traffic. Therefore, during the testing, management connectivity may be lost.
The following test results are possible:
• Ethernet Port - Device FAIL. Through internal loopback testing, the Ethernet
port has been found to be faulty. This is an equipment fault.
• Ethernet Port - Device PASS. Through internal loopback testing, the Ethernet
port has been found to be good.
• No Cable Detected. A cable has not been detected on the Ethernet port.
• 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.
• 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.
• 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.
• EFM Communication Failure. EFM packets sent were not returned.
• Cable OK. A valid termination was detected on the cable.


This additional feature enhances cable fault isolation by correlating fault points
to previously known cable points along the Ethernet cable. It also provides cable
segment identification, isolating faults to any of up to five cable segments. The
user may store up to five cable segment lengths during the installation process.
Each cable segment termination point can be named with a text string to
describe the physical location of each termination point. If a subsequent test
detects an open circuit at one of the stored segments, the system can highlight
its location name.
Etherjack® Diagnostics is automatically triggered when a link failure is detected
(on copper media ports only).
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.
Figure 330: Faulty Segment Identified Using Cable Length Benchmark
Cable Length Benchmarking provides the following features:

• the ability to associate a point on the Ethernet link with a name
• the ability to correlate the results of the Ethernet Cable Test to the nearest
named cable point
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. How-
ever, 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’.
Figure 331: Edit Cable Length Benchmarks

The Cable Length Benchmarking facility has the following capabilities:

• When specifying a cable length, the maximum cable length allowed is 1000
meters.
• When labeling cable termination points, the string is limited to 64 ASCII
characters.
• Cable benchmark termination points are displayed to the user as provi-
sioned (i.e., they are not sorted by cable length).

Manually Entering / Editing Cable Length

Benchmarks
Cable length benchmarks can be manually entered or existing cable length
benchmarks may be edited as shown in Figure 331. Use the following proce-
dure to enter cable length benchmarks or edit existing cable length benchmarks
manually. Up to 5 cable length benchmarks can be saved per copper access
port.
Procedure
Step 1 Enter or edit the cable benchmarks for the desired copper interface.
eVision
Select Maintenance view
Right click on the desired access port in the selection tree
Select Edit Cable Benchmarks
An Edit Cable Benchmarks entry screen displays
Select Enabled for each Point for which data is to be entered
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 Descrip-
tion field
Select Apply
An Operation Complete popup window appears
Select OK
End of Procedure

Overview
The Performance Monitoring (PM) feature enables in-service, non-intrusive sys-
tem 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).
This chapter contains the following step by step procedures:
• Viewing PM Counts and Threshold Values on p. 473
• Initializing PM and Distribution Registers on p. 478
• Editing PM Thresholds on p. 481
For PM commands using CLI, refer to the FSP 150CC-GE11x Command Line
Interface Reference Guide.
Etherjack® PM Features
The following features are provided:
• retrievable performance data for each managed entity, so the user can
determine past and current system operation. PM data collection is per-
formed via a polling mechanism, were primitives are gathered into accumu-
lated counts. After a defined interval, (e.g., 15 minutes or 1 day), the counts
are binned and stored in a database.
• 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:
• threshold setting and automatic TCA message generation
• Current and History PM bins provide a continuous record of service perfor-
mance, allowing for accurate SLA conformance statements.
PM counts can be displayed as a summary or in tabular format in the eVision
web browser management tool, can be filtered and/or refreshed and allows
exporting data as Excel spreadsheets.

Performance Parameters
There are several categories of Performance Parameters (PPs) that are col-
lected, as follows:
• equipment presence and type [e.g., Small Form Factor Pluggable (SFP)
Interface type and presence, module type and presence]
• physical Layer monitoring (e.g., optical power, temperature)
• Ethernet Statistics (e.g., the number of Ethernet packets received/transmit-
ted)
• 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:
• Ethernet Network ports
• Ethernet Access ports
• Ethernet Virtual Connections (EVCs)
• Quality of Service (QoS) Access to Network and Network to Access queues
Performance Parameter Attributes
Each PP can be defined by the attributes outlined in the following table.
Table 24: Performance Parameter Attributes

Attribute Description
Monitor Type The name of the PP. This will be presented in mnemonic
form (e.g. ESF (EtherStat Frames)).
Location Whether the PP is a Near-End or Far-End parameter. The
location is determined in relation to the monitored entity,
in that the PP has occurred:
• Locally to the entity (or at the near end).
• Remotely to the entity (or at the far end).
Direction Whether the PP is a Receive or Transmit parameter. The
direction is in relation to the monitored entity.
Time Period The time period associated with the PP. i.e., 15-Minute,
1-Day or Rollover.

Table 24: Performance Parameter Attributes

Attribute Description
Monitor The time at which the PP was collected:
Timestamp
• The current time is used for Rollover and Current
counters.
• The boundary crossing time is used for History count-
ers (stored as number of seconds since the Epoch).
History Index Indicates a bin from the historical list of bins:
• For 15 Minute history bins, this number is 1 to 32 (1
being the most recent).
• For 1 Day history bins, this number is 1.
• For current and Rollover bins, this number is 0.
Performance Parameter Counters

Each PP is grouped together for a monitored entity and accumulated into:
• Bins, associated with a predefined time period (i.e., 15-Minute or 1-Day) or
• Rollover Counters, for Ethernet managed entities only
The user can reset any individual or all PP counters to zero.
Bins and Bin The following performance bin periods will exist:
Periods • 1 x Current 15-Minute Bin
• 1 x Current 1-Day (24-Hour) Bin
• 32 x Historical 15-Minute Bins
• 1 x Historical 1-Day (24-Hour) Bin
(1) The 32 Historical 15-Minute Bins provide the most recent 8 hours
of performance data.
PS
(2) The Historical 1-Day Bin provides the performance data from the
Note previous day starting from 12:00am (i.e., midnight, 00:00).
Rollover For Ethernet managed entities only, a Rollover Counter is provided. This gives
Counter 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.

Performance Parameter Thresholding

Each PP has a threshold for each bin period which is configurable for each
entity instance. The PP count is compared to the configured threshold and if met
or exceeded, a Threshold Crossing Alert (TCA) is generated.
Provisioning a threshold to zero will disable threshold monitoring for
PS
that entity.
Note
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.
Optical Performance Parameter Thresholding

Some optical PPs have a unique thresholding mechanism.
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) rep-
resents the variance from the configured OPR / OPT thresholds where the mea-
sured 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.
Threshold Crossing Alert Messages

When a PP threshold has been met or exceeded, a TCA is generated. The fol-
lowing table outlines the attributes that are specified in the TCA message.
Table 25: Threshold Crossing Alert Attributes

Attribute Description Values
Entity Identifier The monitored entity’s id Variable.
Monitor Type The name of the PP that has crossed its threshold. See Monitored Types
This will be presented in mnemonic form (e.g. ESF and Default TCA
(EtherStat Frames). Settings on p. 473 for
Monitor Type
mnemonics.
Time Period In which time period the threshold was crossed. 15-Minute
1-Day
Time The time the threshold was crossed. Timestamp

Table 25: Threshold Crossing Alert Attributes (Continued)

Attribute Description Values
Location The location of the TCA generation. This is Near end
determined in relation to the monitored entity, in that Far end
the PP has occurred: None
• Locally to the entity (or at the near end)
• Remotely to the entity (or at the far end).
Direction The direction in relation to the monitored entity. Receive
Transmit
Monitored Value The value of the PP count when the threshold was Up to a 64-bit number
crossed.
Threshold Value The configured threshold at the time the threshold Up to a 64-bit number
was crossed.
Monitored Types and Default TCA Settings

Refer to Performance Monitoring Settings on p. 717 for monitored types and
default Threshold Crossing Alert (TCA) settings.
Viewing PM Counts and Threshold Values

Descriptions and procedures are provided for the following entities/applications:

• Viewing PMs for Network Port, Access Port, Flow or LAG on p. 473
• Viewing PMs for ESA Probes on p. 477
Viewing PMs for Network Port, Access Port, Flow

or LAG
By selecting a Network Port, Access Port, Flow or LAG in the Selection Tree
Pane, the following tabs are provided in the Details Pane for each entity, each
Ethernet Virtual Connection (EVC) and each Quality of Service (QoS) queue:
• Summary, which displays a summary of both transmit and receive statistics.
See Figure 332 for an example view of a Network Port summary.
• 15 Minute, which displays the PM counts in the current 15 Minute perfor-
mance bin. See Figure 333 for an example view of a Network Port 15 Min-
ute PM counters. If the History checkbox is selected the previous 32 periods
are also displayed.
• 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.
• Thresholds, which displays the details and the thresholds that have been
set for each PP. See Figure 334 for an example view of a Network Port
Threshold values.

Procedure
Step 1 Select the Performance Monitoring icon or select Performance Moni-

toring from the Applications menu, then expand the System entity in
the Selection Tree.
Step 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 enti-
ties.
Step 3 Select the desired Network Port, Access Port, LAG, Flow or Probe ID
in the Selection Tree.
The PM Counts pane appears (see Figure 333)
Step 4 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 counters, 1 Day counters tabs: Move, resize windows or
use sliding bars to view data, as required. Windows may be filtered to
display only selected data by selecting the Filter button and select-
ing/de-selecting individual Monitored Type, or by selecting the Select
All or Deselect All buttons. Then select OK. History data may be hid-
den or displayed by de-selecting/selecting the History option. An
asterisk in the Time column indicates data that is suspect.
Thresholds tab: Thresholds are displayed by entity type.
Step 5 If desired, 15 Minute and 1 Day counts can be exported to an Excel
spreadsheet by selecting the Export button.
An export file pane appears (see Figure 335).
Step 6 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 336). Edit or save the exported file as desired.
End of Procedure

Figure 332: Summary PM Counts View of an Access Port Flow

Figure 333: 15 Minute PM Counts View of an Access Port Flow

Figure 334: Current PM Threshold View of a Network Port
Figure 335: Exporting 15 Minute PM Counts to Excel

Figure 336: 15 Minute PM Counts Exported to Excel

Viewing PMs for ESA Probes

For ESA Probes, each threshold value may be viewed by selecting the Probe ID
in the ESA application.
Procedure
Step 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.
Step 2 Select the desired Probe ID and the Thresholds tab.
The Thresholds data pane appears (see Figure 337)
End of Procedure

Figure 337: Thresholds View of an ESA Probe
Initializing PM and Distribution Registers
The following descriptions and procedures are provided for the following enti-
ties/applications:
• Initializing Network Port, Access Port, Flow and LAG Registers on p. 478
• Initializing ESA Probe PM Registers on p. 479
• Initializing ESA Probe Distribution Registers on p. 480
Initializing Network Port, Access Port, Flow and

LAG Registers
For Network Port, Access Port and flow entities, PM data is maintained in indi-
vidual monitored parameter bins for each interval. The system maintains bins
for the following time periods:
• Current 15-minute bin
• Current 24-hour (1-day) bin
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.
Procedure

toring from the Applications menu, then expand the System selection
tree.
Step 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.
Step 3 Enter a right click on the desired Network Port, Access Port, LAG or
Flow in the selection tree and select Init Registers.
An Initialize Registers pane appears (see Figure 338)
Step 4 Select the desired Entity, Interval and Bin Index. Select OK.
The designated PM count registers are cleared
End of Procedure
Figure 338: Initialize PM Registers Pane
Initializing ESA Probe PM Registers

For ESA Probes, each PM register may be initialized within the ESA application.
Procedure
Selection Tree.

Step 2 Enter a right click on the desired Probe ID and select Init. PM Regis-
ters.
The Initialize PM Registers pane appears (see Figure 339)
Step 3 Select the desired bin: current, All History, or specific interval.
Step 4 For a layer-2 probe, select the desired CoS(s), Select All or Deselect
All.
Step 5 Select OK.
End of Procedure
Figure 339: Initialize ESA Probe PM Registers
Initializing ESA Probe Distribution Registers
For ESA Probes, each Distribution register may be initialized within the ESA
application.
Procedure
Selection Tree.
Step 2 Enter a right click on the desired Probe ID and select Init. Dist. Regis-
ters.
The Initialize Distribution pane appears (see Figure 340)
Step 3 Select the desired history distribution register: All History Data, or
specific history data.
Step 4 For a layer-2 probe, select the desired CoS(s), Select All or Deselect
All.

Step 5 Select OK.
End of Procedure
Figure 340: Initialize ESA Probe Distribution Registers

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:
• Edit Network Port, Access Port, Flow or LAG PM Registers on p. 481
• Edit ESA Probe PM Registers on p. 483
Edit Network Port, Access Port, Flow or LAG PM

Registers
For Network Port, Access Port, Flow and LAG, each Performance Parameter
(PP) has a threshold for each bin period which is configurable for each entity
instance. The PP count is compared to the configured threshold and if met or
exceeded, a Threshold Crossing Alert (TCA) is generated.
Provisioning a threshold to zero disables threshold monitoring for that

PS
entity.
Note

Procedure

toring from the Applications menu.
Step 2 Expand the System, Network Element and NTE entities in the Selec-
tion 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.
Step 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.
An Edit Thresholds pane appears (see Figure 341)
Step 4 Edit the desired thresholds for the desired Monitored Type. Select
OK.
End of Procedure
Figure 341: Edit PM Threshold View of an Access Port Flow

Edit ESA Probe PM Registers

For ESA Probes, each PM register may be edited within the ESA application.
Procedure
Selection Tree.
Step 2 Enter a right click on the desired Probe ID and select Edit Thresholds.
The Edit Thresholds pane appears (see Figure 342)
Step 3 Select the desired history distribution register: All History Data, or
specific history data.
Step 4 Edit the desired thresholds for the desired Monitored Type. Select
OK.
Step 5 Select OK.
End of Procedure
Figure 342: Edit PM Threshold View of an ESA Probe



Etherjack Service Assurance (ESA) provisioning and reporting is invoked by
selecting the ESA icon on the Tool Bar or selecting ESA from the Applications
menu and expanding the System, NE-1 and NTE11x entities in the Selection
Tree.
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 Probes. Up to 6 Layer-3 Probes, 6 Reflec-
tors and up to 16 (for GE112)/32 (for GE114/GE114H/GE114PH) 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 on p. 495).
The following procedures are used for setting up ESA:
• Provision a Layer-3 Probe - or - Provision a Y.1731 LM/DM Probe
• Provision a Reflector
• Provision an ESA Schedule
Provision a Layer-3 Probe
The first step in creating an ESA test is to establish a probe at one FSP 150CC.
This procedure provides steps for creating a Layer-3 Probe. 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

PS
edited. If they require modification, the probe must be deleted and

re-entered.
Note
To delete an existing Probe, enter a right click on the desired Probe entity and
select Delete Probe.
A Probe cannot be deleted if it is associated with a Scheduled ESA

Activity. To delete a Probe that is associated with a Scheduled ESA
PS
Activity, the Scheduled ESA Activity must first be deleted (see

Note Provision an ESA Schedule on p. 495).
Refer to ESA Options and Rules on p. 746 to determine the default values,
Procedure
Step 1 Select the ESA icon on the Tool Bar or select ESA from the Applica-
tions menu and expand the System, NE-1 and NTE11x entities in the
Selection Tree.
Step 2 Ensure that services are created and In-Service for the Access Port
that is targeted to create the Layer-3 Probe.

Step 3 Enter a right click on the Probes entity and select Create Probe.
A Create Probe pane appears
Figure 343: Create Probe View (ICMP Timestamp)

Step 4 Enter the desired Probe options:

Identification
a) Probe Index – Unique EID for the probe. Options available are 1 to
255.
b) Probe ID – a text identifier (up to 15 characters, no spaces and
must contain only alpha-numeric characters) for the probe
(required).

Probe Information
c) 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.
d) Source Port – Select the Access Port this probe is assigned to
Service End Points
e) 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
PS
provisioned within the FSP 150CC.

Note
If more than one Probe IP address resides on the same subnet, they
PS
must all be associated with the same flow.

Note
f) Reflector IP Address – the IP address of the reflector to which
echo replies (and optionally, timestamp) will be reflected back.
Traffic Parameters
g) Packet Type – specifies whether the service is VLAN Tagged or
Untagged. To test a specific FID on an existing Flow VLAN ser-
vice, the VLAN ID and Priority entry should be set to VLAN
Tagged.
h) VLAN ID and Priority – the VLAN ID and Priority to be used for test
traffic frames. To test a specific FID on an existing Flow VLAN
service, the VLAN ID and Priority entry should be a member of
that FID. Only applicable if the Packet Type is VLAN Tagged.
i) Priority Map Mode and Priority – identifies the priority classifica-
tion mechanism for ESA traffic. To test a specific FID on an exist-
ing Flow VLAN service, the Priority Map Mode should match the
actual service.
j) Packet Size – the number of bytes for each test frame.
k) Packets Per Sample – the number of test packets to send in a
sample burst.
l) Packet Interval – the interval between packets in a sample burst in
milliseconds.
m) Dead Interval – the settling time to wait after a sample burst is
complete before starting the next sample in seconds.
n) Response Timeout – wait time for a response in seconds. Packets
received after this time-out are considered lost.
History Configuration

o) History Bins – the number of bins of history results to keep.

p) History Interval – the number of minutes in a single interval.
q) History Distribution Bins – the number of distribution history bins
to keep.
r) History Distribution Interval – the number of minutes in a distribu-
tion history bin.
s) Round Trip Delay - set the minimum and maximum values and
the number of bins assigned.
Statistics and Distribution (If Protocol = ICMP Timestamp)
t) Round Trip Delay - set the minimum and maximum values and
u) One Way TX Delay - set the minimum and maximum values and
v) One Way RX Delay - set the minimum and maximum values and
w) One Way TX Jitter - set the minimum and maximum values and
x) One Way RX Jitter - set the minimum and maximum values and
Step 5 Select OK.

Step 6 Expand the Probes entity in the Selection Tree. Select the Probe
Identifier and Configuration and StatsConfig tabs to verify the entry.
Step 7 To view / edit Probe Thresholds, see Viewing PM Counts and Thresh-
old Values on p. 473 or Editing PM Thresholds on p. 481, respec-
tively.
Step 8 Go to Provision a Reflector on p. 493 to create Reflector(s).
End of Procedure

Provision a Y.1731 LM/DM Probe

The first step in creating an ESA test is to establish a probe at one FSP 150CC.
This procedure provides steps for creating a Layer-2 Probe. Prior to creating a
Y.1731 Probe, a CFM MD, MANET, MACOMP and MEP for the desired port
(see CFM Provisioning and Operation on p. 502), must be established.
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

PS
edited. If they require modification, the probe must be deleted and

re-entered.
Note
To delete an existing Probe, enter a right click on the desired Probe entity and
select Delete Probe.
A Probe cannot be deleted if it is associated with a Scheduled ESA

Activity. To delete a Probe that is associated with a Scheduled ESA
PS
Activity, the Scheduled ESA Activity must first be deleted (see

Note Provision an ESA Schedule on p. 495).
Procedure
Step 1 Ensure that services are created and In-Service for the Access Ports
that are targeted for Layer-2 ESA testing.
Step 2 Create a CFM MD, MANET, MACOMP and MEP for the desired ports
at both NEs (see CFM Provisioning and Operation on p. 502).
tions menu and expand the System, NE-1 and NTE11x entities in the
Selection Tree.
Step 4 Enter a right click on the Probes entity and select Create Probe.
A Layer-3 Create Probe pane (default) appears (see Figure 343)
Step 5 Select Protocol type Y.1731 LM/DM from the drop down list.
A Layer-2 Create Probe pane appears (see Figure 344)
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
PS
CFM to create a Y.1731 protocol probe. Additionally, since Y.1731

Note LM/DM only supports point-to-point connections, the CFM MA MEP
list can only have two entries or an error message displays.
Step 6 Continue to enter the desired Probe options:

Identification

a) Probe Index – Unique EID for the probe. Options available are 1 to
255.
b) Probe ID – a text identifier (up to 15 characters, no spaces and
must contain only alpha-numeric characters) for the probe
(required).
Probe Information
c) Protocol – (Y.1731 LM/DM should already be selected)
d) Source Port – Select the Access Port this probe is assigned to
Service End Points
e) Source MEP – drop-down-list of available MEP numbers.
f) Destination MEP Type – MAC address or MEP ID.
g) Destination MAC Address – the MAC address if Destination Type
is MAC Address.
If the user wants to change the configuration of a MEP associated

with an ESA entity, the recommended steps are: first stop or suspend
PS
the associated ESA Schedule, then change the MEP configuration,

Note and finally restart or resume the schedule.
Service Parameters
h) Multi COS – If Multi-COS is disabled, only 1 COS can be selected;
if enabled, each COS can be individually selected as active using
a check box.
i) COS - If Multi COS is disabled, one COS can be selected from a
drop-down list; if Multi COS is enabled, the desired COS are
selected by clicking on the Active check box next to each COS.
j) Frame Size - the packet size in bytes. The default frame size is
128 bytes.
k) Interval – interval between messages. The options are, 10 msec,
100 msec, 1 second, 10 seconds and 1 minute.
l) History Bins – the number of bins of history results to keep. The
default is 8.
m) History Interval – drop-down list - the number of minutes in a sin-
gle interval. The default is 15 minutes.
n) History Distribution Bins – the number of distribution history bins
to keep. The default is 8.
o) History Distribution Interval – drop-down list - the number of min-
utes in a distribution history bin. The default is 15 minutes.

Statistics and Distribution

p) Round Trip Delay - set the minimum and maximum values and
the number of bins assigned
q) One Way TX Delay - set the minimum and maximum values and
r) One Way RX Delay - set the minimum and maximum values and
s) One Way TX Jitter - set the minimum and maximum values and
t) One Way RX Jitter - set the minimum and maximum values and
Step 7 Select OK.
Step 8 Expand the Probes entity in the Selection Tree. Select the Probe
Identifier and Configuration and StatsConfig tabs to verify the entry
(see Figure 345 and Figure 346).
Step 9 To view / edit Probe Thresholds, see Viewing PM Counts and Thresh-
old Values on p. 473 or Editing PM Thresholds on p. 481, respec-
tively.
Step 10 Go to Provision an ESA Schedule on p. 495.
End of Procedure

Figure 344: Create Probe View (Y.1731 LM/DM)

Figure 345: Viewing a Probe Configuration Tab

Figure 346: Viewing a Probe Distribution Statistics
Figure 347: Viewing a Probe Thresholds Tab

Provision a Reflector
The next step in creating a Layer-3 ESA test is to establish a reflector at one
FSP 150CC.
PS
Y.1731 protocol probes do not require a reflector.
Note
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 sta-
tus by selecting the specific Reflector entity.
Entering a right click on an existing Reflector identifier will provide menu selec-
tions for the specific Reflector. Menu selections available for Reflector identifiers
are:
• Edit Reflector - (only Priority Map Mode and Priority are editable)
• Delete Reflector - To delete a reflector.
A Reflector cannot be deleted if its status is Active. To delete a

PS
reflector, it must be suspended first.

Note
• Suspend Reflector - To change the reflector status from Active to Sus-

pended.
• Resume Reflector - To resume the reflector status from Suspended to
Active.
Procedure
tions menu. Expand the System, NE-1 and NTE11x entities in the
Selection Tree.
Step 2 Ensure that services are created and In-Service for the Access Port
that is targeted to create the Reflector.
Step 3 Enter a right click on the Reflectors entity and select Create Reflector.
A Create Reflector pane appears

Figure 348: Create Reflector View
Step 4 Enter the desired Reflector options:

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
d) Reflector IP Address, Mask – the IP address and subnet mask of
the reflector. (The IP address must not overlap with any non-ESA
related subnet provisioned within the FSP 150CC.)
e) Priority Map Mode, Priority - select the priority map mode and pri-
ority assigned to the associated reflector.
Although it is possible for an FSP 150CC to contain both Reflectors
and Probes, it is not possible for a Probe-Reflector pair to be on the
PS
same FSP 150CC. This is determined by the subnet of the Probe and
Note Reflector IP Address.
Step 5 Select OK.

Step 6 Expand the Reflector entity in the Selection Tree. Select the Reflector
Identifier and Configuration tab to verify the entry.
Step 7 Go to Provision an ESA Schedule on p. 495.
End of Procedure

Provision an ESA Schedule

The final step in creating an ESA test is creating an ESA schedule. A Scheduled
ESA may be provisioned as a:
• one-shot or periodic execution
• now or future execution
• forever (continuous) or fixed duration
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 on p. 746 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 and
Resume. To delete a Scheduled ESA, you must first Suspend the activity. To
view the ESA Schedule status, expand the System, NE-1, NTE11x and Sched-
ules entities in the Selection Tree and select the desired Entity ID.
Procedure
tions menu.
Step 2 Expand the System, NE-1 and NTE11x entities in the Selection Tree.
Enter a right click on Schedules and select Create Schedule.
A Create Schedule pane appears
Figure 349: Create Schedule View
Step 3 Enter the desired ESA Schedule options:

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 Sched-
ule (required).

Schedule Parameters
c) Schedule Type - Select either One Shot (continuous) or Periodic
(intervals).
d) Duration - If One Shot is selected: Select either Forever or Fixed.
If Periodic is selected: Only Fixed is applicable.
e) (secs) - If Fixed duration was selected: Enter the number of sec-
onds for the One Shot or Periodic test. If Schedule Type of One
Shot is selected, valid entries are 0 (continuous) through 9999
(seconds). If Schedule Type of Periodic is selected, valid entries
are 60 through 9999 (seconds).
f) Start Time - Select Now to execute an immediate ESA or select
Future for a scheduled ESA.
g) Start Time Entry Windows (yyyy-mm-dd) and (hh:mm:ss) - This
option is only applicable if Future start time is selected. When cur-
sor is placed in the yyyy-mm-dd data entry window and a mouse
click is entered, a calendar selection appears, allowing date
selection. When cursor is placed in data entry window and mouse
click is entered, a start time drop down selectable menu appears,
in 15 minute segments. Entry selection must be greater than the
current time.
h) Periodic Interval - If Schedule Type of Periodic is selected, spec-
ify the interval between subsequent runs (in seconds). Range is 1
to 2147483647 (seconds).
Schedule Probes
i) Select the checkbox next to the desired probes this schedule is
assigned to.
Step 4 Select OK.
Step 5 Expand the Schedules entity and select the Schedule identifier to ver-
ify entry.
Step 6 Once a scheduled ESA has been activated, status results may be dis-
played: 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 26).
Step 7 Select the desired display type of Table or Chart. See Figure 350 for
an example of ESA counts displayed in tabular format, and see
Figure 351 and Figure 352 for examples of ESA counts displayed in
chart format.
Step 8 Select the desired Counters to be displayed: General, Distribution,
Delay or Jitter. If Distribution is selected, also select the desired Distri-
bution Type to be displayed.
Counters may also be filtered by selecting the Filter button (see
Figure 353). Select or de-select individual counter or click the Select
All or Deselect All button in respective counter types to filter the dis-

played data.Then click on the Filter: OK button to confirm the selec-

tion.
Results may be refreshed by selecting the Statistics tab. History data
may be hidden or displayed by de-selecting/selecting the History
option.
Step 9 If desired, Statistics results can be exported to an Excel spreadsheet
by selecting the Export button.
An export file pane appears (see Figure 354).
Step 10 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 355). Edit or save the exported file as desired.
Step 11 If desired, edit ESA Probe thresholds or initialize PM/Distribution reg-
isters. To edit ESA Probe thresholds, see Editing PM Thresholds on
p. 481. To initialize PM or Distribution registers, see Initializing PM
and Distribution Registers on p. 478.
End of Procedure
Table 26: ESA Counts/Thresholds By Protocol Type and Report Group

Probe Protocol
Report Group Count
Type
Probe to Reflector Packets
Reflector to Probe Packets
Probe to Reflector Errored Packets
Reflector to Probe Errored Packets
Lost Packets
Late Packets
General
Number of Gaps in Sequence Numbers
UDP Echo, Out of Sequence Errors
ICMP Echo,
Probe to Reflector Lost Packets
ICMP Timestamp
Y.1731 Reflector to Probe Lost Packets
Probe to Reflector Sync Errors
Reflector to Probe Sync Errors
Minimum Round Trip Delay
Maximum Round Trip Delay
Round Trip Delay Average Round Trip Delay
Sum of Round Trip Delays
Sum of Square of Round Trip Delays
Y.1731 Probe to Reflector Data Frames
Y.1731 Reflector to Probe Data Frames
Y.1731 Y.1731
Y.1731 Probe to Reflector Negative Loss Occurrences
Y.1731 Reflector to Probe Negative Loss Occurrences

Table 26: ESA Counts/Thresholds By Protocol Type and Report Group (Continued)
Probe Protocol
Report Group Count
Type
Probe to Reflector Minimum One Way Delay
Probe to Reflector Maximum One Way Delay
Probe to Reflector Average One Way Delay
Probe to Reflector Sum of One Way Delay
Probe to Reflector Sum of Square of One Way Delays
One Way Delay
Reflector to Probe Minimum One Way Delay
Reflector to Probe Maximum One Way Delay
Reflector to Probe Average One Way Delay
Reflector to Probe Sum of One Way Delay
Reflector to Probe Sum of Square of One Way Delays
Probe to Reflector Minimum Positive Jitters
Probe to Reflector Maximum Positive Jitters
Probe to Reflector Number of Positive Jitters
Probe to Reflector Sum of Positive Jitters
ICMP Timestamp Probe to Reflector Sum of Square of Positive Jitters
Y.1731 Probe to Reflector Minimum Negative Jitters
Probe to Reflector Maximum Negative Jitters
Probe to Reflector Number of Negative Jitters
Probe to Reflector Sum of Negative Jitters
Probe to Reflector Sum of Square of Negative Jitters
Jitter
Reflector to Probe Minimum Positive Jitters
Reflector to Probe Maximum Positive Jitters
Reflector to Probe Number of Positive Jitters
Reflector to Probe Sum of Positive Jitters
Reflector to Probe Sum of Square of Positive Jitters
Reflector to Probe Minimum Negative Jitters
Reflector to Probe Maximum Negative Jitters
Reflector to Probe Number of Negative Jitters
Reflector to Probe Sum of Negative Jitters
Reflector to Probe Sum of Square of Negative Jitters

Figure 350: ESA Test Results in Tabular Format
Figure 351: ESA Statistics Results in Chart Format

Figure 352: ESA Round Trip Delay Distributed Statistics Results in Chart Format

Figure 353: Filtering ESA Probe Statistics
Figure 354: Exporting ESA Probe Statistics to Excel

Figure 355: ESA Probe Statistics Exported to Excel



Connectivity Fault Management (CFM) is an emerging standard aimed at
enhancing Ethernet Service OAM capabilities. The main features provided by
CFM include the ability to detect, verify, isolate and report connectivity faults on
a service instance. CFM features include the ability to:
• Configure Maintenance Domains (MDs)
• Configure Maintenance Association Networks (MANETs)
• Configure and manage Maintenance Association Components (MACOMPs)
• Configure and manage Maintenance End Points (MEPs)
• Configure and manage Maintenance Intermediate Points (MIPs)
• Transmit and receive Continuity Check Messages (CCMs)
• Initiate Loop Back Messages or Link Trace Messages
• Detect and raise CFM-related alarms
The following procedure describes the CFM feature provisioning and operation
process for each node.
Configuration of a CFM MANET with 2 MEPs in its MEP list is

PS
required to support configuration of a Y.1731 ESA Probe.
Note
Procedure
Step 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.
Edit the CFM System Level Parameters.

Step 2 Select CFM from the Applications menu, expand the System and
Maintenance Domain entities in the selection tree.
Step 3 Right click on the System entity in the selection tree and select Edit
System Default MD Level.
An Edit CFM Configuration screen appears
Step 4 Enter/select the following Default MD options:
Select the desired Default MD Level (0-7)
Select the desired MIP Creation Control (None, Default, Explicit)
Step 5 Select OK

Create a Maintenance Domain (MD)

Step 6 Right click on the Maintenance Domain entity in the selection tree and
select Create MD.
A Maintenance Domain creation screen displays
Step 7 Enter/select the following MD options:
Enter an MD Index number (1-70)
Select the desired Format Type (No Name, DNS Name, Mac-Integer,
String)
If String, MAC Integer or DNS Name was selected for Format Type:
Enter the MD Name contents (See Note 1)
Select the desired Level (0-7)
Select the desired MIP Creation Control (None, Default, Explicit) (See
Note 2)
Step 8 Select OK
If Format Type String or DNS Name is selected, allowed characters

are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not
PS
allowed. If Format Type MAC-Integer is selected, the entry must be

Note Hexadecimal characters.
MIPs are not created explicitly via eVision. For information on MIP
PS
rules see Creating and Deleting MIPs on p. 74.

Note
Step 9 Expand the Maintenance Domain entity in the selection tree.

The new Maintenance Domain ID is present in the selection tree
Step 10 Select the new Maintenance Domain ID and verify the entry.
Current Status Then
Are changes other than Level required to Enter a right click on the MD ID
the MD? and select Edit Configuration.
Enter the desired changes and
select OK.
Is a change to the Level required? Enter a right click on the MD ID
and select Delete and then
select OK. Then go to Step
and re-enter the appropriate
MD ID options.
Is the MD information correct? Continue with the next step.

Create a Maintenance Association (MANET).

Step 12 Right click on a Maintenance Domain ID in the selection tree and
select Create MANET.
A Create Maintenance Association - Network screen displays
Figure 356: Create Maintenance Association Window
Step 13 Enter/select the following MANET options:
Enter the desired MANET Index (1-64)
Select the desired name Format Type (Primary VID, String, Integer,
VPN ID, ICC Format)
Enter the MA Name contents (See Note)
Select the desired CCM Interval (3.3 Milliseconds, 10 Milliseconds,
100 Milliseconds, 1 Second, 10 Seconds, 1 Minute, 10 Minutes)
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.
Step 14 Select OK

If Format Type String or ICC Format is selected, allowed characters
PS
are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not
allowed.
Note
Step 15 Expand the Maintenance Domain ID in the selection tree.

The new Maintenance Association ID is present in the selection tree
Step 16 Select the new Maintenance Association ID and verify the entry.
Step 17 If additional MANETs are required for the same Maintenance Domain
ID, repeat Step 12 through Step 14.
Current Status Then
Are Format Type, MA Name, CCM Interval Enter a right click on the MA
or MEP Member List changes required to ID and select Edit
the MA? Configuration and make the
required changes, then select
OK.
No changes are necessary Continue with the next step.
Create a Maintenance Association Component (MACOMP)

Step 19 Expand the MD entity in the selection tree, right click on the associ-
ated MANET entity in the selection tree and select Create MACOMP.
A Create Maintenance Association - Component screen displays
Figure 357: Create Maintenance Association - Component
Step 20 Enter/select the following MACOMP options:

Select the desired Associated Port (Drop-down list)
Enter the Primary VID number (Primary VLAN ID, 0-4095)
Select the desired MIP Creation Control (None, Default, Explicit,
Defer)
Step 21 Select OK

Create a Maintenance End Point (MEP)

Step 22 Expand the NE-1 and NTE entities in the selection tree.
Step 23 Right click on the interface port identified in the MACOMP and select
Create MEP.
A Create Maintenance Domain End Point screen displays
Figure 358: Create MEP

Step 24 Enter/select the following MEP options:

Identification
Select the desired MANET ID (Drop-down list)(see note)
Select the desired MEP Index (Drop-down list)
State
Select the desired Administrative State (IS, Management, Disabled)
Configuration (General)
Select the desired Direction (Drop-down list)
Enable/Disable CCM Generation (Drop-down list)
Select the desired VLAN Priority (Drop-down list)
Enter the desired VLAN Ethertype (Default - 8100)(in Hex)
Select the desired Fault Alarm Priority (Drop-down list)
Select the desired Primary VID (Primary VLAN ID) (Drop-down list)
Select the desired LLF Triggers, if any (Check boxes) (see caution)
Configuration (AIS)
Select the desired AIS Generation status
If the AIS Generation status selected was “Enabled”, select the
desired AIS Triggers, Transmission Period, Priority and Client MD
Level.
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
Step 25 Select OK
Although the MEP Index appears above the MANET ID in the GUI
PS
display, the MANET ID determines what MEP Indexes are available,

so the MANET ID must be selected first.
Note
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
CAUTION
without intervention.
Step 26 Expand the associated Maintenance End Point entity interface in the
selection tree.
The new MEP is present in the selection tree
Step 27 Select the new MEP and verify the entry.


Current Status Then
Are changes other than MEP Direction Enter a right click on the MEP
required to the MEP? and select Edit. Select the
desired changes and select
OK.
Are MEP Direction changes required to Enter a right click on the MEP
the MEP? and select Delete and then
MA ID options.
No changes are necessary. Continue with the next step.

Current Status Then
Is it desired to create VLAN Entries for the Continue with the next step.
port associated with this MEP?
Otherwise Go to Step 33.
Create VLAN Entries.

Step 30 Right click on the desired access/network port and select Create
VLAN Entry.
A Create VLAN Entry screen displays
Figure 359: Create VLAN Entries

Step 31 Enter the following VLAN Entry options:

Enter the Primary VID number
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.
Step 32 Select OK.
If creating a VLAN entry on an access port with no MEP(s) assigned,

a Default MD is created. The Default MD has an MD level of -1, which
indicates an invalid MD. This MD level defaults to the System Default
MD Level unless it is edited to another level.
PS
To edit the Default MD Level and/or the MIP Creation Control, right
Note click on the access port and select “Edit Default MD Level”, then
select the desired MD Level and/or MIP Creation Control settings
from the drop-down lists and select OK.
Step 33 Select the access port associated with the VLAN entry in the selection
tree.
The VLAN data is displayed
a) If the VLAN data requires editing, right click on the interface and
select Edit VLAN Entry, click the “Edit” radio button for the VLAN
entry to edit and edit the VLAN data, then select OK.
b) To delete the VLAN entry, right click on the interface and select
Delete VLAN Entry and then select the delete button for the
desired entry and select OK.
c) To display the Default MD Level, click on the Default MD Level
tab. (see note at step 18)
The Default MD data is displayed
d) To edit the Default MD Level, right click on the access port and
select Edit Default MD Level, then select the desired MD Level
and MIP Creation Control setting and click on OK.
e) To display the CFM N2A Shaper data, click on the Shaper tab.
The CFM N2A Shaper data is displayed
f) To edit the Shaper data, right click on the access port and select
Edit Shaper, then enter the desired values for CIR and Buffer
Size and click on OK.


Current Status Then
Are changes other than MEP Direction Enter a right click on the MEP
required to the MEP? and select Edit. Select the
desired changes and select
OK.
Are MEP Direction changes required to Enter a right click on the MEP
the MEP? and select Delete and then
MA ID options.
No changes are necessary. Continue with the next step.
Step 35 If additional MEPs are required for another Maintenance Association

ID, repeat Step through Step 34.
Step 36 If additional Maintenance Domains, and their associated MD IDs and
MEPs are required, repeat Step through Step 35.
Step 37 Select the maintenance application, expand the tree to see the selec-
tions 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.
Step 38 Repeat Step through Step 37 for each node to be set up for Connec-
tivity Fault Management.
Current Status Then
Do you wish to initiate a Loop Back Continue with the next step.
Message (LBM)?
Do you wish to initiate a Link Trace Go to Step .
Message (LTM)?
Is no further action required at this End of Procedure
time?
Initiate a Loop Back Message (LBM)

Step 40 Expand the Maintenance End Point entity in the selection tree.
Step 41 Right click on the associated MEP interface in the selection tree and
select Loopback.
A Loopback screen displays

Figure 360: Configure Loop Back Message

Step 42 Enter/select the following options:

Select the desired Destination Type (Drop-down list)
Select the desired Destination ID (Drop-down list)
Enter the Number of LBMs to be transmitted
Enter the number of padding bytes in the Data TLV
Select the desired Data Pattern (Drop-down list)
Select the VLAN Priority (Drop-down list)

Enable/Disable VLAN Drop Eligible (Drop-down list)
Step 43 Select Start Loopback.
Before running Loopback, ensure that the Administrative State of the

PS
MEP is IS.
Note
Initiate a Link Trace Message (LTM)

Step 45 Expand the Maintenance End Point entity in the selection tree.

Step 46 Right click on the associated MEP interface in the selection tree and
select Linktrace
An Linktrace screen displays
Figure 361: Configure Link Trace Message
Step 47 Enter/select the following options for Link Trace:
Select the desired Destination Type (Drop-down list)
Select the desired Destination ID (Drop-down list)
Enter the desired TTL
Enable/Disable Use FDB Only (Drop-down list)
Edit the Egress ID if desired
Step 48 Select Start Linktrace.
Before running Linktrace, ensure that the Administrative State of the

PS
MEP is IS.
Note
Step 49 Select the MEP Configuration tab and verify the status
For LTM, click on the LTR Database tab to view the Link Trace Reply
database.

Figure 362: MEP Display Configuration Window

Step 50 Troubleshoot and edit any issues, as required.
End of Procedure

Etherjack® Connection Performance

Analyzer
The Etherjack® Connection Performance Analyzer (ECPA) provides a subset of
Ethernet test equipment functions embedded directly into the port circuitry so
that each individual Access or Network port can act as its own “test equipment”.
This provides a means to test EVC connectivity and verify service conformance
from a remote location without the need for external test equipment.
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
CAUTION
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.
Refer to the following procedures to initiate an Etherjack® Connection Perfor-
mance Analyzer (ECPA) routine on an Access facility:
• Run Untagged ECPA Test on an Access Facility
• Run VLAN ECPA Test on an Access Facility
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 fol-
lowing figure.

Figure 363: Edit ECPA Test Streams Window

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 perform-
ing 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 364 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 Dura-
tion or Frames as appropriate) and ECPA test stream assignments are also
selected and edited from this window.

Figure 364: ECPA Set Configuration Window (Flow VLAN)
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 but-
tons located at the top of the ECPA view. See Figure 365 for the location of the
ECPA First Frame buttons. See Figure 366 for an example of ECPA First Frame
results.
Figure 365: ECPA Test Results Window

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 366.
Figure 366: ECPA First Frame from ECPA Results Window

Run Untagged ECPA Test on an Access Facility

The following procedure describes the ECPA Test feature.
Running an Untagged ECPA test on an Access facility is a Service
Affecting procedure. If customer traffic is present, ensure that the fol-
lowing procedure is performed during a scheduled Maintenance Win-
dow. Creating a VLAN loopback and running a VLAN ECPA test is not
Service Affecting, as long as the test rate does not exceed the avail-
CAUTION
able bandwidth for customer traffic, and as long as the customer is
not using the same VLAN.
Procedure
Step 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.
Step 2 Select Maintenance view, right click on “System” in the selection tree
and select Edit ECPA Streams.
An Edit ECPA Streams window appears

Step 3 Select ECPA Stream-1.

Name
Edit the Name if desired
Configuration
Select the desired Payload Type
Enter the Frame Size (in Bytes)
Enter the desired Rate (in bps)
Enter the MAC Source Address
Enter the MAC Destination Address
Enable/Disable Use Source Port Source MAC
Select the desired IP Precedence
If IP Precedence is TOS or DSCP, select the desired IP Priority
Select the desired IP version
Enter the IP Source Address
Enter the IP Destination Address
VLAN Configuration
Leave the VLAN Configuration entries unselected
Step 4 Select OK
The maintenance status window appears
Step 5 Select the ECPA Streams tab to verify ECPA Stream entry.
Step 6 Place the Access facility in the Maintenance state.
Step 7 Right click on the NTE entity (NTE11x) in the selection tree and select
Run ECPA.
An ECPA Status window appears
Step 8 Select the “Set Configuration” button.
An ECPA Set Configuration window appears
Step 9 Select the desired Source Port
Select “Maintenance” for the Administrative State
Select the desired Injector Type
Select the desired Monitor Type
Select the desired Test Type
If applicable, verify or edit the Test Duration
If applicable, verify or edit the Test Frames
Select the desired Test Stream for Test Stream A (Stream-1 was con-
figured in step 2)
Step 10 Select OK
Step 11 Verify the Administrative State of the facility is in the Maintenance
state.

Step 12 Select the “Start Test” button to start the ECPA test.
ECPA Test Status changes to “In Progress”
Step 13 Observe the test status.
Step 14 Select Stop Test when desired, or wait until the test has completed.
Step 15 View completed ECPA test results
Step 16 Select “Set Configuration” and select “IS” for the Administrative State.
Select Apply
The Administrative State changes to IS
Step 17 Verify the restoration of the facility. Select OK
The ECPA status window appears
Step 18 Review the ECPA test results.
Step 19 If desired, retrieve the first frame received by selecting the desired
ECPA First Frame tab
The ECPA first frame received data is displayed
Step 20 Remove the local or remote loopback.
End of Procedure
Run VLAN ECPA Test on an Access Facility
Procedure
Step 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.
Step 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)
Step 3 Select Maintenance view, right click on “System” in the selection tree
and select Edit ECPA Streams.
An Edit Streams window appears

Step 4 Select the desired ECPA Stream and enter/select the following con-
figuration options:
Name
Edit the Name if desired
Configuration
Select the desired Payload Type
Enter the Frame Size (in Bytes)
Enter the desired Rate (in bps)
Enter the MAC Source Address
The rate should not exceed the facility/path rate, including overhead
PS
bytes.
Note
If required, enter the MAC Destination address

The destination MAC address needs to be specified if the packets
may be traversing a network that has many switches, or if the
configuration uses a MAC-enabled management tunnel. In order to
PS
ensure that the packet reaches the proper destination, the destination
MAC address must be supplied here, and destination/source address
Note
swapping must be requested as part of the loopback at the other end.
Enable/Disable Use Source Port Source MAC

Select the desired IP Precedence
If IP Precedence is TOS or DSCP, select the desired IP Priority
Select the desired IP version
Enter the IP Source Address
Enter the IP Destination Address
VLAN Configuration
Select the desired VLAN Configuration options (Outer VLAN,
InnerVLAN1, Inner VLAN2) and edit the Ethertype and Tag informa-
tion as needed.
Step 5 Select OK.
The maintenance status window appears
Step 6 Select the ECPA Streams tab and stream number tab to verify ECPA
Stream entry.
Step 7 Place the Access facility in the Maintenance state.
Step 8 Right click on the NTE entity (NTE11x) in the selection tree and select
Run ECPA.
Step 9 Select Set Configuration.
An ECPA Set Configuration window appears

Step 10 Select “Access-1” for Source Port

Select “Maintenance” for Administrative state
Select the desired Injector and Monitor points
Select the desired Test Type (Duration, NumFrames or Continuous)
If Test Type is Duration, edit the Test Duration
If Test Type is NumFrames, edit the Test Frames
Select the desired Test Stream number (or “None”) for each Test
Stream
Step 11 Select OK
The Port Administrative State changes to the Maintenance state
Step 12 Verify the Administrative State of the facility is in the Maintenance
state. Select Start Test.
The ECPA Test Status changes to “In Progress”
Step 13 Observe the test status.
Step 14 Select Stop when desired (if TestType is Continuous), or wait until the
test has completed.
Step 15 View completed ECPA test results.
Step 16 Select Set Configuration and select “IS” for the Administrative State.
Step 17 Select Apply.

The Administrative State changes to IS
Step 18 Verify the restoration of the facility and select OK.
The ECPA status window appears
Step 19 Review the ECPA test results.
Step 20 If desired, retrieve the first frame(s) received.
Step 21 Select the desired ECPA First Frame tab.
The ECPA first frame received data is displayed
Step 22 Remove the local or remote loopback.
End of Procedure


Supported in all FSP150CC GE11x products, the Service Activation Testing
(SAT) based on ITU Y.1564 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 test includes
two key sub-tests: the service configuration test and the service performance
test, which are performed in order.
Provisioning level user permission using evision.
Refer to to determine the default values, value ranges and rules for each option
in the following procedure
Procedure
Perform the following at Site A (SAT Control End):

ration from the Application menu. Expand System, NE-1 and NTE11x
entities in the Selection Tree.
Step 2 Right click on a desired Access Port and provision a flow (EPL or
EVPL) (see Provision Access Port Services on p. 255). Set the
Administrative State to IS. Click OK to save the settings.

Figure 367: Provision EVPL Flow for Testing

Step 3 From the Connectivity Fault Management application, create an Up

Maintenance End Point (MEP) (see CFM Provisioning and Operation
on p. 502) on the port where the service is provisioned in the step
above. The figure (Figure 354 on p. 500) below shows an Up MEP
created on E1000-A-3 port.
The SAT Test Stream will use local MEP’s MAC address as its source
PS
MAC address. The local MEP is used to negotiate with the remote
SAT Responder and run delay measurement.
Note

Figure 368: Up MEP on Associated Port
Perform the following step at Site B (SAT Responder End): FSP 150CC-GE11x R6.1 80000026494 Issue: A, © 2013 ADVA Optical Networking SE - Confidential
Step 4 Repeat the above steps at Site B.
Make sure that the CFM settings at Site A and Site B are the same
PS
and the Up MEPs at two sites form a pair.

Note
The destination MEP at Site B is created for the test stream and is
PS
used to negotiate with the local MEP and run delay measurement.
Note
Step 5 Connect the E1000-N-1 ports at Site A and Site B with a cable.

Perform the following at Site A:
Create SAT Control

Step 6 Select the Service Activation Testing Application on the tool bar or
select Service Activation Testing from the Application menu. Expand
the System in the selection tree pane by clicking the “+” sign.
Step 7 Enter a right click on NE-1 and select Create SAT Control.
A Create SAT Control screen displays
Figure 369: Create SAT Control

Step 8 Select/Enter the following SAT Control options:

a) Enter a desired Name for the SAT Control
b) Select the Test Mode
When SAT Control works in “One Way” mode, the SAT Responder
Control option should be Enabled (see Table 83 on p. 758) in
PS
destination MEP, so that the SAT Responder End is capable of

exchanging the control Protocol Data Unit (PDU) with the SAT Control
Note
End.
c) Enter the CIR Test Step Duration, CIR Test Step Number, Test
Duration and Performance Test Duration.
d) Select desired Test Procedures by ticking the checkboxes
Click on OK.
Step 9 Expand the newly created SAT Control entity in the Selection Tree
and select the Configuration tab in the Detail Pane to view the SAT
Control settings.

Figure 370: SAT Control Configuration View
Step 10 Right click on SAT Control and select Edit to make changes as
needed.
Edit SAC Profile
Step 11 From the SAT application, expand the System and SAC Profile enti-
ties.
Step 12 Right click on a SAT Profile ID and select Edit.
An Edit SAC Profile screen displays
Figure 371: Edit SAC Profile
Step 13 Enter the following options:

a) Enter a desired Name
b) Enter desired Frame Loss Rate (FLR), Frame Transmission
Delay (FTD) and Frame Delay Variation (FDV).
Click on OK.

Create SAT Test Stream

Step 14 Right click on SAT Control and select Create Test Stream.
A Create SAT Test Stream screen displays
Figure 372: Create SAT Test Stream

Step 15 Enter/Select the following SAT Test Stream options (refer to ):

Identification
a) Enter a SAT Test Stream Index
b) Enter a desired Name as the alias of this test stream
Configuration
c) Select the Port that is associated with the flow provisioned
d) Select the Local MEP ID associated with the Port
e) Select Destination MEP Type
f) Enter Destination MEP ID if MEP id is selected
g) Enter Destination MEP’s MAC Address if MAC Address is
selected
h) Select the Direction
i) Enter desired DMM Frame Size
j) Select DMM Interval
k) Select a desired Service Acceptance Criteria Profile
FLPDU
l) Enter the Destination MAC Address
m) Select the Payload Type

n) Enter Custom Payload if Payload Type is CUSTOM

o) Enter desired Frame Size List or click on EMIX or EMIX Default to
use a fixed frame size list.
Service
p) Select desired Color Mode
q) Select Use DEI option
r) Enter the same CIR, EIR, CBS and EBS as the flow to be tested
s) Enter Green PCP and Yellow PCP to be associated with the flow
COS
t) Select the desired Inner/Outer VLAN tag check box(es) to allow
tag entry, then enter the desired EtherType and VLAN Tag(s)
Click on OK.
The SAT Test Stream Configuration displays
Figure 373: SAT Test Stream View
Step 16 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.
Step 17 Repeat Step 14 and Step 15 for more Test Streams, if required.
System supports up to four Test Streams running at the same time

and the running test streams may belong to different flows under a
PS
same port or different COS (depending on VID and Priority) under a

Note same flow.

One Local MEP and one Destination MEP can apply to all the four
PS
Test Streams.
Note
Step 18 Initiate a Terminal Port loopback on the E1000-A-3 port on Site B if

“Two Way” Test Mode is selected in SAT Control.
Run SAT Test

Step 19 Right click on the SAT Test Stream ID and select Run to start the test
of a single stream.
A Run SAT Test Stream screen displays
Figure 374: Run SAT Test Stream

Step 20 Enter a right click on the SAT Control entity and select Run to start the
tests of all available streams.

Figure 375: Run SAT Control
When SAT Control works in “One Way” mode, a “Remote Initiated

PS
SAT” alarm will be raised once a test is started.

Note
Step 21 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 part in Run SAT Test Stream screen displays the test
progress, details and result associated with the test stream
Figure 376: SAT Test Status (Run SAT Test Stream)
The Run SAT Control screen displays the general test status, prog-
ress and overall result of each test stream

Figure 377: SAT Test Status (Run SAT Control)
Step 22 If the test needs to be terminated, click on Stop Test.

Step 23 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, or click the test stream and select the Test Result tab in the
Detail Pane.
Figure 378: SAT Test Result View
Only the test result of green packets will be compared against Service
PS
Acceptance Criteria (SAC) parameters.

Note
Frame Loss Ratio (FLR), Max Frame Transmission Delay (Max FTD)
and Max Frame Delay Variance (Max FDV) will be compared against
PS
the FLR, FTD and FDV set in SAC Profile. If any one of these
Note parameters cannot match with SAC criteria, a test will fail.

Step 24 Troubleshoot the parameter settings in flows, test streams and CFM
entities if a test fails.
There is a possibility that the FLR and FL Count for yellow packets
show extremely large values in EIR or Policing test result when Color
Mode is set to Color Aware. This is because the Responder end
PS
received more yellow packets than what the Control end sent. User
Note can troubleshoot this problem by balancing the CIR settings in the
test stream and the associated flow.
Step 25 Click on Export to save the test result as a .csv file to a specified
directory.
Figure 379: Export SAT Test Result
End of Procedure

FSP 150CC-GE11x R6.1 80000026494 Issue: A, © 2013 ADVA Optical Networking SE - Confidential Chapter 6 Etherjack Test Procedures and Performance Monitoring

534

Chapter 7
Alarms, Events and Probable

Causes, Error Codes
Introduction
This chapter contains information supporting alarms and events generated by

the system, their meaning and suggested trouble clearing methods. This chap-
ter contains the following information:
• Recommended Steps for Trouble Clearing
• Obtaining Technical Assistance
• Alarm Attributes, Probable Cause and Trouble Clearing
• Alarm Masking
• Error Codes and System Responses
Recommended Steps for Trouble Clearing

In the event that alarms are raised after commissioning the FSP 150CC-GE11x,
this procedure is provided to assist maintenance personnel in identifying the
probable cause and clearing the alarm.
The following procedure lists the steps to identify, isolate, and correct conditions
that cause alarms reported in eVision Alarm Window.
Procedure
Step 1 Ensure that an interface device, such as a craft interface, is con-

nected to the network and is operating correctly before continuing.
Step 2 Establish a communication connection to the FSP 150CC(s) and log
on. See Logging On and Off on p. 194.

Recommended Steps for Trouble Clearing
Step 3 Observe the Alarms Pane to view all current alarms, and record the
alarm severity. See Getting Familiar with eVision on p. 197 for an
overview of the eVision web browser management tool components
and the location of the Alarm Window.
Step 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.
Step 5 Locate the appropriate alarm indication description and suggested
troubleshooting techniques for the specific problem.
Step 6 Refer to Alarm Attributes, Probable Cause and Trouble Clearing on
p. 537 for identifying, interpreting, and troubleshooting alarms.
Step 7 Refer to Connector and LED Descriptions on p. 114 for descriptions
of connectors and front-panel LED indications.
Step 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).
Step 9 Repeat Step 5 and Step 6 for all alarms.
Step 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).
Step 11 Log off all FSP 150CCs when finished.
End of Procedure

Chapter 7 Alarms, Events and Probable Causes, Error Codes
Obtaining Technical Assistance

Product Maintenance Agreements and other customer assistance agreements
are available for ADVA Optical Networking products through your ADVA Optical
Networking distribution channel. Technical support is available to warranty or
maintenance contract customers who need technical assistance with an ADVA
Optical Networking product that is under warranty or covered by a maintenance
contract. For more information, see Obtaining Technical Assistance on p. 34.
Alarm Attributes, Probable Cause and

Trouble Clearing
All problems causing an alarm event are soaked for 2.5 seconds before the
alarm indication is raised. The problem causing the alarm event must clear for
10 seconds before the alarm indication is cleared. All FSP 150CC System
alarms and default notification codes are shown in Table 28. For all FSP 150CC
Access and Network alarms, see Table 30. For Maintenance End Point (MEP)
alarms, see Table 5-21. Each of the following tables contain a description of the
alarm condition, probable cause and suggested trouble clearing procedure. To
clear alarm conditions, it is suggested that you start by using the trouble clearing
procedure in Recommended Steps for Trouble Clearing on p. 535.
Alarm Profile Notification Codes

The user has the ability to retrieve and edit alarm profile Notification Codes. To
modify alarm Notification Codes for a given alarm condition type using eVision,
select Maintenance view, right click on the desired entity in the Selection Tree
and select Edit Alarm Attributes. The options available for notification codes are:
Critical, Major, Minor, Not Alarmed or Not Reported. For LED locations associ-
ated with an alarm condition, refer to Connector and LED Descriptions on
p. 114. Valid Notification Codes are provided in the following table.

Alarm Attributes, Probable Cause and Trouble Clearing
Table 27: Alarm Profile Notification Codes

Notification
Description
Code
CR Critical - A severe, service-affecting condition has occurred
and that immediate corrective action is imperative.
MJ Major - A serious disruption of service or a malfunction or
failure of an important system function.
MN Minor - Trouble that does not have a serious effect on service
to customers or for trouble in functions that are not essential
to the NE operation.
NA Not Alarmed - A condition that is reported only as an event
and can be retrieved from the system.
NR Not Reported - A condition that is not reported but can be
retrieved from the system.
CL Clear - This value can not be used in an alarm profile. Used
with event reporting only.
Alarms and Events

Refer to the following table for system alarm conditions and their associated
probable cause, default Notification Code and suggested trouble clearing proce-
dure. System components include the following subsystems:
• System
• Network Element
• PSE (GE114H/GE114PH)
• Synchronization (GE114S/GE114SH)
• Precision Time Protocol (PTP) Alarms (GE114S/GE114SH)
• Network Port and Access Port Alarms
• CFM Maintenance End Point Alarms
• CFM QoS Shaper Alarms
• LAG Alarms
• SAT Responder Session Alarms
• ERP Alarms (GE114x)

Table 28: System Alarms and Events

eVision GUI Description / NSA Default SA Default LED

Trouble Clearing Procedure
Condition Type Probable Cause Notification Notification Indication
System
Backup NTP Attempt to connect to the Backup 1) Verify that the IP address can be
Server Failed NTP Server failed.1 reached (respond to pings) by performing
both a ping and a trace route from the
management tunnel’s IP address.
2) Verify management communication
configuration. Minor N/A N/A
a) Target IP address connectivity a) Repair IP address connectivity or
or routing problem. routing problem.
b) No NTP server / NTP server b) Switch to Primary NTP Server. Repair
down. NTP server.
Data Base - File Database file transfer is in No action required.

Not
Transfer In progress. N/A N/A
Reported
Progress
DB Downgrade Database Downgrade - 1) Verify that this database contains the
implementation of a database file desired data. Not
N/A N/A
below the current release level. 2) If required, obtain latest database file, Reported
otherwise - No Action Required.
File Transfer In File transfer is in progress. No action required. Not
N/A N/A
Progress Reported
IP Address IP Address Conflict (declared Verify management communication
Conflict when a DHCP assigned address configuration. N/A CR N/A
overlaps with an existing subnet)
IPv6 Address IPv6 Address Conflict (declared Verify management communication
Conflict when a DHCPv6 assigned configuration
N/A CR N/A
address overlaps with an existing
subnet)
539
Table 28: System Alarms and Events (Continued)
540

LTP Fail Low Touch Provisioning process Check access to installation network
failed DHCP server, Boot CFG file and/or next
server information.
N/A MJ N/A
If problem can not be resolved, user can
provision the unit manually.
LTP In Progress Low Touch Provisioning is in No action required.
N/A N/A N/A
process
Operation In Operation is in progress. No action required. Not
N/A N/A
Progress Reported
Primary NTP Attempt to connect to the Primary 1) Verify that the IP address can be
Server Failed NTP Server failed.1 reached (respond to pings) by performing
both a ping and a trace route from the
management tunnel’s IP address.
2) Verify management communication
configuration. Minor N/A N/A
a) Target IP address connectivity a) Repair IP address connectivity or
or routing problem. routing problem.
b) No NTP server / NTP server b) Switch to Backup NTP Server. Repair
down. NTP server.
SNMP Dying Database or Network issue. Check database settings for SNMP Dying
Gasp - Host Gasp. If correct, test network access - Minor N/A N/A
Unreachable Ping the Host address.


SNMP Dying SNMP Dying Gasp is enabled on Check database settings for SNMP Dying
Gasp - multiple trap hosts and there is Gasp. Delete extra port assignments.
Resource Busy reachability to these trap hosts via
the same interface. On a 1+1
Network Interface, there can only
be a single SNMP trap host with
SNMP Dying Gasp Enabled.
Enabling a second trap host for
SNMP dying gasp raises the
alarm.
Minor N/A N/A
OR -There are multiple
management tunnels active
(Network side is unprotected with

tunnel, Access side also has
tunnel). 2 SNMP trap hosts that
resolve to 2 different interfaces are
supported. Enabling SNMP Dying
Gasp on a third trap host raises
the alarm.
SWDL - Software Download activation is in No action required.
Not
Activation In progress. N/A N/A
Alarmed
Progress
SWDL - File Software Download file transfer is No action required.
Not
Transfer In in progress. N/A N/A
Reported
Progress
SWDL - Software Download installation is No action required.
Not
Installation In in progress. N/A N/A
Reported
Progress
SWDL - Software Download validation is in No action required.
Not
Validation In progress. N/A N/A
Alarmed
Progress
541
542

Network Element
3G USB Modem
Link Down Link Down is generated when a Perform an Etherjack Diagnostic test.
physical connection is lost on the Repair the port using test results. N/A N/A N/A
port.
No SIM Card No SIM card is detected. Unplug the 3G modem, insert the SIM
card into the modem, and re-insert the N/A N/A N/A
3G modem into the USB port.
Modem is not The modem is not qualified by Install an ADVA Optical Networking
N/A N/A N/A
qualified ADVA Optical Networking. qualified 3G modem.
Modem 3G modem is removed from the Re-insert ADVA Optical Networking
N/A N/A N/A
Removed USB port. qualified 3G modem.
DCN Port
Link Down Cable disconnected, cable fault, Check physical cabling, MDIX is not
improper configuration. supported on DCN port. Check settings
on system to match DCN network Not
N/A N/A
requirements. Alarmed
NTE11x Shelf
Over Equipment has exceeded the Check ambient temperature and adjust.
Temperature temperature limit (>= 90 C). Verify that airflow requirements are met.
Status
See Air Flow Requirement in FSP 150CC Minor N/A
Red
GE11x R6.1 Technical Descriptions
document.
Under System temperature has dropped Check ambient temperature and adjust.
Temperature below the minimum temperature Status
Minor N/A
threshold Red
(<= -50 C).


NTE11x Card
Communication Communication Failure Equipment is malfunctioning. Repair or
Minor N/A N/A
Failure replace unit.
Equipment Does Equipment does not match the Verify the provisioning against the Status
Not Match provisioning. equipment. Re-provision as necessary. N/A Critical Blinking
Provisioning Red
Equipment Fault Equipment fault found. Equipment is malfunctioning. Repair or Status
N/A Critical
replace unit. Red
Equipment Equipment is provisioned but Replace equipment or place out of
Provisioned But equipment is removed. service. N/A Critical N/A
Removed
Test Alarm A test alarm is generated to check Ensure alarm propagates properly.
Major N/A N/A
alarm propagation.

Power Supply (PSU) - GE114H/GE114SH/GE114PH
Communication Communication failure. Communications malfunction between
Failure PSU and FSP 150CC. Replace PSU. If
that does not clear the problem, call Minor N/A N/A
ADVA Optical Networking Technical
Support.
Equipment Does Equipment does not match the Verify the provisioning against the Status
Not Match provisioning. equipment. Re-provision as necessary. Minor N/A Blinking
Provisioning Red
Equipment Fault Power Supply Unit power failure. Equipment is malfunctioning. Repair or Status
Minor N/A
replace PSU. Red
Equipment Equipment is provisioned but Replace equipment or place out of
Provisioned But equipment is removed. service. Minor N/A N/A
Removed
Power: No Input Power: No power input or unit Verify power supply input. Adjust power
Status
or Unit Fault fault. supply input to acceptable level or Minor N/A
Red
replace PSU.
543
544

PSE (GE114H/GE114PH)
PSE Group
pse-power-thres PSE Power Threshold Exceeded Check the PoE power budget and
Major N/A N/A
hold-exceeded s consumption for GE114PH.
pse-power-fail PSE power chip Communication Check the hardware of PSE sub-module.
Major N/A N/A
failed
PSE Port
pse-poweroff-ov PSE power off due to over current Check the maximum power allowed by POE
ercurrent the Port/interface. Major N/A Status
RED
pse-poweroff-ov PSE power off due to over voltage Check the hardware of pluggable PSU. POE
ervoltage Major N/A Status
RED
pse-poweroff-ov PSE power off due to over load Check the PoE port output power POE
er classification/allocation of PD. Major N/A Status
RED
pse-poweroff-ov PSE power off due to over Check the hardware of PSE sub-module. POE
ertemp temperature Major N/A Status
RED
pse-poweroff-sh PSE power off due to short circuit 1 Check the cable between PSE port
ort and the related Powered device.

POE
2 Check the hardware of the related Major N/A Status
PD. RED
3 Check the hardware of PSE port


10MHz (CLK) Port/Pulse Per Second (PPS) Port/Time Of Day (TOD) Port
QL Squelch Quality Level Squelch. The port is Verify and troubleshoot clock reference.
squelched due to the system's QL Make sure the system’s QL is higher than
being lower than the port's the port QL.
configured Squelch QL attribute.
The port's QL Mode attribute must Minor N/A N/A
be configured as enabled and the
Squelch QL attribute must be
configured as anything besides
None for this condition to exist.
BITS In Port

Alarm Indication BITS Alarm Indication Signal. Verify and troubleshoot clock reference.
Signal Verify and troubleshoot possible signal
mismatch. In order for proper BITS-IN
and BITS-OUT inter-operate with source
equipment/test sets, the user must
manually match the FSP 150CC's
Network Clock Type with the BITS line
type. Not
N/A N/A
Reported
If a T1 is the desired BITS Line Type,
then Network Clock Type should be set to
"Option 2".
If a 2048kHz or E1 is the desired BITS

Line Type, then Network Clock Type
should be set to "Option 1".
545
546

Frequency Frequency Offset. The Verify and troubleshoot clock reference.
Offset synchronization circuit detected a
frequency offset problem with the
BITS-IN port's recovered clock.
The BITS-IN port must be assigned Minor N/A N/A
and the BITS-IN port must be a
member of the system clock
selector list for this condition to
exist.
Loss of Frame BITS Loss of Frame Verify and troubleshoot clock reference.
Verify and troubleshoot possible signal
mismatch. In order for proper BITS-IN
and BITS-OUT inter-operate with source
equipment/ test sets, the user must
manually match the FSP 150CC's
Network Clock Type with the BITS line
type.
Minor N/A N/A
If a T1 is the desired BITS Line Type,
then Network Clock Type should be set to
"Option 2".
If a 2048kHz or E1 is the desired BITS

Line Type, then Network Clock Type

should be set to "Option 1".
Loss of Signal BITS Loss of Signal. BITS signal is Verify and troubleshoot clock reference
Minor N/A N/A
lost. connection.
Sync QL Invalid Synchronization Quality Level Verify and troubleshoot clock reference.
Minor N/A N/A
Invalid.


Sync QL Synchronization Quality Level Verify and troubleshoot clock reference.
Mismatch Mismatch. The BITS-IN port
receives SSM messages whose
specified Quality Level is lower
than the Expected QL. The
BITS-IN port's QL Mode attribute Minor N/A N/A
must be configured as enabled
and the Expected QL attribute
must be configured as anything
besides None for this condition to
exist.
Sync Reference Synchronization Referencing Verify and troubleshoot clock reference.
Failed Failed. The BITS-IN port has failed
in such a way that its clock cannot

be recovered, thus preventing it
from being used as a Minor N/A N/A
synchronization reference (e.g.,
LOS). The BITS-IN port must be
assigned for this condition
primitive to exist.
Sync Reference A forced switch operation has Evaluate reason for forced switch
Forced Switch been performed on a Sync operation and when appropriate, remove Minor N/A N/A
Reference. the forced switch.
Sync Reference A Sync Reference has been Test the Locked Out Sync Reference and
Locked Out locked out. Usually due to failure, remove lock out when reference is fully
Minor N/A N/A
configuration changes planned or functional again.
maintenance operations.
Sync Reference A manual switch operation has Evaluate reason for the manual switch
Manual Switch been performed on a Sync operation. Minor N/A N/A
Reference.
Sync Reference A Sync Reference has been No Action Required.
Minor N/A N/A
Wait To Restore restored and is in WTR timing.
547
548

BITS Out Port
QL Squelch Quality Level Squelch. The Verify and troubleshoot clock reference.
BITS-OUT port is squelched due Make sure the system’s QL is higher than
to the system's QL being lower the BITS-OUT port QL.
than the BITS-OUT port's
configured Squelch QL attribute.
The BITS-OUT port's QL Mode Minor N/A N/A
attribute must be configured as
enabled and the Squelch QL
attribute must be configured as
anything besides None for this
condition to exist.
GPS (GE114SH)
GPS Antenna GPS Antenna Fail. This condition Connect the GPS antenna with the cable
Fail may be reported during normal directly or shorten the cable length.
GPS Receiver operation when
Minor N/A N/A
active antenna draws less current,
in such cases like connection with
splitter or long antenna cable.
Time Reference Time Reference has been locked Perform “clear lock out” command to
Locked Out out. This alarm is reported only clear this alarm.
Minor N/A N/A
due to the external command “lock
out”.
Time Reference Time Reference is not available. Verify and troubleshoot time reference.
Minor N/A N/A
Unavailable
Time Reference Time Reference is available and No action necessary.
Unavailable Wtr enters Wait-to-Restore state Minor N/A N/A
before recovery.


SYNC-1-1-1-1
All Input Sync All synchronization references in Verify and troubleshoot clock reference.
References the system clock selector list have
Failed failed. The system clock selector
Major N/A N/A
list must have at least one member
in order for this condition primitive
to exist.
Average Clock was not synced long enough No action necessary.
Holdover to enter holdover and is now Not
N/A N/A
Frequency Not freerunning. Reported
Ready
Sys Clock Mode System Clock Mode - Fast No action necessary.
- Fast Acquisition Synchronization. This
Not

Acquisition indicates the clock selector is N/A N/A
Reported
acquiring the phase of the selected
reference.
Sys Clock Mode System Clock Mode - Free Verify synchronization provisioning to
- Freerunning Running Synchronization. This ensure option is set correctly. Otherwise, Not
N/A N/A
indicates the internal oscillator is no action is necessary. Reported
the source of the system clock.
Sys Clock Mode System Clock Mode - Holdover Verify and troubleshoot clock reference.
- Holdover Synchronization. This indicates the
selected reference is invalid and
Not
no other valid input reference is N/A N/A
Reported
available and the system clock has
previously locked to the now
invalid reference.
549
550

Sys Clock Mode System Clock Mode - Loss of Lock. Verify and troubleshoot clock reference.
- Loss of Lock This indicates the selected
reference had locked and is not
invalid and the lock has been lost. Not
N/A N/A
While in this state, the clock Reported
selector will be attempting to
acquire the phase of the selected
reference.
Time Clock (GE114SH)
Time Clock Not Time Reference Locked Out. No action necessary.
Minor N/A N/A
Locked
Time Frequency Time Clock Time Traceability No action necessary.
Minor N/A N/A
Lock status is Time Frequency Lock.
Time Frequency Time Clock Frequency No action necessary.
Not Traceable Traceability status is Not Minor N/A N/A
Traceable.
Time Holdover Time Clock Time Traceability No action necessary.
Minor N/A N/A
status is Holdover.
Time Not Time Clock Time Traceability No action necessary.
Minor N/A N/A
Traceable status is Not Traceable.
1. When 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.
Precision Time Protocol (PTP) Alarms (GE114S/GE114SH)

Refer to the following table for Precision Time Protocol (PTP) alarm conditions and their associated probable cause,
default notification code and suggested trouble clearing procedure.
Table 29: PTP Alarms

Description / NSA Default SA Default LED
Condition Type Trouble Clearing Procedure
Probable Cause Notification Notification Indication
SOOC
PTSF - Loss Packet Timing Signal Fail - Loss Announce. Verify and troubleshoot clock
Announce Announce is not received before reference.
announceReceiptTimeout.
Release loopback. Minor N/A N/A
A loopback on the port on which the PTP
Flowpoint of the SOOC exists will result in a
PTSF - Loss Announce.

PTSF - Loss Packet Timing Signal Fail - Loss of Syn- Verify and troubleshoot clock
Sync chronization. A Sync/Followup is not reference.
received before syncReceiptTimeout or
Delay Response is not received before del-
RespReceiptTimeout. Minor N/A N/A
A loopback on the port on which the PTP Release loopback.

Flowpoint of the SOOC exists will result in a
PTSF - Loss of Sync.
PTSF - Packet Timing Signal Fail - Unusable. The Verify and troubleshoot clock
Unusable PTP packet stream is not usable for clock reference.
recovery. For example, unable to recover Minor N/A N/A
clock due to unacceptable PTP packet
PDV.
Telecom Slave
All SOOCs All Slave-Only Ordinary Clocks (SOOC) Verify and troubleshoot clock
Failed failed. The OC-S Virtual Port in a Faulty reference. N/A Critical N/A
state or a PTSF Alarm exists on the SOOC.
551
Table 29: PTP Alarms (Continued)
552

Frequency Frequency Offset. The synchronization Verify and troubleshoot clock
Offset circuit detected a frequency offset problem reference.
with the TS's recovered clock. The TS must
Minor N/A N/A
be assigned and the TS must be a member
of the system clock selector list for this
condition to exist.
Recovered Recovered Clock Not Holdover Quality. The Verify and troubleshoot clock
Clock Not recovered clock is yet to reach holdover reference. Not
N/A N/A
Holdover quality Reported
Quality
Sync QL Invalid Synchronization Quality Level Invalid. Verify and troubleshoot clock
Minor N/A N/A
reference.
Sync QL Synchronization Quality Level Mismatch. Verify and troubleshoot clock
Mismatch The TS receives SSM messages whose reference.
specified Quality Level is lower than the
Expected QL. The TS's QL Mode attribute
Minor N/A N/A
must be configured as enabled and the
Expected QL attribute must be configured
as anything besides None for this condition
to exist.
Sync Reference Synchronization Referencing Failed. The Verify and troubleshoot clock
Failed TS has failed in such a way that its clock reference.
cannot be recovered, thus preventing it

Minor N/A N/A
from being used as a synchronization
reference. The TS must be assigned for this
condition primitive to exist.
Sync Reference A forced switch operation has been Evaluate reason for forced
Forced Switch performed on a Sync Reference. switch operation and when
Minor N/A N/A
appropriate, remove the forced
switch.
Table 29: PTP Alarms (Continued)


Sync Reference A Sync Reference has been locked out. Test the Locked Out Sync
Locked Out Usually due to failure, configuration Reference and remove lock
Minor N/A N/A
changes planned or maintenance out when reference is fully
operations. functional again.
Sync Reference A manual switch operation has been Evaluate reason for the
Manual Switch performed on a Sync Reference. manual switch operation. Minor N/A N/A
Sync Reference A Sync Reference has been restored and is No Action Required.
Minor N/A N/A
Wait To Restore in WTR timing.
Telecom Slave Telecom Slave in Freerun. The recovered Verify and troubleshoot clock
Not
in Freerun clock is the same as the internal oscillator reference and provisioning. N/A N/A
Reported
and the Telecom Slave is in freerun.
Telecom Slave Telecom Slave in Holdover. The recovered Verify and troubleshoot clock
Not

in Holdover clock is in holdover as there is no valid reference and provisioning. N/A N/A
Reported
SOOC to support clock recovery.
553
Network Port and Access Port Alarms
554

Refer to the following table for Network Port and Access Port alarm conditions and their associated probable cause,
Table 30: Network Port and Access Port Alarms

Bandwidth Bandwidth Exceeds Negotiated Speed. Verify provisioning and adjust
Exceeds accordingly. Facility
Minor Major
Negotiated Speed Red
(Access Port only)
Duplex Mode of Duplex mode of the connected Determine the expected port
Far End Device equipment is unknown. The unit speed setting and ensure that
Unknown determined it cannot conclude both ends are configured to
negotiation with remote end on the reflect that setting. Facility
Minor Major
Ethernet port. Although auto Yellow
negotiation failure is a minor alarm, it is
usually followed by a critical alarm due
to link down.
EFM OAM - Dying Received an EFM OAM Dying Gasp Restore or repair connected Facility
Minor Critical
Gasp Received message. equipment. Red
EFM OAM - EFM OAM protocol discovery failure. Verify that the IP address can
Failure This notification is sent by the interface be reached and verify far end
unit when it is unable to establish EFM equipment EFM provisioning.
based peering with a remote unit (per

802.3ah standard).
Facility
a) Far end does not support EFM-OAM a) Set interface CPD to discard Minor Minor
Yellow
(IEEE 802.3ah). EFM-OAM.
b) Communications problem. b) Repair communications
problem.
c) EFM turned off (not set to Peer) at far c) Provision far end
end. equipment.
Table 30: Network Port and Access Port Alarms (Continued)


EFM OAM - Received an EFM OAM Critical Event Clear critical condition at that
Remote Critical indication. This alarm is sent when a far end.
Facility
Event NID receives an OAM-PDU from the Minor Minor
Yellow
remote end indicating a critical event
has occurred.
EFM OAM - The Link Loss Forwarding (LLF) feature At the far end, clear the fault
Remote Link is enabled and has been activated, and on the LAN port(s) that is
Down a Remote Link Down (RLD) EFM causing the transmission of
message has been received for a the RLD message.
Facility
specific interface. This message is sent Alternatively, the fault Minor Minor
Yellow
by the far end when an Access Port propagation feature can be
problem is detected. The alarm disabled at the near or far end.
specifies the far end Access Port(s) that
is experiencing a problem.

EFM OAM - Received an EFM OAM Remote Link Clear fault (Link Down or SFP)
Facility
Remote Link Status Indication. condition at the far end. Minor Minor
Yellow
Status
EFM OAM - Remote EFM OAM Loopback Failed. Verify remote end.
Remote Loopback (EFM OAM - Remote Loopback Failed
Failed alarm's provisionable severity levels
will never be declared. EFM OAM -
Remote Loopback Failed alarm can Facility
Not Alarmed Minor
only occur when a port is in the Yellow
Maintenance state, and the
Maintenance state forces an alarm to
be declared at NR regardless of
provisioned security level.)
ELMI Sequence Mismatch between CE and PE ends. Disable and enable EMI.
Number Mismatch This will occur if 3 consecutive Minor N/A N/A
messages are mismatched.
ELMI Not Status inquiry not received. Verify provisioning at both
Minor N/A N/A
Operating ends.
555
556

Frequency Offset1 Synchronization Frequency Offset. The Verify synchronization network
synchronization circuit detected a and provisioning.
frequency offset problem with the
Network Port or Access Port’s
Minor N/A N/A
recovered clock. The port must be
assigned and the port must be a
member of the system clock selector
list for this condition to exist.
Link Control Link control protocol (PPP) failed. Verify Network Port alarms at
Protocol Fail the far end.
a) Clear the Network Port
condition that caused the Link Minor Critical N/A
Loss Forwarding feature to
activate.
b) Disable fault propagation.
Link Control Link control protocol detected Remove loopback to clear
Minor Critical N/A
Protocol Loopback loopback. alarm.
Link Down Link Down is generated when a Perform an Etherjack Facility
physical connection is lost on a good Diagnostic test. Repair the port Red
link on the Ethernet interface port using test results. Minor Critical
(Access or Network). Link/Rate
Off
Link Down - Link Down is generated when a Test and repair far end
Facility
Auto-Negotiation physical connection is lost on a good equipment.
Red
Failed link on the Ethernet interface port
Minor Critical
(Access or Network). Auto negotiation
Link/Rate
fault indicates the Far End is not
Off
advertising its auto negotiation rate.


Link Down - Cable Link Down is generated when a Perform an Etherjack
Fault physical connection is lost on a good Diagnostic test. Repair the Facility
link on the Ethernet interface port cable using test results. Red
(Access or Network). A Cable Fault Minor Critical
notification is sent when it is Link/Rate
determined that the link is down due to Off
a cable fault on a copper (RJ-45) port.
Link Down - Cable Link Down is generated when a Insert or repair cable.
Removed physical connection is lost on a good
Facility
link on the Ethernet interface port
Red
(Access or Network). A Cable
Minor Critical
Removed notification is sent when it is
Link/Rate
determined that the link is down due to
Off
a cable being locally removed from its

RJ-45 port connection.
Link Down - Link Down is generated when a Wait a few moments for the
Cause Not physical connection is lost on a good system to isolate the trouble
Facility
Determined link on the Ethernet interface port and observe another Link
Red
(Access or Network). Upon the loss of Down condition on this
Minor Critical
connection on a given port, this is the interface. Troubleshoot
Link/Rate
first notification being sent, before any according to the new
Off
specific cause is determined (such as condition.
cable fault or cable removed).
Link Down - The Link Loss Forwarding (LLF) feature Verify Network Port alarms at
De-activated is enabled and has been activated, the far end.
resulting in the deactivation of this a) Clear the Network Port Facility
Access port. Such alarm indicates that condition that caused the Link Red
the port is down due to Link Loss Loss Forwarding feature to Minor Critical
Forwarding on a corresponding remote activate. Link/Rate
port. The link deactivated message is b) Disable fault propagation. Off
useful in that it ensures that the proper
failed unit will be addressed.
557
558

Link Down - Link Down Master Slave Configuration. Verify Master Slave Facility
Master Slave configuration. Red
Config Minor Critical
Link/Rate
Off
Loss of ESMC Loss of Ethernet Synchronization Verify synchronization network
Minor N/A N/A
Messaging Channel (ESMC). and provisioning.
Protection Switch - A forced protection switch on the Is the reason for originally
Forced (Network Network Port has occurred. A FORCED invoking a forced switch
Port Only) condition is raised when a user has resolved? If so, release the
invoked a protection switch away from forced switch. Otherwise, no
the Port indicated in the event report. action is required at the local
Not Alarmed N/A N/A
This is normally done for a unit.
maintenance and/or troubleshooting
procedure. The FORCED condition will
clear when the user invokes a release
of the protection switch.
Protection Switch - Protection Switch Action - Lockout of Is the reason for originally
Lockout (Network Protect. A user switch request is active invoking a lockout resolved? If
Port Only) against the specified entity. so, release the lockout Not Alarmed N/A N/A
condition. Otherwise, no action
is required.
Receiving Jabber The total number of packets received Verify the signal leaving the far
were longer than the MTU size, and end NID, through any inter-
had either a bad Frame Check mediate equipment, and at the
Facility
Sequence (FCS) with an integral near end. Probable Cause: Minor Major
Red
number of octets (FCS Error), or a bad Network problem, or possibly a
FCS with a non-integral number of bad cable. Repair faulty
octets (Alignment Error). equipment or cable.


Remote Fault Remote Failure Indication received Verify the signal leaving the
Indication2 from remote equipment. Remote end local unit, through any inter-
Facility
has lost the signal originating from the mediate equipment, and at the Minor Minor
Yellow
local unit. far end. Repair faulty
equipment or cable.
SFP is not SFP is not qualified, but inventory Remove SFP module and
qualified (Fiber information indicates that it may still replace with an ADVA Optical
Minor N/A N/A
only) work. Networking-approved module
for that interface type.
SFP - Provisioning Small Form-factor Plug-able (SFP) Remove SFP module and
Mismatch (Fiber optics module mismatch. The installed replace with an ADVA Optical
only) SFP module does not match the Networking-approved module
Facility
provisioned module type for the for that interface type.
Red
interface. The system expects the SFP

Minor Critical
to conform to the MSA specification for
Link/Rate
inventory contents and alarm will be
Off
raised if the SFP’s inventory data does
not reflect that the device supports the
configured speed.
SFP - Removed Small Form-factor Plug-able optics Install SFP module. Facility
(Fiber only) module is removed. Red
Minor Critical
Link/Rate
Off
SFP - Transmit Small Form-factor Plug-able optics Replace SFP module. Facility
Minor Critical
Fault (Fiber only) module failure. Red
559
560

Sync QL Mismatch Synchronization Quality Level Verify synchronization network
Mismatch. The Network Port or Access and provisioning.
Port receives SSM messages whose
specified Quality Level is lower than the
Expected QL. The port's QL Mode Minor N/A N/A
attribute must be configured as enabled
and the Expected QL attribute must be
configured as anything besides None
for this condition to exist.
Sync QL Invalid Synchronization Quality Level Invalid. Verify synchronization network
The Ethernet port receives and provisioning.
Synchronization Status Messaging
(SSM) slow protocol messages whose
Minor N/A N/A
specified Quality Level is invalid. The
Ethernet port's QL Mode attribute must
be configured as enabled for this
condition primitive to exist.
Sync Reference Synchronization Referencing Failed. Verify synchronization network
Failed The Network Port or Access Port has and provisioning.
failed in such a way that its clock
cannot be recovered, thus preventing it Minor N/A N/A
from being used as a synchronization
reference (e.g., LOS). The port must be

assigned for this condition to exist.
Sync Reference A forced switch operation has been Evaluate reason for forced
Forced Switch performed on a Sync Reference. switch operation and when
Minor N/A N/A
switch.
Sync Reference A Sync Reference has been locked out. Test the Locked Out Sync
Locked Out Usually due to failure, configuration Reference and remove lock
Minor N/A N/A
changes planned or maintenance out when reference is fully
operations. functional again.


Sync Reference A manual switch operation has been Evaluate reason for the
Manual Switch performed on a Sync Reference. manual switch operation. Minor N/A N/A
Sync Reference A Sync Reference has been restored No Action Required.

Minor N/A N/A
Wait To Restore and is in WTR timing.
Test Alarm A test alarm is generated to check Ensure alarm propagates
Major N/A N/A
alarm propagation. properly.
1. SFP (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.
2. If 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.

561
CFM Maintenance End Point Alarms
562

Refer to the following table for Connectivity Fault Management (CFM) Maintenance End Point (MEP) alarm conditions
and their associated probable cause, default notification code and suggested trouble clearing procedure.
Table 31: Maintenance End Point Alarms

Alarm Indication CFM MEP Alarm Indication Signal. Verify and troubleshoot MEP. Not
N/A N/A
Signal Reported
Cross Connect Cross-connect Continuity Check Message 1) Verify MA and VLAN
CCM (CCM) defect is raised when one configuration at each end point
cross-connected CCM is received. It is throughout the network.
cleared when a cross- connected CCM is 2) Verify configuration of MA
not received for 3.5 times the provisioned VLANs in the network.
CCM transmission interval of the last cross-
connected CCM.
A CCM is considered cross-connected if
MAID (48 byte entity consisting of MD
name, MA name and MEP ID) does not
match with the MAID of the receiving MEP,
or if MD Level is less than the receiving N/A Minor N/A
MEP’s MD Level. Probable causes are:
a) Erroneous configuration of MA at the a) Reconfigure MA
different end points of the MA. For example, configuration at appropriate
if a different MA name is configured at node(s).

different end points.
b) MD Level is less than the receiving d) Reconfigure MD Level
MEP’s MD Level. configuration at appropriate
node(s).
c) Some other MA’s CCM can be received c) Change MA and/or VLAN
due to mis-configuration of VLANs in the configuration at appropriate
network. node(s).
Table 31: Maintenance End Point Alarms (Continued)


Erroneous CCM Erroneous Continuity Check Message Verify MEP ID and CCM
(CCM) defect is raised when one invalid transmission interval
CCM is received. It is cleared when an configuration at each end point
invalid CCM is not received for 3.5 times the throughout the network.
provisioned CCM transmission interval of
the last invalid CCM. A CCM is invalid if:
1. MEP ID in the received CCM is not
configured in the receiving MEP’s MA.
2. MEP ID in the received CCM matches
the receiving MEP’s MEP ID.
3. CCM interval does not match the interval N/A Minor N/A
configured for the receiving MEP’s MA.
Probable Causes are:
a) Mis-configuration of MA, where the MEP a) Reconfigure MEP list at

list is not consistent at all the end points. appropriate node(s).
b) Mis-configuration of MA, where the MA b) Reconfigure MA CCM
CCM transmission interval is different at transmission interval at
one or more end points of the MA. appropriate node(s).
c) Mis-configuration of MEP, where MEPs c) Reconfigure MEP ID at
with same MEP ID is created at two or more appropriate node(s).
end points of the MA.
563
564

Some MAC Some MAC Status defect exists on a MEP Verify the Remote MEP LAN
Status if: interface connection and
1) At least one remote MEP’s interface is configuration.
unavailable. Troubleshoot and repair the
2) All MEPs on the same interface are Remote MEP interface
reporting that the port is blocked (i.e., all connection or reconfigure the
remote MEPs’ Bridge Ports are not interface.
forwarding data).
N/A Minor N/A
The problem lies at the starting point of the
service instance (the Remote MEP) and
probably not anywhere in the network used
by the MA. In FSP 150CC-GE11x CCMs
generated do not have Port Status or
Interface Status TLVs, but the TLVs are
handled if CCMs are received containing
them.
Some RDI At least one of the Remote MEPs is sending Observe MEP alarm conditions
CCMs with Remote Defect Indication (RDI) at the remote node.
set. Perform appropriate steps in
N/A Minor N/A
RDI is present in the CCMs transmitted this table to clear the condition
when any of the other MEP alarm at the far end.
conditions (above) exist for a Remote MEP.


Some Remote A Remote Maintenance End Point (MEP) 1) Observe if an Erroneous
MEP CCM Continuity Check Message (CCM) defect CCM or Cross-connect CCM
indicates that a CCM is not received from a condition exists on the remote
Remote MEP for 3 consecutive provisioned MEP.
CCM transmission intervals. 2) Verify cable connections
Probable causes are: and configuration at network
equipment / intermediate
nodes.
a) If MEPs in an MA are mis-configured, a) If an Erroneous CCM or
and as a result there are Erroneous CCM or Cross-connect CCM condition N/A Minor N/A
Crossconnect CCM conditions, this alarm exists, refer to the appropriate
could be raised as a side-effect. steps to clear the Erroneous
CCM or Cross-connect CCM
condition.

b) A problem exists causing the CCM to be b) Troubleshoot and repair the
dropped before it reaches the end point, physical network or
such as a physical problem with the reconfigure network equipment
network or mis-configuration of the / intermediate nodes.
equipment in the network.
MEP alarm attributes are editable in CFM mode (by selecting

PS
Applications and then CFM or selecting the CFM icon).

Note
565
CFM QoS Shaper Alarms
566

Refer to the following table for Connectivity Fault Management (CFM) Quality of Service (QoS) Shaper alarm conditions
and their associated probable cause, default notification code and suggested trouble clearing procedure.
Table 32: Qos Shaper Alarms

Shaper BTD Shaper Bytes Tail Dropped by the QoS Verify and troubleshoot MEP
queue. Insufficient bandwidth. bandwidth allocation.
Minor Minor N/A
Re-provision with more
bandwidth, if necessary.
LAG Alarms
Refer to the following table for LAG alarm conditions and their associated probable cause, default notification code and
suggested trouble clearing procedure.
Table 33: LAG Alarms

Link Control Link control protocol failed. Check the configuration of the
Protocol Fail lag-based management tunnel
(Encapsulation Type PPP) and N/A Critical N/A
ensure it functions well; or
delete the management tunnel.
Link Control Link control protocol detected loopback. Remove loopback to clear
Protocol alarm. N/A Critical N/A
Loopback
Table 33: LAG Alarms (Continued)


Link Down Link Down is generated when a physical Perform an Etherjack Facility
connection is lost on a good link on the Diagnostic test. Repair the port Red
LAG. using test results. N/A Critical
Link/Rate
Off
Link Down - The Link Loss Forwarding (LLF) feature is Verify Network Port alarms at
De-activated enabled and has been activated, resulting the far end.
Facility
in the deactivation of this LAG. Such alarm a) Clear the Network Port
Red
indicates that the port is down due to Link condition that caused the Link
N/A Critical
Loss Forwarding on a corresponding Loss Forwarding feature to
Link/Rate
remote port. The link deactivated message activate.
Off
is useful in that it ensures that the proper b) Disable fault propagation.
failed unit will be addressed.

SAT Responder Session Alarms
Refer to the following table for Service Activation Testing (SAT) Responder Session alarm conditions and their associ-
ated probable cause, default notification code and suggested trouble clearing procedure.
Table 34: SAT Responder Session Alarms

Remote This alarm is reported when one responder No action required.
Initiated SAT session is negotiated. Disappear when user
Minor N/A N/A
deletes this session or it is released by
remote SAT Control.
567
ERP Alarms (GE114x)
568

Refer to the following table for Ethernet Ring Protection (ERP) alarm conditions and their associated probable cause,
Table 35: ERP Alarms
ERP FOP Failure of Protocol, Protocol Mismatch. The Verify the ERP provisioning at
Mismatch ERP instance is provisioned as the RPL each node, change the node
Owner; and received a R-APS PDU con- provisioning as required.
taining the MEG Level, Ring ID and VID for
the ERP instance, an OAM Opcode field of N/A Major N/A
40 (R-APS), a Request/Status value of NR
(No Request), an RPL Blocked status of 1
(Blocked) and a Node ID different than the
receiving node.
ERP FOP Failure of Protocol, Timeout. The ERP Check the RAPS Status and
Timeout Instance has not received a R-APS PDU verify R-APS VLAN
containing the MEG Level, Ring ID and VID provisioning to determine the Minor N/A N/A
for the ERP instance for 15s; i.e., 3x the cause, clear trouble as
R-APS PDU transmission period. required.
ERP BlockPort Blocking Ring Port 0/1 - Ring Protection Investigate blocked side of the
Not
0/1 RPL Link. ring, verify CFM messages and N/A N/A
Reported
repair link.
ERP BlockPort Blocking Ring Port 1 - Signal Fail. Verify the signal leaving the far
0/1 SF end unit, through any

inter-mediate equipment, and N/A N/A N/A
at the near end. Repair faulty
equipment or cable.
ERP BlockPort Blocking Ring Port 0/1 - Manual Switch. Evaluate reason for the
N/A N/A N/A
0/1 MS manual switch operation.
Table 35: ERP Alarms (Continued)


ERP BlockPort Blocking Ring Port 0/1 - Forced Switch. Evaluate reason for forced
0/1 FS switch operation and when
N/A N/A N/A
switch.
ERP BlockPort Blocking Ring Port 0/1 - Wait-to-Restore. No Action Required.
N/A N/A N/A
0/1 WTR

569
Alarm Masking
570
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.
System level alarms are not masked.
Table 36: Alarm Masking Rules
Condition Type
Alarm Rule
SNMP Alarm Name eVision GUI Alarm Name
10MHz (CLK) Port / Pulse Per Second (PPS) Port / Time Of Day (TOD) Port
qlsqlch Output Squelch qlsqlch (no masking)
3G USB Modem
lnkdn Link Down linkdn Removed, not Nonqualified, not nosim
modemnonqualified MODEM Is Not Qualified Nonqualified, not Removed

modemremoved MODEM Removed Removed (no masking)
no-sim-card No Sim Card nosim, not Removed or Nonqualified
BITS In Port
ais Alarm Indication Signal ais and not los
freqoff Frequency Offset freqoff (no masking)
lof Loss of Frame lof and not los or ais
los Loss of Signal los (no masking)
qlinvalid Sync QL Invalid qlinvalid (no masking)

qlmismatch Sync QL Mismatch qlmismatch and not qlinvalid
syncref Sync Reference Failed syncref (no masking)
syncreffrc Sync Reference Forced syncreffrc (no masking)
Switch
syncreflck Sync Reference Locked Out syncreflck (no masking)
syncrefman Sync Reference Manual syncrefman (no masking)
Switch
syncrefwtr Sync Reference Wait To syncrefwtr (no masking)
Restore
Table 36: Alarm Masking Rules (Continued)

Condition Type
Alarm Rule
BITS Out
qlsqlch QL Squelch qlsqlch (no masking)
CFM MEP
ais Alarm Indication Signal ais (no masking)
erroneousccm Erroneous CCM erroneousccm and not crossconnectccm or ais
somemacstatus Some MAC Status somemacstatus and not crossconnectccm or erroneousccm or
someremotemepccm or ais
somerdi Some RDI somerdi and not crossconnectccm or erroneousccm or someremotemepccm or
somemacstatus or ais
someremotemepccm Some Remote MEP CCM someremotemepccm and not crossconnectccm or erroneousccm or ais
crossconnectccm Cross Connect CCM crossconnectccm and not ais
CFM QoS Shaper

shaperbtd Shaper BTD shaperbtd (no masking)
DCN Port
lnkdn Link Down no masking
ERP
erpBlockPort0FS ERP BlockPort 0 FS erpBlockPort0FS (no masking)
erpBlockPort0MS ERP BlockPort 0 MS erpBlockPort0MS (no masking)
erpBlockPort0RPL ERP BlockPort 0 RPL erpBlockPort0RPL (no masking)
erpBlockPort0SF ERP BlockPort 0 SF erpBlockPort0SF (no masking)
erpBlockPort0WTR ERP BlockPort 0 WTR erpBlockPort0WTR (no masking)
erpBlockPort1FS ERP BlockPort 1 FS erpBlockPort0MS (no masking)
erpBlockPort1MS ERP BlockPort 1 MS erpBlockPort1MS (no masking)
erpBlockPort1RPL ERP BlockPort 1 RPL erpBlockPort1RPL (no masking)
erpBlockPort1SF ERP BlockPort 1 SF erpBlockPort1SF (no masking)
erpBlockPort1WTR ERP BlockPort 1 WTR erpBlockPort0FS (no masking)
erpFoPPM ERP FOP Mismatch erpFOPM (no masking)
erpFoPTO ERP FOP Timeout erpFoPTO (no masking)
571
572
Alarm Masking
Condition Type
Alarm Rule
Ethernet Port (Access Port and Network Port)
autonegunknown Duplex Mode of Farend autonegunknown and not lnkdownunisolated or lnkdownlpbkfault or
Device Unknown lnkdowncableremoved or lnkdowncablefault or lnkdownautonegfailed or
lnkdeactivated or rxjabber or SGEO or sfpmismatch or sfpremoved or sfptxfault or
dyinggasp or lnkdownmasterslavecfg
bwexceedednegspeed Bandwidth Exceeds bwexceedednegspeed (no masking)
Negotiated Speed
dyinggasp Dying Gasp Received dyinggasp (no masking)
efmfail EFM OAM - Failure efmfail and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved
or lnkdowncablefault or lnkdownautonegfailed or SGEO or sfpmismatch or
sfpremoved or sfptxfault or dyinggasp or lnkdownmasterslavecfg
efmrce EFM OAM - Remote Critical efmrce and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved
Event or lnkdowncablefault or lnkdownautonegfailed or SGEO or sfpmismatch or
efmrld EFM OAM - Remote Link efmrld and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved or
Down lnkdowncablefault or lnkdownautonegfailed or SGEO or sfpmismatch or
efmrls EFM OAM - Remote Link efmrls and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved or
Status lnkdowncablefault or lnkdownautonegfailed or SGEO or sfpmismatch or
elmi-notoper ELMI Not Operating elminotoperational and not lnkdn or lnkdnunisolated or lnkdnlpbkflt or lnkdncbltstflt
or lnkdncblrmv or lnkdncblflt or lnkdnautonegflt or lnkdnmstrslvcfg or sgeo or sfp or

xfp or dyinggasp
elmi-seqnummismatch ELMI Sequence Number elmiseqmismatch and not lnkdn or lnkdnunisolatd or lnkdnlpbkflt or lnkdncbltstflt or
Mismatch lnkdncblrmv or lnkdncblflt or lnkdnautonegflt or lnkdnmstrslvcfg or sgeo or sfp or
xfp or dyinggasp
esmcfail Loss of ESMC esmcfail (no masking)
forced (Network port Protection Switch - Forced forced (no masking)
only)

Condition Type
Alarm Rule
lcpfail Link Control Protocol Fail lcpfail and not lnkdn or lnkdnunisolated or lnkdnlpbkfault or lnkdncabletestfault or
lnkdncableremoved or lnkdncablefault or lnkdnautonegfailed or
lnkdnmasterslavecfg or lnkdeactivated or sgeomea or sgeoflt or sgeounplug or
sfprmv or sfpinserted or sfptxfault or sfpmea or dgasp
lcploopback Link Control Protocol lcploopback and not lcpfail or lnkdn or lnkdnunisolated or lnkdnlpbkfault or
Loopback lnkdncabletestfault or lnkdncableremoved or lnkdncablefault or
lnkdnautonegfailed or lnkdnmasterslavecfg or lnkdeactivated or sgeomea or
sgeoflt or sgeounplug or sfprmv or sfpinserted or sfptxfault or sfpmea or dgasp
lnkdeactivated Link Down - De-activated lnkdeactivated and not SGEO or sfpmismatch or sfpremoved or sfptxfault or
dyinggasp
lnkdn Link Down lnkdn and not lnkdeactivated
lnkdownautonegfailed Link Down - lnkdownautonegfailed and not SGEO or sfpmismatch or sfpremoved or sfptxfault
Auto-Negotiation Failed or dyinggasp or lnkdeactivated or lnkdownmasterslavecfg

lnkdowncablefault Link Down - Cable Fault lnkdowncablefault and not SGEO or sfpmismatch or sfpremoved or sfptxfault or
dyinggasp or lnkdeactivated or lnkdownmasterslavecfg
lnkdowncableremoved Link Down - Cable Removed lnkdowncableremoved and not SGEO or sfpmismatch or sfpremoved or sfptxfault
or dyinggasp or lnkdeactivated or lnkdownmasterslavecfg
lnkdownmasterslavecfg Link Down - Master Slave lnkdownmasterslavecfg and not SGEO or sfpmismatch or sfpremoved or sfptxfault
Config or dyinggasp or lnkdeactivated
lnkdownunisolated Link Down - Cause Not lnkdownunisolated and not lnkdownlpbkfault or lnkdownautonegfailed or
Determined lnkdowncablefault or lnkdowncableremoved or lnkdeactivated or SGEO or
sfpmismatch or sfpremoved or sfptxfault or dyinggasp or lnkdownmasterslavecfg
lockout (Network port Protection Switch - Lockout lockout (no masking)
only)
rfi Remote Fault Indication rfi and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved or
lnkdowncablefault or lnkdownautonegfailed or lnkdeactivated or SGEO or
573
574
Alarm Masking
Condition Type
Alarm Rule
rmtefmlpbkfail EFM OAM - Remote rmtefmlpbkfail and not lnkdownunisolated or lnkdownlpbkfault or
Loopback Failed 1 lnkdowncableremoved or lnkdowncablefault or lnkdownautonegfailed or SGEO or
rxjabber Receiving Jabber rxjabber and not lnkdownunisolated or lnkdownlpbkfault or lnkdowncableremoved
or lnkdowncablefault or lnkdownautonegfailed or lnkdeactivated or SGEO or
sfpmismatch SFP - Provisioning sfpmismatch and not sfpremoved or SGEO
Mismatch
sfpnonqualified SFP is not qualified sfpnonqualified, (no masking)
sfpremoved SFP - Removed sfpremoved and not SGEO
sfptxfault SFP - Transmit Fault sfptxfault and not sfpmismatch or sfpremoved or SGEO or dyinggasp
Switch
Switch
Restore
testalarm Test Alarm testalarm, (no masking)
GPS
gps-antenna-alarm-indi GPS Antenna Alarm (no masking)
cation Indication
timeref-degraded Time Reference Degraded (no masking)
timeref-degraded-wtr Time Reference Degraded (no masking)
Wtr
timeref-locked-out Time Reference Locked Out (no masking)
timeref-unavailable Time Reference Unavailable (no masking)
timeref-unavailable-wtr Time Reference Unavailable (no masking)
Wtr

Condition Type
Alarm Rule
LAG
lcpfail Link Control Protocol Fail lcpfail and not lnkdn or lnkdeactivated
lcploopback Link Control Protocol lcploopback and not lcpfail or lnkdn or lnkdeactivated
Loopback
lnkdeactivated Link Down - Deactivated lnkdeactivated (no masking)
lnkdn Link Down lnkdn and not lnkdeactivated
NTE Card
ctneqpt Communication Failure ctneqpt and not eqptremoved or mismatch
eqptflt Equipment Fault eqptflt and not eqptremoved or mismatch
mismatch Equipment Does Not Match mismatch and not eqptremoved
Provisioning
eqptremoved Equipment Provisioned But eqptremoved (no masking)

Removed
testalarm Test Alarm testalarm, (no masking)
NTE Shelf
overtemp Over Temperature overtemp and not eqptremoved or mismatch
undertemp Under Temperature undertemp and not eqptremoved or mismatch
Power Supply (PSU)
ctneqpt Communication Failure ctneqpt and not eqptremoved or mismatch
eqptflt Equipment Fault eqptflt and not eqptremoved or mismatch
eqptremoved Equipment Provisioned But No masking
Removed
mismatch Equipment Does Not Match mismatch and not eqptremoved
Provisioning
overtemp Over Temperature overtemp and not eqptremoved or mismatch or eqptflt
PSE Group
pse-power-threshold-ex PSE Power Threshold no masking
ceeded Exceeded
575
576
Alarm Masking
Condition Type
Alarm Rule
pse-power-fail PSE power chip no masking
Communication failed
PSE Port
pse-poweroff-overcurre PSE power off due to over no masking
nt current
pse-poweroff-overvolta PSE power off due to over no masking
ge voltage
pse-poweroff-over PSE power off due to over no masking
load
pse-poweroff-overtemp PSE power off due to over no masking
temperature
pse-poweroff-short PSE power off due to short no masking
circuit
SAT Responder Session
remote-initiated-sat Remote Initiated SAT remote-initiated-sat (no masking)
SOOC
ptsflossofannounce PTSF - Loss Announce ptsflossofannounce (no masking)
ptsflossofsync PTSF - Loss Sync ptsflossofsync (no masking)
ptsfunusable PTSF - Unusable ptsfunusable (no masking)
Synchronization
allsyncref All Input Sync Referenced allsyncref (no masking)

Failed
avghldovrfrqnotrdy Average Holdover Fre- avghldovrfrqnotrdy (no masking)
quency Not Ready
frngsync Sys Clock Mode - frngsync (no masking)
Freerunning
fstsync Sys Clock Mode - Fast fstsync (no masking)
Acquisition
hldovrsync Sys Clock Mode - Holdover hldovrsync (no masking)

Condition Type
Alarm Rule
losloc Sys Clock Mode - Loss of losloc (no masking)
Lock
System
bckupntpsvrFailed Backup NTP Server Failed bckupntpsvrFailed (no masking)
db-ftip Database - File Transfer In db-ftip (no masking)
Progress
dbdowngradeip DB Downgrade dbdowngradeip (no masking)
gen-filexfer-ip File Transfer In Progress gen-filexfer-ip (no masking)
gen-oper-ip Operation In Progress gen-oper-ip (no masking)
ipaddrconflict IP Address Conflict ipaddrconflict (no masking)
IPv6 Address Conflict (no masking)
ltpFailure LTP failure ltpFailure(no masking)

ltpInprogress LTP In progress ltpInprogress(no masking)
primntpsvrFailed Primary NTP Server Failed primntpsvrFailed (no masking)
snmpdghostresourcesb SNMP Dying Gasp - snmpdghostresourcesbusy (no masking)
usy Resource Busy
snmpdghostunresolved SNMP Dying Gasp - Host snmpdghostunresolved (no masking)
Unreachable
swdl-actip SWDL - Activation In swdl-actip (no masking)
Progress
swdl-ftip SWDL - File Transfer In swdl-ftip (no masking)
Progress
swdl-instip SWDL - Installation In swdl-instip (no masking)
Progress
swdl-valip SWDL - Validation In swdl-valip (no masking)
Progress
Telecom Slave
allsoocsfailed All SOOCs Failed allsoocsfailed (no masking)
freqoff Frequency Offset freqoff (no masking)
577
578
Alarm Masking
Condition Type
Alarm Rule
Switch
Switch
Restore
tsfreerun Telecom Slave In Freerun tsfreerun (no masking)
tsholdover Telecom Slave In Holdover tsholdover (no masking)
ts-in-time-freerun Telecom Slave In Time (no masking)
Freerun
ts-in-time-hldovr Telecom Slave In Time (no masking)
Holdover
tsholdoverfrqnotready Recovered Clock Not Hold- tsholdoverfrqnotready (no masking)
over Quality
Time Clock
time-clock-not-locked Time Clock Not Locked (no masking)
time-freq-not-traceable Time Frequency Not Trace- (no masking)

able
time-freq-lock Time Frequency Lock (no masking)
time-holdover Time Holdover (no masking)
time-not-traceable Time Not Traceable (no masking)
1. EFM 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.
Error Codes and System Responses

This table lists the error codes and the associated definitions or responses. The
_why_ attribute is a response string that is defined by the system software. All
possible _why_ responses are listed under the “Where Why is:” when an error
code can have multiple responses. Before the response is sent to the user the
error codes are mapped based on the message type. Each group of error codes
is sorted by a system condition or type.
Table 37: Error Codes and Definitions

Error Code Response
GENERAL SYSTEM CONDITIONS
0 Operation completed successfully.
1 Unknown error.
2 Mei application shutdown failed.
3 File _filename_ does not exist
4 No Response _from_
5 User _username_ is locked out.
6 User _username_ is not logged in.
7 User _username_ locked out - _loginnum_ unsuccessful login attempts.
8 User _username_ locked out.

9 Remote User Login failed: _why_
Where Why is:
Athentication failed
Radius setup failed
Invalid password

Error Code Response

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_
266 Invalid EID: _why_
Where Why is:
Protection Group Id must be 1
Value (xxx) out of range
267 IP address _ipaddr_/_mask_ of interface _if_ overlaps with address of interface
_overlapif_
268 Operation denied: _why_
Create denied: _why_
Delete denied: _why_
Edit denied: _why_
Retrieve denied: _why_
Action denied: _why_
Where Why is:
System in Db Maintenance Mode
269 Operation denied: _why_
Edit denied: _why_
Where Why is:
Object is transient

Error Code Response

271 - 275 Operation denied: _why_
Edit denied: _why_
Where Why is:
(EID) MD name causes MA ID length to exceed limit (xxx MIN... yyy MAX)
(EID) Probe's Source MEP(eid2) is in [xxx] state
(xxx) not supported on CP unit return
(xxx) is a lag member port
(xxx) is a member of (yyy) - VID
(xxx) is associated with Management Address Entity of (yyy)
(xxx) is not applicable for Port-Based EVC
(xxx) is not applicable for N2A COS Priority when ITAG control is not (yyy)
(xxx) is not applicable when C-Bit Parity is disabled
(xxx) is not applicable when frame format is (yyy)
(xxx) is not applicable when Management Tunnel is not on Network port
(xxx) is not Ethernet Traffic Port
(xxx) is not supported for UNTAGGED frames
(xxx) is used by IPV4 PROXY ARP ENTRY
(xxx) is used by IPV4 STATIC ARP ENTRY
(xxx) is used by IPV4 STATIC ROUTE

(xxx) has been set as Sync Reference Source
(xxx) has no members
(xxx) has no Remote MEP
(xxx) state is not support on CP Unit
A2N Policer not specified for CTAG's Priority (xxx)
Access Interface cannot be a SHG when PBB Frames is enabled
Access Interface cannot be a SHG when Itag Control is (xxx)
Address cannot be broadcast, mutlicast or all 0's
Address is not a valid unicast address
Admin State is (xxx)
Admin State is not in (xxx) state
AIS client MD level (xxx) must be greater than MEP MD level of (yyy)
AIS generation cannot be enabled at MD level (xxx)
AIS Trigger has duplicate values
Already there have been 20 RIPv2 enable in the system
Already there have been 20 RIPng enable in the system
A member in the VID list (xxx) matches the primary vid of vlan entry [eid]
A MEP exists with associated component ID
An Ethernet port with speed configured as (xxx) cannot be added to the refer-
ence selector list
An Ethernet port with SyncE mode disabled cannot be added to the reference
selector list
Antenna Cable Length may be set to value range: 0 ...100
A port can only be added to the reference selector list if its signal direction is
input

Error Code Response

271 - 275 Where Why is:
(Continued) A port can only be added to the reference selector list if it is assigned
A port in the reference selection list cannot be unassigned
ARP Entries for interfaces other than eth0 exist in the system
Associated MA COMP entity does not exist
Associated Service Flow does not exist (serviceEID)
At least 1 (xxx) must exist on a Flow
At least 1 Policer must exist on a Flow
At least 1 Shaper must exist on a Flow
At least 1 VLAN Member must exist
At least 1 pt_n1_policer must exist on a Flow
At least 1 pt_n2_policer must exist on a Flow
Authentication Protocol cannot be (xxx)
Because there is a Y1731 probe (xxx)
Both Primary and Backup server have zero IP addresses
Build Shadow Tree failed
Cannot change authentication protocol when remote users exist
Cannot change BMAC when the port is in a LAG member port
Cannot create (xxx) flow with VLAN members
Cannot delete a scheduled probe
Cannot delete an active reflector
Cannot delete Dynamic ARP Entry
Cannot disable both Stag and Ctag for VLAN-based Tunnel
Cannot edit Network port 2
Cannot edit Protecting Port attributes
Cannot enable both Stag and Ctag for ITAG-based Tunnel
Cannot enable ITAG for Non ITAG BASED Tunnel
Cannot enable QL mode if Admin Sate is set to unassigned
Cannot enable QL Mode unless SyncE Mode is also enabled
Cannot enable SyncE on a port with speed of 10Mbps
Cannot enable SyncE if any network port has speed of 10Mbps
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
Cannot modify A2N shaping type if the flow is not port-based
Cannot not suspend an active reflector
Cannot resume a reflector that is not suspended
Cannot resume a schedule that is not suspended
Cannot start non-suspended schedule
Cannot stop non-active schedule
Cannot suspend non-active schedule
Cannot unassign a port if the port is provisioned as Ring Port 0 ""or Ring Port 1
of an ERP instance
Can't reopen System Default Db
Can’t set DHCP option enable when DHCP is disable
Card (xxx) found in slot
Changing Service Type and Admin State is not allowed in one operation. Admin
State must first be changed to Unassigned
Chosen DMM Packet Interval consumes (xxx)
CIR and EIR cannot both be 0

Error Code Response

(Continued) Clear not supported on CP unit
Community (xxx) used by Target Address (yyy)
Config file is busy
Config operation failed
Configfile is not in progress
Diagnostics are active on Port
Diagnostics not supported on network port
Data TLV exceed the allowed maximum of (xxx MAX)
Create or Open configfile failed
Data TLV exceeds the allowed maximum of (xxx) bytes
Db State is not ok
Denied due to lockout of the reference
Denied due to signal fail on the reference
Denied due to QL priority being too low. Reference
DHCP is enabled
DHCP log server has been enable in another interface
DHCP ntp server has been enable in another interface
Disable SFTP first, to disable the SSH
Duplicate MA Name - conflicts with (xxx)
Duplicate MD name - conflicts with (eid)
Duplicate MD name (same MD level) - conflicts with (eid)
Duplicate MEP ID list

Duplicate VID list - duplicate entry (xxx) found in (eid)
Duplicate VLAN member (xxx) at positions (yyy) and (zzz)
Dying Gasp is already enabled for IP (xxx) on Target Address (yyy)
ECPA test is active on Port
ECPA test not active
(efmlpbk) exsits on port
enable SSH first, to enable SFTP
Enter a hex number following the MAC address
ESA Probe belongs to an active schedule (xxx)
EtherType can only be (xxx) ot (yyy)
Existing MEP ID (xxx) cannot be removed from the MEP List
Feature of (xxx) cannot be disabled once enabled
Flow is (xxx)
Flow with UNTAGGED support need to be MultiCOS enabled
Flows with UNTAGGED support need to have different COS levels
For primary VID type, range should be (xxx MIN... yyy MAX)
Gateway address is not a valid unicast address
Incompatible (xxx) card for (yyy) slot
Inner VLAN Tag enabled without Outer VLAN Tag enabled
Inner VLAN Tag cannot be enabled with Outer ITag enabled
Inserting AIS is done on (xxx)
Interface (name) cannot be set to (dhcprole) role when Management Traffic
Bridging is enabled
Internal error - unable to allocate resource
Internal error - unable to allocate VLAN entry resources
Internal error - unable to release resource

Error Code Response

(Continued) Internal error - unable to release VLAN entry resources
Invalid hex number
Invalid MAC address
Invalid MAC-INTEGER format
Invalid name format: (xxx)
Invalid primary vid
Ipv6 RA Prefix Length range is 1 ... 64
ITAG Control is not NONE on (xxx)
Invalid primary vid - must be 0, component primary vid or must be from the vlan
table
Invalid Source MEP direction (xxx). Only UP MEPs allowed.
IP Interface starting with ppp is reserved for system functions
IP Management Tunnel is not allowed on Network Port 2 if it is not an indepen-
dent Network port
IP is all 0 for nexthop route
Ipv6 Forward can’t be set when Stateless Address Auto Configuration is
enabled on any interface
Ipv6 Forward can’t be set when ISATAP is created in any interface
ITAG is not allowed to coexist with CTAG or STAG
ITAG is not allowed when JDSU loopback is enabled on (xxx)
ITAG is not allowed when JDSU loopback is enabled on (xxx)
ITAG is not allowed when Access Interface Learning Confront is enabled
ITAG is not allowed when Network Interface Learning Control is enabled
(itagctrltype) is not supported
ITAG ID of (xxx) conflicts with ITAG ID of (yyy)
ITAG ID (*) of (xxx) conflicts with ITAG ID (*) of (yyy)
JDSU Loopback Control cannot be enabled when the port is in (xxx)
JDSU Loopback Control is enabled on (xxx)
LAG member (xxx) does not belong to unit
LLF Trigger has duplicate values
LLF triggers are not supported on service based down MEP
Bridging Security is enabled
Loopback already exists
Loopback is active on Port
(loopbackconfig) is not available when a Management Tunnel is on the port and
Management Traffic Bridging is enabled
(loopbacktype) is not available when a Management Tunnel is on (xxx) whose
working path is (yyy) and Management Traffic Bridging is enabled
MAC address is Broadcast
MAC address is NULL
MA COMP's (eid) Primary VID (xxx) cannot be in VID list
Management port (portid) (name) cannot be in (xx) state when Management
Traffic Bridging is enabled
Management Traffic Bridging must be enabled when Management Traffic
Management Traffic Bridging cannot be enabled when Proxy ARP is enabled
MA name is too long
MA NET Name should be set when changing the MA NET format

Error Code Response

(Continued) MA primary VID cannot be a VID member in VLAN table
Management prot (portid) (name) cannot have Fixed Speed and Half-Duplex
mode (portspeed) when Management Traffic Bridging Security is enabled
MA name causes MA ID length to exceed limit (xxx MIN... yyy MAX)
MA Name format cannot be set to (xxx) when MD Name format is set to (yyy)
MAC-Based Management Tunnel cannot be created when Management Traffic
Bridging is enabled
Management Tunnel Buffer Size must be at least (xxx KB)
Management Tunnel cannot be created when Terminal Loopback is on the port
and Management Traffic Bridging is enabled
Max MEP count exceeded
Management Tunnel CIR must be at least (xxx) bps
Management Tunnels exist in the system
Management Tunnel with (encapsulationtype) encapsulation cannot exist when
Management Tunnel Bridging is enabled
MANET Name cannot be empty
MANET Name should be set when changing the MANET format
Manual Etherjack Diagnostics currently in progress
Max MEP count exceeded for the primary VID
Max MEP count exceeded for the port
Maximum MA name length supported in (xxx) is (yyy)
Maximum management bandwidth (xxx bps) exceeded (yyy bps remaining)

MD Name cannot be empty
MD Name cannot be greater than (xxx MAX)
system
MD Name cannot be set when MD name format is NONE
MD Name format cannot be set to (xxx) when (eid) Name format is set to ICC
format
MD Name is not set
MD Name should be set when changing the MD format
MEP at level (xxx MAX) cannot generate AIS
MEP at this MD level already exists for the primary VID
MEP ID (xxx) is not in the MEP list of MA Network
MEP ID (xxx) not found in the list
Multicast DA is not CFM multicast
MultiCOS not allowed for port level Source MEP (xxx)
N2N Forwarding can be enabled only if Network Interface is ERP
No available resources since there are (xxx) Clock Probes configured in the
N2A Rate Limiting is disabled.
NE already accepted
Neither CIR nor EIR provisioned
Network clock type may be set onlty via Sync
Network Interface cannot be a SHG when PBB Frames is enabled
Network Interface cannot be a ERP when PBB Frames is enabled
Network Interface cannot be a SHG when Itag Control is (xxx)
Network Interface cannot be a ERP when Itag Control is (xxx)
Network interface learning control is not one of NONE or MAC-BASED

Error Code Response

(271-275) Where Why is:
(Continued) No VID based MEP can be created on network port 2
PBB Frames is enabled on (xxx)
PBB frame is not applicable to Regular EVC
Not allowed to remove member port when JDSU Loopback is enabled on the
LAG
NTP client is enabled
One existing route has same destination and metric
Only COPPER port available
Only COS_0 allowed for port level Source MEP (xxx)
Only fully provisioned Telecom Slave can be System Time of Day PTP Clock
Only init/suspended/completed schedule can be deleted
Only one MA COMP can be created under an MA Network
Only one MEP allowed under this MA Network
OAM is disabled on port
Only 1 (xxx) flow may exist on port
Only 1 (xxx) pass-through flow may exist on NE
Only 1 Probe with Packet Interval less than 100 ms is allowed
Only 2 Management Tunnels are most can be active
Only down MEP is allowed on network ports
Only one port based down MEP can be created on a port
Only Telecom Slave can be PTP Clock
Operation not allowed in current state
Out of range. Enter a 2 byte integer
PBB frame is not applicable when JDSU loopback is enabled on (xxx)
PBB frame is not applicable when Network Interface Learning Control is
enabled
PBB frame is not applicable when Access Interface Learning Control is enabled
Port speed of 10 Mbps requires SyncE to be disabled on all network ports
Preserve STag properties is allowed only if STag Control is SWAPVID
Proxy ARP cannot be enabled when Management Traffic Bridging is enabled
Please point out which port should be switched
Port based Down MEP with more than 1 remote MEP is not supported
Port based Up MEP is now allowed on network ports
Port does not exist for (xxx)
Port is a FROM PORT of Network Element (xxx)
Port (xxx) is SHG member
Port (xxx) is provisioned as SYNCREF
Port OAM is enabled
Port QL Mode is enabled
Port Rx Pause is enabled
Port based Up MEP is not allowed on access ports
Port Level Up MEP and VID level Up MEP cannot exist together on the same
port
Primary vid [xxx] found in the VID list of [eid]
Primary VID cannot be in the VID list
Primary VID MANET name is not same as MACOMP primary VID (xxx)
Probe source IP and destination IP cannot be same

Error Code Response

(Continued) Probe source IP and destination IP must be in same subnet
Protecting port is in Sync Reference list
PtpFlowpointEid was not specified
Swap SA-DA must be (xxx) for EFM OAM Loopbacks
quotation marks, semicolon(;) and pound(#)
Protection Group does not exist for port
Protection Switching is not supported in (xxx) mode
PTP Access Flow Point’s parent port must be the same as Service Flow’s par-
ent
PTP Clock Eid must be set when System Time of Day is PTP Clock
PtpFlowpointEid not specified
PtpFlowpointEid does not exist
ReferenceEid must be the same for all PtpProbes
Reflector IP Address cannot overlap PTP IP Interfaces
Regeneration currently in progress
Routes for interfaces other than eth0 exist in the system
SAT Responder cannot be enabled when the MEP is associated with the probe
Secret cannot contain spaces
Security level of the user (xxx) is (yyy)
Service Flow associated with PTP Flow Point must be In-Service
Service Flow is associated with other PTP Flow Point
SFTP can not be set to enabled, when trying to disable SSH

Shaped speed greater than Configured speed
Shaped speed cannot be 0
Shaper is used by Policer (xxx)
Shaping Type should be PORT-BASED
Source IP Address cannot overlap PTP IP Interfaces
Source MEP does not exist
Source MEP (yyy) does not belong to the Source Port (xxx)
Specified MAC address is invalid
Specified Source MEP is already used by (xxx)
SSH can not be set to disabled, when trying to enable SFTP
instance
Stateless address auto configuration is enabled, cannot set default gateway
Switch Action is not supported in (xxx) mode
Sync Not Ready
System in Db Maintenance Mode
Telecom Slave can’t be created when TimeClock admin state is not Unassigned
Test not active
Test stream not active
The a2n shaping type is not flow-based
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
The Interface doesn’t support Ipv6
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 (..)

Error Code Response

(Continued)
The IP Mode cannot be changed after the Ipv6OverIpv4 Tunnel is created,
The mep is enabled for SAT responder, thus, cannot be referred by probe
The port should not be a lag member port
The port should not be a member port of a protection group
The port should not be a SHG member
The port should not be in loopback active state
The port should not be provisioned as Ring Port 0 or Ring Port 1 of an ERP
There are MEP entries for this MA
The port should not have any CFM entity on it
The port should not have any ESM entity on it
The port should not have any esa object
The port should not have any evc
The port should not have any IP Management Tunnel on it
The port should not have any SYNC reference on port
The port should not have MGMT Tunnel on port
The PTP Flowpoint creation on the Network Port 2 is denied if it is not an inde-
pendent Network Port
There are MACOMP entries for this MA
There are MA Network entries for this MD
There is a Y1731 probe (xxx)
There is already one Ipv6OverIpv4 Tunnel in the system
The Shaping Type of the flow is PORT-BASED
The static default route already exists
The Untagged flag must be Disabled, when Vlan is set
This entity has an active ESA Probe (xxx)
There has been a zero prefix length address in other interface, only allow one
VID member (xxx)
VID member (xxx) is used by (yyy)
VID list cannot be empty
This will cause MIPs limit to exceed
This object cannot be deleted
Tunnel already exists on (xxx)
Tunnel index must be from 1 to 255
Tunnel IP address is being used as system source IP address
Tunnel IP address is being used by SNMP v1 trap PDU
VLAN member (xxx) already exists at position (xxx)
VLAN member (xxx) does not exist
VPN OUI out of range (0 .. 0xFFFFFF)
When A2N PBB Frames is enabled, th combination of CTAG control and STAG
control are just allowed (NONE, NONE) and (PUSH, PUSH)
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 0x88a8
When 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
USM Security Name used by Target Parameter
Valid Until date is in the past

Error Code Response

Valid Until date is out of range allowed
Value DEFER is not allowed for MD MHF Creation Control
VID list contains duplicate entries
VID list size exceeds the maximum of [MaxVlanMbrs] including the Primary VID
276 Attribute values are inconsistent
277 _entityname_ does not exist
278 Invalid Admin State: _why_
Where Why is:
(xxx) not valid for entity.
(xxx) state is not supported
A port in the reference selector list cannot be unassigned
Admin State is in (xxx) state
Admin State is not in (xxx) state
Cannot enable QL mode if AdminState is set to unassigned
Entity (xxx) is in (xxx) state
Parent state (xxx) higher than (yyy)
Port must (xxx) to change service type
Port state (xxx) higher than (yyy)
279 Invalid Loopback configuration: _why_
Where Why is:

(xxx) is currently active on this port
(xxx) Loopback cannot have Vlans enabled
(xxx) must have at least one Vlan enabled
Loopback config not supported for OAM passive mode.
OAM mode is (xxx)
Swap SA-DA must be (xxx) for EFM OAM Loopbacks
280 Invalid ECPA test configuration: _why_
Where Why is:
Mixed vlan and non-vlan streams in test configuration
More than one test stream set for non vlan tag test (xxx)
Total stream rate (xxx) exceeds port speed
Injector direction (xxx) and Monitor direction (yyy)
281 Data not available for _entityeid_: _why_
Where Why is:
Admin State is UNASSIGNED
PM Thresholds not supported
PM not monitored on CP Flow
282 Port _entityeid_ is not eligible to be put in selector reference list: _why_
Where Why is:
A port can only be added to the reference selector list if it is assigned
An Ethernet port with speed configured as (xxx) cannot be added to the refer-
ence selector list
An Ethernet port with SyncE mode disabled cannot be added to the reference
selector list
It is already present in the list

Error Code Response

ATTRIBUTE SPECIFIC
512 Invalid value: _why_
Where Why is:
(xxx) already used by user (yyy)
(xxx) ARP route can be created
(xxx) can be set only for protocol belonging to protocol group
(xxx) cannot be set
(xxx) C-Tag Control option is not applicable when service type is (yyy)
(xxx) flow need to be MultiCOS enabled
(xxx) flow with UNTAGGED support need to have different COS level support
(xxx) has more than 1 Remote MEP
(xxx) has no Remote MEPs
(xxx) has non-zero EIR
(xxx) is already scheduled in (yyy)
(xxx) is currently active on this port
(xxx) is different than USM user (yyy)
(xxx) is not valid value
(xxx) is the last Superuser
(xxx) not available
(xxx) not available for (yyy) speed
(xxx) not supported by (yyy)
(xxx) not supported for Service Mode (yyy) (IPort Mode)
(xxx) not supported for UNTAGGED frames
(xxx) not supported on CP unit
(xxx) Out Of Range (xxx MIN...yyy MAX)
(xxx) requires valid address/mask
(xxx) speed not supported on (yyy)
(xxx) state is not supported
A port in the reference selector list cannot be unassigned
A Reference entity must Access, Network or BitsIn port
Address cannot be broadcast, multicast, or begin with 0.
Address cannot be (xxx)
Address cannot be broadcast
Address cannot be broadcast, mutlicast or all 0's.
Address cannot be experimental address
Address cannot be Loopback
Address cannot be loopback, broadcast, multicast, or begin with 0
Address cannot be multicast
Address cannot begin with 0
An Ethernet port in the reference selector list cannot be configured as (xxx)
Attribute missing - authentication key
Attribute missing - authentication protocol
Because Service type is in (xxx) mode
Bin index = (xxx) not in range
Cannot be empty
Cannot configure (xxx) loopback type
Cannot create (xxx) flow
Cannot create (xxx) flow with VLAN members

Error Code Response

512 Where Why is:
(continued) Cannot enable QL Mode because the port configuration does not support SSM
Cannot enable QL Mode unless SyncE Mode is also enabled
Cannot enable SVlan on (xxx)
Cannot enable SyncE on a port with speed of 10Mbps
Cannot set Administrative State to Maintenance/Disabled
Cannot set name to empty string
Community (xxx) used by Target Parameter (yyy)
Component does not exist for (xxx)
Component ID - must be access port or network port
Current Network Clock Type does not support this QL value
Data TLV exceeds the allowed maximum of (xxx MIN... yyy MAX)
Delay must be (xxx MIN... yyy MAX)
DHCP client is enabled on (xxx)
DHCP server already enabled on other interface
Disposition cannot be set to (xxx)
Distrubution History Bin index = (xxx) not in range
Duplicate VLAN member (xxx) at positions (yyy) and (zzz)
Dying Gasp is already enabled for IP (xxx) on Target Address (yyy)
Empty string
Ether type can only be (0X88a8) or (0X8100)
Filename is empty
Filename must begin with digit or alphabet letter

Flows with UNTAGGED support need to be MultiCOS enabled
For TOS should not be higher than (xxx MAX)
Given IP address is not valid
Given IP mask is not valid
History Bin index = (xxx) not in valid range
ID (xxx) already used by (yyy)
ID must be 1
Illegal network mask (xxx)
In DHCP Server mode mask cannot be 255.255.255.254 and 255.255.255.255
Ingress PUSH PVID change disallowed
Inner VLAN Tag enabled without Outer VLAN Tag enabled
Interface must be eth0 or management tunnel interface
Invalid character
Invalid first character
Invalid character (xxx) at position (yyy)
Invalid engine ID - contains non-hex characters
Invalid engine ID - must be 12 octets long (first bit is 0)
Invalid engine ID - must be 5 to 32 octets long (first bit is 1)
Invalid engine ID - must be even number of octets
Invalid IP Address
Invalid port
Invalid Port Number
Invalid shelf state - state not supported
IP Addr Overlaps with other interface
IP is 0.0.0.0 for nexthop route
ipaddr: port format required
Key invalid or not strong enough

Error Code Response

512 Where Why is:
(continued) Length exceeds limit - must be 1 to (xxx)
LTM Egress ID must be in hexadecimal format
LTM Egress ID must contain 8 octets
Max value cannot be less than min value
Message processing model (xxx)
Metric must be (0… xxx MAX)
Min value exceeds max value
Mixed DOS and UNIX path
More than 1 enabled server has priority
Multi COS is disabled
Multi-COS flow must have N2A Rate Limiting enabled
Must be disabled for given Line Type
Must have only a-z, A-Z, 0-9, (.), - and _.
Name must be 1- (xxx) characters long and contain only alphanumeric charac-
ters
Name must be unique
Negative number
Network Port disposition is set to (xxx)
No upper case characters
No lowercase characters
Not a valid IP address
Not a valid IP mask
NTP is disabled
Only (xxx) can be created
Only (xxx) IP route can be created
Only 1 (xxx) Flow may exist on Port
Only 1 is allowed as MA COMP index
Only InService and Management states are valid
Out of Range (0...7)
Out of Range (1...100)
Out of Range (xxx MAX)
Out of Range (xxx MIN... yyy MAX)
Password cannot be “password” or “passw0rd”
Password contains character sequence
Password same as username
Password too long
Password too short
Pathname is empty
Periodic schedule cannot have forever duration
Port belongs to different unit.
Port disposition is set to (xxx) or (yyy)
Port does not exist for (xxx)
Port must be Network Port 1
Port service type is (xxx)
Port shaping is disabled
Port speed of 10 Mbps requires SyncE to be disabled
Priority Out Of Range (xxx MIN… yyy MAX)
Probe's Source MEP
Protocol cannot be none

Error Code Response

512 Where Why is:
(continued) QL Mode is enabled; disable QL Mode first
ROLLOVER
Route to subnet/host (xxx) already exists
Sample time cannot be more than (xxx) Duration time
Sample time cannot be more than Duration time
Schedule list contains entity that is not a probe
Schedule list is empty
Schedule type conflicts with other attribute
Security Level of user (xxx) is (yyy)
Selected MEP destination type does not allow to specify ID
Selected MEP destination type does not allow to specify MAC address
Should be between (xxx MIN) and (yyy MAX) (inclusive)
Should be between (xxx MIN) and (yyy MAX) bytes (inclusive)
Should not be higher than (xxx MAX)
Source IP already in use by a Reflector
Source IP already used by a Probe
Source MEP does not exist
Source MEP should be an Up MEP
Specified IP address is already used by a Probe
Specified IP address is already used by another Reflector
Specified MAC address is invalid
Specified name is already in use (xxx) and (yyy)

Specified Source MEP is already used by (xxx)
Specified tag is invalid
Start Time in the past is not allowed
SyncE Mode cannot be disabled because this port is used in the reference
selector list
SysLog is disabled
Target Parameter (xxx) used by Target Address (yyy)
Too few digits
To few special characters
Too many consecutively repeated chars
Total provisioned CIR (xxx) bps exceeds port speed (yyy) bps
Total provisioned EIR (xxx) bps exceeds (yyy) bps
Traffic Management cannot be disabled
Tunnel already exists on (xxx)
Tunnel index must be from 1 to 255
Unknown interval
Unknown MEP destination type
Unknown Network Clock Type
Unknown priority map mode (xxx)
Unknown protocol type
Unknown/unsupported
Unsupported for given Line Type
Untagged support with (xxx)
Untagged support with (xxx) is disallowed
Username too long
Username too short
USM Security Name (xxx) used by Target Parameter (xxx)

Error Code Response

512 Where Why is:
(continued) Value (xxx) out of range
Value (xxx) out of range (xxx MIN… yyy MAX)
Value must be NONE or PUSH
Value not supported for (xxx)
VLAN member cannot be specified as *-*
Vlan members are not supported for Service Mode (xxx)
VLAN member range must be of the form m:n-*, where (xxx)
VLAN members must have a single wild card value (xxx)
VLAN Tag is off but tag is specified
Vlan Tags not unique
513 Mandatory attribute missing.
514 Attribute cannot be set.
515 Attribute not supported
516 Attribute value (xxx) not supported
517 Invalid MAC address.
518 Invalid VLAN tag.
519 Invalid password: _why_
Where Why is:
Key invalid or not strong enough
Password is same as username
520 Invalid IP Address.
521 Invalid Network Mask.
522 Outer VLAN Tag Control must be enabled to enable Inner VLAN Tag Control.
523 _entityname_ does not exist.
524 Attribute cannot be set _why_
Where Why is:
Because maximum (xxx) number of MEP members has been reached
Because Service type is in (xxx) mode

Error Code Response

SPECIAL CONDITIONS
768 Card _cardeid_ not present.
769 Request Failed - Higher priority switch outstanding.
770 Request Failed - requested switch already in operation.
771 Request Failed - no user switch in operation.
772 Request Failed - Protection Group creation in progress.
773 Invalid Loopback Configuration Type.
774 ECPA resource is busy.
775 Resource in Use by Loopback.
776 Resource in Use by ECPA Test.
777 Resource in Use by Etherjack Diagnostics.
778 ECPA test is currently in progress.
779 Invalid stream number.
780 Timed loopback with Vlan tag enabled.
781 Non-Vlan loopback with Vlan tag enabled.
782 ECPA test Stop is currently in progress.
783 ECPA test is not active.
784 Loopback is not active.
785 Loopback already exists.
786 EFM OAM loopback exists.

787 Loopback Disabled on Remote Port EFMOAM configuration.
788 Port EFMOAM Administrative State Disabled.
789 Port EFMOAM Disposition Not in Peer.
790 Port EFMOAM mode Not Active.
791 Manual Etherjack Diagnostics currently in progress.
792 Automatic Etherjack Diagnostics currently in progress.
793 Etherjack Diagnostics Type Requested is not Valid.
794 Invalid test config.
795 Port Not in Auto Negotiation.
796 Linktrace is currently active
797 Loopback is currently active
798 Maximum active linktrace sessions reached
799 Maximum active loopback sessions reached
800 Port media is invalid.
801 Operation is not supported.
802 No Linktrace Reply found.
803 Interface not configured.
804 Route to Host/Subnetwork already exists.
805 Invalid Gateway IP Address.
806 Invalid Route Type.
807 Invalid SWDL message
808 Backup file is locked
809 Invalid backup type

Error Code Response

810 Database has not been backed up
811 Backup directory is empty
812 Failed to archive files
813 Failed to unarchive files
814 Failed to read directory
815 Transfer in progress
816 Transfer not in progress
817 File Transfer Server Type not supported
818 User id not set
819 Remote host not set
820 Remote file not set
821 Local file not set
822 File Name not set
823 Protocol not set
824 Unsupported protocol
825 Transfer protocol has been disabled
826 Invalid url
827 Transfer canceled
828 Unable to access local file
829 Transfer execute failed
830 Error string returned
831 Bad archive file
832 Error syncing with scu
833 Error processing topology change event
834 SCU push failed
835 Flash erase failed
836 Flash partition sync failed
837 Install Failed
838 Activate Failed
839 Cancel Activate Failed
840 Validate Failed
841 Revert Failed
842 Operation not allowed in current state
843 Invalid Validation Time
844 Invalid Reboot Time
845 Operation not allowed: Database upload in progress
846 Operation not allowed: Database download in progress
847 Operation not allowed: Database backup in progress
848 Operation not allowed: Database restore in progress
849 Operation not allowed: Software download in progress
850 Operation not allowed: Software install in progress
851 Operation not allowed: Software upgrade in progress
852 Operation not allowed: Software validate in progress

Error Code Response

853 Operation not allowed: Software cancel-upgrade in progress
854 Operation not allowed: Software revert in progress
855 Operation not allowed: System rebooting
856 Operation not allowed: System software being upgraded
857 Software is incompatible for Network Element
858 Sysdefdb directory is empty
RESOURCE ERRORS
1024 Exhausted Total Number of Policers.
1025 Exhausted Total Number of Queues.
1026 Exhausted Total Number of Memory Segments.
1027 Exhausted Total Number of VLAN Lookups.
1028 Exhausted Total Number of EVC Lookups.
1029 Insufficient bandwidth for CIR/EIR settings.
1280 Rules check failed.
1281 Rules check failed: (_errstr_).
SOFTWARE RELATED
4096 Invalid message qualifier.
4097 Resource is busy.
4098 Database operation failed: _why_
Where Why is:

Db State is not ok
Can't reopen System Default Db
Build Shadow Tree failed
4099 Loading data from database failed.
4100 User transaction does not exist.
4101 User transaction has not been validated.
4102 Request has been timed out.
4103 Transaction id is 0.
4104 Cannot get global system data.
4105 Invalid application event.
4106 No FROM port found for NE.
4107 Configfile operation failed.
4108 Loading data from configfile failed: _why_
Where Why is:
Can't open configfile
_configFileName_failed_command
Init load failed
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

Error Code Response

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 xx.yy

Chapter 8
Provisioning Rules
Introduction
This chapter provides technical data for the FSP 150CC-GE11x serials. The fol-
lowing is provided:
• Entity State Descriptions

• User Authorization Privilege Levels
• Configuration Settings, Rules and Dependencies
Entity State Descriptions

A state model is maintained for each entity in the system. The state of an entity
is derived from its Administrative State, its Operational State and its Secondary
States.
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:
• IS (in-service) - this is the 'normal' state for an entity that is configured to be
fully operational.
• 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 addi-

tional characteristics associated with this state are that the user data and
management traffic will continue to flow.
• 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.
• Disabled - this is ALSO an “Out of Service” state (i.e., it inherits the proper-
ties 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.
• 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.
Administration State Model Details

It should be noted that the Management, Maintenance and Disabled states are
ALL members of the “Out-Of-Service” (OOS) state. An entity transitional
between any of these three states does not have any impact on it's Parent or
Child entities.
• The equipment Administrative state model will only utilize the In-service and
Management states
• When in the Management or Maintenance state, all alarms against that
entity will be suppressed. The entity will otherwise function as normal.
• When in the Disabled state, user data traffic is suppressed.
• In order to perform maintenance actions on an entity (e.g., Loopback, Diag-
nostics, etc.) the entity must first be put into the Maintenance state.
• 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.
• The Operational State of an entity can be either:
o Normal
o Outage
• 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 Net-
work port. The working Network port cannot be Unassigned.
• The DCN facility Administrative state model is limited to the following states:
o In-service
o Management
o Unassigned

Chapter 8 Provisioning Rules
• 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 sup-
ported. 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).
Parent/Child rules for Equipment entities:
• If an Equipment entity is In-service, its child entities Port entities can be in
any state (supported by that entity).
• If an Equipment entity is Management, its child entities can be in any “Out of
Service” state or Unassigned.
• If an Equipment entity is Unassigned, its child entities must be unassigned.
Parent/Child rules for Port entities:
• If a Port Entity is in In-Service state, its child entities (EVCs) can be in

In-Service, Management or Unassigned state.
• If a Port Entity is in Management, Maintenance or Disabled state, its child
entities can be in Management or Unassigned state
• If a Port Entity is in Unassigned state, its child entities must be in Unas-
signed state.
Parent/Child rules for EVC (Flow) entities. Note that child entities of EVCs are
not user editable.
• If an EVC Entity is in In-Service state, its child entities (policers, shapers)
will be in In-Service.
• If an EVC Entity is in Management state, its child entities will be in Manage-
ment.
• If an EVC Entity is in Unassigned state, its child entities will be in Unas-
signed 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 Dis-
abled) 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:

• editing a Port entity from In-service to Management, Maintenance or Dis-

abled will result in ALL EVCs (Flows) that are children of that Port being
changed from In-service to Management. If an EVC was already Manage-
ment or Unassigned prior to the edit of the Port state, it will not change.
• editing a Port entity from In-service, Management, Maintenance or Disabled
to Unassigned will result in ALL EVCs (Flows) that are children of that Port
being changed to Unassigned.
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
PS
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
Note
also.
Due to the many-to-one relationship between Port entities and EVCs (Flows),
the following behaviors will be implemented:
• editing a Port entity from Management, Maintenance or Disabled to In-Ser-
vice will result in ALL EVCs (Flows) that are children of that Port being
changed from Management to In-Service. If an EVC was Unassigned prior
to the edit of the Port state, it will remain Unassigned.
• editing a Port entity from Unassigned to Management, Maintenance or Dis-
abled will result in ALL EVCs (Flows) that are children of that Port being
changed to Management.
• editing a Port entity from Unassigned to In-Service will result in ALL EVCs
(Flows) that are children of that Port being changed to In-Service.
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
PS
it affects the EVC's Admin state, the above rules will apply such that
Note 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.

Table 38: State Codes and Descriptions

State Entity State Definition
Administration State - Disabled User Traffic is not passed in this
Equipment and state; management traffic is
Facilities passed. Alarms are squelched
in this state.
IS Normal, in-service, traffic
passing state of the entity.
Maintenance Mandatory state for initiating
loopbacks, Etherjack®
Diagnosis. Alarms are
squelched in this state.
Management “Out-Of-Service” state of entity,
traffic is still passed, alarms are
squelched (i.e., not reported).
Unassigned Traffic (user or management)
not passed in this state. Alarms
are not monitored in this state.
Operational State - Normal Normal, in service, traffic
Equipment and passing state of the entity.

Facilities Outage The entity is not operational,
due to alarm condition.
Secondary States - ACT Entity is active.
Equipment and AINS Automatic in-service.
Facilities DSBLD Disabled
FAF Facility failure.
FLT Fault detected.
LPBK Loopback state.
MAINT Maintenance state.
MEA Mismatched equipment.
STBY Standby hot.
SGEO Supported entity outage.
UAS Unassigned.
UEQ Unequipped.
OAM Administration Disabled Disabled.
State Enabled Enabled.
OAM Discovery State Active Send Local Active send local.
Fault Fault detected.
Passive Wait Passive wait.
Send Any Send any.
Send Local/Remote Send local/remote.
Send Local/Remote OK Send local/remote OK.

Table 38: State Codes and Descriptions (Continued)

File Services Status Cannot revert Cannot revert.
Failure Failure.
File not found File not found.
In progress In progress.
Install failed Installation failed.
Invalid file type Invalid file type.
Login failed Login failed.
No backup database There is no backup database.
No space left No disk space left.
No software to install There is no software to install.
Permission denied Permission denied.
Revert failed Revert failed.
Server unreachable Server unreachable.
Success Successful completion.
Software not installed Software not installed.
Upgrade failed Upgrade failed.
Validation timer not active Validation timer not active.
Database or Upgrade Database Backup Database backup.
Current State Database Download Database download.
Database Restore Database restore.
Database Upload Database upload.
Idle Idle.
Rebooting Rebooting.
Software Cancel Upgrade Software cancel upgrade.
Software Download Software download.
Software Install Software install.
Software Upgrade Software upgrade.
Software Validate Software validate.
Software Revert Software revert.
Protection Group FORCED PROTECT Forced to Protect.
Status FORCED WORKING Forced to Working.
LOCKOUT PROTECT Lockout to Protect.
MANUAL PROTECT Manual to Protect.
MANUAL WORKING Manual to Working.
NO OUTSTANDING REQUEST There is no outstanding request.
SD PROTECT Signal Degrade on Protect.
SD WORKING Signal Degrade on Working.
SF PROTECT Signal Failure on Protect.
SF WORKING Signal Failure on Working.
WAIT TO RESTORE Wait to restore.

Table 38: State Codes and Descriptions (Continued)

Protection Unit State Active Indicates this is the active unit.
Standby Indicates this is the standby
unit.
Test Status Aborted Test has been aborted.
(Diagnostics) Completed Test has completed.
Initial Test is initiating.
In-progress Test is in-progress.
Stopped Test has been manually
stopped.
User Authorization Privilege Levels

Refer to the following table for user authorization privilege levels.
Table 39: User Authorization Privilege Levels

User Level Description

Superuser Has access to all commands, including
administration commands.
Provisioning Has access to all commands with the exception of
other user administration options.
Maintenance Has access to a limited set of commands which
support maintenance actions, such as testing,
loopbacks, diagnostics.
Retrieve Has access to commands for displaying
configuration settings and performance data.
Configuration Settings, Rules and

Dependencies
The following provides a summary of configuration default settings, configura-
tion options, provisioning rules and dependencies. For Entity EIDs, please refer
to the FSP 150CC-GE11x Command Line Interface Reference Guide.
The following configuration options and rules tables provide high level option
descriptions and valid entries using the eVision web browser management tool.
The high level option descriptions provided here assume a good working knowl-
edge of the use of each option, and are intended to be used as a guide to oper-
ate, configure and maintain the system. Additional information for each option
description can be found in the FSP 150CC-GE11x Command Line Interface
Reference Guide and Application Notes for specific features. For more informa-

Configuration Settings, Rules and Dependencies
tion regarding navigating and using the eVision, see Chapter 3: eVision Web
Browser Management Tool.
This section provides the following configuration settings information:
• Factory Default Parameters and Maximum Bandwidth on p. 606
• System Configuration Options and Rules on p. 618
• Pass-Through Flow Configuration Options and Rules on p. 652
• LAG Configuration Rules on p. 656
• Network Port Configuration Options and Rules on p. 661
• Access Port Configuration Options and Rules on p. 666
• Management Tunnel Configuration Options and Rules on p. 701
• IPv6 over IPv4 Tunnel Configuration Options and Rules on p. 707
• CPD Filters Options and Rules on p. 709
• LLDP Configuration Settings on p. 713
• Loopback Settings on p. 714
• Environmental Alarms Settings - GE114H/GE114PH on p. 717
• Performance Monitoring Settings on p. 717
• ESA Options and Rules on p. 746
• Scheduled ESA Activity Settings on p. 750
• CFM Configuration Options and Rules on p. 752
• PTP Configuration Options and Rules (GE114S/GE114SH) on p. 763
• SAT Configuration Options and Rules on p. 783
Factory Default Parameters and Maximum Bandwidth

When the database of the FSP 150CC is modified, it stores the changes in
non-volatile memory. If a power loss / system reboot occur, all configuration
data is retained. There are three versions of the database always resident on
the system, plus a “standby” copy of the current database. The three versions
are the current running configuration, System Default (a copy that can be modi-
fied by a user) and Factory Default (a copy that cannot be modified). When first
commissioned, these three database versions are identical. As provisioning
occurs, the current running configuration database is updated with each change
entered.
Refer to Table 40 for ADVA Optical Networking “factory default” configuration
settings. Each functional area and default configuration settings are shown in
order, as seen when using the eVision web browser management tool. Refer to
Table 41 for Network port maximum bandwidth, Access port maximum band-
width and default Access port CIR/PIR values. For default TCA settings, refer to
Performance Monitoring Settings on p. 717.

Table 40: Factory Default Configuration Settings

Functional Area eVision Parameter Default Setting
Name FSP150CC-GE112/GE114/
GE114S/GE114H/GE114SH/
GE114PH
Description FSP150CC-GE112/GE114/
GE114S/GE114H/GE114SH/
GE114PH
Location (blank)
Contact (blank)
CLI Prefix ADVA
Proxy ARP Disabled
Proxy NDP Disabled
IPv6 Forwarding Disabled
Serial Port Enabled
Serial Port Auto Log Off Enabled
System Telnet Disabled
Configuration
SSH Enabled
HTTP Enabled
HTTPS Enabled
FTP Disabled
SFTP Enabled
System SCP Enabled
Authentication Traps Disabled
SSL Cipher Strength Low
CLI Security Prompt Disabled
SNMP Engine ID (variable)
Management Traffic Disabled
Bridging
Mgmt Traffic Bridging Disabled
Security
Security Log Syslog Disabled
Syslog Disabled
Alarm Log
Local Logging Enabled
Syslog Disabled
Audit Log
Local Logging Enabled
Log Server Method User Defined
Log Server 1, 2, 3 IPv4 0.0.0.0
Syslog
IP Address
Log Server 1, 2, 3 Port 514
IP Version IPv4
Access Control IPv4 Address 0.0.0.0
List (ACL)
Network Mask 255.255.255.255
(entries 1-10)
Control Disabled


Transmission Interval 30
Hold Time Multiplier 4
Re-initialization Delay 2
Notification Interval 30
LLDP Maximum Neighbors Discard NEW
System Action
(Continued) LLDP DEST ADDR-1 01:80:c2:00:00:0e
LLDP DEST ADDR-2 01:80:c2:00:00:03
LLDP DEST ADDR-3 01:80:c2:00:00:00
Security Banner This is a private system.
Banner Unauthorized access or use
may lead to prosecution.
System Time Of System Time Of Day Local
Day Date/Time (variable)
Name FSP150CC-GE112/GE114G
E114H/ GE114PH
Location (blank)
NE Configuration Contact (blank)
CLI Prefix NE-1
MEF BWP Line Rate
Administrative State IS
NTE11x Alias (blank)
Configuration Administrative State IS
(e.g., SNMP Dying Gasp Disabled
NTE114H-1-1-1)
Alias (blank)
Administrative State E1000-N-1 = IS
E1000-N-2 = Unassigned
Network Element Media Type Copper
MTU 9612
MDIX Auto
Configured Speed Auto

E1000 Network Auto Diagnostic Enabled
Port Facilities Drop Eligibility Indicator Enabled
Port Shaping Disabled
Port Shaped Speed 0 bps
Q in Q EtherType 0 (hex)
Q in Q EtherType Disabled
Link Loss Forwarding Disabled
Port LLF Status
Link Loss Forwarding 0
Delay


Link Loss Forwarding No Action
TX Action
Link Loss Forwarding None selected
Trigger Events
Link Loss Forwarding E1000-N-1=1
Local Link ID E1000-N-2=2
Remote Link IDs None selected
CPD Filters
Bridge Group Pass Thru
Bridge Group Pause Pass Thru
Bridge Group Discard
EFM-OAM
Bridge Group LACP Pass Thru
Bridge Group LACP Pass Thru
Marker
Bridge Group SSM Discard
Bridge Group Port Pass Thru
Authentication
Bridge Group BPDU Pass Thru

Network Element E1000 Network Bridge Group Bridge Pass Thru
(Continued) Port Facilities Reserved
Bridge Group LLDP Pass Thru
GARP Group Pass Thru
GARP Group GVRP Pass Thru
GARP Group GMRP Pass Thru
GARP Group GARP Pass Thru
Cisco Pass Thru
Cisco ISL Pass Thru
Cisco PAgP Pass Thru
Cisco UDLD Pass Thru
Cisco CDP Pass Thru
Cisco VTP Pass Thru
Cisco DTP Pass Thru
Cisco PVSTP+ Pass Thru
Cisco Uplink Fast Pass Thru
Cisco VLAN Bridge Pass Thru
Cisco L2PT Pass Thru
LAN Bridges Pass Thru
EFM-OAM
OAM Control Disabled (2)
Mode Active (1)


A2N Shaper
Port A2N Shapers 128 for E1000-N-1
Buffer Size N/A for E1000-N-2
PCP Configuration
PCP DE Encoding None
Mode
Sync-E Configuration
Sync-E Mode Disabled
QL Mode Disabled
Assumed QL QL-EEC1
Expected QL QL-NONE
E1000 Network LLDP Configuration
Port Facilities SNMP Notification Disabled
Admin Status Disabled
Basic Optional TLVs Port Descriptions, System
Name, System Description,
System Capabilities
ELMI Configuration
ELMI Control Disabled
T392 Timeout 15
N393 Count 4
Async Status Enabled
Min Async Status 1
Interval
Alias (blank)
Administrative State Unassigned
Network Element Media Type Copper
(Continued) MTU Size 9600
MDIX Auto
Auto Diagnostic Enabled
Drop Eligibility Indicator Enabled
Service Type EPL
Ethernet Access
Port Facility AFP AFP ALL
Q in Q Ethertype 0 (hex)
Q in Q Ethertype Disabled
Override
802.3 Pause RX Disabled
802.3 Pause TX Disabled
Port Shaping Disabled
Port Shaped Speed 0
Link Loss Forwarding Disabled
Port LLF Status


Link Loss Forwarding 0
Delay
Link Loss Forwarding No Action
TX Action
Link Loss Forwarding E1000-A-2=2
Local Link ID E1000-A-3=3
E1000-A-4=4
E1000-A-5=5
E1000-A-6=6
Link Loss Forwarding None selected (Empty)
Trigger Events
Remote Link IDs None selected (Empty)
CPD Filters
Tunnel MAC 01:00:0c:cd:cd:d0
Bridge Group Pass Through
Bridge Group Pause Pass Through
Bridge Group Discard
EFM-OAM
Bridge Group LACP Pass Through
Bridge Group LACP Pass Through

Marker
Bridge Group SSM Discard
Network Element Ethernet Access
(Continued) Port Facility
Bridge Group Port Pass Through
Authentication
Bridge Group BPDU Pass Through
Bridge Group Bridge Pass Through
Reserved
Bridge Group LLDP Pass Through
GARP Group Pass Through
GARP Group GVRP Pass Through
GARP Group GMRP Pass Through
GARP Group GARP Pass Through
Cisco Pass Through
Cisco ISL Pass Through
Cisco PAgP Pass Through
Cisco UDLD Pass Through
Cisco CDP Pass Through
Cisco VTP Pass Through
Cisco DTP Pass Through
Cisco PVSTP+ Pass Through
Cisco Uplink Fast Pass Through
Cisco VLAN Bridge Pass Through
Cisco L2PT Pass Through


LAN Bridges Pass Through
EFM-OAM
OAM Control Disabled (2)
Mode OAM Active (1)
N2A Shaper
Port N2A Shapers 0
Buffer Size
PCP Configuration
PCP DE Encoding enc-none(1)
Mode
Sync-E
Sync-E Mode Disabled
QL Mode Disabled
Ethernet Access Assumed QL QL-EEC1
Port Facility Expected QL QL-NONE
LLDP Configuration
SNMP Disabled
Admin Status Disabled
Basic Optional TLVs Port Descriptions, System
Name, System Description,
System Capabilities
ELMI Configuration
ELMI Control Disabled
T392 Timeout 15
N393 Count 4
Async Status Enabled
Network Element Min Async Status 1
(Continued) Interval
Alias (blank)
DCN (eth0)
MDIX Auto
Alias (blank)
APN N/A
3G Modem Dial # N/A
Redial Timer 10
User Name N/A
Password =**
Alias (blank)
PSU
PT Flow PT FLOW-1-1 (PT Flow not created at
factory default)


PROT GROUP-1-1-1-1 (Protection Group not created
NTE11x
at factory default)
Protection Groups
ERP-1-1 (ERP Group not created at
NE-1
factory default)
LAG-1-1 (LAG Group not created at
LAG
NE-1 LAG-1-2 factory default)
LAG-1-3
SHG-1 (SHG Group not created at
SHG NE-1
factory default)
Alias chassis
Administrative IS
SYNC-1-1-1-1 Network Clock Type Option 1-SDH Regional Clock
WTR Time 5
Selection Mode Priority Mode
Alias (blank)
Administrative Unassigned
WTR 5
TIME
Selection Mode Priority Mode
CLOCK-1-1-1-1
(GE114SH) Time Holdover 5000

Performance
Sync Ref Candidate Disabled
Expected QL QL-NONE
Alias (blank)
Synchronization Administrative Unassigned
(GE114S/GE114 Line Type E1
SH) Line Code E1 HDB3
BITS-IN Frame Format E1 CRC4
SA Bit Bit 4
QL Mode Disabled
Assumed QL QL-EEC1
Expected QL QL-NONE
Alias (blank)
Line Type E1
Line Code E1 HDB3
BITS-OUT Frame Format E1 CRC4
SA Bit Bit 4
QL Mode Disabled
Squelch QL QL-NONE
Line Build Out None


Alias (blank)
Signal Direction Output
CLK-1-1-1-1
Frequency Source Eid None
Squelch Control Never
Squelch QL QL-NONE
Alias (blank)
Signal Direction Output
Cable Delay 0
PPS-1-1-1-1
Compensation
Source Eid None
Synchronization
(Continued)
Squelch QL QL-NONE
Alias
TOD-1-1-1-1 Time of Day Source Eid None
Squelch QL QL-NONE
Alias (blank)
PPS generation 3SATS
GPS-1-1-1-1
condition
Antenna Cable Length, 5
m
IP Address 192.168.0.1
Net Mask 255.255.255.0
DHCP Disabled
eth0 (DCN) DHCP Role DHCP Client
RIPv2 false
DHCP Client ID Control false
DHCP Client ID FSP150CC-GE112/GE114/G
E114H/ GE114PH
Entity ID 1
Communications
Tunnel Name LTP
Associated Port NETWORK PORT-1-1-1-1
Encapsulation Type Ethernet
Mgmt Tunnel-1
IP Mode IPv4 Only
(E1000-N-1)
IP Address 0.0.0.0
Subnet Mask 0.0.0.0
DHCP Enabled
DHCP Log Server Disabled
Control


DHCP NTP Server Disabled
Control
DHCP Client ID Control Disabled
DHCP Client ID Type MAC Address
DHCP Client ID variable (mac address of
net-1)
DHCP Class ID Control Enabled
DHCP Host Name Enabled
Control
DHCP Host Name Type System Name
DHCP Host Name FSP150CC-GE11x
Mgmt Tunnel-1 Edit System Default Disabled
Communications (E1000-N-1) Gateway
(Continued) (Continued)
Gateway IPv4 Address variable
Tunnel Mode MAC Based
C-Tag VLAN Enabled
C-Tag VLAN ID 4095
S-Tag VLAN Disabled
S-TAG VLAN ID 4095

RIPv2 Disabled
CIR 256000
EIR 768000
Buffer Size 32
COS 7
IPv6 over IPv4 Tunnels (not created at factory default)
NE-1
Power Usage 99%

Global Setting Threshold
PSE Notification Control false
Administrative false
Port Setting Power Pairs Alternative A
PSE Port Type Empty
Community Names public, private
Communities
Access Type read-only (public)
read-write (private)
SNMP User ADMIN
User Name ADMIN
SNMP Engine ID local
USM Users Security Name ADMIN
Security Level No Authentication
User Access Type Read/Write
Authentication Protocol None
Privacy Protocol None


SNMP User MONITOR
User Name MONITOR
Engine ID local
Security Name MONITOR
SNMP User OPERATOR
User Name OPERATOR
Engine ID local
USM Users Security Name OPERATOR
(Continued) Security Level No Authentication
SNMP
(Continued) User Access Type Read/Write
SNMP User PROVISION
User Name PROVISION
Engine ID local
Security Name PROVISION
SNMP Dying Gasp SNMP Dying Gasp (no target addresses are
provisioned, thus this option
is disabled)
Local User netadmin
Login netadmin
Password ChgMeNOW
Privilege Provisioning (3)
CLI Paging Enabled (1)
Comment Default User
Local Users Login Timeout 15 (minutes)
Administration
Local User root
Login root
Password ChgMeNOW
Privilege Superuser (4)
Login Timeout 15 (minutes)


Local User user
Login user
Local Users Password ChgMeNOW
(Continued) Privilege Maintenance (2)
Login Timeout 15 (minutes)
No remote user entries N/A
Remote Users
Administration at default
(Continued) Authentication Protocol None (1)
Authorization Type PAP (1)
Remote
NAS IP Address 0.0.0.0
Authentication
Access Order Local (1)
Remote Authentication Disabled (2)
Servers 1-3
Security Policy Policy Strength High (3)
Generate Certificate or Deselected
Key Generation
Key

Table 41: Maximum Network Port/Access Port Bandwidth

Associated EID Port Type Max. CIR Max. EIR
NETWORK PORT-1-1-1-1, E1000 (Fiber SFP or 1000000000 (bps) 8000000000 (bps)
NETWORK PORT-1-1-1-2 Copper):
ACCESS PORT-1-1-1-3 E1000 (Fiber SFP or 1000000000 (bps) 8000000000 (bps)
ACCESS PORT-1-1-1-4 Copper):
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
PS
bandwidth. At default configuration, no management tunnels are

Note provisioned.
System Configuration Options and Rules

Refer to the following table for System configuration settings and associated
rules when using the eVision web browser. Default settings are identified in
bold. The following editable system settings are shown in order, as seen when
using the eVision web browser management tool in Configuration mode.
System configuration options and rules consist of the following entities, which
are provided in Table 42:
• System Configuration
• Network Element (NE-1) Configuration
• NTE11x Configuration
• PT Flows (GE114x)
• Protection Groups (NE-1)
• Power Supply Equipment (GE114PH)
• LAG
• SHG
• Synchronization (GE114S/GE114SH)
• Communications
• SNMP
• Administration

Table 42: System Configuration Settings

Description / Option Settings /
Parameter
Applicable Rules Defaults
System Configuration
System (Edit System)

CLI Prefix When using CLI, this string is displayed at the highest
level prompt after logon. This string can be up to 64
ADVA
printable ASCII characters long, but cannot use the
“space” character.
Management This option is used to enable the management traffic Disabled
Traffic Bridging bridging feature. When bridging is disabled, existing
http, https, telnet, and ssh sessions are unresponsive
for up to 3 seconds. When bridging is enabled, Enabled
existing http, https, telnet, and ssh sessions are
unresponsive for up to 10 seconds.
Mgmt Traffic This option limits acceptance of DCN packets to Disabled
Bridging Security those with an ADVA Optical Networking OUI in the
source MAC (00:80:EA:XX:XX:XX,
00:0B:90:XX:XX:XX, or 00:D0:8B:XX:XX:XX). This Enabled
option is only available if Management Traffic

Bridging is enabled.
Proxy ARP This option defines if the proxy ARP functionality Disabled
should be enabled. If two or more ADVA Optical
Networking FSP 150s are connected via
Management Tunnel as well as connected to the
same LAN, then only one of the NEs/NIDs should Enabled
have the PROXYARP option enabled. Otherwise,
there will be multiple ARP responses for a single
ARP request for a remote reachable IP Address.
Proxy NDP If Enabled, the NE will act as a proxy to respond Disabled
remote Neighbor Discovery Protocol (NDP) request
with the destination MAC or advertise the prefix of the
network. This option can be Enabled only after IPv6 Enabled
Forwarding is Enabled.

Table 42: System Configuration Settings (Continued)

Parameter
IPv6 Forwarding working mode for GE11x: Disabled
• Forwarding enabled: Router mode.
o In Router mode, system support router for-
warding functionality among DCN and man-
agement tunnel interface.
o Any DCN or management tunnel interface
does not receive Router Advertisement (RA)
message from link. Stateless Address
Auto-configuration must be disabled. Also, Enabled
Ipv6OverV4 tunnel with type of ISATAP is not
supported.
o If RA is configured on a DCN or Management
Tunnel, it is capable of dispatching IPv6
Router Advertisement (RA) to external host
connected.
• Forwarding Disable: Host mode.
FTP Enables or disables File Transfer Protocol access to Enabled
the system. If enabled, the FTP client on the system Disabled
can be used for file transfer.
HTTP Enables or disables Hypertext Transfer Protocol Enabled
access to the system. If enabled, the user can access Disabled
the GUI interface using HTTP. Note: HTTP is an
unsecured protocol. Using this protocol to access the
system could compromise the security of the system.
HTTPS Enables or disables Hypertext Transfer Protocol Enabled
Secure access to the system. If enabled, the user can Disabled
access the GUI interface using HTTPS.
SSL Cipher Sets the strength of the SSL cipher. Encryption Low
Strength strength is measured in key length — number of bits in Medium
the key. To decipher an SSL communication, one High
needs to generate the correct decoding key. Mathe-
matically speaking, 2n possible values exist for an
n-bit key. Thus, 40-bit encryption (low) involves 240
possible values, 56-bit encryption (medium) involves
256 combinations, and 128-bit encryption (high) 2128
possible combinations.
Changing the SSL strength setting results in
disconnecting all active web access users, requiring
them to re-login.
SCP Enables or disables Secure Copy Protocol access to Enabled
the system. If enabled, SCP can be used for file Disabled
transfer.
Serial Port Enables or disables RS-232 serial port access to the Enabled
system. Disabled


Parameter
Serial Port Auto If Enabled, causes Auto Logoff of the user session on Enabled
Log Off the serial port, when the serial port is disconnected. Disabled
SFTP Enables or disables Secure File Transfer Protocol Enabled
access to the system. If enabled, SFTP can be used Disabled
for file transfer.
SSH Enables or disables Secure Shell (TCP/UDP port 22) Enabled
access to the system. If enabled, the user can access Disabled
the system through an SSH connection.
Telnet Enables or disables Telnet (TCP port 23) access to Enabled
the system. If enabled, the user can access the Disabled
system through a telnet connection. Note: Telnet is
an insecure protocol. Use of this protocol can have
an impact on the security of the system.
Authentication Enables or disables SNMP Authentication Traps. If Enabled
Traps enabled, SNMP Authentication traps will be sent to Disabled
the configured trap host.
CLI Security Enables or disables the following CLI security Enabled
Prompt prompt: Disabled
************************************************************
*
This is a private system. Unauthorized access or
use may lead to prosecution.
************************************************************
*
Do you wish to continue [Y|N]-->

SNMP Engine ID Allows the user to edit the SNMP Engine ID which 0xhhhhhhhhhhhhhhhh
consists of 22 Hexadecimal characters. hhhhhh
Security Log (Edit Security Log)
Syslog Enable or Disable logging of security related activity Disabled
to the Syslog server. Enabled
Alarm Log (Edit Alarm Log)
Syslog Enable or Disable logging of alarm activity to the Disabled
Syslog server. Enabled
Local Logging Enables or Disables sending Alarm messages to the Enabled
local log. If set to Enabled, view logs by selecting the Disabled
Alarm Log tab.
Audit Log (Edit Audit Log)
Syslog Enable or Disable logging of audit related activity to Disabled
the Syslog server. Enable


Parameter
Local Logging Enables or Disables sending Audit messages to the Enabled
local log. If set to Enabled, view logs by selecting the Disabled
Audit Log tab.
Syslog (Edit Syslog)

IP Address IP Address of a Syslog Server. Entering an IP
address enables transmission of alarm information to
a Syslog Server. Up to three Syslog Servers can be
configured. All syslog messages generated by the 0.0.0.0
unit are sent to all configured Syslog Servers. Setting
the IP Address to 0.0.0.0 will result in the server not
being used.
Port The IP port of each registered Syslog Server. The
514
default port number is 514.
Access Control List (Edit ACL for ACL ID 1 through 10)
Network Address IP Address of the user/subnet allowed to access the
GE11x. Up to 10 user/subnetwork IP addresses can 0.0.0.0
be entered (ACL ID 1-10).
Network Mask Network Mask for the user/subnet IP address allowed
to access the GE11x. Up to 10 user/subnetwork IP
255.255.255.255
address and Network Mask combinations can be
entered (ACL ID 1-10).
Control Each Network Address/Network Mask combination Enabled
can be Enabled or Disabled. The default is Disabled.
Disabling the ACL filtering will “deny” the
corresponding management traffic. Enabled entries Disabled
apply to all management interfaces.
Security Banner (Edit Banner)
Banner Defines a custom security banner (a text string of up This is a private
to 2000 characters in length) which is displayed when system. Unauthorized
a user logs onto the system. This banner is displayed access or use may
on CLI and web browser logins. lead to prosecution.
System Time of Day (Edit System Time of Day)
System Time of Selects the desired system Time of Day mode. Local
Day NTP
• Local: the Time of Day is based on the local oscil-
lator.
• NTP: the Time of Day is updated based on an PTP
external NTP server. (GE114S/GE114SH)
•
If System Time of Day is set to Local:


Parameter
Date/Time The date in format: yyyy-mm-dd and the time in
format hh:mm:ss. If Unicast is selected for NTP Mode
and an NTP server has been linked, changing the
(yyyy-mm-dd)
date and time will be denied. If a date/time is entered
(hh:mm:ss)
that exceeds the provisioned user GUI timeout value
in respect to the current system time, then the user
session will time out.
If System Time of Day is set to NTP:
NTP Server Define NTP Server to be specified by user or to get User Defined
Method from a DHCP server by sending a broadcast DHCP
DHCP
query requesting IP address information.
Primary Server This option is used to configure the IP version and IPv4
the IP address of the primary NTP Server. Leaving IPv6
the IP addresses blank disables this server from 0.0.0.0
being used. Only available when NTP Server Method
0000:0000:0000:0000:
is User Defined.
0000:0000:0000:0000
Backup Server This option is used to configure the IP version and IPv4
the IP address of the backup NTP Server. Leaving IPv6
the IP address blank disables this server from being 0.0.0.0

used. Only available when NTP Server Method is
User Defined. 0000:0000:0000:0000:
0000:0000:0000:0000
Polling Interval Set the NTP polling interval in seconds. Allowed
settings are from 16 to 1024 seconds as powers of 2 16
(16, 32, 64, 128, 256, 512, 1024). Default is 16.
Active Server If both Primary and Backup Server IP Addresses are Primary
configured, the user may switch between them using
Backup
this setting.
If System Time of Day is set to PTP, the PTP Licensable Feature must have been Enabled and a
Telecom Slave have been created:
Source TOD Selects the source TOD Clock (TS-1-1 if
(drop down list of
Clock provisioned).
available Telecom
Slave entities)
Restore System Defaults

Restore System Allows the user to reset the NE back to system OK
Defaults defaults. NOTE: This can cause the loss of all traffic,
user data and DCN communications settings. This
should only be done when re-configuring or Cancel
relocating the NE, or as a last resort when
troubleshooting traffic or communications problems.


Parameter
Network Element (NE-1) Configuration
NE-1 (Edit)
Name This is a text string containing a meaningful
description of the NE. The NE Name must start with a up to 256 characters
letter, end with a letter or digit, and have as interior FSP150CC-GE112/
characters only letters, digits, and hyphens. GE114/ GE114H/
Maximum length is 256 characters. Upper and lower GE114PH
case characters are allowed.
Location This is a text string entry that should specify where
the system is located with enough detail so that up to 256 characters
operations personnel can easily locate the device. (blank)
Maximum length is 256 characters.
Contact This is a text string entry that should specify the
name and contact information of the individual up to 256 characters
responsible for the administration of the system. (blank)
Maximum length is 256 characters.
CLI Prefix When using CLI, this string is displayed when
navigating to the Network Element level menu. This up to 64 characters
string can be up to 64 printable ASCII characters NE-1
long, but cannot use the “space” character.
Bwp Mode Select the desired Bandwidth profile (BWP). Linerate
Changing the BWP mode is not allowed while there
Inforate
are active SAT tests.
Administrative Defines the NE administrative state. IS is In Service IS
State and is the default value. See Entity State
Descriptions on p. 599. Management
NTE11x Configuration
GE11x (Edit)
Alias A text and/or number string the user enters to
up to 64 characters
uniquely identify this entity. This string can be up to
(blank)
64 printable ASCII characters long.
Administrative Defines the GE11x administrative state. IS is In IS
State Service and is the default value. See Entity State
Management
Descriptions on p. 599.
SNMP Dying Enables or disables dying gasp message via SNMP. Enabled
Gasp When enabled, OAM dying gasp messages are sent Disabled
on EFM-enabled interfaces.
Network Ports and Access Ports
See Network Port Configuration Options and Rules on p. 661 and Access Port Configuration
Options and Rules on p. 666.
DCN (eth0) (Edit Configuration)
up to 64 characters
(blank)


Parameter
Administrative Enables or disables the Data Communications IS
State Network. IS is In Service and is the default value. See Management
Entity State Descriptions on p. 599. Unassigned
Configured Defines the line rate of the port and whether it is in Auto
Speed half duplex or full duplex mode. Auto 100 Full
Auto 100 Half
Auto 10 Full
Auto 10 Half
100 Full
100 Half
10 Full
10 Half
MDIX Defines the Media Dependent Interface, Crossover Auto
function for copper interfaces. MDIX allows the Crossed
interface to change cable signal assignments to Uncrossed
compensate for using the incorrect cable type.
Power Supply Unit (PSU-1, PSU-2) - GE114H/GE114SH/GE114PH (Edit Configuration)

up to 64 characters
(blank)
Administrative Enables or disables PSU-1 and PSU-2. IS is In IS
Management
PT Flows (GE114x)
Flow
Create/Edit/Delete - See Pass-Through Flow Configuration Options and Rules on p. 652

Protection Groups (NE-1)
NTE11x (Add Protection Group)

Note: To delete an existing Protection Group, enter a right click on the NTE11x entity and select
Delete. A Protection Group with a Network Port in Loopback cannot be deleted. Deleting a
protection group will not necessarily be hitless.
User Label User Label associated with the Facility Protection up to 64 characters
Group. Up to 64 characters are allowed. (blank)


Parameter
Mode Facility Protection Group's Protection Switch Mode. 1+1
1+1 Protection or Dual Active Receive mode. Dual
Active Receive allows traffic received on both
Network ports to be forwarded to the Access ports.
Data traffic in the Access to Network (A2N) direction
are bridged to both Network ports (as per the 1+1
Dual Active Receive
protection mode). Changing the protection mode
from 1+1 to/from Dual Active Receive requires first
deleting the existing protection group (see above
Note) - it cannot be edited from one protection group
mode to another.
Working Member Selects the Working facility port. Network-1
Network-2
ERP-1--n - (GE114x) (Create/Edit)
Note 1: To create an ERP, enter a right click on NE-1 and select Create ERP. To Edit/Delete an
existing ERP, enter a right click on the ERP entity and select Edit/Delete.
Note 2: Up to 2 ERP instances may be created on a system.
ERP Index Ethernet Ring Protection (ERP) index (EID).
1-n
(Create only)
User Label User Label associated with the ERP instance. Up to up to 64 characters
64 characters are allowed. (blank)
Administrative Defines the ERP administrative state. IS is In Service IS
State and is the default value. See Entity State Management
IS is normal operation. Management suppresses
alarms. Disabled initiates blocking on ring port 0 and
stops all RAPS processing and forwarding.
The ERP instance must be in the Management or Disabled
Disabled state when modifying the following ERP
instance attributes: RAPS VLAN Tag, Ring Port 0/1,
Ring Port 0/1 RPL Role, RAPS Ring ID, RAPS MD
Level and Sub-Ring without Virtual Channel.
RAPS Node ID Node ID of the local system for this ERP instance.
The value is used as the Node ID in the RAPS PDU.
For each node in the ring, a unique node ID identifies
each node. The node ID is the node's MAC address.
You can configure this node ID when configuring the
ring on the node or automatically select an ID such as Default values:
STP. In most cases, you will not configure this and DCN (eth0) MAC
the router will select a node ID, like STP does. It address
should be the manufacturing MAC address. The ring
node ID should not be changed, even if you change
the manufacturing MAC address. Any MAC address
can be used if you make sure each node in the ring
has a different node ID.


Parameter
RAPS Ring ID Ring ID of this ERP instance. The value is used in the
destination address of the RAPS PDU. The Ring ID is
the unique identification of the ring. Each node on a
ring should be configured with the same RAPS Ring
ID. It is also embedded in the R-APS control frame 1-255
sent between units.
The ERP instance must be in the Management or
Disabled state when modifying this ERP instance
attribute.
RAPS VLAN Tag The VID value of the VLAN tag for transmitted/ 1-4095
received RAPS PDUs for this ERP instance. 4094
For each ring port, a dedicated signaling control
channel with a dedicated VLAN ID must be config-
ured. Each node on a ring should be configured with
0-7
the same control channel VLAN ID.
7
attribute.
RAPS Tag The VID value of the VLAN tag for transmit-
0x8100-0x88a8
EtherType ted/received RAPS PDUs for this ERP instance.
RAPS MD Level The MD (or MEG) level of the transmitted/received
RAPS PDUs for this ERP instance. It is recom-
mended set it at higher level or same MD level as the
Down MEP to allow RPL failure CCMs. 0-7
1
attribute.
Management Selects whether this ERP instance is protecting man- Enabled
Tunnel agement Tunnels on the ring ports.
Disabled
Protection
Revertive Revertive control for the ring. Only applicable on the Enabled
RPL Owner node. Disabled
Guard Time The Guard Time value for this ERP instance. Used by
all nodes when changing state; the guard timer
10-2000 (ms)
blocks latent outdated messages from causing
500
unnecessary state changes. Settable from
10-2000ms in steps of 10ms.
Wait-to-Restore The Wait-to-Restore (WTR) time value for this ERP
Time instance. The WTR timer is used to verify that the sig- 1-12 (minutes)
nal failure is not intermittent. Settable from 1-12 min- 5
utes in steps of 1 minute.


Parameter
Hold-off Time The Hold-off Time value for this ERP instance. It is
used by the underlying Ethernet layer to filter out
intermittent link faults. Faults are reported to the ring 0-10000 (ms)
protection mechanism only if this timer expires. Set-
table from 0-10000ms in steps of 100ms.
Sub-Ring without Indicates whether R-APS channel forms a closed Enabled
Virtual Channel loop around the ring.
If Enabled: no RAPS Virtual Channel (i.e., open ring).
If Disabled: RAPS forms a closed loop (major ring or
sub-ring with virtual channel). Disabled
attribute.
Ring Port 0/1 The ID of Ring Ports for this ERP instance (Ring Port
0= the ID of Ring Port 1, Ring Port 1= the ID of Ring
Port 2). (drop down list of
available Network
The ERP instance must be in the Management or Ports)
attribute.
Ring Port 0/1 The Ring Protection Link (RPL) Role of Ring Ports Owner
RPL Role (Ring Port 0= the ID of Ring Port 1, Ring Port 1= the Neighbor
ID of Ring Port 2).
Owner – owner or ERP ring instance, responsible for
blocking traffic over the RPL so that no loops are
formed in the Ethernet traffic. There can be only one
RPL owner in a ring.
Neighbor – An Ethernet ring node adjacent to the RPL
owner. It is responsible for blocking its end of the None
RPL under normal conditions. This node type is
optional and prevents RPL usage when protected.
None – Other members ports.
attribute.
Ring Port 0/1 The ID of MEP monitoring Ring Ports for this ERP None
MEP instance (Ring Port 0= the ID of Ring Port 1, Ring
Port 1= the ID of Ring Port 2). Allows a
tagged/untagged MEP to be used for port monitoring
(do not always use the port MEP). Must be a Down
(drop down list of
MEP and must be associated with the Network port
provisioned MEPs)
identified in the associated Ring Port (ringPort0/ring-
Port1). Provides added value when RAPS and ser-
vice frames are passed through intermediated nodes
that do not participate in this ERP instance.


Parameter
Power Supply Equipment (GE114PH)
PSE Group Setting

Power Usage This threshold expressed in percents for comparing 1-99%
Threshold the measured power and initiating an alarm if the 99
threshold is exceeded
Notification Whether to initialize a Notification if the power Enabled
Control consumed on this port exceed the threshold. Disabled
NonStandard PD Whether to allow Non-Standard Powered Devices to Enabled
Allowed be connected. Disabled
PSE Port Setting

Administrative Enabled: The interface can provides the PSE Unassigned
State functions.
Disabled: The interface acts as if there is no PSE
function. In Service
Note: When port is working in fiber mode, this
attribute must always be disabled.
Power Pairs Which pair in the Ethernet cable is used to carry Alternative A
power:
• Alternative A: that the signal pairs (1/2 and 3/6)
are used. Alternative B
• Alternative B: The spare pairs (4/5 and 7/8) are
used.
PSE Port Type A description about the PSE port, usually related to
up to 255 characters
the type of powered device that is connected to the
(blank)
port.
Available Power Which Power Level is allowed on this port. Class1 (4.00 Watts)
Level
When the Power Level is exceeded, PSE alarm is Class2 (7.00 Watts)
raised.
Class0&3 (15.40
Watts)
Class4 (30 Watts)
LAG
Create/Edit/Delete - See LAG Configuration Rules on p. 656
SHG
NE-1


Parameter
Note 1: To create a Split Horizon Group (SHG), enter a right click on NE-1 in the Selection Tree and
select Create SHG. To view/edit /delete an existing SHG, select the NE-1 entity in the Selection
Tree (an SHG list displays in the Details Pane), enter a right click on the desired SHG EID and
select View Configuration/Edit Configuration/Delete.
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 The Index number of this SHG instance.
1 - 128
(Created Only)
Alias A text and/or number the user enters to uniquely
identify this entity. This string can be up to 256
(blank)
printable ASCII characters long.
Members/ Select the member ports to form a Split Horizon
Members Entry Group (SHG).
List of Member Ports in the SHG entity. Members are
added by selecting from the ‘Port’ drop down list and
clicking on ‘Add’. Members are deleted by selecting
the Member to be deleted from the Members List and
clicking on ‘Delete’. (drop down list of
• A Member List with a combination of Network applicable Network
Ports and Access Ports is not allowed. Ports and Access
Ports
• A Member List with a combination of Network
Ports and Access Port LAG is not allowed.
• A Member List with a combination of Access
Ports and Network Port LAG is not allowed.
• The ports used in ERP instance and Protection
Group cannot be selected as SHG members.
NE-1
NTE114S/NTE114SH
SYNC-1-1-1-1 (Edit Sync)
up to 64 characters
(blank)
Administrative Defines the SYNC administrative state. IS is In IS
Management
Network Clock Select the desired Network Clock Type. Option 1-SDH
Type Regional Clock
Option 2-SONET
Regional Clock


Parameter
WTR Time Time delay in minutes from the recovery of a clock 0-12
source to its restoral as usable in an active state. 5
Selection Mode Defines what system is used to select the active clock Priority Mode
source. QL Mode
SYNC-1-1-1-1 (Add Sync Reference)
Note: A valid Sync Reference source must first be configured and In Service prior to adding a Sync
Reference.
SYNCREF Index Unique identifier of a sync reference entity. While the
Syncref Index is automatically indexed as sync
1-4
references are added, a dropdown list of available
1
indexes is provided for the user to select the desired
one.
up to 64 characters
(blank)
Priority Sets the priority for a sync reference. If the Selection
1-10
Mode is set to ‘Priority Mode’ this setting is used to
1
determine the sync reference hierarchy.
Sync Reference Dropdown list of available sync references. The
(drop down list of

Sources Network Port, Access Port, Telecom Slave or
provisioned Sync
BITS-IN has to be configured for Sync-E operation
Reference sources)
and be in a proper administration state to appear on
the dropdown list.
SYNC-1-1-1-1 (Edit Sync Reference)
Select Ref When BITS-IN, Telecom Slave, a Network Port or
Access Port has been added as a Sync Reference, (list of provisioned
their interface becomes available to choose from the Sync Reference
menu list by selecting its radio button to edit Priority sources)
and/or Alias.
Priority If a displayed Sync Ref Eid has its Select Ref radio
button selected, the user can select a new Priority 1-10
from the dropdown list.
Alias If a displayed Sync Ref Eid has its Select Ref radio
button selected, the user can edit the text and/or
up to 64 characters
number string to uniquely identify this entity. This
(blank)
string can be up to 64 printable ASCII characters
long.
SYNC-1-1-1-1 (Delete Sync Reference)
Select Ref When a Network Port, Access Port, Telecom Slave or
(list of provisioned
BITS-IN has been added as a Sync Reference, their
Sync Reference
interface becomes available to delete from the
sources)
reference list by selecting its radio button.
TIME CLOCK-1-1-1-1 (Edit) - GE114SH
up to 64 characters
(blank)


Parameter
Administrative Defines the SYNC administrative state. IS is In Unassigned
Service and is the default value. See Entity State IS
Descriptions on p. 599. Management
WTR Time Time delay in minutes from the recovery of a clock 0 - 12 (minutes)
source to its restoral as usable in an active state. 5
Selection Mode Specify Active time reference selection mode. Priority Mode
Time Holdover Set required holdover performance of the Time Clock 500
Performance (ns) in nanoseconds. 1000
1500
5000
10000
Sync Ref Specify whether Time Clock output can serve as a Disabled
Candidate Sync reference of the Sync entity in order to prevent
timing loop. Currently, it can only be set to Disabled. Enabled
Expected QL Select the Expected Quality Level used when Time QL-NONE
Clock serves as Sync reference. QL-PRS
QL- STU
QL- ST2
QL-TNC
QL- ST3E
QL-EEC2
QL- SMC
QL- PROV
TIME CLOCK-1-1-1-1 (Add Time Clock Reference) - GE114SH
Note: A valid Sync Reference source must first be configured and In Service prior to adding a Sync
Reference.
TIMEREF Index Unique identifier of a time clock reference entity.
While the Syncref Index is automatically indexed as
sync references are added, a dropdown list of 1
available indexes is provided for the user to select
the desired one.
up to 64 characters
(blank)
Priority Sets the priority for a sync reference. If the Selection
1-10
Mode is set to ‘Priority Mode’ this setting is used to
1
determine the sync reference hierarchy.
Time Clock Dropdown list of available sync references. GPS
GPS-1-1-1-1
Reference input is the default and only option.
Sources
TIME CLOCK-1-1-1-1 (Edit Time Clock Reference) - GE114SH


Parameter
Select Ref When GPS has been added as a Sync Reference, its
(list of provisioned
interface becomes available to choose from the menu
Sync Reference
list by selecting its radio button to edit Priority and/or
sources)
Alias.
Priority If the displayed GPS Eid has its Select Ref radio but-
ton selected, the user can select a new Priority from 1-10
the dropdown list.
Alias If the displayed GPS Eid has its Select Ref radio but-
ton selected, the user can edit the text and/or number up to 64 characters
string to uniquely identify this entity. This string can (blank)
be up to 64 printable ASCII characters long.
TIME CLOCK-1-1-1-1 (Delete Time Clock Reference) - GE114SH
Select Ref When GPS has been added as a Sync Reference, its (list of provisioned
interface becomes available to delete from the Sync Reference
reference list by selecting its radio button. sources)
BITS-1
BITS-IN (Edit Configuration)
up to 64 characters

(blank)
Administrative Defines the SYNC administrative state. See Entity Unassigned
State State Descriptions on p. 599. BITS will not show up IS
as a potential synchronization reference if the
administration state is set to Unassigned. Management
Line Type Sets the BITS line type. If a 2048kHz or E1 is the E1
desired BITS Line Type, then Network Clock Type T1
should be set to “Option 1". If a T1 is the desired
BITS Line Type, then Network Clock Type should be
set to “Option 2". AIS or LOF will be detected at the
BITS interface endpoints if mismatches of the FSP 2048 kHz
150CC's Network Clock Type and the FSP 150CC's
line-type are provisioned. Line Type should be set
prior to selecting other BITS IN Configuration options.
Line Code Sets the BITS line code. If Line Type is set to E1, E1 HDB3
then the options available are E1 HDB3 and E1 AMI. E1 AMI
If Line Type is set to T1, then the options available T1 B8ZS
are T1 B8ZS and T1 AMI. If Line Type is set to 2048
kHz, then this option is not applicable. T1 AMI
Frame Format Sets the BITS Frame Format. If Line Type is set to E1, E1 Unframed
then the options available are E1 Unframed, E1 CRC4 E1 CRC4
and E1 DualFrame. If Line Type is set to T1, then the E1 DualFrame
options available are T1 SuperFrame and T1
T1 SuperFrame
Extended- SuperFrame. If Line Type is set to 2048
kHz, then this option is not applicable. T1 Extended-
SuperFrame


Parameter
SA Bit Select the Signalling Associated (SA) Bit. SA Bit is None
only applicable if Line Type is set to E1. Bit 4
Bit 5
Bit 6
Bit 7
Bit 8
QL Mode Set the Quality Level Mode. If Line Type is set to Disabled
2048 kHz, then this option is not applicable. Enabled
Assumed QL Set the Assumed Quality Level. QL-NONE
QL-PRC
QL-SSU-A
QL-SSU-B
QL-EEC1
Expected QL Set the Expected Quality Level. If Line Type is set to QL-NONE
2048 kHz, then this option is not applicable. QL-PRC
QL-SSU-A
QL-SSU-B
QL-EEC1
BITS-OUT (Edit Configuration)
up to 64 characters
(blank)
Administrative Defines the BITS-Out administrative state. Unassigned
State IS
Management
Line Type Sets the BITS line type. If a 2048kHz or E1 is the E1
desired BITS Line Type, then Network Clock Type T1
should be set to “Option 1". If a T1 is the desired
BITS Line Type, then Network Clock Type should be
set to “Option 2". AIS or LOF will be detected at the
BITS interface endpoints if mismatches of the FSP
150CC's Network Clock Type and the FSP 150CC's 2048 kHz
line-type are provisioned. Line Type should be set
prior to selecting other BITS OUT Configuration
options.
Line Code Sets the BITS line code. If Line Type is set to E1, E1 HDB3
then the options available are E1 HDB3 and E1 AMI. E1 AMI
If Line Type is set to T1, then the options available T1 B8ZS
are T1 B8ZS and T1 AMI. If Line Type is set to 2048
kHz, then this option is not applicable. T1 AMI


Parameter
Frame Format Sets the BITS Frame Format. If Line Type is set to E1, E1 CRC4
then the options available are E1 Unframed, E1 CRC4 E1 DualFrame
and E1 DualFrame. If Line Type is set to T1, then the T1 SuperFrame
options available are T1 SuperFrame and T1
Extended- SuperFrame. If Line Type is set to 2048 T1 Extended-
kHz, then this option is not applicable. SuperFrame
SA Bit Select the Signaling Associated (SA) Bit. SA Bit is Bit 4
only applicable if Line Type is set to E1. Bit 5
Bit 6
Bit 7
Bit 8
QL Mode Set the Quality Level Mode. If Line Type is set to Disabled
2048 kHz, then this option is not applicable. Enabled
Squelch QL Set the Squelch Quality Level. The Squelch QL QL-NONE
attribute is used to define the minimum QL that the QL-PRC
system timing can accept. If the system timing QL QL-SSU-A
drops below this selected value, the BITS-OUT is
QL-SSU-B
turned off (i.e., no BITS-OUT signal is provided).
QL-EEC1
QL-DNU
Line Build Out Option to set impedance for cable length or dB. Only 0-133 Ft
applicable if Line Type is “T1”. 133-266 Ft
266-399 Ft
339-533 Ft
533-655 Ft
7.5 dB
15 dB
22.5 dB
CLK-1-1-1-1 (Edit Configuration)
up to 64 characters
(blank)
Administrative Define the CLK Administrative State. Unassigned
IS
Management
Signal Direction Specify the signal direction on this port. Output
Frequency Frequency Source Equipment Identifier. Drop down None
Source EID list of available PTP reference sources. The Telecom
(drop down list of
Slave has to be configured for PTP operation and be
available Frequency
in a proper admin state to appear on the drop down
Source EIDs)
list.


Parameter
Squelch Control A hierarchy to be established for Squelch control of Never
the CLK timing interfaces. The hierarchy is as fol- Holdover
lows: Lock
• NEVER, where the output is never squelched
• HOLDOVER, where output is squelched only in
freerun state
• LOCK, where output is squelched in holdover Squelch QL
and freerun states
• Squelch QL, where output is squelched only
based on Squelch QL.
Squelch QL Set the Squelch Quality Level. The Squelch QL attri- QL-NONE
bute is used to define the minimum QL that the sys- QL-PRC
tem timing can accept. If the system timing QL drops QL-SSU-A
below this selected value, the CLK-1-1-1-1 is turned
QL-SSU-B
off (i.e., no output signal is provided). This option is
only selectable when Squelch Control is set to QL-EEC1
Squelch QL. QL-DNU
PPS-1-1-1-1 (Edit Configuration)
up to 64 characters
(blank)
Administrative Define the PPS Administrative State. Unassigned
IS
Management
Signal Direction Specify the signal direction on this port. Output
Cable Delay Configure the PPS port input delay compensation,
Compensation which is used when PPS source does not allow delay
0 - 80 (nsec)
compensation configuration or PPS distribution
equipment is used.
Source Eid Source Equipment Identifier. Drop down list of
available PTP reference sources. The Telecom Slave (drop down list of
or Time Clock has to be configured for PTP operation available Source Eids)
and be in a proper admin state to appear on the drop
down list.


Parameter
the PPS timing interfaces. The hierarchy is as fol- Holdover
lows: Lock
• NEVER, where the output is never squelched
freerun state
and freerun states
Squelch QL Set the Squelch Quality Level. The Squelch QL attri- QL-NONE
bute is used to define the minimum QL that the sys- QL-PRC
tem timing can accept. If the system timing QL drops QL-SSU-A
below this selected value, the PPS-1-1-1-1 is turned
QL-SSU-B
off (i.e., no output signal is provided). This option is
only selectable when Squelch Control is set to QL-EEC1
Squelch QL. QL-DNU
TOD-1-1-1-1 (Edit Configuration)

up to 64 characters
(blank)
Administrative Define the TOD Administrative State. Unassigned
IS
Management
Time of Day Time of Day Source Equipment Identifier. Drop down None
Source Eid list of available PTP reference sources. The Telecom
(drop down list of valid
Slave or Time Clock has to be configured for PTP
Time of Day Source
operation and be in a proper admin state to appear
EIDs)
on the drop down list.
TOD timing interface. The hierarchy is as follows: Holdover
• NEVER, where the output is never squelched Lock
freerun state
and freerun states


Parameter
Squelch QL Set the Squelch Quality Level. The Squelch QL QL-NONE
attribute is used to define the minimum QL that the QL-PRC
system timing can accept. If the system timing QL QL-SSU-A
drops below this selected value, the CLK-1-1-1-1 is
QL-SSU-B
turned off (i.e., no output signal is provided).
QL-EEC1
QL-DNU
GPS-1-1-1-1 (Edit Configuration) - GE114SH
up to 64 characters
(blank)
Administrative Define the GPS Administrative State. Unassigned
IS
Management
PPS generation Define how many satellites should be detected 3SATS
condition before PPS signal is generated.
1SAT
Antenna Cable Select the proper cable length attached to the 0 - 100
Length, m antenna. 5
Communications
Static Route (Add Static Route) (see Note)

Dest IP Address Defines the IP address of the destination. The valid
values are the IPv4 addresses. The IP address of
0.0.0.0 is reserved for default routes. You can only 0.0.0.0
enter the static default route of 0.0.0.0 if the system
default router is 0.0.0.0.
Subnet Mask Defines the subnet mask for the destination. The
valid values are IPv4 mask. If you set the IP address
0.0.0.0
to 0.0.0.0, the only available choice for subnet mask
is 0.0.0.0.
Gateway IP Defines the IP address of the next hop for remote
Address destinations. For the routes reachable directly from 0.0.0.0
the specified interface, this value should be 0.0.0.0.
Interface Name Defines the interface to create a static route. eth0
Configured
Management Tunnel
entries
Metric Metric of the route. 0 to 65,535
Advertise Route Defines whether the static route is to be advertised or Enabled
not. When selected, the static route will be advertised
Disabled
on every other interface that has RIP enabled.
Note: To view Static Routes, select the Static Routes tab. To delete an existing Static Route, enter a
right click on the Communication entity in the Selection Tree and select Delete Static Route, then
select the desired static route to delete, then select OK.


Parameter
Static ARP Entry (Add Static ARP Entry) (see Note)
IP Address IP Address to be added to the Address Resolution
0.0.0.0
Protocol entry.
MAC Address Media Access Control Address to be added to the
00:00:00:00:00:00
ARP entry. MAC addresses are hard-coded at the
hh:hh:hh:hh:hh:hh
factory.
Interface Name Defines the interface to create the ARP entry. eth0
Configured
Management Tunnel
entries
Note: To view Static ARP Entries, select the Static ARP Entries tab. To delete an existing Static
ARP Entry, enter a right click on the Communication entity in the Selection Tree and select Delete
Static ARP Entry, then select the desired static ARP entry to delete, then select OK.
IPv6 Static Route (Add IPv6 Static Route)
Destination Enter a valid IPv6 unicast address for the destination
to be added. The IP address of
0000:0000:0000:0000:0000:0000:0000:0000/64 0000:0000:0000:0000:
is reserved for default routes. You can only enter the 0000:0000:0000:0000
static default route of /64

0000:0000:0000:0000:0000:0000:0000:0000
if the system default router is
0000:0000:0000:0000:0000:0000:0000:0000.
Gateway IP Define the IPv6 address for the Gateway of the
Address management interface. For the routes reachable
directly from the specified interface, this value should
0000:0000:0000:0000:
be 0000:0000:0000:0000:0000:0000:0000:0000. For
0000:0000:0000:0000
the routes unreachable directly from the specified
interface, this value is the IP address of the next hop
and should not be all zero.
Interface Name Define an IPv6 management interface to create a
static route. The management interfaces in IPv6
mode will automatically appear in the drop-down list
IPv6 management
for selection. If Management Traffic Bridging is
interface EIDs)
enabled, only eth0 if configured with IPv6 unicast
address is allowed for Interface Name.
Metric Specify the Metric as the priority for the route to be 0 - 65535
added. 1
Advertise Route Enable or Disable advertising the route to the next Disabled
hop. Enabled
Note: To view IPv6 Static Routes, select the IPv6 Static Routes tab. To delete an existing IPv6
Static Route, enter a right click on the Communication entity in the Selection Tree and select Delete
IPv6 Static Route, then select the desired IPv6 static route to delete, then select OK.
IPv6 Static Neighbor Entry (Add IPv6 Static Neighbor Entry)
IP Address Enter a valid IPv6 unicast address for a target 0000:0000:0000:0000:
Neighbor to be added. 0000:0000:0000:0000


Parameter
MAC Address Neighbor Discovery Protocol (NDP) will resolve the
00:00:00:00:00:00
MAC address entered for the target IP address.
Interface Name Select an IPv6 management interface to create a
neighbor entry. The management interfaces in IPv6
mode will automatically appear in the drop-down list
IPv6 management
for selection. If Management Traffic Bridging is
interface EIDs)
enabled, only eth0 if configured with IPv6 unicast
address is allowed for Interface Name.
Note: To view IPv6 Static Neighbor Entry, select the IPv6 Static Neighbor Entry tab. To delete an
existing IPv6 Static Neighbor Entry, enter a right click on the Communication entity in the Selection
Tree and select Delete IPv6 Static Neighbor Entry, then select the desired IPv6 static neighbor entry
to delete, then select OK.
IPv6 Static Proxy ND Entry (Add IPv6 Static Proxy ND Entry)
IP Address Enter a valid IPv6 unicast address for the static proxy 0000:0000:0000:0000:
to be added. 0000:0000:0000:0000
/128
Interface Name Select an IPv6 management interface to create a
static proxy neighbor entry. The management
interfaces in IPv6 mode will automatically appear in
IPv6 management
the drop-down list for selection. If Management
interface EIDs)
Traffic Bridging is enabled, only eth0 if configured
with IPv6 unicast address is allowed for Interface
Name.
Note: To view IPv6 Static Proxy ND Entry, select the IPv6 Static Proxy ND Entry tab. To delete an
existing IPv6 Static Proxy ND Entry, enter a right click on the Communication entity in the Selection
Tree and select Delete IPv6 Static Proxy ND Entry, then select the desired IPv6 static proxy ND
entry to delete, then select OK.
Source Address Config (Edit Source Address Config)
Address Type Specifies whether the System IP Address or the Outgoing Interface IP
Outgoing IP Interface's Address should be used in
System IP Address
outgoing IP PDUs.
Source Address Specifies the IP interface name when Address Type eth0
Interface Name is set to “System IP Address.” The IP Address Configured
associated with the IP interface name is set as the Management Tunnel
source IP Address in outgoing PDUs. entries
Snmp v1 Specifies the IP interface name, which will be used in eth0
Interface Name the SNMPv1 TRAP PDUs as the Agent's IP Address. Configured
Management Tunnel
entries
DCN (eth0) (Edit Configuration)
IP Mode Select the desired IP mode setting for DCN port. IPv4 Only
IPv6 Only
IPv4 and IPv6


Parameter
IP Address IP Address for the Data Communications Network.
This option is not applicable if DHCP is set to 192.168.0.2
Enabled and DHCP Role is set to DHCP Client.
Netmask Defines the subnet mask for the Data
Communications Network. This option is not
applicable if DHCP is set to Enabled and DHCP Role
255.255.255.0
is set to DHCP Client. If DHCP is Enabled and DHCP
Role is set to DHCP Server, the Netmask determines
the number of IP addresses available for assignment.
RIPv2 Allows setting/disabling of Routing Information Enabled
Protocol V2 packets. Disabled
DHCP Defines whether Dynamic Host Configuration Enabled
Protocol is enabled or disabled. If this interface is set
to Enabled and DHCP Role is set to DHCP Client, the
GE11x sends a broadcast query requesting IP Disabled
address information from a DHCP server.
DHCP Role Defines whether Dynamic Host Configuration DHCP Server
Protocol Role is as a server or a client. Servers
assign IP addresses, Clients receive addresses. This
option is only applicable if DHCP is set to Enabled.

If the DHCP Role is set to DHCP Server, the user DHCP Client
must Disable and then Enable DHCP for the
initialization of the server function (IP Address range)
to take place.
DHCP Client ID Enable or Disable transmitting DHCP Client ID Disabled
Control (DHCP Option 61) if configured in DHCP request to
Enabled
the DHCP server.
DHCP Client ID Select a desired DHCP Client ID type when DHCP MAC Address
Type Client ID Control is Enabled. If MAC Address is System Name
selected, the DCN MAC Address will be used as
DHCP Client ID automatically; if System Name is
selected, the System Name shown in System Detail
Pane will be used as DHCP Client ID; if User Defined User Defined
is selected, user is allowed to enter a customized
name as the DHCP Client ID.
DHCP Client ID This option shows or allows the entry of DHCP Client
ID. If DHCP Client ID Type is MAC Address or
(Default as DCN MAC
System Name, this option is not editable, as a value
address or System
corresponding to the selected Client ID Type will be
Name, dependent of
used automatically; if DHCP Client ID Type is User
last operation)
Defined, user is allowed to enter a customized string
up to 254 characters.


Parameter
DHCP Class ID Enable or Disable transmitting DHCP Class ID Enabled
Control (DHCP Option 60) if configured in DHCP request to
the DHCP server. The Class ID is a non-user
definable string. The format is like: <vendor fixed
Disabled
string><space><inventory product name>
e.g: “ADVA FSP150CC-GE112” for the GE112, with
the same format used for other products.
DHCP Host Enable or Disable transmitting DHCP Host Name Enabled
Name Control (DHCP Option 12) if configured in DHCP request to
Disabled
the DHCP server.
DHCP Host Select a desired DHCP Host Name Type when System Name
Name Type DHCP Host Name Control is enabled. If System
Name is selected, the System Name shown in gray
(same as the System Name in System Detail Pane)
User Defined
will be used as the DHCP Host Name; if User Defined
is selected, use is allowed to enter a customized
name as the DHCP Host Name.
DHCP Host This option shows or allows the entry of DHCP Host FSP150CC-GE11x
Name Name. If DHCP Host Name Type is System Name,
this option is not editable, as the System Name will
be used automatically; if DHCP Host Name Type is User-defined string
User Defined, user is allowed to enter a customized
string up to 254 characters.
DHCP Log Enable or Disable receiving the DHCP Log Server Disabled
Server Control (DHCP Option 7) list sent by the DHCP server. Enabled
DHCP NTP Enable or Disable receiving the DHCP NTP Server Disabled
Server Control (DHCP Option 42) list sent by the DHCP server. Enabled
Edit System Selecting the checkbox allows editing the Gateway IP (checkbox,
Default Gateway Address. Only applicable if DHCP is Disabled. unselected)
Gateway IP Enter a Gateway IP Address if the “Edit System
(grayed out)
Address Default Gateway” checkbox is selected.
IPv6 Unicast Enter an IPv6 unicast address for the DCN port. This 0000:0000:0000:0000:
Address option is only applicable when DHCPv6 is disabled 0000:0000:0000:0000
and DHCPv6 Role is Client. /0
Stateless When the NE is working in router mode (IPv6 Disabled
Address Auto Forwarding enabled), this option must be Disabled.
Configuration When the NE is working in host mode (IPv6 Enabled
Forwarding disabled), this option can be Enabled.
DHCPv6 Defines whether Dynamic Host Configuration Disabled
Protocol (DHCP) is enabled or disabled. If this
interface is set to Enabled and DHCP Role is set to
DHCP Client, the GE11x sends a broadcast query Enabled
requesting IPv6 address information from a DHCP
server.


Parameter
DHCPv6 Role Defines whether Dynamic Host Configuration DHCP Client
Protocol Role in IPv6 Network is as a server or a
client. Servers assign IP addresses, Clients receive
addresses. This option is only applicable if DHCP is
set to Enabled. If the DHCP Role is set to DHCP DHCP Server
Server, the user must Disable and then Enable
DHCPv6 for the initialization of the server function (IP
Address range) to take place.
RIPng Allows setting/disabling of Routing Information Disabled
Protocol next generation (RIPng) packets. When
RIPng is enabled on an IPv6 interface, the interface
receive the IPv6 route entry on the link and update
local route table. The interface also sends local Enabled
learned IPv6 route entry to the link via multicast
packets.
IPv6 RA Prefix Whether to Advertise prefix to link in router mode. Disabled
Enabled This is only applicable when IPv6 Forwarding is
enabled on System level. This option and Stateless
Enabled
Address Auto Configuration are mutually exclusive;
they cannot be both Enabled at the same time.

IPv6 RA Prefix The IPv6 Prefix to be dispatched to link in Router 0000:0000:0000:0000:
mode. 0000:0000:0000:0000
/0
Edit System Selecting the checkbox allows editing the Gateway
(checkbox unselected)
Default Gateway IPv6 Address.
Gateway IPv6 Enter a Gateway IPv6 Address if the “Edit System
(grayed out)
Create / Edit / Delete Management Tunnels (see Management Tunnel Configuration Options and
Rules on p. 701)
Create / Edit / Delete IPv6 over IPv4 Tunnels (see IPv6 over IPv4 Tunnel Configuration Options and
Rules on p. 707)
SNMP
Add / Delete Community (see Note)

Community Entry for the valid Community Name. public
Name private
Access Type Defines the access type. Read Only (public)
Read/Write (private)
Note: To delete an existing Community Name, enter a right click on the SNMP entity in the Selection
Tree and select Delete Community. Then select the desired Community Name from the selection
list and select OK.
Add / Delete Target Address (see Note)
Target Address User defined text/number string used to identify this
up to 32 characters
Name target address. Entry can be up to 32 characters
(blank)
long.


Parameter
Transport IPv4 address
0.0.0.0
Address
Port Port of the SNMP trap receiver. 162
Target Params Selectable list of user defined target parameter Selectable list of user
Name names. The associated Target Parameters must first defined target
be entered prior to selecting this option. See Add / parameter names
Delete Target Parameters (see Note) on p. 644. (blank)
Timeout [1/100 s] Length of time to wait before timeout occurs in 1/100s
1500
of a second.
Retry Count How many times to retry. 3
Tag List Drop-down list to select the desired type of tag list for info
this target address. trap
SNMP Dying Whether or not SNMP dying gasp is enabled on the Enabled
Gasp GE11x. Disabled
Note: Up to 10 Target addresses are supported. To delete an existing Target Address, right click the
SNMP entity in the Selection Tree, select Delete Target Address, select a Target Address from the
selection list, and click OK.
Add / Delete Target Parameters (see Note)
Target User defined text/number string used to identify this
up to 32 characters
Parameter Name set of target parameters. Entry can be up to 32
(blank)
characters long.
Security Model Drop-down list for selection of a security model for SNMPv1
this set of target parameters. SNMPv2c
USM
Security Level Sets the security level for the new Target Parameter. No Authentication
Only applicable if Security Level USM is selected. Auth/No Priv
Auth/Priv
Security Name Drop down list of available security names for private
SNMPv1 or SNMPv2c. public
Drop down list of available security names for USM. ADMIN
MONITOR
OPERATOR
PROVISION
Note: To delete an existing Target Parameter, right click the SNMP entity in the Selection Tree,
select Delete Target Parameter, select an Target Parameter from the selection list, and click OK.
Add / Delete USM User (see Note)
User Name Entry for a valid user name. Valid entry contains only
1 to 32 characters
1 to 32 of the following characters are accepted: "a-z
(blank)
A-Z 0-9 ._-".


Parameter
Engine ID An SNMP engine's administratively-unique identifier.
Valid entry is 5 to 32 characters. In a simple agent,
this value is always that agent's own snmpEngineID
value of ‘local’. The value can also take the value of
the snmpEngineID of a remote SNMP engine with
which this user can communicate. 5 to 32 characters
(blank)
Objects of this type are for identification, not for
addressing, even though it is possible that an
address has been used in the generation of a specific
value. The value for this object can not be all zeros or
all 'ff'H or the empty (zero length) string.
Security Name Security Name. Valid entry contains only 1 to 256 of
the following characters are accepted: "a-z A-Z 0-9 1 to 256 characters
._-". Mandatory entry. If no entry is provided, User (blank)
Name is substituted automatically.
Security Level Options are No Authentication, Authentication with No Authentication
No Privacy key or Authentication with Privacy key. Auth/No Priv
Auth/Priv
User Access Specifies the user access type. Read Only

Type Read/Write
Trap Only
Auth. Protocol Drop down list of established authentication MD5
protocols. This option is only available if the Security
SHA1
Level is other than No Authentication.
Auth. Key Entry for an Authentication Key. This option is only
applicable if Auth/Priv or Auth/No Priv Security Level
is selected. A valid entry contains the following:
1. Contains only alphanumeric and special charac-
ters '# * %' and must not begin with '#'.
2. Length from 8 to 32 characters.
8 to 32 characters
3. Contains a mix of upper and lower case alpha (blank)
characters, at least one special character (# * %) and
at least one digit.
4. No more than 2 letters or digits can be repeated in
consecutive character positions.
5. Does not contain a sequence of 3 consecutive let-
ters/digits in ascending/descending order.
Confirm Auth. Reenter the key entered in the Auth. Key box to 8 to 32 characters
Key confirm the key. (blank)
Priv. Protocol Drop down list of established privacy protocols. This DES
option is only available if the Security Level is
AES
Auth/Priv.


Parameter
Priv. Key Entry for a Privacy Key.This option is only applicable
if Auth/Priv Security Level is selected. If a valid entry
contains the following:
1. Contains only alphanumeric and special charac-
ters '# * %' and must not begin with '#'.
2. Length from 8 to 32 characters.
8 to 32 characters
3. Contains a mix of upper and lower case alpha (blank)
characters, at least one special character (# * %) and
at least one digit.
4. No more than 2 letters or digits can be repeated in
consecutive character positions.
5. Does not contain a sequence of 3 consecutive let-
ters/digits in ascending/descending order.
Confirm Priv. Re-enter the key entered in the Priv. Key box to 8 to 32 characters
Key confirm the key. (blank)
Note: To delete an existing USM user, right click on the SNMP entity in the Selection Tree and
select Delete USM User Entry. Then in the Details Pane, select the USM User to delete from the
selection box and click on OK.
Dying Gasp (Edit Dying Gasp)
SNMP Dying Dropdown list for each configured Target Address to
Gasp Enable or Disable SNMP Dying Gasp on that Target (No Target Addresses
Address. At System Defaults, no Target Addresses Exist)
are configured.
Administration
Users (Add User, Edit User or Edit Password)

User Name User Identifier (log-in name). The new login name for
the user account. Must be at least 1 alphanumeric
character long and no more than 32 alphanumeric
characters. If the password security strength is set to
1 to 32 characters
high, the minimum length of a User ID is 6
characters. Spaces are not allowed. The system
See Security Policy
supports three levels of username and password
(Edit Policy) on p. 649”
security, and is dependent on the security policy
setting. See Security Policy (Edit Policy) on p. 649”.
(blank)
The default Superuser user ID is root. Only a
Superuser has the authority to create or delete a user
ID. This option is available when selecting Add User
or Edit Password.


Parameter
Password / User login password. The system supports three
Retype levels of password security, and is dependent on the
1 to 32 characters
Password security policy setting. See Security Policy (Edit
Policy) on p. 649”. Only a Superuser may create a
See Security Policy
password associated with a new User ID. A
(Edit Policy) on p. 649”
Superuser may edit any existing password. Any user
may edit their own password. This option is available
(blank)
when selecting Add User or Edit Password. The
default Superuser password is ChgMeNOW.
Comment User comment text string (maximum 128 characters
in length). Only a Superuser may edit a user up to 128 characters
comment. This option is available when selecting (blank)
Add User or Edit User.
Privilege User Security Level. The Superuser assigns security Superuser
levels for each user. Refer to User Authorization Maintenance
Privilege Levels on p. 605 for more details. Only a Provisioning
Superuser may edit a user privilege level. This option
Not Applicable
is available when selecting Create New User or Edit
User. The default root user ID privilege level is Super Retrieve
User.
Login Timeout Login timeout for the user ID (in minutes). Only a
0 (no logout timer) to
(mins) Superuser may edit a user login timeout value. This
99 (minutes)
option is available when selecting Add User or Edit
15 (minutes)
User.
CLI Paging If the response to a CLI command fills more than one Enabled
screen, the response is divided into multiple pages if
this option is enabled. Disabled
Remote Authentication (Edit Remote Authentication)
Authentication Sets the Remote Authentication Protocol type. NONE
Protocol RADIUS
TACACS
Authentication Remote authentication type. Options available are: PAP
Type Password Authentication Protocol (PAP) or
Challenge- Handshake Authentication Protocol CHAP
(CHAP).
TACACS When Enabled, the system expects the User Disabled
Privilege Control Privilege level to be returned from the TACACS+ Enabled
server.
When Disabled, the system does not expect User
Privilege level information from the TACACS+ server,
but uses the privilege level set in the TACACS
Default Privilege Level attribute.


Parameter
TACACS Default When TACACS Privilege Level Control is Disabled, Retrieve
Privilege this value is used as the user's privilege level once Maintenance
authenticated by the TACACS+ server. Provisioning
Superuser
When TACACS Privilege Level Control is Enabled,
this value is automatically configured to “Not Not Applicable
Applicable”.
NAS IP Address The IP address of the Network Access Security
server. This option is only applicable if Authentication 0.0.0.0
Protocol is set to RADIUS.
Accounting Enable or Disable the use of an accounting port. Disabled
Enabled
Access Order Set the RADIUS access order. If the Access Order is Local
set to Local First (the default), user login is first Remote
authenticated using local user database. If the local
authentication fails, then the system will use RADIUS
(if so configured) to authenticate with the remote
server. If the Access Order is set to Remote First and
if the remote authenticate is enabled, the first try is to
authenticate using the remote server. If the remote
server is reachable but the authentication failed, the
system does not authenticated with the local
database and declares authentication failure. If the
remote authentication is successful, the system
declares the authentication successful. If the remote
authentication is not enabled or if the remote server
is unreachable, then the system uses the local
database to authenticate.
Remote Enables Server for operation. Disabled
Authentication Enabled
Server (1 to 3)
Status
Remote Defines the priority of the server in servicing First
Authentication requests. Multiple servers may have the same priority Second
Server (1 to 3) value. Random ordering will be chosen for those Third
Priority servers with equal priority values. Server 1 default is
First, Server 2 default is Second and Server 3 default
is Third.
Remote The IP address of the specified Remote
Authentication Authentication Server. 0.0.0.0
Server (1 to 3)
IP Address
Edit Server Check box that if selected allows the editing of the
(deselected)
Secret Server Secret.


Parameter
Remote Defines the shared secret used for authenticating the
Authentication GE11x with the Remote Authentication server. Valid
Server (1 to 3) entry is a string of up to 128 non-whitespace
(blank)
Server Secret characters. To make an entry, select the Edit Server
Secret checkbox.
Remote Defines the UDP port to use when communicating
Authentication with the Remote Authentication server. Default is 1 to 65535
Server (1 to 3) 1812 if Authentication Protocol is set to RADIUS or 1812 (RADIUS)
Port None, default is 49 if Authentication Protocol is set to 49 (TACACS)
TACACS.
Remote Defines the UDP port to use for accounting when
Authentication communicating with the Remote Authentication
1 to 65535
Server (1 to 3) server. Default is 1813 if Authentication Protocol is
1813 (RADIUS)
Accounting Port set to RADIUS or None, default is 49 if Authentication
49 (TACACS)
Protocol is set to TACACS. Only editable if
Accounting is Enabled.
Remote Defines the timeout in seconds after which
Authentication communication with this server fails. This option is
2 to 10
Server (1 to 3) only applicable if Authentication Protocol is set to
2
Timeout RADIUS.
Remote The maximum number of tries that will be attempted
Authentication with this server. 0 to 5
Server (1 to 3) 3
Retries
Security Policy (Edit Policy)
Security Policy The system supports the following three levels of High
Strength security strength for local user passwords. This Medium
setting is used for the basis of user name and Low
password entry.
High:
1 User Name must be 6 to 32 characters in length
and no spaces allowed.
2 Password must be 12 to 32 characters in length.
3 Password must contain only alphanumeric and
special characters '# * % - _ .' and must not begin
with '#'.
4 Password must contain upper and lower case
characters, at least 2 special characters and at
least 1 digit.


Parameter
5 Password must not contain more than 2 letters or
digits repeated consecutively.
6 Password must contain upper and lower case
characters, at least 1 special character and at
least 1 digit.
7 Password must not contain more than 2 letters or
digits repeated consecutively.
8 Password must not contain a sequence of 3 con-
secutive alphanumeric characters in ascending
or descending order.
Security Policy 9 Password must not be the same as the user
Strength name.
(Continued)
10 Password must not be 'password/passw0rd' in
lower, upper or mixed case.
Low:
1 User Name must be 1 to 32 characters in length
and no spaces allowed.
2 Password must be 1 to 32 characters in length.
3Password must contain only alphanumeric and
special characters '# * % - _ .' and must not begin
with '#'.
Key Generation (Regenerate Keys)
Regenerate SSL Radio button to create a new SSL certificate. If
Certificate selected, then Edit SSL Certificate Data options are
applicable.
(unselected)
When an SSL Certificate is generated, the HTTP
server is restarted and web access is unavailable
during this time (approximately 15 seconds).
Regenerate SSH Radio button to create a new SSH certificate.
Key
(unselected)
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


Parameter
Email Edit SSL Certificate Data - Email support@advaoptical.
com
Valid Until Edit SSL Certificate Data - Valid Until (varies)

Pass-Through Flow Configuration Options and Rules

The following Network 1 to Network 2 Pass-Through Flow configuration options
are available for the GE114S and GE114SH. Refer to the following table for
Pass-Through flow configuration settings. Default settings are identified in bold.
The following Pass-Through flow settings are shown in order, as seen when
using the eVision web browser management tool in Configuration mode.
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).
Table 43: Configuration Settings for Pass-Through Flows

Parameter
PT Flows (GE114S/GE114SH)
Flow (Create/Edit Flow)

Passthrough The EID of this flow instance. PT FLOW-1-1
Flow EID through
(Create only) PT FLOW-1-128
Circuit Name Defines a circuit identifier for the Flow. Up to 256 up to 256
characters are allowed. characters
(blank)
Administrative Enables or disables the Pass-through Flow. IS is In IS
State Service and is the default value. See Entity State Management
Descriptions on p. 599. Disabled
EVC Type Defines the EVC type. Regular EVC
If Default EVC: N2N Flow Membership based on a frame
received on a Network Port that does not match any other
flow membership (only 1 default flow is allowed per Sys- Default EVC
tem).
If Regular EVC: N2N Flow Membership based on VLAN
Member list.
Policing Control of N2N policing function. Enabled
If Enabled: Bandwidth Profile is applied as a policing func- Disabled
tion (CIR, EIR, CBS, EBS) and shaping function (CIR,
EIR) for N2N frames.
If Disabled: Bandwidth Profile is applied as a shaping
function (CIR, EIR) for A2N frames. A policing function is
not applied to N2N frames.
Multi COS Enables N2N per-COS Bandwidth Profiles. Enabled
Disabled
COS Identifies the CoS for all N2N frames on a flow when Multi
0-7
COS is Disabled.

Table 43: Configuration Settings for Pass-Through Flows (Continued)

Parameter
Untagged Allows for untagged N2N frames to be included as mem- Enabled
Frames bership in the flow. Disabled
Loop Avoidance The protection entity for this flow: None
NONE: no protection.
ERP-1-n
ERP EID: ERP instance controls blocking for this flow.
Shaping Type Specify the shaping type in N2N direction. Flow Based
(GE112/GE114/G
E114H/GE114PH
)
Port Based
(GE114S/GE114
SH)
N2N Auto Controls auto Bandwidth control for this flow. Enabled
Bandwidth If Enabled: the Bandwidth Profile values for this flow are Disabled
determined dynamically and are read-only.
If Disabled: the Bandwidth Profile of the flow is manually
controlled.
Not applicable when Multi COS = Enabled.
N2N Auto CIR Percentage of available CIR on the Network ports

Bandwidth assigned to this flow. The flow guaranteed bandwidth is
Percent set to available bandwidth multiplied by this value.
The sum of N2N auto CIR bandwidth Percentage value for 0-100
all flows with N2N Auto Bandwidth = Enabled must be <=
100%.
Not applicable when Multi COS = Enabled.
N2N Policer CIR Defines the Policer Committed Information Rate (CIR) for 0 to 1 Gbps (for 1
this Policer, in bps. Gbps ports)
0 to 10 Gbps (for
10 Gbps ports)
N2N Policer EIR Defines the Policer Excess Information Rate (EIR) for this 0 to 1 Gbps (for 1
Policer, in bps. Gbps ports)
0 to 10 Gbps (for
10 Gbps ports)
N2N Policer CBS Defines the Policer Committed Burst Size (CBS) for this
Policer, in Kilobytes. The minimum user configurable
value for CBS is MAX[MTU or CIR/(64,000*8)] and it can
be provisioned in increments of 1KB. The maximum value
for CBS/EBS is 10*1024 = 10240 KB. All calculations for
CBS here are in bytes and for user provisioned values
they need to be converted to Kbytes and rounded to the
nearest Kbyte.
N2N Policer EBS Defines the Policer Excess Burst Size (EBS) for this
0 to 1,024 (KB)
policer, in Kilobytes.
N2N Policer Specifies the Policer Color Mode as 'Color Aware' or Color Aware
Color Marking 'Color Blind'. Color Blind


Parameter
N2N Policer Specifies the Policer Coupling Flag. When coupling is Enabled
Color Coupling enabled, tokens that would normally be added to the Disabled
Flag C-bucket are passed to the E-bucket only once the CIR
bucket has reached its CBS level. Therefore under this
condition the E-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 of frames declared ˜yellow” to
be bounded by CIR + EIR.
This allows a higher volume of yellow frames to be

delivered/received 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 a provisioned EIR of 0 allows
for a single rate three color marking (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.
N2N Shaper Represents the Buffer Size of the Shaper. Entered in 10 to 15,360 (KB)
Buffer Size kilobytes. 128 (KB)


Parameter
VLAN Members Defines the frames that belong to the flow. Frames are VLAN ID portion
(Regular EVC classified based on the VLAN tag and the membership is of
only) specified as a list of VLAN IDs. The VLAN member format VLAN ID-Priority:
is VLAN ID-*, VLAN ID (range)-* or *-Priority. The valid
values for VLAN ID are 0 to 4095. Valid values for Priority 0 to 4095, or *
are * or 0 to 7. A VLAN ID range is a contiguous block of Priority portion of
VID values delineated by a first member and a last VLAN ID-Priority:
member, inclusive (e.g., Range 100 - 199 shall consist of
a all frames with VID values {100, 101..... 198, 199}) 0 to 7, or *
including all PRI values for those VIDs, and is entered
using a colon, for example: 100:199. Range must list lower
value on left and larger value on the right. Up to two range
entries are allowed per port.
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.
Regarding the use of the “wildcard” value * - The normal

designation 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 taking
precedence; *-Y members cannot coexist with X-*
members.
To add a VLAN member, enter the valid VLAN ID-Priority

number and select Add. To delete a VLAN member, select
the VLAN ID-Priority number and select Delete. If EVC
Type is set to Default EVC, no VLAN Member value can
be supplied, and 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. If EVC Type is set to
Regular EVC, then individual VLAN Members can be
entered.

LAG Configuration Rules

Refer to the following table for LAG configuration rules. For GE112, up to 2 LAG
groups may be created. For GE114x, up to 3 LAG groups may be created.
• For LAG descriptions and attributes, see Link Aggregation Group in FSP
150CC GE11x R6.1 Technical Descriptions document.
• For LAG configuration procedure, see Provision Ports in a LAG Group on
p. 292.
Table 44 shows the LAG Configuration Rules applying to GE11x. The attributes
are arranged in the same order as on the eVision interface. Default settings are
identified in bold.
Table 44: LAG Configuration Rules
Parameter
NE-1 / LAG Entity (e.g., LAG-1-1)
Note 1: A LAG and port protection cannot co-exist at the same port.
Note 2: A LAG can be created without any member port.
Note 3: Creating or editing a LAG is denied if:
o The Member Port list contains more than 2 member ports
o One or more members in the Member Port list are included in a different LAG
o The speed of any port in the Member Port list is configured as “AUTO”.
o All ports in the Member Port list are not configured with the same port speed
o Auto Diagnostics is enabled.
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 Mem-
ber 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 Net-
work 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 exist-
ing 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 10: A LAG can be created on the Network side or Access side. This is dictated by the first
member port added to the LAG.
Note 11: Regarding the Access LAG, the Service Mode of A LAG can be EVP of EVPL, this is dic-
tated by the Service Mode of the first Member Port added to the LAG. The Service Mode of the sec-
ond 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.


Parameter
Create/Edit LAG Configuration
LAG ID Unique LAG identifier, LAG-1
(Create LAG only) o
GE112: LAG-1, LAG-2
o
GE114x: LAG-1. LAG-2, LAG-3
Alias A text and/or number string the user enters to identify a up to 64 characters
LAG entity. This string can be up to 64 printable ASCII (blank)
characters long. Unique strings across the NE are
recommended.
Administrative Defines the LAG facility administrative state. The IS
State administrative state controls the generation of alarms Management
and event reports. When an entity is in the In-Service
state, it is fully operational. For more information on
Administrative States, see Entity State Descriptions on
p. 599.
LAG Protocols Option is used to enable LAG protocols. Disabled
See Footnote 1. Enabled
LACP Control Option is used to enable LACP Control for the LAG Disabled
entity. Enabled
See Footnote 1.
CCM Defect Option used to enable the use of CFM CCM to detect Disabled
Detection defects on the LAG entity. If CCM Defect Detection is Enabled
desired, a Down MEP with proper provisioning must
preexist on the LAG Port.
System Priority Defines the LACP Actor System Priority. Minimum is 0; 0-65535
Maximum is 65535. 32768
Collector Max Set the maximum delay allowed for collector response. 50-65535
Delay
Members List of Member Ports in the LAG entity. Port Member drop
down list
LAG-1-1
Edit Port Configuration

Alias A text and/or number string the user enters to identify a up to 64 characters
LAG entity. This string can be up to 64 printable ASCII (blank)
characters long. Unique strings across the NE are
recommended.
Administrative Defines the Port facility administrative state. The IS
State administrative state controls the generation of alarms Management
and event reports. When an entity is in the In Service Maintenance
state, it is fully operational. The Administrative State
Disabled
must be set to Maintenance prior to initiating a
loopback or an Etherjack Diagnostic. For more
information on Administrative States, see Entity State
MTU Defines the Maximum Transmission Unit size. 1518-9612
Minimum MTU is 1518; Maximum is 9612.


Parameter
Drop Eligibility Option to enable the use of the Drop Eligibility Indicator Enabled
Indicator Disabled
B-MAC Address The Source MAC address of the PBB Frames sent out The Network Port’s
from this Network P MAC address.
Q in Q EtherType Enables or disables editing the Q in Q EtherType. Enabled
Override
Q in Q EtherType Defines the Stacked Ethertype to be used to 0 (hex.)
interoperate with Q in Q frames with other vendors.
Only editable if Q in Q EtherType Override is enabled.
AFP Traffic type allowed on the LAG AFP All
AFP tagged
AFP Untagged
Port Link Loss Enable or Disable Link Loss Forwarding Port LLF Disabled
Forwarding Status status. Enabled
Note: If the Network Port, LOS or 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.
Link Loss Sets the Link Loss Enable Delay, in seconds, from the 0-3600
Forwarding Delay time Link Loss is detected before Link Loss Forwarding
takes effect. If the loss clears during delay time, it is not
propagated. It is recommended that Link Loss
Forwarding Delay be provisioned with a non-zero
value on LAG port, in case of LLF vibration during the
link switching process. Only effective if Link Loss
Forwarding is Enabled.
Link Loss Sets link Loss Forwarding Transmit Signal Type. No Action
Forwarding TX EFM Signal
Action Link Down
Link Loss Defines the Local Link ID for the Network port to N/A
Forwarding Local indicate which port is faulted.
Link ID
Link Loss Check boxes to select trigger events to generate the EFM
Forwarding Trigger Link Loss Forwarding signal. Either EFM or Link Down Link Down
Events may be selected, or both. At default, none are
selected.
Link Loss Allows selection of the Remote Link ID(s) to be used Remote Link ID
Forwarding for matching against the Link ID in the EFM RLD check boxes
Remote Link IDs (Remote Link Down) message. The same Remote Link (none selected)
ID number may be set for multiple ports, if desired.
Default is no ports selected.
Edit Port CDP Filters - see CPD Filters Options and Rules on p. 709.
Edit Priority Mapping (Network LAG)


Parameter
In Priority For each ‘In Priority’ 0 to 7, the user can select a ‘COS’ COS 0-7
COS (0 to 7) and an ‘Outer Tag Priority’ (0 to 7). The Default Outer Tag Priority
Outer Tag Priority values have the ‘COS’ and ‘Outer Tag Priority’ equal to 0-7
the ‘In Priority’.
Clear Statistics
Delete
Edit A2N Shapers (for Network LAG only)
BS The buffer size of the shaper (in KB). 0-15360 (128)
Edit N2A Shapers (for Access LAG only)
BS The buffer size of the shaper (in KB). 0-15360 (128)
Edit Priority Mapping (EPVL Access LAG only)
In Priority For each “In Priority” (0-7) the user can select a COS
and/or an Outer Tag Priority from a dropdown list. The 0-7
default values of COS and Outer Tag Priority match (not editable)
the In Priority.
Priority Control X-Tag Priority Control. This parameter controls the
(Access LAG only) behavior of the Priority portion of the frame. If NONE is
selected, the incoming priority bits are left unchanged.
None/Swap
If SWAP is selected, the incoming priority bits are
changed by the value specified in the X-Tag Priority
parameter.
New Priority This parameter defines the new priority bits to be used.
0-7
(Access LAG only) Valid only if Priority Control is set to Swap.
COS Class of Service - user can select the desired COS
from a dropdown list. The default value equals the 0-7
related In Priority.
Inner Tag Priority Specifies whether the flow participates in inner-tag
(Access LAG only) priority swap. The Priority Mapping Table allows the
A2N inner-tag priority to be specified based on 0-7
incoming priority at the Access Port (based on the
priority mapping mode - 802.1P, TOS, DSCP).
Outer Tag Priority The user can select the desired Outer Tag Priority from
a dropdown list. The default value equals the related In 0-7
Priority.


Parameter
Edit PCP Configuration
PCP DE Encoding Standardized modes for editing PCP encoding are None
Mode 7P1D, 6P2D and 5P3D which allow the user to edit 1, 2 7P1D
or 3 PCP pairs, respectively. 6P2D
Also provided is a ‘Custom’ mode that allows the user 5P3D
to edit the PCP Encoding and Decoding Tables directly Custom
and ignore the normal rules regarding priority reuse
and hierarchy. Any use of PCP Encoding may affect
existing traffic. The Custom mode has the potential for
causing unexpected and unintended disruption of nor-
mal traffic.
If ‘PCP DE Encoding Mode’ is set to ‘Custom’, a PCP
Encoding Table and PCP Decoding Table are provided
for custom selections. The PCP Encoding Table allows
user-selectable Drop Ineligible and Drop Eligible prior-
ity values. The PCP Decoding Table allows
user-selectable Outgoing Tag Priority and enabling or
disabling whether the tag is Drop Eligible.
PCP Pair 1, 2, 3 If ‘PCP DE Encoding Mode’ is set to ‘7P1D’, ‘6P2D’ or Drop Ineligible
‘5P3D’, the user can edit 1, 2 or 3 PCP pairs, respec- 0-7
tively. Each priority can only be used once, and the Drop Eligible
lower priority of a pair should always be the drop eligi- 0-7
ble one.
Use the Update Table button to update the PCP
Encoding and Decoding Tables after editing PCP Pairs
1, 2 and/or 3.
Use the Reset PCP Defaults button to reset the PCP
Encoding and Decoding Tables back to default values.
LAG Member (e.g., LAG MEMBER-1-1-1)
Edit Member Port Configuration
LACP Force Out Of Used to forcibly remove a port from the port selection Disabled
SYNC process without deleting it as a member. Enable
Administrative Sets Actor LACP control value to the active or passive Active
Activity state. Passive
Administrative Sets Actor LAG Port Actor LACP Timeout control Long
Timeout value. Long timeout value is 30 seconds (where Link is Short
declared dead after 90 seconds [3x30 seconds]). Short
timeout value is 1 second (where Link is declared dead
after 3 seconds [1x3 seconds]).
Port Priority Actor Port Priority is used to determine which of the 1
ports participating in the LAG has higher priority. A 0-65,535
lower value implies higher priority.
Clear Statistics

1
The LACP-Control parameter allows the selection process to be independent
of the LACP protocol for applications that require a conversion from unpro-
tected port to an active-standby LAG. For configurations where LACP-Con-
trol is disabled, the LACP protocol information may not align with the actual
selection state of the active-standby LAG. Collecting & distributing informa-
tion is derived from the LACP protocol. Active/Standby status is derived from
the port selection process.
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 dis-
abled, the 2 partner systems could experience a mismatch of active and
standby ports causing traffic outage.
The GE11x 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 set-
ting 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 Configuration Options and Rules

Refer to the following table for Network Port configuration settings. Also see the
following associated options and rules: CPD Filters Options and Rules on
p. 709. Default settings are identified in bold. The following Network Port set-
tings are shown in order, as seen when using the eVision web browser manage-
ment tool in Configuration mode.
Network Port 2 (if not associated with another entity) may be switched to oper-
ate 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:
• LAG group
• 1+1 Network protection
• MEPs
• MACOMPs
• ERP instance
• 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:
• LAG group
• Management tunnel
• MEPs
• MACOMPs

• SHG group
• ESA probes or reflectors
• Running ECPA test
• PTP related configurations (GE114S/GE114SH)
After the port type changes, the new port is in the unassigned state and all the
attributes use the system default values.

WARNING (or switching back) will cause the system to reboot,
dropping communications and traffic.
Table 45: Network Port Configuration Settings (Edit Configuration)

Parameter
E1000-N-1/E1000-N-2
Edit Configuration
Alias A text and/or number string the user enters to uniquely up to 64 characters
identify this Network Port. This string can be up to 64 (blank)
Administrative Defines the Network Port facility administrative state. IS
State The administrative state controls the generation of Management
alarms and event reports. When an entity is in the In Maintenance
Service state, it is fully operational. The Administrative
Unassigned
State must be set to Maintenance prior to initiating a
loopback or an Etherjack Diagnostic. When a
protection group is configured, and Network Port 2 is
placed in service. Administrative State and Remote
Link ID options are the only editable options on
Network Port 2. For more information on
p. 599.
Media Type Defines the port media type. Fiber
Copper
MTU Defines the Maximum Transmission Unit size in bytes. 1518-9612
Minimum MTU is 1518; Maximum is 9612.
Configured Speed Sets the configured speed for the network interface. Auto 1000 Full
(Fiber) The user can select auto negotiation or manual 1000 Full
configuration. 100 Full

Table 45: Network Port Configuration Settings (Edit Configuration) (Continued)

Parameter
Configured Speed Sets the configured speed for the network interface. Auto
(Copper) The user can select auto negotiation or manual Auto 1000 Full
configuration. Auto 1000 Full
Master
Auto 1000 Full
Slave
Auto 100 Full
Auto 10 Full
100 Full
10 Full
MDIX If Media Type is Copper, MDIX can be edited. If Media Auto
Type is Fiber, MDIX is not applicable. Crossed
Uncrossed
Auto Diagnostic Enables or disables the automatic Cable Diagnostic Enabled
tests when the cable is removed from the port. This Disabled
option is Disable if Media Type is Fiber.
Drop Eligibility Enables or disables Drop Eligibility. Enabled
Indicator Disabled
B-MAC Address Define the Source MAC Address for the I-Tag frames (Network Port MAC
to be transmitted in the Backbone network. Default is Address)
the MAC address of the current Network Port. User
may also enter other MAC address manually.
Port Shaping Enables or Disables Network Port Shaping. Shaping is Enabled
useful to limit the burst size of the traffic being offered Disabled
to the network. Port rate shaping at the Network Port
enables over-subscription of client services without
exceeding a specified Network Port bandwidth.
Port Shaped Speed Defines the maximum bandwidth on the Network Port
(in bps). Applicable when Port Shaping is Enabled.
This allows a carrier to force a virtual maximum
bandwidth on a Network Port and allows Access Port
services (EIR) to compete for bandwidth allocation.
0 to 1,000,000,000
Setting can not be lower than the cumulative CIR
setting for all Access Ports. If Network Port 1 and
Network Port 2 are part of LAG, this attribute can be
edited on Network Port 1 and will be replicated on
Network Port 2.
Q in Q EtherType Defines the Stacked Ethertype to be used to 0 (hex.)
interoperate with Q in Q frames with other vendors.
Only editable if Q in Q EtherType Override is enabled.
Override Disabled


Parameter
Link Loss Enable or Disable Link Loss Forwarding Port LLF Disabled
Forwarding Port status.
LLF Status
Note: If the Network Port, LOS or RFI alarm notification
Enabled
code is set to Not Reported or Not Alarmed, then the
Link Loss Forwarding feature will not activate for that
alarm attribute.
Link Loss Sets the Link Loss Enable Delay, in seconds, from the
Forwarding Delay time Link Loss is detected before Link Loss Forwarding
takes effect. If the loss clears during delay time, it is not 0-3600
propagated. Only effective if Link Loss Forwarding is
Enabled.
Link Loss Sets link Loss Forwarding Transmit Signal Type. No Action
Forwarding TX EFM Signal
Action Link Down
Forwarding Trigger Link Loss Forwarding signal. Either EFM or Link Down
Link Down
Events may be selected, or both. In default, none are selected.
Link Loss Defines the Local Link ID for the Network port to
Forwarding Local indicate which port is faulted. Applicable entries are 1
1 or 2
Link ID or 2. Default for Network port 1 is 1 and the default for
Network port 2 is 2.
Link Loss Allows selection of the Remote Link ID(s) to be used
Forwarding for matching against the Link ID in the EFM RLD
check boxes for
Remote Link IDs (Remote Link Down) message. The same Remote Link
Link IDs
ID number may be set for multiple Network ports, if
desired. Default is no ports selected.
Nearest Bridge: If selected, the LLDP frame propagation scope will
(01:80:c2:00:00:0e include a single LAN which limits the propagation of
Selected
) LLDP frames across a link, and the MAC Address
/Unselected
01:80:c2:00:00:0e will be used as the destination
address in LLDP frames.
Nearest non-TPMR If selected, the LLDP frame propagation scope will
Bridge include the transmission of LLDP frames through
Selected
(01:80:c2:00:00:03 Two-Port MAC Relays (TPMR) between two
/Unselected
) C-VLAN/S-VLAN components or 802.1d bridges. and
the MAC Address 01:80:c2:00:00:03 will be used as
the destination address in LLDP frames,
Nearest Customer If selected, the LLDP frame propagation scope will
Selected
(01:80:c2:00:00:00 TPMRs and S-VLAN components between C-VLAN
/Unselected
) components or 802.1d bridges, and the MAC Address
01:80:c2:00:00:00 will be used as the destination
Edit CPD Filters - see CPD Filters Options and Rules on p. 709.
Edit EFM-OAM


Parameter
State Manages the EFM OAM on the Ethernet Network Port. Disabled
OAM Control Enabled
Local Configuration Configures the OAM sub-layer entity in either Active or OAM Active
Mode Passive mode. OAM Passive
Edit Sync-E
Sync-E Mode When Enabled, the port can be sourced as a reference Disabled
source for the System Clock; when Disabled, the port
is not available in the pick-list for System Clock Enabled
references.
QL Mode When Enabled, the port will receive and generate SSM Disabled
quality level according to G.8264. Enabled
Assumed QL Select the forced QL value if the port is used as the QL-NONE
sync reference and there’s no failure on the recovered QL-PRC
clock, the Assumed QL is used as the QL for sync QL-SSU-A
reference selection.
QL-SSU-B
QL-EEC1
Expected QL This control allows the user to set a minimum expected QL-NONE
QL for that port. If the QL falls below that value, the QL-PRC
port should be considered failed from a Sync QL-SSU-A
Reference perspective and a QL Mismatch alarm will
QL-SSU-B
be raised.
QL-EEC1
Edit Priority Mapping Table
In Priority For each “In Priority” (0-7) the user can select a COS
and/or an Outer Tag Priority from a dropdown list. The 0-7
default values of COS and Outer Tag Priority match (not editable)
the In Priority.
COS Class of Service - user can select the desired COS
from a dropdown list. The default value equals the 0-7
related In Priority.
Outer Tag Priority The user can select the desired Outer Tag Priority from
a dropdown list. The default value equals the related In 0-7
Priority.
Edit A2N Shapers
Buffer Size The buffer size of the shaper. 0-15360
128 for E1000-N-1
N/A for E1000-N-2


Parameter
Edit PCP Configuration (Network Port 1 Only)
or 3 PCP pairs respectively. 6P2D
to edit the PCP Encoding and Decoding Tables directly
mal traffic.
If ‘PCP DE Encoding Mode’ is set to ‘Custom’, a PCP Custom
‘5P3D’, the user can edit 1, 2 or 3 PCP pairs respec- 0-7
tively. Each priority can only be used once, and the
lower priority of a pair should always be the drop eligi-
ble one.
Use the Update Table button to update the PCP Drop Eligible
Encoding and Decoding Tables after editing PCP Pairs 0-7
1, 2 and/or 3.
Edit LLDP - see LLDP Configuration Settings on p. 713
Access Port Configuration Options and Rules

The following option descriptions are provided as a detailed reference for build-
ing services. It provides entry range values, dependencies and identifies default
data. For general instructions on building services, see Provision Access Port
Services on p. 255. For additional technical data, see Traffic Management in
FSP 150CC GE11x R6.1 Installation and Operations Manual document.
The following Access Port settings are shown in order, as seen when using the
eVision web browser management tool 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 oper-
ate 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:
• LAG group
• 1+1 Network protection
• MEPs
• MACOMPs
• ERP instance
• 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:
• LAG group
• Management tunnel
• MEPs
• MACOMPs
• SHG group
• ESA probes or reflectors
• Running ECPA test
• PTP related configurations (GE114S/GE114SH)
After the port type changes, the new port is in the unassigned state and all the
attributes use the system default values.
WARNING (or switching back) will cause the system to reboot,
dropping communications and traffic.
Edit Access Port Configuration

One of two service types may be created for an Access Port: Ethernet Private
Line (EPL) service or Ethernet Virtual Private Line (EVPL) service. Refer to one
of the following for Access Port service configuration options and rules:
• Ethernet Private Line (EPL) Service Provisioning on p. 667
• Ethernet Virtual Private Line (EVPL) Service Provisioning on p. 679
Ethernet Private Line (EPL) Service Provisioning

Refer to the following for provisioning a port in Ethernet Private Line (EPL)
Mode. It is recommended that you review the following configuration options

and rules and pre-determine the desired provisioning details prior to making any
provisioning changes to a service. (Default settings are identified in bold.)
Changing the Service Type on a port will drop all traffic on
Changing the Buffer Size is not hitless. Reducing CBS

WARNING may not be hitless.
Table 46: Configuration Settings for Ethernet Private Line Service

Parameter
Access Port (Edit Configuration)
Alias A text and/or number string the user enters to uniquely up to 64 characters
identify this Access Port. This string can be up to 64 (blank)
Administrative Defines the Access Port facility administrative state. IS
Disabled
loopback or an Etherjack Diagnostic. The Unassigned
Administrative State must first be set to Unassigned
state prior to changing the Service Type. For more
information on Administrative States, see Entity State
Copper
Minimum MTU is 1518; Maximum is 9612. 9600
MDIX Defines the Media Dependent Interface, Crossover Auto
(copper) function for copper interfaces. MDIX allows the Crossed
Configured Speed Sets the configured speed for the access interface. The Auto
(Copper) user can select auto negotiation or manual Auto 1000 Full
Master
Auto 1000 Full
Slave
Auto 100 Full
Auto 10 Full
100 Full
10 Full

Table 46: Configuration Settings for Ethernet Private Line Service (Continued)
Parameter
Configured Speed Sets the configured speed for the access interface. The Auto 1000 Full
(Fiber) user can select auto negotiation or manual 1000 Full
(copper) tests when the cable is removed from the port. Disabled
Indicator Disabled
Service Type Defines the service type for this Access port - either EPL
Ethernet Private Line (EPL) or Ethernet Virtual Private EVPL
Line (EVPL). The Access Port Administrative State
must first be set to Unassigned state prior to changing
the Service Type. When changing from Access Port
Service Type EVPL to EPL, a new Flow is automatically
created in the Unassigned state.
AFP Defines the Acceptable Frame Policy. See Acceptable AFP Tagged
Frame Policy in FSP 150CC GE11x R6.1 Technical AFP Untagged
Descriptions document. AFP All
Q in Q Ethertype Defines the Stacked Ethertype to be used to
inter-operate with Queue-in-Queue frames with other

0 (hex)
vendors. Only editable if Q in Q EtherType Override is
enabled.
Override Disabled
802.3 Pause RX Defines the receive flow control for the facility. Enabled
Disabled
802.3 Pause TX Defines the transmit flow control for the facility. Enabled
Disabled
Port Shaping Enables or Disables Access Port Shaping. Port Enabled
shaping limits the output traffic rate to a value below Disabled
the provisioned/negotiated physical port speed.
Shaping is useful to limit the burst size of the traffic
being offered to the client.
Port Shaped Defines the maximum bandwidth on the Access Port 0 to 1,000,000,000
Speed (in bps). Applicable when Port Shaping is Enabled. (bps)
Link Loss Enable or Disable Link Loss Forwarding. Disabled
Forwarding Port
Enabled
LLF Status
Forwarding Delay time Link Loss is detected before LLF takes effect. If
0-3600 (sec.)
the loss clears during delay time, it is not propagated.
Only effective if Link Loss Forwarding is Enabled.

Parameter
Link Loss Defines the Facility Link Loss Forwarding transmit No Action
Forwarding action to notify the network (upstream) of access port EFM Signal
TX Action failures. All access ports must be set consistently,
otherwise individual access port(s) may be set to No Link Down
Action.
Forwarding Link Loss Forwarding signal. Either EFM or Link Down
Link Down
Trigger Events may be selected, or both.
Link Loss Defines the Local Link ID for the Access port to indicate
1 to 6
Forwarding Local which port is faulted. Local Link ID is only provisionable
N/A
Link ID if Link Loss Forwarding is set to Send EFM RLD Msg.
Link Loss Allows selection of the Remote Link ID(s) to be used
Forwarding for matching against the Link ID in the EFM RLD
1 to 6
Remote Link IDs (Remote Link Down) message. The same Remote Link
N/A
ID number may be set for multiple Access Ports, if
desired.
Nearest Bridge If selected, the LLDP frame propagation scope will
(01:80:c2:00:00:0e include a single LAN which limits the propagation of
Selected
) LLDP frames across a link, and the MAC Address
/Unselected
Nearest If selected, the LLDP frame propagation scope will
non-TPMR Bridge include the transmission of LLDP frames through
Selected
(01:80:c2:00:00:03 Two-Port MAC Relays (TPMR) between two
/Unselected
) C-VLAN/S-VLAN components or 802.1d bridges. and
the MAC Address 01:80:c2:00:00:03 will be used as
the destination address in LLDP frames,
Edge include the transmission of LLDP frames through
Selected
(01:80:c2:00:00:00 TPMRs and S-VLAN components between C-VLAN
/Unselected
) components or 802.1d bridges, and the MAC Address
Edit CDP Filters - see CPD Filters Options and Rules on p. 709.
Edit EFM-OAM
OAM Control Enabled
Local Configures the OAM sub-layer entity in either Active or OAM Active
Configuration Passive mode.
OAM Passive
Mode
Edit Sync-E
Sync-E Mode Determines whether the Ethernet port operates in Disabled
SyncE Mode. Disabled means the port operates in
non-Sync mode. Enabled means the port operates in Enabled
sync mode.

Parameter
QL Mode Determines whether the Ethernet port operates in Disabled
Quality Level (QL) Mode. The QL Mode for an Ethernet
port cannot be set to Enabled unless the SyncE Mode Enabled
attribute is also set to Enabled.
Assumed QL Specifies the assumed Quality Level (QL) on the QL-NONE
Ethernet Port. Assumed QL is a QL value that is forced QL-PRC
at a receiving interface. QL-SSU-A
For QL mode disabled, the selected Assumed QL is a
QL-SSU-B
value specified for the received recovered timing
reference (if not in the failed state).
For QL mode enabled, the selected Assumed QL
overrides the received QL value if interface is not in the
failed state and if the Assumed QL value is not QL-EEC1
QL-NONE. When Assumed QL value is QL-NONE, the
received QL represents the QL for the interface.
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
Expected QL Set the Expected QL for the Ethernet port. When the QL-NONE
Received QL value is lower than the Expected QL QL-PRC

value, the interface is declared as failed and a Sync QL QL-SSU-A
Mismatch alarm is declared against the interface.The
QL-SSU-B
Expected QL only has meaning when the QL Mode
attribute is set to Enabled. QL-EEC1
Valid entry for SONET Network Clock: QL-NONE, QL-NONE
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-PRS
QL-EEC2, QL-SMC, QL-PROV. QL-STU
QL-ST2
QL-TNC
QL-ST3E
QL-EEC2
QL-SMC
QL-PROV
Edit N2A Shapers
Buffer Size The buffer size of the shaper (in KB). 0-15360
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 values.

Parameter
mal traffic.
‘5P3D’, the user can edit 1, 2 or 3 PCP pairs respec- 0-7
tively. Each priority can only be used once, and the
lower priority of a pair should always be the drop eligi-
ble one.
1, 2 and/or 3.
PCP Encoding If ‘PCP DE Encoding Mode’ is set to ‘Custom’ for each Drop Ineligible
Table ‘Incoming Tag Priority’ the user can select the desired 0-7
Drop Ineligible and Drop Eligible priority. Drop Eligible
0-7
PCP Decoding If ‘PCP DE Encoding Mode’ is set to ‘Custom’ for each Outgoing Tag
Table ‘Incoming Tag Priority’ the user can select the desired Priority
Outgoing Tag Priority and enable or disable Drop 0-7
Eligible. Drop Eligible
Disabled/Enabled
Flow
Edit Configuration
Circuit Name Defines a circuit identifier for the Flow. Up to 256 up to 256 characters
characters are allowed. (blank)
COS Specifies the COS (Class of Service) value for the
Traffic Flow. This value is used at flow creation time to 0 to 7
identify the COS level of the A2N and N2A shaper.

Parameter
Network Interface Select the Network Interface for this flow. Candidates NETWORK
include: Network port, Network LAG, Network PPG PORT-1-1-1-1
(including 1+1, Dual-Active, RP entity with network ring
port,), and SHG entity with network member port. Note NETWORK
that PPG, SHG and LAG can not coexist; if any one PORT-1-1-1-2
type exists, the other two cannot exist.
Access Interface Select the Access Interface for this flow. Candidates
include: the current Access port, LAG (if any) with
Current Access Port
current port as member, and SHG (if any) entity with
current port as member.
Policing Enable/Disable the selected Policing Control. When Enabled
the policing is Disabled, the policer in the
Disabled
corresponding direction will not work.
Policing Control Specify the policing direction of the flow. A2N_N2A
A2N
N2A
A2N Shaping If Flow Based is selected, system will assign 8 Flow Based
(GE112/GE114/G independent queues for this flow for A2N shaping; If
E114/GE114PH) Port Based is selected, system will schedule this flow

Port Based
to use the queues of the specified Network Interface
according to the COS specified for this flow.
COS Specify the flow priority scheduled at the Network
0 to 7
Interface.
PBB Frames If Enabled, the flow will forward the received PBB Disabled
frames; If Disabled, the flow will discard the received
Enabled
PBB frames.
Independent N2A Manages N2A rate limiting, independent of A2N rate Disabled
Rate Limiting limiting. When not enabled, N2A specification is the Enabled
same as A2N.
Frame Loss Specifies the frame-loss ratio (%) per flow that starts 0 to 100
Threshold Ratio counting Severely Errored Seconds (SES) on the flow. 30
This functionality is applicable if the flow is monitored
using the Y.1731 ESA functionality.
Frame Loss Specifies the number of frames lost per flow that starts 1 to 2147483647
Threshold counting Errored Seconds (ES) on the flow. This 1
functionality is applicable if the flow is monitored using
the Y.1731 ESA functionality.
N2N Forwarding Enable/Disable Network to Network forwarding when Disabled
the Network Interface of this flow is an ERP ring port. If Enabled
Enabled, the flow received on this access interface
with the same VLAN ID as this flow will be forwarded to
the other ERP ring port in addition to Access to
Network forwarding and reach to the next node in the
ERP group; If Disabled, the flow with the same VLAN
ID as this flow will not be forwarded to the next node,
but received by this flow.

Parameter
Network Interface If set to None, the specified Network Interface will not None
Learning Control learn the Source MAC Address of received frames; If MAC Based
set to MAC Based, the Network Interface will learn the
Source MAC Address of receiving frames.
Protected Network If set to None, the existing MAC addresses learned by None
Learning Control the Network Interface will not prevent the interface Discard
learning the same MAC addresses in the received
frame SA; if set to Discard, the same MAC addresses
in the received frame SA will not be learned and
preserved, but discarded.
Max Network Specify the maximum Forwarding Table Entries (MAC 0 to 2048
Forwarding Table learned) allowed by the Network Interface.
Entries
MAC Table Full The action to take when the MAC table is full. Forward
Action Block
Access Interface If set to None, the specified Access Interface will not None
set to MAC Based, the Access Interface will learn the
Protected Access If set to None, the existing MAC addresses learned by None
Learning Control the Access Interface will not prevent the interface Discard
learning the same MAC addresses in the received Block
frame SA; if set to Discard, the same MAC addresses
in the received frame SA will not be learned and
Max Access Specify the maximum Forwarding Table Entries (MAC 0 to 2048
Forwarding Table learned) allowed by the Access Interface.
Entries
Aging Timer The aging time of the MAC address learned. 0 to 100000000
300
C-Tag Control Defines whether the C (Customer) Tag VLAN ID / Push
VLAN Priority should be PUSHed or no action taken. None
If more than one Access port is to be used in the
system, Push must be selected. If C-Tag Control is set
to None, only one LAN port may be used in the system.
If C-Tag Control is set to None, then C-Tag VLAN ID
and C-Tag VLAN Priority cannot be entered.

Parameter
C-Tag Defines the C-Tag VLAN ID that will be PUSHed. This 1 to 4095
option is only available if C-Tag Control is set to Push. E1000-A-2 (if
All C-Tag and S-Tag VLAN ID-Priority values must not provisioned)
conflict on the Network port. (For example: A service default is 2
with C-Tag PUSH 100-0, S-Tag PUSH 100-0 will E1000-A-3
conflict with another service with the same C-Tag and default is 3
S-Tag. A service with C-Tag PUSH 100-0, S-Tag None
E1000-A-4
will conflict with another service with C-Tag None,
default is 4
S-Tag PUSH 100-0. An EPL service with C-Tag PUSH
100-0, S-Tag NONE will conflict with a Flow with VLAN E1000-A-5
Member 100-0, C-Tag NONE and S-Tag NONE.) default is 5
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).
S-Tag Control Defines whether the S (Service) Tag VLAN ID / VLAN Push
Priority should be PUSHed or no action taken. None

If S-Tag Control is set to None, S-Tag VLAN ID and
C-Tag VLAN Priority cannot be entered.
S-Tag Defines the S-Tag VLAN ID that will be PUSHed. This 1 to 4095
option is only applicable if S-Tag Control is set to Push. E1000-A-2 (if
All C-Tag and S-Tag VLAN ID-Priority values must not provisioned)
conflict on the Network port. (For example: A service default is 2
with C-Tag PUSH 100-0, S-Tag PUSH 100-0 will E1000-A-3
conflict with another service with the same C-Tag and default is 3
S-Tag. A service with C-Tag PUSH 100-0, S-Tag None
E1000-A-4
will conflict with another service with C-Tag None,
default is 4
S-Tag PUSH 100-0. An EPL service with C-Tag PUSH
100-0, S-Tag NONE will conflict with a Flow with VLAN E1000-A-5
Member 100-0, C-Tag NONE and S-Tag NONE.) default is 5
E1000-A-6
default is 6
Defines the S-Tag VLAN Priority that will be PUSHed.
This option is only applicable if S-Tag Control is set to
Push. 0 to 7
conflict on the Network port (see S-Tag VLAN ID).
I-Tag Control Defines whether the I (Instance) Tag SID (Service None
(GE112/GE114/G Instant VLAN ID)/ VLAN Priority should be PUSHed or
E114H/GE114PH) no action taken.
If I-Tag Control is set to None, then I-Tag VLAN ID and Push
I-Tag VLAN Priority cannot be entered.

Parameter
I-Tag Defines the I-Tag VLAN ID that will be PUSHed. This
(GE112/GE114/G option is only applicable if I-Tag Control is set to Push. 256 to 16777214
E114H/GE114PH)
Defines the I-Tag VLAN Priority that will be PUSHed.
This option is only applicable if I-Tag Control is set to 0 to 7
Push.
Destination Enable/Disable Backbone MAC Address in front of Disabled
Backbone MAC Ethernet packet. This option is configurable only when
(GE112/GE114/G I-Tag Control is set to Push. Enabled
E114H/GE114PH)
Backbone MAC The backbone MAC destination address to be added in
Destination front of Ethernet packet. When I-Tag Control is set to
Address Push, Destination Backbone MAC is set to Disabled, a
(GE112/GE114/G default MAC Destination Address calculating with the
01:1e:83:00:00:00
E114H/GE114PH) I-Tag VID will be used; When I-Tag Control is set to
Push, Destination Backbone MAC is set to Enabled,
user can specify a Backbone MAC Destination
Address themselves.
A2N Policer CIR Defines the 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.
• If Network Port Shaping is Disabled: PIR (Peak
Information Rate) = CIR + EIR; must not exceed
the speed of the Network Port.
• If Network Port Shaping is Enabled: PIR must be
less than or equal to the Network Port Shaped
Speed. 0 to 1 Gbps
• If Access Port Shaping is Disabled: PIR (Peak
the speed of the Access Port.
• If Access Port Shaping is Enabled: PIR must be
less than or equal to the Access Port Shaped
Speed.
Entries are rounded up to the next 64,000 bps incre-
ment (e.g., if the value of 1 bps is entered, then the
value will automatically be rounded up to 64,000 bps; if
the value of 5,000,000 bps is entered, then the value
will automatically be rounded up to 5,056,000 bps).

Parameter
A2N Policer EIR Defines the Policer Excess Information Rate (EIR) for
this Policer, in bps. If Policer CIR is set to 0, then a
Policer EIR value of 64,000 bps or greater must be
Network Port speed.
• If Network Port Shaping is Disabled: PIR (Peak
the speed of the Network Port.
• If Network Port Shaping is Enabled: PIR must be
less than or equal to the Network Port Shaped
Speed. 0 to 1,000,000,000
(bps)
• If Access Port Shaping is Disabled: PIR (Peak
the speed of the Access Port.
• If Access Port Shaping is Enabled: PIR must be
less than or equal to the Access Port Shaped
Speed.
Entries are rounded up to the next 64,000 bps incre-

ment (e.g., if the value of 1 bps is entered, then the
A2N Policer CBS Defines the Policer Committed Burst Size (CBS) for
this Policer, in Kilobytes. The minimum Policer CBS
entry allowed is based on the Policer CIR entry, see
0 to 1,024 (KB)
Table 48. For IP type traffic, see Table 49 for
recommended CBS value, based on CIR/EIR entry
range.
A2N Policer EBS Defines the Policer Excess Burst Size (EBS) for this
Policer, in Kilobytes. The minimum Policer EBS entry
allowed is based on the Policer EIR entry, see
0 to 1,024 (KB)
Table 48. For IP type traffic, see Table 49 for
recommended EBS value, based on CIR/EIR entry
range.
A2N Policer Color Specifies the Color Mode as 'Color Aware' or 'Color Color Aware
Marking Blind' for the A2N Policer. Color Blind

Parameter
A2N Policer Color Enable/Disable Color Coupling Flag for the policer in Enabled
Coupling Flag A2N direction. When coupling is enabled, tokens that Disabled
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-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 of frames declared ˜yellow” to be
bounded by CIR + EIR.

delivered/received 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 a provisioned
EIR of 0 allows for a single rate three color marking
(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.
Add Forwarding Table Entry
Destination Add a specified static destination MAC address to the (blank)
Address Forwarding table for this flow.
Destination Port Select the destination port where the input Destination Access Interface of
Address is learned. this flow
Network Interface of
this flow
Learning Action Select the action to take when this Destination Address Block
is learned. If set to Block, the learned address will be Forward
discarded and this flow will block the learning of this
MAC address again; if set to Forward, this flow will
forward this learned Destination Address.

Ethernet Virtual Private Line (EVPL) Service

Provisioning
Refer to the following for provisioning a Ethernet Virtual Private Line (EVPL) ser-
vice. It is recommended that you review the following configuration options and
rules and pre-determine the desired provisioning details prior to making any pro-
visioning changes to a service. Default settings are identified in bold.
Changing Service Type on a port will drop all traffic on the

WARNING port, including Management Tunnel connectivity and
Changing the Buffer Size is not hitless. Reducing CBS

WARNING may not be hitless.
Table 47: Configuration Settings for Ethernet Virtual Private Line Service
Parameter
Access Port (Edit Configuration)
Alias A text and/or number string the user enters to uniquely up to 64
identify this Access Port. This string can be up to 64 characters

printable ASCII characters long. (blank)
Administrative Defines the Access Port facility administrative state. IS

Disabled
loopback or an Etherjack Diagnostic. The Unassigned
Administrative State must first be set to Unassigned
state prior to changing the Service Type. For more
information on Administration States, see Entity State
Copper
Minimum MTU is 1518; Maximum is 9612. 9600
MDIX (Copper) Defines the Media Dependent Interface, Crossover Auto
function for copper interfaces. MDIX allows the Crossed

Table 47: Configuration Settings for Ethernet Virtual Private Line Service (Continued)
Parameter
Configured Speed Sets the configured speed for the access interface. The Auto
(Copper) user can select auto negotiation or manual Auto 1000 Full
Master
Auto 1000 Full
Slave
Auto 100 Full
Auto 10 Full
100 Full
10 Full
Configured Speed Sets the configured speed for the access interface. The Auto 1000 Full
(Fiber) user can select auto negotiation or manual 1000 Full
(Copper) tests when the cable is removed from the port. Disabled
Indicator Disabled
Service Type Defines the service type for this Access port - either EPL
Ethernet Private Line (EPL) or Ethernet Virtual Private EVPL
Line (EVPL). The Administrative State must first be set
to Unassigned state prior to changing the Service Type.
AFP Defines the Acceptable Frame Policy. See Acceptable AFP Tagged
Frame Policy in FSP 150CC GE11x R6.1 Technical AFP Untagged
Descriptions document. AFP All
Q in Q Ethertype Defines the Stacked Ethertype to be used to
inter-operate with Queue-in-Queue frames with other
vendors. Only editable if Q in Q EtherType Override is 0 (hex)
enabled.

Override Disabled
Port Defines the Port VLAN ID. The format is VID-PRIO. 1 to 4095-[0 to 7]
VLAN ID The valid values for VID are 1 to 4095 and valid values E1000-A-2 (if
for PRIO are 0 to 7. If only the VID portion is entered, provisioned)
PRIO will default to 0. If the VID portion is not entered, VID default is 2
PRIO also cannot be specified. This option is only valid E1000-A-3
when Service Type is set to EVPL. VID default is 3
E1000-A-4
VID default is 4
E1000-A-5
VID default is 5
E1000-A-6
VID default is 6

Parameter
Priority Map Mode Defines the Priority Map Mode. It identifies the lookup None
criteria for the priority mapping table. This table is used 802.1p
to perform priority based lookup (to determine low and IP-TOS
normal latency) and/or to change the priority value.
IP-DSCP
Priority Map Mode must be set to anything other than
None in order to enable multi-COS on this Access Port.
If Priority Map Mode is set to anything other than None,
a Priority Mapping Table is created. See Default Priority
Mapping Tables on p. 700 for default Priority Map
settings. This option is only valid when Service Type is
set to EVPL.
Port Shaping Enables or Disables Access Port Shaping. Port shaping Enabled
limits the output traffic rate to a value below the Disabled
provisioned/negotiated physical port speed. Shaping is
useful to limit the burst size of the traffic being offered
to the client.
Port Shaped Speed Defines the maximum bandwidth on the Access Port (in
0 to 1,000,000,000
bps) toward the client. Applicable when Port Shaping is
(bps)
Enabled.
N2A VLAN Enables or disables the Network to Access VLAN Enabled

Trunking trunking on the Ethernet Access port. Disabling VLAN Disabled
trunking removes all VLAN tags before transmitting
traffic out of the access port. This option is only valid
when Service Type is set to EVPL.
A2N Push Port VID Sets Push port VLAN ID in the Access to Network Enabled
direction. When Enabled, the Port VLAN ID is PUSHed Disabled
onto the frame. When Disabled, no tags are PUSHEed
onto the frame (i.e., it stays untagged). This option is
only valid when Service Type is set to EVPL.
N2A Pop Port VID Sets Pop port VLAN ID on N2A frames. If Ingress Enabled
PUSH Port VLAN ID is Enabled, it may be desired that Disabled
the PVID may be POPed. This option is only valid when
Service Type is set to EVPL.
Link Loss Enable or Disable Link Loss Forwarding. Disabled
Forwarding Port
Enabled
LLF Status
Forwarding Delay time Link Loss is detected before LLF takes effect. If
0-3600 (sec.)
the loss clears during delay time, it is not propagated.
Only effective if Link Loss Forwarding is Enabled.
Link Loss Defines the Facility Link Loss Forwarding transmit No Action
Forwarding action to notify the network (upstream) of access port LLF EFM Signal
TX Action failures. All access ports must be set consistently,
otherwise individual access port(s) may be set to No LLF Link Down
Action.

Parameter
Forwarding Trigger Link Loss Forwarding signal. Either EFM or Link Down
Link Down
Events may be selected, or both.
Link Loss Defines the Local Link ID for the Access port to indicate
1 to 6
Forwarding Local which port is faulted. Local Link ID is only provisionable
N/A
Link ID if Link Loss Forwarding is set to Send EFM RLD Msg.
Link Loss Allows selection of the Remote Link ID(s) to be used for
Forwarding matching against the Link ID in the EFM RLD (Remote
1 to 6
Remote Link IDs Link Down) message. The same Remote Link ID
N/A
number may be set for multiple Access Ports, if
desired.
Nearest Bridge If selected, the LLDP frame propagation scope will
(01:80:c2:00:00:0e) include a single LAN which limits the propagation of
Selected
LLDP frames across a link, and the MAC Address
/Unselected
Nearest non-TPMR If selected, the LLDP frame propagation scope will
Selected
(01:80:c2:00:00:03) Two-Port MAC Relays (TPMR) between two
/Unselected
C-VLAN/S-VLAN components or 802.1d bridges. and
the MAC Address 01:80:c2:00:00:03 will be used as the
destination address in LLDP frames,
Edge include the transmission of LLDP frames through
Selected
(01:80:c2:00:00:00) TPMRs and S-VLAN components between C-VLAN
/Unselected
components or 802.1d bridges, and the MAC Address
Edit EFM-OAM
OAM Control Enabled
Local Configuration Configures the OAM sub-layer entity in either Active or OAM Active
Mode Passive mode. OAM Passive
Edit Sync-E
Sync-E Mode Determines whether the Ethernet port operates in Disabled
SyncE Mode. Disabled means the port operates in
non-Sync mode. Enabled means the port operates in Enabled
sync mode.
QL Mode Determines whether the Ethernet port operates in Disabled
Quality Level (QL) Mode. The QL Mode for an Ethernet
port cannot be set to Enabled unless the SyncE Mode Enabled
attribute is also set to Enabled.

Parameter
Assumed QL Specifies the assumed Quality Level (QL) on the QL-NONE
Ethernet Port. Assumed QL is a QL value that is forced QL-PRC
at a receiving interface. QL-SSU-A
For QL mode disabled, the selected Assumed QL is a
QL-SSU-B
value specified for the received recovered timing
reference (if not in the failed state).
For QL mode enabled, the selected Assumed QL
overrides the received QL value if interface is not in the
failed state and if the Assumed QL value is not QL-EEC1
QL-NONE. When Assumed QL value is QL-NONE, the
received QL represents the QL for the interface.
Valid entry for SDH Network Clock: QL-PRC,
QL-SSU-A. QL-SSU-B, QL-EEC1. Default is QL-EEC1.
Expected QL Set the Expected QL for the Ethernet port. When the QL-NONE
Received QL value is lower than the Expected QL QL-PRC
value, the interface is declared as failed and a Sync QL QL-SSU-A
Mismatch alarm is declared against the interface.The
QL-SSU-B
Expected QL only has meaning when the QL Mode
attribute is set to Enabled. QL-EEC1

Valid entry for SONET Network Clock: QL-NONE, QL-NONE
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-PRS
QL-EEC2, QL-SMC, QL-PROV. QL-STU
QL-ST2
QL-TNC
QL-ST3E
QL-EEC2
QL-SMC
QL-PROV
Priority Map (Edit Priority Mapping)
Note: Selecting Edit Priority Mapping option is only selectable (by entering a right click on the
Access Port entity) if a Priority Map Mode selection other than None is made for the Access Port
facility.
Note: TOS/DSCP will only be used for classification if there are no tags (valid or invalid ethertype)
on the frame.
In Priority Priority Map Index Selection. The following ranges of 0 to 7
Indexes are: 0...7 if Priority Map Mode is set to 802.1p (802.1p or
or IP-TOS; 0...63 if Priority Map Mode is set to IP-TOS)
IP-DSCP. 0 to 63 (IP-DSCP)
Priority Control X-Tag Priority Control. This parameter controls the None
behavior of the Priority portion of the frame. If NONE is Swap
selected, the incoming priority bits are left unchanged.
If SWAP is selected, the incoming priority bits are
changed by the value specified in the X-Tag Priority
parameter.

Parameter
New Priority This parameter defines the new priority bits to be used. 0 to 7
Valid only if Priority Control is set to Swap.
COS Class Of Service (COS) Policer. Allows the incoming
traffic to be steered to the appropriate EVC Ingress 0 to 7
Policer.
Inner Tag Priority Specifies whether the flow participates in inner-tag
priority swap. The Priority Mapping Table allows the
A2N inner-tag priority to be specified based on 0 to 7
Outer Tag Priority Specifies whether the flow participates in outer-tag
priority swap. The Priority Mapping Table allows the
A2N outer-tag priority to be specified based on 0 to 7
Port N2A Shapers (Edit N2A Shapers)
N2A Shaper Buffer Represents the Buffer Size of the Shaper. Entered in 10 to 15,360 (KB)
Size kilobytes. 0 (KB)
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 values.
Also provided is a ‘Custom’ mode that allows the user
5P3D
causing unexpected and unintended disruption of
normal traffic.
user-selectable Drop Ineligible and Drop Eligible
priority values. The PCP Decoding Table allows

Parameter
‘5P3D’, the user can edit 1, 2 or 3 PCP pairs 0-7
respectively. Each priority can only be used once, and
the lower priority of a pair should always be the drop
eligible one.
1, 2 and/or 3.
Flow
Flow (Create Flow or Edit Configuration)

Note: To delete a Flow, enter a right click on the desired flow and select Delete Flow. Then select
OK.
Flow ID Defines the Flow Identifier (FID) for this flow. Up to 16
(for GE112) or 32 (for GE114x) flows can be created for
(Create Flow only) the system. Each of the Ethernet Client interfaces can FID-1 to FID-16
support a maximum of 32 flows. Every assigned FID-1 to FID-32

Access port reduces the maximum number of available
flows by 1.
Circuit Name Assigns a circuit name to the flow. Up to 256 characters up to 256
are allowed. characters
(blank)
EVC Type Defines the flow type. If Default EVC is selected, no Default EVC
(Create Flow only) VLAN Member value may be supplied, and this FID Regular EVC
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. If Regular EVC is selected, then
individual VLAN Members may be added to the flow.
Flow Type cannot be edited once a flow is created. To

change the Flow Type, the FID must be deleted and
then re-created with the new Flow Type.
Network Interface Select the Network Interface for this flow. Candidates NETWORK
include: Network port, Network LAG, Network PPG PORT-1-1-1-1
(including 1+1, Dual-Active, RP entity with network ring
port,), and SHG entity with network member port. Note NETWORK
that PPG, SHG and LAG can not coexist; if any one PORT-1-1-1-2
type exists, the other two cannot exist.
Access Interface Select the Access Interface for this flow. Candidates ACCESS
include: the current Access port, LAG (if any) with PORT-1-1-1-N
current port as member, and SHG (if any) entity with (N = 3 to 6
current port as member. respectively for
E1000-A-N)

Parameter
Policing Enable/Disable the selected Policing Control. When the Enabled
policing is Disabled, the policer in the corresponding
Disabled
direction will not work.
Policing Control Specify the policing direction of the flow. A2N_N2A
A2N
N2A
COS Specifies the COS (Class of Service) value for the
Traffic Flow. This value is used at flow creation time to
identify the COS level of the A2N and N2A shaper. If 0 to 7
MULTI COS is Enabled, this option is not applicable
when multiple policers/shapers exist on the flow.
Multi COS Enables or Disables Multi Class Of Service (COS). If Enabled
(Create Flow only) set to the Disabled, one N2A Policer and one A2N Disabled
Policer are provisionable. If set to the Enabled state, up
to 8 N2A Policers and 8 A2N Policers may be
provisioned. Multi COS can only be set to the Enabled
state if Priority Map Mode is set to anything other than
None for the facility.
This option is only available during Flow creation and
cannot be edited. If it is desired to edit an existing Flow,
the Flow must be deleted and then re-created with the
Multi COS change.
N2A COS Priority Specifies whether the flow uses the inner-tag or the Outer VLAN Tag
outer-tag in determining the COS (Class of Service) in Inner VLAN Tag
the N2A direction. This option is only applicable if Multi
COS is Enabled.
Untagged Frames Specifies whether untagged traffic is supported. Enabled
Disabled
PBB Frames If Enabled, the flow will forward the received PBB Disabled
frames; If Disabled, the flow will discard the received
Enabled
PBB frames.
Inner Tag Priority Specifies whether the flow participates in inner-tag Enabled
Control priority swap. The Priority Mapping Table Disabled
cmPrioMapTable allows the A2N inner-tag priority to be
specified based on incoming priority at Access Port
(based on priority mapping mode - 802.1p, IP-TOS,
IP-DSCP). TOS/DSCP will only be used for
classification if there are no tags (valid or invalid
ethertype) on the frame.

Parameter
Outer Tag Priority Specifies whether the flow participates in outer-tag Enabled
Control priority swap. The Priority Mapping Table Disabled
cmPrioMapTable allows the A2N outer-tag priority to be
specified based on incoming priority at Access Port
(based on priority mapping mode - 802.1p, IP-TOS,
IP-DSCP). TOS/DSCP will only be used for
classification if there are no tags (valid or invalid
ethertype) on the frame
Independent N2A Manages N2A rate limiting, independent of A2N rate Enabled
Rate Limiting limiting. When not enabled, N2A specification is the Disabled
same as A2N. This option is only applicable if Multi
COS is Disabled.
Frame Loss Specifies the frame-loss ratio (%) per flow that starts 0 to 100
Threshold Ratio counting Severely Errored Seconds (SES) on the flow. 30
This functionality is applicable if the flow is monitored
using the Y.1731 ESA functionality.
Frame Loss Specifies the number of frames lost per flow that starts 1 to 2147483647
Threshold counting Errored Seconds (ES) on the flow. This 1
functionality is applicable if the flow is monitored using
the Y.1731 ESA functionality.

A2N Shaping Shaping method used on A2N direction. Flow Based
(GE112/GE114/GE For a port-based flow, this can be edited after creation.
114/GE114PH) For a regular or default flow, this can only be set at the
time of creation.
If Flow Based is selected, system will assign 8 Port Based

independent queues for this flow for A2N shaping; If
Port Based is selected, system will schedule this flow to
use the queues of the specified Network Interface
according to the COS specified for this flow.
N2N Forwarding Enable/Disable Network to Network forwarding when Disabled
the Network Interface of this flow is an ERP ring port. If Enabled
Enabled, the flow received on this access interface with
the same VLAN ID as this flow will be forwarded to the
other ERP ring port in addition to Access to Network
forwarding and reach to the next node in the ERP
group; If Disabled, the flow with the same VLAN ID as
this flow will not be forwarded to the next node, but
received by this flow.
Network Interface If set to None, the specified Network Interface will not None
set to MAC Based, the Network Interface will learn the

Parameter
Protected Network If set to None, the existing MAC addresses learned by None
Learning Control the Network Interface will not prevent the interface Discard
frame SA; if set to Discard, the same MAC addresses in
the received frame SA will not be learned and
Max Network Specify the maximum Forwarding Table Entries (MAC 0 to 2048
Forwarding Table learned) allowed by the Network Interface.
Entries
MAC Table Full The action to take when the MAC table is full. Forward
Action Block
Access Interface If set to None, the specified Access Interface will not None
set to MAC Based, the Access Interface will learn the
Protected Access If set to None, the existing MAC addresses learned by None
Learning Control the Access Interface will not prevent the interface Discard
Block
frame SA; if set to Discard, the same MAC addresses in
the received frame SA will not be learned and
Max Access Specify the maximum Forwarding Table Entries (MAC 0 to 2048
Forwarding Table learned) allowed by the Access Interface.
Entries
Aging Timer The aging time of the MAC address learned. 0 to 100000000
300
C-Tag Control Defines whether the C (Customer) Tag VLAN ID / Push
VLAN Priority should be PUSHed, Swapped or no Swap VID
action taken. If Swap VID is selected, only the VLAN ID Push VID
(12 bits) are swapped with the specified C-Tag VLAN
None
ID. If Push VID is selected, only the VLAN ID (12 bits) is
PUSHed - the Priority is copied from the incoming tag’s Pop
Priority. If C-Tag Control is set to None, then C-Tag
VLAN ID cannot be entered and C-Tag Match Rx
Priority cannot be selected. If C-Tag Control is set to
None, Swap VID or Push VID, C-Tag VLAN Priority
cannot be entered.

Parameter
C-Tag Defines the C-Tag VLAN ID. If C-Tag Control is set to
None, then C-Tag VLAN ID cannot be entered.
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-Tag and
1 to 4095
S-Tag combination. A service with C-Tag PUSH 100-0,
S-Tag None will conflict with another 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
0 to 7
entered. All C-Tag and S-Tag VLAN ID-Priority values
must not conflict on the Network port (see above).
I-Tag Control Defines whether the I-Tag and I-Tag Priority should be None
PUSHed, If Push IS is selected, only the VLAN ID (12 Push
bits) is PUSHed - the Priority is copied from the
incoming tag’s Priority. If I-Tag Control is set to None,

then I-Tag ID cannot be entered. Push IS ID
No I-Tag operation can be performed at the same times
as C-Tag or S-Tag Operation.
I-Tag Defines the I-Tag ID. If I-Tag Control is set to None,
256-16777214
then I-Tag ID cannot be entered.
Defines the I-Tag Priority. If I-Tag Control is set to None
0 to 7
or Push IS ID, I-Tag Priority cannot be entered.
S-Tag Control Defines whether the S (Service) Tag VLAN ID / VLAN Push
Priority should be PUSHed, Swapped or no action None
taken. If S-Tag Control is set to None, S-Tag VLAN ID
and S-Tag VLAN Priority cannot be entered. Swap VID
is only available if C-Tag Control is set to “None”.

Parameter
S-Tag 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-Tag and S-Tag
1 to 4095
combination. A service with C-Tag PUSH 100-0, S-Tag
None will conflict with another service with C-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
conflict on the Network port (see above).
I-Tag Control Defines whether the I (Instance) Tag SID (Service None
(GE112/GE114/GE Instant VLAN ID)/ VLAN Priority should be PUSHed or Push
114H/GE114PH) no action taken.
If I-Tag Control is set to None, then I-Tag VLAN ID and Push IS ID
I-Tag VLAN Priority cannot be entered.
I-Tag Defines the I-Tag VLAN ID that will be PUSHed. This
(GE112/GE114/GE option is only applicable if I-Tag Control is set to Push. 256 to 16777214
114H/GE114PH)
Defines the I-Tag VLAN Priority that will be PUSHed.
This option is only applicable if I-Tag Control is set to 0 to 7
Push.
Preserve S-Tag Preserve the S-Tag properties. Disabled
Properties Enabled
N2A Outer Tag Enable/Disable N2A Outer Tag priority. Disabled
Priority Enabled
Destination Enable/Disable Backbone MAC Address in front of Disabled
Backbone MAC Ethernet packet. This option is configurable only when
(GE112/GE114/GE I-Tag Control is set to Push. Enabled
114H/GE114PH)
Backbone MAC The backbone MAC destination address to be added in
Destination front of Ethernet packet. When I-Tag Control is set to
Address Push, Destination Backbone MAC is set to Disabled, a
(GE112/GE114/GE default MAC Destination Address calculating with the
01:1e:83:00:00:00
114H/GE114PH) I-Tag VID will be used; When I-Tag Control is set to
Push, Destination Backbone MAC is set to Enabled,
user can specify a Backbone MAC Destination Address
themselves.

Parameter
Hierarchical COS Whether to use Hierarchical COS Settings. Disabled
Settings Only available for Multi-COS enabled Flow.
Hierarchical COS Settings can be used by selecting the
checkbox. Hierarchical COS settings allows managing
bandwidth profiles of schedule entities by bounding a Enabled
group of traffic classes (Multi COS group). The user
can set values for the guaranteed and maximum flow
bandwidths bounding the whole multi COS group.
Guaranteed Flow Guaranteed bandwidth for the flow.
Bandwidth This option is only available if Multi COS is enabled and
the Hierarchical COS Settings is selected. This allows
the provisioning of guaranteed bandwidth of a flow.
Guaranteed Flow Bandwidth (GFB) must be less than
or equal to the Maximum Flow Bandwidth. The sum of a
Flow's A2N Shaper CIR values must be less than or
equal to the Guaranteed Flow Bandwidth.
By default, GFB is set to the sum of all CIRs for the

Multi COS Group, and can not be set to a lower
0 to 1 Gbps
number. If set to a higher number, the difference is

N/A
termed “excess CIR” for the flow. 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 system.
Entries are rounded up to the next 64,000 bps

increment (e.g., if the value of 1 bps is entered, then the

Parameter
Maximum Flow Supports the Hierarchical Class of Service (HCOS)
Bandwidth 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 Bandwidth
value. Note: The oversubscribed Maximum Flow
Bandwidth 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.
If Access Port Port Shaping is disabled, then Maximum
0 to 1 Gbps
Flow Bandwidth must be less than or equal to the
N/A
Access Port port speed.
If Access Port Port Shaping is enabled, then Maximum
Access Port port shaped speed.
If Network Port Port Shaping is disabled, then
Maximum Flow Bandwidth must be less than or equal
to the Network Port port speed.
If Network Port Port Shaping is enabled, then Maximum
Network Port port shaped speed.
A2N Policer Active Checkbox for selecting the desired Active A2N
Checkbox Policers. This option is only available if Multi COS is Check boxes for
enabled. To activate Policer entry, select the desired Policers 0-7
Policer (0 to 7).

Parameter
A2N Policer CIR 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
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.
If Network Port Port Shaping is Disabled: PIR (Peak
0 to 1 Gbps
Information Rate) = CIR + EIR; must not exceed the
speed of the Network Port.
If Network Port Port Shaping is Enabled: PIR must be
less than or equal to the Network Port Shaped Speed.
If Access Port Port Shaping is Disabled: PIR (Peak

speed of the Access Port.
If Access Port Port Shaping is Enabled: PIR must be
less than or equal to the Access Port Shaped Speed.

Parameter
A2N Policer EIR 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
Network Port speed. 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.
If Network Port Port Shaping is Disabled: PIR (Peak
Information Rate) = CIR + EIR; must not exceed the 0 to 1 Gbps
speed of the Network Port.
If Network Port Port Shaping is Enabled: PIR must be
less than or equal to the Network Port Shaped Speed.
A2N Policer CBS Defines the A2N Policer Committed Burst Size (CBS)
for this port, in Kilobytes. The minimum A2N Policer
CBS entry allowed is based on the A2N Policer CIR
0 to 1,024 (KB)
entry, see Table 48. For IP type traffic, see Table 49 for
range.
A2N Policer EBS Defines the A2N Policer Excess Burst Size (EBS) for
this port, in Kilobytes. The minimum A2N Policer EBS
entry allowed is based on the A2N Policer EIR entry,
0 to 1,024 (KB)
see Table 48. For IP type traffic, see Table 49 for
range.
A2N Policer Color Specifies the A2N Policer Color Mode as 'Color Aware' Color Aware
Marking or 'Color Blind'. Color Blind

Parameter
A2N Policer Color Specifies the A2N Policer Coupling Flag. When Enabled
Coupling Flag coupling is enabled, tokens that would normally be Disabled
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-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 of frames declared ˜yellow” to be bounded by
CIR + EIR. This allows a higher volume of yellow
frames to be delivered/received 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 a provisioned EIR of 0 allows for a single rate three
color marking (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.
A2N Shaper Queue Specifies the A2N Shaper Queue Identifier associated 0-7
ID with this Policer. This option is only available if Multi

COS is enabled.
A2N Shaper Buffer Represents the A2N Buffer Size of the Shaper. Entered 10 to 15,360 (KB)
Size in kilobytes.
N2A Policer Active Checkbox for selecting the desired Active N2A
Checkbox Policers. This option is only available if Multi COS is
Check boxes for
enabled. Box selection must be made before Policer
Policers 0-7
entry is allowed. At least one N2A Policer must exist on
a Flow.
N2A Policer CIR 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.
0 to 1 Gbps

Parameter
N2A Policer EIR 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.
If Port Shaping is Disabled: PIR (Peak Information
Rate) = CIR + EIR; must not exceed the speed of the
0 to 1 Gbps
Access Port.
If Port Shaping is Enabled: PIR must be less than or
equal to the Access Port Shaped Speed.
N2A Policer CBS Defines the N2A Policer Committed Burst Size (CBS)
for this port, in Kilobytes. The minimum N2A Policer
CBS entry allowed is based on the N2A Policer CIR
0 to 1,024 (KB)
entry, see Table 48. For IP type traffic, see Table 49 for
range.
N2A Policer EBS Defines the N2A Policer Excess Burst Size (EBS) for
this port, in Kilobytes. The minimum N2A Policer EBS
entry allowed is based on the N2A Policer EIR entry,
0 to 1,024 (KB)
see Table 48. For IP type traffic, see Table 49 for
range.
N2A Policer Color Specifies the N2A Policer Color Mode as 'Color Aware' Color Aware
Marking or 'Color Blind'. Color Blind

Parameter
N2A Policer Color Specifies the N2A Policer Coupling Flag. When Enabled
Coupling Flag coupling is enabled, tokens that would normally be Disabled
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-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 of frames declared ˜yellow” to be bounded by
CIR + EIR.

delivered/received 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 a provisioned
EIR of 0 allows for a single rate three color marking
(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.

Parameter
VLAN Members Defines the frames that belong to the flow. Frames are VLAN ID portion of
(Regular EVC only) classified based on the VLAN tag and the membership VLAN ID-Priority:
is specified as a list of VLAN IDs. The VLAN member
format is VLAN ID-*, VLAN ID (range)-* or *-Priority. 0 to 4095, or *
The valid values for VLAN ID are 0 to 4095. Valid Priority portion of
values for Priority are * or 0 to 7. A VLAN ID range is a VLAN ID-Priority:
contiguous block of VID values delineated by a first
member and a last member, inclusive (e.g., Range 100 0 to 7, or *
- 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 value on left and larger
value on the right. Up to 16 VLAN ID range entries are
allowed per flow. 2 VLAN ID range entries are allowed
per flow on average.
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.
Regarding the use of the “wildcard” value * - The

normal designation 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 taking precedence; *-Y members cannot coexist
with X-* members.
To add a VLAN member, enter the valid VLAN

ID-Priority number and select Add. To delete a VLAN
member, select the VLAN ID-Priority number and select
Delete. If EVC Type is set to Default EVC, no VLAN
Member value can be supplied, and 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. If EVC Type is set to Regular EVC, then individual
VLAN Members can be entered.
Add Forwarding Table Entry

Parameter
Destination Add a specified static destination MAC address to the (blank)
Address Forwarding table for this flow.
Destination Port Select the destination port where the input Destination Access Interface
Address is learned. of this flow
Network Interface
of this flow
Learning Action Select the action to take when this Destination Address Block
is learned. If set to Block, the learned address will be Forward
discarded and this flow will block the learning of this
MAC address again; if set to Forward, this flow will
forward this learned Destination Address.
Table 48: Minimum CBS / EBS Entry - Depending on CIR / EIR Range
Minimum
CIR / EIR Range
CBS / EBS Value
0 bps 0 KB
1 - 65,536,000 bps 1 KB
65,536,001 - 131,072,000 bps 2 KB
131,072,001 - 196,608,000 bps 3 KB

196,608,001 - 262,144,000 bps 4 KB
262,144,001 - 327,680,000 bps 5 KB
327,680,001 - 393,216,000 bps 6 KB
393,216,001 - 458,752,000 bps 7 KB
458,752,001 - 524,288,000 bps 8 KB
524,288,001 - 589,824,000 bps 9 KB
589,824,001 - 655,360,000 bps 10 KB
655,360,001 - 720,896,000 bps 11 KB
720,896,001 - 786,432,000 bps 12 KB
786,432,001 - 851,968,000 bps 13 KB
851,968,001 - 917,504,000 bps 14 KB
917,504,001 - 983,040,000 bps 15 KB
983,040,001 - 1,000,000,000 bps 16 KB
Table 49: Recommended CBS / EBS Entry - Depending on CIR / EIR

Range
Recommended
CIR / EIR Range
CBS / EBS Value
0 bps 0 KB
1 - 960,000 bps 16 KB
960,001 - 9,984,000 bps 32 KB
9,984,001 - 99,968,000 bps 64 KB

Table 49: Recommended CBS / EBS Entry - Depending on CIR / EIR

Range
Recommended
CIR / EIR Range
CBS / EBS Value
99,968,001 - 249,984,000 bps 128 KB
249,984,001 - 499,968,000 bps 256 KB
499,968,001 - 749,952,000 bps 512 KB
749,952,001 - 1,000,000,000 bps 1024 KB
Default Priority Mapping Tables

Table 50 and Table 51 and identify the default Priority Mapping Tables for
802.1P, IP-TOS and IP-DSCP. TOS/DSCP will only be used for classification if
there are no tags (valid or invalid ethertype) on the frame.
Table 50: 8021P or IP-TOS Default Priority Mapping Table

Index X-Tag PRIO Control New X-Tag Priority Bits Policer COS
0 None N/A 0
1 None N/A 1
2 None N/A 2
3 None N/A 3
4 None N/A 4
5 None N/A 5
6 None N/A 6
7 None N/A 7
Table 51: IP-DSCP Default Priority Mapping Table

Index X-Tag PRIO Control New X-Tag Priority Bits Policer COS
0-7 None N/A 0
8 - 15 None N/A 1
16 - 23 None N/A 2
24 - 31 None N/A 3
32 - 39 None N/A 4
40 - 47 None N/A 5
48 - 55 None N/A 6
56 - 63 None N/A 7

Management Tunnel Configuration Options and Rules

Refer to the following table for management tunnel configuration settings and
associated rules. One management tunnel per traffic interface is supported. Up
to two management tunnels are supported at one time. By default, each Access,
Network or LAG Port is provisioned without a management tunnel. Default set-
tings are identified in bold in the following table. Management Tunnels are cre-
ated by expanding the Communications and Management Tunnel entities and
entering a right click on the NE-1 entity and selecting Create Tunnel. An existing
Management Tunnel entity may be edited by expanding the Management Tun-
nels and NE-1 entities, and entering a right click on the desired Management
Tunnel and selecting Edit Configuration.
To delete an existing management tunnel, enter a right click on the desired
management tunnel and select Delete and then select OK. A Management Tun-
nel 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:
• When no LAG group is established, all Network ports and all Access ports
are available for creating management tunnels.
• 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.
Table 52: Management Tunnel Configuration Settings

Parameter
Management Tunnel Configuration Settings
Management Management Tunnel Index. Unique number associated
Tunnel Index with this management tunnel entity.
1-255
(Create
Tunnel only)
Management Specifies a unique name associated with the
Tunnel Name Management Tunnel entity. This is a mandatory text
(Create string entry with a maximum length of 15 characters.
up to 15 characters
Tunnel only) Note 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
management tunnels.

Table 52: Management Tunnel Configuration Settings (Continued)

Parameter
Associated The associated ports as well as the LAG assigned as the
Port management tunnel. Up to two management tunnels can
(Create be created for the system, either port-based or
Tunnel only) lag-based.
• The associated ports for GE112 include the follow-
ing possible combinations:
o Network Port-1-1-1-1 plus two Access ports
o Network Port-1-1-1-1 plus three Access ports (if
Network Port 2 is switched)
(available ports are
o Network Port-1-1-1-1 plus one LAG
populated in
o Two LAGs
drop-down list)
• The associated ports for GE114x include the follow-
ing possible combinations:
o
Network Port-1-1-1-1 plus two LAGs
o
Network Port-1-1-1-1 plus four Access Ports
o
Network Port-1-1-1-1 plus five Access ports (if
Network Port 2 is switched)
o
Network Port-1-1-1-1, two Access ports and one
LAG
o
3 LAGs
Encapsulation User setting for Ethernet or PPP Encapsulation. PPP Ethernet
Type can only be used for directly connected ADVA Optical
Networking NIDs. Not available if Management Traffic PPP
Bridging is Enabled.
IP Mode Select the desired IP mode setting for DCN port. IPv4 Only
IPv6 Only
IPv4 and IPv6
DHCP Defines whether Dynamic Host Configuration Protocol is Disabled
enabled or disabled. If this interface is set to Enabled,
the GE11x sends a broadcast query requesting IP
address information from a DHCP server. This option
also enables or disables the DHCP Client “Role.” For
Enabled
management tunnels, a separate DHCP Role attribute is
not supported since only DHCP Client is allowed. Not
applicable if Encapsulation is PPP or if Management
Traffic Bridging is Enabled.
DHCP Client Enable or Disable transmitting DHCP Client ID (DHCP Disabled
ID Control Option 61) if configured in DHCP request to the DHCP
server. Not applicable if Encapsulation is PPP or if Enabled
Management Traffic Bridging is Enabled.


Parameter
DHCP Client Select a desired DHCP Client ID type when DHCP Client MAC Address
ID Type ID Control is Enabled. If MAC Address is selected, the System Name
Associate Port’s MAC Address will be used as DHCP
Client ID automatically; if System Name is selected, the
System Name shown in System Detail Pane will be used
as DHCP Client ID; if User Defined is selected, user is User Defined
allowed to enter a customized name as the DHCP Client
ID.
DHCP Client This option shows or allows the entry of DHCP Client ID.
ID If DHCP Client ID Type is MAC Address or System (Default as associated
Name, this option is not editable, as a value port’s MAC address or
corresponding to the selected Client ID Type will be used System Name,
automatically; if DHCP Client ID Type is User Defined, dependent of last
user is allowed to enter a customized string up to 254 operation)
characters.
DHCP Class Enable or Disable transmitting DHCP Class ID (DHCP Enabled
ID Control Option 60) if configured in DHCP request to the DHCP
server. The Class ID is a non-user definable string. The
format is like: <vendor fixed string><space><inventory
product name>
Disabled
e.g: “ADVA FSP150CC-GE112” for the GE112, with the
same format used for other products. Not applicable if
Encapsulation is PPP or if Management Traffic Bridging
is Enabled.
DHCP Host Enable or Disable transmitting DHCP Host Name (DHCP Enabled
Name Control Option 12) if configured in DHCP request to the DHCP
server.Not applicable if Encapsulation is PPP or if Disabled
DHCP Host Select a desired DHCP Host Name Type when DHCP System Name
Name Type Host Name Control is enabled. If System Name is
selected, the System Name shown in gray (same as the
System Name in System Detail Pane) will be used as the
DHCP Host Name; if User Defined is selected, use is User Defined
allowed to enter a customized name as the DHCP Host
Name.
DHCP Host This option shows or allows the entry of DHCP Host FSP150CC-GE11x
Name Name. If DHCP Host Name Type is System Name, this
option is not editable, as the System Name will be used
automatically; if DHCP Host Name Type is User Defined, User-defined string
user is allowed to enter a customized string up to 254
characters.
DHCP Log Enable or Disable receiving the DHCP Log Server Disabled
Server (DHCP Option 7) list sent by the DHCP server. Not
Control applicable if Encapsulation is PPP or if Management Enabled


Parameter
DHCP NTP Enable or Disable receiving the DHCP NTP Server Disabled
Server (DHCP Option 42) list sent by the DHCP server. Not
Control applicable if Encapsulation is PPP or if Management Enabled
IP Address 1 IP Address for the management tunnel. Not applicable if
0.0.0.0
Subnet Mask Defines the subnet mask for the management tunnel.
Not applicable if Management Traffic Bridging is 255.255.255.0
Enabled.
Edit System Check box to permit the editing of the system default
Default gateway IP Address. Not applicable if Management (unselected)
Gateway Traffic Bridging is Enabled.
Gateway IP Entry for a valid IPv4 IP Address. Only applicable if the
Address Edit System Default Gateway checkbox is selected. Not (192.168.0.2)
applicable if Management Traffic Bridging is Enabled.
RIP V2 Allows setting/disabling of Routing Information Protocol Enabled
(RIP) V2 packets. If RIP is enabled on an interface and Disabled
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
system 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. Not applicable if
IPv6 Unicast Enter an IPv6 unicast address for the management 0000:0000:0000:0000:
Address tunnel interface. This option is only applicable when 0000:0000:0000:0000
DHCPv6 is disabled and DHCPv6 Role is Client. /0
Stateless When the NE is working in router mode (IPv6 Disabled
Address Auto Forwarding enabled), this option must be Disabled.
Configuration When the NE is working in host mode (IPv6 Forwarding Enabled
disabled), this option can be Enabled.
DHCPv6 Defines whether Dynamic Host Configuration Protocol Disabled
(DHCP) is enabled or disabled. If this interface is set to
Enabled and DHCP Role is set to DHCP Client, the
Enabled
GE11x sends a broadcast query requesting IPv6
address information from a DHCP server.
DHCPv6 Role Defines whether Dynamic Host Configuration Protocol DHCP Client
Role in IPv6 Network is as a server or a client. Servers
assign IP addresses, Clients receive addresses. This
option is only applicable if DHCP is set to Enabled. If the
DHCP Server
DHCP Role is set to DHCP Server, the user must
Disable and then Enable DHCPv6 for the initialization of
the server function (IP Address range) to take place.


Parameter
RIPng Allows setting/disabling of Routing Information Protocol Disabled
next generation (RIPng) packets. When RIPng is
enabled on an IPv6 interface, the interface receive the
IPv6 route entry on the link and update local route table.
Enabled
The interface also sends local learned IPv6 route entry
to the link via multicast
packets.
IPv6 RA Whether to Advertise prefix to link in router mode. Disabled
Prefix This is only applicable when IPv6 Forwarding is enabled
Enabled on System level. This option and Stateless Address Auto
Enabled
Configuration are mutually exclusive; they cannot be
both Enabled at the same time.
IPv6 RA The IPv6 Prefix to be dispatched to link in Router mode. 0000:0000:0000:0000:
Prefix 0000:0000:0000:0000
/0
Edit System Selecting the checkbox allows editing the Gateway IPv6
Default Address. (checkbox unselected)
Gateway
Gateway IPv6 Enter a Gateway IPv6 Address if the “Edit System
(grayed out)
Tunnel Mode Defines the management tunnel mode. I-Tag based VLAN Based
mode is not applicable to GE114S/GE114SH and is only MAC Based
supported on Network Port management tunnels. ITAG Based
C-Tag VLAN Enable or Disable C-Tag VLAN ID entry. This option is Enabled
not available when Tunnel Mode is set to MAC Based,
and cannot be enabled with S-Tag VLAN at the same Disabled
time when Tunnel Mode is set to ITAG Based.
C-Tag VLAN Define the C-Tag Management VLAN ID. It is used to
ID identify management traffic on the port. This option is 1 to 4095
only editable when C-Tag VLAN is enabled.
S-Tag VLAN Enable or Disable S-Tag VLAN ID entry. This option is Enabled
not available when Tunnel Mode is set to MAC Based
and cannot be enabled with C-Tag VLAN at the same Disabled
time when Tunnel Mode is set to ITAG Based.
S-Tag VLAN Define the S-Tag Management VLAN ID. It is used to
ID identify management traffic on the port. This option is 1 to 4095
only available when S-Tag Vlan is enabled.
I-Tag Enable or Disable I-Tag SID. This option is not Enabled
applicable to GE114S/GE114SH and is only supported
on Network Port management tunnels in ITAG Tunnel Disabled
Mode.
I-SID Define the I-Tag Service Instance Identifier (SID). It’s
used to identify management traffic. This option is only 256 to 16777214
available when I-Tag is enabled.


Parameter
Backbone Enable or Disable Backbone Destination MAC Address Disabled
Destination (BDA) in the management traffic on this interface.This
MAC option is only available to I-TAG Tunnel Mode.
When enabled, the user-provisioned BDA is used for
Enabled
NDP and for management packets; When disabled, the
backbone group MAC address is used for NDP and get
BDA from ARP response.
Backbone Define the Backbone Destination MAC Address for the
00:00:00:00:00:00
Destination I-Tag based management traffic. This option is only
(variable)
MAC Address applicable when Backbone Destination MAC is enabled.
CIR Committed Information Rate for the management tunnel.
Minimum setting is 0 bps, maximum setting is Network 256000
Port bandwidth. Default is 256000 bps.
EIR Excess Information Rate for the management tunnel.
Minimum setting is 0 bps, maximum is Network Port 768000
bandwidth. Default is 768000 bps.
Buffer Size Denotes the amount of memory in KB devoted to
buffering management tunnel packets. Minimum is 32, 32 - 33554
maximum is 33554. Default is 32.
COS Configurable Class Of Service (COS). Specifies the
Class of Service associated with the IP Management
Tunnel. This value is also used in the p-bits of the VLAN 0-7
based management tunnels (for both VLANs in the case
where S-TAG VLAN is enabled).
1. If 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 150CC reboot after changing the IP address. This will force RIP to advertise the address immedi-
ately. 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 over IPv4 Tunnel Configuration Options and

Rules
Refer to the following table for IPv6 over IPv4 tunnel configuration settings and
associated rules. One IPv6 over IPv4 tunnel is supported per system. But
default, no IPv6 over IPv4 management tunnel is provisioned in the system.
Default settings are identified in bold in the following table. An IPv6 over IPv4
tunnel is created by expanding the Communications and IPV6 over IPv4 Tun-
nels entities and entering a right click on the NE-1 entity and selecting Create
Tunnel. An existing IPv6 over IPv4 Tunnel may be edited by expanding the IPv6
over IPv4 Tunnels and NE-1 entities, and entering a right click on the IPv6 over
IPv4 Tunnel and selecting Edit Configuration.
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 can-
not 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 53: IPv6 over IPv4 Tunnel Configuration Settings

Parameter

Identification
IPv6 over IPv4 IPv6 over IPv4 Tunnel Index. Unique number associated
1
Tunnel Index with this tunnel entity.
Specifies a unique name associated with the IPv6 over
IPv4 Tunnel entity. This is a mandatory text string entry
with a maximum length of 15 alphanumeric characters.
IPv6 over IPv4 up to 15 characters
Note that it is not allowed to use system reserved names
Tunnel Name (blank)
(i.e. ltp, cfm, efm, elmi, erppdu, eth0, eth1,jdsu, lagpdu,
lldppdu, lo, ptpsyncjack, ptpts, sat, ssm, etc) to name an
IPv6 over IPv4 tunnel.
Select the Eid of the IPv4 Interface that this IPv6 over (dropdown list of
Associated IPv4 IPv4 Tunnel is created on, which could be DCN or available IPv4
Interface Management tunnel. management
interfaces)
Tunnel

Table 53: IPv6 over IPv4 Tunnel Configuration Settings (Continued)

Parameter
Select the mode of IPv6 over IPv4 tunnel: Configured
• Configured Tunnel: A manually configured tunnel is Auto 6o4
equivalent to a permanent link between two IPv6 IPv4 Compatible
domains over an IPv4 backbone. User specifies both
IPv4 source address and the destination address.
• IPv4 Compatible Tunnel: use IPv4-compatible IPv6
addresses as the format of source and destination
IPv6 address runs on tunnel. IPv4-compatible IPv6
addresses are IPv6 unicast addresses that have
zeros in the high-order 96 bits of the address, and an
IPv4 address in the low-order 32 bits. IP address for-
mat: ::A.B.C.D/96
Mode
• Auto 6to4 Tunnel: Use IPv4 address as one part of
IPv6 prefixes Source IPv6 address is generated by ISATAP
2002:A.B.C.D:SLA:eui-64/48, b.The destination IPv4
address is retrieved from destination IPv6 address
• ISATAT: ISATAP is an automatic overlay tunneling
mechanism that uses the underlying IPv4 network as
an NBMA link layer for IPv6. ISATAP is designed for
transporting IPv6 packets within a site where a
native IPv6 infrastructure is not yet available. IP
address format: Prefix: 0000:5EFE:A.B.C.D. The
ISATAT tunnel is not supported if IPv6 Forwarding is
enabled at the system level.
Tunnel Address
Destination IPv4 Specify the destination IPv4 address for Configured IPv6
0.0.0.0
Address over IPv4 tunnel.
IPv6 Unicast Enter the source IPv6 unicast address used to transmit 0000:0000:0000:00
Address IPv6 packets on tunnel. 00:0000:0000:0000:
0000/0
Potential Router Specify a router that can provide standard router
advertisement network configuration supported for
ISATAP tunnel, so that the other nodes one the end of
0.0.0.0
Tunnel can get prefix from this route. Once a router is
entered, clicking on Add to add it to the Potential Router
List.
Potential Router The list of potential routers. Selecting one router in the (default is a bank
List list and clicking Remove to delete a router. list)

CPD Filters Options and Rules

The following configuration options and rules apply to Access Ports and Flows.
Control Protocol Disposition (CPD) Filter settings are edited by entering a right
click on the entity and selecting Edit CPD Filters (see Table 54). Default settings
are identified in bold.
Table 55 summarizes the list of relevant Layer 2 control protocols and Cisco
proprietary protocols that are the subject of this feature.
Table 54: Control Data Protocol Configuration Options and Rules

Parameter
Tunnel MAC
A user-defined L2PT MAC Tunnel used for all tunneled
Tunnel MAC 01:00:0c:cd:cd:d0
protocols (BPDU, LLDP, CDP, VTP).
Control Protocol Disposition (Edit CPD Filters)
Sets Control Protocol Disposition (CPD) per Ethernet First Use Group Setting
Mile - Operations, Administration and Maintenance (sub-group settings
(EFM-OAM) protocol group or sub group for Port and Flow. only)
Discard
When set to Discard, the CPD frames are discarded and
counted in Etherjack PM parameters. When set to Pass

Thru, the CPD frames are transported transparently
through the system. Selecting Use Group Setting allows
Disposition sub group protocol settings to be provisioned by the Group
setting, e.g., if Bridge Group is set to Pass Thru and SSM is
set to Use Group Setting, then Group Setting is set to Pass Pass Thru
Thru.
Port CPD settings must be provisioned first, because

options available for Flows are determined upon Port CPD
settings (Protocols that have been set to Pass Thru at Port
are provisionable at Flow). Default is Pass Thru.

Table 55: Layer 2 Control Protocol Summary

Protocol Ethertype
Protocol Description MAC Address Notes
Group (Subtype)
By totally encapsulating the
original frame in a two-level
tagging scheme, ISL is
effectively a tunneling
protocol and has the
additional benefit of carrying
non-Ethernet frames. It adds
Inter Switch 01-00-0C-00-
ISL N/A a 26-byte header and 4-byte
Link (ISL) 00-00
Frame Check Sequence
(FCS) to the standard
Ethernet frame - the larger
Ethernet frames are expected
and handled by ports
configured to be trunks. ISL
supports 1024 VLANs.
PAgP is a management
protocol that will check for
parameter consistency at
Port either end of the link and
Aggregation 01-00-0C-CC assist the channel in adapting
PAgP 0x0104
Protocol -CC-CC to link failure or addition.
Cisco (PAgP) IEEE 802.3ad Link
Group Aggregation Control Protocol
(LACP) will likely supersede
PAgP in the long term.
Unidirection UDLD monitors physical
al Link 01-00-0C-CC cabling, shutting down
UDLD 0x0111
Detection -CC-CC miswired ports, protecting
(UDLD) against uni-directional links.
Cisco Proprietary Discovery
01-00-0C-CC
CDP Discovery 0x2000 Protocol
-CC-CC
Protocol
The VTP protocol
communicates between
switches using an Ethernet
destination multicast MAC
address (01-00-0c-cc-cc-cc)
VLAN
01-00-0C-CC and SNAP HDLC protocol
VTP Trunking 0x2003
-CC-CC type Ox2003. It does not work
(VTP)
over non-trunk ports (VTP is a
payload of ISL or 802.1Q), so
messages cannot be sent
until DTP has brought the
trunk online.

Table 55: Layer 2 Control Protocol Summary (Continued)

Protocol Ethertype
Group (Subtype)
DTP negotiates configuration
parameters between a switch
port and its neighbor. Trunks
extend VLANs between
devices by temporarily
identifying and tagging
Dynamic (link-local) the original
01-00-0C-CC
DTP Trunking 0x2004 Ethernet frames, thus
-CC-CC
(DTP) enabling them to be
multiplexed over a single link.
This also ensures the
separate VLAN broadcast
and security domains are
maintained between
switches.
In order to support the IEEE
802.1q standard, Cisco's
existing STP implementation
was extended to become
PVST+ by adding support for

tunneling across an IEEE
Cisco 802.1q mono Spanning Tree
Group region. PVST+ is therefore
(Cont.) Spanning compatible with both IEEE
01-00-0C-CC
PVSTP+ Tree 0x010b 802.1q's MST and Cisco
-CC-CD
PVSTP+ PVST protocols without
requiring extra commands or
configuration. In addition,
PVST+ adds verification
mechanisms to ensure that
there is no configuration
inconsistency of port trunking
and VLAN IDs across
switches.
UplinkFast provides fast STP
convergence after a direct link
failure in the network access
layer. It operates without
Uplink- STP 01-00-0C-CD
0x200a modifying STP, and its
Fast UplinkFast -CD-CD
purpose is to speed up
convergence time in a
specific circumstance to less
than three seconds.


Protocol Ethertype
Group (Subtype)
If there is a need to bridge
non-routable or legacy
protocols between VLANs
VLAN VLAN 01-00-0C-CD
0x010c without interfering with the
Bridge Bridge -CD-CE
IEEE Spanning Tree
Cisco instance(s) running on those
Group VLANs
(Cont.) Layer 2 protocol tunneling
Layer 2 allows Layer 2 protocol data
Protocol 01-00-0C-CD units (PDUs) (CDP, STP, and
L2PT N/A
Tunnelling -CD-D0 VTP) to be tunneled through
(L2PT) a network using a Cisco
proprietary multicast address.
Port Pause 01-80-C2-00- 0x8808 Port Pause Function
Pause
Function 00-01 (00-01)
EFM- EFM OAM Slow protocol
01-80-C2-00- 0x8809
OAM EFM OAM
00-02 (03)
(802.3ah)
Link Aggregation Control
Link
protocol. For Access Ports
LACP Aggregation 01-80-C2-00- 0x8809
being put in service with
(802.3ad) Control 00-02 (01)
Network Ports in LAG groups,
Protocol
this must be set to Discard.
LACP Marker protocol. For
LACP Access Ports being put in
Marker 01-80-C2-00- 0x8809
Marker service with Network Ports in
Protocol 00-02 (02)
(802.3ad) LAG groups, this must be set
Bridge to Discard.
Group Sync 01-80-C2-00- 0x8809 Port QL Function
SSM
Messaging 00-02 (0A)
Port Port Based Port Authentication Protocol
Authentic Network 01-80-C2-00-
0x888E
ation Access 00-03
(802.1x) Control
Rapid N/A - DSAP 42 SSAP 42
Reconfigura
BPDU tion of
(802.1w) Spanning
Tree
(RSTP) 01-80-C2-00-
N/A
00-00
IEEE
BPDU
Spanning
(802.1d)
Tree 802.1d
BPDU Multiple
(802.1s) STP


Protocol Ethertype
Group (Subtype)
01-80-C2-00- Reserved for use by 802.1.
Bridge 00-04 IEEE-802.1D states that a
Bridge Bridge
Group through N/A bridge will never forward a
Reserved Reserved
(Cont.) 01-80-C2-00- frame with one of these
00-0F addresses.
802.1d LAN Bridge All LANs Bridge Management
LAN 01-80-C2-00-
(LAN Manage- N/A
Bridges 00-10
Bridge) ment
GARP Multicast Registration
Multicast 01-80-C2-00- Protocol
GMRP N/A
Registration 00-20
Protocol
GARP VLAN Registration Protocol
VLAN 01-80-C2-00-
GARP GVRP N/A
Registration 00-21
Group
Protocol
01-80-C2-00-
00-22
GARP GARP through N/A
01-80-C2-00-
00-2F
LLDP Configuration Settings

Refer to the following table for Link Layer Discovery Protocol (LLDP) configura-
tion settings. The LLDP Configuration includes the system LLDP Configuration
and the physical Ethernet port settings. For details on LLDP provisioning, see
Provision Link Layer Discovery Protocol (LLDP) on p. 351.
Table 56: System LLDP Configuration Settings

Parameter
Transmission Define the transmission interval of LLDP frames. 5 - 3600 (sec)
Interval 30
Hold Time A multiplier of Transmission Interval used to compute 2 - 10
Multiplier the TTL value of LLDP frame. 4
Re-initialization The delay after Admin Status of port becomes 1 - 10 (sec)
Delay “Disabled” before re-initialization is attempted. 2
Notification The interval for SNMP Notification transmission. 5 - 3600 (sec)
Interval 30
Maximum Tx The maximum number of consecutive LLDPDUs that 1 - 10
Credit can be transmitted at any time. 5
Message Fast Tx Define the time interval in timer ticks between 1 - 3600
transmissions during fast transmission periods. 1


Parameter
Tx Fast Init The interval between successive LLDPDU 1-8
transmissions in fast transmission mode. 4
Maximum When the number of neighbors reaches the maximum Discard NEW
Neighbors Action allowed, the new neighbors will be discarded.
Table 57: Physical Ethernet Port LLDP Configuration Settings

Parameter
Admin Status The admin status for port LLDP. Once Disabled, the Disabled
port will not be able to transmit or receive LLDP TX-ONLY
frames. RX-ONLY
TX-AND-RX
SNMP Enable or Disable SNMP notification when the Disabled
Notification following conditions happen: Remote Table Inserts, Enabled
Remote Table Deletes, Remote Table Drops, Remote
Table Ageouts.
Basic Optional The basic optional TLVs to be transmitted in the LLDP Port Description
TLVs frames from this port. Select/Unselect the checkboxes System Name
to change the settings. System Description
System
Capabilities
Management Select an interface as the LLDP management DCN-1-1-1-1
Interface interface for this port. Up to two management management
interfaces (DCN interface and the management tunnel tunnel
on this port) are allowed, and up to six management
addresses are allowed if IPv4 and IPv6 mode are both
enabled for the two management interfaces.
Control Enable or Disable the transmission of management Disabled
interface in LLDP frames. Enabled
Loopback Settings
Refer to Table 58 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:
Table 58: Loopback Settings

Parameter
Administrative Defines the Access or Network facility administrative IS
State state.The administrative state controls the generation of Management
Service state, it is fully operational. The Administrative State
Disabled
must be set to Maintenance prior to initiating a loopback or
an Etherjack Diagnostic. For more information on Unassigned
p. 599. Disabled state is only applicable to Access Ports.
Loopback Allows you to set the Loopback State for a Network or None
Configuration Access port. Allows constant or timed loopback of terminal EFM-OAM Remote
or up to three individual VLAN flows. The interface must be EFM-OAM Remote
in the assigned state and the Administrative State must be Timed
set to Testing prior to initiating a loopback. To activate a
Facility Port
VLAN loopback, at least one VLAN ID must be selected in
order to activate the VLAN loopback. Facility Port Timed
Facility VLAN
The port EFM-OAM State must be set to Enabled prior to Terminal Port
setting EFM-OAM Remote or EFM-Remote Timed Terminal Port
loopbacks or the selection will be denied. When activating a Timed
Remote EFM-OAM loopback, the loopback includes Terminal VLAN
management traffic, therefore management traffic is
dropped while the EFM-OAM loopback is active. Since all
EFM-OAM frames are still processed, when the Remote
EFM-OAM loopback is released, management connectivity
will also be restored.
When using eVision “None” is used to remove a loopback.
When CCM defect is used as a trigger for protection

switching, performing a loopback on port can cause
undesired protection switching.
JDSU Enable or Disable the GE11x to receive or react to JDSU Disabled
Loopback loopback control messages.
Control In a typical deployment scenario, a port or VLAN terminal
loopback should be established at one end of the service on Enabled
the port connected to CPE device. This port can be an
Access Port or Network Port in GE11x product.

Table 58: Loopback Settings (Continued)

Parameter
First of three Virtual LAN Identifiers available for loopback.
The format is VLAN ID-Priority. Up to three Inner and Outer
VLAN loopbacks may be created per entity. Only applicable
if Terminal VLAN or Facility VLAN is selected. To activate (0 to 4095)-
Inner and
the VLAN ID, the check box must be selected. At least one (0 to 7 or *)
Outer
Inner and Outer VLAN ID must be selected in order to (4094-0 if Terminal
VLAN ID 1
activate the VLAN loopback. Default VLAN ID is the same or Facility VLAN is
as the last VLAN ID used for the entity. Only one VLAN selected)
loopback may be performed per system. Once a VLAN
loopback has been operated, a second VLAN loopback may
not be performed on another entity.
(See above.) (0 to 4095)-
Inner and
Second of three Inner and Outer Virtual LAN Identifiers (0 to 7 or *)
Outer VLAN
available for loopback. (4094-1 if Terminal
ID 2
or Facility VLAN is
selected)
(See above.) (0 to 4095)-
Inner and
Last of three Virtual LAN Identifiers available for loopback. (0 to 7 or *)
Outer VLAN
(4094-2 if Terminal
ID 3
or Facility VLAN is
selected)
Allows swapping the Source Address (SA) and Destination None
Addresses (DA) or Swap DA Overrides SA for loopback Swap SADA
testing. Swap DA Overrides
SA
Swap SADA operation will swap the Source Address and
Destination MAC addresses for looped-back frames. Swap
DA Overrides SA operation will swap DA=SA, SA=Local
Address (LA) (loop-point address), whereby the Destination
Swap SADA
Address is swapped with the Source address and the
Source Address is swapped with the Local Address.
This option is available when in Maintenance View by

selecting Loopbacks. Only one Swap loopback operation
may be performed per system. Once a Swap loopback has
been operated, a second Swap loopback may not be
performed on another entity.
Specifies the amount of time the loopback is to be applied to
10 to 300 (seconds)
Timer a Terminal Port Timed or Facility Port Timed loopback. The
10
loopback is released when the preset time has expired.

Environmental Alarms Settings - GE114H/GE114PH

Refer to the following table for Environmental Alarms option settings. To set
Environmental Alarms options, select Maintenance view, enter a right click on
the desired Environmental Alarm entity in the Selection Tree and select Edit.
The following loopback provisioning options and rules are described for each
option setting available. Default settings are identified in bold.
Table 59: Environmental Alarms Settings

Parameter
Alarm Type Defines the Alarm Type associated with the Alarm Input. Miscellaneous
Battery Discharging
Battery Failure
Cooling Fan Failure
Engine Failure
Fuse Failure
High Temperature
Intrusion
Low Battery
Voltage
Low Temperature
Open Door
Commercial Power
Failure
Notification Defines the Notification Code associated with the Alarm CR
Code Input. MJ
MN
NA
NR
Alarm Input The dry contact alarm inputs are programmable to specify Disabled
Mode whether the alarm shall be raised on contact close or open, Alarm on Open
or disabled. Alarm on Closed
Alarm Hold Enables or disables Alarm Hold Off. Disabled
Off Enabled
Alarm Specifies a description for the associated Alarm Input.
blank
Description
Performance Monitoring Settings

Refer to the following tables for Performance Monitoring (PM) Threshold Cross-
ing Alert (TCA) monitored types and associated default settings:
• Ethernet Network Port Monitored Types on p. 718

• Ethernet Access Port Monitored Types on p. 723

• Ethernet Access Port N2A and LAG A2N Shaper Monitored Types on p. 728
• Flow Monitored Types on p. 729
• Flow A2N Shaper Monitored Types on p. 732
• Flow Policer Monitored Types on p. 732
• ESA Monitored Types on p. 733
• Ethernet (Network/Access) Port PTP Flow Point Monitored Types on p. 739
• PTP MCI Monitored Types on p. 741
• PTP Remote Slave Monitored Types on p. 742
• SOOC Monitored Types on p. 743
• Ethernet (Network/Access) Port PTP Flow Point Monitored Types on p. 739
• PT Flow Shaper (QoS Queues) Monitored Types on p. 745
• PT Flow Policer Monitored Types on p. 745
For RADIUS, PM counters may be displayed and registers may be initialized.
RADIUS PM counts are only applicable where Remote Authentication

PS
Protocol is set to RADIUS.
Note
Refer to Etherjack Test Procedures and Performance Monitoring on p. 459 for

procedures on viewing, editing and initializing PMs using eVision.
Ethernet Network Port Monitored Types

The following performance parameters are related to an Ethernet Network port.
When 1+1 protection is provisioned, each Network port will be monitored for its
performance parameters and will be managed independently from the other.
Table 60: Ethernet Network Port Monitored Types and Default TCA Settings
Monitored Loca- 15
Description Direction 1 Day
Type tion Min.
ABR-RX Average Bit Rate Received. The average Receive Near 0 0
bit rate received over the specific interval End
in the ingress direction. If there is link
down during the interval, the bin is not
accessible. This counter is based on
RMON etherStatsOctets.
ABR-TX Average Bit Rate Transmitted. The Receive Near 0 0
average bit rate transmitted over a specific End
interval in the egress direction, based on
Bytes Sent. If there is link down during the
interval, the bin is not accessible.

Table 60: Ethernet Network Port Monitored Types and Default TCA Settings (Continued)
Monitored Loca- 15
Type tion Min.
ESBF EtherStats Broadcast Frames. The Receive Near 0 0
Broadcast Frames Sent in the egress End
direction If there is link down during the
ESBP EtherStats Broadcast Packets Received. Receive Near 0 0
The total number of good packets received End
that were directed to the broadcast
address. Note that this does not include
multicast packets.
ESBS EtherStats Bytes Sent. The Bytes Sent in Transmit Near 0 0
the egress direction If there is link down End
during the interval, the bin is not
accessible.
ESC EtherStats Collisions. The best estimate of Receive Near 0 0
the total number of collisions on this End
Ethernet segment. The value returned will
depend on the location of the RMON
probe. Section 8.2.1.3 (10BASE-5) and
section 10.3.1.3 (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.
ESCAE EtherStats CRC (Cyclic Redundancy Receive Near 37055 3557280
Check) Aligned Errors. The total number End
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).
ESDE EtherStats Drop Events. The total number Receive Near 37055 3557280
of events in which packets were dropped End
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 condition has been detected.

Monitored Loca- 15
Type tion Min.
ESF EtherStats Fragments. The total number Receive Near 37055 3557280
of packets received that were less than 64 End
octets in length (excluding 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.
ESFS EtherStats Frames Sent. The Frames Transmit Near 0 0
Sent in the egress direction If there is link End
down during the interval, the bin is not
accessible.
ESJ EtherStats Jabbers. The total number of Receive Near 0 0
packets received that were longer than End
1518 octets (excluding 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 this definition of jabber is
different than the definition in IEEE-802.3
section 8.2.1.5 (10BASE5) and section
10.3.1.4 (10BASE2). These documents
define jabber as the condition where any
packet exceeds 20 ms. The allowed range
to detect jabber is between 20 ms and 150
ms.
ESMF EtherStats Multicast Frames. The Receive Near 0 0
Multicast Frames Sent in the egress End
direction If there is link down during the
ESMP EtherStats Multicast Packets Received. Receive Near 0 0
EtherStats Multicast Packets Received. End
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.
ESO EtherStats Octets Received. The total Receive Near 0 0
number of octets of data (including those End
in bad packets) received on the network
(excluding framing bits but including FCS
octets).

Monitored Loca- 15
Type tion Min.
ESOF EtherStats Oversize Frames. The total Transmit Near 0 0
number of frames received that were End
oversized.
ESOP EtherStats Oversize Packets. The total Receive Near 37055 3557280
number of packets received that were End
longer than 1518 octets (excluding framing
bits, but including FCS octets) and were
otherwise well formed.
ESP EtherStats Packets Received. EtherStats Receive Near 0 0
Packets Received. The total number of End
packets (including bad packets, broadcast
packets, and multicast packets) received.
ESP64 EtherStats Packets - 0 to 64 Octets Receive Near 0 0
Frames. The total number of packets End
(including bad packets) received that were
64 octets in length (excluding framing bits
but including FCS octets).

between 65 and 127 octets in length
inclusive (excluding framing bits but
including FCS octets).
ESP256 EtherStats Packets - 256 to 511 Octet Receive Near 0 0
Packets. The total number of packets End

Monitored Loca- 15
Type tion Min.
ESUF EtherStats Unicast Frames. The Unicast Transmit Near 0 0
Frames Sent in the egress direction If End
there is link down during the interval, the
bin is not accessible.
ESUP EtherStats Undersize Packets. The total Receive Near 37055 3557280
number of packets received that were less End
than 64 octets long (excluding framing
L2CPFD Layer 2 Control Protocol Frames Receive Near 0 0
Discarded. Number of Layer 2 Control End
Protocol Frames discarded on the
interface.
L2PTFE Number of received Layer 2 Protocol Receive Near 0 0
Tunneling Frames Encapsulated. End
L2PTFD Number of transmitted Layer 2 Protocol Transmit Near 0 0
Tunneling Frames Decapsulated. End
LES Line Errored Seconds. Increments if a Receive Near 0 0
False Carrier or Errored Symbol event End
occurs since the last 1 second poll.
OPR Optical Power Received (dBm) Receive Near -80 -80
End
OPR-VAR Optical Power Received Variance (+/- Receive Near 4 4
dBm) represents the variance from the End
configured OPR 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.
OPT Optical Power Transmit (dBm) Transmit Near -80 -80
End
OPT-VAR Optical Power Transmit Variance (+/- Transmit Near 4 4
dBm) represents the variance from the End
configured OPR thresholds where the
measured value will not result in the
generation of a TCA. For example: with an
OPR threshold of -80 and an OPT-VAR of
4, no TCA is generated if the measured
OPT is -76 to -84.

Monitored Loca- 15
Type tion Min.
PSC Protection Switch Count Receive Near 0 0
End
TEMP1 Temperature for the physical layer None Near 0 0
(expressed in Celsius). Applicable only if End
the media type is Fiber.
UAS Unavailable Seconds - counted if one or Receive Near 10 10
more of following exists in that second: End
Link down, link deactivated (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 connect defect
(unexpected MD level or MAID Mismatch),
Error CCM Defect (Unexpected MEP or
unexpected period), RMEP CCM Defect
(Loss of Connectivity), and RDI Defect
(unidirectional failure makes the port
based service unavailable).
1. Valid only when the port is configured to use the fiber interfaces.
Ethernet Access Port Monitored Types

The following performance parameters are related to an Ethernet Access port.
The optical, physical layer parameters are only valid when the port is configured
to use the fiber interfaces.
Note that when the Access port is configured in EPL mode, a single service
(Flow) is also configured which has counters associated with it (A2N Shaper,
N2A Shaper, A2N Policer and N2A Policer).
Table 61: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored Loca- 15
Type tion Min.
ABR-RX Average Bit Rate Received. The average Receive Near 0 0
bit rate received over the specific interval in End
the ingress direction. This counter is based
on RMON etherStatsOctets.
ABR-TX Average Bit Rate Transmitted. The average Transmit Near 0 0
bit rate transmitted over a specific interval End
in the egress direction, based on Bytes
Sent.
APFD AFP Priority-tagged Frames Dropped. Receive Near 0 0
Priority-tagged frames dropped due to AFP End
setting. AFP Priority-tagged Frames
Dropped. Priority-tagged frames dropped
due to AFP setting.

Table 61: Ethernet Access Port Monitored Types and Default TCA Settings (Continued)
Monitored Loca- 15
Type tion Min.
AUFD AFP Untagged Frames Dropped. Untagged Receive Near 0 0
frames dropped due to AFP setting. End
ESBF EtherStats Broadcast Frames. If there is Receive Near 0 0
link down during the interval, the bin is not End
accessible.
ESBP EtherStats Broadcast Packets Received (in Receive Near 0 0
the A2N direction). The total number of End
good packets received that were directed to
the broadcast address. Note that this does
not include multicast packets.
ESBS EtherStats Bytes Sent. Transmit Near 0 0
End
ESC EtherStats Collisions. The best estimate of Receive Near 0 0
the total number of collisions on this End
Ethernet segment. The value returned will
depend on the location of the RMON probe.
Section 8.2.1.3 (10BASE-5) and section
10.3.1.3 (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.
ESCAE EtherStats CRC (Cyclic Redundancy Receive Near 37055 3557280
Check) Aligned Errors. The total number of End
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).
ESDE EtherStats Drop Events. The total number Receive Near 37055 3557280
of events in which packets were dropped End
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 condition has been detected.

Monitored Loca- 15
Type tion Min.
ESF EtherStats Fragments. The total number of Receive Near 37055 3557280
packets received that were less than 64 End
octets in length (excluding framing bits but
including FCS octets) and had either a bad
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.
ESFS EtherStats Frames Sent. The Frames Sent Transmit Near 0 0
in the egress direction. End
ESJ EtherStats Jabbers. The total number of Receive Near 0 0
packets received that were longer than End
1518 octets (excluding framing bits, but
including FCS octets), and had either a bad

octets (Alignment Error).
Note that this definition of jabber is different
than the definition in IEEE-802.3 section
8.2.1.5 (10BASE5) and section 10.3.1.4
(10BASE2). These documents define
jabber as the condition where any packet
exceeds 20 ms. The allowed range to
detect jabber is between 20 ms and 150
ms.
ESMF EtherStats Multicast Frames. The Multicast Receive Near 0 0
Frames Sent in the egress direction. End
ESMP EtherStats Multicast Packets Received. Receive Near 0 0
EtherStats Multicast Packets Received. End
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.
ESO EtherStats Octets Received. The total Receive Near 0 0
number of octets of data (including those in End
bad packets) received on the network
(excluding framing bits but including FCS
octets).
ESOF EtherStats Oversize Frames. The total Transmit Near 0 0
number of frames transmitted that were End
oversized.

Monitored Loca- 15
Type tion Min.
ESOP EtherStats Oversize Packets. The total Receive Near 37055 3557280
number of packets received that were End
longer than 1518 octets (excluding framing
ESP EtherStats Packets Received. The total Receive Near 0 0
number of packets (including bad packets, End
broadcast packets, and multicast packets)
received.
64 octets in length (excluding framing bits
but including FCS octets).
ESP256 EtherStats Packets - 256 to 511 Octet Receive Near 0 0
Packets. The total number of packets End

Monitored Loca- 15
Type tion Min.
ESUF EtherStats Unicast Frames sent. If there is Transmit Near 0 0
link down during the interval, the bin is not End
accessible.
ESUP EtherStats Undersize Packets received. Receive Near 37055 3557280
The total number of packets received that End
were less than 64 octets long (excluding
framing bits, but including FCS octets) and
were otherwise well formed.
L2CPFD Layer 2 Control Protocol Frames Receive Near 0 0
Discarded. Number of Layer 2 Control End
interface.
L2CPFP Layer 2 Control Protocol Frames Receive Near 0 0
Processed. Number of Layer 2 Control End

Protocol Frames processed on the
interface.
L2PTFE Number of received Layer 2 Protocol Receive Near 0 0
Tunneling Frames Encapsulated. End
L2PTFD Number of transmitted Layer 2 Protocol Transmit Near 0 0
Tunneling Frames Decapsulated. End
LBC1 Laser Bias Current retrieved from the SFP. Receive Near 0 0
Applicable only if the media type is Fiber. End
LES Line Errored Seconds detected. Increments Receive Near 0 0
if a False Carrier or Errored Symbol event End
occurs since the last 1 second poll.

Monitored Loca- 15
Type tion Min.
TEMP1 Temperature for the physical layer None Near 0 0
(expressed in Celsius). Applicable only if End
the media type is Fiber.
UAS2 Unavailable Seconds. Used by Receive Near 0 0
Network/Service Management Systems to End
compute port-based service un-availability.
Counted if one or more of following exists in
that second:
• Link down
• link deactivated (triggered by LLF)
• SFP faults
• EFM-OAM discovery failure
• EFM-OAM loopback.
Also, any one of the following port based
MEP conditions:
• Port-based cross-connect defect
(unexpected MD level or MAID Mis-
match/Mismerge)
• Port-based MEP Error CCM Defect
(Unexpected MEP or unexpected
period)
• Port-based MEP RMEP CCM Defect
(Loss of Connectivity)
• Port-based MEP RDI Defect (unidirec-
tional failure makes the port based ser-
vice unavailable)
1. Valid only when the port is configured to use the fiber interfaces.
2. Any second that is deemed UAS for the port will also be UAS for all the EVCs on that port.
Ethernet Access Port N2A and LAG A2N Shaper

Monitored Types
The following performance parameters are for each of the QoS queues which
are supported for an Ethernet Access port or LAG. (These queues are shared
by all FLOWs provisioned for this port.)
Table 62: Ethernet Access Port/LAG QoS Queues Monitored Types and Default TCA Settings
Monitored 15 1
Definition Direction Location
Type Min. Day
ABRRL Average Bit Rate - Rate Limited for QoS Receive Near End 0 0
queue n1
BREDD Bytes Random Early Discard Dropped Transmit Near End 0 0

Table 62: Ethernet Access Port/LAG QoS Queues Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
BT Bytes Transmitted by QoS queue n1 Receive Near End 0 0
BTD Bytes Tail Dropped from this QoS queue Receive Near End 0 0
n1 (in the N2A direction)
FD Frames Dequeued by QoS queue n1 Receive Near End 0 0
FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
FTD Frames Tail Dropped by QoS queue n 1 Receive Near End 0 0
1. There can be up to 8 QoS queues, where n is 0 through 7.
Flow Monitored Types

The following performance parameters are related to the Flow as a whole. As
noted in the table, many are an aggregation of the various Policer or Shaper
counts.
Table 63: Flow Monitored Types and Default TCA Settings

Monitored 15 1
Type Min. Day
ABRA2N Average Bit Rate (in the A2N Receive Near End 0 0
direction). This parameter is an
aggregation of up to 81 A2N bytes
received policer counts.
ABRN2A Average Bit Rate (in the N2A Transmit Near End 0 0
direction). This parameter is an
aggregation of up to 81 N2A bytes
transmitted policer counts.
ABRRLA2N Average Bit Rate - Rate Limited (in the Receive Near End 0 0
A2N direction). This parameter is an
aggregation of up to 81 A2N bytes
received QoS queue counts.
ABRRLN2A Average Bit Rate - Rate Limited (in the Transmit Near End 0 0
N2A direction). This parameter is an
aggregation of up to 81 N2A bytes
transmitted QoS queue counts.
BA2N Total Bytes In (in the A2N direction). Receive Near End 0 0
This parameter is an aggregation of up
to 8 A2N BytesIn policer counts.
BN2A Total Bytes In (in the N2A direction). Transmit Near End 0 0
to 8 N2A BytesIn policer counts.
BOA2N Total Bytes Out (in the A2N direction). Receive Near End 0 0
to 8 A2N BytesOut policer counts.

Table 63: Flow Monitored Types and Default TCA Settings (Continued)
Monitored 15 1
Type Min. Day
BON2A Total Bytes Out (in the N2A direction). Transmit Near End 0 0
to 8 N2A BytesOut policer counts.
ES The number of Errored Seconds (ES) Receive Near End 0 0
on the flow.
FMGA2N Frames Marked Green and Passed (in Receive Near End 0 0
the A2N direction). This parameter is
an aggregation of up to 8 A2N Green
frames passed policer counts
FMGN2A Frames Marked Green and Passed (in Transmit Near End 0 0
the N2A direction). This parameter is
an aggregation of up to 8 N2A Green
frames passed policer counts.
FMRDA2N Frames Marked Red and Discarded Receive Near End 0 0
(in the A2N direction). This parameter
is an aggregation of up to 8 A2N Red
frames discarded policer counts.
FMRDN2A Frames Marked Red and Discarded Transmit Near End 0 0
(in the N2A direction). This parameter
is an aggregation of up to 8 N2A Red
frames discarded policer counts.
FMYA2N Frames Marked Yellow and Passed (in Receive Near End 0 0
the A2N direction). This parameter is
an aggregation of up to 8 A2N Yellow
FMYN2A Frames Marked Yellow and Passed (in Transmit Near End 0 0
the N2A direction). This parameter is
an aggregation of up to 8 N2A Yellow
FTDA2N Frames Tail Dropped (in the A2N Receive Near End 0 0
direction).
L2CPFD Layer 2 Control Protocol Frames Receive Near End 0 0
Discarded. Number of Layer 2 Control
interface.

Table 63: Flow Monitored Types and Default TCA Settings (Continued)
Monitored 15 1
Type Min. Day
SES Severely Errored Seconds: 1 second Receive Near End 0 0
period with 30% or more errored or
lost frames. (Note that 30% is a
configured value [user configurable].)
UAS Unavailable Seconds: Used by Receive Near End 0 0
Network/Service Management
Systems to compute port-based and
VLAN-based service availability. A
second is deemed unavailable for an
EVC if any one of the following
service-level defects is detected in that
second:
• VID-based MEP Cross-connect
Defect (Unexpected MD level or
MAID mismatch/Mismerge)
• VID-based MEP Error CCM
Defect (Unexpected MEP or unex-
pected period)
• VID-based MEP RMEP CCM

Defect (Loss of Connectivity)
• VID-based MEP RDI Defect (uni-
directional failure makes the port
based service unavailable)
• VID-based MEP MAC Status
Defect (for LAN Up MEPs)
• Threshold exceeded for frame
loss ratio
1. Up to 8 based on how many policers/queues are being used by the Flow

Flow A2N Shaper Monitored Types

The following performance parameters are for each of the QoS Shaper which
are supported for an Flow.
Table 64: Ethernet Network Port QoS Queues Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
ABRRL Average Bit Rate - Rate Limited for QoS Receive Near End 0 0
queue n1.
BT Bytes Transmitted by QoS queue n 1 Receive Near End 0 0
BTD Bytes Tail Dropped from this QoS queue Receive Near End 0 0
n1(in the N2A direction).
FD Frames Dequeued by QoS queue n1 Receive Near End 0 0
FREDD Frames Random Early Discard Dropped Transmit Near End 0 0
FTD Frames Tail Dropped by QoS queue n 1 Receive Near End 0 0
1. There can be up to 8 QoS shaper on each Network port, where n is 0 through 7.
Flow Policer Monitored Types
The following performance parameters are for each of the Policers which are
supported for a Flow. Policers exist for the A2N direction as well as the N2A
direction.
Table 65: Flow Policer Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
ABR Average Bit Rate - for Policer n1. Receive Near End 0 0
BYTESIN Number of bytes received by the Receive Near End 0 0
Policer.
BYTESOUT Number of bytes transmitted by the Receive Near End 0 0
Policer.
FMG Frames Marked Green and Passed for Receive Near End 0 0
Policer n.
FMRD Frames Marked Red and Discarded for Receive Near End 0 0
Policer n.
FMY Frames Marked Yellow and Passed for Receive Near End 0 0
Policer n.
1. There are at most 8 Policers for each direction, where n is 0 through 7.

ESA Monitored Types

ESA PM thresholds are viewed using eVision by selecting the ESA icon or
selecting ESA from the Applications menu, expanding the selection tree, select-
ing the Probe entity and then selecting the Thresholds tab. To edit PM thresh-
olds, enter a right click on the Probe entity and select Edit Thresholds. See the
following table for ESA monitored types and default TCA settings.
Table 66: ESA Monitored Types and Default TCA Settings
Default
Performance Parameter Definition
Threshold
AVG-RTDELAY The average round-trip delay (in microseconds) across
all packets received in the current interval. The 0
reflector's processing time is excluded from the value.
LOST-FRAMES Lost Frames 0
LOST-PKTS The total number of Lost Packets in the current
interval. Packets which are not received from the
reflector end beyond the configured timeout value are 0
termed as lost. NOTE: This is not applicable for
Y.1731 probes.
MAX-RTDELAY The maximum round-trip delay (in microseconds)
across all packets received in the current interval. The 0
MIN-RTDELAY The minimum round-trip delay (in microseconds)

across all packets received in the current interval. The 0
OUTOFSEQ-ERRS Out of Sequence Errors. The total number of out of
sequence errors across all packets received in the
current interval. If (Received Sequence Number) is
0
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.
P2R-AVGABSJITTER Probe to Reflector Average Absolute Jitter (µsec) 0
P2R-AVG-OWDELAY Probe to Reflector Average Oneway Delay. The
average one-way source to destination delay (in
0
microseconds) across all packets received in the
current interval.
P2R-DATA-FRAMES This attribute is only applicable to Y.1731 probes. This
is the number of data frames counted by the Source
MEP (Probe) that are transmitted towards the
Destination MEP (Reflector). Based on the 0
configuration the MEP counts the data frames with:
• MEP's LM TX priority or all the priorities
• All the VLAN IDs belonging the MEP's MA VID list
P2R-ERR-FRAMES Probe to Reflector Errored Frames 0

Table 66: ESA Monitored Types and Default TCA Settings (Continued)
Default
Threshold
P2R-ERR-PKTS Probe to Reflector Errored Packets. The total number
of Packets in the current interval, for which there was a
problem in transmission. This error is counted when
there is a failure in packet transmission due to
0
resource limitations (buffers). This can happen if the
Probe Configuration was changed to send in a large
number of packets in a time interval. NOTE: This is not
applicable for Y.1731 probes.
P2R-FRAMES Probe to Reflector Frames 0
P2R-LOST-FRAMES Probe to Reflector Lost Frames 0
P2R-LOST-PKTS The number of Lost Packets from probe to reflector in
the current interval. For Y.1731 probes, these are the 0
actual data frames lost.
P2R-MAXABSJITTER Probe to Reflector Maximum Absolute Jitter (µsec) 0
P2R-MAXNEGJITTER Probe to Reflector Maximum Negative Jitters. The
maximum negative one-way jitter from source to 0
destination in the current interval.
P2R-MAX-OWDELAY Probe to Reflector Maximum Oneway Delay. The
maximum one-way source to destination delay (in
0
current interval.
P2R-MAXPOSJITTER Probe to Reflector Maximum Positive Jitters. The
maximum positive one-way jitter from source to 0
P2R-MINABSJITTER Probe to Reflector Minimum Absolute Jitter (µsec) 0
P2R-MINNEGJITTER Probe to Reflector Minimum Negative Jitters. The
minimum negative one-way jitter from source to 0
P2R-MIN-OWDELAY Probe to Reflector Minimum Oneway Delay. The
minimum one-way source to destination delay (in
0
current interval.
P2R-MINPOSJITTER Probe to Reflector Minimum Positive Jitters. The
minimum positive one-way jitter from source to 0

Default
Threshold
P2R-NEG-LOSSES This attribute is only applicable to Y.1731 probes. This
is the number of occurrences of negative frame loss
from Source MEP (Probe) to Destination MEP
(Reflector). If these counts are non-zero, then there
could be some kind of provisioning mismatch between
the Probe MEP and Reflector MEP. Here are some
scenarios where this can happen:
• Probe MEP is configured to count in-profile frames
only and the Reflector MEP is configured to count
all frames with a mismatch in value for the attribute 0
cfmMepLmCount InProfileFrames.
• Probe MEP is configured to count data frames for
specific VLAN priority and the Reflector MEP is
configured to count data frames for all the priorities
with a mismatch in values for the attributes cfmMe-
pLmTx CountAllPrios or cfmMepLm RxCountAll-
Prios. NOTE: This could possibly happen due to
reasons not related to configuration, such as frame
reordering in the network.
P2R-NUMABSJITTER Probe to Reflector Number of Absolute Jitter (µsec) 0

P2R-NUMNEGJITTER Probe to Reflector Number of Negative Jitters. The
total number of negative one-way jitters from source to 0
P2R-NUMPOSJITTER Probe to Reflector Number of Positive Jitters. The total
number of positive one-way jitters from source to 0
P2R-PKTS Probe to Reflector Packets. The total number of
Transmitted Packets in the current interval. In the case
of Y.1731 probes, this reflects the number of DMRs 0
(Delay Measurement Replies) received and this will
always be the same as the esaProbeStatsR2PPkts.
P2R-SUMABSJITTER Probe to Reflector Sum of Absolute Jitter (µsec) 0
P2R-SUMNEGJITTER Probe to Reflector Sum of Negative Jitters. The total
sum of negative one-way jitters from source to 0
P2R-SUM-OWDELAY Probe to Reflector Sum of Oneway Delays. The total
sum of one-way delay from source to destination in the 0
current interval.
P2R-SUMPOSJITTER Probe to Reflector Sum of Positive Jitters. The total
sum of positive one-way jitters from source to 0
P2R-SUMSQABSJITTER Probe to Reflector Sum of Square of Absolute Jitter
0
(µsec)
P2R-SUMSQNEGJITTER Probe to Reflector Sum of Square of Negative Jitters.
The sum of square of negative one-way jitters from 0
source to destination in the current interval.

Default
Threshold
P2R-SUM-SQ-OWDELAY Probe to Reflector Sum of Square of Oneway Delays.
The sum of square of one-way delay from source to 0
P2R-SUMSQPOSJITTER Probe to Reflector Sum of Square of Positive Jitters.
The sum of square of positive one-way jitters from 0
source to destination in the current interval.
P2R-SYNC-ERRS The number of (time) Synchronization Errors from
0
probe to reflector in the current interval.
R2P-AVGABSJITTER Reflector to Probe Average Absolute Jitter (µsec) 0
R2P-AVG-OWDELAY Reflector to Probe Average Oneway Delay. The
average one-way destination to source delay (in
0
current interval.
R2P-DATA-FRAMES This attribute is only applicable to Y.1731 probes. This
is the number of data frames counted by the
Destination MEP (Reflector) that are transmitted
towards the Source MEP (Probe). Based on the
0
configuration the MEP counts the data frames with:
• MEP's LM RX priority or all the priorities
• All the VLAN IDs belonging the MEP's MA VID list
R2P-ERR-FRAMES Reflector to Probe Errored Frames 0
R2P-ERR-PKTS Reflector to Probe Errored Packets. The total number
of Received Packets in the current interval, which had
errors such as length of received packet is less than
0
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.
R2P-FRAMES Reflector to Probe Frames 0
R2P-LOST-FRAMES Reflector to Probe Lost Frames 0
R2P-LOST-PKTS Reflector to Probe Lost Packets. The number of Lost
Packets from reflector to probe in the current interval.
0
For Y.1731 probes, these are the actual data frames
lost.
R2P-MAXABSJITTER Reflector to Probe Maximum Absolute Jitter (µsec) 0
R2P-MAXNEGJITTER Reflector to Probe Maximum Negative Jitters. The
maximum negative one-way jitter from destination to 0
source in the current interval.
R2P-MAX-OWDELAY Reflector to Probe Maximum Oneway Delay. The
maximum one-way destination to source delay (in
0
current interval.
R2P-MAXPOSJITTER Reflector to Probe Maximum Positive Jitters. The
maximum positive one-way jitter from destination to 0
R2P-MINABSJITTER Reflector to Probe Minimum Absolute Jitter (µsec) 0

Default
Threshold
R2P-MINNEGJITTER Reflector to Probe Minimum Negative Jitters. The
minimum negative one-way jitter from destination to 0
R2P-MIN-OWDELAY Reflector to Probe Minimum Oneway Delay. The
minimum one-way destination to source delay (in
0
current interval.
R2P-MINPOSJITTER Reflector to Probe Minimum Positive Jitters. The
minimum positive one-way jitter from destination to 0
R2P-NEG-LOSSES This attribute is only applicable to Y.1731 probes. This
is 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 could
be some kind of provisioning mismatch between the
Probe MEP and Reflector MEP. Here are some
scenarios where this can happen:
• Probe MEP is configured to count in-profile frames
only and the Reflector MEP is configured to count
all frames with a mismatch in value for the attribute 0

cfmMepLmCount InProfileFrames.
• Probe MEP is configured to count data frames for
specific VLAN priority and the Reflector MEP is
configured to count data frames for all the priorities
with a mismatch in values for the attributes cfmMe-
pLmTx CountAllPrios or cfmMepLm RxCountAll-
Prios. NOTE: This could possibly happen due to
reasons not related to configuration, such as frame
reordering in the network.
R2P-NUMABSJITTER Reflector to Probe Number of Absolute Jitter (µsec) 0
R2P-NUMNEGJITTER Reflector to Probe Number of Negative Jitters. The
total number of negative one-way jitters from 0
destination to source in the current interval.
R2P-NUMPOSJITTER Reflector to Probe Number of Positive Jitters. The total
number of positive one-way jitters from destination to 0
R2P-PKTS Reflector to Probe Packets. The total number of
Received Packets in the current interval. In the case of
Y.1731 probes, this reflects the number of DMRs 0
(Delay Measurement Replies) received and this will
always be the same as the esaProbeStatsP2RPkts.
R2P-SUMABSJITTER Reflector to Probe Sum of Absolute Jitter (µsec) 0
R2P-SUMNEGJITTER Reflector to Probe Sum of Negative Jitters. The total
sum of negative one-way jitters from destination to 0

Default
Threshold
R2P-SUM-OWDELAY Reflector to Probe Sum of Oneway Delay. The total
sum of one-way delay from destination to source in the 0
current interval.
R2P-SUMPOSJITTER Reflector to Probe Sum of Positive Jitters. The total
sum of positive one-way jitters from destination to 0
R2P-SUMSQABSJITTER Reflector to Probe Sum of Square of Absolute Jitter
0
(µsec)
R2P-SUMSQNEGJITTER Reflector to Probe Sum of Square of Negative Jitters.
The sum of square of negative one-way jitters from 0
R2P-SUM-SQ-OWDELAY Reflector to Probe Sum of Square of Oneway Delay.
The sum of square of one-way delay from destination 0
to source in the current interval.
R2P-SUMSQPOSJITTER Reflector to Probe Sum of Square of Positive Jitters.
The sum of square of positive one-way jitters from 0
R2P-SYNC-ERRS Reflector to Probe Sync Errors. The number of (time)
Synchronization Errors from reflector to probe in the 0
current interval.
SEQ-GAPS The total number of sequence gaps across all packets
received in the current interval. If (Received Sequence
Number) is greater than or equal to (Last Received 0
Sequence Number + 2)) it is termed as a sequence
gap. NOTE: This is not applicable for Y.1731 probes.
SUM-RTDELAY The total sum of round trip delay (in milliseconds) in
the current interval. The reflector's processing time is 0
excluded from the value.
SUM-SQ-RTDELAY The sum of square of round trip delays in the current
0
interval.

Ethernet (Network/Access) Port PTP Flow Point

Monitored Types
Refer to the following table for Network/Access port PTP Flow Point Threshold
Crossing Alerts (TCAs) and their associated default settings.
Table 67: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings
15
Monitored Type Definition Direction Location 1 Day
Min.
ANNOUNCESRX Number of PTP Announce Receive Near End 0 0
messages received on the PTP
Flow Point.
ANNOUNCESTX Number of Announce Messages Transmit Near End 0 0
transmitted on the PTP Flow
Point. This object is applicable
for transparent clocks.
DELAYREQSRX Number of Delay Request Receive Near End 0 0
Messages received on the PTP
Flow Point.
DELAYREQSTX Number of Delay Request Transmit Near End 0 0
Messages transmitted on the
PTP Flow Point.
DELAYRSPSRX Number of Delay Response Receive Near End 0 0

Flow Point.
DELAYRSPSTX Number of Delay Response Transmit Near End 0 0
PTP Flow Point.
FOLLOWUPSRX Number of Follow up Messages Receive Near End 0 0
received on the PTP Flow Point.
FOLLOWUPSTX Number of Follow up Messages Transmit Near End 0 0
transmitted on the PTP Flow
Point.
MGMTFRAMESR Number of PTP Management Receive Near End 0 0
X Frames received on the PTP
Flow Point.
MGMTFRAMEST Number of PTP Management Transmit Near End 0 0
X Frames Messages transmitted
on the PTP Flow Point.
PDELAYREQSR Number of Peer Delay Request Receive Near End 0 0
X Messages received on the PTP
Flow Point.
PDELAYREQST Number of Peer Delay Request Transmit Near End 0 0
X Messages transmitted on the
PTP Flow Point.
PDELAYRSPSR Number of Peer Delay Response Receive Near End 0 0
X Messages received on the PTP
Flow Point.

Table 67: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings (Continued)
15
Min.
PDELAYRSPSTX Number of Peer Delay Response Transmit Near End 0 0
PTP Flow Point
PDELAYRSPFOL Number of Peer Delay Response Receive Near End 0 0
UPSRX Followup Messages received on
the PTP Flow Point.
PDELAYRSPFOL Number of Peer Delay Response Transmit Near End 0 0
UPSTX Followup Messages transmitted
on the PTP Flow Point.
PTPUNKNOWNS Number of Unknown PTP Receive Near End 0 0
RX Messages received on the PTP
Flow Point.
PTPUNKNOWNS Number of Unknown PTP Transmit Near End 0 0
TX Messages transmitted on the
PTP Flow Point.
SIGNALINGRX Number of PTP Signaling Receive Near End 0 0
Flow Point.
SIGNALINGTX Number of PTP Signaling Transmit Near End 0 0
PTP Flow Point.
SYNCSRX PTP Sync Messages Received Receive Near End 0 0
SYNCSTX PTP Sync Messages Transmit Near End 0 0
Transmitted
AVGSYNCRESTI The average residence time for Receive Near End 0 0
ME PTP Sync messages.
MINSYNCRESTI The minimum residence time for Receive Near End 0 0
MAXSYNCRESTI The maximum residence time for Receive Near End 0 0
AVGDELAYREQ The average residence time for Receive Near End 0 0
RESTIME PTP Delay Request messages.
MINDELAYREQR The minimum residence time for Receive Near End 0 0
ESTIME PTP Delay Request messages.
MAXDELAYREQ The maximum residence time for Receive Near End 0 0
RESTIME PTP Delay Request messages.
AVGPDELAYRE The average residence time for Receive Near End 0 0
QRESTIME PTP Peer Delay Request
messages.
MINPDELAYREQ The minimum residence time for Receive Near End 0 0
RESTIME PTP Peer Delay Response
messages.
MAXPDELAYRE The maximum residence time for Receive Near End 0 0
QRESTIME PTP Peer Delay Request
messages.

Table 67: Ethernet Port PTP Flow Point Monitored Types and Default TCA Settings (Continued)
15
Min.
AVGPDELAYRS The average residence time for Receive Near End 0 0
PRESTIME PTP Peer Delay Response
messages.
MINPDELAYRSP The minimum residence time for Receive Near End 0 0
RESTIME PTP Peer Delay Response
messages.
MAXPDELAYRS The maximum residence time for Receive Near End 0 0
PRESTIME PTP Peer Delay Response
messages.
PTP MCI Monitored Types

Refer to the following table for Master Clock Interface (MCI) Threshold Crossing
Alerts (TCAs) and their associated default settings.
Table 68: Master Clock Interface Monitored Types and Default TCA Settings
Monitored 15
Definition Direction Location 1 Day
Type Min.
MC_PTPDISC PTP Message Discards Receive Near End 0 0
ARDS
MC_ANNOUN Announce Service Denied Events Receive Near End 0 0
CEDENEVTS
MC_SYNCDE Sync Service Denied Events Receive Near End 0 0
NEVTS
MC_DELAYR Delay Response Service Denied Receive Near End 0 0
ESPDENEVTS Events
MC_ANNCAN Announce Service Canceled Events Receive Near End 0 0
CELEVTS
MC_SYNCCA Sync Service Canceled Events Receive Near End 0 0
NCELLEVTS
MC_DELAYR Delay Response Service Canceled Receive Near End 0 0
ESPCANCELE Events
VTS
MC_DYNSLA Dynamic Slaves Learned Count Receive Near End 0 0
VESLEARNC
OUNTS
MC_DYNSLA Dynamic Slaves Service Dropped Receive Near End 0 0
VESDROPPE
D

PTP Remote Slave Monitored Types

Refer to the following table for Remote Slave (Dynamic or Static) Threshold
Table 69: PTP Remote Slave Monitored Types and Default TCA Settings
Monitored 15
Type Min.
ANNOUNC Announce Messages Generated Transmit Near End 0 0
EMSGSGE
N
RS_SYNC Sync Messages Generated Transmit Near End 0 0
MSGSGEN
RS_DELAY DelayResp messages generated Transmit Near End 0 0
RESPMSG
SGEN
RS_SIGNA Signaling Messages generated Transmit Near End 0 0
LMSGSGE
N
RS_SIGNA Signaling Messages Received Receive Near End 0 0
LMSGSRX
RS_DELAY Delay Req Messages Received Receive Near End 0 0
REQMSGS
RX
RS_DELAY Delay Req Messages Dropped Receive Near End 0 0
REQMSGS
DROPPED
RS_INVTL PTP messages with invalid PTP TLV Receive Near End 0 0
VLENDISC length
ARDS
RS_INVTL PTP messages with unknown PTP Receive Near End 0 0
VTYPEDIS TLV type
CARDS
RS_TIMES Times Announce lease duration Receive Near End 0 0
ANNOUNC expired
ELEASEEX
P
RS_TIMES Times Sync lease duration expired Receive Near End 0 0
SYNCLEAS
EEXP
RS_TIMES Times Delay_Resp lease duration Receive Near End 0 0
DELAYRES expired
PEXP

SOOC Monitored Types

Refer to the following table for Slave Only Ordinary Clock (SOOC) Threshold
Table 70: SOOC Monitored Types and Default TCA Settings

Monitored 15
Type Min.
PTPMGMTM PTP Management Message Discards Receive Near End 0 0
SGSD
PTPINVMS PTP Invalid Message Length Discards Receive Near End 0 0
GLEND
PTPUNKMA PTP Unknown Master Discards Receive Near End 0 0
STERD
PTPUNKDO PTP Unknown Domain Discards Receive Near End 0 0
MAIND
PTPMULTIA PTP Multicast Announce Message Receive Near End 0 0
NNOUNCED Discards
PTPOOSAN PTP Out Of Sequence Announce Receive Near End 0 0
NOUNCES Messages
PTPMULTIS PTP Multicast Sync Message Discards Receive Near End 0 0
YNCD
PTPTWOST PTP Two Step Sync Message Discards Receive Near End 0 0
EPSYNCD
PTPFOLLO PTP Follow-up Message Discards Receive Near End 0 0
WUPSD
PTPDELAY PTP Delay_Req Message Discards Receive Near End 0 0
REQSD
PTPPDELA PTP PDelay_Req Message Discards Receive Near End 0 0
YREQSD
PTPPDELA PTP PDelay_Resp Message Discards Receive Near End 0 0
YRSPSD
PTPPDELA PTP PDelay Follow-up Message Receive Near End 0 0
YFOLLOWU Discards
PSD
PTPINVTLV PTP Invalid TLV Length Discards Receive Near End 0 0
LENSD
PTPINVTLV PTP Invalid TLV Type Discards Receive Near End 0 0
TYPESD
AVGSYNCP Average Sync Path Delay (nsec) Receive Near End 0 0
D
MINSYNCP Minimum Sync Path Delay (nsec) Receive Near End 0 0
D
MAXSYNCP Maximum Sync Path Delay (nsec) Receive Near End 0 0
D
MINSYNCP Minimum Sync PDV (nsec) Receive Near End 0 0
DV

Monitored 15
Type Min.
AVGSYNCP Average Sync PDV (nsec) Receive Near End 0 0
DV
MAXSYNCP Maximum Sync PDV (nsec) Receive Near End 0 0
DV
AVGMEANP Average Mean Path Delay (nsec) Receive Near End 0 0
ATHDELAY
MINMEANP Minimum Mean Path Delay (nsec) Receive Near End 0 0
ATHDELAY
MAXMEANP Maximum Mean Path Delay (nsec) Receive Near End 0 0
ATHDELAY
AVGOFM Average Offset from Master (nsec) Receive Near End 0 0
MINOFM Minimum Offset from Master (nsec) Receive Near End 0 0
MAXOFM Maximum Offset from Master (nsec) Receive Near End 0 0
PT Flow Monitored Types

The following performance parameters are related to an Pass-Through (PT)
flow.
Table 71: PT Flow Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
ABRPT12 Average Bit Rate (PT12). Receive Near End 0 0
ABRPT21 Average BIt Rate (PT21). Transmit Near End 0 0
ABRRLPT12 Average Bit Rate - Rate Limited (PT12) Receive Near End 0 0
ABRRLPT21 Average Bit Rate - Rate Limited (PT21) Transmit Near End 0 0
ABRRLRPT Average Bit Rate - Rate Limited and Receive Near End 0 0
Replicated (PT12)
BPT12 Total Bytes In (PT12) Receive Near End 0 0
BPT21 Total Bytes In (PT21) Transmit Near End 0 0
BOPT12 Total Bytes Out (PT12) Receive Near End 0 0
BOPT21 Total Bytes Out (PT21) Transmit Near End 0 0
ES Errored Seconds Receive Near End 0 0
FMGPT12 Frames Marked Green (PT12) Receive Near End 0 0
FMGPT21 Frames Marked Green (PT21) Transmit Near End 0 0
FMRDPT12 Frames Marked Red and Discarded Receive Near End 0 0
(PT12)
FMRDPT21 Frames Marked Red and Discarded Transmit Near End 0 0
(PT21)
FMYPT12 Frames Marked Yellow (PT12) Receive Near End 0 0
FMYPT21 Frames Marked Yellow (PT21) Transmit Near End 0 0
FTDPT12 Frames Tail Dropped (PT12) Receive Near End 0 0
L2CPFD Layer 2 Control Protocol Frame Receive Near End 0 0
Discarded

Table 71: PT Flow Monitored Types and Default TCA Settings (Continued)
Monitored 15 1
Type Min. Day
SES Severely Errored Seconds Receive Near End 0 0
UAS Unavailable Seconds Receive Near End 10 10
PT Flow Shaper (QoS Queues) Monitored Types

The following performance parameters are for each of the Shapers which ares
supported for a Pass-Through Flow. QoS queues exist for the N1 and N2 direc-
tions.
Table 72: PT Flow QoS Shaper Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
ABRRL Average Bit Rate - Rate Limited Receive Near End 0 0
BT Bytes Dequeued (Transmitted) Receive Near End 0 0
BTD Bytes Tail Dropped Receive Near End 0 0
FD Frames Dequeued Receive Near End 0 0
FREDD Frames Random Early Discard Transmit Near End 0 0

Dropped
FTD Frames Tail Dropped Receive Near End 0 0
PT Flow Policer Monitored Types

The following performance parameters are for each of the Policers which are
supported for a Pass-Through Flow. Policers exist for the N1 and N2 directions.
Table 73: PT Flow Policer Monitored Types and Default TCA Settings
Monitored 15 1
Type Min. Day
ABR Average Bit Rate - for Policer n1 Receive Near End 0 0
BYTESIN Total Bytes In Receive Near End 0 0
BYTESOUT Total Bytes Out Receive Near End 0 0
FMG Frames Marked Green and Passed - Receive Near End 0 0
for Policer n
FMRD Frames Marked Red and Discarded - Receive Near End 0 0
for Policer n
FMY Frames Marked Yellow and Passed - Receive Near End 0 0
for Policer n
FTD Frames Tail Dropped - for Policer n Receive Near End 0 0
1. There are at most 8 Policers for each direction, where n is 0 through 7.

ESA Options and Rules

Etherjack Service Assurance (ESA) provisioning and reporting is invoked by
selecting the ESA icon on the Tool Bar or selecting ESA from the Applications
menu and expanding the system folder, NE-1 entity and GE11x entity in the
Selection Tree. Creating Reflectors and Probes are performed by entering a
right click on the Reflectors or Probes entities and selecting Create Reflector or
Create Probe.
Editing or Deleting an existing Reflector or Probe is performed by expanding the
Probes or Reflectors entity (nested Probe and Reflector entities are displayed),
entering a right click on the desired Probe or Reflector entity, and selecting
Edit/Delete Reflector/Probe. (Any ESA Schedule associated with the Probe
must be deleted prior to deleting a Probe.)
The following ESA provisioning options and rules are described for each option
setting available for:
• GE112: Network Port 1 (E1000-N-1), Access Ports E1000-A-3 to
E1000-A-4 or LAGs of Access Ports or Network Ports (and E1000-A-2 - if
provisioned).
• GE114x: Network Port 1 (E1000-N-1) and E1000-A-3 to E1000-A-6 or LAGs
of Access Ports or Network Ports (and E1000-A-2 - if provisioned).
See Table 74 and Table 75 for ESA Reflector and Probe configuration settings,
respectively. Default settings are identified in bold.
Table 74: ESA Reflector Configuration Settings

Parameter
Identification
Reflector Index An Identifier value used to uniquely identify this
(Create Reflector ESA Reflector. 1-255
only)
Reflector ID Reflector identifier (1 to 15 characters - no spaces,
(Create Reflector and must contain only alpha-numeric characters). 1 to 15 characters
only) This is a user specified unique identifier associated (blank)
with a Reflector and must be provided.
Reflector Identification
Source Port Reflector source port. Points to the Port to which
(drop-down list of
(Create Reflector the ESA Reflector is attached, i.e., on which the
available ports)
only) service to be monitored resides.
IP Information
Reflector IP Address Reflector IP address. This is a user specified IP
(Create Reflector address, uniquely associated with an ESA
only) Reflector instance. The IP address must not 0.0.0.0
overlap with any non-ESA related subnets
provisioned within the GE11x. (See Note.)
Mask Reflector Subnet mask.
(Create Reflector 255.255.255.0
only)

Table 74: ESA Reflector Configuration Settings (Continued)

Parameter
Priority Map Mode Priority Map Mode. None
TOS
DSCP
Priority Specifies the Priority Value for ESA Reflector N/A
Priority Map Mode. Only applicable if Priority Map 0-7 (TOS)
Mode is set to TOS or DSCP. 0-63 (DSCP)
If the IP address assigned to the Reflector collides with an IP address

PS
used by the customer traffic, all packets destined for that IP address
are routed up to the Network Processor.
Note
Table 75: ESA Probe Configuration Settings

Parameter

Identification
Probe Index An Identifier value used to uniquely identify this ESA
1-255
(Create Probe only) Probe.
Probe ID Probe identifier (1 to 15 characters - no spaces, and
(Create Probe only) must contain only alpha-numeric characters). This is a 1 to 15 characters
user specified unique identifier associated with a (blank)
Probe and must be provided.
Probe Identification
Protocol Protocol. UDP Echo and ICMP Echo measure the UDP Echo
(Create Probe only) round-trip delay. ICMP Timestamp measures the ICMP Echo
round-trip delay and one-way delay as well as ICMP Timestamp
one-way jitter. Y.1731 links ESA to CFM MEPs for
Y.1731 LM/DM
facilitating ETH-LM Frame Loss Measurements and
ETH-DM Delay Measurements. Selecting a Y.1731
protocol changes the create options. (See Y.1731
only options below.)
Source Port Probe source port. Points to the Port to which the ESA
(drop-down list of
(Create Probe only) Probe is attached, i.e., on which the service to be
available ports)
monitored resides.
Service End Points
Probe IP Address Source (Probe) IP address. This is a user specified IP
(Create Probe only)1 address, uniquely associated with an ESA Probe
instance. This is the IP address to be used in UDP
Echo, ICMP Echo or ICMP Timestamp request. The 0.0.0.0
IP address must not overlap with any non-ESA related
subnet provisioned within GE11x. Not available if
protocol is Y.1731.

Table 75: ESA Probe Configuration Settings (Continued)

Parameter
Probe Mask Probe Subnet mask. Not available if protocol is
255.255.255.0
(Create Probe only) Y.1731.
Reflector IP Address Destination (Reflector) IP address. This is a user
(Create Probe only) specified IP address, which is the ESA Reflector’s IP
IP address
address. This is the IP address to be used in UDP
(blank)
Echo, ICMP Echo or ICMP Timestamp request. Not
available if protocol is Y.1731.
Source MEP Drop-down list of MEPs available on the selected
List of MEPs
(Create Y.1731 only) interface.
Destination MEP Drop-down list of Destination Types. MAC Address
Type MEP Id
(Create Y.1731
LM/DM only)
Destination MAC Destination MAC Address if Destination Type is MAC
Address Address. 00:00:00:00:00
(Create Y.1731 only)
Traffic Parameters (Not available if protocol is Y.1731)
Packet Type2 Specifies whether the service is VLAN Tagged or Untagged
Untagged. Not available if protocol is Y.1731. VLAN Tagged
VLAN ID2 Virtual LAN identifier. Provides the ability to monitor a
0 to 4096
specific service. This option is only applicable when
N/A
Packet Type is set to VLAN Tagged.
VLAN Priority2 Defines the VLAN Priority. This option is only 0 to 7
applicable when Packet Type is set to VLAN Tagged. N/A
Priority Mode Identifies the priority classification mechanism for None
ESA traffic. TOS stands for Type Of Service, and TOS
DSCP is Diffserv Codepoint. Not available if protocol DSCP
is Y.1731.
Priority2 Specifies the ESA service priority bits. Not available if 0 to 63 (DSCP)
protocol is Y.1731. or
0 to 7 (TOS)
N/A
Packet Size2 Set the packet size (in bytes) of the Service
64-1512
Assurance Packets. Not available if protocol is
104
Y.1731.
Packets per Sample2 Set the number of packets per sample. Not available if 1- 99999
protocol is Y.1731. 500
Packet Interval2 Interval between packets (in milliseconds). Not 1-99999
available if protocol is Y.1731. 100
Dead Interval2 Setting time (in seconds) after all packets within a 1-99999
sample are sent. Not available if protocol is Y.1731. 10
Response Timeout2 Set the amount of time to wait for a response (in
1-99999
seconds). Packets received after this timeout are
5
considered lost. Not available if protocol is Y.1731.
Service Parameters (Only available if protocol is Y.1731.)


Parameter
Multi COS Enable or disable Multi COS. If Multi COS is enabled, Disabled
(Y.1731 only) the other Service Parameter settings are entered for
each COS selected as Active by clicking on the Active Enabled
check box next to each COS in the table.
COS COS for the Y.1731 Probe if Multi COS is disabled. COS 0 - COS 7
(Y.1731 only) Only available if protocol is Y.1731. COS 0
Frame Size Delay Measurement Message packet size. DMMs are
(Y.1731 only) normally 64 bytes, but can be made larger by adding a
64-2000
Data TLV padded with all zeros. LMMs are fixed
128
length by standard. Only available if protocol is
Y.1731.
Interval Delay Measurement Message Interval. Only available 10 Milliseconds
(Y.1731 only) if protocol is Y.1731. 100 Milliseconds
1 Second
10 Seconds
1 Minute
History Bins Number of History Bins (up to a maximum of 32 bins). 1 to 32
(Create Probe only) This is the amount of time between history bins. 8
History Distribution Number of History Distribution Bins (up to a maximum
1 to 32
Bins of 32 bins).
8
(Create Probe only)
History Interval History Interval (in minutes). 1 Minute
(Create Probe only) 5 Minutes
10 Minutes
15 Minutes
60 Minutes
History Distribution History Distribution Interval (in minutes). This is the 1 Minute
Interval amount of time between history distribution bins. 5 Minutes
(Create Probe only) 10 Minutes
15 Minutes
60 Minutes
Statistics and Distribution
Min.2 Minimum delay threshold (in milliseconds). The entry
must be less than the entry for Max. Round Trip -2147483647 to
Round Trip Delay, 2147483647
One Way Tx Delay, Delay. Valid entry is -2147483647 to 2147483647.
Default is dependant on the type of statistics and dis- 0
One Way Rx Delay
One Way Tx Jitter, or tribution.
-5000
One Way Rx Jitter


Parameter
Max.2 Maximum delay threshold (in milliseconds). The entry
must be greater than the entry for Min. Round Trip -2147483647 to
Round Trip Delay, 2147483647
One Way Tx Delay, Delay. Valid entry is -2147483647 to 2147483647.
Default is dependant on the type of statistics and 10000
One Way Rx Delay,
One Way Tx Jitter, or distribution.
5000
One Way Rx Jitter
Bins2 Number of bins.
Round Trip Delay,
One Way Tx Delay, 1-10
One Way Rx Delay,
One Way Tx Jitter, or
One Way Rx Jitter
1. If 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.
2. Oneway options are only available if ICMP timestamp is set for protocol type. A Probe that is assigned
to an active schedule cannot be edited.
Scheduled ESA Activity Settings
The following section describes scheduled ESA activities option settings. A
scheduled ESA is invoked by selecting the ESA icon on the Tool Bar or select-
ing ESA from the Applications menu, expanding the system folder in the Selec-
tion Tree, entering a right click on Schedules and selecting Create Schedule.
Default settings are identified in bold. Up to 10 Scheduled ESA groups may be
created.
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, Sus-
pend Schedule and Resume Schedule. To delete an activity, you must first Sus-
pend the activity.
Table 76: Scheduled ESA Configuration Settings

Parameter
Identification
Schedule Index An Identifier value used to uniquely identify
1-255
(Create Schedule only) this ESA Schedule.
Activity ID Activity identifier (1 to 15 ASCII characters).
This is a user specified unique identifier up to 15 characters
associated with a Probe, and is not a (blank)
mandatory entry.
Schedule Parameters
Schedule Type Define schedule type as a one time or periodic One Shot
execution. Periodic

Table 76: Scheduled ESA Configuration Settings (Continued)

Parameter
Start Time Buttons Activate either an immediate ESA or future Now
(scheduled) ESA. Future
Periodic Interval (secs) Specifies the interval between subsequent
Range 1 to
runs (in seconds). This option is only available
2147483647
if Schedule Type of Periodic is selected.
Duration Buttons Define the duration as continuous or a fixed Forever
time (in seconds). Only applicable if Schedule
Fixed
Type of One Shot is selected.
Define the duration in seconds. Valid entries
Duration (secs) are 0 (continuous) through 9999 (seconds) if
Entry Window Schedule Type of One Shot is selected, and 0 to 9999 (One Shot)
valid entries are 60 through 9999 (seconds) if 60 to 9999 (Periodic)
Schedule Type of Periodic is selected. This
option is only valid if Fixed duration is
selected.
Start Time Entry The date in format: yyyy-mm-dd and the time.
Windows When cursor is placed in data entry window
and mouse click is entered, a calendar
selection appears, allowing date selection. yyyy-mm-dd
Entry selection must be the current date or

greater. This option is only applicable if Future
start time is selected.
Define the duration in hours, minutes and
seconds in format: hh:mm:ss (24-hour clock
time entry). When cursor is placed in data
entry window and mouse click is entered, a
start time drop down selectable menu hh:mm:ss
appears, in 15 minute segments. Entry
selection must be greater than the current
time. This option is only applicable if Future
start time is selected.
Schedule Probes Selects the Probes that belong to this ESA
schedule. To add a Probe, select a Probe from
the Schedule Probes list. Multiple Probes may
be selected. Probes may be deselected by
Any available probes
clicking on the Probe once again before hitting
will be displayed in the
the OK button. Only previously created Probes
Schedule Probes list as
that are not used for another Scheduled
a checkbox selection
Activity are available for selection. Once a
schedule has been created, it cannot be
edited. It must be deleted and re-created with
the desired new parameters.

CFM Configuration Options and Rules

The following section describes Connectivity Fault Management (CFM) option
settings. CFM configuration options are created in the following order:
• Configure System Default MD Parameters
• Configure Server MEP Parameters
• Configure CFM VLAN Table
• Configure Maintenance Domain
• Configure Maintenance Association Network
• Configure Maintenance Association Component
• Configure Maintenance End Point
• Initiate Loopback Message
• Initiate Link Trace Message
In addition to configuring CFM options, alarm attributes are editable when the
CFM application is selected (see CFM Maintenance End Point Alarms on
p. 562).
Configure System Default MD Parameters
System Default Maintenance Domain (MD) level parameters may be created by
selecting the CFM icon on the Tool Bar or selecting CFM from the Applications
menu, expanding the system folder in the Selection Tree, entering a right click
on the System entity and selecting Edit System Default MD Level. The Default
MD may be edited by entering a right click on the desired Default MD entity and
selecting Edit.
Table 77: Configure Default MD Parameters Settings
System Level Default MD Description / Option Settings /
Parameter Parameter Applicable Rules Defaults
Configuration
System Default Level System or specified Maintenance
0 to 7
MD Level Domain default MD level.
System MIP MIP Creation MIP Creation Control. If Default is None
Creation Control Control selected, the parameters set in the Default
Default Maintenance Domain will Explicit
be used for MD Level, MIP Creation
Control and Default Sender ID
Control.

Configure Server MEP Parameters

Server MEP level parameters may be created by selecting the CFM icon on the
Tool Bar or selecting CFM from the Applications menu, expanding the system
folder in the Selection Tree, entering a right click on the Server MEPs entity and
selecting Create Server MEP. An existing Server MEP may be edited by entering
a right click on the desired Server MEP entity and selecting Edit Configuration.
To delete a Server MEP, right click on the Server MEP entity and select Delete.
The following MEP provisioning options and rules are described for each option
provisioned).
Table 78: Configure Server MEP Parameters Settings

Parameter
Identification
Server MEP Index number assigned to a specific Server MEP entity.

Index
1 to 255
(Create Sever
MEP Only)
Associated Port Drop-down list of associated interfaces. LAG entities are (drop-down list of
(Create Sever only listed if one or more LAG groups have been available ports)
MEP Only) provisioned.
Configuration
AIS Generation Enable or disable generation of AIS by a Server MEP. Enabled
Disabled
AIS Client MD Set the client MD level of a Server MEP 0-7
Level
AIS Transmission Set the interval for AIS transmission. Only effective if AIS 1 Second
Interval Generation is Enabled. 1 Minute
AIS Priority Set the AIS priority level. 0-7
Configure CFM VLAN Table

The CFM VLAN List may be edited by selecting the CFM icon on the Tool Bar or
selecting CFM from the Applications menu, expanding the system folder in the
Selection Tree, entering a right click on Network Port 1, any Access Port or a
LAG ID and selecting Create VLAN Entry.
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.
See the following table for Maintenance Domain configuration settings.
Table 79: CFM VLAN Table Configuration Settings
Parameter
Primary VID Primary VLAN Identifier. 1 to 4095
CFM Virtual Identifier (VID) list. To add a VID member, enter
VID List a valid VID ID in the VID Entry window and select Add. To
delete a VID member, select the VID number in the VID List
1 to 4095
window and select Remove. The last VID member cannot be
removed.
Configure Maintenance Domain

A Maintenance Domain (MD) may be created by selecting the CFM icon on the
Tool Bar or selecting CFM from the Applications menu, expanding the system
folder in the Selection Tree, entering a right click on the Maintenance Domain
entity and selecting Create MD. To edit an existing MD, expand the Maintenance
Domain entity, enter a right click on the desired MD and select Edit Configura-
tion. The following parameters cannot be edited: MD Index, Level. To edit these
parameters, the MD must be deleted and then re-entered with the new desired
parameters.
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)

PS
must first be deleted.

Note
See the following table for Maintenance Domain configuration settings. Default
settings are identified in bold.
Table 80: Maintenance Domain Configuration Settings
Parameter
Identification
MD Index Maintenance Domain identifier.
(Create MD 1 - 256
Only)

Table 80: Maintenance Domain Configuration Settings (Continued)

Parameter
Configuration
Format Type Selectable Name Entry type. String
MAC - Integer
DNS Name
No Name
MD 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-Integer is selected). If Format Type Text string
String or DNS Name is selected, ASCII characters are MAC address or
allowed. If Format Type MAC-Integer is selected, the DNS name
entry must be Hexadecimal characters.Note that it is not (blank)
allowed to use system reserved names (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.
(Create MD 0 to 7
Only)
MIP Creation MIP Creation Control. If Default is selected, the None

Control parameters set in the Default Maintenance Domain is Default
used for MD Level, MIP Creation Control and Default Explicit
Sender ID Control.
Configure Maintenance Association Network

A Maintenance Association Network (MANET) can be created by selecting the
CFM icon on the Tool Bar or selecting CFM from the Applications menu,
expanding the system and Maintenance Domain folders in the Selection Tree,
entering a right click on the desired Maintenance Domain entity and selecting
Create MANET.
To edit a MANET, expand the Maintenance Domain entity, expand the Mainte-
nance Domain ID, enter a right click on the desired MANET and select Edit Con-
figuration. 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 Main-
tenance 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.
In order to delete an MA, all subordinate entities (MACOMP, MEPs)

PS
must first be deleted.

Note

See the following table for MANET configuration settings. Default settings are
identified in bold.
Table 81: Maintenance Association Network Configuration Settings
Parameter
Identification
MANET Index Maintenance Association Network identifier.
(Create MANET 1 - 256
Only)
Format Type Selectable Name Entry type. Integer
Primary VID
String
VPN Id
ICC Format
MA Name A Maintenance Association name identified by ICC
Format, integer, in Hexadecimal (if Format Type Integer is
selected) or by Primary VLAN Identifier (if Format Type ICC Format,
Primary VID is selected) or by character string (if Format Text string
Type String is selected) or by VPN identifier (if Format Hexidecimal or
Type VPN ID is selected). If Format Type String is Primary VLAN
selected, ASCII characters are allowed. The MA Name Identifier
must be unique per associated MD. Note that it is not
allowed to use system reserved names (i.e. ltp, cfm, efm, (blank)
elmi, erppdu, eth0, eth1,jdsu, lagpdu, lldppdu, lo,
ptpsyncjack, ptpts, sat, ssm, etc) to name CFM entities.
CCM Interval Continuity Check Message (CCM) interval. The same 3.3 Milliseconds
interval must be selected for all MEPs associated with the 10 Milliseconds
MA. For GE11x, up to 16 local MEPs can be created in the 100 Milliseconds
CCM interval of 3.3 ms and 10 ms.
1 Second
10 Seconds
1 Minute
10 Minutes
MEP ID Entry Maintenance End Point (MEP) list. To add a MEP
member, enter the valid MEP ID number in the MEP ID 1 to 8191
Entry window and select Add. To delete a MEP member,
select the MEP number in the MEP ID List window and (blank)
select Delete. The last VID member cannot be removed.

Configure Maintenance Association Component

A Maintenance Association - Component (MACOMP) can be created by select-
ing the CFM icon on the Tool Bar or selecting CFM from the Applications menu,
expanding the system and Maintenance Domain folders in the Selection Tree,
entering a right click on the desired Maintenance Domain ID and MANET enti-
ties and selecting Create MACOMP.
To edit a MACOMP, expand the Maintenance Domain entity, expand the Main-
tenance 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.
In order to delete an MA, all subordinate entities (MEPs) must first be

PS
deleted.
Note
The following MA provisioning options and rules are described for each option

provisioned).
See the following table for MACOMP configuration settings. Default settings are
identified in bold.
Table 82: Maintenance Association Component Configuration Settings

Parameter
Identification
MACOMP Index Maintenance Association Component identifier.
1
(not editable)
Configuration
Associated Port Drop-down list of associated interfaces. LAG entities are
(Create only listed if one or more LAG groups have been (drop-down list of
MACOMP Only) provisioned. available ports)
Primary VID Primary VLAN Identifier. 0 to 4095

(create only) (blank)

Table 82: Maintenance Association Component Configuration Settings (Continued)

Parameter
MIP Creation MIP Creation Control. If Default is selected, the None
Control parameters set in the Default Maintenance Domain will be Default
used for MD Level, MIP Creation Control and Default Explicit
Sender ID Control.
Defer
Configure Maintenance End Point

A Maintenance End Point (MEP) can be created by selecting the CFM icon on
the Tool Bar or selecting CFM from the Applications menu, expanding the sys-
tem, NE-1 and NTE11x entities in the Selection Tree, entering a right click on
the desired Access Port, Network Port or LAG entity, and selecting Create MEP.
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.
Table 83: Maintenance End Point Configuration Settings

Parameter
Identification
MEP Index Maintenance End Point (MEP) identifier. MEP IDs are
(Create MEP created when provisioning a MEP list during MA
Only) creation/edit. Existing MEP IDs are listed in numerical
1 to 8191
order according to the selected MANET ID. The
appropriate MANET ID must be selected prior to
selecting the MEP ID.
MANET ID Maintenance Association - Network identifier associated
(Create MEP with this MEP. The MANET must first be created prior to Available CFM
Only) selecting this MANET ID. The MANET ID must be MANET IDs from
selected first, then the MEP Index, because it option list
determines which MEP Index is available.
State
Administrative MEP state setting. When disabled, the MEP is inactive. Disabled
IS
Management
Configuration (General)
Direction Selects the MEP direction. Up
(Create MEP Down
Only)

Table 83: Maintenance End Point Configuration Settings (Continued)

Parameter
CCM Generation Enable or disable Continuity Check Message (CCM) Disabled
generation. Enabled
VLAN Priority VLAN priority. 0 to 7
LLF Trigger Check boxes to select triggers for Link Loss Forwarding.
The check boxes are for Ethernet Alarm Indication
Signal Defect, Interface Status, Remote Defect (de-selected)
Indication and Remote MEP Continuity Check Message
Interface Status.
VLAN Ethertype Ethertype for MEP VLAN Tag for the MEPs. 8100 (hex)
Fault Alarm Select the priority for fault alarm. The fault priority in MAC Remote
Priority descending order is: XCON, Error, Remote, MAC, All XCON Error
Defined (for RDICCM), and the fault alarm level in All Defined
ascending order is: 1) All Defined, 2) MAC Remote Remote XCON
XCON Error, 3) Remote XCON Error, 4) XCON Error, 5) Error
XCON, 6) No XCON. For example, if All Defined is
XCON Error
selected, all alarms for the five fault priorities will be
reported; if No XCON is selected, no alarms of the five XCON
priorities will be reported. No XCON
Primary VID Primary VLAN Identifier. Options available are 0 to 4095

determined by the selected MACOMP’s Primary VID(s) MACOMP Primary
created. VID
SAT Responder This option should be Enabled at the destination MEP if Disabled
Control SAT test mode is one way. Enabled
Configuration (AIS)
AIS Generation Determines if this MEP can generate ETH-AIS for alarm Disabled
suppression. Enabled
AIS Transmission Sets the repeat period for ETH-AIS message. Period is 1 Second
Interval ineffective unless AIS Generation is Enabled. At the 1 Minute
peer MEP, if no ETH-AIS message is received for 3.5
times the transmission period, ETH-AIS is reset.
AIS Trigger Check boxes for selecting triggers for generating
ETH-AIS. Triggers are ineffective if AIS Generation is
Disabled. Trigger events are Alarm Indication Signal (de-selected)
Defect, Remote Continuity Check Message (CCM),
Error CCM, Cross Connect CCM.
AIS Priority Sets the priority of the ETH-AIS. 0-7
AIS Client MD Drop-down list of configured MD Levels. 1-7
Level
Configuration (ESA)
LM In-Profile Only Only the frames determined as Green (in-profile) by the Enabled
ingress policing are counted for loss measurement. Disabled

Table 83: Maintenance End Point Configuration Settings (Continued)

Parameter
LM TX Count All If Enabled, the frames of all priorities in transmitting Enabled
Priorities direction at the corresponding port are counted for loss Disabled
measurement; If Disabled, only the frames with the
same priority as the probe (same VID as MA Primary
VID) in transmitting direction at the corresponding port
are counted for loss measurement.
Dual-ended If Enabled, the frames of all priorities in both transmitting Enabled
Count All and receiving directions at the corresponding port are Disabled
Priorities counted for loss measurement; If Disabled, only the
frames with the same priority as the probe (same VID as
MA Primary VID) in both directions at the corresponding
port are counted for loss measurement.
LM RX Count All If Enabled, the frames of all priorities in receiving Enabled
Priorities direction at the corresponding port are counted for loss Disabled
measurement; If Disabled, only the frames with the
same priority as the probe (same VID as MA Primary
VID) in receiving direction at the corresponding port are
counted for loss measurement.
Initiate Loopback Message
Loopback Message (LBM) may be initiated by selecting the CFM icon on the
Tool Bar or selecting CFM from the Applications menu, expanding the system,
NE-1, NTE11x and Access Port, Network Port or LAG entities in the Selection
Tree, entering a right click on the desired MEP entity, and selecting Loopback.
See the following table for Initiate Loop Back Message configuration settings.

PS

switching.
Note
Table 84: Initiate Loopback Message Settings

Parameter
Destination Type Selects the LBM destination type. MAC Address
Remote MEP Id
Destination ID Allows entry of the destination MAC address or Available CFM
selection of the desired Remote MEP ID. Remote MEP Id
List
(blank)

Table 84: Initiate Loopback Message Settings (Continued)

Parameter
Number of LBMs to be Allows entry of the number of LBMs to be
1 to 50
transmitted transmitted.
Number of padding Allows entry of the number of padding bytes to be
0 to 1470
bytes in the Data TLV added to the Data TLV.
All Zeros
Data Pattern Selects the LBM Data Pattern to be sent. All Ones
Alternate Zeros
and Ones
Vlan Priority Selects the LBM VLAN priority. 0 to 7
VLAN Drop Eligible Selects whether LBM VLAN drop is enabled or not. Enabled
Disabled
The MEP must be set to the In Service State for the Loop Back
PS
Message to be initiated.
Note
Initiate Link Trace Message

Link Trace Message (LTM) may be initiated by selecting the CFM icon on the
Tool Bar or selecting CFM from the Applications menu, expanding the system,
NE-1, NTE11x and Access Port, Network Port or LAG entities in the Selection
Tree, entering a right click on the desired MEP entity, and selecting Linktrace.
See the following table for Initiate Link Trace Message configuration settings.
Table 85: Initiate Link Trace Message Settings

Parameter
Destination Type Selects the LTM destination type. MAC Address
Remote MEP Id
Destination ID Allows entry of the destination MAC address (Dropdown list of
(hex) or selection of the desired Remote MEP ID. available remote MEPs)
TTL Sets the Time To Live (TTL) value for this LTM. 1 to 255
64
Use FDB Only Selects whether LTM transmit flags are enabled Enabled
or not. Disabled
LTM Egress ID Allows entry of the LTM egress ID in 00:00:00:80:ea:22:00:00
hexadecimal. hh:hh:hh:hh:hh:hh:hh:hh

The MEP must be set to the In Service State for the Link Trace
PS
Message to be initiated.
Note

PTP Configuration Options and Rules

(GE114S/GE114SH)
The following section describes Precision Time Protocol (PTP) option settings.
The options described in this section are performed using the PTP application
(located on the Tool Bar or selectable via the Application menu) once the
license of this feature has been turned on. The PTP License may be enabled by
selecting the Maintenance application, expanding the Administration and Soft-
ware Licensing entities, entering a right click on Feature Management and
selecting Edit Feature.
In addition to configuring PTP options, alarm attributes are editable when the
PTP application is selected (see Precision Time Protocol (PTP) Alarms
(GE114S/GE114SH) on p. 551).
Transparent Clock Provisioning Order

PTP configuration options are created in the following order for Transparent
Clock:
• Create / Edit a Transparent Clock
• Edit Ethernet Port’s Delay Asymmetry
Telecom Slave Provisioning Order

PTP configuration options are created in the following order for Telecom Slave:
• Create a flow on the Associated Port (must be In Service)
• Create / Edit a Telecom Slave
• Create / Edit a Slave Only Ordinary Clock (SOOC)
• Create / Edit a PTP Flow Point (PTPFP)
• Create / Edit an Ordinary Clock Slave (OCS) Port
• Edit Ethernet Port’s Delay Asymmetry
• Add a sync reference and associate the Telecom Slave entity to the Sync
Reference (SYNC-1-1-1-1)
• Associate the Telecom Slave entity to the desired Clock, PPS and/or TOD
interface
• Edit System Time of Day (TOD) via PTP Clock
Boundary Clock Provisioning Order

A Boundary Clock and Master Clock cannot co-exist. Only one or the other may
be provisioned and In Service at a time.
PTP configuration options are created in the following order for Boundary Clock:


• Create / Edit a Boundary Clock
• Create / Edit a Master Clock Interface
• Create / Edit a Master Virtual Port
• Create / Edit a Static Slave or Edit / Delete a Dynamic Slave
Master Clock Provisioning Order (GE114SH Only)

PTP configuration options are created in the following order for Master Clock:
• Edit the Time Clock (see Synchronization (GE114S/GE114SH))
• Add a Time Clock Reference (see Synchronization (GE114S/GE114SH))
• Create / Edit a Master Clock
• Create / Edit a Master Clock Interface
• Create / Edit a Master Virtual Port
• Create / Edit a Static Slave or Edit / Delete a Dynamic Slave

Transparent Clock Parameters

Create / Edit a Transparent Clock
A Transparent Clock may be created by selecting the PTP icon on the Tool Bar
or selecting PTP from the Applications menu, expanding the system folder in the
Selection Tree, entering a right click on the NE-1 entity and selecting Create
Transparent Clock. To edit a Transparent Clock, enter a right click on the Trans-
parent 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.
Table 86: Create/Edit Transparent Clock Parameter Settings
Parameter
TC ID (Create Transparent Clock Identifier
1-32
only)
Alias A text and/or number string the user enters to uniquely
up to 64 characters
identify this entity. This string can be up to 64 printable
(blank)
ASCII characters long.
Administrative Enables or disables the Transparent Clock. When an IS
State entity is in the In Service state, it is fully operational. See

Management
Entity State Descriptions on p. 599.
Clock Identity Clock Identity of the Transparent Clock. A Clock Identity
(Create only) is automatically created by the system but this value can <varies>
be edited.
Service ID Flow Identifier to associate with this Transparent Clock. (drop down list of
(Create only) provisioned Flow
IDs)
Delay Delay Mechanism type to associate with this
Mechanism Transparent Clock (only End to End is supported). End to End
(Create only)
Access PTP Defines the Access PTP Flow Point ID.
Flow Point ID 1-32
(Create only)
Network PTP Defines the Network PTP Flow Point ID.
Flow Point ID 1-32
(Create only)

Edit Ethernet Port’s Delay Asymmetry

Figure 380: Edit Ethernet Port’s Delay Asymmetry Parameter
Parameter
Delay Delay Asymmetry is the asymmetry in the delay of the
Asymmetry path connected to the ingress port and path connected to
the egress port. This value is the half the difference
between the delay of path terminating at the ingress port -1000000000 -
and the path originating at the egress port. If the delay 1000000000
asymmetry is not zero, the value shall be positive if the 0
delay of the path terminating at the ingress port is (nanoseconds)
greater than the delay of the path originating at the
egress port and negative otherwise. The range is -1s to
1s.
Telecom Slave Parameters

PTP configuration options are created in the following order for Telecom Slave:
• Create / Edit a Slave Only Ordinary Clock (SOOC)
• Create / Edit an Ordinary Clock Slave (OCS) Port
• Add a sync reference and associate the Telecom Slave entity to the Sync
Reference (SYNC-1-1-1-1)
• Associate the Telecom Slave entity to the desired Clock, PPS and/or TOD
interface
• Edit System Time of Day (T0D) via PTP Clock

Create / Edit a Telecom Slave

A Telecom Slave may be created by selecting the PTP icon on the Tool Bar or
selecting PTP from the Applications menu, expanding the system folder in the
Selection Tree, entering a right click on the NE-1 entity and selecting Create
Telecom Slave. 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.
Table 87: Create/Edit Telecom Slave Parameter Settings
Parameter
up to 64 characters
(blank)
Clock Identity Indicates the local clock identity in 64 bits UUID.
<varies>
(Create only)
Administrative Enables or disables the Telecom Slave. When an entity IS
State is in the In Service state, it is fully operational. See Entity
State Descriptions on p. 599. Management
PTP Domain This PTP domain number which the Master Clock partic-
Number ipates in. It is used in the domainNumber field of the PTP 0-255
(Create only) header in the PTP packet generated by the SOOC.
Clock Recovery Selects one way or two way clock recovery mode. One Way
Mode • One way: delay request/response messages are not
used and in this mode only frequency can be recov-
ered. (only sync message)
Two Way
• Two way (default): delay request/response will be
used and in this mode frequency and/or phase/time
can be recovered
Time Holdover Selects the time holdover accuracy in nanoseconds for 500
Accuracy (ns) the telecom slave. The Holdover state is entered when 1000
Telecom Slave is currently locked to the Master Clock 1500
and when the active SOOC’s OC-S PTP Virtual Port
5000
goes to LISTENING or UNCALIBRATED. In this state
the phase lock can be sustained for certain amount of
time specified as Holdover time before the accuracy
becomes insufficient for holdover accuracy requirement. 10000
The provisioned value and the assembled oscillator
stability co-determine the Holdover time.

Table 87: Create/Edit Telecom Slave Parameter Settings (Continued)

Parameter
Sync Reference Enable or Disable allowing the Telecom Slave to be Disabled
used as Sync Reference. Default is Disabled.
• If set to Enabled, the TS port is available as a possi-
ble reference for the system Sync object.
• If set to Disabled, the TS port is not available as a Enabled
possible reference for the system Sync object
(SYNC-1-1-1-1). The system Sync object may be
used to drive PTP if this option is disabled AND
SYNC-1-1-1-1 is selected in the Sync ID option.
QL Mode Specifies whether the Ethernet Network Port is enabled Disabled
or disabled for Quality Level (QL) Mode. This option is Enabled
only applicable for Synchronous Ethernet capable ports,
when this option is set to Enabled.
When enabled, on receive side:

-port shall PEER the Synchronization Status Messages
(SSM) slow protocol PDUs and take appropriate action
When enabled, on transmit side:
-port shall periodically (once a second) transmit QL TLV
information PDUs
When disabled, on receive side:

-port shall terminate and discard any SSM slow protocol
PDUs
When disabled, on transmit side:

-port shall not transmit any SSM slow protocol PDUs
Sync ID Selects an external driver for PTP. If Sync Reference is None
set to Disabled AND SYNC-1-1-1-1 is selected, then SYNC-1-1-1-1
SYNC-1-1-1-1 is used to drive PTP. If Sync Reference is
set to Enabled, then only None is applicable. Sync ID is
not editable when an SOOC is associated with the TS.

Table 87: Create/Edit Telecom Slave Parameter Settings (Continued)

Parameter
Assumed QL Specifies the assumed Quality Level (QL) on the QL-PRC
Ethernet Network Port. This object is only applicable for QL-SSU-A
Synchronous Ethernet capable ports. The Assumed QL QL-SSU-B
is only applicable if the Network Clock Type is “option1” -
SDH and the port’s QL Mode is disabled and the port is
being used as an input reference source. Under these
conditions, the specified QL value is assumed to be the
Quality Level of the non-failed reference.
Choices available depend on the Network Clock Type

setting - “option1 - SDH” or “option2 - SONET.” If
“option1 - SDH” is selected, there has to be an Assumed
QL in case the selected sync reference does not support QL-EEC1
SSM. For “option2 - SONET,” the Assumed QL is
automatically set to “QL-STU” and is not editable. If the
Network Clock Type is changed from “option2 - SONET”
to “option1 - SDH,” the “assumed_ql” defaults to
“QL-EEC1.”
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A,

QL-SSU-B, QL-EEC1. Default is QL-EEC1.
Expected QL Specifies the expected Quality Level (QL) when the QL-NONE
Ethernet Network Port is enabled for QL Mode. This QL-PRC
object is only applicable for Synchronous Ethernet QL-SSU-A
capable ports, when QL Mode is Enabled. This option
QL-SSU-B
allows the user to set a minimum 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 Level is not expected.
Choices available depend on the Network Clock Type

setting - “option1 - SDH” or “option2 - SONET.”
QL-EEC1
The default value is QL-NONE. If the Network Clock
Type is changed, Expected QL defaults to
“QL-NONE” regardless of previous setting.
Valid entry for SDH Network Clock: QL-PRC, QL-SSU-A,

QL-SSU-B, QL-EEC1, QL-NONE. Default is QL-NONE.

Create / Edit a Slave Only Ordinary Clock

(SOOC)
Once a Telecom Slave has been created, a Slave Only Ordinary Clock (SOOC)
may be created by entering a right click on the TS-1-n entity and selecting Cre-
ate SOOC. 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.
Table 88: Create/Edit SOOC Parameter Settings
Parameter
up to 64 characters
(blank)
Administrative Enables or disables the Telecom Slave. When an entity IS
State is in the In Service state, it is fully operational. See Entity
Management
State Descriptions on p. 599.
Flow ID (Create Flow Identifier to associate with this SOOC. (drop down list of
only) provisioned Flow
IDs)
Slave IP The IP Address of the SOOC.
Address (Create 0.0.0.0
only)
Slave Subnet The Slave subnet mask.
Mask (Create 0.0.0.0
only)
Interface Name Name for this SOOC interface (mandatory entry).
(blank)
(Create only)
Unicast Enable/Disable Unicast Message Negotiation. When Enabled
Message Enabled the following provisioned rates are used in the
Negotiation negotiation between the master and slave (in the
(Create only) signaling massage). When Disabled, the following Disabled
provisioned rates are used for manually calculating the
negotiation intervals.
Unicast Timeout Unicast timeout (in seconds). 1
Unicast Restart Unicast restart timer (in seconds).
60
Timer
Priority Mode Priority mode for transmitted packets. None
TOS
DSCP
Priority Priority for transmitted packets. 0-7
Master Delay Master Delay Mechanism. Only End to End is supported.
Mechanism End to End
(Create only)
Master Priority Master priority. 0-7

Table 88: Create/Edit SOOC Parameter Settings (Continued)

Parameter
Master Protocol Master protocol. Only IPv4 is applicable.
IPv4
(Create only)
Master Clock IP Master Clock IP Address.
Address (Create 0.0.0.0
only)
Master Selects the mean time interval between successive 1 Packet Per 16
Announce Announce messages. Seconds
Message Rate 1 Packet Per 8
(Create only) Seconds
1 Packet Per 4
Seconds
1 Packet Per 2
Seconds
1 Packet Per 1
Second
2 Packets Per 1
Second
4 Packets Per 1
Second
8 Packets Per 1
Second
Master Indicates how long (in seconds) for the GrandMaster to
Announce send the announce packet. 2-255 (secs)
Receipt Timeout
Master Delay Selects a minimum mean time interval in which the Mas- 1 Packet Per
Response ter Clock responds to successive Delay Request pack- Second
Message Rate ets. 2 Packets Per
(Create only) Second
4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second
Master Delay Master Delay Response Receipt Timeout.
Response 2-255 (secs)
Receipt Timeout

Table 88: Create/Edit SOOC Parameter Settings (Continued)

Parameter
Master Sync Selects a mean time interval between successive Sync 1 Packet Per
Message Rate messages. Second
(Create only) 2 Packets Per
Second
4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second
Master Sync Master Sync Receipt Timeout.
2-255 (secs)
Receipt Timeout
Master Lease Master Lease Duration.
60 - 1000 (secs)
Duration
300
(Create only)
Create / Edit a PTP Flow Point (PTPFP)

Once a SOOC has been created, a PTP Flow Point (PTPFP) may be created by
expanding the NTE114S/NET114SH entity in the Selection Tree, entering a
right click on the associated port entity and selecting Create PTPFP. 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.
Table 89: Create/Edit PTP Flow Point Parameter Settings
Parameter
PTPFP ID Transparent Clock Identifier
1-33
(Create only)
up to 64 characters
(blank)
Administrative Enables or disables the Transparent Clock. When an IS
State entity is in the In Service state, it is fully operational. See
Management
Entity State Descriptions on p. 599.

Table 89: Create/Edit PTP Flow Point Parameter Settings (Continued)

Parameter
PTP FlowPoint Defines the Flowpoint as either an OC Slave or OC OC Slave
Type Master. For Telecom Slave, select OC Slave; for
OC Master
Boundary Clock/Master Clock, select OC Master
Flow ID (Create Flow Identifier to associate with this Transparent Clock. (drop down list of
only) provisioned Flow
IDs)
Untagged Check Defines whether the VLAN configuration is untagged or Selected
Box (Create tagged. Selecting this option sets Untagged VLAN
Unselected
only) configuration.
Outer VLAN Defines whether the Outer VLAN tag entry is allowed. Selected
Check Box Only selectable if the Untagged check box is unselected.
Unselected
(Create only)
Outer VLAN Defines the Ethertype for the Outer VLAN tag.
Ethertype 0
(Create only)
Outer VLAN Tag Defines the VLAN tag and priority that will be associated 1 to 4095
(Create only) with this PTP Flow Point Outer VLAN Tag. 0 to 7
Inner VLAN1 Defines whether the Inner VLAN1 tag entry is allowed. Selected

(Create only) Unselected
Inner VLAN1 Defines the Ethertype for the Inner VLAN1 tag.
Ethertype 0
(Create only)
Inner VLAN1 Defines the VLAN tag and priority that will be associated 1 to 4095
Tag (Create with this PTP Flow Point Inner VLAN1 Tag.
0 to 7
only)
(Create only) Unselected
Outer VLAN Defines the Ethertype for the Inner VLAN2 tag.
Ethertype 0
(Create only)
Outer VLAN Tag Defines the VLAN tag and priority that will be associated 1 to 4095
(Create only) with this PTP Flow Point Inner VLAN2 Tag. 0 to 7

Create / Edit an Ordinary Clock Slave (OCS)

Port
Once a PTPFP has been created, an Ordinary Clock Slave (OCS) Port may be
created by expanding the SOOC entity in the Selection Tree, entering a right
click on the SOOC entity and selecting Create OCS Port. To edit aOCS 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.
Table 90: Create/Edit OCS Port Parameter Settings
Parameter
up to 64 characters
(blank)
PTP Flow Point PTP Flow Point Identifier to associate with this Ordinary (drop down list of
(Create only) Clock Slave Port. The Service Flow associated with Flow provisioned PTP
Point and SOOC must be the same. Flow Point IDs)

Create / Edit a Boundary Clock

A Boundary may be created by selecting the PTP icon on the Tool Bar or select-
ing PTP from the Applications menu, expanding the system folder in the Selec-
tion Tree, entering a right click on the NE-1 entity and selecting Create
Boundary Clock. To edit a Boundary Clock, enter a right click on the Boundary
Clock entity (e.g., BOUNDARY CLOCK-1-1) and select Edit.
To delete a Boundary Clock, enter a right click on the Boundary Clock entity and
select Delete.
Table 91: Create/Edit Boundary Clock Parameter Settings
Parameter
Boundary Clock The index number of the Boundary Clock. Up to two
Index (Create Boundary Clocks may be created per system. 1
only)
up to 64 characters
(blank)
Use Selected Select the “Use Selected Telecom Slave Clock Identity Selected
Telecom Slave Check Box” if its clock identity is to be used.

Clock Identity
Unselected
Check Box
(Create only)
Clock Identity Entry of a Clock Identity of the Telecom Slave is
(Create only) permitted if the “Use Selected Telecom Slave Clock
(varies)
Identity Check Box” is not selected. Entry is 16 HEX
characters.
Administrative Enables or disables the Boundary Clock. See Entity IS
State State Descriptions on p. 599. Management
Timing Source Selects the provisioned Telecom Slave timing source. None
(Create only) (drop-down list)
PTP Domain This PTP domain number is used in the domain Number
Number (Create field of the PTP header in the PTP packet. This PTP
0-127
only) domain number is used when PTP packet is generated
by the SOOC.

Create / Edit a Master Clock

ing PTP from the Applications menu, expanding the system folder in the Selec-
tion Tree, entering a right click on the NE-1 entity and selecting Create Master
Clock. To edit a Master Clock, enter a right click on the Master Clock entity (e.g.,
MASTER CLOCK-1-1) and select Edit.
To delete a Master Clock, enter a right click on the Master Clock entity and
select Delete.
Table 92: Create/Edit Master Clock Parameter Settings
Parameter
Master Clock The index number of the Boundary Clock. Up to two
Index (Create Master Clocks may be created per system. 1-2
only)
up to 64 characters
(blank)
Clock Identity The Master Clock’s Clock Identity. Entry is 16 HEX
(varies)
(Create only) characters.
Administrative Enables or disables the Boundary Clock. See Entity IS
PTP Domain This PTP domain number is used in the domain Number
Number (Create field of the PTP header in the PTP packet. 0-127
only)
Priority 1 Priority 1 (based on IEEE 1588v2). 0-255
128
Priority 2 Priority 2 (based on IEEE 1588v2). 0-255
128
Timing Clock Eid The timing reference of the Master Clock.
(drop-down list)
(Create only)

Create / Edit a Master Clock Interface

ing PTP from the Applications menu, expanding the system folder and Bound-
ary Clock entities in the Selection Tree, entering a right click on the Boundary
Clock entity and selecting Create Master Clock Interface. To edit a Master Clock
Interface, enter a right click on the Master Clock Interface entity (e.g., MASTER
CLOCK INTERFACE-1-1-1) and select Edit.
To delete a Master Clock Interface, enter a right click on the Master Clock Inter-
face entity and select Delete.
Table 93: Create/Edit Master Clock Interface Parameter Settings
Parameter
Master Clock The index number of the Master Clock Interface. Up to
Interface Index Four Master Clock Interfaces may be created per 1-4
(Create only) system.
up to 64 characters
(blank)
Administrative Enables or disables the Master Clock Interface. See IS
State Entity State Descriptions on p. 599. Management
IP Protocol IP Protocol.
IPv4
(Create only)
Master Clock Valid IPv4 address. The IP address must be unique
Interface IP across all IP interfaces in the system.
0.0.0.0
Address
(Create only)
Master Clock Valid IPv4 subnet mask.
Interface Subnet
0.0.0.0
Mask
(Create only)
Interface Name When an Master Clock Interface is created, an IP
(Create only) interface is created with the Interface Name, IP Address
and Subnet Mask. The IP address and Interface Name
(blank)
must be unique across all IP interfaces in the system.
The interface name is from 1 to 15 alphanumeric
characters (no spaces). This entry is mandatory.
Priority Mode Defines the Priority Mode. It identifies the lookup criteria None
(Create only) for the priority mapping table. This table is used to TOS
perform priority based lookup (to determine low and
normal latency) and/or to change the priority value. DSCP
Priority (Create Priority Map Index Selection. The following ranges of 0
only) Indexes are: 0...7 if Priority Mode is set to TOS; 0...63 if 0-7 (TOS)
Priority Map Mode is set to DSCP. 0-63 (DSCP)
Clock Type Selects the Clock Type. Only One Step is applicable in
One Step
(Create only) this release.
Delay Selects the Delay Mechanism. Only End to End is
Mechanism applicable in this release. End to End
(Create only)

Table 93: Create/Edit Master Clock Interface Parameter Settings (Continued)

Parameter
Max Slaves Maximum Slaves Supported
Supported 1
(Create only)
Max Static Maximum Static Slaves Supported
Slaves
0
Supported
(Create only)
Max Announce Maximum Announce Message Rate 1 Packet Per 16
Message Rate Seconds
(Create only) 1 Packet Per 8
Seconds
1 Packet Per 4
Seconds
1 Packet Per 2
Seconds
1 Packet Per 1
Second
Max Sync Maximum Sync Message Rate 1 Packet Per
Message Rate Second
Second
4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second

Table 93: Create/Edit Master Clock Interface Parameter Settings (Continued)

Parameter
Max Delay Maximum Delay Response Message Rate 1 Packet Per
Response Second
Message Rate 2 Packets Per
(Create only) Second
4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second
Max Lease Maximum Lease Duration
60 - 1000 (secs)
Duration (Create
300
only)
Create / Edit a Master Virtual Port

Once a PTPFP has been created, a Master Virtual Port may be created by
expanding the Boundary Clock entity in the Selection Tree, entering a right click
on the Boundary Clock entity and selecting Master Virtual Port. To edit a Master
Virtual Port, enter a right click on the Master Virtual Port entity (e.g., MASTER
VIRTUAL PORT-1-1-1-1) and select Edit.
To delete a Master Virtual Port, enter a right click on the Master Virtual Port
entity and select Delete.
Table 94: Create/Edit Master Virtual Port Parameter Settings
Parameter
up to 64 characters
(blank)
PTP Flow Point PTP Flow Point Identifier to associate with this Master (drop down list of
(Create only) Virtual Port. The Service Flow associated with Flow provisioned PTP
Point and Master Virtual Port must be the same. Flow Point IDs)

Create / Edit a Static Slave

Once a Master Virtual Port has been created, a Static Remote Slave may be
created by expanding the Boundary Clock and Master Clock Interface entities in
the Selection Tree, entering a right click on the Static Slave entity and selecting
Create Static Slave. 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.
The number of Static Slaves that may be created is dependent on the Max
Slaves Supported and Max Static Slaves Supported entries made when creat-
ing the Master Clock Interface (up to 4). If the PTP-MC/BC feature is enabled,
number of remote slaves is extended from 4 to up to 16 at the maximum PTP
message rate.
To delete a Static Slave, enter a right click on the Static Slave entity and select
Delete.
Table 95: Create/Edit Static Slave Parameter Settings
Parameter
Static Remote The index number of the Static Remote Slave.
Slave Index 1-4
(Create only)
up to 64 characters
(blank)
Administrative Enables or disables the Static Remote Slave. See Entity IS
Static Remote Valid IPv4 address. The IP address must be unique
Slave IP across all IP interfaces in the system.
0.0.0.0
Address
(Create only)
Unicast Unicast Message Negotiation Enabled
Message
Negotiation Disabled
(Create only)
Announce Announce Message Rate. (Applicable only if Unicast 1 Packet Per 16
Message Rate Message Negotiation is Disabled.) Seconds
(Create only) 1 Packet Per 8
Announce Message Rate cannot be greater than the
associated MCI Max Announce Message Rate. Seconds
1 Packet Per 4
Seconds
1 Packet Per 2
Seconds
1 Packet Per 1
Second

Table 95: Create/Edit Static Slave Parameter Settings (Continued)

Parameter
Sync Message Sync Message Rate. (Applicable only if Unicast Mes- 1 Packet Per
Rate (Create sage Negotiation is Disabled.) Second
only) 2 Packets Per
Sync Message Rate cannot be greater than the associ-
ated MCI Max Sync Message Rate. Second
4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second
Delay Response Delay Response Message Rate. (Applicable only if 1 Packet Per
Message Rate Unicast Message Negotiation is Disabled.) Second

Delay Response Message Rate cannot be greater than Second
the associated MCI Max Response Message Rate. 4 Packets Per
Second
8 Packets Per
Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second

Edit / Delete a Dynamic Slave

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. The number of Dynamic Slaves that
may be created is dependent on the Max Slaves Supported entries made when
creating the Master Clock Interface (up to 4). If the PTP-MC/BC feature is
enabled, number of remote slaves is extended from 4 to up to 16 at the maxi-
mum PTP message rate.
To delete a Dynamic Slave, enter a right click on the Dynamic Slave entity and
select Delete.
Table 96: Create/Edit Dynamic Slave Parameter Settings
Parameter
up to 64 characters
(blank)
Administrative Enables or disables the Static Remote Slave. See Entity IS

SAT Configuration Options and Rules

The following section describes Service Activation Testing (SAT) option set-
tings. The options described in this section are performed using the SAT appli-
cation (located on the Tool Bar or selectable via the Application menu).
Edit SAT System

The SAT System entity is provisioned as default by the system. Only one SAT
System entity is supported per system and it’s not allowed to delete the SAT
System entity. To edit the SAT System, enter a right click on the SAT System
entity and select Edit.
Table 97:\Edit SAT System Parameter Settings

Parameter
EtherType The EtherType used in Frame Loss Protocol Date Unit 0x600...0xffff
(FLPDU). 9800(hex)
Create/Edit SAT Control

The SAT Control Entity is created by entering a right click on the NE-1 entity and
selecting Create SAT Control. Only one SAT Control entity is supported per sys-
tem. A SAT Control entity may be created, edited and deleted. To Edit a SAT
Control entity, right click on the entity and select Edit; To delete a SAT Control
entity, right click on it and select Delete.
Table 98: Create/Edit SAT Control Parameter Settings

Parameter
Name Name the SAT Control entity with a string of up to 16
(blank)
ASCII characters.
Test Mode Select the test mode. In unidirectional mode (one way), One Way
the SAT Control end need negotiate with the remote SAT
Responder end before starting transmitting test frame. In
this case, the SAT Responder Control should be enabled
at the Responder MEP. In round-trip mode (two way), Two Way
the SAT Control end does not need negotiation with the
remote SAT Responder end; instead a loopback should
be initiated on proper port or VID at the Responder end.

Table 98: Create/Edit SAT Control Parameter Settings (Continued)

Parameter
Test Procedure Select the desired test procedures by selecting or CIR
List unselect the checkbox next to each test type.By default, EIR
CIR, EIR, Policing and Performance tests are all Policing
selected. CBS and DBS are not supported in current
release. Performance
CIR Test Step Configure the duration for CIR step test. 1 - 60 (sec)
Duration 20
CIR Test Step Configure the number of steps that the CIR Test will
1 - 10
Number perform.
Test Duration Configure the duration for EIR or Policing test. 1 - 86400 (sec)
20
Performance Configure the duration for Performance test. Suggested 1 - 1440 (min)
Test Duration values are 15 min, 120 min and 1440 min. 15
Create/Edit SAT Test Stream

Up to four SAT Test Streams are supported per system in GE11x. The test
streams may belong to different flows, or same flow but different COS depend-
ing on the VID and priority in the stream.
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.
Table 99: Create/Edit SAT Test Stream Parameter Settings

Parameter
SAT Test The index number of the test stream to be created. The
1- 4
Stream Index system will automatically assign it in order.
Name Name the test stream with a string up to 64 ASCII
(blank)
characters.
Port Select the associated port of the flow the test stream is to ACCESS
test. Since the four test stream can only be used to test PORT-1-1-1-3
the different flows or different COS under the same flow, (dropdown list of
the port specified in different test stream should be available Ethernet
consistent. ports)
Local MEP Select the local UP MEP EID associated with the flow to (dropdown list of
be tested. The Local MEP will be used to initiate control available MEP EIDs
protocol and run Delay Measurement (DM). on the selected
Port)

Table 99: Create/Edit SAT Test Stream Parameter Settings (Continued)

Parameter
Destination MEP Select using MEP Id or MAC Address to identify the MEP Id
Type destination MEP. MAC Address
Destination MEP Enter the ID of the destination MEP used to terminate 0
ID control protocol and run Delay Measurement, if (valid MEP ID
Destination MEP Type is MAC Id. number)
Destination Enter the MAC address of the destination MEP used to
MEP’s MAC terminate control protocol and run delay measurement. if 00:00:00:00:00:00
Address Destination MEP Type is MAC Address.
Direction Select the desired test direction of this test stream. The Forward
test direction has no effect on the settings on SAT
Control end and the SAT Responder end. The SAT
Responder Control should always be enabled on the
Responder end in one-way mode. The different test Backward
direction only affects the FLPDU transmission direction.
This option is meaning less if test mode is two way.
DMM Frame Define the frame size (in bytes) for Delay Measurement 64 - MTU
Size Message (DMM). 128 (Bytes)
DMM Interval Select the desired DMM transmission interval, wherein 10 Milliseconds
10 ms and 100 ms are not supported on GE112. 100 Milliseconds

1 Second
10 Seconds
1 Minute
Service Select the desired Service Acceptance Criteria (SAC) SAT SAC
Acceptance Profile for the CIR test result to compare against. PROFILE-1
Criteria Profile (dropdown list of the
four SAT SAC EIDs)
Destination MAC Specify the MAC Address for the destination the FLPDU
Address stream reaches. This value can be any or left blank if the
Control end and the Responder end are both ADVA
equipment and there are no other devices between
them. If there are layer-2 network devices between the 00:00:00:00:00:00
Control end and the Responder end, this value is the (valid MAC address)
same as the Destination MEP’s MAC Address; If there
are layer-3 network devices between the Control end
and the Responder end, this value should be the MAC
address of the forwarding port at the next hop.
Payload Type Select the desired payload type for the test stream. PRBS31
CUSTOM
Custom Payload Enter the customized payload as hex format, and up to
16 characters (0 -9, a - f, A - F) are supported. The input
55AA55AA55AA55
string are converted to 8 bytes when filling in frame. The
AA
system will fill zero to complete 8 bytes if user has not
(hex)
configured enough bytes. This option is only available
when Payload Type is set to CUSTOM.
Frame Size List Customize the frame size (in bytes) or select fixed frame
512 (Bytes)
size pattern by clicking on EMIX or EMIX Default button.


Parameter
Color Mode Set the test stream to either Color Aware or Color Blind. Color Aware
• If Color Mode is set to Color Aware:
o DEI can be enabled or disabled.
o Green PCP will be used as the priority of green
frames’ outer VLAN tag;
o Yellow PCP will be used as the priority of yellow
frames’ outer VLAN tag, the priority of SAT con-
trol protocol PDU and the priority of SAT
DMM/DMR.
o Outer VLAN Tag specifies the outer VLAN ID of Color Blind
FLPDU (included in flow’s VLAN member list)
• If Color Mode is set to Color Blind:
o
DEI can only be disabled.
o
Green PCP and Yellow PCP are not applicable
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.
DEI Enable/Disable the Drop Eligibility Indicator. Disabled
• In Color Aware mode:
o
if DEI is enable:
• Generate Test Function (GTF) will set DEI
to 0 for green frames, 1 for yellow frames;
Collect Test Function (CTF) will distin-
guish color by (DEI || priority).
o
if DEI is disabled:
• GTF will set DEI to 0 for both green and Enabled
yellow frames; CTF distinguishes color
only by priority.
• In Color Blind mode:
o
DEI can only be disabled.
• GTF will set DEI to 0 for both green and
yellow frames. CTF distinguishes color
only by priority
CIR Set the green FLPDU sending rate. 0 (Kbps)
EIR Set the yellow FLPDU sending rate. 0 (Kbps)
CBS Set the FLPDU committed burst size. CBS cannot be 0
0 - 256(KBytes)
when CIR is not 0.
EBS Set the FLPDU excess burst size. EBS cannot be 0
0 - 256(KBytes)
when EIR is not 0.
Green PCP Enter the priority of the green frames’ outer VLAN tag.
0-7
Only applicable in color aware mode.


Parameter
Yellow PCP Enter the priority of the yellow frames’ outer VLAN tag,
which will also be used as the priority of the SAT Control
0-7
Protocol PDU and the priority of SAT DMM/DMR. Only
applicable in color aware mode.
Outer VLAN Defines whether the Outer VLAN tag entry is allowed. Selected
Check Box Only selectable if the Untagged check box is unselected. Unselected
Outer VLAN Defines the Ethertype for the Outer VLAN tag. 0x8100 or
8100 (hex)
Ethertype 0x88a8.
Outer VLAN Tag Defines the VLAN tag and priority that will be associated 1 - 4094
with the FLPDU. In Color Aware mode, the VLAN ID
should be included in flow’s VLAN member list; in Color
Blind mode, the VID should be same as flow’s VLAN 0-7
member and the priority will be used by SAT control
PDU, DMM/DMR and FLPDU.
8100 (hex)
Ethertype
Inner VLAN1 Defines the VLAN tag and priority that will be associated 1 - 4094
Tag with FLPDU Inner VLAN1 Tag. 0-7
8100 (hex)
Ethertype
Inner VLAN2 Defines the VLAN tag and priority that will be associated 1 - 4094
Tag with FLPDU Inner VLAN2 Tag. 0-7
Edit SAC Profile

Up to four Service Acceptance Criteria profiles are supported per system. The
SAC Profile may be edited by entering a right click on the SAC Profile entity and
selecting Edit.
Table 100: Create/Edit SAC Profile Parameter Settings

Parameter
Name Name the SAC profile with a string of up to 64 ASCII
1-4
characters.
FLR Specify the desired Frame Loss Ratio (FLR) for the test
0 - 100
rest. If the FLR of the test cannot match the value as
5
specified in SAC profile criteria, the test fails.

Table 100: Create/Edit SAC Profile Parameter Settings (Continued)

Parameter
FTD Specify the desired Frame Transmission Delay (FTD) for
the test result. If the max Frame Delay cannot match with 0 - 10000000
the value as specified in SAC profile criteria, the test 300
fails.
FDV Specify the desired Frame Delay Variance (FDV) for the
test result. If the max Frame Delay Variance cannot 0 -10000000
match the value as specified in SAC profile criteria, the 300
test fails.

FSP 150CC-GE11X R6.1 Installation and Operations Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FSP 150CC-GE11X R6.1 Installation and Operations Manual

Uploaded by

Copyright:

Available Formats

FSP 150CC-GE11x

Fiber Service Platform 150CC-

Installation and Operations

Product Release 6.1

Chapter 1 FSP 150CC-GE11x Overview . . . . . . . . . . 27

Installation and Operations Manual 3

4 Installation and Operations Manual

Chapter 2 Physical Installation . . . . . . . . . . . . . . . 123

Install the FSP 150CC-GE11x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Installation and Operations Manual 5

Chapter 3 eVision Web Browser Management Tool

6 Installation and Operations Manual

Chapter 4 Operations Provisioning . . . . . . . . . . . . 219

Installation and Operations Manual 7

8 Installation and Operations Manual

Chapter 5 Communications Provisioning . . . . . . . 399

Chapter 6 Etherjack Test Procedures and Performance

Installation and Operations Manual 9

Chapter 7 Alarms, Events and Probable Causes, Error

10 Installation and Operations Manual

Chapter 8 Provisioning Rules . . . . . . . . . . . . . . . . 599

Secondary State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

Installation and Operations Manual 11

12 Installation and Operations Manual

Figure 10: FSP 150CC-GE114x in a G.8032 Ring Application . . . . . . . . . . . 38

Installation and Operations Manual 13

14 Installation and Operations Manual

Figure 70: Install Full-width Units in Standard Rack in I-Temp Environment

Figure 81: GE114H/GE114SH/GE114PH Rear Panel Frame Ground Point. . 151

Installation and Operations Manual 15

16 Installation and Operations Manual

Figure 140: Remove Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Figure 158: Edit Access Port EFM-OAM View . . . . . . . . . . . . . . . . . . . . . . 272

Installation and Operations Manual 17

18 Installation and Operations Manual

Figure 217: Create Master Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Figure 235: Sync Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Installation and Operations Manual 19

20 Installation and Operations Manual

Figure 295: Create Management Tunnel - Bridging Enabled . . . . . . . . . . . 424

Figure 313: Delete IPv6 Static Neighbor Entry. . . . . . . . . . . . . . . . . . . . . 441

Installation and Operations Manual 21

22 Installation and Operations Manual

Figure 372: Create SAT Test Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

Installation and Operations Manual 23

Table 10: +24 VDC PSU Cable Wire Assignments . . . . . . . . . . . . . . . . . 182

Installation and Operations Manual 25

26 Installation and Operations Manual

Table 80: Maintenance Domain Configuration Settings . . . . . . . . . . . . . 754

Installation and Operations Manual 27

FSP 150CC-GE11x Overview

over a fiber-based access network in a temperature-hardened platform ideal for

Common OAM Capabilities

Installation and Operations Manual 27

28 Installation and Operations Manual

Figure 1: FSP 150CC-GE112

• 802.1ad Provider Bridge C-Tag / S-Tag Mapping

Figure 2: FSP 150CC-GE114

Installation and Operations Manual 29

Figure 3: FSP 150CC-GE114S

30 Installation and Operations Manual

• 802.1ad Provider Bridge C-Tag / S-Tag Mapping

Figure 4: FSP 150CC-GE114H

Figure 5: FSP 150CC-GE114SH