Provisioning and

Operations
OSA 5422
Product Release: 11.1.1
Document Issue: A
Document Number: 80000067459
Copyright © 2020-2022 ADVA Optical Networking
All rights reserved. Hardware and software mentioned in this document includes software developed by
ADVA Optical Networking ("ADVA"), the Apache Software Foundation (http://www.apache.org), Teodor
Danciu (http://jasperreports.sourceforge.net), and/or other open source software.

libnetconf - Copyright and Permission Notice

Copyright (c) 2012-2014 CESNET, z.s.p.o.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the Company nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.

This software is provided "as is", and any express or implied warranties, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the
company or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential
damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or
profits; or business interruption) however caused and 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 software, even if
advised of the possibility of such damage.

Patents
The content described in this document may be covered by patents or pending patent applications of ADVA.
The furnishing of this document does not give you any license to these patents.

Disclaimers
Nothing in this document shall be construed as granting any license or rights with respect to its content or the
patents and trademarks mentioned above. The content of this document may include technical inaccuracies or
typographical errors, and is subject to change at any time without notice. Reliance on this content is at the
relying party's sole risk and will not create any liability or obligation for ADVA. Any references in this document
to publications and/or Internet sites that are not from ADVA 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 information, product, or service,
and use of those publications and/or Internet sites is at your own risk.

THE CONTENT OF THIS DOCUMENT IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ADVA, ITS AFFILIATES, EMPLOYEES, OFFICERS
OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND BASED
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 2

Oscilloquartz: An ADVA Company

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE. THE SAME APPLIES FOR ANY HARDWARE OR SOFTWARE COVERED
BY THIS DOCUMENT, UNLESS A SIGNED AGREEMENT WITH ADVA OR THE APPLICABLE PRODUCT LIABILITY
LAW EXPRESSLY STATES OTHERWISE.

ADVA
Fraunhoferstr. 9a
82152 Martinsried/Muenchen
Germany
Phone +49(0)89-890665-0
Fax +49(0)89-890665-699
http://www.adva.com

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 3

Contents
Contents 4

About This Guide 14

Documentation 14
Related Documentation 15
Accessing Documentation 15
Documentation Feedback 15
Obtaining Technical Assistance 15
Customer Portal 16
Technical Services 16
Call ADVA 16
Safety Symbol and Message Conventions 17

Overview 20
Management Overview 20
Management Features 21
Provisioning Communications 21
User Management and Security 21
Managing Local User Profiles 22
Managing SNMP Users 23
Access Control Lists 23
Custom Security Banner 23
RADIUS or TACACS+ 23
Provisioning Operations 24
Provisioning System Options 24
Provisioning Network Elements 24
Provisioning Secure Access 25
Provisioning Alarms 25
Provisioning Performance Monitoring 25

Element Management System 26

Minimum System Requirements 28
Logging In, Logging Off, and User Session Timeouts 30
Logging In 30
Logging Off 32

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 4

Oscilloquartz: An ADVA Company Contents

User Session Timeout 32

Getting to Know the User Interface 33
Title Bar 34
Menu Bar 34
Toolbar 34
Tree Pane 34
Details Pane 35
Alarms Pane 36
Keyboard Navigation 37
EMS Applications 41
Configuration View 41
Maintenance View 44
Managing Database Configuration 45

Provisioning Communications 46
Provisioning Communications 47
Implementing Management Communication to the OSA 5422 47
Signing In with User Names and Passwords 48
Connecting to the Serial Port 48
Setting Up the OSA 5422 DCN eth0 Port Through the Serial Port 49
Verifying the DHCP Status of the eth0 Port 51
Changing the DHCP Status of the eth0 Port 52
Configuring the eth0 Port 52
Verifying the IP Address of the eth0 Port 53
Verifying That HTTP and HTTPS Settings are Enabled 54
Verifying Connection with the Web-Based EMS 54
Disconnecting the Serial Port and Ending the Session 55
Accessing OSA 5422 with a Browser-Based IP Connection 55
Editing the DCN eth0 Configuration 56
Configuring the DCN as a DHCP Server 59
Configuring the DCN as a DHCP Client 60
Disabling DHCP 62
Manually Configuring the IP Address 64
Adding/Deleting IPV4 Static ARP Entries 65
Adding/Deleting IPv6 Static Routes 67
Adding/Deleting IPv6 Static Neighbor Entries 69
Adding/Deleting IPv4 Static Routes 72
Setting up a Network Example for GNE-to-SNE Over a Management Tunnel 74

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 5

Oscilloquartz: An ADVA Company Contents

Provisioning Operations 79
Provisioning the OSA 5422 79
Recommended Steps after the Initial Power On 80
Verifying the Installed Shelf and Oscillator Type 80
Entity State Descriptions 81
Administration State 81
Details about the Administration State Model 82
Understanding Parent-Child Rules 83
Understanding Many-to-One Relationships 84
Operational State 85
Secondary State 85
Upgrading the Software Version 88
Upgrading the Software Version 89
Validating the Upgrade 91
Canceling a Scheduled Activation 91
Provisioning System Options 92
Configuring the System for Optimal Security 92
Configuring the System Identity and Configuration 93
Configuring SNMP Traps Forwarding for Login or Logout 97
Configuring Logs 97
Configuring Security Logs 98
Configuring Alarm Logs 98
Configuring Audit Logs 99
Configuring System Logs 100
Configuring the Management Access Control List 102
Editing the Security Banner 103
Editing the Time Zone 104
Configuring an NTP Client 107
Configuring PTP or NTP Security for IP Addresses 109
Configuring the IP Traffic ACLs 109
Configuring the ICMPv4 and ICMPv6 Filters 112
Activating Software Licenses 115
Enabling a Software License 116
Provisioning Common Units 117
Configuring NE-1 117
Configuring NTEOSA 5422 119
Configuring PSUs 120
Provisioning the Display Card 121
Provisioning Line Cards 122

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 6

Oscilloquartz: An ADVA Company Contents

Provisioning a BITS-X16 Line Card 123

Provisioning a CLK-X16 Line Card 126
Provisioning a PPS-X16 Line Card 128
Provisioning a TOD-PPS-X16 Line Card 130
Provisioning an GE-4S Line Card 132
Provisioning an IRIG-B Line Card 134
Provisioning an LPN Line Card 138
Provisioning Secure Access 140
Configuring the Security Policy 141
Configuring Local Users 142
Adding a User 143
Editing User Data 144
Changing a User Password 145
Deleting a User 145
Unlocking Users 146
Configuring Remote Authentication to the Device 147
Configuring Data Anonymity 151
Managing Certificates 152
Configuring Security Keys 153
Copying an SSL Certificate from a Remote Source 155
Copying a Private Key from a Remote Source 156
Copying an Encrypted Private Key from a Remote Source 156
Copying an SSL Certificate and Private Key from a Remote Source 157
Setting the SSL Certificate Key Pair 158
Trusting Root CA Certificates 158
Editing an HTTPS SSL Certificate Expiry Notification Period 159
Manually Enrolling a Certificate 159
Generating and Deleting RSA Key Pairs 159
Generating Certificate Signing Requests 160
Copying Certificate Signing Requests to a Remote Computer 160
Deleting Certificate Signing Requests 160
Automatic Certificate Enrollment 161
Creating Cetificate Authority Profiles 161
Editing and Deleting CA Profiles 162
Creating a Certification Authority 163
Starting Automatic Enrollment 163
Getting Certificate Authority Certificates 164
Deleting a Certification Authority 164
Provisioning SNMP Access 164

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 7

Oscilloquartz: An ADVA Company Contents

Provisioning Access Ports 164

Detailed Access Port Configuration Options and Rules 167
Provisioning Synchronization 168
Editing the System Sync 171
Editing a Time Clock 172
Editing the BITS-IN Entity 175
Editing BITS-OUT 177
Editing Clock Ports 179
Editing PPS Ports 181
Editing ToD & PPS Ports 182
Provisioning the GNSS Receiver 185
Editing a GNSS Port 186
Setting Location Control 194
Viewing Tracked GNSS Satellite Data 196
Restarting the Survey During Run-time 196
Calculating the Elevation Value 197
Resetting the GNSS Receiver 197
Editing the System Time of Day Using NTP or the Time Clock Configuration 198
Editing the System ToD Using NTP 198
Editing the System ToD Using the Time Clock 199
Editing Synchronous Ethernet on Access Ports 199
Detailed Sync-E Configuration Options and Rules 201
Adding a Time Clock Reference 204
Operating e-PRTC Mode for a Time Clock Reference 206
Adding a Sync Reference 209
Editing a Sync Reference 211
Deleting a Sync Reference 212
Provisioning the Network Time Protocol 212
Creating an NTP Flow Point 213
Creating an NTP Clock 213
Setting up NTP Peering 215
Activating Symmetric Key NTP Authentication 215
Activating Autokey Authentication 219
Creating an NTP Clock Interface 220
Creating an NTP Virtual Port 223
Provisioning the Precision Time Protocol 225
Layer 3 PTP G.8265.1 or G.8275.2 Grandmaster Clock Provisioning Order 226
Layer 3 PTP G.8265.1 Telecom Slave Provisioning Order 226
Layer 3 PTP G.8275.2 Telecom Slave Provisioning Order 227

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 8

Oscilloquartz: An ADVA Company Contents

Layer 3 PTP Enterprise Profile or Default Profile Slave Clock Provisioning Order 227
Layer 3 Enterprise or Default Profile Grandmaster Clock Provisioning Order 227
Layer 3 PTP G.8265.1 and G.8275.2 Boundary Clock Provisioning Order 229
Layer 3 PTP Broadcast Profiles Master Clock Provisioning Order 229
Layer 3 PTP Broadcast Profiles Master Clock Provisioning Order 230
Layer 2 PTP Multicast G.8275.1 and Default Profile Grandmaster Clock Provisioning
Order 231
Layer 2 PTP Multicast G.8275.1 Boundary Clock and Slave Clock Provisioning Order 231
Layer 2 PTP Power Profiles Grandmaster Clock Provisioning Order 232
PTP Procedures 233
Editing the Delay Asymmetry Setting of an Ethernet Port 233
Creating a Telecom Slave 234
Creating a Slave-Only Ordinary Clock 236
Creating a PTP Flow Point 239
Creating an Ordinary Clock Slave Port 240
Creating a Boundary Clock 243
Steps for Creating a Boundary Clock 244
Creating a Master Clock Interface 245
Creating a Master Virtual Port 249
Creating Layer 3 PTP Master Clock 249
Creating G.8275.2 or G.8265.1 Static Remote Slave 253
Validating MCI Dynamic Remote Slave 256
Verifying a Dynamic Remote Slave Connectivity 257
Creating a PTP Clock 260
Verifying Remote Slave Connectivity 263
Creating a Power Profile Grandmaster Clock 264
Creating a PTP Flow Point 267
Creating a PTP Port 270
Creating an L3 PTP Port 275
PTP Configuration Parameter Options 280
Telecom Slave Parameter Options 280
Slave Only Ordinary Clock Parameter Options 285
PTP Flow Point Parameter Options 290
Ordinary Clock Slave Port Parameter Options 292
Boundary Clock Parameter Options 293
Master Clock Parameter Options 294
Master Clock Interface Parameter Options 295
Master Virtual Port Parameter Options 299
Static Slave Parameter Options 299

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 9

Oscilloquartz: An ADVA Company Contents

Dynamic Slave Parameter Options 301

PTP Clock Parameter Options 302
PTP Port Parameter Options 306
Provisioning Rules 309
Factory Default Parameters and Maximum Bandwidth 309
System Configuration Options and Rules 323
System Configuration 323
Network Element Configuration 333
NTEOSA 5422 Configuration 334
Access Ports 339
Synchronization 350
System Configuration Settings 368
Communications 368
SNMP 373
Administration 376
Syncjack Configuration Options and Rules 384
Clock Accuracy Parameters 384
Clock Analysis Parameters 389
Telecom Slave Parameters 394
PTP Network Analysis Parameters 395
Scheduled Syncjack Activity Settings 398
Result Analysis Parameters 400
Raw Data Collection Parameters 401

Maintenance Operations 402

Modifying Default Alarms Notification Codes 402
Pinging an IP Address 403
Implementing Traceroute 405
Flushing the ARP Cache 406
Flushing the NDP Cache 407
Managing Database and Configuration Files 408
Managing ICF Configuration Files 409
Determining the Database Configuration Status 409
Setting a Default Database 410
Creating a Backup Database 415
Restoring a Database 418
Restoring System Defaults 422
Restoring Factory Defaults 424
Managing Configuration Files using CLI 425

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 10

Oscilloquartz: An ADVA Company Contents

Transferring a File (transfer-file) 426

Listing Configuration Files (list) 426
Forcing System Reset (Restart-with-configfile) 426
Running a Configuration File (load) 426
Viewing Configuration File (show ConfigFile) 426
Entering or Editing Description (description) 427
Deleting a Configuration File (remove) 427
Managing Configuration Files using Web EMS 428
Creating a New Configuration File 428
Updating an Existing Configuration File 429
Verifying the Status of the Configuration Files 430
Restarting the System with a Configuration File 430
Importing a Configuration File 431
Exporting a Configuration File 433
Editing the Description of a Configuration File 434
Deleting a Configuration File 435
Default Settings File 436
Viewing and Transferring the Last Reset Cause 438
Bulk Log Transfer 440
Managing Diagnostics Files 443
Saving Diagnostic Files 444
Copying Diagnostic Files to a Remote Repository 445

Performance Monitoring 448

Monitoring Access Ports 448
Performance Monitoring Features 449
Performance Parameters 449
Performance Parameters Attributes 450
Performance Parameters Counters 450
Performance Parameters Thresholds 451
Threshold Crossing Alert Messages 451
Configuring System Level Performance Monitoring 452
Viewing performance monitoring Counts and Threshold Values 453
Initializing Performance Monitoring Registers 455
Editing Performance Monitoring Thresholds 456
Monitoring PTP 457
Performance Monitoring Features 459
Performance Parameters 459
Performance Parameter Attributes 459

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 11

Oscilloquartz: An ADVA Company Contents

Performance Parameter Counters 460

Performance Parameter Thresholds 461
Threshold Crossing Alert Messages 461
Viewing PTP Port, PTP Flow Point and SOOC Performance Monitoring Counts and
Threshold Values 462
Initializing PTP Port, PTP Flow Point and SOOC Performance Monitoring Registers 465
Editing PTP Port, PTP Flow Point and SOOC Performance Monitoring Thresholds 466
TCA Monitored Types 468
Ethernet Access port Monitored Types 468
Ethernet Access Port Monitored Types 475
PTP Flow Point Monitored Types 483
PTP SOOC Monitored Types 485
PTP MCI Monitored Types 487
PTP Port Monitored Types 488
PTP Remote Slave Monitored Types 490
Telecom Slave Clock Analysis Monitored Types 491
PTP Network Probe Monitored Types 491

Syncjack Testing 496

Probing Features 497
Performing Clock Accuracy Testing 498
Creating a Clock Probe 498
Editing or Deleting a Clock Probe 503
Performing Clock Analysis 504
Creating a PTP Clock Probe 504
Editing or Deleting a PTP Clock Probe 511
Clock Analysis — Telecom Slave Score 512
Viewing Telecom Slave Configurations and Statistics 512
Configuring T-SC Target Values for Frequency and Phase 513
Initializing the Telecom Slave Performance Monitoring Registers 514
Editing the Telecom Slave Performance Monitoring Thresholds 515
Performing PTP Network Analysis 515
Creating a PTP Network Probe 516
Verifying the PTP Network Probe 518
Editing or Deleting a PTP Network Probe (PTP Probe) 520
Creating a Schedule 521
Deleting a Schedule 522
Verifying the Syncjack Schedule State and Testing Progress 523
Viewing the Status Tab 523

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 12

Oscilloquartz: An ADVA Company Contents

Viewing the Tests Tab 526

Viewing the TIE/TE Graph and Recent TIE/TE Graph Tabs 526
Viewing the Statistics Tab 529
Viewing History Results 531
Obtaining an MTIE Comparison 532
Viewing Results in the Dashboard Meter 533
Performing an MTIE Result Comparison 535
Configuring a Custom MTIE Mask 536
Provisioning Raw Data Collection 538
Raw Data File Format 541

Alarms, Events, Probable Causes, and Error Codes 543

Recommended Steps for Clearing Alarms 544
Error Codes and System Responses 545
Alarm Attributes, Probable Cause, and Troubleshooting 564
Alarms and Events 564
System Alarms 565
NTEOSA 5422 Card and Shelf Alarms 569
Synchronization Alarms 587
Line Cards Alarms 590
NTP Clock Alarms 595
PTP Alarms 595
Telecom Slave Alarms 595
SOOC Alarms 600
PTP Clock Alarms 601
PTP Port Alarms 605
L3 PTP Port Alarms 607
Access Port Alarms 609
Syncjack Alarms 618
Clock Probe Alarms 618
PTP Clock Probe Alarms 619
PTP Network Probe Alarms 620
Alarm Masking 621

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 13

About This Guide
This manual explains how to provision and operate the OSA 5422 and provides step-by-
step instruction of the provisioning process.

l For more information about configuring the product using

CLI commands, see the OSA 5422 CLI Reference Manual.
l For more information about configuring the product using SNMP,
see the OSA 5422 SNMP User Guide.

These are the main topics of the guide:

Overview— A brief overview of the product and its management features.

Element Management System — An overview of the web EMS workspace including

procedures for logging in and logging out of the application.

Provisioning Communications — Step-by-step procedures for provisioning the

communications interfaces. The content is organized in the recommended workflow for
new installations and can be applied to existing systems.

Provisioning Operations — Step-by-step operations and provisioning procedures. The

content is organized in the recommended workflow for new installations and can be
applied to existing systems.

Performance Monitoring — Step-by-step procedures for viewing performance monitoring

counters, setting thresholds, and initializing counters.

Syncjack Testing — Step-by-step procedures for performing Syncjack tests.

Alarms, Events, Probable Causes, and Error Codes — List of all the alarms and events
generated by the system including probable cause and troubleshooting instructions.

Documentation
Related Documentation 15
Accessing Documentation 15
Documentation Feedback 15

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 14

Oscilloquartz: An ADVA Company About This Guide

Related Documentation
l OSA 54xx Safety Guide
l GNSS Antennas and Accessories Installation Guide
l OSA Access Compatibility Matrix
l Pluggable Transceiver Module Specification
l OSA 5422 Installation and Commissioning Manual
l OSA 5422 System Description
l OSA 5422 Command Line Reference Guide
l OSA 5422 SNMP User Guide

Accessing Documentation
Documentation Portal https://advadocs.com/

Documentation Feedback
We want our documentation to be as helpful as possible. Feedback is always welcome.

Email [email protected]
Mail ADVA
Technical Documentation
Märzenquelle 1-3
98617 Meiningen-Dreissigacker
Germany

Obtaining Technical Assistance

Product Maintenance Agreements and other customer assistance agreements are available
for Oscilloquartz: An ADVA Company products through your Oscilloquartz: An ADVA
Company distribution channel. Our service options include:

l 24 x 7 telephone support
l Web-based support tools
l On-site support
l Technical training, both on-site and at ADVA facilities in Germany and the USA
l Expedited repair service
l Extended hardware warranty service

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 15

Oscilloquartz: An ADVA Company About This Guide

Customer Portal
You can use the customer portal to:

l Access company information and resources at any time.

l Find information specific to your requirements, such as networking solutions,
services, and programs.
l Resolve technical issues by using online support services.
l Download and test software packages.
l Order ADVA training materials.

Access https://www.adva.com/en/customer-portal
Questions [email protected]

Technical Services
Technical services are available to customers who need technical assistance with an
Oscilloquartz: An ADVA Company product that is under warranty or covered by a
maintenance contract.

Online https://www.adva.com/en/about-us/contact
Email [email protected]

Call ADVA
Europe, Middle East and Africa
Martinsried/Munich, Germany
+49 (0)89 89 06 65 0

North America
Norcross, GA, USA
+1 678 728 8600

Asia
Shenzhen, China
+86 755 8621 7400

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 16

Oscilloquartz: An ADVA Company About This Guide

Safety Symbol and Message

Conventions
You will see these symbols throughout the documentation. All personnel should correctly
follow and not ignore any safety instructions.

Icon Meaning Description

Warning Means danger and alerts you to a situation that
could cause bodily injury. Before you work on any
equipment, be aware of the hazards involved and
be familiar with standard practices for preventing
accidents.
Electric Voltage Means danger and alerts you to risks caused by
Warning electricity that could result in death or serious
injury. Before you work on any equipment, be
aware of the hazards involved with electrical
circuitry and be familiar with standard practices for
preventing accidents.
Shock hazard Indicates that all power sources must be
warning. disconnected before servicing to avoid shock
Disconnect all hazard.
power plugs.
Laser Radiation Warns you about the risk of possible laser
Warning radiation, which may result in a serious eye injury.

Laser Radiation Warns you about the risk of possible laser radiation
Warning – Hazard if the system is not used as designed or altered in
Level 3B any way.

Laser Radiation Warns you that the equipment contains Class 1

Warning — Class lasers, which are safe under all normal use
1 Laser conditions. It also alerts you to the risk of possible
laser radiation if the system is not used as designed
or altered in any way.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 17

Oscilloquartz: An ADVA Company About This Guide

Icon Meaning Description

Laser Radiation Warns you that the equipment contains Class 1M
Warning – Class lasers, which are safe for all conditions of use
1M Laser except when the beam is passed through
magnifying optics. It also alerts you to the risk of
possible laser radiation if the system is not used as
designed or altered in any way.
Laser Radiation Warns you that the equipment contains Class 1M
Warning – Hazard lasers, which are safe for all conditions of use
Level 1M except when the beam is passed through
magnifying optics. It also alerts you to the risk of
possible laser radiation if the system is not used as
designed or altered in any way.
Caution Alerts you to a potentially hazardous situation or
condition that may result in minor or moderate
injury.
Lifting Hazard Indicates a potentially hazardous situation or
Caution condition that may result in a personal injury or
damage to equipment due to the weight of an
object.
Skin Burn Caution Indicates the risk of possible skin burns. When
working with system components, be aware of
proper handling procedures.
Electrostatic Indicates the possibility of equipment damage due
Caution to electrostatic discharge (ESD). If the ESD-
prevention instructions are ignored or not followed
correctly, damage can occur.
Notice Indicates the risk of equipment damage,
malfunction, process interruption, or negative
impacts on surroundings.
Documentation Advises of the importance of carefully reading all
instructions before proceeding or provides links to
additional information to read. Failure to do so
may result in personal injury or damage to
equipment.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 18

Oscilloquartz: An ADVA Company About This Guide

Icon Meaning Description

Waste Disposal Points out the importance of properly disposing of
Alert waste electrical or electronic equipment and its
components. Disregard of the instruction can
threaten the environment.
Note Indicates supplemental information or helpful
recommendations.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 19

 Chapter 1

Overview
The OSA 5422 is a cost-effective, mid-scale synchronization distribution and assurance
device. You can use the OSA 5422 in a variety of network synchronization applications.
These applications include the IEEE 1588v2 PTP grandmaster clock, boundary clock, slave
clock, Assisted Partial Timing Support (APTS), and the NTP server. The built-in GNSS
receiver, Primary Reference Time Clock (PRTC) capability, and a redundant power supply
make this device ideal for reliable synchronization delivery.

For a detailed list of system features, see the OSA 5422

System Description.

Management Overview 20
Management Features 21

Management Overview
This section describes the general management communications architecture and the
management features that the OSA 5422 supports:

Management Interface Connectors

The OSA 5422 supports these management interface connectors:

l Local Area Network (MGMT LAN) port, 100/1000 BaseT with an RJ45 connector to
connect to a management Data Communications Network (DCN) or a local PC.
l Serial port, RS232 with an RJ45 connector, for access to the CLI from a local PC.
l VLAN-based management tunnels. The OSA 5422 supports one management
tunnel on each access port.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 20

Oscilloquartz: An ADVA Company Overview

Management Features
This section describes these management features:

Provisioning Communications 21
User Management and Security 21
Managing Local User Profiles 22
Managing SNMP Users 23
Access Control Lists 23
Custom Security Banner 23
RADIUS or TACACS+ 23
Provisioning Operations 24
Provisioning System Options 24
Provisioning Network Elements 24
Provisioning Secure Access 25
Provisioning Alarms 25
Provisioning Performance Monitoring 25

Provisioning Communications
The OSA 5422 provides facilities to set up a management communication configuration for
a particular site or specific network configuration. The product supports several
management configurations and options.

Typical deployment scenarios are in common IP network configurations. Within an IP

environment, you can connect the OSA 5422 in several different ways, including:

l Directly connect to a LAN, or connect through a router or an Ethernet switch.

l Create static routes to provision connections between a workstation and an
OSA 5422.
l Make use of different IP functions to achieve specific network goals. For example,
you can use the Address Resolution Protocol (ARP) to specify one LAN-connected
OSA 5422 to serve as a gateway for other equipment that does not connect to the
LAN.

User Management and Security

Security features include:

l User access security levels

l Secure Sockets Layer (SSL)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 21

Oscilloquartz: An ADVA Company Overview

l Support for security of Secure Hypertext Transfer Protocol (HTTPS)

l Secure Shell (SSH) management protocols
l RADIUS/TACACS remote authentication
l SNMPv3 support
l Post login security banner
l Access Control List (ACL) management.

Web access to the onboard Element Manager is through:

l HTTP
–or–
l HTTPS

You can individually set Telnet, SSH, HTTP, HTTPS, FTP, SFTP and SCP protocols to enabled
or disabled. You can disable serial port access. When a user logs off the serial port, the
system automatically logs off that user, which is a configurable setting.

Managing Local User Profiles

The system supports up to 10 local user accounts and four privilege levels: superuser,
provisioning, maintenance, and retrieve. You can configure an inactivity time-out to define a
time-out for each user ID of any access type.

The product provides three preconfigured user accounts, which are the default:

User Account Level

root superuser
netadmin provisioning
user maintenance

The default password for all preconfigured user accounts is ChgMeNOW. The default
inactivity timeout is 15 minutes for each preconfigured user account.

After 3 unsuccessful login attempts, the system locks a user account for a period of
5 minutes. This feature does not apply when a system uses RADIUS authentication. The
number of unsuccessful log in attempts are displayed in the user profile. You cannot
configure the lockout period.

For more information about how to manage local users, see Configuring Local Users.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 22

Oscilloquartz: An ADVA Company Overview

Managing SNMP Users

The OSA 5422 supports the SNMP MD5/SHA1 authentication protocols and AES/DES
privilege protocols.

The device provides these four preconfigured SNMP user accounts, by default:

l ADMIN
l MONITOR
l OPERATOR
l PROVISION

Access Control Lists

The OSA 5422 supports access control lists (ACLs) for management and traffic.

ACL Type Description

Management The system maintains an optional MGMT ACL to restrict acceptance of
IP addresses. For example, you can use this feature to restrict the
management, PTP, and NTP connections that the system accepts. An
operator can use the ACL to add up to 100 subnetworks or individual
IP addresses to the ACL list. When the ACL is active, only those with
valid IP addresses that are in the ACL can manage the system.
Traffic The system maintains an optional traffic ACL to restrict the IP addresses
that traffic ports can accept. For example, use this feature to restrict the
acceptable in-band management, PTP, and NTP connections. An
operator can use the traffic ACL to add up to 100 subnetworks or
individual IP addresses to the ACL list. When the ACL is active, only
those valid IP addresses that are in the ACL can use in-band
management. In addition, ACL can restrict PTP and NTP IP addresses.
This traffic ACL is hardware-based. Therefore the ACL can effectively
protect the system from Distributed Denial-of-Service (DDoS) attacks
that originate from addresses outside the accepted list.

Custom Security Banner

An operator uses the security banner feature to define a custom security banner. This
banner displays immediately after users log in to the system. This banner also displays in CLI
and web browser log ins. The system ships with a configured default security banner.

RADIUS or TACACS+
You can configure up to three RADIUS or TACACS+ servers for remote authentication. Both
types of servers support accounting.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 23

Oscilloquartz: An ADVA Company Overview

Provisioning Operations
Provisioning operations includes these tasks:

Provisioning System Options 24

Provisioning Network Elements 24
Provisioning Secure Access 25
Provisioning Alarms 25
Provisioning Performance Monitoring 25

Provisioning System Options

Provision system options in the Configuration application. For more information about
provisioning system options, see Provisioning System Options.

System options include these.

System Option Description

Common system options l System identity
l IP connectivity
l Time
l Access
l SNMP traps
Information logs Security, alarm, audit, and system logs
System security The configuration of users, MGMT ACL, and the login security
banner (see Management Features).
The Network Time Protocol (NTP)

Provisioning Network Elements

You can provision the network Element Identity (EID) and configure access interfaces, which
include port services, see Provisioning Access Ports.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 24

Oscilloquartz: An ADVA Company Overview

Provisioning Secure Access

You can ensure secure access to the OSA 5422 management system. For information about
how to provision secure access, see Provisioning Secure Access.

Secure access includes the configuration of these items:

l SNMP details
l Users, including:
o Add, edit, and delete users

o Edit passwords
o Edit GUI login time-outs
l Remote authentication
l Data anonymization (see Configuring Data Anonymity)

Provisioning Alarms
In the Maintenance application, you can modify alarm notification codes for given alarm
condition types.

For information about how to edit the default notification codes, see Modifying Default
Alarms Notification Codes.

Provisioning Performance Monitoring

Edit performance monitoring threshold levels and initialize performance monitoring
registers in the Performance Monitoring application. For information about how to
provision performance monitoring, see Performance Monitoring.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 25

 Chapter 2

Element Management
System
The web-based element management system (EMS) provides a graphical user interface
(GUI) for operation, administration, and maintenance (OAM) functions. Run the EMS in your
web browser where you can operate fault, configuration, performance, and security
functions. Connect your PC or laptop to a DCN interface. See Minimum System
Requirements for more information.

For all editable fields in the EMS, use only US-ASCII characters. The system
does not support extended ASCII characters.

This section includes these topics:

Minimum System Requirements 28

Logging In, Logging Off, and User Session Timeouts 30
Getting to Know the User Interface 33
EMS Applications 41
Managing Database Configuration 45

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 26

Oscilloquartz: An ADVA Company Element Management System

Maintenance
The Maintenance feature provides the user with a single view from which to perform all
testing and maintenance related operations, such as:

l View current conditions

l Reboot system, perform lamp test, raise/clear test alarm
l Ping, Trace Route, Flush ARP Cache, and Flush NDP Cache
l Perform sync reference switching
l Edit alarm attributes
l Software upgrade
l Database management
l CLI configuration file management
l Software Licensing

See Maintenance View for further details.

Performance Monitoring (Access Ethernet Ports)

Performance monitoring provides the user with the ability to perform these tasks:

l Obtain performance monitoring reports and chart them.

l View and configure performance parameter threshold values.

See Performance Monitoring View for further details.

Precision Time Protocol (PTP)

The Precision Time Protocol (PTP) feature provides the ability to create and monitor End-to-
End (E2E) functionality for use in high accuracy time and frequency synchronization
applications. Functions supported include:

l Create/edit/delete Telecom Slave (TS), Boundary Clock (BC), Master Clock (MC),
PTP Clock.
l Create PTP Flow Point (PTPFP).
l Monitor/configure PTPFP statistics.
l Create/edit/delete Slave Only Ordinary Clock (SOOC), Master Clock Interface (MCI),
PTP Port, and L3 PTP Port.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 27

Oscilloquartz: An ADVA Company Element Management System

SyncJack
Monitor and analyze the clock and PTP Network. Functions supported include:

l View overall sync network status.

l Clock accuracy
o Create/edit/delete clock probe.

o Monitor TIE-History measurements.

l Clock analysis
o Create/edit/delete PTP clock probe.

o Monitor TIE-History estimations.

o Monitor/edit Telecom Slave analysis.
o Edit TS thresholds.
l PTP network analysis
o Create/edit/delete PTP network probe.

o Monitor PTP network probe statistics.

o Edit PTP network probe thresholds.
l Manage SyncJack schedules

Network Time Protocol (NTP)

l Create/edit/delete NTP clock
l Create/edit/delet NTP flow point

Minimum System Requirements

Before you run EMS, ensure that the management system computer meets the minimum
system requirements listed in this table.

Table 1: Minimum System Requirements

Item Requirement
Processor 200 Mhz
Operating System Supported versions:
Microsoft Windows XP, Vista, Windows 7, or Windows 10
Browser l Microsoft Internet Explorer
l Mozilla Firefox
l Google Chrome

Note: For specific versions, see the release notes.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 28

Oscilloquartz: An ADVA Company Element Management System

Table 1: Minimum System Requirements

Item Requirement
RAM 128 Mb
Adobe Acrobat Reader Version 5.0 or greater. Version 6.0 is included.
Recommended display 1024 x 768 with 16+ color bits

If you use earlier versions of Internet Explorer, to correctly view certain

EMS elements do this: In Internet Explorer, enable the compatibility view
and add the product IP address to the data field.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 29

Oscilloquartz: An ADVA Company Element Management System

Logging In, Logging Off, and User

Session Timeouts
This section includes these topics:

Logging In 30
Logging Off 32
User Session Timeout 32

Logging In
When you log in to the OSA 5422 EMS, you must enable HTTP and HTTPS access.

To log in to the application:

1. Establish a DCN connection to the OSA 5422,

–or–
Connect the PC to the DCN port, as required.
2. Open a browser window and enter the address:

http://xxx.xxx.xxx.xxx

where xxx.xxx.xxx.xxx is the IP address of the DCN that the OSA 5422 connects to.
This IP address is the one that you assign to the DCN port (eth0) during the initial IP
configuration. If no IP address is set, use the default 192.168.0.2.

The log-in window opens.

3. Enter a valid User ID and the password.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 30

Oscilloquartz: An ADVA Company Element Management System

The default user ID is root. The default password is ChgMeNOW. For additional log in
information, see Provisioning Secure Access.
Some systems implement remote authentication through RADIUS by using a two-factor
mode authentication, such as RSA. The first time the login processes uses the secure ID
token as the password, you might be prompted to enter your old password. A prompt
asks you to define a PIN of 4 to 8 alphanumeric characters as shown in the figure that
follows.
In the New PIN and Confirm PIN fields, enter your PIN. Click Create PIN.

After you change your PIN, a prompt asks you to enter the PIN and a new six digit token
code in the Passcode field, which the authenticating device provides. You will use this
combination of PIN+token code as the password on each subsequent login.

For more information about how to implement remote authentication,

such as RADIUS, see Configuring Remote Authentication to the Device.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 31

Oscilloquartz: An ADVA Company Element Management System

4. Click Login.
The security banner is displayed.

After three unsuccessful login attempts, the software locks an account for
5 minutes.

5. Click Continue. The EMS opens.

Figure 1: The EMS GUI

Logging Off
To log off from the OSA 5422 EMS:

1. From the File menu, select Exit.

2. Close your browser.

User Session Timeout

ADVA preconfigures the session timeout for each user to 15 minutes. Superusers can edit
the session timeout value.

After a user session is inactive for the amount of time configured in the session timeout
value, the software automatically signs out the session to ensure system security. To
continue to work in EMS, sign in to EMS again.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 32

Oscilloquartz: An ADVA Company Element Management System

Getting to Know the User Interface

EMS is a user interface that you use for operation, administration, and maintenance (OAM)
functions.

The menu bar, toolbar, and tree pane provide easy access to the workflow of interest, such
as when you want to provision an entity or perform maintenance functions. The Details
pane displays different editing options based on which application and entity you select.
The Alarms pane displays continuous alarm monitoring.

Figure 2 illustrates the UI areas:

Figure 2: EMS Components

These sections describe the UI areas:

Title Bar 34
Menu Bar 34
Toolbar 34
Tree Pane 34
Details Pane 35
Alarms Pane 36
Keyboard Navigation 37

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 33

Oscilloquartz: An ADVA Company Element Management System

Title Bar
The Title bar displays the current application that you select from the Application menu or
the Toolbar.

Menu Bar
The Menu bar contains the File menu and the Application menu.

Menu Description
File Provides a way to log off.
Application Provides:

l Configuration
l Maintenance
l Performance monitoring
l PTP
l NTP
l SyncJack

Toolbar
The Toolbar provides quick access to EMS applications. You can also access these
applications from the Application menu:

Configuration, see Configuration View.

Maintenance, see Maintenance View.

Performance Monitoring, see Performance Monitoring View.

Precision Time Protocol, see Precision Time Protocol.

SyncJack, see Syncjack Testing.

Network Time Protocol, see Configuring an NTP Client.

Tree Pane
The tree pane, located on the left of the UI, displays a hierarchical tree of the entities that
are part of the OSA 5422 system. The tree pane also displays related entities of each of

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 34

Oscilloquartz: An ADVA Company Element Management System

those systems. Each item on the tree represents a specific entity type such the NE, access
port, communications, SNMP, and administration.

In the tree pane, you select entities to display their current provisioning details and status in
the Details pane on the right. Or, you can right-click entities to access configuration options.
The information that the Details pane displays depends on which application you select
from the Application menu or the toolbar.

Click + to expand or – to collapse tree elements and access the system entities.

Figure 3: Tree Pane with a Menu Selected

Details Pane
The Details pane displays the status of the element you select in the Tree pane. The
software sometimes displays the details on several tabs, which change according to the
application you select.

To open an edit window in the Details pane, right-click an element and select one of the
available configuration options. See Figure 4.

Figure 4: Details Pane for PTP

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 35

Oscilloquartz: An ADVA Company Element Management System

Alarms Pane
Alarms appear in the Alarms pane at the bottom of the EMS. This provides constant visibility
and access to current alarms, and enables you to continuously monitor alarms no matter
what application you currently view.

The alarms are color-coded by severity:

l Red, critical
l Orange, major
l Yellow, minor

Each alarm is listed as a separate line item, with these details:

l Interface type
l Notification code
l Description
l Date/timestamp

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 36

Oscilloquartz: An ADVA Company Element Management System

Keyboard Navigation
You can use the keyboard exclusively to navigate through the active EMS elements:

l Navigate to all interactive elements without using a mouse.

l Direct your focus to the browser user elements based on how you use the
keyboard.
l Highlight active elements.
l Access activated elements by repeatedly pressing Tab or Alt+Tab, including sub -
lements within an area.
l Return to the active area after you perform an action.
l Zoom in and out of the user interface.

Mouse Navigation Keyboard Navigation

Navigate to most elements using a l Tab: Press Tab to change the active element
mouse. from left to right and from top to bottom in
the clockwise direction.
l Shift+Tab: Press Shift +Tab to reverse the
direction in the counterclockwise direction.

For these keys to function correctly ensure that:

l Keyboard active element indicators are

present, such as a blue box around active
item and background color of active element
changes to light blue.
l Navigation order is logical and intuitive.
Click a link. Press Enter.
Click a button. Press Enter.
– or –
Press the Spacebar.
Select or clear an option, if you can Press the Spacebar.
select one or more options.
Select or clear an option, if you can l Select or clear an option: Use the arrow
select only one option from a group . keys.
l Navigate between elements: Press Tab .

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 37

Oscilloquartz: An ADVA Company Element Management System

Mouse Navigation Keyboard Navigation

Select a menu command. l Navigate between menu options: Press the
arrow keys.
l Expand menus: Press the Spacebar.
l Filter through options: Begin typing the
command, and the behavior differs by
browser. For example, some browsers filter
as you type, similar to autocomplete. Others
only sort by letter. For example, in a list of
states, pressing A, and then R might display
Arizona, Alabama, or Rhode Island
depending on the filter.
l Activate a menu command: Press these
keys:
l Spacebar
– or –
l Enter
Autocomplete 1. Type to begin filtering.
2. Navigate to an option by pressing the Down
Arrow (↓) and Up Arrow (↑) keys.
3. To select an option, press Enter.
Close a dialog box. For example, by l To close the dialog box, press Esc.
clicking Close.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 38

Oscilloquartz: An ADVA Company Element Management System

Mouse Navigation Keyboard Navigation

Use a mouse to set a slider value by l To increase or decrease a slider value, press
moving the slider to the right or left to the arrow keys.
increase or decrease the value.
l To navigate to the value at the beginning of
the slider, press Home.
l To navigate to the value at the end of the
slider, press End.
l To set a range when you use a double-slider,
press these keys to toggle between each end:
l Tab
– or –
l Shift+Tab
l In some sliders, you can press these keys to
increase or decrease a slider value by a larger
increment, such as through increments of 10:
l Page Up: To increase the value.
l Page Down: To decrease the value.
Select a menu bar command, which can l To navigate to the next menu command,
include pointing to a command to open press the Down Arrow.
the submenu, where you can then select l To navigate to a previous menu command,
the appropriate command. press the Up Arrow.
l To open a submenu from the menu bar, if
applicable, press Enter.
l To expand a submenu, press the Right Arrow
(→).
l To collapse a submenu, press the Left Arrow
(←).
l To activate the menu command, press these
keys:
l Spacebar
– or –
l Enter
l To close the contextual menu, press Esc.

Note: Some menu commands do not require

you to press these keys. For example, to activate
a command in a simple menu that has no
submenus, you can press Tab and Enter.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 39

Oscilloquartz: An ADVA Company Element Management System

Mouse Navigation Keyboard Navigation

Navigate through the various options l To navigate to or frp, a group of tabs, press
that a window or panel displaysand that Tab.
includes tabs. Note: Navigation between tabs using the
Tab key is for window tabs, which change
without loading a new page. If a menu
displays as a group of tabs, which link to
different pages, use Tab and Enter .
l To navigate to the previous tabs, press either
the:
l Up Arrow
– or –
l Left Arrow
l To navigate to the next tabs, press either the:
l Down Arrow
– or –
l Right Arrow

Note: The content that the tab

displayesautomatically updates after you press
the arrow keys. Pressing Enter does not activate
the tab.
Select a selection tree menu command, l To navigate to the next menu command,
which can include pointing to a press the Down Arrow.
command on the main menu to open l To navigate to a previous menu command,
the submenu, where you can then select press the Up Arrow.
the appropriate command. l To expand a submenu or move up a level,
press the Right Arrow.
l To collapse a submenu or move down a level,
press the Left Arrow .
Open the context menu of the pointed l
element. Windows Context Menu Key
– or –
l Shift+F10 keys.

Note: When you use Windows in a Firefox

browser, press Shift+ F10 + F10 instead of
Shift+F10.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 40

Oscilloquartz: An ADVA Company Element Management System

Mouse Navigation Keyboard Navigation

Scroll in a window. l Press the Up Arrow and Down Arrow to scroll
vertically.
l Press the Left Arrow and Right Arrow to scroll
horizontally.
l To scroll by page, press these keys:
o Spacebar

– or –
o Shift+Spacebar

Zoom in and out l Press Ctrl + Plus sign (+) to zoom in.
l Press Ctrl + Minus sign (–) to zoom out.

EMS Applications
The EMS provides these applications:

l Configuration (see Configuration View).

l Maintenance (see Maintenance View).
l Performance Monitoring (see Performance Monitoring).
l PTP (see Provisioning the Precision Time Protocol).
l Syncjack (see Syncjack Testing).
l NTP (see Configuring an NTP Client).

Each of the applications can be selected from the Menu Bar or Toolbar. The Title Bar
displays the latest application that has been selected (see Title Bar).

Configuration View
In the Configuration view you provision elements and view provisioning attributes of the
selected entity in the tree pane or the entity details pane.

l In the tree pane:

o Click an item to display the item current status and configuration.

o Right-click an item to displays a list of configuration items you can edit.

l Alarm status is displayed in the alarms pane at the bottom of the screen.

The Configuration view includes these elements:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 41

Oscilloquartz: An ADVA Company Element Management System

System
The System entity displays system-level settings in these tabs. To edit system options,
right-click and select the required option. For more information about editing system
options, see Provisioning System Options.

l Identification
l Security Log
l Alarm Log
l Audit Log
l Syslog
l Managing Access Control List (MGMT ACL)
l Banner
l Time Zone
l Network Time Protocol (NTP)
l Traffic ACL (PTP/NTP)
l ICMP Filter

Network Element (NE)

The NE-1 entity provides access to the equipment associated with the OSA 5422.

Under NE-1, you can provision:

l Access ports
l Line cards
l DCN
l Power supply units

Navigate to NE-1 > NTEOSA 5422 > Resources tab to view allocated and available system
traffic resources.

Synchronization
Navigate to Synchronization > NE-1 > NTEOSA 5422 to configure frequency and time
synchronization interfaces.

l SYNC-1-1-1-1 – provision frequency synchronization for the device.

Right-click the SYNC-1-1-1-1 entity to manage synchronization sources.
l TIME CLOCK-1-1-1-1 – provision time synchronization for the device.
Right-click the TIME CLOCK-1-1-1-1 entity to edit time reference.
l BITS-1/BITS-2 – povision the device BITS in and BITS out ports.
l CLK-1-1-1-1/CLk-1-1-1-2 – provision the device 10 MHz frequency reference
ports.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 42

Oscilloquartz: An ADVA Company Element Management System

l PPS-1-1-1-1/PPS-1-1-1-2 – provision the device PPS ports.

l TOD-1-1-1-1 & PPS/TOD-1-1-1-2 & PPS – provision the device ToD & PPS input
and output ports..
l GPS-1-1-1-1 – provision the device GNSS port and reciever settings.

Communications
Use the Communications element to add or delete static routes, static ARP entries, IPv6
static routes, IPv6 static neighbor entries, and source address configuration in
corresponding tabs.

Expand Communications to access DCN (eth0) and management tunnels for the NE.

SNMP
Use the Simple Network Management Protocol (SNMP) element to add or delete:

l SNMP communities
l Target addresses
l Target parameters
l User-based security model (USM) user entries
l SNMP dying gasp

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 43

Oscilloquartz: An ADVA Company Element Management System

Administration
Use the Administration element manage these elements:

l Users
l Remote authentication
l Security policy
l User data policy
l Key generation

Maintenance View
Use the Maintenance view to compete these tasks:

l Run diagnostics.
l Raise and clear test alarms
l Set and retrieve alarm attributes
l Restart the device
l Upgrade the device software
l Back up and restore the database
l Manage configuration files
l Enable software licenses
l Maintain sync and time clock reference

For more information about maintenance operations, see Maintenance Operations.

The Maintenance view includes these elements:

Element Description
System View system identification and conditions list.
NE-1 l View conditions lists associated with the device.
l Expand NE-1 > NTEOSA 5422 to view the equipment associated
with the device. Select equipment to view its operation status.
l Right-click NE-1 to perform a lamp test.
l Right-click NTEOSA 5422 to raise and clear test alarms or reboot the
shelf.
Synchronization Expand Synchronization > NE-1 > NTEOSA 5422 to access SYNC-1-1-1-
1 and Time Clock-1-1-1-1 elements. Right-click these elements to
operate the reference switch.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 44

Oscilloquartz: An ADVA Company Element Management System

Element Description
Communications T
l Select the Communications entity to view the routing, ARP, IPv6
routing, IPv6 NDP tables, the results of the last ping command, and
the results of the last trace route command.
l Right-click the Communications entity to ping, trace route, flush
ARP cache, and flush NDP cache.
Alarm Attributes l Expand the Alarm Attributes entity and select an element to view the
current alarm attribute settings for this element.
l Right-click an element to edit the alarm severity of each listed
condition.
Administration Expand the Administration entity to access these maintenance
functions:

l Right-click Administration to restore system defaults or restore

factor default. See Restoring System Defaults and Restoring Factory
Defaults.
l Right-click Updgrade to transfer, install, activate, and validate a
sfotware upgardae. See Upgrading the Software Version.
l Right-click Database to run database backup and restore
operations. See Managing Database and Configuration Files.
l Right-click Default Database to run operations on the default
database.
l Select Default Settings to copy a values file to the device.
l Right-click Configuration Files to create a new configuration file, or
copy from remote. Right-click a configuration files in the details
pane to perform operations on the file.
l Right-click Last Reset Cause to copy to remote debug fiels.
l Right-click Transfer Log to select a log to transfer.
l Right-click Diagnostics Files to save or copy the diagnostics file to a
remote location. see Managing Diagnostics Files
l Expand Software Licensing and right-click Features Management
to enable or disable software features. see Activating Software
Licenses

Managing Database Configuration

These operations are available for managing configuration data:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 45

Oscilloquartz: An ADVA Company Provisioning Communications

l Determine the database configuration status.

l Restore system defaults.
l Backup the database.
l Restore the database.
l Modify the system default database.
l Reset to system defaults.
l Reset to factory defaults.
l Change the default value file.

For more information, see these topics:

l Managing Database and Configuration Files

l Restoring a Database
l Restoring System Defaults

Chapter 2

Provisioning
Communications
This section contains communications provisioning information and procedures for the
OSA 5422, including how to set up initial communications to the unit. Provisioning details
and an example scenario of Gateway Network Element (GNE) to Subtending NE (SNE)
communications are provided.

The topics covered in this section include:

Provisioning Communications 47
Implementing Management Communication to the OSA 5422 47
Accessing OSA 5422 with a Browser-Based IP Connection 55
Editing the DCN eth0 Configuration 56
Adding/Deleting IPV4 Static ARP Entries 65

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 46

Oscilloquartz: An ADVA Company Provisioning Communications

Adding/Deleting IPv6 Static Routes 67

Adding/Deleting IPv6 Static Neighbor Entries 69
Adding/Deleting IPv4 Static Routes 72
Setting up a Network Example for GNE-to-SNE Over a Management Tunnel 74

Provisioning Communications
The OSA 5422 supports several management configurations and options. Deployment
scenarios of the OSA 5422 in common IP network configurations are varied and numerous.

Additionally, the network administrators of most organizations either provision the

OSA 5422 or create work orders that provide the provisioning details. A comprehensive
explanation of IP networking concepts is beyond the scope of this document.

Oscilloquartz: An ADVA Company sets the factory default settings for the OSA 5422 so that
you can connect the MGMT LAN (DCN) RJ45 connector to your local or remote DCN.
Oscilloquartz: An ADVA Company preconfigures interface eth0 with the DHCP in client
mode and with the DHCP function disabled. You can quickly ascertain the status of the DCN
using the RS-232 serial port to query the NE for the DCN settings. Use this same interface to
enable DHCP or to set the IP address of the eth0 interface if the DCN does not use DHCP.

You can deploy the unit with settings other than the factory defaults or establish a system
default database with user-specified DCN settings. You can also configure a management
tunnel on one or more network or access ports.

Implementing Management
Communication to the OSA 5422
To connect a PC or laptop to the product management interface, use the CLI through a
direct local-serial link. You can also connect to the product from a remote DCN through a
DCN network.

You must use a valid IP address for the Management LAN interface when you connect
through the DCN. Although the OSA 5422 ships with the default IP address of 192.168.0.2 /
24, the default is the same for each unit. To ensure a reliable connection to the OSA 5422,
first configure the IP address of the Management LAN interface to use a unique IP address
that is compatible with its network. In most cases, the system configures this address
automatically by using DHCP. Or, you can create a serial connection to manually configure
the IP address to the OSA 5422, and then configure the IP address during installation. See
Connecting to the Serial Port for more information.

Some information about the examples in this section:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 47

Oscilloquartz: An ADVA Company Provisioning Communications

l The use of a PC or laptop running Microsoft Windows and the terminal emulation
program are for illustration purposes only. You can use other terminal emulation
programs that run on a different platform. For more information, contact ADVA
Technical Support (see Call ADVA).
l It is outside the scope of this document to describe the use of any computer
operating system, terminal emulation program, or internet browser.

Signing In with User Names and Passwords

The default password to access the management interface is ChgMeNOW. Use this password
to access these accounts when you first access the device:

l The root, netadmin or user account.

l An account that an administrator changed.

When you sign in using the default password, you must change the password to minimize
possible exposure, restrict access to the system, and increase system security. All account
names and passwords are case-sensitive.

After you use the local password file for user authentication, and after 3 unsuccessful login
attempts, the system locks the sign-in account for 5 minutes.

Connecting to the Serial Port

For information about using CLI commands through the serial port, see the
OSA 5422 CLI Reference Guide .

To make a serial connection to the OSA 5422:

1. Ensure that you establish a physical serial connection from a PC or laptop to the
OSA 5422 RS-232 connector.
2. Start a serial terminal emulation program such as Tera Term Web to establish a
connection.
3. Select the outgoing communication port.
4. Set these terminal-emulation program communication settings:
o 9600 baud

o 8 data bits
o No parity bit
o 1 stop bit
o No flow control

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 48

Oscilloquartz: An ADVA Company Provisioning Communications

5. Save these settings for later use.

This login prompt is displayed:
Login:
6. Sign in using these default credentials, unless you or an administrator already changed
the default settings:
o User ID: root

oPassword: ChgMeNOW
A security banner is displayed.
7. Press Y to continue.
This prompt is displayed:

ADVA-->

Setting Up the OSA 5422 DCN eth0 Port Through

the Serial Port
This section explains how to set up the OSA 5422 DCN eth0 port MGMT LAN using the RS-
232 serial port and the CLI.

For more information about the CLI command structure, see the OSA 5422
CLI Reference Guide.

Prerequisites
To complete this procedure, we assume that you have not yet installed the Ethernet cable
that connects the MGMT LAN to the DCN network.

Requirements
l A PC or laptop with a serial communications port such as COM1 or COM2.
l 2 Category 5 LAN cables with RJ45 connectors.
l A DB-9-to-RJ45 converter, Oscilloquartz: An ADVA Company part number
2036904035-01 or 1036904035.
l A communications program such as TeraTerm Pro Web, a free software terminal
emulator for Microsoft Windows.
l An Internet browser such as Internet Explorer or Firefox. You should complete this
procedure during the commissioning process or as a standalone procedure.

Guidelines
l You must complete this procedure during the commissioning process or as a
standalone procedure.
l The default DHCP setting for the DCN port is disabled and set as a DHCP client.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 49

Oscilloquartz: An ADVA Company Provisioning Communications

l This procedure is the optimal way to set up an IP address using the CLI. You access
the CLI through the RS-232 serial console port. If a DHCP server is unavailable for
the DCN port, you must set DHCP to disabled.
By default, DHCP is disabled on the DCN and not set as a DHCP client.

The IP addresses and subnet mask entries in these procedures are for
example only. Determine the information you enter from your local
sources.

Table 2: Setting Up the DCN eth0 Port MGMT LAN Through the RS-232 Serial Port
Task Reference
1. Connect a serial cable between the OSA 5422 RS- See Connecting to the Serial
232 serial port and a PC. Port.
2. Log in to the device.

3. Verify the DHCP status of the eth0 port for the DCN See Verifying the DHCP Status of
interface, which determines your next step. the eth0 Port.

4. Change the DHCP status of the eth0 port according See Changing the DHCP Status
to your requirements. of the eth0 Port.

Note: The next steps differ depending on whether the DHCP status is disabled or enabled.
DHCP status is disabled:
1. Configure the eth0 port with a valid IP address, See Configuring the eth0 Port.
network mask, and default gateway for the DCN
network that the NE connects to.
2. Verify that the HTTP and HTTPS settings are enabled See Verifying That HTTP and
on the system, and if not, enable them. HTTPS Settings are Enabled.
3. Use an Ethernet cable to connect the MGMT LAN Not applicable
RJ45 connector to the network DCN.

4. Verify that you correctly configured the web-based See Verifying Connection with
EMS connection for the IP address of the network the Web-Based EMS.
DCN that the device connects to.

5. Disconnect the serial port and end the session. See Disconnecting the Serial Port
and Ending the Session.
6. Disconnect the serial cable from the RS 232 Not applicable
connector on the device.
DHCP status is enabled:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 50

Oscilloquartz: An ADVA Company Provisioning Communications

Table 2: Setting Up the DCN eth0 Port MGMT LAN Through the RS-232 Serial Port
Task Reference
1. Use an Ethernet cable to connect the MGMT LAN Not applicable
RJ45 connector to the network DCN.

2. Verify the IP address of the eth0 port. See Verifying the IP Address of
the eth0 Port.
3. Verify that the HTTP and HTTPS settings are enabled See Verifying That HTTP and
on the system, and if not, enable them. HTTPS Settings are Enabled.

4. Verify that you correctly configured the web-based See Verifying Connection with
EMS connection for the IP address of the network the Web-Based EMS.
DCN that the device connects to.

5. Disconnect the serial port and end the session. See Disconnecting the Serial Port
and Ending the Session.
6. Disconnect the serial cable from the RS 232 Not applicable.
connector on the device.

Verifying the DHCP Status of the eth0 Port

You can set the DHCP status of the eth0 port for the DCN interface to enabled or disabled.
When you set up the DCN eth0 port, you must ensure that the DHCP status is correct
according to your system requirements. If not, you can change the status before you
continue.

To view the current DHCP setting for the DCN interface on the OSA 5422 use the show ip-
interface eth0 command. See this example:

ADVA--> show ip-interface eth0

Name : eth0
IP Address : 192.168.0.2
Netmask : 255.255.255.255
DHCP Role : dhcp-client
DHCP : disabled
DHCP Client ID : OSA OSA 5422
RIPv2 : disabled
MTU (bytes) : 1500
MAC Address : 00:80:ea:02:62:01
System Default Gateway : 0.0.0.0

The next step depends on the DHCP status of the eth0 port:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 51

Oscilloquartz: An ADVA Company Provisioning Communications

DHCP Status Task

Set to disabled. Configuring the eth0 Port
Set to enabled. Use an Ethernet cable to connect the MGMT LAN
RJ45 connector to the network DCN. See step #1 in
Table 2 in the DHCP status is enabled section.
You need to change the status. Changing the DHCP Status of the eth0 Port

Changing the DHCP Status of the eth0 Port

To change the DHCP status of the eth0 port, use the configure communication
command. To set the applicable DHCP status, after the next level-prompt is displayed.

For example:

ADVA--> configure communication

ADVA:comms--> configure eth0 dhcp-control enabled
ADVA:comms-->

To verify the status after you change it, see Verifying the DHCP Status of the eth0 Port.

The next step to set up the DCN using the RS-232 serial port depends on whether you
configured the DHCP status as enabled or disabled:

l If the DHCP status of eth0 port is set to disabled, see Configuring the eth0 Port.
–or–
l If the DHCP status of eth0 port is set to enabled, connect the MGMT LAN RJ45
connector to the network DCN using an Ethernet cable. See step #1 in Table 2 in
the DHCP status is enabled section.

Configuring the eth0 Port

If you set the DHCP status to disabled, you must configure the eth0 port with a valid
IP address, network mask, and default gateway for the DCN network that the NE connects
to. Use the configure eth0 command as shown illustrated in the example. After you
change the status, you can also verify the eth0 port settings as shown in the example.

In most cases, your network administrator provides the IP address and net-
work mask information.

Example:

ADVA--> configure communication

ADVA:comms-->

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 52

Oscilloquartz: An ADVA Company Provisioning Communications

ADVA:comms--> configure eth0 ip-address 172.17.11.33 255.255.255.0 172.17.11.1

ADVA:comms-->

After you configure the port, verify the current IP address and network mask setting for the
DCN interface on the OSA 5422 using the show eth0 command. If the eth0 port settings
are incorrect, for example an incorrect IP address or network mask is displayed, reconfigure
the port using the configure eth0 command.

Example:

ADVA:comms--> show eth0

Name : eth0
IP Address : 172.17.11.33
Netmask : 255.255.255.0
DHCP Role : dhcp-client
DHCP : disabled
DHCP Client ID : OSA OSA 5422
RIPv2 : disabled
MTU (bytes) : 1500
Physical Address : 00:80:ea:02:62:01
System Default Gateway : 0.0.0.0

Verifying the IP Address of the eth0 Port

After you successfully change the DHCP status to enabled, you can verify the IP address of
the eth0 port using the the show ip-interface eth0 command output.

l If the CLI lists an IP address other than 0.0.0.0, verify that you enabled the HTTP and
HTTPS settings on the system (see Verifying That HTTP and HTTPS Settings are
Enabled).
–or–
l If the IP address displays as 0.0.0.0, wait one minute, and then re-enter the show
ip-interface eth0 command. Verify that the IP address updates. If after
four attempts, the IP address still does not change, contact your system
administrator. After an IP address other than 0.0.0.0 is present, proceed with
Verifying That HTTP and HTTPS Settings are Enabled.

Example:

ADVA--> show ip-interface eth0

Name : eth0
IP Address : 192.168.0.2
Netmask : 255.255.255.255
DHCP Role : dhcp-client
DHCP : disabled
DHCP Client ID : OSA OSA 5422
RIPv2 : disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 53

Oscilloquartz: An ADVA Company Provisioning Communications

MTU (bytes) : 1500

MAC Address : 00:80:ea:02:62:01
System Default Gateway : 0.0.0.0

Verifying That HTTP and HTTPS Settings are

Enabled
You must set the HTTP and HTTPS settings to enabled. To verify that these settings are
enabled, use the show system command. For example:

ADVA:comms--> home
ADVA--> show system

If the HTTP or HTTPS settings are not enabled, use the configure system command and
specify either

l http enabled
–or–
l https enabled

Example:

ADVA:comms--> home
ADVA--> configure system
ADVA:system--> http enabled
ADVA:system--> https enabled

Verifying Connection with the Web-Based EMS

You can verify the successful connection with the web-based EMS for the IP address of the
DCN that connects to the product.

To verify the web-based EMS connection:

1. Open your browser and enter the address in this format:

http://xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the DCN that connects to the OSA 5422.
This IP address is the one that you assigned to the DCN port eth0 during the initial IP
configuration.
–or–
If you did not specify an IP address, the default is 192.168.0.2.
The EMS opens and displays the Login window:

2. Enter a valid User ID and Password and click Login. The default user ID is root and the
default password is ChgMeNOW. The security banner is displayed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 54

Oscilloquartz: An ADVA Company Provisioning Communications

3. Click Continue. The web interface opens in the System view.

4. To log out, from the File menu, select Logout.

Disconnecting the Serial Port and Ending the

Session
In the serial port session, use the quit command to log off and end the session.

Example:

ADVA:comms--> quit
Logged Out

Login:

Accessing OSA 5422 with a Browser-

Based IP Connection
To ensure a reliable connection over an Ethernet DCN network, configure the IP address of
the management interface for the OSA 5422 to a unique address that is compatible with its
network.

Per-session cookies authenticate commands that you enter in an internet

browser. This process means that the browser stores a cookie only tem-
porarily. If you are unable to log in to the web interface, verify that you con-
figured your browser to accept these types of cookies.

For more information about using the web interface, see the OSA 5422 Pro-
visioning and Operations Manual.

To access the OSA 5422:

1. Ensure that you configured a unique IP address for the OSA 5422 management
interface. See Setting Up the OSA 5422 DCN eth0 Port Through the Serial Port.
2. Ensure that you established a physical Ethernet connection from the DCN PC to the
OSA 5422,.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 55

Oscilloquartz: An ADVA Company Provisioning Communications

3. Verify that your PC IP address and net mask address match the values that the network
administrator provided. This step is necessary so the PC can access the OSA 5422
network.
4. In a browser window, enter this address:
http://xxx.xxx.xxx.xxx
–or–
https://xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the OSA 5422 to connect to. This IP
address is the address that you assigned to the product during initial IP configuration. If
you did not specify an address, the default is 192.168.0.2.
The Login page of the web-based EMS is displayed.
5. Unless you already changed the default settings, enter the default user ID and password,
and click Login.
o User ID: root

o Password: ChgMeNOW (or as appropriate).

After you make three (3) unsuccessful login attempts, the software locks
that login account for 5 minutes.

6. Click Continue.
The web interface opens in the System view.

Editing the DCN eth0 Configuration

You can configure the Management LAN interface, which supports both IPv4 and IPv6
modes:

l as an IPv4 DHCP server

l as an IPv4/IPv6 DHCP client
–or–
l with DHCP disabled in either IP mode.

If you do not use the DHCP client mode, you can edit the IPv4 address and network mask. If
you disable DHCPv6 mode, you can edit the IPv5 Unicast address with its prefix.
Additionally, you can set RIPv2 and RIPng to enabled or disabled. This procedure provides
instructions to edit the DCN options.

The factory default settings specify that the DHCP for IPv4 and IPv6 is disabled in the client
role, and also set RIPv2 and RIPng to disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 56

Oscilloquartz: An ADVA Company Provisioning Communications

Prerequisites
l Configure the NE with an IP address and connected the NE to a DCN or LAN. See
Setting Up the OSA 5422 DCN eth0 Port Through the Serial Port
l Sign in to the web-based EMS.

You can complete these additional DCN (eth0) configuration editing tasks:

To edit the DCN (eth0) configuration:

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration.
The Edit DCN (eth0) window opens. The options that display differ depending on
whether you set IP Mode to IPv4 Only, which is the default, or IPv4 and IPv6. In this
example, IP Mode is set as IPv4 and IPv6, which displays all available options.

3. In the Edit DCN (eth0) window, complete these settings to your system network
requirements:

Area Field Setting

Interface IP Mode Select either the default, IPv4 Only, or IPv4 and IPv6.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 57

Oscilloquartz: An ADVA Company Provisioning Communications

Area Field Setting

IPv4 IP Address Enter the applicable IPv4 address. Set this option to
Enabled only when you set DHCP mode to Disabled or
define the DHCP Role as a DHCP Server. Otherwise,
when you set up an IPv4 DHCP client, this option does
not apply and is unavailable.
Netmask Enter the applicable IPv4 subnet mask for the DCN. This
option applies only if you set DHCP to Disabled or set
DHCP Role to DHCP Client. If you set DHCP to
Enabled and you set the DHCP Role to DHCP Server,
the netmask determines the number of IPv4 addresses
available for assignment.
RIPv2 Select Enabled or Disabled. The default is disabled.
DHCP Select Enabled or Disabled. The default is disabled. If
you set this interface to Enabled and you set the DHCP
Role to DHCP Client, the OSA 5422 sends a broadcast
query to request IPv4 address information from a DHCP
server.
IPv4 DHCP Role This option applies only if you set DHCP to Enabled.
(continued) Select server or client. The default is client. Servers
assign IPv4 addresses, and clients receive IPv4
addresses. If you set the DHCP Role to DHCP Server,
you must Disable and then Enable DHCP. This setting is
necessary for the server function to initialize, and the IP
address range to occur.
DHCP Client Select whether to insert the DHCP client ID in DHCP
ID Control messages when you set the DHCP Role to DHCP Client.
To configure this setting, select Enabled, or select
Disabled, the default. When you set the DHCP Role to
DHCP Server, this field is unavailable.
DHCP Client Enter the appropriate ID using a maximum of
ID 254 characters. The default value is the system name
truncated to 254 characters. Specify this field only if you
set the DHCP Role to DHCP Client and set the DHCP
Client ID Control to Enabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 58

Oscilloquartz: An ADVA Company Provisioning Communications

Area Field Setting

System Edit System Select to edit the gateway IPv4 address. Specify this field
Default Default only if you set DHCP to Disabled. Otherwise , this field
Gateway (for Gateway is unavailable.
IPv4) Gateway IPv4 If you select Edit System Default Gateway, enter a
Address gateway IPv4 address.
IPv6 IPv6 Unicast Enter the IPv6 unicast address for the DCN port. This
Address option applies only when you set DHCPv6 to disabled.
Note: When you configure an IPv6 network and IPv4 is
unnecessary, set the IPv4 DHCP to Disabled and the IPv4
address to 0.0.0.0/0.
DHCPv6 Select whether to set the DHCP to enabled or disabled. If
you set this interface to Enabled and the DHCPv6 Role
to DHCP Client, the OSA 5422 sends a broadcast query
to request IPv6 address information from a DHCP server.
DHCPv6 Role This role in an IPv6 network is fixed as a DHCP Client.
Clients receive IPv6 addresses.
RIPng Select Enabled, or the default, Disabled. When you set
RIPng to enabled on an IPv6 interface, the interface
receives the IPv6 route entry on the link and updates the
local route table. The interface also uses multicast
packets to send local IPv6 route entries to the link.
System Edit System Select to edit the gateway IPv6 address.
Default Default
Gateway (for Gateway
IPv6) Gateway IPv6 If you selected Edit System Default Gateway, enter an
Address address.

4. After you complete the DCN (eth0) options, click OK. The software updates the DCN
(eth0) settings.

Configuring the DCN as a DHCP Server

You can configure the DCN eth0 port as an IPv4 DHCP server.

To configure the DCN eth0 as an IPv4 server:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 59

Oscilloquartz: An ADVA Company Provisioning Communications

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. In the IPv4 section, complete these settings:

Field Description
DHCP Select Enabled.
DCCP Role Select DHCP Server. The IP Address and Netmask fields are currently
unavailable.
IP Address Enter the applicable address for IPv4.
Netmask Enter the applicable address, where the range of the netmask that you
specify determines the number of IPv4 addresses available for this server
to assign
RIVv2 Select Enabled or Disabled to define how to set the RIPv2 packets. The
default is disabled

4. Click OK. The software updates the DCN eth0 settings.

To activate the new IP address and DCHP server function with the IP address range, you
must cycle the DHCP control as follows:

1. Repeat steps 1 to 2 in the previous set of steps..

2. In the DHCP field, select Disabled, and then click OK.
3. Repeat steps 1 to 2 in the previous set of steps..
4. In the DHCP field, select Enabled, and then click OK.

Configuring the DCN as a DHCP Client

You can configure the DCN eth0 port as an IPv4 DHCP client or an IPv6 DHCP client.

To configure an IPv4 DHCP client:

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. In the IP Mode field, select IPv4 Only.
4. Complete these fields in the IPv4 area.
Field Description

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 60

Oscilloquartz: An ADVA Company Provisioning Communications

DHCP Select Enabled.

DHCP Role Select DHCP client.
DHCP Client ID Control Select Enabled or Disabled to specify whether to insert the
DHCP Client ID in DHCP messages.
(optional) Edit the DHCP Client ID from the default configuration. This
DHCP Client ID field is available only when you set the DHCP Client ID
Control to Enabled.
RIPv2 Select Enabled or Disabled to enable or disable RIPv2
packages. The default is disabled.
IPv6 RA Prefix Enabled Select whether to advertise the prefix to link to in router
mode. This setting applies only when you set IPv6 forwarding
to enabled at the system level. This option and the Stateless
Address Auto Configuration are mutually exclusive. If you
set one to enabled, you must set the other to disabled.
IPv6 RA Prefix Enter the IPv6 Prefix that the system will dispatch to link to in
Router mode. This option is set to enabled only if you set the
IPv6 RA Prefix Enabled to Enabled.
To edit the system default gateway of the IPv6 address, select
Edit System Default Gateway, and then enter the applicable
Gateway IPv6 Address.
Edit System Gateway Select and enter the applicable Gateway IPv6 Address.

5. Click OK. The software updates the DCN eth0 settings.

To configure an IPv6 DHCP client:

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. In the IP Mode field, select IPv4 and IPv6.
4. When you configure an IPv6 network you do not need to configure IPv4.
In the IPv4 area, complete these settings:
o In the DHCP field, select Disabled.

o In the IP Address field, enter 0.0.0.0/0.

5. In the IPv6 area, complete these settings:
Field Description
DHCPv6 Select Enabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 61

Oscilloquartz: An ADVA Company Provisioning Communications

DHCPv6 Role The role is fixed as a DHCP client.

Stateless Address Auto
1. When the NE is working in router mode with IPv6
Configuration Forwarding enabled, you must set this option to Disabled,
the default. When the NE is working in host mode with IPv6
Forwarding disabled, you can set this option to Enabled.
RIPng 1. Select whether the RIPng packets are set to Enabled or
Disabled. The default is disabled. When you set RIPng to
enabled on an IPv6 interface, the interface receives the IPv6
route entry on the link, and then updates the local route table.
The interface also sends local IPv6 route entries to the link
using multicast packets.
IPv6 RA Prefix Enabled Select whether to advertise the prefix to link to in router
mode. This setting applies only when you set IPv6 forwarding
to enabled at the system level. This option and the Stateless
Address Auto Configuration are mutually exclusive. If you
set one to enabled, you must set the other to disabled.
IPv6 RA Prefix Enter the IPv6 prefix that the system will dispatch to link to in
router mode. This option is set to enabled only if you set the
IPv6 RA Prefix Enabled to Enabled.
To edit the system default gateway of the IPv6 address, select
Edit System Default Gateway, and then enter the applicable
gateway IPv6 address.
Edit System Gateway Select and enter the applicable gateway IPv6 address.

6. Click OK. The software updates the DCN (eth0) settings.

Disabling DHCP
You can disable DHCP in both IPv4 and IPv6.

To disable DHCP functionality for IPv4:

1. From the Configuration view, expand System > Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 62

Oscilloquartz: An ADVA Company Provisioning Communications

3. Complete these settings in the IPv4 area:

Field Description
DHCP Select Disabled.
IP Address Enter the applicable IP address.
Netmask Enter the applicable IP address.
RIPv2 Select Enabled or Disabled for the RIPv2 packets. The default
is disabled.
Edit System Default Select this option to edit the IPv4 gateway address.
Gateway
Gateway IPv4 Address Enter the applicable address.

4. Click OK. The software updates the DCN (eth0) settings.

To disable DHCP functionality for IPv6:

1. From the Configuration view, expand System > Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. In the IP Mode field, select IPv4 and IPv6.
4. When you configure an IPv6 network and IPv4 is not needed, in the IPv4 area, complete
these settings:
o In the DHCP field, select Disabled.

o In the IPv4 IP Address field, enter 0.0.0.0/0.

5. In the IPv6 area, complete these settings:
Field Description
DHCPv6 Select Disabled.
IPv6 Unicast Address Enter the applicable address.
RIPng Select Enabled or Disabled. If you set RIPng on an IPv6
interface to enabled, the interface receives the IPv6 route
entry on the link and updates the local route table. The
interface also sends local IPv6 route entries to the link using
multicast packets.
Edit System Default Select to set this gateway address, and then enter the
Gateway applicable enter the gateway IPv6 address.

Click OK. The software updates the DCN (eth0) settings.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 63

Oscilloquartz: An ADVA Company Provisioning Communications

Manually Configuring the IP Address

You can manually configure the IPv4 and IPv6 addresses for the DCN (eth0) port.

To manually configure the IPv4 address and netmask:

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. Specify these options in the IPv4 section:

l In the DHCP field, select Disabled.

l In the IPv4 field, enter the applicable IP address.
l In the Netmask field, enter the network mask address.
l In the RIPv2 menu, select Enabled or Disabled for the RIPv2 packets. The
default is disabled.

4. Click OK. The software updates the DCN (eth0) settings.

To manually configure the IPv6 address and prefix:

1. From the Configuration view, expand System>Communications.

2. Right-click DCN (eth0), and then select Edit Configuration. The Edit DCN (eth0)
window opens.
3. When you configure an IPv6 network and IPv4 is not needed, complete these fields in
the IPv4 area:

l In the DHCP field, select Disabled.

l In the IPv4 IP Address field, enter 0.0.0.0/0.

4. Set these options in the IPv6 area:

l In the DHCP field, select Disabled.

l In the IPv6 Unicast Address field, enter the applicable address and prefix.
l In the RIPng field, select Enabled or Disabled for RIPng packets. The
default is disabled. When you enable RIPng on an IPv6 interface, the
interface receives the IPv6 route entry on the link and updates the local
routing table. The interface also uses multicast packets to send local IPv6
route entries to the link.

5. Click OK. The software updates the DCN (eth0) settings.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 64

Oscilloquartz: An ADVA Company Provisioning Communications

Adding/Deleting IPV4 Static ARP

Entries
You can view, create, and delete static ARP entries for an IPv4 address. To edit an existing
IPv4 static ARP entry, delete it and add a new static ARP entry.

For more information on flushing the ARP cache, see Flushing the ARP
Cache.

Prerequisites
1. Configure the NE with an IP address and connect the NE to a DCN or LAN. See .
2. Sign in to the web-based EMS.

You can perform these tasks:

Task Link to Task

Add Static ARP Entries To add a static ARP Entry:
View Static ARP Entries To view static ARP entries:
Delete Static ARP Entries To delete a static ARP entry:

To add a static ARP Entry:

1. On the toolbar, select Configuration.

– or –
From the Application menu, select Configuration.
2. In the tree pane, next to the System entity, click +.
3. Right-click the Communications entity, and then select Add Static ARP Entry. The
Add Static ARP Entry window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 65

Oscilloquartz: An ADVA Company Provisioning Communications

4. To create a Static ARP Entry, in the Add Static ARP Entry area, set these options:

Field Setting
IP Address Enter a valid IPv4 address.
MAC Address Enter the Media Access Control (MAC) Address to be
added to the ARP entry. MAC addresses are hardcoded at
the factory.
Interface Name Select the applicable Interface Name.
When Management Traffic Bridging is enabled, only eth0
is allowed for the Interface Name. To enable
Management Traffic Bridging, see Configuring the
System Identity and Configuration.

5. Click OK.

To view static ARP entries:

Left-click the Communications entity, and then select the Static ARP Entries tab. The ARP
Entry Table is displayed.

To delete a static ARP entry:

1. Right-click the Communications entity, and then select Delete Static ARP Entry. The
Delete Static ARP Entry window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 66

Oscilloquartz: An ADVA Company Provisioning Communications

2. In the Static ARP Entry Table, select the ARP entries that you want to delete.
3. Click OK

Adding/Deleting IPv6 Static Routes

You can view, create, and delete static routes for an IPv6 address. To edit an existing IPv6
static route, delete it, and add a new static route.

Prerequisites
1. Configure the NE with an IP address and connect the NE to a DCN or LAN. See .
2. Sign in to the web-based EMS.
3. Ensure that the IP Mode of the DCN (etho) is set to IPv4 and IPv6 (see ).

You can perform these tasks:

Task Then See

Add an IPv6 Static Route See To add an IPv6 Static Route:
View IPv6 Static Routes See To view IPv6 Static Routes:
Delete an IPv6 Static Route See To delete an IPv6 Static Route:

To add an IPv6 Static Route:

1. On the toolbar, select Configuration.

– or –
From the Application menu, select Configuration.
2. In the tree pane, next to the System entity, click +.
3. Right-click the Communications entity, and then select Add IPv6 Static Route. The
Add IPv6 Static Route window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 67

Oscilloquartz: An ADVA Company Provisioning Communications

4. To create a IPv6 static route, in the Add IPv6 Static Route area, set these options:

Field Setting
Destination Enter a valid IPv6 address.
Gateway IP Address Enter a valid Gateway IPv6 address.
Interface Name Select the applicable Interface Name.
When Management Traffic Bridging is enabled, only eth0
configured with an IPv6 unicast address is allowed for the
Interface Name. To enable Management Traffic
Bridging, see Configuring the System Identity and
Configuration.
Metric Enter a value from 0 to 65535. The default is 0.
Advertise Route Select Enabeled to advertise the IPv6 static route or
Disabled to not advertise the IPV6 static rout.
The default is disabled. If enabled, the route is advertised
to the next hop.

5. Click OK.

To view IPv6 Static Routes:

Left-click the Communications entity, and then select the IPv6 Static Routes tab. The IPv6
Static Route Table is displayed.

To delete an IPv6 Static Route:

1. Right-click the Communications entity, and then select Delete IPv6 Static Route. The
Delete IPv6 Static Route window opens.

2. In the Delete column of the table, select the routes that you want to delete.
3. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 68

Oscilloquartz: An ADVA Company Provisioning Communications

Adding/Deleting IPv6 Static Neighbor

Entries
You can view, create, and delete static neighbor entries for an IPv6 address. To edit an
existing IPv6 static neighbor entry, delete it, and add a new static route.

For more information on flushing the NDP cache, see Flushing the NDP
Cache.

Prerequisites
1. Configured the NE with an IP address, connected the NE to a DCN or LAN (see ).
2. Logged in to the web-based EMS.
3. Ensure that the IP Mode of the DCN (etho) is set to IPv4 and IPv6 (see ).

These tasks can be performed:

Task Then See

Add an IPv6 Static Neighbor Entry. See To add an IPv6 static neighbor
entry:
View IPv6 Static Neighbor Entries. See To view IPv6 Static Neighbor
Entries:
Delete an IPv6 Static Neighbor See To delete a Static Neighbor Entry:
Entry.

To add an IPv6 static neighbor entry:

1. Select the Configuration application by performing either of these steps:

On the toolbar, click the Configuration icon.
– or –
From the Application menu, select Configuration.
2. In the selection tree, next to the System entity, click +.
3. Right-click the Communications entity, and then select Add IPv6 Static Neighbor
Entry.
The Add IPv6 Static Neighbor Entry window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 69

Oscilloquartz: An ADVA Company Provisioning Communications

4. To create a static neighbor entry, in the Add IPv6 Static Neighbor Entry area, set these
options:

Field Setting
IP Address Enter a valid IPv6 unicast address.
MAC Address Enter the MAC Address, where the Neighbor Discovery
Protocol (NDP) resolves the MAC address entered for the
target IP address.
Interface Name Select the applicable Interface Name.
When Management Traffic Bridging is enabled, only eth0,
if configured with an IPv6 unicast address, is allowed for
the Interface Name. To enable Management Traffic
Bridging, see Configuring the System Identity and
Configuration.

5. Click OK.

To view IPv6 Static Neighbor Entries:

Click the Communications entity, and then select the IPv6 Static Neighbor Enties tab.
The IPv6 Static Neighbor Entries Table is displayed.

To delete a Static Neighbor Entry:

1. Right-click the Communications entity, and then select Delete IPv6 Static Neighbor
Entry. The Delete IPv6 Static Neighbor Entry window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 70

Oscilloquartz: An ADVA Company Provisioning Communications

2. In the IPv6 Static Neighbor Entries Table, select the routes that you want to delete.
3. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 71

Oscilloquartz: An ADVA Company Provisioning Communications

Adding/Deleting IPv4 Static Routes

You view, create, and delete static routes for an IPv4 address. To edit an existing static route,
delete it, and add a new static route.

Prerequisites
1. Configure the NE with an IP address and connect the NE to a DCN or LAN. See .
2. Sign in to the web-based EMS.

These tasks can be performed:

Task Then See

Add IPv4 Static Routes See To add/delete an IPv4 Static Route:
View IPv4 Static Routes See To view IPv4 Static Routes:
Delete IPv4 Static Routes See To delete an IPv4 Static Route:

To add/delete an IPv4 Static Route:

1. On the toolbar, select Configuration.

– or –
From the Application menu, select Configuration.
2. In the tree pane, next to the System entity, click +.
3. Right-click the Communications entity, and then select Add Static Route. The Add
Static Route window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 72

Oscilloquartz: An ADVA Company Provisioning Communications

4. To create a static route, in the Add Static Route area, set these options:

Field Setting
Dest IP Address Enter a valid IPv4 address.
Subnet Mask Enter a valid IPv4 mask.
Gateway IP Address Enter a valid Gateway IPv4 address.
Interface Name Select the applicable Interface Name.
When Management Traffic Bridging is enabled, only eth0
is allowed for the Interface Name. To enable
Management Traffic Bridging, see Configuring the
System Identity and Configuration.
Metric Enter a value from 0 to 65535. The default is 0.
Advertise Route Select Enabeled to advertise the IPv4 static route or
Disabled to not advertise the IPV4 static rout.
The default is disabled. If enabled, the IPv4 static route is
advertised on every other interface that is RIP enabled.

5. Click OK

To view IPv4 Static Routes:

Left-click the Communications entity, and then select the Static Routes tab. The Static
Route Table is displayed.

To delete an IPv4 Static Route:

1. Right-click the Communications entity, and then select Delete Static Route. The
Delete Static Route window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 73

Oscilloquartz: An ADVA Company Provisioning Communications

2. In the Delete column, select the routes that you want to delete.
3. Click OK.

Setting up a Network Example for

GNE-to-SNE Over a Management
Tunnel
This example shows how to set up communications between two OSA 5422 devices using a
management tunnel in a laboratory or in a back-to-back small network configuration.

Figure 5 shows an example of:

l A back-to-back OSA 5422, where the EMS workstation, Gateway NE (GNE), and
Subtending NE (SNE) are on the same subnet, and the network port connectivity
between the devices is through a management tunnel.
l OSA 5422 #1 and the Workstation reside on LAN segment A.
l OSA 5422 #2 has no management LAN connection and has a network port
management tunnel connection to OSA 5422 #1.

For management tunnels where RIP is enabled, under a Denial of Service

attack scenario, the system will most likely discard the RIP PDUs. As a result
of this action, the system withdraws all RIP learned routes from the routing
table. On the GNE, this action causes the network to lose the route to the
SNE.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 74

Oscilloquartz: An ADVA Company Provisioning Communications

Figure 5: Workstation, GNE, and SNE on the Same Subnet

OSA 5422 #2 (SNE) Example:

Complete these steps on the OSA 5422 #2 (SNE)

1. On the OSA 5422 #2, complete these tasks:

o See Connecting Power Cables and Applying Power in the Provisioning and

Operations.
oConnecting to the Serial Port.
You should currently be logged in to the RS232 (serial port) of the OSA 5422 #2 using
the CLI.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 75

Oscilloquartz: An ADVA Company Provisioning Communications

2. Provision the eth0 (system) IP address using this CLI command entry:

ADVA--> configure communication

ADVA:comms--> configure eth0 ip-address 192.168.2.3 255.255.255.0
ADVA:comms-->

3. Provision the network port management tunnel using this 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 5, you should complete these settings

on the OSA 5422 #2:

l Set the management tunnel of OSA 5422 #2 to use the Ethernet

Layer 2 protocol.
l Specify VLAN-based with the VLAN ID set to 100.
l Disable DHCP.
l Set the IP address to 10.10.10.5 with a subnet mask of
255.255.255.0.
l Set RIPv2 to enabled.

4. To edit the management tunnel in order to enable RIPv2 packets, use this CLI command:

ADVA:comms--> configure mgmttnl mgmt_tnl-1

ADVA:comms:mgmt_tnl-1--> rip2Pkts-control enabled

5. Set the Management LAN port (eth0) admin state to unassigned using this CLI
command:

ADVA:comms:mgmt_tnl-1--> home
ADVA--> network-element ne-1
ADVA-NE-1--> configure nte nteosa5422-1-1-1
ADVA-NE-1:nteosa5422-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

6. Add a static route to point to the management tunnel on the OSA 5422 #2 using this CLI
command:

ADVA--> configure communication

ADVA:comms--> add ip-route nexthop 0.0.0.0 0.0.0.0 10.10.10.4 phoenix1 1 disabled

7. Use a show system command and verify that you disabled the proxy ARP setting.
If proxy ARP is enabled, use this command:
ADVA:comms--> home
ADVA--> configure system
ADVA:system--> proxy-arp disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 76

Oscilloquartz: An ADVA Company Provisioning Communications

Verify that the Proxy ARP option is set correctly for the devices. If two or
more Oscilloquartz: An ADVA Company NEs or OSA 5422 devices are
connected through SDCC or a Management Tunnel and are connected to
the same LAN segment, then only one of the them should have the Proxy
ARP option enabled. Otherwise, there will be multiple ARP responses for a
single ARP request for a remote reachable IP address from each NE/device
in the same LAN that has Proxy ARP enabled.

8. Log off from the CLI session and remove any commissioning cables such as an Ethernet
cable and console cable from the OSA 5422 front panel connectors, as required.
9. Connect the optical cables to the OSA 5422 network port front panel connectors, if they
are not already connected.

OSA 5422 #1 (GNE) Example

Complete these steps on the OSA 5422 #1 (GNE):

1. On the OSA 5422 #1, these tasks:

o See Connecting Power Cables and Applying Power in the Provisioning and

Operations.
oConnecting to the Serial Port.
You should currently be logged in to the RS232 (serial port) of the OSA 5422 #1 using
the CLI.
2. Provision a management tunnel using this CLI command:
ADVA--> configure communication
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 5, these settings should be set on the OSA 5422 #1:
o The management tunnel of the OSA 5422 should be set to the Ethernet Layer 2

Protocol.
o VLAN based with the VLAN ID set to 100.
o DHCP disabled.
o The IP address should be set to 10.10.10.4 with a Subnet Mask of 255.255.255.0.
o RIPv2 should be set to enabled.
3. Edit the management tunnel to enable RIPv2 packets:
ADVA:comms--> configure mgmttnl mgmt_tnl-1
ADVA:comms:mgmt_tnl-1--> rip2Pkts-control enabled

4. Provision the eth0 (system) IP address using this CLI command entry:
ADVA:comms:mgmt_tnl-1--> home
ADVA--> configure communication
ADVA:comms--> configure eth0 ip-address 192.168.2.2 255.255.255.0
ADVA:comms-->home

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 77

 Oscilloquartz: An ADVA Company Provisioning Communications

5. Enable the Proxy ARP setting using this CLI command:

ADVA:comms--> home
ADVA--> configure system
ADVA:system--> proxy-arp enabled

Verify that the Proxy ARP option is set correctly for the devices. If two or
more Oscilloquartz: An ADVA Company NEs or OSA 5422 devices are
connected through SDCC or a Management Tunnel and are connected to
the same LAN segment, then only one of the them should have the Proxy
ARP option enabled. Otherwise, there will be multiple ARP responses for a
single ARP request for a remote reachable IP address from each NE/device
in the same LAN that has Proxy ARP enabled.

6. Log off the CLI session, and then remove any commissioning cables such as an Ethernet
cable and console cable from the OSA 5422 front panel connectors, as required.
7. Ensure the DCN connection for the LAN Segment A connects to the MGMT LAN (eth0)
port.
8. Connect the optical cables to the OSA 5422 network port front panel connectors, if they
are not already connected.
9. Observe the Network Port Net and Act LEDs on the front panel. They should be solid
green. If the LEDs are not solid green, troubleshoot the connections between the
OSA 5422 #1 and the OSA 5422 #2.
10. Depending on your configuration, either:
o Set the Web Based EMS workstation default gateway to point to the GNE of the

OSA 5422 Management LAN port IP address.

–or–
o Create a static route on the PC to communicate to the SNE, such as from the
Windows command prompt. Then enter route add 192.168.2.3 mask
255.255.255.255 192.168.2.2 according to the example in Figure 5 so that you can
connect to the SNE.
11. From the Web Based EMS Workstation, verify connectivity to the OSA 5422 #1 and
OSA 5422 #2:
a. Open a browser window, and then enter the IP address of the OSA 5422 #1 to access
the Web Based EMS.
b. Log in using a valid user name and password, where the default User ID is root and
password is ChgMeNOW.
c. Repeat these steps for the OSA 5422 #2.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 78

 Chapter 3

Provisioning Operations
This section contains system provisioning details for the OSA 5422 and provides a
recommended workflow for new installations. You can also use these procedures to
incorporate provisioning changes to existing systems.

This section includes these topics:

Provisioning the OSA 5422 79

Verifying the Installed Shelf and Oscillator Type 80
Entity State Descriptions 81
Upgrading the Software Version 88
Provisioning System Options 92
Activating Software Licenses 115
Provisioning Common Units 117
Provisioning Secure Access 140
Managing Certificates 152
Provisioning SNMP Access 164
Provisioning Access Ports 164
Provisioning Synchronization 168
Provisioning the Network Time Protocol 212
Provisioning the Precision Time Protocol 225

Provisioning the OSA 5422

First install, cable, power, and set the initial communications for the device. Before you
implement the system into your network, complete the procedures in this section in the
listed order. You can also use these procedures to change existing systems. See the
OSA 5422 Installation and Commissioning Manual for more information about the initial
procedures.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 79

 Oscilloquartz: An ADVA Company Provisioning Operations

Recommended Steps after the Initial Power On

1. Connecting to the Serial Port.
2. Setting Up the OSA 5422 DCN eth0 Port Through the Serial Port.
3. Verifying Connection with the Web-Based EMS.
4. Verifying the Installed Shelf and Oscillator Type on p. 80.
5. Upgrading the Software Version.
6. Provisioning System Options on p. 92.
7. Provisioning Common Units on p. 117.
8. Provisioning Secure Access on p. 140.
9. Provisioning SNMP Access on p. 164.
10. Provisioning Access Ports on p. 164.
11. Provisioning Synchronization on p. 168.
12. Activating Software Licenses on p. 115.
13. Provisioning the Precision Time Protocol on p. 225.
14. Provision Syncjack (see Syncjack Testing).
15. Clear all alarms (see Recommended Steps for Clearing Alarms on p. 544).
16. Creating a Backup Database on p. 415.
17. Monitoring Access Ports.

Verifying the Installed Shelf and

Oscillator Type
You can verify the shelf and the oscillator type installed with the OSA 5422.

For OSA 5422 part numbers, see Equipment Part Numbers in the OSA 5422
System Description.

Prerequisites
1. Configure the OSA 5422 with an IP address.
2. Connect the OSA 5422 to a DCN or LAN. See Setting Up the OSA 5422 DCN eth0 Port
Through the Serial Port.
3. Sign in through EMS.

To verify the installed shelf equipment type and oscillator type:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 80

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. In the tree pane, expand System and then select NE-1. View the shelf inventory:

3. In the Shelf Physical Inventory area, Part Number field, verify the part number to
ensure that the proper equipment is installed.

Entity State Descriptions

The system maintains a state model for each entity in the system and derives the state of an
entity from these states:

Administration State 81
Details about the Administration State Model 82
Operational State 85
Secondary State 85

Administration State
Several rules relate to the behavior of the administrative state as it relates to the parent-
child relationship of objects. For example, a parent state must already be in a certain state
for a child to be valid in that same state. The administrative state model consists of these
states.

State Description
IS (in-service) The normal, fully-operational, and configured state of an entity.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 81

Oscilloquartz: An ADVA Company Provisioning Operations

State Description
Management Also known as the Out of Service state. In this state, the system
squelches all alarms for the entity. The system clears any standing
alarm and then re-raises that alarm as being in a not-alarmed (NA)
condition. The intended use of this state is to squelch alarms that are of
no interest. In addition, for any traffic-affecting provisioning change,
the system places the entity into this state, but does not enforce this
requirement. Additional, associated characteristics of this state are that
user data and management traffic continue to flow.
Maintenance Known as an Out of Service state. For example, this state inherits the
properties described in the Management state. Additional, associated
characteristics of this state are that the system can perform
maintenance operations on an entity that is in this state. Maintenance
operations might affect user data or management data. Maintenance
state operations include, for example, loopback, Etherjack diagnostic,
and so on.
Disabled Also known as an Out of Service state. For example, this state inherits
the properties described in the Maintenance state. In addition, no user
data traffic passes in this state. Its purpose is to disable user traffic
while still preserving management connectivity with the entity.
Unassigned This state is essentially equivalent to deletion of an entity. The system
factors no entity in this state into any of the rule verification. An entity
in this state raises no alarms and carries no traffic. You must first set the
administrative state to unassigned before you change the service type
of an access port.

Details about the Administration State Model

The management, maintenance, and disabled states are out-of-service
(OOS) states. An entity that is in transition between any of these three states
has no impact on its child or parent entities.

l The equipment administrative state model uses only the In-service and
management states.
l When in the management or maintenance state, the system supresses all alarms
against that entity. Otherwise, the entity functions normally.
l When in the disabled state, the system suppresses user data traffic.
l To perform maintenance actions such as diagnostics on an entity, you must first set
the entity into the maintenance state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 82

Oscilloquartz: An ADVA Company Provisioning Operations

l An entity in the disabled state will not pass user data traffic. Management traffic,
such as management tunnel traffic and EFM OAM, continues to pass in this state.
l The operational state of an entity can be either:
o Normal

o Outage: The operational state of an entity is in outage when the admin state is
unassigned, or when the secondary state is FAF, FLT, SGEO, UEQ, MEA.
l The facility administrative state model uses all states described in the operational
state. The exceptions are:
o The disabled state applies only to access ports.

o Network ports do not support the disabled state. In relation to network ports,
the unassigned state does not apply to the working access port.
o The working access port cannot be unassigned.
l The DCN facility administrative state model is limited to these states:
o In-service

o Management
o Unassigned
l EVC flows, policers and shapers support these states:
o In-service

o Management
o Disabled
o Unassigned

EVC flows: The system supports the admin state control between in-service and
management and derives the disabled and unassigned states from the parent port.

Policers and Shapers: The admin state is read-only. The system always derives the state from
the parent EVC.

You can edit the state of the equipment, port, and EVC flow. The system derives the policer
and shaper states directly from the EVC flow state. According to the rules outlined as
follows, you can edit the EVC state.

The system can overwrite the state of the individual EVC by a subsequent
edit of the parent port object. See the behavior rules that follow.

Understanding Parent-Child Rules

The parent-child rules for equipment entities are:

l If an equipment entity is in-service, its child entity port entities can be any state
that the entity supports.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 83

Oscilloquartz: An ADVA Company Provisioning Operations

l If an equipment entity is management, its child entities can be any out of service
state or unassigned.
l If an equipment entity is unassigned, its child entities must also be unassigned.

The parent-child rules for rort entities are:

l If a port entity is in in-service state, its child entities, or EVCs, can also be in an in-
service, management, or unassigned state.
l If a port entity is in a management, maintenance, or disabled state, its child entities
can be in a management or unassigned state.
l If a port entity is in an unassigned state, its child entities must be in an unassigned
state.

The parent-child rules for EVC flow entities are listed as follows.

You cannot edit EVC child entities.

l If an EVC entity is in an in-service state, its child entities such as policers and
shapers are in-service.
l If an EVC entity is in a management state, its child entities are also in management.
l If an EVC entity is in an unassigned state, its child entities are also in an unassigned
state.

If you change the equipment entity state from in-service to management, the port state will
also change from in-service to management. Any port already in an OOS state, including
management, maintenance, or disabled, remains in that state. Any port already in the
unassigned state remains in the unassigned state.

If you change an equipment entity from management to in-service, no changes occur to the
port state. The port state will remain as it was.

Understanding Many-to-One Relationships

Because of the many-to-one relationship between port entities and EVCs flows, the system
implements these behaviors:

l You can edit a port entity from in-service to management, maintenance, or

disabled. All EVC flows that are children of this port then change from in-service to
management. If an EVC was already in management or unassigned before you
made edits to the port state, the state of that port stays the same.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 84

Oscilloquartz: An ADVA Company Provisioning Operations

l You can edit a port entity from being in-service, management, maintenance, or
disabled to be unassigned. If so, all EVC flows that are children of that port change
to unassigned.

This effect will also occur if you edit the port parent entity. For example, if you edit the
equipment entity state in a way that affects the port administration state, the rules in the
previous list means that these edits will also propagate to the port child entities.

Because of the many-to-one relationship between port entities and EVC flows, you can
implement these behaviors:

l You can edit a port entity from management, maintenance, or disabled to In-
Service. This edit changes all EVC flows that are children of that port from
management to in-service. If an EVC was unassigned before you made an the edit
of the port state, the EVC will remain unassigned.
l If you edit a port entity from unassigned to management, maintenance, or
disabled, all EVCs flows that are children of that port change to management.
l If you edit a port entity from unassigned to in-service, all EVCs flows that are
children of that port change to in-service.
l If you edit a port entity from unassigned to disabled, all EVCs flows that are
children of that port change to in-service.

This effect also occurs as a result of an edit of the EVC parent entity. For example, if you edit
the port entity state in such a way that it affects the EVC admin state, the rules listed in the
previous list will apply also propagate to the EVC child entities.

Operational State
This attribute contains the current actual state of the entity. This attribute is based on both
the provisioned state and the actual physical state of the entity.

Secondary State
This attribute refines or provides added information about the operational state of the
entity.

This table details the state values and their definitions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 85

Oscilloquartz: An ADVA Company Provisioning Operations

Table 3: State Codes and Descriptions

State Entity State Definition
Administration Disabled User traffic does not pass in this state,
State - Equipment but management traffic does pass. In
and Facilities this state, the system squelches alarms.
IS The normal, in-service, traffic passing
state of the entity.
Maintenance Mandatory state for initiating diagnoses.
In this state, the system squelches
alarms.
Management This state is the out-of-service state for
an entity. Traffic still passes, and the
system squelches alarms but does not
report them.
Unassigned In this state, user or management traffic
does not pass, and the system does not
monitor alarms.
Operational State - Normal Normal, in service, traffic passes in this
Equipment and state.
Facilities Outage The entity is not operational because of
an 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.
STBY Standby hot.
SGEO Supported entity outage.
MEA Mismatched equipment.
UAS Unassigned.
UEQ Unequipped.
INIT Initializing.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 86

Oscilloquartz: An ADVA Company Provisioning Operations

Table 3: State Codes and Descriptions

State Entity State Definition
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 No backup database.
No space left No disk space left.
No software to install No software to install.
Permission denied Permission denied.
Revert failed Revert failed.
Server unreachable Server unreachable.
Success Successful completion.
Software not Software is not installed.
installed
Upgrade failed Upgrade failed.
Validation timer not Validation timer is inactive.
active
Database or Database Backup Database backup.
Upgrade Current Database Download Database download.
State
Database Restore Database restore.
Database Upload Database upload.
Idle Idle.
Rebooting A reboot is occurring.
Software Cancel Software cancel upgrade.
Upgrade
Software Download Software download.
Software Install Software install.
Software Upgrade Software upgrade.
Software Validate Software validate.
Software Revert Software revert.
Protection Unit Active Indicates this unit is the active unit.
State Standby Indicates this unit is the standby unit.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 87

Oscilloquartz: An ADVA Company Provisioning Operations

Upgrading the Software Version

Complete the instructions in this section to upgrade the software. The software upgrade is a
multiple-step process. After an upgrade from an earlier release, stored passwords continue
to use MD5 hashing. Recreate these passwords to use SHA512 hashing.

ADVA does not support software downgrades.

1. Transfer the new software from an external repository to a temporary location on the
node. Supported transfer protocols are:
o HTTP (web)

o HTTPS (web)
o FTP
o SFTP
o SCP
2. Install the software on the node.
3. Activate the software. The OSA 5422 supports immediate or scheduled activation and
includes a validation timer. You can revert to the previous version:
o In scheduled activation, you can cancel the activation at any time before the

activation occurs.
o If you also set a validation timer, you must accept the upgrade by the specified time,
or the device automatically reverts to the previous version.

Activation resets the device, temporarily interrupts traffic, and cancels all
active sessions.

Follow these guidelines when you upgrade the software:

l We recommend that you save the configuration files before or after you upgrade
the new software, not during a software upgrade.
l The OSA 5422 provides the ongoing standing conditions to keep you informed
about the upgrade status. By default, the software sets these conditions with a
notification code of Not Reported. To view these conditions, select Maintenance >
System, and then select the Conditions List tab.
l To dynamically see the status conditions, edit the notification codes for SWDL and
Data Base condition types to NA for not alarmed. The conditions will then display
in the Alarm pane. These are the conditions:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 88

Oscilloquartz: An ADVA Company Provisioning Operations

o SWDL – File Transfer In Progress: the system copies the software from a remote
source to temporary memory.
o SWDL – Installation In Progress: the system writes the software to the shelf.
o SWDL – Activation In Progress: the system activates the software or schedules
the software for activation.
o SWDL – Validation In Progress: the system activates the software and sets the
validation timer.
l In the Configuration > System > Audit Log tab, you can see the settings for the
scheduled activation or validation timer.

To improve performance, internet browsers save websites information in

cache and cookies. If an "Operation Error: unexpected token" message
appears after an upgrade, clear the browser cookies to resolve this mes-
sage.

Upgrading Tasks
Upgrading the Software Version 89
Validating the Upgrade 91
Canceling a Scheduled Activation 91

Upgrading the Software Version

Prerequisites
1. Assign an IP address to the node.
2. Connect the node to a DCN or to a LAN. Setting Up the OSA 5422 DCN eth0 Port
Through the Serial Port.
3. Log in to EMS.
4. Disable Clock e-PRTC mode before an upgrade.

To upgrade the software version:

1. On the toolbar, select Maintenance, or from the Application menu, select

Maintenance.
2. In the tree pane, expand System > Administration.
3. Right-click Upgrade, and then select Transfer.
The Transfer Upgrade window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 89

Oscilloquartz: An ADVA Company Provisioning Operations

4. In the Method area, File Transfer Method field, select FTP, SFTP, or SCP.
The window displays a File Transfer area.
5. In the File transfer area, complete these fields to set the file transfer options required to
access the FTP, SFTP, or SCP server:

Field Setting
Server IP a. Select the applicable server IP as either IPv4 or IPv6. The default is
IPv4.
b. Enter the applicable server IP address.
User ID Enter the applicable user ID.
User Password Enter the applicable password.
Software Image Enter the path to the image file and include the IMG file extension.

6. Click OK.
The file transfer begins, and a status bar displays the progress:

The Status changes from In progress to Success, which shows that the system
completed the file transfer.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 90

Oscilloquartz: An ADVA Company Provisioning Operations

7. In the tree pane, right-click Upgrade, and then select Install.

The Install Upgrade window opens.

8. Click OK.
The window displays a progress bar. After the system completes the installation, the
status changes from In progress to Success.

Validating the Upgrade

If you set a validation timer, you must validate the upgrade before the time-out expires.
Otherwise the device automatically reverts to the previous software version. If you are
unable to log in, the validation timer eventually times out and the node reverts to the
previously installed software version. After the node resets, you can then reconnect.

If you did not set a validation timer, and after the upgrade you cannot access the device,
contact ADVA Technical Support.

To validate the upgrade:

1. In the tree pane, expand the System>Administration entities.

2. Right-click Upgrade, and then select Validate.
3. To validate the upgrade, click Accept Upgrade.
–or–
To cancel the upgrade and revert to the previous software version, select Cancel
Upgrade.
4. Click OK.

Canceling a Scheduled Activation

You can cancel a scheduled activation any time before its specified start date and time.

1. On the toolbar, select Maintenance, or from the Application menu, select

Maintenance.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 91

Oscilloquartz: An ADVA Company Provisioning Operations

2. In the tree pane, expand System>Administration.

3. Right-click Upgrade, and then select Activate.
The Activate Upgrade window opens with the Activate Now field selected.

4. Select Cancel Previous Scheduled Activation, and then click OK.

Provisioning System Options

Provision all system options in the Configuration application, which you access as follows:

l On the toolbar, click Configuration.

– or –
l From the Application menu, select Configuration.

Provisioning system options includes these tasks:

Configuring the System for Optimal Security 92

Configuring the System Identity and Configuration 93
Configuring SNMP Traps Forwarding for Login or Logout 97
Configuring Logs 97
Configuring the Management Access Control List 102
Editing the Security Banner 103
Editing the Time Zone 104
Configuring an NTP Client 107
Configuring PTP or NTP Security for IP Addresses 109

Configuring the System for Optimal Security

Configure these settings for optimal system security and for complying with security scans.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 92

Oscilloquartz: An ADVA Company Provisioning Operations

1. Disable HTTP and set SSL Cipher Strength to high:

a. In the Configuration application, right-click System > Edit System.
b. Set these options:

Area Field Setting

Configuration HTTP Disabled.
SSL Cipher Strength High.

c. Click OK.
2. Delete default SNMP communities:
a. Right-click SNMP > Delete Community.
b. Select private and click Apply.
c. Select public and click OK.

You can also complete these configurations via the CLI:

ADVA--> configure system

ADVA:system--> http disabled
ADVA:system--> back
ADVA--> configure user-security
ADVA:user-sec--> config-ssl-strength high
ADVA:user-sec--> back
ADVA--> configure snmp
ADVA:snmp--> delete community public
ADVA:snmp--> delete community private

For additional security settings that are not required for general security scans, complete
these configurations:

l Create IPv4/IPv6 access lists.

l Create ICMP filter.
l Change default passwords and create non-default users.
l Set the password policy to high.
l Delete default SNMPv3 USM users and create non-default users with proper
authentication and privacy.

Configuring the System Identity and

Configuration
This section explains how to configure the system identity and configuration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 93

Oscilloquartz: An ADVA Company Provisioning Operations

Prerequisites
1. Configure the OSA 5422 with an IP address.
2. Connect the OSA 5422 to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port
Through the Serial Port).
3. Log in using the EMS.

To configure the system identity and configuration:

1. In the selection tree pane, right-click the System entity, and then select Edit System.
The Edit System window opens.

2. You can change the system-level options shown in the table that follows. For more
information about these options, see System Configuration Options and Rules.

Area Field Setting

Identity CLI Prefix Enter a new CLI prompt prefix.
– or –

Leave the default ADVA prompt prefix.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 94

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Management Select Enabled or Disabled. The default is
Traffic Bridging Disabled.
Mgmt Traffic Select Enabled or Disabled. The default is
Bridging Security Disabled.
Note: No more MAC addresses in the valid range
are available. We suggest that you do not use
this option in new deployments.
Proxy ARP Select Enabled or Disabled. The default is
Disabled.
IPv6 Forwarding Select Enabled to allow IPv6 routing between
management interfaces. The default is Disabled.
Date Select the date in the format: yyyy-mm-dd.
Time Enter the time in the format: hh:mm:ss.
System Time Of Select the applicable system Time of Day mode.
Day The default is Local.
FTP Select Enabled or Disabled. The default is
Disabled.
FTP Port Number Set the FTP server port number. 1 to 65535. The
default is 21.
HTTP Select Enabled or Disabled. The default is
Enabled.
HTTPS Select Enabled or Disabled. The default is
Enabled.
SSL Cipher Select the applicable strength of the SSL cipher.
Strength The default is Low.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 95

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration SCP Select Enabled or Disabled. The default is
(continued) Enabled.
Serial Port Select Enabled or Disabled. The default is
Enabled.
Serial Port Auto Select Enabled or Disabled. The default is
Log Off Enabled.
SFTP Select Enabled or Disabled. The default is
Enabled.
SSH Select Enabled or Disabled. The default is
Enabled.
Telnet Select Enabled or Disabled. The default is
Disabled.
Authentication Select one of these options:
Traps
l Enabled: Enables SNMP Aauthentication traps.
If enabled, the system sends SNMP
authentication traps to the configured trap
host.
l Disabled: The system sends no traps related
to SNMP authentication, which is the default.
Note: This setting excludes sending traps related
to user login or logout. To define settings related
to the user login or logout, see the Login/Logout
Trap Control setting.
Login/Logout Trap Select one of these options. The system sends:
Control
l All: All login and logout timeout traps.

l Failed Login: Only failed login traps.

l Disabled: No traps related to user login or
logout. This is the default option.
See Configuring SNMP Traps Forwarding for
Login or Logout.
CLI Security Select Enabled or Disabled. The default is
Prompt Disabled.
SNMP Engine ID Use to edit the SNMP engine ID, which consists of
22 hexadecimal characters.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 96

Oscilloquartz: An ADVA Company Provisioning Operations

You can edit the system identity information that is unavailable to edit in
this window, such as Name, Description, Location, and Contact. Right-click
NE-1, and then select Edit Configuration.

3. Verify that the information you entered in Step #2 applies, and then click OK. The
window updates to reflect the data you entered.

Configuring SNMP Traps Forwarding for Login or

Logout
You can configure whether the system forwards secured event SNMP traps to a trap host,
such as the FSP Network Manager, whenever a user logs in or out of the application. If
enabled, the software sends the SNMP login and logout traps to the configured trap host.
By default, the device does not send these login and logout traps. This setting is relevant
only when you use the SNMP management interface.

You can configure forwarding SNMP login and logout traps on any SNMP
version. We recommend that you disable this setting if the SNMP version
does not allow encryption, such as with SNMPv1 or SNMPv2.

To configure SNMP traps forwarding for login and logout activity:

1. In the tree pane, right-click the System entity, and then select Edit System. The Edit
System window opens.
2. In the Configuration area, Login/Logout Trap Control field, select one of these
options:
o All: The software sends all login and logout timeout traps.

o Failed Login: The system sends only failed login traps.

o Disabled: The system sends no traps related to the user login or logout, which is the
default.
3. Click OK.

Configuring Logs
You can configure these types of logs in the system:

l Security Logs (see Configuring Security Logs).

l Alarm Logs (see Configuring Alarm Logs)
l Audit Logs (see Configuring Audit Logs).
l System Logs (see Configuring System Logs).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 97

Oscilloquartz: An ADVA Company Provisioning Operations

Prerequisites
First complete these tasks:
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN, see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port.
3. Log in using EMS.

Configuring Security Logs

To configure security logs:

1. In the selection tree pane, right-click the System entity, and then select Edit Security
Log. The Edit Security Log window opens.

2. In the Configuration area, Syslog field, select either:

o Enabled to include Security Log messages

– or –
o Disabled to exclude Security Log messages. The default is Disabled.
3. Click OK.

Configuring Alarm Logs

1. In the selection tree pane, right-click the System entity, and then select Edit Alarm Log.
The Edit Alarm Log window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 98

Oscilloquartz: An ADVA Company Provisioning Operations

2. In the Configuration area, Syslog menu, select either:

o Enabled to include Alarm Log messages in the Syslog.

– or –
o Disabled to exclude Alarm Log messages in the Syslog. The default is Disabled.
3. From the Local Logging menu, select either:
o Enabled to enable sending Alarm messages to the local log (Alarm Log tab). The

default is enabled.
– or –
o Disabled to disable sending Alarm messages to the local log (Alarm Log tab)
4. Click OK.

Configuring Audit Logs

1. In the selection tree pane, right-click the System entity, and then select Edit Audit Log.
The Edit Audit Log window opens.

2. In the Configuration area, Syslog menu, select either:

o Enabled to include Audit Log messages in the Syslog.

– or –

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 99

Oscilloquartz: An ADVA Company Provisioning Operations

o Disabled to exclude Audit Log messages in the Syslog. The default is Disabled.
3. From the Local Logging menu, select either:
o Enabled to enable sending Alarm messages to the Alarm Log tab local log. The

default is Enabled.
– or –
o Disabled to disable sending Alarm messages to the Alarm Log tab local log.
4. Click OK.

Configuring System Logs

1. In the selection tree pane, right-click the System entity, and then select Edit Syslog. The
Edit Syslog window opens.

2. In the Log Server Configuration area, Time Stamp Format menu, select the particular
time stamp format used in the system log:

l ADVA: Uses the format YYYY-MM-DD hh:mm:ssxxx:yy. This is the default

option.
– or –
l RFC3164: Uses the format Mmm dd hh:mm:ss.

3. In the Log Server 1 Edit, Log Server 2 Edit, and Log Server 3 Edit areas, enter syslog
server information for up to 3 servers including:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 100

Oscilloquartz: An ADVA Company Provisioning Operations

Field Setting
IP Address a. Select the applicable server IP:
IPv4
– or –
IPv6.
The default is IPv4.
b. Enter the applicable server IP address.
Port Enter the Port number for the log server. The default is 514.

4. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 101

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring the Management Access Control List

Use the management access control list (ACL) to limit access to the NE through DCN or
management tunnels to specific IP addresses or IP address ranges, or subnetworks. For
example, you can use the management ACL to restrict the management, PTP, and NTP
connections that the system accepts. You can have up to 100 entries and individually enable
or disable each entry. Enabled entries apply to all management interfaces.

Perquisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in using EMS.

To configure the management ACL:

1. In the tree pane, right-click the System entity, and then select Edit MGMT ACL. The
Edit MGMT Access Control List window opens.

2. The Access Control List table contains 100 entries. Each entry consists of these
configurable options:

Column Setting
IP Version Select the type of IP address as either IPv4 or IPv6. The default is IPv4.
IPv4 Address Enter the IPv4 address of the user or subnet that the system allows to
access the OSA 5422. This column is enabled only if the IP version is
set to IPv4.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 102

Oscilloquartz: An ADVA Company Provisioning Operations

Column Setting
IPv4 Address Enter the IPv4 address of the user or subnet that the system allows to
access the OSA 5422. This column is enabled only if the IP version is
set to IPv4.
Network Mask Enter the network mask for the user or subnet IPv4 address that the
system allows to access the OSA 5422. This column is enabled only if
the IP version is set to IPv4.
IPv6 Address Enter the IPv6 address of the user or subnet that the system allows to
access the OSA 5422. This column is enabled only if the IP version is
set to IPv6.
Prefix Enter the prefix for the user or subnet IPv6 address that the system
allows to access the OSA 5422. This column is enabled only if the IP
version is set to IPv6.
Control Defines whether this IP address definition in the system is either:

l Enabled
– or –
lDisabled.
The default is Disabled.

3. After you define the IP addresses in the ACL, click OK. The MGMT ACL tab displays the
updated ACL.

Editing the Security Banner

This section explains how to edit the security banner, which displays during each CLI or GUI
log in. You can edit the banner to display a customized message of up to 1024 characters.
The default banner message is:

This is a private system. Unauthorized access or use may lead to prosecution.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To edit the security banner:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 103

Oscilloquartz: An ADVA Company Provisioning Operations

1. In the selection tree pane, right-click the System entity, and then select Edit Banner.
The Edit Banner window opens.

2. In the Banner area, edit the text according to your requirements.

3. Click OK. The window updates to display the edited banner message.

Editing the Time Zone

You can configure the system time zone and Daylight Saving Time (DST) depending on your
system requirements. The system time uses the configured time zone and DST for all system
time references.

After you change the time zone or DST, the system generates any alarms and events that
occur afterwards with the new local time in the alarm timestamp. The alarm and event
timestamp field indicates a UTC offset, such as 2016-08-28, 18:40:03 (–2:00). If the time zone
changes while an event or alarm is active, existing alarms and events remain the same. The
system does not change previous alarms and events in the alarm logs, so the timestamp of
the original event remains the same.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To edit the time zone:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 104

Oscilloquartz: An ADVA Company Provisioning Operations

1. In the selection tree pane, right-click the System entity, and then select Edit Time Zone.
The Edit Time Zone window opens.

2. Set these options:

For some fields, you can configure the related list selections only if you set
DST Control Enabled to Enabled.

Area Field Setting

Configure Time UTC Offset Enter the applicable UTC offset in hours and
Zone minutes using the format +/- hh:mm. The default
is +00:00.
Time Zone Enter a name for the time zone. The maximum
Name number of characters is ten.

DST Control Define whether the user can set the DST by
Enabled selecting either Enabled or Disabled. The default is
Disabled, and the other options are disabled. When
Enabled, you can set the other options.
DST Start Month Select the DST Start Month. The default is March.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 105

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

DST Start Day Enter the DST Start Day using this format:
l Day-of-week >= day-of-month
– or –
l Day-of-week =< day-of-month
The default is SUNDAY>=8. For example,
Sunday>=15 means that DST starts on the first
Sunday on or after or the 15th day of the specified
month.
DST Start Time Enter the DST Start Time in hours and minutes using
the format hh:mm. The default is 02:00.
DST Offset Enter the DST Offset for the UTC in hours and
minutes using the format +/- hh:mm. The default
is +01:00.
DST End Month Select the DST End Month. The default is
November.
DST End Day Enter the DST End Day in this format:
l Day-of-week >= day-of-month
– or –
l Day-of-week =< day-of-month
The default is SUNDAY<=7. For example,
Monday<=18 means that DST ends on the last
Monday before or on the 18th day of the specified
month.
DST End Time Enter the DST End Time in hours and minutes in the
format hh:mm. The default is 02:00.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 106

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

UTC To TAI Leap59 Set to True to configure leap59 second adjustment
Offset when when the TOD input protocol does not
provide leap second information.
Leap61 Set to True to configure leap61 second adjustment
when the TOD input protocol does not provide leap
second information.
UTC to TAI Enter the UTC offset from TAI in seconds when the
Offset TOD input protocol does not provide UTC offset
information.
Valid values: -45000 to 45000, the default is 37.
Leap Second Enter the next leap second date when the
Date TOD input protocol does not provide leap second
information.
Date format: ddmmyy.

3. After you complete the time zone options, click OK.

Configuring an NTP Client

You can configure an NTP client to have a primary and backup server for a particular IP
address (IPv4 and IPv6).

IPv4 addresses must be other than zeros or all ones. For example,
255.255.255.255. IPv4 addresses must also be addresses other than a sub-
net broadcast address, multicast address, or experimental subnet.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure NTP:

1. In the tree pane, right-click the System, and then select Edit NTP.
The Edit NTP window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 107

Oscilloquartz: An ADVA Company Provisioning Operations

2. In the Configuration area, State field, select Enabled for the NTP state.
3. If you set the NTP state to Enabled, you must define at least one primary server, which
you designate by setting its IP address. Complete these fields.

Area Name Field Name Setting

Configuration Primary Server [MANDATORY] Define a primary server:

a. Select the applicable server IP type:

IPv4
– or –
IPv6.
The default is IPv4.
b. Enter the applicable server IP address.
Backup Server [OPTIONAL] If a second server exists, complete
these tasks:

a. Select the applicable server IP type:

IPv4
– or –
IPv6.
The default is IPv4.
b. Enter the applicable server IP address.
Polling Interval Set the polling interval for NTP messages: 16, 32,
64, 128, 256, 512, or 1024 seconds. The default is
16 seconds.
Switch server Active server If you configure both a primary and a backup
server, to activate either one, select the
applicable server from the menu.

4. After you complete the NTP options, click OK.

5. Click the System entity.
6. In the Identification tab, verify that the System Time of Day now shows NTP.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 108

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring PTP or NTP Security for IP Addresses

The OSA 5422 has an integrated IPv4 and IPv6 security mechanism to reduce the likelihood
of a system failure. A failure might occur if a Distributed Denial-of-Service (DDos) attack
occurs and filters out NTP/PTP packets. You can configure two security features: an ICMP
filter and an ACL. These filters relate to the IPv4 and IPv6 data plane (PTP/NTP), and do not
include management.

Configuring the IP Traffic ACLs 109

Configuring the ICMPv4 and ICMPv6 Filters 112

Configuring the IP Traffic ACLs

You can use the ACL for IPv4 and IPv6 traffic to filter for in-band management, PTP, and
NTP packets from a specific IP source address. This source address includes the IP address
and the applicable network mask or prefix.

The source address for IPv4 and IPv6 can be of any type and is not limited to unicast
addresses. You can use up to 100 entries for each IP type and individually enable or disable
each entry. Enabled entries apply to all PTP or NTP interfaces.

l IPv6 does not support NTP traffic.

l If you also configure the management ACL, make sure that you set
the MCI/NCI IP and subnet mask in the management ACL (see
Configuring the Management Access Control List).
l When you configure IPv4 and IPv6 traffic ACL entries, ensure that
you define subnet entries that do not partially or fully overlap with
each other.

Configuring the IPv4 Traffic ACL

1. In the selection tree pane, right-click the System entity, and then select Edit IPv4
Traffic ACL. The Edit IPv4 Traffic Access Control List window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 109

Oscilloquartz: An ADVA Company Provisioning Operations

2. The IPv4 Traffic Access Control List table contains 100 entries. Columns for each entry
consists of these configurable options:

Column Setting
IP Address Enter the IPv4 address that contains the PTP/NTP traffic that you want
the device to filter.
Network Mask Enter the network mask for the IPv4 address that contains the PTP/NTP
traffic that you want the device to filter.
Control Defines whether this IP address definition in the system is Enabled or
Disabled. The default is Disabled.

3. After you finish defining the IP addresses in the IPv4 Traffic ACL, click OK. The Traffic
ACL tab opens.
4. To verify the changes, open the IPv4 Traffic Access Control List tab, and verify that the
IPv4 addresses are listed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 110

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring the IPv6 Traffic ACL

1. In the selection tree pane, right-click System, and then select Edit IPv6 Traffic ACL. The
Edit IPv6 Traffic Access Control List window opens.

2. The IPv6 Traffic Access Control List table contains 100 entries. Each entry consists of
columns with these configurable options, where the system supports only PTP traffic:

Column Setting
Address Enter the IPv6 address that contains the PTP traffic you want the device
to filter.
Prefix Enter the prefix for the IPv4 address that contains the PTP you want the
device to filter.
Control Defines whether this IP address definition in the system is Enabled or
Disabled. The default is Disabled.

3. After you finish defining the IP addresses in the IPv6 Traffic ACL, click OK. The Traffic
ACL tab opens.
4. To verify the changes, open the IPv6 Traffic Access Control List tab, and verify that the
IPv6 addresses are listed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 111

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring the ICMPv4 and ICMPv6 Filters

ICMP filters for either IPv4 or IPv6 traffic search for ICMP packets that are unnecessary or
unrelated to the device and filters them out. Depending on the IP type, you can configure
different ICMPv4 or ICMPv6 filters.

To configure the ICMPv4 filter:

1. In the selection tree pane, right-click the System entity, and then select Edit ICMPv4
Filter. The Edit ICMPv4 Filter window opens.

2. Set these ICMPv4 filter options:

o ICMPv4 Filter: Defines whether you can edit the ICMPv4 filter options. If you

enabled these filters, you can set other filters. If disabled, you are unable to change
the filters. The default is Disabled.
o Drop Echo Requests: Defines whether to accept or block echo requests for ICMPv4
packets. The default is configured to accept these packets because this filter is set to
Disabled. To block echo requests, set this filter to Enabled.
3. After you complete the ICMPv4 filter option settings, click OK. The ICMP Filter tab
opens and displays the ICMPv4 Filter section changes.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 112

Oscilloquartz: An ADVA Company Provisioning Operations

To configure the ICMPv6 filter:

1. In the selection tree pane, right-click System, and then select Edit ICMPv6 Filter. The
Edit ICMPv6 Filter window opens.

2. Set these ICMPv6 filter options:

Field Setting
ICMPv6 Filter Defines whether you can edit the ICMPv6 filter options. If enabled, you
can set the other filters. If disabled, you cannot change the filters. The
default is Disabled.
Drop Echo Defines whether to accept or block echo requests for ICMPv6 packets.
Requests The default is to accept these packets because this filter is set to
Disabled. To block echo requests, select Enabled.
Drop Router Defines whether to accept or block router solicitation requests for
solicitation ICMPv6 packets. The default is to accept these packets because this filter
is set to Disabled. To block router solicitation requests, select Enabled.
Drop Router Defines whether to accept or block router advertisement requests for
Advertisement ICMPv6 packets. The default is configured to accept these packets
because this filter is set to Disabled. To block router advertisement
requests, select Enabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 113

Oscilloquartz: An ADVA Company Provisioning Operations

Field Setting
Drop Neighbor Defines whether to accept or block neighbor solicitation requests for
Solicitation ICMPv6 packets. The default is configured to accept these packets
because this filter is set to Disabled. To block neighbor solicitation
requests, select Enabled.
Drop Neighbor Defines whether to accept or block neighbor advertisement requests for
Advertisement ICMPv6 packets. The default is configured to accept these packets
because this filter is set to Disabled. To block neighbor advertisement
requests, select Enabled.

Redirect packets are blocked by default. You cannot configure this setting.

3. Afte you complete the ICMPv6 filter settings, click OK. The ICMP Filter tab opens and
displays the ICMPv6 Filter changes.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 114

Oscilloquartz: An ADVA Company Provisioning Operations

Activating Software Licenses

These software-licensing options are available.

License Option Description

PTP-MC-BC-IP-UNICAST- Use to enable or disable the Master Clock/Boundary Clock
Profile-<number of remote license for a G8265.1 profile or a Grandmaster Clock license
slaves>-Remote-Slaves for a G8275.2 profile. This license supports one Clock Probe,
one PTP Clock Probe, one PTP Network Probe, and up to the
<number of remote slaves> listed in the license. The number
of remote slaves available in a license are: 64, 128, 256, 512,
and 1024, which depends on your network system
configuration.
SyncJack-Extended-Scaled This license is required for full scale Syncjack probing. You
can enable this license when the PTP-MC/BC feature is
enabled. This license extends the maximum number of
Syncjack probes that you can create. When enabled, you can
create up to two clock probes, four PTP clock probes, and
one PTP network probe.
PTP-Clock-G-8275-1-and- This license is required for Layer 2 Ethernet multicast
IEEE-1588-2008-Annex-F- [G.8275.1] and enables use of the Phase and Time Telecom
Profiles profile G.8275.1. Use this key for support of G.8275.1 in PTP
Sync Delivery and Sync assurance features.
PTP-Enterprise-and-IEEE- Use to enable or disable the PTP Enterprise profile and Layer
1588-2008-L3-Multicast- 3 PTP multicast profile.
Profiles
NTP Server Use to enable Network Time Protocol provisioning.
e-PRTC Use to enable or disable the time clock to combine the
stable frequency input, such as a Cesium Clock. The purpose
is to extend the holdover capability to meet the e-PRTC
performance standards.
PTP-Clock-Power-and- Use to enable or disable the PTP time clock for power system
Utility-Profiles applications (IEEE C37.238 2011 and 2017) and power utility
automation (IEC PAS 61850-9-3).
Advanced-Interference-
Detection

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 115

Oscilloquartz: An ADVA Company Provisioning Operations

License Option Description

PTP-Broadcast-Profiles Use to enable IEEE 1588-2008 Precision Time Protocol for
media applications (AES67) and media synchronization
(SMPTE 2059-2).
HIGH-ACCURACY-BC Use to enable boundary clock high-accuracy license.

Enabling a Software License

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the tree pane, expand System > Administration > Software Licensing.
3. Right-click Feature Management, and then select Edit Feature. The Edit Feature
Management window opens.

4. Select the software license that you want to enable and in the Status column for that
license, select Enabled. If you enable a license, a License Warning message displays.
5. Click OK. The Edit Feature Management window displays the software license as
Enabled.
6. Click OK. The Edit Feature Management window closes. You can no longer edit the
software licenses in the Feature Management window.
7. Repeat Step #3 to 6 for each additional license.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 116

Oscilloquartz: An ADVA Company Provisioning Operations

Provisioning Common Units

This section explains how to provision these common units:

Configuring NE-1 117

Configuring NTEOSA 5422 119
Configuring PSUs 120
Provisioning the Display Card 121
Provisioning Line Cards 122

Configuring NE-1
Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure the NE-1:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System entity, click +.
3. Right-click the NE-1 entity, and then select Edit Configuration. The Edit Configuration

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 117

Oscilloquartz: An ADVA Company Provisioning Operations

window opens.

4. In the Network Element Settings and Shelf State areas, complete these settings:

Area Name Field Name Setting

Network Name Enter the name of the NE-1. The default is OSA 5422.
Element Location Enter the NE-1 location.
Information
Contact Enter the NE-1 contact person.
CLI Prefix Enter the CLI prefix for the network element. The
default is NE-1.
Shelf State Administrative Select the applicable administrative state either IS or
Management. The default is IS .For more information,
see Entity State Descriptions.

5. Click OK. The window updates to show the edited information.

Except for the CLI Prefix, the NE-1 identity information that is available for
editing in the window is the same identity information that the System
view displays.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 118

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring NTEOSA 5422

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure the NTEOSA 5422:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>NE-1 entities, click +.
3. Right-click NETOSA 5422, and then select Edit Configuration. The Edit Configuration
window opens.

4. Complete these settings:

Area Field Setting

Identification Alias Enter the applicable alias to help identify this
particular NETOSA 5422.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 119

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

State Administrative Select the applicable administrative state:

l IS
– or –
l Management

The default is IS. For more information, see

Entity State Descriptions.
Settings SNMP Dying Gasp Select Enabled or Disabled. The default is
Disabled.

5. Click OK. The window updates to show the edited information.

Configuring PSUs
You can configure both PSU-1 and PSU-2, or only PSU-1. For example, if you install only the
first PSU and prefer that the second PSU reports no alarms, set the Administrative state to
Management.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure a PSU:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>NE-1 entities, click +.
3. Right-click the PSU entity that you want to configure and select Edit Configuration. The
Edit Configuration window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 120

Oscilloquartz: An ADVA Company Provisioning Operations

4. In the Identification area, Alias field, enter the applicable alias to make it easy to
identify the PSU. The default is undefined.
5. In the State area, Administrative field, select IS (in service) or Management.
The default is IS. If you want to implement only PSU1 and do not want PSU2 to report
alarms, set the Administrative state to Management. For more information, see Entity
State Descriptions.
6. In the Physical Inventory area, complete these fields.
a. PSU Part Number field, verify the correct PSU is installed for this equipment.
b. In the PSU Type field, ensure that the correct PSU is installed in the applicable unit.
The OSA 5422 requires 40W power supplies.
When you install an OSA 5422 with power redundancy, ensure that the power
capacity of both PSUs is the same. The PSUs are hot swappable. You can leave the
power to the OSA 5422 on when you install a unit.

For associated part numbers, see Equipment Part Numbers in the OSA 5422
System Description.

7. After you complete these setting, click OK. The Configuration window updates with the
changes.

Provisioning the Display Card

You can view the display card inventory information and temperature. The display card
element appears below the NE-1 element.

To view display card inventory:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 121

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand the System > NE-1 elements, and then click Display Card-1.

The application raises an Equipment Fault alarm if the system detects that the card is
faulty. The system raises an Over Temperature alarm if the ambient temperature exceeds
the threshold. For related troubleshooting information, see Line Cards Alarms.

Provisioning Line Cards

This section provides instructions to provision these line cards::

Provisioning a BITS-X16 Line Card 123

Provisioning a CLK-X16 Line Card 126
Provisioning a PPS-X16 Line Card 128
Provisioning a TOD-PPS-X16 Line Card 130
Provisioning an GE-4S Line Card 132
Provisioning an IRIG-B Line Card 134
Provisioning an LPN Line Card 138

Prerquisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 122

Oscilloquartz: An ADVA Company Provisioning Operations

Provisioning a BITS-X16 Line Card

When you set the line card type to E1, you can activate or deactivate specific ports. You can
also set the output signal to E1 or 2048 kHz on the ports you activate. To set the line type to
E1, first set the BITS-OUT element to E1. This element is located below the BITS-1 element.

To provision BITS-X16 line card:

1. Click Configuration, or from the Application menu, select Configuration..

2. In the selection tree, next to the System>NE-1 entities, click +.
3. Right click LC-1 or LC-2, and then select Create Card. The Create Card (Slot-#) window
opens.

4. Set these line card options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the administrative state to either In Service
(IS) or Management. The default is Management.
For more information, see Entity State Descriptions.
Settings Card Type Select BITS-X16.

5. After you finish setting the line card options, click OK. The window updates with the
changes. The tree pane updates the line card and associated Group1 and Group2
entities.
6. In the selection tree pane, next to the new line card entity, click +. The Group1 and
Group2 entities are displayed.
7. Right-click Group1 (1-8), and then select Edit Configuration. The 8xBITS Group
Configuration window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 123

Oscilloquartz: An ADVA Company Provisioning Operations

8. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the applicable administrative state to either
In Service (IS) or Management. The default is
Management. For more information, see Entity
State Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 124

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Line Type Select the applicable line type.

l Automatically set to T1 if the BITS out setting

on the main board is T1.
l E1 or 2048 kHz if the BITS out setting on the
main board is E1.
l Automatically set to 2048 kHz if the BITS out
setting on the main board is 2048 kHz.
Line l Line type T1 – fixed at 100 Ω.
Impedance l Line type E1 – select the line impedance.
l Line type 2048 kHz – select the line impedance.
Line Code Select the line code. Available options depend on
the selected line type.
Line type 2048 kHz – None.
Frame Format Select the frame format. Available options depend
on the selected line type.
Line type 2048 kHz – None.
SA Bit Select the SA Bit. Available options depend on the
selected line type.
Line type T1 and 2048 KHz – None.
QL Mode Select the applicable QL mode. Available options
depend on the selected line type.
Disabled for line type 2048 kHz.
Squelch QL Select the applicable squelch QL. If the reference
clock drops below this setting, the system
supresses the BITS-OUT output.
Line Build Out Applies to line type T1. Select the appropriate
value.
Per Port Activation Select which ports in the group are active. Select
Configuration All to activate all ports.
Signal If you set line type to E1, you can select the output
signal for each port in the group to E1 or
2048 kHz.
Alias Type in an alias per port. Up to 256 characters.
Default is none.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 125

 Oscilloquartz: An ADVA Company Provisioning Operations

9. Click OK.
10. Repeat steps 7 to 9 to define Group2 (9 to 16) output options.
11. Repeat all the previous steps for the second line card, if applicable.

Provisioning a CLK-X16 Line Card

To provision the clock (CLK) x 16 outputs, you must first provision the main board CLK-1-1-
1-1 and CLK-1-1-1-2 signal direction to output.

Configuring the Main Board CLK-1-1-1-1 or CLK-1-1-1-2 Interface

1. Select Configuration on the toolbar, or from the Application menu, select
Configuration.
2. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click CLK-1-1-1-2/CLK-1-1-1-2, and then select Edit Configuration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 126

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line
card. The default is undefined.
State Administrative Select IS for in-service.
Configuration Signal Direction Select Output.
Squelch Control Select the applicable squelch control.
The default is Never.
Squelch QL Available only when you set Squelch
Control to Squelch quality level (QL).
Select the applicable squelch QL. The
default is QL-NONE.
Assumed QL Select the assumed QL. The default is
QL-EEC1.

5. Click OK. The window updates to reflect the changes.

Provisioning the CLX-X16 Line Card

1. In the tree pane, expand System > NE-1, right-click LC-1 or LC-2, and then select
Create Card. The Create Card (Slot-#) window opens.

2. Set these options:

Area Field Setting

Identification Alias Either type in an alias or leave blank.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 127

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

State Administrative Select the applicable administrative state
to be either In Service (IS) or Management.
The default is Management.
Settings Card Type Select CLK-X16.

3. Click OK to apply the card options. The window updates with the changes. The tree pane
updates the line card and associated Group1 entity.
4. Right-click LC-1/2 <CLKX16> and select Edit Configuration. The Edit LC window
opens. Set these options:

Area Field Setting

Identification Alias The default is undefined.
State Administrative Select the applicable administrative state, either
In Service (IS) or Management. The default is
Management.

5. Click OK.
6. Repeat all the previous steps for the second line card, if needed.

Provisioning a PPS-X16 Line Card

Complete these steps to provision a packets per second (PPS) X16 line card.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System > Synchronization > NTEOSA 5422 entities,
click +.
3. Right-click PPS-1-1-1-1 or PPS-1-1-1-2, and then select Edit Configuration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 128

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line
card. The default is undefined.
State Administrative Select IS for in-service.
Configuration Signal Direction Select Output.
Cable Delay If you set signal direction to output, this
Compensation (ns) field is irrelevant and fixed at 0. Leave
the default setting.
Source Eid From the list of provisioned Clock
Reference sources, select a source Eid
for the output signal direction.
Sequelch Control If you configure the PPS port as an
output, select the hierarchy established
for squelch control of the PPS timing
interface. The default is Lock.

To set the PPS 16-port group, you must set the PPS-1-1-1-1 or
PPS-1-1-1-2 signal direction to Output.

5. After you finish setting the options, click OK. The window updates with the changes.
6. In the selection tree pane, next to the System>NE-1 entities, click +.
7. Right click LC-1 or LC-2, and then select Create Card. The Create Card (Slot-#) window
opens.
8. Set these line card options:

Area Field Setting

Identification Alias Enter an alias to help identify the line
card. The default is undefined.
State Administrative Select the applicable administrative
state, either In Service (IS) or
Management. The default is
Management. For more information,
see Entity State Descriptions.
Settings Card Type Select PPS-X16.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 129

 Oscilloquartz: An ADVA Company Provisioning Operations

9. After you finish setting the line card options, click OK. The window updates with the
changes. The selection tree pane updates the line card and associated Group1 entity.
10. Right-click Group1 (1-16), and then select Edit Configuration. The PPS-X16 Group
Configuration window opens.

11. In the Configuration area, Cable Delay Compensation (ns) field, enter a value in
nanoseconds. The default is 0.
12. Click OK.

Provisioning a TOD-PPS-X16 Line Card

Complete these steps to provision a Time-of-Day (ToD) PPS line card.

1. Click Configuration, or from the Application menu, select Configuration..

2. In the selection tree, next to the System>NE-1 entities, click +.
3. Right-click LC-1 or LC-2, and then select Create Card. The Create Card (Slot-#)
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 130

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these line card options:

an Field Setting
Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the applicable administrative state,
either In Service (IS) or Management. The
default is Management. For more information,
see Entity State Descriptions.
Settings Card Type Select TOD-PPS-X16.

5. After you finish setting the line card options, click OK. The window updates with the
changes. The selection tree pane updates the line card and associated Group1 entity.
6. Right-click the Group1 (1-16) entity, and then select Edit Configuration. The
TodPPS16Ports Group Configuration window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 131

Oscilloquartz: An ADVA Company Provisioning Operations

7. In the Configuration area, Cable Delay Compensation (ns) field, enter a value in
nanoseconds. The default is 0.
8. Click OK.

Provisioning an GE-4S Line Card

1. Click Configuration, or from the Application menu, select Configuration.
2. In the tree pane, expand the System>NE-1 nodes.
3. Right click LC-1 or LC-2 and select Create Card. The Create Card (Slot-#) window
opens.

4. Set these line card options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card.
The default is undefined.
State Administrative Select the administrative state, either IS (In
Service) or Management. The default is
Management. For more information, see
Entity State Descriptions.
Settings Card Type Select GE-4S.

5. Click OK. The window updates with the changes. The tree pane updates the line card
and associated Ethernet port entities.
6. In the tree pane, next to the new line card entity, click +.
7. Right-click the required Ethernet port, and then select Edit Configuration. The Edit
Configuration window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 132

 Oscilloquartz: An ADVA Company Provisioning Operations

8. Set these port options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card.
The default is undefined.
State Administrative Select the required administrative state,
either In Service (IS) or Management. The
default is Management. For more
information, see Entity State Descriptions.
Port Media Type Select the media type, either Copper SFP or
Fiber.
MTU If a value other than the default is required,
enter the MTU value.
Configured Speed Select the required configured speed.
Auto Diagnostic Select Enabled or Disabled.
Note: You cannot enable this setting for an
optical port.

9. After you finish setting the port options, click OK. The window updates with the
changes.
10. In the selection tree, right-click the Ethernet port that you configured in the previous
steps, and then select Edit Sync-E. The Edit Sync-E window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 133

 Oscilloquartz: An ADVA Company Provisioning Operations

11. In the Configuration area, Sync-E Mode menu, select Enabled, and then click OK.
12. Repeat the steps for each Ethernet port, E1000-A-1 to E1000-A-4.

Provisioning an IRIG-B Line Card

Complete these steps to provision an Inter-Range Instrumentation Group (IRIG)-B line card.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the tree pane, expand the System > NE-1 nodes.
3. Right click LC-1 or LC-2 and select Create Card. The Create Card (Slot-#) window
opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 134

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these line card options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the administrative state, either IS (In
Service) or Management. The default is
Management. For more information, see Entity
State Descriptions.
Settings Card Type Select IRIG-B.

5. Click OK. The window updates with the changes, and the software creates these
interfaces below the line card node:
o IRIG RS242-1-[slot number]-[group index]-1

o IRIG OPT-1-[slot number]-[group index]-1

The software does not manage the optical port. To enable or disable the port, use
the CHO switch on the front panel of the line card.
o IRIG RELAY-1-[slot number]-[group index]-1
o IRIG GROUP-1-[slot number]-[group index]-1
o IRIG-IN-1-1-[slot number]-1
6. To provision these interfaces, right-click an interface. Select Edit Configuration, and
then set the interface properties. See Table 4 for time code formats:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 135

Oscilloquartz: An ADVA Company Provisioning Operations

Interface Property Description

IRIG RS242 Time Code Select the applicable time code. The default is
B004.
Control Field Applies only if you select time code B004. The
default is IEEE1344.
IRIG OPT Time Code Select the applicable time code: B004, B006, B007.
Control Field Applies only if you select Time Code B004. The
default is IEEE1344.
IRIG RELAY Relay Operation Select the applicable option from the list:

l 1PPH – the relay state changes every hour.

l 1PPM – the relay state changes every minute.
l Locked – the relay state is active when the time
clock is locked.
l Alarm – the relay state is inactivate when a
critical alarm is raised.
IRIG GROUP Panel Select the operation type:
Configuration
l None – line card only.
l Extension Cable – select when you connect a
fan-out cable (part number 1036005407).
l Patch Panel – select when you connect the line
card to a patch panel (part number
1047026092-01) with a high density cable (part
number 1036005406).
Note: the system does not issue a cable
missmatch warning when you connect a patch
panel to the line card port, but configure the panel
with an extension cable.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 136

Oscilloquartz: An ADVA Company Provisioning Operations

Interface Property Description

IRIG OUT (1 to Output Type Select the output type Digital or Analog. The
10) default is digital.
Time Code Select the applicable time code, which depends on
the output type. The default code for analog
output is B122. The default code for digital and
optical outputs is B004.
Control Field Applies only when you select time code B004. The
default is IEEE1344.
Digital Voltage Select the output voltage. Only outputs 9 and 10
support 10 V. The default is 5 V.
Note: If the subtended devices use 50 ohm
termination, the expected levels are 50%: 2.5V
when you configure 5V; 5V when you configure
10V.
IRIG IN Time Code Select the input time code format:

l For AM input, select B124

l For DCLS input, select B004 (default).

Control Field Select IEEE1344 IEEE or C37.118 (defualt).

Assumed Clock Select the port clock class: 6, 7, 140, 150, 160, 248.
Class The default is 6.
Leap61 Indicates a pending leap61 second event.
Leap59 Indicates a pending leap59 second event.
Leap Second Date Shows the date for the next leap second in the
format: ddmmyy.
UTC to TAI Offset Shows UTC to TAI offset in seconds. Configure UTC
offset to TAI in Editing the Time Zone.
Current Time of Specifies the last received Time of Day value.
Day
Cable Delay Enter the delay caused by the cable in
Compensation nanoseconds. Valid values: -5000000 to 5000000.
The default is 0.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 137

Oscilloquartz: An ADVA Company Provisioning Operations

Table 4: IRIG-B Time Code Format

B 0 0 6
Code A 1000 pps 0 DC level shift (DCLS) (pulse width 0 No carrier (DCLS) 0 BCD, CF, SBS
Code B 100 pps coded without carrier) 1 100 Hz 1 BCD, CF
Code D 1 ppm 1 Sine wave carrier, amplitude (10 ms resolution) 2 BCD
Code E 10 pps modulated (AM) 2 1 kHz 3 BCD, SBS
Code G 10,000 pps 2 Manchester modulated (1 ms resolution) 4 BCD, BCD_Year,
Code H 1 pps 3 10 kHz CF, SBS
(100 μs resolution) 5 BCD, BCD_Year,
4 100 kHz CF
(10 μs resolution) 6 BCD, BCD_Year
5 1 MHz 7 BCD, BCD_Year,
(1 μs resolution) SBS

7. Click OK to save the configuration.

Provisioning an LPN Line Card

Complete these steps to provision a Low Phase Noise (LPN) line card.

After the first sync component lock or after an holdover lock, an LPN card
can take up to 11,000 seconds to stabilize the outputs. During this time,
LPN outputs may be outside the range of the outputs performance
specifications.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the tree pane, expand the System>NE-1 nodes.
3. Right click LC-1 or LC-2 and select Create Card. The Create Card (Slot-#) window
opens.

4. Set these options:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 138

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the administrative state, either IS (In
Service) or Management. The default is
Management. For more information, see Entity
State Descriptions.
Settings Card Type Select CLK-X4-LPN.

5. Click OK. The window updates with the changes. The tree pane updates the line card
and associated group ports.
6. In the tree pane, next to the new line card entity, click +.
7. Right-click Group (1-4), and then select Edit Configuration.

8. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the administrative state, either IS (In
Service) or Management. The default is
Management. For more information, see Entity
State Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 139

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Group Squelch Control Select the squelch condition for the ports. The
Configuration default is Never.
Squelch QL Select the squelch quality level when you select
Squelch Control, Squelch QL. The default is QL-
None.
Per Port Activation Select which of the 1 to 4 ports you want to
Configuration enable.

9. Click OK to update the changes.

Provisioning Secure Access

You can ensure that access to the OSA 5422 management system is secure. Table 5 lists the
tasks required to provision secure access.

Table 5: Tasks to Provision Secure Access

Task Reference
You have a number of ways to access the OSA 5422. You Provisioning System Options.
can view and edit these options in the System and Edit
System views respectively.

l Serial port
l Telnet
l SSH
l HTTP
l HTTPS
l FTP
l SFTP
l SCP
Access through SSH- and SSL-based protocols, which use Configuring Security Keys.
certificates and keys that you can configure.
Configure the local-user access-security policy for low, Configuring the Security
medium, or high security levels. Policy.
Restrict access by using the ACL. The system then permits Configuring the Management
access only to designated IP addresses or subnetworks. Access Control List.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 140

Oscilloquartz: An ADVA Company Provisioning Operations

Table 5: Tasks to Provision Secure Access

Task Reference
Limit system access by using locally-defined users. These Configuring Local Users.
definitions can include a user ID, password, and an access
level - superuser, provisioning, maintenance, or
monitoring.
Restrict system access by using remote authentication with Configuring Remote
an externally defined and controlled user set. Authentication to the Device.
Restrict the processing and storage of personal data Configuring Data Anonymity.
through data anonymization.

Configuring the Security Policy

You can configure the strength of the security policy to be:

l High
l Medium
l Low

For more information about security policy strengths, see the Security Policy window Policy
Description area in the illustration that follows.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure the strength of the security policy:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Security Policy, and then select Edit Policy. The Security Policy window
opens, which displays the current Policy Strength setting details. This window also
includes a description of the policy rules.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 141

Oscilloquartz: An ADVA Company Provisioning Operations

4. In the Policy Strength area, Strength menu, select the applicable setting, and then click
OK.

Configuring Local Users

The system provides these privilege levels:

Table 6: User Authorization Privilege Levels

TACACS+
User Level Description
Level
Superuser 12, 13, 14, 15 Access to all commands, including administration
commands.
Provisioning 8, 9 Access to all commands except the administration options
of other users.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 142

Oscilloquartz: An ADVA Company Provisioning Operations

Table 6: User Authorization Privilege Levels

TACACS+
User Level Description
Level
Maintenance 4, 5, 6, 7 Access to a limited set of commands, which support
maintenance actions such as testing and diagnostics.
Testuser 2, 3 Has access to retrieve level privileges and single service
maintenance operations, such as VLAN loopbacks, ECPA
tests, or layer 3 ESA tests. Has access to a limited set of
commands that support maintenance actions that affect a
single service. Retrieve privilege is included.
Retrieve 0, 1 Access to commands that display configuration settings
and performance data.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

Complete these tasks to configure local users:

Adding a User 143

Editing User Data 144
Changing a User Password 145
Deleting a User 145
Unlocking Users 146

Adding a User
You need superuser privileges to add a new user to the system.

1. Click Configuration, or from the Application menu, select Configuration..

2. In the tree pane, expand System>Administration>Users.
3. Right-click Local, and then select Add User. The Add User window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 143

Oscilloquartz: An ADVA Company Provisioning Operations

4. In the Identity area, set the new user options. For details about the function and rules
for each data entry, see System Configuration Options and Rules.
5. After you define the user information, click OK.

Editing User Data

Complete these steps to edit the data of an existing user other than the user password. You
must have superuser privileges to make these edits.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration>Users>Local entities, click +.
3. Right-click the username that you want to edit, and then select Edit User. The Edit User
window opens.

4. In the Identity area, edit the user options according to your requirements. For details
about the function and rules for each data entry, see System Configuration Options and
Rules.
5. After you edit the user information, click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 144

Oscilloquartz: An ADVA Company Provisioning Operations

Changing a User Password

You can always change your own user password. To change the password of another user,
you must have superuser privileges.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration>Users>Local entities, click +.
3. Right-click the username whose password you want to change, and then select Edit
Password. The Edit Password window opens.

4. In the Edit Password area, Type New Password and Retype Password fields, enter the
new user password. Supported characters are:
0 - 9, a - z, A - Z, # * % - _ . @ !
A password cannot start with the # (number sign) character
5. Click OK.

Deleting a User
To delete a user, you must have superuser privileges.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration>Users>Local entities, click +.
3. Right-click the username that you want to delete, and then select Delete User. The
Delete User window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 145

Oscilloquartz: An ADVA Company Provisioning Operations

4. Verify that the selected user is the one you want to delete, and then click OK. The
software deletes that user from the system.

Unlocking Users
A user might get locked out of the system. To unlock a user, you must have superuser
privileges.

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration>Users>Local entities, click +.
3. Right-click the name of the locked user, and then select Remove Lock. The Remove
Lock window opens.

4. Verify that the selected user is the one that you want to unlock, and then click OK. The
software unlocks that username.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 146

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring Remote Authentication to the Device

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure remote authentication:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Remote Authentication, and then click Edit Remote Authentication. The
Edit Remote Authentication window opens.

4. In the Remote Authentication Protocol System Level Configuration area, set these
options:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 147

Oscilloquartz: An ADVA Company Provisioning Operations

Field Setting
Authentication Select the Remote Authentication Protocol type. The default is
Protocol None.

l NONE
l RADIUS
l TACACS
Authentication Type Select the remote authentication type. The default is PAP.

l Password Authentication Protocol (PAP).

– or –
l Challenge- Handshake Authentication Protocol (CHAP).
TACACS Privilege Select Enabled or Disabled. The default is Disabled.
Control
l When Enabled, the system expects the TACACS+ server to
return the User Privilege level.
l When Disabled, the TACACS+ server should not provide User
Privilege level information. Instead, the system uses the
privilege level that you specify in the TACACS Default Privilege
level attribute.
TACACS Default Select the TACACS default privilege level:
Privilege
l Retrieve
l Maintenance
l Provisioning
l Superuser
l Not Applicable

If you set TACACS Privilege Level Control to Disabled, the

TACACS+ server authenticates the user privilege and the server
uses this value as the user privilege level.

If you set the TACACS Privilege Level Control to Enabled, the

software automatically configures this value to Not Applicable.
NAS IP Address Enter the network access security server IPv4 address. This option
applies only if you set the authentication protocol to RADIUS.
NAS IP Address (v6) Enter the IPv6 address and prefix of the network access security
server. This option applies only if you set the authentication
protocol to RADIUS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 148

Oscilloquartz: An ADVA Company Provisioning Operations

Field Setting
TACACS +Accounting Select Enabled or Disabled, which refers to the use of an
accounting port. The default is Disabled.
Access Order Select the RADIUS access order as follows. The default is Local.

l Local: The software firsts authenticates the user login using the
local user database. If local authentication fails, the system uses
RADIUS, if configured, to authenticate the user login by using
the remote server.
l Remote:
o You set the Access Order to remote first. If remote

authenticatation is enabled, the software first tries to

authenticate the user login by using the remote server.
o The remote server is reachable but authentication might
fail. If so, the system does not use the local database to
authenticate the user login and declares authentication
failure.
o The remote authentication succeeds, and the system
declares the authentication successful.
o The remote authentication is disabled, or the remote server
is unreachable. If either of these occur, the system uses the
local database to authenticate the user login.

5. In the Remote Authentication Server (1, 2, and 3) areas, set these options:

Field Setting
Server Status Select Enabled or Disabled to specify whether the server is operational.
The default is Disabled.
Priority Select the priority of the server in servicing requests:

l First
l Second
l Third

Multiple servers can have the same priority value. The software uses
random ordering for those servers with equal priority values. The Server 1
default is First, the Server 2 default is Second, and the Server 3 default is
Third.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 149

Oscilloquartz: An ADVA Company Provisioning Operations

Field Setting
IP Address 1. Select the IP type as either IPv4 or IPv6.
2. In the field below IP Address, enter the IP address of the specified
remote server.
Server Secret Select this field to edit the Server Secret. The default is not allowed, or not
selected.
Port Enter the UDP port to use when the system communicates with the
remote authentication server.

l If you set the Authentication Protocol to RADIUS or None, the default

is 1812.
l If you set the authentication protocol is set to TACACS, the default is
49.
Accounting Enter the UDP port to use for accounting when the system communicates
Port with the remote authentication server.

l If the authentication protocol is set to RADIUS, the default is 1813.

l If the Authentication Protocol is set to TACACS, the default is 49.

You can edit the accounting port only if the TACACS + Accounting is
Enabled.
Timeout Enter the timeout to be 2 to 10 seconds, after which communication with
this server fails. This option applies only if the Authentication Protocol is
set to RADIUS. The default is 3 seconds.
Retries The maximum number of tries that the software will attempt for
authentication using this server. You can select 0 to 5. The default is 5.

For more information about the function and rules of each entry, see
System Configuration Options and Rules.

If you activate remote authentication, you can restrict or disable local

access.

6. Verify that all data is entered correctly, and click OK.

If you implement remote authentication through RADIUS using a two-

factor mode authentication, such as RSA, be aware of the first-time log in
steps. For more information, see Logging In.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 150

Oscilloquartz: An ADVA Company Provisioning Operations

Configuring Data Anonymity

To restrict the processing and volume of personal data that the OSA 5422 stores, you can
configure data anonymity. Data anonymity ensures that the software deletes user names in
each log entry only for a certain time interval. The software then replaces these entries with
the string XXXXXXXX. This time interval is called a logging anonymity interval.

By default, the system logs each action that a user performs with their user name and never
deletes the logs. Only a user with superuser privileges can configure data anonymity and
change this time interval from 1 to 1,096 days (3 years).

If you do not want to configure data anonymity for all user names and
instead leave the default configuration, a system administrator can create
an anonymous user as XXXXXXXX.

Guidelines
The system follows these guidelines to implement data anonymity:

l If the logging anonymity interval is set to NEVER, the user names are never
anonymous, which is the default setting.
l For all other values of 1 to 1,096 days, after the configured number of days pass,
the system anonymizes the user names. At midnight of that day, the system
anonymizes all the log entries that precede the configured value.

l Because the minimum value is 1 day, user data is visible for at least 24
hours.
l When you restore the factory defaults, the logging anonymity interval
changes to NEVER.

l When the system time changes, the system reviews the log files. The system then
anonymizes existing log entries depending on when the logs were created and the
logging anonymization interval.
l If you configure data anonymization, the system anonymizes any user names in the
log entries that exceed the logging anonymization interval.
l You cannot retroactively make anonymous any log information that already
transmitted, such as through the Syslog, or that the OSA 5422 transmits.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 151

Oscilloquartz: An ADVA Company Provisioning Operations

the Serial Port).

3. Log in to EMS.

To configure data anonymity:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click User Data Policy, and then click Edit Data Policy. The User Data Policy
window opens.

4. In the Logging anonymization interval area, Interval in days field, select 1 to 1096
days (3 years) to specify when the software will anonymize user names in the logs after
this time interval expires.
5. Click OK.
The window updates with the changes.

For more information, see System Configuration Options and Rules.

Managing Certificates
This section includes SSL certificates operations. The operations you perform under
managing SSL certificates are:

Configuring Security Keys 153

Copying an SSL Certificate from a Remote Source 155
Copying a Private Key from a Remote Source 156
Copying an Encrypted Private Key from a Remote Source 156

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 152

Oscilloquartz: An ADVA Company Provisioning Operations

Copying an SSL Certificate and Private Key from a Remote Source 157
Setting the SSL Certificate Key Pair 158
Trusting Root CA Certificates 158
Editing an HTTPS SSL Certificate Expiry Notification Period 159
Manually Enrolling a Certificate 159
Generating and Deleting RSA Key Pairs 159
Generating Certificate Signing Requests 160
Copying Certificate Signing Requests to a Remote Computer 160
Deleting Certificate Signing Requests 160
Automatic Certificate Enrollment 161
Creating Cetificate Authority Profiles 161
Editing and Deleting CA Profiles 162
Creating a Certification Authority 163
Starting Automatic Enrollment 163
Getting Certificate Authority Certificates 164
Deleting a Certification Authority 164

Configuring Security Keys

If you change the security keys, that process can interrupt any current secure sessions that
used the existing keys for authentication.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

To configure security keys:

1. Click Configuration, or from the Application menu, select Configuration..

2. Expand System > Administration and click Key Generation. The Key Generation
window opens with the current SSL certificate and SSH key information.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 153

Oscilloquartz: An ADVA Company Provisioning Operations

3. To regenerate the SSL certificate or SSH key, in the selection tree pane, right-click Key
Generation, and then select Regenerate Keys. The Regenerate Keys window opens.

4. In the Generate Certificate or Key area, select Regenerate SSL Certificate to

regenerate the SSL certificate. Click OK. This message appears:
When an SSL Certificate is generated, the HTTP server will be restarted and web access
will be unavailable during this time (approximately 15 seconds).
5. Click OK. The software regerates an SSL certificate. An Edit SSL Certificate Data area
then displays in the Regenerate Keys window.

6. In the Edit SSL Certificate Data area, edit the certificate data, and then click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 154

Oscilloquartz: An ADVA Company Provisioning Operations

7. In the Generate Certificate or Key area, select Regenerate SSH Key to regenerate the
SSH key, and then click OK. A dialog box opens and displays this text:

When an SSH Key is generated, all SSH users will be logged off.

8. Click OK. The window updates with the changes.

Copying an SSL Certificate from a Remote Source

Complete these steps to copy an SSL certificate in X509 format to the device. You must have
a file that contains the SSL certificate. The preferable filename extension is CRT.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management, and then right-click
Certificates.
3. Select Copy SSL Certificate from Remote. The Copy SSL Certificate from Remote
window opens.
4. In the SSL Certificate/Private Key Pair Name field, enter a name for the key pair.
5. In the Method area, File Transfer Method field, select a file-transfer method. The file
transfer window that corresponds to the selected method opens.
6. Complete these file-transfer settings.
o If you select Web, click Choose File and enter the filename. Include the server IP

address and path of the certificate file. A certificate file must have a filename
extension of CRT.
o If you select SCP, FTP, SFTP, or TFTP as the file transfer method, complete these

settings:

Field Description
Server IP Version Select the IP version.
Server IP Enter the valid IPv4 or IPv6 address of the server.
Remote File Enter the filename of the SSL certificate that is on the
server. Include the path.
User ID Enter the remote server login username. This field does
not apply to TFTP.
User Password Enter the remote server login password. This field does
not apply to TFTP.

7. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 155

Oscilloquartz: An ADVA Company Provisioning Operations

Copying a Private Key from a Remote Source

Complete these steps to copy a private key to the device. You must have a file that contains
the private key. The preferred filename extension is KEY.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management and right-click
Certificates.
3. Select Copy Private Key from Remote.
4. In the SSL Certificate/Private Key Pair Name field, enter a name for the key pair.
5. In the Password (Private Key decryption) field, enter the password.
6. In the Method area, File Transfer Method field, select a file-transfer method. The file
transfer window that corresponds to the selected method opens.
7. Complete these file-transfer settings.
o If you select Web, click Choose File and enter the filename. Include the server IP

address and path of the certificate file. A key file must have a filename extension of
KEY.
o If you select SCP, FTP, SFTP, or TFTP as the file transfer method, complete these

settings:

Field Description
Server IP Version Select the IP version.
Server IP Enter the valid IPv4 or IPv6 address of the server.
Remote File Enter the filename of the SSL certificate that is on the
server. Include the path.
User ID Enter the remote server login username. This field does
not apply to TFTP.
User Password Enter the remote server login password. This field does
not apply to TFTP.

8. Click OK.

Copying an Encrypted Private Key from a Remote

Source
Complete these steps to copy an encrypted private key in PKCS#8 format to the device. You
must have a file that contains the private key and the password. The preferred filename
extension is KEY.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 156

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management and right-click
Certificates.
3. Select Copy Encrypted Private Key from Remote.
4. In the SSL Certificate/Private Key Pair Name field, enter a name for the key pair.
5. In the Password (Private Key decryption) field, enter the password.
6. In the Method area, File Transfer Method field, select a file-transfer method. The file
transfer window that corresponds to the selected method opens.
7. Complete these file-transfer settings.
o If you select Web, click Choose File and enter the filename. Include the server IP

address and path of the certificate file. A key file must have a filename extension of
KEY.
o If you select SCP, FTP, SFTP, or TFTP as the file transfer method, complete these

settings:

Field Description
Server IP Version Select the IP version.
Server IP Enter the valid IPv4 or IPv6 address of the server.
Remote File Enter the filename of the SSL certificate that is on the
server. Include the path.
User ID Enter the remote server login username. This field does
not apply to TFTP.
User Password Enter the remote server login password. This field does
not apply to TFTP.

8. Click OK.

Copying an SSL Certificate and Private Key from a

Remote Source
Complete these steps to copy an SSL certificate and private key pair in PKCS#12 format to
the device. Ensure that you have a file that contains an SSL certificate and private key. The
preferable filename extension is PK12.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management, and then right-click
Certificates.
3. Select Copy SSL Certificate/Private Key from Remote.
4. In the SSL Certificate/Private Key Pair Name field, enter a name for the key pair.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 157

Oscilloquartz: An ADVA Company Provisioning Operations

5. In the Password (Private Key decryption) field, enter the password.

6. In the Method area, File Transfer Method field, select a file-transfer method. The file
transfer window that corresponds to the selected method opens.
7. Complete these file-transfer settings.
o If you select Web, click Choose File and enter the filename. Include the server IP

address and path of the certificate file. A key file must have a filename extension of
KEY.
o If you select SCP, FTP, SFTP, or TFTP as the file transfer method, complete these

settings:

Field Description
Server IP Version Select the IP version.
Server IP Enter the valid IPv4 or IPv6 address of the server.
Remote File Enter the filename of the SSL certificate that is on the
server. Include the path.
User ID Enter the remote server login username. This field does
not apply to TFTP.
User Password Enter the remote server login password. This field does
not apply to TFTP.

8. Click OK.

Setting the SSL Certificate Key Pair

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management, and then right-click
Certificates.
3. Select Set HTTPS SSL Certificate/Key Pair. The Set HTTPS SSL Certificate Key Pair
window opens.
4. In the HTPPS SSL Certificate/Key Pair Name field, select a certificate / key pair name
you have imported or the default, locally-generated Self-Signed certificate and
corresponding key.

Trusting Root CA Certificates

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management.
3. Click Certificates and select the SSL Certificate / Private Key Pairs tab.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 158

Oscilloquartz: An ADVA Company Provisioning Operations

4. Right-click an existing SSL certificate and select Trust Root CA Certificate. The Trust
Root CA Certificate window opens.
5. Click OK.

Editing an HTTPS SSL Certificate Expiry

Notification Period
Specify the number of days before a certificate expires, which results in an expiry pending
notification.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management, and then right-click
Certificates.
3. Select Edit HTTPS SSL Certificate Expiry Notification Period. The configuration
window opens.
4. In the HTTPS SSL Certificate Expiry Notification Period field, enter a notification
period of 1 to 180 days. The default is 90 days.

Manually Enrolling a Certificate

To manually enroll a certificate for the certificate authority (CA), you must first create a
certificate signing request (CSR) . You can configure up to four CSRs, which you can then
copy to remote locations by using standard protocols.

A typical flow consists of these tasks:

1. Generate an RSA key pair with a specified key name and key length. See Generating and
Deleting RSA Key Pairs.
2. Generate a CSR for the generated key pair name. See Generating Certificate Signing
Requests.
3. Retrieve the CSR and provide this request to the certificate authority.
4. The certificate authority issues and provides you with an SSL certificate.
5. Copy the SSL certificate to the system. Identify the certificate according to the key pair
name that you assigned to the CSR. See Copying Certificate Signing Requests to a
Remote Computer.
6. Configure the certificate to work with HTTPS. You can also edit the certificate expiry
notification period. See Editing an HTTPS SSL Certificate Expiry Notification Period.

Generating and Deleting RSA Key Pairs

You can generate up to four RSA key pairs.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 159

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management.
3. To generate a key pair, right-click RSA Key Pairs and select Generate new RSA Key
Pair. The Generate RSA Key Pair window.
a. In the RSA Key Name field, enter a name for the key, with a maximum 64 characters.
b. In the RSA Key Length field, select the key length and click OK. The system requires
up to 1 minute to generate an RSA key pair. The key is available after the key
generation process completes.
4. To delete an RSA key pair, expand System > Administration > Certificate
Management, and then click RSA Key Pairs. The RSA Key Pairs window opens.
5. Right-click the RSA key pair you want to delete and select Delete RSA Key Pair.
6. Click OK.

Generating Certificate Signing Requests

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management.
3. Right-click Certificate Signing Requests and select Generate new certificate signing
request.
4. In the Name field, enter a name for this request.
5. In the RSA Key Pair Name field, select a previously generated RSA key-pair name. See
Generating and Deleting RSA Key Pairs.
6. Complete any remaining fields on the form.
7. Click OK.

Copying Certificate Signing Requests to a Remote

Computer
1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management.
3. Click Certificate Signing Requests. The Certificate Signing Requests window opens.
4. Right-click an existing CSR and select Copy to Remote.
5. Select the applicable transmission method.
6. Complete any related data for FTP, SCP, SFTP, or TFTP, as required.
7. Click OK.

Deleting Certificate Signing Requests

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 160

Oscilloquartz: An ADVA Company Provisioning Operations

3. Click Certificate Signing Requests. The Certificate Signing Requests window opens.
4. Right-click an existing CSR and select Delete.
5. Click OK.

Automatic Certificate Enrollment

The system supports automatic certificate enrollment when you use the Secure Certificate
Enrollment Protocol (SCEP).

A typical flow includes these tasks:

1. Configure a certification authority (CA) profile that specifies the auto-enrollment

protocol and its corresponding parameters. See Creating Cetificate Authority Profiles.
2. Create a certificate authority that uses the configured certificate authority profile. See
Creating a Certification Authority.
3. When you retrieve an SSL certificate for the first time, specify that you trust the
certificate authority certificate. See Trusting Root CA Certificates.
4. Include a PKCSReq message when you enroll the device certificate for the first time. See
Starting Automatic Enrollment. The response can be one of these:
o Success

o Failure
o Pending

After successful enrollment, the certificate authority process verifies the device
certificate using the chain of trust for the applicable certificates.

If you configure the certificate authority profile to automatically renew, the certificate
automatically does so after the certificate lifetime reaches the specified percentage. See
Creating Cetificate Authority Profiles.

Creating Cetificate Authority Profiles

A certificate authority (CA) configuration requires a certificate authority profile. You can
configure up to four profiles.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. Right-click CA Profile and select Create CA Profile. The CA Profile window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 161

Oscilloquartz: An ADVA Company Provisioning Operations

4. Complete these settings.

Area Field Description

Identification CA Profile Entity identifier for the certificate authorityprofile.
ID
Configuration Name (Optional) Enter a name for the certificate authority
profile. The name can have 0 to 64 characters including [a
to z], [A to Z], [0 to 9], _ and -.
Enrollment Select the enrollment protocol. The available protocol is
Protocol CSEP.
HTTP Port Enter the HTTP port number. SCEP uses HTTP, and this
setting specifies the TCP port that HTTP uses. Do not use
ports designated for other standard protocols. The default
is 80.
Auto Select Enabled to automatically renew or re-enroll the
Renewal certificate.
Renewal Enter the percentage of the certificate lifetime at which
Percent point the automatic certificate renewal process begins.
Lifetime This field is available only if Auto Renewal is enabled. The
default is 75.
Renewal To have the process regenerate an RSA key pair before
New Key each certificate renewal, select Enabled.
Pair This field is available only if Auto Renewal is enabled. The
Generation default is disabled.

5. Click OK. The CA Profile window displays the new certificate authority profile.

Editing and Deleting CA Profiles

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. To edit a certificate authority profile, right-click an existing certificate authority profile
and select Edit CA Profile.
4. In the CA Profile configuration window, edit the profile .
5. To delete a certificate authority profile, right-click the profile you want to delete and
select Delete CA Profile.
6. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 162

Oscilloquartz: An ADVA Company Provisioning Operations

Creating a Certification Authority

A certification authority (CA) is required for automatic certification enrollment.

1. Click Configuration, or from the Application menu, select Configuration.

2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. Right-click Certification Authority and select Create Certification Authority.
4. Complete these settings:

Field Description
Name Enter a unique name for the certificate authority . The name can have 0 to
64 characters and include [a to z], [A to Z], [0 to 9], _ and -.
CA Profile Select a certificate authority profile. One or more certificate authority
profiles must already exist.
CA URL Enter the certificate enrollment URL that has a certificate authority .
CA SCEP If the server is a PKI server that uses the SCEP protocol, enter a query
Query message for a successful communication with the server. Otherwise, select
Message None. The default is None.

5. Click OK. The Certification Authority window displays the new certificate authority.

Starting Automatic Enrollment

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. Click Certification Authority, right-click an existing certificate authority, and then select
Start Auto Enrollment.
4. Complete these settings.

Area Field Description

Certificate Signing CSR Name Select a CSR.
Request Challenge Enter the password for the certificate authority
Password challenge.

5. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 163

Oscilloquartz: An ADVA Company Provisioning Operations

Getting Certificate Authority Certificates

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. Click Certification Authority, right-click an existing certificate authority, and then select
Get CA Certificates.
4. Click OK.

Deleting a Certification Authority

1. Click Configuration, or from the Application menu, select Configuration.
2. Expand System > Administration > Certificate Management > Automatic
Certificate Enrollment.
3. Click Certification Authority, right-click the certificate authority you want to
delete, and then select Delete Certification Authority.
4. Click OK.

Provisioning SNMP Access

To provision SNMP access, you must have superuser privileges. For more information about
SNMP settings, see System Configuration Options and Rules.

Provisioning Access Ports

The OSA 5422 provides two 100/1G copper ports and an additional eight 1G/10G fiber
ports. ADVA includes four ports with the basic license and additional four ports with
software licenses. The 10G option requires a dedicated software license. To view your
specific current allocated and available traffic resources, expand System > NE-1, select
NTEOSA 5422, and then select the Resources tab.

l Access ports 1 (E1000-A-1) and 2 (E1000-A-2) media type is fixed to copper.

l You can provision access ports 3 (E1000-A-3) to 10 (E1000-A-10) media type to
either fiber or copper SFP.

To configure PTP, see Provisioning the Precision Time Protocol.

To configure Sync-E, see Provisioning Synchronization.

To provision an access port:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 164

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. In the tree pane, expand System >NE-1 > NTEOSA 5422.
3. Right -click the access port you want to configure, and then select Edit Configuration.
The Edit Configuration window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 165

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set the access port options. For detailed field descriptions, see Detailed Access Port
Configuration Options and Rules

Area Field Setting

Identification Alias Enter an alias to help identify the access port,
which can have up to 64 ASCII characters. The
default is undefined.
State Administrative Select the administrative state. The default is IS.
l IS (In Service)
l Management
l Unassigned
Port Media Type Select the media type:

l Ports E1000-A-1 and E1000-A-2 are fixed to

copper.
l For all other ports, select Fiber or Copper SFP.
MTU Enter the applicable MTU size in bytes. The
default is 9600 bytes.
Configured Select the speed:
Speed l The Fiber default is Auto 1000 Full.
l The Copper SFP default is Auto 1000 Full
Master.
MDIX The available MDIX media type is only for
copper. Select an option.
Auto Select Enabled or Disabled. The default is
Diagnostic Enabled.
PowerOverEthernet Powered Available only for access port E1000-A-1. Select
Device Enabled to activate PoE functionality. The default
Detection is Disabled.
Use this option to power an external OSA 5405
device. For high accuracy, set the port speed to
1Gb.

5. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 166

Oscilloquartz: An ADVA Company Provisioning Operations

Detailed Access Port Configuration Options and

Rules
The default values appear in bold typeface.

Table 7: Access Port Configuration Options and Rules

Field Description /Applicable Rules Settings / Defaults

Alias A text or number string, or a combination Up to 64 characters

of both, that you enter to uniquely identify Blank
this access port. This string can be up to 64
printable ASCII characters.

Administrative Defines the access port facility l IS

administrative state. The administrative l Management
State
state controls the generation of alarms
l Maintenance
and event reports. An entity in the In
Service state is fully operational. l Disabled
l Unassigned
l Before you initiate a loopback or an
Etherjack diagnostic, you must set the
administrative state to Maintenance.
l Before you change the service type,
you must first set the administrative
state to Unassigned.

Media Type Defines the port media type, either Fiber l Fiber
or Copper. You can provision access port 1 l Copper
(E1000-A-1 to E1000-A-4) as either media
type. access port 2 (E1000-A-2) is fixed as
Fiber.

MTU Defines the Maximum Transmission Unit 1518-9600

size. The minimum MTU is 1518, and the
maximum is 9600.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 167

Oscilloquartz: An ADVA Company Provisioning Operations

Table 7: Access Port Configuration Options and Rules

Field Description /Applicable Rules Settings / Defaults

Configured Speed Sets the configured speed for the access Auto
(Copper) interface, either auto-negotiation or Auto
manual configuration.
Auto 1000 Full
Auto 1000 Full Master
If you configure the access port as an
electrical interface, you must configure this Auto 1000 Full Slave
port as Auto 1000 Full Slave. This Auto 100 Full
restriction is necessary so that a Sync Auto 10 Full
Reference can select it. You must configure 100 Full
the access port as Auto 1000 Full Master
10 Full
for the system to be use it as a Sync-E
Master to a remote node.

Configured Speed Sets the configured speed for the access Auto 1000 Full
Access Port (Fiber) interface. You can select auto-negotiation 1000 Full
or manual configuration.
100 Full

MDIX Defines the MDIX function for copper Auto

(copper) interfaces. The copper interface uses MDIX Crossed
to change cable signal assignments in
Uncrossed
order to compensate if the interface uses
an incorrect cable type.

Auto Diagnostic Enables or disables the automatic cable Enabled

(copper) diagnostic tests if you remove the cable Disabled
from the port.

Provisioning Synchronization
The OSA 5422 provides Sync-E functionality on the access port. Complete the steps in this
section to configure Synchronous Ethernet on the OSA 5422 access port.

This table details the supported speeds for Sync-E on the main board ports:

Speed Description
1G Supported as Sync-E master and slave in 1G :Auto full 1000 full master.
1G Auto full 1000 full slave
100M Supported as Sync-E master, slave is not supported.
100M 100 full. Not supported in Auto 100 Full

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 168

Oscilloquartz: An ADVA Company Provisioning Operations

Supported Synchronization Capabilities

The OSA 5422 supports these synchronization capabilities:

l Option 1: SDH
l Option 2: SONET

The default is Option 1 SDH. For SDH, the BITS interfaces support both E1 and 2048 kHz
options. For SONET, the BITS interfaces support only T1 .

Steps for Provisioning Sync-E

You can individually configure and enable the BITS-IN and BITS-OUT interfaces, which share
basic configuration settings. If you change the line type or coding of one interface, the same
settings change on the other corresponding interface.
1. Edit the system Sync-E.
2. Provision the BITS-IN/OUT interfaces.
3. Provision the PTP time clock or Telecom slave.
4. Provision and enable Sync-E on associated Ethernet ports.
5. Provision CLK, PPS, and GNSS interfaces, if needed.
6. Provision and associate the timing domain on associated facilities.
7. Add sync reference sources to the system sync domain, SYNC-1-1-1-1. The sync
reference sources include a Sync-E enabled access port, BITS-IN, a time clock, or a
Telecom slave or both.

Ethernet services support one system sync domain with up to two reference sources. You
can associate these sources with an Ethernet access port, BITS-IN, CLK in, PPS in, PTP clock,
GNSS, time clock, or a Telecom slave.

Enable Sync-E on a per port basis. If you enable Sync-E mode on a port, you can select that
port as a reference source for the system clock. If you set Sync-E mode to disabled for that
port, the list of available System Clock references will not include that port.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN.
3. Log in to EMS as a superuser.
4. Provision these items:
o Access port (see Provisioning Access Ports)

o Telecom slave (see Creating a Telecom Slave).

o PTP time clock (Editing a Time Clock).

For Synchronization provisioning rules, see System Configuration Options and Rules.

The tasks in this section include:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 169

Oscilloquartz: An ADVA Company Provisioning Operations

Editing the System Sync 171

Editing a Time Clock 172
Editing the BITS-IN Entity 175
Editing BITS-OUT 177
Editing Clock Ports 179
Editing PPS Ports 181
Editing ToD & PPS Ports 182
Provisioning the GNSS Receiver 185
Editing the System Time of Day Using NTP or the Time Clock Configuration 198
Editing Synchronous Ethernet on Access Ports 199
Adding a Time Clock Reference 204
Operating e-PRTC Mode for a Time Clock Reference 206
Adding a Sync Reference 209
Editing a Sync Reference 211
Deleting a Sync Reference 212

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 170

Oscilloquartz: An ADVA Company Provisioning Operations

Editing the System Sync

1. Click Configuration, or from the Application menu, select Configuration.
2. In the selection tree, next to the System > Synchronization > NE-1 > NTEOSA 5422
entities, click +.
3. Right-click the SYNC-1-1-1-1 entity, and then select Edit Sync. The Edit Sync window
opens.

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The default is
undefined.
State Administrative Select IS for In Service.
Configuration Network Clock Select the applicable network clock type.
Type
l Option 1-SDH Regional Clock.

– or –
l Option 2-SONET Regional Clock.
WTR Time Enter the Wait To Restore (WTR) time in minutes. The
default is 5 minutes.
Selection Select the active reference selection mode, either QL
Mode Mode or Priotity Mode. The default is Priority Mode.

Clock PLL Select the clock PLL bandwidth as either EEC or SSU. The
Bandwidth default is EEC. When you change between the options,
verify that no references are assigned to the sync.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 171

Oscilloquartz: An ADVA Company Provisioning Operations

5. If you change the Network Clock Type, the options available for Sync-E functions on
BITS-IN, BITS-OUT interfaces and on the access port also change. If you previously
configured any of these interfaces for Sync-E functions, the Assumed QL, Expected QL
and Squelch QL settings revert to default values. You must reconfigure them.
6. Click OK.

Editing a Time Clock

The time clock selects an active time reference from two configured time references, which
can include:

l Telecom slave
l PTP clock
l SYNC
l PPS
l GNSS
l CLK

You can also use the time clock to feed the physical output interfaces, such as a TOD and
PPS Out, or the master clock and PTP clock. This section explains how to edit a time clock.

Prerequisites
Before you create a master clock or PTP clock, first provision the time clock and place it In
Service.

l To provision a Telecom slave, see Creating a Telecom Slave.

l To provision the GNSS receiver port, see Provisioning the GNSS Receiver.
l To provision synchronization, see Provisioning Synchronization.

You can provision a second-priority time-clock reference as a backup if

the process loses the first priority reference.

To edit a time clock:

1. Click Configuration, or from the Application menu, select Configuration.

2. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click the TIME CLOCK node, and then select Edit Time Clock.
The Edit Time Clock window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 172

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these time clock options:

Area Field Setting

Identification Alias Enter an alias.
State Administrative Select IS. The default is Management.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 173

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration WTR Time Enter the appropriate time. The default is 5 minutes.
Selection Mode Leave this field set to Priority Mode.
Time Holdover Select the appropriate value. The default is 5,000 ns.
Performance (ns)
Sync Reference Select Enabled or Disabled. The default is Disabled.
Candidate
Expected QL Select the appropriate choice. The default is QL-
NONE.
Time Scale Select either of these settings:

l PTP (the default): The TimeClock time origin is PTP

epoch.
l ARB: The TimeClock time origin is not traceable to
TAI, such as SYNC-1-1-1-1.
e-PRTC Mode Select Enabled or Disabled. The default is Disabled.
For more information about e-PRTC mode, see
Operating e-PRTC Mode for a Time Clock Reference.

l If you configure an ARB time scale with SYNC-1-1-1-1 as a reference to

a time clock, the master clock PTP profile is G.8265.1 or G.8275.2. The
master clock interface clock class profile is IEEE1588. The transmitted
clock class should be 13. If no reference exists, the software transmits
clock class 248.
l If you configure SYNC-1-1-1-1 as a reference, the clock is designated
as clock class 13, and the time clock enters inter-holdover mode. The
transmitted clock class should be 14. For G.8265.1 clock class profiles,
define the holdover clock class as defined in G.8265.1.
l If the clock class profile for a master clock interface is G.8265.1, define
the transmitted clock classes as G.8265.1.

5. After you set the time clock options, click OK.

6. To verify the configuration, click the time clock entity, and then select the Configuration
tab.

To add a time clock reference, see Adding a Time Clock Reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 174

Oscilloquartz: An ADVA Company Provisioning Operations

Editing the BITS-IN Entity

1. On the toolbar, click Configuration, or from the Application menu, select
Configuration.
2. Expand the System > Synchronization > NE-1 > NTEOSA 5422 > BITS-1 entities.
3. Right-click the BITS-IN entity, and then select Edit Configuration. The Edit
Configuration window opens.

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The default
is undefined.
State Administrative Select the administrative state:
l In Service (IS)
l Management
l Unassigned
The default is Unassigned. For more information, see
Entity State Descriptions.
Note: BITS does not display as a potential
synchronization reference if the administration state is
set to Unassigned.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 175

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Line Type Select the applicable line type:

l T1– verify that the Sync-1-1-1-1 Network Clock

Type is set to Option-2 SONET.
l E1 or 2048 kHz – verify that the Sync-1-1-1-1
Network Clock Type is set to Option-1 SDH.
The available options for Line Code, Frame Format, SA
Bit, and QL Mode change according to the selected
line type.
To switch between line types:

1. Set the BITS port to Unassigned.

2. Set the Sync-1-1-1-1 Network Clock Type
accordingly: Option-1 for E1/2048kHz, Option-2 for
T1.
3. Change the BITS port line type and then set the
port to Assigned.
Line Code Select the applicable line code, where the options
available are dependent on the Line Type that you
select.
Frame Format Select the applicable frame format, where the options
available are dependent on the Line Type that you
select.
SA Bit Select the applicable SA Bit, where the options
available are dependent on the Line Type that you
select.
QL Mode Select the applicable QL mode, where the options
available are dependent on the Line Type that you
select.
Note: For SDH (Option-1), if QL Mode is Disabled,
Assumed QL must be set to a value other than None.
Assumed QL Select the applicable Assumed QL.

5. Click OK to save the changes.

6. Click the BITS-IN entity to verify entries and status outputs. In the Status area, the
Received QL status indicates the correct state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 176

Oscilloquartz: An ADVA Company Provisioning Operations

Editing BITS-OUT
1. On the toolbar, click Configuration, or from the Application menu, select
Configuration.
2. Expand the System>Synchronization > NE-1 > NTEOSAOSA 5422 > BITS-1 entities.
3. Right-click the BITS-OUT entity, and then select Edit Configuration.

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The default
is undefined.
State Administrative Select the applicable administrative state:
l In Service (IS)
l Management
l Unassigned
The default is Unassigned. For more information, see
Entity State Descriptions.
Note: BITS does not display as a potential
synchronization reference if the administration state is
set to Unassigned.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 177

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Line Type Select the line type:

l T1– verify that the Sync-1-1-1-1 Network Clock

Type is set to Option-2 SONET.
l E1 or 2048 kHz – verify that the Sync-1-1-1-1

Network Clock Type is set to Option-1 SDH.

The available options for Line Code, Frame Format, SA
Bit, and QL Mode change according to the selected
line type.
To switch between line types:

1. Set the BITS port to Unassigned.

2. Set the Sync-1-1-1-1 Network Clock Type
accordingly: Option-1 for E1/2048kHz, Option-2 for
T1.
3. Change the BITS port line type and then set the
port to Assigned.
Line Code Select the line code, where the options available
depend on the Line Type that you select.
Frame Format Select the applicable frame format, where the options
available depend on the Line Type that you select.
SA Bit Select the applicable SA Bit, where the options
available depend on the Line Type that you select.
QL Mode Select the applicable QL mode, where the options
available depend on the Line Type that you select.
Note: For SDH (Option-1), if QL Mode is Disabled, you
must set the Assumed QL to a value other than None.
Squelch QL Select the applicable Squelch QL. If the reference clock
is below this setting, the software supresses the BITS-
OUT output.

The BITS-IN and BITS-OUT entites share the Line Type, Line Code, Frame
Format and SA Bit (for E1) settings. If you change one, the other also
changes.

5. Click OK to save and close the window.

6. Click the BITS-OUT entity to verify entries and status outputs. In the Status area, the
Transmit QL status indicates the correct state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 178

Oscilloquartz: An ADVA Company Provisioning Operations

Editing Clock Ports

You can provision each clock port, CLK-1-1-1-1 or CLK-1-1-1-2, as an input or output port.

To edit clock ports:

1. On the toolbar, click Configuration, or from the Application menu, select

Configuration.
2. Expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click a clock port, and then select Edit Configuration.

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the administrative state:

l IS (In Service)
l Management
l Unassigned
The default is Unassigned. For more information,
see Entity State Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 179

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Signal Direction Select the applicable Signal Direction as either Input
or Output. The default is Input.
Signal Type Select either the 10 MHz or 2048 kHz input signal.
Note: for 2048 kHz input signal, interface
impedance changes to 75 Ohm.
Squelch Control When you provision an output port, select the
applicable squelch control.
This setting is unavailable for CLK-1-1-1-1 and CLK-
1-1-1-2 if you provision them as input ports.
Squelch QL When you provision an output port, select the
applicable squelch QL.
This setting is unavailable for CLK-1-1-1-1 and CLK-
1-1-1-2 if you provision them as input ports.
Assumed QL Select the correct Assumed QL.

5. Click OK to save the changes.

6. In the tree pane, click the clock entity to verify configuration details. In the Status area,
the Current QL status indicates the correct state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 180

Oscilloquartz: An ADVA Company Provisioning Operations

Editing PPS Ports

You can provision the PPS ports, PPS-1-1-1-1 and PPS-1-1-1-2, as input or output ports.

If you set the PPS-1-1-1-1 or PPS-1-1-1-2 entity as an output, the squelch

control setting will be the same for the ToD-1-1-1-1 & PPS port.

Prerequisites
First provision the related source EID, and then provision a PPS-1-1-1-1/2 with an output
signal direction.

To edit PPS ports:

1. On the toolbar, click Configuration, or from the Application menu, select

Configuration.
2. Expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click the entity, and then select Edit Configuration.

4. Set these PPS options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 181

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

State Administrative Select the applicable administrative state:
l IS (In Service)
l Management
l Unassigned
The default is Unassigned. For more information, see
Entity State Descriptions.
Configuration Signal For PPS-1-1-1-1/2, select the applicable Signal
Direction Direction as either Input or Output. The default is
Input.
Input Rate For an input PPS, select the applicable input rate:

l Pulse Per Second (default)

l Pulse Per 2 Seconds
Assumed Clock For PPS Input, select the clock class:, 6, 7, 140, 150,
Class 160, or 248. The default is 6.
This setting is unavailable if you configure the port as
an output port.
Cable Delay Enter the applicable Cable Delay Compensation in
Compensation nanoseconds. Valid values: -5000000 – 5000000. The
(ns) default is 0.

Source Eid Select an EID to provision PPS-1-1-1-1 or PPS-1-1-1-

2 as an output port.
Squelch Select a squelch control to provision PPS-1-1-1-1 or
Control PPS-1-1-1-2 as an output port.

PPS Width Set the PPS output width in microseconds:

1 to 500,000µs. The default is 134,200µs.

5. Click OK to save the changes.

6. In the tree pane, click the PPS-1-1-1-1 or PPS-1-1-1-2 entity to verify the configuration
details.

Editing ToD & PPS Ports

The OSA 5422 can synchronize to one PPS input. An external source, such as an accurate
Layer 1 or Layer 2 GNSS receiver, must provide the phase through a PPS input. In this mode,
the GNSS receiver provides the time of day (ToD). You can set a ToD & PPS port as an

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 182

Oscilloquartz: An ADVA Company Provisioning Operations

output according to your network system requirements for the Telecom slave, time clock,
and PTP clock.

You can provision the ToD & PPS ports TOD-1-1-1-1 and TOD-1-1-1-2 as either input or
output ports.

Prerequisites
First provision the source EID, and then set the ToD & PPS port as an output source.

To edit the ToD & PPS port:

1. On the toolbar, click Configuration, or from the Application menu, select

Configuration.
2. Expand System>Synchronization > NE-1 > NTEOSA 5422.
3. Right-click TOD-1-1-1-1 & PPS or TOD-1-1-2-1 & PPS and select Edit Configuration.

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 183

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

State Administrative Select the administrative state:

l IS (In Service)
l Management
l Unassigned
The default is Unassigned. For more information,
see Entity State Descriptions.
Configuration Signal Direction Select the signal direction:
l Input, the default.
– or –
l Output, which is unavailable for the TOD-1-1-2-
1 & PPS port.
Input Rate For an input TOD & PPS, the input rate is fixed as
pulse per second.
Cable Delay l To provision the port as an input port, enter the
Compensation delay that the cable introduces in nanoseconds.
(ns) Valid values: –5000000 to 5000000. The default
is 0.
l As an output port, this port is automatically set
to 0.
Assumed Clock For the TOD & PPS port input, select the clock class:
Class 6, 7, 140, 150, 160, or 248. The default is 6.
If you configure the port as an output, this setting is
unavailable.
Source Eid Select the applicable source EID:

If you provision the port as output, select a

provisioned clock reference source.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 184

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration Squelch Control If you configure the ToD & PPS port as an output,
select the hierarchy that you previously established
(continued)
for squelch control of the ToD & PPS timing
interface. The default is Never. If you configure an
input ToD & PPS port, this setting is irrelevant and
unavailable.
Format Type Select the ToD & PPS port format:

l NMEA - when the signal direction is input, set

leap second, leap second date, and UTC to TAI
offset values in the system time zone
configuration, see Editing the Time Zone.
l CCSA - when the signal direction is input,

messages include only Leap61 second. If Leap59

second is expected, set the Leap59 field in
Editing the Time Zone to true.
l ITUT - when the signal direction is input, no

need for additional leap second configuration.

l N/A

The default is N/A.

PPS Width Set the PPS output width in microseconds:
1 to 500,000µs. The default is 134,200µs.

5. Click OK to save the changes.

6. In the tree pane, click TOD-1-1-1-1 & PPS or TOD-1-1-2-1 & PPS to verify the
configuration details.

Provisioning the GNSS Receiver

ADVA assembles the system with a single band or a multiband Layer 1 or Layer 2
GNSS receiver according to your order. Both types of receivers support these constellations:

l GPS
l GLONASS
l BEIDOU
l GALILEO
l SBAS
l QZSS

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 185

Oscilloquartz: An ADVA Company Provisioning Operations

To provision the GNSS-1-1-1-1 receiver, navigate to System > Synchronization > NE-1 >
NETOSAOSA 5422.

Complete these tasks to provision the GNSS receiver:

Editing a GNSS Port 186

Setting Location Control 194
Viewing Tracked GNSS Satellite Data 196
Restarting the Survey During Run-time 196
Calculating the Elevation Value 197
Resetting the GNSS Receiver 197

Editing a GNSS Port

1. Click Configuration, or from the Application menu, select Configuration.
2. In the tree pane, expand the System > Synchronization > NE-1 > NTEOSA54125422>
entities.
3. Right-click GNSS-1-1-1-1 and select Edit Configuration. The Edit Configuration
window opens.

4. Set these options:

Area Field Setting

Identification Alias Type an alias.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 186

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

State Administrative Select the state. The default is Unassigned.
To reset the GNSS receiver to the factory default,
select Unassigned if it is set to Assigned.
GNSS System l GPS Select the GNSS system type. The default is GPS.
Types The system supports these concurrent
l GLONASS
GNSS types:
l BEIDOU
l GALILEO l GPS
l SBAS l Galileo
l QZSS l GLONASS
l BeiDou
l GPS + Galileo
l GPS + Galileo + GLONASS
l GPS + Galileo + BeiDou
l GPS + GLONASS
l GPS + BeiDou
l Galileo + GLONASS
l Galileo + BeiDou
l GLONASS + BeiDou
The GNSS system types share different time
references. If you change the reference type while
the port is in service, this change can impact the
time clock.
To minimize this impact:

1. Before you change the configuration, manually

enable the Time Clock Reference Lock Out.
2. After the GNSS receiver is stable, clear the Lock
out. Typically, the receiver is stable after 1 hour
or at the end of the survey period.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 187

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Configuration PPS generation Select the number of minimum satellites that need
condition to be in a locked state before the system can
generate PPS output. The default is 1SAT.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 188

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Antenna Cable Enter the delay value and select the measurement
Delay type:

l Meters - 0 to 999,999. The default is 5.

l Nanoseconds - -100,000 to 100,000.
For the best absolute PPS accuracy, adjust the
cable delay to match the installed cable length.
Verify the delay for a specific cable type with your
cable manufacturer.
Note: We recommend not to change the delay
value, while the GNSS receiver is used as a time
clock reference. To change the delay value,
remove or lockout the GNSS from the time clock
reference, change the value, and then add the
GNSS to the time clock reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 189

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Installation Select the GNSS antenna installation type. The
Type default is Full Sky View, where the C/No Mask is
28, and the Elevation Mask is 10 degrees.
– or –
Select Limited Sky View where the C/No Mask is 0,
and the Elevation Mask is 0 degrees.
The system reports 100% survey in full sky view
when:

l Self-survey is complete
l Location reached accuracy of 1 meter
The system reports 100% survey in limited sky
view, when:

l Self-survey is complete
l Location reached accuracy of 100 meter

C/No Mask Enter the appropriate value, which is the quality of

received GNSS satellite-signals that the software
reports as a carrier-to-noise power ratio (C/No).
The receiver can use this mask to exclude satellites
with a specific C/No of 0 to 55 dB-Hz. The default
is 28 db-Hz.
Ignore Antenna Select Enabled to cause the GNSS receiver to
Condition ignore the antenna fault and to continue to lock
onto the GNSS signal.
Advance Select Enabled to activate the advanced jamming
Interference and spoofing detection. To enable this option, you
Detection must:

l Enable the Advanced-Interference-Detection

license, see Activating Software Licenses.
l Select GPS for one of the GNSS system types.
Alarms while Select Disabled to mask GNSS port alarms during
failure suspend failure suspend time.
When Enabled, the GNSS port reports alarms as
usual during failure suspend time.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 190

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Elevation Mask Enter the appropriate value in degrees, from 0 to
90 degrees. The default 10°. In general, signals
from low-elevation satellites are of lower quality
than signals from higher elevation satellites. The
receiver can use this mask to exclude satellites
with a low elevation.
Systems with a multiband GNSS receiver. If you set
the elevation mask to 5 degrees or higher, the
software counts satellites with a lower elevation in
the GNSS Satellites Data tab. This count does not
affect precision.
PDOP Mask Enter the appropriate value. Position Dilution of
Precision (PDOP) measures the prevailing satellite
geometry. Low PDOP values, in the range of 4.0 or
less, indicate good satellite geometry. A PDOP
greater than 7.0 indicates that satellite geometry
is weak.
During the location survey, this mask excludes a
position that it calculates based on lower quality
PDOP. The range is 2 to 12. The default is 6. This
field applies only while the location survey is in
progress and not after the location is determined.
Note: PDOP applies only during a self-survey or
when the receiver performs position fixes. The
PDOP Mask displays Not Available after the GNSS
receiver terminates self-survey mode.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 191

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Self Survey Specifies the number of position fixes to be
Period averaged together to form the self-surveyed
position. The range is 1 to 500,000 seconds. The
default is 86,400.
It is not possible to change the survey time after
the survey is complete (100% progress). You can
change the survey time while the survey runs or
after setting Administrative to Unassigned.
We recommend that you always use a 24 hours
survey time, which is an average of 86,400 values.
Note: While the position is calculated during the
self-survey period, the timing performance of the
device is not yet optimal. Wait until the self-survey
period is completed before starting any
measurements of the timing outputs, such as PPS
and PTP.
Alternatively, enter coordinates manually when
the coordinates are the result of a 24 hours survey
ran previously. See Setting Location Control.
Sat Min1 Enter the applicable satellite value, which sets the
Threshold number of in use satellites thresholds. The default
is 3.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 192

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Sat Min2 Enter the applicable satellite value, which sets the
Threshold number of in-use satellites thresholds. The default
is 2. This value must be less than the Sat Min1
Threshold setting, and you can only set it after you
set the Sat Min1 Threshold.

The range for the sat thresholds is 1 to 32

satellites. These numbers determine which alarm
is asserted or cleared if the number of in-use
GNSS satellites is below or above thresholds
according to these conditions:

l If the number of valid satellites that the

receiver observes is less than the Sat Min2
Threshold, the Sat Min2 Threshold alarm is
raised.
l If the Sat Min2 Threshold is less than the
number of valid satellites that the receiver
observes, and the number of satellites is less
than the Sat Min1 Threshold, the Sat Min1
Threshold alarm is raised.
l If the Sat Min1 Threshold is less than or equal
to the number of valid satellites observed by
the receiver, no alarm is raised.
Failure In GNSS failure, specifies the time in seconds the
Suspend Time GNSS receiver continues to report normal
operation to keep the TimeClock in locked state.
In the Alarms while failure suspend field you
can set how the GNSS port reports alarms during
failure suspend time.
Valid values: 3 to 86400 seconds. Default is 3 sec.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 193

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Output Squelch Jamming When enabled and the time clock uses the
Control GNSS port as reference, the GNSS port fails when a
jamming condition occurs.
Spoofing When enabled and the time clock uses the
GNSS port as reference, the GNSS port fails when a
spoofing condition occurs.
Advanced When enabled and the time clock uses the
Interference GNSS port as reference, the GNSS port fails when
an advanced jamming or advanced spoofing
conditions occur.

5. After you set the GNSS options, click OK to save the changes.
6. To view the configuration details and status, click the GNSS-1-1-1-1 entity.
In the Configuration tab, the Status area indicates tracked satellites.
In the GNSS Satellites Data tab, you can view information about the tracked GNSS
satellites and graphically view the satellites. The positioning of the satellites is based on
azimuth and elevation data that displays in the satellites table. The satellite data
refreshes every 20 seconds, but you must refresh the tab to see the new data.
7. Select the GNSS entity again and observe when Survey Progress is 100% complete.

Setting Location Control

You can manually configure the location of the device, or you can use the GNSS receiver
self-survey. The automatic location configuration is the default. In manual location, you can
configure the NE location coordinates of latitude, longitude, and altitude.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 194

Oscilloquartz: An ADVA Company Provisioning Operations

1. Right-click GNSS-1-1-1-1 and select Edit Location Control.

2. Set these options:

Field Settings
Self-survey l Select Enabled to activate the automatic location control using the
GNSS self-survey.
Once the GNSS settings are configured, five valid position fixes from
five or more satellites are needed for the GNSS receiver to start the
Self Survey Period. These measurements are considered valid only
when using qualified satellites with all mask criteria passed, and good
geometry within the PDOP Mask.
After the self-survey starts, four valid satellites are needed during the
self-survey period. If less than four valid satellites are available during
the self-survey period, the self-survey is suspended until at least four
valid satellites are available. The survey may take more than the
configured self-survey period if the number of valid satellites is less
than four throughout the self-survey period. When the survey
completes, the averaged location is stored and the receiver switches
to Over Determined mode, where at least one qualified satellite is
required.
l Select Disabled to manually enter the device coordinates.
Coordinate Type in the required coordinates.
Latitude,
Note: the GNSS receiver provides altitude reading according to the HAE
Coordinate
(Height Above Ellipsoid) model. To compare HAE value with orthometric
Longitude,
height (MSL), see Calculating the Elevation Value.
Coordinate
Altitude

3. Click OK to update your changes.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 195

Oscilloquartz: An ADVA Company Provisioning Operations

Viewing Tracked GNSS Satellite Data

Open the GNSS Satellites Data tab to view information about the tracked GNSS satellites in
the Satellite Entry Table. The Sky View area displays an image of GNSS satellites. The
positioning of the satellites is based on azimuth and elevation data that the GNSS Satellite
Entry Table reports. The internal satellite data refreshes every 20 seconds, which you can see
in the GNSS Satellites Data tab whenever the view refreshes.

During the self-survey, the Satellites table and the Sky View show all avail-
able GNSS satellites including satellites below the elevation mask. After the
survey is complete, the Satellites table and the Sky View show all available
GNSS satellites that are above the elevation mask.

This image shows location of GNSS satellites data for a GPS and GLONASS constellation.

Restarting the Survey During Run-time

Perform one of these actions:

l Restart the unit.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 196

Oscilloquartz: An ADVA Company Provisioning Operations

–or–

l Right-click GNSS-1-1-1-1 and select Edit Configuration.

Change the Administrative field from Unassigned to IS/Management and click
Apply if you are not using the source as a reference.

–or–

l After you configure the device with a fixed position, self-survey is disabled:
a. Right-click GNSS-1-1-1-1 and select Edit Location Control.
b. In the Automatic Location Control window, change the Self-survey field to
Enabled.

–or–

l If the system is unable to determine the current position, the self-survey will
automatically restart. For example, the self-survey will automatically restart if:
o You manually enter a position that is too far from the true position, and the

GNSS receiver self-survey is disabled.

o The self-survey is enabled, but the system cannot determine the position at all.

Calculating the Elevation Value

The OSA 5422 reports the altitude of the antenna as the height above ellipsoid (HAE) value,
but most maps use orthometric height or the mean sea level (MSL). Use a conversion source
to compare the HAE value of the device with the orthometric height of the map.

To convert HAE value to orthometric height:

1. Enter the device coordinates into a source that converts coordinates to Geoid height.
For example, https://geographiclib.sourceforge.io/cgi-bin/GeoidEval.
2. Enter the Geoid height in the formula H = h – N.
Where H is the orthometric height, h is HEA, and N is the Geoid height.

For example, enter altitude: 47.01275, longitude: 6.99213, and altitude (HAE): 492.5m.
The conversion returns Geoid 49.8422.

Then, substitute the values in the formula, so the orthometric height is 492.5 m - 49.8422
= 437.1578 m.

Resetting the GNSS Receiver

You can reset the GNSS receiver. After the reset, the receiver reacquires the GNSS signal.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 197

Oscilloquartz: An ADVA Company Provisioning Operations

1. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
2. Right-click GPS-1-1-1-1 (GNSS) and select Cold Reset.
3. Click OK to confirm and execute the reset.

Editing the System Time of Day Using NTP or the

Time Clock Configuration
To edit the system ToD using the local clock configuration, see Configuring the System
Identity and Configuration.
If you change the date and time to other than that of the user log in the
timeout setting, the session logs off. If this occurs, log back in to the system.

Editing the System ToD Using NTP

1. In the tree pane, right-click System and select Edit NTP. The Edit NTP window opens.

2. Set the NTP options as described in Configuring an NTP Client.

3. In the tree pane, right-click System and select Edit System. The Edit System window
opens.

4. In the Configuration area, System Time Of Day, select NTP.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 198

Oscilloquartz: An ADVA Company Provisioning Operations

5. Click OK.
6. Click the System entity, and in the Identification tab verify the system date and time.

Editing the System ToD Using the Time Clock

The source ToD clock can be set to time clock. If so, before you select the
time clock as a source, you must provision the time clock. Also, associated
references must be set to In Service. See Provisioning the Precision Time
Protocol.

1. In the tree pane, right-click System and select Edit System.

2. In the Configuration area, set these system TOD options:

Menu Setting
System Time Of Day Select Time Clock.
Source TOD Clock Select TIMECLOCK-1-1-1-1.

3. Click OK.
4. Click the System entity, and in the Identification tab verify the system date and time.

Editing Synchronous Ethernet on Access Ports

1. On the toolbar, click Configuration, or from the Application menu, select
Configuration.
2. In the tree pane, expand System > NE-1 > NTEOSA 5422.
3. Right-click the port you want to edit, and then select Edit Sync-E. The Edit Sync-E
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 199

Oscilloquartz: An ADVA Company Provisioning Operations

4. In the Configuration area, select the applicable settings for Sync-E Mode, QL Mode,
Assumed QL, and Expected QL.
For detailed Sync-E configuration options and rules, see Detailed Sync-E Configuration
Options and Rules.
o If you select SDH (Option-1), and the QL Mode is Disabled, you must select an

Assumed QL other than None.

o When the QL Mode is set to Enabled and two Sync references for SYNC-1-1-1-1

have the same QL, the software gives precedence to the reference that supports
phase.
5. Click OK.
6. In the tree pane, select the access port and then click the Sync-E tab to review the
configuration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 200

Oscilloquartz: An ADVA Company Provisioning Operations

Detailed Sync-E Configuration Options and Rules

Table 8: Sync-E Configuration Options and Rules
Field Description /Applicable Rules Settings / Defaults

Sync-E Mode Specifies whether the Ethernet Access port Disabled

is enabled or disabled for Synchronous Enabled
Ethernet Mode. Default is Disabled.

QL Mode Specifies whether the Ethernet Access port Disabled

is enabled or disabled for Quality Level
Enabled
(QL) Mode. If you set this option to
Enabled, this option applies only to
Synchronous Ethernet capable ports.

l If set to enabled on the receive side,

the port will PEER the Synchronization
Status Messages (SSMs), slow protocol
PDUs, and take appropriate action.
l If set to enabled on the transmit side,
the port will periodically transmit QL
TLV information PDUs, once a second.
l If set to disabled on the receive side,
the port will terminae and discard any
SSM slow protocol PDUs.
l If set to disabled on the transmit side,
the port will not transmit any SSM slow
protocol PDUs.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 201

Oscilloquartz: An ADVA Company Provisioning Operations

Table 8: Sync-E Configuration Options and Rules

Assumed QL Assumed QL specifies the assumed QL-NONE
Quality Level (QL) on the interface. This
QL-PRC
setting applies only to Synchronous
Ethernet capable ports with Sync-E Mode QL-SSU-A
enabled. QL-SSU-B
QL-EEC1
If the interface QL Mode is disabled, the
specified Assumed QL value is the Quality
Level of the interface, and you cannot set
the Assumed QL to QL-NONE.

If the interface QL Mode is enabled, the

specified Assumed QL value overrides the
received Quality Level of the interface
unless you set the Assumed QL to QL-
NONE.

If the Network Clock Type is SONET

(Option2) and QL Mode is disabled, the
software automatically sets the Assumed
QL to QL-STU. You cannot edit this
setting.

If you change the Network Clock Type

from SONET to SDH and QL Mode is
Disabled, the Assumed QL defaults to QL-
EEC1.

For both SDH and SONET options, if QL-

Mode is Enabled and you change the
Network Clock Type, the Assumed QL
defaults to QL-NONE.

The valid entry for SDH Network Clock is:

QL-NONE, QL-PRC, QL-SSU-A, QL-SSU-B,
QL-EEC1. The default is QL-EEC1, QL Mode
Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 202

Oscilloquartz: An ADVA Company Provisioning Operations

Table 8: Sync-E Configuration Options and Rules

The valid entry for SONET Network Clock QL-EEC2
is: QL-NONE, QL-PRS, QL-STU, QL-ST2, QL-PROV
QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, or
QL-PRS
QL-PROV. The default is QL-STU, QL Mode
QL-SMC
Disabled.
QL-STU
QL-ST2
QL-ST3E
QL-TNC

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 203

Oscilloquartz: An ADVA Company Provisioning Operations

Table 8: Sync-E Configuration Options and Rules

Expected QL Specifies the expected Quality Level (QL) If QL-NONE
you enabled the Ethernet port for QL QL-PRC
Mode. This object applies only to QL-SSU-A
Synchronous Ethernet capable ports, when
QL-SSU-B
QL Mode is Enabled. You can use this
QL-EEC1
option to set a minimum expected
received Quality Level on the port. The
valid values depend upon the SYNC entity
Network Clock Type. A value of None
means that a minimum Quality Level is not
expected.

The selections available depend on the

Network Clock Type setting - option1 -
SDH or option2 - SONET.

The default value is QL-NONE. If you

change the Network Clock Type, the
Expected QL defaults to QL-NONE
regardless of the previous setting.

The valid entry for the SDH Network Clock

is: QL-PRC, QL-SSU-A, QL-SSU-B, QL-EEC1,
or QL-NONE. THe default is QL-NONE.
THe valid entry for the SONET Network QL-PRS
Clock is: QL-PRS, QL-STU, QL-ST2, QL- QL-STU
TNC, QL-ST3E, QL-EEC2, QL-SMC, QL- QL-ST2
PROV, or QL-NONE. The default is QL-
QL-TNC
NONE.
QL-ST3E
QL-EEC2
QL-SMC
QL-PROV

Adding a Time Clock Reference

This section includes steps to add a time clock reference to the time clock. You can
provision up to three time-clock references for PRTC mode. ePRTC mode does not support
three time-clock references.

To add a time clock reference:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 204

Oscilloquartz: An ADVA Company Provisioning Operations

1. Click Configuration, or from the Application menu, select Configuration.

2. In the selection tree, next to the System >Synchronization > NE-1 > NTEOSA 5422
entities, click +.
3. Right-click the time clock entity, and then select Add Time Clock Reference.
The Add Time Clock Reference window opens.

4. Set these time clock reference options:

Area Field Setting

Identification TimeREF Index Select the applicable number.
Alias Enter the alias for this reference.
Configuration Priority Select the priority level. The default is 1.
Time Clock Reference Select the applicable sources:
Sources l GPS, PTP clock - always phase.
l PPS-IN - phase if ToD from GNSS is
available; frequency if ToD from GNSS
is not available.
l TOD & PPS-IN - phase if the message
type is not NA If the message type is
NA: phase if TOD from GNSS is
available; frequency if TOD from GNSS
is not available.
l TSC - phase if the Clock Recovery Mode
is set to Two way; otherwise frequency.
l CLK, BITS, Sync-E, Sync - always
frequency.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 205

Oscilloquartz: An ADVA Company Provisioning Operations

5. Click OK.
6. To add another time clock reference, if required, repeat steps 3 to 5.
7. To verify the reference configuration and status, click the time clock entity, and then
select the Status tab. Wait a few minutes for alarms to clear and for the clock mode to
update to Locked.
8. Select the time clock entity again to observe the progress described here.
o The Clock Mode should indicate Locked, and the Source Status should indicate

Reference OK.
o The time clock locks to the reference within 5 to 15 minutes, depending on visibility

and conditions.
o When the time clock establishes synchronization with the reference, the clock mode

is Tracking.
o When the system determines that it can synchronize, the clock mode changes to

Locked.
o The mode might not change to Locked, and the source status might not display

Reference OK. If so, verify the previous provisioning steps and time clock
interconnectivity to the selected reference.

Operating e-PRTC Mode for a Time Clock

Reference
We recommend to enable e-PRTC mode only for QUARTZ HQ++ and Rubidium oscillators
and only after you have connected the cables and verified that the reference signals are
available.

In e-PRTC mode, the Time Clock always uses reference with priority 1 as phase reference
and reference with another priority as frequency reference. The Time Clock can use some
references, such as PPS as either phase or frequency source. Make sure the signals are
connected properly.

Testing e-PRTC performance requires an excellent reference, 10 times better than the e-
PRTC mode. This means that the reference must be -/+ 3 to 5 ns from UTC.

After you enable e-PRTC mode, the Time Clock moves through these states as long as both
references are available and provide required performance:

l Tracking state – typically takes 4 days, in which the TimeClock tracks the GNSS and
Cesium clock. At the end of this state the TimeClock switches to locked state.

l Locked state – in this state the TimeClock is locked and keeps improving the data
that is used in holdover (if the GNSS is lost).
o Optimal holdover data is achieved after e-PRTC is locked for 26 days (30 days

including the tracking state).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 206

Oscilloquartz: An ADVA Company Provisioning Operations

o If the e-PRTC switches to holdover before 26 days, the holdover is good, but
not optimal and may not meet the G.8272.1 e-PRTC holdover specifications.
o If the e-PRTC switches to holdover after 26 days, the holdover is optimal and is
within the G.8272.1 e-PRTC holdover specifications.

Prerequisites
l All cables are connected and reference signals are available.
l Activated the e-PRTC license (see Activating Software Licenses).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 207

Oscilloquartz: An ADVA Company Provisioning Operations

To enable e-PRTC mode:

1. Complete the tasks in Editing a Time Clock and in the e-PRTC Mode field, select
Enabled.
The time clock combines a stable frequency input, such as a Cesium clock, to extend
holdover capabilities to meet the e-PRTC performance standards.
The internal Time Clock algorithm restarts and the Clock Mode may change to Tracking
or Holdover state.
2. Complete the tasks in Adding a Time Clock Reference and in Time Clock Reference
Sources, select the time clock for which you enabled e-PRTC mode.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 208

Oscilloquartz: An ADVA Company Provisioning Operations

Adding a Sync Reference

You can add up to three sync references.

Prerequisites
Before you add a sync reference, you must provision the applicable sync reference port:
l Access port
l BITS-IN
l CLK
l Telecom slave
l PTP time clock

To add a sync reference:

1. On the toolbar, click the Configuration, or from the Application menu, select
Configuration.
2. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click SYNC-1-1-1-1, and then select Add Sync Reference. The Add Sync
Reference window opens.

4. Set these options:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 209

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Identification SYNCREF Index Select the sync reference index number 1 to 3.
The default is 1.
Alias Enter an alias to help identify the line card. The
default is undefined.
Configuration Priority Select the priority value, 1 to 10. The default is
1.
Sync Reference Source Select the Sync Reference Source.

l An interface appears in the Synch Reference Sources list after you

enable Sync-E mode and set its status to IS or Management. Sync-E
does not support a copper SFP.
l If you configure the access port as a 1000Base-T electrical interface,
you must configure this interface as Auto 1000 Full Slave to select it as
a Sync Reference.

5. Click OK.
6. In the selection tree, click the SYNC-1-1-1-1 entity, and in the Configuration tab verify
the entry.
7. Click the Status tab to verify the status. An example is shown in this illustration, where
the Clock Mode is Locked and the Source Status indicates Reference OK.

8. Repeat steps 2 to 7 to add additional sync references, up to three.

9. In the selection tree, click the SYNC-1-1-1-1 entity, and in the Status tab verify that in
the Synchronization Reference List area, the status of each Sync Reference Identifier
(Sync Ref EID) is displayed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 210

Oscilloquartz: An ADVA Company Provisioning Operations

Editing a Sync Reference

1. On the toolbar, click Configuration, or from the Application menu, select
Configuration.
2. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click SYNC-1-1-1-1, and then select Edit Sync Reference. The Edit Sync
Reference window opens.

4. In the Synchronization Reference List area, Select Ref column, select the reference
that you want to edit.
5. In the Priority column, select the applicable priority.
6. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 211

Oscilloquartz: An ADVA Company Provisioning Operations

Deleting a Sync Reference

1. On the toolbar, click Configuration, or from the Application menu, select
Configuration.
2. In the tree pane, expand System > Synchronization > NE-1 > NTEOSA 5422.
3. Right-click SYNC-1-1-1-1, and then select Delete Sync Reference. The Delete Sync
Reference window opens.

4. In the Synchronization Reference List area, Select Ref column, select the reference
that you want to delete.
5. Click OK.

Provisioning the Network Time

Protocol
All NTP provisioning tasks require these prerequisites

1. Configure the NE with an IP address.

2. Connect the NE to a DCN or LAN (see Setting Up the OSA 5422 DCN eth0 Port Through
the Serial Port).
3. Log in to EMS.

4. Enable the NTP-Server license, see Activating Software Licenses.

l First set the system clock, and then you can provision NTP.
l If you configure a unit as a client, that unit receives its NTP packets
through the Management port (DCN).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 212

Oscilloquartz: An ADVA Company Provisioning Operations

l If you configure a unit as a server, that unit sends its NTP packets
through the operational access and network ports.

To provision the NTP, complete these tasks:

1. Configuring an NTP Client

2. Creating an NTP Flow Point
3. Creating an NTP Clock on p. 213
4. Creating an NTP Clock Interface on p. 220
5. Creating an NTP Virtual Port on p. 223

Creating an NTP Flow Point

1. On the toolbar, click NTP, or from the Application menu, select NTP.
2. In the selection tree, next to the System>NE-1>NTEOSA 5422 entities, click +.
3. Right-click an access port, and then select NTPFP. The Create NTP Flow Point window
opens.
4. In the VLAN Configuration area, select or clear the Untagged option as required.
5. Click OK. In the tree pane below the port, the NTP flow point appears.

Creating an NTP Clock

1. On the toolbar, click NTP, or from the Application menu, select NTP.
2. In the Tree pane, expand the System element, right-click NE-1, and then select Create
NTP Clock.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 213

Oscilloquartz: An ADVA Company Provisioning Operations

3. In the Create NTP Clock window, set these NTP clock options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select IS for in service.
NTP Clock NTP Mode Select either:
Configuration
l NTP Server - the NTP clock receives time
from the time reference.
l NTP Peering - the NTP clock receives time
from another server. See Setting up NTP
Peering.
NTP Server Select Enabled.
State

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 214

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

NTP Authentication (optional) Select Enabled to activate autokey
Auto Key authentication. When enabled, the system uses
the RFC5906 Autokey for NTP server
authentication. See Activating Autokey
Authentication.
(optional) Select Enabled to activate MD5 or SHA1
Symmetric Key authentication. See Activating Symmetric Key
Authentication NTP Authentication

(optional) Enabled – the NTP clock responds only to valid

NTP Secure authenticated NTP requests.
Mode
Disabled – the NTP clock responses to any NTP
request.

4. Click OK. The NTP clock appears below the NTEOSA 5422 element.
To complete the Symmetric Key Authentication process, upload and activate an
NTP keys file. See Activating Symmetric Key NTP Authentication.

Setting up NTP Peering

You can set NTP peering without symmetric associations on the OSA 5422. The upper
stratum servers deliver timing signals to the NTP client, which serves as a system time
source. In this mode, the NTP clock operates as a regular NTP server and the time derives
from the system time.

To set up NTP peering:

1. Configure an NTP client as described in Configuring an NTP Client with higher stratum
servers.
2. Set the system ToD to NTP.
3. Create an NTP clock as described in Creating an NTP Clock.
4. Set Server Mode to NTP Peering, and NTP Server State to Enabled.
5. Configure NTP clock interfaces as described in Creating an NTP Clock Interface.

Activating Symmetric Key NTP Authentication

Enable MD5 or SHA1 authentication to guarantee protection for network clients and servers
from accidental or malicious attacks.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 215

Oscilloquartz: An ADVA Company Provisioning Operations

Authenticated NTP packets use NTP extension fields to append an encrypted message
digest. The encryption mechanism can be either MD5 or SHA1. The encryption protocols
require authentication keys that you can save to the device as a text file.

The authentication key files are separate from the system configuration
files. After you restart the system from a configuration file, you must re-load
the authentication key files as described in this procedure.

Prerequisites
1. Set System Time of Day to Time Clock.
2. Complete the steps described in Creating an NTP Clock.

To save authentication key files to your device and enable NTP authentication:

1. Expand the NTP Clock node, right-click NTP Keys, and select Files > Copy from
Remote.

2. In the Method area, File Transfer Method field, select Web, FTP, SCP, or SFTP.
o If you select the Web option, click Choose File and select the NTP Key file.

o If you select FTP, SCP, or SFTP, in the File Transfer area, complete these fields:

Field Setting
Server IP a. Select the applicable server IP as either IPv4 or IPv6. The
default is IPv4.
b. Enter the server IP address.
User ID Enter the user ID.
User Password Enter the password.
Remote File Enter the path to the key file.

3. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 216

Oscilloquartz: An ADVA Company Provisioning Operations

The upload begins, and a status bar displays the progress. The upload is complete when
the status changes to Success.
4. Right-click NTP Keys and select File > Activate.

5. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 217

Oscilloquartz: An ADVA Company Provisioning Operations

To edit an NTP key file:

1. Right-click NTP Keys ans select Edit.

2. Enable or disable keys and click OK to save your changes.

Example NTP Authentication File - Correct Keys

The NTP clock uses only the first 20 keys that are formatted correctly.

# Mon Feb 4 09:35:02 2019

1 MD5 Nny]PCEEP9zraD|uMQ0p # MD5 key
2 MD5 a||cP%0Mw8)}={f!3m^| # MD5 key
3 MD5 5eeGF^<~Zzg+F=>|H{s+ # MD5 key
4 MD5 _m{9F.7P+J3>le`TocO\ # MD5 key
5 MD5 <&1.x&OH[;J(QpJjtm&\ # MD5 key
6 MD5 @p54>MQ7;%Q)yQPGY]-+ # MD5 key
7 MD5 fanp&q(rJ?%:tSJb3]h% # MD5 key
8 MD5 f0&Qa?)59j]r2cW)_/&$ # MD5 key
9 MD5 Ha1oT?"s"?O_+b<l^p;, # MD5 key
10 MD5 fNhRO0M7UtiPw9~3M,t- # MD5 key
11 SHA1 a5645ed4301683782fded6d49aa56ec8e10b9c0e # SHA1 key
12 SHA1 9ec0dbd9df682f67053962cd458df74c9fcc6d8b # SHA1 key
13 SHA1 a5167ea461d1d93c28db178a0600bd13f4a6f1b2 # SHA1 key
14 SHA1 14889885e95c1f9b8d0f7d3e36e533674bb48c5a # SHA1 key
15 SHA1 cbe581e5bbd6da9973cfdb1504447417e59294c8 # SHA1 key
16 SHA1 0023ad0a42f7b0fb2b8101d73759b49e0de039fb # SHA1 key
17 SHA1 b9c01c94d35961d64fda09e152f494c36dae6a0c # SHA1 key
18 SHA1 04b6233c1d8069094062860aac5584c51c7c1d4f # SHA1 key
19 SHA1 702f3d6a152ea9d596042fc064d62a851fb2cc5a # SHA1 key
20 SHA1 fcfeacc948bfb7378cd8a6ba37bb3cf3e36d30e8 # SHA1 key

Example NTP Authentication File - Incorrect Keys

# Mon Feb 4 09:35:02 2019
# This is a keys file with some invalid keys

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 218

Oscilloquartz: An ADVA Company Provisioning Operations

0 MD5 UtiPw9~3M,t-QpJjtm&\ # KeyId 0 not permitted

1 md5 Nny]PCEEP9zraD|uMQ0p # md5 is valid
2 Md5 a||cP%0Mw8)}={f!3m^| # Md5 is valid
3 M 5eeGF^<~Zzg+F=>|H{s+ # M is valid
4 m _m{9F.7P+J3>le`TocO\ # m is valid
5 MD5 <&1.x&OH[;J(QpJjtm&\ # MD5 key
6 MD5 @p54>MQ7;%Q)yQPGY]-+ # MD5 key
7 MD5 hello # MD5 key
8 MD5 f0&Qa?)59j]r2cW)_/&$ # MD5 key
9 MD5 Ha1oT?"s"?O_+b<l^p;, # MD5 key
10 MD5 fNhRO0M7UtiPw9~3M,t- # MD5 key
10 SHA1 0023ad0a42f7b0fb2b8101d73759b49e0de039fb # KeyId already defined
17 sha1 b9c01c94d35961d64fda09e152f494c36dae6a0c # SHA1 key
18 SHA1 04b6233c1d8069094062860aac5584c51c7c1d4f # sha1 is valid
19 SHA1 702f3d6a152ea9d596042fc064d62a851fb2cc5a # SHA1 is valid
20 SHA1 fcfeacc948bfb7378cd8a6ba37bb3cf3e36d30e8 # SHA1 key
23 SHA1 ThisIsPermitted # SHA1 key
24 MD5 fcfeacc948bfb7378cd8a6ba37bb3cf3e36d30e8 # this is also permitted
25 MD5 ThisIsNotPermitted_Max20AsciiChars # key is too long for ASCII chars
65011 SHA1 a5645ed4301683782fded6d49aa56ec8e10b9c0e # SHA1 key
65012 SHA1 9ec0dbd9df682f67053962cd458df74c9fcc6d8b # SHA1 key
65013 SHA1 A5167EA461d1d93c28db178a0600bd13f4a6f1b2 # Capital letters are allowed
65014 SHA1 14889885e95c1f9b8d0f7d3e36e533674bb48c5a # SHA1 key
65015 SHA1 cbe581e5bbd6da9973cfdb1504447417e59294c8 # SHA1 key
65535 SHA256 a5645ed4301683782fded6d49aa56ec8e10b9c0e # Max KeyId, SHA256 not supported

Activating Autokey Authentication

Enable Autokey authentication to guarantee protection fornetwork clients and servers from
accidental or malicious attacks. In Autokey authentication, the system generates keys and
automatically validates them between certified hosts.

Prerequisites
Set System Time of Day to Time Clock.

To activate autokey authentication:

1. Complete the steps described in Creating an NTP Clock.

2. In the NTP Authentication area, enable Auto Key.
The system automatically creates a trusted host certificate and a private key, and then
NTPC is ready for the certificate.

The certificate expires one year after the generation date according to the
system time. The system issues a notification two weeks before expiration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 219

Oscilloquartz: An ADVA Company Provisioning Operations

3. To update the certificate, right-click NTP AutoKey, and then select Certificate Update.
4. In the Update NTP Clock Auto Key area, click OK.

Creating an NTP Clock Interface

The number of transactions per seconds (TPS) that the NTEOSA 5422 supports depends on
these factors, for more information see the OSA 5422 System Description:

l The number of NTP clock interfaces.

l The NTP client addresses are on the same subnet as the NTP server or on a
different subnet through the gateway.
l The interface uses IPv4 or IPv6.

To create an NTP clock interface:

1. On the toolbar, select the NTP application, or from the Application menu, select NTP.
2. In the tree pane, expand System>NE-1.
3. Right-click the NTP CLOCK node, and then select Create NTP Clock Interface.
The Create NTP Clock Interface window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 220

Oscilloquartz: An ADVA Company Provisioning Operations

4. Set these options:

Area Field Setting

Identification Alias Enter an alias to help identify the line card. The
default is undefined.
State Administrative Select the applicable administrative state, either
IS for In Service or Management. The default is
Management. For more information, see Entity State
Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 221

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Time Time Scale Select the NTP server time:

l UTC time
l Local time - UTC time with local time zone offset
including Daylight Saving Time as configured in
Editing the Time Zone.
l GPS time

Current Time of Displays the current time of day of the NTP server.
Day
IP Interface IP Protocol Select the appropriate IP protocol, where the default
configuration is IPv4.
Default Select Enabled to activate the IPv4 or IPv6 gateway
Gateway address. The default setting is Disabled.
Control
IPv6 Address Enter the applicable address.
IPv6 Gateway An incorrect IP setting can cause service packets to
IPv4 Address leak through the default route interface.

Subnet Mask
Default GW
Interface Name This is a mandatory field. Enter the name of the
interface.
DSCP Enter a value from 0 to 63. The default is 0.
Time and Time Protocol Select Enabled to activate time protocol (RFC868) for
Daytime the NCI. The default is Disabled.
Configuration Daytime Select Enabled to activate daytime protocol (RFC867)
Protocol for the NCI. The default is Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 222

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Broadcast State Select Enabled to generate NTP broadcast messages
Configuration on the NCI.
Note: If the time clock is not locked or in holdover
state, the server does not generate broadcast
messages. If you want to use the broadcast server
regardless of the time clock, configure the time clock
holdover to not available.
Default is Disabled.
IPv6 Address Available when IP Protocol is set to IPv6.
Enter an applicable IPv6 address for the broadcast.
Valid values: FF0x:x:x:x:x:x:x:x.
Default: ff05::101.
IPv4 Address Available when IP Protocol is set to IPv4.
Enter an applicable IPv4 address for the broadcast.
Valid values: 224.0.1.0 ... 238.255.255.255
Default: 224.0.1.1, or the network broadcast address.
Interval Select the broadcast interval from the list.
Default is 64 seconds.
Max Hops Enter the maximum TTL/Hop Limit of the NTP
broadcast messages.
Valid values: 1 to 255. Default is 1.
Symmetric Key Enter the key ID that is used to authenticate
broadcast messages.
Version Select the version of the NTP broadcast messages.
Default is NTPV4.

5. Click OK. Below the NTP Clock Interface, the NTP Clock is displayed.

Creating an NTP Virtual Port

To create an NTP virtual port:

1. On the toolbar, click the NTP, or from the Application menu, select NTP.
2. In the tree pane, expand System>NE-1>NTP CLOCK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 223

Oscilloquartz: An ADVA Company Provisioning Operations

3. Right-click the NTP Clock Interface, and then select Create NTP Virtual Port. The
Create NTP Virtual Port window opens.
4. In the Configuration area, NTP Flow Point menu, select an NTP flow point.

If you created an NTP flow point, the Configuration area is displayed (see
Creating an NTP Flow Point).

5. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 224

Oscilloquartz: An ADVA Company Provisioning Operations

Provisioning the Precision Time

Protocol
This section provides the Precision Time Protocol (PTP) configurations, including:

Layer 3 PTP G.8265.1 or G.8275.2 Grandmaster Clock Provisioning Order 226

Layer 3 PTP G.8265.1 Telecom Slave Provisioning Order 226
Layer 3 PTP G.8275.2 Telecom Slave Provisioning Order 227
Layer 3 PTP Enterprise Profile or Default Profile Slave Clock Provisioning Order227
Layer 3 Enterprise or Default Profile Grandmaster Clock Provisioning Order 227
Layer 3 PTP G.8265.1 and G.8275.2 Boundary Clock Provisioning Order 229
Layer 3 PTP Broadcast Profiles Master Clock Provisioning Order 229
Layer 3 PTP Broadcast Profiles Master Clock Provisioning Order 230
Layer 2 PTP Multicast G.8275.1 and Default Profile Grandmaster Clock
Provisioning Order 231
Layer 2 PTP Multicast G.8275.1 Boundary Clock and Slave Clock Provisioning
Order 231
Layer 2 PTP Power Profiles Grandmaster Clock Provisioning Order 232
PTP Procedures 233

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 225

 Oscilloquartz: An ADVA Company Provisioning Operations

Layer 3 PTP G.8265.1 or G.8275.2 Grandmaster

Clock Provisioning Order
Create the Layer 3 PTP unicast G.8265.1 or G.8275.2 grandmaster clocks in this order:

1. Activate the applicable PTP-MC-BC-IP-UNICAST-Profile-<number of remote slaves>-

Remote-Slaves license (see Activating Software Licenses).
2. Ensure that you provision the port associated with the PTP flow point and set the port to
In Service (see Provisioning Access Ports).
3. Edit the Ethernet port Delay Asymmetry setting (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit a time clock (see Editing a Time Clock).
5. Add a time clock reference (see Adding a Time Clock Reference), which can optionally
include: Provisioning the GNSS Receiver.
6. Create a G.8265.1 or G.8275.2 grandmaster clock (see Creating Layer 3 PTP Master
Clock).
7. Create a master clock interface ( see Creating a Master Clock Interface).
8. Create a PTP flow point with type OC Master (see Creating a PTP Flow Point).
9. Create a master virtual port (see Creating a Master Virtual Port).
10. Create a static remote slave (see Creating G.8275.2 or G.8265.1 Static Remote Slave).

Layer 3 PTP G.8265.1 Telecom Slave Provisioning

Order
You can create a single Telecom slave for the system. Create theTelecom slave and its
associated timing functions in this order.

1. Verify that you provision the ports associated with the PTP flow point and set the port to
In Service (see Provisioning Access Ports).
2. Edit the Ethernet ports Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
3. Create a Telecom slave (see Creating a Telecom Slave).
4. Create a Slave-Only Ordinary Clock (SOOC). See (Creating a Slave-Only Ordinary Clock).
5. Create a PTP flow point (PTPFP) for the ordinary clock slave (see Creating a PTP Flow
Point).
6. Create an ordinary clock slave port (see Creating an Ordinary Clock Slave Port).
7. Repeat Steps 4 to 6 for a second SOOC.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 226

Oscilloquartz: An ADVA Company Provisioning Operations

Layer 3 PTP G.8275.2 Telecom Slave Provisioning

Order
Create a Layer 3 G.8275.2 Telecom slave in this order:

1. Verify that you provision the ports associated with the PTP flow points, and that you set
the ports to In Service (see Provisioning Access Ports).
2. Edit the Ethernet port Delay Asymmetry setting (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
3. Create a slave-only PTP clock with G.8275.2 profile.
4. Create a PTP flow point (see Creating a PTP Flow Point).
5. Create a Layer 3 PTP port (see Creating a PTP Port).

Layer 3 PTP Enterprise Profile or Default Profile

Slave Clock Provisioning Order
Create a Layer 3 Enterprise profile or default (IEEE 1588 2008 Annex J3) profile slave clock in
this order:

1. Verify that you provision the ports associated with the PTP flow points, and that you set
the ports to In Service, see Provisioning Access Ports.
2. Edit the Ethernet port Delay Asymmetry setting, see Editing the Delay Asymmetry
Setting of an Ethernet Port.
3. Create a slave-only PTP clock with ENTERPRISE or IEEE_1588_2008_ANNEX_J3, see
Creating a PTP Clock.
4. Create a PTP flow point, see Creating a PTP Flow Point.
5. Create a Layer 3 PTP port, see Creating an L3 PTP Port.

Layer 3 Enterprise or Default Profile Grandmaster

Clock Provisioning Order
Create a Layer 3 enterprise or default profile grandmaster clock in this order:

1. Activate the software license PTP-Enterprise-and-IEEE-1588-2008-L3-Multicast-Profile

(see Activating Software Licenses).
2. Verify that you provision the ports associated with the PTP flow points and set the ports
to In Service (see Provisioning Access Ports).
3. Edit the Ethernet ports Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 227

Oscilloquartz: An ADVA Company Provisioning Operations

4. Edit a time clock (see Editing a Time Clock).

5. Add a time clock reference (see Adding a Time Clock Reference), which can include:
(Optional) Provisioning the GNSS Receiver.
6. Create a Layer 3 enterprise profile grandmaster clock:
a. Create a master clock with a PTP Enterprise profile.
b. Create a master clock interface (see Creating a Master Clock Interface).
c. Create an OC Master PTP flow point (see Creating a PTP Flow Point).
d. Create a master virtual port ( see Creating a Master Virtual Port).
7. Validate dynamic remote slaves (see Verifying a Dynamic Remote Slave Connectivity).
8. Repeat step 6 for additional MCIs.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 228

 Oscilloquartz: An ADVA Company Provisioning Operations

Layer 3 PTP G.8265.1 and G.8275.2 Boundary Clock

Provisioning Order
Create the Layer 3 PTP G.8265.1 or G.8275.2 boundary clock in this order:

1. Activate the software license for PTP features (see Activating Software Licenses).
2. Ensure that you provision the ports associated with the PTP flow points for the master
virtual ports, and set the ports to In Service (see Provisioning Access Ports).
3. Edit the Ethernet ports Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Create a Telecom slave clock (see Creating a Telecom Slave) or G.8275.2 slave clock (see
Creating a Telecom Slave)
5. Create a boundary clock (see Creating a Boundary Clock).
6. Create a master clock interface (see Creating a Master Clock Interface).
7. Create a PTP flow point for the ordinary clock master (see Creating a PTP Flow Point).
8. Create a master virtual port (see Creating a Master Virtual Port).
9. Create static remote slaves (see Creating G.8275.2 or G.8265.1 Static Remote Slave).
10. Validate dynamic remote slaves (see Validating MCI Dynamic Remote Slave).

Layer 3 PTP Broadcast Profiles Master Clock

Provisioning Order
The OSA 5422 supports these broadcast profiles for professional media applications:

l AES67 — IEEE 1588-2008 Precision Time Protocol for PTP profile for media
applications
l SMPTE ST 2059-2 — IEEE 1588-2008 Precision Time Protocol optimized to the
needs of media synchronization

Provision the Layer 3 PTP broadcast profiles master clock in this order:

1. Activate the PTP-Broadcast-Profiles software license (see Activating Software Licenses).

2. Ensure that you provision the port associated with the PTP flow point and that you set
the port to In Service (see Provisioning Access Ports).
3. Edit the Ethernet port Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit the GNSS receiver port (see Editing a GNSS Port).
5. Edit a time clock (Editing a Time Clock).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 229

 Oscilloquartz: An ADVA Company Provisioning Operations

6. Add a time clock reference (see Adding a Time Clock Reference). This can include editing
the GNSS receiver port (optional).
7. Create a PTP master clock with AES67_MDIA or SMPTE_ST_2059_2 profile (see Creating
Layer 3 PTP Master Clock).
8. Create an Ethernet Multicast PTP flow point (see Creating a PTP Flow Point).
9. Create a PTP port (see Creating a PTP Port).
10. Repeat steps 8 and 9 for additional PTP ports.

Layer 3 PTP Broadcast Profiles Master Clock

Provisioning Order
The OSA 5422 supports these broadcast profiles for professional media applications:

l AES67 — IEEE 1588-2008 Precision Time Protocol for PTP profile for media
applications
l SMPTE ST 2059-2 — IEEE 1588-2008 Precision Time Protocol optimized to the
needs of media synchronization

Provision the Layer 3 PTP broadcast profiles master clock in this order:

1. Activate the PTP-Broadcast-Profiles software license (see Activating Software Licenses).

2. Ensure that you provision the port associated with the PTP flow point and that you set
the port to In Service (see Provisioning Access Ports).
3. Edit the Ethernet port Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit the GNSS receiver port (see Editing a GNSS Port).
5. Edit a time clock (Editing a Time Clock).
6. Add a time clock reference (see Adding a Time Clock Reference). This can include editing
the GNSS receiver port (optional).
7. Create a PTP master clock with AES67_MDIA or SMPTE_ST_2059_2 profile (see Creating
Layer 3 PTP Master Clock).
8. Create an Ethernet Multicast PTP flow point (see Creating a PTP Flow Point).
9. Create a PTP port (see Creating a PTP Port).
10. Repeat steps 8 and 9 for additional PTP ports.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 230

 Oscilloquartz: An ADVA Company Provisioning Operations

Layer 2 PTP Multicast G.8275.1 and Default Profile

Grandmaster Clock Provisioning Order
Create a Layer 2 PTP multicast G.8275.1 or default profile (Annex F) grandmaster clock in
this order:

1. Activate the software license PTP-Clock-G-8275-1-and-IEEE-1588-2008-Annex-F-

Profiles (see Activating Software Licenses).
2. Verify that you provision the ports associated with the PTP flow points and that the ports
are set to In Service (see Provisioning Access Ports).
3. Edit the Ethernet ports Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit a GNSS receiver port (see Provisioning the GNSS Receiver).
5. Edit a time clock (Editing a Time Clock).
6. Add a time clock reference (see Adding a Time Clock Reference). This step can optoinally
include editing a GNSS port.
7. Create a master-only PTP Clock with a G.8275.1 or IEEE_1588_2008_ANNEX_F profile
(seeCreating a PTP Clock).
8. Create an Ethernet Multicast PTP flow point (see Creating a PTP Flow Point).
9. Create a PTP port (see Creating a PTP Port).
10. Verify the connectivity of the remote slaves (see Verifying Remote Slave Connectivity).
11. Repeat Steps 9 and 10 for additional PTP ports.

Layer 2 PTP Multicast G.8275.1 Boundary Clock

and Slave Clock Provisioning Order
Create a Layer 2 PTP multicast G.8275.1 boundary clock or slave clock in this order:

1. Activate the software license PTP-Clock-G-8275-1-and-IEEE-1588-2008-Annex-F-

Profiles (see Activating Software Licenses).
2. Verify that you provision the ports associated with the PTP flow points and set the ports
to In Service (see Provisioning Access Ports).
3. Edit the Ethernet ports Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit a GNSS receiver port (see Provisioning the GNSS Receiver).
5. Edit a time clock (see Editing a Time Clock).
6. Add a time clock reference (see Adding a Time Clock Reference).
7. Create PTP clock type Boundary Clock or type Slave Only with G.8275.1 profile (see
Creating a PTP Clock).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 231

 Oscilloquartz: An ADVA Company Provisioning Operations

8. Create an PTP flow point type Eth Multicast (see Creating a PTP Flow Point).
9. Create a PTP port (see Creating a PTP Port).
10. Verify the connectivity of G.8275.2 remote slaves for boundary clock ports in Master
state (see Verifying Remote Slave Connectivity).
11. Repeat steps 8 to 10 for additional PTP ports.

Layer 2 PTP Power Profiles Grandmaster Clock

Provisioning Order
The OSA 5422 supports these power system profiles:

l IEEE C37.238 2011 and 2017 — IEEE Standard Profile for Use of IEEE 1588™
Precision Time Protocol in Power System Applications
l IEC PAS 61850-9-3 — Precision Time Protocol Profile for Power Utility Automation

POWER_C37_238_2011 and optionally POWER_C37_238_2017 profiles in

ALTERNATE_TIME_OFFSET_INDICATOR TLV use the Time Zone Name con-
figured per system, see Editing the Time Zone.

Provision the Layer 2 PTP power profiles grandmaster clock in this order:

1. Activate the software license PTP-Clock-Power-and-Utility-Profiles (see Activating

Software Licenses).
2. Ensure that you provision the port associated with the PTP flow point and that you set
the port to In Service (see Provisioning Access Ports).
3. Edit the Ethernet port Delay Asymmetry settings (see Editing the Delay Asymmetry
Setting of an Ethernet Port).
4. Edit the GNSS receiver port (see Editing a GNSS Port).
5. Edit a time clock (Editing a Time Clock).
6. Add a time clock reference (see Adding a Time Clock Reference). This can include editing
the GNSS receiver port (optional).
7. Create Master Only PTP clock with POWER_C37_238_2011, POWER_C37_238_2011, or
UTILITY_IEC_61850_9_3 profile (see Creating a PTP Clock).
For POWER_C37_238_2011 and POWER_C37_238_2017 profiles specify Grandmaster
identity.
8. Create an Ethernet Multicast PTP flow point (see Creating a PTP Flow Point).
9. Create a PTP port (see Creating a PTP Port).
10. Repeat steps 8 and 9 for additional PTP ports.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 232

Oscilloquartz: An ADVA Company Provisioning Operations

PTP Procedures
Editing the Delay Asymmetry Setting of an Ethernet Port 233
Creating a Telecom Slave 234
Creating a Boundary Clock 243
Creating a Master Clock Interface 245
Creating a Master Virtual Port 249
Creating Layer 3 PTP Master Clock 249
Creating G.8275.2 or G.8265.1 Static Remote Slave 253
Validating MCI Dynamic Remote Slave 256
Verifying a Dynamic Remote Slave Connectivity 257
Creating a PTP Clock 260
Verifying Remote Slave Connectivity 263
Creating a Power Profile Grandmaster Clock 264
Creating a PTP Flow Point 267
Creating a PTP Port 270
Creating an L3 PTP Port 275

Editing the Delay Asymmetry Setting of an Ethernet Port

Asymmetry introduces time error. Link delay might be asymmetrical. You can configure the
link delay asymmetry of the Ethernet ports. It is possible that you already know the value of
the link asymmetry that you must consider. You can configure this value for any number in
the range –2,147,483,648 to 2,147,483,648 nanoseconds. The clock uses the configured
delay asymmetry value to compensate for known asymmetry associated with the link.

To edit the delay asymmetry setting of an Ethernet port:

1. On the toolbar, click the PTP or from the Application menu, select PTP.
2. Expand the System > NE-1 > NTEOSA 5422 entities.
3. Right-click the Ethernet Port entity, and then select Edit.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 233

Oscilloquartz: An ADVA Company Provisioning Operations

An Edit PTP Access Port window opens.

4. In the Configuration area, Delay Asymmetry field, enter the appropriate value in
nanoseconds, and then click OK.

Creating a Telecom Slave

Complete these tasks to create a Telecom slave:

Creating a Slave-Only Ordinary Clock 236

Creating a PTP Flow Point 239
Creating an Ordinary Clock Slave Port 240

To edit a Telecom slave, right-click the Telecom slave entity (TS-1-1), and then select Edit.
To delete a Telecom slave, right-click the Telecom slave entity, and then select Delete.

Prerequisites
l Provision the master clock device.
l Verify that there is a network connection to the parent master port.

To create a Telecom slave:

1. On the toolbar, click PTP or from the Application menu, select PTP.
2. Expand the System entity, right-click NE-1, and then select Create Telecom Slave.
The Create Telecom Slave window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 234

Oscilloquartz: An ADVA Company Provisioning Operations

3. In the Create Telecom Slave window, set these Telecom slave options:
For more information about the Telecom slave parameter options, see Telecom Slave
Parameter Options.

Area Field Setting

Identification Alias Enter the alias.
Clock Identify Enter the appropriate value, or use the value
that the node populates.
State Administrative Select the appropriate choice.
TS Configuration PTP Domain Number Enter the domain number. Valid values:
0 to 255. The default is 4.
Clock Recovery Select either One Way for frequency or Two-
Mode Way for frequency and phase.

Time Holdover Select the holdover value.

Accuracy (ns)
WTR Time (min) Enter the wait-to-restore time in minutes.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 235

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Sync Sync Reference Select Enabled or Disabled.
Configuration
l If set to Enabled, the Telecom slave is
available as a possible reference for the
system synchronization object.
l If set to Disabled, the Telecom slave port
is unavailable as a possible reference for
the system sync object.
You can use the sync object for the Telecom
slave clock frequency synchronization if you
select it as Sync ID reference.
QL Mode Select the appropriate option.
Sync ID Select the appropriate option.
Assumed QL Select the appropriate option.
Expected QL Select the appropriate option.

4. After you finish setting the Telecom slave options, click OK.
A Telecom slave entity is displayed below the Ethernet ports in the selection tree.
5. To view the configuration details, click the Telecom slave entity (TS-1-1).

Creating a Slave-Only Ordinary Clock

After you create a Telecom slave, you can create a slave-only ordinary clock (SOOC). You
can create a maximum of two SOOCs per Telecom slave. You can configure a SOOC for IPv4
or IPv6. Each SOOC is IP version-independent. For example, one SOOC can operate over
IPv4 and the other over IPv6.

IPv4 addresses cannot be zero or all ones, such as 255.255.255.255, or be a

subnet broadcast address, multicast address, or experimental subnet.

To edit an SOOC, right-click the SOOC entity (SOOC-1-1-1-1-1), and then select Edit. To
delete an SOOC, right-click the SOOC entity, and then select Delete. You cannot delete the
SOOC if the Telecom slave is associated with a synchronization reference.

To create a Slave-Only Ordinary Clock:

1. Right-click the Telecom entity (TS-1-1), and then select Create SOOC to open the
Create Slave-Only Ordinary Clock window.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 236

Oscilloquartz: An ADVA Company Provisioning Operations

2. Set these options:

Area Name Field Name Setting

Identification SOOC ID Enter the SOOC ID. You can create a maximum of 2
SOOCs per Telecom slave.
Alias Enter the alias you want to use.
State Administrative Select the state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 237

Oscilloquartz: An ADVA Company Provisioning Operations

Area Name Field Name Setting

Configuration IP Protocol Select the appropriate protocol.
Slave IPv4 Address Enter the applicable address. An incorrect IP setting
Slave Subnet Mask can cause service packets to leak through the
default route interface.
Slave IPv6 Address
Interface Name (Mandatory) Enter the name of the interface.
Unicast Message Select Enabled or Disabled.
Notification
Expected Clock Enter a value from 0 to 255 for the maximum
Class expected clock class. If the received clock class is
higher than the expected clock class value, the
system drops the packets from the parent
grandmaster or boundary clock sending this clock
class. In addition, a ClockClassMismatch alarm is
generated (see SOOC Alarms). The default is 247.
Unicast Timeout Enter a value from 1 to 600 seconds.
Unicast Restart Enter a value from 30 to 1,800 seconds.
Timers
Priority Mode Select the mode you want to use, or None.
Priority Enter the priority level for the priority mode.
Master Clock Master Delay Select the delay mechanism.
Configuration Mechanism
Master Priority Enter 0 to 255.
Master Clock Enter this address.
IPv4 Address
Master Clock IPv6 Enter this address.
Address

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 238

Oscilloquartz: An ADVA Company Provisioning Operations

Area Name Field Name Setting

Master Clock Master Announce Select the applicable rate.
Message Message Rate
Rates/Duration Master Announce Enter the applicable interval from 2 to 255 intervals.
Receipt Timeout
Master Delay Select the applicable rate.
Response Message
Rate
Master Delay Enter the applicable interval from 2 to 255.
Response Receipt
Timeout
Master Sync Select the applicable rate.
Message Rate
Master Sync Enter the applicable interval from 2 to 255.
Receipt Timeout
Master Lease Enter the seconds from 60 to 1,000.
Duration
E2E Asymmetry E2E Asymmetry Select the applicable mode.
Delay Delay Comp Mode
Compensation E2E Asymmetry If you set the E2E Asymmetry Delay Comp Mode
Delay Comp to Enabled, enter the value from –100,000,000 to
100,000,000 nanoseconds.
Protection Lockout Control Select Enabled or Disabled.
Configuration

For more information on the SOOC parameter options, see Slave Only
Ordinary Clock Parameter Options.

3. Click Apply to apply the changes, and then click OK.

4. In the selection tree, expand the Telecom slave entity, such as TS-1-1.
An SOOC entity displays below the Telecom slave entity.
5. To view the configuration details, click the SOOC entity.

Creating a PTP Flow Point

To edit a PTPFP entity, for example, ACC PTP FLOW PT-1-1-1-1-1, right-click it, and then
select Edit. To delete a PTPFP, right-click the PTPFP entity, and then select Delete.

For instructions to create a PTP flow point, see Creating a PTP Flow Point.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 239

Oscilloquartz: An ADVA Company Provisioning Operations

Creating an Ordinary Clock Slave Port

After you create a PTP flow point , you can then create an ordinary clock slave (OCS) port.
See Creating a PTP Flow Point.

To edit the OCS port, right-click the OCS port entity, OCS PORT-1-1-1-1, and then select
Edit. To delete an OCS port, right-click the OCS port entity, and then select Delete.

For more information about the OCS port parameter options, see Ordinary Clock Slave Port
Parameter Options.

To create an ordinary clock slave port:

1. In the selection tree, right-click the SOOC entity, and then select Create OCS Port.
The Create Ordinary Clock Slave Port window opens.

2. In the Identification area, Alias field, enter the OCS port alias.
3. In the Configuration area, PTP Flow Point field, select the flow point associated with
the clock source.
4. After you set the OCS port options, click OK.
In the selection tree, an OCS PORT entity dislays below the associated SOOC entity.
5. To view the configuration details and port state, click the OCS PORT entity. Wait a few
minutes for alarms to clear, and the Port State updates to Slave. Click the OCS PORT
entity again to observe progress.

The OCS recovered clock locks to the selected master clock within 5 to 60
minutes, depending on network conditions. If the software receives no
messages, the Port State is Listening. After the software receives
messages from the master clock, the Port State updates to Uncalibrated.
When the system determines it can calibrate time, the Port State updates
to Slave, and the Telecom slave locks to the Master (Locked). If the lock
does not occur, verify the previous provisioning steps and whether there
is interconnectivity to the master clock.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 240

Oscilloquartz: An ADVA Company Provisioning Operations

6. To view Performance Monitoring data, click the PTP flow point entity and open the
Statistics tab. Ensure that the software is receiving messages. If not, troubleshoot
accordingly. Current PTP statistics are displayed as shown in this illustration.

7. To view Performance Monitoring data, click the SOOC entity and open the Statistics tab
and the Summary tab. If required, open the Raw PTP Messages tab to view raw PTP
messages.
Examples are provided in the next two illustrations.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 241

Oscilloquartz: An ADVA Company Provisioning Operations

8. To view configuration details and port state, click the OCS PORT entity. Wait until the
Port Status updates to Slave.
An example is shown in this illustration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 242

Oscilloquartz: An ADVA Company Provisioning Operations

Creating a Boundary Clock

You can create a boundary clock by completing the instructions in this section. When you
create a boundary clock, see the example configuration for the provisioning procedure in
this section.

To edit a boundary clock, right-click the boundary clock entity, such as BOUNDARY CLOCK-
1-1), and then select Edit. To delete a boundary clock, right-click the boundary clock entity,
and then select Delete.

This table details support of boundary clock classes according to port speed and media
type:

OSA 5422 Boundary Clock Class (G.8273.2)

1G fiber, including 4x1G line card D
10G fiber D
1G copper C
100M copper A
1G sync copper SFP C
100M sync copper SFP A

An example configuration is shown in this illustration.

Figure 6: Example Boundary Clock and Dynamic Remote Slave in a G.8265.1 Topology

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 243

Oscilloquartz: An ADVA Company Provisioning Operations

Boundary Clock Provisioning Slave Clock Provisioning

l Boundary Clock l Telecom Slave TS-1-1
l TS-1-1: PTP Domain Number= 4, Sync Reference= l PTP Domain Number= 4
Disabled, Sync ID= None
l SOOC: Slave IP: 192.168.106.5, Subnet Mask = l SOOC: Slave IP: 10.206.206.6,
255.255.255.0 Subnet Mask = 255.255.255.0
l MC IP: 192.168.106.1, Subnet Mask = l MC IP: 10.206.206.1, Subnet
255.255.255.0 Mask = 255.255.255.0
l Unicast Message Negotiation= Enabled l Unicast Message
Negotiation= Enabled
l Access port PTP Flow Point: Outer VLAN l NET PTP Flow Point: Outer VLAN
EtherType=8100, VLAN=106-0, OC Slave EtherType=8100, VLAN=206-7,
OC Slave
l OCS Port: to Access port PTP Flow Point l OCS Port to NET Port PTP Flow
Point
l MCI: IP 10.206.206.1, Subnet Mask =
255.255.255.0
l Access Port PTP Flow Point: Outer VLAN
EtherType=8100, VLAN=206-7, OC Master
l MVP: to Access Port PTP Flow Point
l Dynamic Slave: IP 10.206.206.6

Steps for Creating a Boundary Clock

1. Click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System, right-click NE-1, and then select Create Boundary
Clock. The Create Boundary Clock window opens.

3. Set these boundary clock options:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 244

Oscilloquartz: An ADVA Company Provisioning Operations

For more information on the boundary clock parameter options, see Boundary Clock
Parameter Options.

Area Field Setting

Identification Boundary Clock Enter the appropriate value.
Index
Alias Enter the alias for the boundary clock.
Use Selected Select to use the Clock Identity that the node
Telecom Slave populates.
Clock Identity
Clock Identify To use a different Clock Identity than what the
node populates, enter the Clock Identity.
State Administrative Select IS.
Boundary Timing Source Enter Telecom slave or PTP clock with a G.8275.2
Clock profile.
Configuration PTP Domain Enter the PTP domain number. Valid values are 0
Number to 255. The default depends on the selected
PTP profile.

4. After you set the boundary clock options, click OK.

The boundary clock displays below the network element entity in the selection tree.
5. To verify the configuration details, click the boundary clock entity.

Creating a Master Clock Interface

You can create a Master Clock Interface (MCI) for a master clock or boundary clock and
configure an MCI for IPv4 or IPv6 networks. Each MCI is IP version-independent. For
example, one MCI can run over IPv4 and the other over IPv6. You can configure up to 16
MCIs per boundary clock.

IPv4 addresses cannot be zero or all ones (such as 255.255.255.255), or be a

subnet broadcast address, multicast address, or experimental subnet.

To edit an MCI, right-click the master clock interface entity, such as MCI-1-1-1, and then
select Edit. To delete an MCI, right-click the MCI entity, and then select Delete.

For demonstration or debug purposes, you can configure grand master and slave clocks in
the same device and connect between the device ports via loopback. Then, configure these
static ARP settings:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 245

Oscilloquartz: An ADVA Company Provisioning Operations

l Add a static ARP entry: <slave IP address> <slave port MAC address> <master IP
interface>
l Add a static ARP entry: <master IP address> <master port MAC address> <slave IP
interface>

To create a master clock interface:

1. Right-click the boundary clock or master clock element and select Create Master Clock
Interface.
The Create Master Clock Interface window opens.

2. Set these master clock interface options:

For more information about the master clock interface parameter options, see Master
Clock Interface Parameter Options.

Area Field Setting

Identification Master Clock Interface Enter the appropriate value.
Index
Alias Enter the alias for this interface.
State Administrative Select IS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 246

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

IP Interface IP Protocol Select the appropriate IP protocol. The
configuration default is IPv4.
Default Gateway Control Select Enabled to activate IPv4 or IPv6
gateway address. The default is Disabled.
IPv6 Address Enter the applicable address. An incorrect
IP setting can cause service packets to leak
PIv4 Address
through the default route interface.
Subnet Mask
Interface Name This field is mandatory. Enter the name of
the interface.
Priority Mode Select the mode you want to use, or None.
Default for AES67_MEDIA and SMPTE_ST_
2059_2 is DCSP.
Priority If you set the Priority Mode, select the
priority level.
Default for AES67_MEDIA and SMPTE_ST_
2059_2 is 46.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 247

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

PTP Clock Type Select the type. The default is One Step.
Clock Class Profile Select the profile, which is relevant for
G.8265.1, PTP Enterprise-And-IEEE-1588-
2008, and G.8275.2 master clocks. The
default is G.8275.2.
N/A for AES67_MEDIA and SMPTE_ST_
2059_2.
Delay Mechanism Select the applicable mechanism. The
default is End to End.
Max Slaves Supported Enter the value. [maximum number of
dynamic slaves] + [maximum number of
static slaves]
Max Static Slaves Enter the applicable value.
Supported
Max Announce Message Select the appropriate rate. The default is 1
Rate packet per second.
The default for SMPTE_ST_2059_2 is 4
packets per second.
Max Sync Message Rate Select the appropriate rate. The default is
32 packets per second.
The default for AES67_MEDIA and SMPTE_
ST_2059_2 is 8 packets per second.
Max Delay Response Select the applicable delayed response
Message Rate rate. The default is 32 packets per second.
The default for AES67_MEDIA and SMPTE_
ST_2059_2 is 8 packets per second.
Max Lease Duration Enter the appropriate value from 60 to
1,000 seconds. The default is 300 seconds.
Announce Extension TLV When applicable, enable or disable the
Announce Extension TLV. This extension is
used when a Master clock is configured to
use the Enterprise profile.

3. After you set the master clock interface options, click OK.
4. In the tree pane, expand the boundary clock entity.
The master clock interface entity is displayed.
5. To verify the configuration details, click the master clock interface entity.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 248

Oscilloquartz: An ADVA Company Provisioning Operations

Creating a Master Virtual Port

You can create a master virtual port after you create a PTP flow point (see Creating a PTP
Flow Point) and Master Clock Interface (see Creating a Master Clock Interface).

To create or edit a master virtual port, right-click the master virtual port entity, such as
MASTER VIRTUAL PORT-1-1-1-1, and then select Edit. To delete a master virtual port, right-
click the master virtual port entity, and then select Delete.

To create or edit a master virtual port:

1. Right-click the master clock interface entity, and then select Create Master Virtual
Port. The Create Master Virtual Port window opens.

2. Set these master virtual port options:

a. In the Identification area, Master Virtual Port Index field, enter the applicable
value.
b. In the Identification area, Alias field, enter the applicable alias.
c. In the Configuration area, PTP Flow Point field, select the appropriate flow point.

For more information about the master virtual port parameter options,
see Master Virtual Port Parameter Options.

3. After you set the master virtual port options, click OK.
The master virtual port entity is displayed below the associated master clock interface
entity in the selection tree pane.
4. To view the configuration details, click the master virtual port entity.

Creating Layer 3 PTP Master Clock

To edit a master clock, right-click the master clock entity (such as MASTER CLOCK-1-1), and
select Edit. To delete a master clock, right-click the master clock entity, and select Delete.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 249

Oscilloquartz: An ADVA Company Provisioning Operations

The OSA 5422 supports the G.8275.2 profile only as a Grandmaster clock,
not as a Boundary clock.

This example configuration illustrates the provisioning procedure.

Figure 7: Example Grandmaster Clock and Dynamic Remote Slave in a G.8265.1 Topology

G.8265.1 GM Provisioning Slave Clock Provisioning

Master Clock l Telecom Slave TS-1-1
l PTP Profile= G.8265.1 l PTP Domain Number= 4
l PTP Domain Number= 4 l SOOC: Slave IP: 10.206.206.6, Subnet
Mask = 255.255.255.0
l Time Clock EID= TIME CLOCK-1-1-1-1-1
l MC IP: 10.206.206.1, Subnet Mask =
255.255.255.0
l MCI: IP 10.206.206.1, Subnet Mask =
255.255.255.0 l Unicast Message Negotiation=
Enabled
l ACC PTP Flow Point: Outer VLAN
EtherType=8100,
l NET PTP Flow Point: Outer VLAN
EtherType=8100, VLAN=206-7,
l VLAN=206-7, OC Master
l OC Slave
Time Clock l OCS Port to NET Port PTP Flow Point
TIMEREF-1-1-1-1-1, Priority 1, Source=
GPS-1-1-1-1

To create a Layer 3 Master Clock:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 250

Oscilloquartz: An ADVA Company Provisioning Operations

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System, right-click NE-1, and then select Create Master Clock.
The Create Master Clock window opens.

3. Set these master clock options:

For more information about the master clock parameter options, see Master Clock
Parameter Options.

Area Field Setting

Identification Master Clock Index Enter the value.
Alias Enter the alias.
Clock Identity Keep the hex number that the node
populates, or enter an applicable ID.
State Administrative Select IS for In Service.
Master Clock PTP Profile Select the required PTP profile.
Configuration PTP Domain Number Enter the PTP domain number. Valid values
are 0 to 255. The default depends on the
selected PTP profile.
Priority 1 Enter the appropriate value based on IEEE
1588v2.
Priority 2 Enter the appropriate value based on IEEE
1588v2.
Time Clock Eid Select the applicable ID.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 251

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

SMPTE System Frame Available when the selected PTP profile is
Rate Numerator SMPTE_ST_2059_2:
Sets the default video frame rate of the
slave system as a lowest term rational. The
data type is a pair of integer values coded in
big-endian form where the first is the
numerator.
Default is 24.
SMPTE System Frame Available when the selected PTP profile is
Rate Denumerator SMPTE_ST_2059_2:
Sets the default video frame rate of the
slave system as a lowest term rational. The
data type is a pair of integer values coded in
big-endian form where the second is the
denominator. The denominator is the
smallest value that represents the frame
rate denominator.
Default is 0.
SMPTE Time Address Available when the selected PTP profile is
Flags SMPTE_ST_2059_2:
Indicates the intended SMPTE ST 12-1 flags.

l Bit 0: Drop frame

o 0: Non-drop-frame

o 1: Drop-frame
l Bit 1: Color Frame Identification
o 0: Not in use

o 1: In use
l Bits 2-7: Reserved
Default is 0.

4. After you set the master clock options, click OK.

In the selection tree, the master clock entity displays below the network element entity.
5. To verify configuration details, click the master clock entity.
6. Create a Master Clock Interface (MCI), see Creating a Master Clock Interface.
7. Create a PTP flow point, see Creating a PTP Flow Point.
8. Create a master virtual port, see Creating a Master Virtual Port.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 252

Oscilloquartz: An ADVA Company Provisioning Operations

Creating G.8275.2 or G.8265.1 Static Remote Slave

First you create a master virtual port by creating a master clock interface. Then you can
create a static remote slave at the boundary clock or master clock node.

The number of static slaves that you can create depends on the Max Slaves Supported and
Max Static Slaves Supported settings that you specify when you create the master clock
interface, up to 4. If you set the applicable PTP-MC-BC-IP-UNICAST-Profile-<number of
remote slaves>-Remote-Slaves to enabled, the number of supported remote slaves will
depend on the number displayed in the name of the license.

To edit a static slave, right-click the static slave entity, such as STATIC SLAVE-1-1-1-1, and
then select Edit. To delete a static slave, right-click the static slave entity, and then select
Delete.

This example configuration illustrates the provisioning procedure.

Figure 8: Example Static Slave Clock in a G.8265.1 Topology

Telecom Slave TS-1-1 Provisioning

l PTP Domain Number= 4

l SOOC: Slave IP: 10.206.206.6, Subnet Mask = 255.255.255.0
l Master Clock IP: 10.206.206.1
l Unicast Message Negotiation= Enabled
l Access port PTP Flow Point: Outer VLAN EtherType=8100, VLAN=206-7, OC Slave
l OCS Port to Access port PTP Flow Point

To create a static remote slave:

1. In the toolbar, click the Precision Time Protocol (PTP) icon on the toolbar or from the
Application menu, select PTP.
2. In the selection tree, right-click the static slaves entity, and then select Create Static
Slave. The Create Static Remote Slave window opens, shown in this illustration. The
output changes depending on whether the slave clock is configured for an IPv4 or IPv6

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 253

Oscilloquartz: An ADVA Company Provisioning Operations

address. The example in the illustration is for an IPv4 Address.

3. Set these static remote slave options:

Area Field Setting

Identification Static Remote Slave Index Enter the index.
Alias Enter the alias.
State Administrative Select IS.
Configuration IPv4 Address Enter the address, which depends on the
master clock configuration of the static
remote slave.
IPv6 Address Enter the address, which depends on the
master clock configuration of the static
remote slave.
Unicast Message Select Enabled or Disabled. If you select
Negotiation Disabled, complete the settings in the
Message Rates area. Otherwise, these
settings are disabled.
Messages Rates Announce Message Rate Select the rate. The default is 1 Packet per
Note: Options Second.
are enabled
when Sync Message Rate Select the rate. The default is 32 Packets per
Configuration Second.
area, Unicast
Message
Negotiation Delay Response Message Select the rate. The default is 32 Packets per
field set to Rate Second.
Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 254

Oscilloquartz: An ADVA Company Provisioning Operations

IPv4 addresses cannot be zero or all ones (such as 255.255.255.255), or be

a subnet broadcast address, multicast address, or experimental subnet.

For more information about the static remote slave parameter options,
see Static Slave Parameter Options.

4. After you set the static remote slave options, click OK.
5. In the selection tree, click the static slaves entity that now displays a number within the
bracket to indicate the new static slave, for example Static Slave (1).
The Static Remote Slave Table is displayed with the new static slave listed. An example
is shown in this illustration.

6. To view the configuration details and status, click the Static Slave entity in the table.
The Configuration tab opens, shown in this illustration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 255

Oscilloquartz: An ADVA Company Provisioning Operations

7. To view receive and transmit statistics, complete these steps:

a. Click the Static Remote Table tab, and then right-click the static slave entity.
b. Select Statistics to open the Edit STATIC SLAVE tab, shown in this illustration.

If the statistics do not indicate the message receive and transmit statistics as
expected, troubleshoot connectivity and provisioning.

When the statistics update as expected, you can verify the static remote slave
connectivity.

Validating MCI Dynamic Remote Slave

To create a dynamic slave entity, you must first provision:

l A remote slave node with Unicast Message Negotiation Enabled, a dynamic slave.
l The master clock interface entity at the boundary clock or master clock node with
the correct number of Maximum Slaves Supported (where Maximum Slaves
Supported = <maximum number of Dynamic Slaves> + <maximum
number of Static Slaves>) to accept the Dynamic Slave unit.

You must also complete a set of prerequisite steps at the remote slave node if you want the
system to automatically create a dynamic slave. For these steps, see Prerequisite Steps.

The number of dynamic slaves that you can create depends on the Max Slaves Supported
entries completed when Creating a Master Clock Interface (up to 4). If the PTP-MC-BC-IP-
UNICAST-Profile-<number of remote slaves>-Remote-Slaves license is activated, the
number of remote slaves depends on the number of remote slaves displayed in the license
name.(max 1024).

After you create a dynamic remote slave, you can verify its connectivity (see Verifying a
Dynamic Remote Slave Connectivity).

To edit a dynamic slave, right-click the dynamic slave entity, such as DYNAMIC SLAVE-1-1-
1-1, and then select Edit. To delete a dynamic slave, right-click the dynamic slave entity, and
then select Delete.

For more information about the dynamic slave parameter options, see
Dynamic Slave Parameter Options.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 256

Oscilloquartz: An ADVA Company Provisioning Operations

This example configuration illustrates the provisioning procedure.

Figure 9: Example Dynamic Slave Clock in a G.8265.1 Topology

Telecom Slave TS-1-1 Provisioning

l PTP Domain Number= 4

l SOOC: Slave IP: 10.206.206.6, Subnet Mask = 255.255.255.0
o Master Clock IP: 10.206.206.1

o Unicast Message Negotiation= Enabled

l Access port PTP Flow Point: Outer VLAN EtherType=8100, VLAN=206-7, OC Slave
l OCS Port to Access port PTP Flow Point

Prerequisite Steps
Before the software can automatically create a G.8265.1 dynamic remote slave, first
complete these steps at the OSA 5422 remote slave node:

1. Ensure that a cable runs from the OSA 5422 to the Ethernet port associated with the
master clock or boundary clock node.
2. Activate the software license for the PTP feature (see Activating Software Licenses).
3. Provision the Ethernet port associated with the PTP flow point for the OCS port and set
this port to In Service (see Provisioning Access Ports).
4. Edit the Delay Assymmetry setting for the Ethernet port that is associated with the PTP
flow point (see Editing the Delay Asymmetry Setting of an Ethernet Port).
5. Create a Telecom slave (see Creating a Telecom Slave).
6. Provision the boundary clock or master clock node to accept this dynamic remote slave
(see Creating a Boundary Clock or Creating Layer 3 PTP Master Clock). When this static
remote slave operates with another type of node, such as an FSP 150, provision the
other node according to its documentation and verify connectivity.

Verifying a Dynamic Remote Slave Connectivity

Complete these steps to verify the connectivity of a dynamic remote slave at the OSA 5422
boundary clock or master clock site for the remote slave.

Prerequisites
Ensure that you create and verify the G.8265.1 static remote slave (see Validating
MCI Dynamic Remote Slave).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 257

Oscilloquartz: An ADVA Company Provisioning Operations

After you provision the remote slave as a dynamic slave and correctly provision the master
clock entity, the dynamic slave entity displays in the selection tree.

Complete these tasks to ensure that you correctly provisioned the dynamic remote slave
entity:

l Set the Unicast Message Negotiation of the dynamic remote slave to Enabled
(Dynamic Slave).
l Provision the master clock interface with the correct number of master slaves
supported to accept the dynamic slave ( where Maximum Slaves Supported =
the maximum number of Dynamic Slaves + the maximum number of
Static Slaves)
l Provision the master clock interface for the correct MAX PTP rates (Max Announce
Message Rate, Max Sync Message Rate, and Max Delay Response Message Rate).
l Provision the master clock interface for the correct IP Address and PTP Domain
Number.

To verify the static remote slave connectivity:

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the selection tree, next to the System>NE-1 entity, click +, and then navigate to the
dynamic slave. If the dynamic slave entity is not present as expected, troubleshoot
connectivity and provisioning.
3. To view the configuration details of the dynamic slave, click Dynamic Slaves or L2
Dynamic Slaves. The Dynamic Remote Slave table opens.
o The number of slaves refreshes once per minute in both the table and the

navigation pane.
o Click the Dynamic Slaves node to refresh the number of slaves if 15 seconds passed

from the last refresh.

o Double-click the Dynamic Slaves node to immediately refresh the number of slaves

in the table and the navigation pane.

o If the system is connected to a large number of slaves, the list may take up to 15

seconds to load.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 258

Oscilloquartz: An ADVA Company Provisioning Operations

4. Expand the remote slave node, and then click the OCS PORT entity to view the
configuration details and port state of the OCS port.
5. Wait until the Port Status changes to Slave.

6. To view the receive statistics of the SOOC entity, click the SOOC entity, and then open
the Statistics tab, as shown in this illustration.

If the output does not indicate message receive statistics as expected, troubleshoot
connectivity and provisioning.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 259

Oscilloquartz: An ADVA Company Provisioning Operations

Creating a PTP Clock

To edit a PTP clock, right-click the PTP clock entity, such as PTP CLOCK-1-1, and then select
Edit. To delete a PTP clock, right-click the PTP clock entity, and then select Delete.

This example configuration illustrates the provisioning procedure.

Figure 10: Example Grandmaster Clock and Dynamic Remote Slave in G.8275.1
Topology - No Backup

GM Provisioning Slave Clock Provisioning

Time Clock PTP Clock
TIMEREF-1-1-1-1-1, Priority 1, Source= PTP Clock Profile: G8275_1, Slave Only, PTP
GPS-1-1-1-1 Domain #= 24
PTP Clock PTP Port: NET PTP FLOWPT-1-1-1-1-1, ETH
Multicast
PTP Clock Profile: G8275_1, Clock Type=
Master Only, Dest Mac Addr Type: Forwardable

PTP Domain #= 24
PTP Port: ACC PTP FLOWPT-1-1-1-1-1,
ETH Multicast
Dest Mac Addr Type: Forwardable

To create a PTP clock:

1. Click (PTP) or from the Application menu, select PTP.

2. Expand System, right-click NE-1, and then select Create PTP Clock .

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 260

Oscilloquartz: An ADVA Company Provisioning Operations

The Create PTP Clock window opens.

3. Complete these PTP clock settings:

Area Field Setting

Identification PTP Clock Index Enter the index.
Alias Enter the alias.
Clock Identity Keep the hex number that the
node populates, or enter an
applicable ID.
State Administrative Select IS for In Service.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 261

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

PTP Clock PTP Clock Profile Select the required PTP profile.
Configuration Application Mode Available for G.8275.2,
Enterprise, and IEEE_1588_
2008_Annex_J3 profiles: PTS,
DOCSIS, or FTS.
PTP Clock Type Available only for G.8275.1
profile. Select the required
PTP clock type. For other
profiles, clock type is
automatically set.
PTP Domain Number Enter the applicable domain
number. Valid values are 0 to
255. The default depends on
the selected PTP profile.
Priority 1 Enter the applicable priority for
each field.
Priority 2
Not available for Enterprise
and IEEE_1588_2008_Annex_J3
Local Priority
profiles.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 262

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Sync Configuration Sync Reference Select Enabled or Disabled.

l When Enabled, the PTP

clock is available as a
possible reference for the
system synchronization
object.
l When Disabled, the PTP
clock is unavailable as a
possible reference for the
system synchronization
object (SYNC-1-1-1-1).
You can use the system
synchronization object to drive
PTP if this option is disabled
AND SYNC-1-1-1-1 is selected
in the Sync ID field.
Sync ID Select the clock
synchronization source. None
for Enterprise and IEEE_1588_
2008_Annex_J3 profiles.
QL Mode Select the applicable options
Assumed QL for these fields.

Expected QL
Received QL

For more information about PTP clock parameter options, see PTP Clock
Parameter Options.

4. After you set the PTP Clock options, click OK.

The PTP clock entity is displayed below the network element entity in the tree pane.
5. To verify configuration details, click the PTP clock entity.
You can now create a PTP flow point, see Creating a PTP Flow Point.

Verifying Remote Slave Connectivity

First create the PTP port. Then you can verify remote slave connectivity for a Layer 2
dynamic remote slave. The system shows Layer 2 dynamic remote slaves for PTP ports on a

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 263

Oscilloquartz: An ADVA Company Provisioning Operations

Master state with profiles that use end-to-end delay measurement.

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System >NE-1 > PTP Clock > PTP Port, and click L2
Dynamic Slaves. The Dynamic Remote Slave table opens.
View remote slaves in the table:
o The number of slaves refreshes once per minute in both the table and the

navigation pane.
o Click the Dynamic Slaves node to refresh the number of slaves if 15 seconds passed

from the last refresh.

o Double-click the Dynamic Slaves node to immediately refresh the number of slaves

in the table and the navigation pane.

o If the system is connected to a large number of slaves, the list may take up to 15

seconds to load.

Creating a Power Profile Grandmaster Clock

This section explains how to create a G.8275.1 grandmaster clock, which includes these
tasks:

To edit a PTP clock, right-click the PTP clock entity, such as PTP CLOCK-1-1, and then select
Edit. To delete a PTP clock, right-click the PTP clock entity, and then select Delete.

Figure 11: Example Grandmaster Clock in Substation Topology

Prerequisites
1. Ensure that a cable runs from OSA 5422 to the Ethernet ports associated with the
remote unit (master clock or remote slave).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 264

Oscilloquartz: An ADVA Company Provisioning Operations

2. Ensure that a GNSS is installed and cabled to OSA 5422.

3. Activate the PTP-Clock-Power-and-Utility-Profiles license (see Activating Software
Licenses).
4. Edit the access port that is associated with the PTP flow point for the PTP port, and place
it In Service (see Provisioning Access Ports).
5. Edit the Delay Asymmetry setting of an Ethernet port that is associated with the PTP flow
point for the PTP port (see Editing the Delay Asymmetry Setting of an Ethernet Port).
6. Edit the time clock and add the GNSS as the first priority reference. See Editing a Time
Clock, Adding a Time Clock Reference, and Provisioning the GNSS Receiver.
You can provision a second-priority time clock reference as a backup if the process loses
the first priority reference.

To create a power profile grandmaster clock:

1. Click the PTP, or from the Application menu, select PTP.

2. Expand System, right-click NE-1, and then select Create PTP Clock.
The Create PTP Clock window opens.

3. Complete these PTP clock settings:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 265

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Identification PTP Clock Enter the index.
Index
Alias Enter the alias.
Clock Identity Keep the hex number that the node populates, or
enter an applicable ID.
State Administrative Select IS for In Service.
PTP Clock PTP Clock Select the applicable profile:
Configuration Profile
l POWER_C37_238_2011
l POWER_C37_238_2017
l UTILITY_IEC_61580_9_3
PTP Clock Type Automatically set to Master.
PTP Domain Enter the applicable domain number.
Number
l POWER_C37_238_2011 and UTILITY_IEC_61580_9_3
default is 0.
l POWER_C37_238_2017 default is 254.
Priority 1 Enter the applicable priority for each field.
Priority 2
Local Priority
Grandmaster Enter the grandmaster ID that the ORGANIZATION_
Identity EXTENSION_TLV uses.
POWER_C37_238_2011 limits the range 0x0003 to
0x00FE.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 266

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Setting

Sync Sync Reference Select Enabled or Disabled.
Configuration
l If you select Enabled, the PTP clock is available as a

possible reference for the system synchronization

object.
l If you select Disabled, the PTP clock is unavailable
as a possible reference for the system
synchronization object (SYNC-1-1-1-1).
You can use the system synchronization object to
manage PTP if you set this option to Disabled AND
select SYNC-1-1-1-1 in the Sync ID field.
QL Mode Select the rate. The default is 32 packets per second.
Sync ID Select the clock synchronization source.
Assumed QL Select the applicable options.
Expected QL
Received QL

For more information about PTP clock parameter options, see PTP Clock
Parameter Options.

4. After you set the PTP Clock options, click OK.

The PTP clock entity is displayed below the network element entity in the tree pane.
5. To verify configuration details, click the PTP clock entity.
You can now create a PTP flow point (see Creating a PTP Flow Point).

Creating a PTP Flow Point

You can edit a PTPFP entity, for example, ACC PTP FLOW PT-1-1-1-1-1. Right-click the
entity, and then select Edit. To delete a PTPFP, right-click the PTPFP entity, and then select
Delete.

To create a PTP flow point:

1. In the tree pane, expand System > NE-1 > NTEOSA 5422.
2. Right-click the required network or access port and select Create PTPFP. The Create
PTP Flow Point window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 267

Oscilloquartz: An ADVA Company Provisioning Operations

3. Set these PTP flow point options:

For more information about the PTPFP parameter options, see PTP Flow Point Parameter
Options.

Area Name Field Name Setting

Identification PTPFP ID Enter the ID.
Alias Enter the alias.
AdminState Administrative Select the state.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 268

Oscilloquartz: An ADVA Company Provisioning Operations

Area Name Field Name Setting

Configuration PTP FlowPoint Select the appropriate type as either OC Slave,
Type OC Master, Monitoring, or Eth Multicast. The
default is OC Slave. The setting you select
depends on the requirements for your
configuration.

l To configure a Telecom slave, set this value

to OC slave.
l To configure a PTP flow point for a Layer 4
master clock interface, such as for a
boundary clock or a G.8265.1 or G.8275.2
grand master, set this value to OC Master.
l For a PTP clock or power profile
grandmaster clock, set this value to
Eth Multicast.
l For a G.8275.2 Slave clock, set this value to
L3.
Flow ID Select None.
COS Enter the applicable value. The default is 0.
CIR Enter the applicable value. The default depends
on the selected flow point type.
EIR Enter the applicable value. The default depends
on the selected flow point type.
Buffer Size Enter the applicable value in KB. The default
depends on the flow point type.
VLAN Configuration Untagged If you need to enter Inner and Outer VLAN tags,
clear this field.
Outer VLAN, Select the applicable VLAN fields for tag entry.
Inner VLAN1, Enter the applicable EtherTypes and VLAN tags.
Inner VLAN2 Note: The software uses a VLAN tag value of 0
for priority tagged frames. For proper
operation, use VLAN 0 as the last VLAN tag in
the VLAN stack.

4. After you set the PTP flow point options, click OK.
5. In the selection tree, expand the access port or access port entity that is associated with
the PTP flow point you just created.
A PTP FLOW PT element displays below the associated Ethernet port in the tree pane.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 269

Oscilloquartz: An ADVA Company Provisioning Operations

6. To view the configuration details, click the PTP FLOW PT entity, and open the
Configuration tab.

Creating a PTP Port

After you create a PTP clock and a PTP flowpoint, you can create a PTP port.

To edit a PTP port, right-click the PTP port entity (PTP PORT-1-1-1), and then select Edit. To
delete a PTP port, right-click the PTP port entity, and then select Delete.

To create a PTP port:

1. Right-click the PTP clock entity, and then select Create PTP Port.
The Create PTP Port window opens, shown in this illustration.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 270

Oscilloquartz: An ADVA Company Provisioning Operations

2. Complete these PTP port settings:

Area Field Name Setting
Identification PTP Port Index Enter the applicable index.
Alias Enter the applicable alias.
State Administrative Select IS for In Service.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 271

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Name Setting

PTP Clock Port Virtual Port Select Enabled to connect a virtual port
Configuration to a G.8275.1 boundary clock.
The virtual port is connected to the time
clock. The virtual port is part of the
PTP clock BMCA.
The default is Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 272

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Name Setting

Master Clock Type Select the applicable choice. The default
is One Step.
Note: When the port is configured to
10G, it is not possible to set Two Step for
a master clock configured to one of the
power profiles or for a GE-4S line card.
Local Priority Enter the applicable value. The default is
128.
PTP Flowpoint Select the applicable flow point.
Dest Mac Addr Type Select the applicable address type. The
default is Non Forwardable.
Not available for power profiles.
Probing Slave Select Enabled or Disabled to configure
a Layer 2 PTP clock probe monitoring a
third party G.8275.1 or Layer 2 master
port. The default is Disabled.
Not available for power profiles.
Delay Responder Type Available for power profiles only.
Select the applicable type: One Step or
Two Step.
Sync Message Rate Select the applicable synchronizing rate.
The default depends on the PTP profiles
of the parent PTP clock.
For power profiles set 1 Packet per
Second.
Delay Resp Message Rate Select the applicable rate. The default
depends on the PTP profiles of the parent
PTP clock.
Announce Message Rate Select the applicable rate. The default
depends on the PTP profiles of the parent
PTP clock.
For power profiles set 1 Packet per
Second.
Announce Receipt Enter the applicable timeout.
Timeout

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 273

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Name Setting

Sync Receipt Timeout Enter the applicable timeout.
Delay Resp Timeout Enter the applicable timeout.
Expected Clock Class Note: This value is only applicable for a
dynamic or slave port that is related to a
PTP clock, either a boundary clock or
slave clock. Otherwise, this field is not
applicable (N/A) and cannot be
configured.
Enter a value from 0 to 255 for the
maximum expected clock class. If the
received clock class is greater than the
expected clock class value, the packets
from the parent PTP port, which sends
this clock class, are dropped. In addition,
an alarm called ClockClassMismatch
is generated (see PTP Port Alarms). The
default is 247.
Asymmetry Delay Comp Select Automatic or Manual delay
Mode asymmetry compensation for
PTP G8275.1 boundary or slave clock.
Asymmetry Delay Comp When Asymmetry Delay Comp Mode is
Value set to Manual, specify the delay
asymmetry compensation in
nanoseconds. Valid values: -10,000,000 to
10,000,000. Default is 0.

For more information on the PTP Port parameter options, see PTP Port
Parameter Options.

3. After you finish setting the PTP port options, click OK.
The PTP Port node is created below the associated PTP clock.
4. To view the configuration details, click the PTP Port entity. Review the port status in the
Status area:
Time Traceable Status — indicates the status of the transmitted (for master clock) or
the received (for slave clock) time traceable flag.
Frequency Traceable Status — indicates the status of the transmitted (for master

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 274

Oscilloquartz: An ADVA Company Provisioning Operations

clock) or the received (for slave clock) frequency traceable flag.

Creating an L3 PTP Port

After you create a PTP clock with the G8275.2, Enterprise, or IEEE_1588_2008_Annex_J3
profiles and a PTP flow point, you can create a Layer 3 PTP port.

To edit a PTP port, right-click the PTP port entity, and then select Edit. To delete a PTP port,
right-click the PTP port entity, and then select Delete.

To create a Layer 3 PTP port:

1. Right-click the PTP clock entity, and then select Create PTP Port.
The Create L3 PTP Port window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 275

Oscilloquartz: An ADVA Company Provisioning Operations

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 276

Oscilloquartz: An ADVA Company Provisioning Operations

2. Complete these PTP port settings:

Area Field Name Setting
Identification PTP Port Index Enter the applicable index.
Alias Enter the applicable alias.
State Administrative Select IS for In Service.
Slave Configuration IP Protocol Select the applicable IP protocol.
Default is IPv4.
Default Gateway Select Enabled to activate IPv4 or IPv6
Control gateway address. Disabled by default.
(missing or bad snippet)
IPv4 Address Enter L3 PTP Port IP interface attributes.
IPv4 Subnet
Mask
IPv4 Gateway
Slave IPv6
Address
IPv6 Gateway
Interface Name Mandatory field. Enter the name of the
interface.
Expected Clock Enter a value from 0 to 255 for the maximum
Class expected clock class. If the received clock class
is greater than the expected clock class value,
the packets from the parent PTP port, which
sends this clock class, are dropped. In
addition, the ClockClassMismatch alarm is
raised (see PTP Port Alarms). The default is
247.
Unicast Message Select Enabled or Disabled.
Negotiation
Unicast Timeout Set the unicast timeout in seconds.
Valid values: 1 to 600 sed. The default is 1 sec.
Unicast Restart Set the unicast restart in seconds.
Timer Valid values: 30 to 1800 seconds. The default
is 60 sec.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 277

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Name Setting

Priority Mode Select the applicable value: None, TOS, DSCP.
The default is None.
Priority Set the priority for this port:
0
0-7 (TOS)
0-63 (DSCP)
Master Local Priority Enter the applicable value. The default is 128.
Configuration
Master IPv4 Enter the Master clock address.
Not available for
Address
Enterprise and IEEE_
1588_2008_Annex_ Master IPv6 Enter the Master clock address.
J3 profiles. Address

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 278

Oscilloquartz: An ADVA Company Provisioning Operations

Area Field Name Setting

PTP Configuration PTP Flowpoint Select the applicable flow point.
Announce Select the applicable rate.
Message Rate Default value for Enterprise profile is 1 pkt per
second.
Default value for IEEE_1588_2008_Annex_J3
profile is 1 pkt per 2 second.
Announce Enter the applicable timeout.
Receipt Timeout
Sync Message Select the applicable sync message rate.
Rate Default value for Enterprise and IEEE_1588_
2008_Annex_J3 profiles is 1 pkt per second.
Sync Enter the applicable timeout.
Receipt Timeout
Delay Resp Select the applicable rate. The default
Message Rate depends on the PTP profiles of the parent PTP
clock.
Default value for Enterprise and IEEE_1588_
2008_Annex_J3 profiles is 1 pkt per second.
Delay Resp Enter the applicable timeout.
Timeout
Lease Duration Enter the applicable duration in seconds.
Valid values: 60 to 1000 seconds. The default
is 300 sec.
Delay Assymetry Delay Asym Select Automatic or Manual delay
Compensation Comp Mode asymmetry compensation.

Delay Asym When Asymmetry Delay Comp Mode is set

Comp Value to Manual, specify the delay asymmetry
compensation in nanoseconds. Valid values: -
10,000,000 to 10,000,000. Default is 0.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 279

PTP Configuration Parameter Options
This section provides the details of the PTP configuration parameter options for these
topics:

Telecom Slave Parameter Options

This table provides details on the Telecom Salve parameter options available when creating
or editing a Telecom Slave. For more information on creating a Telecom Slave, see Creating
a Telecom Slave.

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Alias A text and/or number string the user up to 64 characters
enters to uniquely identify this entity. (blank)
This string can be up to 64 printable
ASCII characters long.
Clock Identity (Create Clock Identity of the Telecom Slave. (varies)
only) Entry is 16 HEX characters. A Clock
Identity is automatically created by the
system but this value can be edited.
Administrative State Enables or disables the Telecom Slave. IS
Management
PTP Domain Number This PTP domain number is used in the 0 — 255.
(Create only) domainNumber field of the PTP header The default depends
in the PTP packet. This PTP domain on the selected
number is used when PTP packet is profile.
generated by the SOOC.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 280

Oscilloquartz: An ADVA Company

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Time Holdover Accuracy Selects the time holdover accuracy in 500
(ns) (Create only) nanoseconds for the telecom slave. The
Holdover state is entered when Telecom
Slave is currently locked to the Master 1000
Clock and when the active SOOC’s OC-S
PTP Virtual Port goes to LISTENING or
UNCALIBRATED. In this state the phase 1500
lock can be sustained for certain amount
of time specified as Holdover time
5000
before the accuracy becomes insufficient
for holdover accuracy requirement. The
provisioned value and the assembled
10000
oscillator stability co-determine the
Holdover time.
WTR Time Wait to restore time. 0-15
5
Clock Recovery Mode Selects one way or two way clock One Way
(Create only) recovery mode.

l One way: delay request/response

messages are not used and in this
mode only frequency can be
recovered (only sync message) Two Way
l Two way (default): delay
request/response will be used and in
this mode frequency and/or
phase/time can be recovered

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 281

Oscilloquartz: An ADVA Company

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Sync Reference Enable or Disable allowing the Telecom Disabled
Slave to be used as Sync Reference.
Default is Disabled.

l If set to Enabled, the TS port is

available as a possible reference for
the system Sync object.
l If set to Disabled, the TS port is not
Enabled
available as a 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 use of QL when the telecom Disabled
slave serves as Syncjack or Time Clock
reference. Enabled

Sync ID Selects an external driver for PTP. If Sync None

Reference is set to Disabled AND SYNC-
1-1-1-x-1 is selected, then SYNC-1-1-x-1
is used to drive PTP. If Sync Reference is
set to Enabled, then only None is SYNC-1-1-x-1
applicable. Sync ID is not editable when
an SOOC is associated with the TS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 282

Oscilloquartz: An ADVA Company

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Assumed QL Assumed QL Specifies the assumed QL-NONE
Quality Level (QL) of the clock.

If the interface’s QL Mode is disabled,

the specified Assumed QL value is the
Quality Level of the clock. In this case,
Assumed QL can not be set to QL-
NONE. QL-PRC

If the clock QL Mode is enabled, the

specified Assumed QL value overrides
the received Quality Level unless
Assumed QL is set to QL-NONE.
QL-SSU-A
If the Network Clock Type is SONET
(Option2) and QL Mode is disabled, the
Assumed QL is automatically set to “QL-
STU” and is not editable.

If the Network Clock Type is changed

from SONET to SDH and QL Mode is QL-SSU-B
Disabled, the “Assumed QL” defaults to
“QL-EEC1.”

For both SDH and SONET options, if QL-

Mode = Enabled and the Network Clock
Type is changed, the Assumed QL
QL-EEC1
defaults to QL-NONE.

Valid entry for SDH Network Clock: QL-

NONE, QL-PRC, QL-SSU-A, QL-SSU-B,
QL-EEC1. Default is QL-EEC1 (QL Mode
= Disabled).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 283

Oscilloquartz: An ADVA Company

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Valid entry for SONET Network Clock: QL-EEC2
QL-NONE, QL-PRS, QL-STU, QL-ST2, QL- QL-PROV
TNC, QL-ST3E, QL-EEC2, QL-SMC, QL-
QL-PRS
PROV. Default: QL-STU (QL Mode =
Disabled) QL-SMC
QL-STU
QL-ST2
QL-ST3E
QL-TNC
Expected QL Specifies the expected Quality Level (QL) QL-NONE
when the clock is enabled for QL Mode.
This object is only applicable when QL
Mode is Enabled. This option allows the
user to set a minimum expected
QL-PRC
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. QL-SSU-A

Choices available depend on the

Network Clock Type setting - “option1 -
SDH” or “option2 - SONET.”
QL-SSU-B

The default value is QL-NONE. If the

Network Clock Type is changed,
Expected QL defaults to “QL-NONE”
regardless of previous setting. QL-EEC1
Valid entry for SDH Network Clock: QL-
PRC, QL-SSU-A, QL-SSU-B, QL-EEC1, QL-
NONE. Default is QL-NONE.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 284

Oscilloquartz: An ADVA Company

Table 9: Telecom Slave Parameter Options

Option Settings and
Parameter Description and Applicable Rules
Defaults
Valid entry for SONET Network Clock: QL-PRS
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL- QL-STU
ST3E, QL-EEC2, QL-SMC, QL-PROV, QL-
QL-ST2
NONE. Default is QL-NONE.
QL-TNC
QL-ST3E
QL-EEC2
QL-SMC
QL-PROV

Slave Only Ordinary Clock Parameter Options

This table provides details on the Slave Only Ordinary Clock (SOOC) parameter options
available when creating or editing a SOOC. You can only create a SOOC once a Telecom
Slave is created. A maximum of two SOOCs can be created per Telecom Slave. For more
information on creating a SOOC, see Creating a Slave-Only Ordinary Clock.

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
SOOC ID SOOC identifier (a maximum of 1-2
two SOOCs may be created per
Telecom Slave).
Alias A text and/or number string the up to 64 characters
user enters to uniquely identify (blank)
this entity. This string can be up
to 64 printable ASCII characters
long.
Administrati Enables or disables the Telecom IS
ve State Slave. See Entity State
Descriptions. Management

IP Protocol Defines the IP protocol as either IPv4

IPv4 or IPv6. IPv6

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 285

Oscilloquartz: An ADVA Company

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
Slave IPv4 Valid Slave IPv4 address. The IP 0.0.0.0
Address address must be unique across all
(Create IP interfaces in the system.
only)
Note: IPv4 addresses cannot be
zero or all ones (such as
255.255.255.255), and not a
subnet broadcast address,
multicast address, or
experimental subnet.
Slave Valid Slave IPv4 subnet mask. 0.0.0.0
Subnet
Mask
(Create
only)
Slave IPv6 Valid Slave IPv6 unicast address. 0000:0000:0000:0000:0000:0000:0000:
Address The IP address must be unique 0000/0
(Create only) across all IP interfaces in the
system. The range is between
2000::/3 (2000::0000 to
3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFF
F:FFFF).
Interface When an SOOC is created, an IP (blank)
Name interface is created with the
(Create Interface Name, IP Address and
only) Subnet Mask. The IP address and
Interface Name 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.
Unicast Enables or Disables Unicast Enabled
Message Message Negotiation.
Negotiation
(Create Disabled
only)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 286

Oscilloquartz: An ADVA Company

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
Expected Minimum expected clock class, 0-255
Clock Class which sets the minimum
247
threshold for receiving packets. If
the received clock class is greater
than the expected clock class
value, the packets for the
grandmaster or boundary clock
that are sending this clock class
are dropped. In addition, an alarm
called ClockClassMismatch is
generated (see SOOC Alarms).
Unicast Unicast timeout is user 1 sec
Timeout configurable. The range is 1 to
(1-600 seconds)
600 seconds. The default value is
1 second.
This is a read-write attribute and
will apply to next restart of
request unicast transmission
signaling messages.
Unicast Unicast restart timeout is user 60 sec
Restart configurable. The range is 30 to
(30 to 1800 seconds)
Timer 1800 seconds. The default value is
60 seconds.
This is a read-write attribute and
will apply to the next restart of
request unicast transmission
signaling messages.
Priority Defines the Priority Mode. It None
Mode identifies the lookup criteria for
the priority mapping table. This
TOS
table is used to perform priority
based lookup (to determine low
and normal latency) and/or to DSCP
change the priority value.
Priority Priority Map Index Selection. The 0
following ranges of Indexes are:
0-7 (TOS)
0...7 if Priority Mode is set to TOS;
0...63 if Priority Map Mode is set 0-63 (DSCP)
to DSCP.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 287

Oscilloquartz: An ADVA Company

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
Master Master Delay Mechanism. Only End-to-End
Delay End to End is supported.
Mechanism
(Create
only)
Master Master Priority. 0-255
Priority
Master Master Clock IPv4 address. 0.0.0.0
Clock IPv4
Address
(Create
only)
Master Master Clock IPv6 unicast address. 0000:0000:0000:0000:0000:0000:0000:00
Clock IPv6 The range is between 2000::/3 00
Address (2000::0000 to
(Create only) 3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFF
F:FFFF).
Master Master Announce Message Rate. 1 Packet Per 16 Seconds
Announce Defines the mean time interval 1 Packet Per 8 Seconds
Message between successive Announce
1 Packet Per 4 Seconds
Rate (Create messages.
only) 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 Master Announce Receipt 2-255 (secs)
Announce Timeout. Defines how long (in
Receipt seconds) for the GrandMaster to
Timeout send the announce packet.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 288

Oscilloquartz: An ADVA Company

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
Master Master Delay Response Message 1 Packet Per Second
Delay Rate. Defines a minimum mean 2 Packets Per Second
Response time interval in which the Master
4 Packets Per Second
Message Clock responds to successive
Rate (Create Delay Request packets. 8 Packets Per Second
only) 16 Packets Per Second
32 Packets Per Second
64 Packets Per Second
128 Packets Per Second
Master Master Delay Response Receipt 2-255 (secs)
Delay Timeout
128
Response
Receipt
Timeout
Master Sync Master Sync Message Rate. 1 Packet Per Second
Message Selects a mean time interval 2 Packets Per Second
Rate (Create between successive Sync
4 Packets Per Second
only) messages.
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
10
Timeout
Master Master Lease Duration 60 - 1000 (secs)
Lease
300
Duration
(Create
only)
E2E Enable or Disable End to End Automatic
Asymmetry Asymmetry Delay Compensation
Delay Comp Mode. If set to Automatic, the Disabled
Mode Time Clock must have GNSS
Manual
provisioned as a reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 289

Oscilloquartz: An ADVA Company

Table 10: SOOC Parameter Options

Description and Applicable
Parameter Option Settings and Defaults
Rules
E2E End to End Asymmetry Delay -100000000 to 100000000
Asymmetry Compensation in nsec. Applicable
0
Delay Comp if E2E Asymmetry Delay Comp
Mode is set to Manual.
Lockout Enable or Disable Lockout Enabled
Control Control. Enabling Lockout Control
places the SOOC into lockout. Disabled

PTP Flow Point Parameter Options

This table provides details on the PTP Flow Point (PTPFP) parameter options available when
creating or editing a PTPFP. For more information on creating a PTPFP, see Creating a PTP
Flow Point.

Table 11: PTP Flow Point Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
PTPFP ID PTP Flow point identifier. 1-33
(Create only)
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 Enables or disables the Transparent Clock. See IS
State Entity State Descriptions. Management

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 290

Oscilloquartz: An ADVA Company

Table 11: PTP Flow Point Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
PTP Flowpoint Defines the Flowpoint as either an OC Slave, OC OC Slave
Type (Create Master, Monitoring or Ethernet Multicast type.
Only)
l OC Slave is used when associated with an OCS
Port for a Slave Clock and monitoring the t3
[slave timestamp (locally)] or t1 [master
timestamp (remote)] of this PTP session is OC Master
desired.
l OC Master is used when configuring a Master
Clock Interface, have a remote slave, and
monitoring the t3 [slave timestamp(remote)] is
desired. Monitoring
l Monitoring is used when monitoring a PTP
session that works regardless of this OSA 5422
and the traffic is mirrored to the OSA 5422 - it
can monitor t3 (slave to master) or t1 (master to
slave). Eth Multicast
l PTP port of G.8275 profile uses Ethernet
Multicast addressing (selected as forwardable or
non-forwardable) for the transmission of all PTP
messages
COS Class Of Service. 0-7
CIR Committed Information Rate in bps. Minimum 0-1000000000
setting is 0 bps, maximum setting is port
The default
bandwidth.
depends on flow
point type.
EIR Excess Information Rate in bps. Minimum setting is 0-1000000000
0 bps, maximum setting is port bandwidth.
Buffer Size Buffer size in KB. Minimum setting is 0, maximum 0-15360
setting is 15360.
128
Untagged Defines whether the VLAN configuration is Selected
Check Box untagged or tagged. Selecting this option sets
(Create only) Untagged VLAN configuration. If PTP Flowpoint
Type is set to Eth Multicast then Untagged is Unselected
applied.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 291

Oscilloquartz: An ADVA Company

Table 11: PTP Flow Point Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Outer VLAN Defines whether the Outer VLAN tag is allowed. Selected
Check Box Only selectable if the Untagged check box is
(Create only) unselected. Unselected

Outer VLAN Defines the Ethertype for the Outer VLAN tag. 0
Ethertype
(Create only)
Outer VLAN Tag Defines the VLAN tag and priority that is associated 0 to 4095
(Create only) with this PTP Flow Point Outer VLAN Tag. 0 to 7
Inner VLAN1/2 Defines whether the Inner VLAN1/2 tag is allowed. Selected
Check Box Only selectable if the Untagged check box is
(Create only) unselected. Unselected

Inner VLAN1 Defines the Ethertype for the Inner VLAN1/2 tag. 0
Ethertype
(Create only)
Inner VLAN1/2 Defines the VLAN tag and priority that is associated 0 to 4095
Tag (Create with this PTP Flow Point Inner VLAN1/2 Tag.
only) 0 to 7

Ordinary Clock Slave Port Parameter Options

This table provides details on the Ordinary Clock Slave (OCS) Port parameter options
available when creating or editing a OCS Port. Once a PTP Flow Point has been created (see
Creating a PTP Flow Point), an Ordinary Clock Slave (OCS) Port can be created. For more
information on creating a OCS Port, see Creating an Ordinary Clock Slave Port.

Table 12: OCS Port Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
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.
PTP Flow Point PTP Flow Point Identifier to associate with this (drop down list of
(Create only) Ordinary Clock Slave Port. The Service Flow provisioned PTP
associated with Flow Point and SOOC must be the Flow Point IDs)
same.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 292

Oscilloquartz: An ADVA Company

Boundary Clock Parameter Options

This table provides details on the Boundary Clock parameter options available when
creating or editing a Boundary Clock. PTP-MC-BC-IP-UNICAST-Profile-<number of remote
slaves>-Remote-Slaves Software Licensing must be enabled prior to provisioning a
Boundary Clock. For more information on creating a Boundary Clock, see Creating a
Boundary Clock.

Table 13: Boundary Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Boundary Clock The index number of the Boundary Clock. One 1
Index (Create Boundary Clock may be created per system.
only)
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.
Use Selected Select the “Use Selected Telecom Slave Clock Selected
Telecom Slave Identity Check Box” to use the Clock Identity
Clock Identity proposed by the node. Leaving this box unselected
Check Box allows manual entry of a Telecom Slave Clock Unselected
(Create only) Identity.
Clock Identity Entry of a Clock Identity of the Telecom Slave is (varies)
(Create only) permitted if the “Use Selected Telecom Slave Clock
Identity Check Box” is not selected. Entry is 16 HEX
characters.
Administrative Enables or disables the Boundary Clock. See Entity IS
State State Descriptions. Management
Timing Source Selects the provisioned Telecom Slave timing (drop-down list of
(Create only) source. available timing
sources)
PTP Domain This PTP domain number is used in the domain 0-127
Number (Create Number field of the PTP header in the PTP packet.
0
only) This PTP domain number is used when PTP packet
is generated by the SOOC.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 293

Oscilloquartz: An ADVA Company

Master Clock Parameter Options

This table provides details on the Master Clock parameter options available when creating
or editing a Master Clock. The applicable software licenses must be enabled prior to
provisioning a Master Clock. For more information on creating a Master Clock, see Creating
Layer 3 PTP Master Clock and Creating a L3 PTP Multicast or Enterprise Profile Grandmaster
Clock.

Table 14: Master Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Master Clock The index number of the Master Clock. One Master 1
Index (Create Clock may be created per system.
only)
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.
Clock Identity The Master Clock’s Clock Identity. Entry is 16 HEX (varies)
(Create only) characters.
Administrative Sets the Administrative state, which enables or IS
disables the Master Clock. See Entity State
Descriptions. Management

PTP Profile Defines the PTP Profile by selecting the applicable G.8265.1
one. PTP_ENTERPRISE
(applicable for both
L3 PTP and
Enterprise profiles)
G.8275.2
PTP Domain This PTP domain number is used in the domain 0-127
Number (Create Number field of the PTP header in the PTP packet.
0
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 The timing reference of the Master Clock. Drop-down list of
Eid (Create only) available clock
sources.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 294

Oscilloquartz: An ADVA Company

Master Clock Interface Parameter Options

This table provides details on the Master Clock Interface (MCI) parameter options available
when creating or editing a MCI. PTP-MC-BC-IP-UNICAST-Profile-<number of remote
slaves>-Remote-Slaves Software Licensing must be enabled prior to provisioning an MCI.
For more information on creating a MCI, see .Creating a Master Clock Interface.

Table 15: Master Clock Interface Parameter Options

Parameter Description and Applicable Rules Option Settings and Defaults
Master Clock The index number of the Master 1-4
Interface Clock Interface. Up to Four Master
Index Clock Interfaces may be created per
(Create only) system.
Alias A text and/or number string the user up to 64 characters
enters to uniquely identify this entity. (blank)
This string can be up to 64 printable
ASCII characters long.
Administrati Enables or disables the Master Clock IS
ve State Interface. See Entity State
Descriptions on p. 81. Management

IP Protocol IP Protocol. IPv4

(Create only) IPv6
IPv6 Address Valid IPv6 unicast address. The IP 0000:0000:0000:0000:0000:0000:000
(Create only) address must be unique across all IP 0:0000 /0
interfaces in the system.
The IP address of
0000:0000:0000:0000:0000:0000:000
0: 0000/64 is reserved for default
routes. You can only enter the static
default route of
0000:0000:0000:0000:0000:0000:000
0:
0000 if the system default router is
0000:0000:0000:0000:0000:0000:0000
:0000. The range is between 2000::/3
(2000::0000 to
3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FF
FF).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 295

Oscilloquartz: An ADVA Company

Table 15: Master Clock Interface Parameter Options

Parameter Description and Applicable Rules Option Settings and Defaults
IPv4 Address Valid IPv4 address. The IP address 0.0.0.0
(Create only) must be unique across all IP
interfaces in the system.
Note: IPv4 addresses cannot be zero
or all ones (such as 255.255.255.255),
and not a subnet broadcast address,
multicast address, or experimental
subnet.
Subnet Mask Valid IPv4 subnet mask. 0.0.0.0
(Create only)
Interface When an Master Clock Interface is (blank)
Name created, an IP interface is created
(Create only) with the Interface Name, IP Address
and Subnet Mask. The IP address and
Interface Name 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 Defines the Priority Mode. It None
Mode identifies the lookup criteria for the
(Create only) priority mapping table. This table is
TOS (option disabled for IPv6)
used to perform priority based
lookup (to determine low and normal
latency) and/or to change the priority DSCP
value.
Priority Priority Map Index Selection. The 0
(Create only) ranges of Indexes are: 0...7 if Priority
0-7 (TOS)
Mode is set to TOS; 0...63 if Priority
Map Mode is set to DSCP. 0-63 (DSCP)
Clock Type Selects the Clock Type. One Step
(Create only) Two Step
Clock Class Defines the Clock Class Profile by G.8265.1
Profile selecting the desired profile. PTP-Enterprise-And- IEEE-1588-2008
(Create only) G.8275.2

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 296

Oscilloquartz: An ADVA Company

Table 15: Master Clock Interface Parameter Options

Parameter Description and Applicable Rules Option Settings and Defaults
Delay Selects the Delay Mechanism. Only End to End
Mechanism End to End is applicable in this
release.
(Create only)
Max Slaves Maximum Slaves Supported. This is 1-128
Supported the maximum number of Dynamic 1-256
Slaves + maximum number of Static
(Create only) 1-512
Slaves supported. The total number
available is dependent on the PTP- 1-1024
MC-BC-IP-UNICAST-Profile-
<number of remote slaves>-
Remote-Slaves Licensing Agreement
selected for the <number of remote
slaves>.
See Activating Software Licenses.
Max Static Maximum Static Slaves Supported 0-128
Slaves
0-256
Supported
(Create only) 0-512
0-1024
Max Maximum Announce Message Rate 1 Packet Per 16 Seconds
Announce 1 Packet Per 8 Seconds
Message
1 Packet Per 4 Seconds
Rate (Create
only) 1 Packet Per 2 Seconds
1 Packet Per 1 Second
Max Sync Maximum Sync Message Rate 1 Packet Per Second
Message 2 Packets Per Second
Rate (Create
4 Packets Per Second
only)
8 Packets Per Second
16 Packets Per Second
32 Packets Per Second
64 Packets Per Second
128 Packets Per Second

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 297

Oscilloquartz: An ADVA Company

Table 15: Master Clock Interface Parameter Options

Parameter Description and Applicable Rules Option Settings and Defaults
Max Delay Maximum Delay Response Message 1 Packet Per Second
Response Rate 2 Packets Per Second
Message
4 Packets Per Second
Rate (Create
only) 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
300
(Create only)
Announce When applicable, enable or disable Disabled (when configurable)
Extension the Announce Extension TLV. This N/A (when not configurable)
TLV extension may be used when a
Master Clock is configured to use the
Enterprise Profile and should be
disabled otherwise (for example,
when used as a L3 PTP multicast
profile). When this field is not
configurable, it is set to N/A.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 298

Oscilloquartz: An ADVA Company

Master Virtual Port Parameter Options

This table provides details on the Master Virtual Port parameter options available when
creating or editing a Master Virtual Port. Once a PTPFP has been created, a Master Virtual
Port can be created. For more information on creating a Master Virtual Port, see Creating a
Master Virtual Port.

Table 16: Master Virtual Port Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
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.
PTP Flow Point PTP Flow Point Identifier to associate with this (drop down list of
(Create only) Master Virtual Port. The Service Flow associated provisioned PTP
with Flow Point and Master Virtual Port must be the Flow Point IDs)
same.

Static Slave Parameter Options

This table provides details on the Static Remote Slave parameter options available when
creating or editing a Static Remote Slave. Once a Master Virtual Port has been created (by
creating a Master Clock Interface), a Static Remote Slave may be created at the Boundary
Clock/Master Clock node. For more information on creating a Static Remote Slave, see
Creating G.8275.2 or G.8265.1 Static Remote Slave.

Table 17: Create/Edit Static Slave Parameter Settings

Parameter Description and Applicable Rules Option Settings and Defaults
Static The index number of the Static Remote 1-4
Remote Slave.
(or 1-16)
Slave Index
(Create
only)
Alias A text and/or number string the user up to 64 characters
enters to uniquely identify this entity. (blank)
This string can be up to 64 printable
ASCII characters long.
Administrati Enables or disables the Static Remote IS
ve State Slave. See Entity State Descriptions. Management

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 299

Oscilloquartz: An ADVA Company

Table 17: Create/Edit Static Slave Parameter Settings

Parameter Description and Applicable Rules Option Settings and Defaults
Static Valid IPv4 address. The IP address 0.0.0.0
Remote must be unique across all IP interfaces
Slave IPv4 in the system.
Address
Note: IPv4 addresses cannot be zero
(Create only,
or all ones (such as 255.255.255.255),
if
and not a subnet broadcast address,
applicable)
multicast address, or experimental
subnet.
Static Valid IPv4 unicast address. The IP 0000:0000:0000:0000:0000:0000:000
Remote address must be unique across all IP 0:0000 /0
Slave IPv6 interfaces in the system. Valid IPv6
Address unicast address.
(Create only, The IP address of
is 0000:0000:0000:0000:0000:0000:0000:
applicable) 0000/64 is reserved for default routes.
You can only enter the static default
route of
0000:0000:0000:0000:0000:0000:0000:
0000 if the system default router is
0000:0000:0000:0000:0000:0000:0000:
0000.
The range is between 2000::/3
(2000::0000 to
3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFF
F).
Unicast Enables or Disables Unicast Message Enabled
Message Negotiation.
Negotiation
(Create Disabled
only)
Announce Announce Message Rate. (Applicable 1 Packet Per 16 Seconds
Message only if Unicast Message Negotiation is 1 Packet Per 8 Seconds
Rate (Create Disabled.)
only) 1 Packet Per 4 Seconds
Announce Message Rate cannot be
greater than the associated MCI Max 1 Packet Per 2 Seconds
Announce Message Rate. 1 Packet Per 1 Second

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 300

Oscilloquartz: An ADVA Company

Table 17: Create/Edit Static Slave Parameter Settings

Parameter Description and Applicable Rules Option Settings and Defaults
Sync Sync Message Rate. (Applicable only if 1 Packet Per Second
Message Unicast Message Negotiation is 2 Packets Per Second
Rate (Create Disabled.)
4 Packets Per Second
only)
Sync Message Rate cannot be greater 8 Packets Per Second
than the associated MCI Max Sync
Message Rate. 16 Packets Per Second
32 Packets Per Second
64 Packets Per Second
128 Packets Per Second
Delay Delay Response Message Rate. 1 Packet Per Second
Response (Applicable only if Unicast Message 2 Packets Per Second
Message Negotiation is Disabled.)
4 Packets Per Second
Rate (Create
Delay Response Message Rate cannot 8 Packets Per Second
only)
be greater than the associated MCI
Max Response Message Rate. 16 Packets Per Second
32 Packets Per Second
64 Packets Per Second
128 Packets Per Second

Dynamic Slave Parameter Options

This table provides details on the Dynamic Slave parameter options available when creating
or editing a Dynamic Slave. For more information on creating a Dynamic Slave, see
Validating MCI Dynamic Remote Slave.

Table 18: Dynamic Slave Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
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 Enables or disables the Static Remote Slave. See IS
State Entity State Descriptions. Management

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 301

Oscilloquartz: An ADVA Company

PTP Clock Parameter Options

This table provides details on the PTP Clock parameter options available when creating or
editing a PTP Clock. PTP-Clock-G-8275-1-and-IEEE-1588-2008-Annex-F-Profiles
Software Licensing must be enabled prior to provisioning a PTP Clock. For more information
on creating a PTP Clock, see Creating a PTP Clock and .

Table 19: PTP Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
PTP Clock Index The index number of the PTP Clock. 1
(Create only)
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.
Clock Identity The Master Clock’s Clock Identity. Entry is 16 HEX (varies)
(Create only) characters.
Administrative Enables or disables the PTP Clock. See Entity State IS
State Descriptions. Management
PTP Clock Defines the PTP Clock Profile. G8275_1
Profile IEEE_1588_2008_
ANNEX_F
POWER_C37_238_
2011
POWER_C37_238_
2017
UTILITY_IEC_61850_
9_3
G8275_2
PTP Clock Type Defines the G.8275 PTP Clock Type. For Remote Master Only
Slave, set to Master Only. For Master Clock node, Slave Only
set to Slave Only.
Static BC
Boundary Clock
PTP Domain This PTP domain number is used in the domain 0-127
Number (Create Number field of the PTP header in the PTP packet.
0
only)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 302

Oscilloquartz: An ADVA Company

Table 19: PTP Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Priority 1 Priority 1 (based on IEEE 1588v2). 0-255
128
Priority 2 Priority 2 (based on IEEE 1588v2). 0-255
128
Local Priority Defines the Local Priority. 0-255
128
Sync Reference Enable or Disable allowing the PTP Clock to be used Disabled
as Sync Reference. Default is Disabled.

l If set to Enabled, the PTP Clock is available as a

possible reference for the system Sync object.
l If set to Disabled, the PTP Clock is not available
as a possible reference for the system Sync Enabled
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 use of QL when the telecom slave serves Disabled
as Syncjack or Time Clock reference. Enabled
Sync ID Selects an external driver for PTP. If Sync Reference None
is set to Disabled AND SYNC-1-1-X-1 is selected,
then SYNC-1-1-X-1 is used to drive PTP. If Sync
Reference is set to Enabled, then only None is SYNC-1-1-X-1
applicable. Sync ID is not editable when an SOOC is
associated with the TS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 303

Oscilloquartz: An ADVA Company

Table 19: PTP Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Assumed QL Assumed QL Specifies the assumed Quality Level QL-NONE
(QL) of the clock.

If the interface’s QL Mode is disabled, the specified

Assumed QL value is the Quality Level of the clock.
In this case, Assumed QL can not be set to QL-
QL-PRC
NONE.

If the clock QL Mode is enabled, the specified

Assumed QL value overrides the received Quality
Level unless Assumed QL is set to QL-NONE.
QL-SSU-A
If the Network Clock Type is SONET (Option2) and
QL Mode is disabled, the Assumed QL is
automatically set to “QL-STU” and is not editable.

If the Network Clock Type is changed from SONET

QL-SSU-B
to SDH and QL Mode is Disabled, the “Assumed
QL” defaults to “QL-EEC1.”

For both SDH and SONET options, if QL-Mode =

Enabled and the Network Clock Type is changed,
the Assumed QL defaults to QL-NONE. QL-EEC1

Valid entry for SDH Network Clock: QL-NONE, QL-

PRC, QL-SSU-A, QL-SSU-B, QL-EEC1. Default is QL-
EEC1 (QL Mode = Disabled).
Valid entry for SONET Network Clock: QL-NONE, QL-EEC2
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL- QL-PROV
EEC2, QL-SMC, QL-PROV. Default: QL-STU (QL
QL-PRS
Mode = Disabled)
QL-SMC
QL-STU
QL-ST2
QL-ST3E
QL-TNC

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 304

Oscilloquartz: An ADVA Company

Table 19: PTP Clock Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Expected QL Specifies the expected Quality Level (QL) when the QL-NONE
clock is enabled for QL Mode. This object is only
applicable when QL Mode is Enabled. This option
allows the user to set a minimum expected received
Quality Level on the port. The valid values depend QL-PRC
upon the SYNC entity’s Network Clock Type. A
value of None represents that a minimum Quality
Level is not expected.
QL-SSU-A
Choices available depend on the Network Clock
Type setting - “option1 - SDH” or “option2 -
SONET.”
QL-SSU-B
The default value is QL-NONE. If the Network Clock
Type is changed, Expected QL defaults to “QL-
NONE” regardless of previous setting.
QL-EEC1
Valid entry for SDH Network Clock: QL-PRC, QL-
SSU-A, QL-SSU-B, QL-EEC1, QL-NONE. Default is
QL-NONE.
Valid entry for SONET Network Clock: QL-PRS, QL- QL-PRS
STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, QL-STU
QL-PROV, QL-NONE. Default is QL-NONE.
QL-ST2
QL-TNC
QL-ST3E
QL-EEC2
QL-SMC
QL-PROV

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 305

Oscilloquartz: An ADVA Company

PTP Port Parameter Options

This table provides details on the PTP Port parameter options available when creating or
editing a PTP Port. Once a PTP Clock and PTPFP are created, a PTP Port can be created. For
more information on creating a PTP Port, see Creating a PTP Port.

Table 20: PTP Port Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
PTP Port Index The index number of the PTP Port. 1
(Create only)
Alias A text and/or number string the user enters to up to 64 characters
uniquely identify this entity. This string can be up (blank)
to 64 printable ASCII characters long.
Administrative Defines the administrative state. Management
IS (In Service)
Master Clock Defines the type of Master Clock. One Step
Type Two Step
Local Priority Defines the Local Priority. 0-255
128
PTP Flow Point PTP Flow Point Identifier to associate with this PTP (drop down list of
(Create only) Port. provisioned PTP
Flow Point IDs)
Dest Mac Addr Destination MAC Address Type. Non Forwardable
Type Forwardable
Probing Slave Define whether the PTP port is a Probing Slave, Disabled
which is configured for L2 PTP Clock Probe
monitoring of a third party G.8275.1/L2 Master
port. This could be a port associated with a T-GM
or T-BC. The probing salve port can be created on
any type of PTP clock for up to 12 PTP ports of this
type. Enabled

Note: When this L2 PTP port is configured as a

slave and the probing slave mode is enabled, the
PTP port is not used as a slave port recovering the
clock, and is only used for monitoring.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 306

Oscilloquartz: An ADVA Company

Table 20: PTP Port Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Sync Message Synchronization Message Rate. 1 Packet Per Second
Rate (Create 2 Packets Per Second
only)
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 Req Delay Request Message Rate. 1 Packet Per Second
Message Rate 2 Packets Per Second
(Create only)
4 Packets Per Second
8 Packets Per Second
16 Packets Per
Second
32 Packets Per
Second
64 Packets Per
Second
128 Packets Per
Second

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 307

Oscilloquartz: An ADVA Company

Table 20: PTP Port Parameter Options

Option Settings
Parameter Description and Applicable Rules
and Defaults
Announce 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
2 Packets Per 1
Second
4 Packets Per 1
Second
8 Packets Per 1
Second
Announce Announce Receipt Timeout. 2-128 (secs)
Receipt
16
Timeout
Sync Receipt Sync Receipt Timeout. 2-128 (secs)
Timeout
32
Delay Resp Delay Response Timeout 2-128 (secs)
Timeout
32
Expected Clock Note: This value is only applicable for a dynamic or 0-255
Class slave port that is related to a PTP clock, either a 247
boundary clock or slave clock. Otherwise, this field
is not applicable (N/A) and cannot be configured.
Minimum expected clock class, which sets the
minimum threshold for receiving packets. If the
received clock class is greater than the expected
clock class value, the packets for the grandmaster
or boundary clock that are sending this clock class
are dropped. In addition, an alarm called
ClockClassMismatch is generated (see PTP
Port Alarms).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 308

 Chapter B

Provisioning Rules
This section provides provisioning rule information for the OSA 5422 and includes these
topics:

Factory Default Parameters and Maximum

Bandwidth
If you modify the OSA 5422 database, it stores the changes in non-volatile memory. If a
power loss or system reboot occurs, the database retains all configuration data. Three
versions of the database always reside on the system, plus a standby copy of the current
database. The three versions are

l The current running configuration.

l The system default, a copy that you can modify.
l The factory default, a copy that you cannot modify.

When you first commission your system after shipment from ADVA, these three database
versions are identical. As you provision your system, the process updates the current
running configuration database with each change.

See Table 21 for the Oscilloquartz: An ADVA Company factory default configuration
settings. Each functional area and default configuration settings are shown in the same
orderthat you see them in EMS. See Table 27 for access port maximum bandwidth, access
port maximum bandwidth, and default access port CIR/PIR values. For default TCA settings,
see TCA Monitored Types.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 309

Oscilloquartz: An ADVA Company

Table 21: System

Entity Parameter Default Settings
System CLI Prefix ADVA
Configuration Provisioning Mode Autoprov
Management Disabled
Traffic Bridging
Mgmt Traffic Disabled
Bridging Security
Proxy ARP Disabled
Date/Time (variable)
FTP Disabled
HTTP Enabled
HTTPS Enabled
SSL Cipher Low
Strength
SCP Enabled
Serial Port Enabled
Serial Port Auto Enabled
Log Off
SFTP Enabled
SSH Enabled
Telnet Disabled
Authentication Disabled
Traps
CLI Security Disabled
Prompt
SNMP Engine ID 12 Octets (variable)
Security Log Syslog Disabled
Alarm Log Syslog Disabled
Local Logging Enabled
Audit Log Syslog Disabled
Local Logging Enabled
Syslog Log Server 1, 2, 3 0.0.0.0
IP Address
Log Server 1, 2, 3 514
Port

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 310

Oscilloquartz: An ADVA Company

Table 21: System

Entity Parameter Default Settings
MGMT Access IP Version IPv4
Control List (ACL) IPv4 Address 0.0.0.0
(Entries 1-100)
Network Mask 255.255.255.255
Control Disabled
Banner Security Banner This is a private system. Unauthorized access or
use may lead to prosecution.
Time Zone UTC Offset +00:00
DST Control Disabled, which disables the rest of the
Enabled configuration settings.
NTP State Disabled
Polling Interval 16
(seconds)
Primary Server 0.0.0.0
Backup Server 0.0.0.0
Active Server Primary
IPv4 Traffic ACL IP Address 0.0.0.0
(Entries 1-100) Network Mask 255.255.255.255
Control Disabled
IPv6 Traffic ACL Address 0000:0000:0000:0000:0000:0000:0000:0000
(Entries 1-100) Prefix 64
Control Disabled
ICMPv4 Filter ICMPv4 Filter Disabled
Drop Echo Disabled
Requests
ICMPv6 Filter ICMPv6 Filter Disabled
Drop Echo Disabled
Requests
Drop Router Disabled
solicitation

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 311

Oscilloquartz: An ADVA Company

Table 21: System

Entity Parameter Default Settings
Drop Router Disabled
Advertisement
Drop Neighbor Disabled
Solicitation
Drop Neighbor Disabled
Advertisement

Table 22: NTE NE-1 NTEOSA 5422

Entity Parameter Default Settings
NE Configuration Name OSA 5422
(NE-1) Location (blank)
Contact (blank)
CLI Prefix NE-1
Administrative IS
State
PSU-1 to PSU-2 Alias (blank)
Administrative IS
State
NTEOSA 5422 Alias (blank)
Configuration Administrative IS
State
SNMP Dying Gasp Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 312

Oscilloquartz: An ADVA Company

Table 22: NTE NE-1 NTEOSA 5422

Entity Parameter Default Settings
E1000 Access port Alias (blank)
Facilities Administrative Management/Unassigned
State
(E1000-A-1/
Media Type Copper
E1000-A-2)
MTU Size 9612 (bytes)
Configured Speed Auto 1000 Full
MDIX Auto2
Auto Diagnostic Enabled
Drop Eligibility Enabled
Indicator
Port Shaping Disabled
Port Shaped Speed 0 (bps)
Q in Q Ethertype 88a8 (hex)
Q in Q Ethertype Disabled
Override
Sync-E Mode Disabled
QL-Mode Disabled
Assumed QL QL-EEC1
Expected QL QL-NONE

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 313

Oscilloquartz: An ADVA Company

Table 22: NTE NE-1 NTEOSA 5422

Entity Parameter Default Settings
Ethernet Access Alias (blank)
Port Facility Administrative Unassigned
State
(E1000-A-3/ Media Type Fiber, Copper SFP
E1000-A-10) MTU Size 9600
Configured Speed Copper = Auto,
Fiber = 100 Full
MDIX Auto
MDIX for Media Type copper. If Media Type is
fiber, MDIX is not applicable.
Auto Diagnostic Enabled
Port Mode CO (Connection-Oriented)
Service Type EPL
AFP AFP ALL
Q in Q Ethertype 8100 (hex)
Q in Q Ethertype Enabled
Override
Port Shaped Speed 0 (bps)
Sync-E Mode Disabled
QL-Mode Disabled
Assumed QL QL-EEC1
Expected QL QL-NONE
DCN (eth0) Alias (blank)
Administrative IS
State
Configured Speed Auto
MDIX Auto
PSU-1/PSU-2 Alias (blank)
Administrative IS
State

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 314

Oscilloquartz: An ADVA Company

Table 23: Synchronization

Entity Parameter Default Settings
SYNC-1-1-1- Alias (blank)
1 Administrative IS
State
Network Clock Option-1-SDH Regional Clock
Type
WTR Time 5 (minutes)
Selection Mode Priority Mode
Add/Edit/Delete (No Sync References Exist at System Default)
Sync Reference
BITS-1> Alias (blank)
BITS IN Administrative Unassigned
State
Line Type E1
Line Code E1 HDB3
Frame Format E1 CRC4
SA Bit Bit 4
QL Mode Disabled
Assumed QL QL-EEC1
Expected QL QL-NONE
BITS-1> Alias (blank)
BITS-OUT Administrative Unassigned
State
Line Type E1
Line Code E1 HDB3
Frame Format E1 CRC4
SA Bit Bit 4
QL Mode Disabled
Squelch QL QL-NONE
Line Build Out None

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 315

Oscilloquartz: An ADVA Company

Table 23: Synchronization

Entity Parameter Default Settings
CLK-1-1-1-1 Alias (blank)
(In) Administrative Unassigned
State
Signal Direction Input
Squelch Control Never
Squelch QL QL-NONE
Assumed QL QL-EEC1
CLK-1-1-1-2 Alias (blank)
Administrative Unassigned
State
Signal Direction Output
Squelch Control Never
Squelch QL QL-NONE
Assumed QL QL-EEC1
PPS-1-1-1-1 Alias (blank)
(In) Administrative Unassigned
State
Signal Direction Input
Squelch Control Lock
Input Rate Pulse Per Second
Delay 0
Compensation
PPS-1-1-1-2 Alias (blank)
Administrative Unassigned
State
Signal Direction Output
Squelch Control Never
Input Rate Pulse Per Second
Delay 0
Compensation

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 316

Oscilloquartz: An ADVA Company

Table 23: Synchronization

Entity Parameter Default Settings
TOD-1-1-1-1 Alias (blank)
& PPS Administrative Unassigned
Signal Direction Output
Input Rate Pulse Per Second
Cable Delay 0 (only relevant when Signal Direction is set to Input,
Compensation otherwise disabled)
Source Eid Defaults change according to Signal Direction
configured:
Input: GPS-1-1-1-1
Output: List of provisioned Clock Reference sources.
Squelch Control Never (only relevant when Signal Direction is set to
Output, otherwise disabled)
Output Format NMEA (only relevant when Signal Direction is set to
Output, otherwise disabled)
GNSS-1-1-1- Alias (blank)
1 Administrative Unassigned
State
PPS generation 1SAT
condition
Antenna Cable Measurement: 5 meters (default)
Length
Time:0 ns
GNSS System GPS Only
Types
Installation Type Full Sky View
C/No Mask 28 dB-Hz
Elevation Mask 10 degrees
PDOP Mask 6
Self Survey Period 86400 seconds
Sat Min1 3 satellites
Threshold
Sat Min2 2 satellites
Threshold

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 317

Oscilloquartz: An ADVA Company

Table 24: Communications

Entity Parameter Default Settings
DCN (eth0) IP Address 192.168.0.2
Net Mask 255.255.255.0
RIPv2 Disabled
DHCP Disabled
DHCP Role DHCP Client
DHCP Client ID Control Disabled
DHCP Client ID (System Name)
Edit System Default Gateway Not selected (Empty)
Gateway IP Address 192.168.0.0
Management Tunnels (None Created) (None Created)

Table 25: SNMP

Entity Parameter Default Settings
Communities Community Names public, private
Access Type read-only (public)
read-write (private)
Target Target Addresses (None Exist at System Defaults)
Addresses
Target Target Parameters (None Exist at System Defaults)
Parameters

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 318

Oscilloquartz: An ADVA Company

Table 25: SNMP

Entity Parameter Default Settings
USM Users SNMP User ADMIN
User Name ADMIN
Engine ID local
Security Name ADMIN
Security Level No Authentication
User Access Type Read/Write
Authentication None
Protocol
Privacy Protocol None
SNMP User MONITOR
User Name MONITOR
Engine ID local
Security Name MONITOR
Security Level No Authentication
User Access Type Read/Write
Authentication None
Protocol
Privacy Protocol None
SNMP User OPERATOR
User Name OPERATOR
Engine ID local
Security Name OPERATOR
Security Level No Authentication
User Access Type Read/Write
Authentication None
Protocol

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 319

Oscilloquartz: An ADVA Company

Table 25: SNMP

Entity Parameter Default Settings
USM Users Privacy Protocol None
SNMP User PROVISION
User Name PROVISION
Engine ID local
Security Name PROVISION
Security Level No Authentication
User Access Type Read/Write
Authentication None
Protocol
Privacy Protocol None
SNMP Dying SNMP Dying Gasp (no target addresses are provisioned, thus this option
Gasp is disabled)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 320

Oscilloquartz: An ADVA Company

Table 26: Administration

Entity Parameter Default Settings
Local Users Local User netadmin
User Name netadmin
Password ChgMeNOW
Privilege Provisioning
CLI Paging Enabled
Comment Default User
Login Timeout 15 (minutes)
Local User root
User Name root
Password ChgMeNOW
Privilege Superuser
CLI Paging Disabled
Comment Default User
Login Timeout 15 (minutes)
Local User user
User Name user
Password ChgMeNOW
Privilege Maintenance
CLI Paging Disabled
Comment Default User
Login Timeout 15 (minutes)
Remote Users No remote user entries are N/A
entered at default
Remote Authentication Protocol None
Authentication Authorization Type PAP
Access Order Local
TACACS Privilege Control Enabled
TACACS Default Privilege N/A
NAS IP Address 0.0.0.0
Accounting Disabled
Remote Authentication Servers Disabled
1-3

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 321

Oscilloquartz: An ADVA Company

Table 26: Administration

Entity Parameter Default Settings
Security Policy Policy Strength High
Key Generation: Edit SSL Country US
Certificate Data State Texas
Locality Richardson
Organization ADVA Optical Networking
Organization Unit Metro Ethernet Access
Name ADVA Optical Networking
Email [email protected]
Valid Until varies (yyyy-mm-dd)

Table 27: Maximum Access Port Bandwidth

Port Type Associated EID Max. CIR Max. EIR
E1000 (Fiber or Copper): ACCESS PORT-1-1-1-1 1000000000 (bps) 8000000000 (bps)
E1000 (Fiber Only): ACCESS PORT-1-1-1-2 1000000000 (bps) 8000000000 (bps)

All maximum values shown in the above table are indicative of a port
without a management tunnel, which utilizes a configurable amount of
bandwidth. At default configuration, no management tunnels are
provisioned.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 322

Oscilloquartz: An ADVA Company

System Configuration Options and Rules

The tables in this section provide information about the system configuration settings and
associated rules when you use EMS. Default settings are identified in bold.

l System Configuration Options and Rules

l Network Element (NE-1) Configuration: NE-1 Edit

System Configuration
Table 28: System Configuration: Edit System
Option
Parameter Description and Applicable Rules Settings and
Defaults
CLI Prefix When you use the CLI, this string is displayed at the ADVA
login prompt. This string can be up to 64 printable ASCII
characters, but cannot use the spacebar as a character.
Provisioning For OSA 5422, this feature has no effect on normal l Autoprov
Mode operation. The user should not modify the default l Autoprov
setting. Off
l Autoprov
Confirm
Management This option is used to enable the management traffic Enabled or
Traffic Bridging bridging feature. Disabled
When bridging is disabled, existing http, https, telnet,
and ssh sessions are unresponsive for up to 3 seconds.
When bridging is 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 those Enabled or
Bridging with an ADVA OUI in the source MAC Disabled
Security (00:80:EA:XX:XX:XX, 00:0B:90:XX:XX:XX, or
00:D0:8B:XX:XX:XX). This option is only available if
Management Traffic Bridging is enabled.
Note: the available MAC addresses within the valid
range have run out. We suggest not to use this option in
new deployments.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 323

Oscilloquartz: An ADVA Company

Table 28: System Configuration: Edit System

Option
Parameter Description and Applicable Rules Settings and
Defaults
Proxy ARP This option defines if the proxy ARP functionality should Enabled or
be enabled. If two or more OSA 5422 are connected via Disabled
Management Tunnel as well as connected to the same
LAN, then only one of the NEs/OSA 5422 should have
the PROXYARP option enabled. Otherwise, there will be
multiple ARP responses for a single ARP request for a
remote reachable IP Address.
Date/Time The date in format: yyyy-mm-dd and the time in format: varies
hh:mm:ss. If Unicast is selected for NTP Mode and an
NTP server has been linked, changing the date and time
is denied. If a date/time entered exceeds the
provisioned user GUI timeout value in respect to the
current system time, then the user session will time out.
System Time of Select the applicable system Time of Day mode: Local, NTP,
Day PTP CLock, Time
l Local: The system Time of Day is based on the local oscillator.

l NTP: The system Time of Day is updated based on an Clock

external NTP server.
l PTP Clock: The system Time of Day is updated based
on the Telecom Slave’s Time of Day. (PTP Clock is
only selectable when a Telecom Slave has been
provisioned.)
l Time Clock: The system Time of Day is updated
based on the provisioned Time Clock reference list.
Source TOD Selects the source TOD Clock. A drop-down list is None
Clock provided that contains all configured TOD clock sources. Configured,
TS-1-1, if provisioned, is available if PTP Clock is selected TS-1-1, TIME
for the System Time Of Day option. TIME CLOCK-1-1-1- CLOCK-1-1-1-1
1, if provisioned, is available if Time Clock is selected for
the System Time Of Day option.
FTP Enables or disables File Transfer Protocol access to the Enabled,
system. If enabled, the FTP client on the system can be Disabled
used for file transfer.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 324

Oscilloquartz: An ADVA Company

Table 28: System Configuration: Edit System

Option
Parameter Description and Applicable Rules Settings and
Defaults
HTTP Enables or disables Hypertext Transfer Protocol access Enabled,
to the system. If enabled, the user can access the GUI Disabled
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 access Enabled,
to the system. If enabled, the user can access the GUI Disabled
interface using HTTPS
SSL Cipher Sets the strength of the SSL cipher. Encryption strength Low, Medium,
Strength is measured in key length — number of bits in the key. High
To decipher an SSL communication, one needs to
generate the correct decoding key. Mathematically
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 the Enabled,
system. If enabled, SCP can be used for file transfer. Disabled
Serial Port Enables or disables RS-232 serial port access to the Enabled,
system. Disabled
Serial Port Auto If Enabled, causes Auto Logoff of the user session on the Enabled,
Log Off serial port, when the serial port is disconnected. Disabled
SFTP Enables or disables Secure File Transfer Protocol access Enabled,
to the system. If enabled, SFTP can be used for file Disabled
transfer.
SSH Enables or disables Secure Shell (TCP/UDP port 22) Enabled,
access to the system. If enabled, the user can access the Disabled
system through an SSH connection.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 325

Oscilloquartz: An ADVA Company

Table 28: System Configuration: Edit System

Option
Parameter Description and Applicable Rules Settings and
Defaults
Telnet Enables or disables Telnet (TCP port 23) access to the Enabled,
system. If enabled, the user can access the system Disabled
through a telnet connection. Note: Telnet is an unsecure
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 are sent to the Disabled
configured trap host.
Note: This setting excludes sending traps related to user
login or logout. To define settings related to the user
login or logout, see the Login/Logout Trap Control
setting.
Login/ Logout Select one of these options for configuring whether All, Failed,
Trap Control secured events SNMP traps are forwarded to a trap Disabled
host, such as the FSP Network Manager, whenever a
user logs in or out of the application:

l All: All login and logout timeout traps are sent.

l Failed Login: Only failed login traps are sent.
l Disabled: No traps related to user login or logout are
sent. This is the default option.

If enabled, SNMP Login/Logout traps are sent to the

configured trap host. See Configuring SNMP Traps
Forwarding for Login or Logout.
Enables or disables the following CLI security prompt:
CLI Security *****************************************
Enabled,
Prompt This is a private system. Unauthorized access or use Disabled
may lead to prosecution.
*****************************************
Do you wish to continue [Y|N]-->

SNMP Engine Allows the user to edit the SNMP Engine ID, which 0xhhhhhhhhhh
ID consists of 22 Hexadecimal characters. hhhhhhhhhhhh

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 326

Oscilloquartz: An ADVA Company

Table 29: System Configuration: Logs

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Security Log: Edit Security Log
Syslog Specify whether to send security related activity to the Syslog Enabled,
server. Disabled
Alarm Log: Edit Alarm Log
Syslog Specify whether to send alarm activity to the Syslog server. Enabled,
Disabled
Local Specify whether to send alarm messages to the local log. If set to Enabled,
Logging Enabled, you can view log on the Alarm Log tab. Disabled
Audit Log: Edit Audit Log
Syslog Specif whether to send logs of audit related activity to the Syslog Enabled,
server. Disabled
Local Specify whether to send audit messages to the local log. If set to Enabled,
Logging Enabled, you can view logs on the Audit Log tab. Disabled
Syslog: Edit Syslog
Time Stamp Select the specific time stamp format to use in the system log: ADVA,
Format RFC3164
l ADVA: Uses the format YYYY-MM-DD hh:mm:ssxxx:yy.
l RFC3164: Uses the format Mmm dd hh:mm:ss.
IP Address The Syslog server IP address. Enter an IP address to transmit 0.0.0.0
Log Server alarm information to a Syslog Server. You can configure up to
1-3 three Syslog servers. The log process sends all syslog messages
that the device generates to all configured Syslog servers. If you
set the IP address to 0.0.0.0, the system cannot use the Syslog
server.
Port The IP port of each registered Syslog server. The default port 514
Log Server number is 514.
1-3

Table 30: System Configuration: MGMT Access Control List

Option Settings and
Parameter Description and Applicable Rules
Defaults
Edit MGMT ACL for ACL ID 1 through 100

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 327

Oscilloquartz: An ADVA Company

Table 30: System Configuration: MGMT Access Control List

Option Settings and
Parameter Description and Applicable Rules
Defaults
IP Version Defines the type of IP address as either IPv4 or IPv6. IPv4, IPv6
Depending on your selection different options are
enabled or disabled.
IPv4 IPv4 address of the user/subnet allowed to access 0.0.0.0
Address OSA 5422. Up to 100 user/subnetwork IP addresses
can be entered (ACL ID 1-100). This option is only
enabled if the IP Version is set to IPv4.
Network The network mask for the user/subnet IPv4 address 255.255.255.255
Mask that can access the OSA 5422. You can enter up to
100 user/subnetwork IP addresses and network
mask combinations (ACL ID 1-100). This option is
enabled only if you set the IP Version to IPv4.
IPv6 IPv6 address of the user/subnet that can access 0000:0000:0000:0000:
Address OSA 5422. You can enter up to 100 0000:0000:0000:0 000
user/subnetwork IP addresses (ACL ID 1-100). This
option is enabled only if you set the IP Version is
set to IPv6.
The range is 2000::/3 (2000::0000 to
3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:
FFFF:FFFF).
Prefix Prefix for the user/subnet IPv6 address that can 64
access the OSA 5422. You can enter up to 100
user/subnetwork IP address and prefix
combinations can be entered (ACL ID 1-100). This
option is enabled only if you set the IP Version is set
to IPv6.
Control You can set each network IPv4 address-network Enabled, Disabled
mask-IPv6 address-prefix combination to Enabled
or Disabled. If you set an entry to Enabled, the
software applies this setting to every management
interface with ACL enabled.

Table 31: System Configuration: Security Banner

Option Settings and
Parameter Description and Applicable Rules
Defaults
Edit Banner

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 328

Oscilloquartz: An ADVA Company

Table 31: System Configuration: Security Banner

Option Settings and
Parameter Description and Applicable Rules
Defaults
Banner Defines a custom security banner, which is a text This is a private
string of up to 2000 characters. The banner system. Unauthorized
displays each time a user logs in to the system on access or use may lead
both the CLI and EMS. to prosecution.

Table 32: System Configuration: Time Zone

Option
Parameter Description and Applicable Rules Settings and
Defaults
Edit Time Zone
UTC Offset Coordinated Universal Time (UTC) offset value in hours and +00:00
minutes. The range is –12 to +14 : 00 to 59.
DST Control Daylight Saving Control. Enable for daylight saving use. Enabled or
Enabled Disabled
DST Start Daylight Saving Start Month. Effective only if you set DST March
Month Control Enabled to Enabled. The list provides months to
select.
DST Start Daylight Saving Start Day. Effective only if you set DST SUNDAY>=8
Day Control Enabled to Enabled. Entere as the day of the week in
all caps, day of month (1 to 31), or a logical function of both
(>=,<=).
DST Start Daylight Saving Start Time in hours and minutes using the 02:00
Time format hh:mm. Effective only if you set DST Control Enabled
to Enabled. The range is (00 to 23):(00 to 59).
DST Offset Daylight Saving Time Coordinated Universal Time (UTC) +01:00
Offset value in hours and minutes. Effective only if you DST
Control Enabled to Enabled. The range is (–12 to +14): 00 to
59.
DST End Daylight Saving End Month. Effective only if you set DST November
Month Control Enabled to Enabled. The list provides months to
select.
DST End Daylight Saving End Day. Effective only if you set DST SUNDAY<=7
Day Control Enabled to Enabled. Enter as the day of the week in
all caps, day of month (1 to 31), or a logical function of both
(>=,<=).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 329

Oscilloquartz: An ADVA Company

Table 32: System Configuration: Time Zone

Option
Parameter Description and Applicable Rules Settings and
Defaults
DST End Daylight Savings End Time in hours and minutes using the 02:00
Time format hh:mm. Only effective if DST Control Enabled is set
to Enabled. The range is between (00 to 23):(00 to 59).

Table 33: System Configuration: NTP

Option Settings and
Parameter Description and Applicable Rules
Defaults
Edit NTP
State Set the Network Time Protocol client to Enabled or Enabled or Disabled
Disabled. If you enable the NTP client, a Unicast
(point-to-point) request to a server IP address will
occur and expect a reply that indicates the time.
You can provision up to two IP addresses.
Primary Defines the type of IP address. Use to set the IPv4, 0.0.0.0
Server IPv4/IPv6 address of the primary NTP server.
or
Setting this address to
0.0.0.0/0000:0000:0000:0000:0000:0000:0000:0000 IPv6,
disables this server. This setting applies only if NTP 0000:0000:0000:0000:
state is enabled. 0000:0000:0000:0000
Note: IPv4 addresses cannot be zero or all ones,
such as 255.255.255.255, nor a subnet broadcast
address, multicast address, or experimental subnet.
Backup Defines the type of IP address. Use to set the IPv4, 0.0.0.0
Server IPv4/IPv6 address of the backup NTP server.
or
Setting this address to
0.0.0.0/0000:0000:0000:0000:0000:0000:0000:0000 IPv6,
disables this server. This setting applies only if NTP 0000:0000:0000:0000:
state is enabled. 0000:0000:0000:0000
Note: IPv4 addresses cannot be zero or all ones
such as 255.255.255.255, nor a subnet broadcast
address, multicast address, or experimental subnet.
Polling Set the NTP polling interval in seconds. Settings 16-1024
Interval can be 16 to 1024 seconds as powers of 2 (16, 32,
64, 128, 256, 512, 1024).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 330

Oscilloquartz: An ADVA Company

Table 33: System Configuration: NTP

Option Settings and
Parameter Description and Applicable Rules
Defaults
Active If you configure both the primary and backup Primary
Server server, the software configures IP sddresses. You Backup
can change between the servers using this setting.
Applies only if NTP state is enabled.

Table 34: System Configuration: IPv4 Traffic ACL

Option Settings
Parameter Description and Applicable Rules
and Defaults
IPv4 Traffic ACL: Edit Traffic for ACL ID 1 through 100
IP Address Defines the IPv4 address that contains the PTP/NTP 0.0.0.0
traffic, which you want to filter.
Network Defines the network mask for the IPv4 address, which 255.255.255.255
Mask contains the PTP/NTP traffic that you want to filter.
Control Defines whether this IP address definition is enabled or Enabled or
disabled in the system. Disabled

Table 35: System Configuration: IPv6 Traffic ACL

Parameter Description and Applicable Rules Option Settings and Defaults
IPv6 Traffic ACL: Edit IPv6 Traffic ACL for ACL ID 1 through 100
Note: IPv6 does not support NTP traffic.
Address Defines the IPv6 address that 0000:0000:0000:0000:0000:0000:
containsthe PTP traffic you want to 0000:0000
filter.

The range is 2000::/3 (2000::0000 to

3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:
FFFF:FFFF).
Prefix Defines the prefix for the IPv4 address, 64
which contains the PTP traffic that you
want to filter.
Control Defines whether this IP address Enabled or Disabled
definition is enabled or disabled in the
system.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 331

Oscilloquartz: An ADVA Company

Table 36: System Configuration: Edit ICMPv4 Filter

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
ICMPv4 Defines whether you can edit the ICMPv4 filter options. If set to Enabled
Filter enabled, you can also set the other filters. If set to disabled, you or
cannot change the filters. Disabled
Drop Echo Defines whether to accept or block echo requests for ICMPv4 Enabled
Requests packets. The default is configured to accept these packets or
because this filter is set to Disabled. To block echo requests, set Disabled
this filter to Enabled.
Drop Echo Defines whether to accept or block echo requests for ICMPv4 Enabled
Requests packets. The default is configured to accept these packets or
because this filter is set to Disabled. To block echo requests, set Disabled
this filter to Enabled.

Table 37: System Configuration: Edit ICMPv6 Filter

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
ICMPv6 Filter Defines whether you can edit the ICMPv6 filter options. If set to Enabled
enabled, you can set the other filters. If set to disabled, you or
cannot change the filters. Disabled
Drop Echo Defines whether to accept or block echo requests for ICMPv6 Enabled
Requests packets. The default is configured to accept these packets or
because this filter is set to Disabled. To block echo requests, Disabled
set this filter to Enabled.
Drop Router Defines whether to accept or block router solicitation requests Enabled
solicitation for ICMPv6 packets. The default is configured to accept these or
packets because this filter is set to Disabled. To block router Disabled
solicitation requests, set this filter to Enabled.
Drop Router Defines whether to accept or block router advertisement Enabled
Advertisement requests for ICMPv6 packets. The default is configured to or
accept these packets because this filter is set to Disabled. To Disabled
block router advertisement requests, set this filter to Enabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 332

Oscilloquartz: An ADVA Company

Table 37: System Configuration: Edit ICMPv6 Filter

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Drop Neighbor Defines whether to accept or block neighbor solicitation Enabled
Solicitation requests for ICMPv6 packets. The default is configured to or
accept these packets because this filter is set to Disabled. To Disabled
block neighbor solicitation requests, set this filter to Enabled.
Drop Neighbor Defines whether to accept or block neighbor advertisement Enabled
Advertisement requests for ICMPv6 packets. The default is configured to or
accept these packets because this filter is set to Disabled. To Disabled
block neighbor advertisement requests, set this filter to
Enabled.

Table 38: System Configuration: Edit Restore System Defaults

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Restore Use this setting to reset the NE back to system defaults. OK or
System Note: If you reset the NE to the system defaults, this might cause Cancel
Defaults the loss of all traffic, user data, and DCN communications settings.
Reset to system defaults only if you re-configure or relocate the
NE, or, as a last resort, if you troubleshoot traffic or
communications problems.

Network Element Configuration

Table 39: Network Element (NE-1) Configuration: NE-1 Edit
Option
Parameter Description and Applicable Rules Settings and
Defaults
Name A text string that contains a meaningful description of the up to 256
NE. The NE Name must start with a letter, end with a letter characters or
or digit, and have only letters, digits, and hyphens in Undefined
between. The maximum length is 256 characters.
Uppercase and lowercase characters are allowed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 333

Oscilloquartz: An ADVA Company

Table 39: Network Element (NE-1) Configuration: NE-1 Edit

Option
Parameter Description and Applicable Rules Settings and
Defaults
Location A text string entry that should specify where the system is up to 256
located with enough detail so that operations personnel characters or
can easily locate the device. Maximum length is 256 Undefined
characters.
Contact A text string entry that should specify the name and up to 256
contact information of the individual responsible for the characters or
administration of the system. Maximum length is 256 Undefined
characters.
CLI Prefix When you use the CLI and navigate to the NE level menu, Up to 64
this string is displayed. This string can be up to 64 characters or
printable ASCII characters long, but cannot use the space NE-1
character.
Administrative Defines the NE administrative state. IS is In Service and is IS or
State the default value. See Entity State Descriptions. Management

NTEOSA 5422 Configuration

Default settings are shown in bold text, if applicable.

Table 40: NTE Configuration: Power Supply Units PSU-1 to PSU-2, Edit
Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Enables or disables PSU-1 to PSU-2. Depending on your IS or
State network system configuration, you might want to Management
implement only one PSU, not both. For example, if you
intentionally do not install the second PSU and do not the
PSU to report alarms, set the Administrative state to
Management. See Entity State Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 334

Oscilloquartz: An ADVA Company

Table 41: NTEOSA 5422 Edit

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the OSA 5422 administrative state. See Entity State IS or
State Descriptions. Management

SNMP Dying Enables or disables a dying gasp message through SNMP. Enabled or
Gasp If enabled, the system sends OAM dying-gasp messages Disabled
on EFM-enabled interfaces.
SNMP dying gasp is supported only with IP management
tunnel and when the system management IP uses DCN0.

Table 42: GNSS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned or
Descriptions. IS
PPS generation The minimum number of satellites that need to be locked 1SAT or 3SATS
condition before the system can generate PPS output.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 335

Oscilloquartz: An ADVA Company

Table 42: GNSS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Antenna Cable Defines the delay that the cable introduces. This cable Measurement:
Delay connects the antenna to the GPS interface. The delay can 5 meters
be either a measurement in meters (default 5) or time in (default)
nanoseconds (default 0). The measurement is 0 to
Time: 0 ns
999999 meters. The time is –100000 to 100000
(default)
nanoseconds. For the best absolute PPS accuracy, adjust
the cable delay to match the installed cable length. Verify
with your cable manufacturer the delay for your specific
cable type. The length is set in meters. The cable delay
calculation assumes 4.5 nsec/meters.
Note: You can use this attribute for the compensation of
the delay that the GNSS Antenna Kit creates, which
includes cable delays, antenna delays, lightning protector
delays, and any other cable that might contribute to the
delay.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 336

Oscilloquartz: An ADVA Company

Table 42: GNSS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
GNSS System Defines the type of GNSS system in use. If you change GPS Only
Types the GNSS system types while the GPS 1-1-1-1 is In
GLONASS Only
Service, performance can be affected. Because the
different GNSS system types sometimes share different GPS and
time references, changing between them can impact the GLONASS
time clock. If one of these transitions occurs, the system
BEIDOU and
automatically executes a cold reset of the GNSS receiver:
GPS
l GPS only to GLONASS only
BEIDOU Only
l GPS only to GALILEO only
GALILEO Only
l GPS only to BEIDOU only
l GPS only to GALILEO and GPS GALILEO and
GPS
In these cases, the GNSS survey restarts.
Note: To minimize the impact of modifying the
GNSS system types, we recommend that you complete
these steps:

1. Manually enable the Lock out of the Time Clock

Reference before the configuration change.
2. After the GNSS receiver is stable, clear the Lock out.
Typically, the receiver is stable after 1 hour or at the
end of the survey period, if the survery was
reinitialized.
Installation Defines the GNSS antenna installation scenario: Full Sky Full Sky View
Type View, where C/No Mask is 35 and Elevation Mask is 20 or Limited Sky
degrees. Or Limited Sky View, where C/No Mask is 0 and View
Elevation Mask is 0 degrees.
C/No Mask Defines the quality of received GNSS satellite-signals, 35 dB-Hz
which the software reports as a Carrier-to-Noise (C/No)
power ratio. Use this mask to instruct the receiver to
exclude satellites with a particular C/No. The value can be
0 to 55 dB-Hz with a default of 35 db-Hz. Low C/No
values can result from low-elevation satellites, which are
partially obscured signals that occur because of dense
foliage for example, or reflected RF signals such as in a
multipath.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 337

Oscilloquartz: An ADVA Company

Table 42: GNSS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Elevation Mask Defines the elevation mask in degrees, where the range is 20 degrees
between 0 to 90 degrees. Generally, signals from low-
elevation satellites are of poorer quality than signals from
higher elevation satellites. These signals travel farther
through the ionospheric and tropospheric layers and
undergo distortion due to these atmospheric conditions.
This mask enables excluding satellites with poor elevation
from being used by the receiver. For example, an
elevation mask of 10° excludes very low satellites from
position fix computations and reduces the likelihood of
potential errors induced by using those signals.
PDOP Mask Defines the Position Dilution of Precision (PDOP) Mask 6
value, where PDOP is a measure of the error caused by
the geometric relationship of the satellites used in the
position solution, and is used to measure the current
satellite geometry. This mask can be used to exclude a
position calculated based on poor PDOP to be used
during location survey. The range is between 2 to 12. It
takes into account each satellite’s location relative to the
other satellites in the constellation. Satellite sets that are
tightly clustered or aligned in the sky have a high PDOP
and contribute to lower position accuracy.
Note: PDOP is applicable only during self-survey or
whenever the receiver is performing position fixes. The
PDOP Mask displays Not Available after the GNSS
receiver terminates self-survey mode.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 338

Oscilloquartz: An ADVA Company

Table 42: GNSS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Self Survey Defines the Self Survey Period, which is used to specify 86400 seconds
Period the number of position fixes that are to be averaged
together to form the self-surveyed position. The range is
between 1-500,000 seconds. For applications that require
a high level of time accuracy, it is recommended to use a
long position survey time, such as one day (average of
86400 values).
Note: While the position is calculated during the self-
survey period, the timing performance of the device is
not yet optimal. Therefore, we recommend waiting until
the self-survey period is completed before starting any
measurements of the timing outputs, such as PPS and
PTP.
Sat Min1 Defines the first minimum (Min1) number of in use 3 satellites
Threshold satellite thresholds. The range is between 1-32 satellites.
Sat Min2 Defines the second minimum (Min2) number of in use 2 satellites
Threshold satellite thresholds. The Sat Min2 Threshold must be
less than the Sat Min1 Threshold, and cannot be set
before the Sat Min1 Threshold is defined. The range is
between 1-32 satellites. The Sat Min1 Threshold and
Sat Min1 Threshold numbers are used to determine
which alarm is asserted (or cleared) if a number of in-use
GNSS satellites is below or above thresholds according to
these conditions:

l When the number of valid satellites observed by the

receiver is less than equal to the Sat Min2 Threshold,
the Sat Min2 Threshold alarm is asserted.
l When the Sat Min2 Threshold is less than the
number of valid satellites observed by the receiver,
and the number of satellites is less than the Sat Min1
Threshold, the Sat Min1 Threshold alarm is asserted.
l When the Sat Min1 Threshold is less than equal to
the number of valid satellites observed by the
receiver, no alarm is asserted.

Access Ports
See Access Port Configuration Options and Rules.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 339

Oscilloquartz: An ADVA Company

Table 43: Access Ports: DCN (eth0): Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. or Undefined

Administrative Enables or disables the Data Communications Network. IS,

State See Entity State Descriptions. Management,
or Unassigned
Configured Defines the line rate of the port and its mode, either half Auto
Speed 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 medium-dependent interface crossover Auto
(MDIX) function for copper interfaces. The interface uses Crossed
MDIX to change cable signal assignments in order to
compensate for the use of an incorrect cable type. Uncrossed

Table 44: Access Ports: BITS 1 — BITS IN: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the SYNC administrative state. See Entity State Unassigned
State Descriptions. If you set the administration state to IS
Unassigned, BITS do not display as a potential
synchronization reference. Management

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 340

Oscilloquartz: An ADVA Company

Table 44: Access Ports: BITS 1 — BITS IN: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Line Type Sets the BITS line type. If the applicagle BITS Line Type is: EI

l I2048 kHz, set the Network Clock Type to Option 1. T1

l T1, set the Network Clock Type to Option 2. 2048 kHz

The software will detect AIS or LOF at the BITS interface

endpoints if you provision mismatches of the device
Network Clock Type and the device line-type. Before you
configure other BITS IN options, set the Line Type.
Line Code Sets the BITS line code. If you set the Line Type to: E1 HDB3

l E1, the available options are E1 HDB3 and E1 AMI. E1 AMI

l T1, the available options are T1 B8ZS and T1 AMI. T1 B8ZS
l 2048 kHz, this option does not apply.
T1 AMI
Frame Format Sets the BITS Frame Format. If you set the Line Type to: E1 Unframed

l E1, the available options are E1 Unframed, E1 CRC4, E1 CRC4

and E1 DualFrame. E1 DualFrame
l T1, the available options are T1 SuperFrame and T1
T1
Extended- SuperFrame.
SuperFrame
l 2048 kHz, this option does not apply.
T1 Extended-
SuperFrame
SA Bit Select the Signalling Associated (SA) Bit. SA Bit applies None
only if you set the Line Type to E1. Bit 4

Bit 5
Bit 6
Bit 7
Bit 8
QL Mode Set the quality level mode. If you set the Line Type to Enabled or
2048 kHz, this option does not apply. Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 341

Oscilloquartz: An ADVA Company

Table 44: Access Ports: BITS 1 — BITS IN: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Assumed QL l If you set the interface QL Mode to disabled, the QL-NONE
specified Assumed QL value is the quality level of the QL-PRC
interface. You cannot set the Assumed QL to QL-
QL-SSU-A
NONE.
l If you set the interface QL Mode to enabled, the QL-SSU-B
specified Assumed QL value overrides the received QL-EEC1
quality level of the interface unless Assumed QL is set
to QL-NONE. QL-EEC2
l If the Network Clock Type is SONET (Option2) and QL QL-PROV
Mode is disabled, the Assumed QL is automatically set QL-PRS
to QL-STU. You cannot edit this setting.
QL-SMC
l If you change the Network Clock Type from SONET to
SDH, and QL Mode is Disabled, the Assumed QL QL-STU
defaults to QL-EEC1.
QL-ST2
l For both SDH and SONET options, if QL-Mode is
QL-ST3E
Enabled and you change the Network Clock Type, the
Assumed QL defaults to QL-NONE. QL-TNC
l Valid entries for the SDH Network Clock are: QL-NONE,
QL-PRC, QL-SSU-A, QL-SSU-B, QL-EEC1. The default is
QL-EEC1, QL Mode Disabled.
l Valid entries for the SONET Network Clock: QL-NONE,
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2,
QL-SMC, QL-PROV. The default is QL-STU, QL Mode
Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 342

Oscilloquartz: An ADVA Company

Table 44: Access Ports: BITS 1 — BITS IN: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Expected QL Set the Expected Quality Level. If Line Type is set to 2048 QL-NONE
kHz, this option does not apply.
QL-PRC
l A valid entry for SDH Network Clock is: QL-NONE, QL- QL-SSU-A
PRC, L-SSU-A, QL-SSU-B, QL-EEC1. Default is QL-
NONE. QL-SSU-B
l A valid entry for SONET Network Clock is: QL-NONE, QL-EEC1
QL-PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2,
QL-EEC2
QL-SMC, QL-PROV.
QL-PROV
l The default is: QL-NONE.
QL-PRS
QL-SMC
QL-STU
QL-ST2
QL-ST3E
QL-TNC

Table 45: Access Ports: BITS 1 — BITS OUT: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned
State Descriptions. If you set the administrative state to IS
unassigned, the entity does not display as a potential
synchronization reference. Management

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 343

Oscilloquartz: An ADVA Company

Table 45: Access Ports: BITS 1 — BITS OUT: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Line Type Sets the BITS line type. If you want to set the BITS line type E1
to
T1
l 2048kHz or E1, set the Network Clock Type to Option 2048 kHz
1.
l T1, set Network Clock Type to Option 2.

The system will detect AIS or LOF at the BITS interface

endpoints if you provision mismatches of the device
Network Clock Type and the device line-type. Set the Line
Type before you configure other BITS OUT options.
Line Code Sets the BITS line code. If you set the Line Type to: E1 HDB3

l E1, the options available are E1 HDB3 and E1 AMI. E1 AMI

l T1, the options available are T1 B8ZS and T1 AMI. T1 B8ZS
l 2048 kHz, this option does not apply.
T1 AMI
Frame Format Sets the BITS frame format. If you set the Line Type to: E1 Unframed

l E1, the available options are E1 Unframed, E1 CRC4, E1 CRC4

and E1 DualFrame. E1 DualFrame
l T1, the options are T1 SuperFrame and T1
T1
Extendeavailable d- SuperFrame.
SuperFrame
l 2048 kHz, this option does not apply.
T1 Extended-
SuperFrame
SA Bit Select the Signalling Associated (SA) Bit. The SA Bit applies None
only 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 you set the line type to Enabled or
2048 kHz, this option does not apply. Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 344

Oscilloquartz: An ADVA Company

Table 45: Access Ports: BITS 1 — BITS OUT: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Squelch QL Sets the Squelch quality level. Use the Squelch QL attribute QL-NONE
to define the minimum QL that the system timing can QL-PRC
accept. If the system timing QL falls below this selected
value, the software turns off the BITS-OUT and the QL-SSU-A
interface provides no BITS-OUT signal. QL-SSU-B
QL-EEC1
QL-DNU
Line Build Out Option to set impedance for cable length or dB. Applies 0-133 ft
only if Line Type is T1. 133-266 ft
266-339 ft
339-533 ft
533-655 ft
7.5 dB
15 dB
22.5 dB

Table 46: Access Ports: CLK-1-1-1-1 and CLK-1-1-1-2 : Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned
State Descriptions. If you set the administrative state to IS
unassigned, the entity does not display as a potential Management
synchronization reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 345

Oscilloquartz: An ADVA Company

Table 46: Access Ports: CLK-1-1-1-1 and CLK-1-1-1-2 : Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Signal Defines the signal direction for this interface. Options are Input
Direction Input or Output. CLK-1-1-1-1 is input only, and Signal
Output
(PPS-1-1-1-2) Direction is unavailable.
For a CLK-X16 line card: if the Signal Direction of CLK-1-1-
1-2 is Input, you cannot create a clk16port group.
Squelch If you configure the CLK timing interfaces as outputs, you Never
Control must establish a hierarchy:
Holdover
l NEVER, if the system never squelches the output. Lock
l HOLDOVER, if the system squelches the output only in
Squelch QL
freerun state.
l LOCK, if the system squelches the output in holdover
and freerun states
l Squelch QL, if the system squelches the output based
only on the Squelch quality level.

Note: This setting does not apply to CLK-1-1-1-1 which is

input only, or if you configure CLK-1-1-1-2 as input.
Squelch QL Sets the Squelch quality level. Use the Squelch QL attribute QL-NONE
to define the minimum QL that the system timing can QL-PRC
accept. If the system timing QL falls below this selected
value, the system turns off the interface, and the interface QL-SSU-A
provides no output signal. Squelch QL does not apply to QL-SSU-B
interfaces that you configure as input or when you set
QL-EEC1
Squelch Control to Never.
QL-DNU
Assumed QL Set the Assumed quality level. If you configure the CLK QL-PRC
interface as Input, you can select an assumed QL level. QL-SSU-A
QL-SSU-B
QL-EEC1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 346

Oscilloquartz: An ADVA Company

Table 47: Access Ports: PPS-1-1-1-1: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned
State Descriptions. If you set the administrative state to IS
unassigned, the entity does not display as a potential Management
synchronization reference.
Signal Defines the signal direction for this interface. Options are Input
Direction Input or Output. PPS-1-1-1-1 is input only, and Signal
Output
for PPS-1-1-1- Direction is unavailable.
2 Note: For a PPS-X16 line card: If the Signal Direction of
PPS-1-1-1-2 is Input, you cannot create a pps16port
group.
Squelch If you configure PPS timing interfaces as outputs, you Never
Control must establish this hierarchy for squelch control: Holdover
Lock
l NEVER, the system never squelches the output.
l HOLDOVER, the system squelches theoutput only in a
freerun state.
l LOCK, the system squelches the output in holdover and
freerun states.

This setting does not apply to PPS-1-1-1-1, which is input

only, or if you configure PPS-1-1-1-2 as input.
Input Rate Defines the input rate. Applies if you set the signal Puse Per
direction to Input. Selcond
Pulse Per 2
Seconds
Cable Delay Cable Delay Compensation in ns. –100000000
Compensation to 100000000
(ns) 0
Source Eid Defines the source EID to provide as a PPS output when Select from
you set the signal direction to Output. the Clock
Reference
sources list

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 347

Oscilloquartz: An ADVA Company

Table 48: Access Ports: TOD-1-1-1-1 & PPS: Edit Configuration

Option Settings and
Parameter Description and Applicable Rules
Defaults
Alias A text or number string, or combination, that up to 64 characters
you enter to uniquely identify this entity. This Unassigned
string can be up to 64 printable ASCII characters
long.
Administrative Defines the administrative state. See Entity State Unassigned or IS
Descriptions.
Signal Defines the signal direction for this interface. Input or Output
Direction Options are Input or Output.
Input Rate Defines the input rate. Applies when you set the Pulse Per Second
Signal Direction to Input.
Cable Delay If you configure the ToD & PPS port as input, 0 ns
Compensation this value defines the delay compensation. The
time is
–100000 to 100000 nanoseconds.
Source Eid Defines the source EID to provide as a ToD Defaults change
+PPS input or output, depending on the according to the
defined Signal Direction. configured Signal
Direction:
Input: GPS-1-1-1-1. The
source of the ToD is
GPS/GNSS, not the
serial ToD.
Output: List of
Provisioned Clock
Reference sources.
Squelch A hierarchy to establish for Squelch control of Never
Control the TOD & PPS timing interface. The hierarchy is
Holdover
relevant only if you set Signal Direction to
Output: Lock

l NEVER, where the output is never squelched.

l HOLDOVER, where output is squelched only
in freerun state.
l LOCK, where output is squelched in
holdover and freerun states.
Output Format TOD & PPS port output format. NMEA
CCSA

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 348

Oscilloquartz: An ADVA Company

Table 49: Power Supply Units PSU-1 and PSU-2: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to Up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Administrative Enables or disables PSU-1 and PSU-2. Depending on your IS or
State network system configuration, you might want to Management
implement only 1 PSU. For example, if you intentionally do
not install a second PSU and you do not want the PSU to
report alarms, set the Administrative state to
Management. See Entity State Descriptions.

Table 50: Line Card LC1 or LC2: Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long.A text and/or number Undefined
string the user enters to uniquely identify this entity. This
string can be up to 64 printable ASCII characters long.
Administrative Enables or disables LC-1 and LC-2. See Entity State IS
State Descriptions. Management
Card Type Selects the line card type. BITS-X16
(Create Only) PPS-X16
l For PPS-X16: If the PPS-1-1-1-2 signal direction is set
to Input, you cannot create a pps16port group. CLK-X16
l For CLK-X16: If the CLK-1-1-1-2 signal direction is set
TOD-PPS-X16
to Input, you cannot create a clk16port group.
IRIG-B
LPN/ULPN

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 349

Oscilloquartz: An ADVA Company

Table 51: Group1 (1 to 8) or Group2 (9 to 16): Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you up to 64
enter to uniquely identify this entity. This string can characters
be up to 64 printable ASCII characters long. Undefined
Administrative State Enables or disables the selected group. See Entity IS or
State Descriptions. Management
Line Type (BITS-X16) Determines the Line Type for the Group. The settings T1, E1, or
for BITS-1 determine the available options. 2048 kHz

Line Impedance Selects the Line Impedance. The settings for BITS-1 120 Ohm
(BITS-X16) determine the available options. 75 Ohm
Cable Delay Sets the Cable Delay Compensation in ns. 0 to 9999999
Compensation (ns)
for TOD-PPS-X16,
PPS-X16

Synchronization
Default settings are shown in bold text, if applicable.

Table 52: NE-1 NTE OSA 5422Sync-1-1-1-1: Edit Synchronization

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 350

Oscilloquartz: An ADVA Company

Table 52: NE-1 NTE OSA 5422Sync-1-1-1-1: Edit Synchronization

Option
Parameter Description and Applicable Rules Settings and
Defaults
Administrative Defines the SYNC administrative state. See Entity State IS
State Descriptions. Management
Network Clock Defines the network clock type. If the appropriate Option 1-
Type BITS Line Type is SDH
Regional
l 2048kHz or E1, set the Network Clock Type to Option Clock
1.
l T1, set the Network Clock Type to Option 2.

The software will detect AIS or LOF at the BITS interface

endpoints if you provision mismatches of the device
Network Clock Type and the device line-type.
WTR Time Time delay in minutes from the recovery of a clock source Option 2-
to its restoration as usable in an active state. SONET
Regional
Clock
WTR Time Time delay in minutes from the recovery of a clock source 0 to 12
to its restoration as usable in an active state. 5
Selection Defines the method to use for selecting the active Priority
Mode reference source. Mode
QL Mode
Clock PLL Defines the type of tracking filter. EEC
Bandwidth SSU

Table 53: NE-1 NTE OSA 5422Sync-1-1-1-1: Add Sync Reference

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Note: Before you add a Sync Reference, you must first configure a valid Sync Reference
source with Sync reference set to Enabled and In Service.
SYNCREF Unique identifier of a sync reference entity. The software 1 to 2
Index automatically indexes the Syncref Index as a sync reference and 1
provides a list of available indexes that you can select.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 351

Oscilloquartz: An ADVA Company

Table 53: NE-1 NTE OSA 5422Sync-1-1-1-1: Add Sync Reference

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Priority Sets the priority for a sync reference. If you set the Selection 1 to 10
Mode to Priority Mode, the software uses this setting to 1
determine the sync reference hierarchy.
Sync To display a list of provisioned services, you must first List of
Reference configure the sources for Sync-E operation. These sources must provisioned
Sources be in the proper admin state. The sources include the access Sync
port, which includes line card ports, Time Clock, Telecom Slave, Reference
PTP Clock, CLK-IN, or BITS-IN. Sync-E does not support Copper
sources
SFPs.
If you configure the access port as a 1000Base-T electrical
interface, you must set it to Auto 1000 Full Slave to add it to the
list of Sync Reference sources. You must also configure the
access port as Auto 1000 Full Master to use this port as a Sync-
E Master to a remote node.

Table 54: NE-1 NTE OSA 5422Sync-1-1-1-1: Edit Sync Reference

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Select Ref If you add BITS-IN, CLK-IN, Time Clock, Telecom Slave, or an List of
access port as Sync References, you can select these from the provisioned
list of provisioned references and edit their Priority or Alias Sync
settings. Reference
sources
Priority If you select a Sync Ref Eid, you can select a new Priority. 1 to 10
Alias If you select a Sync Ref EID, you can edit the text or number up to 64
string, or a combination, to uniquely identify this entity. This characters
string can be up to 64 printable ASCII characters.
Undefined

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 352

Oscilloquartz: An ADVA Company

Table 55: NE-1 NTE OSA 5422Sync-1-1-1-1: SYNC-1-1-1-1: Delete Sync Reference
Option
Parameter Description and Applicable Rules Settings and
Defaults
Select Ref If you add an access port, Time Clock, Telecom Slave, CLK- List of
IN, or BITS-IN as a Sync Reference source, you can select it provisioned
and then delete it from the list. Sync Reference
sources

Table 56: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Edit Time Clock
Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter up to 64
to uniquely identify this entity. This string can be up to characters or
64 printable ASCII characters long. Undefined
Administrative Defines the time clock administrative state. See Entity IS or
State State Descriptions. Management
WTR Time Time delay in minutes from the recovery of a clock 0 to 12
source to its restoration as usable in an active state. 5
Selection Mode Defines what method to use for selecting the active Priority Mode
reference source.
Time Holdover Configure this value in nanoseconds to determine when 0, 100, 500,
Performance (ns) the system should change from Holdover to Freerun 1000, 1500,
clock mode. When the device time-error estimation 5000, 10000,
exceeds the configured value, the time clock changes NA
from Holdover to Freerun.

If you select 0, the system immediately changes to

Freerun and omits the Holdover mode.
If you select NA for not applicable, and a frequency
reference is available to the time clock, this frequency is
traceable to PRC/PRS. The time clock stays in Holdover
mode. For example, the send clock class 7, time, and
frequency flags are set to true. For any other situation, if
no frequency reference is available or the frequency
reference available is not PRC/PRS, the time clock
changes to Freerun mode.
Sync Ref Enable or disable a Sync Reference Candidate. Enabled or
Candidate Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 353

Oscilloquartz: An ADVA Company

Table 56: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Edit Time Clock
Option
Parameter Description and Applicable Rules Settings and
Defaults
Expected QL Set the Expected Quality Level. If Line Type is set to QL-NONE, QL-
2048 kHz, this option does not apply. PRC, QL-SSU,
QL-SSUB, QL-
EEC1
Time Scale Set the Time Scale as either: PTP, ARB
l PTP: This is the default setting. The TimeClock epoch
is based on the TimeClock reference, the GNSS, PTP
slave, and PPS+ToD input.
l ARB: The TimeClock epoch drives the system ToD
with a maximum error of 300 seconds. If you specify
this setting, the system locks to the reference, which
is not traceable to the TAI (SYNC-1-1-1-1).
e-PRTC Mode Select Enabled or Disabled. If you set this field to Enabled or
enabled, the time clock combines the stable frequency Disabled
input, such as a Cesium Clock, to extend the holdover
capability to meet the e-PRTC holdover standards.
Before you configure this setting, ensure that you
activate the e-PRTC license (see Activating Software
Licenses).
Note: This setting applies only to Rb/HQ++ oscillators.

Table 57: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Add Time Clock
Option
Settings
Parameter Description and Applicable Rules
and
Defaults
TimeREF Time reference index. 1 to 2
Index
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 354

Oscilloquartz: An ADVA Company

Table 57: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Add Time Clock
Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Priority Se the priority for this Time Clock Reference. The time 1 to 10
traceable reference will have the highest internal priority. If
two references have the same time or frequency traceable, the
system uses the prority that you configure.
Time Clock Select the Time Clock Reference Source. List of
Reference provisioned
Sources Time Clock
Reference
sources

Table 58: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Edit Time Clock Reference
Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Select Ref Select the corresponding Time Clock Reference that you want Select the
field to edit. field
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Priority Sets the priority for this Time Clock Reference. 1 to 10

Table 59: NE-1 NTE OSA 5422 Time Clock-1-1-1-1: Delete Time Clock Reference
Option Settings and
Parameter Description and Applicable Rules
Defaults
Select Ref Select the corresponding Time Clock Reference that Select the field.
field you want to delete.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 355

Oscilloquartz: An ADVA Company

Table 60: NE-1 NTE OSA 5422 BITS-1 BITS-IN: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned,
State Descriptions. If you set the administrative state to IS, or
unassigned, the entity does not display as a potential Management
synchronization reference.
Line Type Sets the BITS line type. If the appropriate BITS Line Type is E1, T1,
2048 kHz
l 2048kHz or E1, set the Network Clock Type to Option 1.

l T1, set the Network Clock Type to Option 2.

The system will detect AIS or LOF at the BITS interface

endpoints if you provision mismatches of the device
Network Clock Type and the device line-type. Before you
configure any other BITS IN options, specify the Line Type.
Line Code Sets the BITS line code. If you set Line Type to: E1 HDB3, E1
AMI, T1 B8ZS,
l E1, the available options are E1 HDB3 and E1 AMI.
T1 AMI,
l T1, the available options are T1 B8ZS and T1 AMI.
l 2048 kHz, this option does not apply.
Frame Format Sets the BITS Frame Format. If you set the Line Type to: E1 Unframed,
E1 CRC4, E1
l E1, the available options are E1 Unframed, E1 CRC4. DualFrame,
and E1 DualFrame. T1
l T1, then the available options are T1 SuperFrame and SuperFrame,
T1 Extended- SuperFrame. T1 Extended-
l 2048 kHz, this option does not apply. SuperFrame

SA Bit Select the Signalling Associated (SA) Bit. SA Bit applies only None, Bit 4,
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 2048 kHz, Enabled or
this option does not apply. Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 356

Oscilloquartz: An ADVA Company

Table 60: NE-1 NTE OSA 5422 BITS-1 BITS-IN: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Assumed QL l If the interface QL Mode is disabled, the specified QL-NONE,
Assumed QL value is the Quality Level of the interface. QL-PRC, QL-
In this case, you cannot set the Assumed QL to QL- SSU-A, QL-
SSU-B, QL-
NONE.
EEC1
l If the interface QL Mode is enabled, the specified
Assumed QL value overrides the received Quality Level
of the interface, unless Assumed QL is set to QL-NONE.
l If the Network Clock Type is SONET (Option2) and QL
Mode is disabled, the software automatically sets the
Assumed QL set to QL-STU. And, you cannot edit this
setting.
l If you change the Network Clock Type from SONET to
SDH and QL Mode is Disabled, the Assumed QL setting
defaults to QL-EEC1.
l For both SDH and SONET options, if QL-Mode is
Enabled and you change the the Network Clock Type,
the Assumed QL defaults to QL-NONE.
l Valid entries for SDH Network Clock: QL-NONE, QL-
PRC, QL-SSU-A, QL-SSU-B, QL-EEC1. The default is QL-
EEC1, QL Mode Disabled.

Valid entries for SONET Network Clock: QL-NONE, QL-PRS, QL-EEC2,

QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, QL- QL-PROV,
PROV. The default is QL-STU, QL Mode Disabled. QL-PRS,
QL-SMC,
QL-STU,
QL-ST2,
QL-ST3E,
QL-TNC
Expected QL Sets the Expected Quality Level. If Line Type is set to QL-NONE,
2048 kHz, this option does not apply. QL-PRC,
QL-SSU-A,
Valid entries for SDH Network Clock: QL-NONE, QL-PRC, QL-SSU-B,
QL-SSU-A, QL-SSU-B, QL-EEC1. The default is QL-NONE. QL-EEC1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 357

Oscilloquartz: An ADVA Company

Table 60: NE-1 NTE OSA 5422 BITS-1 BITS-IN: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Valid entries for SONET Network Clock: QL-NONE, QL-PRS, QL-EEC2,
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, QL- QL-PROV,
PROV. The default is QL-NONE. QL-PRS,
QL-SMC,
QL-STU,
QL-ST2,
QL-ST3E,
QL-TNC
Assumed QL l If the interface QL Mode is disabled, the specified QL-NONE,
Assumed QL value is the Quality Level of the interface. QL-PRC,
In this case, you cannot set the Assumed QL to QL- QL-SSU-A,
NONE. QL-SSU-B,
l If the interface QL Mode is enabled, the specified QL-EEC1
Assumed QL value overrides the received Quality Level
of the interface, unless Assumed QL is set to QL-NONE.
l If the Network Clock Type is SONET (Option2) and QL
Mode is disabled, the software automatically sets the
Assumed QL to QL-STU. And you cannot edit this
setting.
l If you change the Network Clock Type from SONET to
SDH and QL Mode is Disabled, the Assumed QLdefaults
to QL-EEC1
l For both SDH and SONET options, if QL-Mode is
Enabled and you change the Network Clock Type, the
Assumed QL defaults to QL-NONE.
l Valid entries for SDH Network Clock: QL-NONE, QL-
PRC, QL-SSU-A, QL-SSU-B, QL-EEC1. The default is QL-
EEC1, QL Mode Disabled.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 358

Oscilloquartz: An ADVA Company

Table 60: NE-1 NTE OSA 5422 BITS-1 BITS-IN: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Valid entries for SONET Network Clock: QL-NONE, QL-PRS, QL-EEC2,
QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-SMC, QL- QL-PROV,
PROV. The default is QL-STU, QL Mode Disabled. QL-PRS,
QL-SMC,
QL-STU,
QL-ST2,
QL-ST3E,
QL-TNC
Expected QL Sets the Expected quality level. If Line Type is set to 2048 QL-EEC2
kHz, this option does not apply. QL-PROV
QL-PRS
Valid entries for SDH Network Clock: QL-NONE, QL-PRC, QL-SMC
QL-SSU-A, QL-SSU-B, QL-EEC1. The default is QL-NONE. QL-STU
QL-ST2
Valid entries for SONET Network Clock: QL-NONE, QL-
QL-ST3E
PRS, QL-STU, QL-ST2, QL-TNC, QL-ST3E, QL-EEC2, QL-
QL-TNC
SMC, QL-PROV. The default is QL-NONE.

Table 61: NE-1 NTE OSA 5422 BITS-1 BITS-OUT: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter up to 64
to uniquely identify this entity. This string can be up to characters or
64 printable ASCII characters long. Undefined
Administrative Defines the SYNC administrative state. See Entity State Unassigned,
State Descriptions. BITS will not show up as a potential IS, or
synchronization reference if the administration state is Management
set to Unassigned.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 359

Oscilloquartz: An ADVA Company

Table 61: NE-1 NTE OSA 5422 BITS-1 BITS-OUT: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Line Type Sets the BITS line type. If the applicable BITS Line Type is E1, T1, or
2048 kHz
l 2048 kHz or E1, set the Network Clock Type to

Option 1.
l T1, set the Network Clock Type to Option 2.

The software will detect AIS or LOF at the BITS interface

endpoints if you provision mismatches of the device
Network Clock Type and the device line-type. Before
you configure other BITS OUT options, set the Line Type
.
Line Code Sets the BITS line code. If Line Type is set to E1 HDB3,
E1 AMI, T1
l E1, the available options are E1 HDB3 and E1 AMI.
B8ZS, T1 AMI
l T1, the available options are T1 B8ZS and T1 AMI.
l 2048 kHz, this option does not apply.
Frame Format Sets the BITS Frame Format. If Line Type is set to E1 Unframed,
E1 CRC4,
l E1, available the options are E1 Unframed, E1 CRC4
E1 DualFrame.
and E1 DualFrame.
T1 Superframe,
l T1, the available options are T1 SuperFrame and T1
T1 Extended-
Extended- SuperFrame.
Superframe
l 2048 kHz, this option does not apply.
SA Bit Select the Signalling Associated (SA) Bit. SA Bit applies if None,
Line Type is set to E1. Bit 4,
Bit5,
Bit 6,
Bit 7,
Bit 8
QL Mode Set the Quality Level Mode. If Line Type is set to 2048 Enabled or
kHz, this option does not apply. Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 360

Oscilloquartz: An ADVA Company

Table 61: NE-1 NTE OSA 5422 BITS-1 BITS-OUT: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Squelch QL Set the Squelch Quality Level. The Squelch QL attribute QL-NONE,
defines the minimum QL that the system timing can QL-PRC,
accept. If the system timing QL falls below this selected QL-SSU-A,
value, the software turns off BITS-OUT and priovides no QL-SSU-B,
BITS-OUT signal. QL-EEC1,
QL-DNU
Line Build Out Option to set impedance for cable length or dB. Applies 0 to 133 ft,
only if Line Type is T1. 133 to 266 ft,
266 to 399 ft,
339 to 533 ft,
533 to 655 ft,
7.5 dB,
15 dB,
22.5 dB

Table 62: NE-1 NTE OSA 5422 PPS-1-1-1-1 and PPS-1-1-1-2: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
alias A text or number string, or combination, that you enter to up to 64
uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the administrative state.The entity does not show Unassigned,
up as a potential synchronization reference if the IS,or
administration state is set to Unassigned. See Entity State Management
Descriptions.
Signal Defines the signal direction for this interface. Options are Input or
Direction Input or Output, that you can select from a list. PPS-1-1-1- Output
(PPS-1-1-1-2) 1 is input only, and Signal Direction is unavailable.
For a PPS-X16 line card: If the Signal Direction of PPS-1-1-
1-2 is Input, you cannot create a pps16port group.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 361

Oscilloquartz: An ADVA Company

Table 62: NE-1 NTE OSA 5422 PPS-1-1-1-1 and PPS-1-1-1-2: Edit Configuration
Option
Parameter Description and Applicable Rules Settings and
Defaults
Squelch You must establish this hierarchy for Squelch control of Never,
Control the PPS timing interfaces if you configured these interface Holdover,
as Outputs: Lock
l NEVER, where the output is never squelche.d
l HOLDOVER, where output is squelched only in freerun
state.
l LOCK, where output is squelched in holdover and
freerun states.

This setting does not apply to PPS-1-1-1-1 which is input

only, or if you configured PPS-1-1-1-2 as input.
Input Rate Defines the input rate. Applies if you set the Signal Pulse Per
Direction to Input. Second, Pulse
Per 2 Seconds
Cable Delay Cable Delay Compensation in ns. –100000000
Compensation to 100000000
(ns) 0
Source Eid Defines the source EID to provide as a PPS output if you List of
set the Signal Direction to Output. provisioned
Clock
Reference
sources

Table 63: NE-1 NTEOSA 5422 TOD-1-1-1-1 & PPS: Edit Configuration
Option Settings and
Parameter Description and Applicable Rules
Defaults
alias A text or number string, or combination, that up to 64 characters or
you enter to uniquely identify this entity. This Undefined
string can be up to 64 printable ASCII characters
long.
Administrative Defines the administrative state. See Entity State Unassigned or IS
Descriptions.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 362

Oscilloquartz: An ADVA Company

Table 63: NE-1 NTEOSA 5422 TOD-1-1-1-1 & PPS: Edit Configuration
Option Settings and
Parameter Description and Applicable Rules
Defaults
Signal Defines the signal direction for this interface. Input or Output
Direction Options are Input or Output, that you can select.
Input Rate Defines the input rate. Applies if you set the Pulse Per Second
Signal Direction to Input.
Cable Delay If you configure the ToD & PPS port as an input, 0 ns
Compensation this value defines the delay compensation. The
time is –100000 to 100000 nanoseconds.
Source Eid Defines the source EID to provide as a ToD +PPS Defaults change
input or output depending on the defined Signal according to the
Direction. configured Signal
Direction:
Input: GPS-1-1-1-1 The
ToD source is from
GPS/GNSS, not from
serial ToD.
Output: List of
provisioned Clock
Reference sources.
Squelch You should establish this hierarchy for Squelch Never, Holdover, Lock
Control control of TOD & PPS timing interface. This
setting applies only if you set the Signal
Direction ito Output.

l NEVER, where the output is never squelched.

l HOLDOVER, where output is squelched only
in freerun state.
l LOCK, where output is squelched in holdover
and freerun states.
Output Format TOD & PPS port output format. NMEA or CCSA

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 363

Oscilloquartz: An ADVA Company

Table 64: NE-1 NTEOSA 5422GNSS-1-1-1-1 Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Alias A text or number string, or combination, that you enter up to 64
to uniquely identify this entity. This string can be up to 64 characters or
printable ASCII characters long. Undefined
Administrative Defines the administrative state. See Entity State Unassigned or
Descriptions. IS
PPS generation The minimum number of satellites that need to be locked 1 SAT or
condition before the system can generate PPS output. 3 SATS
Antenna Cable Defines the delay that the cable introduces. This cable Measurement:
Delay connects the antenna to the GPS interface as either a 5 meters
measurement in meters (default 5) or time in (default)
nanoseconds (default 0). The measurement is 0 to
Time: 0 ns
999999 meters. The time is –100000 to 100000
(default)
nanoseconds. For the best absolute PPS accuracy, adjust
the cable delay to match the installed cable length. Verify
with your cable manufacturer for the delay for a specific
cable type. Set the length in meters. The cable delay
calculation assumes 4.5 nsec/meter.
Note: You can use this attribute to compensate for the
delay that the GNSS Antenna Kit creates. The delay can
include cable delays, antenna delays , lightning protector
delays, and any other cable that contributes to the delay.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 364

Oscilloquartz: An ADVA Company

Table 64: NE-1 NTEOSA 5422GNSS-1-1-1-1 Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
GNSS System Defines the type of GNSS system used. Changing the GPS Only,
Types GNSS System Types, while the GPS 1-1-1-1 is In Service, GLONASS
can affect performance. Since the different GNSS system Only, GPS and
types do not always share the same time reference, GLONASS,
switching between them can impact the Time Clock. The
BEIDOU and
system automatically executes a cold reset of the GNSS
GPS, BEIDOU
receiver, when one of these transitions occurs:
Only, GALILEO
l GPS Only to GLONASS Only Only, GALILEO
l GPS Only to GALILEO Only and GPS
l GPS Only to BEIDOU Only
l GPS Only to GALILEO and GPS

In these cases, the GNSS survey restarts.

Note: To minimize the impact of modifying the GNSS
System Types, we recommend performing these steps:

1. Manually enable the Lock out of the Time Clock

Reference before the configuration change.
2. Clear the Lock out, when the GNSS receiver is stable.
Typically, after 1 hour or at the end of the survey
period, if the survery was reinitialized.
Installation Defines the GNSS antenna installation scenario: Full Sky Full Sky View,
Type View (where C/No Mask is 35 and Elevation Mask is 20 Limited Sky
degrees) or Limited Sky View (where C/No Mask is 0 and View
Elevation Mask is 0 degrees).
C/No Mask Defines the quality of received GNSS satellite-signals, 35 dB-Hz
which is reported as a C/No value (Carrier-to-Noise
power ratio). This mask enables excluding satellites with a
particular C/No from being used by the receiver. The
range is between 0 to 55 dB-Hz (default 35 db-Hz). Low
C/No values can result from low-elevation satellites,
partially obscured signals (due to dense foliage for
example), or reflected RF signals (multipath).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 365

Oscilloquartz: An ADVA Company

Table 64: NE-1 NTEOSA 5422GNSS-1-1-1-1 Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Elevation Mask Defines the elevation mask in degrees, where the range is 20 degrees
between 0 to 90 degrees. Generally, signals from low-
elevation satellites are of poorer quality than signals from
higher elevation satellites. These signals travel farther
through the ionospheric and tropospheric layers and
undergo distortion due to these atmospheric conditions.
This mask enables excluding satellites with poor elevation
from being used by the receiver. For example, an
elevation mask of 10° excludes very low satellites from
position fix computations and reduces the likelihood of
potential errors induced by using those signals.
PDOP Mask Defines the Position Dilution of Precision (PDOP) Mask 6
value, where PDOP is a measure of the error caused by
the geometric relationship of the satellites used in the
position solution, and is used to measure the current
satellite geometry. This mask can be used to exclude a
position calculated based on poor PDOP to be used
during location survey. The range is between 2 to 12. It
takes into account each satellite’s location relative to the
other satellites in the constellation. Satellite sets that are
tightly clustered or aligned in the sky have a high PDOP
and contribute to lower position accuracy.
Note: PDOP is applicable only during self-survey or
whenever the receiver is performing position fixes. The
PDOP Mask displays Not Available after the GNSS
receiver terminates self-survey mode.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 366

Oscilloquartz: An ADVA Company

Table 64: NE-1 NTEOSA 5422GNSS-1-1-1-1 Edit Configuration

Option
Parameter Description and Applicable Rules Settings and
Defaults
Self Survey Defines the Self Survey Period, which is used to specify 86400 seconds
Period the number of position fixes that are to be averaged
together to form the self-surveyed position. The range is
between 1-500,000 seconds. For applications that require
a high level of time accuracy, it is recommended to use a
long position survey time, such as one day (average of
86400 values).
Note: While the position is calculated during the self-
survey period, the timing performance of the device is
not yet optimal. Therefore, we recommend waiting until
the self-survey period is completed before starting any
measurements of the timing outputs, such as PPS and
PTP.
Sat Min1 Defines the first minimum (Min1) number of in use 3 satellites
Threshold satellite thresholds. The range is between 1-32 satellites.
Sat Min2 Defines the second minimum (Min2) number of in use 2 satellites
Threshold satellite thresholds. The Sat Min2 Threshold must be
less than the Sat Min1 Threshold, and cannot be set
before the Sat Min1 Threshold is defined. The range is
between 1-32 satellites. The Sat Min1 Threshold and
Sat Min1 Threshold numbers are used to determine
which alarm is asserted (or cleared) if a number of in-use
GNSS satellites is below or above thresholds according to
these conditions:

l When the number of valid satellites observed by the

receiver is less than equal to the Sat Min2 Threshold,
the Sat Min2 Threshold alarm is asserted.
l When the Sat Min2 Threshold is less than the
number of valid satellites observed by the receiver,
and the number of satellites is less than the Sat Min1
Threshold, the Sat Min1 Threshold alarm is asserted.
l When the Sat Min1 Threshold is less than equal to
the number of valid satellites observed by the
receiver, no alarm is asserted.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 367

Oscilloquartz: An ADVA Company

System Configuration Settings

Default settings are shown in bold text, if applicable.

Communications
For more information about how to add, delete, or display IPv4 static
routes, see Adding/Deleting IPv4 Static Routes.

Table 65: NE-1 NTEOSA 5422 IPv4 Static Route: Add Static Route
Settings and
Parameter Description
Defaults
Dest IP Defines the IPv4 address of the destination. The IPv4 0.0.0.0
Address address of 0.0.0.0 is reserved for default routes. You can
only enter the IPv4 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 0.0.0.0
values are IPv4 mask. If you set the IP address to 0.0.0.0,
the only available choice for subnet mask is 0.0.0.0.
Gateway IP Defines the IPv4 address of the next hop for remote 0.0.0.0
Address destinations. For the routes that the specified interface can
directly reach, set this value to 0.0.0.0.
Interface Defines the interface to use to create an IPv4 static route. eth0
Name List of valid
interface
entries
Metric Metric of the route. 0 to 65,535
Advertise Defines whether the IPv4 static route is to be advertised or Enabled or
Route not. When enabled, the IPv4 static route advertises on Disabled
every other interface that has RIP enabled.

Table 66: [NE-1 NTEOSA 5422 IPv4 Static ARP Entry: Add Static ARP Entry
Parameter Description Settings and Defaults
IP Address IPv4 address to add to the Address Resolution 0.0.0.0
Protocol entry.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 368

Oscilloquartz: An ADVA Company

Table 66: [NE-1 NTEOSA 5422 IPv4 Static ARP Entry: Add Static ARP Entry
Parameter Description Settings and Defaults
MAC Address MAC Address to add to the ARP entry. MAC 00:00:00:00:00:00
addresses are hardcoded at the factory. hh:hh:hh:hh:hh:hh
Interface Name Defines the interface to use create the ARP eth0
entry. List of valid interface
names

For more information about how to add, delete, or display IPv6 static
routes, see Adding/Deleting IPv6 Static Routes.

Table 67: [NE-1 NTEOSA 5422 IPv6 Static Route: Add Static Route
Paramete
Description Settings and Defaults
r
Destina- Defines the IPv6 unicast address of the 0000:0000:0000:0000:0000:
tion added destination. The IP address of 0000:0000:0 000 /64
0000:0000:0000:0000:0000:0000:
0000:0000/64 is reserved for default
routes. You can enter the static default
route of
0000:0000:0000:0000:0000:0000:0000:
0000 only if the system default router
is
0000:0000:0000:0000:0000:0000:0000:
0000.
The range is 2000::/3 (2000::0000 to
3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFF
F).
Gateway Defines the IPv6 address for the 0000:0000:0000:0000:0000:0000:00
IP Address management interface gateway. For 00:0 000
routes that the specified interface can
directly reach, this value should be
0000:0000:0000:0000:0000:0000:
0000:0000. For the routes that the
specified interface cannot directly
reach, this value is the IP address of the
next hop and should not be all zeros.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 369

Oscilloquartz: An ADVA Company

Table 67: [NE-1 NTEOSA 5422 IPv6 Static Route: Add Static Route
Paramete
Description Settings and Defaults
r
Interface Defines an IPv6 management interface List of valid IPv6 management
Name to use to create a static route. The interface EIDs.
management interfaces in IPv6 mode
automatically display in the list. If you
enable Management Traffic Bridging,
and you configure eth0 with an IPv6
unicast address, you can use only eth0
for the interface name.
Metric Specify the metric as the priority for the 0 to 65535
route that you add. 1
Advertise Enable or Disable advertising the route Enabled or Disabled
Route to the next hop.

For more information about how to add, delete, or display IPv6 static neigh-
bor entries, see Adding/Deleting IPv6 Static Neighbor Entries.

Table 68: NE-1 NTEOSA 5422 IPv6 Static Neighbor Entry

Option Settings and
Parameter Description and Applicable Rules
Defaults
IP Address Enter a valid IPv6 unicast address for a target 0000:0000:0000:0000:0000:
Neighbor that you want to add. 0000:0000:0 000
MAC Neighbor Discovery Protocol (NDP) resolves 00:00:00:00:00:00
Address the MAC address entered for the target IP
address.
Interface Select an IPv6 management interface to create List of valid IPv6 management
Name a neighbor entry. The management interfaces interface EIDs.
in IPv6 mode automatically disply in list of
names.
If you enable Management Traffic Bridging,
and you configure eth0 with an IPv6 unicast
address, you can use only eth0 for the
interface name.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 370

Oscilloquartz: An ADVA Company

Table 69: NE-1 NTE OSA 5422Source Address Code Edit Source Address Config
Option
Parameter Description and Applicable Rules Settings and
Defaults
Address Type Specifies whether the software should use the system IP Outgoing
address or the IP address of the outgoing interface in interface IP
outgoing IP PDUs. address or
system
IP address
Source Specifies the IP interface name when you set Address Type eth0 or
Address to System IP Address. The software sets the IP address Configured
Interface associated with the IP interface name as the source IP Management
Name address in outgoing PDUs. Tunnel entries
Configured Configured Management Tunnel entries. eth0 or
Management Configured
Tunnel entries Management
Tunnel entries

Table 70: NE-1 NTEOSA 5422DCN (eth0) Edit Configuration

Option Settings
Parameter Description and Applicable Rules
and Defaults
IP Mode Management tunnels IPv4 only or IPv4
and IPv6
IP Address IPv4 address for the DCN port. If DCHP is set to Enabled Disabled: IPv4
or DHCP Role is set to DHCP Client, this option does not automatically set.
apply. Enabled: 0.0.0.0.
Netmask Defines the IPv4 subnet mask for the DCN. If DCHP is set Disabled:
to Enabled or DHCP Role is set to DHCP Client, this option 255.255.255.0
does not apply. If DHCP is Enabled and the DHCP Role is Enabled: 0.0.0.
set to DCHP Server, the netmask determines the number
of IPv4 addresses available for assignment.
RIPv2 Specifies whether the Routing Information Protocol V2 Enabled or
packets are enabled or disabled. Disabled.
DHCP Defines whether Dynamic Host Configuration Protocol is Enabled or
enabled or disabled. If this interface is set to Enabled and Disabled.
DHCP Role is set to DHCP Client, the device sends a
broadcast query that requests IP address information
from a DHCP server.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 371

Oscilloquartz: An ADVA Company

Table 70: NE-1 NTEOSA 5422DCN (eth0) Edit Configuration

Option Settings
Parameter Description and Applicable Rules
and Defaults
DHCP Role Defines whether the DHCP Role is as a server or a client. DHCP Server or
Servers assign IPv4 addresses, and clients receive IPv4 DHCP Client
addresses. This option applies only if DHCP is set to
Enabled.
If the DHCP Role is set to DHCP Server, you must Disable
and then Enable DHCP for the initialization of the server
function (IP Address range) to take place.
DHCP Client Use this field to insert the DHCP Client ID in DHCP Enabled or
ID Control messages if the DHCP Role is set to DHCP Client. Disabled.
If the DHCP Role is set to DHCP Server, this option is
disabled.
DHCP Client The Client ID maximum length is 254 characters. The system name
ID default value is the System Name truncated to 254
characters. Set this field only if the DHCP Role is set to
DHCP Client and the DHCP Client ID Control is Enabled.
Edit System Select this field to edit the Gateway IPv4 Address. Applies Field is cleared.
Default only if DHCP is Disabled. Otherwise, the option is
Gateway disabled.
Gateway IP Enter a Gateway IPv4 Address if the Edit System Default Unavailable
Address Gateway check box is selected.
IPv6 Unicast Specifies the IPv6 unicast address for the DCN port. This IPv6
Address option applies only if DHCPv6 is disabled. automatically set
Note: When you configurean IPv6 network and do not unless manually
need IPv4, disable the IPv4 DHCP and set the IPv4 address configured.
to 0.0.0.0/0.
DHCPv6 Specifies whether the DHCP is enabled or disabled. If this Enabled or
interface is set to Enabled and the DHCPv6 Role is set to Disabled.
DHCP Client, the device sends a broadcast query to
request IPv6 address information from a DHCP server.
DHCPv6 Defines the DHCP Role in an IPv6 network, which is fixed DHCP Client or
Role as a client. Clients receive IPv6 addresses.
Unavailable

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 372

Oscilloquartz: An ADVA Company

Table 70: NE-1 NTEOSA 5422DCN (eth0) Edit Configuration

Option Settings
Parameter Description and Applicable Rules
and Defaults
RIPng Defines whether the Routing Information Protocol next Enabled or
generation (RIPng) packets are enabled or disabled. IF Disabled.
RIPng is enabled on an IPv6 interface, the interface
receives the IPv6 route entry on the link and updates the
local route table. The interface also sends local IPv6 route
entries to the link using multicast packets.
Edit System Select to edit the Gateway IPv6 Address. Field is cleared.
Default
Gateway
Gateway Enter a Gateway IPv6 Address if the Edit System Default Unavailable
IPv6 Gateway this field is selected.
Address

Table 71: NE-1 NTEOSA 54223G DCN: Select to Display Configuration

Parameter Description and Applicable Rules Option Settings and Defaults
You can view the 3G DCN information but not edit it.

SNMP
To delete an existing community name, in the selection tree, right-click the
SNMP entity and select Delete Community. Select the appropriate Com-
munity Name from the list and select OK.

Table 72: SNMP Add or Delete Community

Parameter Description and Applicable Rules Option Settings and Defaults
Community Name Entry for the valid Community Name. public
private
Access Type Defines the access type. Read Only (public)

The system supports up to 10 target addresses. To delete an existing target

address, in the selection tree and Target Addresses tab, select the SNMP
entity. Right-click the appropriate target address and select Delete Entry.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 373

Oscilloquartz: An ADVA Company

Table 73: SNMP Add or Delete Target Address

Option Settings
Parameter Description and Applicable Rules
and Defaults
Target A text or number string that you define, which identifies up to 32 characters
Parameter this set of target parameters. You can use up to 32 or Undefined
Name characters.
Security List of security models for this set of target parameters. SNMPv1, SNMPv2,
Model USM
Security Specifies the security level for the new target No Authentication,
Level parameter. Applies only if you select Security Level USM Auth/No Priv,
. Auth/Priv
Security List of available security names for SNMPv1 or private or public
Name SNMPv2c.
List of available security names for USM. ADMIN, MONITOR,
OPERATOR,
PROVISION

To delete an existing target parameter, in the selection tree, right-the SNMP

entity and select the Delete Target Parameter item. Right click the Target
Address you want to delete, and then select Delete Entry.

Table 74: SNMP Add or Delete Target Parameters

Option Settings
Parameter Description and Applicable Rules
and Defaults
Target User defined text or number string that you use to up to 32 characters
Parameter identify this set of target parameters. You can enter up or
Name to 32 characters. Undefined
Security Select a security model for this set of target parameters. SNMPv1, SNMPv2,
Model USM
Security Specifies the security level for the new target parameter. No
Level Applies only if you select Security Level USM. Authentication,
Auth/NoPriv,
Auth/Priv
Security List of available security names for SNMPv1 or public or private
Name SNMPv2c.
List of available security names for USM. ADMIN, MONITOR,
OPERATOR,
PROVISION

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 374

Oscilloquartz: An ADVA Company

To delete an existing USM user, in the selection tree, right-click the SNMP
entity and select Delete USM User Entry. In the Details pane, select the USM
User to delete and click OK.

Table 75: SNMP: Add or Delete USM User

Option
Parameter Description and Applicable Rules Settings and
Defaults
User Name Enter a valid user name. A valid entry contains 1 to 32 1 to 32
characters. These characters are accepted: a to z, A to Z, 0 to characters or
9, and these . _ - " Undefined
Engine ID The administratively-unique identifier of an SNMP engine. 5 to 32
A valid entry is 5 to 32 characters. In a simple agent, this characters
value is always that agent's own snmpEngineID value of or Undefined
local. The value can also use the value of the snmpEngineID
of a remote SNMP engine that this user can communicate
with.
Objects of this type are for identification, not for addressing.
It is possible that an address was used in the generation of a
specific value. The value for this object cannot be all zeros
or all 'ff', or an empty zero-length string.
Security Security Name. A valid entry contains 1 to 256 of these 1 to 256
Name characters: a to z, A to Z, 0 to 9 and these ._-". You must characters
enter a security name. If you do not, the system or Undefined
automatically uses User Name.
Security Options are No Authentication, Authentication with No No
Level Privacy key, or Authentication with Privacy key. Authentication,
Auth/No Priv,
Auth/Priv
User Access Specifies the user access type. Read only or
Type Read/Write
Auth. Select from the list of established authentication protocols. MD5 or SHA1
Protocol This option is available only if the Security Level is other than
No Authentication.
Auth. Key Available when you select Auth/Priv or Auth/No Priv (blank)
Security Level. A valid entry depends on the selected
security level, see, Security Policy Strength.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 375

Oscilloquartz: An ADVA Company

Table 75: SNMP: Add or Delete USM User

Option
Parameter Description and Applicable Rules Settings and
Defaults
Confirm Reenter the key that yo entered in the Auth. Key field to blank
Auth. Key confirm the key.
Priv. Select from the list of established privacy protocols. This DES or AES
Protocol option is available only if you set the Security Level to
Auth/Priv.
Priv. Key Available when you select Auth/Priv Security Level. A valid blank
entry depends on the selected security level, see, Security
Policy Strength.
Confirm Reenter the key that you entered in the Priv. Key field to 8 to 32
Priv. Key confirm the key. characters
Undefined

Table 76: SNMP Dying Gasp: Edit Dying Gasp

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
SNMP Select from the list of each configured Target Address to Enable No Target
Dying Gasp or Disable SNMP Dying Gasp on that Target Address. The system Addresses
defaults contain no configured target addresses. Exist
SNMP dying gasp is supported only with IP management tunnel
and when the system management IP uses DCN0.

Administration
Users: Add User, Edit User, or Edit Password

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 376

Oscilloquartz: An ADVA Company

Table 77: Users: Add User, Edit User, or Edit Password

Option
Parameter Description and Applicable Rules Settings and
Defaults
User Name User Identifier, which is your log-in name. Specify 1 to 32 1 to 32
alphanumeric characters. If the password security strength is characters or
set to high, the minimum length of a User ID is 6 characters. Undefined
Spaces are not allowed. The system supports three levels of
username and password security and depends on the security
policy setting. See Configuring the Security Policy. The default
Superuser ID is root. Only a Superuser can create or delete a
user ID. This option is available when you select Add User or
Edit Password.
Password Your login password. The system supports three levels of 1 to 32
and Retype password security and depends on the security policy setting. characters
Password See Configuring the Security Policy. Only a Superuser can Undefined
create a password associated with a new User ID. A Superuser
can edit any existing password. Any user can edit his or her
own password. This option is available when you select Add
User or Edit Password. The default Superuser password is
ChgMeNOW.
Comment User comment text string, a maximum of 128 characters. Only up to 128
a Superuser can edit a user comment. This option is available characters
when you select Add User or Edit User. Undefined
Privilege User Security Level. The Superuser assigns security levels for Superuser,
each user. See Only a Superuser can edit a user privilege level. Maintenance,
This option is available when you select Create New User or Provisioning,
Edit User. The default root user ID privilege level is Super User. Retrieve
Login Login timeout for the user ID in minutes. Only a Superuser 0 (no logout
Timeout can edit a user login timeout value. This option is availabletimer) to
(mins) when you select Add User or Edit User. 99 (minutes)
A change in the Login Timeout value becomes active after the 15 (minutes)
user logs off and then logs in again.
CLI Paging If the response to a CLI command fills more than one screen, Enabled
the UI separates the response into multiple screens if you
enable this option.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 377

Oscilloquartz: An ADVA Company

Table 78: Remote Authentication

Parameter Description and Applicable Rules Option Settings and Defaults
Authentication Sets the Remote Authentication NONE, RADIUS, TACACS
Protocol Protocol type.
Authentication Remote authentication type. Options PAP, CHAP
Type available are: Password Authentication
Protocol (PAP) or Challenge-
Handshake Authentication Protocol
(CHAP).
TACACS If you set this field to Enabled, the Enabled or Disabled
Privilege system expects the User Privilege level
Control to be returned from the TACACS+
server.
WIf you set this field to Disabled, the
system does not expect User Privilege
level information from the TACACS+
server. The server instead uses the
privilege level set in the TACACS
Default Privilege Level attribute.
TACACS If you set TACACS Privilege Level Retrieve, Maintenance,
Default Control to Disabled, the software uses Provisioning, Superuser, Not
Privilege this value as the user's privilege level Applicable
after the TACACS+ server
authenticates the user.
If you set TACACS Privilege Level
Control to Enabled, the software
automatically sets this value to Not
Applicable.
NAS IP Address The IPv4 address of the Network 0.0.0.0
Access Security server. This option
applies only if you set the
Authentication Protocol to RADIUS.
NAS IP Address The IPv6 address and prefix of the 0000:0000:0000:0000:
(v6) Network Access Security server. This 0000:0000:0000:0000/64
option applies only applicable if you
set the Authentication Protocol to
RADIUS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 378

Oscilloquartz: An ADVA Company

Table 78: Remote Authentication

Parameter Description and Applicable Rules Option Settings and Defaults
TACACS + Enable or Disable the use of an Enabled or Disabled
Accounting accounting port.
Access Order Set the RADIUS access order. If the Local or Remote
Access Order is set to Local First (the
default), user login is first
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. Enabled or Disabled
Authentication
Server (1 to 3)
Status
Remote Defines the priority of the server in First, Second, Third
Authentication servicing requests. Multiple servers can
Server (1 to 3) have the same priority value. Random
Priority ordering is chosen for those servers
with equal priority values. Server 1
default is First, Server 2 default is
Second and Server 3 default is Third.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 379

Oscilloquartz: An ADVA Company

Table 78: Remote Authentication

Parameter Description and Applicable Rules Option Settings and Defaults
Remote Define the IP type as either IPv4 or IPv4
Authentication IPv6,and in the field beneath enter the 0.0.0.0
Server (1 to 3) IP address of the specified Remote
IP Address Authentication Server. IPv6
0000:0000:0000:0000:0000:0000:
0000:0000
Edit Server Check box that if selected allows the (clear)
Secret editing of the Server Secret.
Remote Defines the shared secret used for up to 128 characters
Authentication authenticating the OSA 5422 with the (blank)
Server (1 to 3) Remote Authentication server. Valid
Server Secret entry is a string of up to 128 non-
whitespace characters. To make an
entry, select the Edit Server Secret
check box.
Remote Defines the UDP port to use when 1 to 65535
Authentication communicating with the Remote 1812 (RADIUS)
Server (1 to 3) Authentication server. Default is 1812 if 49 (TACACS)
Port Authentication Protocol is set to
RADIUS or None, default is 49 if
Authentication Protocol is set to
TACACS.
Remote Defines the UDP port to use for 1 to 65535
Authentication accounting when communicating with 1813 (RADIUS)
Server (1 to 3) the Remote Authentication server. 49 (TACACS)
Accounting Default is 1813 if Authentication
Port Protocol is set to RADIUS or None,
default is 49 if Authentication Protocol
is set to TACACS. Only editable if
Accounting is Enabled.
Remote Defines the timeout in seconds after 2 to 10
Authentication which communication with this server 3
Server (1 to 3) fails. This option is only applicable if
Timeout Authentication Protocol is set to
RADIUS.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 380

Oscilloquartz: An ADVA Company

Table 78: Remote Authentication

Parameter Description and Applicable Rules Option Settings and Defaults
Remote The maximum number of tries that will 0 to 5
Authentication be attempted with this server. 5
Server (1 to 3)
Retries

Table 79: Security Policy: Edit Policy

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Security The system supports these three levels of security strength for High,
Policy local user passwords. This setting is used for the basis of user Medium,
Strength name and password entry. Low
High:
1. The User Name must be 6 to 32 characters with no spaces.
The password must:
2. Be 12 to 32 characters in length.
3. Not begin with # and contain only alphanumeric and these
special characters: # * % - _
4. Contain uppercase and lowercase characters, at least 2 special
characters, and at least 1 digit.
5. Contain no more than 2 consecutively repeated letters or digits.
6. Not contain a sequence of 3 consecutive alphanumeric
characters in ascending or descending order.
7. Be different from the User Name.
8. Not be password/passw0rd in lowercase, uppercase, or a
combination.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 381

Oscilloquartz: An ADVA Company

Table 79: Security Policy: Edit Policy

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Medium:
1. THe User Name must be 1 to 32 characters with no spaces.

The password must:

2. Be 8 to 32 characters.
3. Not begin with # and contain only alphanumeric and these
special characters: # * % - _
4. Must contain uppercase and lowercase characters, at least 1
digit.
5. Not contain more than 2 consecutively repeated letters or
digits.
6. Not contain a sequence of 3 consecutive alphanumeric
characters in ascending or descending order.
7. Be different from the user name.
8. Not be password/passw0rd in lowercase, uppercase or a
combination.
Low:
1. The User Name must be 1 to 32 characters with no spaces
allowed.
The password must:
2. Be 1 to 32 characters.
3. Not begin with # and contain only alphanumeric and these
special characters: # * % - _

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 382

Oscilloquartz: An ADVA Company

Table 80: User Data Policy: Edit Policy

Option
Settings
Parameter Description and Applicable Rules
and
Defaults
Interval in Select a value of 1 to 1096 days, which is 3 years. This value NEVER
days indicates when the system anonymizes the user names in the logs 1 to 1096
after this time interval. The software anonymizes the user names at days
midnight of that day, after the configured number of days pass, in
all the log entries that precede the configured value. If you set the
logging anonymization interval to NEVER, the software will never
anonymize the user name, which is the default setting.

Table 81: Key Generation

Option Settings and
Parameter Description and Applicable Rules
Defaults
Regenerate Select to create a new SSL certificate, and then Not selected
SSL Edit the SSL Certificate Data options are
Certificate applicable.
When an SSL Certificate generates, the HTTP
server restarts and web access is unavailable
during this time, which is approximately 15
seconds.
Regenerate Select to create a new SSH certificate. Not selected
SSH Key When an SSH Key is generated, all SSH users
are logged off.
Country Edit SSL Certificate Data - Country US
State Edit SSL Certificate Data - State Texas
Locality Edit SSL Certificate Data - Locality Richardson
Organization Edit SSL Certificate Data - Organization ADVA Optical Networking
Organization Edit SSL Certificate Data - Organization Unit Ethernet Access
Unit
Name Edit SSL Certificate Data - Name ADVA
Email Edit SSL Certificate Data - Email [email protected]
Valid Until Edit SSL Certificate Data - Valid Until (varies)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 383

Oscilloquartz: An ADVA Company

Syncjack Configuration Options and Rules

This section describes Syncjack option settings. The options described in this section are
performed using the Syncjack application (located on the Toolbar or available through the
Application menu) once the license of the PTP feature has been activated (see Activating
Software Licenses).

In addition to configuring Syncjack options, TIE-History stats are available in the Syncjack
application.

Clock Accuracy Parameters

The Clock Accuracy parameters when creating or editing a clock probe are explained in this
table.

For more information on clock accuracy testing, see Performing Clock

Accuracy Testing.

Table 82: Create/Edit Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Clock Probe Clock Probe Index. Number is automatically 1-32

Index (Create indexed, but is user editable.
only)
Name A text and/or number string the user enters to up to 15
uniquely identify this entity. This string can be characters
up to 15 printable ASCII characters long. (blank)
Reference Defines the reference source for the Clock CLK-1-1-1-1
Probe. References available are presented in a CLK-1-1-1-2
drop-down list.
SYNC-1-1-1-1
BITS IN-1-1-1-1
TS-1-1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 384

Oscilloquartz: An ADVA Company

Table 82: Create/Edit Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Reference PPS-1-1-1-1
(con't) PPS-1-1-1-2
ACCESS PORT-1-
1-1-1
ACCESS PORT-1-
1-1-2
NETWORK PORT-
1-1-1-1
NETWORK PORT-
1-1-1-2
TIME CLOCK-1-1-
1-1
GPS-1-1-1-1
PTP CLOCK-1-1
Reference Defines the expected Quality Level of the QL-NONE
Expected QL selected reference for the Clock Probe. Available QL-PRC
QL levels are presented in a drop-down list.
QL-SSU-A
QL-SSU-B
QL-EEC1
Source Defines the source of the clock to be measured CLK-1-1-1-1
by the Clock Probe. Sources available are CLK-1-1-1-2
presented in a drop-down list.
SYNC-1-1-1-1
BITS IN-1-1-1-1
TS-1-1
PPS-1-1-1-1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 385

Oscilloquartz: An ADVA Company

Table 82: Create/Edit Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Source PPS-1-1-1-2
(con't) ACCESS PORT-1-
1-1-1
ACCESS PORT-1-
1-1-2
NETWORK PORT-
1-1-1-1
NETWORK PORT-
1-1-1-2
TIME CLOCK-1-1-
1-1
GPS-1-1-1-1
PTP CLOCK-1-1
Source Type Selection for measuring frequency or phase. Frequency
Phase
MTIE Mask Define the predefined MTIE Mask to use for G823 E1 Ssu
measurements. Choices are presented in a drop- G823 E1 Sec
down list.
G823 E1 Traffic
G823 Pdh
G824 T1 Sync
G824 T1 Traffic
G8261 E1 Case 1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 386

Oscilloquartz: An ADVA Company

Table 82: Create/Edit Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

MTIE Mask G8261 T1 Case 1

(con't) G8261 E1 Case 2
G8261 EEC Opt1
G8263
G8263 temp
G8272 PRTC
G8261 1
G8262 EEC Opt1
G8262 EEC Opt1
temp
G8262 EEC Opt2
G8262 EEC Opt1
Tolerance
Mask The margin percentage to be applied to the 0
Margin,% selected MTIE Mask. Range is from 0 to 100.
Raw Data Enables or disables Raw Data to be sent to a Enabled
Collection remote Raw Data Collection server. Disabled
Measurement Selects the measurement type. Frequency
Type Phase
MTIE Restart Defines whether the MTIE measurement is Enabled
restarted every 24 hours at 00:00:00 according
to the system time. This ensures that the
measurement is updated with the most recent
values. When restarted, the values of the Mask
Failure, Mask Crossed Time, Mask Margin
Failure, and Mask Margin Crossed Time are
reinitiated and start from a new time period.
Disabled
Note: If this setting is disabled, the MTIE
measurement is calculated over the entire
period from when the clock probe is activated.
Therefore, the MTIE graph can include
measurements that are not relevant as they are
dated.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 387

Oscilloquartz: An ADVA Company

Table 82: Create/Edit Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Max TE Maximum Time Error Threshold (in ns). This 0–100000000

Threshold (ns) option is only applicable if Measurement Type is
set to Phase. If measurement exceeds this
threshold (+ or - direction in respect to 0 on the
phase TE graph) then this will create an SJ Max
TE Threshold Exceeded alarm. Max TE threshold
must be at least 50 ns greater than the clear
threshold. Setting both Max TE Threshold and
Max TE Clear Threshold to 0 will disable this
TCA.
Max TE Clear Maximum Time Error Clear Threshold (in ns). 0–100000000
Threshold (ns) This option is only applicable if Measurement
Type is set to Phase. If the measurement meets
this threshold (+ or - direction in respect to 0 on
the phase TE graph) will clear an existing SJ Max
TE Threshold Exceeded alarm.
Const TE Constant Time Error Threshold (in ns). This 0–100000000
Threshold (ns) option is only applicable if Measurement Type is
set to Phase. If the constant measurement
(average measurement) exceeds this threshold
(+ or - direction in respect to 0 on the phase TE
graph) then this will create an SJ Constant TE
Threshold Exceeded alarm. Constant TE
threshold must be at least 50 ns greater than
the clear threshold. Setting both Const TE
Threshold and Const TE Clear Threshold to 0 will
disable this TCA.
Const TE Clear Constant Time Error Clear Threshold (in ns). This 0–100000000
Threshold (ns) option is only applicable if Measurement Type is
set to Phase. If the constant measurement
(average measurement) meets this threshold (+
or - direction in respect to 0 on the phase TE
graph) will clear an existing SJ Constant TE
Threshold Exceeded alarm.
Const TE Constant Time Error Window Size (in seconds). 500–2000
Window (s) This is the size of the sliding window of sampled
1000
measurements made for constant TE calculation.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 388

Oscilloquartz: An ADVA Company

Clock Analysis Parameters

The Clock Analysis parameters when creating or editing a PTP clock probe are explained in
this table.

For more information on clock analysis testing, see Performing Clock

Analysis.

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

PTP Clock Probe PTP Clock Probe Index. Number is 1-32

Index (Create automatically indexed, but is user editable.
only)
Name A text and/or number string the user enters 1 to 15 characters
to uniquely identify this entity. This string can (blank)
be up to 15 printable ASCII characters long.
PTP Flowpoint Identifies the PTP Flowpoint used by the PTP (drop-down list of
Clock Probe. A drop-down list of the provisioned PTP
provisioned flowpoints available for use is Flow Points)
provided.
IP Version Defines the PTP Clock Probeas using IPv4, IPv4
which is the only supported option.
Master IP Address Entry for the IP address of the Master Clock. 0.0.0.0
Entry is a valid IPv4 or IPv6 address according
to the IP Version entry. If the PTP Flow Point
Type is set to OC Slave, then the Master IP
Address must be configured the same as the
SOOC.
Slave IP Address Entry for the IP address of the Slave Clock. 0.0.0.0
Entry is a valid IPv4 or IPv6 address according
to the IP Version entry. If the PTP Flow Point
Type is set to OC Slave, then the Slave IP
Address must be configured the same as the
SOOC.
Slave Port Identity Enter the hex slave port identity. This field is Blank
only enabled depending on the PTP
Flowpoint selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 389

Oscilloquartz: An ADVA Company

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Master Port Enter the hex master port identity. This field is Blank
Identity only enabled depending on the PTP
Flowpoint selected.
Direction Direction of PTP Clock Probe operation. Slave to Master

l If the Flow Point Type of the associated

PTP Flow Point is set to OC Slave, then Master to Slave
Slave to Master or Master to Slave may be
selected. 2 Way
l If the Flow Point Type of the associated
PTP Flow Point is set to OC Master, then Master to Slave T4
only Slave to Master selection is allowed.
Reference Defines the reference source for the PTP CLK-1-1-1-1
Clock Probe. References available are CLK-1-1-1-2
presented in a drop-down list.
SYNC-1-1-1-1
BITS IN-1-1-1-1
TS-1-1
PPS-1-1-1-1
PPS-1-1-1-2
ACCESS PORT-1-
1-1-1
ACCESS PORT-1-
1-1-2
NETWORK PORT-
1-1-1-1
NETWORK PORT-
1-1-1-2
Reference TIME CLOCK-1-1-
(con't) 1-1
GPS-1-1-1-1
PTP CLOCK-1-1

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 390

Oscilloquartz: An ADVA Company

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Reference Defines the expected Quality Level of the QL-NONE

Expected QL selected reference for the PTP Clock Probe. QL-PRC
Available QL levels are presented in a drop-
QL-SSU-A
down list.
QL-SSU-B
QL-EEC1
MTIE Mask Define the predefined MTIE Mask to use for G823 E1 Ssu
measurements. Choices are presented in a G823 E1 Sec
drop-down list.
G823 E1 Traffic
G823 Pdh
G824 T1 Sync
G824 T1 Traffic
G8261 E1 Case 1
G8261 T1 Case 1
G8261 E1 Case 2
G8261 EEC Opt1
G8263
G8263 temp
MTIE Mask G8272 PRTC
(con't) G8261 1
G8262 EEC Opt1
G8262 EEC Opt1
temp
G8262 EEC Opt2
G8262 EEC Opt1
Tolerance
Mask Margin,% The margin percentage to be applied to the 0
selected MTIE Mask. Range is from 0 to 100.
Raw Data Enables or disables Raw Data to be sent to a Enabled
Collection remote Raw Data Collection server. Disabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 391

Oscilloquartz: An ADVA Company

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Measurement Selects the measurement type. Frequency

Type Phase
Delay Delay Compensation (in ns) represents the -100000000 to
Compensation known delay between the master and slave 100000000
(ns) in case the measurement type is Master to
0
Slave or Master to Slave T4, or the known
asymmetry in case the measurement type is
2 Way. This option is only applicable if
Measurement Type is set to Phase and the
direction is not Slave to Master.
MTIE Restart Defines whether the MTIE measurement is Enabled
restarted every 24 hours at 00:00:00
according to the system time. This ensures
that the measurement is updated with the
most recent values. When restarted, the
values of the Mask Failure, Mask Crossed
Time, Mask Margin Failure, and Mask Margin
Crossed Time are reinitiated and start from a
new time period. Disabled

Note: If this setting is disabled, the MTIE

measurement is calculated over the entire
period from when the clock probe is
activated. Therefore, the MTIE graph can
include measurements that are not relevant
as they are dated.
Max TE Threshold Maximum Time Error Threshold (in ns). This 0-100000000
(ns) option is only applicable if Measurement
Type is set to Phase. If measurement exceeds
this threshold (+ or - direction in respect to 0
on the phase TE graph) then this will create
an SJ Max TE Threshold Exceeded alarm. Max
TE threshold must be at least 50 ns greater
than the clear threshold. Setting both Max TE
Threshold and Max TE Clear Threshold to 0
will disable this TCA.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 392

Oscilloquartz: An ADVA Company

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Max TE Clear Maximum Time Error Clear Threshold (in ns). 0-100000000
Threshold (ns) This option is only applicable if Measurement
Type is set to Phase. If the measurement
meets this threshold (+ or - direction in
respect to 0 on the phase TE graph) will clear
an existing SJ Max TE Threshold Exceeded
alarm.
Const TE Constant Time Error Threshold (in ns). This 0-100000000
Threshold (ns) option is only applicable if Measurement
Type is set to Phase. If the constant
measurement (average measurement)
exceeds this threshold (+ or - direction in
respect to 0 on the phase TE graph) then this
will create an SJ Constant TE Threshold
Exceeded alarm. Constant TE threshold must
be at least 50 ns greater than the clear
threshold. Setting both Const TE Threshold
and Const TE Clear Threshold to 0 will disable
this TCA.
Const TE Clear Constant Time Error Clear Threshold (in ns). 0-100000000
Threshold (ns) This option is only applicable if Measurement
Type is set to Phase. If the constant
measurement (average measurement) meets
this threshold (+ or - direction in respect to 0
on the phase TE graph) will clear an existing
SJ Constant TE Threshold Exceeded alarm.
Const TE Window Constant Time Error Window Size (in 10-20000
(s) seconds).
1000
This is the size of the sliding window of
sampled measurements made for constant
TE calculation.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 393

Oscilloquartz: An ADVA Company

Table 83: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Inst TE Threshold Instant Time Error Threshold (in ns). This 0-100000000
(ns) option is only applicable if Measurement
Type is set to Phase. If the constant
measurement (average measurement)
exceeds this threshold (+ or - direction in
respect to 0 on the phase TE graph) then this
will create an SJ Instant TE Threshold
Exceeded alarm. Instant TE threshold must
be at least 50 ns greater than the clear
threshold. Setting both Inst TE Threshold and
Inst TE Clear Threshold to 0 will disable this
TCA.
Inst TE Clear Instant Time Error Clear Threshold (in ns). 0-100000000
Threshold (ns) This option is only applicable if Measurement
Type is set to Phase. If the constant
measurement (average measurement) meets
this threshold (+ or - direction in respect to 0
on the phase TE graph) will clear an existing
SJ Instant TE Threshold Exceeded alarm.

Telecom Slave Parameters

The Telecom Slave Analysis parameters when creating or editing a Telecom Salve Analysis
entity are explained in this table.

For more information on Telecom Slave Analysis, see Clock Analysis —

Telecom Slave Score.

Table 84: Edit Telecom Slave Analysis Parameters

Description / Option Settings /
Parameter
Applicable Rules Defaults

Frequency Drop-down list to select the applicable frequency G823-PDH-Traffic

Recovery Target recovery target. G823-PDH-Sync
G8261.1-Output-
Wander
Phase Recovery Enter the applicable phase recovery target. Range is 500
Target from 1 to 100,000 nanoseconds. Default is 500.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 394

Oscilloquartz: An ADVA Company

PTP Network Analysis Parameters

The PTP Network Analysis parameters when creating or editing a PTP network probe are
explained in this table.

For more information on PTP network analysis, see Performing PTP

Network Analysis.

Table 85: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

PTP Probe Index PTP Probe Index. Number is automatically 1-32

(Create only) indexed, but is user editable.
Name A text and/or number string the user 1 to 15 characters
enters to uniquely identify this entity. This (blank)
string can be up to 15 printable ASCII
characters long.
PTP Flowpoint Identifies the PTP Flowpoint used by the (drop-down list of
PTP Clock Probe. A drop-down list of the provisioned PTP
provisioned flow points available for use is Flow points)
provided
IP Version Defines the PTP Clock Probe as using IPv4. IPv4
Master IP Address Entry for the IP address of the Master 0.0.0.0
Clock. Entry is a valid IPv4 or IPv6 address
according to the IP Version entry.
Slave IP Address Entry for the IP address of the Slave Clock. 0.0.0.0
Entry is a valid IPv4 or IPv6 address
according to the IP Version entry.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 395

Oscilloquartz: An ADVA Company

Table 85: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

Reference Defines the reference source for the PTP CLK-1-1-1-1

Network Probe. References available are CLK-1-1-1-2
presented in a drop-down list.
SYNC-1-1-1-1
BITS IN-1-1-1-1
TS-1-1
PPS-1-1-1-1
PPS-1-1-1-2
ACCESS PORT-1-
1-1-1
ACCESS PORT-1-
1-1-2
NETWORK PORT-
1-1-1-1
NETWORK PORT-
1-1-1-2
TIME CLOCK-1-1-
1-1
GPS-1-1-1-1
PTP CLOCK-1-1
Reference Expected Defines the expected Quality Level of the QL-NONE
QL selected reference for the PTP Network QL-PRC
Probe. Available QL levels are presented in
QL-SSU-A
a drop-down list.
QL-SSU-B
QL-EEC1
RPDV fw Low (ns) Residual Packet Delay Variation (RPDV), 1 - 4294967295
forward, low (in nanoseconds).
200
RPDV fw Medium Residual Packet Delay Variation, forward, 1 - 4294967295
(ns) medium (in nanoseconds). Must be higher
500
than the RPDV fw Low setting and lower
than the RPDV fw High setting.
RPDV fw High (ns) Residual Packet Delay Variation, forward, 1 - 4294967295
high (in nanoseconds).
2000

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 396

Oscilloquartz: An ADVA Company

Table 85: Create/Edit PTP Clock Probe Parameter Settings

Description / Option Settings
Parameter
Applicable Rules / Defaults

RPDV rev Low (ns) Residual Packet Delay Variation, reverse, 1 - 4294967295
low (in nanoseconds).
200
RPDV rev Medium Residual Packet Delay Variation, reverse, 1 - 4294967295
(ns) medium (in nanoseconds). Must be higher
500
than the RPDV rev Low setting and lower
than the RPDV rev High setting.
RPDV rev High (ns) Residual Packet Delay Variation, reverse, 1 - 4294967295
high (in nanoseconds).
2000

FPP Cluster Range - Packet Delay Variation Assured (in 1 - 4294967295

Assured (ns) nanoseconds)
25000
FPP Cluster Range - Packet Delay Variation Satisfied (in 1 - 4294967295
Satisfied (ns) nanoseconds)
150000

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 397

Oscilloquartz: An ADVA Company

Scheduled Syncjack Activity Settings

The scheduled Syncjack activity settings when creating or editing a Syncjack schedule are
explained in this table. Up to 10 Syncjack schedules can created.

For more information on creating Syncjack schedules, see these sections:

l Performing Clock Accuracy Testing

l Performing Clock Analysis
l Performing PTP Network Analysis.

Table 86: Syncjack Schedule Configuration Settings

Option Settings /
Parameter Description / Applicable Rules
Defaults
Identification
Schedule Index An Identifier value used to uniquely 1-255
identify this Syncjack Schedule.
(Create Schedule only)

Activity ID Activity identifier (1 to 15 ASCII up to 15 characters

characters). This is a user specified (blank)
unique identifier associated with a
Probe, and is not a mandatory entry.
Schedule Parameters
Schedule Type Define schedule type as a one time or One Shot
periodic execution. The current release
only supports One Shot scheduling.
Start Time Buttons Activate either an immediate Syncjack Now
or future (scheduled) Syncjack. Future
Periodic Interval Specifies the interval between Range 1 to
(secs) subsequent runs (in seconds). This 2147483647
option is only available if Schedule Type
(future)
of Periodic is selected. This option is not
available in the current release.
Duration Buttons Define the duration as continuous or a Forever
fixed time (in seconds). Only applicable
if Schedule Type of One Shot is Fixed
selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 398

Oscilloquartz: An ADVA Company

Table 86: Syncjack Schedule Configuration Settings

Option Settings /
Parameter Description / Applicable Rules
Defaults
Define the duration in seconds. Valid 0 to 9999 (One Shot)
entries are 0 (continuous) through 9999
Duration (secs) 60 to 9999 (Periodic)
(seconds) if Schedule Type of One Shot
Entry Window
is selected, and valid entries are 60
through 9999 (seconds) if 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 yyyy-mm-dd
Windows the time. When cursor is placed in data
entry window and mouse click is
entered, a calendar selection appears,
allowing date selection. 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 hh:mm:ss
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 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 SJ Test Selects the Probes that belong to this Any available probes
Items Syncjack schedule. To add a Probe, will be displayed in
select a Probe from the Schedule the Schedule SJ test
Probes list. Multiple Probes may be Items list as a
selected. Probes may be de-selected by checkbox selection
clicking on the Probe once again before
hitting the OK button. Only previously
created Probes that are not used for
another Scheduled 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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 399

Oscilloquartz: An ADVA Company

Result Analysis Parameters

The result analysis parameters when performing a MTIE Result Comparison are explained in
this section.

For more information on performing a MTIE result comparison, see

Performing an MTIE Result Comparison.

Table 87: Configure MTIE Comparison Analysis

Description / Option Settings /
Parameter
Applicable Rules Defaults

MTIE Mask Define the predefined MTIE Mask to use for G823 E1 Ssu
measurements. Choices are presented in a drop- G823 E1 Sec
down list.
G823 E1 Traffic
G823 Pdh
G824 T1 Sync
G824 T1 Traffic
G8261 E1 Case 1
G8261 T1 Case 1
G8261 E1 Case 2
G8261 EEC Opt1
G8263
G8263 temp
G8272 PRTC
G8261 1
G8262 EEC Opt1
G8262 EEC Opt1
temp
G8262 EEC Opt2
G8262 EEC Opt1
Tolerance
Test Result Selects the Probes that have been previously Any available
Entity Checkbox scheduled. To add a Probe, select a Probe from the probes will be
Test Result Entity list. Multiple Probes (up to 4) may displayed in the
be selected. Test Result list as a
checkbox selection

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 400

Oscilloquartz: An ADVA Company

Raw Data Collection Parameters

The raw data collection parameters when provisioning the raw data collection server are
explained in this section.

For more information on how to provision the raw data collection server,
see Provisioning Raw Data Collection.

Table 88: Raw Data Collection Parameters

Description / Option Settings
Parameter
Applicable Rules / Defaults

File Transfer Drop-down list to select the desired File Transfer FTP
Method Method. The desired protocol must be enabled
SCP
at the System level (see System Configuration
Options and Rules). SFTP
Server IP The IP Address of the Raw Data Server. 0.0.0.0
User ID The User ID of the Raw Data Server. (empty)
User Password The User Password of the Raw Data Server. (empty)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 401

 Chapter C

Maintenance Operations
This section includes these topics:

Modifying Default Alarms Notification Codes 402

Pinging an IP Address 403
Implementing Traceroute 405
Flushing the ARP Cache 406
Flushing the NDP Cache 407
Managing Database and Configuration Files 408

Modifying Default Alarms Notification

Codes
You can edit the default alarms notification codes (NC) for an alarm condition type.

To modify the notification codes:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the tree pane, expand System>Alarm Attributes, right-click an element and select
Edit Alarm Attributes.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 402

Oscilloquartz: An ADVA Company Maintenance Operations

3. Under the NC column, select the required notification for each alarm you want to
change. The notification code options include:
o CR — Critical. A severe, service-affecting condition has occurred and that immediate

corrective action is imperative.

o MJ — Major. A serious disruption of service or a malfunction or failure of an
important system function.
o MN — Minor. An issue that does not have a serious effect on service to customers
or for trouble in functions that are not essential to the NE operation.
o NA — Not Alarmed. A condition that is reported only as an event and can be
retrieved from the system.
o NR — Not Reported. A condition that is not reported but can be retrieved from the
system.
4. Click OK to save changes.

Pinging an IP Address
For any IPv4 or IPv6 address, you can ping the IP network to test the communication with a
host. You can also ping a DCN (eth0) port.

When you ping IPv6 addresses in-band management is not included.

To ping an IP address:

1. In the Maintenance view, right-click the System>Communications entities, and select

Ping. The Ping window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 403

Oscilloquartz: An ADVA Company Maintenance Operations

2. Set these options:

Field Description
IP Address Select the type of IP address that you want to test (default IPv4)
and enter the address in the applicable format.
Link-Local Addr IPv6 only. Leave this option selected if the IPv6 address is linked
to a local address.
Other Addr IPv6 only. Leave this option selected if the IPv6 address is linked
to another address that is not local.
Interface Name Select the applicable PTP interface. When you enable
management traffic bridging only eth0 is possible for Interface
Name. To enable Management Traffic Bridging, see Configuring
the System Identity and Configuration.

The system supports ping only to PTP IPv6 interfaces. You cannot ping
IPv6 multicast addresses that begin with FF, local link, or unique local link
address.

3. Click OK.
The Last Ping tab displays the progress of the ping operation. This figure displays the
output when you ping an IPv4 address.

4. Select the Last Ping tab to refresh the results.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 404

Oscilloquartz: An ADVA Company Maintenance Operations

The Last Ping tab displays the results of the test.

Implementing Traceroute
You can traceroute an IPv4 or a management IPv6 address to display the path and measure
the transit delays of packets across the IP network. You can also traceroute a DCN (eth0)
port.

To traceroute an IP address:

1. In the Maintenance view, expand System, right-click Communications, and select

Trace Route. The Trace Route window opens.

2. Select the type of IP Address that you want to traceroute (default IPv4) and enter the
address in the applicable format.

You can traceroute only management IPv6 addresses.

3. Click OK.
The Last Trace Route tab displays the traceroute operation progress. This figure shows
the output when you traceroute an IPv4 address.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 405

Oscilloquartz: An ADVA Company Maintenance Operations

4. Click the Last Trace Route tab to refresh the results.

Flushing the ARP Cache

Flush the ARP cache to delete dynamic ARP entries listed in the ARP entry table.

To flush the ARP cache:

1. In the Maintenance view, expand System, right-click Communications, and select

Flush ARP Cache. The Flush ARP Cache window opens.

2. Click OK.
The Routing Table tab along with other communications tab display the results, so you

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 406

Oscilloquartz: An ADVA Company Maintenance Operations

can verify that the entries have been deleted in the appropriate tabs.

Flushing the NDP Cache

Flush the NDP cache to delete the dynamic NDP entries listed in the NDP entry table.

To flush the NDP cache:

1. In the Maintenance view, expand System, right-click Communications, and select

Flush NDP Cache. The Flush NDP Cache window opens.

2. Click OK. The software deletes the entries.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 407

Oscilloquartz: An ADVA Company Maintenance Operations

Managing Database and Configuration

Files
There are two different ways to manage database files on the OSA 5422:

l Managing ICF Configuration Files (binary) using the web-based EMS, SNMP, and
CLI.
l Managing Configuration Files using CLI (text based) through the CLI and web-
based EMS.

These two types of files can be used in a complimentary fashion, or they can be used
independently. Each type of file and its use is described under the headings Managing ICF
Configuration Files and Managing Configuration Files using CLI.

There is a third type of Database File supported by the OSA 5422 called the Default Settings
File. This is an XML based file that changes the default settings applied when a new entity
(such as an EVPL Flow) is created. This file is downloaded and applied to the unit if the
factory default values are determined to be not applicable or unacceptable to the user’s
application. See Default Settings File.

A configuration file can be created ONLY after software has been com-
pletely downloaded.

If you are using Internet Explorer 8, to view certain web-based EMS elements correctly,
specifically data provided in the Maintenance View, such as Restore factory defaults,
Restore system defaults, Restore database, and New System Defaults File, enable
Compatibility View in IE. This is performed by selecting Tools, Compatibility View Settings,
and adding the OSA 5422 IP address to the list of websites data field.

Database and configuration files are managed in the Maintenance view. These options are
accessible in the web-based EMS by performing either of these tasks:

l On the toolbar, click the Maintenance icon.

– or –
l From the Application menu, select Maintenance.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 408

Oscilloquartz: An ADVA Company Maintenance Operations

Managing 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 OSA 5422 provides an easy means to manage
the binary database files using these configuration database management functions using
the web-based EMS:

l Creating a Backup Database

l Restoring a Database
l Setting a Default Database
l Restoring System Defaults
l Restoring Factory Defaults

Determining the Database Configuration Status

When the database of the OSA 5422 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 current copy should be the
default database for this unit, at which time the user should perform the Setting a Default
Database procedure. Then, if required the database can be restored to these settings by
performing the Restoring System Defaults procedure.

The Factory Default Database never changes, and as a last resort troubleshooting tool, or
upon decommissioning, the current database can be reset to factory defaults by performing
the Restoring Factory Defaults procedure.

The Default Database can also be reset to Factory Defaults using the “New” option in the
Setting a Default Database procedure. The difference is, when using the “New” option
selection, any user uploaded “Default Settings” will be erased.

To view the configuration database information in the Web Based EMS, select Maintenance
view, expand the Administration entity, and then select the Database entity. See Figure 12
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 409

Oscilloquartz: An ADVA Company Maintenance Operations

Figure 12: Database Status Display

Setting a 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 configuration has been provisioned.

The OSA 5422 permits the user to designate the current configuration as the Default
Database or to reset the Default Database to factory defaults using this procedure.

This procedure includes steps for setting a Default Database using the web-based EMS. It is
also possible to perform this process using the CLI. For more information, see the OSA 5422
CLI Guide.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see ).
3. Log in to the web-based EMS.

To set the current database as the default database:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Default Database, and then select Save.
The Save Configuration to System Defaults window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 410

Oscilloquartz: An ADVA Company Maintenance Operations

4. Click OK.

To copy the system default database to a remote site:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Default Database, and then select Copy to Remote.
The Copy System Default Database to Remote window opens.

4. To transfer the file using the web, perform these steps:

a. In the Method area, File Transfer Method menu, leave the Web option.
b. Click OK.
c. To receive the HTTP File Transfer, click the here link.
You are prompted to open or save the file.
The options presented for saving a file are dependent on the browse and the
settings configured. For example, MS Internet Explorer prompts you for file
name and the location to save the file; Firefox saves the file with the default file

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 411

Oscilloquartz: An ADVA Company Maintenance Operations

name to the computer desktop.

A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully downloaded to the
system. With this configuration, the system logs may indicate successful file
download, when the browser has not properly saved the file. The file may be
successfully downloaded and saved by disabling either the File Download
Prompting or pop-up blocking, or using the browser’s pop-up override
capability to allow the file save to complete.

5. To transfer the file using FTP, SCP, or SFTP, perform these steps:

a. In the Method area, File Transfer Method menu, select either FTP, SFTP, or
SCP.
The window opens with a File Transfer area, which is identical for each
selection. This example figure displays the window contents when SCP is
selected.

b. Set the file transfer options required to access the FTP, SFTP, or SCP server:

Field Setting
Server IP Select the type of server IP as either:

l IPv4
– or –
l IPv6

The default is IPv4.

In the field, enter the server IP address.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 412

Oscilloquartz: An ADVA Company Maintenance Operations

Field Setting
User ID Enter the User ID to access the server.
User Password Enter the password to access the server.
Remote File Enter the name of the log including the complete file path that
you want to transfer.

c. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from In Progress to Success, the file has been
transferred.

To copy a default database from a remote site:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Default Database, and then select Copy from Remote.
The Copy System Default Database From Remote window opens.

4. To transfer the file using the web, perform these steps:

a. In the Method area, File Transfer Method menu, leave the Web option
selected.
b. In the HTTP Transfer area, Remote File field, enter the path to the remote file
to restore, or browse to the file location, then click OK.
The file is copied from the source location and the Detail Pane indicates when
the file transfer is 100% complete.

c. To transfer the file using FTP, SCP, or SFTP, perform these steps:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 413

Oscilloquartz: An ADVA Company Maintenance Operations

a. In the Method area, File Transfer Method menu, select either FTP, SFTP, or
SCP.
The window opens with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is
selected.

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.

Field Setting
Server IP Select the type of server IP as either:

l IPv4
– or –
l IPv6

The default is IPv4.

In the field, enter the server IP address.
User ID Enter the User ID to access the server.
User Password Enter the password to access the server.
Remote File Enter the name of the log including the complete file path that
you want to transfer.

c. Click OK.
The file transfer begins, and is indicated in the window.
The file is copied from the source location and the Detail Pane indicates when
the file transfer is 100% complete.

To reset the default database to factory defaults:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 414

Oscilloquartz: An ADVA Company Maintenance Operations

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Default Database, and then select New.
The New System Defaults File window opens.

Resetting the database to factory defaults drops all traffic and erases all
communications and user settings, including the loss of the Web Based
EMS connection to the NE. When using the New option selection, any
user uploaded Default Settings are erased. It may be advisable to backup
the current database so that it can be restored later.

3. Click OK.
The System resets the Default Database and Active Database to Factory Defaults.

Creating a Backup Database

Backing up the system database is a two-step process:

1. Transferring the database to a temporary location on the NE.

2. Transferring the database file to a remote repository. The NE supports a transfer using
HTTPS (Web), FTP, SFTP, and SCP protocols.

You can also backup the database using the CLI. For more information, see
the OSA 5422 Command Line Reference Guide.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see ).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 415

Oscilloquartz: An ADVA Company Maintenance Operations

3. Log in using the web-based EMS.

To create a backup database:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Database, and then select Backup Database.
The Backup Database window opens.

4. Click OK.
5. In the tree selection pane, right-click Database, and then select Copy to Remote.
The Copy Database to Remote window opens.

6. To copy the file using the web, perform these steps:

a. In the Method area, File Transfer Method menu, leave the Web option
selected.
b. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 416

Oscilloquartz: An ADVA Company Maintenance Operations

c. To receive the HTTP File Transfer, click the here link.

You are prompted to open or save the file.
The options presented for saving a file are dependent on the browse and the
settings configured. For example, MS Internet Explorer prompts you for file
name and the location to save the file; Firefox saves the file with the default file
name to the computer desktop.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully downloaded to the
system. With this configuration, the system logs may indicate successful file
download, when the browser has not properly saved the file. The file may be
successfully downloaded and saved by disabling either the File Download
Prompting or pop-up blocking, or using the browser’s pop-up override
capability to allow the file save to complete.

7. To transfer the file using FTP, SCP, or SFTP, perform these steps:

a. In the Method area, File Transfer Method menu, select either FTP, SFTP, or
SCP.
The window opens with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is
selected.

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 417

Oscilloquartz: An ADVA Company Maintenance Operations

Field Setting
Server IP Select the type of server IP as either:

l IPv4
– or –
l IPv6

The default is IPv4.

In the field, enter the server IP address.
User ID Enter the User ID to access the server.
User Password Enter the password to access the server.
Remote File Enter the name of the log including the complete file path that
you want to transfer.

c. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the file has been
transferred.

Restoring a Database
Restoring the database is a multi-step process:

1. Transfer the database file from an external repository to a temporary location on the NE.
The NE supports transfer through HTTP (Web), FTP, SFTP and SCP protocols.
2. Transfer the database file to standby memory on the NE.

3. Activate the database, which causes the NE to reset and temporarily interrupt traffic, and
cancel active user sessions.

You can also restore the database using the CLI. For more information, see the OSA 5422
CLI Reference Guide.

Prerequisites
1. Configure the NE with an IP address.
2. Connect the NE to a DCN or LAN (see ).
3. Log in to the web-based EMS.

To restore the database:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 418

Oscilloquartz: An ADVA Company Maintenance Operations

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System>Administration entities, click +.
3. Right-click Database, and then select Copy from Remote.
The Copy From Remote window opens.

4. To transfer the file using the web, perform these steps:

a. In the Method area, File Transfer Method menu, leave the Web option
selected.
b. In the HTTP Transfer area, Remote File field, enter the path to the remote file
to restore, or browse to the file location, then click OK.
The file is copied from the source location and the Detail Pane indicates when
the file transfer is 100% complete.

5. To transfer the file using FTP, SCP, or SFTP, perform these steps:

a. In the Method area, File Transfer Method menu, select either FTP, SFTP, or
SCP.
The window opens with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is
selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 419

Oscilloquartz: An ADVA Company Maintenance Operations

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.

Field Setting
Server IP Select the type of server IP as either:

l IPv4
– or –
l IPv6

The default is IPv4.

In the field, enter the server IP address.
User ID Enter the User ID to access the server.
User Password Enter the password to access the server.
Remote File Enter the name of the log including the complete file path that
you want to transfer.

c. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the file transfer is
complete.

6. In the selection tree, right-click Database, and then select Restore Database. The
Restore Database window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 420

Oscilloquartz: An ADVA Company Maintenance Operations

7. Click OK.
A progress bar is displayed in the window.
8. When the restore completes, in the selection tree, right-click Database, and then select
Activate Database.
The Activate Standby Database window opens.

9. To accept the restored database, click OK.

The NE restarts.

When restoring a database taken from a different unit (for example, if

you are replacing a failed unit with another unit and restoring a database
backup from the first unit), the original SNMP engine ID (snmpEngineId)
of the unit is preserved. This ensures that the configured USM auth and
priv keys remain valid. If the snmpEngineId is edited, the USM auth and
priv keys automatically reset to ChgMeNOW and needs to be changed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 421

Oscilloquartz: An ADVA Company Maintenance Operations

Restoring System Defaults

There are two types of database resets available in the OSA 5422:

l Restore System Defaults

l Restore Factory Defaults.

The difference between System Defaults and Factory Defaults is explained in Determining
the Database Configuration Status.

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 decommissioned and moved to a new location or when the software or
database is corrupted. It is advisable to backup the database before performing this
procedure.

Prerequisites
1. Configured the NE with an IP address.
2. Connected the NE to a DCN or LAN (see ).
3. Logged in to the web-based EMS.

To restore system defaults:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System entity, click +.
3. Right-click Administration, and then select Restore System Defaults.
The Restore System Defaults window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 422

Oscilloquartz: An ADVA Company Maintenance Operations

Resetting the database to system defaults may drop all traffic and erase
all communications and user settings, including the loss of the web-
based EMS connection to the NE. It may be advisable to backup the
current database so that it can be restored later.

4. To reset the system database to the factory defaults, click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 423

Oscilloquartz: An ADVA Company Maintenance Operations

Restoring Factory Defaults

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
corrupted. It is advisable to backup the database before performing this procedure.

There are two types of database resets available on the OSA 5422:

l Restore System Defaults.

l Restore Factory Defaults.

The difference between System Defaults and Factory Defaults is explained in Determining
the Database Configuration Status.

Prerequisites
1. Configured the NE with an IP address.
2. Connected the NE to a DCN or LAN (see ).
3. Logged in to the web-based EMS.

To restore factory defaults:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. In the selection tree, next to the System entity, click +.
3. Right-click Administration, and then select Restore Factory Defaults.
The Restore Factory Defaults window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 424

Oscilloquartz: An ADVA Company Maintenance Operations

Resetting the database to factory defaults drops all traffic and erases all
communications and user settings, including the loss of the web-based
EMS connection to the NE. We recommend to backup the current
database so that it can be restored later, if needed.

3. To reset the current database to the factory defaults, click OK.

Managing Configuration Files using CLI

In addition to the ICF database files (see Managing Database and Configuration Files), the
system also supports text based configuration files based on the output from the CLI
command:

show running config

You use the configuration files to configure new installed systems, transition from an
installation network to the traffic-carrying network, or to provision a system following a
restore operation.

The system supports up to five configuration files in persistent memory. You can operate
configuration files using CLI commands or the web EMS.

Configuration files remain in memory following restore operations. So that

If you marked a configuration file to load after a reboot, it may change the
configuration again immediately following the restore operation.

The CLI commands to operate configuration files include:

l Entering or Editing Description (description)

l Listing Configuration Files (list)
l Running a Configuration File (load)
l Deleting a Configuration File (remove)
l Forcing System Reset (Restart-with-configfile)
l Save
l Viewing Configuration File (show ConfigFile)
l Transferring a File (transfer-file)

For more information about these commands, see the OSA 5422 CLI Refer-
ence Guide

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 425

Oscilloquartz: An ADVA Company Maintenance Operations

Transferring a File (transfer-file)

You can export or import a configuration file using 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.

Listing Configuration Files (list)

You can list all the configuration files using the list command, as in:
ADVA:config-file--> list
|File Name |Description
|--------------------------------|---------------|
|configfile2 |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.

Forcing System Reset (Restart-with-configfile)

The restart-with-configfile command is used to force an immediate system reset,
then execute the designated configfile. The basic command is:

ADVA:config-file--> restart-with-configfile configfile4 yes

ADVA:config-file-->
U-Boot 2017.03-14408 (Jan 13 2018 - 14:21:19) MPC83XX

Running a Configuration File (load)

You can run a configuration file now using the load command, as in:

ADVA:config-file--> load configfile4

ADVA:config-file-->

Viewing Configuration File (show ConfigFile)

You can view the contents of a configuration file using the show ConfigFile command,
as in:
ADVA:config-file--> show configfile configfile4

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 426

Oscilloquartz: An ADVA Company Maintenance Operations

File Name : configfile4

Description :
Context : below

# DO NOT EDIT THIS LINE. FILE_TYPE=CONFIGURATION_FILE

#
#CLI:ACCESS PORT-1-1-1-1 Edit
#
home
network-element ne-1
configure nte nteosa5422-1-1-1-1
configure access-port access-1-1-1-1

#
#CLI:FLOW-1-1-1-6-1 Create
#
home
network-element ne-1
configure nte nteosa5422-1-1-1-1
configure access-port access-1-1-1-1

#end
home
admin config-file
ADVA:config-file-->

Entering or Editing Description (description)

You can enter or edit the description of a configuration file using the description
command, as in:

description <configfile-name> <description>

The description can be up to 127 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"
ADVA:config-file--> list
|File Name |Description
|-------------------------|----------------------|
|configfile2 |root
|configfile3 |
|configfile4 |set access6 to EVPL and create a flow
ADVA:config-file-->

Deleting a Configuration File (remove)

You can delete a configuration file using the remove command, as in:

remove <configfile-name>

Example:
ADVA:config-file--> remove configfile2
ADVA:config-file--> list
|File Name |Description

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 427

Oscilloquartz: An ADVA Company Maintenance Operations

|-------------------------|----------------------|
|configfile3 |
|configfile4 |set access1 to EVPL and create a flow
ADVA:config-file-->

Managing Configuration Files using Web EMS

Prerequisites to all configuration file tasks are:

1. Configure the NE with an IP address and connected the NE to a DCN or LAN (see ).
2. Log in using the web-based EMS.
3. On the toolbar, click the Maintenance, or from the Application menu, select
Maintenance.
4. In the tree pane, expand System > Administration.
Configuration files tasks:

Task Link
Create a new configuration file. Creating a New Configuration File
Update an existing configuration file. Updating an Existing Configuration File
List/check status of the configuration Verifying the Status of the Configuration Files
files.
Restart the system with a Restarting the System with a Configuration File
configuration file.
Import a configuration file. Importing a Configuration File
Export a configuration file. Exporting a Configuration File
Edit the description of a configuration Editing the Description of a Configuration File
file.
Delete a configuration file. Deleting a Configuration File
Done working with configuration files. If configuration changes were implemented
using the tasks in this table, verify the changes,
then save the configuration using the Creating
a Backup Database procedure.

Creating a New Configuration File

To create a new configuration file:

1. In the selection tree, right-click the Configuration Files entity, and then select Create.
The Create Configuration Files window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 428

Oscilloquartz: An ADVA Company Maintenance Operations

2. In the File Name field, enter the applicable file name with no spaces or slashes (/).
3. Select OK. The configuration file contains the delta between the default database and
the current active database.
4. Click the Configuration Files entity to view the configuration file status.

Updating an Existing Configuration File

To update the existing configuration file:

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 429

Oscilloquartz: An ADVA Company Maintenance Operations

2. In the Files table, right-click the configuration file that you want to update, and then
select Save.
The configuration file is updated and contains the delta between the default database
and the current active database, and overwrites the existing file.

Verifying the Status of the Configuration Files

To verify the status of the configuration files:

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

2. In the Status area, verify the status of the configuration files.

3. In the Files table, verify the details of the existing configuration files including the file
name and description (if any).

Restarting the System with a Configuration File

To restart the system with a configuration file:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 430

Oscilloquartz: An ADVA Company Maintenance Operations

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

2. In the Files table, right-click the configuration file that you want to run when the system
is restarted, and then select Restart with File.
The device restarts with the selected configuration file.

Importing a Configuration File

To import a configuration file:

1. In the selection tree, right-click the Configuration Files entity, and then select Copy
from Remote. The Copy Configuration File From Remote window opens.

2. To import the file using the web, perform these steps:

a. In the Method area, File Transfer Method menu, leave the Web option
selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 431

Oscilloquartz: An ADVA Company Maintenance Operations

b. In the HTTP Transfer area, Remote File field, enter the path to the remote file
to restore, or browse to the file location, then click OK.
The file is copied from the source location and the Detail Pane indicates when
the file transfer is 100% complete.

3. To transfer the file using FTP, SCP, or SFTP, perform these steps:

a. In the Method area, File Transfer Methodmenu, select either FTP, SFTP, or
SCP.
The window opens with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is
selected.

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.

Field Setting
Server IP Select the type of server IP as either:

l IPv4
– or –
l IPv6

The default is IPv4.

In the field, enter the server IP address.
User ID Enter the User ID to access the server.
User Password Enter the password to access the server.
Remote File Enter the name of the log including the complete file path that
you want to transfer.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 432

Oscilloquartz: An ADVA Company Maintenance Operations

c. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the file transfer is
complete.

Exporting a Configuration File

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

2. In the Files table, right-click the configuration file that you want to export, and then
select Copy to Remote. The Copy Configuration File to Remote window opens.

3. To copy the file using the web, in the Method area, File Transfer Method menu, leave
the Web option selected, and continue to step #5.

4. To copy files using FTP, SFTP, or SCP, follow these steps:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 433

Oscilloquartz: An ADVA Company Maintenance Operations

a. In the Method area, File Transfer Method menu, select one of these options:
FTP, SFTP, or SCP.
The window displays with a File Transfer area, which is identical for each
selection. This example illustration displays the window contents when SCP is
selected.

b. In the File transfer area, set the file transfer options required to access the FTP,
SFTP, or SCP server:

Field Setting
Server IP a. From the menu, select the applicable server IP as either:
IPv4
– or –
IPv6.
The default is IPv4.
b. In the field, enter the applicable server IP address.
User ID Enter the applicable User ID to access the server.
User Password Enter the applicable password to access the server.
Path Enter the file path where to export the file.

5. Click OK.
The export begins. When the Status changes from In Progress to Success, the file has
been exported.

Editing the Description of a Configuration File

To edit the description of a configuration file:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 434

Oscilloquartz: An ADVA Company Maintenance Operations

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

2. In the Files table, right-click the configuration file with the description you want to edit,
and then select Edit Description. The Edit File Description dialog box is displayed.

3. In the Description field, enter the description for the file of up to 127 ASCII characters
with no spaces or slashes (/).
4. Click OK.
In the Files table, the description is updated.

Deleting a Configuration File

To delete a configuration file:

1. In the selection tree, click the Configuration Files entity. The Configuration Files
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 435

Oscilloquartz: An ADVA Company Maintenance Operations

2. In the Files table, right-click the configuration file that you want to run when the system
is restarted, and then select Remove. The configuration file is deleted from the table.

Default Settings File

Installing a default settings file changes the settings applied when a new entity or object is
created. The factory default settings were carefully vetted to avoid potential conflicts.

If you determine that the default settings applied when a new entity is created are not
applicable or unacceptable, you can download an XML file containing alternate settings and
apply it to the OSA 5422.

This procedure should only be performed by well-trained personnel with a

file that was tested in a lab to ensure proper operation. Changes in the
factory default settings may result in corruption of the database or inability
to work with certain object.

The restore factory defaults function erases any user defined default
settings.

Prerequisites
1. Configure the NE with an IP address and connected the NE to a DCN or LAN (see ).
2. Log in to the web-based EMS.

To install the Default Settings Value file:

1. On the toolbar, click Maintenance, or from the Application menu, select Maintenance.
2. Expand System > Administration, and select Default Settings.
The Copy System Default Settings From Remote window displays.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 436

Oscilloquartz: An ADVA Company Maintenance Operations

3. To transfer the file using the web:

a. Leave the File Transfer Method set to Web
b. Enter the path to the Remote File to copy, or browse to the file location, then click
OK.
The file is copied from the source location and the Detail Pane indicates when the file
transfer is 100% complete.
4. To transfer the file using FTP, SCP, or SFTP:
a. In the File Transfer Method drop-down menu, select either FTP, SFTP, or SCP.
The window displays with a File Transfer section, which is identical for each
selection.

b. In the File Transfer area, set these options, which are required to access the FTP,
SFTP, or SCP server.
l Server IP: Select the type of server IP as either IPv4 (default) or IPv6, and in
the field enter the server IP address.
l User ID: Enter the User ID to access the server.
l User Password: Enter the password to access the server.
l Remote File: Enter the name of the file including the complete file path that
you want to transfer.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 437

Oscilloquartz: An ADVA Company Maintenance Operations

c. Click OK. The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the file transfer is complete.

Viewing and Transferring the Last Reset Cause

You can view information about the Last Reset Type and Last Reset Cause from the
database along with identifiers for up to three debug files (if any exist). You can also transfer
these reset debug files.

These tasks are performed in the Maintenance view, which is accessible by either clicking
the Maintenance icon on the toolbar, or from the Application drop-down menu, selecting
Maintenance.

To view the last reset cause information:

In the Maintenance view, expand System >Administration, and select Last Reset Cause.
The Last Reset Cause window displays with the last reset cause information.

To transfer the last reset cause debug files:

1. In the Maintenance view, expand System>Administration, right-click Last Reset

Cause, and select Copy to Remote.
The Transfer Reset Files window displays.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 438

Oscilloquartz: An ADVA Company Maintenance Operations

2. To transfer the file using the web, perform these steps:

a. Leave the File Transfer Method set to Web.

b. Click OK.
c. To receive the HTTP File Transfer, click the here link.
You are prompted to open or save the file.
The options presented for saving a file are dependent on the browse and the
settings configured. For example, MS Internet Explorer prompts you for file
name and the location to save the file; Firefox saves the file with the default file
name to the computer desktop.
A browser with File Download Prompting enabled and pop-up blocking
enabled may not allow a transferred file to be successfully downloaded to the
system. With this configuration, the system logs may indicate successful file
download, when the browser has not properly saved the file. The file may be
successfully downloaded and saved by disabling either the File Download
Prompting or pop-up blocking, or using the browser’s pop-up override
capability to allow the file save to complete.

3. To transfer the file using FTP, SCP, or SFTP, perform these steps:
a. In the File Transfer Method drop-down menu, select either FTP, SFTP, or SCP.
The window displays with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 439

Oscilloquartz: An ADVA Company Maintenance Operations

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.
o Server IP: Select the type of server IP as either IPv4 (default) or IPv6, and in the

field enter the server IP address.

o User ID: Enter the User ID to access the server.
o User Password: Enter the password to access the server.
o Remote File: Enter the name of the log including the complete file path that you
want to transfer.
c. Click OK. The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the file has been transferred.

Bulk Log Transfer

The Audit Log, Alarm Log, and Security Log can be bulk transferred to a remote repository.
The NE supports transfer using HTTPS (Web), FTP, SFTP, and SCP protocols. Transferring the
Security Log requires the user to have Superuser access.

This task is performed in the Maintenance view, which is accessible by either clicking the
Maintenance icon on the toolbar, or from the Application drop-down menu, selecting
Maintenance.

Prerequisites
1. Configure the NE with an IP address and connected the NE to a DCN or LAN (see ).
2. Log in to the web-based EMS.

To perform a web bulk log transfer:

1. In the Maintenance view, expand System>Administration, right-click Transfer Log,

and then select the particular log file to transfer: Transfer Alarm Log, Transfer Audit
Log, or Transfer Security Log.
The window contents that displays is the same for each log except for the name of the

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 440

Oscilloquartz: An ADVA Company Maintenance Operations

window. The Transfer Alarm Log window is provided as an example, and used in the
subsequent steps. These steps can be used for each log.

2. In the File Transfer Method drop-down menu, select Web.

3. Click OK.
You are prompted to open or save the file.
The options presented for saving a file are dependent on the browse and the settings
configured. For example, MS Internet Explorer prompts you for file name and the
location to save the file; Firefox saves the file with the default file name to the computer
desktop.
A browser with File Download Prompting enabled and pop-up blocking enabled may
not allow a transferred file to be successfully downloaded to the system. With this
configuration, the system logs may indicate successful file download, when the browser
has not properly saved the file. The file may be successfully downloaded and saved by
disabling either the File Download Prompting or pop-up blocking, or using the
browser’s pop-up override capability to allow the file save to complete.

To perform a FTP, SFTP, or SCP bulk log transfer:

1. In the Maintenance view, expand System>Administration, right-click Transfer Log,

and select the particular log file to transfer: Transfer Alarm Log, Transfer Audit Log, or
Transfer Security Log.
The window contents that displays is the same for each log except for the name of the
window. The Transfer Alarm Log window is provided as an example, and used in the
subsequent steps. These steps can be used for each log.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 441

Oscilloquartz: An ADVA Company Maintenance Operations

2. In the File Transfer Method drop-down menu, select either FTP, SFTP, or SCP.
The window displays with a File Transfer section, which is identical for each selection.
This example figure displays the window contents when SCP is selected.

3. Set the file transfer options required to access the FTP, SFTP, or SCP server:

l Server IP: Select the type of server IP as either IPv4 (default) or IPv6, and
in the field enter the server IP address.

l User ID: Enter the User ID to access the server.

l User Password: Enter the password to access the server.
l Remote File: Enter the name of the log including the complete file path
that you want to transfer.

4. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from In Progress to Success, the file has been transferred.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 442

Oscilloquartz: An ADVA Company Maintenance Operations

Managing Diagnostics Files

Diagnostic files are helpful when you need assistance troubleshooting your device. These
files contain specific information about your setup, which you can send to ADVA Customer
Support to troubleshoot your problem. You can save the diagnostic files as a zipped file and
then copy these files to a remote repository. Once the diagnostic files are saved, you can
view the file status and timestamp. Transferring diagnostic files requires Superuser access.

Diagnostic files include this data:

l System inventory information.

l System Field Replaceable Units including PSUs.
l Current versions of the software.
l Hardware
l FPGA and CPLD
l Running configuration file output.
l Current database
l Current alarms and conditions.
l All alarm logs, audit logs, and security logs generated or preserved since the
initialization of the system.

These transferring protocols are available:

l HTTPS (web)
l FTP
l SFTP
l SCP

Prerequisites
1. Configure the NE with an IP address and connect the NE to a DCN or LAN (see ).
2. Log in to the web-based EMS as a Superuser.

This section includes these tasks:

Saving Diagnostic Files 444

Copying Diagnostic Files to a Remote Repository 445

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 443

Oscilloquartz: An ADVA Company Maintenance Operations

Saving Diagnostic Files

You can save diagnostic files as a zipped file. Once the diagnostic files are saved, you can
view the file status and timestamp.

To save diagnostic files:

1. From the Maintenance view, in the selection tree, next to the System>Administration
entities, click +.
2. Right-click Diagnostics Files, and then click Save. The Save Diagnostics Files window
opens.

3. Click OK. The Save Diagnostics Files Progress window opens, which indicates the
status of the task.

When the files are saved successfully, the Save Diagnostics Files window is updated, as
shown in this image.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 444

Oscilloquartz: An ADVA Company Maintenance Operations

4. In the selection tree, select the Diagnostic Files entity to view the status and timestamp
of the diagnostic files.

Copying Diagnostic Files to a Remote Repository

Once the diagnostic files are saved, you can copy these files to a remote repository using
any of these transferring protocols:

l HTTPS (web)
l FTP
l SFTP
l SCP

To copy diagnostic files to a remote repository:

1. From the Maintenance view, in the selection tree, next to the System>Administration
entities, click +.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 445

Oscilloquartz: An ADVA Company Maintenance Operations

2. Right-click Diagnostics Files, and then click Copy to Remote. The Transfer
Diagnostics Files window opens.

3. To transfer the file using the web, perform these steps:

a. In the Method area, leave the File Transfer Method field set to Web.
b. Click OK.
A dialog box is displayed at the bottom of the window. The options presented for file
saving are dependent on the browser you are using and the options you have set for
the browser.

A browser that blocks pop-ups can prevent the diagnostics files from
being successfully downloaded to the system. The system logs can
indicate a successful file download, when the browser has not properly
saved the file. We recommend to disable pop-up blocking or use the
browser’s pop-up override.

c. Choose whether to open or save the files by clicking Open or Save. The files are
zipped to a file called diagnostics.
4. To transfer the file using FTP, SCP, or SFTP, perform these steps:
a. In the File Transfer Method drop-down menu, select either FTP, SFTP, or SCP.
The window displays with a File Transfer section, which is identical for each
selection. This example figure displays the window contents when SCP is selected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 446

Oscilloquartz: An ADVA Company Maintenance Operations

b. Set the file transfer options required to access the FTP, SFTP, or SCP server.
o Server IP: Select the type of server IP as either IPv4 (default) or IPv6, and in the
field enter the server IP address.
o User ID: Enter the User ID to access the server.
o User Password: Enter the password to access the server.
o Remote File: Enter the name of the log including the complete file path that you
want to transfer.
c. Click OK.
The file transfer begins, and is indicated in the window.
When the Status changes from Progress to Success, the files are transferred.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 447

 Chapter D

Performance Monitoring
This section contains information and procedures related to performance monitoring:

Monitoring Access Ports 448

Monitoring PTP 457

Monitoring Access Ports

Performance monitoring enables in-service, non-intrusive system monitoring to aid in
diagnosing and isolating issues that can occur during operation. Performance monitoring
enables you to detect and react to potential failures prior to a customer outage. In addition
to providing traditional SNMP MIB Etherstats, Syncjack® provides performance parameters
and features similar to those found in traditional services (see Syncjack Testing). This allows
Ethernet 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
performance monitoring thresholds. You can edit performance monitoring thresholds and
initialize registers (with a proper access permission level).

This section contains these step by step procedures:

l Configuring System Level Performance Monitoring

l Initializing Performance Monitoring Registers
l Editing Performance Monitoring Thresholds

For performance monitoring commands using the CLI, see the OSA 5422
Command Line Reference Guide.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 448

Oscilloquartz: An ADVA Company Performance Monitoring

Performance Monitoring Features

l Retrievable performance data for each managed entity, so the user can determine
past and current system operation. Performance monitoring data collection is
performed via a polling mechanism, were primitives are gathered into accumulated
counts. After a defined interval, such as 15 minutes or 1 day, the counts are binned
and stored in a database.
l Checking performance monitoring 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.

Performance monitoring supports:

l Threshold setting and automatic TCA message generation.

l Current and History performance monitoring bins provide a continuous record of
service performance, allowing for accurate SLA conformance statements.

Performance monitoring counts can be displayed as a summary or in tabular format in the

Web Based EMS, can be filtered and refreshed, and allows exporting data as Excel
spreadsheets.

Performance Parameters
The system collects performance parameters in several categories:

l Equipment presence and type, such as small form-factor pluggable (SFP) Interface
type and presence, module type, and presence.
l Physical Layer monitoring, such as optical power and temperature.
l Ethernet Statistics, such as the number of Ethernet packets received or transmitted.
l Protocol Statistics, such as the number of protocol dependent packets received or
transmitted.
l These entities are monitored for performance data which is accumulated into
performance parameters:
o Ethernet Access ports.

o Telecom Slave (TS)

o Slave Only Ordinary Clock (SOOC).
o PTP Port
o PTP Flow point.
o PTP Network Probe.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 449

Oscilloquartz: An ADVA Company Performance Monitoring

Performance Parameters Attributes

Each PP can be defined by the attributes outlined in this table.

Table 89: Performance Parameter Attributes

Attribute Description
Monitor Type The name of the PP. This is presented in mnemonic form, such as
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:

l Locally to the entity (or at the near end).

l 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 (15-Minute, 1-Day, or
Rollover).
Monitor Timestamp The time at which the PP was collected:

l The current time is used for Rollover and Current counters.

l The boundary crossing time is used for History counters (stored
as number of seconds since the Epoch).
History Index Indicates a bin from the historical list of bins:

l For 5 minute or 15 Minute history bins, this number is 1 to 32 (1

being the most recent).
l For 1 Day history bins, this number is 1.
l For current and Rollover bins, this number is 0.

Performance Parameters Counters

Each PP is grouped together for a monitored entity and accumulated into:

l Bins, associated with a predefined time period, such as 5-minutes, 15-Minutes, or

1-Day.
– or –
l Rollover Counters, for Ethernet managed entities only.

The user can reset any individual or all PP counters to zero.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 450

Oscilloquartz: An ADVA Company Performance Monitoring

Bins and Bin Periods

These performance bin periods will exist:

l 1 x Current 15-Minute or 5-Minute Bin.

l 1 x Current 1-Day (24-Hour) Bin.
l 32 x Historical 15-Minute or 5-Minute Bins.
l 1 x Historical 1-Day (24-Hour) Bin.

(1) The 32 Historical 15-Minute Bins provide the most recent 8 hours of performance data.

(2) The Historical 1-Day Bin provides the performance data from the previous day starting
from 12:00am, such as midnight, 00:00.

Rollover Counter
For Ethernet managed entities only, a Rollover Counter is provided. This gives the current
performance data since monitoring began. The counter accumulates until it reaches its
maximum size (64 bits). When this happens the counter will ‘roll over’ to zero and begin
again.

Unlike Bins, the Rollover Counter is not related to the time of day, but to system uptime.

Performance Parameters Thresholds

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 disables threshold monitoring for that entity.

Each Access Port and Flow 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.

Threshold Crossing Alert Messages

When a PP threshold has been met or exceeded, a TCA is generated. The following table
outlines the attributes that are specified in the TCA message.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 451

Oscilloquartz: An ADVA Company Performance Monitoring

Table 90: Threshold Crossing Alert Attributes

Attribute Description Values
Entity The monitored entity’s id. Variable.
Identifier
Monitor Type The name of the PP that has crossed its For Monitor Type
threshold. This will be presented in mnemonics, see
mnemonic form, such as ESF (EtherStat Monitored Types
Frames). and Default TCA
Settings .
Time Period In which time period the threshold was 15-Minute or
crossed. 5-Minute
1-Day
Time The time the threshold was crossed. Timestamp
Location The location of the TCA generation. This is Near end
determined in relation to the monitored
Far end
entity, in that the PP has occurred:
None
l Locally to the entity (or at the near end)
l Remotely to the entity (or at the far end).
Direction The direction in relation to the monitored Receive
entity.
Transmit
Monitored The value of the PP count when the threshold Up to a 64-bit
Value was crossed. number
Threshold The configured threshold at the time the Up to a 64-bit
Value threshold was crossed. number

Monitored Types and Default TCA Settings

For monitored types and default Threshold Crossing Alert (TCA) settings, see TCA
Monitored Types.

Configuring System Level Performance

Monitoring
The OSA 5422 allows you to configure the bin period for Performance Monitoring at the
system level.

To configure a system level performance monitoring:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 452

Oscilloquartz: An ADVA Company Performance Monitoring

1. Click PM, or from the Application menu, select Performance Monitoring.

2. In the tree pane, right-click the NE-1 entity, and then select Edit. The Edit PM
Configuration window opens.

3. In the Settings area, PM Interval menu, select the applicable performance monitoring
period.
4. Click OK.

Viewing performance monitoring Counts and

Threshold Values
By selecting a Network or Access Port in the selection tree, these tabs are provided in the
Details pane for each port:

l Summary: Displays a summary of both transmit and receive statistics. See Figure
13 for an example view of an Access port summary.
l 15 Minute (or 5 Minute): Displays the performance monitoring counts in the
current 15 Minute (or 5 Minute) performance bin. See Figure 14 for an example
view of an Access port 15 Minute performance monitoring counters. If the History
check box is selected, the previous 32 periods are also displayed.
l 1 Day: Displays the performance monitoring counts in the current 1 Day
performance bin. If the History check box is selected, the previous period is also
displayed.
l Thresholds: Displays the details and the thresholds that have been set for each PP.
See Figure 15 for an example view of an Access port Threshold values.

To view performance monitoring counts and threshold values:

1. On the toolbar, select Performance Monitoring, or from the Application menu, select
Performance Monitoring.
2. In the tree pane, next to the System > NE-1 > NTEOSA 5422 entities, click +.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 453

Oscilloquartz: An ADVA Company Performance Monitoring

3. Select the applicable Access Port. The performance monitoring Counts pane is displayed
(see Figure 14).
4. Select the applicable tab to view the Summary, 15 Minute (or 5 Minute) counters, 1 Day
counters, or Threshold levels. Use sliding bars to view data, as required. An asterisk in
the Time column indicates data that is suspect. (See Figure 14 and Figure 15.)
5. Optional, you can export 15 Minute (or 5 Minute), and 1 Day counts to an Excel
spreadsheet by clicking Excel. A dialog box is displayed at the bottom of the window.

6. Choose whether to open or save the file by clicking Open or Save. The file in the format
[Port]_[YYYY-MM-DD] is saved in the selected application. Excel is the default
application (see Figure 16). Edit or save the exported file as required.
Figure 13: Access Port Summary performance monitoring Counts

Figure 14: Access Port 15 Minute performance monitoring Counts

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 454

Oscilloquartz: An ADVA Company Performance Monitoring

Figure 15: Access Port performance monitoring Thresholds

Figure 16: 15 Minute performance monitoring Counts Exported to Excel

During LoS (link down) of a port, the Summary page displays N/A for the Optical
Power Received (OPR) field and the PM Rport page displays -100.

Initializing Performance Monitoring Registers

For Access Port entities, performance monitoring data is maintained in individual monitored
parameter bins for each interval. The system maintains bins for these time periods:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 455

Oscilloquartz: An ADVA Company Performance Monitoring

l Current 15-minute (or 5 Minute) bin.

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

To initialize performance monitoring registers:

1. Click PM, or from the Application menu, select Performance Monitoring.

2. In the tree pane, expand System > NE-1 > NTEOSA 5422.
3. Right-click the applicable access port, and then select Init Registers to initialize the port
counters. The Initialize Registers window opens.

4. In the Register and Interval Selection area, Interval and Bin Index menus, select the
applicable interval and bin index.
5. Click OK. The designated performance monitoring count registers are cleared.

Editing Performance Monitoring Thresholds

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

An Access Port entity type has default thresholds for its PPs, which are used when an entity
is provisioned. The default thresholds are configurable.

To edit performance monitoring thresholds:

1. Click PM, or from the Application menu, select Performance Monitoring.

2. In the tree pane, expand System > NE-1 > NTEOSA 5422.
3. Right-click the applicable access port, and then select Edit Thresholds. The Edit
Thresholds window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 456

Oscilloquartz: An ADVA Company Performance Monitoring

4. In the Entity Selection area, Entity menu, select the applicable port entity, and then
click OK. The Edit Thresholds window opens with a table listing the performance
monitoring thresholds related to the applicable port entity selected.

5. Edit the applicable thresholds for the applicable Monitored Type. Use the sliding bars on
the right of the window to view the data, as required.
6. Click OK.

Monitoring PTP
The OSA 5422 PTP feature provides performance monitoringfor PTP Port, PTP Flow points
and the Slave Only Ordinary Clock (SOOC). Additionally, the Syncjack feature provides stats
for the Telecom Slave (TS), Clock Probes (Clock Accuracy), PTP Clock Probes (Clock Analysis)
and the PTP Network Probe (PTP Network Analysis) as well has history results for Clock
Probes (Clock Accuracy) and PTP Clock Probes (Clock Analysis). These PMs follow the same

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 457

Oscilloquartz: An ADVA Company Performance Monitoring

patterns and rules as the Ethernet interface PMs (see Monitoring Access PortsMonitoring
Access PortsMonitoring Access PortsMonitoring Access Ports)

Performance monitoring enables in-service, non-intrusive system monitoring to aid in

diagnosing and isolating issues that may occur during operation. Performance monitoring
enables users to detect and react to potential failures prior to a customer outage. In
addition to providing traditional SNMP MIB Etherstats, Syncjack® provides performance
parameters and features similar to those found in traditional services. This allows Ethernet
service assurance to be integrated into a carrier’s existing service assurance infrastructure.
See Syncjack Testing.

The Performance monitoring view allows you to view performance monitoring counts and
view performance monitoring thresholds. Performance monitoring thresholds can be
edited, and registers can be initialized for users with proper user access permission level.

This section contains these step by step procedures:

l Viewing PTP Port, PTP Flow Point and SOOC Performance Monitoring Counts and
Threshold Values
l Initializing PTP Port, PTP Flow Point and SOOC Performance Monitoring Registers
l Editing PTP Port, PTP Flow Point and SOOC Performance Monitoring Thresholds
l Probing Features
l Performing Clock Accuracy Testing
l Performing Clock Analysis
l Performing PTP Network Analysis

For performance monitoring commands using the CLI, see the OSA 5422
Command Line Reference Guide.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 458

Oscilloquartz: An ADVA Company Performance Monitoring

Performance Monitoring Features

l Retrievable performance data for each managed entity, so the user can determine
past and current system operation. Performance monitoring data collection is
performed via a polling mechanism, were primitives are gathered into accumulated
counts. After a defined interval, such as 15 minutes or 1 day, the counts are binned
and stored in a database.
l Checking performance monitoring 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.

Performance monitoring supports:

l Threshold setting and automatic TCA message generation.

l Current and History performance monitoring bins provide a continuous record of
service performance, allowing for accurate SLA conformance statements.

performance monitoring counts can be displayed as a summary or in tabular format in the

web-based EMS, 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 collected. These
entities are monitored for performance data which are accumulated into PPs:

l PTP Flow point.

l SOOC
l PTP Port
l Telecom Slave under the Syncjack application (Syncjack Testing).

Performance Parameter Attributes

Each PP can be defined by the attributes outlined in this table.

Table 91: Performance Parameter Attributes

Attribute Description
Monitor Type The name of the PP. This is presented in mnemonic form, such as
ANNOUNCESRX (PTP Announce Messages Received).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 459

Oscilloquartz: An ADVA Company Performance Monitoring

Table 91: Performance Parameter Attributes

Attribute Description
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:

l Locally to the entity (or at the near end).

l 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, such as 15-Minute or 1-Day.
Monitor The time at which the PP was collected:
Timestamp
l The current time is used for Rollover and Current counters.
l The boundary crossing time is used for History counters (stored as
number of seconds since the Epoch).
History Index Indicates a bin from the historical list of bins:

l For 15 Minute history bins, this number is 1 to 32 (1 being the most

recent).
l For 1 Day history bins, this number is 1.
l 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, such as 15-Minute or 1-Day.

The user can reset any individual or all PP counters to zero.

Bins and Bin Periods

These performance bin periods will exist:

l 1 x Current 15-Minute Bin

l 1 x Current 1-Day (24-Hour) Bin
l 32 x Historical 15-Minute Bins
l 1 x Historical 1-Day (24-Hour) Bin

(1) The 32 Historical 15-Minute Bins provide the most recent 8 hours of performance data.

(2) The Historical 1-Day Bin provides the performance data from the previous day starting
from 12:00 AM, such as midnight, 00:00.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 460

Oscilloquartz: An ADVA Company Performance Monitoring

Performance Parameter Thresholds

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 that entity.

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

Threshold Crossing Alert Messages

When a PP threshold has been met or exceeded, a TCA is generated. This table outlines the
attributes that are specified in the TCA message.

Table 92: Threshold Crossing Alert Attributes

Attribute Description Values
Entity The monitored entity’s id. Variable.
Identifier
Monitor Type The name of the PP that has crossed its See TCA Monitored
threshold. This is presented in mnemonic Types for Monitor
form. Type mnemonics.
Time Period In which time period the threshold was 15-Minute
crossed.
1-Day
Time The time the threshold was crossed. Timestamp
Location The location of the TCA generation. This is Near end
determined in relation to the monitored
Far end
entity, in that the PP has occurred:
None
l Locally to the entity (or at the near end).
l Remotely to the entity (or at the far end).
Direction The direction in relation to the monitored Receive
entity.
Transmit
Monitored The value of the PP count when the threshold Up to a 64-bit
Value was crossed. number
Threshold The configured threshold at the time the Up to a 64-bit
Value threshold was crossed. number

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 461

Oscilloquartz: An ADVA Company Performance Monitoring

Monitored Types and Default TCA Settings

For monitored types and default Threshold Crossing Alert (TCA) settings, see TCA
Monitored Types.

Viewing PTP Port, PTP Flow Point and SOOC

Performance Monitoring Counts and Threshold
Values
In the PTP application, select PTP Port, PTP flow point, or SOOC and then select the
Statistics tab to view these performance monitoring summaries for each entity:

l Summary: Displays a summary of both transmit and receive statistics. See Figure
17 for an example view of an Access port summary.
l 15 Minute: Displays the performance monitoring counts in the current 15 minute
performance bin. See Figure 19 for an example view of a PTP flow point 15 minute
performance monitoring counters. If you select History, the previous periods are
also displayed.
l 1 Day: Displays the performance monitoring counts in the current 1 day
performance bin. If you select History, the previous period are also displayed.
l Thresholds: Displays the details and the thresholds that have been set for each
performance parameter. See Figure 21 for an example view of an access port
threshold values.

To view performance monitoring counts and threshold values:

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System > NE-1.
3. Expand the applicable entity depending on performance monitoring counts and
thresholds you want to view:
o For Network/ Access PTP flow point: expand NTEOSAOSA 5422 > E1000-A-

1/E1000-N-1.
o For SOOC: expand TS-1-1.
o For PTP Port or L3 PTP Port: expand PTP Clock-1-x.
4. Select the Statistics tab. The performance monitoring Counts window opens (see Figure
17 and Figure 18).
5. Select the applicable tab to view Summary, 15 Minute counters, 1 Day counters, or
Threshold levels. Use the sliding bars to view data, as required. An asterisk in the Time
column indicates data that is suspect (see Figure 19, Figure 20, Figure 21, and Figure 22).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 462

Oscilloquartz: An ADVA Company Performance Monitoring

6. If applicable, 15 Minute and 1 Day counts can be exported to an Excel spreadsheet by

clicking Excel. A dialog box is displayed at the bottom of the window.

7. Select to open or save the file. The filen ame in the format [Entity name]_[YYYY-MM-DD],
such as NET_PTP_FLOW_PT-1-1-1-1_2018-01-02, is created in the selected application.
Excel is the default application. Edit or save the exported file as required.
Figure 17: Summary performance monitoring Counts — PTP Flow point

Figure 18: Summary performance monitoring Counts — L3 PTP Port

Figure 19: 15 Minute performance monitoring Counts — PTP Flow point

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 463

Oscilloquartz: An ADVA Company Performance Monitoring

Figure 20: 15 Minutes performance monitoring Counts — L3 PTP Port

Figure 21: performance monitoring Threshold — PTP Flow point

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 464

Oscilloquartz: An ADVA Company Performance Monitoring

Figure 22: performance monitoring Threshold — L3 PTP Port

Initializing PTP Port, PTP Flow Point and SOOC

Performance Monitoring Registers
For PTP entities, performance monitoring data is maintained in individual monitored
parameter bins for each interval. The system maintains bins for the following time periods:

l Current 15-minute bin

l 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, or All History.

To initialize performance monitoring registers:

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System>NE-1.
3. Expand the applicable entity depending on the performance monitoring counts and
thresholds you want to view:
o For access PTP flow point: expand NTEOSA 5422 > E1000-A-1 to 10.

o For SOOC: expand the TS-1-1 entity.

o For PTP port: expand the PTP clock element.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 465

Oscilloquartz: An ADVA Company Performance Monitoring

4. To view PTP performance monitoring counts, select the Statistics tab and Summary
tab.
5. To initialize counters, right-click the applicable PTP Port, PTP Flow point, or SOOC entity,
and then select Init Registers. The Initialize Registers window opens.

6. In the Register and Interval Selection area, Interval and Bin Index menus, select the
applicable interval and bin index.
7. Click OK. The designated performance monitoring count registers are cleared.

Editing PTP Port, PTP Flow Point and SOOC

Performance Monitoring Thresholds
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 entity.

Each entity type has default thresholds for its PPs, which are used when an entity is
provisioned. The default thresholds are configurable.

To edit performance monitoring thresholds:

1. On the toolbar, click PTP, or from the Application menu, select PTP.
2. In the tree pane, expand System > NE-1.
3. Expand the applicable entity depending on the performance monitoring counts and
thresholds you want to edit:
o For Access PTP flow point: expand NTEOSA 5422 > E1000-A-1 to 10.

o For SOOC: expand the TS-1-1 entity.

o For PTP port: expand the PTP clock entity.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 466

Oscilloquartz: An ADVA Company Performance Monitoring

4. Right-click the applicable PTP Port, PTP Flow point, or SOOC entity, and then select Edit
Thresholds. The Edit Thresholds window opens.
5. Edit the applicable thresholds for the applicable Monitored Type. Use the sliding bars to
view the data, as required.

6. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 467

 Appendix E

TCA Monitored Types

These tables explain the performance monitoring Threshold Crossing Alert (TCA) monitored
types and associated default settings for access ports, flows, shapers, QOS, and the policer:

l Ethernet Access Port Monitored Types

l PTP Flow Point Monitored Types
l PTP SOOC Monitored Types
l PTP MCI Monitored Types
l PTP Port Monitored Types
l PTP Remote Slave Monitored Types
l Telecom Slave Clock Analysis Monitored Types
l PTP Network Probe Monitored Types

For procedures on viewing, editing and initializing PMs using the web-based EMS, see
Monitoring Access Ports.

Ethernet Access port Monitored Types

These performance parameters are related to an Ethernet Access port.

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ABR-RX Average Bit Rate Received. The Receive Near End 0 0
average bit rate received over the
specific interval in the ingress
direction. If there is link down
during the interval, the bin is not
accessible. This counter is based
on RMON etherStatsOctets.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 468

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ABR-TX Average Bit Rate Transmitted. The Transmit Near End 0 0
average bit rate transmitted over
a specific interval in the egress
direction, based on Bytes Sent. If
there is link down during the
interval, the bin is not accessible.
ESBF EtherStats Broadcast Frames. The Transmit Near End 0 0
Broadcast Frames Sent in the
egress direction If there is link
down during the interval, the bin
is not accessible.
ESBP EtherStats Broadcast Packets Receive Near End 0 0
Received. The total number of
good packets received that were
directed to the broadcast address.
Note that this does not include
multicast packets.
ESBS EtherStats Bytes Sent. The Bytes Transmit Near End 0 0
Sent in the egress direction. If
there is link down during the
interval, the bin is not accessible.
ESC EtherStats Collisions. The best Receive Near End 0 0
estimate of the total number of
collisions on this 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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 469

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESCAE EtherStats CRC (Cyclic Receive Near End 37055 3557280
Redundancy Check) Aligned
Errors. The total number of
packets received that had a length
(excluding framing bits, but
including FCS octets) of between
64 and 1518 octets, 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 None Near End 37055 3557280
number of events in which
packets were dropped due to lack
of resources. Note that this
number is not necessarily the
number of packets dropped; it is
just the number of times this
condition has been detected.
ESF EtherStats Fragments. The total Receive Near End 37055 3557280
number of packets received that
were less than 64 octets in length
(excluding framing bits but
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 470

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESFS EtherStats Frames Sent. The Transmit Near End 0 0
Frames Sent in the egress
direction. If there is link down
during the interval, the bin is not
accessible.
ESJ EtherStats Jabbers. The total Receive Near End 0 0
number of packets received that
were longer than 1518 octets
(excluding framing bits, but
including FCS octets), and had
either a bad Frame Check
Sequence (FCS) with an integral
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 Transmit Near End 0 0
Multicast Frames Sent in the
egress direction. If there is link
down during the interval, the bin
is not accessible.
ESMP EtherStats Multicast Packets Receive Near End 0 0
Received. The total number of
good packets received that were
directed to a multicast address.
Note that this number does not
include packets directed to the
broadcast address.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 471

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESO EtherStats Octets Received. The Receive Near End 0 0
total number of octets of data
(including those in bad packets)
received on the network
(excluding framing bits but
including FCS octets).
ESOF EtherStats Oversize Frames. The Transmit Near End 0 0
total number of frames received
that were oversized.
ESOP EtherStats Oversize Packets. The Receive Near End 37055 3557280
total number of packets received
that were longer than 1518 octets
(excluding framing bits, but
including FCS octets) and were
otherwise well formed.
ESP EtherStats Packets Received. Receive Near End 0 0
EtherStats Packets Received. The
total number of packets
(including bad packets, broadcast
packets, and multicast packets)
received.
ESP64 EtherStats Packets - 0 to 64 Octets Receive Near End 0 0
Frames. The total number of
packets (including bad packets)
received that were 64 octets in
length (excluding framing bits but
including FCS octets).
ESP65 EtherStats Packets - 65 to 127 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 65
and 127 octets in length inclusive
(excluding framing bits but
including FCS octets).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 472

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESP128 EtherStats Packets - 128 to 255 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 128
and 255 octets in length inclusive
(excluding framing bits but
including FCS octets).
ESP256 EtherStats Packets - 256 to 511 Receive Near End 0 0
Octet Packets. The total number
of packets (including bad packets)
received that were between 256
and 511 octets in length inclusive
(excluding framing bits but
including FCS octets).
ESP512 EtherStats Packets - 512 to 1023 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 512
and 1023 octets in length
inclusive (excluding framing bits
but including FCS octets).
ESP1024 EtherStats Packets - 1024 to 1518 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 1024
and 1518 octets in length
inclusive (excluding framing bits
but including FCS octets).
ESP1519 EtherStats Packets - 1519 to 1536 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 1519
and 1536 octets in length
inclusive (excluding framing bits
but including FCS octets).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 473

Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESUF EtherStats Unicast Frames. The Transmit Near End 0 0
Unicast Frames Sent in the egress
direction. If there is link down
during the interval, the bin is not
accessible.
ESUP EtherStats Undersize Packets. The Receive Near End 37055 3557280
total number of packets received
that 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 End 0 0
Discarded. Number of Layer 2
Control Protocol Frames
discarded on the interface.
L2CPFP Layer 2 Control Protocol Frames Receive Near End 0 0
Processed. Number of Layer 2
Control Protocol Frames
processed on the interface.
LBC1 Laser Bias Current retrieved from Receive Near End 0 0
the SFP.
OPS1 Optical Power Receive. Received Receive Near End -80 -80
Optical Power (in dBm) retrieved
from the SFP.
OPT1 Optical Power Transmit. Transmit Transmit Near End -80 -80
Optical Power (in dBm) retrieved
from the SFP.
OPR-VAR Optical Power Received - Receive Near End 4 4
Variance. The variance from the
configured OPR threshold that
does not result in generating a
TCA. For example, if OPR is -80
and OPR-VAR is 4, no TCA is
generated if OPR is between -76
and -84. Applicable only if the
media type is Fiber.

1. Valid only when the port is configured to use the fiber interfaces.
OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 474
Oscilloquartz: An ADVA Company

Table 93: Ethernet Access port Monitored Types

Monitored 5/15
Description Direction Location 1 Day
Type Min.
OPT-VAR Optical Power Transmit - Transmit Near End 4 4
Variance. The variance from the
configured OPT threshold that
does not result in generating a
TCA. For example, if OPT is -80
and OPR-VAR is 4, no TCA is
generated if OPT is between -76
and -84. Applicable only if the
media type is Fiber.
TEMP Temperature for the physical layer None Near End 0 0
(expressed in Celsius). Applicable
only if the media type is Fiber.
UAS Unavailable Seconds - counted if Receive Near End 10 10
one or more of following exists in
that second: 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).

Any second that is deemed UAS

for the port will also be UAS for all
the EVCs on that port.

Ethernet Access Port Monitored Types

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

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 475

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ABR-RX Average Bit Rate Received (in the Receive Near End 0 0
A2N direction). The average bit
rate received over the specific
interval in the ingress direction.
This counter is based on RMON
etherStatsOctets.
ABR-TX Average Bit Rate Transmitted (in Transmit Near End 0 0
the N2A direction). The average
bit rate transmitted over a specific
interval in the egress direction,
based on Bytes Sent.
APFD AFP Priority-tagged Frames Receive Near End 0 0
Dropped. Priority-tagged frames
dropped due to AFP setting. AFP
Priority-tagged Frames Dropped.
Priority-tagged frames dropped
due to AFP setting.
AUFD AFP Untagged Frames Dropped. Receive Near End 0 0
Untagged frames dropped due to
AFP setting.
ESBF EtherStats Broadcast Frames. If Receive Near End 0 0
there is link down during the
interval, the bin is not accessible.
ESBP EtherStats Broadcast Packets Receive Near End 0 0
Received (in the A2N direction).
The total number of good packets
received that were directed to the
broadcast address. Note that this
does not include multicast
packets.
ESBS EtherStats Bytes Sent. Transmit Near End 0 0

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 476

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESC EtherStats Collisions. The best Receive Near End 0 0
estimate of the total number of
collisions on this 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 Receive Near End 37055 3557280
Redundancy Check) Aligned
Errors. The total number of
packets received that had a length
(excluding framing bits, but
including FCS octets) of between
64 and 1518 octets, 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 Receive Near End 37055 3557280
number of events in which
packets were dropped due to lack
of resources. Note that this
number is not necessarily the
number of packets dropped; it is
just the number of times this
condition has been detected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 477

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESF EtherStats Fragments. The total Receive Near End 37055 3557280
number of packets received that
were less than 64 octets in length
(excluding framing bits but
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 Transmit Near End 0 0
Frames Sent in the egress
direction.
ESJ EtherStats Jabbers. The total Receive Near End 0 0
number of packets received that
were longer than 1518 octets
(excluding framing bits, but
including FCS octets), and had
either a bad Frame Check
Sequence (FCS) with an integral
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 478

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESMF EtherStats Multicast Frames. The Transmit Near End 0 0
Multicast Frames Sent in the
egress direction.
ESMP EtherStats Multicast Packets Receive Near End 0 0
Received. EtherStats Multicast
Packets Received. The total
number of good packets received
that were directed to a multicast
address. Note that this number
does not include packets directed
to the broadcast address.
ESO EtherStats Octets Received. The Receive Near End 0 0
total number of octets of data
(including those in bad packets)
received on the network
(excluding framing bits but
including FCS octets).
ESOF EtherStats Oversize Frames. The Transmit Near End 0 0
total number of frames
transmitted that were oversized.
ESOP EtherStats Oversize Packets. The Receive Near End 37055 3557280
total number of packets received
that were longer than 1518 octets
(excluding framing bits, but
including FCS octets) and were
otherwise well formed.
ESP EtherStats Packets Received. The Receive Near End 0 0
total number of packets
(including bad packets, broadcast
packets, and multicast packets)
received.
ESP64 EtherStats Packets - 0 to 64 Octets Receive Near End 0 0
Frames. The total number of
packets (including bad packets)
received that were 64 octets in
length (excluding framing bits but
including FCS octets).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 479

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESP65 EtherStats Packets - 65 to 127 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 65
and 127 octets in length inclusive
(excluding framing bits but
including FCS octets).
ESP128 EtherStats Packets - 128 to 255 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 128
and 255 octets in length inclusive
(excluding framing bits but
including FCS octets).
ESP256 EtherStats Packets - 256 to 511 Receive Near End 0 0
Octet Packets. The total number
of packets (including bad packets)
received that were between 256
and 511 octets in length inclusive
(excluding framing bits but
including FCS octets).
ESP512 EtherStats Packets - 512 to 1023 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 512
and 1023 octets in length
inclusive (excluding framing bits
but including FCS octets).
ESP1024 EtherStats Packets - 1024 to 1518 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 1024
and 1518 octets in length
inclusive (excluding framing bits
but including FCS octets).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 480

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
ESP1519 EtherStats Packets - 1519 to 1536 Receive Near End 0 0
Octets Frames. The total number
of packets (including bad packets)
received that were between 1519
and 1536 octets in length
inclusive (excluding framing bits
but including FCS octets).
ESUF EtherStats Unicast Frames sent. If Transmit Near End 0 0
there is link down during the
interval, the bin is not accessible.
ESUP EtherStats Undersize Packets Receive Near End 37055 3557280
received. The total number of
packets received that 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 End 0 0
Discarded. Number of Layer 2
Control Protocol Frames
discarded on the interface.
L2CPFP Layer 2 Control Protocol Frames Receive Near End 0 0
Processed. Number of Layer 2
Control Protocol Frames
processed on the interface.
LBC1 Laser Bias Current retrieved from Receive Near End 0 0
the SFP. Applicable only if the
media type is Fiber.
LES Line Errored Seconds detected. Receive Near End 0 0
Increments if a False Carrier or
Errored Symbol event occurs
since the last 1 second poll.
OPR1 Optical Power Receive. Received Receive Near End -80 -80
Optical Power (in dBm) retrieved
from the SFP.

1. Valid only when the port is configured to use the fiber interfaces.
OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 481
Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
OPT1 Optical Power Transmit. Transmit Receive Near End -80 -80
Optical Power (in dBm) retrieved
from the SFP.
OPR-VAR1 Optical Power Received - Receive Near End 4 4
Variance. The variance from the
configured OPR threshold that
does not result in generating a
TCA. For example, if OPR is -80
and OPR-VAR is 4, no TCA is
generated if OPR is between -76
and -84. Applicable only if the
media type is Fiber.
OPT-VAR1 Optical Power Transmit - Transmit Near End 4 4
Variance. The variance from the
configured OPT threshold that
does not result in generating a
TCA. For example, if OPT is -80
and OPR-VAR is 4, no TCA is
generated if OPT is between -76
and -84. Applicable only if the
media type is Fiber.
TEMP Temperature for the physical layer None Near End 0 0
(Applicible (expressed in Celsius).
only to
Fiber)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 482

Oscilloquartz: An ADVA Company

Table 94: Ethernet Access Port Monitored Types and Default TCA Settings
Monitored 5/15
Description Direction Location 1 Day
Type Min.
UAS Unavailable Seconds. Used by Receive Near End 0 0
Network/Service Management
Systems to compute port-based
service unavailability. Counted if
one or more of following exists in
that second:

l Link down
l link deactivated (triggered by
LLF)
l SFP faults
l EFM-OAM discovery failure
l EFM-OAM loopback

Also, any one of the following

port based MEP conditions:

l Port-based cross-connect
defect (unexpected MD level
or MAID Mismatch/Mismerge)
l Port-based MEP Error CCM
Defect (Unexpected MEP or
unexpected period)
l Port-based MEP RMEP CCM
Defect (Loss of Connectivity)
l Port-based MEP RDI Defect
(unidirectional failure makes
the port based service
unavailable)

Any second that is deemed UAS

for the port will also be UAS for all
the EVCs on that port.

PTP Flow Point Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on PTP Flow Points. The following PMs are accessed via the

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 483

Oscilloquartz: An ADVA Company

Precision Time Protocol application when PTP Flow Points are created.

Table 95: PTP Flow Point Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
ANNOUNCESRX PTP Announce Messages Receive Near End 0 0
Received
ANNOUNCESTX PTP Announce Messages Transmit Near End 0 0
Transmitted
DELAYREQSRX PTP Delay_Req Messages Receive Near End 0 0
Received
DELAYREQSTX PTP Delay_Req Messages Transmit Near End 0 0
Transmitted
DELAYRSPSRX PTP Delay_Resp Receive Near End 0 0
Messages Received
DELAYRSPSTX PTP Delay_Resp Transmit Near End 0 0
Messages Transmitted
FOLLOWUPSRX PTP Follow_Up Messages Receive Near End 0 0
Received
FOLLOWUPSTX PTP Follow_Up Messages Transmit Near End 0 0
Transmitted
MGMTFRAMESRX PTP Management Frames Receive Near End 0 0
Received
MGMTFRAMESTX PTP Management Frames Transmit Near End 0 0
Transmitted
PDELAYREQSRX PTP Pdelay_Req Receive Near End 0 0
Messages Received
PDELAYREQSTX PTP Pdelay_Req Transmit Near End 0 0
Messages Transmitted
PDELAYRSPSRX PTP Pdelay_Resp Receive Near End 0 0
Messages Received
PDELAYRSPSTX PTP Pdelay_Resp Transmit Near End 0 0
Messages Transmitted
PDELAYRSPFOLUPSRX PTP Pdelay_Resp_Follow_ Receive Near End 0 0
Up Messages Received
PDELAYRSPFOLUPSTX PTP Pdelay_Resp_Follow_ Transmit Near End 0 0
Up Messages Transmitted

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 484

Oscilloquartz: An ADVA Company

Table 95: PTP Flow Point Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
PTPUNKNOWNSRX Unknown PTP Messages Receive Near End 0 0
Received
PTPUNKNOWNSTX Unknown PTP Messages Transmit Near End 0 0
Transmitted
SIGNALINGRX PTP Signaling Messages Receive Near End 0 0
Received
SIGNALINGTX PTP Signaling Messages Transmit Near End 0 0
Transmitted
SYNCSRX PTP Sync Messages Receive Near End 0 0
Received
SYNCSTX PTP Sync Messages Transmit Near End 0 0
Transmitted

PTP SOOC Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a Slave Only Ordinary Clock (SOOC). The following PMs
are accessed via the Precision Time Protocol application when PTP software licensing is
enabled and a Telecom Slave is created.

Table 96: SOOC Monitored Types and Default TCA Settings

5/15 1
Monitored Type Definition Direction Location
Min. Day
PTPMGMTMSGSD PTP Management Receive Near End 0 0
Message Discards
PTPINVMSGLEND PTP Invalid Message Receive Near End 0 0
Length Discards
PTPUNKMASTERD PTP Unknown Master Receive Near End 0 0
Discards
PTPUNKDOMAIND PTP Unknown Domain Receive Near End 0 0
Discards
PTPMULTIANNOUNCED PTP Multicast Announce Receive Near End 0 0
Message Discards
PTPOOSANNOUNCES PTP Out Of Sequence Receive Near End 0 0
Announce Messages

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 485

Oscilloquartz: An ADVA Company

Table 96: SOOC Monitored Types and Default TCA Settings

5/15 1
Monitored Type Definition Direction Location
Min. Day
PTPMULTISYNCD PTP Multicast Sync Receive Near End 0 0
Message Discards
PTPTWOSTEPSYNCD PTP Two Step Sync Receive Near End 0 0
Message Discards
PTPFOLLOWUPSD PTP Follow-up Message Receive Near End 0 0
Discards
PTPDELAYREQSD PTP Delay_Req Message Receive Near End 0 0
Discards
PTPPDELAYREQSD PTP PDelay_Req Receive Near End 0 0
Message Discards
PTPPDELAYRSPSD PTP PDelay_Resp Receive Near End 0 0
Message Discards
PTPPDELAYFOLLOWUPSD PTP PDelay Follow-up Receive Near End 0 0
Message Discards
PTPINVTLVLENSD PTP Invalid TLV Length Transmit Near End 0 0
Discards
PTPINVTLVTYPESD PTP Invalid TLV Type Receive Near End 0 0
Discards
AVGSYNCPD Average Sync Path Delay Receive Near End 0 0
(nsec)
MINSYNCPD Minimum Sync Path Receive Near End 0 0
Delay (nsec)
MAXSYNCPD Maximum Sync Path Receive Near End 0 0
Delay (nsec)
AVGSYNCPDV Average Sync PDV (nsec) Receive Near End 0 0
MINSYNCPDV Minimum Sync PDV Receive Near End 0 0
(nsec)
MAXSYNCPDV Maximum Sync PDV Receive Near End 0 0
(nsec)
AVGMEANPATHDELAY Average Mean Path Receive Near End 0 0
Delay (nsec)
MINMEANPATHDELAY Minimum Mean Path Receive Near End 0 0
Delay (nsec)
MAXMEANPATHDELAY Maximum Mean Path Receive Near End 0 0
Delay (nsec)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 486

Oscilloquartz: An ADVA Company

Table 96: SOOC Monitored Types and Default TCA Settings

5/15 1
Monitored Type Definition Direction Location
Min. Day
AVGOFM Average Offset from Receive Near End 0 0
Master (nsec)
MINOFM Minimum Offset from Receive Near End 0 0
Master (nsec)
MAXOFM Maximum Offset from Receive Near End 0 0
Master (nsec)

PTP MCI Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a Precision Time Protocol (PTP) Master Clock Interface
(MCI). The following PMs are accessed via the Precision Time Protocol application when PTP
software licensing is enabled and a remote slave is created.

Table 97: PTP MCI Monitored Types and Default TCA Settings
15 1
Monitored Type Definition Direction Location
Min. Day
MCI_ANNCANCELEVTS Announce Service Receive Near End 0 0
Canceled Events
MCI_ANNOUNCEDENEVTS Announce Service Receive Near End 0 0
Denied Events
MCI_ Delay Response Receive Near End 0 0
DELAYRESPCANCELEVTS Service Canceled
Events
MCI_DELAYRESPDENEVTS Delay Response Receive Near End 0 0
Service Denied Events
MCI_ Dynamic Slaves Receive Near End 0 0
DYNSLAVESLEARNCOUNTS Learned Count
MCI_DYNSLAVESDROPPED Dynamic Slaves Receive Near End 0 0
Service Dropped
MCI_PTPDISCARDS PTP Message Discards Receive Near End 0 0
MCI_SYNCCANCELLEVTS Sync Service Canceled Receive Near End 0 0
Events
MCI_SYNCDENEVTS Sync Service Denied Receive Near End 0 0
Events

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 487

Oscilloquartz: An ADVA Company

PTP Port Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a Precision Time Protocol (PTP) Port. The following PMs
are accessed via the Precision Time Protocol application when PTP software licensing is
enabled and a PTP Port is created.

Table 98: PTP Port Monitored Types and Default TCA Settings
15 1
Monitored Type Definition Direction Location
Min. Day
AVGANNOUNCERATE PTP Port Receive Near End 0 0
Average
Announce Rate
AVGSYNCRATE PTP Port Receive Near End 0 0
Average Sync
Rate
AVGDELAYREQRATE PTP Port Receive Near End 0 0
Average Delay
Req Rate
AVGDELAYRESPRATE PTP Port Receive Near End 0 0
Average Delay
Resp Rate
PTPUNKDOMAIND PTP Port Receive Near End 0 0
Mismatch
Domain
Discards
MSGWRONGTYPEDSCRD Receive Near End 0 0
PTP Port
Message
Wrong Type
Discards
PTPINVMSGLEND PTP Port Receive Near End 0 0
Messages
Wrong Length
Discards
MINOFM PTP Port Min Receive Near End 0 0
Offset From
Master

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 488

Oscilloquartz: An ADVA Company

Table 98: PTP Port Monitored Types and Default TCA Settings
15 1
Monitored Type Definition Direction Location
Min. Day
MAXOFM PTP Port Max Receive Near End 0 0
Offset From
Master
AVGOFM PTP Port Receive Near End 0 0
Average Offset
From Master
MINSYNCPD PTP Port Min Receive Near End 0 0
Sync Path Delay
MAXSYNCPD PTP Port Max Receive Near End 0 0
Sync Path Delay
AVGSYNCPD PTP Port Receive Near End 0 0
Average Sync
Path Delay
AVGDELAY_RESPPD PTP Port Receive Near End 0 0
Average Delay
Resp Path
Delay
MAXDELAY_RESPPD PTP Port Max Receive Near End 0 0
Delay Resp
Path Delay
MINDELAY_RESPPD PTP Port Min Receive Near End 0 0
Delay Resp
Path Delay
MINMEANPATHDELAY PTP Port Min Receive Near End 0 0
Mean Path
Delay
MAXMEANPATHDELAY PTP Port Max Receive Near End 0 0
Mean Path
Delay
AVGMEANPATHDELAY PTP Port Receive Near End 0 0
Average Mean
Path Delay
UNKNOWNMASTERDISCARDS PTP Port Receive Near End 0 0
Unknown
Master Discards

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 489

Oscilloquartz: An ADVA Company

PTP Remote Slave Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a Precision Time Protocol (PTP) Static Slaves and
Dynamic Slaves. The following PMs are accessed via the Precision Time Protocol application
when PTP software licensing is enabled and a remote slave is created.

Table 99: PTP Remote Slave Monitored Types and Default TCA Settings
15 1
Monitored Type Definition Direction Location
Min. Day
RS_ANNOUNCEMSGSGEN Announce Transmit Near End 0 0
Messages
Generated
RS_ Delay_Req Receive Near End 0 0
DELAYREQMSGSDROPPED Messages
Dropped
RS_DELAYREQMSGSRX Delay_Req Receive Near End 0 0
Messages
Received
RS_DELAYRESPMSGSGEN Delay_Resp Transmit Near End 0 0
Messages
Generated
RS_INVTLVLENDISCARDS PTP messages Receive Near End 0 0
with invalid PTP
TLV length
RS_INVTLVTYPEDISCARDS PTP messages Receive Near End 0 0
with unknown
PTP TLV type
RS_SIGNALMSGSGEN Signaling Transmit Near End 0 0
Messages
Generated
RS_SIGNALMSGSRX Signaling Receive Near End 0 0
Messages
Received
RS_SYNCMSGSGEN Sync Messages Transmit Near End 0 0
Generated
RS_ Times Announce Receive Near End 0 0
TIMESANNOUNCELEASEEXP lease duration
expired

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 490

Oscilloquartz: An ADVA Company

Table 99: PTP Remote Slave Monitored Types and Default TCA Settings
15 1
Monitored Type Definition Direction Location
Min. Day
RS_TIMESDELAYRESPEXP Times Delay_Resp Receive Near End 0 0
lease duration
expired
RS_TIMESSYNCLEASEEXP Times Sync lease Receive Near End 0 0
duration expired

Telecom Slave Clock Analysis Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a Telecom Slave (TS-1-1) under Clock Analysis in
SyncJack. The following PMs are accessed via the SyncJack application when PTP software
licensing is enabled and a Telecom Slave is created.

Table 100: Telecom Slave Clock Analysis Monitored Types and Default TCA
Settings
Monitored 5/15 1
Definition Direction Location
Type Min. Day
TOTALTIMECR5 Total time clock recovery Receive Near End 0 0
score = 5
TOTALTIMECR4 Total time clock recovery Receive Near End 0 0
score = 4
TOTALTIMECR3 Total time clock recovery Receive Near End 0 0
score = 3
TOTALTIMEPR5 Total time pulse recovery Receive Near End 0 0
score = 5
TOTALTIMEPR4 Total time pulse recovery Receive Near End 0 0
score = 4
TOTALTIMEPR3 Total time pulse recovery Receive Near End 0 0
score = 3

PTP Network Probe Monitored Types

These performance parameters and associated default settings are for each of the
thresholds which are supported on a PTP Network Probe. The following PMs are accessed
via the SyncJack application when PTP software licensing is enabled and a PTP Network
Probe is created.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 491

Oscilloquartz: An ADVA Company

Table 101: PTP Network Probe Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
AVGMEANPATHDELAY Average Mean Receive Near End 0 0
Path Delay, ns
MINMEANPATHDELAY Minimum Mean Receive Near End 0 0
Path Delay, ns
MAXMEANPATHDELAY Maximum Mean Receive Near End 0 0
Path Delay, ns
AVGSYNCPD Average Path Receive Near End 0 0
Delay From
Master To Slave,
ns
MINSYNCPD Minimum Path Receive Near End 0 0
Delay From
Master To Slave,
ns
MAXSYNCPD Maximum Path Receive Near End 0 0
Delay From
Master To Slave,
ns
MINRPDVFWD Minimum Residual Receive Near End 0 0
Packet Delay
Variation Forward
Direction, ns
AVGRESPDVFWD Average Residual Receive Near End 0 0
Packet Delay
Variation Forward
Direction, ns
RESPDVFWDLOW Total Number Of Receive Near End 0 0
Forward Residual
Packet Delay
Variation Results
In Low Range
RESPDVFWDMEDIUM Total Number Of Receive Near End 0 0
Forward Residual
Packet Delay
Variation Results
In Medium Range

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 492

Oscilloquartz: An ADVA Company

Table 101: PTP Network Probe Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
RESPDVFWDHIGH Total Number Of Receive Near End 0 0
Forward Residual
Packet Delay
Variation Results
In High Range
RESPDVFWDTOTAL Total Number Of Receive Near End 0 0
Valid RPDVfrw
Results
MINRPDVREV Minimum Residual Receive Near End 0 0
Packet Delay
Variation Reverse
Direction
AVGRESPDVREV Average Residual Transmit Near End 0 0
Packet Delay
Variation Reverse
Direction
RESPDVREVLOW Total Number Of Receive Near End 0 0
Reverse Residual
Packet Delay
Variation Results
In Low Range
RESPDVREVMEDIUM Total Number Of Receive Near End 0 0
Reverse Residual
Packet Delay
Variation Results
In Medium Range
RESPDVREVHIGH Total Number Of Receive Near End 0 0
Reverse Residual
Packet Delay
Variation Results
In High Range
RESPDVREVTOTAL Total Number Of Receive Near End 0 0
Valid RPDVrev
Results
FWDSCORE5 Total Time Receive Near End 0 0
Forward Score=5,
s

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 493

Oscilloquartz: An ADVA Company

Table 101: PTP Network Probe Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
FWDSCORE4 Total Time Receive Near End 0 0
Forward Score=4,
s
FWDSCORE3 Total Time Receive Near End 0 0
Forward Score=3,
s
REVSCORE5 Total Time Receive Near End 0 0
Reverse Score=5,
s
REVSCORE4 Total Time Receive Near End 0 0
Reverse Score=4,
s
REVSCORE3 Total Time Receive Near End 0 0
Reverse Score=3,
s
SYNCSRX Number of Receive Near End 0 0
Received Sync
Messages
LOSTSYNCMSGS Number of Lost Receive Near End 0 0
Sync Messages
DELAYRSPSRX Number of Receive Near End 0 0
Received Delay
Response
Messages
LOSTDELAYRSPMSGS Number of Lost Receive Near End 0 0
Delay Response
Messages
MINDELAYREQPATHDELAY Minimum Delay Receive Near End 0 0
Req Path Delay
MAXDELAYREQPATHDELAY Maximum Delay Receive Near End 0 0
Req Path Delay
AVGDELAYREQPATHDELAY Average Delay Receive Near End 0 0
Req Path Delay
MINPATHASYMMETRY Minimum Path Receive Near End 0 0
Asymmetry

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 494

Oscilloquartz: An ADVA Company

Table 101: PTP Network Probe Monitored Types and Default TCA Settings
5/15 1
Monitored Type Definition Direction Location
Min. Day
MAXPATHASYMMETRY Maximum Path Receive Near End 0 0
Asymmetry
AVGPATHASYMMETRY Average Path Receive Near End 0 0
Asymmetry

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 495

 Chapter F

Syncjack Testing
Syncjack is a collection of monitoring and measurement tools that allows maintenance and
performance monitoring of synchronization services.

The OSA 5422 uses these Syncjack tools:

l Clock Probe: The Clock Probe is used to measure clock frequency and phase
accuracy.
l PTP Clock Probe: The PTP Clock Probe is used for PTP clock analysis.
l PTP Network Probe: The PTP Network Probe is used for network analysis of PTP
message transport.

The Syncjack suite is comprised of a Syncjack Network Management System (NMS) and
Syncjack embedded applications. See Figure 23 for an example.

Figure 23: Syncjack Suite

Syncjack provisioning and reporting is invoked by selecting the Syncjack application.

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 496

Oscilloquartz: An ADVA Company Syncjack Testing

To view the Syncjack testing:

1. Select the Syncjack application by performing either of these steps:

On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System entity, click +.
3. Select the NE-1 entity. The Network Element window opens with the Syncjack Global
Dashboard View.

The Global status reflects a composite of 3 status meters:

l Clock Accuracy
l Clock Analysis
l PTP Network Analysis.

For the indicator bar:

l A horizontal line indicates N/A.

l Green indicates normal operation.
l Yellow indicates some issue exists.
l Red indicates a significant problem.

Probing Features
To measure meaningful results, the accuracy of the reference used by the probes should be
accurate by at least one order of magnitude compared to the signal under test, such as

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 497

Oscilloquartz: An ADVA Company Syncjack Testing

when using GNSS as a reference, the time error generated by the GPS/GNSS receiver/PRTC
can be up to 100 +/- nsec (according to G.8272). Therefore, the TE/ TIE/MTIE can be
effected by the GNSS reference time error and wander.

We recommend not to change the GNSS constellation while the probe runs.
This can cause incorrect probe results. If the GNSS constellation changed
during the measurement, we recommend that you restart the probe.

Performing Clock Accuracy Testing

The OSA 5422 Clock Accuracy testing uses a user selected reference clock and a source
clock and measures the offset between them. The output of the measurement is provided in
the form of MTIE, TE/TIE graphs, and MTIE results.

Prerequisites
The procedure for performing Clock Accuracy testing assumes that the OSA 5422 is
properly connected to the clock inputs to be measured and the appropriate OSA 5422
interfaces have been configured. See Provisioning the OSA 5422.

To perform a clock accuracy test:

1. Create a Clock Probe (see Creating a Clock Probe).

2. Create a Schedule (see Creating a Schedule).
3. Verify the Syncjack Schedule State and Test Progress (see Verifying the Syncjack
Schedule State and Testing Progress).

Creating a Clock Probe

1. On the toolbar, click Syncjack or from the Application menu, select Syncjack.
2. In the selection tree, next to the System > NE-1 > Clock Accuracy entities, click +.
3. Right-click Clock Probes, and then select Create Clock Probe. The Create Clock Probe
window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 498

Oscilloquartz: An ADVA Company Syncjack Testing

4. Set these clock probe options:

For more information on these options, see Clock Accuracy Parameters.

Area Field Setting

Identification Clock Probe Index EID for the probe. Enter a number from 1
to 9. The number is automatically
indexed, but is user editable.
Name [MANDATORY] Enter a text identifier for
the probe of up to 15 ASCII characters
with no spaces or special characters.
Configuration Reference Select the signal reference for this Clock
Probe.
Reference Expected QL Select the clock quality level of the
selected reference. The default is QL-
None.
Source Select the applicable source for the clock
under test.
Source Type Select either Frequency or Phase for the
source type. The default is Frequency.
MTIE Mask Select the applicable MTIE Mask. The
default is G823 Pdh.
Mask Margin (%) Enter the applicable Mask Margin as a
percentage from 0 to 99. The default is 0.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 499

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Raw Data Collection If the Raw Data Collection Server is
provisioned, enable or disable sending
raw data to a remote raw data collection
server. The default is Disabled. See
Provisioning Raw Data Collection.
Measurement Type Select the measurement type as either
Frequency or Phase. The default is
Frequency.
MTIE Restart Defines whether the MTIE measurement
is restarted every 24 hours at 00:00:00
according to the system time. This
ensures that the measurement is
updated with the most recent values.
Select either:

l Enabled
– or –
l Disabled
The default is Disabled.
When restarted, the values of the Mask
Failure, Mask Crossed Time, Mask Margin
Failure, and Mask Margin Crossed Time
are reinitiated and start from a new time
period.
Note: If this setting is disabled, the MTIE
measurement is calculated over the
entire period from when the clock probe
is activated. Therefore, the MTIE graph
can include measurements that are not
relevant as they are dated.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 500

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

TE Monitoring Max TE Threshold (ns) Enter the Maximum Time Error Threshold
Note: These in nanoseconds. If the measurement
options are only exceeds this threshold (+ or - direction in
enabled if the respect to 0 on the phase TE graph), the
Measurement SJ Max TE Threshold Exceeded
Type is set to alarm is generated. The Max TE threshold
Phase. must be at least 50 ns greater than the
clear threshold. Setting both the Max TE
Threshold and Max TE Clear Threshold to
0 disables this TCA. The default is 0.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 501

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Max TE Clear Threshold Enter the Maximum Time Error Clear
(ns) Threshold in nanoseconds. If the
measurement meets this threshold (+ or -
direction in respect to 0 on the phase TE
graph) clears an existing SJ Max TE
Threshold Exceeded alarm. The
default is 0.
Const TE Threshold (ns) Enter the Constant Time Error Threshold
in nanoseconds. If the constant
measurement (average measurement)
exceeds this threshold (+ or - direction in
respect to 0 on the phase TE graph), the
SJ Constant TE Threshold
Exceeded alarm is generated. The
Constant TE threshold must be at least 50
ns greater than the clear threshold.
Setting both the Const TE Threshold and
Const TE Clear Threshold to 0 disables
this TCA. The default is 0.
Const TE Clear Enter the Constant Time Error Clear
Threshold (ns) Threshold in nanoseconds. If the constant
measurement (average measurement)
meets this threshold (+ or - direction in
respect to 0 on the phase TE graph) clears
an existing SJ Constant TE
Threshold Exceeded alarm. The
default is 0.
Const TE Window (s) Enter the Constant Time Error Window
Size in seconds. This is the size of the
sliding window of sampled
measurements made for constant TE
calculation. The default is 1000.

5. Click OK.
6. In the tree pane, next to Clock Probes, click +.
The newly created Clock Probe entity is displayed.
7. Select the Clock Probe entity and in the window select the Status tab to verify the entry
and connection status as illustrated in the image below.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 502

Oscilloquartz: An ADVA Company Syncjack Testing

If any Source or Reference Failures are indicated, troubleshoot, and clear the failure as
necessary.
A Clock Probe can be edited after creation by right-clicking the entity name, and then
selecting Edit Clock Probe. All fields except the Clock Probe Index can be edited. Once
a probe is scheduled, it cannot be modified or deleted.

Editing or Deleting a Clock Probe

You can edit or delete a Clock Probe through the Syncjack application:

l On the toolbar, click the Syncjack icon.

– or –
l From the Application menu, select Syncjack.

To edit an existing Clock Probe:

1. In the selection tree, next to the System>NE-1>Clock Accuracy>Clock Probes entities,

click +.
2. Right-click the applicable Clock Probe entity, and then select Edit. The Edit Clock Probe
window opens.
3. Set the Clock Probe options (see Clock Accuracy Parameters).
4. Click OK.

To delete a Transparent Clock:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 503

Oscilloquartz: An ADVA Company Syncjack Testing

1. In the selection tree, next to the System>NE-1>Clock Accuracy>Clock Probes entities,

click +.
2. Right-click the applicable Clock Probe entity, and then select Delete.
3. Click OK.

Performing Clock Analysis

Syncjack Clock Analysis measurements are based on the PTP timestamps generated by the
clock under test.

Prerequisites
l The OSA 5422 is properly connected to the clock inputs to be measured and the
appropriate OSA 5422 interfaces have been configured. See Provisioning the
OSA 5422.

l The Slave port under test must populate the origin timestamp t3 in Delay_Req
messages to allow monitoring.

l This procedure requires a PTP Flow Point and a reference. To create a PTP Flow
Point, see Provisioning the Precision Time Protocol.

To perform clock analysis:

1. Create a PTP Clock Probe (see Creating a PTP Clock Probe).

2. Create a PTP Schedule (see Creating a Schedule).

3. Verify the Syncjack Schedule State and Test Progress (see Verifying the Syncjack
Schedule State and Testing Progress).

Creating a PTP Clock Probe

1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>Clock Analysis entities, click +.
3. Right-click PTP Clock Probes, and then select Create Clock Probe. A Create PTP
Clock Probe window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 504

Oscilloquartz: An ADVA Company Syncjack Testing

4. Set these PTP clock probe options:

Area Field Setting

Identification PTP Clock Probe Index EID for the probe. Enter a number from 1 to
4. This field is only configurable when the
PTP clock probe is created.
Name [MANDATORY] Enter a text identifier of up
to 15 characters with no spaces or special
characters for the probe.
Configurations PTP Flowpoint Select the applicable PTP Flowpoint.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 505

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Configurations IP Version Select the applicable IP version, where IPv4
(con't) is the only option supported.
Master IP Address Enter the IP address of the master clock. If
the PTP Flow Point Type is set to OC Slave,
the Master IP Address must be configured
the same as the SOOC.
Slave IP Address Enter the IP address of the slave clock. If the
PTP Flow Point Type is set to OC Slave, the
Slave IP Address must be configured the
same as the SOOC.
Slave Port Identity Enter the hex slave port identity. This field is
only enabled depending on the PTP
Flowpoint selected.
Master Port Identity Enter the hex master port identity. This field
is only enabled depending on the PTP
Flowpoint selected.
Direction Select the applicable Direction:

l Slave to Master
– or –
l Master to Slave

If the Flow Point Type of the associated PTP

Flow Point is set to OC Slave, Slave to
Master or Master to Slave can be selected.
If the Flow Point Type of the associated PTP
Flow Point is set to OC Master, only the
Slave to Master option is permitted. The
default is Slave To Master.
Reference Select the signal reference for this clock
probe.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 506

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Configurations Reference Expected QL Select the clock quality level of the selected
(con't) reference. The default is QL-None.
MTIE Mask Select the applicable MTIE Mask. The
default os G823 Pdh.
Mask Margin (%) Enter the applicable Mask Margin as a
percentage from 0 to 99.
Raw Data Collection If the Raw Data Collection Server is
provisioned, enable or disable sending raw
data to a remote raw data collection server.
The default is Disabled. See Provisioning
Raw Data Collection.
Measurement Type Select the measurement type as either
Frequency or Phase. The default is
Frequency.
Delay Compensation Enter the Delay Compensation in
(ns) nanoseconds for the known delay between
the master and slave, when the
measurement type is Master to Slave or
Master to Slave T4, or the known
asymmetry in case the measurement type is
2 Way. This option is only applicable if the
Measurement Type is set to Phase and the
Direction is not Slave to Master.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 507

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Configurations MTIE Restart Defines whether the MTIE measurement is
(con't) restarted every 24 hours at 00:00:00
according to the system time. This ensures
that the measurement is updated with the
most recent values. Select either:

l Enabled
– or –
l Disabled

The default is Disabled.

When restarted, the values of the Mask
Failure, Mask Crossed Time, Mask Margin
Failure, and Mask Margin Crossed Time are
reinitiated and start from a new time
period.
Note: If this setting is disabled, the MTIE
measurement is calculated over the entire
period from when the clock probe is
activated. Therefore, the MTIE graph can
include measurements that are not relevant
as they are dated.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 508

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

TE Monitoring Max TE Threshold (ns) Enter the Maximum Time Error Threshold in
Note: These nanoseconds. If the measurement exceeds
options are only this threshold (+ or - direction in respect to
enabled if the 0 on the phase TE graph), the SJ Max TE
Measurement Threshold Exceeded alarm is
Type is set to generated. The Max TE threshold must be
Phase. at least 50 ns greater than the clear
threshold. Setting both the Max TE
Threshold and Max TE Clear Threshold to 0
disables this TCA. The default is 0.
Max TE Clear Threshold Enter the Maximum Time Error Clear
(ns) Threshold in nanoseconds. If the
measurement meets this threshold (+ or -
direction in respect to 0 on the phase TE
graph) clears an existing SJ Max TE
Threshold Exceeded alarm. The default
is 0.
Const TE Threshold (ns) Enter the Constant Time Error Threshold in
nanoseconds. If the constant measurement
(average measurement) exceeds this
threshold (+ or - direction in respect to 0 on
the phase TE graph), the SJ Constant
TE Threshold Exceeded alarm is
generated. The Constant TE threshold must
be at least 50 ns greater than the clear
threshold. Setting both the Const TE
Threshold and Const TE Clear Threshold to
0 disables this TCA. The default is 0.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 509

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

TE Monitoring Const TE Clear Threshold Enter the Constant Time Error Clear
(con't) (ns) Threshold in nanoseconds. If the constant
measurement (average measurement)
Note: These meets this threshold (+ or - direction in
options are only
respect to 0 on the phase TE graph) clears
enabled if the
an existing SJ Constant TE
Measurement
Threshold Exceeded alarm. The default
Type is set to
Phase. is 0.
Const TE Window (s) Enter the Constant Time Error Window Size
in seconds. This is the size of the sliding
window of sampled measurements made
for constant TE calculation. The default is
1000.
Inst TE Threshold (ns) Enter the Instant Time Error Threshold in
nanoseconds. If the constant measurement
(average measurement) exceeds this
threshold (+ or - direction in respect to 0 on
the phase TE graph), the SJ Instant TE
Threshold Exceeded alarm is
generated. The Instant TE threshold must
be at least 50 ns greater than the clear
threshold. Setting both the Inst TE
Threshold and Inst TE Clear Threshold to 0
disables this TCA. The default is 0.
TE Monitoring Inst TE Clear Threshold Enter the Instant Time Error Clear Threshold
(con't) (ns) in nanoseconds. If the constant
measurement (average measurement)
Note: These meets this threshold (+ or - direction in
options are only
respect to 0 on the phase TE graph) clears
enabled if the
an existing SJ Instant TE Threshold
Measurement
Exceeded alarm. The default is 0.
Type is set to
Phase.

For more information on these options, see Clock Analysis Parameters.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 510

Oscilloquartz: An ADVA Company Syncjack Testing

5. Click OK.
6. In the selection tree, next to PTP Clock Probes, click +. The newly created PTP Clock
Probe entity is displayed.
7. Select the PTP Clock Probe entity and in the window select the Status tab to verify the
entry and connection status as illustrated in the image below.
If any Failures are indicated, troubleshoot, and clear the failure as necessary.
All PTP Clock Probes must use the same reference.
A PTP Clock Probe can be edited after creation by right-clicking the entity name, and
then selecting Edit PTP Clock Probe. All fields except the PTP Clock Probe Index can be
edited. Once a probe is scheduled it cannot be modified or deleted.

8. Repeat Steps #3 to 7 to create additional PTP Clock Probes, if applicable (up to 4).

Editing or Deleting a PTP Clock Probe

You can edit or delete a PTP Clock Probe through the Syncjack application:

l On the toolbar, click the Syncjack icon.

– or –
l From the Application menu, select Syncjack.

To edit PTP Clock Probe:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 511

Oscilloquartz: An ADVA Company Syncjack Testing

1. In the selection tree, next to the System>NE-1>Clock Analysis>PTP Clock Probes

entities, click +.
2. Right-click the applicable PTP Clock Probe entity, and then select Edit. The Edit Clock
Probe window opens.
3. Set the Clock Probe options (see Clock Analysis Parameters).
4. Click OK.

To delete a PTP Clock Probe:

1. In the selection tree, next to the System>NE-1>Clock Analysis>PTP Clock Probes

entities, click +.
2. Right-click the applicable PTP Clock Probe entity, and then select Delete.
3. Click OK.

Clock Analysis — Telecom Slave Score

If you configured a telecom slave in the OSA 5422 under PTP, you can use Syncjack to test
and score internal slave performance. Syncjack provides three scores for frequency and time
recovery:

l 5 – high score = high performance

l 4 – medium score = marginal performance
l 3 – low score = low performance

This scoring is used to estimate the frequency and phase accuracy of the internal OSA 5422
slave clock. Unlike network usability, this is the quality of the slave clock, not the network.
The input is PTP packets, the output is a frequency accuracy and a phase accuracy score of
3, 4, or 5 for each as performance monitor.

These tasks are related to the telecom slave scoring:

Viewing Telecom Slave Configurations and Statistics 512

Configuring T-SC Target Values for Frequency and Phase 513
Initializing the Telecom Slave Performance Monitoring Registers 514
Editing the Telecom Slave Performance Monitoring Thresholds 515

Viewing Telecom Slave Configurations and Statistics

1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 512

Oscilloquartz: An ADVA Company Syncjack Testing

2. In the selection tree, next to the System>NE-1>Clock Analysis entities, click +.

3. Select the Telecom Slave (TS-1-1) entity.
See Figure 24 for the configuration view and Figure 25 for the statistics summary view.

Figure 24: Telecom Slave Configuration View

Figure 25: Edit Telecom Slave Statistics Summary View

Configuring T-SC Target Values for Frequency and Phase

1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>Clock Analysis entities, click +.
3. Right-click the Telecom Slave (TS-1-1) entity, and then select Edit TelecomSlave
Analysis. The Edit Telecom Slave Analysis window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 513

Oscilloquartz: An ADVA Company Syncjack Testing

4. In the Configuration area, set these options:

l Frequency Recovery Target: Select the applicable value.

l Phase Recovery Target: Enter the applicable value in nanoseconds.

For more information on these options, see Telecom Slave Parameters.

5. Click OK.

Initializing the Telecom Slave Performance Monitoring

Registers
1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>Clock Analysis entities, click +.
3. Right-click the Telecom Slave (TS-1-1) entity, and then select Init Registers. The
Initialize Registers window opens.
4. In the Register and Interval Selection area, Interval and Bin Index menus, select the
applicable interval and bin index.
5. Click OK. The designated performance monitoring count registers are cleared.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 514

Oscilloquartz: An ADVA Company Syncjack Testing

Editing the Telecom Slave Performance Monitoring

Thresholds
1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>Clock Analysis entities, click +.
3. Right-click the Telecom Slave (TS-1-1) entity, and then select Edit Thresholds. The Edit
Thresholds window opens.
4. In the Entity Selection area, Entity menu, select the applicable port entity, and then
click OK. The Edit Thresholds window opens with a table listing the performance
monitoring thresholds related to the applicable port entity selected.
5. Edit the applicable thresholds for the applicable Monitored Type. Use the sliding bars on
the right of the window to view the data, as required.
6. Click OK.

Performing PTP Network Analysis

Syncjack PTP Network Analysis measures network conditions of the PTP communication
path. The measurement is based on Packet Delay (PD) and Packet Delay Variation (PDV)
either one-directional or two-directional. The input is reference clock used as reference to
the Master Clock. The output is network statistics, path delay and network usability score.

Prerequisites
l Connect the OSA 5422 to the clock inputs you want to measure.
l Configure the appropriate OSA 5422 interfaces. See Provisioning the OSA 5422.

To perform PTP network analysis:

1. Create a PTP Network Probe (see Creating a PTP Network Probe).

2. Create a PTP Schedule (see Creating a Schedule).

3. Verify the PTP Network Probe (see Verifying the PTP Network Probe).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 515

Oscilloquartz: An ADVA Company Syncjack Testing

Creating a PTP Network Probe

1. Select the Syncjack application by performing either of these steps:
On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>PTP Network Analysis entities, click +.
3. Right-click PTP Network Probes, and then select Create PTP Network Probe. The
Create PTP Network Probe window opens.

4. Set these PTP Network Probe options:

Area Field Setting

Identification PTP Network Probe EID for the probe. Enter a number from 1 to
Index 9. This field is only configurable when the
PTP network probe is created.
Name [MANDATORY] Enter a text identifier of up
to 15 characters with no spaces or special
characters for the probe.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 516

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Configurations PTP Flowpoint Select the applicable PTP Flowpoint.
IP Version Select the applicable IP version.
Master IP Address Enter the IP address of the master clock. For
parallel mode this IP must be as configured
for the PTP SOOC.
Slave IP Address Enter the IP address of the slave clock. For
parallel mode, the IP must be as configured
for the PTP SOOC.
Reference Select the signal reference for this probe.
Reference Expected QL Select the clock quality level of the selected
reference. The default is QL-None.
RPDV fw Low, ns Enter the applicable Residual Path Delay
Variation (RPDV) forward, low in
nanoseconds.
RPDV fw Medium, ns Enter the applicable RPDV forward, medium
in nanoseconds.
RPDV fw High, ns Enter the applicable RPDV forward, high in
nanoseconds.
Configurations RPDV rev Low, ns Enter the applicable RPDV reverse, low in
(con't) nanoseconds.
RPDV rev Medium, ns Enter the applicable RPDV reverse, medium
in nanoseconds.
RPDV rev High, ns Enter the applicable RPDV reverse, high in
nanoseconds.
PDV Cluster Range - Enter the applicable value in nanoseconds.
Assured, ns
PDV Cluster Range - Enter the applicable value in nanoseconds.
Satisfied, ns

For more information on these options, see PTP Network Analysis

Parameters.

5. Click OK.
In the selection tree, expand PTP Network Probes. The newly created PTP Network
Probe entity is displayed.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 517

Oscilloquartz: An ADVA Company Syncjack Testing

6. Select the newly created PTP Network Probe entity, and in the window that is displayed
select the Configuration tab to verify the entry.
A PTP Network Probe can be edited after creation by right-clicking the entity name and
selecting Edit Clock Probe. All fields, except the Clock Probe Index, can be edited.
When a probe is scheduled, it cannot be modified or deleted.

Verifying the PTP Network Probe

1. Select the PTP Network Probe entity and in the Configuration tab you can view the
Syncjack Schedule State and test progress. The State indicates whether the test is Failed,
Waiting (Scheduled), Running, or Completed.

2. Click the PTP Network Probe entity again to observe when the test is completed. If a
fixed Syncjack schedule fixed duration time was entered.
3. During the test or after the test is completed, the results are available by selecting the
applicable PTP Network Probe, and selecting the Statistics tab.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 518

Oscilloquartz: An ADVA Company Syncjack Testing

4. In the selection tree, select the PTP Network Analysis entity to view the PTP Network
Analysis results through the Dashboard meter.

5. In the selection tree, select the Network Element entity to view the PTP Network Analysis
and Global results through the Dashboard meter.
The Clock Analysis meter displays test results only if the associated Syncjack schedule is
present. Each result is associated with a color coded radio button according to its
Probe/Score (green, yellow, or red). If grey, this indicates the Syncjack schedule has been
deleted or no score results are present.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 519

Oscilloquartz: An ADVA Company Syncjack Testing

6. To initialize the performance monitoring registers, right-click the PTP Network Probe,
and then select Init Registers. Then follow the procedure in Initializing Performance
Monitoring Registers.

7. To edit the performance monitoring Thresholds, right-click the PTP Network Probe, and
then select Edit Thresholds. Then follow the procedure in Editing Performance
Monitoring Thresholds.

Editing or Deleting a PTP Network Probe (PTP

Probe)
1. On the toolbar, click Syncjack, or from the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>PTP Network Analysis>PTP Network
Probes entities, click +.
3. Right-click the applicable PTP Network Probe entity, and then select Edit. The Edit PTP
Network Probe window opens.
4. Set the PTP Network Probe options (see PTP Network Analysis Parameters).
5. Click OK.

To delete a PTP Network Probe:

1. In the selection tree, next to the System>NE-1>PTP Network Analysis>PTP Network

Probes entities, click +.
2. Right-click the applicable PTP Network Probe entity, and then select Delete.
3. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 520

Oscilloquartz: An ADVA Company Syncjack Testing

Creating a Schedule
You can create a Syncjack Schedule for any type of probe. The task below provides an
example of creating a schedule for a clock probe, but the same steps would be followed for
a PTP clock probe or network probe.

If the scheduled time expires, the probe sends raw data file without measurements with this
status: #Adva Status: NOTSCHEDULED.

To create a Syncjack Schedule:

1. In the selection tree, right-click SyncJack Schedules, and then select Create Schedule.
A Create Schedule window opens.

2. Set these Syncjack Schedule options:

Area Field Setting

Identification Schedule Index EID for the schedule. Enter a number
from 1 to 255.
Activity ID Enter a text identifier of up to 15
characters with no spaces or special
characters for the probe.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 521

Oscilloquartz: An ADVA Company Syncjack Testing

Area Field Setting

Schedule Parameters Schedule Type Select the applicable type of schedule,
where One Shot is the only option
supported.
Duration Select the schedule duration as either
Forever or Fixed. If Fixed is selected,
in the textbox enter the applicable
duration in seconds.
Start Time Select the schedule start time as either
Now or Future. If Future is selected,
in the applicable textboxes, enter the
date in the format yyyy-mm-dd and
time in the format hh:mm:ss for the
test to start.
Schedule SJ Test Items Select the applicable Probes for this
test from the list provided by clicking
the related check boxes.

For more information on these options, see Scheduled Syncjack Activity

Settings.

3. Click OK.
4. In the selection tree, expand Syncjack Schedules.
A new Syncjack Schedule entity is displayed.
5. To verify the entry, select the Syncjack Schedule entity.

Deleting a Schedule
1. In the selection tree, next to the System>NE-1>Syncjack Schedules entities, click +.
2. Right-click the applicable schedule entity, and then select Delete Schedule.
A Delete SyncJack Schedule window opens.
3. Click OK.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 522

Oscilloquartz: An ADVA Company Syncjack Testing

Verifying the Syncjack Schedule State

and Testing Progress
Once a clock probe or PTP clock probe is created and a Syncjack schedule is associated with
the probe, you can verify the state of the Syncjack schedule and test the progress of the
probe. This is performed in the selection tree by selecting the applicable clock probe entity
that you want to check, and then opening the Status tab (see Viewing the Status Tab).

When viewing the clock probe or PTP clock probe test results, there are a number of
different tabs available:

l Status
l Tests
l TIE/TE Graph
l Recent TIE/TE Graph
l Statistics

Each of these tabs are explained in the sections below with sample output.

Viewing the Status Tab 523

Viewing the Tests Tab 526
Viewing the TIE/TE Graph and Recent TIE/TE Graph Tabs 526
Viewing the Statistics Tab 529

Prerequisites
Verify that you set up raw data collection (see Provisioning Raw Data Collection).

Viewing the Status Tab

The Status tab enables you to observe the Syncjack schedule state and test the progress.
The state indicates whether the test is in any of these states:

l Not Scheduled
l Failed
l Waiting [Scheduled - Future]
l Running
l Completed

After the test is completed, a subset of the clock probe or PTP clock probe Status tab data
is available in a history entity (see Viewing History Results).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 523

Oscilloquartz: An ADVA Company Syncjack Testing

The task below provides an example for a clock probe, but the same
steps would be followed for a PTP clock probe.

To verify Syncjack Schedule State and test progress in the Status tab:

1. Select the Status tab

The Clock Probe Status window opens.

2. Click the Clock Probe entity again to observe continued progress while the test is
running. Observe the Actual Test Duration (s) status to determine how long the test
has been running and how much time is left before completion, if a Fixed Duration was
scheduled.
3. Click the Clock Probe entity again to observe when the test is completed, if a fixed
Syncjack schedule duration time was entered. An example is provided in this figure.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 524

Oscilloquartz: An ADVA Company Syncjack Testing

4. Observe the test result details by interval by viewing the Test Result table or hovering
the mouse over the interval marker in the graph.

5. Test results can be exported to Microsoft Excel or other programs by selecting the
Export button. A dialog box is displayed at the bottom of the window.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 525

Oscilloquartz: An ADVA Company Syncjack Testing

After opening the Excel file, the output is displayed as illustrated in this example.

Viewing the Tests Tab

After the test is completed, select the Tests tab to view test results in tabular format. Scroll
over to determine if any thresholds have been crossed.

Figure 26 provides an example for a clock probe. Similar output is displayed for a PTP clock
probe.

Figure 26: Tests Tab for Clock Probe

Viewing the TIE/TE Graph and Recent TIE/TE

Graph Tabs
In the TIE/TE Graph tab, test results are provided in a TIE Graph (see Figure 27). If a source
or reference failure occurs and eventually recovers during the Syncjack scheduled window,
the failed region is indicated by a red shadowed area of the TIE/TE graph (see Figure 28).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 526

Oscilloquartz: An ADVA Company Syncjack Testing

If the clock probe or PTP clock probe threshold levels are provisioned, select the Zoom to
TIE/TE Graph check box in the TIE/TE graph tab to zoom in on the threshold levels along
with measured results. Provisioned Threshold levels are identified in the legend at the
bottom of the window. For examples of the TIE/TE graphs with thresholds, see Figure 29
and Figure 30.

If the clock probe or PTP clock probe threshold levels are provisioned and thresholds have
been exceeded, the Clock Probe threshold exceeded alarms should be present once the
threshold has been crossed. For an example, see Figure 31. Provisioned Threshold levels are
identified in the legend at the bottom of the window.

If the test duration is longer than 2000 seconds, select the Recent TIE Graph tab to view
the last 2000 seconds of the test results.

The example figures provided in this section are for a clock probe. Similar
output is displayed for a PTP clock probe.

Figure 27: Clock Probe Result in TIE Graph

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 527

Oscilloquartz: An ADVA Company Syncjack Testing

Figure 28: Example Clock Probe TIE/TE Graph with Failed Region

Figure 29: Clock Probe - TIE/TE Graph Tab With Threshold Levels Identified

Figure 30: Clock Probe - TIE/TE Graph Tab With Zoom to TE Graph Selected

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 528

Oscilloquartz: An ADVA Company Syncjack Testing

Figure 31: Clock Probe State - Threshold Exceeded Alarms Present

Viewing the Statistics Tab

The Statistics tab provides data on the performance monitoring statistics in these different
tabs:

The figures provided in this section are for a clock probe. Similar output
is displayed for a PTP clock probe.

l Summary: Contains the most relevant information related to the MTIE and TE,
which are calculated from the beginning of the measurement. The TE measurement
performance monitoring is calculated and presented as the maximum average
signed value for 1s, 10s, 100s, 1000s, 10,000s, and 50,000s. For example, if the
current performance monitoring value is 150 ns and the next average calculation
bears -200 ns, the current performance monitoring value is -200 ns (see Figure 32).

Figure 32: Summary Tab Details in Statistics Tab

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 529

Oscilloquartz: An ADVA Company Syncjack Testing

l 15 Minute or 5 Minute: Depending on your configuration, performance

monitoring statistics are collected every 5 minutes or 15 minutes. The name of the
tab is dependent on the configuration, where the default is 15 minutes (see Figure
33).

Figure 33: 15 Minutes Tab Details in Statistics Tab

l 1 Day: performance monitoring statistics collected after 24 hours, which is the

average result for all TEs over this interval (see Figure 34).

Figure 34: 1 Day Tab Details in Statistics Tab

l Thresholds: Displays the thresholds you have configured when editing the
thresholds of the clock accuracy probe or clock analysis probe. Threshold SNMP
traps are generated if these thresholds are exceeded. See Figure 35.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 530

Oscilloquartz: An ADVA Company Syncjack Testing

Figure 35: Thresholds Tab Details in Statistics Tab

Viewing History Results

After a clock probe or clock PTP probe test is completed, a subset of the clock probe Status
tab data is available in a result entity. The location of the result entity depends on the type
of probe:

l Clock Probes: History Results>Clock Probe Result entities

l PTP Clock Probes: History Estimations>PTP Clock Probe Result entities

For more information on the Status tab, see Viewing the Status Tab.

Once the history results are displayed, you can export the results and obtain a MTIE
comparison (see Obtaining an MTIE Comparison).

You can also edit or delete a history result by right-clicking the applicable entity, and
selecting either Edit History Result or Delete History Result.

The task below provides an example of viewing history results for a clock
probe, but the same steps would be followed for a PTP clock probe.

To view history results:

1. In the selection tree, next to the System>NE-1>Clock Accuracy>History Results

entities, click +.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 531

Oscilloquartz: An ADVA Company Syncjack Testing

When viewing PTP clock probe history results, expand the System>NE-
1>Clock Analysis>History Estimations entities.

2. Select the applicable Clock Probe Result entity that you want to view.
A clock probe history Result window opens.

3. History Test results can be exported to Microsoft Excel or another program by selecting
the Export button.

Obtaining an MTIE Comparison

From a clock probe or PTP clock probe history Result window, you can obtain a MTIE
comparison.

To obtain a MTIE comparison:

1. In each applicable clock probe or PTP clock probe history Result window, select the Add
To Result Analysis check box .
2. In the selection tree, next to the System>NE-1>Result Analysis entities, click +.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 532

Oscilloquartz: An ADVA Company Syncjack Testing

3. Select MTIE comparison. The MTIE comparison results are displayed in the window. An
example is provided in this illustration for a clock probe.

Viewing Results in the Dashboard

Meter
You can view results using the dashboard meter for these entities:

l Clock Accuracy: Displays the Clock Accuracy results for each scheduled clock
probe.
l Clock Analysis: Displays the Clock Analysis results for each scheduled PTP clock
probe.
l PTP Network Analysis: Displays the PTP Network Analysis results for each
scheduled PTP network probe.

The meter displays test results only if the associated Syncjack schedule is
present. Each Probe/Score is associated with a color coded radio button
according to its test result (green, yellow, or red). If gray, this indicates the
Syncjack schedule has been deleted or no score results are present.

l NE-1: Displays the Syncjack Global results and individual probe results.

To view probe results through the probe entity:

The task below provides an example of viewing results for a clock probe
through the Clock Analysis entity. Follow the same steps for a PTP clock
probe or PTP network probe for the applicable entity.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 533

Oscilloquartz: An ADVA Company Syncjack Testing

1. In the selection tree, next to the System>NE-1entities, click +.

2. Select the Clock Accuracy entity to view the Clock Accuracy results using the
Dashboard meter. If two Clock Probes have been scheduled, the results of both Clock
Probes are displayed.

To view the results through the NE-1 entity:

1. In the selection tree, next to the System entity, click +.

2. Select the NE-1 entity to view each of the probe results and Global results through the
Dashboard meter.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 534

Oscilloquartz: An ADVA Company Syncjack Testing

Performing an MTIE Result Comparison

Syncjack MTIE Result Comparison provides a comparison chart of up to 4 Results.

To perform an MTIE result comparison:

1. Select the Syncjack application by performing either of these steps:

On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System>NE-1>Result Analysis entities, click +.
3. Right-click MTIE Comparison, and then select Configure. The Results window opens.

4. Enter these options to configure the MTIE Comparison:

o Select the applicable MTIE Mask.

o Select the check box for each applicable Probe Results, for a maximum of four, to
include in the comparison.

For more information on these options, see Result Analysis Parameters.

5. Click OK.
6. In the selection tree, select the MTIE Comparison entity. The MTIE Comparison results
are displayed in the window.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 535

Oscilloquartz: An ADVA Company Syncjack Testing

Configuring a Custom MTIE Mask

You can create a custom MTIE mask by configuring the default User MTIE Mask element
under NE-1. Once you use the custom MTIE mask in a SyncJack probe, it is not possible to
edit the mask.

To configure a custom MTIE mask:

1. From the toolbar, select SyncJack or from the Application menu, select SyncJack.
2. Under NE-1, right-click User MTIE Mask and then select Edit User Mask.
The User Mask Configuration screen is displayed.

3. Set these MTIE mask options:

Field Description
MTIE Mask Specify an easy to remember name for this custom mask. Default:
Name UserDefined.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 536

Oscilloquartz: An ADVA Company Syncjack Testing

Field Description
X, Y Display Specify up to 64 X, Y pairs that are used to display the mask on a graph.
Points Use a comma (,) to separate X from Y and a semicolon (;) to separate
pairs.
X – predefined observation intervals in seconds: 0.1, 0.2, 0.5, 1, 2, 5, 10,
20, 50, 100, 200, 500, 1000, 2000, 5000, 10000, 20000, 50000, 100000
Valid range: 0.1 to 100000.
Y – the expected MTIE results you have calculated in Measurement
Points.
Valid range: integers.
Measurement Enter a string of 19 expected MTIE results in nanoseconds (rounded to
Points the nearest integer). Calculate the results according to the standard
definition.
Each MTIE result corresponds to one of the observation intervals (X).
For example, the first element in the string corresponds to interval 0.1

l You can enter non-valid intervals by typing one or more -1 at the

beginning or end of the string.
l Except for non-valid intervals, each result must be equal or grater
than the previous.

4. Click OK to save the mask.

You can now select this mask by selecting UserDefined.
See this sample mask for G.812 Types II and III.

Sample mask for G.812 Types II and III:

1. For each of these intervals:

0.1, 0.2, 0.5, 1, 2, 5, 10, 20, 50, 100, 200, 500, 1000, 2000, 5000, 10000, 20000, 50000,
100000,
calculate the expected MTIE result according to the standard definition:

MTIE limit (ns) Observation interval t (s)

40 0.1 < t ≤ 1
40 × t 0.4 1 < t ≤ 10
100 t > 10

Expected MTIE results:

0.1 — 40
0.2 — 40

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 537

Oscilloquartz: An ADVA Company Syncjack Testing

0.5 — 40
1 — 40
2 — 53
5 — 76
10 — 100
20 — 100
50 — 100
100 — 100
200 — 100
500 — 100
1000 — 100
2000 — 100
5000 — 100
10000 — 100
20000 — 100
50000 — 100
2. In the Measurement Points field, enter 19 expected results as a comma-separated
string (round fractions to the nearest integer).
3. In the X, Y Display Points field, enter pairs of observation intervals (X) and expected
results (Y):
0.1,40;1,40;2,53;5,76;7,87;10,100;100000,100
Intervals between 10 and 10000 were omitted because they have the same value.

Provisioning Raw Data Collection

Perform this procedure when a raw data collection server is used for receiving Clock
Accuracy and Clock Analysis results for further calculations.

For security reasons, the system does not save raw data collection configuration such as
server IP and passwords in the configuration file.

Prerequisites
Ensure that the relevant file transfer protocol is enabled. See Configuring the System
Identity and Configuration.

To enable relevant file transfer protocol:

1. Select the Syncjack application by performing either of these steps:

On the toolbar, click the Syncjack icon.
– or –
From the Application menu, select Syncjack.
2. In the selection tree, next to the System entity, click +.

To provision the Raw Data Server:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 538

Oscilloquartz: An ADVA Company Syncjack Testing

1. In the selection tree, right-click Raw Data Collection, and then select Edit Raw Data
Server.
The Raw Data Collection window opens.

2. Set these raw data collection options:

Area Field Setting

Method File Transfer Method Select the applicable File Transfer Method.
The default is FTP.
Raw Data Server IP Enter the server IP address.
Server User ID Enter the server User ID.
User Password Enter the server User Password.

For more information on these options, see Raw Data Collection

Parameters.

3. Click OK.
4. In the selection tree, click Raw Data Collection to verify the entry.

To enable raw data collection on the relevant probe:

1. In the selection tree, next to the NE-1>Clock Accuracy / Clock Analysis entities, click +.
2. Right-click the relevant Clock Probe or PTP Clock Probe, and then select Edit Clock
Probe / Edit PTP Clock Probe.
The Edit Clock Probe/Edit PTP Clock Probe window opens.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 539

Oscilloquartz: An ADVA Company Syncjack Testing

3. In the Configuration area, Raw Data Collection menu, select Enabled, and then click
OK.
4. Schedule the Probe (see Performing Clock Accuracy Testing or Performing Clock
Analysis).
5. Concatenate the relevant files on the server.
For example, this script can be used in Linux:

#!/bin/bash

if [ "$2" == "" ]; then

script_name=`basename $0`
echo "USAGE: $script_name <out-file> <file1> <file2> ...
<fileN> "
exit 1
fi

out_file=$1
shift

header_lines=11
temp_file=tmp.txt

echo output file is $out_file

rm -f $temp_file
rm -f $out_file

while (( "$#" )); do

if [ ! -f $out_file ]; then
echo adding header
gzip -dc $1 | head -$header_lines > $out_file
fi

echo processing $1
head -n -1 $out_file > $temp_file
gzip -dc $1 | tail -n +$header_lines >> $temp_file
mv $temp_file $out_file

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 540

Oscilloquartz: An ADVA Company Syncjack Testing

shift
done

For example, this command concatenates all files with CLOCK_PROBE-1-1 string to CLOCK_
PROBE_ALL.txt output file:
adva_raw_data_unzip CLOCK_PROBE_ALL.txt `ls *CLOCK_PROBE-1-
1*.gz`

6. Load to the relevant software for analysis.

Raw Data File Format

Raw Data File Format – Header
#Type: [Phase|Frequency]
#Start: [start time yyyy/mm/dd/ hh:mm]
#Frequency: [Reference frequency in Hz]
#TimeMultiplier: 1 [time stamp multiplier]
#Multiplier: 1 [result multiplier]
#Title: [string 64]
#Adva Device: [ipAddress]
#Adva Probe: [ClockProbe|PTPClockProbe]
#Adva Reference: [Reference type]
#Adva Source: [Source type|measured PTP clock IP]
#Adva Direction: [Forward|Reverse|Two-Way|NA]
#Adva Version: 1.0
#Adva Status: RUNNING
#Adva MTIE Mask: G8272-PRTC
#Adva Mask Margin: 0

Example Clock Probe:

#Type: Phase
#Start: 2014/05/04 07:32:02
#Frequency: 10
#TimeMultiplier: 1
#Multiplier: 1
#Title: ClockProbe1
#Adva Probe: ClockProbe
#Adva Reference: 10-MHz
#Adva Source: TS
#Adva Direction: NA

Raw Data File Format – Measurement Results

Supported format is dual column: [time_from_start], [value]

Example:

2.3950001938E+03, 4.0000000000E-09
2.3951001938E+03, 4.0000000000E-09

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 541

Oscilloquartz: An ADVA Company Syncjack Testing

2.3952001938E+03, 8.0000000000E-09
2.3953001938E+03, 4.0000000000E-09
2.3954001938E+03, 4.0000000000E-09
2.3955001938E+03, 4.0000000000E-09
2.3956001938E+03, 4.0000000000E-09
2.3957001938E+03, 4.0000000000E-09

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 542

 Chapter G

Alarms, Events, Probable

Causes, and Error Codes
This section contains information supporting alarms and events generated by the system,
their meaning and suggested trouble clearing methods. This section contains the following
information:

Recommended Steps for Clearing Alarms 544

Error Codes and System Responses 545
Alarm Attributes, Probable Cause, and Troubleshooting 564

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 543

Recommended Steps for Clearing
Alarms
In the event that alarms are raised after commissioning the OSA 5422, you can try to
identify the alarm and the probable cause of the alarm, so you can clear it from the system.

To clear an alarm:

1. Ensure that an interface device, such as a craft interface, is connected to the network and
is operating correctly before continuing.
2. Establish a communication connection to the OSA 5422 and log in to the web-based
EMS (see Logging In).
3. Observe the Alarms pane to view all current alarms, and record the alarm severity. For an
overview of the web-based EMS components and the location of the Alarm window, see
Getting to Know the User Interface.
4. Determine which current alarm has the greatest service effect, and record the alarm.
Troubleshoot alarms according to this order:
a. Service-affecting (SA) critical alarms.
b. Major SA alarms.
c. Minor SA alarms.
d. Non-service-affecting (NSA) major alarms.
e. NSA minor alarms.
5. Locate the appropriate alarm indication description and suggested troubleshooting
techniques for the specific problem.
6. For identifying, interpreting, and troubleshooting alarms, see Alarm Attributes, Probable
Cause, and Troubleshooting.
For descriptions of connectors and front-panel LEDs, see the OSA 5422 Installation and
Commissioning guide.
7. After performing suggested troubleshooting actions, verify that the alarm or status
condition is now clear.
o If it is clear, record the time the alarm was cleared, and continue with the next step.

o If it is not cear, obtain assistance (see Obtaining Technical Assistance).

8. Repeat Step 5 and Step 6 for all alarms.
9. Observe the Alarms pane to view all current alarms, and then verify that the alarm
conditions are cleared.
o If it is clear, continue with the next step.

o If it is not cear, obtain assistance (see Obtaining Technical Assistance).

OSA 5422 R11.1.1 -Provisioning and Operations - Issue: A 544

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

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 102: 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:

l Authentication failed
l Radius setup failed
l Invalid password
ENTITY CONDITIONS
256 Entity does not exist.
257 Entity already exists.
258 Next child entity does not exist.
259 Set operation is not supported.
260 Create operation is not supported.
261 Delete operation is not supported.
262 _actiontype_ operation is not supported.
263 Get variable objects operation is not supported.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 545

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
264 Maximum (_maxnum_) number of _entityname_ entities has been reached.
265 Total _rsrc_ resource amount of _totalval_ exceeds max limit of _maxval_
266 Allocating_val_#_unit_of_rsrc_resource from _container_failed - total amount
of _totalval_#_unit1_ exceeds max limit of _maxval_#_unit2_
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_
Create denied: _why_
Delete denied: _why_
Edit denied: _why_
Retrieve denied: _why_
Action denied: _why_
Where Why is:

Object is transient

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 546

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
270 Operation denied: _why_
Create denied: _why_
Delete denied: _why_
Edit denied: _why_
Retrieve denied: _why_
Action denied: _why_
Where Why is:
Clock Probe belongs to an active schedule

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 547

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
271 - 275 Operation denied: _why_
Create denied: _why_
Delete denied: _why_
Edit denied: _why_
Retrieve denied: _why_
Action denied: _why_
Where Why is:

(xxx) not supported on CP unit return

(xxx) is used by IPV4 PROXY ARP ENTRY
(xxx) is used by IPV4 STATIC ARP ENTRY
(xxx) is used by IPV4 STATIC ROUTE
(xxx) state is not support on CP Unit
A2N Policer not specified for CTAG's Priority (xxx)
A member in the VID list (xxx) matches the primary vid of vlan entry [eid]
Address cannot be broadcast, mutlicast or all 0's
Admin State is (xxx)
Admin State is not in (xxx) state
An Ethernet port with speed configured as (xxx) cannot be added to the
reference selector list
Authentication Protocol cannot be (xxx)
Both Primary and Backup server have zero IP addresses
Build Shadow Tree failed
Cannot delete a scheduled probe
Cannot delete an active reflector
Cannot have both Primary and Backup server's IP addresses set to zero
Cannot not suspend an active reflector
Cannot resume a schedule that is not suspended
Cannot start non-suspended schedule
Cannot stop non-active schedule
Cannot suspend non-active schedule
Can't reopen System Default Db
Card (xxx) found in slot

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 548

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
271 - 275 Where Why is:
CIR and EIR cannot both be 0
(Continued) Clear not supported on CP unit
Community (xxx) used by Target Address (yyy)
Community (xxx) used by Target Parameter (yyy)
Config file is busy
Config operation failed
Configfile is not in progress
Create or Open configfile failed
Db State is not ok
DHCP is enabled
Diagnostics are active on Port
Diagnostics not supported on Access port
Data TLV exceed the allowed maximum of (xxx MAX)
Disable SFTP first, to disable the SSH
Duplicate VID list - duplicate entry (xxx) found in (eid)
enable SSH first, to enable SFTP
Enter a hex number following the MAC address
Incompatible (xxx) card for (yyy) slot
Internal error - unable to allocate resource
Internal error - unable to allocate VLAN entry resources
Internal error - unable to release resource
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
Invalid primary vid - must be 0, component primary vid or must be from the
vlan table
Loopback already exists
Loopback is active on Port

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 549

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
271 - 275 Where Why is:
Management Tunnel Buffer Size must be at least (xxx KB)
(Continued) Management Tunnel CIR must be at least (xxx) bps
Maximum management bandwidth (xxx bps) exceeded (yyy bps remaining)
N2A Rate Limiting is disabled.
NE already accepted
Network clock type may be set onlty via Sync
No VID based MEP can be created on Access port 2
NTP client is enabled
OAM is disabled on port
Only down MEP is allowed on network ports
Only COPPER port available
Only init/suspended/completed schedule can be deleted
Out of range. Enter a 2 byte integer
Port does not exist for (xxx)
Port is a FROM PORT of Network Element (xxx)
Port OAM is enabled
Port QL Mode is enabled
Port Rx Pause is enabled

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 550

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
271 - 275 Where Why is:
Primary vid [xxx] found in the VID list of [eid]
(Continued) Primary VID cannot be in the VID list
Protecting port is in Sync Reference list
Protection Group does not exist for port
Protection Switching is not supported in (xxx) mode
Regeneration currently in progress
Security level of the user (xxx) is (yyy)
SFTP can not be set to enabled, when trying to disable SSH
Shaper is used by Policer (xxx)
Shaped speed greater than Configured speed
Shaped speed cannot be 0
SSH can not be set to disabled, when trying to enable SFTP
Switch Action is not supported in (xxx) mode
System in Db Maintenance Mode
System Defaults Database is busy
System Defaults Value File is busy
Test not active
Test stream not active
The File description is invalid, length of string is 0-127 and can't contains
double quotation marks, semicolon(;) and pound(#)
The file name must be 1-32 characters long, must have only a-z, A-Z, 0-9, (.),
- and _, but can not be (.) or (..)
This object cannot be deleted
Tunnel IP address is being used as system source IP address
Tunnel IP address is being used by SNMP v1 trap PDU
Two vlan entries cannot have the same VID list for the same port
Valid Until date is in the past
Valid Until date is out of range allowed
VID member (xxx)
VLAN member (xxx) already exists at position (xxx)
VLAN member (xxx) does not exist
VPN OUI out of range (0 .. 0xFFFFFF)
276 Attribute values are inconsistent
277 _entityname_ does not exist

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 551

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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
280
281 Data not available for _entityeid_: _why_
Where Why is:

Admin State is UNASSIGNED

PM Thresholds not supported
PM not monitored on CP Flow

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 552

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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
reference selector list
An Ethernet port with SyncE mode disabled cannot be added to the
reference selector list
It is already present in the list
ATTRIBUTE SPECIFIC

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 553

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 554

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
512 Invalid value: _why_
Where Why is:
(continued) Cannot create (xxx) flow
Cannot create (xxx) flow with VLAN members
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 Access 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
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)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 555

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
512 Where Why is:
Invalid engine ID - must be 5 to 32 octets long (first bit is 1)
(continued) 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
Length exceeds limit - must be 1 to (xxx)
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
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
characters
Name must be unique
Negative number
Access 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 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)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 556

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
512 Where Why is:
Password cannot be “password” or “passw0rd”
(continued) 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 Access 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
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)
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
Specified IP address is already used by a Probe
Where Why is:
Specified IP address is already used by another Reflector
Specified MAC address is invalid
Specified name is already in use (xxx) and (yyy)
Specified tag is invalid

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 557

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
512 Start Time in the past is not allowed
SyncE Mode cannot be disabled because this port is used in the reference
(continued)
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 Network Clock Type
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)
Value (xxx) out of range
Value (xxx) out of range (xxx MIN… yyy MAX)
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 558

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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 not applicable _why_
Where Why is:
Management Traffic Bridging is enabled
Network mask is not applicable for PPP
DHCP is not applicable for PPP
RIPv2 is not applicable for PPP
SPECIAL CONDITIONS
768 Card _cardeid_ not present.
773 Invalid Loopback Configuration Type.
775 Resource in Use by Loopback.
780 Timed loopback with Vlan tag enabled.
781 Non-Vlan loopback with Vlan tag enabled.
784 Loopback is not active.
785 Loopback already exists.
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 559

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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
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

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 560

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 561

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
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
8000 MEIATTR_TIMING_SOURCE
8001 MEIATTR_MAX_SLAVE_SUPPORTED
8002 MEIATTR_MAX_STATIC_SLAVE_SUPPORTED
8003 MEIATTR_SLAVE_ANNOUNCE_MSG_RATE
8004 MEIATTR_SLAVE_SYNC_MSG_RATE
8005 MEIATTR_SLAVE_DELAY_RESP_MSG_RATE
8006 MEIATTR_ALIAS_ERROR

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 562

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 102: Error Codes and Definitions

Error Code Response
8007 MEIATTR_TIME_CLOCK_EID
8008 MEIATTR_TIMEREF
8009 MEIATTR_SYNC_OPER_TYPE
8010 MEIATTR_SYNC_REF_REQ
8011 MEIATTR_SYNC_DOMAIN
8012 MEIATTR_SELECTION_MODE
8192 Invalid message received
8193 Invalid user
8194 Unable to update profile
8195 Internal error
8196 Internal error
8197 Internal error - IPC
8198 Internal error
8199 Internal error - EP
8200 Invalid user name received
8201 insufficient privilege level
SNMP SPECIFIC
20480 Attribute is deprecated
20481 VLAN ID is not specified
20482 Invalid Data for Cable Length Benchmark, Required format xx.yy

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 563

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Alarm Attributes, Probable Cause, and

Troubleshooting
All the issues that can raise an alarm event have a soaking time of 2.5 seconds before the
alarm indication is raised. The problem causing the alarm event has to be clear for 10
seconds before the system clears the alarm indication.

The tables in this section list all OSA 5422 system alarms and default notification codes.
Each table contains a description of the alarm condition, probable cause and suggested
troubleshooting procedure.

To clear alarm conditions, start with the troubleshooting procedure in Recommended Steps
for Clearing Alarms.

Alarms and Events 564

Alarm Masking 621

Alarms and Events

These tables lists alarm conditions and their associated probable cause, default notification
code, and suggested troubleshooting. System components include these subsystems:

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 564

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

System Alarms
Table 103: System Alarms and Events
Default
Condition Description /
Troubleshooting Notification SA/NSA LED
Type Probable Cause
Code
Primary NTP Attempt to 1) Verify that the IP Minor NSA N/A
Server Failed connect to the address responds to
Primary NTP pings by performing
Server failed.1 both a ping and a trace
route from the
management tunnel’s
IP address.
2) Verify management
communication
configuration.
a) Target IP a) Repair IP address
address connectivity or routing
connectivity or problem.
routing problem.
b) No NTP server b) Switch to Backup
/ NTP server NTP Server. Repair NTP
down. server.

1When using Ethernet encapsulated management tunnels, the source IP address of the
ping used to validate reachability of the trap host is the IP address assigned to the
management tunnel, and not the system IP address.
OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 565
Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 103: System Alarms and Events

Default
Condition Description /
Troubleshooting Notification SA/NSA LED
Type Probable Cause
Code
Backup NTP Attempt to 1) Verify that the IP Minor NSA N/A
Server Failed connect to the address can be reached
Backup NTP (respond to pings) by
Server failed. performing both a ping
and a trace route from
the management
tunnel’s IP address.
2) Verify management
communication
configuration.
a) Target IP a) Repair IP address
address connectivity or routing
connectivity or problem.
routing problem.
b) No NTP server b) Switch to Primary
/ NTP server NTP Server. Repair NTP
down. server.
IP Address IP Address Verify management Critical SA N/A
Conflict Conflict communication
(declared when a configuration.
DHCP assigned
address overlaps
with an existing
subnet)
IPv6 Address IPv6 Address Verify management Critical SA N/A
Conflict Conflict communication
(declared when a configuration.
DHCP assigned
IPv6 address
overlaps with an
existing subnet)
Database - File Database file No action required. Not NSA N/A
Transfer In transfer is in Reported
Progress progress.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 566

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 103: System Alarms and Events

Default
Condition Description /
Troubleshooting Notification SA/NSA LED
Type Probable Cause
Code
SWDL - File Software No action required. Not NSA N/A
Transfer In Download file Reported
Progress transfer is in
progress.
SWDL - Software No action required. Not NSA N/A
Installation In Download Reported
Progress installation is in
progress.
SWDL - Software No action required. Not NSA N/A
Activation In Download Reported
Progress activation is in
progress.
SWDL - Software No action required. Not NSA N/A
Validation In Download Reported
Progress validation is in
progress.
SNMP Dying Database or Check database Minor NSA N/A
Gasp - Host Network issue. settings for SNMP
Unreachable Dying Gasp. If correct,
test network access -
Ping the Host address.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 567

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 103: System Alarms and Events

Default
Condition Description /
Troubleshooting Notification SA/NSA LED
Type Probable Cause
Code
SNMP Dying SNMP Dying Check database Minor NSA N/A
Gasp - Gasp is enabled settings for SNMP
Resource Busy on multiple trap Dying Gasp. Delete
hosts and there extra port assignments.
is 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.
DB Downgrade Database No Action Required Not NSA N/A
Downgrade - Reported
implementation
of a database file
below the
current release
level.
File Transfer In File transfer is in No action required. Not N/A N/A
Progress progress. Reported
Operation In Operation is in No action required. Not N/A N/A
Progress progress. Reported
Degraded System time is Minor NSA N/A
system time derived from the
from Time Time Clock with
Clock non traceable
time

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 568

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

NTEOSA 5422 Card and Shelf Alarms

Table 104: NTEOSA 5422 Card Alarms and Events
Default SA/
Condition Type Description Troubleshooting LED
Notification NSA
Communication Communication Equipment is Minor NSA N/A
Failure Failure malfunctioning.
Repair or replace
unit.
Equipment Fault Equipment fault Equipment is Critical SA Status
found. malfunctioning. Red
Repair or replace
unit.
Equipment Does Equipment does Verify the Critical SA Status
Not Match not match the provisioning Blinking
Provisioning provisioning. against the Red
equipment. Re-
provision as
necessary.
Equipment Equipment is Replace Critical SA N/A
Provisioned But provisioned but equipment or
Removed equipment is place out of
removed. service.
Test Alarm A test alarm is Ensure alarm Major NSA N/A
generated to propagates
check alarm properly.
propagation.
NTEOSA 5422 Shelf Alarms and Events
Over Equipment has Check ambient Minor NSA Status
Temperature exceeded the temperature and Red
temperature adjust. Verify that
limit. airflow
requirements are
met.
Under System Check ambient Minor NSA Status
Temperature temperature has temperature and Red
dropped below adjust.
the minimum
temperature
threshold.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 569

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 105: GNSS Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
GPS Antenna GPS Antenna Fail. l Check number of Minor NSA N/A
Alarm tracked Satellites.
Indication If 0, check
antenna cable is
securely
connected to the
antenna input.
l Ensure the
antenna required
power is
compatible with
the device
supplied power.
l Ensure sufficient
sky view is
available above
the antenna.
l Replace antenna.
Time Reference Minor NSA
Locked Out
Time Reference Time clock time Check the reference Minor NSA N/A
Unavailable reference failed. state and conditions.
Time Reference Time Clock time Check the reference Minor NSA N/A
Degraded reference cannot state and conditions.
provide ToD
information.
Time Reference Minor NSA
Forced Switch
Time Reference Minor NSA
Unavailable
WTR
Time Reference Minor NSA
Degraded WTR

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 570

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 105: GNSS Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
No Satellites No satellites for Check the following: Critical NSA N/A
Tracked the GNSS port 1. GNSS antenna
have been cable connection.
tracked. 2. C/No Mask,
Elevation Mask,
and PDOP Mask
settings.
3. The number of
tracking satellites.
4. Installation Type
(Full Sky View)
settings.
5. The
Administrative
state is set to IS
(in service.

Leap Second An expected leap This alarm cannot be Minor NSA N/A
Expected second update is cleared.
scheduled for
midnight. This
alarm is
generated 12
hours before the
scheduled
update time.
PPS Not The GNSS Ensure that enough Major NSA N/A
Generated receiver does not usable satellites are
generate a PPS available to generate
signal. accurate PPS output.
Sat Min1 The number of Change the Sat Min1 Major NSA N/A
Threshold satellites in use is Threshold value.
Crossed below the SAT_
Min1 threshold.
Sat Min2 The number of Change the Sat Min2 Major NSA N/A
Threshold satellites in use is Threshold value.
Crossed below the SAT_
Min2 threshold.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 571

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 105: GNSS Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
PDOP Mask PDOP mask value Improve the visibility Major NSA N/A
Cross is too high. of satellites by
improving the
antenna location, or
optimizing the
Elevation Mask and
C/No Mask and/or
include additional
GNSS constellations.
Alternatively, the
PDOP Mask can be
adjusted to the
observed value,
which may degrade
the accuracy of the
phase recovered by
the receiver.
Jamming The device Switch to backup Not reported NSA N/A
Detection monitors the reference and
background noise investigate the
and identifies possible reasons for
when a noise detected jamming.
exceeds the
threshold.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 572

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 105: GNSS Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Spoofing The device Switch to backup Major NSA N/A
Detection monitors changes reference and
in the GNSS investigate the
signal that possible reasons for
indicate external detected spoofing.
manipulation. The
detection is
successful only
when the original
signal is genuine
and then
transitions to a
spoofed signal.
The alarm is not
issued if the
device starts up
with a spoofed
signal. The device
cannot identify
spoofing when
only a single
constellation is
used.
Advanced Jamming Switch to backup Major NSA N/A
Jamming detected. reference and
Detection investigate the
possible reasons for
detected jamming.
Advanced Spoofing Switch to backup Major NSA N/A
Spoofing detected. reference and
Detection investigate the
possible reasons for
detected spoofing.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 573

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 106: PSU Alarms and Events

Default
Description/ SA/
Condition Type Troubleshooting Notification LED
Probable Cause NSA
Code
Communication Communication Communications Minor NSA N/A
Failure failure. malfunction
between PSU and
the device.
Replace PSU. If the
problem
continues, call
ADVA Technical
Support.
Equipment Does Equipment does Verify the Major NSA Status
Not Match not match the provisioning Blinking
Provisioning provisioning. against the Red
equipment. Re-
provision as
necessary.
Equipment Fault Power Supply Unit Equipment is Major NSA Status
power failure. malfunctioning. Red
Repair or replace
PSU.
Equipment Equipment is Replace Major NSA N/A
Provisioned But provisioned but equipment or
Removed equipment is place out of
removed. service.
Power: No Input Power: No power Verify power Major NSA Status
or Unit Fault input or unit fault. supply input. Red
Adjust power
supply input to
acceptable level or
replace PSU.
Power: No Power: No power Verify power Not Reported NSA N/A
Redundant Input input or unit fault supply input.
in one of the PSUs. Adjust power
supply input to
acceptable level or
replace PSU.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 574

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 107: DCN Port

Name Description To Clear Severity SA/NSA LED
Link Down Cable disconnected, Check physical Not SA N/A
cable fault, cabling, MDIX is not Alarmed
improper supported on DCN
configuration. port. Check settings
on system to match
DCN network
requirements.

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Alarm BITS Alarm Verify and troubleshoot Not Reported N/A N/A
Indication Indication Signal. clock reference. Verify
Signal Alarm Indication and troubleshoot
Signal indicates possible signal
that there is a mismatch. For proper
problem receiving BITS-IN and BITS-OUT
a signal from the operation with source
far end unit. When or test equipment sets,
a unit detects LOS manually match the
or LOF on its device network clock
receive side, it type with the BITS line
raises an AIS. type.
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".

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 575

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Frequency Frequency Offset. Verify and troubleshoot Minor N/A N/A
Offset The clock reference.
synchronization
circuit detected a
frequency offset
problem with the
BITS-IN port's
recovered clock.
The BITS-IN port
must be assigned
and the BITS-IN
port must be a
member of the
system clock
selector list for this
condition to exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 576

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Loss of BITS Loss of Verify and troubleshoot Minor N/A N/A
Frame Frame. Loss of clock reference. Verify
Frame indicates and troubleshoot
the incoming possible signal
T1/E1 signal is mismatch. In order for
severely proper BITS-IN and
degraded. LOF BITS-OUT inter-operate
indicates that a with source
signal is present, equipment/ test sets,
but the framing manually match the
pattern can not be device network clock
discerned. type with the BITS line
type.
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 BITS Loss of Signal. Verify and troubleshoot Minor N/A N/A
Signal BITS incoming clock reference
signal is lost. connection.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 577

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync QL A Synchronization Verify and troubleshoot Minor N/A N/A
Invalid Quality Level clock reference.
Invalid condition
exists when the
Ethernet port
receives SSM slow
protocol
messages whose
specified Quality
Level is invalid.
The Ethernet
port’s QL Mode
attribute must be
configured as
enabled for this
condition to exist.
Sync QL Synchronization Verify and troubleshoot Minor N/A N/A
Mismatch Quality Level clock reference.
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
must be
configured as
enabled and the
Expected QL
attribute must be
configured as
anything besides
None for this
condition to exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 578

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync Synchronization Verify and troubleshoot Minor N/A N/A
Reference Referencing 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
synchronization
reference (e.g.,
LNKDN, but not
EFMFAIL). The
BITS-IN port must
be a member of
the system clock
selector list for
this condition to
exist.
Sync A Sync Reference No Action Required. Minor N/A N/A
Reference has been restored
Wait To and is in WTR
Restore timing.
Sync A Sync Reference Test the Locked Out Minor N/A N/A
Reference has been locked Sync Reference and
Locked Out out. Usually due to remove lock out when
failure, reference is fully
configuration functional again.
changes planned
or maintenance
operations.
Sync A forced switch Evaluate reason for Minor N/A N/A
Reference operation has forced switch operation
Forced been performed and when appropriate,
Switch on a Sync remove the forced
Reference. switch.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 579

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 108: BITS In Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync A manual switch Evaluate reason for the Minor N/A N/A
Reference operation has manual switch
Manual been performed operation.
Switch on a Sync
Reference.

Table 109: BITS Out Port Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Output Squelch Quality Level Verify and Minor N/A N/A
Squelch. The BITS- troubleshoot clock
OUT port is reference.
squelched because
the system's QL is
lower than the
configured Squelch
QL attribute. Enable
the BITS-OUT port's
QL Mode attribute
and configure the
Squelch QL attribute
to anything except
none to apply the
condition.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 580

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 110: CLK Port Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync Sync Reference Failed. Ensure that the Minor NSA N/A
Reference This alarm reported CLK cable is
Failed when the CLK port is connected.
used as system
Synchronization input.
The port must be
assigned and the port
must be a member of
the system clock
selector list for this
condition to exist.
Frequency Frequency Offset. The Verify and Minor NSA N/A
Offset synchronization circuit troubleshoot clock
detected a frequency reference.
offset problem with
the port's 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.
Loss of Signal Input signal is lost. Verify and Minor NSA N/A
troubleshoot clock
reference
connection.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 581

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 110: CLK Port Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Output The port is squelched Verify and Minor NSA N/A
Squelch due to the port's troubleshoot clock
output signal QL reference.
being lower than the
port's configured
Squelch attribute. The
port's QL Mode
attribute must be
configured as enabled
and the Squelch QL
attribute must be
configured as
anything besides
None for this
condition to exist.
Sync A Sync Reference has Test the Locked Minor NSA N/A
Reference been locked out. Out Sync
Locked Out Usually due to failure, Reference and
configuration changes remove lock out
planned or when reference is
maintenance fully functional
operations. again.
Sync A forced switch Evaluate reason Minor NSA N/A
Reference operation has been for forced switch
Forced Switch performed on a Sync operation and
Reference. when appropriate,
remove the forced
switch.
Sync A manual switch Evaluate reason Minor NSA N/A
Reference operation has been for the manual
Manual Switch performed on a Sync switch operation.
Reference.

Sync A Sync Reference has No Action Minor NSA N/A

Reference been restored and is Required.
Wait To in Wait to Restore
Restore timing.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 582

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 111: PPS Port Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Output Output of the Verify and troubleshoot Minor NSA N/A
Squelch PPS port has PPS port source.
been squelched
due to change
of state of the
entity serving as
the port's
source.
Time PPS port Check PPS port Sync Minor NSA N/A
Reference provisioned as References, ensure that
Unavailable Time Reference PPS port Operational
of Time Clock state is "Normal" and
Clock Mode is "Locked".
and Unavailable
to serve as valid
reference.
LOSS No signal at the Major SA N/A
PPS port for
three seconds.

Table 112: Time of Day (TOD) & PPS Port Alarms and Events
Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Output Output of the Verify and Minor NSA N/A
Squelch TOD & troubleshoot TOD &
PPS port has PPS port source.
been
squelched due
to change of
state of the
entity serving
as the port's
source.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 583

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 112: Time of Day (TOD) & PPS Port Alarms and Events
Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Time TOD Check TOD & PPS port Minor NSA N/A
Reference & PPS port sync references,
Unavailable provisioned as ensure that TOD &
time reference PPS port operational
state is normal and
of time clock
clock code is locked.
and is
unavailable to
serve as valid
reference.
LOSS No signal at Major SA N/A
the PPS port
for three
seconds.
Leap Second Pending leap Minor NSA N/A
Expected second event.
No Valid TOD No TOD Major SA N/A
Input messages.
Message

Table 113: Time Clock Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync Synchronization Verify and Minor NSA N/A
Reference Referencing Failed. The troubleshoot clock
Failed Time Clock has failed reference.
in such a way that its
clock cannot be
recovered, thus
preventing it from
being used as a
synchronization
reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 584

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 113: Time Clock Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync QL Synchronization Verify and Minor NSA N/A
Mismatch Quality Level troubleshoot clock
Mismatch. The Time reference.
Clock receives SSM
messages whose
specified Quality Level
is lower than the
Expected QL. The Time
Clock 's QL Mode
attribute must be
configured as enabled
and the Expected QL
attribute must be
configured as anything
besides None for this
condition to exist.
Frequency Frequency Offset. The Verify and Minor NSA N/A
Offset synchronization circuit troubleshoot clock
detected a frequency reference.
offset problem with the
Time Clock's recovered
clock.
Sync QL A Synchronization Verify and Minor NSA N/A
Invalid Quality Level Invalid troubleshoot clock
condition exists when reference.
the Time Clock receives
SSM slow protocol
messages whose
specified Quality Level
is invalid. The Time
Clock’s QL Mode
attribute must be
configured as enabled
for this condition to
exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 585

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 113: Time Clock Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync A Sync Reference has Test the Locked Minor NSA N/A
Reference been locked out. Out Sync
Locked Out Usually due to failure, Reference and
configuration changes remove lock out
planned or when reference is
maintenance fully functional
operations. again.
Sync A forced switch Evaluate reason Minor NSA N/A
Reference operation has been for forced switch
Forced performed on a Sync operation and
Switch Reference. when appropriate,
remove the forced
switch.
Sync A manual switch Evaluate reason Minor NSA N/A
Reference operation has been for the manual
Manual performed on a Sync switch operation.
Switch Reference.

Sync A Sync Reference has No Action Minor NSA N/A

Reference been restored and is in Required.
Wait To WTR timing.
Restore
Switch Over Not Reported NSA N/A
Time Clock Time Reference Locked N/A Minor NSA N/A
Not Locked Out.
Frequency Time Clock Time N/A Minor NSA N/A
Lock Traceability status is
Time Freq Lock.
Frequency Time Clock Frequency N/A Minor NSA N/A
Not Traceability status is
Traceable Not Traceable.
Time Time Clock Time N/A Minor NSA N/A
Holdover Traceability status is
Holdover.
Time Not Time Clock Time N/A Minor NSA N/A
Traceable Traceability status is
Not Traceable.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 586

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Synchronization Alarms
Table 114: Synchronization (SYNC-1-1-1( Alarms and Events
Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
All Input Sync All non-locked out Verify and Major NSA N/A
Referenced synchronization troubleshoot clock
Failed references in the reference.
system clock
selector list have
failed. The system
clock selector list
must have at least
one SyncRef
member for the
condition to exist.
Sys Clock System Clock No action necessary. Not Reported NSA N/A
Mode - Fast Mode - Fast
Acquisition Acquisition
Synchronization.
This indicates the
clock selector is
acquiring the
phase of the
selected reference.

Sys Clock System Clock Verify synchronization Not Reported NSA N/A
Mode - Mode - Free provisioning to ensure
Freerunning Running option is set correctly.
Synchronization. Otherwise, no action is
necessary.
This indicates the
internal oscillator
is the source of
the system clock.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 587

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 114: Synchronization (SYNC-1-1-1( Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sys Clock System Clock Verify and Not Reported NSA N/A
Mode - Mode - Holdover troubleshoot clock
Holdover Synchronization. reference.
This indicates the
selected reference
is invalid and no
other valid input
reference is
available - and the
system clock has
previously locked
to the now invalid
reference.
Sys Clock System Clock Verify and Not Reported NSA N/A
Mode - Loss Mode - Loss of troubleshoot clock
of Lock Lock. This reference.
indicates the
selected reference
had locked and is
not invalid and the
lock has been lost.
While in this state,
the clock selector
will be attempting
to acquire the
phase of the
selected reference.

Average Clock was not No action necessary. Not Reported NSA N/A
Holdover synced long
Frequency enough to enter
Not Ready holdover and is
now freerunning.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 588

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 114: Synchronization (SYNC-1-1-1( Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Time Sync-1-1-1 Test the Locked Out Minor NSA N/A
Reference provisioned as Time Reference and
Locked Out Time Reference of remove lock out when
Time Clock and reference is fully
functional again.
has been Locked
out.
Time Sync-1-1-1 Evaluate reason for Minor NSA N/A
Reference provisioned as forced switch
Forced Switch Time Reference of operation and when
Time Clock and appropriate, remove
the forced switch.
Force Switch has
been applied.
Time Sync-1-1-1 Check Sync-1-1-1 Minor NSA N/A
Reference provisioned as Sync References,
Unavailable Time Reference of ensure that Sync-1-1-
Time Clock and 1 Operational state is
"Normal" and Clock
Unavailable to
Mode is "Locked".
serve as valid
reference.
Time Sync-1-1-1 N/A Minor NSA N/A
Reference provisioned as
Degraded Time Reference of
Time Clock and
can't provide valid
TOD. This
condition is
persistently
reported.
Time Sync element N/A Not Reported NSA N/A
Reference provisioned as
Unavailable Time Reference of
WTR Time Clock and
recovers from
Unavailable
condition.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 589

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 114: Synchronization (SYNC-1-1-1( Alarms and Events

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Time Sync element N/A Not Reported NSA N/A
Reference provisioned as
Degraded Time Reference of
WTR Time Clock and
recovers from
Degraded
condition.

Line Cards Alarms

Table 115: GE-4S Line Card Alarms and Events
Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Card not Ready The card is not ready Major SA
for operation
because the system
upgrades the card,
sync PLL is not
locked, TSGI or TSGII
is not locked, or any
other condition the
card is not delivering
the required service.
Equipment Equipment is Major SA N/A
Fault malfunctioning.
Repair or replace
card.
Equipment Equipment does not Verify the Major SA Status
Does Not match the provisioning Blinking
Match provisioning. against the Red
Provisioning equipment. Re-
provision as
necessary.
Equipment Equipment is Replace Major SA N/A
Provisioned But provisioned but equipment or
Removed equipment is place out of
removed. service.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 590

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 115: GE-4S Line Card Alarms and Events

Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Over Equipment has Check ambient Minor NSA N/A
Temperature exceeded the temperature and
temperature limit. adjust. Verify that
airflow
requirements are
met.
Time Src Major SA N/A
Unavailable
Sync Src Major SA N/A
Unavailable

Table 116: BITS-X16 Line Card Alarms and Events

Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Card not Ready The card is not ready Major SA
for operation
because the system
upgrades the card,
sync PLL is not
locked, TSGI or TSGII
is not locked, or any
other condition the
card is not delivering
the required service.
Equipment Equipment is Major SA N/A
Fault malfunctioning.
Repair or replace
card.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 591

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 116: BITS-X16 Line Card Alarms and Events

Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Equipment Equipment does not Verify the Major SA Status
Does Not match the provisioning Blinking
Match provisioning. against the Red
Provisioning equipment. Re-
provision as
necessary.
Equipment Equipment is Replace Major SA N/A
Provisioned But provisioned but equipment or
Removed equipment is place out of
removed. service.
Over Equipment has Check ambient Minor NSA N/A
Temperature exceeded the temperature and
temperature limit. adjust. Verify that
airflow
requirements are
met.

Table 117: MB GNSS Line Card Alarms and Events

Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Equipment Equipment is Major SA N/A
Fault malfunctioning.
Repair or replace
card.
Equipment Equipment does not Verify the Major SA Status
Does Not match the provisioning Blinking
Match provisioning. against the Red
Provisioning equipment. Re-
provision as
necessary.
Equipment Equipment is Replace Major SA N/A
Provisioned But provisioned but equipment or
Removed equipment is place out of
removed. service.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 592

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 117: MB GNSS Line Card Alarms and Events

Default
Condition SA/
Description Troubleshooting Notification LED
Type NSA
Code
Jamming The device monitors Switch to backup Not reported NSA N/A
Detection the background reference and
noise and identifies investigate the
when a noise possible reasons
exceeds the for detected
threshold. jamming.
Spoofing The device monitors Switch to backup Major NSA N/A
Detection changes in the GNSS reference and
signal that indicate investigate the
external possible reasons
manipulation. The for detected
detection is spoofing.
successful only when
the original signal is
genuine and then
transitions to a
spoofed signal. The
alarm is not issued if
the device starts up
with a spoofed
signal. The device
cannot identify
spoofing when only
a single constellation
is used.

Table 118: IRIG-B Line Card Alarms and Events

Default
SA/
Condition Type Description Troubleshooting Notification LED
NSA
Code
Equipment Fault Equipment is Major SA N/A
malfunctioning.
Repair or replace
card.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 593

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 118: IRIG-B Line Card Alarms and Events

Default
SA/
Condition Type Description Troubleshooting Notification LED
NSA
Code
Card Type Equipment does Verify the Major SA Status
Mismatch not match the provisioning against Blinking
provisioning. the equipment. Re- Red
provision as
necessary.
Card is Removed Equipment is Replace equipment Major SA N/A
provisioned but or place out of
equipment is service.
removed.
Temperature l Verify that Minor NSA N/A
Exceeded ambient
temperature does
not exceed
operational
temperature
range.
l Check proper
shelf installation
and make sure
enough space
between adjacent
devices.
l Replace the card.
Missing Cable The patch panel Verify that the Major SA N/A
high density required cable is
cabler or the fan connected properly.
out high density
cable is missing.
Loss Loss of signal Verify and Major SA N/A
troubleshoot clock
reference connection.
Leap Second A leap second Minor NSA N/A
Expected event is pending.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 594

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

NTP Clock Alarms

This table details the NTP clock alarm conditions and their associated probable cause,
default notification code, and suggested troubleshooting procedure.

Table 119: NTP Clock Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
No Symmetric key Upload and activate Major SA N/A
NTP Keys authentication is NTP keys files, see
enabled, but no Activating Symmetric
NTP keys file Key NTP
uploaded or activated. Authentication.
No The Autokey Update the Major SA N/A
Certificate certificate is not certificate, see
updated. Activating Autokey
Authentication.
Certificate The Autoky certificate Update the Minor NSA N/A
Expired is about to expire. certificate, see
Soon Activating Autokey
Authentication.

PTP Alarms
This section describes PTP alarm conditions:

Telecom Slave Alarms

This table details the PTP Telecom Slave alarm conditions and their associated probable
cause, default notification code, and suggested trouble-clearing procedure.

Manual configuration or automatic update of asymmetry delay

compensation can cause the telecom slave to change state with several
alarms..

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 595

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 120: Telecom Slave Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
Sync Synchronization Verify and Minor NSA N/A
Reference Referencing Failed. troubleshoot clock
Failed The TS has failed in reference.
such a way that its
clock cannot be
recovered, thus
preventing it from
being used as a
synchronization
reference. The TS
must be assigned for
this condition
primitive to exist.
Sync QL Synchronization Verify and Minor NSA N/A
Mismatch Quality Level troubleshoot clock
Mismatch. The TS reference.
receives SSM
messages whose
specified Quality Level
is lower than the
Expected QL. The TS's
QL Mode attribute
must be configured as
enabled and the
Expected QL attribute
must be configured as
anything besides
None for this
condition to exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 596

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 120: Telecom Slave Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
Frequency Frequency Offset. The Verify and Minor NSA N/A
Offset synchronization circuit troubleshoot clock
detected a frequency reference.
offset problem with
the TS's recovered
clock. The TS must be
assigned and the TS
must be a member of
the system clock
selector list for this
condition to exist.
Sync QL Synchronization Verify and Minor NSA N/A
Invalid Quality Level Invalid. troubleshoot clock
reference.
Sync A Sync Reference has Test the Locked Out Minor N/A N/A
Reference been locked out. Sync Reference and
Locked Out Usually due to failure, remove lock out
configuration changes when reference is
planned or fully functional
maintenance again.
operations.
Sync A forced switch Evaluate reason for Minor NSA N/A
Reference operation has been forced switch
Forced performed on a Sync operation and when
Switch Reference. appropriate, remove
the forced switch.
Sync A manual switch Evaluate reason for Minor NSA N/A
Reference operation has been the manual switch
Manual performed on a Sync operation.
Switch Reference.

Sync A Sync Reference has No Action Required. Minor NSA N/A

Reference been restored and is
Wait To in WTR timing.
Restore

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 597

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 120: Telecom Slave Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
All SOOCs All Slave-Only Verify and Critical SA N/A
Failed Ordinary Clocks troubleshoot clock
(SOOC) failed. The reference.
OC-S Virtual Port in a
Faulty state or a PTSF
Alarm exists on the
SOOC.
Telecom Telecom Slave in Verify and Not Reported NSA N/A
Slave in Freerun. The troubleshoot clock
Freerun recovered clock is the reference and
same as the internal provisioning.
oscillator and the
Telecom Slave is in
freerun.
Telecom Telecom Slave in Verify and Not Reported NSA N/A
Slave in Holdover. The troubleshoot clock
Holdover recovered clock is in reference and
holdover as there is no provisioning.
valid SOOC to support
clock recovery.
SJ No Time Syncjack is not locked Verify and Major SA N/A
Lock to a reference time troubleshoot clock
source. reference and
provisioning.
SJ No Syncjack is not locked Verify and Major SA N/A
Frequency to a reference troubleshoot clock
Lock frequency source. reference and
provisioning.
Time Telecom Slave N/A Minor NSA N/A
Reference provisioned as Time
Locked Out Reference for the
Time Clock and has
been locked out.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 598

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 120: Telecom Slave Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
Time Telecom Slave N/A Minor NSA N/A
Reference provisioned as Time
Forced Reference for the
Switch Time Clock and has
been Forced.
Time Telecom Slave Check the Telecom Minor NSA N/A
Reference provisioned as Time Slave Frequency
Unavailable Reference for the traceability status
Time Clock and (Syncjack clock
Unavailable. analysis is required).
If Syncjack is not
available, check the
Telecom Slave
Frequency Recovery
state.
Time Telecom Slave Check the Telecom Minor NSA N/A
Reference provisioned as Time Slave Time
Degraded Reference for the traceability status
Time Clock and can't (Syncjack clock
provide valid TOD. analysis is required).
If Syncjack is not
available, check the
Telecom Slave Phase
Recovery state.
Telecom Telecom Slave is not N/A Minor NSA N/A
Slave in Time locked to TOD.
Freerun
Telecom Telecom slave time N/A Not Reported NSA N/A
Slave in Time recovery is in
Holdover Holdover.
Time Telecom Slave N/A Minor NSA N/A
Reference provisioned as Time
Unavailable Reference for the
WTR Time Clock and is in
recovery process from
Unavailable condition.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 599

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 120: Telecom Slave Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
Time Telecom Slave N/A Minor NSA N/A
Reference provisioned as Time
Degraded Reference for the
WTR Time Clock and is in
recovery process from
Degraded condition.

SOOC Alarms
This table details PTP Slave-Only Ordinary Clocks (SOOC) alarm conditions and their
associated probable cause, default notification code, and suggested trouble clearing
procedure.

Table 121: SOOC Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
AADC AADC Failed alarm is Verify and Minor NSA N/A
Failed asserted if a reference time troubleshoot clock
stamp is not observed. reference.
Clock Class If the received clock class is Verify the Major NSA N/A
Mismatch greater than the expected grandmaster or
clock class value, the boundary clock
packets for the grandmaster status.
or boundary clock that are
sending this clock class are
dropped.
PTSF - Loss Packet Timing Signal Fail - a) Verify and Minor NSA N/A
Sync Loss of Synchronization. A troubleshoot clock
Sync/Followup is not reference.
received before
syncReceiptTimeout or
Delay Response is not
received before
delRespReceiptTimeout.
A loopback on the port on
which the PTP Flowpoint of b) Release
the SOOC exists will result loopback.
in a PTSF - Loss of Sync.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 600

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 121: SOOC Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
PTSF - Loss Packet Timing Signal Fail - a) Verify and Minor NSA N/A
Announce Loss Announce. Announce troubleshoot clock
is not received before reference.
announceReceiptTimeout.
A loopback on the port on
b) Release
which the PTP Flowpoint of
loopback.
the SOOC exists will result
in a PTSF - Loss Announce.
PTSF - Packet Timing Signal Fail - Verify and Minor NSA N/A
Unusable Unusable. The PTP packet troubleshoot clock
stream is not usable for reference.
clock recovery. For
example, unable to recover
clock due to unacceptable
PTP packet PDV.

PTP Clock Alarms

This table details PTP Clock alarm conditions and their associated probable cause, default
notification code, and suggested trouble-clearing procedure.

Manual configuration or automatic update of asymmetry delay

compensation can cause the PTP clock to change state with several alarms..

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 601

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 122: PTP Clock Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync Synchronization Verify and Minor NSA N/A
Reference Referencing Failed. troubleshoot clock
Failed The PTP Clock has reference.
failed in such a way
that its clock cannot
be recovered, thus
preventing it from
being used as a
synchronization
reference. The PTP
Clock must be
assigned for this
condition primitive
to exist.
Sync QL Synchronization Verify and Minor NSA N/A
Mismatch Quality Level troubleshoot clock
Mismatch. The PTP reference.
Clock receives SSM
messages whose
specified Quality
Level is lower than
the Expected QL. The
PTP Clock's QL
Mode 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 Synchronization Verify and Minor NSA N/A
Invalid Quality Level Invalid. troubleshoot clock
reference.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 602

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 122: PTP Clock Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync A Sync Reference Test the Locked Out Minor NSA N/A
Reference has been locked out. Sync Reference and
Locked Out Usually due to remove lock out
failure, configuration when reference is
changes planned or fully functional
maintenance again.
operations.
Sync A forced switch Evaluate reason for Minor NSA N/A
Reference operation has been forced switch
Forced performed on a Sync operation and when
Switch Reference. appropriate, remove
the forced switch.
Sync A manual switch Evaluate reason for Minor NSA N/A
Reference operation has been the manual switch
Manual performed on a Sync operation.
Switch Reference.

Sync A Sync Reference No Action Required. Minor NSA N/A

Reference has been restored
Wait To and is in WTR timing.
Restore
Time PTP Clock N/A Minor NSA N/A
Reference provisioned as Time
Locked Out Reference for the
Time Clock and has
been locked out.
Time PTP Clock N/A Minor NSA N/A
Reference provisioned as Time
Forced Reference for the
Switch Time Clock and has
been Forced.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 603

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 122: PTP Clock Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Time PTP Clock Check the PTP Clock Minor NSA N/A
Reference provisioned as Time Frequency
Unavailable Reference for the traceability status
Time Clock and (Syncjack clock
Unavailable. analysis is required).
If Syncjack is not
available, check the
PTP Clock
Frequency Recovery
state.
Time PTP Clock Check the PTP Clock Minor NSA N/A
Reference provisioned as Time Time traceability
Degraded Reference for the status (Syncjack
Time Clock and can't clock analysis is
provide valid TOD. required). If
Syncjack is not
available, check the
PTP Clock Phase
Recovery state.
Time PTP Clock N/A Minor NSA N/A
Reference provisioned as Time
Unavailable Reference for the
WTR Time Clock and is in
recovery process
from Unavailable
condition.
Time PTP Clock N/A Minor NSA N/A
Reference provisioned as Time
Degraded Reference for the
WTR Time Clock and is in
recovery process
from Degraded
condition.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 604

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 122: PTP Clock Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
PTP Clock in PTP Clock in Verify and Not Reported NSA N/A
Frequency Frequency Freerun. troubleshoot clock
Freerun The recovered clock reference and
is the same as the provisioning.
internal oscillator
and the PTP Clock is
in freerun.
PTP Clock in PTP Clock is not N/A Not Reported NSA N/A
Time locked to TOD.
Freerun
PTP Clock in PTP Clock time N/A Not Reported NSA N/A
Time recovery is in
Holdover Holdover.
PTP Clock PTP Clock Time Not Verify and Major NSA N/A
Time Not Traceable. troubleshoot clock
Traceable reference and
provisioning.
PTP Clock PTP Clock Frequency Verify and Minor NSA N/A
Frequency Not Traceable. troubleshoot clock
Not reference and
Traceable provisioning.

PTP Port Alarms

This table details PTP Port alarm conditions and their associated probable cause, default
notification code, and suggested trouble-clearing procedure.

Table 123: PTP Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Announce Announce Timeout - PTP Port has to Minor NSA N/A
Timeout alarm is asserted once receive at least
Announce message one Announce
wasn’t received at the message. Verify
slave for a specified and troubleshoot
time period network and
(configurable). provisioning.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 605

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 123: PTP Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Clock Class If the received clock Verify the Major NSA N/A
Mismatch class is greater than grandmaster or
the expected clock boundary clock
class value, the status.
packets for the
grandmaster or
boundary clock that
are sending this clock
class are dropped.
Delay Delay Response Verify and Minor NSA N/A
Response Timeout- alarm is troubleshoot
Timeout asserted once Delay network and
response message provisioning.
wasn’t received at the
slave for a specified
time period
(configurable).
Multiple Multiple Peers- alarm Alarm is cleared Major SA N/A
Peers is asserted if PTP Port when PTP Port
received one received for 50-70
Announce messages sec Announce
from more than one messages from
PTP Port. single PTP Port.
Verify and
troubleshoot
network and
provisioning.
Sync Sync Timeout- alarm PTP Port has to Minor NSA N/A
Timeout is asserted once Sync receive at least
message wasn’t one Sync
received at the slave message. Verify
for a specified time and troubleshoot
period (configurable). network and
provisioning.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 606

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 123: PTP Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Wrong Wrong Domain - Alarm is cleared if Major SA N/A
Domain alarm is asserted if PTP Port received
PTP Port received for 50-70 sec
Announce messages Announce
with domain number message with a
that is not equal to correct domain
the domain number number. Verify
configured for the and troubleshoot
parent PTP Clock. network and
provisioning.
Max The number of salves Set extra slave to Major SA N/A
Expected exceeds the out of service or
Slave configured maximum increase the
number of expected maximum number
slave for the profile. of expected slaves.

L3 PTP Port Alarms

This table details L3 PTP Port alarm conditions and their associated probable cause, default
notification code, and suggested trouble-clearing procedure.

Table 124: L3 PTP Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Announce The port did not The L3 PTP port Minor NSA N/A
Timeout receive PTP announce has to receive at
message in the least one
specified time Announce
message. Verify
and troubleshoot
network and
provisioning.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 607

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 124: L3 PTP Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync The port in slave The port must Minor NSA N/A
Timeout mode did not receive receive at least
PTP sync messages for one sync message.
the specified time. Verify and
troubleshoot
network and
provisioning.
Delay Resp The port in slave Verify and Minor NSA N/A
Timeout mode did not receive troubleshoot
PTP Delay_Resp network and
messages for the provisioning.
specified time.
Wrong The port received Alarm is cleared Major SA N/A
Domain Announce messages when the L3 PTP
with domain number port receives for
that is not equal to 50-70 sec
the domain number Announce
configured for the message with a
parent PTP Clock. correct domain
number. Verify
and troubleshoot
network and
provisioning.
PTSF- The PTP packet timing Verify and Major SA N/A
Unusable signal is not usable for troubleshoot
the slave to achieve network and
the performance provisioning.
target.
AADC Failed Automatic Asymmetry Verify and Minor NSA N/A
Delay Compensation troubleshoot
failed. network and
provisioning.
PTP Ports PTP Port state has Not reported NSA
State been changed.
Changed

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 608

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Access Port Alarms

This table details the Access Port (including Line Card Access Port) alarm conditions and
their associated probable cause, default notification code, and suggested trouble-clearing
procedure.

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Duplex Duplex mode of Determine the Major SA Facility
Mode of Far the connected expected port Yellow
End Device equipment is speed setting and
Unknown unknown. The ensure that both
unit determined it ends are
cannot conclude configured to
negotiation with reflect that setting.
remote end on
the Ethernet port.
Although auto
negotiation
failure is a minor
alarm, it is usually
followed by a
critical alarm due
to link down.
Link Down - Critical SA
Deactivated
(Access Port
only)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 609

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Link Down - Link Down is Wait a few Critical SA Facility
Cause Not generated when a moments for the Red
Determined physical system to isolate
Link/Rate
connection is lost the trouble and
Off
on a good link on observe another
the Ethernet Link Down
interface port condition on this
(Access or interface.
Network). Upon Troubleshoot
the loss of according to the
connection on a new condition.
given port, this is
the first
notification being
sent, before any
specific cause is
determined (such
as cable fault or
cable removed).
Link Down - Link Down is Perform an Critical SA Facility
Cable Fault generated when a Etherjack Red
physical Diagnostic test.
Link/Rate
connection is lost Repair the cable
Off
on a good link on using test results.
the Ethernet
interface port
(Access or
Network). A Cable
Fault notification
is sent when it is
determined that
the link is down
due to a cable
fault on a copper
(RJ-45) port.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 610

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Link Down - Link Down is Insert or repair Critical SA Facility
Cable generated when a cable. Red
Removed physical
Link/Rate
connection is lost
Off
on a good link on
the Ethernet
interface port
(Access or
Network). A Cable
Removed
notification is
sent when it is
determined that
the link is down
due to a cable
being locally
removed from its
RJ-45 port
connection.
Link Down - Link Down is Test and repair far Critical SA Facility
Auto- generated when a end equipment. Red
Negotiation physical
Link/Rate
Failed connection is lost
Off
on a good link on
the Ethernet
interface port
(Access or
Network). Auto
negotiation fault
indicates the Far
End is not
advertising its
auto negotiation
rate.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 611

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Link Down Link Down is Perform an Critical SA Facility
generated when a Etherjack Red
physical Diagnostic test.
Link/Rate
connection is lost Repair the port
Off
on a good link on using test results.
the Ethernet
interface port
(Access or
Network).
Link Down - A Link Down Verify Master Critical SA Facility
Master Slave Master Slave Slave Red
Config Configuration configuration.
Link/Rate
condition is set
Off
when the
Ethernet port fails
to auto negotiate
when configured
as a master or
slave due to a
misconfiguration
of the
master/slave
settings between
the near end and
the far end.
Receiving The total number Verify the signal Major SA Facility
Jabber of packets leaving the far Red
received were end, through any
longer than the inter- mediate
MTU size, and equipment, and at
had either a bad the near end.
frame check Probable cause:
sequence (FCS) network problem,
with an integral or possibly a bad
number of octets cable. Repair faulty
(FCS Error), or a equipment or
bad FCS with a cable.
non-integral
number of octets
(alignment error).

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 612

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
SFP is not SFP is not Remove SFP Minor NSA N/A
qualified qualified, but module and
(Fiber only) inventory replace with an
information ADVA Optical
indicates that it Networking-
may still work. approved module
for that interface
type.
SFP - Small Form-factor Remove SFP Critical SA Facility
Provisioning Plug-able (SFP) module and Red
Mismatch optics module replace with an
Link/Rate
(Fiber only) mismatch. The ADVA Optical
Off
installed SFP Networking-
module does not approved module
match the for that interface
provisioned type.
module type for
the interface. The
system expects
the SFP to
conform to the
MSA specification
for inventory
contents and and
alarm will be
raised if the SFP’s
inventory data
does not reflect
that the device
supports the
configured speed.
SFP - Small Form-factor Install SFP module. Critical SA Facility
Removed Plug-able optics Red
(Fiber only) module is
Link/Rate
removed.
Off
SFP - Small Form-factor Replace SFP Critical SA Facility
Transmit Plug-able optics module. Red
Fault module failure.
(Fiber only)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 613

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync Synchronization Verify Minor NSA N/A
Reference Referencing synchronization
Failed Failed. The Access network and
Port has failed in provisioning.
such a way that
its clock cannot
be recovered,
thus preventing it
from being used
as a
synchronization
reference (such as
LNKDN, but not
EFMFAIL). The
Ethernet port
must be a
member of the
system clock
selector list for
this condition to
exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 614

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Loss of ESMC Loss of Ethernet Verify Minor NSA N/A
Synchronization synchronization
Messaging network and
Channel (ESMC). provisioning.
The Ethernet port
fails to receive an
Synchronization
Status Messaging
(SSM) slow
protocol message
within a 5 second
period and clears
as soon as a
single SSM is
received. The
Ethernet port’s QL
Mode attribute
must be
configured as
enabled for this
condition to exist.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 615

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync QL Synchronization Verify Minor NSA N/A
Mismatch Quality Level synchronization
Mismatch. The network and
Access Port provisioning.
receives SSM
messages whose
specified Quality
Level is lower
than the Expected
QL. The port's QL
Mode attribute
must be
configured as
enabled and the
Expected QL
attribute must be
configured as
anything besides
None for this
condition to exist.
Frequency Synchronization Verify Minor NSA N/A
Offset Frequency Offset. synchronization
The network and
synchronization provisioning.
circuit detected a
frequency offset
problem with the
Access Port’s
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.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 616

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync QL Synchronization Verify Minor NSA N/A
Invalid Quality Level synchronization
Invalid. The network and
Ethernet port provisioning.
receives SSM slow
protocol
messages whose
specified Quality
Level is invalid.
The Ethernet
port's QL Mode
attribute must be
configured as
enabled for this
condition
primitive to exist.
Bandwidth Bandwidth Verify provisioning Major SA Facility
Exceeds Exceeds and adjust Red
Negotiated Negotiated accordingly.
Speed Speed.
(Access Port
only)
Sync A Sync Reference No Action Minor NSA N/A
Reference has been restored Required.
Wait To and is in WTR
Restore timing.
Sync A Sync Reference Test the Locked Minor NSA N/A
Reference has been locked Out Sync
Locked Out out. Usually due Reference and
to failure, remove lock out
configuration when reference is
changes planned fully functional
or maintenance again.
operations.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 617

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 125: Access Port Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
Sync A forced switch Evaluate reason Minor NSA N/A
Reference operation has for forced switch
Forced been performed operation and
Switch on a Sync when appropriate,
Reference. remove the forced
switch.
Sync A manual switch Evaluate reason Minor NSA N/A
Reference operation has for the manual
Manual been performed switch operation.
Switch on a Sync
Reference.
Link Control Critical SA
Protocol Fail
(Access Port
only)
Link Control Critical SA
Protocol
Loopback
(Access Port
only)

Syncjack Alarms
This section describes Syncjack alarm conditions:

Clock Probe Alarms

This table details the Clock Probe alarm conditions and their associated probable cause,
default notification code, and suggested trouble-clearing procedure.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 618

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 126: Clock Probe Alarms

Condition Default
Description Troubleshooting SA/NSA LED
Type Notification
SJTEST Probe Reference For case of external Minor NSA N/A
Reference signal failed. May be signal check cable
Fail caused by signal loss connection.
or signal accuracy
degradation
detected.
SJTEST Probe source signal For case of external Minor NSA N/A
Source Fail failed. May be signal check cable
caused by signal loss connection.
or signal accuracy
degradation
detected.
SJ Max TE Indicates a N/A Minor NSA N/A
Threshold maximum TE
Exceeded accumulated time
reaches a given
threshold.
SJ Constant Indicates a constant N/A Minor NSA N/A
TE TE (a “DC”/static
Threshold offset component of
Exceeded TE) reaches a given
threshold.

PTP Clock Probe Alarms

This table details the PTP Clock Probe alarm conditions and their associated probable cause,
default notification code, and suggested trouble-clearing procedure.

Table 127: PTP Clock Probe Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
SJTEST Probe Reference For case of external signal Minor NSA N/A
Reference signal failed. May check cable connection.
Fail be caused by signal
loss or signal
accuracy
degradation
detected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 619

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 127: PTP Clock Probe Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
SJTEST No PTP Clock probe Make sure PTP Clock Minor NSA N/A
Timestamp does not receive under test event messages
valid timestamps in comprise valid
the PTP event timestamps.
messages.
SJTEST No PTP Clock probe Validate PTP Clock Probe Minor NSA N/A
Messages does not receive configuration, check
PTP event connectivity to the Clock
messages from the under test.
Clock under test.
SJ Max TE Indicates a N/A Minor NSA N/A
Threshold maximum TE
Exceeded accumulated time
reaches a given
threshold.
SJ Constant Indicates a constant N/A Minor NSA N/A
TE Threshold TE (a “DC”/static
Exceeded offset component
of TE) reaches a
given threshold.
SJ Instant TE Indicates an instant N/A Minor NSA N/A
Threshold TE time reaches a
Exceeded given threshold.

PTP Network Probe Alarms

This table details the PTP Network Probe alarm conditions and their associated probable
cause, default notification code, and suggested trouble-clearing procedure.

Table 128: PTP Network Probe Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
SJTEST Probe Reference For case of external Minor NSA N/A
Reference signal failed. May be signal check cable
Fail caused by signal loss connection.
or signal accuracy
degradation
detected.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 620

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 128: PTP Network Probe Alarms

Condition Default SA/
Description Troubleshooting LED
Type Notification NSA
SJTEST No PTP Clock probe does Validate PTP Clock Minor NSA N/A
Messages not receive PTP event Probe configuration,
messages from the check connectivity to
Clock under test. the Clock under test.

Alarm Masking
These tables provide the alarm masking rules, where certain alarms or conditions can mask
the raising of an underlying condition, and until the “masking” alarms are cleared, the
underlying alarms cannot be seen.

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
10MZ Port (CLK)
freqoff Frequency Offset freqoff (no masking)
los Loss of Signal los (no masking)
qlsqlch QL Squelch qlsqlch (no masking)
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
BITS In Port
ais Alarm Indication Signal ais and not los
AIS alarm is also triggered
when E1 input is connected to
BITS input that is configured to
2.048 MHz.
freqoff Frequency Offset freqoff (no masking)
lof Loss of Frame lof and not los or ais
los Loss of Signal los (no masking)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 621

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
qlinvalid Sync QL Invalid qlinvalid and not los or lof or
ais
qlmismatch Sync QL Mismatch qlmismatch and not qlinvalid
or los or lof or ais
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
BITS Out Port
qlsqlch QL Squelch qlsqlch (no masking)
BITS Out x16 Card
eqptflt Equipment Fault eqptflt and not eqptremoved
or mismatch
mismatch Equipment Does Not Match mismatch and not
Provisioning eqptremoved
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
PPS x16 Port Card
eqptflt Equipment Fault eqptflt and not eqptremoved
or mismatch
mismatch Equipment Does Not Match mismatch and not
Provisioning eqptremoved
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
CLK x16 Port Card
eqptflt Equipment Fault eqptflt and not eqptremoved
or mismatch
mismatch Equipment Does Not Match mismatch and not
Provisioning eqptremoved

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 622

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
TOD and PPS x16 Port Card
eqptflt Equipment Fault eqptflt and not eqptremoved
or mismatch
mismatch Equipment Does Not Match mismatch and not
Provisioning eqptremoved
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
Clock Probe
sjConstTeThrshld SJ Constant TE Threshold sjConstTeThrshld (no masking)
Exceeded
sjtealert SJ Max TE Threshold sjtealert (no masking)
Exceeded
sjtestreferencefail SJTEST Reference Fail sjtestreferencefail (no masking)
sjtestsourcefail SJTEST Source Fail sjtestsourcefail (no masking)
DCN Port
lnkdown Link Down lnkdown and not
lnkdownunisolated or
lnkdownautonegfailed or
lnkdownmasterslavecfg,
lnkdowncablefault or
lnkdowncableremoved or
lnkdeactivated or SGEO or
sfpmismatch or sfpremoved or
sfptxfault or dyinggasp.
Ethernet Port

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 623

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
autonegunknown Duplex Mode of Farend autonegunknown and not
Device Unknown lnkdown or lnkdownunisolated
or lnkdowncableremoved or
lnkdowncablefault or
lnkdownautonegfailed or
lnkdownmasterslavecfg or
lnkdeactivated or rxjabber or
SGEO or sfpmismatch or
sfpremoved or sfptxfault or
dyinggasp.
bwexceedednegspeed Bandwidth Exceeds bwexceedednegspeed (no
Negotiated Speed masking)
freqoff Frequency Offset freqoff (no masking)
lcpfail Link Control Protocol Fail lcpfail and not lcploopback or
SGEO or dyinggasp
lcploopback Link Control Protocol lcploopback and not SGEO or
Loopback dyinggasp
lnkdeactivated Link Down - Deactivated lnkdeactivated and not
sfpmismatch or sfpremoved or
sfptxfault or SGEO or
dyinggasp
lnkdown Link Down lnkdown and not
lnkdownunisolated or
lnkdownautonegfailed or
lnkdownmasterslavecfg,
lnkdowncablefault or
lnkdowncableremoved or
lnkdeactivated or SGEO or
sfpmismatch or sfpremoved or
sfptxfault or dyinggasp.
lnkdownautonegfailed Link Down - Auto- lnkdownautonegfailed and not
Negotiation Failed SGEO or sfpmismatch or
sfpremoved or sfptxfault or
dyinggasp or lnkdeactivated.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 624

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
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
Config not SGEO or sfpmismatch or
sfpremoved or sfptxfault or
dyinggasp or lnkdeactivated
lnkdownunisolated Link Down - Cause Not lnkdownunisolated and not
Determined lnkdownautonegfailed or
lnkdownmasterslavecfg or
lnkdowncablefault or
lnkdowncableremoved or
lnkdeactivated or SGEO or
sfpmismatch or sfpremoved or
sfptxfault or dyinggasp
qlinvalid Sync QL Invalid qlinvalid and not lnkdown or
lnkdownunisolated or
lnkdowncableremoved or
lnkdowncablefault or
lnkdownautonegfailed or
lnkdownmasterslavecfg or
lnkdeactivated or rxjabber or
autonegunknown or SEGO
sfpmismatch or sfpremoved or
sfptxfault

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 625

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
qlmismatch Sync QL Mismatch qlmismatch and not qlinvalid
or lnkdown or
lnkdownunisolated or
lnkdowncableremoved or
lnkdowncablefault or
lnkdownautonegfailed or
lnkdownmasterslavecfg or
SGEO or sfpmismatch or
sfpremoved or sfptxfault or
lnkdeactivated or rxjabber or
autonegunknown
rfi Remote Fault Indication rfi and not lnkdown or SGEO
or sfpmismatch or sfpremoved
or sfptxfault or dyinggasp
rxjabber Receiving Jabber rxjabber and not lnkdown or
lnkdownunisolated or
lnkdowncableremoved or
lnkdowncablefault or
lnkdownautonegfailed or
lnkdownmasterslavecfg or
lnkdeactivated or SGEO or
sfpmismatch or sfpremoved or
sfptxfault or dyinggasp
sfpmismatch SFP - Provisioning sfpmismatch and not
Mismatch sfpremoved or SGEO
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
syncref Sync Reference Failed syncref (no masking)
syncreffrc A forced switch operation syncreffrc (no masking)
has been performed on a
Sync Reference.
syncreflck Sync Reference Locked Out syncreflck (no masking)
syncrefman Sync Reference Manual syncrefman (no masking)
Switch

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 626

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
syncrefwtr Sync Reference Wait To syncrefwtr (no masking)
Restore
testalarm Test Alarm testalarm (no masking)
GPS/GNSS Port
gpsantennafail GPS Antenna Alarm gpsantennafail (no masking)
Indication
leapsecondexpected Leap Second Expected leapsecondexpected (no
masking)
min-sat-1-thrshld-crossed Sat Min1 Threshold Crossed min-sat-1-thrshld-crossed and
not gpsantennafail or min-sat-
2-thrshld-crossed
min-sat-2-thrshld-crossed Sat Min2 Threshold Crossed min-sat-2-thrshld-crossed and
not gpsantennafail
nosatellitercv No Satellites Tracked nosatellitercv and not
gpsantennafail
pdop-mask-cross PDOP Mask Cross pdop-mask-cross (no masking)
pps-not-generated PPS Not Generated pps-not-generated and not
gpsantennafail
timeRefUnavailable Time Reference Unavailable timeRefUnavailable (no
masking)
timeRefDegraded Time Reference Degraded timeRefDegraded (no masking)
NTEOSA 5422 Card
ctneqpt Communication Failure ctneqpt and not eqptremoved
or mismatch
eqptflt Equipment Fault eqptflt and not eqptremoved
or mismatch
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
mismatch Equipment Does Not Match mismatch and not
Provisioning eqptremoved
testalarm Test alarm testalarm (no masking)
NTEOSA 5422 Shelf
overtemp Over Temperature overtemp (no masking)
undertemp Under Temperature undertemp (no masking)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 627

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
Power Supply (PSU)
ctneqpt Communication Failure ctneqpt (no masking)
eqptflt Equipment Fault eqptflt (no masking)
mismatch Equipment Does Not Match mismatch (no masking)
Provisioning
eqptremoved Equipment Provisioned But eqptremoved (no masking)
Removed
pwrnoinputunitfault PWR: No Input Or Unit Fault pwrnoinputunitfault (no
masking)
Pulse Per Second (PPS) Port
qlsqlch Output Squelch synctimeout (no masking)
PTP Clock
ptpfreqfrun PTP Clock in Frequency ptpfreqfrun (no masking)
Freerun
ptpfreqhldovr PTP Clock in Frequency ptpfreqhldovr (no masking)
Holdover
ptpfreqnottraceable PTP Clock Frequency Not ptpfreqnottraceable (no
Traceable masking)
ptptimefrun PTP Clock in Time Freerun ptptimefrun (no masking)
ptptimehldovr PTP Clock in Time Holdover ptptimehldovr (no masking)
ptptimenottraceable PTP Clock Time Not ptptimenottraceable (no
Traceable masking)
qlinvalid Synchronization Quality qlinvalid (no masking)
Level Invalid.
qlmismatch Synchronization Quality qlmismatch and not qlinvalid
Level Mismatch.
syncref Synchronization syncref (no masking)
Referencing Failed.
syncreffrc Sync Reference Forced syncreffrc (no masking)
Switch
syncreflck A Sync reference has been syncreflck (no masking)
locked out.
syncrefman Sync Reference Manual syncrefman (no masking)
Switch

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 628

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
syncrefwtr Sync Reference Wait To syncrefwtr (no masking)
Restore
timeRefDegraded Time Reference Degraded timeRefDegraded (no masking)
timeRefDegradedWTR Time Reference Degraded timeRefDegradedWTR (no
WTR masking)
timeRefFrc Time Reference Forced timeRefFrc (no masking)
Switch
timeRefLock Time Reference has been timeRefLock (no masking)
locked out.
timeRefUnavailable Time Reference are timeRefUnavailable (no
Unavailable. masking)
timeRefUnavailableWTR Time Reference Unavailable timeRefUnavailableWTR (no
WTR masking)
PTP Clock Probe
sjConstTeThrshld SJ Constant TE Threshold sjConstTeThrshld (no masking)
Exceeded
sjInstTeThrshld SJ Instant TE Threshold sjInstTeThrshld (no masking)
Exceeded
sjtealert SJ Max TE Threshold sjtealert (no masking)
Exceeded
sjtestnomessages SJTEST No Messages sjtestnomessages (no masking)
sjtestnotimestamp SJTEST No Timestamp sjtestnotimestamp (no
masking)
sjtestreferencefail SJTEST Reference Fail sjtestreferencefail (no masking)
PTP MCI
maxexpectedslaves Max Expected Slaves maxexpectedslaves (no
masking)
PTP Network Probe
sjtestnotimestamp SyncJack Test No sjtestnotimestamp (no
Timestamp masking)
sjtestreferencefail SyncJack Test Reference sjtestreferencefail (no masking)
Fail.
PTP Port
announcetimeout Announce Timeout announcetimeout (no masking)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 629

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
clock-class-mismatch Clock Class Mismatch clock-class-mismatch (no
masking)
delayresptimeout Delay Response Timeout delayresptimeout (no masking)
multiplepeers Multiple Peers multiplepeers (no masking)
synctimeout Sync Timeout synctimeout (no masking)
wrongdomain Wrong Domain wrongdomain (no masking)
maxexpectedslaves Max Expected Slaves maxexpectedslaves (no
masking)
Slave Only ordinary Clock (SOOC)
clock-class-mismatch Clock Class Mismatch clock-class-mismatch (no
masking)
ptsflossofannounce Packet Timing Signal Fail - ptsflossofannounce (no
Loss Announce. Announce masking)
is not received before
announceReceiptTimeout.
ptsflossofsync Packet Timing Signal Fail - ptsflossofsync (no masking)
Loss of Synchronization. A
Sync/Followup is not
received before
syncReceiptTimeout or
Delay Response is not
received before
delRespReceiptTimeout.
ptsfunusable Packet Timing Signal Fail - ptsfunusable (no masking)
Unusable. The PTP packet
stream is not usable for
clock recovery. For example,
unable to recover clock due
to unacceptable PTP packet
PDV.
aadcfailed AADC Failed aadcfailed (no masking)
Synchronization
allsyncref All Input Sync Referenced allsyncref (no masking)
Failed
frngsync Sys Clock Mode - frngsync (no masking)
Freerunning

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 630

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
fstsync Sys Clock Mode - Fast fstsync (no masking)
Acquisition
hldovrsync Sys Clock Mode - Holdover hldovrsync (no masking)
losloc Sys Clock Mode - Loss of losloc (no masking)
Lock
avghldovrfrqnotrdy Average Holdover avghldovrfrqnotrdy (no
Frequency Not Ready masking)
timeRefLock Time Reference Locked Out timeRefLock (no masking)
timeRefUnavailable Time Reference Unavailable timeRefUnavailable (no
masking)
timeRefUnavailableWTR Time Reference Unavailable timeRefUnavailableWTR (no
WTR masking)
timeRefDegraded Time Reference Degraded timeRefDegraded (no masking)
timeRefFrc Time Reference Forced timeRefFrc (no masking)
Switch
timeRefDegradedWTR Time Reference Degraded timeRefDegradedWTR (no
WTR masking)
System
bckupntpsvrFailed Backup NTP server failed. bckupntpsvrFailed (no
Attempt to connect to the masking)
Backup NTP Server failed
due to:
a) Target IP address
connectivity or routing
problem.
b) No NTP server / NTP
server down.
db-ftip Database - file transfer in db-ftip (no masking)
progress.
dbdowngradeip Database downgrade dbdowngradeip (no masking)
standing condition.
gen-filexfer-ip File Transfer In Progress. gen-filexfer-ip (no masking)
gen-oper-ip Operation In Progress. gen-oper-ip (no masking)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 631

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
ipaddrconflict IP Address Conflict. ipaddrconflict (no masking)
Declared when a DHCP
assigned address overlaps
with an existing subnet.
primntpsvrFailed Primary NTP Server Failed. primntpsvrFailed (no masking)
Attempt to connect to the
Primary NTP Server
failed1due to:
a) Target IP address
connectivity or routing
problem.
b) No NTP server / NTP
server down.
snmpdghostresourcesbusy Dying Gasp resources busy. snmpdghostresourcesbusy (no
masking)
snmpdghostunresolved Dying Gasp host snmpdghostunresolved (no
unresolved. masking)
swdl-actip Software download - swdl-actip (no masking)
activation in progress.
swdl-ftip Software download - file swdl-ftip (no masking)
transfer in progress.
swdl-instip Software download - swdl-instip (no masking)
installation in progress.
swdl-valip Software download - swdl-valip (no masking)
validation in progress.
Telecom Slave
allsoocsfailed All SOOCs Failed allsoocsfailed (no masking)
freqoff Frequency Offset freqoff (no masking)
qlinvalid Sync QL Invalid qlinvalid (no masking)
qlmismatch Sync QL Mismatch qlmismatch and not qlinvalid

1When using Ethernet encapsulated management tunnels, the source IP address of the ping used to
validate reach ability of the trap host is the IP address assigned to the management tunnel, and not the
system IP address.

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 632

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
sjnofreqlock SyncJack is not locked to a sjnofreqlock (no masking)
reference frequency source.
sjnotimelock SyncJack is not locked to a sjnotimelock (no masking)
reference time source.
sjnofreqlock SYNCJACK No Frequency sjnofreqlock (no masking)
Lock
sjnotimelock SYNCJACK No Time Lock sjnotimelock (no masking)
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
timeRefDegraded Time Reference for the Time timeRefDegraded (no masking)
Clock and can't provide
valid TOD.
timeRefDegradedWTR Time Reference for the Time timeRefDegradedWTR (no
Clock and is in recovery masking)
process from Degraded
condition.
timeRefFrc Telecom Slave provisioned timeRefFrc (no masking)
as Time Reference for the
Time Clock and has been
Forced.
timeRefLock Time Reference for the Time timeRefLock (no masking)
Clock has been locked out.
timeRefUnavailable Time Reference for the Time timeRefUnavailable (no
Clock are Unavailable. masking)
timeRefUnavailableWTR Time Reference Unavailable timeRefUnavailableWTR (no
WTR masking)
tsfreerun Telecom Slave In Freerun tsfreerun (no masking)
tsholdover Telecom Slave In Holdover tsholdover (no masking)
Time Clock

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 633

Oscilloquartz: An ADVA Company Alarms, Events, Probable Causes, and Error Codes

Table 129: Alarm Masking Rules

Condition Type
Alarm Rule
SNMP Alarm Name GUI Alarm Name
timeClockNotLocked Time Reference Locked Out. timeClockNotLocked (no
masking)
timeFreqNotTraceAble Time Clock Frequency timeFreqNotTraceAble (no
Traceability status is Not masking)
Traceable.
timeHoldOver Time Clock Time timeHoldOver (no masking)
Traceability status is
Holdover.
timeNotTraceAble Time Clock Time timeNotTraceAble (no
Traceability status is Not masking)
Traceable.
Time of Day (Tod) Port
qlsqlch QL Squelch qlsqlch (no masking)

OSA 5422 R11.1.1 Provisioning and Operations - Issue: A 634