EMS-APT V3.1 Performance Management Guide PDF

EMS-APT®
Version 3.1
Performance Management
Guide
EMS-APT Performance Management Guide
V3.1
Catalog No: X35650
Drawing No: 4BGHT6-EMSW-415
July 2014
1st Edition
ECI's NPT-1200, NPT-1020, NPT-1021, and NPT-1010 comply with the CE2.0 standard.
ECI's NPT-1600 complies with the MEF9 and MEF14 standards.
ECI's qualification lab is accredited by A2LA for competence in electrical testing according to
the International Standard ISO IEC 17025-2005 General Requirements for the Competence of
Testing and Calibration Laboratories.
ECI's management applications run on VMWare virtualization hypervisors.
© Copyright by ECI, 2013-2014. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Ltd. (“ECI”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE
AGREEING TO BE BO UND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN
THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR
OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM.
The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent, and other laws protecting
intellectual property, as well as any specific agreement protecting ECI's rights in the aforesaid information. Neither this document nor the
information contained in the documentation and/or disk may be published, reproduced, or disclosed to third parties, in whole or in part, without
the express prior written permission of ECI. In addition, any use of this document, the documentation and/or the disk, or the information contained
therein for any purposes other than those for which it was disclosed, is strictly forbidden.
ECI reserves the right, without prior notice or liability, to make changes in equipment design or specifications. Information supplied by ECI is
believed to be accurate and reliable. However, no responsibility whatsoever is assumed by ECI for the use ther eof, nor for th e rights of third parties,
which may be affected in any way by the use and/or dissemination thereof. Any repr esentation(s) in the documentation and/or disk concerning
performance of ECI product(s) are for informational purposes only and are not warranties of product performance or otherwise, either express or
implied. ECI's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty offered by ECI.
The documentation and/or disk is provided “AS IS” and may contain flaws, omissions, or typesetting errors. No warranty is granted nor liability
assumed in relation thereto, unless specifically undertaken in ECI's sales contract or order confirmation. Information contained in the
documentation and in the disk is periodically updated, and changes will be incorporated in subsequent editions. If you have encountered an error,
please notify ECI. All specifications are subject to change without prior notice. All graphics included in this document are for illustrative purposes
only and might not correspond with your specific product version.
The documentation and/or disk and all information contained therein is owned by ECI and is protected by all relevant copyright, patent, and other
applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any
other copyrighted material (for example, a book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as applicable. YOU MAY NOT USE, COPY,
MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHO LE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE.
ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI.
All trademarks mentioned herein are the property of their respective holders.
ECI shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in
connection with this documentation and/or disk, the information contained ther ein, its use, or otherwise. Notwithstanding the generality of the
aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage
which may arise in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if advised of the
possibility of such damages.
The end user her eby undertakes and acknowledges that they read the "Befor e You Start/Safety Guidelines" instructions (when provided by ECI) and
that such instructions were understood by them. It is hereby clarified that ECI shall not be liable to you or to any other party for any loss or damage
whatsoever or howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failing to fulfill in whole or in part the "Before
You Start/Safety Guidelines" instructions.
Contents
1 About This Guide ............................................................................................ 1-1
1.1 Overview ...................................................................................................................... 1-1
1.2 Intended Audience ........................................................................................................ 1-1
1.3 Document Contents ...................................................................................................... 1-1
1.4 Notes and Warnings ...................................................................................................... 1-1
1.5 Related Publications ...................................................................................................... 1-2
1.6 How to Obtain ECI Telecom Technical Documentation..................................................... 1-3
1.7 Technical Assistance ...................................................................................................... 1-3
2 Fault Management ......................................................................................... 2-1

2.1 Overview ...................................................................................................................... 2-1
2.2 Configuring Fault Management ...................................................................................... 2-1
2.2.1 Configuring NE Fault Settings....................................................................................................... 2-1
2.2.2 Monitoring and Reporting Alarms............................................................................................... 2-5
2.2.3 Setting Switch Alarms................................................................................................................... 2-9
2.2.4 Managing External Alarms ......................................................................................................... 2-11
2.2.5 Performing Severity Settings...................................................................................................... 2-13
2.2.6 Performing Alarm Notification Settings .................................................................................... 2-15
2.2.7 Viewing Alarm Log File ............................................................................................................... 2-18
2.2.8 Finding Alarm Definition............................................................................................................. 2-19
2.3 Managing Current Alarms ............................................................................................ 2-19
2.3.1 Viewing Current Alarms.............................................................................................................. 2-20
2.3.2 Determining the Cause of an Alarm .......................................................................................... 2-22
2.3.3 Filtering Current Alarms ............................................................................................................. 2-23
2.3.4 Sorting Current Alarms............................................................................................................... 2-25
2.3.5 Acknowledging Current Alarms ................................................................................................. 2-25
2.3.6 Exporting Current Alarms to Files.............................................................................................. 2-25
2.3.7 Viewing a Chart for Current Alarms........................................................................................... 2-27
2.3.8 Manually Synchronizing Alarms................................................................................................. 2-27
2.4 Managing Alarms History ............................................................................................. 2-28
2.4.1 Viewing Historical Alarms History.............................................................................................. 2-28
2.4.2 Filtering Alarms History .............................................................................................................. 2-30
2.4.3 Sorting Alarms History................................................................................................................ 2-30
2.4.4 Exporting Alarms History to Files............................................................................................... 2-30
2.5 Monitoring Events ....................................................................................................... 2-31
ECI Telecom Ltd. Proprietary iii

EMS-APT® Performance Management Guide Contents
2.6 Managing Unreported Alarms ...................................................................................... 2-33

2.7 Managing Archived Alarm Files .................................................................................... 2-38
2.8 Managing NE Alarms Log ............................................................................................. 2-42
2.8.1 Viewing NE Alarm Log................................................................................................................. 2-42
2.8.2 Exporting NE Alarm Log to Files................................................................................................. 2-43
2.9 Troubleshooting Alarms............................................................................................... 2-44
2.9.1 Equipment Alarms ...................................................................................................................... 2-45
2.9.2 Processing, Timing, and Miscellaneous Alarms ........................................................................ 2-53
2.9.3 SDH and PDH Port Alarms .......................................................................................................... 2-59
2.9.4 EoS and EoP Port Alarms............................................................................................................ 2-65
2.9.5 Ethernet PHY (ETY) Port Alarms................................................................................................. 2-67
2.9.6 Ethernet Service Alarms ............................................................................................................. 2-71
2.9.7 MPLS Alarms................................................................................................................................ 2-73
2.9.8 CES Service Alarms...................................................................................................................... 2-75
2.9.9 EDFA and OTN Port Alarms ........................................................................................................ 2-76
3 Performance Monitoring ................................................................................ 3-1

3.1 Performance Data ......................................................................................................... 3-1
3.2 Viewing Performance Data ............................................................................................ 3-4
3.2.1 Viewing Current Performance ..................................................................................................... 3-5
3.2.2 Viewing Performance History .................................................................................................... 3-11
3.2.3 Viewing Recent Performance..................................................................................................... 3-17
3.3 Configuring Performance Settings ................................................................................ 3-18
3.3.1 Opening Archived Performance Files ........................................................................................ 3-19
3.3.2 Setting Performance Threshold ................................................................................................. 3-20
3.3.3 Setting DCC Performance ........................................................................................................... 3-30
3.3.4 Setting PM ................................................................................................................................... 3-39
3.3.5 Managing Threshold Settings..................................................................................................... 3-45
3.3.6 Viewing Transceiver Alarms and Warning Threshold .............................................................. 3-45
3.3.7 Viewing Invalid MPLS-TP OAM Statistics................................................................................... 3-46
3.3.8 Viewing TDM/Packet Engine Utilization.................................................................................... 3-47
3.3.9 Viewing/Exporting Laser Performance...................................................................................... 3-50
3.3.10 Resetting Performance Counters............................................................................................... 3-52
3.4 PM Counters and TCA .................................................................................................. 3-52
3.4.1 Ethernet and Layer2 PM Counters and TCA ............................................................................. 3-53
3.4.2 EoS PM Counters and TCA.......................................................................................................... 3-58
3.4.3 CFM PM Counters and TCA ........................................................................................................ 3-58
ECI Telecom Ltd. Proprietary iv

3.4.4 CES Port PM Counters and TCA ................................................................................................. 3-60

3.4.5 PTP1588 PM Counters and TCA................................................................................................. 3-63
3.5 Performing PM Export Configuration ............................................................................ 3-64
3.5.1 Configuring PM Export Settings................................................................................................. 3-64
3.5.2 Viewing the Exported Files......................................................................................................... 3-69
3.5.3 PM Counters Lists ....................................................................................................................... 3-73
3.5.4 SDH PM Counters........................................................................................................................ 3-75
3.5.5 OTN PM Counters and TCA ........................................................................................................ 3-91
3.5.6 CES Service PM Counters and TCA...........................................................................................3-104
3.5.7 CES Port PM Counters and TCA ...............................................................................................3-108
4 Performing Maintenance Operations ............................................................. 4-1

4.1 Preventive Maintenance Operations .............................................................................. 4-1
4.1.1 Saving NE Configuration Data ...................................................................................................... 4-1
4.1.2 Clearing NE Configuration Data ................................................................................................... 4-1
4.1.3 Checking Configuration Consistency ........................................................................................... 4-2
4.1.4 Testing Connectivity ..................................................................................................................... 4-3
4.1.5 Performing a Fully Upload............................................................................................................ 4-4
4.1.6 Performing a Fully Download....................................................................................................... 4-5
4.1.7 Performing a LED Test .................................................................................................................. 4-7
4.1.8 Viewing Bit Codes ......................................................................................................................... 4-7
4.1.9 Managing Defined Bit Code ......................................................................................................... 4-8
4.1.10 Viewing PPI Status ...................................................................................................................... 4-10
4.1.11 Performing Preventive Maintenance ........................................................................................ 4-12
4.2 Managing Databases ................................................................................................... 4-12
4.3 Performing Card Maintenance ..................................................................................... 4-15
4.3.1 Resetting a Card.......................................................................................................................... 4-15
4.3.2 Obtaining the SFP Type .............................................................................................................. 4-16
4.3.3 Performing XFP Management.................................................................................................... 4-20
4.3.4 Managing T-SFP+ Settings .......................................................................................................... 4-22
4.3.5 OTN Wrapping for STM-16/64 Interface in CPTS100 ............................................................... 4-26
4.3.6 OTN Wrapping for 10GE Interface in CPTS100/CPS100........................................................... 4-28
4.3.7 Managing OTN in XIO64 ............................................................................................................. 4-30
4.3.8 Performing Basic Parameter Backup in SFP.............................................................................. 4-35
4.4 Performing Transmission Object Maintenance Operations............................................. 4-36
4.4.1 Using the Maintenance List........................................................................................................ 4-36
4.4.2 Performing/Releasing Loopback................................................................................................ 4-38
4.4.3 Performing AIS/RDI..................................................................................................................... 4-42
ECI Telecom Ltd. Proprietary v

4.4.4 Performing PRBS ......................................................................................................................... 4-44

4.4.5 Switching to Protection .............................................................................................................. 4-45
4.4.6 Setting the Link Down Status ..................................................................................................... 4-46
4.4.7 Performing CES Maintenance .................................................................................................... 4-47
4.5 Performing Maintenance on Timing ............................................................................. 4-50
4.5.1 Viewing TMU Working Mode..................................................................................................... 4-50
4.5.2 Forcing the Timing Source.......................................................................................................... 4-52
4.6 Managing SNMP Configuration .................................................................................... 4-53
4.6.1 Overview...................................................................................................................................... 4-54
4.6.2 Accessing SNMP Configuration Window................................................................................... 4-54
4.6.3 Managing SNMP Configuration ................................................................................................. 4-55
4.7 Enabling Link Loss Carry Forward (LLCF)........................................................................ 4-77
4.8 Managing EMS Events ................................................................................................. 4-78
4.9 Viewing System Fault Details ....................................................................................... 4-82
4.10 Performing Link OAM Loopback Testing ....................................................................... 4-82
4.11 Setting NE Security Mode ............................................................................................ 4-85
ECI Telecom Ltd. Proprietary vi

List of Figures
Figure 3-1: PB Ethernet connection view ............................................................................................... 3-2
Figure 3-2: MPLS Ethernet connection view ........................................................................................... 3-2
Figure 3-3: Zoomed-in illustration of objects within PB PE ...................................................................... 3-3
Figure 3-4: Zoomed-in illustration of objects within MPLS PE .................................................................. 3-3
Figure 4-1: LLCF module ..................................................................................................................... 4-77
ECI Telecom Ltd. Proprietary vii

List of Tables
Table 2-1: Icons in the Severity Settings window .................................................................................. 2-14
Table 2-2: Icons on the current alarm toolbar ...................................................................................... 2-20
Table 2-3: Icons on the historical alarm toolbar ................................................................................... 2-29
Table 2-4: Equipment alarm list .......................................................................................................... 2-45
Table 2-5: Processing, timing, and miscellaneous alarm list .................................................................. 2-53
Table 2-6: SDH and PDH port alarm list................................................................................................ 2-59
Table 2-7: EoS and EoP port alarm list ................................................................................................. 2-65
Table 2-8: Ethernet PHY (ETY) port alarm list ....................................................................................... 2-67
Table 2-9: Ethernet service alarm list .................................................................................................. 2-71
Table 2-10: MPLS alarm list................................................................................................................. 2-73
Table 2-11: CES service alarm list ........................................................................................................ 2-75
Table 2-12: EDFA and OTN port alarm list ............................................................................................ 2-76
Table 3-1: Ethernet and Layer2 PM counters and TCA .......................................................................... 3-53
Table 3-2: EoS/GFP PM counters and TCA............................................................................................ 3-58
Table 3-3: CFM PM counters and TCA.................................................................................................. 3-58
Table 3-4: CES port PM counters and TCA............................................................................................ 3-60
Table 3-5: ES service PM counters and TCA.......................................................................................... 3-61
Table 3-6: PTP1588 PM counters and TCA ........................................................................................... 3-63
Table 3-7: Slot names and relevant slot numbers ................................................................................. 3-72
Table 3-8: SDH PM counters ............................................................................................................... 3-75
Table 3-9: Data PM counters .............................................................................................................. 3-80
Table 3-10: OTN PM counters and TCA ................................................................................................ 3-91
Table 3-11: CES Service PM counters and TCA.....................................................................................3-104
Table 3-12: CES port PM counters and TCA .........................................................................................3-108
Table 4-1: EMS-APT preventive maintenance procedures ..................................................................... 4-12
ECI Telecom Ltd. Proprietary viii

1 About This Guide
1.1 Overview
This book describes how to use the EMS-APT MSPP network management system (NMS) for fault
management, performance monitoring, and maintenance operations.
1.2 Intended Audience

The EMS-APT User Manual is intended for Network Operation Center (NOC) administrators and NOC
personnel managing the Access Packet Transport (APT) products, including BroadGate (BG) family and
Native Packet Transport (NPT) family of networks.
Parent Topic
1 About This Guide
1.3 Document Contents

This document contains the following sections:
 Fault Management: Describes how to configure fault management and alarms, including current
alarms, alarms history, NE alarms log, and troubleshooting alarms.
 Performance Monitoring: Describes the EMS-APT performance monitoring (PM) mechanisms,
including viewing current, historical, and recent performance.
 Performing Maintenance Operations: Describes how to perform standard maintenance, such as
loopbacks, path payload tests, and consistency and connectivity checks.
Parent Topic
1 About This Guide
1.4 Notes and Warnings

When applicable, this guide uses the following notes and warnings:
NOTE: clarifying information, specific instructions, commentary, sidelights, or interesting

points of information.
CAUTION: failure to follow directions could result in damage to equipment or loss of

information.
ECI Telecom Ltd. Proprietary 1-1

EMS-APT® Performance Management Guide About This Guide
WARNING: failure to follow directions could result in bodily harm or loss of life.
LASER WARNING: how to avoid personal injury. All personnel involved in equipment
installation, operation, and maintenance must be aware that laser radiation is invisible.
Therefore, although protective devices generally prevent direct exposure to the beam,
personnel must strictly observe the applicable safety precautions and, in particular, must
avoid staring into optical connectors, either directly or using optical instruments.
ESD: information on how to avoid discharge of static electricity and subsequent damage to
the unit.
TIP: helpful information and handy hints that can make your task easier.
IMPORTANT: essential information to which you must pay attention.
Parent Topic
1 About This Guide
1.5 Related Publications

The following publications may be of assistance to you regarding EMS-APT operations:
 EMS-APT User Guide
 EMS-APT Service Management Guide
 EMS-APT Network Management Guide
 EMS-APT Supporting Information
 BroadGate Product Line General Description
 BroadGate Product Line Reference Manual
 LCT-APT User Guide
 EMS-APT Installation Manual
 LightSoft Network Management System User Guide
Parent Topic
1 About This Guide

EMS-APT® Performance Management Guide About This Guide
1.6 How to Obtain ECI Telecom Technical

Documentation
To obtain technical documentation related to any ECI Telecom product, contact:
ECI Telecom Ltd.
ECI Documentation Group
30 Hasivim St.
Petach Tikva 4959388 – Israel
Fax: +972-3-9268060
Email: techdoc.feedback@ecitele.com
Parent Topic
1 About This Guide
1.7 Technical Assistance

For all product-related questions and issues, including installation, configuration, operation, and
maintenance, contact your local ECI Telecom Customer Support representative.
You can also contact the global ECI Telecom Customer Support Center at:
Telephone +972-3-9266000
Telefax +972-3-9266370
Email on.support@ecitele.com
Parent Topic
1 About This Guide

2 Fault Management
2.1 Overview
This section discusses how to use the EMS-APT for configuring, managing, filtering, and troubleshooting NE
alarms.
The EMS-APT equipment provides local alarm display and configuration access facilities in the event of
equipment failure and for maintenance purposes. These displays include LEDs on the front panel of the
EMS, which correspond to visual LED indicators on the EMS-APT screen.
The EMS-APT provides exceptionally powerful tools for viewing and analyzing alarms, enabling you to
optimize alarm-processing operations.
2.2 Configuring Fault Management

A key step in initial system setup involves defining your alarm management configuration.
Parent Topic
2 Fault Management
2.2.1 Configuring NE Fault Settings

This section describes how to configure NE settings. For the BG-40 NE, NE settings include NE History Log
Setting and Alarm Hold-Off Time. For the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021
NEs, there is an additional AinS Timer setting.

EMS-APT® Performance Management Guide Fault Management
To configure BG-40 NE settings:

1. In the NE Shelf View window, select working mode Fault and then the NE Settings tab. The following
window opens.
2. Modify the NE settings as required:

a. NE History Log Settings: Alarm log settings specify the working mode of logs on the NE equipment
and include the log length setting, the log working status, and the processing mode after a log is
full. The following terms relate to alarm log settings:
 The NE alarm log is a flow record table of alarm events and other events generated in an
NE.
 The NE History specifies whether the log is currently in use or has been stopped. It has two
modes: Disabled and RAM logging only. RAM logging only mode means the alarm log
keeps collecting events and saves the events in RAM. Disabled mode means the alarm log
is no longer in use. Default is RAM logging only.
 The Log Size defines the maximum number of records that can be stored in a log on the NE
equipment, from 0 to 1,000 (default 1,000).
When a log is full, it has two processing modes: Overwrite and Stop (default Overwrite). In
Overwrite mode, new records replace the oldest records. In Stop mode, the alarm log stops
collecting events.

b. Alarm Hold-Off Time: You can set the hold-off time for alarm generation and clearance, to
prevent alarm generation and clearance from being incorrectly reported and to suppress
excessively frequent alarm generation and clearance. An alarm’s status change is not validated
until the hold-off time has elapsed. The hold-off time is defined by the alarm generation hold-off
period and the alarm clearance hold-off period.
For the alarm generation hold-off period, an alarm event is not reported and the current alarm
status is not updated until a generated alarm is detected and its alarm status lasts 3-30 sec
(default 3 sec).
For the alarm clearance hold-off period, any alarm clearance detected is not considered as
cleared unless the clearance status lasts 3-30 sec (default 3 sec).
c. To save the changes, click Apply.
3. To refresh and retrieve the information of the NE settings, click .
4. To copy the settings from the selected NE to other NEs, click .
To configure BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/
NPT-1010 NE settings:
1. In the topology view, in the object tree list, select the BG-20/BG-20C/BG-30/BG-64/NPT-1200/
NPT-1020/NPT-1021/NPT-1010 NE to be configured. On the main menu, select working mode Fault,
Fault Settings and then the NE Settings tab. The following window opens.

For the BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE, the following window opens.
2. Modify the NE settings as required. In the AinS Timer area, the NEs define two AinS timer ranges from
1-1,800 sec, in steps of 1 sec. Default for Time1 is 10 sec and Time2 180 sec.
The settings in NE History Log Settings and Alarm Hold-Off Time areas are performed in the same
manner as for the BG-40 NE.
3. To save the changes, click Apply.
Parent Topic

2.2.2 Monitoring and Reporting Alarms

In the EMS-APT, you can perform alarm source masking in the Monitoring and Reporting tab.
In some cases, the alarms of some ports and functional blocks are irrelevant to the service, and then alarms
can be masked to avoid confusing them with the alarms caused by actual faults. Alarms that are masked
(shielded) are not monitored and do not affect card and equipment alarm indications (namely, the
card-level alarm status and NE-level alarm status). No alarm data is reported or recorded for shielded
alarms.
Generally, the following cases use alarm masks:

 Many service routes are open, but currently only some are in use. Unused service ports send LOS
alarms. In this case, you can mask the alarms of the service ports not used but configured with routes.
Unmask the alarms when necessary to use these service ports.
 For some ADM NEs, fiber connections at both optical interfaces are planned. However, in actual
engineering, one of the following may apply:
 The fiber in one direction is not laid as planned, and only fibers at one optical interface can be
provided.
 A protection network is planned, but the actual network has no protection due to lack of fiber
resources.
In these cases, the fibers at some optical interfaces need to be removed because the signals at some
optical interfaces are lost. In such situations, the alarms at the unused optical interface can be
masked.
In the EMS-APT, alarms can be masked for the optical interface, electrical interface, and SDH
functional block. Generally, to mask optical interface alarms, all SPI, RS, MS, AU-4, and VC-4 alarms
are masked. To mask electrical interface alarms, all VC and PPI alarms are masked.
When the alarms of a certain object are masked, the alarms related to this object in the current alarm DB
are cleared. After the alarm mask is released, the equipment reports the current alarm. Therefore, the NE
equipment for which the alarms have been masked should have no alarm indication.

To mask (shield) an alarm in the BG-40 NE:

1. In the topology view, in the object tree list, select a BG-40 NE, and on the main menu, select working
mode Fault, Fault Settings and then the Monitoring and Reporting tab. The following window opens.
2. To mask (shield) an alarm, clear the Monitor attribute checkbox. The default is checked.
3. To send the settings information to the NE equipment, click Apply.

To configure the settings for the BG-20/BG-20C/BG-30/BG-64/NPT-1200/

NPT-1020/NPT-1010 NEs:
1. In the topology view, in the object tree list, select a BG-20/BG-20C/BG-30/BG-64/NPT-1200/
NPT-1020/NPT-1010 NE, and on the main menu, select working mode Fault, Fault Settings and then
the Monitoring and Reporting tab. The following window opens.
2. Set the attributes for each object as needed, and click Apply to save the changes.

4. To batch edit the attributes, on the toolbar, click . Then click to select the required operation
as you need.

From this window, you can set three attributes for each object. For the Monitor attribute, the setting is the
same as for the BG-40 NE. For the Auto Report attribute, from the dropdown list, select Report or No
Report.
In addition, for the objects with AinS Timer Select attribute, you can select Report, No Report, or Auto
Report in the Auto Report attribute. Only when Auto Report is selected, the AinS Timer Select attribute is
enabled, which can be selected from Timer1 or Timer2 (default is Timer1).
The AinS attribute applies only on the following interfaces:
 PPI
 FE LAN
 GE LAN
 Codirectional
Parent Topic

2.2.3 Setting Switch Alarms

You can set the alarm monitoring and reporting for the following classes:
 Switch
 VSI
 Tunnel
 MA
 CES Interface
 Queue Block
 BD LSP
 Management VLAN
 Linear Protection Domain
To set alarm for the switch module:

1. In the NE Shelf View window, in the left object tree, select the Switch module. In the Fault and Fault
Settings working mode, select the Monitoring and Reporting tab.

2. To obtain object data from the NE equipment, in the Display dropdown list, select a required class
and click . The following figure shows, for example, the VSI settings.

3. Modify object parameters as required in Monitor and Auto Report lists.
4. To send settings to a piece of equipment and save them to the EMS-APT DB, click Apply.
Parent Topic
2.2.4 Managing External Alarms

The external alarm interface provides an input/output external alarm, and is used to input external alarms,
such as an ambient temperature alarm, smog alarm, door warning, and so on. It can also be used to input
an alarm from other equipment, such as PCM equipment, so that the EMS-APT can manage and indicate
various external alarms.
The external alarm interface, as a universal TTL-level input interface, can be defined as required by any
user. The output interface can be used to output the control volume (for example, the control relay switch)
and to provide alarm output to an external piece of equipment.

To manage external alarms:

1. In the NE Shelf View window , in the left object tree, select the NE, and on the menu, select Fault and
then External Alarms.
The window has two areas: Input Ports and Output Ports.
The Input Ports area displays the configuration of the four input ports of the NE. You can assign a
name to the port in the Port Name field and specify the upper TTL level representing the alarm status
or normal status in the Contacts field.
The Output Ports area displays configuration of the three output ports. These ports are: major alarm,
minor alarm, and sound alarm. You can set the alarm output switch as Yes or No.
2. To send the configuration data to the equipment and save it in the DB, click Apply.
3. To retrieve port information from the equipment, click .
Parent Topic

2.2.5 Performing Severity Settings

This section describes how to configure severity settings.
Each alarm has the following four attributes in the Severity Settings window:
 Severity
 Report
 Alarm Cause
 Reason ID
Only the Severity and Report attributes can be configured.

Alarms are categorized into five levels by the Severity attribute:
 Mask
 Critical
 Major
 Minor
 Warning

To configure the severity settings:

1. In the NE Shelf View window, select the working mode Fault and then the Severity Settings tab. The
following window opens.
2. Set alarm attributes as needed for each alarm title by selecting the relevant Severity attribute from
the dropdown list, and selecting or clearing the checkbox in the Report attribute.
3. To send the settings information to the NE equipment, click Apply.
The functions of the icons on the toolbar are set out in the following table.
Table 2-1: Icons in the Severity Settings window
Icon Description
Refresh - retrieves information from the equipment.
Set as default - views alarm attribute table information for the NE.
Propagate - copies the settings from the selected NE to other NEs.
Open a profile file - imports a profile file from your computer disk.
Save as a profile file - exports the settings as a profile file.
Parent Topic

2.2.6 Performing Alarm Notification Settings

You can perform alarm configuration in fault management, including Visual Notifications, Audio
Notifications, Alarm Counters, and Report to NMS.
To configure visual notifications:

1. In the EMS-APT main window, on the main menu, select Fault and then Alarm Notification Setting. In
the open window, select the Visual Notifications tab.
2. Configure the settings in the window by selecting the corresponding button and checkbox.
4. The following figure shows the Alarm Notification window. Show or hide this window by selecting in
the EMS main window, on the main menu, Fault, Display, and then Alarm Notification. The default is
unselected.

To configure audio notifications:

1. In the EMS-APT main window, on the main menu, select Fault and then Alarm Configuration. In the
open window, select the Audio Notifications tab.
2. From each dropdown list, select a sound file, and click Play to test the sound.
To configure alarm counters:

open window, select the Alarm Counter tab.

2. Select which counter type and alarm type you want to display by selecting the corresponding buttons
and checkboxes:
3. Show or hide the alarm counter bar by selecting or clearing the Show Alarm Counter checkbox.
To configure reporting to NMS:

open window, select the Report to NMS tab.
2. Select the alarm types you want to report to NMS by selecting the corresponding checkboxes.
3. To save your settings, click Apply.
Parent Topic

2.2.7 Viewing Alarm Log File
To view the alarm log file:

1. In the EMS-APT main window, on the main menu, select Fault and then View Alarm Log File. The
Alarm-Import window opens.
2. To open a file, on the toolbar click . The Open window opens.
3. Select a file from the disk and click Open.
Parent Topic

2.2.8 Finding Alarm Definition

You can view all the alarms from the find alarm definition list, and from the list, you can find a specific
alarm with the reason ID or alarm name.
To find alarm definition:

1. In the EMS-APT main topology view window, from the main menu, select Fault and then Find Alarm
Definition. The Find Alarm Definition window opens.
2. To find an alarm, in the Filter area, enter Reason ID or Alarm Name, then click the filter button .
3. To refresh the information to view, on the toolbar, click .
Parent Topic
2.3 Managing Current Alarms

A current alarm identifies an existing abnormal event caused by a problem in the equipment or the
communication line. This section describes how to manage current alarms.
Parent Topic
2 Fault Management

2.3.1 Viewing Current Alarms

Current alarms are represented on the screen as LEDs on each NE icon. The color of the LED corresponds to
the most severe alarm affecting it.
In the Current Alarms window, you can view a summary of the alarms currently present in EMS, and you
can apply user-defined filters to display custom current alarm reports.
To view current alarms for a specific NE:

1. In the EMS topology map, select an NE whose alarm information you want to view. If no NE is
selected, current alarm information for all NEs is displayed by default.
2. On the main menu, select Fault and then Current Alarms. The following window opens.
The icons on the alarm toolbar are listed in the following table.
Table 2-2: Icons on the current alarm toolbar
Icon Description
Acknowledges alarms.
Displays alarm details.
Exports current alarms as an XML file.
Exports current alarms as a CSV file.

Icon Description
Shows the current alarms as a list.
Shows the current alarms as a chart.
Selects all the alarms.
Deselects all the alarms.
Synchronizes the alarms manually.
Refreshes the current alarms list automatically.
Deletes the selected alarms.
To view current alarms for a specific card:

1. In the topology map, select an NE, and on the main menu, select Fault and then Current Alarms.
2. In the open window, in the left object tree, select the card whose alarm information you want to
view.

To view current alarms for a specific object:

1. In the topology map, select an NE, and on the main menu, select Fault and then Current Alarms.
2. In the open window, in the left object tree, click before the tributary card or port to display all
the objects.
3. Select the object whose alarm information you want to view.
Parent Topic
2.3.2 Determining the Cause of an Alarm

You can determine the cause of an alarm appearing in the Alarm Details window.
To determine the cause of an alarm:

1. In the Current Alarms window, click a specific alarm. The alarm row is highlighted.

2. To see detailed information of the alarm in the Alarm Details window (including Alarm Cause, NE,
Card, Object, etc.), on the current alarm toolbar click the Alarm Details icon . The Alarm Details
window opens.
Parent Topic
2.3.3 Filtering Current Alarms

You can filter current alarms according to the following three specific types:
 Severity
 Alarm Type
 Acknowledge

To filter current alarms:

1. To unfold the filter area, on the Filter bar, click +. The following window opens.
2. Clear the checkbox that you do not want to view in the current alarms window (by default, all objects
are checked.
3. To save the setting of the alarm filter, select the Keep Filter checkbox.
4. To filter the current alarms, click the Filter icon in the lower right corner.
Parent Topic

2.3.4 Sorting Current Alarms

You can change the default display of the current alarms by sorting them by specific columns.
To sort current alarms:

 In the Current Alarms window, click the column heading in the current alarm information list to sort
the information according to this column.
Parent Topic
2.3.5 Acknowledging Current Alarms

Acknowledging an alarm indicates you are aware of it and will deal with it. You can acknowledge alarms
singly or grouped.
To acknowledge a current alarm:

 In the Current Alarms window, select one or more alarms in the current alarm list, and on the
toolbar, click . Or, select a current alarm and right-click, and from the shortcut menu, click .
Parent Topic
2.3.6 Exporting Current Alarms to Files

You can save the current alarms information as a file.
To export current alarms to files:

1. To save current alarm records as an XML file:
a. On the toolbar of the Current Alarms window, click . The Save window opens.

b. Select the location folder, enter the file name for the XML file, and click Save.
2. To export the alarm list as a CSV file:
a. On the toolbar click . The following window opens.
b. Select the location folder, enter the file name for the CSV file, and click Save.
Parent Topic

2.3.7 Viewing a Chart for Current Alarms
To view a chart for current alarms:
 In the Current Alarms window, on the toolbar click . A histogram is displayed showing different
current alarm severity according to colored blocks.
Parent Topic
2.3.8 Manually Synchronizing Alarms

If EMS-APT alarms and equipment alarms cannot be acknowledged as consistent, the Manually
Synchronize Alarm function can be used to ensure consistency between them. Based on the current alarm
on the equipment side, this operation refreshes the current alarm on the EMS-APT side.
Manually synchronizing an NE alarm is not affected by the auto-report attribute.
Two synchronization options are available:
 Manually synchronize an NE alarm
 Manually synchronize a card alarm

To manually synchronize an alarm on an NE:

1. In the Current Alarms window, in the left object tree, select the NE.
2. On the toolbar click the green icon . If you synchronize successfully, the following message
appears.
Parent Topic
2.4 Managing Alarms History

Historical alarms refer to alarm records automatically cleared after the equipment returns to normal status.
As with current alarms, historical alarms are saved in the DB.
Parent Topic
2 Fault Management
2.4.1 Viewing Historical Alarms History
To view historical alarms for a specific NE:

1. In the EMS topology map, select an NE whose alarm information you want to view. (If no NE is
selected, current alarm information for all NEs is displayed by default.)
2. On the main menu, select Fault and then Cleared Alarms.

3. To display the information, click .
The icons on the alarm toolbar are listed in the following table.
Table 2-3: Icons on the historical alarm toolbar
Icon Description
Obtains the information from the equipment.
Displays alarm details.
Shows the historical alarms as a list.
Shows the historical alarms as a chart.
Selects all the alarms.
Deselects all the alarms.
Deletes the selected alarms.
Exports historical alarms as an XML file.
Exports historical alarms as a CSV file.

To view historical alarms for a specific card:

1. In the EMS topology map, select an NE, and on the main menu, select Fault and then Cleared Alarms.
2. In the open window, in the left object tree, select the card whose alarm information you want to
view.
To view historical alarms for a specific object:

1. In the EMS topology map, select an NE, and on the main menu, select Fault and then Cleared Alarms.
2. In the open window, in the left object tree, click before the tributary card or port to display all
the objects.
3. Select the object whose alarm information you want to view.
Parent Topic
2.4.2 Filtering Alarms History

This function is performed in the same way as Filtering Current Alarms.
Parent Topic
2.4.3 Sorting Alarms History

This function is performed in the same way as Sorting Current Alarms.
Parent Topic
2.4.4 Exporting Alarms History to Files

This function is performed in the same way as Exporting Current Alarms to Files.
Parent Topic

2.5 Monitoring Events

The events function provides a convenient real-time mechanism for viewing alarms and events. It faithfully
records all notices from the equipment, including alarms, alarm clearing actions, and events.
To monitor events:
1. In the EMS topology map, select an NE whose events you want to view. (If no NE is selected, events
for all NEs are displayed by default.)
2. On the main menu, select Fault and then Events. The following window opens.

3. To view event details, select an event in the list, and on the toolbar click the Event Details icon .
4. To export and save the queried current alarm records as an XML file:
a. On the toolbar click .

5. To export the events as a CSV file:
6. To delete events, select the events in the list you want to delete, and on the toolbar click .
Parent Topic
2 Fault Management
2.6 Managing Unreported Alarms

This section describes how to manage unreported alarms.
To manage unreported alarms:

1. In the EMS topology map, select an NE whose unreported alarm information you want to view. (If no
NE is selected, unreported alarm information for all NEs is displayed by default.)

2. On the main window, select Fault and then Unreported Alarms. The following window opens.
3. To retrieve the information to view, on the toolbar click .
4. To view the alarms in a list, on the toolbar click the Show as List icon .

5. To view the alarms in a chart, on the toolbar click the Show as Chart icon .

6. To view unreported alarm details, select a cleared alarm in the list, and on the toolbar click the Alarm
Details icon .
7. To export the unreported alarms as an XML file:
a. On the toolbar click . The Save window opens.

8. To export the unreported alarms as a CSV file:
a. On the toolbar click . The following window opens.
9. To delete the unreported alarm records, in the list select the alarms you want to delete, and on the
toolbar click .
Parent Topic
2 Fault Management

2.7 Managing Archived Alarm Files
To manage archived alarm files:

1. In the EMS-APT main window, on the main menu, select Fault and then Archived Files. The following
window opens.
2. To open an archived file, on the toolbar click . The following window opens.

3. Select the file in your local disk and click Open. The following window opens.
4. To view the alarms in a list, on the toolbar click the Show as List icon .

5. To view the alarms in a chart, on the toolbar click the Show as Chart icon .

6. To view alarm details, select an alarm in the list, and on the toolbar click the Alarm Details icon .
7. To export the alarms to files:

b. Enter a name in the File Name field and click Save.
8. To delete alarm records, in the list select the alarms you want to delete, and on the toolbar click .
Parent Topic
2 Fault Management
2.8 Managing NE Alarms Log

The NE alarms log records the alarm and event information saved in the NE equipment. If an NE is
disconnected during a certain period, all its alarms and events generated during this period are recorded in
the log.
Parent Topic
2 Fault Management
2.8.1 Viewing NE Alarm Log
To view NE alarm log records:

1. In the EMS topology map, select an NE whose alarm information you want to view, and on the main
menu, select Fault and then NE History.

2. To view the records, click .
Parent Topic
2.8.2 Exporting NE Alarm Log to Files

You can export the NE alarm log as an XML or CSV file.
To export NE alarm log records to a file:

1. To export the alarm list as an XML file:
a. In the NE History Alarms window, on the toolbar click . The Save window opens.
2. To export the alarm list as a CSV file:

Parent Topic
2.9 Troubleshooting Alarms

This section provides a comprehensive list of EMS-APT alarms and maintenance operations relevant to each
object in the EMS-APT.
Alarms are listed alphabetically within each alarm type category.
Details for each alarm are provided, including the alarm name, description, severity, and corrective
action(s).
Parent Topic
2 Fault Management

2.9.1 Equipment Alarms

Table 2-4: Equipment alarm list
ID Alarm Cause ID Source Default Description Applicable system

name severity
MSPP BG-2 BG-20C BG-3 BG-6 NPT-10 NPT- NPT-10

0 0 4 20 1200 10
Card and Slot (General)
1 Card-Out 75 Card Critical No card detected as Y Y Y Y Y Y Y

expected in the slot.
Applicable to all slots.
2 Communica 658 Card Critical Card SW has no response Y Y Y Y Y Y Y

tion-Fail to main control unit. It
becomes unmanaged.
3 Card-Ctrl-Fa 451 Card Critical Card has no reply or Y Y Y Y Y Y Y

il incorrect reply to MCP
polling request and the
card has entered "not
operational" state while
communication channel is
active (ping is OK).
4 CBUS-Error 430 Card Critical Control bus failure Y Y Y Y Y Y Y

detected at physical and
link layer.
5 Type-Unkno 389 Slot Critical Card type cannot be Y Y Y Y Y Y Y

wn recognized by system due
to:
 IDPROM verification
fail - not applicable
to SFP; SFP IDPROM
verification fail has
a separate alarm -
SFP-ID Fail.
 Card type read is
unknown.
This alarm is only related

to physical slots.
6 Type-Misma 76 Card Critical Card Type Mismatch. Y Y Y Y Y Y Y

tch Indicates that the wrong
card was inserted in the
slot or DB. Actual card
type is not the one
expected.
7 Card-Reassi 390 Slot Warning Current actual card type is Y Y Y Y Y

gnable partially compatible with
the assigned card type,
but with capability to be
reassigned to a new card
with higher rate and/or
larger capacity.


name severity

0 0 4 20 1200 10
8 Card-Under 438 Slot Warning The actual card is fully Y Y Y Y Y

utilized compatible with the
assigned card (logical
card), but HW capability is
not fully utilized, it can be
reassigned as a new card
with larger capacity.
9 Card-Detect 77 Slot Warning For a slot, a card insertion Y Y Y Y Y Y Y

ed is detected while there is
no card assigned for this
slot.
10 Card-Fail 385 Slot Critical HW BIT-Fail is detected on Y Y Y Y Y

MCP.
11 Card-PWR-F 405 Slot Critical Power failure. Y Y Y Y

ail
12 BIT-FAIL 381 Actual Critical BIT not passed due to Y Y Y Y Y Y Y

card Critical Failure.
13 BIT-Not-OK 382 Actual Major BIT not passed due to Y Y Y Y Y Y Y

card Major Failure, but the
failure may not be caused
by local components.
14 BIT-Degrade 383 Actual Minor BIT not passed due to Y Y Y Y Y Y Y

card Performance Degrade.
15 BIT-Slightly- 384 Actual Warning BIT not passed due to Y Y Y Y Y Y Y

Degrade card Performance Slight
Degrade.
16 CPU-Utilizat 809 Card Major The utilization of CPU Y Y Y Y Y Y Y

ion-High exceeds threshold.
17 Free-Mem-L 810 Card Major The unused (free) memory Y Y Y Y Y Y Y

ow space is lower than
threshold.
18 Free-NVM-L 811 Card Major The unused (free) NVM Y Y Y Y Y Y Y

ow space is lower than
threshold.
19 Temp-High 401 Card Critical Board temperature is Y Y Y Y Y Y Y

crossing predefined alarm
threshold; card is too hot.
20 Temp-H-Wa 806 Card Minor Temperature of Y Y Y Y Y Y Y

rning equipment is higher than
high temperature warning
threshold.
21 Temp-Low 807 Card Major Temperature of Y Y Y Y Y Y Y

equipment is lower than
low temperature alarm
threshold.


name severity

0 0 4 20 1200 10
22 Temp-L-Wa 808 Card Minor Temperature of Y Y Y Y Y Y Y

rning equipment is lower than
low temperature warning
threshold.
23 Warm-Rese 461 Card Event Warm reset. A reset event Y Y Y Y Y Y Y

t means the card has
experienced a warm
restart procedure just
now. Warm reset
operation resets CPU and
its peripherals only -
traffic is not affected.
24 Cold-Reset 462 Card Event Cold reset. A reset event Y Y Y Y Y Y Y

means the card has
experienced cold restart
procedure just now. Cold
reset operation resets all
logic circuits on the card.
It is traffic affecting.
Support parameter for
"cold reset" event to
indicate the reset type of
all cards and MCP Type of
BG-30:
Reset type:
 0 – Non-specified;
 256 – Power on
reset;
 512 – Command
cold reset
 Other value -
non-specific
MCP type (for BG-30
only):
 0 – MCP30;
 1 – MCP30B;
 Other – reserved
(not specified)
25 XIO-protecti 489 XSA Event XIO30-1/4/16, Y Y Y

on-switch XIO30Q_1&4, XIO64,
XIO16_4 protection switch
occurs due to failure
detected or maintenance
operations.
26 Card-Protec 671 Protected Event Tributary protection Y Y Y Y

tion-switch card switch occurs due to
automatic switch or
maintenance operations
on protected card. The
event pertains to a
protected card.
27 NVM-Repla 692 MCP64 Event NVM (CF) card or MCP64 Y Y Y

ced is present but not locked.


name severity

0 0 4 20 1200 10
28 Card-Lock-O 693 MCP64, Critical Inserted NVM card is not Y Y Y

pen NVM card the one that is extracted
before.
29 Card-reassig 41 MCP Internal Card Reassignment is Y Y Y Y Y Y

ned Event finished successfully or fai.
Parameter: success/fail.
Invisible event for internal

use.
30 Card-Reassi 440 MCP Event Card Reassignment is Y Y Y Y Y

gn-Notificati finished - successfully or
on faied.
Parameters are defined to

indicate success/fail,
source card type and
destination card type.
1. The highest bit is
defined to indicate
the success/fail:
 0-
Reassignment
is successful
 1-
Reassignment
failed
1. The 3rd byte of
parameter indicates
the source card type.
2. The 4th byte of
parameter indicates
the destination card
type.
31 PoE-Over-V 422 Card Critical The power supply of PoE Y Y Y Y Y Y

oltage is over-voltage (>58V);
This alarm is supported

only in cards which
supports PoE
functionality.
32 PoE-Under- 423 Card Critical The power supply of PoE Y Y Y Y Y

Voltage is under-voltage (<37V)
This alarm is supported

only in cards which
supports PoE
functionality.
33 PoE-Voltage 443 Card Major The voltage is lower than Y

-Low 44V or 50V which is
required by IEEE 802.3at
PoE specification.


name severity

0 0 4 20 1200 10
33 HW-Rev-Mi 429 Card Critical Some feature is not Y Y Y Y Y Y

smatch supported by current HW
revision, i.e., it is required
to replace card with high
revision to support the
new feature.
34 HW-Rev-Mi 429 Card Critical Some feature is not Y Y Y Y Y Y

smatch supported by current HW
revision, i.e., it is required
to replace card with high
revision to support the
new feature.
35 CF-Loss 441 Card Critical Control frame from Y Y

DHFE_L2 to CPTS/CPS is
lossed.
36 MF-Loss 442 Card Critical Management frame from Y Y

DHFE_L2 to CPTS/CPS is
lossed.
Shelf and MBP
1 E-Shelf-Not- 393 E-Shelf Critical The expansion platform is Y Y Y Y Y

Installed not installed as expected.
2 E-Shelf-Det 394 MCP Warning The expansion shelf is Y Y Y Y Y

ected detected, but not
assigned.
3 Unknow-E- 804 MCP Critical The MBP type is not Y Y Y Y Y

MBP-Type recognized.
4 MBP-Type- 805 E-Shelf Critical The MBP of the expansion Y Y Y Y Y

Mismatch platform is not compatible
with the assigned
platform type.
5 PWR-Consu 726 MBP Critical The actual power Y Y Y Y Y

mption-TC- consumption of the
Alarm platform is crossing the
alarm threshold - the total
power budget of the
platform.
6 PWR-Consu 727 MBP Warning The actual power Y Y Y Y Y

mption-TC- consumption of the
Warning platform is crossing the
warning threshold - the
total power budget of the
platform minus MSPC.
7 BG-20E-Not 386 E-Shelf Critical BG-20E platform is

-Installed present as expected.
8 BG-20E-Det 387 MCP Warning BG-20E platform is

ected present but not assigned.


name severity

0 0 4 20 1200 10
9 Shelf-Replac 434 MCP Event This event represents that Y Y

ed NE shelf has been
replaced with a
compatible shelf, the
actual NE type may be
changed.
Parameter is defined to
indicate source NE type
and destination NE type.
 The high 2 bytes of
parameter indicates
the source NE type.
 0x0064 =
BG-64
 The low 2 bytes of
parameter indicates
the destination NE
type.
 0x1200 =
NPT-1200
Power Supply and Fan
1 DC-IN-Fail 391 Single Critical DC power-in failure, Y Y Y Y Y

feeding caused by power cable
INF disconnection, power off,
or low voltage.
2 DC-Out-Fail 392 Single Critical DC power output failure, Y Y Y Y Y Y

feeding caused by DC-IN-Fail or
INF INF failure.
3 DC-IN-A-Fail 378 Dual-feedi Critical DC power-in fail on port A. Y Y Y Y

ng INF
4 DC-IN-B-Fail 379 Dual-feedi Critical DC power-in fail on port B. Y Y Y Y

ng INF
5 Power-in-A 406 INF Event Transient power-in Y Y Y Y Y

nomaly anomaly
Parameter:
0 - Transient DC-IN-Fail
1 - Transient DC-Out-Fail
6 Fan-FAIL 351 FCU Critical Fan Fault，Stop running Y Y Y Y Y Y Y

due to Fault.
7 Fan-Filter-N 813 FCU with Major Fan filter needs to be Y

eed-Clean dust filter cleaned.
8 ENV-Temp- 814 FCU with Critical The environment Y Y Y Y Y Y Y

High temperatu temperature is crossing
re sensor the threshold. For class
3.3 (such as BG-30B), the
threshold should be
72/70C; for class 3.1, the
threshold should be
57C/55C.


name severity

0 0 4 20 1200 10
9 ENV-Temp-L 836 FCU with Major The environment Y Y Y Y Y Y Y

ow temperatu temperature is crossing
re sensor the threshold. For class
3.3 (such as BG-30B), the
threshold should be
-25/-23C. For class 3.1, the
threshold should be
-7C/-5C.
10 Fan-Speed-c 484 FCU Event Fan speed changes from Y Y Y Y Y Y Y

hange low to high level or from
high to low.
Transceiver (SFP/XFP/SFP+/CSFP)
1 SFP-Out 355 SFP/XFP/S Critical SFP is not present as Y Y Y Y Y Y Y

FP+ expected.
2 SFP-ID-Fail 672 SFP/XFP/S Critical Failed to find ECI ID in the Y Y Y Y Y Y Y

FP+ SFP (SFP ID verification
fail).
3 SFP-Type-U SFP/XFP/S Major SFP type read from ID is

nknown FP+ unknown.
4 SFP-Type-M 380 SFP/XFP/S Critical Actual SFP type is not Y Y Y Y Y Y Y

ismatch FP+ compatible with expected
SFP type.
5 SFP-AppCod 815 SFP/XFP/S Major Actual SFP application Y Y Y Y Y Y

e-Mismatch FP+ code is not compatible
with expected application
code.
6 SFP-Temp-H 362 SFP/XFP/S Critical Laser temperature is Y Y Y Y Y Y Y

igh FP+ crossing high alarm
threshold.
7 SFP-Temp-L 363 SFP/XFP/S Minor Laser temperature is Y Y Y Y Y Y Y

ow FP+ crossing low alarm
threshold.
8 VCC3-High 364 SFP/XFP/S Critical Supply voltage of +3.3 V is Y Y Y Y Y Y Y

FP+ crossing high alarm
threshold.
9 VCC3-Low 365 SFP/XFP/S Critical Supply voltage of +3.3 V is Y Y Y Y Y Y Y

FP+ crossing low alarm
threshold.
10 VCC2-High 827 XFP Critical Supply voltage of +1.8 V is Y Y

crossing high alarm
threshold.
11 VCC2-Low 828 XFP Critical Supply voltage of +1.8.V is Y Y

crossing low alarm
threshold.
12 VCC5-High 829 XFP Critical Supply voltage of +5 V is Y Y

crossing high alarm
threshold.


name severity

0 0 4 20 1200 10
13 VCC5-Low 830 XFP Critical Supply voltage of +5 V is Y Y

crossing low alarm
threshold.
14 TX-LBC-High 366 SFP/XFP/S Major Laser TX bias current is Y Y Y Y Y Y Y

FP+ crossing high alarm
threshold.
15 TX-LBC-Low 367 SFP/XFP/S Minor Laser TX bias current is Y Y Y Y Y Y Y

FP+ crossing low alarm
threshold.
16 TX-oPower- 368 SFP/XFP/S Major TX Optical Power is Y Y Y Y Y Y Y

High FP+ crossing high alarm
threshold.
17 TX-oPower- 369 SFP/XFP/S Critical TX Optical Power is Y Y Y Y Y Y Y

Low FP+ crossing low alarm
threshold.
18 RX-oPower- 609 SFP/XFP/S Major RX Optical Power is Y Y Y Y Y Y Y

High FP+ crossing high alarm
threshold.
19 RX-oPower- 610 SFP/XFP/S Critical RX Optical Power is Y Y Y Y Y Y Y

Low FP+ crossing low alarm
threshold.
20 SFP-Temp-H 370 SFP/XFP/S Minor Laser temperature high Y Y Y Y Y Y Y

-Warning FP+ warning.
21 SFP-Temp-L 371 SFP/XFP/S Warning Laser temperature low Y Y Y Y Y Y Y

-Warning FP+ warning.
22 VCC3-H-Wa 372 SFP/XFP/S Warning Supply voltage of +3.3 V Y Y Y Y Y Y Y

rning FP+ high warning.
23 VCC3-L-War 373 SFP/XFP/S Major Supply voltage of +3.3 V Y Y Y Y Y Y Y

ning FP+ low warning.
24 VCC2-H-Wa 831 XFP Warning Supply voltage of +1.8 V Y Y

rning high warning.
25 VCC2-L-War 832 XFP Major Supply voltage of +1.8 V Y Y

ning low warning.
26 VCC5-H-Wa 833 XFP Warning Supply voltage of +5 V Y Y

rning high warning.
27 VCC5-L-War 834 XFP Major Supply voltage of +5 V low Y Y

ning warning.
28 TX-LBC-H-W 374 SFP/XFP/S Warning Laser bias high warning. Y Y Y Y Y Y Y

arning FP+
29 TX-LBC-L-W 375 SFP/XFP/S Warning Laser bias low warning. Y Y Y Y Y Y Y

arning FP+
30 TX-oPower- 376 SFP/XFP/S Warning TX Optical Power high Y Y Y Y Y Y Y

H-Warning FP+ warning.


name severity

0 0 4 20 1200 10
31 TX-oPower- 377 SFP/XFP/S Major TX Optical Power low Y Y Y Y Y Y Y

L-Warning FP+ warning.
32 RX-oPower- 611 SFP/XFP/S Warning RX Optical Power high Y Y Y Y Y Y Y

H-Warning FP+ warning.
33 RX-oPower- 612 SFP/XFP/S Major RX Optical Power is Y Y Y Y Y Y Y

L-Warning FP+ crossing low warning
threshold.
34 SFP-Rx-LOS 607 SFP/XFP/S Critical Rx loss of signal (Rx_LOS) Y Y Y Y Y

FP+ indication is asserted by
the transceiver (SFP, XFP,
CSFP, SFP+)
2.9.2 Processing, Timing, and Miscellaneous Alarms

Table 2-5: Processing, timing, and miscellaneous alarm list
ID Alarm Cause Source Default Description Applicable system

name ID severity
MSPP BG-2 BG-2 BG-3 BG-6 NPT-1 NPT-12 NPT-10

0 0C 0 4 020 00 10
TMU
1 LTI-1 625 TMU Major Nominated Timing Source #1 Y Y Y Y Y Y Y

Loss of Timing Input.
2 OOR-1 626 TMU Major Nominated Timing Source #1 Y Y Y Y Y Y Y

Frequency Out Of Range.






9 T3-0-LOF 633 TMU Minor Loss of Frame, only for framed Y Y Y Y Y

2 Mbps or 1.5 Mbps T3 input.


name ID severity

0 0C 0 4 020 00 10
10 T3-0-AIS 634 TMU Minor Alarm indication signal of 2 Y Y Y Y Y

Mbps or 1.5 Mbps T3 input.
11 T3-0-LOS 635 TMU Minor Loss of Signal for 2 Mbps or Y Y Y Y Y

1.5 Mbps.
12 T3-1-LOS 636 TMU Minor Loss of Signal for 2 MHz or 1.5 Y Y Y Y Y

MHz.
13 T4-LTO 606 TMU Minor Loss of Timing Output (T4 Y Y Y Y Y

output is squelched).
14 TLoss-of-Sy 330 TMU Critical Total loss of synchronization Y Y Y Y Y Y Y

nc sources. No available timing
source, all synchronization
sources selected are lost or
unusable.
15 Timing-Sou 163 TMU Event Timing source switch from one Y Y Y Y Y Y Y

rce-Switch to another.
16 Timing-Mo 163 TMU Event Timing mode switch (such as Y Y Y Y Y Y Y

de-Switch freerun -> locked, locked ->
holdover).
17 QL-Change 717 TMU Event Timing source quality level Y Y Y Y Y Y Y

change.
18 TM-unsync 652 TMU Minor Timing mode of main TMU is Y Y Y

hronized different from that of standby
TMU (e.g., main is locked to T3
and standby is locked to
XIO30-A).
19 LOL 467 TMU Event Current Timing Source Loss of

Locked.
20 PTP-port-fa PTP-TMU PTP port is faulty (this should

ult be BIT).
21 PTP-Slave- 261 PTP-TMU Major PTP TMU in slave mode is not Y Y Y Y Y Y

Unsync working in locked mode, i.e.,
PTP slave is not synchronized
to the master.
This alarm is available only

when PTP is enabled and
works in slave mode.
22 PTP-Maste 262 PTP-TMU Major PTP TMU in master mode is Y Y Y Y Y

r-Unsync not working in locked mode,
the synchronization source
may be lost or out of range.
This alarm is available only

when PTP is enabled and
works in master mode.
23 1PPS-Loss PTP-TMU Loss of 1PPS input Y Y Y


name ID severity

0 0C 0 4 020 00 10
External Alarms
1 Ext-Alm1 356 External Major User definition alarm 1 Y Y Y Y Y Y

(External Alarm 1).

(External Alarm 2).

(External Alarm 3).

(External Alarm 4).
SW and Processing Alarm
1 MCP-Start- 703 MCP Critical Critical error is detected. MCP Y Y Y Y Y

Fail SW fails to start normally, and
enters safe mode instead.
Parameters are defined to

indicate detail reason.
2 MCP-Start- 444 MCP Critical MCP is started with debug Y Y Y Y Y

In-Debug mode
3 NE-Restart- 465 MCP Event This event notifies Y Y Y Y Y Y Y

Notificatio management of the NE restart
n mode with details.
4 NE-Upgrad 407 MCP Event This event notifies Y Y Y Y Y Y Y

e-Notificati management of the NE version
on upgrade status.
5 Cfg-Restor 485 Card Event Configuration data restored Y Y Y Y Y Y Y

e-Success successfully.
6 Cfg-Restor 687 Card Critical Restoring configuration data Y Y Y Y Y Y Y

e-Fail for card/module failed.
7 CFG-Incons 437 Card Critical This alarm indicates that card Y Y Y Y Y Y

istency configuration is not
synchronized with MCP.
This alarm should be

announced when fail to
configure the card (during
online status) but no roll back
mechanism exists;This alarm
should be clear when card gets
reset.
8 DB-mismat 490 MCP Event DB restored from NVM is Y Y Y Y Y

ch different from equipment
(CVW of DB is not equal to
that of XIO).
9 NE-DB-upd 491 MCP Event NE configuration is Y Y Y Y Y Y Y

ate synchronized with a new DB.
A new NE DB is activated and

recovered. EMS should initiate
upload if received this event.


name ID severity

0 0C 0 4 020 00 10
10 Patch-upda 724 Card Event A hot patch is activated; this Y Y Y Y Y Y Y

te card and NE patch version is
updated.
11 SM-Ver-Mi 704 MXC-20 Critical SM_10E version in MXC-20 is Y

smatch not consistent with current
system version.
12 Ver-Misma 466 MCP Event Software version cannot Y Y Y Y Y Y Y

tch match current NE DB, or active
version on NVM is inconsistent
with RAM version
13 HS-Mismat 685 MCP Critical SW package cannot match Y

ch current HW configuration:
0 - SW unable to support
BG-20B_L2M;
1 - SW unable to support
SM_10E;
14 SW-HW-Mi 817 Card Critical If card B is Y Y Y Y Y Y

smatch controlled/managed by card A,
for example, ODU is managed
by MIF.
HW revision of card B (such as
ODU) is not compatible with
the SW/FW of card A.
15 SW-SW-Mi 818 Card Critical If card B is Y Y Y Y Y Y

smatch controlled/managed by card A,
for example, ODU is managed
by MIF.
SW version of card B (such as

ODU) is not compatible with
the SW/FW version of card A.
16 PS-FCU-Mis 819 MCP Critical Current power supply type is Y Y Y Y Y

match not compatible with current
fan unit , the power unit may
have no enough power to
drive the fans. It is required to
replace the power supply unit.
17 System-Err 452 NE Event Some kind of system error or Y Y Y Y

or anomaly occurs, such as task
suspend, free-memory-low,
CPU utilization high,
free-FD-low, memory block
header error, etc.
18 System-Fa 431 NE Critical Some kind of system error or Y Y Y Y Y Y Y

ult anomaly is detected and
persists for 3 seconds, such as
task suspend,
free-memory-low, CPU
utilization high, free-FD-low,
memory block header error,
etc.


name ID severity

0 0C 0 4 020 00 10
19 Cfg-Save-F 728 NE Critical Error or failure occurred when Y Y Y Y Y Y Y

ail NE saves configuration DB to
NVM, which may result in
failure to save DB or DB
corruption.
20 NEDB-Chec 409 NE Critical Error is found in validity Y Y Y Y Y Y Y

k-Fail checking of NE database
21 Version-act 402 NE Event Version activation is cancelled Y Y Y Y Y Y Y

ivation-fail because scheduled time is
past.
22 Patch-activ 403 NE Event Patch activation is cancelled Y Y Y Y Y Y

ation-fail because scheduled time is
past.
23 Patch-Insta 432 Card Major Patch is not installed Y Y Y Y Y Y

ll-Fail successfully on the card, it
may be caused by abnormity
of the card.
24 Version-Rol 404 NE Event Due to DB conversion fail, NE Y Y

lback version rolls back to previous
version during version
upgrade.
25 LCT-Master 550 NE Event LCT login NE.The event occurs Y Y Y Y Y Y Y

-Login only when LCT works in master
mode.
26 LCT-Master 551 NE Event LCT request for master work Y Y Y Y Y Y Y

-Request mode.
27 LCT-Master 500 NE Event LCT logout NE. The event Y Y Y Y Y Y Y

-Logout occurs only when LCT works in
master mode.
28 CLI-Login 688 NE Event CLI logs in to the NE. Y Y Y Y Y Y Y
29 CLI-Logout 689 NE Event CLI logs out from the NE. Y Y Y Y Y Y Y
30 CLI-In-Conf 690 NE Event CLI enters configuration mode. Y Y Y Y Y Y Y

ig-Mode
31 CLI-Exit-Co 691 NE Event CLI exits from configuration Y Y Y Y Y Y Y

nfig-Mode mode.
32 Security-ve NE Event Tried to log in to NE three

rify-fail times with wrong user name
or password.
33 CLI-Config- NE Event CLI requests configuration

Request mode.
34 CLI-Config- NE Event If the configuration is changed

Update by CLI, notify to EMS


name ID severity

0 0C 0 4 020 00 10
35 Current-Ve 421 MCP Critical This alarm indicates that Y Y Y Y

rsion-Repla current version in active bank
ced on NVM is not synchronized
with the running version of
memory.
This alarm could occur when

the version in current/active
bank is changed by special
tools (LCT, FTP).
36 Fail-To-Loa 439 MCP Event For BG-20, the SW version Y

d-SW-From package does not include SW
-EMS of some cards (DMCE1_32,
P345_3E), these cards will load
SW from EMS directly during
upgrade.
This event means the MCP

failed to load card SW from
EMS for consecutive three
attempts. The possible reason
is that proper SW
(WBG20_Emb_xxxx.bin) is
NOT installed in the ftp folder
of EMS server.
DCC/GCC
1 DCC-RX-De 519 COM-DCC Major DCC channel degrade in Y Y Y Y Y Y

grade receive direction.
2 DCC-TX-De 520 COM-DCC Major DCC channel degrade in Y Y Y Y Y Y

grade transmit direction.
3 DCC-Link-F 820 COM-DCC Critical DCC link is down due to AIS or Y Y Y Y Y Y

ail severe error rate.
4 RX-DCC-Err 821 COM-DCC Minor Error packets received within Y Y Y Y Y Y

Pkts-15M-T 15 minutes are crossing the
C threshold.
5 TX-DCC-Err 822 COM-DCC Minor Packets loss due to transmit Y Y Y Y Y Y

Pkts-15M-T failure within 15 minutes is
C crossing the threshold.
6 DCC-Drop- 823 Minor This alarm is effective only

Pkts-15M-T when DCC aggregation is
C enabed in MW-2M card.
Dropped packets within 15

minutes is crossing the
threshold due to congestion.
Miscellaneous
1 MT-Releas 835 MO Event Maintenance operation with Y Y Y Y Y Y

e timeout is released due to
timer expiration.
This event should contain a

parameter to specify which
maintenance operation of this
MO is released.


name ID severity

0 0C 0 4 020 00 10
2 RTC-Reque 435 MCP Event Represents NE RTC is not Y Y Y Y

st initialized and request for a
NE-RTC SET operation (to be
synchronized with EMS).
EMS should initiate NE RTC set

operation upon this event.
3 RTC-Chang 436 MCP Event NE RTC is changed. This event Y Y Y Y

e should be reported when new
NE RTC is accepted by MCP.
Parent Topic
2.9.3 SDH and PDH Port Alarms

Table 2-6: SDH and PDH port alarm list
ID Alarm name Cause ID Source Default Description Applicable system

severity
MSPP/N BG-2 BG-2 BG-3 BG-6 NPT-10 NPT-12 NPT-10

PT 0 0C 0 4 20 00 10
PDH Physical Layer (PPI)
1 PPI-LOS 324 PPI Critical Loss of signal on PDH Y Y Y Y Y Y Y

physical interface.
2 PPI-R-AIS 325 PPI Major Alarm Indication Signal Y Y Y Y Y Y Y

(AIS) detected in PDH
line Rx direction.
3 PPI-T-AIS 801 PPI Minor Sending AIS in PDH line Y Y Y Y Y Y Y

Tx direction, i.e., PDH AIS
detected or inserted in
PDH demapping path.
4 PPI-LOF 326 PPI Major Loss of frame.
5 PPI-LOMF 668 PPI Major Loss of multiframe.
6 PPI-RAI 327 PPI Warning Remote alarm indication.
7 PPI-SD 623 PPI Minor Bit error rate is crossing

SD threshold.
8 PPI-EXC 624 PPI Major Bit error rate is excessive

and crossing SF
threshold.
9 Codir-LOS 644 Codir Critical Loss of signal on Y Y Y Y Y

interface of
SM_Codir_4E


severity

PT 0 0C 0 4 20 00 10
10 Line-Rx-Inac 415 V.24 Major No actvity is detected on Y Y Y Y Y

tivity line of V.24 port Rx.
PDH Path Layer - E1 Framer and C37.94
1 E1-LOS 645 E1 Major E1 loss of signal.
2 E1-AIS 646 E1 Major Alarm indication signal of Y Y Y Y Y Y

E1.
3 E1-LOF 647 E1 Major Loss of Frame (only for Y Y Y Y Y Y

framed mode).
4 E1-CAS-LOM 674 E1 Major Loss of CAS multiframe Y Y Y Y Y Y

F (only for PCM30). CAS
means channel
associated signaling.
5 E1-CRC-LO 675 E1 Major Loss of CRC-4 multiframe Y Y Y Y Y Y

MF (only for PCM with CRC).
6 E1-RAI 649 E1 Minor Remote Alarm Indication Y Y Y Y Y Y

(only for framed mode).
7 E1-SD 650 E1 Minor 2M Signal Degrade (only Y Y Y Y Y Y

for framed mode).
8 E1-EXC 651 E1 Major 2M Excessive Bit Error Y Y Y Y Y Y

(only for framed mode).
9 Yellow 705 C37.94 Minor Remote defect Y Y Y Y Y

indication.
10 N-Mismatch 706 C37.94 Major This alarm exists only in Y Y Y Y Y

manual mode. When N
from line is bigger than N
configured is received,
this alarm should be
declared.
11 Line-N-Error 707 C37.94 Major The N value received Y Y Y Y Y

from line is not a valid
value. The valid value
should be 1~12.
12 E1-N-Error 708 C37.94 Major Unable to get valid OH (N Y Y Y Y Y

and signaling) from E1
channel (actually from
internal 4M-PCM) and
OH channel is not all of
them, exists only in
transparent mode. OH
channel not configured
or E1-LOF SHOULD NOT
result in this alarm.
SDH Physical Interface Layer - SPI
1 SPI-LOS 301 SPI Critical SDH Physical Interface Y Y Y Y Y Y

Loss of Signal.
2 SPI-TF 348 SPI Critical SDH Physical Interface Y Y Y Y Y Y

Transmit Failure.


severity

PT 0 0C 0 4 20 00 10
SDH Regenerator Section Layer - RS
1 RS-LOF 302 RS Critical Regenerator Section Loss Y Y Y Y Y Y

of Frame.
2 RS-OOF 303 RS Critical Regenerator Section Out Y Y Y Y Y Y

of Frame.
3 RS-TIM 304 RS Major Regenerator Section Y Y Y Y Y Y

Trace Identification(J0)
Mismatch.
SDH Multiplexing Section Layer - MS
1 MS-AIS 305 MS Major Multiplex Section Alarm Y Y Y Y Y Y

Indication Signal.
2 MS-RDI 306 MS Minor Multiplex Section Y Y Y Y Y Y

Remote Defect
Indication.
3 MS-REI 307 MS Mask Multiplex Section Y Y Y Y Y Y

Remote Error Indication.
4 MS-SD 617 MS Minor MS Signal Degrade due Y Y Y Y Y Y

to BER exceeding SD
threshold.
5 MS-EXC 618 MS Major MS Excessive Bit Error Y Y Y Y Y Y

and exceeds SF
threshold.
6 MSP-PM 642 MS Major MSP Protocol mismatch. Y Y Y Y Y Y
7 MS-Protecti 477 MS Event MS protection switch Y Y Y Y Y Y

on-Switch event (for MSP 1+1).
8 MS-SPRing- 709 MS-R-PG Event An MS-SPRing switching Y Y Y

Switch and bridging action has
been executed
successfully.
Parameter: West/east
9 MS-SPRing- 710 MS-R-PG Event A MS-SPRing switching & Y Y Y

Switch-Rele bridge action is released
ase
Parameter: West/East
10 West-Incons 711 MS-R-PG Major Inconsistent APS codes Y Y Y

isten-APS-C received.
odes
11 West-Defaul 712 MS-R-PG Minor Default K1/K2 bytes Y Y Y

t-K-Bytes received.
12 West-Impro 713 MS-R-PG Major Improper APS codes Y Y Y

per-APS-Co received.
des
13 East-Inconsi 720 MS-R-PG Major Inconsistent APS codes Y Y Y

sten-APS-Co received.
des


severity

PT 0 0C 0 4 20 00 10
14 East-Default 721 MS-R-PG Minor Default K1/K2 bytes Y Y Y

-K-Bytes received.
15 East-Improp 722 MS-R-PG Major Improper APS codes Y Y Y

er-APS-Code received.
s
16 APS-Channe 714 MS-R-PG Critical Process fails in APS Y Y Y

l-Proc-Fail controller.
17 Node-ID-Mi 715 MS-R-PG Critical Node ID is unexpected Y Y Y

smatch and mismatched
according to ring map.
18 MS-SPRing- 716 MS-R-PG Warning HO or LO VC-4 squelch Y Y Y

Squelch action occurs.
SDH High-Order Path Layer - HP (VC-4)
1 AU-LOP 308 AU-4 Major Administration Unit Loss Y Y Y Y Y Y

of Pointer.
2 HP-LOM 309 VC-4 Major High Order Path Loss of Y Y Y Y Y Y

Multiframe.
3 HP-AIS 310 VC-4 Major High Order Path Alarm Y Y Y Y Y Y

Indication Signal, i.e.,
AU-AIS.
4 HP-RDI 311 VC-4 Minor High Order Path Remote Y Y Y Y Y Y

Defect Indication.
5 HP-REI 312 VC-4 Mask High Order Path Remote Y Y Y Y Y Y

Error Indication.
6 HP-TIM 313 VC-4 Minor High Order Path Trace Y Y Y Y Y Y

Identification (J1)
Mismatch.
7 HP-UNEQ 314 VC-4 Minor High Order Path Y Y Y Y Y Y

Unequipped.
8 HP-SLM 315 VC-4 Minor High Order Path Signal Y Y Y Y Y Y

Label (C2) Mismatch.
9 HP-SD 619 VC-4 Minor VC-4 Signal Degrade. Y Y Y Y Y Y
10 HP-EXC 620 VC-4 Major VC-4 Excessive Bit Error Y Y Y Y Y Y

(Cross SF threshold).
SDH Low-Order Path Layer - HP (VC-3, VC-12)
1 TU-LOP 316 LOVC Major Tributary Unit Loss of Y Y Y Y Y Y

Pointer.
2 LP-AIS 317 LOVC Major Low Order Path Alarm Y Y Y Y Y Y

Indication Signal, i.e,
TU-AIS.
3 LP-RDI 318 LOVC Minor Low Order Path Remote Y Y Y Y Y Y

Defect Indication.


severity

PT 0 0C 0 4 20 00 10
4 LP-REI 319 LOVC Mask Low Order Path Remote Y Y Y Y Y Y

Error Indication.
5 LP-TIM 321 LOVC Minor Low Order Path Trace Y Y Y Y Y Y

Identification Mismatch.
VC-12P
6 LP-UNEQ 322 LOVC Minor Low Order Path Y Y Y Y Y Y

Unequipped.
7 LP-SLM 323 LOVC Minor Low Order Path Signal Y Y Y Y Y Y

Label Mismatch.
8 LP-ESLM 615 LOVC Minor Low Order Path

Extended Signal Label
(K4) Mismatch.
9 LP-SD 621 LOVC Minor VC-3/VC-12 Signal Y Y Y Y Y Y

Degrade.
10 LP-EXC 622 LOVC Major VC-3/VC-12 Excessive Bit Y Y Y Y Y Y

Error.
11 SNC-Protect 483 LOVC Event SNCP Selector switched Y Y Y

ion- Switch due to SD/SF or
maintenance.
TCA for SDH and PDH layers
1 UAT-NE 501 RS, MS, Major UAS Start Near End. Y Y Y Y Y Y Y

VC-4,
VC-3,
VC-12, PPI,
Framed E1
2 UAT-FE 214 MS, Major UAS Start Far End. Y Y Y Y Y Y Y

VC-4,
VC-3,
VC-12,
Framed E1
3 ESTC-15M-N 201 RS, MS, Minor ES in 15 minutes Y Y Y Y Y Y Y

E VC-4, threshold crossing near
VC-3, end.
VC-12, PPI,
Framed E1
4 SESTC-15M- 202 RS, MS, Major SES in 15 minutes Y Y Y Y Y Y Y

NE VC-4, threshold crossing near
VC-3, end.
VC-12, PPI,
Framed E1
5 BBETC-15M- 203 RS, MS, Minor BBE in 15 minutes Y Y Y Y Y Y Y

VC-3, end.
VC-12,
Framed E1


severity

PT 0 0C 0 4 20 00 10
6 UASTC-15M 215 RS, MS, Major UAS in 15 minutes Y Y Y Y Y Y Y

-NE VC-4, threshold crossing near
VC-3, end.
VC-12, PPI,
Framed E1
7 CV-15M-NE 524 PPI Major CV in 15 minutes Y Y Y Y Y Y

threshold crossing near
end.
8 ESTC-15M-F 207 MS, VC-4, Warning ES in 15 minutes Y Y Y Y Y Y Y

E VC-3, threshold crossing near
VC-12, PPI, end.
Framed E1
9 SESTC-15M- 208 MS, VC-4, Warning SES in 15 minutes Y Y Y Y Y Y Y

FE VC-3, threshold crossing near
VC-12, PPI, end.
Framed E1
10 BBETC-15M- 209 MS, VC-4, Warning BBE in 15 minutes Y Y Y Y Y Y Y

FE VC-3, threshold crossing far
VC-12, end.
Framed E1
11 UASTC-15M 802 MS, VC-4, Warning UAS in 15 minutes Y Y Y Y Y Y Y

-FE VC-3, threshold crossing far
VC-12, end.
Framed E1
12 OFSTC-15M 502 RS Major OFS in 15 minutes Y Y Y Y Y Y

threshold crossing.
13 PPJCTC-15M 503 AU-4, TU Minor PPJC in 15 minutes Y Y Y Y Y Y

threshold crossing.
14 NPJCTC-15 504 AU-4, TU Minor NPJC in 15 minutes Y Y Y Y Y Y

M threshold crossing.
15 ESTC-24H-N 204 RS, MS, Minor ES in 24 hours threshold Y Y Y Y Y Y Y

E VC-4, crossing near end.
VC-3,
VC-12, PPI,
Framed E1
16 SESTC-24H- 205 RS, MS, Major SES in 24 hours threshold Y Y Y Y Y Y Y

NE VC-4, crossing near end.
VC-3,
VC-12, PPI,
Framed E1
17 BBETC-24H- 206 RS, MS, Minor BBE in 24 hours Y Y Y Y Y Y Y

VC-3, end.
VC-12,
Framed E1
18 UASTC-24H- 216 RS, MS, Major UAS in 24 hours Y Y Y Y Y Y Y

VC-3, end.
VC-12, PPI,
Framed E1


severity

PT 0 0C 0 4 20 00 10
19 CV-24H-NE 525 PPI Major CV in 24 hours threshold Y Y Y Y Y Y

crossing near end.
20 ESTC-24H-F 210 MS, VC-4, Warning ES in 24 hours threshold Y Y Y Y Y Y Y

E VC-3, crossing far end.
VC-12,
Framed E1
21 SESTC-24H- 211 MS, VC-4, Warning SES in 24 hours threshold Y Y Y Y Y Y Y

FE VC-3, crossing far end.
VC-12,
Framed E1
22 BBETC-24H- 212 MS, VC-4, Warning BBE in 24 hours Y Y Y Y Y Y Y

FE VC-3, threshold crossing far
VC-12, end.
Framed E1
23 UASTC-24H- 803 MS, VC-4, Warning UAS IN 24 hours Y Y Y Y Y Y Y

FE VC-3, threshold crossing at
VC-12, end.
Framed E1
24 OFSTC-24H 505 RS Major OFS in 24 hours Y Y Y Y Y Y

threshold crossing.
25 PPJCTC-24H 506 AU-4, TU Minor PPJC in 24 hours Y Y Y Y Y Y

threshold crossing.
26 NPJCTC-24H 507 AU-4, TU Minor NPJC in 24 hours Y Y Y Y Y Y

threshold crossing.
Parent Topic
2.9.4 EoS and EoP Port Alarms

Table 2-7: EoS and EoP port alarm list

severity

0 0C 0 4 20 00 10
GFP Layer
1 LOFD 335 GFP Critical Loss of Frame Y Y Y Y Y Y

Delineation
2 CSF-1 638 GFP Major Client Signal Failure Y Y Y Y Y Y

(Type 1, loss of signal)
3 CSF-2 639 GFP Major Client Signal Failure

(Type 2, loss of sync)


severity

0 0C 0 4 20 00 10
4 UPI-Mismat 654 GFP Major User payload identifier Y Y Y Y Y Y

ch mismatch
5 EXI-Mismatc 339 GFP Major Extension header Y Y Y Y Y Y

h indication mismatch
6 GFP-R-ErrPk 526 GFP Major Rx Error Pkts 15min Y Y Y Y Y Y

ts-TC-15M Threshold Crossing
7 EOS-EXC 419 GFP Critical Excessive GFP packet

errors are detected and
exceeds the EXC
threshold.
8 EOS-SD 420 GFP Minor Packet error rate of

GFP exceeds the
Degrade threshold
VCAT Group Layer
1 LOA 340 VCG Critical VCG Loss of Alignment Y Y Y Y Y Y
2 TLCr 613 VCG Critical Total Loss of Capacity Y Y Y Y Y Y

in receive direction
3 TLCt 800 VCG Critical Total Loss of Capacity Y Y Y Y Y Y

in transmit direction
4 PLCr 614 VCG Major Partial Loss of Capacity Y Y Y Y Y Y

on RX side
5 PLCt 616 VCG Major Partial Loss of Capacity Y Y Y Y Y Y

on TX side
VC Layer (LCAS)
1 LP-LOM 341 VC12/VC3( Critical Low Order Path Loss of Y Y Y Y Y Y

VCAT) Multiframe
2 LP-SQM 344 VC12/VC3( Major Low Order Path SQ Y Y Y Y Y Y

VCAT) Number Mismatch
3 HP-SQM 347 VC-4(VCAT Major High Order Path SQ Y Y Y Y Y Y

) Number Mismatch
4 LCAS-Fail 342 E1/VC12/V Major LCAS member Y Y Y Y Y Y

C3/VC-4(V Add/Remove failed
CAT)
5 LCAS-CRC-Er 343 E1/VC12/V Major LCAS protocol data Y Y Y Y Y Y

ror C3/VC-4(V package CRC Error
CAT)
Parent Topic

2.9.5 Ethernet PHY (ETY) Port Alarms

Table 2-8: Ethernet PHY (ETY) port alarm list

name ID severity

PT 0 0C 0 20 0 0
Ethernet PHY&MAC
1 GE-LOS 637 Ethernet Critical Optical loss of signal Y Y

PHY on GE port of
ESW_2G_8F_E.
2 PHY-LOS 673 Ethernet Critical Optical signal loss on Y Y Y Y Y Y

PHY receive side of GbE or
FX optical port.
3 Link-Fail 42 Ethernet Major Link fail (detected in Y Y Y Y Y Y Y

PHY the Ethernet PHY).
MNG-Port- 794 MCP Card Major The management port Y Y Y Y Y Y Y

Down gets link down.
4 AN-Ability- 640 Ethernet Major Auto-negotiation Y Y Y Y Y Y Y

Mismatch PHY result in link capacity
not being fully
utilized.
5 Master-Sla 725 Ethernet Major Master/slave Y Y Y Y Y Y

ve-Config-F PHY configuration fault,
ault local PHY operating
mode is same as that
of remote/peer PHY,
i.e., both are master
or slave.
6 AN-Fail 678 Ethernet Major Auto-negotiation fail. Y Y Y Y Y Y Y

PHY
7 Remote-Fa 679 Ethernet Minor Remote link fault (PHY Y Y Y Y Y Y Y

ult PHY MII status indication).
8 Rx-ErrPkts- 521 Ethernet Major Rx Error Pkts 15-min Y Y Y Y Y Y Y

TC-15M MAC Threshold Crossing.
9 Rx-BCPkts- 522 Ethernet Major Rx Broadcast Pkts Y Y Y Y Y Y Y

TC-15M MAC 15-min Threshold
Crossing.
10 Rx-MCPkts- 523 Ethernet Major Rx Multicast Pkts Y Y Y Y Y Y Y

TC-15M MAC 15-min Threshold
Crossing.
11 Tx-DropRat 824 Ethernet Major Drops per million for Y Y Y Y Y Y Y

ioPpm-TC MAC egress interface for
each Class of Service
exceeding the
threshold.


name ID severity

PT 0 0C 0 20 0 0
12 L2 Traffic 677 MESW_6F Event MESW_6F traffic Y

Recovered recovered from a fatal
error (queue stops
working due to
unknown reason).
13 Port-Q-Bloc 686 MESW_6F Critical FE LAN port of Y Y

ked , MESW_6F and
ESW_2G_ ESW_2G_8F_E get
8F_E blocked due to a fatal
error (Queue stops
FE LAN working)
port
14 High-BER 416 10GE Port Critical Excessive Sync errors Y Y Y Y

are detected and
exceeds the HI_BER
threshold (1E-4).
15 ETH-EXC 417 Ethernet Major Excessive packet

Port errors are detected
and exceeds the EXC
threshold.
16 ETH-SD 418 Ethernet Minor Packet error rate

Port exceeds the Degrade
threshold.
17 LOSYNC 130 10GE Port Major Loss of Y Y Y

Synchronization
18 LF 135 10GE Port Major Local Fault Y Y Y
18 PCS-ESTC-1 143 10GE Port Minor ES in 15 Minutes Y Y Y

5M-NE Threshold Crossing
Near End in PCS
20 PCS-SESTC- 144 10GE Port Major SES in 15 Minutes Y Y Y

15M-NE Threshold Crossing
Near End in PCS
21 PCS-CV-15 145 10GE Port Major CV in 15 Minutes Y Y Y

M-NE Threshold Crossing
Near End in GFP
Link OAM
1 OAM-Disco 659 Ethernet Minor If Discovery process Y Y Y Y Y Y Y

very-fail PHY cannot successfully
complete, Discovery
Failed alarm is raised.


name ID severity

PT 0 0C 0 20 0 0
2 OAM-Link-L 660 Ethernet Major After Discovery Y Y Y Y Y Y Y

ost PHY process completes,
both local and remote
ports transmit
OAMPDUs to each
other once per
second. If no
OAMPDU is received
for 5 seconds, Link
Lost alarm raised.
3 OAM-Remo 661 Ethernet Minor If local port receives Y Y Y Y Y Y Y

te-Link-Faul PHY OAMPDU with Link
t Fault, flag is set.
4 OAM-Local- 662 Ethernet Major When there are Y Y Y Y Y Y Y

Link-Event PHY problems detected on
the link.
5 OAM-Remo 663 Ethernet Minor If local port receives Y Y Y Y Y Y Y

te-Link-Eve PHY Link Event OAMPDU
nt from the remote port.
6 OAM-Local- 664 Ethernet Event Issued when port Y Y Y Y Y Y Y

loopback PHY enters local loopback
mode as a result of
remote loopback
request.
7 OAM-Local- 670 Ethernet Event Issued when port local Y Y Y Y Y Y Y

loopback-r PHY loopback is released
elease as a result of remote
loopback release
request.
8 Port-Is-Loo 719 Ethernet Warning External loopback is Y Y Y Y Y Y Y

ped PHY detected on the
Ethernet port on
which link OAM is
enabled. The
loopback may be
caused by external
loopback cable or
facility loopback on
link partner.
LAG
1 LAG-Partial 641 LAG Major Partial Loss of Y Y Y Y Y Y Y

-Links-Dow Capacity
n (bidirectional).
2 LAG-Link-d 643 LAG Critical LAG Link down due to Y Y Y Y Y Y Y

own the number fo failed
ports exceeding the
defined threshold.
3 LAG-All-Lin 608 LAG Critical All ports in the LAG Y Y Y Y Y Y Y

ks-Down are down.


name ID severity

PT 0 0C 0 20 0 0
ETY Interface
 MoE interface
1 Fail-to-Get- 825 MoE Critical Y Y Y Y Y Y Y
MAC Interface  CESoIP
interface
 CESoMPLS
interface
2 Header-Err 826 MoE Warning MoE interface Y Y Y Y Y Y Y

or-TC Interface
PoE
1 PD-Disconn 424 PoE Port Event PD is disconnected Y Y Y Y Y Y

ect from PSE.
Detect only when PoE

is enabled.
2 PD-Over-cu 425 PoE Port Event PD over-current Y Y Y Y Y Y

rrent occurs.

is enabled.
3 PD-Short-c 426 PoE Port Event PD short current Y Y Y Y Y Y

urrent occurs.
is enabled.
4 PD-Startup- 427 PoE Port Event PD startup Over Y Y Y Y Y Y

Over-curre Current occurs.
nt
is enabled.
5 PD-Fault 428 PoE Port Critical Fault (such as Y Y Y Y Y Y

over-current, short,
startup over current)
is detected, and
power feeding over
Ethernet is shutdown
due to this fault. To
clear this alarm, need
to check the line and
PD, or disable/enable
PoE.
Parent Topic

2.9.6 Ethernet Service Alarms

Table 2-9: Ethernet service alarm list

name severity

PT 0 0C 0 4 20 00 10
VSI (VPN)
1 McVpnDrop 665 VSI Warning Storm Control Dropped Y Y Y Y Y Y Y

Octets Octets, Number of
multicast, broadcast,
and unknown
destination unicast
bytes dropped by BSC
policer of this VPN,
exceeds the threshold.
2 VPNQuotaD 666 VSI Warning Packets dropped due Y Y Y Y Y Y Y

ropPackets to FIB quota exceeding
threshold.
3 LowClassDis 667 VSI Warning Percentage of low class

cardPPS packets discards due to
throughput control.
4 MACMoveE 723 VSI Major Number of MAC move Y Y Y Y Y Y Y

vents-TC events exceeds
threshold
5 CESVPN-PB 408 VSI (PB Event Protection Switch Y Y Y Y Y Y

P2P-APS P2P Event for 1+1 PB-P2P
CES-VSI) CES VSI
Parameters:
1. Last working
VLAN-ID;
2. New working
VLAN-ID.
Ethernet Service (CFM)
1 INVALID_M 694 Local MEP Major Invalid MA ID Y Y Y Y Y Y Y

AID
Receiving CCM frame
with invalid MA_ID or
on port that is not
registered in VSI.
2 LOW_LEVEL 695 Local MEP Major Received lower level Y Y Y Y Y Y Y

_CCM CCM
Receiving CCM frame
with valid MA_ID and
invalid MEP_ID, invalid
CCM_Period.
3 MEP_NOT_ 696 Local MEP Major Received unexpected Y Y Y Y Y Y Y

CONFIGURE MEP ID.
D
4 MEP_SAME 697 Local MEP Major Received duplicate Y Y Y Y Y Y Y

_MEPID MEP ID.


name severity

PT 0 0C 0 4 20 00 10
5 CCM_INTER 698 Local MEP Major Incorrect CCM Interval. Y Y Y Y Y Y Y

VAL_MISM
ATCH
6 RX_CCM_TI 699 Local MEP Major CCM timer expired/ Y Y Y Y Y Y Y

MER_EXPIR Connectivity Loss
ED
Failing to receive valid
CCM frame from one
of the remote MEPs of
MA during the time
period of 3.5 *
MA_CCMPeriod.
7 MEP_INTER 700 Local MEP Minor AC interface down Y Y Y Y Y Y Y

FACE_STAT
US One or more of the
remote MEPs is
reporting a failure in its
interface state (not
isUp).
8 MEP_PORT 701 Local MEP Minor AC port down. Y Y Y Y Y Y Y

_STATUS
9 MEP_RDI 702 Local MEP Minor Received CCM with RDI Y Y Y Y Y Y Y

bit.
Indicating the
aggregate health of the
remote MEPs.
10 RMEP_ 837 Remote Major Raised when the Y Y Y Y Y Y Y

FD_NOT_C MEP percentile of
OMPL_ALM non-compliant FD
_15M measurements in
15-min exceeds the
threshold value
100-MA_PERCENTILE_F
D.
11 RMEP_FDV_ 838 Remote Major Raised when percentile Y Y Y Y Y Y Y

NOT_COMP MEP of non-compliant FDV
L_FWD_AL measurements
M_15M (forward direction) in
15 min exceeds the
threshold value
100-MA_PERCENTILE_F
DV.
12 RMEP_FDV_ 839 Remote Major Raised when percentile Y Y Y Y Y Y Y

NOT_COMP MEP of not-compliant FDV
L_BCK_ALM measurements
_15M (backward direction) in
15 min exceeds the
threshold value
100-MA_PERCENTILE_F
DV.
13 RMEP_UNA 756 Remote Major Raised when Y Y Y Y Y Y Y

VAIL_FWD_ MEP unavailability period is
ALM detected in forward
direction.


name severity

PT 0 0C 0 4 20 00 10
14 RMEP_UNA 757 Remote Major Raised when Y Y Y Y Y Y Y

VAIL_BCK_A MEP unavailability period is
LM detected in backward
direction.
ERPS and xSTP
1 ERPS-Topo- 718 ERPS-VSI Event Ethernet Ring Switch Y Y Y Y Y Y Y

Change happened.
Ring protection link

(RPL) state in Ethernet
Ring is changed from
blocked to unblocked
or unblocked to
blocked.
2 Bridge-topo 487 Swtich Event Topology of span tree Y Y Y Y Y Y Y

-change instance changed.
3 Root-port-c 676 Switch Event Root port of STP Y Y Y Y Y Y Y

hange changed.
Parent Topic
2.9.7 MPLS Alarms

Table 2-10: MPLS alarm list

name severity

PT 0 0C 0 4 20 0
MPLS Tunnel (tOAM, Y.1711)
1 OAM-LOCV 680 MPLS Major Loss of Connectivity Y Y Y Y Y Y

tunnel verification.
2 OAM-TTSI- 681 MPLS Major Tunnel Trail Termination Y Y Y Y Y Y

Mismerge tunnel Source Identifier
Mismerge.
3 OAM-TTSI- 682 MPLS Major Tunnel Trail Termination Y Y Y Y Y Y

Mismatch tunnel Source Identifier
Mismatch.
4 OAM-Exces 683 MPLS Major Excessive CV or FFD Y Y Y Y Y Y

s tunnel packets.
5 PerfLspOut 684 Queue Minor WRED discard ratio in Y Y Y Y Y Y Y

WredRatioP per MPLS current monitored interval
pm-TC tunnel or for this out-segment is
per QB crossing threshold.


name severity

PT 0 0C 0 4 20 0
MPLS NNI Port
1 FRR-InUse-S 729 MPLS NNI Event This event notifies Y Y Y Y Y Y Y

tate-Chang (MoT/Mo manager of the change of
e E) FRR in-use state:
 When traffic on at
least one protected
tunnel on this MPLS
NNI port is switched
to FRR tunnel, the
port should enter or
keep in
"FRR-InUse-state".
 When traffic of all
protected tunnels
are reverted from
bypass tunnels, the
port should exit
from
"FRR-InUse-State".
 When the state
changes, this event
should be reported
with proper
parameter to
indicate the final
state.
BFD
1 BFD-Down 753 Bi-LSP/Por Major Raised when BFD state Y Y Y Y Y Y Y

t machine lies in DOWN
state.
(dLOC, dRDI, dLDI, ADMIN

DOWN. Etc)
2 BFD-LOC 754 Bi-LSP/Por Major Raised when no BFD CC Y Y Y Y Y Y Y

t packets is received in
detect time
3 BFD-RDI 755 Bi-LSP/Por Major Raised when received Y Y Y Y Y Y Y

t remote DOWN status
PW
1 pw-redund 433 MPLS Event PW (mpls tunnel + VSI) Y Y Y Y Y Y Y

ancy-APS tunnel + primary/secondary swtich
VSI event
LSP 1:1 (BD Tunnel)
1 Linear 781 BD Tunnel Event This is an event. Y Y Y Y Y Y Y

Protection
Switching Raised when primary->
secondary or secondary->
primary switching and
SHALL notify direction of
switching from XX to XX.


name severity

PT 0 0C 0 4 20 0
2 Linear 782 BD Tunnel Minor Raised when If there is an Y Y Y Y Y Y Y

Protection inconsistency for PT
Type between the two end
Mismatch points in this protection
domain.
Cleard when if there is an

consistency for PT.
3 Linear 783 BD Tunnel Minor Raised in all cases when Y Y Y Y Y Y Y

Protection Protecting LSP does not
PSC receive PSC message in
Protocol 60s (max periodical
Down interval*2).
Cleared when there are

PSC packets received in
secondary Bi-LSP.
4 Tunnel 784 BD Tunnel Minor Raised when primary or Y Y Y Y Y Y Y

Protection secondary path fails.
Degrade
Clear when both paths are
UP or DOWN.
5 Tunnel 785 BD Tunnel Major Raised when primary and Y Y Y Y Y Y Y

Down secondary paths fail.
Clear when at least one
path is UP.
Parent Topic
2.9.8 CES Service Alarms

Table 2-11: CES service alarm list

name severity

PT 0 0C 0 4 20 0 0
CES Service
1 RxPsnLOPS 211 CES Major LOPS alarm at PSN to Y Y Y Y Y Y

Service TDM direction.
2 RxPsnStray 222 CES Minor Excessive stray packet Y Y Y Y Y Y

Pkts Service discards at PSN to TDM
direction.
3 RxPsnMalfo 223 CES Minor Excessive malformed Y Y Y Y Y Y

rmPkts Service packet discards at PSN
to TDM direction.


name severity

PT 0 0C 0 4 20 0 0
4 RxPsnBuffer 224 CES Minor Excessive jitter buffer Y Y Y Y Y Y

Overrun Service overruns at PSN to
TDM direction.
5 RxPsnPLR 225 CES Minor Excessive packet loss Y Y Y Y Y Y

Service ratio at PSN to TDM
direction.
6 RxPsnPER 226 CES Minor Excessive packet error Y Y Y Y Y Y

Service ratio at PSN to TDM
direction.
7 RxPsnFarEn 227 CES Major Remote IWF is in LOPS Y Y Y Y Y Y

dLOPS Service state.
8 RxPsnRecCl 228 CES Minor Recovered clock state Y Y Y Y Y Y

k Service is abnormal.
Parent Topic
2.9.9 EDFA and OTN Port Alarms

Table 2-12: EDFA and OTN port alarm list

name severity

PT 0 0C 0 4 20 00 10
EDFA
1 Power-In-L 790 Amplifier Major Input power is less than Y Y Y Y

OS the input LOS threshold.
Detected by OBC SW
when EDFA pin “Loss of
Input Alarm” (pin 19) is
high. When Loss of input
signal is detected, Laser
Pump will be shut down.
2 Output-Pow 791 Amplifier Major The deviation of output Y Y Y Y

er-Degrade power from the target
value exceeds the
threshold. Detected by
OBC SW when EDFA pin “
Output Power Alarm ”
(pin 20) is high.
3 Power-In-O 792 Amplifier Major Input power is out of Y Y Y Y

verload overload tolerance of the
EDFA receiver.


name severity

PT 0 0C 0 4 20 00 10
4 Power-In-D 793 Amplifier Major IuInput power is lower Y Y Y Y

egrade than the expected
degraded threshold of the
EDFA receiver.
Optical Physical Layer (OPS)
1 OP-LOS 816 OPS Major Loss of optical signal on Y Y Y Y

laser receiver, detected
on RX-LOS of XFP output.
OTN Section Layer - OTUk
1 OTN-LOS 730 OTUk Critical Loss of signal Y Y Y
2 OTN-LOF 731 OTUk Critical Loss of frame.If the frame Y Y Y

alignment process is in
the out-of-frame (OOF)
state for 3 ms, LOF shall
be declared.
3 OTU-LOM 732 OTUk Critical Loss of multiframe. Y Y Y
If the multiframe
alignment process is
persistently in the
out-of-multiframe (OOM)
state for 3 ms, LOM
defect shall be declared.
LOM shall be cleared
immediately when the
multiframe alignment
process is in the
in-multiframe (IM) state.
4 OTU-AIS 733 OTUk Major OTU AIS (Alarm Indication Y Y Y

Signal), PN11
5 OTU-BDI 734 OTUk Minor OTU backward Defect Y Y Y

Indication.
BDI shall be declared if
the BDI bit in the SM
overhead field (byte 3, bit
5) is "1" for 5 consecutive
frames. BDI shall be
cleared if the BDI bit in
the SM overhead field is
"0" for 5 consecutive
frames. During signal fail
conditions of the data
signal, BDI shall be set to
false.


name severity

PT 0 0C 0 4 20 00 10
6 OTU-TIM 735 OTUk Major Trace identifier mismatch Y Y Y

in OUT.
The TTI mismatch process

reports the trace
identifier mismatch defect
(dTIM). The process is
based on the comparison
of expected APIs (i.e.,
SAPI and DAPI) with the
APIs in the incoming
signal. The APIs are part
of the 64 byte TTI as
defined in [ITU-T G.709].
Depending on the
topology, only the SAPI,
only the DAPI or both SAPI
and DAPI are taken into
account for the mismatch
detection.
7 OTU-DEG 736 OTUk Major Signal Degraded. Y Y Y
A degraded signal defect

(DEG) shall be detected if
the equivalent BER
exceeds a preset
-x
threshold of 10 , x = 5, 6,
7, 8 or 9. The degraded
signal defect shall be
cleared if the equivalent
-(x+1)
BER is better than 10 .
8 OTU-IAE 101 OTUk Major Incoming alignment error; Y Y Y
IAE shall be declared if the

IAE bit in the SM
frames. dIAE shall be
cleared if the IAE bit in the
SM overhead field is "0"
for 5consecutive frames.
9 OTU-BIAE 102 OTUk Major Backward Incoming Y Y Y

alignment error;
dBIAE shall be declared if

the BEI/BIAE bits in the
SM/TCM overhead field
(byte 3, bits 1 to 4) are
"1011" for 3consecutive
frames. dBIAE shall be
cleared if the BEI/BIAE
bits in the SM/TCM
overhead field are not
equal to "1011" for 3
consecutive frames.


name severity

PT 0 0C 0 4 20 00 10
10 FCE-EXC 737 OTUk Minor FEC corrected errors - Y Y Y

excessive errors present.
The FCE-EXC alarm is

raised based on the
FCE-BER parameter. The
FCE-BER is calculated from
the FEC corrected errors
counts over a 25 second
integration window and is
updated once a second.
The FCE-EXC alarm is
raised and cleared on a
one second basis. The
FCE-BER threshold to
trigger the FCE-EXC is
"FCE-BER>10^-4"
11 FCE-DEG 738 OTUk Warning FEC corrected errors- Y Y Y

degraded errors present
The FCE-DEG alarm is
raised based on the
FCE-BER parameter. The
FCE-BER is calculated from
the FEC corrected errors
counts over a 25 second
integration window and is
updated once a second.
The FCE-DEG alarm is
raised and cleared on a
one second basis. The
FCE-BER threshold to
trigger the FCE-DEG alarm
is "FCE-BER>10^-6".
12 OTU-UAT-N 739 OTUk Major Unavailable time near end Y Y Y

E
13 OTU-UAT-F 740 OTUk Minor Unavailable time far end Y Y Y

E
14 OTU-BBE-TC 741 OTUk Minor Threshold-crossing alert Y Y Y

-15M-NE for BBE accumulated near
end in 15Min

-15M-FE for BBE accumulated far
end in 15Min

-24H-NE for BBE accumulated near
end in 24 hours

-24H-FE for BBE accumulated far
end in 24 hours
18 OTU-ES-TC- 745 OTUk Minor Threshold-crossing alert Y Y Y

15M-NE for ES accumulated near
end in 15Min


name severity

PT 0 0C 0 4 20 00 10

15M-FE for ES accumulated far
end in 15Min

24H-NE for ES accumulated near
end in 24 hours

24H-FE for ES accumulated far
end in 24 hours
22 OTU-SES-TC 749 OTUk Major Threshold-crossing alert Y Y Y

-15M-NE for SES accumulated near
end in 15Min

-15M-FE for SES accumulated far
end in 15Min

-24H-NE for SES accumulated near
end in 24 hours
25 OTU-SES-TC 752 ODUk Major Threshold-crossing alert Y Y Y

-24H-FE for SES accumulated far
end in 24 hours
26 OTU-CE-TC- 103 ODUk Minor Threshold-crossing alert Y Y Y

15M-NE for Corrected Errors
accumulated near end in
15Min
27 OTU-CE-TC- 104 ODUk Minor Threshold-crossing alert Y Y Y

24H-NE for Corrected Errors
accumulated near end in
24 hours
OTN Path Layer - ODUk-PM
1 ODU-AIS 760 ODUk Major ODU2-AIS is specified as Y Y Y

all "1"s in the entire ODU2
signal, excluding the
frame alignment
overhead (FA OH), OTU2
overhead (OTU2 OH) and
ODU2 FTFL


name severity

PT 0 0C 0 4 20 00 10
2 ODU-OCI 761 ODUk Major Open Connection Y Y Y

Indication
ODU2-OCI is specified as a
repeating "0110 0110"
pattern in the entire
ODU2 signal, excluding
the frame alignment
overhead (FA OH) and
OTU2 overhead (OTU2
OH).
ODU-OCI (Open
connection indication)
shall be declared if the
accepted STAT
information is "110".
ODU-OCI shall be cleared
if the accepted STAT
information is not equal
to "110". During signal fail
signal, ODU-OCI shall be
set to false
3 ODU-LCK 762 ODUk Major ODU Locked Y Y Y

ODU2-LCK is specified as a
repeating "0101 0101"
pattern in the entire
ODU2 signal, excluding
the frame alignment
overhead (FA OH) and
OTU2 overhead (OTU2
OH).
ODU-LCK (Locked Defect)

shall be declared if the
accepted STAT
information is "101".
ODU-LCK shall be cleared
if the accepted STAT
information is not equal
to "101". During signal fail
signal, ODU-LCK shall be
set to false.


name severity

PT 0 0C 0 4 20 00 10
4 ODU-TIM 763 ODUk Major Trace identifier mismatch Y Y Y

in ODU
The TTI mismatch process

reports the trace
identifier mismatch defect
(dTIM). The process is
based on the comparison
of expected APIs (i.e.,
SAPI and DAPI) with the
APIs in the incoming
signal. The APIs are part
of the 64 byte TTI as
defined in [ITU-T G.709].
Depending on the
topology, only the SAPI,
only the DAPI or both SAPI
and DAPI are taken into
account for the mismatch
detection.
5 ODU-PLM 764 ODUk Critical Payload Mismatch Y Y Y
The Payload Label

Mismatch (PLM) defect
shall be detected if the
"accepted TSL" code does
not match the "expected
TSL" code. If the
"accepted TSL" is
"equipped non-specific",
the mismatch is not
detected.
In the case of a PLM

condition, the PLM defect
shall be cleared if the
"accepted TSL" code
matches the "expected
SL" code or if the
"accepted TSL" code is
"equipped non-specific".
6 ODU-BDI 765 ODUk Minor ODU Backward defect Y Y Y

indication
dBDI shall be declared if

the BDI bit in the PM
frames. dBDI shall be
cleared if the BDI bit in
the PM overhead field is
"0" for 5 consecutive
frames. During signal fail
signal, dBDI shall be set to
false.


name severity

PT 0 0C 0 4 20 00 10
7 ODU-DEG 766 ODUk Major ODU-Degraded Y Y Y
The ODU-DEG signal

degrade defect is derived
from the BIP8
calculations. A degraded
signal defect (DEG) shall
be detected if the
equivalent BER exceeds a
-x
preset threshold of 10 , x
= 5, 6, 7, 8 or 9. The
degraded signal defect
shall be cleared if the
equivalent BER is better
-(x+1)
than 10 .
8 ODU-CSF 105 ODUk Major A single-bit OPUk client Y Y Y

signal fail to convey the
signal fail status of client
signal
9 OPU-PN11 106 ODUk Major Generic AIS, Indicates Y Y Y

client Port LOS
10 OPU-MSIM 107 ODUk Major Multiplex Structure Y Y Y

Identifier Mismatch
11 ODU-GMP-L 108 ODUk Major ODUk GMP Loss of Y Y Y

OSYNC synchronization alarm
12 ODU-UAT-N 767 ODUk Major ODUk Unavailable time Y Y Y

E near end
13 ODU-UAT-F 768 ODUk Major ODUk Unavailable time Y Y Y

E near end
14 ODU-BBE-T 769 ODUk Minor Threshold-crossing alert Y Y Y

C-15M-NE for BBE accumulated near
end in 15Min

C-15M-FE for BBE accumulated far
end in 15Min

C-24H-NE for BBE accumulated near
end in 24 hours

C-24H-FE for BBE accumulated far
end in 24 hours
18 ODU-ES-TC- 773 ODUk Minor Threshold-crossing alert Y Y Y

15M-NE for ES accumulated near
end in 15Min

15M-FE for ES accumulated far
end in 15Min

24H-NE for ES accumulated near
end in 24 hours


name severity

PT 0 0C 0 4 20 00 10

24H-FE for ES accumulated far
end in 24 hours
22 ODU-SES-TC 777 ODUk Major Threshold-crossing alert Y Y Y

-15M-NE for SES accumulated near
end in 15Min

-15M-FE for SES accumulated far
end in 15Min

-24H-NE for SES accumulated near
end in 24 hours

-24H-FE for SES accumulated far
end in 24 hours
26 ODU-TSE-TC 109 ODUk Minor Test Sequence Errors in Y Y Y

-15M 15 min (from apollo)
27 ODU-TSE-TC 110 ODUk Minor Test Sequence Errors in Y Y Y

-24H 24 hours
OTU Port - STM/OC
1 SPI-LOS 301 SPI Crirical SDH Physical Interface Y Y Y

Loss of Signal
2 RS-LOF (iin 302 RS Critical Regenerator Section Loss Y Y Y

SDH) of Frame
3 RS-TIM (in 304 RS Major Regenerator Section Trace Y Y Y

SDH) Identification(J0)
Mismatch
4 MS-SD (in 617 MS Minor MS Signal Degrade due to Y Y Y

SDH) BER exceeding SD
threshold
5 MS-EXC (in 618 MS Major MS Excessive Bit Error and Y Y Y

SDH) exceeds SF threshold
6 LOF-S (in 156 Section Critical Loss of Frame in section Y Y Y

SONET) layer
7 TIM-S (in 157 Section Major Section Trace Y Y Y

SONET) Identification(J0)
Mismatch
8 SD-L (in 158 Line Minor Line layer Signal Degrade Y Y Y

SONET) due to BER exceeding SD
threshold
9 EXC-L (in 159 Line Major Line layer Excessive Bit Y Y Y

SONET) Error and exceeds SF
threshold


name severity

PT 0 0C 0 4 20 00 10
OTU Port - ETY1G301/ETY1Ge
1 PHY-LOS 673 1GE Port Critical Optical signal loss on Y Y Y

receive side of GbE port
2 LOSYNC 130 1GE Port Major Loss of Synchronization Y Y Y
3 High-BER 416 1GE Port Major Excessive Sync errors are Y Y Y

detected and exceeds the
HI_BER threshold (1E-4)
4 GFP-LFD 131 GFP Major GFP-T Loss of Frame Y Y Y

Delineation
5 GFP-UPIM 132 GFP Major User Payload Identifier Y Y Y

mismatch alarm
6 GFP-PTIM 133 GFP Major Payload Type Identifier Y Y Y

mismatch alarm
7 GFP-EXIM 134 GFP Major Extension header Y Y Y

Mismatch
8 GFP-CSF 137 GFP Major Client signal Fail Far-end Y Y Y

indication
OTU Port - ETY10GOC

receive side of ETY10GOC
port

5 RF 136 10GE Port Major Remote Fault Y Y Y
OTU Port - ETY10G

receive side of ETY10G
port

5 RF 136 10GE Port Major Remote Fault Y Y Y
6 GFP-LFD 131 GFP Major GFP-T Loss of Frame Y Y Y

Delineation
7 GFP-UPIM 132 GFP Major User Payload Identifier Y Y Y

mismatch alarm


name severity

PT 0 0C 0 4 20 00 10
8 GFP-PTIM 133 GFP Major Payload Type Identifier Y Y Y

mismatch alarm
9 GFP-EXIM 134 GFP Major Extension header Y Y Y

Mismatch
10 GFP-CSF 137 GFP Major Client signal Fail Far-end Y Y Y

indication
OTN Port -FC1200/FC800/FC400/FC200/FC100
1 PHY-LOS 673 FC-1200 Critical Optical signal loss on Y Y Y

port
2 LOSYNC 130 FC-1200 Major Loss of Synchronization Y Y Y
3 High-BER 416 FC-1200 Major Excessive Sync errors are Y Y Y

OTN Port - CBR (VIDEO270, HDSI1485, HDSDI3G)
1 PHY-LOS 673 FC-1200 Critical Optical signal loss on Y Y Y

port
TCA for client port layers
1 UAT-NE 501 Major UAS Start Near End Y Y Y
2 PCS-UAT-NE 141 Major PCS UAS Start Near End Y Y Y
3 GFP-UAT-N 142 Major GFP UAS Start Near End Y Y Y

E
4 ESTC-15M- 201 Minor ES in 15 Minutes Y Y Y

NE Threshold Crossing Near
End
5 SESTC-15M- 202 Major SES in 15 Minutes Y Y Y

NE Threshold Crossing Near
End
6 BBETC-15M 203 Minor BBE in 15 Minutes Y Y Y

-NE Threshold Crossing Near
End
7 CV-15M-NE 524 Major CV in 15 Minutes Y Y Y

Threshold Crossing Near
End
8 PCS-ESTC-1 143 Minor ES in 15 Minutes Y Y Y

5M-NE Threshold Crossing Near
End in PCS
9 PCS-SESTC-1 144 Major SES in 15 Minutes Y Y Y

End in PCS
10 PCS-CV-15 145 Major CV in 15 Minutes Y Y Y

M-NE Threshold Crossing Near
End in GFP


name severity

PT 0 0C 0 4 20 00 10
11 GFP-ESTC-1 146 Minor ES in 15 Minutes Y Y Y

End in GFP
12 GFP-SESTC- 147 Major SES in 15 Minutes Y Y Y

End
13 ESTC-24H-N 204 Minor ES in 24 Hours Threshold Y Y Y

E Crossing Near End
14 SESTC-24H- 205 Major SES in 24 Hours Threshold Y Y Y

NE Crossing Near End
15 BBETC-24H- 206 Minor BBE in 24 Hours Threshold Y Y Y

NE Crossing Near End
16 CV-24H-NE 525 Major CV in 24 Hours Threshold Y Y Y

Crossing Near End
17 PCS-ESTC-2 148 Minor ES in 24 Hours Threshold Y Y Y

4H-NE Crossing Near End in PCS
18 PCS-SESTC-2 149 Major SES in 24 Hours Threshold Y Y Y

4H-NE Crossing Near End in PCS
19 GFP-ESTC-2 150 Minor ES in 24 Hours Threshold Y Y Y

4H-NE Crossing Near End in GFP
20 GFP-SESTC- 154 Major SES in 24 Hours Threshold Y Y Y

24H-NE Crossing Near End in GFP
21 PHY-RBBTC- 152 Minor Rx Bad Octets in 15 Y Y Y

15M-NE Minutes Threshold
Crossing Near End
22 PHY-RBFTC- 153 Minor Rx Bad Frames in 15 Y Y Y

Crossing Near End
23 PHY-TBBTC- 154 Minor Tx Bad Octets in 15 Y Y Y

Crossing Near End
24 PHY-TBFTC- 155 Minor Tx Bad Frames in 15 Y Y Y

Crossing Near End
Parent Topic

3 Performance Monitoring
Performance data reflects the network running quality. This section discusses how to monitor the bit errors
for each section, the SDH layers, and the path for evaluating QoS.
The EMS-APT performance functions provide instant monitoring and regular statistics for the error codes of
various SDH and Ethernet section layers and paths. Such data is essential to ensure optimal network
performance.
The following performance-related operations can be performed:

 Viewing Performance Data
 Configuring Performance Attributes
 PM Counters and TCA
 Performing PM Export Configuration
3.1 Performance Data

Performance data can be viewed for different monitored objects, as follows:
 SDH: digital bit stream errors, and the number of transferring packets and error packages.
 Port: Ethernet MAC layer statistics, including the number of received frames of varying length and
type, and their error packets.
 EoS: number of sent packets and error packages.
 DCC: network traffic errors, and the number of monitored packets and error packages.
 L2 Extend: extend performance of the ports of Layer 2 cards.
 PTP TMU: performance counters of PTP TMU objects.
 PTP Port: performance counters of PTP ports.
 OTN: performance counters of OTN.
 MCC NI: performance counters of MCC network interface.
 CES Extend: extend performance of MSM cards.
 Current Rate: current rate of CES port.
In the MSM cards, when the work mode is set as Standalone, then Performance and Performance Settings
of GE-ETY ports can be supported. The difference with L2 ETY ports is that CES Extend performance is
instead of L2 extend performance.
The Layer 2 cards support Ethernet PM counters for the objects: Switch, VSI, Policer, CoS, Tunnel, MA, Local
MEP, Remote MEP, CFM PM Switch, CFM DM Session, CFM LM Session, CES Interface, Queue Block, BD LSP
and Management VLAN.

EMS-APT® Performance Management Guide Performance Monitoring
The following figure shows the PB Ethernet connection view.

Figure 3-1: PB Ethernet connection view
The following figure shows the MPLS Ethernet connection view.

Figure 3-2: MPLS Ethernet connection view
The VSI performs the learning and forwarding actions for specific L2 VPN in the local PE element using its
virtual Forwarding Information Base (vFIB). Every VSI connects the user ports from one side to the remote
VSIs on the other PEs via MPLS tunnels.

The following is a zoomed-in illustration of objects within PB PE.

Figure 3-3: Zoomed-in illustration of objects within PB PE
The following is a zoomed-in illustration of objects within MPLS PE.

Figure 3-4: Zoomed-in illustration of objects within MPLS PE
In the figure, the packet received from a UNI port will be counted by the counter of port: If the packet
belongs to the macro flow which has a policer, the packet will be counted by the policer; if the packet is a
broadcast packet and belongs to a VSI of MPtMP, it will be counted by the BSC policer of that VSI. The
packet will be counted by the tunnel if it is forwarded by a tunnel. The MSTP topology change and FIB
utilization will be counted on the object of the switch.
Performance data is divided into the following monitoring periods:

 15-minute: Equipment performance data is measured in 15-minute intervals. At the end of each 15
minutes, the value of the 15-minute performance data counter is reported to the EMS-APT. At the
same time, the performance data counter is reset and another round of 15-minute performance
statistics starts to accumulate.
 24-hour: Equipment performance data is measured in 24-hour intervals. At the end of each 24 hours,
the value of the 24-hour performance data counter is reported to the EMS-APT. At the same time, the
counter is reset and another round of 24-hour performance statistics starts to accumulate.

 Instant: current values of the 15-minute or 24-hour performance data counters.

Through the analysis of historical performance data in the EMS-APT, the errors at each SDH section/layer
can conveniently be checked. If there are errors in the RS, MS, and VC-4, the typical cause is poor aggregate
(card) performance.
Possible causes are:

 Low laser power.
 High laser power.
 Excessive input jitter caused by a poor contact on the optical interface, or a relay less distance of the
fiber that is too long.
Performance data can be used as an analytical tool, as follows:
 By examining the 15-minute performance data for a given day, you can analyze the equipment
performance for that day.
 By examining the 24-hour performance for a month, you can analyze the equipment running status
for that month.
 By examining the 24-hour performance for a year or several years, you can analyze the long-term
running of the equipment.
The EMS-APT provides a performance curve diagram, which shows equipment performance changes during
a specific period visually. This mechanism provides a convenient way to analyze the communication link
quality over time.
Parent Topic
3.2 Viewing Performance Data

The EMS-APT enables you to view the current, historical, and recent performance of a transmission object
for 15-minute or 24-hour time intervals.
The performance data is divided into the following classes:
 SDH
 Port
 EoS
 DCC
 L2 Extend
 PTP TMU
 PTP Port
 MCC NI
 CES Extend
 Current Rate (only available when there are activated CES services)

When you select a class, the related performance data is displayed. The default is SDH performance data.
For the ETY ports of the MSPP L2 cards, you can view the current/recent/historical performance data as
port utilization.
Parent Topic
3.2.1 Viewing Current Performance

Current performance data refers to the present value of the current 15-minute or 24-hour performance
data counter.
After you set the refresh interval and click Start Refresh, current performance data is retrieved based on
the specified monitoring cycle interval (15-minute or 24-hour).
Current performance data is divided into the following classes:
 SDH
 Port
 EoS
 DCC
 L2 Extend
 PTP TMU
 PTP Port
 MCC NI
 CES Extend
When you select a class, the related current performance data is displayed.

To view current performance data:

1. In the NE Shelf View window, in the left object tree, select the NE, or a card, or a port. In the
Performance working mode Current tab, you can view the current performance data.
Before performing operations in this window, select the relevant button in the Type and Display
fields.
2. To retrieve the current performance data from the NE equipment, on the toolbar click .
3. To refresh data:
a. Select the Refresh data dynamically checkbox and set the Refresh Interval.
b. To dynamically observe any performance data changes, click Start Refresh. Data is refreshed, based
on the Refresh Interval you specify.
c. To cancel the refresh operation, click Stop Refresh.

4. To view the information in a list, click the Sheet View icon .
5. To view the information in a chart, click the Chart View icon . In the Filter area, select the chart
parameters as required and click Create Chart.

6. To view the information as port utilization for an ETY port of a Layer2 card, click the Port Utilization
icon .

In the Filter area, you can select Rate(including In Rate and Out Rate), or PPS (including In PPS and
Out PPS) in the same chart. For In Rate and Out Rate, the unit can be set as Kbps or Mbps (default is
Mbps).Then click the Create Chart button.
To reset the statistics, click the Clear button. All the statistics will be cleared and re-calculated based
on the data that begins from the last click time.
Parent Topic
3.2.1.1 Viewing Switch PM Data

You can view the Switch PM data for the following classes:
 Switch
 VSI
 Policer
 CoS
 Tunnel
 MA
 Local MEP
 Remote MEP
 CFM PM Switch

 CFM DM Session
 CFM LM Session
 CES Interface
 Queue Block
 BD LSP
 Management VLAN
To view the PM data:

1. In the NE Shelf View window, in the left object tree, select the Switch module, and then in the
Performance working mode Current tab, select the relevant Type in the Display dropdown list. The
current performance data of the corresponding object is shown.
2. To retrieve the current performance data from the NE equipment, on the toolbar, click .
The CFM PM counters and TCA are described in the table CFM PM Counters and TCA.
Parent Topic
3.2.1 Viewing Current Performance

3.2.2 Viewing Performance History

The EMS History window enables you to view the historical performance parameters of a network.
Historical performance data can be obtained for various PM counters.
Equipment performance data is stored in various performance counters, which report the data as historical
performance when the count cycle expires. The EMS-APT saves reported historical performance to a DB.
Historical performance data is divided into the following classes:

 SDH
 Port
 EoS
 DCC
 L2 Extend
 PTP TMU
 PTP Port
 MCC NI
 CES Extend
When you select a class, the related historical performance data is displayed.

To view historical performance data:

1. In the NE Shelf View window, in the left object tree, select the NE, or a card, or a port. Then in the
Performance working mode, select the EMS History tab.
2. In the Display field select a performance class.

3. To expand the filter options, click + in the Filter field.

4. To view the information in a chart, click the Chart View icon . In the Filter area, select the chart
parameters as required and click the Create Chart button.

5. To view the information as port utilization for an ETY port of a Layer2 card, click the Port Utilization
icon .

In the Filter area, in the Chart Parameters field, you can select Rate(including In Rate and Out Rate),
or PPS (including In PPS and Out PPS) in the same chart. For In Rate and Out Rate, the unit can be set
as Kbps or Mbps (default is Mbps).Then click .
To reset the statistics, click the Clear button. All the statistics will be cleared and re-calculated based
on the data that begins from the last click time.
6. To display historical performance data in the list, set the data counter and period definitions in the
relevant field and click .
7. To retrieve the historical performance parameters from the NE equipment, click .
8. To export the NE list as an XML file, on the toolbar click .
9. To export the NE list as a CSV file, on the toolbar click .
10. To delete the selected data, on the toolbar click . Click to select all and click to deselect
all.
Parent Topic

3.2.3 Viewing Recent Performance

For all functional block performance objects, the NE provides a recent performance register which is a
first-in first-out (FIFO) queue used to save the latest performance data (meaning, historical performance
data) of the NE. There are N (N=16) recent 15-minute registers and M (M=6) recent 24-hour registers. (For
Data cards, N=16, M=1.) When the data collection time of the current register reaches 15 minutes or 24
hours, if the data is valid, it is dumped to the recent registers. If the recent registers overflow, the earliest
recent data register is overwritten. The EMS-APT can acquire values stored in the recent 15-minute and
24-hour registers.
Recent performance data is divided into the following classes:

 SDH
 Port
 EoS
 DCC
 L2 Extend
 PTP TMU
 PTP Port
 MCC NI
 CES Extend
When you select a class, the related recent performance data is displayed. The default is SDH performance
data.

To view recent performance data:

1. In the NE Shelf View window, in the left object tree, select the NE, or a card, or a port. In the
Performance working mode, select the NE History tab.
2. Select the relevant Display button.

3. To obtain and display the performance parameter values stored in the recent performance registers
of the NE equipment, click .
Parent Topic
3.3 Configuring Performance Settings

The EMS-APT enables you to configure the performance attributes, including setting performance
thresholds, setting PM switches, and resetting performance counters.
Parent Topic

3.3.1 Opening Archived Performance Files
To open archived performance files:

1. In the NE Shelf View window, in the left object tree, select the NE, and then in the Performance
working mode, select the Archived Files tab. The following window opens.
2. To open an archived file, on the toolbar click . The following window opens.

3. Select the file in your local disk and click Open. The following window opens.
Parent Topic
3.3.2 Setting Performance Threshold

A performance threshold is the allowable upper limit for performance data when a system works normally.
When a performance indicator crosses a threshold, the system generates a corresponding event report.
You can obtain and set the performance threshold parameters of a network.
The performance type can be specified as either a 15-minute or 24-hour period.

To set TDM TCA thresholds:

1. In the NE Shelf View window, in the left object tree, select the NE. In the Performance and
Performance Settings working mode area, select the TDM TCA Threshold tab.
2. To display the performance threshold value obtained from an NE, click .
3. To copy the performance threshold value to other NEs, click .

4. To send performance threshold values to the NE and save them to the DB, click Apply.

5. To set the SD/EXC threshold, select the SD/EXC tab.

To set Ethernet TCA thresholds (for ETY or EoS ports):

1. In the NE Shelf View window, in the left object tree, under a Layer 2 card, select the ETY or EoS port
object. In the working mode area, select Performance, Performance Settings, and then select the
Threshold Setting tab.
2. To display the performance threshold value obtained from an NE for viewing, click .

3. To set the performance thresholds for EoS, in the NE Shelf View window, in the left object tree, under
a Layer 2 card, select the EoS object. In the working mode area, select Performance, Performance
Settings, and then the Threshold Setting tab.
4. To display the performance threshold value obtained from an NE for viewing, click .

5. To set the performance thresholds for switch, in the NE Shelf View window, in the left object tree,
under a Layer 2 card, select the Switch object. In the working mode area, select Performance,
Performance Settings, and then the Threshold Setting tab.
6. In the Display field, select the relevant button, and to display the performance threshold value
obtained from an NE for viewing, click .
Parent Topic
3.3.2.1 Setting Switch Performance Threshold

You can set the Switch performance threshold for the following classes:
 VSI
 Tunnel
 MA
 CFM DM Session
 CES Interface
 Queue Block
 BD LSP
 Management VLAN

To set the performance threshold for the switch:

1. In the NE Shelf View window, in the left object tree, select the Switch module. In the Performance
working mode, select the Threshold Setting tab.

2. In the Display area, select the corresponding button (for example, the Tunnel settings below).

3. To obtain object data from the NE equipment, select the corresponding checkboxes in the Filter area,
and click .
4. Modify object parameters as required in the corresponding area, and to send settings to a piece of
equipment and save them to the EMS-APT DB, click Apply.
Parent Topic

3.3.2.2 Setting OTN TCA Threshold
To set OTN TCA thresholds:

1. In the NPT NE Shelf View window, in the left object tree, select the NE. In the Performance and
Performance Settings working mode area, select the OTN TCA Threshold tab.

Parent Topic
3.3.2.3 Setting SONET TCA Threshold

You can set the SONET TCA threshold for an NE with SONET framing mode.

To set SONET TCA thresholds:

1. In the SONET NE Shelf View window, in the left object tree, select the NE. In the Performance and
Performance Settings working mode area, select the SONET TCA Threshold tab.

Parent Topic
3.3.3 Setting DCC Performance

You can set DCC performance for BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020 NEs, including:
 Setting DCC TCA thresholds
 Setting DCC PM and reporting
 Viewing DCC current/recent PM
 Resetting DCC PM counters

To set DCC TCA thresholds:

1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020 NE Shelf View window, in the left object
tree, select the NE. In the Performance and Performance Settings working mode area, select the DCC
TCA Threshold tab.

3. Set the parameters as required, and click Apply to save them to the DB.

To set DCC PM and reporting:

tree, select the NE. In the Performance and Performance Settings working mode area, select the
Monitoring and Reporting tab.

Or, in the left object tree, select the MCP/MXC object, and in the Performance and Performance
Settings working mode area, select the Monitoring and Reporting tab.

Or, in the object tree, select a DCC object, and then in the Performance and Performance Settings
working mode area, select the Monitoring and Reporting tab.
2. Set the Monitor Active and Auto-Report attributes as required by selecting the corresponding
checkboxes.
3. To batch edit the monitoring and reporting attribute, on the toolbar, click .
4. Click Apply to save your settings.

To view DCC current/recent PM:

1. To view DCC current PM, in the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020 NE Shelf View
window, in the left object tree, select a DCC object. In the Performance working mode area, select
the Current tab.

2. To view DCC recent PM, in the NE Shelf View window, in the left object tree, select a DCC object. In
the Performance working mode area, select the NE History tab.
3. To display the performance data obtained from an NE, click .

To reset DCC PM counters:

tree, select a DCC object. From the menu, select Performance and then Reset PM Counters.

Or, in the DCC Current PM window, on the toolbar, click the Reset PM Counters button .
2. A Confirmation window opens, prompting you to select 15-minute, 24 hour or both for the PM
counters.
3. Select the type as required and click Yes to confirm.
Parent Topic

3.3.4 Setting PM
This operation enables you to monitor the performance of an NE by setting a main switch for NE PM and
setting the start and end times for the monitoring process. The performance object monitoring switch
determines whether to monitor the performance of a specific functional block in an NE. The autoreport
switch determines whether to allow historical performance data for a specific functional block in an NE to
be automatically reported to the EMS-APT.
The following terms relate to the Performance Monitor Switch operation:

 Main switch for NE PM: Determines whether to monitor the performance of an NE. When this switch
is disabled, the collection of statistics and the monitoring of all performance objects in an NE are
terminated. In this case, the EMS-APT cannot obtain any current performance counters and the NE
does not automatically report any historical performance data. When enabled, the switch monitors
the performance of an NE between the start and end times.
 Performance object monitoring switch: Determines whether to monitor the performance of a specific
functional block in an NE. If this switch is disabled, it terminates the collection of statistics and the
monitoring of all performance objects within this functional block.
 Autoreport switch: Determines whether to report to the EMS-APT automatically historical
performance data for a specific functional block within an NE. If this switch is enabled, historical
performance data of a functional block in an NE is automatically reported to the EMS-APT. When
disabled, performance statistics collection and monitoring are implemented within an NE, but there is
no reporting. Therefore, current performance counter values can still be obtained.
 Specific SDH and Ethernet functional block.

To set PM:
1. In the NE Shelf View window, in the left object tree, select the NE, and in the Performance and
Performance Settings working mode, select the Monitoring and Reporting tab.
2. To obtain object data from the NE equipment, click .
3. To batch edit the TTI Detection attribute, on the toolbar, click .

4. Modify object parameters as required.

6. To set monitoring switch parameters for an NE, select the Schedule tab.
Parent Topic
3.3.4.1 Setting Switch Performance

You can set the PM and reporting for the following classes:
 Switch
 VSI
 CoS
 Tunnel
 MA
 Local MEP
 Remote MEP
 CES Interface
 Queue Block
 BD LSP
 Management VLAN

To set PM for the switch module:

1. In the NE Shelf View window, in the left object tree, select the Switch module. In the Performance
and Performance Settings working mode, select the Monitoring and Reporting tab.

2. To obtain object data from the NE equipment, in the Display area, select the corresponding button,
and click . The following window opens, showing, for example, the VSI settings.

3. Modify object parameters as required by select the checkboxes in Monitor Active and Auto-Report.
Parent Topic
3.3.4 Setting PM

3.3.5 Managing Threshold Settings
To manage threshold settings:

1. In an NE Shelf View window, in the left object tree, select an Ethernet port. In the Performance
working mode, select the Threshold Setting tab.
2. Set the parameters as needed, and click Apply to save your changes.
3. To retrieve the parameters, on the toolbar, click .
4. To copy the settings to other ports, on the toolbar, click the Propagate icon .
Parent Topic
3.3.6 Viewing Transceiver Alarms and Warning Threshold

You can view transceiver alarms and warning thresholds for an optical port.

To view transceiver alarms and warning thresholds:

1. In an NE Shelf View window, in the left object tree, select an optical port. In the Performance working
mode, select the Transceiver alarm and warning thresholds tab.
Parent Topic
3.3.7 Viewing Invalid MPLS-TP OAM Statistics

You can view the invalid MPLS Transport Profile (MPLS-TP) OAM statistics for the switch module.

To view invalid MPLS-TP OAM statistics:

1. In an NE Shelf View window, in the left object tree, select the Switch Object. In the Performance
working mode, select the Invalid MPLS-TP OAM Statistics tab.
3. To clear the data, on the toolbar, click .
Parent Topic
3.3.8 Viewing TDM/Packet Engine Utilization

You can view the TDM and Packet engine utilization from EMS-APT via graphical indicator.
Packet Engine Utilization
For packet engine utilization, there are two pointers supported on packet engine dash board:
 One is for "Occupied Network Processor (NP) table or memory resource /maximum NP table or
memory resource on devices", which does not move without change configuration.

 NP shall detect 5 table and memory resources utilization which related to VSI, tunnel /Queues,
C-VLAN groups etc.
 PB Classifications Utilization
 MPLS Classifications Utilization
 PB VSI Interfaces Utilization
 MPLS VSI Interfaces Utilization
 Ingress Tunnel Label Mapping Utilization
 EMS only shows the biggest value with one pointer on the dash board.
 You can also select to view all the 5 table/memory resource utilization.
 The other is for "current real throughput/ maximum switch capacity", which is always moving.
Packet Engine Utilization is supported for the following PEs:

 Central PE of NPT-1200
TDM Engine Utilization
TDM Engine Utilization reflects the utilization of the SDH cross-connect matrix.
TDM engine utilization definition:
 The utilization of NE SDH XC matrix, that is the ratio of configured total XC bandwidth/physical matrix
capacity. It is a read-only attribute, always got from NE/MCP, and calculated by MCP according to
system matrix card capacity.
 Deactivated XCs are not included for TDM engine utilization – in case XC is cleared (deactivate all), the
utilization is 0.
 Add/drop VC-4 server XCs are not included for TDM engine utilization.
This attribute is available for TDM or hybrid configuration. Pure packet configuration does not have such
attribute. Following are the NEs without TDM engine utilization:
 NPT-1200 system with CPS100/CPS200
 NPT-1021
 NPT-1010

To view TDM/Packet engine utilization:

1. In the BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window, in the left object tree,
select the NE. Then in the Performance working mode, select the TDM/Packet Utilization tab.
2. To refresh the information manually, click .
3. To view details of NP table or memory resource, on the toolbar, click .

4. To refresh the information automatically:

a. Select the Refresh Data Dynamically checkbox.
b. Enter the refresh interval in the Refresh Interval field.
c. To refresh the TDM/Packet Engine Utilization, click Start Refresh.
Parent Topic
3.3.9 Viewing/Exporting Laser Performance
To view/export laser performance:

1. In an NE Shelf View window, in the left object tree, select an optical port. In the Performance working
mode, select the Laser Performance tab.

2. To open the laser performance view list, in the main topology view, select the NEs whose laser
performance you want to view, and on the main menu, select working mode Performance and then
the Laser Performance tab. The Laser Current Performance window opens.
3. In the Filter area, select the port type by selecting the corresponding checkboxes.
4. To retrieve the parameters for viewing, on the toolbar, click .

5. To export the laser performance information as a CSV file:
a. On the toolbar, click . The following window opens.
6. To exit the Laser Current Performance window, on the toolbar, click .
Parent Topic

3.3.10 Resetting Performance Counters

Use this operation to manually reset the near-term or current performance registers on an NE or object. Do
not use this operation until system debugging is in service or the faulty equipment has been restored.
To reset performance counters:

1. In the NE Shelf View window, in the left object tree, select the NE or card whose performance
counters you want to reset. On the menu, select Performance and then PM Reset Counters. The
following confirmation message is displayed.
2. Select a type of the PM counters you want to reset and click Yes to confirm.
Parent Topic
3.4 PM Counters and TCA

This section describes the performance counters and TCA in EMS-APT. All the counters have the same
granularity (15-min/24-hour).
For the OTN PM counters and TCA, see OTN PM Counters and TCA.
Parent Topic

3.4.1 Ethernet and Layer2 PM Counters and TCA

Table 3-1: Ethernet and Layer2 PM counters and TCA
EMS name TCA Description

Port Level
Rx Octets N Received total number of bytes for all good packets (unicast +
multicast + broadcast).
Rx Pkts N Received total number of good packets (unicast + multicast +
broadcast).
Rx Broadcast Pkts Y Received total number of good broadcast packets.
Rx Multicast Pkts Y Received total number of good multicast packets.
Tx Octets N Transmitted total number of bytes for all good packets (unicast +
Tx Pkts N Transmitted total number of good packets (unicast + multicast +
broadcast).
Rx Error Pkts Y Received total number of dropped packets, including all bad packets
and dropped good packets.
Rx Pkts 64 N Received total number of good packets of size 64 bytes.
Rx Pkts 65-127 N Received total number of good packets of size 65-127 bytes.
Rx Pkts 1024-MTU N Received total number of good packets of size 1024 to MTU bytes.
Rx CRC Align Error Pkts N Received total number of bad packets which meet all the following
conditions:
 Packet length is valid (between 64 and MTU).
 Packet has invalid CRC.
 Collision event has not been detected.
Rx Undersize Pkts N Received total number of bad packets which meet all the following
conditions:
 Packet length is less than 64 bytes.
 Packet has valid CRC.
Rx Oversize Pkts N Received total number of bad packets which meet all the following
conditions:
 Packet length is larger than MTU.
 Packet has valid CRC.
Rx Pause Pkts N Received total number of Pause frames.
Collision Errors N Total number of collision events has been detected.


ACL Discard Pkts N Packets discarded due to ACL rule.
VLAN filtering Discard N Per port counter for RX good packets discarded due to VLAN filtering
packets should be added for Ezchip NP-based cards.
Ingress classification N Per port counter for packets discarded by NP due to ingress
Discard packets classification for EzChip NP-based cards.
Mac Filtering Discard Pkts N Per Port counter for packets discarded due to mac filterint when mac
filtering enabled.
TC Ingress Process PTP N Number of PTP packets modified in Ingress
Pkts
TC Egress Process PTP N Number of PTP packets modified in Engress
Pkts
Port Utilization
IN Maximum Rate N Maximum rate one of all polling periods since operation starts to
(Kbps/Mbps) current on RX direction.
IN Average Rate N Average rate since operation starts to current on RX direction.
(Kbps/Mbps)
IN Current Rate N Current rate in this polling period on RX direction.
(Kbps/Mbps)
IN Maximum PPS N Maximum PPS (Packets per Second) one of all polling periods since
operation starts to current on RX direction.
IN Average PPS N Average PPS since operation starts to current on RX direction.
IN Current PPS N Current PPS in this polling period on RX direction.
IN Maximum Utilization N Maximum utilization one of all polling periods since operation starts to
(%) current on RX direction.
IN Average Utilization (%) N Average utilization since operation starts to current on RX direction.
IN Current Utilization (%) N Current utilization in this polling period on RX direction.
OUT Maximum Rate N Maximum rate one of all polling periods since operation starts to
(Kbps/Mbps) current on TX direction.
OUT Average Rate N Average rate since operation start to current on TX direction.
(Kbps/Mbps)
OUT Current Rate N Current rate in this polling period on TX direction.
(Kbps/Mbps)
OUT Maximum PPS N Maximum PPS one of all polling periods since operation starts to
current on TX direction.
OUT Average PPS N Average PPS since operation starts to current on TX direction.
OUT Current PPS N Current PPS in this polling period on TX direction.
OUT Maximum Utilization N Maximum utilization one of all polling periods since operation starts to
(%) current on TX direction.
OUT Average Utilization N Average utilization since operation starts to current on TX direction.
(%)


OUT Current Utilization N Current utilization in this polling period on TX direction.
(%)
Link Down Seconds (s) N Link down time since operation starts time to current.
Switch Level
MSTP Topology Changes N Total number of topology changes detected by the switch.
FIB Full Seconds Counter N Number of seconds in which FIBActualSize was at its maximum value
(32K).
FIB Utilization N FIB current size/32K.
FIB Quota Utilization N FIB current size/total provisioned size.
ForwardedPackets N Forwarded Packets by the NPU
Forwarding Average Bit N The average bit rate of NPU forwarding in 15min or 24h.
Rate
Forwarding Min Bit Rate N The minimum bit rate of NPU forwarding in 15min or 24h, this bit rate
is calculated per 10 seconds of interval.
Forwarding Max Bit Rate N The maximum bit rate of NPU forwarding in 15min or 24h, this bit rate
is calculated per 10 seconds of interval.
Forwarding Average Pkt N The average packet rate of NPU forwarding in 15min or 24h.
Rate
Forwarding Min Pkt Rate N The minimum packet rate of NPU forwarding in 15min or 24h, this
packet rate is calculated per 10 seconds of interval.
Forwarding Max Pkt Rate N The maximum packet rate of NPU forwarding in 15min or 24h, this
packet rate is calculated per 10 seconds of interval.
Drop Pkts in Stage1 N Dropped Packets by the NPU engine #1
TC Good Process PTP Pkts N Number of PTP packets that "Correction Field Modified Successfully"
TC Bad Process PTP Pkts N Number of PTP packets that "Correction Field Modified
Unsuccessfully"
SOAM PM Frames N Total number of SOAM PM frames discarded by NPU for various
Discarded by NPU reasons
Invalid DMM Discarded N Total number of discarded invalid DMM frames
Invalid DMR Discarded N Total number of discarded invalid DMR frames
Invalid SLM Discarded N Total number of discarded invalid SLM frames
Invalid SLR Discarded N Total number of discarded invalid SLR frames
PM/Switch
SOAM PM Frames N Total number of SOAM PM frames discarded by NPU for various
Discarded by NPU reasons.
Invalid DMM Discarded N Total number of discarded invalid DMM frames.
Invalid DMR Discarded N Total number of discarded invalid DMR frames


Invalid SLM Discarded N Total number of discarded invalid SLM frames
Invalid SLR Discarded N Total number of discarded invalid SLR frames
Policer Level
Act Pkts N Number of packets handled by the policer.
Act Octets N Number of octets handled by the policer.
Green Pkts N Number of green packets for this policer.
Yellow Pkts N Number of yellow packets for this policer.
Drop Pkts N Number of red packets for this policer.
Green Octets N Number of green bytes for this policer.
Yellow Octets N Number of yellow bytes for this policer.
Drop Octets N Number of red bytes for this policer.
Conforming Octet Rate N Average bit rate of conforming (green + yellow) policed traffic.
Policer Utilization N Average bit rate of conforming (green + yellow) policed traffic.
Non Conforming Octets N Average bit rate of conforming (green + yellow) policed traffic.
VSI Level
BSC Conforming Octets N Number of multicast, broadcast, and unknown destination unicast
bytes received by all ports for this VPN.
BSC Dropped Octets Y Number of multicast, broadcast, and unknown destination unicast
bytes dropped by BSC policer of this VPN.
BSC Dropped Pkts N Number of multicast, broadcast, and unknown destination unicast
packets dropped by BSC policer of this VPN.
BSC Average Rate N Average bit rate of conforming octets accepted by BSC policer.
BSC Utilization N Utilization of the permitted capacity of BSC policer (CIR).
Rx IGMP Reported Pkts N Number of IGMP reported packets received from all access ports of
leaf VSI.
MAC Move (events) Y Detection of duplicate MAC, number of MAC move events.
Quota Drop Packets Y Number of packets discarded due to FIB over quota.
Queue Level (per cos per tunne, Or per cos per QB, or per cos per port)
Tx Octets N Number of bytes transmitted for this tunnel/CoS (PB).
Tx Pkts N Number of packets transmitted for this tunnel/CoS (PB).
Tx Wred Octets Y Number of octets discarded by WRED on this tunnel/CoS (PB) out.
Tx Wred Pkts N Number of packets discarded by WRED on this tunnel/CoS (PB) out.
Tx Average Rate N An average bit rate of octets transmitted on this flow per CoS per
tunnel.
Tx Utilization N Tx Average Rate/Tunnel Bandwidth
Tunnel Level
Rx Octets N Number of bytes received for this tunnel/CoS (PB).


Rx Pkts N Number of packets received for this Tunnel / CoS(PB)
Rx Average Rate Y Average octets rate of packets received for this tunnel
TunnelDownSec N Number of seconds during which the operational state of this XC was
down. Relevant only when OamCvState = Enabled.
TunnelDownSecRatioPpm N Ratio of time during which the operational state of this XC was down.
In-band MCC
Rx Octets N Number of bytes received for this in-band MCC NI
Rx Pkts N Number of packets received for this in-band MCC NI
Rx Dropped Octets N Number of received bytes dropped for this NI
Rx Dropped Pkts N Number of received packets dropped for this NI
Tx Octets N Transmitted total number of bytes for this in-band MCC NI
Tx Pkts N Transmitted total number of good packets for this in-band MCC NI
Tx Dropped Octets N Number of bytes dropped for this NI before transmitting, due to rate
limit.
Tx Dropped Pkts N Number of packets dropped for this NI before transmitting, due to
rate limit.
GRE enabled MoE
Rx TL Error Pkts N Received and dropped total number of packets due to Total Length
mismatch
Rx IP address Error Pkts N Received and dropped total number of packets due to IP address
mismatch
Traffic Management Level (per CoS per port)
Tx Octets N Number of bytes transmitted on this flow per CoS per port.
Tx Pkts N Number of packets transmitted on this flow per CoS per port.
Tx Wred Octets N Number of octets discarded by WRED on this FlowOut per CoS per
port.
Tx Wred Pkts N Number of packets discarded by WRED on this FlowOut per CoS per
port.
Tx Average Rate N An average bit rate of octets transmitted on this flow per CoS per port.
E1 Interface
E1ES Y ESs. If errors occur within a certain second, this second is called an
errored second.
E1SES Y SESs. If there are errors in 30% of the frames, the errors exceed the
threshold, or the signal fails within a certain second, this second is
called a severely errored second. ESs are not counted when SESs
occur.
E1BBE Y Background block errors. If there are errors in a frame of data, this
frame is counted as a block error. The background block error is the
block error with the number of SESs deducted from the counting
interval.


E1UAS Y Unavailable seconds. When an SES lasts for 10 seconds, it becomes a
UAS. When there are no SESs within 10 seconds, it is no longer
counted as a UAS. The UAS is not calculated in SES calculations.
E1FEES Y Far-end ESs.
E1FESES Y Far-end SESs.
E1FEBBE Y Far-end background block errors.
E1FEUAS Y Far-end unavailable seconds.
3.4.2 EoS PM Counters and TCA

Table 3-2: EoS/GFP PM counters and TCA
Counter names TCA Description

Rx Octets N Received total number of bytes for all good packets (unicast +
Rx Pkts N Received total number of good packets (unicast + multicast +
broadcast).
Tx Octets N Transmitted total number of bytes for all good packets (unicast +
Tx Pkts N Transmitted total number of good packets (unicast + multicast +
broadcast).
Rx Error Pkts Y Received total number of dropped packets, including all bad packets
and dropped good packets.
Rx Drop Pkts N Received total number of dropped good packets.
Rx FCS Error Pkts N Received total number of packets with FCS error.
Rx GFP header Error Pkts N Received total number of packets with GFP header error.
3.4.3 CFM PM Counters and TCA

Table 3-3: CFM PM counters and TCA
Counter name TCA Description

MA Level
MA Down Seconds N Number of seconds during which the operational state of MEG was
down.
MA Down Seconds PPM N Ratio of time during which the operational state of MEG was down.
Local MEP Level per MA
CCM Frames Tx N Total number of transmitted CCM frames.
CCM Frames Rx N Total number of valid received CCM frames.


LBM Frames Tx N Total number of transmitted LBM frames.
LBM Frames Rx N Total number of valid received LBM frames.
LBR Frames Tx N Total number of transmitted LBR frames.
LBR Frames Rx N Total number of valid received LBR frames.
LTM Frames Tx N Total number of transmitted LTM frames.
LTM Frames Rx N Total number of valid received LTM frames.
LTR Frames Tx N Total number of transmitted LTR frames.
LTR Frames Rx N Total number of valid received LTR frames.
Remote MEP
Remote MEP Down N Number of seconds during which the operational state of remote MEP
Seconds was down.
Remote MEP Down N Ratio of time during which the operational state of remote MEP was
Seconds PPM down.
DM/Remote MEP
DMM Frames N Number of transmitted DMM frames (i.e., number of initiated
Transmitted measurements).
DMR Frames Received N Number of received DMR frames (i.e., number of completed
measurements).
Not Compliant FD Y Number of FD measurements which fell above the threshold.
Measurements
Not Compliant FDV Y Number of FDV measurements in forward direction which fell above
Measurements (forward the threshold.
direction)
Not Compliant FDV Y Number of FDV measurements in backward direction which fell above
Measurements (backward the threshold.
direction)
Average FD N Average FD (used) during the interval.
Maximum FD N Maximum FD (used) during the interval.
Minmum FD N Minmum FD (used) during the interval.
Average FDV (forward N Average FDV (used) during the interval in forward direction.
direction)
Average FDV (backward N Average FDV (backward direction)
direction)
Minimum FDV (forward N Minimum FDV(usec) during the interval in forward direction
direction)
Maximum FDV (forward N Maximum FDV(usec) during the interval in forward direction
direction)
Minimum FDV (backward N Minimum FDV(usec) during the interval in backward direction
direction)


Maximum FDV (backward N Maximum FDV(usec) during the interval in backward direction
direction)
SLM session Level per Remote MEP per MA (LM/SLM session)
SLM Frames Transmitted N Number of transmitted SLM frames (i.e. number of initiated
measurements)
SLR Frames Received N Number of received SLR frames (i.e. number of completed
measurements)
Last Far End FLR N Last Far End FLR for the remote MEP
Min Far End FLR N The minimum Far End FLR for the remote MEP during this
Measurement Interval.
Max Far End FLR N The maximum Far End FLR for the remote MEP during this
Avg Far End FLR N The average Far End FLR for the remote MEP during this Measurement
Interval.
Last Near End FLR N Last Near End FLR for the remote MEP
Min Near End FLR N The minimum Near End FLR for the remote MEP during this
Max Near End FLR N The Maximum Near End FLR for the remote MEP during this
Avg Near End FLR N The average Near End FLR for the remote MEP during this
Far End SES N Number of Far End Severely Errored Windows (windows with FLR >
MA_UNAVAIL_THRESH)
Near End SES N Number of Near End Severely Errored Windows (Wondows with FLR >
MA_UNAVAIL_THRESH)
Far End UAS N Number of seconds evaluated as unavailable in the forward direction.
Near End UAS N Number of seconds evaluated as available in the backward direction.
3.4.4 CES Port PM Counters and TCA

Table 3-4: CES port PM counters and TCA

STM-1/OC3 Port or E1/DS1 Port (For both E1-T1 cards and STM-1/OC3 cards)
PortDownSeconds N Total time in seconds when Port is down.
AdminDownSeconds N Total time in seconds when Port Admin state is down.
E1-PPI
E1CV Y Coding Violations


E1ES_PPI Y Errored seconds. A count of seconds during which one or more of the
following has occurred: CVs, LOSs.
E1SES_PPI Y Severely errored seconds. If there are errors in 30% of the frames, the
errors exceed the threshold, or the signal fails within a certain second,
this second is called a SES. ESs are not counted when SESs occur.
E1LOSS-PPI N A count of 1-sec intervals containing one or more LOS defects.
DS1-LINE
DS1ES-L Y Errored seconds. a count of seconds during which one or more of the
following has occurred: BPVs, EXZs, and LOSs.
DS1SES-L Y Severely errored seconds. If there are errors in 30% of the frames, the
errors exceed the threshold, or the signal fails within a certain second,
this second is called a severely errored second. Errored seconds (ESs)
are not counted when severely errored seconds occur.
DS1CV-L Y Coding Violations. The Coding Violations is the block error with the
number of severely errored seconds deducted from the counting
interval.
DS1FEES-L Y Far-end errored seconds.
DS1LOSS-L N A count of 1-second intervals containing one or more LOS defects.
Table 3-5: ES service PM counters and TCA

CES Interface
AdminDownSec N Time in sec when Admin state of the CES interface is Down.
OperDownSec N Time in sec when Oper state of the CES interface is Down.
TxPsnPkts N Number of packets sent.
TxPsnOctets N Number of octets sent.
TxPsnDiscardPkts N Number of packets not sent.
TxPsnDiscardOctets N Number of octets not sent.
RxPsnOverrunEvents N Number of buffer overrun events.
RxPsnUnderrunEvents N Number of buffer underrun events.
RxPsnLopsEvents N Number of PSN Failure events.
RxPsnSwitchoverEvents N Number of sequence number switchover events.
RxPsnValidPkts N Number of valid packets received and delivered to TDM port.
RxPsnValidOctets N Number of valid octets received and delivered to TDM port.
RxPsnReorderPkts N Number of packets received and were reordered successfully.
RxPsnLbitDiscardPkts N Number of packets received with L-bit set and discarded.
RxPsnStrayDiscardPkts N Number of stray packets received and discarded.
RxPsnMalformDiscardPkts N Number of malformed packets received and discarded.


RxPsnDuplicatDiscardPkts N Number of packets received with SN already in jitter buffer.
RxPsnOowDiscardPkts N Number of packets received out of window (cannot be
reordered).
RxPsnOverrunDiscardPkts N Number of packets received and discarded for causing overrun.
RxPsnLostPkts N Number of packets received and categorized as lost.
Equals:
RxPsnMalformDiscardPkts+
RxPsnLbitDiscardPkts+
RxPsnLostOctets N Number of octets received and categorized as lost.
RxPsnPatternPackets N Number of packets received as lost or not received, and thereby
replaced by the predefined pattern.
RxPsnPatternOctets N Number of octets received as lost or not received, and thereby
replaced by the predefined pattern.
RxPsnLbitSec N Number of seconds during which L-bit was set in received
packets.
RxPsnRbitSec N Number of seconds during which R-bit was set in received
packets.
RxPsnLMbitSec N Number of seconds during which (L,M) = (0,10) in received
packets.
RxPsnES N Number of ESs.
RxPsnSES N Number of SESs.
RxPsnUAS N Number of Unavailable Seconds (UASs).
RxPsnRecClkFreeRunEvents N Number of transitions of RecClkState from any state to Freerun.
RxPsnRecClkPMSMEvents N Number of transitions of RecClkState from Normal to PMSM.
RxPsnRecClkHoldoverTime N Time during which RecClkState was Holdover.
LdpInNotificationStatus0x24 N Number of LDP Notification packets received with this status
data.
data.
data.
LdpInNotificationStatus0x2A N Number of LDP Notification packets received with this status
data.
RxPsnDeniedPkts N Number of packets received and discarded for other bad
formatting.
RxPsnGapsPkts N Number of gaps in jitter buffer, due to which a replacement
pattern was sent.
PM Common for CESoETH service (CES over PB PtP and CES over PB MPtMP)
AdminDownSec N Time in sec when Admin state of the CES service is Down.
OperDownSec N Time in sec when Oper state of the CES service is Down.


PM for CES service - PB PtP
APSSwitchEvent N Number of VLAN 1+1 switchover events.
PM for CES service - PB MPtMP
BSCConformOctets N Number of multicast, broadcast, and unknown destination
unicast bytes received by all ports for this VPN.
BSCDroppedOctets N Number of multicast, broadcast, and unknown destination
unicast bytes dropped by BSC policer of this VPN.
BSCDroppedPackets N Number of multicast, broadcast, and unknown destination
unicast packets dropped by BSC policer of this VPN.
BSCAverageRate N The Average Rate of MC, BC and Unknown packets in the
monitored seconds.
BSCUtilization N BSCAverageRate/BSCCIR * 100%.
QuotaDropPackets N Number of packets dropped due to exceeding the vFIB quota.
3.4.5 PTP1588 PM Counters and TCA

Table 3-6: PTP1588 PM counters and TCA

PTP-PktStatis
PTP-Pkt-uni_rx N Number of Ucast pkt received in 1min
PTP-Pkt-uni_max N Maximum number of Ucast received in 1min
PTP-Pkt-uni_min N Minimum number of Ucast received in 1min
PTP-Pkt-uni_avg N Average number of Ucast received in 1min
PTP-Pkt-multi_rx N Number of Mcast pkt received in 1min
PTP-Pkt-multi_max N Maximum number of Mcast received in 1min
PTP-Pkt-multi_min N Minimum number of Mcast received in 1min
PTP-Pkt-multi_avg N Average number of Mcast received in 1min
PTP-slaveNetworkMinMax
PTP-slave-pdv_min N Minimum PDV in usec
PTP-slave-pdv_max N Maximum PDV in usec
PTP-slave-pdv_sum N Accumulation of all max PDV in each minute
PTP-slave-td_min N Minimum measured round trip delay
PTP-slave-td_max N Maximum measured round trip delay
PTP-slave-td_sum N Accumulation of all min RTD in each minute
PTP-slave-tu_min N Minimum RTD uncertainty in nsec
PTP-slave-tu_max N Maximum RTD uncertainty in nsec


PTP-slave-tu_sum N Accumulation of all max RTDU in each minute
PTP-slave-ffoff_1pps_max N Maximal measured FFOFF
PTP-slave-ffoff_10M_max N Maximal measured FFOFF
3.5 Performing PM Export Configuration

This section describes how to perform PM export configuration, including how to configure PM export
settings, how to view the exported files, and the relevant PM counter tables.
Parent Topic
3.5.1 Configuring PM Export Settings

Before EMS-APT V2, it only supports configuring the PM export settings via script. From EMS-APT V2, you
can also configure the PM export settings in EMS-APT, as described in this section.
To configure PM export settings via script:

 Open the file under the path: EMS-APT/etc/emsserver_config.xml, and configure the script as
follows:

<PMExportConfig>
<PMEnable>false</PMEnable>
<ExportPath>ASCIIPMLogs</ExportPath>
<IntervalHour>1</IntervalHour>
<Format>PLAIN</Format>
<ExpirationDay>6</ExpirationDay>
</PMExportConfig>
The parameters are as follows:
 PMEnable: enables the PM export (default "false"; set "true" to enable).
 ExportPath: path of the PM file to export.
 IntervalHour: interval of PM export. The unit is hour.
 ExpirationDay: the file expiration time. The unit is day. When you perform the exporting tasks,
it will check the last time you exported. If the difference between the last time and current time
exceeds the ExpirationDay you set, the file will be deleted. If the ExpirationDay is set to -1, it will
not delete any files.

 Format: format of the file. There are four formats supported: PLAIN, FORMATTED,
EXTEND_FORMATTED and XML.
 If it is set as PLAIN, the file will be exported as the format "txt". The default setting is PLAIN.
For this format, when you perform the export task, it will export all records prior to the
current time, and does not distinguish the performance data between 15min and 24h.
When the export task is completed, all the export records will be deleted from database.
 If it is set as FORMATTED, the file will be exported as the format "csv". For this format,
when you perform the export task, it will export the performance data before current
time, within IntervalHour hours. In one day, each performance will be generated into two
PM files: 15min and 24h, and then each export will be appended to these generated
15min or 24h files until new files are generated the next day. When the export task is
completed, all the export records in database will not be deleted. The file name is similar
to "VC4_15min_20130313_101500_HOST.csv" or
"RS_24h_20130313_101500_HOST.csv".
 If it is set as EXTEND_FORMATTED, the file will be exported as the format "csv". It supports
exporting all types of the historical performance. The exported file format is the same with
FORMATTED, but the classification is not as detailed as FORMATTED. For example, for the
counters such as VC4, RS, MS, etc, the FORMATTED format exports the performance into
different files, while EXTEND_FORMATTED only exports them into the SDH performance
file. When you perform the export task, it will export the performance data before current
time, within IntervalHour hours. Each export will generate different files, and does not
distinguish between 15min and 24hour. When the export task is completed, all the export
records in database will not be deleted. The file name is similar to
"SDHHisPerformanceInfo_20130313_101500_HOST.csv".
 If it is set as XML, the file will be exported as the format "xml". It supports the same
historical performance type with the FORMATTED format. When you perform the export
task, it will export the performance data before current time, within IntervalHour hours,
and does not distinguish between 15min and 24hour. When the export task is completed,
all the export records in database will not be deleted. The file name is similar to
"VC4_20130313_101500_HOST.xml".
 For the XML format and FORMATTED format, you can also enable or disable the export of a
specified historical PM type in the emsserver_config.xml file, as described below. The
ExportEnable is set as "true", indicating the relevant PM type is enabled to be exported.
To disable, set "false".
<ConfigItem>
<MOType>RS</MOType>
<ExportEnable>true</ExportEnable>
<ArchiverName>SDH History Performance</ArchiverName>
</ConfigItem>
<ConfigItem>
<MOType>MS</MOType>
</ConfigItem>
<ConfigItem>

<MOType>VC4</MOType>
</ConfigItem>
<ConfigItem>
<MOType>VC3</MOType>
</ConfigItem>
To configure PM export settings in EMS-APT:

1. In the EMS-APT main topology view window, from the main menu, select System and then
Performance Export Settings. The Performance Export Settings window opens.
2. To enable the PM export settings, select the Enabled checkbox, and the attributes are available to be
configured.

3. In the Format dropdown list, you can select a required format of your export file.
4. To save your settings, click the Apply button.
The four export formats can be described as below:

 When the Format is set as EXTEND_FORMATTED, all types of counters can be exported.
 When the Format is set as XML or FORMATTED, the following types of counters can be exported:
 VC4
 VC3
 VC12
 MS
 RS
 PPI
 E1
 DCC
 Eth Port (GE/FE Port)
 WAN Port (EoS/MOT Port)
 LAG
 Eth Port L2
 POS
 EoS
 VSI
 Policer
 Switch
 Tunnel
 Tunnel CoS (L-LSP)
 E-LSP CoS
 CFM MA

 Local MEP
 Remote MEP
 When the Format is set as PLAIN, the following types of counters can be exported:
 VC4
 VC3
 VC12
 MS
 RS
 PPI
 EoS
 FE LAN
 GE LAN
 LAG
 EoS Port
 VSI
 Policer
 Switch
 Tunnel
 E-LSP Tunnel Queue
 L-LSP Tunnel CoS
In EMS, there are two types of PM counters in the L2 Card MoT/EoS Port:
 Port Counter (MAC layer counters)
 EoS Counter (GFP layer counters)
The cards below support both of the counters:
 ESW_2G_8F
 ESW_2G_8F_E
 MESW_6F
The File Name of Export PM Log for EoS Counters will be such as "EoS_20120620-130000-HOST.txt".
The File Name of Export PM Log for Port counters will be such as
"EoS_Port_20120620-130000-HOST.txt".
The cards below can only support EoS Counters (GFP layer counters):
 DMGE_2_L2
 DMGE_4_L2
 DMGE_8_L2
 MPS_2G_8F
 ME_2G_4F

 MPOE_12G
 DMXE_48_L2
 DMXE_22_L2
 CPTS100
 CS10
The File Name of Export PM Log will be such as "EoS_20120620-130000-HOST.txt".
To clarity EoS_Port or MoT port, there is a column named "porttype" in the txt file:
 If "porttype=6", the port is MOT Port.
 If "porttype=8", the port is EOS Port.
Parent Topic
3.5.2 Viewing the Exported Files

This section describes the description of the exported files.
To view an exported file:

 To view an exported file, double-click the file you want to view.
The following describes the examples of the exported files.
 If the Format is set as PLAIN, there are 4 types of exported txt files:
 For an SDH port type, the exported txt file will be shown as below.
NEID;NEName;SlotNumber;SubSlotNumber;UpParentMONo;UpParentMOType;ParentMO
No;ParentMOType;MOType;MONo;PortType;PortNo;Granularity;ReportTime;BBE;ES
;SES;UAS;FEES;FESES;FEBBE;FEUAS;OFS;PPJC;NPJC;Selected;revBadPacketBytes;
sendBadPacketBytes;rxTotalPayloadOct;totalFrameBytes;singleBitErrFrames;m
ultiBitErrFrames;PSC;Rx_Broadcast_Pkts;Rx_Multicast_Pkts;Rx_CRC_Align_Err
or_Pkts;Collision_Errors;Rx_Error_Pkts;Rx_Octets;Tx_Octets;
----;------;----------;-------------;------------;--------------;--------
--;------------;------;----;-----------;----------;---;--;---;---;----;--
---;-----;-----;---;----;----;--------;-----------------;----------------
--;-----------------;---------------;------------------;-----------------
;---;-----------------;-----------------;-----------------------;--------
--------;-------------;---------;---------;
1;BG64-1;10;-1;-1;-1;-1;-1;26;1;5;1;0;2012-06-13
16:45:00;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;649;649;649;649;649;0;0;
1;BG64-1;10;-1;-1;-1;-1;-1;26;2;5;2;0;2012-06-13
16:45:00;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;649;649;649;649;649;0;0;
 For a VSI type, the exported txt file will be shown as below.

NEID;NEName;SlotNumber;SubSlotNumber;VPNID;Granularity;ReportTime;BSC
Conforming Octets;BSC Dropped Octets;BSC Dropped Packets;BSC Average
Rate;BSC Utilization;Quota Drop Packets;Mac Move Events;Rx IGMP Pkts
----;------;----------;-------------;-----;-----------;----------;-------
--------------;------------------;-------------------;----------------;--
-------------;------------------;---------------;------------
1;BG64-1;10;-1;1;0;2012-06-13 16:45:00;684;684;684;684;684;684;684;684;
1;BG64-1;10;-1;1;0;2012-06-13 17:00:00;684;684;684;684;684;684;684;684;
 For a Policer type, the exported txt file will be shown as below.
NEID;NEName;SlotNumber;SubSlotNumber;MOType;MONo;VPNID;GroupID;CoS;Granul
arity;ReportTime;Act Pkts;Act Octets;Green Pkts;Yellow Pkts;Drop Pkts;Green
Octets;Yellow Octets;Drop Octets;Conforming Octet Rate;Policer
Utilization;Non Conforming Octets;Peak Octect Rate;Peak Octect Rate time
----;------;----------;-------------;------;----;-----;-------;---;------
-----;----------;--------;----------;----------;-----------;---------;---
---------;-------------;-----------;---------------------;---------------
----;---------------------;----------------;---------------------
1;BG64-1;10;-1;26;0;1;1;0;0;2012-05-31
11:15:00;369;369;369;369;369;369;369;369;369;369;369;369;null;
1;BG64-1;10;-1;26;0;1;1;0;0;2012-05-31
11:30:00;369;369;369;369;369;369;369;369;369;369;369;369;null;
 For a Switch type, the exported txt file will be shown as below.
NEID;NEName;SlotNumber;SubSlotNumber;Granularity;ReportTime;MSTP Topology
Changes;FIB Full Seconds Counter;FIB Utilization;FIB Quota
Utilization;Forwarded Packets
----;------;----------;-------------;-----------;----------;-------------
--------;------------------------;---------------;---------------------;-
----------------
1;BG64-1;10;-1;0;2012-05-31 11:15:00;147;147;147;147;147;
1;BG64-1;10;-1;0;2012-05-31 11:30:00;147;147;147;147;147;
 If the Format is set as FORMATTED, the exported csv files of each types are different. Following
shows an example of an exported csv file:
ID,NE,Object,Granularity,Report
Time,Rx_Pkts_64,Rx_Pkts_65_127,Rx_Pkts_128_255,Rx_Pkts_256_511,Rx_Pkts_51
2_1023,Rx_Pkts_1024_1518,Rx_Pkts_1519_MTU,Rx_Undersize_Pkts,Rx_Oversize_P
kts,Rx_Fragments,Rx_Jabber_Pkts,Rx_Broadcast_Pkts,Rx_Multicast_Pkts,Rx_CR
C_Align_Error_Pkts,Collision_Errors,Rx_Error_Pkts,Rx_Octets,Rx_Pkts,Tx_Oc
tets,Tx_Pkts
1,178,TS5:DMGE_4_L2 GE-ETY port 1,15min,2012-07-03
15:14:06,900,900,900,900,900,900,900,900,900,900,900,900,900,900,900,900,
900,900,900,900
2,178,TS5:DMGE_4_L2 GE-ETY port 1,15min,2012-07-03
15:44:06,900,900,900,900,900,900,900,900,900,900,900,900,900,900,900,900,
900,900,900,900

 If the Format is set as EXTEND_FORMATTED, the exported csv files of each types are different.
Following shows an example of an exported csv file:
ID,NE,Object,Granularity,Report
Time,BBE,FEBBE,FECCE,FEES,FESES,UAS,SES,PSC,PPJC,OFS,NPJC,FEUAS,ES
1,BG64-1,XS A:SAM64 oPort 1-VC4#20,15min,2013-01-18
00:00:00.0,156,338,-1,577,261,990,769,0,67,209,201,967,19
2,BG64-1,XS A:SAM64 oPort 1-VC4#20,15min,2013-01-18
00:15:00.0,851,81,-1,168,41,316,20,0,828,688,902,253,499
From the files, you can see that the text consists of the historical performance parameters' names and
values, which are divided into two parts by the short lines and can be viewed in one line. They are in a
one-to-one relationship. The names and values are separated by a series of spaces and semicolons. As
shown in the file, one copy of historical performance data is reported.
The following are some of the parameters in the texts:
 NEID: ID of the monitored NE.
 SlotNumber: slot number.
 SubSlotNumber: subslot number.
 UpParent MONo: Up-parent MO number.
 UpParent MOType: type of the Up-parent MO.
 Parent MONo: parent MO number.
 Parent MOType: type of the parent MO.
 MOType: type of the MO.
 MONo: MO number.
 PortType: type of port.
 PortNo: port number.
 Granularity: monitor periods (15-minute or 24-hour).
 ReportTime: interval start time.
NOTE: MO here is defined as three types:

 UpParent MO
 Parent MO
 MO

The following table describes the slot (subslot) numbers and the relevant slot name the number represents.
Table 3-7: Slot names and relevant slot numbers
Slot (index BG-40 BG-20 BG-30 BG-64 NPT-1200 NPT-1020 NPT-1021 NPT-1010
from 0 in
DB)
0 XTC MXC MS MS MS MXC1020 MXC1021 MXC1010
1 OW OW BG_OW OW OW OW OW
2 TMU XS A XSA_TM XSA_TMU TMU TMU TMU
U
3 XS B XSB_TMU XSB_TMU CPE CPE CPE
4 Subcard 1 A1 XS A XSA_SAM XSA_SAM SAM
5 Subcard 2 A2 XS B XSB_SAM XSB_SAM
6 XS A XSA_XIO XSA_XIO MGE_12 MGE_12 MGE
7 IOM XS B XSB_XIO XSB_XIO MEoS_8
8 Subcard 3 TS1 TS1 TS1 TS TS TS
9 Subcard 4 EME1_21 TS2 TS2 TS2 EME1_21
10 Extended ES1 TS3 TS3 TS3
Slot 1
11 Extended ES2 ES1 TS4 TS4
Slot 2
12 ES3 ES2 TS5 TS5
13 ES3 TS6 TS6
14 TS7 TS7
15 ES1 ES1
16 ES2 ES2
17 ES3 ES3
18 CF CF CF CF CF
19 B_BACK B_BACK B_BACK
20 PSA PSA PSA
21 PSB PSB
22 FS FS FS
23 E_BACK E_BACK
24 PSA_E PSA_E
25 PSB_E PSB_E
26 FS_E FS_E
27 MAX_SLOT
_NUM

Slot (index BG-40 BG-20 BG-30 BG-64 NPT-1200 NPT-1020 NPT-1021 NPT-1010
from 0 in
DB)
96 BG-20B BG-30B BG-64B NPT-1200B
97 FAN FCU-B FCU-30B FS FS
98 INF-DC INF-20B PS_B A PSA PSA
99 BG20-E BG-30E
101 PS_B B PSB PSB
147 FCU-E FCU-30E FS_E FS_E
148 INF-20E PS_E A PSA_E PSA_E
151 PS_E B PSB_E PSB_E
For the other object ID references, see the Object ID Reference Tables part in the <PM Export in XML
Format> document.
Parent Topic
3.5.3 PM Counters Lists

In EMS-APT, there are current PM counters that are always visible in the EMS GUI, and history PM counters
that are always exportable from the EMS.
There are two methods to export the history PM counters: ASCII/CSV and XML, with all the history PM
counters available via XML, and a small subset available via ASCII/CSV.
Basically, the same objects have the same PM counters. But there may be some differences in PM
capability for the same object in different cards due to hardware limitation:
 All SDH cards support PM for Optical, RS, MS, VC-4.
 All E1 cards support PM for PPI, VC-12.
 All E3/DS3 cards support PM for PPI, VC-3.
 All L1 cards support PM for Ethernet port, EoS, and VCG member (VC-n).
 All L2 cards support PM for Ethernet port, EoS, VCG member (VC-n), switch, VSI, Policer, tunnel (for
MPLS card only), Queue/CoS, CFM (MA, MEP).
SDH cards include:

 BG-20: A1/A2 SAM, SMD1H, OMS4H, S1_4
 BG-20C: A1/A2 SAM
 BG-30: XIO30-1, XIO30-4, XIO30-16, XIO30Q_1&4, SMD1B, SMS4, SMD4, SMQ1&4, SMQ1, SMS16,
S1_4, S4_1
 BG-64: XIO64, XIO16_4, SMS16, SMQ1&4, SMQ1, SMD1B, S1_4
 NPT-1200: CPTS100 SAM10 & SAM25_2, XIO64, XIO16_4, SMS16, SMQ1&4, SMQ1, SMD1B, S1_4

 NPT-1020: SAM4_2, SMS4, SMD1B, S1_4

PDH cards include:
 BG-20: EME1_21, ME1_21H, ME1_42H, PE1_63, P345_3E, M345_3
 BG-20C: EME1_21
 BG-30: PME1_21, PME1_63, PM345_3, PE1_63, P345_3E
 BG-64: PME1_21, PME1_63, PM345_3, PE1_63, P345_3E
 NPT-1200: PME1_21, PME1_63, PM345_3, PE1_63, P345_3E
 NPT-1020: PME1_21, PME1_63, PM345_3, PE1_63, P345_3E
EoP cards include: MEOP_4H, DMEOP_4, SM_EOP
L1 cards include:
 BG-20: L1B_6F, MGE_1_L1
 BG-30: DMFE_4_L1, DMFX_4_L1, DMGE_1_L1, DMGE_4_L1
 BG-64: DMFE_4_L1, DMFX_4_L1, DMGE_4_L1
 NPT-1200: DMFE_4_L1, DMFX_4_L1, DMGE_4_L1
L2 cards include:
 BG-20: MESW_6F, MPS_6F, ME_2G_4F, MPS_2G_8F, ESW_2G_8F_E, MPOE_12G
 BG-20C: MPS_4F
 BG-30: DMFE_4_L2, DMFX_4_L2, DMGE_2_L2, DMGE_4_L2, MPS_2G_8F, ESW_2G_8F_E,
DMXE_22_L2, MPOE_12G
 BG-64: DMFE_4_L2, DMFX_4_L2, DMGE_2_L2, DMGE_4_L2, MPS_2G_8F, DMGE_8_L2, DMXE_48_L2,
DMXE_22_L2, MPOE_12G
 NPT-1200: CPTS100, CPS100, DMFE_4_L2, DMFX_4_L2, DMGE_2_L2, DMGE_4_L2, MPS_2G_8F,
DMGE_8_L2, DMXE_48_L2, DMXE_22_L2, MPOE_12G, DHGE_8, DHGE_4E, DHGE_16, DHGE_24,
DHXE_2, DHFE_12, DHFX_12
 NPT-1020: CS10, CPS50, DHGE_8, DHGE_4E, MPOE_12G, DHFE_12, DHFX_12
 NPT-1021: CS10, CPS50, DHGE_8, DHGE_4E, DHFE_12, DHFX_12
 NPT-1010: CS5
CES cards include:

 BG-20: DMCE1_32
 BG-30: DMCE1_32, DMCES1_4
 BG-64: DMCE1_32, DMCES1_4
 NPT-1200: DMCE1_32, DMCES1_4, MSE1_16
 NPT-1020/NPT-1021: DMCE1_32, DMCES1_4, MSE1_16
 NPT-1010: TMSE1_8

PCM cards include:

 BG-20: SM_10E
 BG-30: SM_10E
 BG-64: SM_10E
 NPT-1200: SM_10E, EM_10E
 NPT-1020: SM_10E, EM_10E
 NPT-1021: EM_10E
The lists of counters are shown below, indicating the relationship of the counters (The value range of
Counter32 is 264-1, and counter64 is 264-1).
Parent Topic
3.5.4 SDH PM Counters

Table 3-8: SDH PM counters
No. Counter Description Current PM History PM ASCII Values 15-Min valid 24-Hrs Supported in
name export value valid value
Regenerator Section
1 BBE Near-end Yes Yes Yes Error Counter32 Counter32 All SDH cards in
Background count BG-20/20C/30/64
block error.
2 OFS Number of out of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
frame seconds BG-20/20C/30/64
accumulated.
3 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
near end BG-20/20C/30/64
accumulated.
4 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 All SDH cards in
near end BG-20/20C/30/64
accumulated. If
30% frames are
errored, this
second is SES.
5 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
unavailable BG-20/20C/30/64
seconds near
end
accumulated.
Multiplexing Section
1 BBE Near-end Yes Yes Yes Error Counter32 Counter32 All SDH cards in
Background count BG-20/20C/30/64
block error
2 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
near-end BG-20/20C/30/64
accumulated

3 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 All SDH cards in
near-end BG-20/20C/30/64
accumulated
4 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
seconds
near-end
accumulated
5 FE-BBE Far-end Yes Yes Yes Error Counter32 Counter32 All SDH cards in
background count BG-20/20C/30/64
block error
6 FE-ES Number of SEs Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
far-end BG-20/20C/30/64
accumulated
7 FE-SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 All SDH cards in
far-end BG-20/20C/30/64
accumulated
8 FE-UAS Number of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards in
seconds
near-end
accumulated
VC-4/AU-4
1 BBE Near-end Yes Yes Yes Error Counter32 Counter32 All SDH cards and
Background count VC-4-Xv VCG of
block error L1/L2 cards
2 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 All SDH cards and
near-end VC-4-Xv VCG of
accumulated L1/L2 cards
3 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 All SDH cards and
4 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards and
unavailable VC-4-Xv VCG of
seconds L1/L2 cards
near-end
accumulated
5 NPJC Number of Yes Yes Yes Event Counter32 Counter32 All SDH cards and
negative pointer count VC-4-Xv VCG of
justifications L1/L2 cards
accumulated
6 PPJC Number of Yes Yes Yes Event Counter32 Counter32 All SDH cards and
positive pointer count VC-4-Xv VCG of
justifications L1/L2 cards
accumulated
7 FE-BBE Far-end Yes Yes Yes Counter32 Counter32 Counter32 All SDH cards and
background VC-4-Xv VCG of
block error L1/L2 cards
8 FE-ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 All SDH cards and
far-end VC-4-Xv VCG of

9 FE-SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 All SDH cards and
10 FE-UAS Number of Yes Yes Yes Seconds 0~900 0~86400 All SDH cards and
seconds L1/L2 cards
near-end
accumulated
VC-3/TU-3
1 BBE Near-end Yes Yes Yes Error Counter32 Counter32 E3/DS3 cards and
Background count VC-3-Xv VCG of
block error L1/L2 card
2 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 E3/DS3 cards and
accumulated L1/L2 card
3 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 E3/DS3 cards and
4 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 E3/DS3 cards and
seconds L1/L2 card
near-end
accumulated
5 NPJC Number of Yes Yes Yes Event Counter32 Counter32 E3/DS3 cards and
negative pointer count VC-3-Xv VCG of
justifications L1/L2 card
accumulated
6 PPJC Number of Yes Yes Yes Event Counter32 Counter32 E3/DS3 cards and
positive pointer count VC-3-Xv VCG of
justifications L1/L2 card
accumulated
7 FE-BBE Far-end Yes Yes Yes Error Counter32 Counter32 E3/DS3 cards and
background count VC-3-Xv VCG of
block error L1/L2 card
8 FE-ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 E3/DS3 cards and
9 FE-SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 E3/DS3 cards and
10 FE-UAS Number of Yes Yes Yes Seconds 0~900 0~86400 E3/DS3 cards and
seconds L1/L2 card
near-end
accumulated
VC-12/TU-12
1 BBE Near-end Yes Yes Yes Error Counter32 Counter32 E1 cards, EOP
Background count card and
block error VC-12-Xv VCG of
L1/L2 card

2 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 E1 cards, EOP
near end card and
accumulated VC-12-Xv VCG of
L1/L2 card
3 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 E1 cards, EOP
near-end card and
L1/L2 card
4 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 E1 cards, EOP
unavailable card and
seconds VC-12-Xv VCG of
near-end L1/L2 card
accumulated
5 NPJC Number of Yes Yes Yes Event Counter32 Counter32 E1 cards, EOP
negative pointer count card and
justifications VC-12-Xv VCG of
6 PPJC Number of Yes Yes Yes Event Counter32 Counter32 E1 cards, EOP
positive pointer count card and
justifications VC-12-Xv VCG of
7 FE-BBE Far-end Yes Yes Yes Error Counter32 Counter32 E1 cards, EOP
background count card and
block error VC-12-Xv VCG of
L1/L2 card
8 FE-ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 E1 cards, EOP
far-end card and
L1/L2 card
9 FE-SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 E1 cards, EOP
far-end card and
L1/L2 card
10 FE-UAS Number of Yes Yes Yes Seconds 0~900 0~86400 E1 cards, EOP
unavailable card and
seconds VC-12-Xv VCG of
near-end L1/L2 card
accumulated
PPI
1 CV Number of code Yes Yes Yes Error Counter32 Counter32 PDH cards
violations count
near-end
accumulated
2 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 PDH cards
near-end
accumulated
3 SES Number of SESs Yes Yes Yes Seconds 0~900 0~77760 PDH cards
near-end
accumulated

4 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 PDH cards
unavailable
seconds
near-end
accumulated
E1
1 CV Number of code Yes Yes Yes Error Counter32 Counter32 SM_10E, EOP
violations count cards
near-end
accumulated
2 BBE Near-end Yes Yes Yes Error Counter32 Counter32 SM_10E, EOP
Background count cards
block error
3 ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 SM_10E, EOP
near end cards
accumulated
4 SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 SM_10E, EOP
near-end cards
accumulated
5 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 SM_10E, EOP
unavailable cards
seconds
near-end
accumulated
6 FE-BBE Far-end Yes Yes Yes Error Counter32 Counter32 SM_10E, EOP
background count cards
block error
7 FE-ES Number of ESs Yes Yes Yes Seconds 0~900 0~86400 SM_10E, EOP
far-end cards
accumulated
8 FE-SES Number of SESs Yes Yes Yes Seconds 0~810 0~77760 SM_10E, EOP
far-end cards
accumulated
9 FE-UAS Number of Yes Yes Yes Seconds 0~900 0~86400 SM_10E, EOP
unavailable cards
seconds
near-end
accumulated
Optical (SFP)
1 Rx-Optical-Po RX optical power Yes No No -40~+8.2 NA NA All optical SFP,

wer dBm' XFP
2 Tx-Optical-Po TX optical power Yes No No -40~+8.2 NA NA All optical SFP,

wer dBm' XFP
3 Tx-Laser-Bias TX Laser Bias Yes No No 0~131mA NA NA All optical SFP,

Current current XFP
4 SFP-Temp Transceiver Yes No No -128~+128 NA NA All optical SFP,

Temperature C' XFP
5 VCC3 3.3 V Power Yes No No 0~6.55V NA NA All optical SFP,

supply Voltage XFP

DCC
1 RX-Octets Number of bytes Yes Yes Yes Bytes Counter64 Counter64 BG-30, BG-64
received
2 RX-Packets Number of good Yes Yes Yes Packets Counter32 Counter32 BG-30, BG-64
packets received
3 Number of error Yes Yes Yes Packets Counter32 Counter32 BG-30, BG-64
RX-Error-Pkts packets received
4 TX-Octets Number of bytes Yes Yes Yes Bytes Counter32 Counter32 BG-30, BG-64
transmitted
5 TX-Packets Number of good Yes Yes Yes Packets Counter32 Counter32 BG-30, BG-64
packets
transmitted
successfully
6 TX-Error-Pkts Number of Yes Yes Yes Packets Counter32 Counter32 BG-30, BG-64
transmit fail
events
Table 3-9: Data PM counters
No. Counter Description Current PM History PM ASCII Values 15-Min valid 24-Hrs valid
name export value value
Port Level
1 Rx Octets Received total number of Yes Yes Yes Bytes Counter64 Counter64
bytes for all good packets
(Unicast+Multicast+Broad
cast).
2 Rx Pkts Received total number of Yes Yes Yes Packets Counter64 Counter64
good packets (Unicast +
Multicast + Broadcast).
3 Rx Broadcast Received total number of Yes Yes Yes Packets Counter64 Counter64
Pkts good Broadcast packets.
4 Rx Multicast Received total number of Yes Yes Yes Packets Counter64 Counter64
Pkts good Multicast packets.
5 Tx Octets Transmitted total number Yes Yes Yes Bytes Counter64 Counter64
of bytes for all good
packets (Unicast +
6 Tx Pkts Transmitted total number Yes Yes Yes Packets Counter64 Counter64
of good packets (Unicast +
7 Rx Error Pkts Received total number of Yes Yes Yes Packets Counter64 Counter64
dropped packets, includes
all bad packets and
dropped good packets.
8 Rx Pkts 64 Received total number of Yes Yes Yes Packets Counter64 Counter64
good packets with size of
64 bytes.

65-127 good packets with size of
from 65 to 127 bytes.
128-255 good packets with size
128-255 bytes.
256-511 bytes.
512-1023 bytes.
13 Rx Pkts Received total number of Yes No Yes Packets Counter64 Counter64

1024-MTU good packets with size
1024 to MTU bytes.
14 Rx CRC Align Received total number of Yes Yes Yes Packets Counter64 Counter64
Error Pkts bad packets which meets
all the following
conditions:
 Packet length is
valid (between 64
and MTU).
 Packet has invalid
CRC.
 Collision event has
not been detected.
15 Rx Undersize Received total number of Yes Yes Yes Packets Counter64 Counter64
Pkts bad packets which meets
all the following
conditions:
 Packet length is less
than 64 bytes.
 Packet has valid
CRC.
not been detected.
16 Rx Oversize Received total number of Yes Yes Yes Packets Counter64 Counter64
Pkts bad packets which meets
all the following
conditions:
 Packet length is
larger than MTU.
 Packet has valid
CRC.
not been detected.
17 Rx Pause Received total number of Yes Yes Yes Packets Counter64 Counter64
Pkts Pause frames.
18 Collision Total number of collision Yes Yes Yes Events Counter64 Counter64
Errors events has been detected.
19 ACL Discard Packets discarded due to Yes Yes Yes Packets Counter64 Counter64
Pkts ACL rule.

20 VLAN Per port counter for RX Yes Yes Yes Packets Counter64 Counter64
Filtering good packets discarded
Discard Pkts due to VLAN filtering
should be added for
Ezchip NP based cards.
21 Ingress Per port Counter for Yes Yes Yes Packets Counter64 Counter64
classification packets discarded by NP
Discard due to ingress
packets classification for EzChip
NP based cards.
22 Mac Filtering Per Port counter for Yes Yes Yes Packets Counter64 Counter64
Discard Pkts packets discarded due to
mac filterint when mac
filtering enabled.
23 TC Ingress Number of PTP packets Yes Yes Yes Packets Counter64 Counter64
Process PTP modified in Ingress
Pkts
24 TC Egress Number of PTP packets Yes Yes Yes Packets Counter64 Counter64
Process PTP modified in Engress
Pkts
Switch Level
1 MSTP The total number of Yes Yes Yes Event Counter64 Counter64
Topology topology changes count
Changes detected by the switch.
2 FIB Full Number of seconds in Yes Yes Yes Seconds 0~900 0~86400
Seconds which FIBActualSize was
Counter in its maximum value
(32K).
3 FIB FIB current Size/32k. Yes Yes Yes Percents 0~100% 0~100%
Utilization
4 FIB Quota FIB current Size/Total Yes Yes Yes Percents 0~100% 0~100%
Utilization Provisioned Size.
5 Forwarded Forwarded Packets by the Yes Yes Yes Packets Counter64 Counter64
Packets switch.
6 Forwarding The average bit rate of Yes Yes Yes Gbps Counter64 Counter64
Average Bit NPU forwarding in 15min
Rate or 24h.
7 Forwarding The minimum bit rate of Yes Yes Yes Gbps Counter64 Counter64
Min Bit Rate NPU forwarding in 15min
or 24h, this bit rate is
calculated per 10 seconds
of interval.
8 Forwarding The maximum bit rate of Yes Yes Yes Gbps Counter64 Counter64
Max Bit Rate NPU forwarding in 15min
or 24h, this bit rate is
calculated per 10 seconds
of interval.
9 Forwarding The average packet rate Yes Yes Yes Kpps Counter64 Counter64
Average Pkt of NPU forwarding in
Rate 15min or 24h.

10 Rorwarding The minimum packet rate Yes Yes Yes Kpps Counter64 Counter64
Min Pkt Rate of NPU forwarding in
15min or 24h, this packet
rate is calculated per 10
seconds of interval.
11 Forwarding The maximum packet rate Yes Yes Yes Kpps Counter64 Counter64
Max Pkt of NPU forwarding in
Rate 15min or 24h, this packet
rate is calculated per 10
seconds of interval.
12 Drop Pkts in Dropped Packets by the Yes Yes Yes Packets Counter64 Counter64
Stage1 NPU engine #1
15 TC Good Number of PTP packets Yes Yes Yes Packets Counter64 Counter64
Process PTP that "Correction Field
Pkts Modified Successfully"
16 TC Bad Number of PTP packets Yes Yes Yes Packets Counter64 Counter64
Process PTP that "Correction Field
Pkts Modified Unsuccessfully"
17 SOAM PM Total number of SOAM Yes Yes Yes Packets Counter64 Counter64
Frames PM frames discarded by
Discarded by NPU for various reasons
NPU
18 Invalid DMM Total number of Yes Yes Yes Packets Counter64 Counter64
Pkts discarded invalid DMM
frames.
19 Invalid DMR Total number of Yes Yes Yes Packets Counter64 Counter64
Discarded discarded invalid DMR
frames
20 Invalid SLM Total number of Yes Yes Yes Packets Counter64 Counter64
Discarded discarded invalid SLM
frames
21 Invalid SLR Total number of Yes Yes Yes Packets Counter64 Counter64
Discarded discarded invalid SLR
frames
Policer Level
1 Act Pkts Number of received good Yes Yes Yes Packets Counter64 Counter64
frames handled by the
policer.
2 Act Octets Number of received good Yes Yes Yes Bytes Counter64 Counter64
bytes handled by the
policer.
3 Green Pkts Number of Green Packets Yes Yes Yes Packets Counter64 Counter64
for this policer.
4 Yellow Pkts Number of Yellow Packets Yes Yes Yes Packets Counter64 Counter64
for this policer.

5 Drop Pkts Number of Red Packets Yes Yes Yes Packets Counter64 Counter64
for this policer.
6 Green Number of Green bytes Yes Yes Yes Bytes Counter64 Counter64
Octets for this policer.
7 Yellow Number of Yellow bytes Yes Yes Yes Bytes Counter64 Counter64
Octets for this policer.
8 Drop Octets Number of Red bytes for Yes Yes Yes Bytes Counter64 Counter64
this policer.
9 Conforming Average octet rate of Yes Yes Yes bps 0~1Gbps 0~1Gbps
Octet Rate conforming octets (an
octet accepted by the
policer).
10 Policer Utilization of the Yes Yes Yes Percents 0~100% 0~100%

Utilization permitted capacity (CIR).
11 Non Percentage of octets Yes Yes Yes Bytes Counter64 Counter64

Conforming dropped by this policer.
Octets
VSI Level
1 BSC Number of broadcast, Yes Yes Yes Bytes Counter64 Counter64

Conforming unknown destination
Octets unicast/multicast bytes
received by all ports for
this VPN.
2 BSC Number of broadcast, Yes Yes Yes Bytes Counter64 Counter64

Dropped unknown destination
Octets unicast/multicast bytes
dropped by BSC policer of
this VPN.
3 BSC Number of broadcast, Yes Yes Yes Packets Counter64 Counter64

Dropped unknown destination
Pkts unicast/multicast packets
dropped by BSC policer of
this VPN.
4 BSC Average Average octet rate of Yes Yes Yes bps 0~No Rate Limit 0~No Rate Limit
Rate conforming octets (an
octet accepted by BSC
policer).
5 BSC Utilization of the Yes Yes Yes Percents 0~100% 0~100%

Utilization permitted capacity of BSC
policer (CIR).
6 Rx IGMP Number of IGMP reported Yes Yes Yes Packets Counter64 Counter64
Reported packets received from all
Pkts access ports of leaf VSI.
7 MAC Move Number of MAC move Yes Yes Yes Event Counter64 Counter64
Events events (duplicate MAC count
learned).
8 Quota Drop Number of packets Yes Yes Yes Packets Counter64 Counter64
Packets discarded due to FIB over
quota.

Queue Level (per CoS per tunne, Or per CoS per QB, or per CoS per port)
1 Tx Octets Number of bytes Yes Yes Yes Bytes Counter64 Counter64

transmitted for this CoS of
tunnel/port out
2 Tx Pkts Number of packets Yes Yes Yes Packets Counter64 Counter64

transmitted for this CoS of
tunnel/port out
3 Tx Wred Number of octets Yes Yes Yes Bytes Counter64 Counter64

Octets discarded by WRED on
this CoS of tunnel/port
out
4 Tx Wred Number of packets Yes Yes Yes Packets Counter64 Counter64

Pkts discarded by WRED on
this CoS of tunnel/port
out
5 Tx Average Average octets rate of this Yes Yes Yes bps 0~1Gbps 0~1Gbps
Rate CoS of tunnel/port out
6 Tx Utilization Tx Average Rate/Tunnel Yes Yes Yes Percents 0~100% 0~100%

Bandwidth
Tunnel Level (for both E-LSP and L-LSP)
1 Rx Octets Number of bytes received Yes Yes Yes Bytes Counter64 Counter64
for this tunnel
2 Rx Pkts Number of packets Yes Yes Yes Packets Counter64 Counter64

received for this tunnel
3 Rx Average Average octets rate of Yes Yes Yes bps 0~1Gbps 0~1Gbps
Rate packets received for this
tunnel
4 TunnelDown Number of seconds Yes Yes Yes Seconds 0~900 0~86400

Sec during which the
Operational state of this
tunnel was down
5 TunnelDown Ratio of time during Yes Yes Yes PPM 0~1,000,000 0~1,000,000
SecRatioPp which the Operational
m state of this tunnel was
down
MA Level
1 MA Down Number of seconds Yes Yes Yes Seconds 0~900 0~86400

Seconds during which the
Operational state of MEG
was down.
2 MA Down Ratio of time during Yes Yes Yes PPM 0~1,000,000 0~1,000,000
Seconds which the the Operational
PPM state of MEG was down
(0-1,000,000 @ 1).
Local MEP Level per MA
1 CCM Frames Total number of Yes Yes Yes Packets Counter64 Counter64
Tx transmitted CCM frames.

2 CCM Frames Total number of valid Yes Yes Yes Packets Counter64 Counter64
Rx CCM frames received.
3 LBM Frames Total number of Yes Yes Yes Packets Counter64 Counter64
Tx transmitted LBM frames.
4 LBM Frames Total number of valid Yes Yes Yes Packets Counter64 Counter64
Rx LBM frames received.
5 LBR Frames Total number of Yes Yes Yes Packets Counter64 Counter64
Tx transmitted LBR frames.
6 LBR Frames Total number of valid LBR Yes Yes Yes Packets Counter64 Counter64
Rx frames received.
7 LTMFrames Total number of Yes Yes Yes Packets Counter64 Counter64

Tx transmitted LTM frames.
8 LTM Frames Total number of valid LTM Yes Yes Yes Packets Counter64 Counter64
Rx frames received.
9 LTR Frames Total number of Yes Yes Yes Packets Counter64 Counter64
Tx transmitted LTR frames.
10 LTR Frames Total number of valid LTR Yes Yes Yes Packets Counter64 Counter64
Rx frames received.
Remote MEP Level per MA
1 Remote MEP Number of seconds Yes Yes Yes Seconds 0~900 0~86400
Down during which the
Seconds Operational state of
remote MEP was down.
2 Remote MEP Ratio of time during Yes Yes Yes PPM 0~1,000,000 0~1,000,000
Down which the Operational
Seconds state of Remote MEP was
PPM down.
3 DMM Number of transmitted Yes Yes Yes Packets Counter64 Counter64

Frames DMM frames (i.e.,
Transmitted number of initiated
measurements).
4 DMR Frames Number of received DMR Yes Yes Yes Packets Counter64 Counter64
Received frames (i.e., number of
completed
measurements).
5 Not Number of FD Yes Yes Yes Packets Counter64 Counter64

Compliant measurements which fell
FD above the threshold.
Measureme
nts
6 Not Number of FDV Yes Yes Yes Packets Counter64 Counter64

Compliant measurements in forward
FDV direction which fell above
Measureme the threshold.
nts (forward
direction)

7 Not Number of FDV Yes Yes Yes Packets Counter64 Counter64

Compliant measurements in
FDV backward direction which
Measureme fell above the threshold.
nts
(backward
direction)
8 Average FD Average FD (usec) during Yes Yes Yes Microseco Counter64 Counter64
the interval. nds
9 Maximum Maximum FD (used) Yes Yes Yes Microseco Counter64 Counter64

FD during the interval. nds
10 Minimum FD Minimum FD (usec) Yes Yes Yes Microseco Counter64 Counter64

during the interval. nds
11 Average FDV Average FDV (usec) during Yes Yes Yes Microseco Counter64 Counter64
(forward the interval in forward nds
direction) direction.
12 Average FDV Average FDV (usec) during Yes Yes Yes Microseco Counter64 Counter64
(backward the interval in backward nds
direction) direction
13 Minimum Minimum FDV (usec) Yes Yes Yes Microseco Counter64 Counter64
FDV during the interval in nds
(forward forward direction
direction)
14 Maximum Maximum FDV (usec) Yes Yes Yes Microseco Counter64 Counter64
(forward forward direction
direction)
15 Minimum Minimum FDV (usec) Yes Yes Yes Microseco Counter64 Counter64
(backward backward direction
direction)
16 Maximum Maximum FDV (usec) Yes Yes Yes Microseco Counter64 Counter64
(backward backward direction
direction)
SLM session Level per Remote MEP per MA
1 SLM Frames Number of transmitted Yes Yes Yes Packets Counter64 Counter64
Transmitted SLM frames (i.e. number
of initiated
measurements)
2 SLR Frames Number of received SLR Yes Yes Yes Packets Counter64 Counter64
Received frames (i.e. number of
completed
measurements)
3 Last Far End Last Far End FLR for the Yes Yes Yes Percents 0~100% 0~100%
FLR remote MEP
4 Min Far End The minimum Far End FLR Yes Yes Yes Percents 0~100% 0~100%
FLR for the remote MEP
during this Measurement
Interval.

5 Max Far End The maximum Far End FLR Yes Yes Yes Percents 0~100% 0~100%
Interval.
6 Avg Far End The average Far End FLR Yes Yes Yes Percents 0~100% 0~100%
Interval.
7 Last Near Last Near End FLR for the Yes Yes Yes Percents 0~100% 0~100%
End FLR remote MEP
8 Min Near The minimum Near End Yes Yes Yes Percents 0~100% 0~100%
End FLR FLR for the remote MEP
Interval.
9 Max Near The Maximum Near End Yes Yes Yes Percents 0~100% 0~100%
End FLR FLR for the remote MEP
Interval.
10 Avg Near The average Near End FLR Yes Yes Yes Percents 0~100% 0~100%
End FLR for the remote MEP
Interval.
11 Far End SEW Number of Far End Yes Yes Yes Seconds 0~900 0~86400
Severely Errored
Windows (windows with
FLR >
MA_UNAVAIL_THRESH)
12 Near End Number of Near End Yes Yes Yes Seconds 0~900 0~86400
SEW Severely Errored
Windows (Wondows with
FLR >
MA_UNAVAIL_THRESH)
13 Far End UAS Number of seconds Yes Yes Yes Seconds 0~900 0~86400
evaluated as unavailable
in the forward direction.
14 Near End Number of seconds Yes Yes Yes Seconds 0~900 0~86400
UAS evaluated as available in
the backward direction.
Port Utilization
1 IN Maximum Maximum rate one of all Yes Yes Yes bps Counter64 Counter64
Rate polling periods since
(Kbps/Mbps) operation start to current
on rx direction.
2 IN Average Average rate since Yes Yes Yes bps Counter64 Counter64
Rate operation start to current
(Kbps/Mbps) on rx direction.
3 IN Current Current rate in this polling Yes Yes Yes bps Counter64 Counter64
Rate period on rx direction.
(Kbps/Mbps)

4 IN Maximum Maximum PPS one of all Yes Yes Yes PPS Counter64 Counter64
PPS polling periods since
operation start to current
on rx direction.
5 IN Average Average PPS since Yes Yes Yes PPS Counter64 Counter64
PPS operation start to current
on rx direction.
6 IN Current Current PPS in this polling Yes Yes Yes PPS Counter64 Counter64
PPS period on rx direction.
7 IN Maximum Maximum utilization one Yes Yes Yes Percents 0~100% 0~100%
Utilization of all polling periods since
(%) operation start to current
on rx direction.
8 IN Average Average utilization since Yes Yes Yes Percents 0~100% 0~100%
Utilization operation start to current
(%) on rx direction.
9 IN Current Current utilization in this Yes Yes Yes Percents 0~100% 0~100%
Utilization polling period on rx
(%) direction.
10 OUT Maximum rate one of all Yes Yes Yes bps Counter64 Counter64
Maximum polling periods since
Rate operation start to current
(Kbps/Mbps) on tx direction.
11 OUT Average rate since Yes Yes Yes bps Counter64 Counter64
Average operation start to current
Rate on tx direction.
(Kbps/Mbps)
12 OUT Current Current rate in this polling Yes Yes Yes bps Counter64 Counter64
Rate period on tx direction.
(Kbps/Mbps)
13 OUT Maximum PPS one of all Yes Yes Yes PPS Counter64 Counter64
Maximum polling periods since
PPS operation start to current
on tx direction.
14 OUT Average PPS since Yes Yes Yes PPS Counter64 Counter64
Average PPS operation start to current
on tx direction.
15 OUT Current Current PPS in this polling Yes Yes Yes PPS Counter64 Counter64
PPS period on tx direction.
16 OUT Maximum utilization one Yes Yes Yes Percents 0~100% 0~100%
Maximum of all polling periods since
Utilization operation start to current
(%) on tx direction.
17 OUT Average utilization since Yes Yes Yes Percents 0~100% 0~100%
Average operation start to current
Utilization on tx direction.
(%)
18 OUT Current Current utilization in this Yes Yes Yes Percents 0~100% 0~100%
Utilization polling period on tx
(%) direction.

19 Link Down Link down time since Yes Yes Yes Seconds 0~900 0~86400
Seconds (s) operation start time to
current.
In-band MCC Network Interface (NI)
1 Rx Octets Number of bytes received Yes Yes Yes Bytes Counter64 Counter64
for this in-band MCC NI
2 Rx Pkts Number of packets Yes Yes Yes Packets Counter64 Counter64

received for this in-band
MCC NI
3 Rx Drop Number of received bytes Yes Yes Yes Bytes Counter64 Counter64
Octets dropped for this NI
4 Rx Drop Pkts Number of received Yes Yes Yes Packets Counter64 Counter64
packets dropped for this
NI
5 Tx Octets Transmited total number Yes Yes Yes Bytes Counter64 Counter64
of bytes for this in-band
MCC NI
6 Tx Pkts Transmited total number Yes Yes Yes Packets Counter64 Counter64
of good packets for this
in-band MCC NI
7 Tx Drop Number of bytes dropped Yes Yes Yes Bytes Counter64 Counter64
Octets for this NI before
transmitting, due to rate
limit.
8 Tx Drop Pkts Number of packets Yes Yes Yes Packets Counter64 Counter64
dropped for this NI before
transmitting, due to rate
limit.
GRE enabled MoE
1 Rx TL Error Received and dropped Yes Yes Yes Packets Counter64 Counter64
Pkts total number of packets
due to Total Length
mismatch
2 Rx IP Received and dropped Yes Yes Yes Packets Counter64 Counter64

address total number of packets
Error Pkts due to IP address
mismatch

3.5.5 OTN PM Counters and TCA

Table 3-10: OTN PM counters and TCA
No. Counter Description Current NE History NE History EMS Values 15-Min valid 24-Hrs valid TCA
value value
OTU2/OTU2e/OTU2f (Optical Transport Unit)
1 FEC-CE FEC corrected Yes Yes Yes Error count 0~100,000,00 0~10, Y
errors. 0 000,000,000
[100000 – [100000]
100]
for any OTUk
for any OTUk
2 BBE-NE Background Yes Yes Yes Error count 0- 11,072,610 0 - Y

block error Near for OTU2; 1,062,970,56
end. 0 for OTU2;
0-
An errored block 11,459,655 0-
not occurring as for OTU2e; 1,100,126,88
part of SES. 0 for OTU2e;
0 -11,701,710
for OTU2f; 0-
1,123,364,16
[10000 -200]
0 for OTU2f;
[40000]
0 -2,756,835 264,656,160
for OTU1; for OTU1;
[2500 -50] [10000]
3 ES-NE ES Near end. Yes Yes Yes Seconds 0~900 0~86400 Y

1-second period [180, 20] [1500]
which contains
at least one
errored blocks or
at least one
defect.
4 SES-NE SES Near end. Yes Yes Yes Seconds 0~810 0~77760 Y
1-second period [15, 0] [100]
which contains
≥15% errored
blocks or at least
one defect.
5 UAS-NE Unavailable Yes Yes Yes Seconds 0~900 0~86400 N

seconds Near
end.
6 OFS Out-frame Yes Yes Yes Seconds 0~900 0~86400 N

seconds.
The counter shall
be increased if at
least one Out Of
Frame defect
occurred during
a second.

value value
7 BBE-FE Background Yes Yes Yes Error count 0- 11,072,610 0 - Y

block error Far for OTU2; 1,062,970,56
end. 0 for OTU2;
0-
not occurring as for OTU2e; 1,100,126,88
part of SES-FE. 0 for OTU2e;
0 -11,701,710
for OTU2f; 0-
1,123,364,16
[10000, 200] 0 for OTU2f;
[40000]
0 -2,756,835 264,656,160
for OTU1; for OTU1;
[2500 -50] [10000]
8 ES-FE ES Far end. Yes Yes Yes Seconds 0~900 0~86400 Y

1-second period [180, 20] [1500]
which contains
at least one
errored blocks or
at least one
defect.
9 SES-FE SES Far end. Yes Yes Yes Seconds 0~810 0~77760 Y
1-second period [15, 0] [100]

which contains
≥15% errored
blocks or at least
one defect.
10 UAS-FE Unavailable Yes Yes Yes Seconds 0~900 0~86400 N

second Far end.
ODUk PM
1 BBE-NE Background Yes Yes Yes Error count 0- 11,072,610 0 - Y

block error Near for ODU2; 1,062,970,560
end. for ODU2;
0-
not occurring as for ODU2e; 1,100,126,880
part of SES. for ODU2e;
0 -11,701,710
for ODU2f; 0-
1,123,364,160
[10000, 200]
for ODU2f;
[40000]
0 -2,756,835 264,656,160
for ODU1; for ODU1;
[2500, 50] [10000]
0 – 1,372,545 0 –
for ODU0; 131,764,320
for ODU0;
[1250, 25]
[5000]

value value
0-9,377,505 0–
for 900,240,480
ODUF-FC800; for
ODUF-FC800;
[10000, 200]
[40000]
0-4,688,820 0–
for 450,126,720
ODUF-FC400; for
ODUF-FC400;
[3000, 50]
[20000]
0-3,309,795 0–
for 317,740,320
ODUF-SDI3G; for
ODUF-SDI3G;
0-3,306,489
for 0–
ODUF-SDI3G- 317,086,110
NA; for
ODUF-SDI3G-
[2500, 50] NA;
[10000]
2 ES-NE Errored second Yes Yes Yes Seconds 0~900 0~86400 Y

Near end.
[180, 20] [1500]
1-second period
which contains
at least one
errored blocks or
at least one
defect.
3 SES-NE Severely errored Yes Yes Yes Seconds 0~810 0~77760 Y

second Near
end. [15, 0] [100]
1-second period
which contains
≥15% errored
blocks or at least
one defect.
4 UAS-NE Unavailable Yes Yes Yes Seconds 0~900 0~86400 N

seconds Near
end.
5 BBE-FE Background Yes Yes Yes Error count 0- 11,072,610 0 - Y

block error Far for ODU2; 1,062,970,560
end. for ODU2;
0-
not occurring as for ODU2e; 1,100,126,880
part of SES-FE for ODU2e;
0 -11,701,710
for ODU2f; 0-
1,123,364,160
[10000, 200] for ODU2f;
[40000]
0 -2,756,835 264,656,160
for ODU1; for ODU1;
[2500, 50] [10000]

value value
0 – 1,372,545 0 –
for ODU0; 131,764,320
for ODU0;
[1250, 25]
[5000]
0-9,377,505 0–
for 900,240,480
ODUF-FC800; for
ODUF-FC800;
[10000, 200]
[40000]
0-4,688,820 0–
for 450,126,720
ODUF-FC400; for
ODUF-FC400;
[3000, 50]
[20000]
0-3,309,795 0–
for 317,740,320
ODUF-SDI3G; for
ODUF-SDI3G;
0-3,306,489
for 0–
ODUF-SDI3G- 317,086,110
NA; for
ODUF-SDI3G-
[2500, 50] NA;
[10000]
6 ES-FE Errored second Yes Yes Yes Seconds 0~900 0~86400 Y

Far end.
[180, 20] [1500]
1-second period
which contains
at least one
errored blocks or
at least one
defect
7 SES-FE Severely errored Yes Yes Yes Seconds 0~810 0~77760 Y

second Far end.
[15, 0] [100]
1-second period
which contains
≥15% errored
blocks or at least
one defect.
8 UAS-FE Unavailable Yes Yes Yes Seconds 0~900 0~86400 N

second far end.
9 TSE Test Sequence Yes Yes Yes Error count 0- 10,000,000 0 - Y

Error. for all ODUk 1,000,000,000
and ODUFlex; for all ODUk
Counts the and ODUFlex;
number of
invalid test
pattern. [250, 5] [1000]
OTN Port-STM
1 BBE Near-end Yes Yes Yes Error count 0-2159100 0-207273600 Y

Background
block error [9000, 200] [48000]

value value
2 OFS Number of out of Yes Yes Yes Seconds 0~900 0~86400 N

frame seconds
accumulated
3 ES Number of Yes Yes Yes Seconds 0~900 0~86400 Y

Errored seconds
[180, 20] [1500]
near end
accumulated
4 SES Number of Yes Yes Yes Seconds 0~810 0~77760 Y

Severely errored
seconds near [15, 0] [100]
end
accumulated. If
30% frames are
errored, this
second is SES.
5 UAS Number of Yes Yes Yes Seconds 0~900 0~86400 N

unavailable
seconds near
end accumulated
OTN Port-OC
1 CV-S Section Coding Yes Yes Yes Error count counter64 counter64 Y
Violations
[16383 [1048575
a count of BIP blocks] blocks]
errors detected
at the Section
layer
2 SEFS-S Section Severely Yes Yes Yes Seconds 0~900 0~86400 N

Errored Framing
Seconds
3 ES-S errored seconds. Yes Yes Yes Seconds 0~900 0~86400 Y

If errors occur
within a certain [180] [1500]
second, this
second is
called an errored
second.
4 SES-S severely errored Yes Yes Yes Seconds 0~810 0~77760 Y

seconds. If there
are errors in 30% [15] [100]
of the frames,
the
errors exceed
the threshold, or
the signal fails
within a certain
second, this
second is called a
severely errored
second. Errored
seconds (ESs) are
not
counted when
severely errored
seconds occur.

value value
OTN Port - ETY1G/ETY1Ge
1 PCS-LCV PCS Errored Yes Yes Yes Error count counter64 counter64 N
Blocks, counts
the number of
times of entering
to Error state
(Errored Blocks
or sequence) or
Line Code
Violation
2 PCS-ES Number of PCS Yes Yes Yes Seconds 0~900 0~86400 Y

Errored seconds
near end [180, 20] [1500]
accumulated.
Rx_LCV or LOS,
LOSYNC, Hi-BER
3 PCS-SES Number of PCS Yes Yes Yes Seconds 0~810 0~77760 Y

Severely errored
[15, 0] [100]
seconds near
end
accumulated. If
30% Rx_LCV are
errored or LOS,
LOSYNC, Hi-BER,
this second is
SES.
4 PCS-UAS Number of PCS Yes Yes Yes Seconds 0~900 0~86400 N

unavailable
seconds near
end accumulated
5 GFP-ES Number of GFP Yes Yes Yes Seconds 0~900 0~86400 Y

Errored seconds
near end [180, 20] [1500]
accumulated.
6 GFP-SES Number of GFP Yes Yes Yes Seconds 0~810 0~77760

Y
Severely errored
end
accumulated.
7 GFP-UAS Number of GFP Yes Yes Yes Seconds 0~900 0~86400 N

unavailable
seconds near
end accumulated
OTN Port -ETY10GOC
1 PCS-LCV PCS Errored Yes Yes Yes Error count 0…2^64-1 0…2^64-1 Y
Blocks, counts
the number of [90, 2] (without 24H
times of entering TCA)
to Error state
(Errored Blocks
or sequence) or
Line Code
Violation

value value

Errored seconds
[180, 20] [1500]
near end
accumulated.
Rx_LCV or LOS,
LOSYNC, Hi-BER

Severely errored
end
accumulated. If
30% Rx_LCV are
errored or LOS,
LOSYNC, Hi-BER,
this second is
SES.

unavailable
seconds near
end accumulated
OTN Port -ETY10G
Blocks, counts
TCA)
times of entering
to Error state
(Errored Blocks
or sequence) or
Line Code
Violation

Errored seconds
near end [180, 20] [1500]
accumulated.
Rx_LCV or LOS,
LOSYNC, Hi-BER

Severely errored
end
accumulated. If
30% Rx_LCV are
errored or LOS,
LOSYNC, Hi-BER,
this second is
SES.

unavailable
seconds near
end accumulated
5 GFP-ES Number of GFP Yes Yes Yes Seconds 0~900 0~86400 Y

Errored seconds
near end [180, 20] [1500]
accumulated.

value value
6 GFP-SES Number of GFP Yes Yes Yes Seconds 0~810 0~77760 Y

Severely errored
[15, 0] [100]
seconds near
end
accumulated.
7 GFP-UAS Number of GFP Yes Yes Yes Seconds 0~900 0~86400 N

unavailable
seconds near
end accumulated
8 GFP-Rx Received total Yes Yes Yes counters counter64 counter64 N

Octets number of bytes
for all good
packets
(Unicast+Multica
st+Broadcast).
9 GFP-Rx Pkts Received total Yes Yes Yes counters counter64 counter64 N
number of good
packets
(Unicast+Multica
st+Broadcast).
10 GFP-Tx Transmited total Yes Yes Yes counters counter64 counter64 N

Octets number of bytes
for all good
packets
(Unicast+Multica
st+Broadcast).
11 GFP-Tx Pkts Transmited total Yes Yes Yes counters counter64 counter64 N
number of good
packets
(Unicast+Multica
st+Broadcast).
12 GFP-Rx Error Received total Yes Yes Yes counters counter64 counter64 N
Pkts number of
dropped packets,
Includes all bad
packets and
dropped good
packets.
13 GFP-Rx FCS Received total Yes Yes Yes counters counter64 counter64 N
Error Pkts number of
packets which
have FCS error.
14 GFP-Rx GFP Received total Yes Yes Yes counters counter64 counter64 N
header Error number of
Pkts packets which
have GFP header
error.

value value
OTN Port -FC1200/FC800/FC400/FC200/FC100
Blocks, counts
times of entering TCA)
to Error state
(Errored Blocks
or sequence) or
Line Code
Violation

Errored seconds
near end [180, 20] [1500]
accumulated.
Rx_LCV or LOS,
LOSYNC, Hi-BER

Severely errored
[15, 0] [100]
seconds near
end
accumulated. If
30% Rx_LCV are
errored or LOS,
LOSYNC, Hi-BER,
this second is
SES.

unavailable
seconds near
end accumulated
OTN Port -CBR (VIDEO270, HDSI1485, HDSDI3G)
1 ES caused by LOS Yes Yes Yes Seconds 0~900 0~86400 Y

only
[180, 20] [1500]
2 SES caused by LOS Yes Yes Yes Seconds 0~810 0~77760 Y

only
[15, 0] [100]
3 UAS caused by LOS Yes Yes Yes Seconds 0~900 0~86400 N

only
GCC
1 RX-Octets Number of bytes Yes Yes Yes Bytes Counter64 Counter64 N

received
2 RX-Packets Number of good Yes Yes Yes Packets Counter32 Counter32 N

packets received
3 TX-Octets Number of bytes Yes Yes Yes Bytes Counter64 Counter64 N

transmitted
4 TX-Packets Number of good Yes Yes Yes Packets Counter32 Counter32 N

packets
transmitted
successfully

value value
5 Discard-RX-O Number of bytes Yes Yes Yes Bytes Counter64 Counter64 N

ctets discard in Rx
direction
6 CRC-Error-cnt CRC error Yes Yes Yes Packets Counter32 Counter32 N

packets
7 Mflr-Error-cn Malform error Yes Yes Yes Packets Counter32 Counter32 N

t packets due to
frame size
abnormal
8 Busy-Error-cn error packets Yes Yes Yes Packets Counter32 Counter32 N

t due to Rx BD no
empty
9 RX-Error-Pkts Number of error Yes Yes Yes Packets Counter32 Counter32 Y

packets received,
it is [100, 10]
CRC-Error-cnt +
Mflr-Error-cnt +
Busy-Error-cnt
10 TX-Error-Pkts Number of Yes Yes Yes Packets Counter32 Counter32 Y

transmit fail
events, it is error [100, 10]
packets due to
Tx underrun
(underrun-Error-
cnt)
PM counters for ETY1G, ETY1Ge, ETY10G, ETY10GOC
1 Rx Octets Received total Yes Yes Yes Bytes counter64 counter64

number of bytes
for all good
packets
(Unicast+Multica
st+Broadcast).
2 Rx Good Sum of payload Yes Yes Yes Bytes counter64 counter64

Octets and padding
octets of frames
received without
errors.
3 Rx Bad Octets Sum of payload Yes Yes Yes Bytes counter64 counter64 Y
and padding
octets of frames [1000. 20]
received with
errors.
4 Rx Pkts Received total Yes Yes Yes Packets counter64 counter64

number of good
packets
(Unicast+Multica
st+Broadcast).
5 Rx Good Pkts Number of Yes Yes Yes Bytes counter64 counter64

frames received
without error
(including Pause
frames).

value value
6 Rx Bad Pkts RX_ERR_FRAMES Yes Yes Yes Bytes counter64 counter64 Y

Number of [100, 2]
frames received
with error:
• CRC error.
• Length error.
• Alignment
error.
7 Rx Broadcast Received total Yes Yes Yes Packets counter64 counter64

Pkts number of good
Broadcast
packets.
8 Rx Multicast Received total Yes Yes Yes Packets counter64 counter64

Pkts number of good
Multicast
packets.
9 Rx Unicast Number of valid Yes Yes Yes Bytes counter64 counter64

Pkts received Unicast
frames.
10 Tx Octets Transmited total Yes Yes Yes Bytes counter64 counter64

number of bytes
for all good
packets
(Unicast+Multica
st+Broadcast).
11 Tx Good Sum of payload Yes Yes Yes Bytes counter64 counter64

Octets and padding
octets of frames
transmitted
without errors.
12 Tx Bad Sum of payload Yes Yes Yes Bytes counter64 counter64 Y

Octets and padding
[1000. 20]
octets of frames
transmitted with
errors.
13 Tx Pkts Transmited total Yes Yes Yes Packets counter64 counter64

number of good
packets
(Unicast+Multica
st+Broadcast).
14 Tx Good Pkts Number of Yes Yes Yes Bytes counter64 counter64

frames
transmitted
without error
(including Pause
frames).

value value
15 Tx Bad Pkts TX_ERR_FRAMES Yes Yes Yes Bytes counter64 counter64 Y

Number of [100, 2]
frames
transmitted with
error:
• CRC error.
• Length error.
• Alignment
error.
16 Rx FCS error Number of Yes Yes Yes Packets counter64 counter64

Pkts frames received
with a CRC error
and legal
termination. This
count does not
include frames
that are marked
too long or too
short.
17 Rx Pkts 64 Received total Yes Yes Yes Packets counter64 counter64

number of good
packets with size
of 64bytes.

65-127 number of good
packets with size
of from 65 to
127 bytes.

packets with size
of from 128 to
255 bytes.

packets with size
of from 256 to
511 bytes.

packets with size
of from 512 to
1023 bytes.

packets with size
of from 1024 to
1518 bytes.
23 Rx 1519-Max Received total Yes Yes Yes Packets counter64 counter64

Frame Size number of good
packets with size
of from 1519 to
max frame size
bytes.

value value
24 Rx Undersize Received total Yes Yes Yes Packets counter64 counter64

Pkts number of bad
packet which
meets all the
following
conditions:
 Packet
length is
less than
64bytes.
 Packet has
valid CRC.
 Collision
event has
not been
detected.
25 Rx Oversize Received total Yes Yes Yes Packets counter64 counter64

Pkts number of bad
packet which
meets all the
following
conditions:
 Packet
length is
larger than
MTU.
 Packet has
valid CRC.
 Collision
event has
not been
detected.
26 Rx Pause Pkts Received total Yes Yes Yes Packets counter64 counter64
number of Pause
frames.
27 Rx Fragments Total number of Yes Yes Yes Events counter64 counter64

Pkts frames received
that are shorter
than 64 bytes
and have bad
CRC.
28 Rx Good Contains a count Yes Yes Yes Packets counter64 counter64

Jumbo Pkts of good jumbo
frames received
by the device.
Jumbo frames
are defined as
frames greater
than 1518 bytes
(excluding
framing bits but
including FCS).
NOTE: In the above table:

 The value in [Bracket] is default TCA value. If two values in [Bracket], they are enter and
exit threshold respectively; if only one vaule in [Bracket], then only one threshold is using.
 PM Counters with Italic format is different as ETY&L2 port.

3.5.6 CES Service PM Counters and TCA

Table 3-11: CES Service PM counters and TCA
No. Counter Description Current PM History PM ASCII Values 15-Min valid 24-Hrs valid TCA
Export value value
CES Interface
1 AdminDownS Time in Sec when Yes Yes Yes Seconds 0~900 0~86400 N
ec Admin state of the
CES interface is
Down
2 OperDownSe Time in Sec when Yes Yes Yes Seconds 0~900 0~86400 N
c Oper state of the
CES interface is
Down
3 TxPsnPkts Number of packets Yes Yes Yes Packets Counter64 Counter64 N

sent
4 TxPsnOctets Number of octets Yes Yes Yes Bytes Counter64 Counter64 N

sent
5 TxPsnDiscard Number of packets Yes Yes Yes Packets Counter64 Counter64 N

Pkts not sent
6 TxPsnDiscard Number of octets Yes Yes Yes Bytes Counter64 Counter64 N

Octets not sent
7 RxPsnOverru Number of buffer Yes Yes Yes Error count Counter64 Counter64 N
nEvents overrun events
8 RxPsnUnderr Number of buffer Yes Yes Yes Error count Counter64 Counter64 N
unEvents underrun events
9 RxPsnLopsEve Number of PSN Yes Yes Yes Error count Counter64 Counter64 N
nts Failure events
10 RxPsnSwitcho Number of Yes Yes Yes Error count Counter64 Counter64 N

verEvents sequence number
switchover events
11 RxPsnValidPkt Number of valid Yes Yes Yes Packets Counter64 Counter64 N

s packets received
and delivered to
TDM port
12 RxPsnValidOc Number of valid Yes Yes Yes Bytes Counter64 Counter64 N

tets octets received
and delivered to
TDM port
13 RxPsnReorder Number of packets Yes Yes Yes Packets Counter64 Counter64 N

Pkts received and were
reordered
successfully
14 RxPsnLbitDisc Number of packets Yes Yes Yes Packets Counter64 Counter64 N

ardPkts received with L-bit
set and discarded
15 RxPsnStrayDis Number of stray Yes Yes Yes Packets Counter64 Counter64 N

cardPkts packest received
and discarded

Export value value
16 RxPsnMalfor Number of Yes Yes Yes Packets Counter64 Counter64 N

mDiscardPkts malformed packets
received and
discarded
17 RxPsnDuplica Number of packets Yes Yes Yes Packets Counter64 Counter64 N

tDiscardPkts received with SN
already in jitter
buffer
18 RxPsnOowDis Number of packets Yes Yes Yes Packets Counter64 Counter64 N

cardPkts received out of
window (cannot be
reordered)
19 RxPsnOverru Number of packets Yes Yes Yes Packets Counter64 Counter64 N

nDiscardPkts received and
discarded for
causing overrun
20 RxPsnLostPkt Number of packets Yes Yes Yes Packets Counter64 Counter64 Y

s received and
categorized as lost
Equals:
RxPsnMalformDisc
ardPkts+
RxPsnLbitDiscardPk
ts+
21 RxPsnLostOct Number of ocets Yes Yes Yes Bytes Counter64 Counter64 N

ets received and
categorized as lost
22 RxPsnPattern Number of packets Yes Yes Yes Packets Counter64 Counter64 N

Packets received as lost or
not received, and
were thereby
replaced by the
predefined pattern
23 RxPsnPattern Number of octets Yes Yes Yes Bytes Counter64 Counter64 N

Octets received as lost or
not received, and
were thereby
replaced by the
predefined pattern
24 RxPsnLbitSec Number of seconds Yes Yes Yes Seconds Counter64 Counter64 N

during which L-bit
was set in received
packets
25 RxPsnRbitSec Number of seconds Yes Yes Yes Seconds Counter64 Counter64 N

during which R-bit
was set in received
packets
26 RxPsnLMbitSe Number of seconds Yes Yes Yes Seconds Counter64 Counter64 N

c during which
(L,M)=(0,10) in
received packets
27 RxPsnES Number of Error Yes Yes Yes Seconds Counter64 Counter64 N

Seconds (ES)

Export value value
28 RxPsnSES Number of Yes Yes Yes Seconds Counter64 Counter64 N

Severely Error
Seconds (SES)
29 RxPsnUAS Number of Yes Yes Yes Seconds Counter64 Counter64 N

Unavailable
Seconds (UAS)
30 RxPsnRecClkF Number of Yes Yes Yes Count Counter64 Counter64 N

reeRunEvents transitions of
RecClkState from
any state to
Freerun
31 RxPsnRecClkP Number of Yes Yes Yes Count Counter64 Counter64 N

MSMEvents transitions of
RecClkState from
Normal to PMSM
32 RxPsnRecClkH Time during which Yes Yes Yes Seconds Counter64 Counter64 N
oldoverTime RecClkState
was Holdover
33 LdpInNotifica Number of LDP Counter64 Counter64 N

tionStatus0x2 Notification
4 packets received
with this status
data

6 packets received
with this status
data

7 packets received
with this status
data

A packets received
with this status
data
37 RxPsnDenied Number of packets Yes Yes Yes Packets Counter64 Counter64 N

Pkts received and
discarded for other
bad formatting
38 RxPsnGapsPkt Number of gaps in Yes Yes Yes Packets Counter64 Counter64 N

s jitter buffer, due to
which a
replacement
pattern was sent
PM Common for CESoETH service (CES over PB P2P and CES over PB MP2MP)
1 AdminDownS Time in Sec when Yes Yes Yes Seconds 0~900 0~86400 N
ec Admin state of the
CES service is
Down

Export value value
2 OperDownSe Time in Sec when Yes Yes Yes Seconds 0~900 0~86400 N
c Oper state of the
CES service is
Down
PM for CES service - PB P2P
1 APSSwitchEve The number of Yes Yes Yes Count Counter64 Counter64 N

nt VLAN 1+1
Switchover events
PM for CES service - PB MP2MP
1 BSCConform Number of Yes Yes Yes Bytes Counter64 Counter64 N

Octets multicast,
broadcast, and
unknow
destination unicast
bytes received by
all ports for this
VPN
2 BSCDropped Number of Yes Yes Yes Bytes Counter64 Counter64 N

Octets multicast,
broadcast, and
unknow
destination unicast
bytes dropped by
BSC policer of this
VPN
3 BSCDroppedP Number of Yes Yes Yes Packets Counter64 Counter64 N

ackets multicast,
broadcast, and
unknow
destination unicast
packets dropped
by BSC policer of
this VPN
4 BSCAverageR The Average Rate Yes Yes Yes bps 0~No Rate 0~No Rate N
ate of MC, BC and Limit Limit
Unkown packets in
the monitored
seconds
5 BSCUtilization BSCAverageRate/B Yes Yes Yes Percents 0~100% 0~100% N

SCCIR *100/%
6 QuotaDropPa Number of packets Yes Yes Yes Packets Counter64 Counter64 Y

ckets dropped due to
exceed the vFIB
quota

3.5.7 CES Port PM Counters and TCA

Table 3-12: CES port PM counters and TCA
Export value value
E1-PPI
1 E1CV Coding Violations Yes Yes Yes Error count Counter32 Counter32 Y
2 E1ES_PPI Errored seconds. a Yes Yes Yes Seconds 0~900 0~65535 Y

count of seconds
during which one
or more of the
following has
occurred: CVs,
LOSs.
3 E1SES_PPI Severely errored Yes Yes Yes Seconds 0~900 0~65535 Y

seconds. If there
are errors in 30%
of the frames, the
errors exceed the
threshold, or the
signal fails within a
certain second, this
second is called a
severely errored
second. Errored
seconds (ESs) are
not counted when
severely errored
seconds occur.
4 E1LOSS-PPI A count of Yes Yes Yes Seconds 0~900 0~65535 N

1-second intervals
containing one or
more LOS defects.
DS1-LINE
1 DS1ES-L Errored seconds. a Yes Yes Yes Seconds 0~900 0~65535 Y

count of seconds
during which one
or more of the
following has
occurred: BPVs,
EXZs, and LOSs.
2 DS1SES-L Severely errored Yes Yes Yes Seconds 0~900 0~65535 Y

seconds. If there
are errors in 30%
of the frames, the
errors exceed the
threshold, or the
signal fails within a
certain second, this
second is called a
severely errored
second. Errored
seconds (ESs) are
not counted when
severely errored
seconds occur.

Export value value
3 DS1CV-L Coding Violations. Yes Yes Yes Error count Counter32 Counter32 Y
The Coding
Violations is the
block error with
the number of
severely errored
seconds deducted
from the
counting interval.
4 DS1FEES-L Far-end errored Yes Yes Yes Seconds 0~900 0~65535 Y

seconds.
5 DS1LOSS-L A count of Yes Yes Yes Seconds 0~900 0~65535 N

1-second intervals
containing one or
more LOS defects.

4 Performing Maintenance Operations
This section discusses how to perform routine maintenance operations on the cards and internal objects.
4.1 Preventive Maintenance Operations

This section describes how to perform preventive maintenance operations.
Parent Topic
4.1.1 Saving NE Configuration Data

This operation is only available for the BG-40 NE. You can manually save all BG-40 NE configuration data to
the flash and use it to restore the BG-40 NE when necessary.
To save NE configuration data:

 In the BG-40 NE Shelf View window, on the menu, select Maintenance and then Save NE
Configuration.
Parent Topic
4.1.2 Clearing NE Configuration Data

This operation restores all configurations within an NE to their initial status by clearing all configuration
data in the NE equipment, including data and trail information.
To clear NE configuration data:

1. In the NE Shelf View window, on the main menu, select Maintenance and then Clear NE's
Configuration. A Confirmation window opens, prompting you to confirm clearing the data.
2. Click Yes to confirm.
Parent Topic

EMS-APT® Performance Management Guide Performing Maintenance Operations
4.1.3 Checking Configuration Consistency

This section describes how to check the configuration consistency between the EMS-APT and the
equipment. Key configuration data is traffic-affecting data, such as slots, cards, VCG allocation, XCs, and
maintenance.
If NE key configuration data is inconsistent with the EMS-APT, the inconsistency icon is displayed in
the lower-right corner of the NE icon.
To check configuration consistency:

 Select the inconsistently configured NEs in the topology view, and on the main menu, select
Maintenance and then Full Upload NE Data. The EMS-APT uploads all the configuration data from the
equipment and saves it to the DB. If the operation succeeds, all NEs’ configuration is consistent with
the EMS-APT, and the icon in the corner disappears. If the operation fails, the NEs’ configuration
remains inconsistent with the EMS-APT.
To manage the inconsistent NE list:

1. In the EMS-APT main window, do not select any NE, and on the main menu, select Maintenance and
then View Inconsistent NE List. The Inconsistent NE List window opens.
2. To check the signature of the NEs, select the NEs in the window, and on the toolbar click the Check
Signature icon . A Confirmation window opens. Click Yes to check the signature.

3. To upload NE data, select the NEs, and on the toolbar click . A Confirmation window opens. Click
Yes to upload the NE data.
Parent Topic
4.1.4 Testing Connectivity

This operation sends a ping to the NE equipment to verify the connection to the NE equipment. The ping
checks the connection between a local host and the network by sending one Internet Control Message
Protocol (ICMP) ECHO packet to the host over the network, and subsequently monitoring the returned
ECHO REPLY packet. This operation can only be performed at the system operation level.
To perform connectivity testing:

1. In the EMS topology view, select an NE, and on the main menu, select Maintenance and then Ping.
The following Ping window opens.
2. Set the size of a ping test packet by entering a numeric value in the Package Size field.

3. Click Ping. The returned ping results are displayed.
4. To cancel the ping test, click Stop Pinging. The display area shows the ping statistics.
5. To clear the contents in the display area, click Clear Result.
Parent Topic
4.1.5 Performing a Fully Upload

This operation uploads all the configuration data on the equipment, including SDH, Ethernet, and PCM
configuration. All configuration data is saved in the EMS-APT DB to maintain consistency between the
EMS-APT and the equipment. An option is available to optimize the full upload.
To perform a fully upload:

1. In the EMS-APT main window, select the NE you want to upload, and on the main menu, select
Maintenance and then Fully Upload. Or, in the NE Shelf View window, in the left object tree, select
the NE, and from the menu, select Maintenance and then Fully Upload. The following confirmation
window opens.

3. To view the upload status, on the main menu, select Maintenance and then View Upload Status. The
following window opens.
4. Click the Details button to view the detailed information of the upload status.
5. To view error tasks, select the Error Tasks tab.
Parent Topic
4.1.6 Performing a Fully Download

This operation downloads all the configuration data from the equipment, including SDH, Ethernet, and PCM
configuration.

To perform a fully download:

1. In the EMS-APT main window, select the NE you want to download, and on the main menu, select
Maintenance, Advanced and then Fully Download NE Data. Or, in the NE Shelf View window, in the
left object tree select the NE, and from the menu, select Maintenance, Advanced and then Fully
Download NE Data. The following confirmation window opens.

3. To view the download status, on the main menu, select Maintenance, Advanced and then View
Download Status. The details are displayed about 10 minutes after the download operation.
Parent Topic

4.1.7 Performing a LED Test

All LEDs within an NE can be tested to verify the quality of the indicator hardware, and to improve the
reliability of the alarm indicator indications.
To perform a LED test:

1. In the NE Shelf View window, in the main menu, select Maintenance and then Test LED. A
Confirmation window opens.
2. Click Yes to perform test operations.
Parent Topic
4.1.8 Viewing Bit Codes

Built-In Test (BIT) provides the ability to reveal hardware failures in real time. There are three types of BIT:
 Power Up BIT: Power up BIT must take power up time into consideration (not to exceed power up
time limitation). Note that Power up BIT does not have traffic considerations (since there is no traffic
in power up), and can be destructive (can run tests that require initialization of HW devices on test
complete), can use devices testing mode, can consume most of the CPU resources (there is no other
important activity running on this time), etc.
 Periodic BIT: Periodic BIT must be non traffic affecting.
 Maintenance BIT
This section describes how to view the Bit codes in EMS-APT.

To view Bit codes:

1. In the NE Shelf View window, in the left object tree, select a card, and on the menu, select
Maintenance and then Bit Code. The Bit Code window opens.
2. To retrieve the information, click .
Parent Topic
4.1.9 Managing Defined Bit Code

You can manage defined BIT code for the following cards:
 All XIO cards
 MXC-1020
 MXP10
 DHFE_12
 DHFX_12
 CPTS100
 CPS100
 DMGE_4_L2
 DMGE_8_L2
 DMXE_22_L2

 DMXE_48_L2
 MPS_2G_8F
 MPoE_12G
 S1_4
To manage defined Bit code:

1. In the NE Shelf View window, in the left object tree, select a card. Then on the menu, select
Maintenance and then Defined Bit Code. The Defined Bit Code window opens.
2. To reload the information to view, on the toolbar, click .

3. To export the defined BIT code list to a CSV file, on the toolbar, click .
4. Select the location folder, enter the file name for the CSV file, and then click Save.
Parent Topic
4.1.10 Viewing PPI Status

The EMS-APT supports a Get PPI Status feature, which queries a loss of signal on each PDH interface. The
PPI status can be used to verify the cable connection status when installing the equipment. The PPI status is
obtained directly from the hardware and is not affected by the alarm filter.

To view the PPI status:

1. In the NE Shelf View window, in the object tree list, select an E1/E3 card, and then in the
Maintenance working mode, select the PPI Status tab.
2. To refresh the information manually, click . To refresh the information automatically:

a. Select the Refresh Data Dynamically checkbox.
b. Enter the refresh interval in the Refresh Interval field.
c. To refresh the PPI status, click Start.
d. To terminate the refresh process, click Stop.
Parent Topic

4.1.11 Performing Preventive Maintenance

The following table describes the preventive maintenance procedures you must carry out to ensure proper
operation.
Table 4-1: EMS-APT preventive maintenance procedures
Procedure When to perform

Save the NE DB configuration to Once a week, or following major changes in network topology
hard disk
Check version correspondence Once a week, or whenever major changes are made to system
configuration
Delete old system files Once a week, or following major changes in network topology
Check performance Once a week, or according to working procedures
Check EMS-APT to NE Once a week, or according to working procedures
communications
Save the EMS-APT configuration Once a week, or following major changes in network topology
to hard disk
Check switching to protection Once a quarter, according to network administrator's instructions
Note: This operation is traffic-affecting.
Export XC data to XML files Once a month, or according to working procedures
Check optical parameters Once a month, or according to working procedures
Export topology data to an XML Once a month, or according to working procedures
file
Export card inventory data to Once a month, or according to working procedures
an XML file
Parent Topic
4.2 Managing Databases

You can back up the EMS database to simplify network management and maintenance tasks.

To back up the DB:

1. In the EMS main window, on the main menu, select System, EMS DB, and then Backup Immediately.
The Backup EMS Database Immediately window opens.
2. Click Apply.
3. To backup to RDR server:
a. In the EMS main window, on the main menu, select System, EMS DB, and then RDR Settings. The
EMS Database RDR Backup Setting window opens.
b. Select the RDR Enable checkbox if you want it to work. If enabled, you can set the Backup to RDR
Server in the Backup EMS Database Immediately window.

You can also set an automatic time for EMS backup, as described below.
To perform backup settings:

1. In the EMS main window, on the main menu, select System, EMS DB, and then Backup Settings. The
EMS Database Backup Settings window opens.
2. In the Backup Mode area, select a mode as follows:

 Not Backup: Automatic backup is not allowed.
 Backup Date: Automatically back up the DB at the time you set.
 Periodic Backup: Automatically back up the DB periodically at the time you set.
3. In the Backup Directory field, enter the directory for saving the backup files.
Parent Topic

4.3 Performing Card Maintenance

4.3.1 Resetting a Card
When the physical device of a card does not work normally and needs to be initialized, a Card Reset
operation is performed. Both warm and cold resets are available.
A warm reset resets only the central processing unit of the cards, namely, it repositions the running of card
usage programs. A cold reset resets both the central processing unit and the peripheral hardware. Warm
resets do not affect traffic; cold resets do.
MXC-1020 supports Power on reset, which means the software can be used to power on the MXC-1020
directly.
To reset a card:
1. In the NE Shelf View window, in the left object tree, select a card.
2. From the menu select Maintenance and then Reset. The Reset Card window opens.
3. Select the reset mode as required and click OK to confirm. A confirmation window opens, prompting
you to confirm the reset.
4. To confirm reset, click Yes.

To perform Power on reset:

1. In the NPT-1020 NE Shelf View window, in the left object tree, select an MXC-1020 card.
2. From the menu select Maintenance and then Reset. The Reset Card window opens.
3. Select Power on reset and click OK. A confirmation window opens, prompting you to confirm the
reset.
4. To confirm reset, click Yes.
Parent Topic
4.3.2 Obtaining the SFP Type

The SFP type has two parameters that can be configured:
 Expected SFP Type
 Application Code
This section describes how to obtain the SFP type.

To obtain the SFP type:

1. In the NE Shelf View window, in the left object tree, select an oPort, and then in the Configuration
working mode, select the SFP Setting tab. The following window opens.

2. Select the required Expected SFP Type and the Application Code from the respective dropdown lists.
3. To retrieve the information to view, click .

4. To view WDM information of the SFP, in the left object tree, select an oPort under the card that
supports viewing actual WDM information. In the Configuration working mode, select the SFP Setting
tab.
The following WDM information is displayed:

 Module sub-type
 Application code
 Number of supported channels
 WDM first channel number
 Channel spacing
Parent Topic

4.3.3 Performing XFP Management

This section describes the management of the tunable-XFP (T-XFP) and OTN-XFP in STM-64, including:
 Managing T-XFP
 Managing OTN-XFP
 Viewing Serial ID
OTR10T_AL is a tunable DWDM XFP, and its wavelength (or frequency) is configurable between full ITU-T C
band channels with channel spacing of 50 GHz.
When OTN-XFP is assigned to a STM-64 port with OTN enabled, the port becomes an OTN interface (ONNI).
It can be connected to a port with the same OTN rate (OTU2) and it cannot be connected to an STM-64 port
without OTN XFP.
NOTE: From CPTS100 in EMS-APT V3, OTN-XFP (OTRN10_AL) can be assigned but OTN
function cannot be enabled – always work in “OTN pass through” mode, DWDM relevant
configuration remains as before. OTRN10 is handled as a regular tunable DWDM XFP.
To manage T-XFP:
1. In the BG-64/NPT-1200 NE Shelf View window, in the left object tree, select the oPort under XS
A:SAM64. In the Configuration working mode, select the XFP Setting tab.

2. In the Expected SFP Type dropdown list, select OTR10T. View the relevant parameters in the window
that opens.

To view XFP serial ID:

A:SAM64. In the Configuration working mode, select the Serial ID tab.
Parent Topic
4.3.4 Managing T-SFP+ Settings

T-SFP+ is tunable Dense wavelength division multiplexing (DWDM) SFP+ module, which wavelength (or
frequency) is configurable between full ITU-T C-band channels with channel spacing of 50GHz.
Following lists the T-SFP+ supported cards:
 CPTS100 – two 10GE ports of AMXE_2 (NPT-1200)
 DMXE_48_L2 – four 10GE ports (NPT-1200)
 DMXE_22_L2 – two 10GE ports (NPT-1200)
 CPS50 – two 10GE ports (NPT-1020/NPT-1021)

To manage T-SFP+ settings:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select a 10GE port under the T-SFP+
supported cards, and then in the Configuration working mode, select the SFP+ Setting tab.

2. Select OTP10T/OTP10T_2/OTP10T_17 in the Expected SFP Type dropdown list.

3. When OTP10T/OTP10T_2/OTP10T_17 is selected, the T-SFP area is available in the SFP+ Setting tab.
The parameters are described as below:

 Channel Selection
 Channel Frequency (f): Laser frequency of desired DWDM channel.
 Wavelength: Corresponding laser wavelength in nm concluded from the frequency input.
 Tuning Capability
 Frequency Tuning: Tunable DWDM (selection by channel, bytes 144-145).
 Wavelength Tuning: Tunable DWDM (selection in 50pm steps, bytes 146-147).
 Tx Dither Support: Support for Tx dithering.
 Tunable Range
 First Frequency: Laser first frequency in THz, read from actual SFP+.
 Last Frequency: Laser last frequency in THz, read from actual SFP+.
 Minimum Supported Grid Spacing: Laser minimum supported grid spacing in GHz, read
from actual SFP+.

 Tx Dither Setting
 Tx Dither: Enable Tx Dither or disable Tx Dither.
Parent Topic
4.3.5 OTN Wrapping for STM-16/64 Interface in CPTS100

For OTU1 interface:
You can set OTN enable/disable for SAM25_2 STM-16 interface. The attribute "OTU1 Wrapper" defines
whether STM-16 will be mapped to ODU1/OTU1 and becomes an OTU1 uplink. When OTU1 Wrapper is
enabled, the port becomes a OTU1 port, and relevant OTN objects shall be created:
 ODU1
 OTU1
For OTU2 interface:
You can set OTN enable/disable for SAM10 STM-64 interface. The attribute "OTU2 Wrapper" defines
whether STM-64 will be mapped to ODU2/OTU2 and becomes an OTU2 uplink. When OTU2 Wrapper is
enabled, the port becomes a OTU2 port, and relevant OTN objects are created:
 ODU2
 OTU2

To configure OTN Wrapping for STM-16/64 interface:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select the oPort (STM-64)/oPort
(STM-16) under SAM10/SAM25_2. Then in the Configuration working mode, select the OTN Setting
tab.
2. You can enable the OTN Wrapper as required. The default is disabled.

3. Click Apply to save the settings and you can view the oPort (OTN) in the object tree.
Parent Topic
4.3.6 OTN Wrapping for 10GE Interface in CPTS100/CPS100

From NPT-1200 V3, CPTS100 10GE ports support OTN encapsulation. The two 10GE ports of CPTS100
(AMXE_2) can support OTN encapsulation based on the 10GE PHY.
Following are the PHY types supported in 10GE port of AMXE_2:
 10GBase-R
 10GBase-W
 10GBase-R with OTU2e Mapping
 10GBase-W with OTU2 Mapping
You can activate or deactivate OTN by changing the PHY type. Relevant OTN objects will be created if the
PHY type is set as OTN mapping:
 10GBase-R with OTU2e Mapping --> OTU2e, ODU2e
 10GBase-W with OTU2 Mapping --> OTU2, ODU2

To activate/deactivate OTN for 10GE interface:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select the activated 10GE port under
AMXE_2. Then in the Configuration working mode, select the General tab.
2. You can activate or deactivate OTN by changing the PHY type.

3. Click Apply and the OTN for the 10GE interface is activated.
Parent Topic
4.3.7 Managing OTN in XIO64

The OTN-XFP module can work in two modes:
 OTN mode: OTN enabled
 OTN Bypass mode: OTN disabled. FEC is not supported in this mode.
When the OTN is enabled, the following objects are created:
 OPS: with alarm monitor; not displayed in the object tree.
 OTU2: with default OTU2 setting, alarm monitor, performance monitor, and TCA.
 ODU2: with default ODU2 setting, alarm monitor, performance monitor, and TCA.

To manage OTN-XFP:
A:SAM64. In the Configuration working mode, select the XFP Setting tab.

From the Expected SFP Type dropdown list, select OTRN10.
2. In the OTN XFP area, configure the attributes as described below:

 Operation Mode:
 OTN Enable
 OTN Bypass
 FEC Control: GFEC, EFEC or Off. It is only configurable when OTN is enabled.
 Selected Wavelength: 20 (192.0THz) or 21 (192.1THz).
3. To save your settings, click Apply. A warning window opens, prompting you to confirm this action.
Click Yes to continue.

4. To configure the parameters for OTU2, in the object tree, select the OTU2 object. In the
Configuration working mode, select the General tab.

5. To configure the parameters for ODU2, in the object tree, select the ODU2 object. In the
Configuration working mode, select the General tab.
Parent Topic

4.3.8 Performing Basic Parameter Backup in SFP

This section describes how to back up basic parameters in SFP for BG-20 NEs.
To back up basic parameters in SFP:

1. In the EMS-APT main topology view, on the main menu, select Maintenance and then Backup Basic
Parameter in SFP.
2. In the left-hand NE list, select the NEs by selecting the corresponding checkboxes. To select all NEs,
select the All NEs checkbox.

3. To obtain information to view, on the toolbar click .
4. In the Backup NE Basic Parameter in SFP list select the checkboxes as required, and click Apply to
back up the corresponding parameters.
Parent Topic
4.4 Performing Transmission Object Maintenance

Operations
The EMS-APT enables you to perform maintenance operations on transmission objects.
Parent Topic
4.4.1 Using the Maintenance List

The EMS-APT conveniently provides a graphical symbol above the NE icon in the EMS-APT main
window indicating that a maintenance operation has been performed on it. In addition, it also enables you
to view a list of the maintenance operations performed on an NE.

To use the maintenance list:

1. In the NE Shelf View window, from the menu, select the working mode Maintenance and then the
Maintenance List tab.
Or
In the EMS main window, select one or more NEs, and on the main menu, select Maintenance and
then Maintenance List. You can manage the NEs in the Muti-NE window.

2. To release maintenance operation data, select an operation from the list, and on the toolbar click
, or right-click and select Release from the shortcut menu.
Parent Topic
4.4 Performing Transmission Object Maintenance Operations
4.4.2 Performing/Releasing Loopback

The loopback operation is designed to aid in testing the service path and service interface. In this context,
loopback refers to a software loopback, meaning that it is set through the EMS-APT.
After an E2E trail has been configured, a loopback can be used to test whether the whole path works
normally and whether meters receive and send consistently. The absence of an error code indicates that
everything is working normally.
The loopback operation includes:
 Terminal (NE) loopback: Looping back signals from the XC unit to the same unit. The terminal
loopback operation can be used to test the flow of signals in the system.
 Facility (FE) loopback: Directly looping back signals received by the physical port to the output port
corresponding to it, without changing the signal structure. The facility loopback operation can be used
to test the connector.
NOTE: The loopback operation is traffic-affecting.

To perform a loopback:
1. In the NE Shelf View window, in the left object tree, select a card that has undergone maintenance
and requires a loopback. In the Maintenance working mode, select the Loopback tab.
2. Modify loopback parameters as required by selecting a loopback from the Loopback Type list.

3. To batch edit the loopback type, on the toolbar, click . Then click to select the required
operation as you need.
5. To refresh the information in the list, click .

To release a loopback:
1. In the above window, select the Maintenance List tab next to the Loopback tab and click to
refresh the data in the list.
2. From the list, you can see the loopback operations you performed. Select the loopback you want to
release, and on the toolbar click , or right-click the loopback and select Release from the shortcut
menu.
Parent Topic

4.4.3 Performing AIS/RDI
To perform AIS/RDI:
1. In an NE Shelf View window, in the left object tree, under all optical interface and service cards,
select the VC-4/VC-3/VC-12 or MS/RS module. In the Maintenance working mode, select the Force
Signal tab.

2. From the DownStream dropdown list, select the operation to be performed (either None or AIS).
3. From the UpStream dropdown list, select None, AIS, or RDI.

4. To insert the AIS/RDI, click Apply.
Parent Topic

4.4.4 Performing PRBS
To perform a PRBS:
1. In the NE Shelf View window, in the left object tree, select the required card and then select VC-4 or
PPI. In the Maintenance working mode, select the PRBS tab.
2. In the Generator Side area, perform PRBS generation as follows:

a. Set the Switch mode to On.
b. Specify the Generator Pattern.
c. Select the Invert Signal checkbox.
d. In the Direction field, select the Upstream or Downstream button.
e. Click Apply.
f. To insert an additional error bit, click the Add single bit error icon .
3. In the Monitor Side area, perform PRBS monitoring as follows:
a. Set the Switch mode to On.
b. Specify the Generator Pattern.
c. Select the Invert Signal checkbox.
d. In the Direction field, select the Upstream or Downstream button.

e. Click Restart. The error code is added to the Counter.

f. To refresh the Counter value, click Refresh.
4. To retrieve the current status, on the toolbar click .
Parent Topic
4.4.5 Switching to Protection

The EMS-APT provides the following options for switching to protection:
 Manual Switch: Only if the protected object has no alarms on it. Manual switch is a persistent
command and can be removed only by clearing it. It has a lower priority than alarms, which means
that a manual switch returns to the main object if the protected object has an alarm on it.
 Force Switch: Switching to protection is made from the active object to the backup object. In this
mode, traffic is switched permanently, even if conditions do not require automatic switching.
 Lockout: Switching to protection is prevented, even if conditions require automatic switching.
Lockout remains in effect until the action is released.
To switch to protection:
1. For the XIO cards, in the NE Shelf View window, in the left object tree, select the Main XIO card, and
then select the Maintenance working mode and the Equipment Protection Switch tab.

2. Set the protection switch by selecting a mode in the Switch Command area and clicking Apply to save
the setting:
 Release: Removes current maintenance operations and enters automatic mode.
 Force Switch to XS A: Switches XIO30 A to active state and XIO30 B to standby state, regardless
of a failure in XIO30 A, unless high-priority conditions exist (e.g. a lockout, the XIO30 A is not
present, or the FPGA is not loaded).
 Force Switch to XS B: Switches XIO30 B to active state and XIO30 A to standby state, regardless
of a failure in XIO30 B, unless high-priority conditions exist (e.g. a lockout, the XIO30 B is not
present, or the FPGA not loaded).
 Lock out of Protection: Standby card is locked out and cannot be used by protection.
 Manual Switch to XS A: Switches XIO30 A to active state and XIO30 B to standby state, unless
XIO30 A is in a failure state or high-priority conditions exist (e.g. a forced switch, lockout, the
XIO30 A is not present, or the FPGA is not loaded).
 Manual Switch to XS B: Manually switches to XS B, which means that XIO30 B is switched to
active state and XIO30 A is switched to standby state, unless XIO30 B is in a failure state or
high-priority conditions exist (e.g. a forced switch, lockout, the XIO30 B is not present, or the
FPGA is not loaded).
Parent Topic
4.4.6 Setting the Link Down Status

For an EoP port, the link down status can be set as:
 Force Link Down
 Release

To set the link down status for an EoP port

1. In the left object tree, select an EoP port. Then in the Maintenance working mode, select the Force
Link Down tab.
2. You can set the Link Down Status as Force Link Down or release the force link down maintenance, by
selecting the corresponding radio button.
Parent Topic
4.4.7 Performing CES Maintenance

This section describes the CES maintenance that can be performed on the E1 objects with CES service.
Parent Topic

4.4.7.1 Forcing CES Signal
To force CES signal:

1. In the NE Shelf View window, in the left object tree, under a CES card, select an E1 port with CES
service, then in the Maintenance working mode, select the Force CES Signal tab.
2. You can force L bit or force R bit by selecting the corresponding checkbox.
3. Click Apply to save your setting.
Parent Topic

4.4.7.2 Configuring Timing Commands
To configure timing commands:

1. In the NE Shelf View window, in the left object tree, under a CES card, select an E1 port with CES
service, then in the Maintenance working mode, select the Timing Commands tab.
2. You can set the timing command by selecting the corresponding radio button:
 None
 Reset clock recovery mechanism
 Move clock recovery state to FreeRun
 Force clock recovery state to Holdover
 Release clock recovery state from Holdover
3. Click Apply to save your setting.
Parent Topic

4.5 Performing Maintenance on Timing

This section describes maintenance operations that can be performed on timing objects and TMUs.
Parent Topic
4.5.1 Viewing TMU Working Mode

You can determine the TMU working mode by querying the current clock working mode and the clock
reference of the NE.
The clock working mode can be one of the following:
 Capture mode
 Tracing mode
 Holding mode
 Free oscillation mode
To view the TMU working mode for BG-40/BG-20 NE:

1. In the BG-40 NE Shelf View window, in the left object tree, select Control and Physical Object and
then MXC4X. In the Maintenance working mode, select the Timing Maintenance tab.
Or
In the BG-20 NE Shelf View window, select Control and Physical Object and then the TMU object. In
the Maintenance working mode, select the Timing Maintenance tab.

2. To retrieve the TMU work mode, on the toolbar, click .

To view the TMU working mode for BG-30/BG-64/NPT NE:

1. In the BG-30/BG-64/NPT NE Shelf View window, in the left object tree, select Control and Physical
Object and then the XS A:TMU/BS:TMU object, while in the BG-20C NE, select TMU. In the
Maintenance working mode, select the Timing Maintenance tab. The following window opens, in
which you can view the Main TMU Working Mode and the Standby TMU Working Mode.
2. To retrieve the TMU work mode, click .
Parent Topic
4.5.2 Forcing the Timing Source

Even if the system has made a different selection, the EMS-APT enables you to force a specific timing
source based on the quality of the sources and the priorities assigned.
To force the timing source:

1. In the NE shelf view, select the Timing Maintenance tab as described in Viewing TMU Working Mode.

2. Select an object in the Timing list and right-click, as shown in the following figure:
The following operations can be performed from the right-click menu:

 Lockout
 Release Lockout
 Forced Switch
 Manual Switch
 Clear
Parent Topic
4.6 Managing SNMP Configuration

This section describes how to manage SNMP configuration for BG-20/BG-20C/BG-30/BG-64/NPT-1200/
NPT-1020/NPT-1021/NPT-1010 NEs.
Parent Topic

4.6.1 Overview
When integrated with third party SNMP network management, you can manage the SNMP V3
configuration as described in this section.
4.6.2 Accessing SNMP Configuration Window

All SNMP configuration functions are performed from the SNMP Configuration window, that displays:
 Users
 Groups
 View
 Context
 Access
 Trap
To access the SNMP Configuration window:

 In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window,
in the left object tree, select the NE. From the menu bar, select Configuration and then SNMP User to
open the SNMP Configuration window.
Parent Topic

4.6.3 Managing SNMP Configuration

This section describes how to manage SNMP configuration. This includes managing users, managing groups,
managing views, managing contexts, managing accesses, and managing traps.
Parent Topic
4.6.3.1 Managing SNMP Users
To manage an SNMP user:

1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window,
in the left object tree, select the NE. From the menu bar, select Configuration and then SNMP User to

2. To add a user, in the left-hand list, select User, or from the menu bar, select SNMP V3 and then User.
In the right area of the window, click the Add button. The Add User window opens.
a. Complete the following fields:

 User Name: name of user (must be unique). At most, you can add 20 users.
 Authentication Protocol: can be set as None, MD or SHA (default None).
 Authentication Key: only available when Authentication Protocol is MD or SHA. The length
of the string cannot be less than 8 and not more than 32.
 Privacy Protocol: can be set as None or DES (default None).
 Privacy Key: only available when Privacy Protocol is MD or SHA. The length of the string
cannot be less than 8 and not more than 32.

b. Click Apply to save the changes.

3. To edit a user, in the user list, select the user you want to edit, and click the Edit button. The Edit
window opens.
Edit the information that you want to change, and click Apply. The new information is saved.

4. To view detailed information of a user, select the user in the left-hand list. The information is
displayed in the right area of the window.
5. To delete a user, in the SNMP user list, select the user you want to delete, and click the Delete
button.
Parent Topic

4.6.3.2 Managing SNMP Groups
To manage SNMP groups:

in the left object tree, select the NE. From the menu bar, select Configuration and then SNMP V3 to

2. To add a group, in the left-hand list, select Group, or from the menu bar, select SNMP V3 and then
User Group. In the right area of the window, click the Add button. The Add Group window opens.
 Complete the fields as required:

 Group Name: the name of the group (must be unique). At most, you can add 20 groups.
 User: Select at least one user for the group.

3. To edit a group, in the group list, select the group you want to edit, and then click the Edit button.
Edit the information you want to change, and click Apply. The new information is saved.
4. To view detailed information of a group, select the group in the left-hand list. The information is
displayed in the right area of the window.

To view the users in the group, select the User List tab.
5. To delete a group, in the SNMP group list, select the group you want to delete, and then click the
Delete button.
Parent Topic

4.6.3.3 Managing SNMP Views
To manage SNMP views:

2. To add a view, in the left-hand list, select View, or from the menu bar, select SNMP V3 and then
View. In the right area of the window, click the Add button. The Add View window opens.

a. Complete the following fields:

 View Name: name of the view (must be unique). At most, you can add 20 views.
 Oid Name: The Oid name should start with dot and only allow number such as .1.2.3.
 Include: Select the checkbox as required.
b. Click Apply to save the changes.
3. To edit a view, in the view list, select the view you want to edit, and then click the Edit button. The
Edit View window opens.

4. To view detailed information of a view, select the view in the left-hand list. The information is
displayed in the right-hand side of the window.
5. To delete a view, in the SNMP view list, select the view you want to delete, and then click the Delete
button.
Parent Topic

4.6.3.4 Managing SNMP Contexts
To manage SNMP contexts:

2. To add a context, in the left-hand list, select Context, or from the menu bar, select SNMP V3 and then
User Context. In the right area of the window, click the Add button. The Add Context window opens.
Enter the Context Name (must be unique). At most, you can add 20 contexts.

3. To view detailed information of a context, select the context in the left-hand list. The information is
displayed in the right-hand area of the window.
4. To delete a context, in the SNMP context list, select the context you want to delete, and then click the
Delete button.
Parent Topic

4.6.3.5 Managing SNMP Accesses
To manage SNMP accesses:

1. In the BG-20/BG-20C/BG-30/BG-64/NPT NE Shelf View window, in the left object tree, select the NE.
From the menu bar, select Configuration and then SNMP V3. The SNMP Configuration window
opens.
2. To add an access, in the left-hand list, select Access, or from the menu bar, select SNMP V3 and then
User Access. In the right area of the window, click the Add button. The Add Access window opens.
a. Complete the fields as required:

 Access Name: Name of the access (must be unique). At most, you can add 20 accesses.
 Group Name: Select a group you have created.
 Context: Select a context you have created.
 Security Level: Can be set as None, AuthNoPriv, or AuthPriv (default None).
 Read View: Select a view you have created as read view.
 Write View: Select a view you have created as write view.
 Trap View: select a view you have created as trap view.
3. To edit the access, in the access list, select the access you want to edit, and then click the Edit button.
The Edit Access window opens.

4. To view detailed information of an access, select the access in the left-hand list. The information is
5. To delete an access, in the SNMP access list, select the access you want to delete, and then click the
Delete button.
Parent Topic

4.6.3.6 Managing SNMP Traps
To manage SNMP traps:

1. In the BG-20/BG-20C/BG-30/BG-64/NPT NE Shelf View window, in the left object tree, select the NE.
From the menu bar, select Configuration and then SNMP V3 to open the SNMP Configuration
window.
2. To add a trap, in the left-hand list, select Trap, or from the menu bar, select SNMP V3 and then User
Trap. In the right area of the window, click the Add button. The Add Trap window opens.

Complete the fields as required:

 Version: Can be set as V1, V2C, or V3. If it is set as V1 or V2C, the User Name and Security Level
are disabled.
 IP Address: Set the IP address for the trap.
 Port Number: Set the port number for the trap.
 User Name: Select a user you have created.
 Security Level: None, AuthNoPriv, or AuthPriv (default None).
 Is Administrator: Select the checkbox if you want to set it as administrator.
3. To edit the trap, in the trap list, select the trap you want to edit, and then click the Edit button. The
Edit Trap window opens.
 Edit the information you want to change, and click Apply. The new information is saved.

4. To view detailed information of a trap, select the trap in the left-hand list. The information is
5. To delete a trap, in the SNMP trap list, select the trap you want to delete, and then click the Delete
button.
Parent Topic

4.6.3.7 Overwriting SNMP Configuration

You can overwrite all the SNMP configuration from the NE equipment to the DB.
To overwrite SNMP configuration:
 In the SNMP Configuration window, in the toolbar, click .
Parent Topic

4.6.3.8 Propagating SNMP Configuration

You can propagate the SNMP configuration from one NE to one or more other NEs of the same NE type.
To propagate SNMP configuration:
1. In the SNMP Configuration window, in the toolbar, click . The Propagate window opens.

2. From the left-hand NE list, select the NEs you want to propagate the SNMP configuration to, and then
click the Add button to add them to the right-hand list.
3. Click the Propagate button. You can view the results in the Task Monitor window.
Parent Topic

4.7 Enabling Link Loss Carry Forward (LLCF)

This section describes LLCF in EMS-APT, as illustrated in the following figure.
Figure 4-1: LLCF module
Remote ETY or Tunnel defect can be a trigger for local ETY port down.
To enable LLCF:
1. In the NE Shelf View window, in the left object tree, select an ETY port, and in the Configuration
working mode, select the General tab.

2. From the LLCF Enable field, set LLCF as disabled or enabled as required (default is disabled).
Parent Topic
4.8 Managing EMS Events

Two types of events can be managed as EMS events: RDR backup and license events.
To manage EMS events:

1. In the EMS-APT main topology view window, on the main menu, select System and then EMS Events.
The EMS Events window opens.

2. Select an event in the list, and on the toolbar click the Event Details icon . The following window
opens.
3. To delete an event, select it in the list, and on the toolbar click .

4. To export the NE list as an XML file:
b. Select the location folder, enter the file name for the XML file, and then click Save.
5. To export the NE list as a CSV file:
a. On the toolbar click . The Export Event List as CSV File window opens.

b. Select the location folder, enter the file name for the CSV file, and then click Save.
6. To delete an event, select it in the list, and on the toolbar click .

7. To import archived event files, select the Archived Files tab in the window.
8. To import an XML file:
a. On the toolbar click . The Open window opens.

b. Select an XML file you want to import, and click Open to import it.
The operations in the toolbar are the same as those in the EMS Events tab window.
Parent Topic

4.9 Viewing System Fault Details

You can view the detailed system error information in EMS-APT.
To view system fault details:

1. In the BG-20/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window, on the
menu, select Maintenance and then View System Fault Details. The System Fault Details window
opens.
2. To retrieve the information to view, on the toolbar, click .
Parent Topic
4.10 Performing Link OAM Loopback Testing

The Link OAM Loopback Testing function can be supported for the PB ETY and MoE ports in all the LSI and
Ezchip cards.
To perform Link OAM Loopback Testing:

1. You are not able to start the Link OAM Loopback Testing if Link OAM is disabled or Link OAM remote
loopback is disabled.

2. To enable the Link OAM and the Link OAM remote loopback, in the NE Shelf View window, in the left
object tree, select a port of a data card. Then in the Configuration working mode, select the ETY
Maintenance tab.
 To enable the Link OAM, select the Enable OAM checkbox. The default is disabled.
 To enable the Link OAM remote loopback, select the Remote Loopback Request checkbox. It
can only be set when the Link OAM is enabled.
3. Click Apply to save your changes.

4. To perform Link OAM Loopback Testing function, in the Maintenance working mode, select the Link
OAM Loopback tab.
The following parameters can be configured as required:

 Destination MAC: The destination MAC address of testing packets that generated by CPU.
 Packets Count: The number of packets sent in the storm operation. The default value is 100
packets.
 Delay Between Packets: Delay between packets in the range of 0~600,000 ms. The default
value is 0.
 Size: The size of the test packet. The default value is 64 bytes.
 Timeout: Wait for response in seconds. The default value is 2,000 ms.
5. To start the Link OAM Loopback Testing, on the toolbar, click . When the Link OAM Loopback
Testing is started, the parameters cannot be edited.
6. To restart the Link OAM Loopback Testing, on the toolbar, click . You can restart the Link OAM
Loopback Testing When it has already been started.
7. To stop the Link OAM Loopback Testing, on the toolbar, click .

8. You can also view the the Link OAM Loopback Testing status, as described below.
 Running Status: This attribute describes the running status of this session. If the session is
started, then the status is "Running", otherwise if it is stopped or the session has been ended,
then the status is "End".
 Running Time: This attribute describes running time of Link OAM testing session.

 Number of Tx Packets: Total number of Link OAM testing packets transmitted by CPU.
 Number of Rx Packets: Total number of Link OAM testing packets received by CPU.
 Number of Invalid Rx Packets: Total number of Link OAM testing packets received with invalid
ethernet type by CPU.
 Frame Loss Ratio: This attribute describes average FLR of Link OAM testing session.
Parent Topic
4.11 Setting NE Security Mode
To set NE security mode:

1. To set NE security mode for one or more NEs, in the main topology view window, select one or more
NEs.
2. From the main menu, select Maintenance>NE Security Mode. The NE Security Mode window opens.

3. To set selected NE(s) work in security mode, in the list, select one or more NEs and click . A
confirmation dialog box opens, prompting you to confirm the operation.
4. To confirm, click Yes.
Parent Topic

EMS-APT V3.1 Performance Management Guide PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

EMS-APT V3.1 Performance Management Guide PDF

Transféré par

Droits d'auteur :

Formats disponibles

EMS-APT®

ECI's NPT-1600 complies with the MEF9 and MEF14 standards.

ECI's management applications run on VMWare virtualization hypervisors.

© Copyright by ECI, 2013-2014. All rights reserved worldwide.

2 Fault Management ......................................................................................... 2-1

ECI Telecom Ltd. Proprietary iii

2.6 Managing Unreported Alarms ...................................................................................... 2-33

3 Performance Monitoring ................................................................................ 3-1

ECI Telecom Ltd. Proprietary iv

3.4.4 CES Port PM Counters and TCA ................................................................................................. 3-60

4 Performing Maintenance Operations ............................................................. 4-1

ECI Telecom Ltd. Proprietary v

4.4.4 Performing PRBS ......................................................................................................................... 4-44

ECI Telecom Ltd. Proprietary vi

ECI Telecom Ltd. Proprietary vii

ECI Telecom Ltd. Proprietary viii

1.2 Intended Audience

1.3 Document Contents

1.4 Notes and Warnings

NOTE: clarifying information, specific instructions, commentary, sidelights, or interesting

CAUTION: failure to follow directions could result in damage to equipment or loss of

ECI Telecom Ltd. Proprietary 1-1

IMPORTANT: essential information to which you must pay attention.

1.5 Related Publications

ECI Telecom Ltd. Proprietary 1-2

1.6 How to Obtain ECI Telecom Technical

ECI Telecom Ltd.

ECI Documentation Group

1.7 Technical Assistance

ECI Telecom Ltd. Proprietary 1-3

2.2 Configuring Fault Management

2.2.1 Configuring NE Fault Settings

ECI Telecom Ltd. Proprietary 2-1

To configure BG-40 NE settings:

2. Modify the NE settings as required:

ECI Telecom Ltd. Proprietary 2-2

3. To refresh and retrieve the information of the NE settings, click .

4. To copy the settings from the selected NE to other NEs, click .

ECI Telecom Ltd. Proprietary 2-3

For the BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE, the following window opens.

4. To refresh and retrieve the information of the NE settings, click .

5. To copy the settings from the selected NE to other NEs, click .

ECI Telecom Ltd. Proprietary 2-4

2.2.2 Monitoring and Reporting Alarms

Generally, the following cases use alarm masks:

ECI Telecom Ltd. Proprietary 2-5

To mask (shield) an alarm in the BG-40 NE:

4. To refresh and retrieve the information of the NE settings, click .

5. To copy the settings from the selected NE to other NEs, click .

ECI Telecom Ltd. Proprietary 2-6

To configure the settings for the BG-20/BG-20C/BG-30/BG-64/NPT-1200/

3. To refresh and retrieve the information of the NE settings, click .

ECI Telecom Ltd. Proprietary 2-7

5. To copy the settings from the selected NE to other NEs, click .

ECI Telecom Ltd. Proprietary 2-8

2.2.3 Setting Switch Alarms

To set alarm for the switch module:

ECI Telecom Ltd. Proprietary 2-9

ECI Telecom Ltd. Proprietary 2-10

3. Modify object parameters as required in Monitor and Auto Report lists.

2.2.4 Managing External Alarms

ECI Telecom Ltd. Proprietary 2-11

To manage external alarms: