EMS-BGF UM A00 V12.1 en PDF

EMS-BGF
Version 12.1
User Manual
426006-2421-173-A00
EMS-BGF User Manual
V12.1
Catalog No: X38347
September 2010
1st Edition
Copyright by ECI Telecom, 2002-2010. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Telecom Ltd. (ECI Telecom). BY OPENING THE
DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND 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 Telecom'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 Telecom. 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 Telecom reserves the right, without prior notice or liability, to make changes in equipment design or
specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no
responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which
may be affected in any way by the use and/or dissemination thereof.
Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for
informational purposes only and are not warranties of product performance or otherwise, either express or implied.
ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty
offered by ECI Telecom.
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 Telecom'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
Telecom. All specifications are subject to change without prior notice.
The documentation and/or disk and all information contained therein is owned by ECI Telecom 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 WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT
EXPRESSLY GRANTED ARE RESERVED BY ECI Telecom.
All trademarks mentioned herein are the property of their respective holders.
ECI Telecom 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
therein, 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 hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines"
instructions and that such instructions were understood by them.
It is hereby clarified that ECI Telecom 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 failed to fulfill
in whole or in part the "Before You Start/Safety Guidelines" instructions.
Contents
About This Manual .................................................................... ix
Overview ............................................................................................................. ix
Intended Audience .............................................................................................. ix
Document Objectives ...........................................................................................x
Document Contents..............................................................................................x
Related Publications............................................................................................ xi
Document Conventions ...................................................................................... xii
Obtaining Technical Documentation ................................................................. xiii
Technical Assistance......................................................................................... xiv
EMS-BGF Overview ................................................................. 1-1

What is the EMS-BGF? .................................................................................... 1-1
Main EMS-BGF Tasks...................................................................................... 1-2
EMS-BGF Architecture ..................................................................................... 1-5
General EMS-BGF Operational Principles ....................................................... 1-6
Getting Started......................................................................... 2-1

Overview .......................................................................................................... 2-1
Accessing EMS-BGF ........................................................................................ 2-2
Working in the EMS-BGF Environment ............................................................ 2-5
Using the EMS-BGF Graphic User Interface .................................................... 2-6
Using Online Help .......................................................................................... 2-19
Managing Users and Security ................................................ 3-1

Overview .......................................................................................................... 3-1
Workflow........................................................................................................... 3-2
The Security Configuration Window ................................................................. 3-2
Managing Security Configuration ..................................................................... 3-3
Working with LCT-BGF .................................................................................. 3-24
Viewing the Security Log ................................................................................ 3-25
Viewing the Action Log ................................................................................... 3-27
Configuring and Managing NEs ............................................. 4-1

Overview .......................................................................................................... 4-1
Workflow........................................................................................................... 4-2
Creating UMEs ................................................................................................. 4-2
Creating NEs .................................................................................................... 4-5
Slot Assignment ............................................................................................... 4-8
Setting NE Time ............................................................................................. 4-13
Routing Table ................................................................................................. 4-14
Managing OSPF ............................................................................................. 4-16
426006-2421-173-A00 ECI Telecom Ltd. Proprietary i

Contents EMS-BGF User Manual
Configuring NE Attributes ............................................................................... 4-24

Batch Modify NE Names ................................................................................ 4-25
Performing NE Discovery ............................................................................... 4-26
Modifying NEs ................................................................................................ 4-28
Removing NEs ............................................................................................... 4-31
Resetting NEs ................................................................................................ 4-32
NE Data Backup ............................................................................................. 4-33
Configuring Timing Source .................................................... 5-1

Overview .......................................................................................................... 5-1
Configuring the Synchronous Timing Table ..................................................... 5-2
Configuring the Synchronous Ethernet ............................................................ 5-5
Configuring PCM Timing .................................................................................. 5-9
Configuring and Managing Cards .......................................... 6-1

Overview .......................................................................................................... 6-1
Workflow........................................................................................................... 6-1
Working with Cards .......................................................................................... 6-2
Managing the BG_OW ................................................................................... 6-16
PDH Cards ..................................................................................................... 6-20
SDH Cards ..................................................................................................... 6-23
Data Cards ..................................................................................................... 6-30
PCM Cards ................................................................................................... 6-143
Control Cards ............................................................................................... 6-152
Power Units .................................................................................................. 6-164
Fan Control Units ......................................................................................... 6-165
Managing MPLS Services ....................................................... 7-1

Overview .......................................................................................................... 7-1
Workflow........................................................................................................... 7-3
Supported Cards .............................................................................................. 7-3
Managing Tunnels ............................................................................................ 7-4
Creating MPLS Services ................................................................................ 7-43
Connectivity Fault Management (CFM) .......................................................... 7-77
Configuring ACL Profile .................................................................................. 7-95
Port Mirror ...................................................................................................... 7-97
Configuring Switch OAM ................................................................................ 7-99
Fast ReRoute (FRR) .................................................................................... 7-100
Managing Network in Stand Alone Mode .............................. 8-1

Overview .......................................................................................................... 8-1
Workflow........................................................................................................... 8-1
Managing the Topology .................................................................................... 8-2
Managing Trails .............................................................................................. 8-11
Managing Data Service .................................................................................. 8-28
ii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Contents
Extended DCC ............................................................................................... 8-43

MS DCC Swap ............................................................................................... 8-49
Configuring DCC Over 2M ............................................................................. 8-49
Managing Network in Integrated Mode .................................. 9-1

Overview .......................................................................................................... 9-1
Workflow........................................................................................................... 9-1
Managing SDH Service in Integrated Mode ..................................................... 9-2
Managing Tunnel Service in Integrated Mode .................................................. 9-2
Managing Ethernet Data Service in Integrated Mode ...................................... 9-3
Managing Cross Connections .............................................. 10-1

Overview ........................................................................................................ 10-1
Workflow......................................................................................................... 10-1
Creating XC .................................................................................................... 10-2
Managing the XC List ................................................................................... 10-17
Configuring SNCP Attributes ........................................................................ 10-24
Exporting and Importing XC Files ................................................................. 10-25
Working with Protection ....................................................... 11-1

Overview ........................................................................................................ 11-1
Workflow......................................................................................................... 11-1
Working with TP ............................................................................................. 11-2
Working with MSP 1+1 ................................................................................. 11-14
Working with STP and MSTP ....................................................................... 11-20
MS Shared Protection Ring (MS-SPRing) .................................................... 11-26
Ethernet Ring Protection Switching (ERPS) ....................... 12-1

Overview ........................................................................................................ 12-1
Workflow......................................................................................................... 12-2
Creating PB Ring ERP Control VSI ................................................................ 12-4
Creating MPLS Ring ERP Control VSI ......................................................... 12-10
Viewing ERPS Instance ............................................................................... 12-15
Fault Management ................................................................. 13-1

Overview ........................................................................................................ 13-1
Workflow......................................................................................................... 13-2
Configuring Fault Management ...................................................................... 13-3
Managing Current Alarms ............................................................................ 13-18
Managing Alarms History ............................................................................. 13-25
Managing Cleared Alarms ............................................................................ 13-28
Monitoring Events ......................................................................................... 13-32
Managing Unreported Alarms ...................................................................... 13-35
Managing Archived Alarm Files .................................................................... 13-39
Managing NE Alarms Log ............................................................................ 13-44
426006-2421-173-A00 ECI Telecom Ltd. Proprietary iii

BIT Codes .................................................................................................... 13-46

Viewing PPI Status ....................................................................................... 13-47
Troubleshooting Alarms ............................................................................... 13-48
Monitoring Performance ....................................................... 14-1

Overview ........................................................................................................ 14-1
Performance Data .......................................................................................... 14-1
Workflow......................................................................................................... 14-5
Viewing Performance Data............................................................................. 14-5
Configuring Performance Attributes ............................................................. 14-11
PM Counters and TCA ................................................................................. 14-30
Performing Performance Export Configuration ............................................ 14-34
Performing Maintenance Operations ................................... 15-1

Overview ........................................................................................................ 15-1
Workflow......................................................................................................... 15-1
Preventive Maintenance Operations .............................................................. 15-2
Managing Database ..................................................................................... 15-18
Perform Card Maintenance .......................................................................... 15-20
MSP 1+1 Maintenance Operation ................................................................ 15-26
Managing SNCP Attributes .......................................................................... 15-27
Perform Transmission Object Maintenance Operations ............................... 15-28
Perform Maintenance on Timing .................................................................. 15-36
Trap Manager Table ..................................................................................... 15-40
Link Loss Carry Forward (LLCF) .................................................................. 15-41
Managing Reports ................................................................. 16-1

Overview ........................................................................................................ 16-1
Using the Report Window ............................................................................... 16-2
XML File ................................................................................... A-1

Overview .......................................................................................................... A-1
XML and DTDs ................................................................................................. A-1
Example ........................................................................................................... A-3
Summary of Menu Commands .............................................. B-1

Overview .......................................................................................................... B-1
Software Upgrade ................................................................... C-1

Software Upgrade Overview ............................................................................ C-1
Software Upgrade Workflow ............................................................................. C-2
Performing Software Upgrade .......................................................................... C-2
iv ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Contents
NE Version Live Update ......................................................... D-1

Overview ..........................................................................................................D-1
Workflow...........................................................................................................D-2
Embedded SW Patching .................................................................................. D-2
Activate NE Patches......................................................................................... D-7
View Scheduled Activation Info ...................................................................... D-11
Cancel Activate NE Patches .......................................................................... D-12
Clear NE Patches ........................................................................................... D-12
RDR ...........................................................................................E-1
Overview .......................................................................................................... E-1
RDR Solutions .................................................................................................. E-2
RDR Schemes.................................................................................................. E-2
Failover Processing .......................................................................................... E-4
Alarm Export Using FTP ......................................................... F-1

Overview .......................................................................................................... F-1
Alarm Export Topology ..................................................................................... F-2
Alarm Export Mechanism ................................................................................. F-2
Alarm Format.................................................................................................... F-3
Using Alarm Export .......................................................................................... F-5
Moving MEs on NMS .............................................................. G-1

Overview ..........................................................................................................G-1
Procedure of Moving MEs ................................................................................G-1
Managing Event Logs ............................................................ H-1

Overview ..........................................................................................................H-1
Archive Settings ............................................................................................... H-2
Archive Immediately ......................................................................................... H-3
Viewing Archive Logs ....................................................................................... H-4
Managing License .................................................................... I-1

License Overview .............................................................................................. I-1
License Control Mechanism .............................................................................. I-2
License Control Workflow .................................................................................. I-2
Managing Licenses in the EMS-BGF ................................................................ I-4
Fix Tool ..................................................................................... J-1

Using Fix Tool ...................................................................................................J-1
Index .......................................................................................... I-1
426006-2421-173-A00 ECI Telecom Ltd. Proprietary v

vi ECI Telecom Ltd. Proprietary 426006-2421-173-A00

List of Tables
Table 2-1: Basic Keys ............................................................................................. 2-5
Table 2-2: Application program icons ................................................................... 2-13
Table 2-3: Subnet icons ........................................................................................ 2-13
Table 2-4: Normal NE icons.................................................................................. 2-13
Table 2-5: Status definitions ................................................................................. 2-14
Table 2-6: Function and operation icons .............................................................. 2-15
Table 3-1: EMS New User Parameters .................................................................. 3-5
Table 3-2: Fields and buttons in the Add UserGroup window .............................. 3-12
Table 3-3: Fields in the Add UserGroup window .................................................. 3-16
Table 3-4: Fields in the Add Domain window ....................................................... 3-19
Table 5-1: Synchronous Ethernet capability of Layer 2 cards ................................ 5-8
Table 6-1: Description of BG-40 cards and applicable slots .................................. 6-5
Table 6-4: Description of BG-64 cards and applicable slots ................................ 6-11
Table 6-5: Policer Value Rules ............................................................................. 6-92
Table 6-6: SM10 traffic modules ......................................................................... 6-143
Table 6-7: SM_10E traffic modules .................................................................... 6-146
Table 7-1: PE name and PE ID list ....................................................................... 7-20
Table 7-2: PE, PE Name and PE ID list ............................................................... 7-25
Table 11-1: BG-30 Tributary Protection Group Options ......................................... 11-2
Table 13-1: Icons in the Severity Settings window ............................................... 13-12
Table 13-2: Icons on the current alarm toolbar..................................................... 13-19
Table 13-3: Icons on the historical alarm toolbar.................................................. 13-26
Table 13-4: Equipment & Process Failure Alarms and Events ............................ 13-48
Table 13-5: Communications Alarms.................................................................... 13-55
Table 13-6: Service Alarms .................................................................................. 13-68
Table 13-7: Timing Alarms.................................................................................... 13-68
Table 13-8: Threshold Crossing Alarms ............................................................... 13-69
Table 13-9: External Alarms ................................................................................. 13-72
Table 13-10: PCM and EOP Alarms ....................................................................... 13-72
Table 13-11: MPLS Tunnel and tOAM Alarms........................................................ 13-74
Table 13-12: Ethernet Service Alarms .................................................................... 13-74
426006-2421-173-A00 ECI Telecom Ltd. Proprietary vii

List of Tables EMS-BGF User Manual
Table 13-13: ERPS Alarms ..................................................................................... 13-75

Table 14-1: Performance threshold value ranges ................................................ 14-12
Table 14-2: Port/Switch/Policer/VSI/Tunnel Level PM Counters and TCA .......... 14-30
Table 14-3: EoS Mapper PM Counters and TCA ................................................. 14-33
Table 14-4: Slot names and relevant slot numbers .............................................. 14-36
Table 14-5: MO names and relevant MO numbers .............................................. 14-37
Table 14-6: Counter List - VC4 ............................................................................. 14-39
Table 14-7: Counter List - MS............................................................................... 14-39
Table 14-8: Counter List - EoS Port...................................................................... 14-39
Table 14-9: Counter List - EoS................................................................................... 14-41
Table 14-10: Counter List - ETY Port ......................................................................... 14-41
Table 15-1: EMS-BGF preventive maintenance procedures ................................ 15-17
Table B-1: View Menu ............................................................................................. B-1
Table B-2: Configuration Menu ............................................................................... B-2
Table B-3: Services Menu ....................................................................................... B-2
Table B-4: Fault Menu ............................................................................................. B-3
Table B-5: Performance Menu ................................................................................ B-4
Table B-6: Maintenance Menu ................................................................................ B-4
Table B-7: Security Menu........................................................................................ B-5
Table B-8: System Menu......................................................................................... B-5
Table B-9: Help Menu ............................................................................................. B-6
Table F-1: Export title header ................................................................................. F-3
Table F-2: Alarm record format ............................................................................... F-3
Table F-3: Alarm record attributes .......................................................................... F-3
Table F-4: Alarm Object attribute format ................................................................ F-4
viii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

About This Manual
In this chapter:
Overview ........................................................................................................... ix
Intended Audience ............................................................................................. ix
Document Objectives ......................................................................................... x
Document Contents ............................................................................................ x
Related Publications .......................................................................................... xi
Document Conventions .................................................................................... xii
Obtaining Technical Documentation ............................................................... xiii
Technical Assistance ....................................................................................... xiv
Overview
This book describes the operation of the EMS-BGF network management
system. It presents a detailed description of the product including, a general
product overview, a description of the user interface, a guide to basic
operations, and a comprehensive description of functionality.
Intended Audience
The BroadGate EMS-BGF User Manual is intended for Network Operation
Center (NOC) administrators and NOC personnel managing BroadGate (BG)
family networks, as well as BG family trainers and field service personnel.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary ix

About This Manual EMS-BGF User Manual
Document Objectives
This book provides basic operating instructions for EMS-BGF platform.
Document Contents
This document contains the following sections:
EMS-BGF Overview (on page 1-1) provides an overview of the EMS-BGF
application, and describes its primary functions and architecture, as well as
a typical workflow for working with the application.
Getting Started (on page 2-1) describes the graphical user interface for
EMS-BGF, its organization and operation, as well as how to access the
application.
Managing Users and Security (on page 3-1) describes how to manage users
and security, including the security mechanism, security levels and user
domain.
Configuring and Managing NEs (on page 4-1) describes how to configure
and manage network elements, external network elements and other
devices in the network.
Configuring Timing Source (on page 5-1) describes how to configure the
synchronous timing sources and timing table used by the system.
Configuring and Managing Cards (on page 6-1) describes how to configure
card attributes and view card-related information.
Managing MPLS Services (on page 7-1) describes how to configure and
manage cards with MPLS services.
Managing Network in Stand Alone Mode (on page 8-1) describes how to
manage the topology, orderwire, DCC and overhead in standalone mode.
Managing Network in Integrated Mode (on page 9-1) describes how to
manage data service, PCM, DCC and overhead in integrated mode.
Managing Cross Connects (on page 10-1) describes how to create and
manage XC, as well as the procedure for exporting and importing SNC
files.
Working with Protection (on page 11-1) describes how to work with IOP,
MSP 1+1, STP and MSTP, and MS-SPRing.
Ethernet Ring Protection Switching (ERPS) (on page 12-1) describes how
to create and manage PB Ring ERP Control VSI and MPLS Ring ERP
Control VSI.
Fault Management (on page 13-1) describes how to configure fault
management and alarms, including current alarms, alarms history, NE
alarms log and troubleshooting alarms.
x ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual About This Manual
Monitoring Performance (on page 14-1) describes the EMS-BGF

performance monitoring mechanisms, including viewing current, historical,
and recent performance.
Performing Maintenance Operations (on page 15-1) describes how to
perform standard maintenance, such as loopbacks, path payload tests, and
consistency and connectivity checks.
Managing Reports (on page 16-1) describes the procedure for managing
reports.
XML File (on page A-1) describes the XML file used in EMS-BGF.
Summary of Menu Commands (on page B-1) describes the menu
commands of the EMS-BGF GUI.
Software Upgrade (on page C-1) describes how to upgrade software in
EMS-BGF.
NE Version Live Update (on page D-1) describes the procedure of NE
version live update.
RDR (on page E-1) describes the Remote Data Replicate feature of EMS-
BGF.
Alarm Export Using FTP (on page F-1) describes the alarm export feature.
Managing License (on page I-1) describes the license control mechanism in
EMS-BGF and embedded software, as well as the procedure for license
management.
Fix Tool (on page J-1) describes how to use the fix tool.
Related Publications
The following publications may be of assistance to you regarding EMS-BGF
operations:
BroadGate Product Line General Description
BroadGate Product Line Reference Manual
BroadGate BG-40 Installation, Operation, and Maintenance Manual
BroadGate LCT-BGF User Manual
BroadGate EMS-BGF Installation Manual
LightSoft Network Management System User Manual
426006-2421-173-A00 ECI Telecom Ltd. Proprietary xi

Document Conventions
When applicable, this manual uses the following conventions.
Convention Indicates Example
Bold Names of windows, dialog In the Alarms menu...
boxes, menus, buttons, and
most other GUI elements
Menu > Option Selection from a menu, or Select Update > View
leading to another Objects
command
Italics New terms and emphasized Examples in text
text
Borders around text Notes, cautions, and See examples below
warnings
Note: Text set off in this manner presents clarifying

information, specific instructions, commentary, sidelights, or
interesting points of information.
CAUTION: Text set off in this manner indicates that failure

to follow directions could result in damage to equipment or
loss of information.
WARNING: Text set off in this manner indicates that failure

to follow directions could result in bodily harm or loss of life.
LASER WARNING: Text set off in this manner indicates

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.
xii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual About This Manual
ESD: Text set off in this manner indicates information on

how to avoid discharge of static electricity and subsequent
damage to the unit.
TIP: Text set off in this manner includes helpful information

and handy hints that can make your task easier.
IMPORTANT: Text set off in this manner presents essential

information to which you must pay attention.
Obtaining Technical
Documentation
To obtain technical documentation related to ECI Telecom products, please
contact:
ECI Telecom Ltd.
Documentation Department
30 Hasivim St.
Petach Tikva 49130
Israel
Fax: +972-3-9268060
Email: techdoc.feedback@ecitele.com
426006-2421-173-A00 ECI Telecom Ltd. Proprietary xiii

Technical Assistance
The configuration, installation, and operation of the and its operation in a
network are highly specialized processes. Due to the different nature of each
installation, some planning aspects may not be covered in this manual.
If you have questions or concerns about your network design or if you require
installation personnel to perform the actual installation process, ECI Telecom
maintains a staff of design engineers and highly trained field service personnel.
The services of this group are available to customers at any time.
If you are interested in obtaining design assistance or a network installation
plan from ECI Telecom's Customer Support team, contact your ECI Telecom
sales representative. With any support related issues, technical or logistic,
contact the ECI Telecom Customer Support center at your location or our
central customer support center action line at:
Telephone +972-3-9266000
Telefax +972-3-9266370
Email on.support@ecitele.com
ECI Telecom's XDM and BroadGate product lines are

certified to comply with MEF9 and MEF14 standards.
ECI Telecom'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.
xiv ECI Telecom Ltd. Proprietary 426006-2421-173-A00

1
EMS-BGF Overview
In this chapter:
What is the EMS-BGF? ................................................................................... 1-1
Main EMS-BGF Tasks .................................................................................... 1-2
EMS-BGF Architecture ................................................................................... 1-5
General EMS-BGF Operational Principles ..................................................... 1-6
What is the EMS-BGF?

The EMS-BGF is an advanced Element Management System designed to
manage the BroadGate (BG) family of networks. It has an advanced
architecture which supports multiple operating systems for integrated
management, either standalone or with NMS.
The EMS-BGF offers end-to-end service provisioning for a host of low bit rate
services. It consists of a GUI client and a server application. The client and
server can be located either on the same PC (single-system mode) or on
different PCs (standard client/server structure).
426006-2421-173-A00 ECI Telecom Ltd. Proprietary 1-1

EMS-BGF Overview EMS-BGF User Manual
Main EMS-BGF Tasks

The following subsections discuss the management functions available in the
EMS-BGF.
Configuration Management
The EMS-BGF supports the following configuration management tasks:
Creating, deleting, and resetting elements
Viewing card and network element attributes
Performing card panel actual view
Managing Orderwire, Overhead, and DCC configuration
Performing gateway protection
Managing external elements
XC and Trail Management

The EMS-BGF supports the following XC and trail management tasks:
XC management, including:
XC creation and deletion
XC list and filter
Granularities of XC are VC12/VC3/VC4/VC4-4c/VC4-16C/VC4-64C
Unidirectional, bidirectional, broadcast and loopback for XCs
SNCP-I, SNCP-N, MSP 1+1 and MS-SPRing protection
XC export and import using XML
End-2-end trail management, including:
Trail creation, deletion, and editing
Trail activation and deactivation
Trail list and filter
Trail export and import using XML
Protection operations
1-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual EMS-BGF Overview
Data Management
The EMS-BGF supports the following data capabilities:
Layer 1 and layer 2 services for end-users
MPLS and services over MPLS
VCG and ports configuration
VPN services
Data performance
Data OAM
Fault Management
The EMS-BGF supports the following fault management tasks:
Displaying current NE alarms
Displaying and handling alarm logs
Setting options for audible alarms and reminders
Exporting logs
Correcting alarms
Acknowledging alarms
Maintenance Management
Maintenance tasks include:
Managing maintenance list
Performing remote software upgrade for NEs and cards
Operating and releasing loopbacks
Sending an Alarm Indication Signal (AIS) force
Forcing an RDI
Performing NE configuration file maintenance
Pinging any NE
Performing miscellaneous maintenance operations
Performing remote command line operation for XML files import and
export

Performance Management
Performance Management tasks include:
Retrieving and displaying current performance data for each NE (every 15
minutes or 24 hours)
Retrieving and displaying historical performance data for each NE, by
stored time/date or by interval (every 15 minutes or 24 hours)
Resetting PM counters
Performing performance threshold configuration
Security Management
Security management tasks include:
Setting passwords
Managing user groups
Assigning capabilities to user groups
Detecting and alerting the unauthorized use
Locking the GUI

EMS-BGF User Manual EMS-BGF Overview
EMS-BGF Architecture
This section introduces the EMS-BGF architecture and application. The
following figure shows the EMS-BGF architecture.
In this scheme, the EMS-BGF consists of a server and a client application. Its
server includes a Java Server application, an Agent Manager and the
Northbound interfaces. It communicates with the EMS-BGF GUI client using
RMI, and receives alarms/events using JMS.

General EMS-BGF Operational

Principles
All functions of the EMS-BGF can be divided into two parts: network
configuration and network maintenance. Configuration refers to implementing
NE functions and dynamic customization according to networking
requirements, such as topology operations, NE attribute configuration, slot
configuration, and clock and orderwire configuration. Maintenance refers to
customizing and collecting NE information (such as alarm and performance),
determining the NE status, and executing maintenance operations. All EMS-
BGF operations are subject to these two categories.
The following principles ensure the security, reliability, and manageability of
the network:
Configuration before maintenance. Generally, NE configuration is always
completed before various maintenance operations. Maintenance operations
become meaningless if configuration has not been completed as a
prerequisite.
There is generally a strict sequence for configuration. Configuration
procedures are interdependent and cannot be reversed. Thus, they should be
rational, well planned, and adhere to the appropriate sequence.
It is best to check an NEs current status first, before deciding on the
necessary configuration operation. Operational procedures differ markedly
for configured and unconfigured NEs. The operations that have already
been performed on an NE should be determined first. New operations
should be performed based on this determination. You should never
perform operations on an NE based on suppositions about its status. An
NEs current status should always be determined first. Failure to do so may
lead to the abnormal working of the NE.
Consistency principle. Consistency between the configuration on the EMS-
BGF and that on the NE should always be ensured. Otherwise, errors may
occur.
Correct use of offline configuration and off-card configuration options. For
ease of use and convenience, the EMS-BGF supports complete offline and
off card configuration. However, the data may easily be inconsistent when
these configuration options are used inappropriately. The operator should
always know whether the data and current operation are being performed
on the EMS-BGF side or the NE side. In addition, the operator should be
able to differentiate between the expected configuration, the EMS-BGF
configuration, and the actual NE configuration.

2
Getting Started
In this chapter:
Overview ......................................................................................................... 2-1
Accessing EMS-BGF ...................................................................................... 2-2
Working in the EMS-BGF Environment ......................................................... 2-5
Using the EMS-BGF Graphic User Interface .................................................. 2-6
Using Online Help ......................................................................................... 2-19
Overview
This section explains the first steps for getting the EMS-BGF up and running. It
also describes the basic concepts of the EMS-BGF Client and its operating
conventions, including how to log into and log out of the EMS-BGF, how to
work with its windows, and how to configure the EMS-BGF.

Getting Started EMS-BGF User Manual
Accessing EMS-BGF
Logging into an EMS-BGF client gives access to the EMS-BGF's features, in
accordance with assigned security permissions and purchased optional features.
Starting EMS-BGF
This section describes the EMS-BGF startup procedure.
To start EMS-BGF:
1. After successfully installing the EMS-BGF server program, a shortcut icon
appears on the desktop. Start the EMS-BGF server by double-clicking

this icon. After the program successfully starts, a small computer icon
appears in the task bar, as shown in the following figure. Double-click this
icon to open the EMS-BGF server and to view the status of each running
EMS-BGF service.
2. Once the server is running, you can run the Client program. After
successfully installing the EMS-BGF application, a Client shortcut icon
appears on the desktop. Double-click it to open the User Login

window.

EMS-BGF User Manual Getting Started
Logging In/Logging Out of EMS-BGF

Once the Server and Client are running, you can log into EMS-BGF and log
out of EMS-BGF after it runs.
To log into EMS-BGF:

1. In the User Login window, enter the correct user name and password.

2. Click the Advanced button to open the Server List window, as shown in
the following figure. During the EMS-BGF installation, the default
parameters are set automatically. You can add, edit, or remove a server in
the Server List window. For each server, different ports must be set to
avoid conflict.
3. In the User Login window click Login. The EMS-BGF main window
opens. The user name and password for first-time EMS-BGF use are admin
and blank, respectively. To ensure the security of the system, set a new
password for the Administrator as soon as possible.
To log out of EMS-BGF:

1. In the EMS-BGF main window, on the menu bar, select System > Logout.
This logs you out from EMS-BGF but does not exit the application.
2. To resume work in the EMS-BGF, log into it by typing your name and
password in the User Login window.

Working in the EMS-BGF

Environment
There are a number of aspects involved in working on the EMS-BGF that may
be different from what you are used to. This section discusses some of these
aspects.
Using Menus
There are several types of menus in EMS-BGF:
Menus Menus display when you click the menu name in the menu bar. A
menu may have one or more items from which you can choose by moving
the mouse pointer over that item. When the item you want is highlighted,
click the left mouse button.
Popup menus Popup menus are displayed by clicking the right mouse
button (right-clicking) on a window area that supports popup menus. The
menu is displayed over the window where you clicked. You select an item
by highlighting it with the mouse and then clicking it.
Submenus Submenus are menus that contain a list of choices related to a
menu item. When you select the menu item, the submenu is displayed. You
select an item from a submenu by clicking it.
The Keyboard
The EMS-BGF uses an industry-standard keyboard similar to the keyboards
connected to most personal computers. The following table lists the basic keys
and their functions:
Table 2-1: Basic Keys
Key Action
<Tab> Moves the text cursor to the next field or object within a window.
<Backspace> When positioned inside a field, erases the character to the left of the
text cursor, or clears the contents of a field when the entire field is
selected.
<Del> Erases the character to the right of the text cursor when positioned
inside a field, or clears the contents of a field when the entire field is
selected.
<PgUp> Scrolls through lists upwards whenever there are several items on the
list.
<PgDn> Scrolls through lists downwards whenever there are several items on
the list.
< > Moves up to the next listing in a list box.

Key Action
< > Moves down to the next listing in a list box.
< > Moves the text cursor one character to the right.
< > Moves the text cursor one character to the left.
<Home> When positioned inside a field, moves the cursor to beginning of the
field.
<End> When positioned inside a field, moves the cursor to the end of the
field.
Using the EMS-BGF Graphic User

Interface
You can configure and monitor the entire EMS-BGF from the EMS-BGF main
window.
EMS-BGF GUI Style

The EMS-BGF Graphical User Interface(GUI) meets general GUI guidelines:
One integrated window which includes main menu, toolbar, objects tree,
and Properties Area (tabs).
Object management (add, delete, view, etc.) is performed by selecting
objects in the object tree. The actions are performed via the toolbar or via
right-click menus.
The child entities of the selected object are presented in a list format in the
Properties Area.
The Properties Area is a set of tabs which are relevant to the selected object
and working mode.
Alarms and maintenance indications appear on the tree.
The operation sequence is:
Select the working mode.
Select an object from the Object Tree.
Select the target tab from the relevant tabs shown in the Properties
Area.
Select the toolbar and perform the desired operation.

EMS-BGF Main Window

When you log into the EMS-BGF, the main window is displayed. You access
all EMS-BGF functions from this window. The main window is the
background for all other EMS-BGF windows and dialog boxes, and is always
displayed unless minimized. The following figure shows the main window.
You can zoom in, zoom out, or move this window. All EMS-BGF functions
can be performed via interactions between the mouse and the keyboard on the
main desktop. A color coding scheme provides a view of the managed NEs'
alarm status. When an alarm is detected, you can easily drill down to detect its
exact source. The topology tree (on the left) allows complete navigation
between NEs, slots, cards, and ports, and provides direct access to
corresponding objects and windows.
Title Bar
The title bar is located at the top of the main window, and displays the EMS-
BGF title and icon.

Main Menu Bar

Located below the title bar, the main menu enables you to access all EMS-BGF
functions. When you click a menu name, the menu opens.
Toolbar
The toolbar is located below the main menu, and provides quick access to
EMS-BGF functions. Clicking a button may display a window or dialog box, or
perform a function.
Topology View
The topology view area is located below the toolbar, and provides a topological
display for the managed equipment. It reflects the status of the equipment in
real time. You access the managed equipment via the topology view to check
its details or conduct functional operations.
Status Bar
The status bar is located at the bottom of the main window, and is used to
display the current login users, connecting server, and time.

Object Tree
The object tree displays the hierarchy of objects which exist in the system. The
following figure shows the object tree window.
You can select the object in the object tree, and then select the operation in the
toolbar, and the related menu will pop up. When you click an object in the
object tree, that object is highlighted in the topology view.
Each node in the object tree can be expanded or collapsed. A next to the
node indicates that the node is expandable. A next to the node indicates that
the node is collapsible. Click or double-click the node to expand it and view
the objects it contains. Click or double-click the node to collapse it. The root
node in the topology, does not have or next to it.
In addition, you can click button to expand/collapse all cards or ports.

Working Mode Bar

The working mode bar displays the working mode in EMS-BGF. The
following figure shows the working mode bar.
Properties Tab
The following figure shows the properties area in EMS-BGF. It is represented
by a set of tabs. The relevant information of the selected MO is displayed in the
tab. Changing the working mode will cause the working area to change to the
relevant set of tabs. Also, changing the MO in the object tree will cause the tab
contents to change to the relevant information.
The hierarchy of the selected object is reflected in the object path, which is
separated by the '>>'. The Properties tab includes toolbar, filter, and list. The
Properties toolbar contains the most used functions for the selected object
under the selected working mode. The filter can be expanded and collapsed.
When it is collapsed, the Filter title displays the filter name. The filter can be
expanded to input the filtering condition.

Navigator
The Navigator is a small window that shows the entire map of the current
network topology. This is useful when the entire map is too large to be
displayed in the current view. In that case, you can use the Navigator to select
the portion of the map you want to display in the current view. The view is
refreshed as you drag the view in the main window. The Navigator can also be
used to magnify the view in the Main window by dragging the border of the
Navigator window.
In addition, by right-clicking on the navigator window, you can select Fill

Mode, Update Interval, View Mask, View Border, and Show Title.
To show /hide the Navigator window:

From the main menu bar, select View > Display > Show/Hide Overview.
Or, right-click on the topology view, select Display > Overview.
Alarm Counter Bar

The alarm counter bar provides an indication of the alarm statistics in the
network. Each alarm severity has an alarm icon and a number indicating the
alarm number.
By default, the alarm counter bar is displayed on top so that users can view
these important indications at all times. You can close the bar by selecting
Fault > Display > Alarm Counter in the main menu.

NE Shelf View
The NE shelf view represents the physical reality. It displays only physical
objects. Logical objects are not visible in the shelf view. The NE alarms'
overview is also displayed in the shelf view. The following figure shows the
BG-30E NE shelf view:
Every card has a rectangular frame to facilitate the quick identification of the
individual cards. Names of the cards are written at the top of the rectangle, in
the upper left corner. An empty slot is indicated by an empty rectangle.
The connection to the external orderwire(OW) box is displayed. If there is no
connection, the OW connector will appear empty. The following figure shows
the connection representation of the OW:
The upper left corner is a status area, showing the alarm indications.
Port alarms are reflected in their parent card status. If several ports have alarms
of different severity, the card always gets the most critical alarm.
Logical objects alarms are reflected in their parent card status. Therefore, the
card can have an alarm even if none of its physical ports have alarms.

EMS-BGF Client Icon Definition

This section defines the icons used in the EMS-BGF Client application.
After the installation of the EMS-BGF, an icon representing the Client appears
on the desktop. EMS-BGF operation requires several background service
programs. The application programs needing user interactions are described in
the following table.
Table 2-2: Application program icons
Application program Icon Description

EMS-BGF Client EMS-BGF client program
EMS-BGF server EMS-BGF dispatcher program for the

program background service program
The following table illustrates the subnet icons used in the EMS-BGF.
Table 2-3: Subnet icons
Description Icon
Subnet
No Critical Major Minor Warning

alarm Alarm alarm alarm alarm
The following table describes the NE icons used in the EMS-BGF.
Table 2-4: Normal NE icons
Description Icon
BG-40 NE
BG-20B NE
BG-20E NE


Description Icon
BG-30B NE
BG-30E NE

BG-20C
BG-64

BG-64E

The following table describes the status definition icons used in the EMS-BGF.
Table 2-5: Status definitions
Status definition Icon or Description

color
Alarm status (The alarm status of the Red Critical alarm (Critical).
NE, card, and/or object to be Orange Major alarm (Major).
managed have the same definition.)
Yellow Minor alarm (Minor).
Purple Warning alarm (Warning).
Green Normal or cleared (Cleared).
NE disconnection status Communication connection
between the EMS-BGF and NE is
lost.
Route status If this icon appears at the upper-left
corner of the NE icon, this NE is
configured with routes.
Maintenance status If this flag appears under the NE
icon, this NE is set with the
operation and has not been
released.
Inconsistency status If this icon appears at the lower-left
corner of the NE icon, this NE is
inconsistent with EMS.

The following table describes the function and operation icons used in the
EMS-BGF main window.
Table 2-6: Function and operation icons
Icon Name Application description

Help Displays online help topics describing how to use
the EMS-BGF.
Logout Logs out from the current user environment
without closing the interface, and then logs in as a
new user.
Exit Exits the EMS-BGF and disconnects the client.
Show/Hide tree Shows or hides the tree in the topology view.
Lock topolink Locks the topolink.
Zoom in Magnifies the current view.
Zoom out Demagnetizes the current view.
Fit to view Fits the view of the Main window so that you can
see the entire network topology.
Pan Drags the background of the topology view.
Open in fault mode Opens the selected NE in fault mode.
Open in configuration Open the selected NE in configuration mode.

mode
Open in maintenance Opens the selected NE in maintenance mode.
mode
Open in performance Opens the selected NE in performance mode.
mode
Open in services mode Opens the selected NE in services mode.
Create NE Creates one or more NEs.
Create Group Creates a group.
Propagate Copies some NE properties from the selected NE

to other NEs.
Trail list Displays the trail list.
Create trail Creates a trail.

Icon Name Application description

View topolink list Displays the topolink list.
Create topolink Creates a topolink.
Modify topolink Modifies the topolink.
Auxiliary Features
This section describes additional features available in the EMS-BGF, such as
the customizable toolbar and using the search function.
Customizing the Toolbar

This section describes how to customize the EMS-BGF toolbar.
To customize the toolbar:

1. By default, the toolbar is shown, displaying the quick access to EMS-BGF
functions. You can right-click on the toolbar and click Hide Toolbar, or
select View > Display > Show/Hide Toolbar to hide it.
2. Right-click on the toolbar. On the pop-up menu, you can choose which tool
to display by selecting the corresponding checkbox.
3. There are several toolbar handles in the toolbar. You can set the order of
the tools by dragging the handles. The handle figure is shown here:
4. You can lock the toolbar by selecting Lock the Toolbar in the right-click
menu.

Searching for an NE
You can search for an NE in the EMS-BGF's main topology view.
To find an NE:
1. In the main topology view window, select View > Find in the main menu.
The Search window opens.

2. In the relevant field, enter the information pertaining to the NE that you
want to find, and select the corresponding checkboxes in the Type area.
3. Select the NE you want to find in the NE list below. This NE will be
highlighted in the topology view window.
4. Click Clear to clear the search information you typed in from the window.
5. Click Close to close the Search window.

Searching the Topology Tree

You can search the contents of the Topology Tree for a particular object.
To use the search:

1. Enter the details about the object you want to find in the Find dialog box.
2. If the search is successful, items that meet the search criteria will be
highlighted in the Topology Tree.
Using Online Help

For further reference, a context sensitive online help and PDF file are available
for researching questions quickly and learning more about operating the EMS-
BGF.
To use the online help:
1. On the main toolbar, click . An EMS-BGF PDF opens, where you can
access information on how to use the EMS-BGF management interface.
(The help system runs in HotJava, an HTML browser running on the Sun
workstation and similar in operation to Netscape.)
2. On the toolbar, click . The Help window opens, displaying information

relevant to the active window.
3. In the Table of Contents (left pane), click any of the topics. The relevant
topic appears in the workspace (right pane) of the online help.


3
Managing Users and Security
In this chapter:
Overview ......................................................................................................... 3-1
Workflow ......................................................................................................... 3-2
The Security Configuration Window .............................................................. 3-2
Managing Security Configuration ................................................................... 3-3
Working with LCT-BGF ............................................................................... 3-24
Viewing the Security Log .............................................................................. 3-25
Viewing the Action Log ................................................................................ 3-27
Overview
This section discusses how to use the EMS-BGF for managing security and
user access rights. Users are given permissions, or roles, to perform certain
functions within the system by assigning them to a particular user group.
The user group is assigned both a capability profile that describes what
functions group members can perform, as well as one or more resource
domains, which specify what resources the user can operate on. In turn, roles
consist of individual capabilities grouped into a profile. (A role is a function
that can be performed in the system, such as deleting users or creating trails.)
Resource domains are composed of individual EMS resources which can be
assigned to user.
This hierarchical structure provides ample flexibility in security management.
This chapter describes these topics in detail.

Managing Users and Security EMS-BGF User Manual
Workflow
The administrator is responsible for managing users and user groups in the
EMS-BGF, as well as for overseeing the assignment of access rights to specific
user groups. The administrator can also perform various other user
management functions. These administrative actions can be performed in any
order, as required.
Basic operations include:
Managing Users (on page 3-3)
Managing User Groups (on page 3-10)
Managing Roles (on page 3-14)
Managing Domains (on page 3-17)
Changing a Password (on page 3-21)
Working with LCT-BGF (on page 3-24)
Viewing the Security Log (on page 3-25)
Viewing the Action Log (on page 3-27)
The Security Configuration

Window
All EMS-BGF security functions are performed from the Security
Configuration window. The Security Configuration window consists of the
following list:
Users
User Groups
Roles
Domains

EMS-BGF User Manual Managing Users and Security
To access the Security Manager window:

In the main menu of the EMS-BGF, select Security > Security Configuration.
The Security Configuration window opens.
Managing Security Configuration

This section describes how to manage security configuration. This includes
managing users, managing user groups, managing roles, managing domains,
changing passwords, and forcing user logout.
Managing Users
When you log into the EMS-BGF, you enter your user name and password in
the Login dialog box, and then click Apply or press Enter. The EMS-BGF
opens with your user account constraints. What you see in topology views, or
trees such as the Topology Tree are dependent upon your user permissions and
the user group that you belong to. You can only perform tasks assigned to the
user group of which you are a member.
Users are managed in the Security Manager window on the Users tab. Each
user occupies one record.
This section describes how to manage user access, including adding, editing,
and deleting EMS-BGF users.

NOTE: Throughout this section, the term "user" refers to

someone authorized to use EMS-BGF, regardless of whether
he or she is a user of the system on which the EMS-BGF
application runs.
Adding New Users

The system administrator can add new users to the EMS-BGF system.
To add a new user:

1. In the EMS-BGF main window, on the menu bar, select Security >
Security Configuration to open the Security Configuration window.

2. Click Add. The Add User window opens.
3. Fill in the fields, as described in EMS New User Parameters (on page 3-5).
4. Click Apply to save the changes and close the window. (If you only click
Close and not Apply, your changes are not applied.)
Table 3-1: EMS New User Parameters
Field Description
User Name The name used to log on to the EMS-BGF system and access EMS-
BGF functions. User names must be unique.
Full Name User's full (real) name.
Password Password for new user. (For security reasons, passwords are not
displayed on screen.)
Confirm Verification of the users password.
Password
Description More information of the user.

Field Description
User Group The group to which you want to assign new user. From the Group
dropdown list, select:
AdminGroup
SecurityGroup
ConfigurationGroup
ProvisioningGroup
MaintenanceGroup
ObserverGroup
Level1Group
Level2Group
(An EMS-BGF group is a set of users with same capabilities within
system.)
Email User's email address.
Home Phone User's home phone number.
Office Phone User's office phone number.
Cell Phone User's Cell phone number.
Rank Rank of the user.
Expire Date Password expiration date, day, month, and year. When the expiration
date approaches, the system generates a reminder window prompting
you to change the user password.
Is Disabled Select the checkbox if you want to disable a user.

Editing Users
The system administrator can edit user properties in the EMS-BGF system.
To edit a user:
1. Open the Security Configuration window and select User in the left tree
list. The User List tab is displayed.

2. Select a user from the Users List.

3. Click Edit. The Edit User window opens with information about the
selected user.
4. Edit the information that you want to change and click Apply. The new
information is saved.
5. To close the window without making any changes, click Close.

Deleting Users
The system administrator can delete users in the EMS-BGF system when they
are not logged in.
To delete a user:
1. On the Main menu bar, select Security > Security Configuration, the
Security Configuration window opens with the User List tab displayed.
2. Select a user from the User List.

3. Click Delete to directly remove the user from the list.

Managing User Groups

A group is a set of users with the same capabilities assigned to them within the
EMS-BGF system. All users in the group share the assigned capabilities. The
administrator can create new groups or delete existing groups.
User groups allow you to provide users with access to only those functions
(capabilities) they need. More experienced users and managers can be assigned
to groups with more advanced capabilities. Groups can be created for every
type of user at your site.
Users are granted access to network resources by assigning a Resource Domain
to the user group of which the user is a member. This allows you to specify the
part of the network on which the users can operate. A user group can be
assigned multiple resource domains.
User groups are managed in the User Groups in the tree of the Security
Configuration window.

Adding New User Groups

The administrator can create new user groups and assign their group
capabilities. Capabilities cannot be assigned to individual users.
NOTE: The administrator cannot change the capabilities of

predefined EMS-BGF default groups.
To add a new user group:

1. In the EMS-BGF main window, select Security > Security Configuration
in the main menu. In the Security Configuration window, select User
Groups in the left tree list.

2. To add a new user group, click Add. The Add UserGroup window opens.
3. Fill in the fields, as described in the following table.

4. Click Apply to save your changes.
Table 3-2: Fields and buttons in the Add UserGroup window
Field Description
Name The name of the group.
Role The selected capability assigned to the group. The capability
determines what functions members of the group can perform.
Description Description of the group.
Available Users List all available users that can be selected into the new group.
Selected Users List the users that have been selected to the new group.
Available Resource List all available resource domains that can be assigned to the
Domains user group.
Selected Resource List the resource domains assigned to the user group.
Domains
Move-to-right click to remove the selected member from the
left list to the right list.

Field Description
Move-to-left click to move the selected member from the
right list to the left list.
Move-all-to-right click to move all of the members from left
list to the right list.
Move-all-to-left click to move all of the members from the
right list to the left list.
Editing User Groups

Existing user groups can be edited by changing group information in the Edit
UserGroup window. When a group is edited, no change is made to the
members of the group.
To edit a user group:

1. On the Main menu bar, select Security > Security Configuration. In the
Security Configuration window, select User Groups in the left tree list.
Select a user group and click Edit.
2. Change the information as required.

3. When all information is correct, click Apply to save the changes.

Deleting User Groups

User groups can be deleted when they are no longer needed. All users must be
removed from the user group before deleting the group. If users are still
assigned as members of the group you want to delete, a warning message is
displayed.
To delete a user group:

1. On the Main menu bar, select Security > Security Configuration. The
Security Configuration window opens.
2. Click User Groups in the left tree list, select a user group and click Delete.
Managing Roles
A role is a set of functions that a user can perform in EMS-BGF. Users can
access only those functions that are included in the role assigned to their user
group.
The following window shows the Role List tab in the Security Configuration
window.
NOTE: If a user group is assigned a role, that role cannot be

deleted.

Adding New Roles

You can add roles that are tailored to your specific user needs.
To add a new role:

in the main menu. In the Security Configuration window, select Roles in
the left tree list.
2. To add a new role, click Add. The Add Role window opens.


Table 3-3: Fields in the Add UserGroup window
Field Description
Name Enter a name for the new role. This name is listed in the
Name column in the Role List.
Description Enter a description of the new role.
Available Permissions List all of the available permissions.
Selected Permissions List the selected permissions that are to be part of the new
role.
Editing Roles
You can edit existing roles. If the role is in use, the EMS-BGF will prompt you
if you want to perform the edit. All changes take place the next time a user logs
into the system.
To edit a role:
Security Configuration window, select Roles in the left tree list. Select a
role and click Edit.
2. Change the information as you want. When all information is correct, click
Edit to save the changes.

Deleting Roles
You can delete user-created roles. If a capability profile is assigned to a user
group, it cannot be deleted.
To delete a role:
2. Click Roles in the left tree list, select a role and click Delete.
Managing Domains
This section describes how to use the EMS-BGF to manage domains. Resource
domains are managed from the Resource Domain List tab of the Security
Configuration window.

Adding New Domains

You can add a new resource domain to limit user access to only those parts of
the network to which they need access.
To add a new resource domain:

in the main menu. In the Security Configuration window, select Domains
in the left tree list.

2. To add a new domain, click Add. The Add Domain window opens.

Table 3-4: Fields in the Add Domain window
Field Description
Name Enter a name for the new resource domain. This name is listed in the
Name column in the Resource Domain List.
Available NEs List all of the existing NEs that can be selected in the new domain.
Selected NEs List of the selected NEs.
Available List all of the existing available user groups that can be selected in the
UserGroups new domain.
Selected List of the selected user groups.
UserGroups

Editing Domains
Existing resource domains can be edited to meet new network conditions. A
warning message indicates that the changes will affect all user groups that use
this resource domain.
To edit a domain:
Security Configuration window, select Domains in the left tree list. Select
a domain and click Edit.
2. Change the information as you want. When all information is correct, click
Apply to save the changes.
Deleting Domains
Resource domains can be deleted when no longer needed. A resource domain
cannot be deleted if any resource domain is assigned to a user group.
To delete a user group:

2. Click Domains in the left tree list, select a domain and click Delete.

Changing a Password
The EMS-BGF enables administrators to change a currently logged in user
password. Users can also change their own passwords.
To change a password:
1. In the EMS-BGF main window, on the menu bar, select Security >
Change Password. The Change Password window opens.
2. In the Old Password field, type in your current password. (For security
reasons, passwords are always indicated as asterisks.)
3. In the New Password field, type in your new password.
4. In the Confirm Password field, retype your new password.
5. Click Apply to save the changes.

6. If an administrator wants to change an other user's password, select

Security > Security Configuration from the main menu. In the Security
Configuration window, select a user in the User List and click the
Change Password button.
7. Or from the left list of the opened window, click the Users tab to expand
the list of users. Then right-click on the user whose password you want to
change under the Users is to be changed as shown below.

8. From the pop up menu, select Change Password. The Change Password
window opens.
Change the Password as needed and click Apply to save the changes.
Forcing User Logout

The EMS-BGF enables administrators to force the logout of selected users.
To force a user to log out:

1. In the EMS-BGF main window, on the menu bar, select Security > Active
Users. The Active Users window opens.
2. Select a user in the list and click Force Logout. The EMS-BGF User
Login window opens, displaying a message that the selected user was
logged out.
3. To access EMS-BGF, the user must log in again.

Working with LCT-BGF

This section describes the EMS-BGF and the LCT-BGF application
interactions.
If you are logged in to the EMS-BGF with configuration rights for a specific
NE, and a terminal running the LCT-BGF requests to perform configuration
changes to that NE, you will receive a message requesting permission to grant
configuration access.
To grant or deny access to the LCT-BGF:

1. Right-click an NE and select Configuration in the popup menu. Select the
NE Settings tab in the properties area.
2. In the General area, you can see the LCT Security Mode field:
The default state is Waiting for approval.
To approve access, select Approval in the pull-down list.
To reject access, click No approval.
NOTE: Do not make any configuration changes to the NE

from the EMS-BGF while the LCT-BGF is connected. Such
changes can corrupt the NE database.

Viewing the Security Log

The EMS-BGF enables the system administrator to view the history of login
and logout activities.
NOTE: Only the administrator can use the Security Log

function. It cannot be assigned to other users.
To view security Log:

1. In the EMS-BGF main window, select Security > Security Log in the
main menu. The Security Log window opens, displaying the history login
list.

2. Click + in the Filter bar to expand the filter area. Use the following
window to filter information in the Security Log list.
After setting the filter options, select File > Refresh in the menu, or click
on the toolbar to refresh the list.
3. To delete the history logs, select the logs that you want to delete in the list.
Then select File > Delete, or click on the toolbar.

Viewing the Action Log

The EMS-BGF enables the administrator to view the history of a wide range of
actions performed by the EMS-BGF.
To view the action log:

1. In the EMS-BGF main window, select Security > Action Log in the main
menu. The Action Log window opens.
2. Filtering and deleting the action logs are performed in the same manner as
for Viewing the Security Log (on page 3-25).


4
Configuring and Managing
NEs
In this chapter:
Overview ......................................................................................................... 4-1
Workflow ......................................................................................................... 4-2
Creating UMEs ................................................................................................ 4-2
Creating NEs ................................................................................................... 4-5
Slot Assignment............................................................................................... 4-8
Setting NE Time ............................................................................................ 4-13
Routing Table ................................................................................................ 4-14
Managing OSPF ............................................................................................ 4-16
Configuring NE Attributes ............................................................................ 4-24
Batch Modify NE Names .............................................................................. 4-25
Performing NE Discovery ............................................................................. 4-26
Modifying NEs .............................................................................................. 4-28
Removing NEs............................................................................................... 4-31
Resetting NEs ................................................................................................ 4-32
NE Data Backup ............................................................................................ 4-33
Overview
This section describes how to use the EMS-BGF to configure and manage NEs
via the EMS-BGF NE shelf view window.

Configuring and Managing NEs EMS-BGF User Manual
Workflow
You can perform many NE management operations from the NE shelf view
window:
Creating UME (on page 4-2)
Creating NEs (on page 4-5)
Slot Assignment for NEs (on page 4-8)
Configuring NE Attributes (on page 4-24)
Removing NEs (on page 4-31)
Resetting NEs (on page 4-32)
NE Data Backup (on page 4-33)
Creating UMEs
When performing network management with the network element from a third
part equipment, to create the end-to-end XCs, UME is required to simulating
the third part equipment. It can only be used in the Standalone mode.
The following features are supported in UMEs:
Create/Modify UME
Assgin Cards
Create TopoLink
Change the Port Rate
VC4-4c Configuation
Create VCGs
Define MOT
Create Trails (for EMS)
SDH XC List
XC/Trail Export and Import
To performing the above operations, refer to the corresponding procedures of
the NEs.

EMS-BGF User Manual Configuring and Managing NEs
To create a UME:
1. In the main menu, select Configuration > Create > UME. The Create NE
window opens.
There three areas in the Create NE window:

Use the NE Details area to input an NE's information and add it to the
Recent Saved NEs area.
Create the UME in the Recent Saved NEs area.
View the NE shelf in the NE Preview area.
2. Enter the NE Name and NE ID in the NE Details area.
3. Enter the UME's IP address in the IP field in the window.
4. If a group is selected, the UME is added to a specified group.
5. Enter a number in the Batch NE Number field to create a batch UMEs one
time.

6. Click Save to add the UME to the Recent Saved NEs area. Do the same
operations to add more UMEs if needed, as shown in the following
window.
7. Select the UME to be created in the Recent Saved NEs list. Click Select
All to select all the UMEs in the list.
8. Click Create. The following window opens, showing the creating progress:
After all the UMEs in the list are created, click Close to close the window.

9. To remove one UME, right-click on this NE and click Remove in the right
menu.
10. Click Close to close the window without saving any information.
Creating NEs
EMS-BGF allows you to add new NEs to the database. You can add one or
more NEs concurrently.
Whenever you create an NE, an NE icon appears in the EMS-BGF main
window. You can freely move NE icons to any location in the main window by
dragging and dropping.
NOTE: You can only create as many NEs as allowed by your

system license limit.
To Create an NE:
1. In the main menu, select the Create NE button or select

Configuration > Create > NE. The Create NE window opens.
There three areas in the Create NE window:

Use the NE Details area to input an NE's information and add it to the
Recent Saved NEs area.
Create and upload the NE data in the Recent Saved NEs area.
View the NE shelf in the NE Preview area.

2. Enter the NE Name and NE ID in the NE Details area.

3. Enter the NE's IP address and subnet mask in the respective fields in the
window.
4. Click Get NE to retrieve the NE Type from the NE. Or select an NE type
from the Type list.
5. If a group is selected, the NE is added to a specified group.
6. Click Save to add the NE to the Recent Saved NEs area. Do the same
operations to add more NEs if needed, as shown in the following window.
7. Select the NE to be created in the Recent Saved NEs list. Click Select All
to select all the NEs in the list.
8. User can click the Export button to export the NE information to an XML
file.

9. User can click the Import button to import the NE information from an
XML file.
10. Click Create. Click Create&Upload to create and upload the NE data
automatically. The following window opens, showing the creating
progress:
After all the NEs in the list are created, click Close to close the window.
11. Click Hide Groups to hide the groups showing in the list.
12. To remove one NE, right-click on this NE and click Remove in the right
menu.
13. Click Close to close the window without saving any information.
In addition, you can also create NEs in NE List (see "Modifying NEs" on page
4-28).

Slot Assignment
Overview
Slot assignment involves assigning card types for various slots (or subcard
slots) of the NE equipment, setting up objects corresponding to the physical
cards in the EMS-BGF and setting the corresponding values for them, and
displaying icons in the EMS-BGF window. Corresponding card attributes and
services can only be configured after slot assignment is completed.
Slot assignment makes offline configuration of the EMS-BGF possible. You
can conduct all the offline operations after saving the expected logical slots.
The following terms relate to the card assignment process:
Get Logical Card: The logical slot is defined from the top down. This
defines the expected configuration and is both readable and writable.
Get Physical Card: The physical slot is the actual configuration of the
current NE equipment.
Set As Logical: Once you obtain the actual physical cards from the
database, you can set them as logical cards.
Slot Assignment for BG-20 and BG-30

The BG-20 has two units the basic unit (BG-20B) and an extension unit (BG-
20E), which can be stacked together. When a BG-20 NE is created in the EMS-
BGF, it is configured as the BG-20B, and the shelf view window only displays
the BG-20B shelf. You can change the configuration to the BG-20E during slot
assignment by selecting the BG-20E. This action changes the NE icon in the
topology view to the BG-20E icon, and the NE Shelf View window is
refreshed to reflect the change.
Similar to the BG-20, the BG-30 has two units a basic unit (BG-30B) and an
extension unit (BG-30E), which can be stacked together.

To perform slot assignment for the BG-20 and the BG-30:

1. From the main menu, select an NE in the topology view and then select
Configuration > Slot Assignment, or from the menu of the NE shelf,
select Configuration > Slot Assignment. The Slot Assignment window
opens.
2. If the NE is a BG-20E/BG-30E, select the BG20E/BG-30E checkbox.

3. Right-click on a slot in the window, select Add and then select a card in the
pop-up list to assign. Select Delete to delete the card.
4. After adding the corresponding card type in the corresponding slot, click
Apply.
5. Click Get Logical Card to get the expected configuration from database.
Click Get Physical Card to get the actual configuration from the
equipment. If you want to set the physical cards as logical cards, click Set
As Logical.
Slot Assignment for BG-40

This section describes how to perform slot assignment for the BG-40.
To perform slot assignment for the BG-40:

1. From the main menu, select an NE in the topology view and then select
Configuration > Slot Assignment. Or from the menu of NE shelf view,
select Configuration > Slot Assignment. The Slot Assignment window
opens.

Apply.
As Logical.
Slot Assignment for BG-64

This section describes how to perform slot assignment for the BG-64.
To perform slot assignment for the BG-64:

1. From the main menu, select an BG-64 NE in the topology view and then
select Configuration > Slot Assignment. Or from the menu of NE shelf
view, select Configuration > Slot Assignment. The Slot Assignment
window opens.

2. If the NE is a BG-64E, select the BG30E checkbox.
Apply.
6. Click Get Physical Card to get the actual configuration from the
equipment.
7. If you want to set the physical cards as logical cards, click Set As Logical.

Setting NE Time
The default start time in NE devices is not necessarily the actual time. The NE
time must be set so that it is consistent with the actual time after the NE starts
to run. Each NE has its own clock that reflects the NEs time. The time
generated for both alarms and events is determined by the NE time. The real
time of the PC refers to the current time of the EMS-BGF PC. The NE time and
the EMS-BGF PC time should be synchronized.
NOTE: It is suggested that you set the NE time immediately

after you create an NE.
To set the NE time:

1. In the NE shelf view window, select Configuration > NE Time Setting in
the main menu. The NE Time Setting window opens.
2. Click to directly read the system time of the PC, or manually enter the
time.
3. Click to get the NE's time.

4. Click Apply to set the time.
NOTE: It is suggested that you set the NE time immediately

after creating an NE.

Routing Table
Viewing Actual Routes
You can view the actual IP routes of a selected BG-20, BG-30 or BG-64 NE.
To view the actual routes of a BG-30 or BG-64 NE:

1. In a BG-20, BG-30 or BG-64 NE shelf view window, select Configuration
> Routing Table from the menu. The following window opens.
2. Click to retrieve the information to view.

Managing Static Routes

You can view, add, and delete static IP routing entries for a selected BG-20,
BG-30 or BG-64 NE.
To manage the static routes:

1. In a BG-20, BG-30 or BG-64 NE shelf view window, select Configuration
> Routing Table from the menu. From the opened Routing Table
window, select the Static Routes tab.
2. To add a new IP route, select from the toolbar. The Create Static IP
Route window opens.
Enter the relevant IPs as needed and click OK to apply the setting.
3. To delete a static route, select the route you want to delete in the list and
select from the toolbar.

Managing OSPF
OSPF is a routing protocol that determines the best path for routing IP traffic
over a TCP/IP network, based on distance/metric between nodes. OSPF is an
Interior Gateway Protocol (IGP) that works within an Autonomous System
(AS). It is a link state protocol capable of handling large networks with little
protocol traffic overhead.
OSPF Overview
OSPF management is only supported for the BG-30 and BG-64 in EMS-BGF.
OSPF supports the following network connections:
DCC
Gateway
Clear Channel
The following functions are supported by OSPF:
Point-to-Point and Broadcast interfaces
Up to four OSPF areas
Address summarization
Area Border Router (ABR) functionality
Autonomous System Border Router (ASBR) functionality, including
redistribution of Static Routes
Loopback address as Router ID
Configuration of Hello Protocol parameters
Support of "passive" interfaces to allow distribution of routes to attached
devices

To access the OSPF management window:

In a BG-30 or BG-64 NE shelf view window, select the NE in the left
object tree, then select Configuration > IP Networking from the menu.
The IP Networking window opens as shown in the following figure.

Overall OSPF
This section describes how to configure overall OSPF settings.
To configure overall OSPF settings:

1. In a BG-30 or BG-64 NE shelf view window, select the NE in the left
object tree, then select Configuration > IP Networking in the menu.
Select the Overall OSPF tab in the opened window.
The areas in this window are described as follows:

OSPF Enable: state of OSPF, Enable or Disable. The default is
Disable.
AS Border Router: state of ASBR, Enable or Disable. The default is
Disable. When it is set, OSPF advertises its static routes.
OSPF Area ID: comprises 1 to 4 distinct areas coded as 32-bit integers
and displayed as IP addresses. By default, first row of the table shows
the backbone area (0.0.0.0). User can add and remove OSPF areas from
table. There are two constraints for this attribute:
There is at least one row in the table.
Areas used in an area range or defined for an OSPF interface cannot
be removed.

OSPF Area Range Table: supports up to 12 distinct area ranges. Area

ranges are used to summarize NEs advertised over area boundaries.
Users can edit, add, or remove selected rows from the table. Range
Address and Range Mask fields define subnet of NEs. The Area ID
dropdown list displays area IDs already defined. User have to pay more
attention to make sure that the area IDs is configured right.
LAN Emulation Interworking: Toggles built-in LAN emulation
interworking functions. When enabled, this prevents packet duplication
from flooding domain with multiple gateways (dynamic routing
"islands"). When performing OSPF over LAN Emulation interface, the
EMS-BGF performs multicast address translation to allow elements in
flooding domain. Management Address and Management Mask must
match the IP address of Management Station that is defined as subnet.
2. Set the state of OSPF by selecting the Enable or Disable radio button in
the OSPF Enable area.
3. Set the state of ASBR by selecting the Enable or Disable radio button in
the ASBR Enable area. If it is enabled, OSPF advertises its static routes.
4. In the OSPF Area ID area, click + to add a valid ID to the table. The
system downloads the configuration to the NE after performing a validation
check to confirm that the new entry is unique.
5. In the OSPF Area Range Table area, click + to add an area range to the
table.
6. In the LAN Emulation Interworking area, if the LAN Emulation
Interworking checkbox is selected, set the Management Address and
Management Mask in the corresponding fields.
7. Click Apply to save your settings.

Network Interfaces
In the Network Interfaces tab window, user can create, modify, or delete
network interfaces. For one NE, a maximum of 12 IP network interfaces can be
created.
To manage network interfaces:

1. In a BG-30 or BG-64 NE shelf view window, select the NE in the left
object tree, then select Configuration > IP Networking in the menu.
Select the Network Interfaces tab in the opened window.
The Dcc0 network interface is created by default. It cannot be deleted from

the list, but it can be edited.

2. To create a new network interface, click in the toolbar. The Create

New Network Interface window opens.
In the Network Interface Attributes area, the following attributes can be

configured:
Encapsulation: Encapsulation type. The value can be LAN or PPP,
according to the selection in Network Interface drop-down list at the
top of the window.
Numbering: can be set as Unnumbered or Numbered:
Unnumbered: no IP address is assigned.
Numbered: explicit IP address assigned to interface.
IP Address: IP Address of interface.
Mask: Mask for IP Address.
In the OSPF Interface Attributes area, the main attributes that can be
configured are described as follows:
OSPF Enable: the OSPF state can be set as enable or disable. The
default is disabled.
Passive: the OSPF can be set as passive or active.
Passive: Relevant for OSPF enabled interfaces. OSPF protocol is
not performed over interface, but OSPF advertises hosts on
interface subnet. Area ID and Metric attribute must be defined.
Active: Active operational status.
Area ID: Relevant only when OSPF is enabled. Dropdown list allows
selection of area from one of four areas defined in Overall OSPF tab.

3. To edit a network interface, select the interface you want to edit and click
in the toolbar.
4. To delete a network interface, select the interface you want to delete can
click in the toolbar.
DCC Terminations
Terminate DCC refers to the XC which is created between the COM_DCC and
the R_DCC, M_DCC or Clear Channel of the optical ports. This section
describes how to configure the terminate DCC.
To configure the terminate DCC channels:

1. In a BG-30 NE shelf view window, select the NE in the left object tree,
then select Configuration > OSPF Configuration in the menu. Select the
DCC Terminations tab in the opened window.
2. From this window, you can set network interfaces to COM objects by
selecting the interfaces from the dropdown lists.

OSPF Interfaces
The parameters of the OSPF interfaces can only be viewed. You cannot delete
OSPF interfaces from the OSPF interfaces table. The OSPF interface is an
extension of the network interface. There is always an OSPF interface entry
(enabled or disabled) for each network interface. When you delete network
interfaces in the Network interfaces table, OSPF interfaces are automatically
deleted (except for the dcc0 OSPF interface object, which is never deleted).
To view the OSPF interfaces:

1. In a BG-30 NE shelf view window, select the NE in the left object tree,
then select Configuration > OSPF Configuration in the menu. Select the
OSPF Interfaces tab in the opened window.
2. Click in the toolbar to retrieve information of the OSPF interfaces to

view.

Configuring NE Attributes
You can configure NE attributes in the NE Settings window.
NOTE: When performing offline configuration, changes to

NEs are only saved to the EMS-BGF database and are not
actually sent to the NE.
To configure NE attributes:
1. Right-click an NE, and select Configuration in the right menu. In the
opened window, select the NE Settings tab.
2. Set the NE attributes in the window. The read-only attributes without

editing areas cannot be changed.
3. After entering the information, click Apply to send the information to the
NE.
4. Click to refresh the information in the window.

Batch Modify NE Names

This section describes how to batch modify NE's names.
To enable this function, user should firstly go to the EMS-BGF installation
folder open the file client properties under: \EMS-BGF\etc. In the file, modify
"enable_batch_modify_name = false" as "enable_batch_modify_name = true"
and save the file. Restart the EMS-BGF, the function is enabled.
To batch modify NE names:

1. In EMS-BGF main window, select Configuration > Modify > Batch
Modify NE's Name in the main menu. The Modify NE's Name window
opens.
2. Modify the NE names as you need and click OK to save the changes.

Performing NE Discovery
You can use the NE discovery function to find which NEs exist on a specific
shelf. You can create them in the EMS-BGF database if needed.
To perform NE discovery:
1. In the EMS-BGF main window, select Configuration > Discovery > NE
Discovery in the main menu. The NE Auto Discovery window opens.

2. Input the IPs in Search IP Range area, and click Add to add the range to
the list below, as shown in the following figure. To execute more
operations, select the IP range in the list and right-click on it.
3. Click Search to start the NE discovery process. To view the progress

details, click Details. To stop the discovery, click Stop.
4. When the discovery is finished, the results will be displayed in the NE
Discovery Result area. Select a discovered NE that is not in the database.
Click Create NE to create the NE in your database.
5. Click Close to close the window.

Modifying NEs
You can modify NEs in NE List window.
To modify an NE:
1. Select the NE whose information you want to modify and select
Configuration > View > NE List in the main menu. If you do not select an
NE, the NE List window displays a list with all the NEs in the topology.
2. Click in the toolbar to refresh the versions in the list.

3. Select an NE in the list and click in the toolbar to open the Edit NE
window. To search a specific NE, input the NE name in the search area
and click Find.
The NE name and ID are gray. They are read-only attributes and cannot be
edited.
4. Click OK to save the changes.
5. To export the NE list as an XML file, click in the toolbar.
Select the location folder and enter the file name for the XML file, then
click Save.

6. To export the NE list as a CSV file, click in the toolbar.
Select the location folder and enter the file name for the CSV file, then
click Save.
In addition, in the NE List window, you can click to create a new NE. To
delete an NE, select the unwanted NE and click in the toolbar.

Removing NEs
The Removing NE operation removes an NE object from the EMS-BGF,
thereby preventing the EMS-BGF from managing the physical devices
represented by this NE. When deleting an NE, the EMS-BGF deletes the data
on the EMS-BGF side related to the NE.
To remove NEs:
1. In the topology view, select the NEs you want to remove.
2. In the EMS main menu, select Configuration > Delete > NE.
3. In the popped Confirm window, click Yes to delete the NEs. If you don't
want to delete, Click No.
In addition, you can also remove NEs using NE List (see "Modifying NEs" on
page 4-28).

Resetting NEs
The NE reset function is used when an NE physical device does not work
normally and needs to be initialized. The NE reset operation resets all cards
except the MCU. Both warm and cold resets are available. A warm reset resets
only the main processing unit of the card, meaning it resets the application
program that is running. A warm reset has no influence on the service. A cold
reset resets not only the main processing unit but also the peripheral chips. A
cold reset influences services on the card.
To reset an NE:
1. Select the NE you want to reset in the EMS topology view, and then select
Maintenance > Reset NE in the main menu.
2. Select the Warm Reset or Cold Reset radio button.

3. Click OK. A confirmation window opens prompting you to confirm
resetting.
4. Click Yes to confirm.

NE Data Backup
This section describes the NE data backup procedure, which simplifies network
management and maintenance tasks.
To backup NE DB File:
1. Select the NEs whose data you want to back up, and select Maintenance >
NE DB > Backup in the main menu. If you do not select one, the Backup
NE DB File window displays a list with all the NEs in the topology.
2. Select the NEs that you want to back up by clicking the adjacent
checkboxes.
3. Click Set Backup File Path to select a folder in which to save the file.
4. If you want to backup the NE data to RDR Server, select the Backup to
RDR Server checkbox. To make the checkbox available, you have to
enable the RDR that described in Failover Processing (on page E-4).
5. Click Start to activate the NE data backup program.
6. Click Stop to stop the program.

To restore the NE data backup:

1. Select the NEs whose you want to restore, and select Maintenance > NE
DB > Restore in the main menu. If you do not select one, the Restore NE
DB File window displays a list with all the NEs in the topology.
2. Select the NEs that you want to restore by clicking the adjacent
checkboxes.
3. Click the button in File Name list to select the folder containing the backup
file to restore.
4. Click Start to activate the NE data restore program.
5. Click Stop to stop the program.

To backup NE DB automatically:
1. In the EMS-BGF main topology view, select Maintenance > NE DB >
Backup Settings in the main menu. The NE DB Backup Setting window
opens.
2. Configure the parameters as required:

Interval Day: the interval for which day you want to save, for example:
1 will be every day, 2 will perform the NE DB Backup in each second
day and etc.
Backup Time: the database will backup automatically at the time you
set periodically.
Max Thread: the maximum number of threads.
Max Backup File: the maximum number of backup files.
Backup Path: the directory for saving the backup files in the Backup
Directory area.
3. If you want to backup the NE data automatically to RDR Server, select the
Backup to RDR Server checkbox. To make the checkbox available, you
have to enable the RDR that described in Failover Processing (on page E-
4).
4. Click Apply to save the NE DB backup settings.


5
Configuring Timing Source
In this chapter:
Overview ......................................................................................................... 5-1
Configuring the Synchronous Timing Table ................................................... 5-2
Configuring the Synchronous Ethernet ........................................................... 5-5
Configuring PCM Timing ............................................................................... 5-9
Overview
Synchronous timing configuration enables an NE to automatically select and be
synchronized with the highest-quality clock source in the network. This
achieves clock synchronization for the entire network.
The following operations can be performed:
Configuring synchronous timing
Obtaining the clock working mode
Calibrating the clock card frequency
Calibrating the active/standby switching of the clock card
These operations can be performed at the system operator level.
The NE synchronous timing table window lists all the clocks for external
references that can be selected. You manually select options and set priorities
for them to form a synchronous clock table, and then send it to the equipment.
After setting the synchronous timing table, determine whether the equipment is
correctly locked with the expected clock source by viewing the clock working
mode. In addition, you can view the current clock working mode and clock
reference of the NE in the NE shelf view's Timing Settings window.

Configuring Timing Source EMS-BGF User Manual
Configuring the Synchronous

Timing Table
The handling of synchronous timing for SDH equipment utilizes a
Synchronous Timing table. The NE Synchronous Timing table enables you to
determine the selection range of NE references and customize the attributes of
each external reference. The Synchronous Timing table specifies the quality
level and availability status of the external references.
Each NE has a Synchronous Timing table that collects all the optional clock
references and various attributes for the NEs current configuration. The NE
equipment can select the reference with the optimum quality in this table as its
synchronous timing source.
Each clock reference has multiple reference attributes, including the reference
ID, physical location, clock frequency, synchronous status S1 type value, S1
user-defined attributes, priority, availability status, and application status.
Using these attributes, you can identify a reference, specify its quality level,
monitor its availability status, and control its application.
This section describes how to configure synchronous timing for NEs in the
EMS-BGF.
To configure synchronous timing for the BG-40:

1. In BG-40 NE shelf view window, select Control and Physical Object >
MXC4X in the left object tree and then select the Timing Settings tab
under Configuration working mode.

EMS-BGF User Manual Configuring Timing Source

3. Select the corresponding external references for the clock.
4. Click Apply to send the external clock references to the NE.
5. Click to copy the settings to other NEs.

The clock availability status indicates whether the clock reference is currently
available. This field is read-only and cannot be modified.
To configure synchronous timing for the BG-20/BG-

20C/BG-30:
1. In BG-20/BG-20C/BG-30 NE shelf view window, select Control and
Physical Object > TMU in the left object tree and then select the Timing
Settings tab under Configuration working mode.
2. For each timing priority, select the corresponding external references for
the clock.

To configure synchronous timing for the BG-64:

1. In BG-64 NE shelf view window, select Control and Physical Object >
XS A: TMU in the left object tree and then select the Timing Settings tab
under Configuration working mode.
2. For each timing priority, select the corresponding external references for
the clock.

Configuring the Synchronous

Ethernet
Only the GbE ports of the following cards support Synchronous Ethernet:
ME_2G_4F
MPS_2G_8F
DMGE_4_L2
DMGE_8_L2
Following is a figure indicating the Hybrid SDH/Synchronous Ethernet
Synchronous Equipment Timing Source (SETS) function.
The figure shows the equivalent selection mechanism of an SDH SETS

function that has been adapted to hybrid SDH/Synchronous Ethernet equipment
having Synchronous Ethernet and SDH interfaces. ETY & STM-N input (TE
and T1) and output (T0) represent the various Ethernet traffic interfaces
(100BASE-TX, 1000BASE-SX, etc.) and SDH traffic interfaces. The SETG
has characteristics defined in ITU-T G.8262/Y.1362 for Synchronous Ethernet
and in ITU-T G.813 and G.812 for SDH. Also note that in North American
networks the use of the T4 interface is to provide network timing to a
BITS/SSU only. Selection of line interfaces (TE or T1 in the figure) is only
provided via selector A. Selector C can only select the output from Selector A.
T4 is not filtered by the SETG, as any filtering is done by the BITS/SSU.

To configure the Synchronous Ethernet:

1. In the NE shelf view window, select a GE-ETY port under the card that
supports Synchronous Ethernet, then select the General tab under
Configuration working mode.
2. To configure the Synchronous Ethernet, the related attributes are described

as below:
PHY Type: The Synchronous Ethernet attributes are effective only
when the PHY Type is configured as 1000Base-T or
10/100/1000Base-T mode.
Master-slave Manual Configuration: This attribute defines if
master/slave mode of PHY is configured manually or auto-negotiated.
Enable: master/slave is configured manually during negotiation.
Disable: master/slave is negotiated automatically.
Local Master-slave Mode: This attribute is available only when
Master/slave Manual Configuration is enabled, it defines the value of
master/slave of local PHY during negotiation.
Master: local PHY is configured as master during negotiation.
Slave: local PHY is configured as slave during negotiation.

Master-slave Resolution: This is a read-only attribute which indicates

the current status of PHY master/slave resolution. It can be Master or
Slave, depending on real resolution of current 1000Base-T link. It is
N/A when current PHY is not working in 1000Base-Tx mode.
ESMC Generation: For an ETY port, Synchronization Status Message
(SSM) is carried through Ethernet Synchronization Messaging Channel
(ESMC). SSM definition is same as SDH port per ITU-T G.781, and
the rules of SSM generation and reception are same as G.781 (such as
loop prevention, QL change, SSM delay, etc.). It should be configured
as Enable when ETY port is selected as timing source with SSM
enabled. Otherwise, DNU cant be sent out.
3. To set the TMU configuration for supporting Synchronous Ethernet, select
Control and Physical Object > XS A:TMU in the left object tree, then
select the Timing Settings tab under the Configuration working mode.

4. Select a timing source in the Timing Source drop-down list and then set
the relevant parameters of the timing source as required.
In the following table, only the ports whose TE Capable is Yes can be
selected as timing source. TE Capable means being able to be selected as
nominated TE/T4 timing source of TMU.
Table 5-1: Synchronous Ethernet capability of Layer 2 cards
Card Type ETY Port PHY Type TE Capable

DMGE_4_L2 GbE 1#~4# (SFP only) 1000Base-X Yes
1000Base-T No
DMGE_8_L2 GbE 1#-2# (COMBO) 1000Base-X Yes
10/100/1000Base-T Yes
GbE 3#~8# (SFP only) 1000Base-X Yes
1000Base-T No
ME_2G_4F GbE 1#~2# (COMBO) 1000Base-X Yes
100Base-FX Yes
10/100/1000Base-T Yes
FE 1#~2# 10/100Base-T No
FX 1#~2# 100Base-FX No
MPS_2G_8F GbE 1#~2# (COMBO) 1000Base-X Yes
100Base-FX Yes
10/100/1000Base-T Yes
FE 1#~8# 10/100Base-T No

The principle of the parallel selection of the timing source number is:
2 for BG-20B D-slot
2 for BG-20E E-slot
1 for BG-30E/BG-64E E-slot
2 for BG-30B/BG-64 T-slot
If a GE port has been selected as timing source, the current PHY Type
cannot be changed to the PHY Type whose TE Capable is No in the
above table, and the Local Master-slave Mode cannot be set as Master.
Click Apply to save the settings.
Configuring PCM Timing

Synchronous timing configuration of a PCM card enables the card to
automatically select and be synchronized with the highest-quality clock source
in the network. This achieves clock synchronization for the entire network.
To configure SM10 timing:

1. Right-click on a BG-40 NE, select Configuration. In the opened shelf
view, select SM10 in the left object tree and select the Timing Settings tab
in the properties area.
2. Click to retrieve the timing configuration from the equipment.

3. Set the timing parameters and click Apply to send the configuration to the
EMS-BGF database and the equipment.

To configure SM_10E timing:

1. Right-click on a BG-20 NE, select Configuration. In the opened shelf
view, click SM_10E > TMU in the left object tree and select the Timing
Settings tab in the properties area.
2. Click to retrieve the timing configuration from the equipment.

3. Set the timing parameters and click Apply to send the configuration to the
EMS-BGF database and the equipment.

6
Configuring and Managing
Cards
In this chapter:
Overview ......................................................................................................... 6-1
Workflow ......................................................................................................... 6-1
Working with Cards......................................................................................... 6-2
Managing the BG_OW .................................................................................. 6-16
PDH Cards ..................................................................................................... 6-20
SDH Cards ..................................................................................................... 6-23
Data Cards ..................................................................................................... 6-30
PCM Cards .................................................................................................. 6-143
Control Cards............................................................................................... 6-152
Power Units ................................................................................................. 6-164
Fan Control Units ........................................................................................ 6-165
Overview
This section discusses how to use the EMS-BGF to configure and manage
cards.
Workflow
You can configure and manage the following types of cards in the EMS-BGF:
SDH cards: includes E1, E3 and STM-1/STM-4 cards.
Optical cards: includes SAMQ, SMQ1_4, SMS4, OMD1, S1_4 cards.
XIO cards: includes XIO30-1/4/16, XIO30Q_1&4 and XIO64 cards.
Data cards: includes Layer 1, Layer 2, MPLS and EOP cards.
PCM cards: includes SM10 and SM_10E cards.

Configuring and Managing Cards EMS-BGF User Manual
Working with Cards

Configuring Card Attributes
Card attributes depend on the configuration requirements for each card. In the
Card Attributes Setup window, you can configure overhead parameters,
loopback attributes, and special card attributes.
To configure card attributes:

1. In the NE shelf view window, select a card in the left object tree and select
the Configuration working mode. The descriptive information for each
card is displayed in the General tab.

EMS-BGF User Manual Configuring and Managing Cards
2. To configure the overhead parameters, select the TTI and TSL tab in the
properties area.
3. To configure the attribute for a single VC-4/VC-12, select the VC-4/VC-12

in the tree, and then select the Configuration working mode.
To view the overhead information of a single VC-4/VC-12, select the VCs

tab from the above window.

5. Click to retrieve the information.
Card Layout Description

This section describes the layout of the cards.
BG-40
The BG-40 is a compact STM-1/STM-4-compatible multiservice transmission
system offering powerful expansion capabilities. Within its 2 U (88 mm)
height, it can provide a maximum of either 88 E1 services, 10 E3/DS-3
services, or 36 10BaseT/100BaseT Ethernet services. It also supports six 155
Mbps optical or electrical interfaces, or two 622 Mbps optical interfaces and
two 155 Mbps optical or electrical interfaces simultaneously. According to
networking needs, it can be flexibly configured as TM, ADM, or multi-ADM.
In addition, it supports a variety of complete and flexible network-level
protection.
The BG-40 supports two power supply modes: -48 VDC and 220 VAC. In
combination with its multiservice access capability, small size, and low cost, it
can be deployed widely in various carrier MAN access layers and private
communication networks.
The BG-40 card layout diagram is shown in the following figure.
The following designations apply in this diagram:

MS designates the main slot.
ES1 and ES2 are extension slots.
PS is the power module slot.
DS1, DS2, and DS3 are the three service daughterboard slots on the main
board.
DS-OW is the orderwire daughterboard slot on the main board.
In the BG-40, the card applicable to each slot is shown in the following table.

Table 6-1: Description of BG-40 cards and applicable slots
Module Description MS DS1 DS2 DS3 DS-OW ES1 ES2 PS

MXC4X Cross connect, timing,
and control card
OMD1 2_STM-1 optical or
electrical module
OMS4 1_STM-4 module
MET_L1 4_10/100BaseT module
OW_4X Orderwire module
M345_2 3_E3/DS-3 module
ME1_8F 8_E1 module
PE1_32 32_E1 card
PE1_16 16_E1 card
P345_3 3_E3/DS3 card
FE_L12 Ethernet card with L2
switch
(16_10/100BaseT)
ESW_2G_8F L1/2 Ethernet card with
2xGbE and
8x10/100BaseT
interfaces
SM10 Intelligent PCM card
(26-channel N_64
Kbps)
Note: Only one card
can be installed in a
BG-40 shelf
INF_40X Power Filter Unit
(-48 VDC)
AC_CONV-40X Power Conversion Unit
(220 VAC)

BG-20
The BG-20 is a compact STM-1/STM-4-compatible multiservice transmission
system offering powerful expansion capabilities. It is a multipurpose SDH
network element that supports ring, chain, and mesh network topologies.

ESlots (ES1/ES2/ES3) are extension slots.
BASE designates the main slot.
FCU indicates the fan slot.
INF is the power module slot.
DSlot is the service daughterboard slot on the main board.
In the BG-20, the card applicable to each slot is shown in the following table.

Module BG-20B BG-20E
PS_B FS_B MS L12 Dslot OW PS_E FS_E ES1 ES2 ES3
INF_20B
AC_CONV_20B
FCU_20B
MXC-20
L1B_6F
MESW_6F
MPS_6F
M345_3
SMD1
SMD1H
OMS4B
OMS4H
MEOP_4

Module BG-20B BG-20E

PS_B FS_B MS L12 Dslot OW PS_E FS_E ES1 ES2 ES3
MEOP_4H
MGE_1_L1
ME1_21
ME1_21H
ME1_42
ME1_42H
ME_2G_4F
INF-20E
AC_CONV_20E
FCU-20E
ESW_2G_8F_E
MPS_2G_8F
PE1_63
P345_3E
SM_10E
S1_4
BG-OW
BG-20C
The BG-20C is a new, very low cost and miniature MSPP product. The
Hardware architecture is based on BG-20B_L2M, but without any
extensibility.
The BG-20C provides a very low cost, miniature and MPLS capable
demarcation platform. It is small STM-1/4 TM/ADM equipment with fixed E1
and FE interfaces. To meet the tough TTM, BG-20C is designed based on BG-
20B_L2M platform by removing unnecessary functions & interfaces and
merging everything to a single board.
BG-30
The BG-30 is a miniature, low-cost, flexible, redundant ADM1/4/16 MSPP for
access networks, offered as part of the overall Network Solutions Division
solution. It supports interoperability with the XDM and the BG-40/BG-20 in all
aspects, including SDH, PDH, Data, DCC, management, and other net-wide
functions.
The BG-30 can interface both SDH and data functions at a very low cost, very
small size, and with a wide operating temperature and humidity range. It can be
mounted on street cabinets, indoors, and on walls.

The BG-30 includes two units the BG-30B (base unit) and the BG-30E
(expansion unit). The BG-30B offers a lower entry cost, while the BG-30E
enables higher expandability. All expansion cards for the BG-20E can be
reused in the BG-30E.

PSA, PSB: power supply module slots for the BG-30B and BG-30E
XSA, XSB: XIO module slots for the BG-30B
MS: MCP module slot for the BG-30B
TS 1#, 2#, 3#: tributary module slots for the BG-30B
FS: FCU module slot for the BG-30B and the BG-30E
ES 1#, 2#, 3#: expansion card slots for the BG-30E
The following table provides a description of each BG-30 card and its
applicable slot in the shelf.
Module Description Applicable slot

INF-30B Single input DC power supply PSA_B, PSB_B
module, with input filtering and Fan
Power supply
INF-30BH Enhanced INF for BG-30B shelf PSA_B, PSB_B
INF-30E Single input DC power supply PSA_E, PSB_E
module, with input filtering and Fan
Power supply
AC_CONV-30B Single input AC power supply card, PSA_B (will also
with AC to -48V converter and Fan occupy PSB space)
Power supply
AC_CONV-30E Single input AC power supply card, PSA_E (will also
with AC to -48V converter and Fan occupy PSB space)
Power supply


FCU-30B Fan Control units with Fans for BG- FS_B
30B shelf, also includes the
connector for T3/T4 interfaces
FCU-30BH Enhanced FCU for BG-30B shelf FS_B
FCU-30E Fan Control units with Fans for BG- FS_E
30E shelf
MCP30 A card with the units main CPU, MS
providing main control,
communication and overhead
processing functions, and various
management and housekeeping
interfaces
MCP30B an enhanced substitute for MCP30 MS
XIO30-1 A card with one STM1o/e aggregate XSA, XSB
interface, SDH XC and timing unit
XIO30-4 A card with one STM1/STM4 XSA, XSB
compatible aggregate interface, SDH
XC and timing unit
XIO30Q_1&4 A card with 4 STM1/4 aggregate XSA, XSB
interfaces, SDH XC and timing unit
XIO30-16 A card with one STM16 aggregate XSA, XSB
interface, SDH XC and timing unit
PME1_21 21 x E1 (balanced only) tributary TS1#, TS2#, TS3#
card
PME1_63 63 x E1 (balanced only) tributary TS1#, TS2#, TS3#
card
PM345_3 3 x E3/DS3 tributary. Each interface TS1#, TS2#, TS3#
can be configured to E3 or DS3
independently
DMFE_4_L1 L1 card with 4 x 10/100Base-T TS1#, TS2#, TS3#
interfaces and 4 EoP WANs
DMFE_4_L2 L2 card with 4 x 10/100Base-T TS1#, TS2#, TS3#
interfaces and 8 EoS WANs
DMFX_4_L1 L1 card with 4 x 10/100Base-FX TS1#, TS2#, TS3#
DMFX_4_L2 L2 card with 4 x 10/100Base-FX TS1#, TS2#, TS3#
DMEOP_4 AC/DC power converter and FAN TS1#, TS2#, TS3#
power supply unit for BG-20B
DMGE_1_L1 L1 card with 1 x GbE interfaces TS1#, TS2#, TS3#


SMD1B 2 x STM-1 interfaces card, each SFP TS1#, TS2#, TS3#
can be electrical or optical
SMS4 1 x STM-4 interfaces card TS1#, TS2#, TS3#
SMD4 2 x STM-4 interfaces card TS2#, TS3#
SMQ1 IO card with 4 x STM-1 TS1#, TS2#, TS3#
SMQ1&4 4 x STM-1/4 interfaces card TS1#, TS2#, TS3#
SMS16 Single STM-16 IO card TS1#, TS2#, TS3#
PE1_63 63 x E1 (balanced only) expansion ES1#, ES2#, ES3#
card
P345_3E 3 x E3/DS3 tributary. Each interface ES1#, ES2#, ES3#
can be configured to E3 or DS3
independently
S1_4 4 x STM-1 interfaces card, each SFP ES1#, ES2#, ES3#
can be electrical or optical
S4_1 1 x STM-4 interfaces card ES1#, ES2#, ES3#
ESW_2G_8F_E L2 data expansion card with 2 x GBE ES1#, ES2#, ES3#
and 8 x 10/100Base-T interfaces and
16 EoS WANs
MPS_2G_8F L2 data expansion card with 2 x GBE ES1#, ES2#, ES3#
and 8 x 10/100Base-T interfaces and
at least 16 EoS WANs, both provider
bridge and MPLS are supported.
SM_10E PCM expansion card withDXC1/0 ES1#, ES2#, ES3#
and up to 24 channels of varies types
of Nx64k interfaces
TP21_2 TP card for 21_E1 interfaces in 1:2 ES1#, ES2#, ES3#
protection mode.
TPS1_1 TP card for 4_STM1 or 3_E3/DS3 ES1#, ES2#, ES3#
cards in 1:1 protection mode.
TP63_1 TP card for 63_E1 interfaces in 1:1 ES3#
protection scheme.

BG-64
BG-64 is a low cost, miniature, redundant ADM-64 Multiple Service Transport
Platform (MSTP) for NGN (MSAN), Cellular hub migration, Ethernet
aggregation and TDM.
The BG-64 card layout diagram is shown in the following figure. BG-30E shelf
can be assigned. Default is not assigned.

INF-64: DC power supply and input filter, redundant
FCU-64: Fan unit for BG-64
MCP64: main control card for BG-64
XIO64: XFP based STM-64 interface, timing unit, cross-connect matrix,
support redundancy
TS 1#~7#: tributary module slots for BG-64. The slot dimension is the
same as BG-30B Tslot.
The following table provides a description of each BG-64 card and its
applicable slot in the shelf.

Module BG-64 BG-30E
PS A PS B FS MS XSA XSB TS1 TS2 TS3 TS4 TS5 TS6 TS7 PSA_E PSB_E FS_E ES1 ES2 ES3
INF-64
FCU_64
MCP64
XIO64
XIO16_4
PME1_21
PME1_63
PM345_3
SMQ1
SMQ1&4 V

Module BG-64 BG-30E

PS A PS B FS MS XSA XSB TS1 TS2 TS3 TS4 TS5 TS6 TS7 PSA_E PSB_E FS_E ES1 ES2 ES3
SMS16
DMFE_4_L1
DMFX_4_L
1
DMFE_4_L2
DMFX_4_L
2
DMGE_1_L
1
DMGE_4_L
1
DMGE_2_L
2
DMGE_4_L
2
DMGE_8_L
2
INF_30E
AC_CONV_
30E
FCU_30E
PE1_63
P345_3E
S1_4
SM_10E
MPS_2G_8F
TPS1_1

Hot Insertion
Hot insertion enables you to insert cards on the equipment without powering
off. To increase system availability, hot insertion is used to reduce down time
and facilitate system upgrades.
The EMS-BGF can assign ME1_42H, ME1_21H, SMD1H, OMS4H, and
MGE_1_L1 cards in the BG-20 NE:
The following cards, modules, and functionality support hot insertion:

ME1_42H: 42 x E1 module for a Dslot that supports hot insertion. The
card supports full interchangeability with the current ME1_42, but has a
different card type.
ME1_21H: 21 x E1 module for a Dslot that supports hot insertion. The
card supports full interchangeability with the current ME1_21, but has a
SMD1H: 2 x STM-1 module for a Dslot that supports hot insertion. The
card supports full interchangeability with the current SMD1, but has a
OMS4H: single STM-4 module for a Dslot that supports hot insertion. The
card supports full interchangeability with the current OMS4B, but has a
MEOP_4H: 4 x FE EOP module for a Dslot that supports hot insertion.
The card supports full interchangeability with the current MEOP_4, but has
a different card type.
MGE_1_L1: Single GbE module with layer 1 functionality.

Slot Reassignment
Reassigning a card means assigning a higher-capacity card of the same card
type to a slot that already has a slot assignment. This may be a traffic-affecting
operation, and the operation can be performed even if the original card is
carrying live traffic.
Reassignment features are as follows:
Reassignment deletes the current logical card and assigns the new logical
card.
Unlike the Delete operation, reassignment allows the traffic existing on the
old card to be kept and moved to the new card smoothly.
To support reassignment, the cross connection and related properties of the
old card should be mapped to the new card.
Reassignment moves the existing cross connection and properties to the
new card automatically.
Reassignment is an operation for a logical card (not a physical card).
Reassignment has strict requirements regarding the order in which you
perform the required operations. You must first change the physical card
and then reassign the required logical card. Reassignment will fail if the
physical card is not changed to the required card.
The BG-30 supports reassignment for XIO30-1/XIO30-4/XIO30-
16/XIO30Q_1&4 cards.
Reassignment Procedure
The following figure illustrates the BG-30 reassignment procedure.
As illustrated in the preceding figure, the Expected Card is the logical card and
the Actual Card is the physical card.

Several reassignment status issues exist in the system. These are:

1. Initial status (traffic is normal on the old card).
2. Card is reassigned, but not replaced (not permitted).
3. Card is reassigned and replaced (traffic is normal on the new card).
4. Card is replaced, but not reassigned (compatible; traffic OK).
The proper reassignment procedure is 1 4 3:
1. Check the initial status. The traffic should be normal.
2. Replace the physical card.
3. Perform the reassignment.
Setting the Laser On/Off Status

This operation controls the on/off status of each laser. An automatic shutdown
function can be used to shut down the laser when a received loss of signal
(LOS) is detected.
To set the laser on/off status:

1. In the NE shelf view window, select an optical interface in the left object
tree, and then select the Maintenance working mode. The window opens
as shown below.

2. Click to obtain the laser on/off attribute of this optical interface from
the NE.
3. Set the laser attribute value, as required.
4. Click Apply to send the attribute value to an NE, and save it to the
database.
Managing the BG_OW

The external orderwire (OW) box provides orderwire functionality using 64
Kbps voice communication channels between NEs. These channels are used for
interfacing with the BG-20B, conference processing, CODECs, DTMF
detection, signal processing, four-wire interfaces to the handset, and so on.
Slot Assignment for OW

This section describes the procedure for assigning the OW card.
To assign the OW card:

1. Select an NE in the EMS topology map, and then select Configuration >
Slot Assignment in the main menu. The Slot Assignment window opens.

2. Right-click on the OW slot and select Add > OW in the popup menu.
3. Click Apply to send the configuration to the NE and the database.
Configuring OW Settings
Orderwire attribute configuration configures the orderwire telephone, orderwire
attributes, and orderwire routing of all NEs. Orderwire telephone configuration
relates to the entire network and can only be performed on NEs in the
management domain. Operation authorities are needed from all NEs in the
network to perform orderwire configuration in the network.
The orderwire telephone is used for orderwire contacts between SDH NEs that
support the addressing call and conference calls. The orderwire number is a
three-digit integer number.
SDH orderwire provides communication for field engineers and equipment
maintenance personnel, and supports address selective calls and conference
calls.

To configure BG-40 orderwire settings:

1. In the BG-40 NE shelf view window, select Control and Physical Object
> OW in the left object tree. Then select the OW Settings tab under the
2. Configure the settings in the window. The parameters are describes as

below:
Phone Number 1 /Phone Number 2: the orderwire number of the end
NE.
Conference Call Attribute: refers to the NE conference telephone when
it is used in conversation. There are two options: Listen and Talk and
Listen Only.
Conference Call Number: refers to the conference telephone number for
all NEs that support conference calling.
Conference waiting time: applies to the entire network. The unit is
seconds.
3. Click Apply to deliver the orderwire attributes of the NE to the NE
equipment and save them to the database.
4. Click to display the NE orderwire attributes obtained from the NE

equipment.

To configure BG-20/BG-30/BG-64 orderwire settings:

1. In the BG-20/BG-30/BG-64 NE shelf view window, select Control and
Physical Object > OW in the left object tree. Then select the OW Settings
tab under the Configuration working mode.
2. Configure the settings in the window.

3. Click Apply to deliver the orderwire attributes of the NE to the NE
equipment and save them to the database.
4. Click to display the NE orderwire attributes obtained from the NE

equipment.

PDH Cards
PDH cards include E1 and E3 cards, as described in this section.
E1 Cards
Following lists the E1 cards:
ME1_8F: 8_E1 card for BG-40.
ME1_8: 8_E1 card for BG-40 (fixed).
PE1_16: 16_E1 card for BG-40.
PE1_32: 32_E1 card for BG-40.
EME1_21: 21_E1 interfaces with mappers and LIU functionality for BG-
20.
ME1_21: 21_E1 card for BG-20.
ME1_21H: 21_E1 card supporting hot-swapping for BG-20.
ME1_42: 42_E1 card for BG-20.
ME1_42H: 42_E1 card supporting hot-swapping for BG-20.
PME1_21: 21_E1 card for BG-30B and BG-64.
PME1_63: 61_E1 card for BG-30B and BG-64.
PE1_63: 63_E1 card for BG-20 and BG-30.
You can perform overhead attribute and E1 port attribute configuration for E1
cards.

To configure E1 cards:
1. In the NE shelf view window, select an E1 card in the left object tree. Then
select the E1 Ports tab under the Configuration working mode.

E3 Cards
These are the E3 cards:
P345_3: 3 configurable E3/DS3 card for BG-40.
M345_3: 3 configurable E3/DS3 card for BG-20.
M345_2: 2 configurable E3/DS3 card for BG-40.
PM345_3: 3 configurable E3/DS3 card for BG-30B and BG-64.
P345_3E: 3 configurable E3/DS3 extension card in BG-30E.
To configure E3 cards:
1. In the NE shelf view window, select an E3 card in the left object tree. Then
select the E3/DS3 Ports tab under the Configuration working mode.

SDH Cards
This section describes the SDH cards.
SAM-1/SAM-4
The SAM1/4 is not a physical card or module, but is an abstract object of the
BG-20B SDH interface. The BG-20B SDH interface is STM-1/4-compatible,
and can be switched between STM-1 and STM-4 smoothly by software
configuration without affecting traffic.
Upgrading the BG-20B from STM-1 to STM-4 or installing a BG-20B as an
STM-4 NE requires a license. The STM-4 license is based on the NE serial
number, and is against an appropriate purchase order accompanied by a list of
required serial numbers.
NOTE: For details about handling license keys for an STM-4

license, refer to Managing License (on page I-1).
To switch between SAM1 and SAM4:

1. In the BG-20 NE shelf view window, select Configuration > Slot
Assignment from the menu. The Slot Assignment window opens.

2. Right-click on the A1 or A2 slot and select SAM4 from the pop up menu.
3. Click Apply to save the change. The SDH interface is smoothly switched
to STM-4.
SMD4
SMD4 provides two STM-4 ports. It can only be inserted to Tslot 2# and Tslot
3# of BG-30B, and can only be assigned in ADM-16 configurations.
VC-4 Contiguous Concatenation

The following cards support VC-4 concatenation:
SAM-16
SAMQ
SMS4
SMD4
SMQ1_4
In these cards, VC-4s can be concatenated. After being concatenated, the four
VC-4s can only operate as one managed object until concatenation is released.
A VC-4 concatenation can only be released when no trail exists on it.

To create VC-4 contiguous concatenation:

1. In the NE shelf view window, in the left object tree, select the card that
support VC-4 concatenation. Then select the VC-4 Concatenation tab
under the Configuration working mode.
2. Select the VC-4-4c concatenated checkbox as required.

SMQ1
The SMQ1 card is a new IO card with 4 x STM-1 that can be inserted to any
Tslot of BG-30B and BG-64.

SMQ1&4
The SMQ1&4 card can be inserted to any Tslot of BG-30B and BG-64, but can
only be assigned in ADM-16 configurations. It has four SDH ports and each
port rate is STM-1/4 compatible.
To change rate for SMQ1&4:

1. In a BG-30 or BG-64 NE shelf view window, in the left object tree, select a
port under SMQ1&4 card. Then select the Rate Setting tab under the
Configuration working mode, as shown in the following figure.
2. Click in the toolbar to get the information from the database in order to
view it.
3. Select the Change rate to STM-4 radio button as required.

SMS16
SMD4 is a single STM-16 IO card with SFP based STM-16 interface. It has
same PCB as SMQ1&4 and can only be assigned in BG-30B ADM-16 system
and BG64.
The SMS16 card can provide the following features:
Supports 1 X STM-16 and can be inserted to BG-30B ADM-16 system and
BG64
Based on SFP modules and supports uncolored and colored SFP.
Provides the backplane interfacing with 2 x 2.5G ESSI links, STM-16
Framing, HOPP, TUPP and L-code insertion functions
Traffic and Timing signals connect to both XIO cards and supports the
switching between two XIO cards with ACT signals from two XIO cards
Provides one timing references to each XIO card
Provides the conversion between RS&MS bytes and System Overhead
interface (8M PCM).
Without local CPU and is controlled by CPU in MCP30/MCP30B
Output 1 timing reference clock to TMU.
External interfaces:
1 x STM-16: SFP
Channel LEDs: 1 x laser On
Card level LEDs: ACT, FAIL
XIO30-1/XIO30-4/XIO30-16/XIO30Q_1&4
The XIO30 card integrates the cross-connect matrix, timing module, and SAM
module. The XIO30-1 card contains the SAM1 module, the XIO30-4 contains
the SAM4 module, the XIO30-16 contains the SAM16 module, and the
XIO30Q_1&4 contains the SAMQ module. The XIO30 card supports 1+1
protection. This means that, from a logical perspective, there is always one
main XIO30 card and one standby XIO30 card.
The ADM rate is decided by the XIO30 card type:
XIO30-1: ADM-1
XIO30-4: ADM-4
XIO30-16: ADM-16
XIO30Q_1&4: 4 x ADM-1/4
For XIO30Q_1&4, its SAMQ module has four SDH ports and each port rate is
STM-1/4 compatible, which is the same with SMQ1&4 (on page 6-26).

For XIO30-1, XIO30-4 and XIO30-16 cards, an ADM rate change is achieved
by XIO30 reassignment:
XIO30-1 can be reassigned to XIO30-4 or XIO30-16 without removing
existing traffic.
XIO30-4 can be reassigned to XIO30-1 or XIO30-16 without removing
existing traffic.
And you can perform downgrading from XIO30-16 to XIO30-1 or XIO30-4 in
the BG-30 Slot Assignment window.
To perform reassignment for XIO30-1 and XIO30-4:

1. In a BG-30 NE shelf view window, select XS A:XIO30-1 in the left object
tree. Then select the Reassign tab under Configuration working mode.
2. Select the relevant reassign radio button in the window.

3. Click Apply. A confirmation window opens as shown below.
Click Yes to confirm.

4. When XIO cards are reassigned to XIO30-16, the following window opens
upon successful completion of the reassignment.
To downgrade from XIO30-16 to XIO30-1 or XIO30-4:

1. Remove the traffic on the corresponding VC-4 on the XIO30-16 card, and
make sure that there is no SMD4 assigned on the Tslots.
2. In a BG-30 NE shelf view window, select the NE in the left object tree and
then select Configuration > Slot Assignment in the menu.
3. Right-click on the XS A slot and, from the pop up menu, select the XIO
card that you want to assign.
Before the reassignment command is sent to the BG-30 NE, the EMS-BGF
checks the traffic on the corresponding VC-4 of the XIO30-16 card. If
traffic exists, the reassignment cannot continue and the EMS-BGF displays
a warning message.
4. Click Apply to save your change.

Data Cards
The data cards are sorted into Layer 1 cards, Layer 2 cards, and EOP cards, as
described in this section.
L1 Cards
This section describes the Layer 1 cards.
L1B_6F
The L1B_6F is a Layer 1 data card in BG-20B. This section describes how to
configure L1B_6F card attribute.
To configure L1B_6F card attribute:

1. In a BG-20 NE shelf view window, select the L1B_6F card in the left
object tree. In the General tab under Configuration working mode, you
can view the general information of L1B_6F.

2. To configure the EoS encapsulation protocol, select the EoS Ports tab in
the above window.
This window contains the EoS Protocol information and General

information settings. Set the parameters as required and click Apply to save
your changes.

3. To perform VCG configuration, in the left object tree, right-click on the

L1B_6F card or an EoS port. In the pop up menu, select Create VCG. The
VCG Attribute window opens.
Use this window to configure the virtual cascade mode (E1), the bandwidth
of each VCG, and the LCAS attributes.

4. To add or remove a VCG member, select the VCG in the object tree. Then
select the Configuration working mode.
For every member of this VCG, the E1s can be deactivated from this VCG.
5. To configure the port attribute, select an EoS port in the object tree. Then

6. To view real-time traffic, select the L1B_6F card in the left object tree.
Then select the EoS Payload tab under Maintenance working mode.
In this window, you acquire the Rx and Tx traffic of EoS and FE ports
(ports 1 through 6). The traffic here refers to the average traffic within the
first 15 minutes in the acquisition process.
For the acquired traffic information, the data display unit is specified in
bps.

7. To perform loopback maintenance, select the Loopback tab under

Maintenance working mode.
The Loopback Type values are Terminal Loopback, Facility Loopback,

and No Loopback. The default is No Loopback.
8. To perform MST maintenance, select VCG in the left object tree, and then
select the Maintenance working mode.

For LCAS members, the MST FAIL force/release function can be

performed. MST Attribute values are Auto and Force Fail. The default is
Auto.
MGE_1_L1
The MGE_1_L1 is a single GbE module that supports hot insertion with layer 1
functionality in BG-20B.
Its functionality is the same as the DMGE_1_L1 (on page 6-36).
DMFE_4_L1
The DMFE_4_L1 is a Layer 1 data card that supports 4 x 10/100BaseT LAN
interfaces and 4 x EoS WAN interfaces for the BG-30B. It supports live
insertion.
You can manage the DMFE_4_L1 as per the L1B_6F (on page 6-30).
DMFX_4_L1
The DMFX_4_L1 is a Layer 1 card that can be inserted into any Tslot in BG-
30B.
Most of its functions are the same as those of the DMFE_4_L1 (on page 6-36),
apart from the physical interfaces:
Four 100Base-FX interfaces.
Optical connector type: SFP and LC.
An SFP module that supports laser parameters monitoring and relevant
TCAs.
Laser control: Force on, Force off (the default is on).
DMGE_1_L1
The DMGE_1_L1 card supports one GbE interface with a total bandwidth of 4
x VC-4 and can be inserted into any Tslot in BG-30B.
The functionality of the DMGE_1_L1 is very similar to DMFE_4_L1 (on page
6-36), except that it has only one VCG and one port, and only supports one
LAN interface (GbE).
The DMGE_1_L1 supports the following:
1 x GbE interface, based on the SFP module.
1000Base-SX, 1000Base-LX, 1000Base-ZX, and electrical SFP.
ADM622 as the EoS mapper.

One EoS channel, which can be VC-12, VC-3, and VC-4 concatenations.
The maximum bandwidth is 4 x VC-4.
GFP encapsulation.
A Force-link-on maintenance operation for FE interfaces physical testing.
The same XIO switch-over scheme as that used on the DMFE_4_L1.
VC-12/VC-3/VC-4 monitor termination using an auxiliary port of a
PM5337.
Local XC capability by a PM5337 core XC module.
Customer Signal Failure(CSF) and Trail Signal Failure(TSF). They are
both controlled by the setting of CSF.
BIT.
To configure DMGE_1_L1 port attribute:

1. In a BG-30 NE shelf view window, select an EoS port of the DMGE_1_L1
card in the object tree. Then select the Configuration working mode.
2. Set the parameters as required.

4. Click to retrieve the information from NE equipment.
5. When Negotiation is set to Enable, you can click in the toolbar to

restart auto-negotiation.

DMGE_4_L1
The DMGE_4_L1 supports 4 GbE interfaces with standard EoS L1
functionality. The total bandwidth is 16 x VC-4. It can be inserted to any TSlot
in BG-30B, but can only be used in ADM-16 system including XIO30Q_1&4
system.
The DMGE_1_L1 supports the following:
VC-4/VC-3/VC-12 virtual concatenation, LCAS and GFP
Optical and electrical SFP
4 GbE LAN interfaces based on SFPs and 4 EoS WAN interfaces
Local CPU to improve survivability
To configure DMGE_4_L1 port attribute:

1. In a BG-30 NE shelf view window, select an EoS port of the DMGE_4_L1
card in the object tree. Then select the Configuration working mode.
2. Set the parameters as required.

4. Click to retrieve the information from NE equipment.
5. When Negotiation is set to Enable, you can click in the toolbar to

restart auto-negotiation.

L2 Cards
MESW_6F
The MESW_6F is a data card on the BG-20B that can provide not only
Ethernet Private Line (EPL) service, but also Ethernet Virtual Private Local
Area Network (EVPLAN) service. The MESW_6F can also manage the
Ethernets QoS and bandwidth.
MESW_6F card management objects can be:
ETY interfaces
Switch
EoS interfaces (ports, EoSs, VCGs)
Managing Ports
The MESW_6F card has 14 FE ports, six of which are ETY ports that connect
to the local side and eight of which are EoS ports that connect to the remote
side through an EoS mapper.
To configure MESW_6F card attributes:

1. In a BG-20 NE shelf view window, select the MESW_6F card in the left
object tree. In the General tab under the Configuration working mode,
you can view the general information of the MESW_6F.

2. To configure the ETY port attribute, select the ETY Ports tab in the above
window.
In this window, the following attributes can be configured:

Auto-Negotiation: Values are Auto-negotiation or no Auto-
negotiation. The default is Auto-negotiation (enabled).
Local Pause Mode: The default is No Pause.
Speed: 100M or 10M. The default is 100M.
Duplex: Full or Half. The default is Full.

3. To configure the EoS encapsulation protocol and the EoS port attribute
settings, select the EoS Ports tab in the window.
For the MESW_6F cards EoS channel, one of two types of

encapsulation protocol can be designated:
GFPF (the default)
LAPS
The Send FCS may be Enabled or Disabled. The default is Disabled.
The Dedicate attribute value may be Yes or No.
For the EoS port attributes, three attributes can be configured and three
attributes are read-only.
Read-only attributes are:
Duplex Status
Speed Status
Flow Control Status
Configurable attributes are:
NNI/UNI setting. Default settings are:
I-NNI for EoS port 1 through EoS port 4.
UNI for EoS port 5 through EoS port 8.
Max Package Length: The valid range is 1518 bytes to 9022 bytes.
The default is 9022 bytes.
Subnetwork ID: Can be set for each WAN port. It is used to
distinguish the VLAN subnetwork.

4. To configure the port licenses of the ETY ports, select the Port Licenses
tab in the window.


MESW_6F card or an EoS port. In the popup menu, select Create VCG.
The VCG Attribute window opens.
Use this window to configure the virtual cascade mode (VC-12/VC-3/VC-

4), bandwidth of each VCG, and LCAS attributes.

6. To add or remove a VCG member, select the VCG in the object tree. Then
For each member of this VCG, a Deactivated attribute can be set. This
entails removing the member from the VCG.
7. To configure a single EoS port attribute, select an EoS port in the object
tree. Then select the Configuration working mode.

8. To view real-time traffic, select the MESW_6F card in the left object tree
and then select the EoS Payload tab under the Maintenance working
mode.
In this window, you acquire the Rx and Tx traffic of EoS ports (ports 1
through to 8). The traffic here refers to the average traffic within the first 15
minutes in the acquisition process.
bps.

9. To perform loopback maintenance, select the Loopback tab under the


and No Loopback. The default is No loopback.
Set the Loopback Type for each VCG in this window, and click Apply to
save the configuration in the database and the NE.
10. To perform MST maintenance, select a VCG in the left object tree and then


Auto.
Managing a Link Aggregation Group

The MESW_6F supports up to 13 aggregation groups. An aggregation can be
supported in the MESW_6F, as follows:
Two/four ports for NNI WAN FE ports
Two/four ports for UNI LAN FE ports
Two/four ports for UNI WAN FE ports
User can also configuring a link aggregation group. Server load balancing and
failover mechanisms are supported via flexible link aggregation that is based
on the MAC destination and source addresses. The port within an LAG that is
to be used as a destination can be selected based on the Ethernet source and/or
destination address or the IP source and/or destination address. The MESW_6F
card does not support IP addresses.

To create LAGs:
1. In a BG-20 NE shelf view window, in the left object tree, right-click on the
MESW_6F card and select Create LAG in the popup menu. The
Create/Edit Aggregation Ports window opens.

2. Select an aggregation group from the Aggregation Group dropdown list.

3. Select ports in the left list and click to add the ports to the right
aggregation group.
4. To remove a port from the right aggregation group, select the port(s) in the
right list and click .
5. Click Apply to save the results.

To configure an LAG:
1. In the BG-20 NE shelf view window, select the MESW_6F card in the left
object tree. Then select the LAGs tab under the Configuration working
mode.
2. Select the required aggregate groups in the Aggregation Group list.

3. Select the trunk mode in the Trunk Mode dropdown list. Trunk mode is
used to select a physical port on a LAG on which to send packets. This
mode is also called Distribution Algorithm. The distribution algorithm
implements load sharing between all ports in the LAG while maintaining
the order of packets for each service. The supported trunk modes are:
Source MAC: Packets with different source MAC addresses are sent
through different physical ports of the LAG.
Destination MAC: Packets with different destination MAC addresses
are sent through different physical ports of the LAG.
Source XOR Destination MAC: Packets with different source MAC
addresses or different destination MAC addresses are sent through
different physical ports of the LAG. This is the default mode.
Although all three modes ensure the packet order in each service, the
difference between them is the level of load sharing. Source XOR
Destination MAC provides the best load sharing between physical ports of
the LAG.
4. Click Apply to save the settings.

Managing the Bandwidth Profile

A bandwidth profile is used when creating a policer. This profile affects the
MESW_6F card, and enables you to change the bandwidth to meet the policer
requirements, if needed.
To access the bandwidth profile:

1. In the BG-20 NE shelf view window, select MESW_6F > Switch in the
left object tree. Then select the Bandwidth Profile tab under the Services
working mode.
2. Click in the toolbar to restore the default bandwidth profile.
3. Click to retrieve the bandwidth profile from the equipment.

4. Change the Committed Information Rate (CIR) and Committed Burst Size
(CBS) values as required, and click Apply to save the settings.
NOTE: Due to a hardware limitation, the MESW_6F card

only supports eight bandwidth profile levels.

Managing Policers
When creating PB MPtMP, each UNI port must have a policer. Each policer
can be used only once. Policers values can be identical, except for the policer
name. Up to 128 policers can be defined per MESW_6F card.
To create a policer:
1. In the BG-20 NE shelf view window, select the MESW_6F > Switch in
the left object tree. Then select the Policer Profile List tab under the
Services working mode.

2. To create a policer, click the Create Policer button in the toolbar. The
Create Policer Profile window opens.
3. In the Create Policer Profile window, enter the following parameters for
the policer:
Policer Name: Enter a name for the policer.
Policer Profile ID: Enter a numeric value between 1 and 128 for the
policer. Up to 128 policers can be defined.
CIR: Select the Committed Information Rate (CIR) in the dropdown
list.
CBS: Select the Committed Burst Size (CBS) in the dropdown list.
S-VLAN CoS: Select the Class of Service (COS) where the customers
traffic enters the providers network.
Service State: Select Enabled or Disabled in the dropdown list to
enable or disable the service. The default is Enabled.
4. Click Apply to create the policer.
For details about setting policer value, refer to Policer Value Rules (on page 6-
92).

To use the policer list:

1. You can view the policer list in the following window:
2. To edit a policer, select the policer in the Policer Profile List and select the
Edit Policer button in the toolbar. The Edit Policer Profile window
opens.
Change the policer values as required, and click Apply to save the settings.

3. To view the details of a policer, select the policer and click in the
toolbar. The View Policer Profile window opens.
4. To delete a policer, select the policer in the list and click in the toolbar.
To delete all of the policers in the list, click the Select All button and
then click . Click to deselect all.
5. To upload policers, click the Policer Upload button in the toolbar. The
Policer Profile Upload window opens, as shown below.

Click Upload to upload policers from the MESW_6F card.
The status bar shows the consistency status between the NE and the
database. Click Overwrite to overwrite the database with the NE data.
If the NE and the database are inconsistent, select the Policer Profile
Compare tab to display the inconsistency results.

Managing VSI Services

The MESW_6F supports a Virtual Private Network (VSI). VSIs define policies
and provide users' Service Level Agreements (SLAs).
The MESW_6F supports the following VSI types:
EPL
PB MPtMP
Creating an EPL
This section describes how to create an EPL for MESW_6F.
To create an EPL:
left object tree. Then select the VSI List tab under the Services working
mode.

2. Click the Create VSI button in the toolbar. The Create VSI window
opens.
3. To create an EPL, select EPL from the Service Type drop-down list.
4. Enter the values of VSI ID, NMS VSI ID, User Label and Customer in
the respective fields.
5. Select the Enabled CSF checkbox, if needed. You can also input
additional description into the VSI Description field.

6. In the right Objects Selections area, select one ETY port and one EoS port
or two EoS port in the relevant list. Right-click an object to deselect, or you
can select an object in the lower-right list and click in the toolbar.
You can also click in the toolbar to create a policer.

7. Click Active to create and activate the EPL. If you click Save, the EPL will
be saved but not activated. To activate it, select the Recent Saved VSIs
tab.
8. Select the VSI you want to activate in this window and click Active. The
EPL then is activated.

Creating PB MPtMP
This section describes how to create PB MPtMP for the MESW_6F.
To create PB MPtMP:
mode.

opens.
3. To create PB MPtMP, select PB MPtMP from the Service Type drop-

down list.
4. Enter the VSI ID, NMS VSI ID, User Label, Customer, S-VLAN, and
vFIB Quota values in the left areas of the window. The vFIB Total
Reserved Entries field indicates the total number of reserved entries in the
vFIB. You can also input additional description into the VSI Description
field.

5. In the right Objects Selections area, select ETY ports and EoS ports as you
want in the relevant list. Right-click an object to deselect, or you can select
an object in the lower-right list and click in the toolbar.
You can click in the toolbar to create a policer.

6. For the selected UNI ports, the Tag Type and C-VLAN ID values should
be set. User can click "+" to expand the UNI port and can enlarge the
lower-right area by dragging the separating line above the toolbar, as
shown below.

7. In the Tag Type & C-VIDs field, select the Specific C-VIDs checkbox
and define the C-VID range. Also, select the Untagged and the Priority
Tagged checkboxes if needed. To add PVID for an untagged FE-ETY port,
select the Double tag checkbox and set the number in the field next to.
8. To map policers, click in the toolbar and select the corresponding port
where you want to perform CoS-Mapping. The following window opens.

Input the tags listed in the Available Tags into the Add Tags area and
click Add. To delete the CVlans, select the Delete Priority & Policer
Mapping radio button.
Click "+", in the expanded area, select the Priority values in the From and
To dropdown lists, and select a policer in the Policer dropdown list. Click
Add to add the policer to the C-VLAN.
Do the same operation for the other CVLans. Click Save to save your
settings.

9. Repeat Step 8 to map policers for other UNI ports.
10. Click Active to create and activate the PB MPtMP. If you click Save, the
PB MPtMP will be saved but not activated. To activate it, select the Recent
Saved VSIs tab.
Select the VSI you want to activate in this window and click Active. The
PB MPtMP then is activated.

Using the VSI List

The VSI list enables you to view and manage VSI items.
To use the VSI list:

1. You can view the VSI list in the following window:
2. To activate a VSI, select a VSI in the list and click in the toolbar. Click
to deactivate it.

3. To Edit a VSI, select the VSI in the list and select the Edit VSI button
in the toolbar The Edit VSI window opens.
Modify the VSI as required, and click Apply to save the settings.
4. To view the details of a VSI, select the VSI and click in the toolbar.
The View VSI window opens.

5. To delete a VSI, select the VSI in the list and click in the toolbar. To
delete all of the VSIs in the list, click the Select All button and then
click . Click to deselect all.
6. To upload VSIs, click the VSI Upload button in the toolbar. The VSI
Upload window opens, as shown below.
Click Upload to upload VSIs from the MESW_6F card.

database. If the NE and the database are inconsistent, select the VSI
Click Save To DB to send the data from the NE to database, or click Delete
from DB to delete the data from database.

7. User can also access some operations from the right-click menu, as shown
below.
Configuring the vFIB

vFIB-related operations include configuring the Aging Time, flushing the
vFIB, and configuring the Port Lock.
The MESW_6F has a dynamic address-learning function. All the dynamically
learned addresses need aging.
The MESW_6F has seven levels of aging time:
280 seconds
70 minutes
210 minutes
14 hours
56 hours
14 days
No aging

The following considerations apply to the aging process:

When an address is learned dynamically, the aging timer is started.
If the address can be learned during the Aging Time, it is removed from the
vFIB.
The Aging Time is the initial value for the aging timer.
If no aging mechanism is used, the vFIB may contain many invalid
addresses.
To configure vFIB settings for MESW_6F:

left object tree. Then select the vFIB Setting tab under the Configuration
working mode.
2. Set the Aging Time value and the Port Lock status. When the Port Lock is
enabled, the address-learning function is disabled. If a MAC frame contains
a new source MAC address, this frame is discarded.
3. Click Apply to save the setting.

To use the vFIB list:

left object tree. Then select the vFIB List tab under the Services working
mode.
2. To flush a specific VSI, select the VSI from the VSI drop-down list in the
Filter area and click the Flush button in the toolbar.
3. To flush all the VSIs, select the Flush All button in the toolbar.

4. To add new items to vFIB tables, select the Static radio button in the Filter
area, then click . The Create New Static vFIB Entry window opens.
Set the VSI ID, MAC and Port, then click Apply to create.
5. To view the vFIB items, select the attributes you want to view in the Filter
area and then click Get & Filter.
6. Click Query to retrieve the static vFIB items.
Configuring MSTP
The MESW_6F supports the Multiple Spanning Tree Protocol (MSTP).
For details about configuring MSTP, refer to Configuring STP and MSTP (on
page 11-22).
DMFE_4_L2
The DMFE_4_L2 is a Layer 2 data card that provides Ethernet switched
service.
The card contains the following main functional blocks:
4 x FE PHY
8 x EoS mapper with an ESSI interface module
Flexible L2 packet processor module
Local CPU with HDLC processing module

The DMFE_4_L2 card also supports MPLS services.

For the details of MPLS services, refer to the chapter Managing MPLS
Services (on page 7-1).
Managing Ports
The DMFE_4_L2 card has 12 FE ports, four of which are ETY ports that
connect to the local side through an RJ-45 connector and eight of which are
EoS ports that connect to the remote side through an EoS mapper. Each EoS
port is fixed to connect one EoS channel with a PHY interface.
All 12 FE ports are interconnected by a switch core. All NE configuration data
is stored on the NVM card. The system retrieves NE data from the NVM card
after a reset. NE replacement is implemented by inserting the NVM card into a
new BG-30. No other actions are required.
To configure DMFE_4_L2 card attributes:

1. In a BG-30 NE shelf view window, select the DMFE_4_L2 card in the left
can view the DMFE_4_L2's general information.

window.
The default type for all ETY ports is UNI.

For a UNI port type, the following attributes can be configured:
Untagged Frame: Frames can be block, forward, or forward with
PVID. The default is forward.
Priority Tagged Frame: Frames can be block, forward, or forward
with PVID. The default is forward.
PVID: The range is 0-4094. The default is N/A. This field can only be
set when forward with PVID is selected in the Untagged Frame field.
Default CD Priority: The range is 0-7. The default is 0.
If a port is configured as forwarded with PVID, then this port is
dedicated as an Untagged type and can only be added once.

The type for EoS ports can be UNI, I-NNI, or E-NNI.

I-NNI is an internal NNI within the provider domain.
E-NNI is an external NNI that connects external devices.
The default value for the EoS ports 1 through 4 is UNI and for the others is
I-NNI.
For more details about port management for the DMFE_4_L2, refer to
Managing Ports (on page 6-39) in the MESW_6F.

CoS Shapping and CoS WRED

For the DMFE_4_L2 card, you can configure CoS shapping for each ETY port,
and configure both CoS shapping and CoS WRED for the each EoS port. This
section describes how to configure CoS shapping and CoS WRED for
DMFE_4_L2 card.
To configure CoS shapping:

1. In the DMFE_4_L2 shelf view window, in the left object tree, select an
ETY or EoS port. Then select the CoS Shapping tab under the

3. Setting the parameters for each CoS as needed.

To configure CoS WRED:

1. In the DMFE_4_L2 shelf view window, in the left object tree, select an
EoS port. Then select the CoS WRED tab under the Configuration
working mode.

3. Setting the attributes for each CoS as needed.

Managing a Link Aggregation Group

Use the following procedure to configure a link aggregation group (LAG) in
the DMFE_4_L2.
NOTE: The procedures described in this section also apply to

other data cards, such as the DMFX_4_L2, MPS_6F,
DMGE_2_L2, DMGE_4_L2 and DMGE_8_L2,.
To create LAGs:
1. In a BG-30 NE shelf view window, in the left object tree, right-click on the
DMFE_4_L2 card and select Create LAG in the pop up menu. The
Create/Edit Aggregation Ports window opens.
2. Select an aggregation group from the Aggregation Group dropdown list.

3. Select ports in the left list and click to add the ports to the right
aggregation group.
If a port is added to a LAG with LAG Distribution Enable value set to

disabled, or the LAG port member is changed from LAG Distribution
enabled to disabled, the LAGs traffic is not distributed to the port, and the
packets received from that port are not discarded.
4. To remove a port from the right aggregation group, select the port(s) in the
right list and click .
5. Select the LAG Distribution Enable checkbox, if needed, set the Hold Off
Time and click Apply to save the results.

To configure an LAG:
1. In the BG-30 NE shelf view window, select the LAG object in the left
object tree. Then select the Configuration working mode.
2. Modify the LAG as needed and click Apply to save the settings.
EFM Link OAM

Ethernet in the First Mile Link Operation, Administration, and Maintenance, or
EFM Link OAM, has the following objectives:
Remote failure indication: indicates to a peer that the receive path of the
local port is not operational.
Remote loopback control: supports data-link layer frame-level loopback
mode.
Link monitoring: supports event notification that permits the inclusion of
diagnostic information. Link monitoring tools are used to detect and
indicate link faults under a variety of circumstances.

To manage ETY maintenance:

object tree. Then select the ETY Maintenance tab under the Maintenance
working mode.
2. Set the parameters for Link OAM attribute and Link OAM remote
loopback.

To manage ETY Link OAM events and threshold:

object tree. Then select the ETY Link OAM Window and Threshold tab
under the Maintenance working mode.
2. Set the parameters in the window.


To view ETY Link OAM events statistics:

1. In a BG-30 NE shelf view window, select an ETY port in the left object
tree. Then select the ETY Link OAM Events Statistics tab under the

The DMFE_4_L2 Fiber Database (vFIB) table length is 32 K.
The DMFE_4_L2's vFIB can flush:
All vFIBs for an entire bridge
A vFIB for a specific VSI
A vFIB for a specific port on a given VSI

To use the vFIB list:

1. In the BG-20 NE shelf view window, select DMFE_4_L2 > Switch in the
left object tree. Then select the vFIB List tab under the Services working
mode.
2. To flush a specific VSI, select the VSI from the VSI drop-down list in the
Filter area and click the Flush button in the toolbar.
3. To flush all the VSIs, select the Flush All button in the toolbar.

4. To add new items to vFIB tables, select the Static radio button in the Filter
area, then click . The Create New Static vFIB Entry window opens.
Set the VSI ID, MAC and Port, then click Apply to create.
5. To view the vFIB items, select the attributes you want to view in the Filter
area and then click Get & Filter.
6. Click Query to retrieve the static vFIB items.
Configuring MSTP
The DMFE_4_L2 supports the Multiple Spanning Tree Protocol (MSTP).
For details about configuring MSTP, refer to Configuring STP and MSTP (on
page 11-22).

Managing Policers
When creating PB PtP or PB MPtMP, each UNI port must have a policer. Each
policer can be used only once. Policers values can be identical, except for the
policer name.
To create a policer:
left object tree and then select the Policer Profile List tab under the

2. To create a policer, click the Create Policer button in the toolbar. The
Create Policer Profile window opens.
3. In the Create Policer Profile window, enter the following parameters for
the policer:
Policer Name: Enter a name for the policer.
Policer Profile ID: Enter a numeric value between 1 and 128 for the
policer. Up to 128 policers can be defined.
CIR: Set the Committed Information Rate (CIR).
CBS: Set the Committed Burst Size (CBS).
CM: Select the Color Mode (CM) in the drop-down list.
CF: Select Coupling Flag (CF) as in the drop-down list.
4. Click Apply to create the policer.
For details about setting policer value, refer to Policer Value Rules (on page 6-
92).

To use the policer list:

1. You can view the policer list in the following window:
2. To edit a policer, select the policer in the Policer Profile List and select the
Edit Policer button in the toolbar. The Edit Policer Profile window
opens.
Change the policer values as required, and click Apply to save the settings.

3. To view the details of a policer, select the policer and click in the
toolbar. The View Policer Profile window opens.
4. To delete a policer, select the policer in the list and click in the toolbar.
To delete all of the policers in the list, click the Select All button and
then click . Click to deselect all.
5. To upload policers, click the Policer Upload button in the toolbar, the
Policer Profile Upload window opens, as shown below.

Click Upload to upload policers from the DMFE_4_L2 card.
database. If the NE and the database are inconsistent, select the Policer
Profile Compare tab to display the inconsistency results.
Click Overwrite to overwrite the database with the NE data.

Policer Value Rules

Policer for
DMFE_L2/DMFX_L2/DMGE_2_L2/DMGE_4_L2/DMGE_8_L2/BG-
20B_L2M card has strict restriction rules. Policer from NMS can have arbitrary
CIR/CBS/EIR/EBS values, and these values should comply with the EMS-BGF
rules.
Table 6-5: Policer Value Rules
Profile Name Policer Value Rule

CIR/EIR Step of: 64Kbits/s for 0~2Mbits/s; 1Mbits/s for 2Mbits/s~Full port
rate (100, 400Mbit/s or 1Gbit/s).
CBS/EBS 0~12M bytes, Step of 4kbytes. Can be configurable by
EMS/NMS. Default CBS/EBS on EMS:
If CIR is less than 1Mbits/s, the CBS is equal to 16kbytes.
Otherwise, Min(CIR/128, 12M bytes);
If EIR is less than 1Mbits/s, the EBS is equal to 16kbytes,
Otherwise, EBS is equal to Min(EIR/32, 12M bytes);
CBS for BSC policer is editable by NMS. The default CBS of
EMS(not configurable by EMS user): Min(CIR/32, 4M bytes) and
no less than 32kbytes.
CM Color-blind/Color-aware
CF Enabled/Disabled

Managing VSI Services

The DMFE_4_L2 supports the following VSI types:
EPL
PB PtP
PB MPtMP
Creating an EPL
This section describes how to create an EPL for DMFE_4_L2.
To create an EPL:
mode.

opens.
3. To create an EPL, select EPL from the Service Type dropdown list.
4. Select the VSI State by selecting the radio button. When disabled, all
policers block their traffic, including NNI ports. When enabled, all policers
enable traffic flow. This field is editable with no constraints. The default is
Enabled.
5. Enter the values of VSI ID, User Label, and Customer in the respective
fields.
6. Select the Enabled CSF checkbox, if needed. You can also input

7. In the right Objects Selections area, select one ETY port and one EoS port
or two EoS port in the relevant list. Right-click an object to deselect, or you

8. Click Active to create and activate the EPL. If you click Save, the EPL will
be saved but not activated. To activate it, select the Recent Saved VSIs
tab.
EPL then is activated.

Creating PB PtP
This section describes how to create PB PtP for DMFE_4_L2.
To create PB PtP:
mode.

opens.
3. To create PB PtP, select PB PtP from the Service Type dropdown list.
Enabled.
5. Enter the VSI ID, User Label, Customer and S-VLAN values in the left
areas of the window. You can also input additional description into the VSI
Description field.

6. In the right Objects Selections area, you can select one ETY port and EoS
port, or two EoS ports as you want in the relevant list. Right-click an object
to deselect, or you can select an object in the lower-right list and click
in the toolbar.

7. All selected VSI UNI or E-NNI ports have the same Ethernet priority,
which is determined by the provider CoS mapping policy. This mapping is
defined in the UNI Ingress CoS Mapping, E-NNI Ingress CoS Mapping,
and E-NNI Egress CoS Priority Swapping fields in the Create VSI
window. Click "+" to expand the UNI port and can enlarge the lower-right
area by click the icon above the toolbar, as shown below.
The following apply when defining the CoS mapping:
For each priority (0 to 7), only one provider CoS should be selected.
The default is CoS0 for all priorities.
All priority values should be mapped.
The priority value of untagged frames is defined in the UNI port
attributes.
Any change that conflicts with an already defined policer or that is set
with No Rate Limit is rejected.
A CoS can only be removed or discarded from the mapping when it is not
associated with No Rate Limit or a policer profile. When this occurs, the
operation is rejected and the following message is displayed: A policer is
associated with this CoS.

and define the C-VID range. Also, select the Untagged, Priority Tagged,
and Tag Translation checkboxes if needed.
Select in the toolbar, the following window opens.

Use this window to add, move, delete tags, or delete groups by selecting the
corresponding radio button.
9. Click Active to create and activate the PB PtP. If you click Save, the PB
PtP will be saved but not activated. To activate it, select the Recent Saved
VSIs tab.
PB PtP then is activated.

Creating PB MPtMP
This section describes how to create PB MPtMP for the DMFE_4_L2.
To create PB MPtMP:
mode.

opens.
3. To create PB MPtMP, select PB MPtMP from the Service Type dropdown

list.
Enabled.
5. Enter the VSI ID, User Label, Customer, S-VLAN and BSC Threshold
values as required in the left areas of the window.
6. The vFIB Quota can only be set for a PB MPtMP. When this quota is
reached, the learning process can be halted, in which case flooding is
performed (when the Switch Quota is forwarded), or unknown addresses
are dropped (when the action is dropped).
7. Select the Enable MAC Address Learning checkbox if needed. You can
also input additional description into the VSI Description field.

8. In the right Objects Selections area, you can select the ETY ports and EoS
ports as you want in the relevant list. Right-click an object to deselect, or
you can select an object in the lower-right list and click in the toolbar.


attributes.
A CoS can only be removed or discarded from the mapping when it is
not associated with No Rate Limit or a policer profile. When this
occurs, the operation is rejected and the following message is
displayed: A policer is associated with this CoS.
10. For the DSCP Mapping area, all the UNI/E-NNI ports of the VSI have an
option to enable the same DSCP to provider CoS mapping policy. The
DSCP to CoS mapping can be disabled and enabled. The default is
disabled.

and Tag Translation checkboxes if needed. Here for this port, Untagged
and Priority Tagged have been used in PB PtP and are not available for
PB MPtMP.

12. Click Active to create and activate the PB PtP. If you click Save, the PB
MPtMP will be saved but not activated. To activate it, select the Recent
Saved VSIs tab.
PB MPtMP is then activated.

Using the VSI List

The VSI list enables you to view and manage VSI items.
To use the VSI list:

1. You can view the VSI list in the following window:
2. To activate a VSI, select a VSI in the list and click in the toolbar. Click
to deactivate it.
3. To enable a VSI, select a VSI in the list and click in the toolbar. Click
to disable it.

4. To Edit a VSI, select the VSI in the list and select the Edit VSI button
in the toolbar, the Edit VSI window opens.
Modify the VSI as required, and click Apply to save the settings.
5. To view the details of a VSI, select the VSI and click in the toolbar.
The View VSI window opens.

6. To delete a VSI, select the VSI in the list and click in the toolbar. To
delete all of the VSIs in the list, click the Select All button and then
click . Click to deselect all.
7. To upload VSIs, click the VSI Upload button in the toolbar. The VSI
Upload window opens, as shown below.
Click Upload to upload VSIs from the MESW_6F card.

database. If the NE and the database are inconsistent, select the VSI
Click Save To DB to send the data from the NE to database, or click Delete
from DB to delete the data from database.

8. You can also access some operations from the right-click menu, as shown
below.
Executing the VSI performance

This section describes how to execute the VSI performance, including:
Current Performance
Recent Performance
History Performance
TCA Threshold
Monitor and Report
Reset Performance Counters
Policer performance can also be performed, including:
Current Performance
Recent Performance
History Performance
Monitor and Report

To perform the VSI performance:

1. In the VSI list, select a VSI and right-click on it. From the pop up menu,
select VSI Performance.
2. To view the current performance of the selected VSI, select VSI

Performance > Current.
Click to retrieve the information to view.

3. To view the recent performance of the selected VSI, select VSI

Performance > NE History.

4. To view the historical performance of the selected VSI, select VSI
Performance > EMS History.

5. To set threshold of the selected VSI, select VSI Performance > Threshold
Setting.

6. To set monitoring and reporting, select VSI Performance > Monitoring
and Reporting.
From this window, you can set whether to monitor and auto-report the VSI.

7. To reset the performance counters, select VSI Performance > Reset

Performance Counters.
Managing VSI Alarms

This section describes how to manage the VSI alarms, including:
Current
History
Mask
To manage VSI alarms:

1. In the VSI list, select a VSI and right-click on it. From the pop up menu,
select VSI Alarm.

2. To view current alarms, select VSI Alarm > Current.
3. To view historical alarms, select VSI Alarm > History.

4. To mask the alarms of the selected VSI, select VSI Alarm > Monitoring
and Reporting.

Exporting and Importing VSIs
Exporting VSIs
This section describes how to export VSIs in the EMS-BGF.
To export VSIs:
1. In the EMS-BGF main window, select Services >Export > Export VSIs in
the main menu. The Export VSI window opens.
2. Select the VSIs you want to export. Click in the toolbar to select all the
VSIs in the list.

3. Click in the toolbar. The Save window opens.
4. Select a folder to save the file, enter the file name, and click Save.
Importing VSI XML Files

This section describes how to import VSI XML files to the EMS-BGF.
To import VSIs:
1. In the EMS-BGF main window, select Services >Import > Import VSIs
in the main menu. The Import VSI window opens.

2. Click in the toolbar to open a file. The Open window opens.
3. Select a file from the disk and click Open.
4. Select the XC in the list that you want import and click the Import button
in the toolbar.

DMFX_4_L2
The DMFX_4_L2 is a Layer 2 data card with 4 x 100Base-FX that can be
inserted into any BG-30B Tslot. The only difference between the DMFX_4_L2
card and the DMFE_4_L2 (on page 6-73) card is that the DMFX_4_L2 card
has four SFP blocks.
The DMFX_4_L2 card also supports MPLS services.
DMGE_2_L2
The DMGE_2_L2 is supported in both the ADM-1/4, ADM-16 and 4 x ADM-
1/4 systems, and can be assigned to any Tslot in BG-30B. When it works in
ADM-1/4, the ESSI rate is 622M and when it works in ADM-16 or 4 x ADM-
1/4, the ESSI rate is 2.5G.
Main features of the DMGE_2_L2 are list as follows:
2 x GbE interfaces in LAN side based on SFP modules
64 x EoS interfaces in WAN side with total traffic bandwidth up to 2.5G
Configurable ESSI rate: 2.5Gb/s or 622Mb/s, depending on XIO30 type
No local XC capability. When working with the ADM1/4 system, dynamic
bandwidth adjustment will result in traffic-hit. A user confirmation is
required in such a case, or Bandwidth compression is not supported
Traffic and timing signals connect to both XIO cards. Support the
switching between two XIO cards with ACT signals from two XIO cards
The DMGE_2_L2 Layer 2 functionality is the same as the DMFE_4_L2 (on
page 6-73) but with higher capacity and larger throughput.
The DMGE_2_L2 card also supports MPLS services.

DMGE_4_L2
DMGE_4_L2 is a single Tslot module supporting 4 GbE interfaces based on
SFP which can be inserted to any Tslot of BG-30B and BG-64. It has up to 64
EoS channels with total bandwidth of 2.5Gb/s, and supports L2 functionality:
both MPLS & PB, IEEE1588 and Synchronous Ethernet.
MPLS and PB functionality
16 x VC-4 WAN bandwidth & 64 x EoS/MoT channels
4 x GbE interface (SFP only)
IEEE1588
Synchronous Ethernet
DMGE_4_L2 has larger throughput, more GbE interfaces, higher EOS and
MoT bandwidth and larger service capacity than DMGE_2_L2, while layer 2
features and functionality are similar. DMGE_4_L2 supports all features that
DMGE_2_L2 supports.
DMGE_8_L2
DMGE_8_L2 is a double Tslot module supporting 2 GE combo ports and 6 GE
ports based on SFP which can be inserted to TS1-2 and TS6-7 of BG-64.
Combo ports support both SFP and RJ45 interface. It has up to 96 EoS ports
with total bandwidth is 5Gb/s and supports L2 functionality: both MPLS & PB,
IEEE1588 and Synchronous Ethernet.
MPLS and PB functionality
32 x VC-4 WAN bandwidth & 96 x EoS/MoT channels
8 x GbE interface (2 of them are COMBO)
IEEE1588
Synchronous Ethernet
DMGE_8_L2 has larger throughput, more GbE interfaces, higher EOS and
MoT bandwidth and larger service capacity than DMGE_2_L2, while layer 2
features and functionality are similar. DMGE_8_L2 supports all features that
DMGE_2_L2 supports.

MPS_6F
The BG_20B with an MPS_6F card on the L12 module is called the BG-
20B_L2M. The MPS_6F card is the same as the DMFE_4_L2 (on page 6-73)
card, except for the number of the LAN ports.
MPS_6F includes the following main function blocks:
6 x FE PHY
EoS ports located on MXC-20
FE PHY located on MXC-20
The MPS_6F card also supports MPLS services.
MPS_4F
MPS_4F is a Layer 2 data card in BG-20C. The traffic functionality (including
EOS, ETY and Switch) of MPS_4F is mostly the same as MPS_6F (on page 6-
122), except that MPS_4F has four FE ETY ports while MPS_6F has six.
The MPS_4F provides:
8 x EoS ports
8 x EoS objects
4 x ETY ports
1 x Switch object
FE_L12
The Fast Ethernet Module (FE_L12) is a multi-EoS Ethernet interface card
providing up to eight EoS channels. The total bandwidth of the eight EoSs
cannot exceed 63 VC-12s, and the EoS encapsulation protocol is optional.
Externally, eight 10BaseT/100BaseT Ethernet transparent transmission
interfaces can be provided. Internally, an eight-port L2 switching module is
integrated, which supports the L2 switching function through an external cable
connection.
The functional blocks contained in the FE_L12 card include eight VCGs, eight
EoSs, and 16 ports. The port involves two layers: MAC and PHY. VCG is the
collection of VC-12s or VC-3s. The specific number of VC-12s or VC-3s
depends on the VCGs virtual cascade mode and maximum traffic.

Managing Ports
This section describes how to configure the FE_L12 card attributes.
To configure FE_L12 card attributes:

1. In a BG-40 NE shelf view window, select the FE_L12 card in the left
can view the general information of the FE_L12.

window.


FE_L12 card or an EoS port. In the pop up menu, select Create VCG. The
VCG Attribute window opens.
Use this window to configure the virtual cascade mode (VC-12/VC-3), the
bandwidth of each VCG, and the LCAS attributes.

5. To add or remove a VCG member, select the VCG in the object tree, and
then select the Configuration working mode.
For every member of this VCG, a Deactivated attribute can be set. this
entails removing the member from the VCG.
6. To view real-time traffic, select the FE_L12 card in the left object tree.
Then select the EoS Payload tab under the Maintenance working mode.

In this window, you acquire the Rx and Tx traffic of EoS ports (ports 1
through to 8). The traffic here refers to the average traffic within the first 15
minutes in the acquisition process.
bps.
7. To view real-time traffic for ETY ports, select the FE_L12 card in the left
object tree. Then select the ETY Payload tab under the Maintenance
working mode.


The Loopback Type values are Terminal Loopback and No Loopback.

The default is No Loopback.
Set the Loopback Type for each VCG in this window. Click Apply to save
the configuration in the database and the NE.

9. To perform MST maintenance, select a VCG in the left object tree and then

Auto.
Configuring the VLAN

A Virtual Local Area Network (VLAN) is a logical network topology. It
logically divides the network into several broadcast domains. The packets can
only transmit inside the VLAN. Communication between VLANs is through a
Layer 3 routing switch.
A VLAN can reduce the broadcast domain by segmenting the network
efficiently. It optimizes network performance and security, and is easy to
manage.
The FE_L12 supports two types of VLAN: a port-based VLAN and a TAG-
based VLAN. TAG is defined in IEEE 802.1q. It adds a tag in the MAC frame
header, which contains the priority and VLAN ID of this MAC frame.
FE_L12 VLAN processing rules are:
VLAN processing for an untagged MAC frame at the ingress port.
Untagged MAC frames do not contain VLAN information. When an
untagged frame enters a Layer 2 port of the FE_L12 card, the FE_L12 adds
a tag to this frame to indicate that this MAC frame belongs to a specific
VLAN. The MAC frame then enters the filter and switch processing. The
FE_L12 Layer 2 ports default Port VID determines in which VLAN the
untagged MAC frames belong. The Port VID can be configured.

VLAN processing for a tagged MAC frame at the ingress port.

Tagged MAC frames contain VLAN information. When entering the Layer
2 port of the FE_L12, the frame goes to the filter and switch processing
directly.
Filter mechanism at the ingress port.
The FE_L12 filter is always enabled at the ingress port. When a MAC
frame enters the ingress port, the VLAN ID of the tag is checked. If the port
is not a member of the VLAN, the frame is dropped.
The FE_L12 does not support filtering based on the frame type. If an
untagged frame enters the ingress port, it is not dropped. A tag is added to
the MAC frame to indicate that the frame belongs to the default VLAN of
the ingress port. The frame then enters the filter processing.
VLAN processing at the egress port.
VLAN processing at the egress port has two options when a MAC frame
belonging to a specific VLAN exits the Layer 2 port of the FE_L12 card:
tagged or untagged. This can be configured. If the VLAN information is
not needed when the MAC frame exits a specific member port, this member
port is configured as Untagged. This occurs when the VLAN member port
is connected to the LAN. If the VLAN information is still needed when the
MAC frame exits a specific member port, this member port can be
configured as Tagged. This occurs when the VLAN crosses several
switches.
A Layer 2 port of the FE_L12 card can be a tagged member port of several
VLANs, but cannot be an untagged member port of multiple VLANs. For
example, a port can be the tagged member port of VLAN 100 and VLAN
200, and the untagged member port of VLAN 300. However, this port
cannot be the untagged member port of VLAN 400 at the same time.
Static VLAN table and current VLAN table.
The FE_L12 supports manual VLAN configuration. Manually configured
VLANs are static VLANs. The Static VLAN table is a subset of the current
VLAN table. In addition to Static VLANs, the current VLAN table also
contains VLANs dynamically registered through GVRP. As the network
grows, the VLAN configuration can be applied to the entire network
through GVRP, without having to manually configure all the switches.

To configure the VLAN:

1. In the BG-40 NE shelf view window, select FE_L12 > Switch in the left
object tree. Then select the Services working mode.
2. To create a VLAN, in the above VLAN List tab window, click Create. A
Create window opens.
3. Input the VLANID and VLAN Name.

4. Add the member ports by selecting ports in the VLAN Port area.

5. Define the untagged member ports in the Untagged Port area.

6. Click OK to create the VLAN.
7. To edit or delete a VLAN, select the VLAN to be edited or deleted in the
VLAN list. Then click Edit or Delete.
To configure a ports default VLAN ID:

In the BG-40 NE shelf view window, select FE_L12 > Switch in the left
object tree. Then select the Port VID tab under the Services working
mode.
The FE_L12 cards port PVID (default VLAN ID) does not need
configuration. When the port is an untagged member port of a specific
VLAN, the port PVID is set to the ID of the VLAN. This PVID cannot be
changed. When the port is a tagged member port of one or several VLANs
and is not an untagged member port of any VLAN, the port PVID must be
configured.


The FE_L12 Filter Database (vFIB) table length is 4K. vFIB-related operations
include configuring the Aging Time, flushing the vFIB, configuring the Static
vFIB table, and configuring the Port Lock.
The FE_L12 Layer 2 module has a dynamic address-learning function. All the
dynamically learned addresses need aging.
The following considerations apply to the aging process:
When an address is learned dynamically, the aging timer is started.
If the address can be learned during the Aging Time, it is removed from the
vFIB.
The Aging Time is the initial value for the aging timer.
If no aging mechanism is used, the vFIB may contain many invalid
addresses.
User can configure the aging time of FE_L12 in the following window:
The default value for the aging time is 336 seconds. The step value for setting
the aging time is 21 seconds.
For details about configuring the vFIB, refer to Configuring the vFIB (on page
6-70) of the MESW_6F.

ESW_2G_8F/ESW_2G_8F_E
ESW_2G_8F cards placed in the BG-40/BG-20 chassis can operate as either a
providers core (P) RS or a providers edge (PE) RS, in order to implement a
BG-based provider network. The customers edge (CE) RS and the customers
LAN are outside the scope of this document.
A BG-based provider network, based on the P and PE RSs and the connecting
EoS links, functions as an Ethernet (Reference: IEEE 802.3) virtual-bridged
local area network (Reference: IEEE 802.1Q) using 802.1Q/P encapsulation
(VLAN tags) and a switching/bridging algorithm (Reference: IEEE 802.1D).
The Layer 1/SDH topology of the network is transparent to the Layer
2/Ethernet. Either a ring or mesh topology of SDH trails accommodates point-
to-point links in a switched Ethernet network. The same Layer 1 network can
accommodate multiple Layer 2 networks using separate SDH paths. The basic
rate of an EoS connection uses VC-12/VC-3 granularity, meaning N x 2 Mbps
or N x 50 Mbps.
The ESW_2G_8F provides three types of ports:
2 x ETY GE ports
8 x ETY ports
16 x EoS ports
The ESW_2G_8F is a front-access card containing the following interfaces:
Two GE interfaces (SFP)
Eight ETY interfaces (RJ-45)
An LED indicator for the ESW_2G_8F card: Alarm/Active/Fail
An LED indicator for the ports: LINK/RX/SPEED
When the ESW_2G_8F card is reused in the BG-20E shelf, it is called the
ESW_2G_8F_E. Both of these cards actually have the same PCB, but a
different assembly. From a management perspective, the ESW_2G_8F_E is a
new card type with an independent type ID. It has no relationship to the
ESW_2G_8F.
The ESW_2G_8F/ESW_2G_8F_E card has the same feature as the MESW_6F
card, which is a daughter card of BG-20B. For more details about
ESW_2G_8F/ESW_2G_8F_E card operation, refer to the sections in this
manual relating to the MESW_6F (on page 6-39).

ME_2G_4F
ME_2G_4F is a Dslot module for BG-20B_L1, BG-20B_L2 and BG-
20B_L2M. It supports two GE ports and four FE ports (two optical and two
electrical), L2 functionality with MPLS and PB capability.
The ME_2G_4F provides 4 types of ports:
4 x VC-4 WAN bandwidth and 64 x EoS channel
2 x GbE interface (Combo)
2 x 10/100Base-T interface (Copper)
2 x 100Base-FX interface (Optical)
ME_2G_4F can only be assigned in BG-20B when INF-20BH is assigned, with
larger power output.
ME_2G_4F can load software or FPGA version from MXC-20 in both boot
status and running status. FPGA load is done by local CPU and reset is
required after FPGA is loaded. Only cold reset is supported.
The XC model of ME_2G_4F is same as ESW_2G_8F_E, so XC calculation
and allocation mechanism is the same.
ME_2G_4F supports both PB and MPLS functionalities, all L2 features are
synchronized with DMGE_2_L2 (on page 6-120) in BG-30B.
MPS_2G_8F
MPS_2G_8F is substitute of ESW_2G_8F_E, with richer features and
capability. It is a L2 data expansion card with 2 x GBE and 8 x 10/100Base-T
interfaces and at least 16 EoS WANs. Both provider bridge and MPLS are
supported in MPS_2G_8F.
MPS_2G_8F has 64 EoS ports and 2 GBE COMBO & 8 FE Ethernet LAN
ports. It has a local XC, supporting VC-12/VC-3/VC-4 cross-connect, so it can
support time-slot re-allocation (in order to save VC-4) without affecting traffic.
The XC is the same as ESW_2G_8F_E.
MPS_2G_8F L1 and L2 functionality is similar as DMGE_2_L2 (on page 6-
120) except that it has 8 FE ports.

EoP Cards
There are three EoP cards: the MEOP_4, the MEOP_4H, and the DMEOP_4.
This section describes these cards.
MEOP_4/MEOP_4H
The MEOP_4 and MEOP_4H is a DSlot module designed for BG-20B, it
supports up to 4 10/100Base-T interfaces for Ethernet service with standard
EoP (Ethernet over PDH) technology. It maps Ethernet packets to E1 or E1
virtual concatenation group first, and then maps E1s to VC-12s which are
connected to SDH matrix of ADM. The total bandwidth of MEOP_4H is up to
32 E1.
With limited L2 features, MEOP_4H/MEOP_4 supports both EPL and PB P2P
service, it can support two aggregation groups, each group has 8 VCGs/EoP
channels at WAN side and 2 FE ports at LAN side; the maximum bandwidth of
WAN ports is 16 E1 per group. 8:1 aggregation is supported per group. Traffic
aggregation is based on S-VLAN or C-VLAN ID.
MEOP_4H supports live insertion, while MEOP_4 does not support live
insertion.
Attribute management for the MEOP_4 card includes:
Configuration management:
VCG configuration
Adding or removing a VCG member
EoP encapsulation protocol configuration
Port attribute configuration
Create/delete/edit EPL and PB P2P VSI
Fault management:
Current alarms
Historical alarms
Alarm configuration
Performance management:
Current performance
Historical performance
Performance threshold
Maintenance:
Real-time traffic view
Loopback
Force link down

The MEOP_4H has the same functionality as the MEOP_4. It supports hot-
insertion.
To configure MEOP_4 card attribute:

1. In a BG-20 NE shelf view window, select the MEOP_4 card in the left
can view the general information of the MEOP_4.

2. To configure the EoP encapsulation protocol, select the EoP Ports tab in the
above window.
This window contains the EoP Protocol information and General

information. Set the parameters as required and click Apply to save your
changes.


MEOP_4 card or an EoP port. In the pop up menu, select Create VCG.
The VCG Attribute window opens.
Use this window to configure the virtual cascade mode (E1), and
bandwidth of each VCG.

4. To add or remove a VCG member, select the VCG in the object tree, and
then select the Configuration working mode.
For every member of this VCG, the E1s can be deactivated from this VCG.
5. To view real-time traffic of EoP ports, select the MEOP_4 card in the left
object tree. Then select the EoP Payload tab under the Maintenance
working mode.

In this window, you acquire the Rx and Tx traffic of EoP and FE ports
(ports 1 through 4). The traffic here refers to the average traffic within the
first 15 minutes in the acquisition process.
bps.
6. To view real-time traffic for ETY ports, select the MEOP_4 card in the left
object tree. Then select the ETY Payload tab under the Maintenance
working mode.



and No Loopback. The default is No Loopback.
DMEOP_4
The DMEOP_4 can be inserted into any Tslot in the BG-30B. It is very similar
to the MEOP_4 (see "MEOP_4/MEOP_4H" on page 6-136) module for the
BG-20B Dslot, except for backplane interface. It has:
2 ESSI bus: one connected to XIO30 A, another connected to XIO30 B.
The same redundancy design as the BG-30B module, like the PME1_21.

PCM Cards
This section describes how to access, assign, and configure the SM10 and the
SM_10E cards.
SM10 Card
SM10 Card Overview

The SM10 card is an external BG-40 PCM card that comprises eight E1
interfaces with LIU and framing, and a 512 x 512 DS-0 cross-connection
matrix with full-capacity hardware-based CAS processing, timing, and control
and communication functions of the system.
Supported Modules
The SM10 supports three common traffic module slots, as well as a special
small traffic module slot for Ethernet interfaces.
The following table lists the modules supported by the SM10 card.
Table 6-6: SM10 traffic modules
Name Description
SM_FXO_8 Eight foreign exchange office (FXO) or RD channels
SM_FXS_8 Eight foreign exchange stations (FXS) or FXD channels
SM_V24_8 Eight V.24 channels
SM_EM_24W6 Six 2W or 4W E&M channels
SM_V24 Can be configured with one synchronous, two asynchronous,
or eight transparent V.24 channels
SM_V24_D Supports point-to-multipoint operation
SM_V35_2 Two V.35 channels
SM_Omnicentor Supports the central side of an Omnibus type of service (OW
on PDH)
SM_Codir_4 Quad-port 64 K codirectional G.703 interface module for the
SM10 card
SM_FE_A Two 10/100BaseT channels (the bandwidth of each channel
can be E1 or N x 64 Kbps)

SM10 Slot Assignment

This section describes the slot assignment for the SM10.
To perform slot assignment for the SM10:

1. In a BG-40 NE shelf view window, select the SM10 card in the left object
tree. Then select the SubCards tab under the Configuration working
mode.
2. Click in the toolbar to open the Slot Assignment window.

3. Right-click on the sub slot that you want to assign. In the right menu, click
Add and select a card to assign.
4. Click Apply to save your assignment.

As Logical.
SM_10E Card
SM_10E Card Overview

The SM_10E card is a PCM card for BG-20 and BG-30 NEs. The card has the
following features:
Multiservice access through multiple daughter modules
Nonblocking DS-0 1280 x 1280 crossing matrix
44 E1s mapper/demapper
32 E1s framer
12 Mbps traffic bandwidth for each module slot; traffic add-and-drop
capacity up to 24 Mbps
622 Mbps ESSI bus access to MXC20
Fully loaded 40 W power consumption

Dimensions:
Base card:
Size (height): 25.4 mm
Size (width): 265 mm
Size (depth): 210 mm
Module:
Size (height): 20.0 mm
Size (width): 67.4 mm
Size (depth): 154 mm
Front-access connectors
Supported Modules
There are three module slots in the SM_10E, each with a capacity of 12 Mbps.
These can accommodate the interface modules described in the following table.
Table 6-7: SM_10E traffic modules
Name Description
SM_FXO_8E Eight-channel FXO access module
SM_FXS_8E Eight-channel FXS access module
SM_EM_24W_6E Six channels E&M signaling; six-channel 2/4 VF access
module
SM_V24E Configurable V.24 data access module that supports the
following three modes:
Eight transparent-only V.24
Four Asynchronous with full controls V.24
Two Synchronous with full controls V.24 that support
point-to-multipoint
SM_V35E Two-channel V.35 data access module
SM_Omni_E Omnibus central unit with external 2 x 24W interfaces
SM_Codir_4E Four-channel 64 K codirectional data access module
SM_EOP Two FE channels over E1 with a total WAN bandwidth of 8 x
E1s
SM_V35U_E Two-channel V.35 module support V.35 over both framed and
unframed E1
SM_V35_V11 Two-channel V.35 module support V.35/V.11 over both
framed and unframed E1
SM_C37.94 Two optical ports for teleprotection. A new module in BG-20.

SM_10E Slot Assignment

This section describes the slot assignment for the SM_10E.
To perform slot assignment for SM_10E:

1. In a BG-20 NE shelf view window, select the SM_10E card in the left
object tree. Then select the SubCards tab under the Configuration
working mode.
2. Click in the toolbar to open the Slot Assignment window.

3. Right-click on the sub slot that you want to assign. In the right menu, click
Add and select a card to assign.
4. Click Apply to save your assignment.

As Logical.

SM_C37.94
SM_C37.94 is a new module in BG-20 NE. This section describes how to
configure the SM_C37.94 module.
To configure the SM_C37.94 ports:

1. In a BG-20 NE shelf view window, in the left object tree, select Control
and Physical Object > MXC. Then select the C37.94 Port tab under the
2. Click in the toolbar to retrieve the information from NE equipment.

3. Set the attributes for the ports as described below:
Operation Mode: Auto or Manual or Transparent. Default is Auto
mode.
Max/Expected Bandwidth (N):
When Operation Mode is set as Manual, it stands for expected N,
default is 12;
When Operation Mode is set as Transparent or Auto mode, it stands
for max N, default is 12.
N Received From Line: the real N received from port line, read only.
Valid value is from 1 to 12.
N Sent To Line: the real N on TX direction, read only. Valid value is
from 1 to 12.
Port Status: the status of loss of optical signal on receive side.

Alarm Support of SM_10E from EMS

When the SM_10E service port is selected on the left object tree, the associated
E1/VC-12 port and its alarms will be displayed in current alarm page. This
feature enables customers to check associated E1/VC-12 alarms of service port.
To perform alarm support of SM_10E from EMS:

1. In the NE shelf view window, right-click on a service port with XCs of
SM_10E and click View Correlative E1 Alarm in the pop-up menu.

2. When you click View Correlative E1 Alarm in the right-click menu, the
associated E1/VC-12 port and its alarms will be displayed as below.
3. User can check the associated E1/VC-12 alarms of service port from this
window.

Control Cards
This section describes the control cards.
MXC4X
The MXC4X is the cross-connect, timing, and control units of the BG-40.
To view the MXC4X card:

and Physical Object > MXC4X. Then select the Configuration working
mode. The description of the MXC4X card is shown in the General tab in
the following figure.

MXC20
The MXC20 is the control card of the BG-20, including cross-connect matrix,
control unit, and other functions.
To view the MXC20 card:

and Physical Object > MXC. Then select the Configuration working
mode. The description of the MXC20 card is shown in the General tab in

MCP30/MCP30B
The performance of MCP30 (original main control card of BG-30) is
inadequate to manage BG-30 element, some deficiencies have been exposed in
testing and real applications, such as:
Inefficient internal communication
Very slow startup procedure
Slow response when operating complex commands
Uptight memory allocation
When more and more new cards and features are added, especially new L2
cards, the MCP performance (CPU, communication, memory, etc.) is becoming
bottleneck of the system, which may produce more and more limitations for
NE configuration and applications.
MCP30B is an enhanced substitute for MCP30, it is designated to overcome
the deficiencies of MCP30 and significantly increase overall performance of
control unit including microprocessor and communication. Besides enhancing
performance, some improvements and optimization can also be considered in
MCP30B to improve the system reliability and maintainability, depending on
the cost and necessity.
MCP30B is a new card type, which makes MS slot of BG-30B able to support
two kinds of card: MCP30 and MCP30B.

To manage the MCP30 card:

and Physical Object > MCP30. Then select the Configuration working
mode. The description of the MCP30 card is shown in the General tab in

2. To set the VC12 objects, select Control and Physical Object > MCP30 in
the object tree and then select the TTI and TSL tab under the
3. When XIO30 is assigned as XIO30Q_1&4, only the Unframed Clear

Channel mode is supported, as shown in the following window.

From this window, the VC-12 can be set to following modes:

Framed Clear Channel--Standard
Framed Clear Channel--BG-40 2nd Channel Compatible
Unframed Clear Channel
To manage the MCP30B card:

and Physical Object > MCP30B. Then select the Configuration working

2. To manage the ports, select Control and Physical Object > MCP30B and
then select the Management Ports tab under the Configuration working
mode.
Or you can select Control and Physical Object > MCP64 from the left
object tree and then select the Configuration working mode.

3. To set the VC12, select Control and Physical Object > MCP30B in the
object tree and then select the TTI and TSL tab under the Configuration
working mode.
4. Select Control and Physical Object > MCP30B >VC12 in the object tree
and then select the Clear Channel tab under the Configuration working
mode.


MCP64
MCP64 is the main control unit for BG-64 shelf. It is responsible for both
internal and external communications, equipment and network element
management and control.
The main functions of MCP64 are:
Provide NE management interface for management stations: EMS-BGF
and LCT-BGF
Internal communication and control for all cards and components
DCC, clear channel processing and routing for network communication
SDH OH process and interface
NE management including configuration, alarm, PM and various
maintenance functionality
T3/T4 Interface
NE alarm indication and alarm outputs/inputs
MCP64 CF card is extractable from front panel and supports hot-swapping.
Data integrity protection is supported in case of power loss. Power supply
system supports 10ms hold-up time, when power input is down, it should
produce an interrupt to CPU to inform the power failure. When CF card is
being accessed, LED indication is supported.
MCP64 can be reset by a button on front panel and the button reset is a warm
reset.

To manage the MCP64 card:

and Physical Object > MCP64. Then select the Configuration working

2. To manage the ports, select Control and Physical Object > MCP64 and
then select the Management Ports tab under the Configuration working
mode.
Or you can select Control and Physical Object > MCP64 from the left
object tree and then select the Configuration working mode.

3. To set the VC12, select Control and Physical Object > MCP64 in the
object tree and then select the TTI and TSL tab under the Configuration
working mode.
4. Select Control and Physical Object > MCP64 >VC12 in the object tree
and then select the Clear Channel tab under the Configuration working
mode.


Power Units
This section describes the power units.
The BG-40 NE has two power supply modes:
INF_4X-DC: Power Filter Unit (-48 VDC)
AC_CONV-4X: Power Conversion Unit (220 VAC)
When fully configured, the maximum power consumption of the BG-40
equipment is 110 W.
The INF/AC_CONV is the power module for the BG-20 NE. Power
consumption: 60 W for BG-20B and 150 W for BG-20E.
There is a new INF-20B type: INF-20BH with larger power output to meet the
assignment of ME_2G_4F.
The BG-30 NE's power units are as follows:
INF-30B/INF-30BH/INF-30E: Single input DC power supply module
with input filtering and a fan power supply.
AC_CONV-30B/AC_CONV-30E: Single input AC power supply card,
with AC-to-(-48 V) converter and fan power supply.
INF-64 is the DC power supply with input filtering in BG-64. It supports 1+1
with analog protection for -48V and Fan PS and one INF-64 can serve the
power supply for the whole BG-64 shelf. INF-64 can provide 48V power for all
cards in BG-64. The Maximum Power Consumption of BG-64 supported by
INF-64 is 360W.

Fan Control Units

Setting the Fan Work Mode
The EMS-BGF can manage the NE fans work mode. Fan work modes are:
Force Open: The user starts the fan manually.
Temperature Auto Control: The fan is controlled by the temperature sensor.
When the temperature exceeds the threshold, the fan starts.
To access the Fan Status window:

1. In an NE shelf view window, select the fan unit under Control and
Physical Object in the left object tree. Then select the Status tab under the
2. Modify the fan work mode for the NE as required.

4. Click in the toolbar to retrieve the information to view.


7
Managing MPLS Services
In this chapter:
Overview ......................................................................................................... 7-1
Workflow ......................................................................................................... 7-3
Supported Cards .............................................................................................. 7-3
Managing Tunnels ........................................................................................... 7-4
Creating MPLS Services ............................................................................... 7-43
Connectivity Fault Management (CFM) ....................................................... 7-77
Configuring ACL Profile ............................................................................... 7-95
Port Mirror ..................................................................................................... 7-97
Configuring Switch OAM ............................................................................. 7-99
Fast ReRoute (FRR) .................................................................................... 7-100
Overview
This section describes the Multi Protocol Label Switching (MPLS) services.
A label is assigned for an IP packet at the MPLS edge router (LER: Label Edge
Router-PE) when the IP packet entering the MPLS network and the MPLS core
network routers (LSR: Label Switching Router-P) make forwarding decisions
based on the label. The MPLS has a Control Plane and a Data Plane, as shown
in the following figure:

Managing MPLS Services EMS-BGF User Manual
The Control Plane is responsible for the establishment and maintenance of

correct label binding information among routers; the Data Plane uses label
information carried in the packets, and label binding information maintained by
the LSR, to forward the packet.
The value of the MPLS is in Traffic Engineering. The major goal of the MPLS
Traffic Engineering (MPLS-TE) system is to facilitate efficient and reliable
network operations while simultaneously optimizing network resource
utilization and performance. The MPLS-TE reduces the overall cost of
operations by efficient use of bandwidth resources and provides the QoS.
An MPLS network consists of MoT links, MPS PEs with MPLS NNI ports,
and MPLS tunnels.
VC Label is supported in MPLS services and MPLS Ring ERP Control VSI.
This is the inner label used to distinguish between services using the same
tunnel. Single tunnel can carry multiple services. The Ethernet frames are
encapsulated in MPLS frames with a tunnel outer label (MPLS label) and an
inner label (VC label) indicating the service to which the frame belongs.
For different data cards, the attribute of the VC Label Scheme can be Single
Label or Same Incoming Label:
Single Label: In this mode, all the InVClabel and OutVClabel should be
set the same. The range is 1024~waterline (default is 4096).
Same Incoming Label: In this mode, all the InVClabel should be set the
same, and all the OutVClabel settings can be different.
To define the waterline, open the file emsserver.properties under the folder:
\EMS-BGF\etc and there is a line to set the waterline:
VC_Label_Waterline = 4096

EMS-BGF User Manual Managing MPLS Services
Modify the setting as you want and save the setting to the file. If the value of
the existing Single VCLabel is greater than 4096, the waterline must be set
greater than the value of the existing Single VCLabel.
Workflow
The procedure for creating Ethernet Services over an MPLS can be performed
as below:
Define the Configuration Mode as MPLS.
Assign PE ID and MPLS Network ID. Each MPLS requires a unique PE
ID.
Configure ports as MoT port type.
Set the VCG attribute. In the Create VCGs window, configure the VCG
bandwidth.
Create required tunnels.
Select ports and remote PEs for the services.
Set the other required attributes for the services.
Supported Cards
Following are the Layer 2 data cards in the MPLS services:
MPS_4F
MPS_6F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
MPS_2G_8F
ME_2G_4F
The MPLS support five types of Ethernet Services:
MPLS P2P
MPLS MP2MP
MPLS RootedMP/Leaf
MPLS RootedMP/Root
MPLS BPDU Tunneling

The MPLS RootedMP/Leaf and MPLS RootedMP/Root can be supported in

DMGE_2_L2, DMGE_4_L2 and DMGE_8_L2.
Managing Tunnels
This section describes the tunnels in the MPLS network.
Overview
A tunnel is composed of tunnel segments. Each tunnel segment is associated
with a single MPS card.
The tunnel model is shown in the following figure:
A tunnel segment is subdivided to in-segment CTP and out-segment(s) CTP

objects that are interconnected by a single cross-connect (XC) object:
In-segment CTP is analogous to [Ingress I/F, MPLS Label].
Out-segment CTP is analogous to [Egress I/F, MPLS Label].
Cross-connect (XC or SNC) describe the conceptual connection between
one in-segment and one or more out-segments, where multiple out-
segments can exist in point-to-multipoint (P2MP) tunnel segment.
Both P2P and P2MP tunnel XCs are supported in EMS-BGF.
P2P Tunnel: a tunnel originates at the source PE, traverses through Transit
Ps, and terminates at the destination PE.

The following figure illustrates the Point-to-Point (P2P) tunnel:
The source PE pushes two MPLS labels into each customer's Ethernet
packet entering the tunnel. The inner MPLS label is called VC-label,
which represents the VPN to which the packet belongs. The VC label
serves as demultiplexor field. The outer MPLS label is called Tunnel
label, and represents the tunnel to which the packet is mapped to.
The transit Ps simply swap the MPLS packets from (InPort, InLabel) to
(OutPort, OutLabel). For MPS, there is no tunnel label swap along the
path.
The destination PE determines that it is the destination of the tunnel
based on the Tunnel label, and finds out the VPN of the packet based
on the VC label. It then looks up the MAC of the packet to find out the
destination Ethernet port, pops out the two MPLS labels, and forwards
the packet to the CE port or ports.
P2MP Tunnel: a point-to-multipoint (P2MP) tunnel at an LSR is modeled
as in-segment and out-segment(s) interconnected by a cross-connect (XC).
The following figure shows the P2MP tunnel model:

The in-segment is analogous to [Ingress I/F, MPLS Label], and

contains parameters such as CoS. Head in-segment (ingress PE) has no
I/F and label.
The out-segment is analogous to [Egress I/F, MPLS Label], and
contains parameters such as bandwidth. Tail out-segment (egress PE)
has no I/F and label.
The cross-connect (XC) is analogous to [Tunnel ID], and contains
parameters such as ingress PE, and also contains a list of attributes per
sub-tunnel where each sub-tunnel is analogous to [Tunnel ID, Egress
PE].
Sub-tunnel: A P2MP tunnel is constructed from sub-tunnels. Each sub-
tunnel starts at same source PE and ends at a different destination PE. Sub-
tunnels may share a branch, in which case the data plane forwards only one
packet copy to that link.
For sub-tunnels belonging to a same P2MP tunnel XC:
They share the common properties of the branch tunnel, such as In-
Segment object. When adding sub-tunnels to the P2MP tunnel XC,
these properties are read-only.
Each sub-tunnel has one Out-Segment connects to a unique remote PE.
When adding a sub-tunnel, user is required to configure the Out-
Segment:
Select an out MoT port.
User can change the label.
Sub-Tunnels can share the Out-Segment. The link between this
transit PE and the next hop (NH) become the shared branch.
Sub-Tunnels may share the By-Pass tunnel.
Tail Sub-Tunnel: Transit PEs contain many sub-tunnels but only one tail
sub-tunnel. Tail sub-tunnel terminated at this PE.
For P2MP Transit&Tail PE, user can configure only one tail sub-tunnel
for the tunnel XC.
A Transit&Tail PE can be configured without tail sub-tunnel.
Tail sub-tunnel does connect to any MoT port. When configuring the
tail sub-tunnel, user just need mark the P2MP XC has a tail sub-tunnel.

Workflow
To create a P2P tunnel XC, use the following steps orderly:
1. Define the Configuration Mode as MPLS.
2. Assign PE ID and MPLS Network ID. Each MPLS requires a unique PE
ID.
3. Configure ports as MoT port type. MPLS supports a hybrid of PB ports
with MPLS ports. You should set the port type as MoT for P2P tunnels.
4. Set the VCG attribute. In the Create VCGs window, configure the VCG
bandwidth.
5. To define a Destination PE or Source PE: Be sure that there is at least one
another MPLS switch object that has the same MPLS Network ID as the
switch that you are configuring.
6. Create a tunnel XC for the selected MoT port. In the Create Tunnel XC
window, the following parameters can be configured:
Input the XC Name, Customer, CoS and Bandwidth.
Select the XC Role as one of the following values:
Head. Configure the Out-Segment: set MPLS Out Label, select
one of the MoT ports as the Out Port, and select a Destination PE.
Tail. Configure the In-Segment: MPLS In Label, In Port, and
Source PE.
Transit. Configure both the In-Segment and Out-Segment: MPLS
In Label, MPLS Out Label, In Port and Out Port. There is no
Label Swap for MPLS, so the MPLS In Label and MPLS Out
Label should be same.
Configure the Protection Type. A tunnel XC can be configured as:
Unprotected.
Bypass.
Protected.
7. Configure other advanced parameters, such as:
Enable Tunnel OAM
To create sub-tunnel:
1. Create the P2MP XC, the XC role can be Head or Transit&Tail.
2. The Head tunnel XC need not configure the In-Segment.
3. The Transit&Tail XC need configure the In-Segment, which is shared by
the sub-tunnels.
4. For Head tunnel XC, user can add the sub-tunnel to it.
5. For Transit&Tail XC, user can add sub-tunnel to it or edit it as a tail sub-
tunnel.

6. For MoT port, the Out Label on all of the sub-tunnel should be same.
7. The Adding sub-tunnel window displays the common properties of the sub-
tunnels as read-only. User need configure the below:
The remote PE.
The Out-Segment connects the remote PE.
Creating Tunnel XCs

This section describes the procedure for creating tunnel XCs, including P2P
and P2MP tunnel XCs.
Accessing the Create Tunnel XC Window

This section describes how to access the Create Tunnel XC window.
To access the Create Tunnel XC window:

1. In the BG-20/BG-20C/BG-30/BG-64 NE shelf view window, select the
Switch object under an MPLS card in the left object tree. Then select the
General tab under the Configuration working mode.

2. In the above window, set the Switching Mode to MPLS PE. In the MPLS
PE Configuration field, assign a PE ID.
Set the other configurations if needed. Click Apply to save your settings.

3. Right-click on the MPLS card in the left object tree and select Define MoT
Port from the menu. The Define MoT Port window opens.

From the window, set the ports as MoT ports and click Apply.

4. To configure the VCG bandwidth, right-click on the MPLS card in the left
object tree. The Create VCGs window opens.

5. To define a destination PE or source PE, do the same operation from Step 1

to Step 4 for another MPLS switch object. This switch can be either in
another MPLS card or in the same MPLS card (except the MOT port and
destination/source PE) with the Switch object that you are configuring, but
they must set with the same MPLS Network ID.

6. In the NE shelf view window, select the Switch object in the left object
tree. Then select the Tunnel XC List tab under the Services working
mode.
7. To create a tunnel XC, select the Create Tunnel XC button in the

toolbar. The Create Tunnel XC window opens.

Creating P2P Tunnel XC

This section describes the procedure for creating P2P tunnel XC.
There's Label Swap supported, so the MPLS In Label and MPLS Out Label
of the PtP Transit Tunnel XC can be set different. When Dual FRR is disabled,
the MPLS In Label and MPLS Out Label of the PtMP Transit Tunnel XC
can be set different. When Dual FRR is enabled, the MPLS In Label and
MPLS Out Label of the PtMP Transit Tunnel XC should be the same.
To create an unprotected/bypass tunnel XC:

1. To create a P2P tunnel XC, in the Create Tunnel XC window (see
"Accessing the Create Tunnel XC Window" on page 7-8), do the following
configurations:
Select the Protection Type. A tunnel XC can be configured as:
Unprotected or Bypass.
Select PtP as XC Type.
Select the XC Role as one of the below values: Head, Transit or Tail.
Head. Configure the Out-Segment: set MPLS Out Label, select
one of the MoT ports as the Out Port, and select a Destination PE.
Tail. Configure the In-Segment: MPLS In Label, In Port, and
Source PE.
Transit. Configure both the In-Segment and Out-Segment: MPLS
In Label, MPLS Out Label, In Port and Out Port.
Input the XC Name, XC ID, Customer, CoS and Bandwidth. CAC is
implemented in LightSoft only. In EMS-BGF standalone mode, user
have to configure enough tunnel and bypass tunnel bandwidth.
Select the Enable Tunnel OAM checkboxes if needed.

2. For Transit and Tail of a Bypass tunnel XC, user can also configure the
DualFRR. Select the DualFRR checkbox if needed.

3. Click Save to save the tunnel to the Recent Saved XCs area. Or click
Activate to save and activate the XC.
4. To activate a tunnel XC, select the tunnel XC in the Recent Saved XCs list
and click Activate All.

To create a protected tunnel XC:

1. To create a protected tunnel XC, select an unprotected head /unprotected
transit /unprotected transit&tail tunnel XC tunnel XC from the Tunnel XC
List tab window.
2. Select the Add/Remove ByPass Tunnel XC button in the toolbar. The

Add Bypass XC window opens.

3. The SubTunnel Select field lists the entire bypass tunnel XCs that protect
the selected Out Port with the same CoS with the configuring bypass XC.
Select an XC from the Select Bypass Tunnel XC list, set the NNH Out
Label value if needed and click Add Bypass.
To remove the bypass tunnel XC, select the bypass XC you want to remove
in the Recent Saved Bypass XCs list, and click Remove Bypass.
4. Close the Add Bypass XC window. You can view the protected tunnel XC
and its bypass tunnel XC highlighted in the list.

5. To remove the bypass tunnel XC of a protected tunnel XC, select the

protected tunnel XC in the Tunnel XC List and click .
6. In the Recent Saved Bypass XCs area, select the bypass XC you want to
remove and click Remove Bypass.
Creating P2MP Tunnel XC

This section describes the procedure for creating P2MP tunnel XC. A P2MP
tunnel is constructed from sub-tunnels. Each sub-tunnel starts at same source
PE and ends at a different destination PE. Sub-tunnels may share a branch, in
which case the data plane forwards only one packet copy to that link.
DMGE_2_L2, DMGE_4_L2, DMGE_8_L2, MPS_2G_8F and ME_2G_4F
support creating P2MP tunnel XC.
Table 7-1: PE name and PE ID list
NE Name PE ID
a 3
b 4
c 2
d 1

To create the P2MP tunnel XC:

1. Create P2MP tunnel XC for a, as shown below. PE3 is the head PE.
In the Create Tunnel XC window:

Select Unprotected as Protection Type.
Select PtMP as XC Type.
In the XC Role list, select Head.
Select port and destination PE in the Select Port and Select
Destination PE lists.
Set the MPLS Out Label.
In the MPLS XC Information field, set XC ID, Customer and XC
Name as needed.
Click AddBypass. The sub-tunnel is added into the Sub Tunnel list.
When you finish adding the sub-tunnel, click Save to save the tunnel
XC to the Recent Saved XCs list. Or click Activate to activate the
tunnel XC.
To activate the saved XCs in the Recent Saved XCs list, click Activate
All.

2. Create P2MP tunnel XC for d, as shown below.
In the Create Tunnel XC window:

In the XC Role list, select Transit&Tail.
Enable Add Local Tail by selecting the checkbox before it.
Select In Port, Out Port and Destination PE in the corresponding
lists.
Set the MPLS In Label and MPLS Out Label.
Name as needed.
Click Add Subtunnel. The sub-tunnel is added into the Sub Tunnel
list.
In the Sub Tunnel list, you can enable the DualFRR for sub-tunnels as
needed by selecting the checkboxes of DualFRR.
When you finish adding the sub-tunnel, click Save to save the tunnel
XC to the Recent Saved XCs list. Or click Activate to activate the
tunnel XC.
All.

3. Create P2MP tunnel XC for b, as shown below.
In the Create Tunnel XC window of MPS_2G_8F in the BG20-1 NE:

In the XC Role list, select Transit&Tail.
Enable Add Local Tail by selecting the checkbox before it.
Select In Port in the Select In Port list. We don't need to select out
port and destination PE for PE4 in the example module.
Set the MPLS In Label. There is no out label for PE4.
Name as needed.
Click Save to save the tunnel XC to the Recent Saved XCs list. Or
click Activate to activate the tunnel XC.
All.

4. User can view from Lightsoft after admitting successfully.
Dual FRR
The idea of Dual FRR is to define a bypass tunnel that provides link and node
protection concurrently. This bypass tunnel originates at the PLR, drops node-
protected traffic at N-MP, and continues to L-MP where it drops link-protected
traffic. The behavior at N-MP may be referred to as "Drop & Continue".
As illustrated in the figure, P2MP tunnel flows from PE1 (PLR) to PE2 (L-
MP), where it splits towards PE3 (N-MP). This P2MP tunnel is protected as
follow:
Bypass B1 protects the sub-tunnels to PE2 against the failure of link PE1-
PE2 (Link protection).

Bypass B1 protects the sub-tunnels to PE3 against the failure of PE2 (Node
protection).
Dual FRR is enabled as follow:
Bypass Dual FRR need by enabled at Transit and Tail, no need for Head:
B1 XC at PE2 (L-MP) and PE3 (N-MP)
P2MP Sub-tunnels Dual FRR need be enabled at Transit&Tail:
Sub-tunnels to PE3/PE5 at Transit&Tail (PE2/PE3)
We have configured the MPLS cards in EMS-BGF for the above module, as
shown in the following table.
Table 7-2: PE, PE Name and PE ID list
PE NE Name PE ID
PE1 a 3
PE2 d 1
PE3 b 4
B1 c 2
From Lightsoft, we can view the P2MP tunnel in the example module as
below.

From EMS-BGF, we can see the details of the tunnels in the example module
as below.
1. Tunnel XC Detail for PE1.

Using the Tunnel XC List

You can perform the following tunnel XC' s management actions in the tunnel
list:
Filter the tunnel list
Activate/Deactivate tunnel XCs
View/Edit/Delete a tunnel XC
Upload tunnel XCs
Export XCs
Tunnel XC WRED profile
Tunnel XC performance, including:
Current
NE History
EMS History
Threshold Settings
Monitoring and Reporting

Tunnel XC Alarm, including:

Current
History
For a head tunnel XC, user can also perform the operation: Tunnel XC OAM
State.
To access the tunnel XC list:

In the NE shelf view window, select the MPLS Switch object in the left
object tree. Then select the Tunnel XC List tab under the Services
working mode.

Filtering the Tunnel XC List

This section describes how to filter the tunnel XC list.
To filter the tunnel XC list:

1. In the tunnel XC list, click + to expand the Filter area.
2. Set the attributes in the area as required.

3. Click to filter the list.

Viewing/Editing/Deleting a Tunnel XC
This section describes how to view, edit, or delete a tunnel XC.
To view/edit/delete a tunnel XC:

1. In the tunnel XC list, select a tunnel XC and right-click on it. A menu pops
up.

2. To view a tunnel XC, select the XC in the list, and then select View
Tunnel XC from the pop up menu. The Tunnel XC Detail window opens.
3. To edit a tunnel XC, select the XC in the list, and then select the Edit
Tunnel XC from the pop up menu. The Edit Tunnel XC window opens.

4. To delete a tunnel XC, you should first deactivate the XC:

Select the XC in the list, and then select the Deactivate Tunnel XC
from the pop up menu.
Select Delete Tunnel XC from the pop up menu.
You can perform these operations by selecting the tool buttons in the toolbar.
Uploading Tunnel XCs

This section describes how to upload tunnel XCs.
To upload tunnel XCs:
1. In the tunnel XC list, select the Upload button in the toolbar. The
Tunnel XC Upload window opens.

2. Click Upload to upload all the Tunnel XCs. The status bar shows the
consistency status between the NE and the database. If the NE and the
database are inconsistent, select the Compare Result tab to display the
inconsistency results.
3. Click Overwrite to overwrite the database with the NE data.

Exporting Tunnel XCs

This section describes how to export tunnel XCs as an XML file.
To export Tunnel XCs:

1. In the tunnel XC list, select a tunnel XC in the list and then click in the
toolbar. The following window opens.
2. Click Save to export the selected XC as a XML file.

Configuring Tunnel XC WRED Profile

This section describes how to configure the tunnel XC WRED profile.
To configure tunnel XC WRED profile:

1. In the tunnel XC list, select a tunnel XC and right-click on it. Select
Tunnel XC WRED Profile from the pop up menu. The Tunnel State
WRED Profile window opens.
2. Select the State and Mode from the corresponding dropdown list.
Performing Tunnel XC Performance

This section describes how to perform the tunnel XC performance, including:
Current Performance
Recent Performance
History Performance
TCA Threshold
Monitor and Report

To perform the tunnel XC performance:

1. In the tunnel XC list, select a tunnel XC and right-click on it. From the
popup menu, select Tunnel XC Performance.
2. To view the current performance of the selected tunnel XC, select Tunnel
XC Performance > Current Performance.

3. To view the recent performance of the selected tunnel XC, select Tunnel
XC Performance > Recent Performance.

4. To view the historical performance of the selected tunnel XC, select
Tunnel XC Performance > History Performance.

5. To set threshold of the selected tunnel XC, select Tunnel XC

Performance > Threshold Setting.

6. To set monitoring and reporting, select Tunnel XC Performance >
Monitoring and Reporting.
From this window, you can set whether to monitor and auto-report the
tunnel XC.

7. To reset the performance counters, select Tunnel XC Performance >

Reset Performance Counters. A confirmation window opens prompting
you to confirm resetting the PM counters.
Click Yes to confirm.
Managing Tunnel XC Alarms

This section describes how to manage the tunnel XC alarms, including:
Current
History
To manage tunnel XC alarms:

1. In the tunnel XC list, select a tunnel XC and right-click on it. From the pop
up menu, select Tunnel XC Alarm.

2. To view current alarms, select Tunnel Alarm > Current.
3. To view historical alarms, select Tunnel Alarm > History.

4. To mask the alarms of the selected tunnel XC, select Tunnel Alarm >
Monitoring and Reporting.

Viewing Tunnel XC OAM State

For head tunnel XCs, you can also view the tunnel XC OAM state.
To view tunnel XC OAM State:

In the tunnel XC list, select a tunnel XC and right-click on it. Select
Tunnel XC OAM State from the menu. The Tunnel XC State window
opens.

Creating MPLS Services

Once you have created the tunnels, you can create MPLS services, as described
in this section.
For the MPS_4F, MPS_6F, DMFE_4_L2, DMFX_4_L2, ME_2G_4F and
MPS_2G_8F cards, you can create the following three MPLS services:
MPLS PtP service
MPLS MPtMP service
BPDU Tunneling service
For the DMGE_2_L2, DMGE_4_L2, DMGE_8_L2 card, you can create the
following five MPLS services:
MPLS PtP service
MPLS MPtMP service
MPLS RootedMP/Leaf service
MPLS RootedMP/Root service
MPLS BPDU Tunneling service

MPLS PtP Service

This section describes how to create an MPLS PtP service.
To create an MPLS PtP service:

1. In an NE shelf view window, in the left object tree, select the Switch object
under an MPLS card. Then select the VSI List tab under the Services
working mode.

opens.
3. To create MPLS PtP, select MPLS PtP from the Service Type dropdown
list.
Enabled.
5. Enter the VSI ID, User Label, Customer and S-VLAN values in the left
areas of the window and select the VC Label Scheme. You can also input

6. In the right Objects Selections area, you can select one port and one
remote PE from the relevant list. Right-click an object to deselect, or select
an object in the lower-right list and click in the toolbar.

window. Click + to expand the UNI port. You can enlarge the lower-right
area by clicking the icon above the toolbar, as shown below.

attributes.
Any change that conflicts with an already defined policer, or that is set
with No Rate Limit, is rejected.
A CoS can only be removed or discarded from the mapping when it is not
associated with No Rate Limit or a policer profile. When this occurs, the
operation is rejected and the following message is displayed: A policer is
associated with this CoS.
disabled.


10. For the selected Remote PE, select a head tunnel XC that can reach the
Remote PE from the CoS drop-down list and set the In VC Label and Out
VC Label in the corresponding field according to the VC Label Scheme
you have selected.
11. Click Active to create and activate the MPLS PtP. If you click Save, the PB
PtP will be saved but not activated. To activate it, select the Recent Saved
VSIs tab.
MPLS PtP then is activated.

MPLS MPtMP Service

This section describes how to create an MPLS MPtMP.
To create an MPLS MPtMP service:

1. In the NE shelf view window, select the Switch object in the left object
tree, then select the VSI List tab under the Services working mode.

opens.
3. To create MPLS MPtMP, select MPLS MPtMP from the Service Type
drop-down list.
Enabled.
5. Enter the VSI ID, User Label, Customer, S-VLAN and BSC Threshold
values as required and select the VC Label Scheme in the left areas of the
window.
6. The vFIB Quota can be set for PB/MPLS MPtMP. When this quota is
reached, the learning process can be halted, in which case flooding is
performed (when the Switch Quota is forwarded), or unknown addresses
are dropped (when the action is dropped).
7. Select the Enable PM Collection and Enable Egress Counting
checkboxes if needed. You can also input additional descriptions into the
VSI Description field.

8. In the Objects Selections area, you can select the ports and Remote PEs in
the relevant list. Right-click an object to deselect, or you can select an
object in the lower-right list and click in the toolbar.

window. Click + to expand the UNI port. You can enlarge the lower-right
area by clicking above the toolbar, as shown below.


attributes.
option to enable the same DSCP to provide CoS mapping policy. The
disabled.

Select in the toolbar. The following window opens.
you have selected.

13. Click Active to create and activate the MPLS MPtMP. If you click Save,
the MPLS MPtMP will be saved but not activated. To activate it, select the
Recent Saved VSIs tab.
MPLS MPtMP is then activated.

MPLS BPDU Tunneling Service

This section describes how to create an MPLS BPDU Tunneling service.
To create an MPLS BPDU Tunneling Service

1. In the BG-30 NE shelf view window, select the Switch object under an
MPLS card in the left object tree. Then select the VSI List tab under the

opens.
3. To create MPLS MPtMP, select MPLS BPDU Tunneling from the

Service Type dropdown list.
enabled.
5. Enter the VSI ID, User Label, Customer, and S-VLAN values as required
and select the VC Label Scheme in the left areas of the window.

7. In the Objects Selections area, you can select one port and one Remote PE,
or two ports with the same port type. Right-click an object to deselect, or
you can select an object in the lower-right list and click in the toolbar.


attributes.
9. In the Tag Definitions field, only Untagged can be used for BPDU, so
user don't need to select the type of tag.
you have selected.

11. Click Active to create and activate the MPLS BPDU Tunneling. If you
click Save, the MPLS BPDU Tunneling will be saved but not activated. To
activate it, select the Recent Saved VSIs tab.
MPLS BPDU Tunneling then is activated.

MPLS RootedMP/Leaf Service

This section describes how to create an MPLS RootedMP/Leaf. It is supported
for the DMGE_2_L2, DMGE_4_L2 and DMGE_8_L2 card.
To create an MPLS RootedMP/Leaf service:

1. In the BG-30 NE shelf view window, select the Switch object under
DMGE_2_L2/DMGE_4_L2/DMGE_8_L2 card in the left object tree. Then
select the VSI List tab under the Services working mode.

opens.
3. To create an MPLS RootedMP/Leaf, select MPLS RootedMP/Leaf from

the Service Type dropdown list.
enabled.
5. Enter the VSI ID, User Label, Customer, VC Label, S-VLAN, and BSC
Threshold values as required and select the VC Label Scheme in the left
areas of the window.

7. In the Objects Selections area, you can select the ports and, at most, two
Remote PEs in the relevant list. Right-click an object to deselect, or you

window. Click + to expand the UNI port and can enlarge the lower-right

attributes.
disabled.


you have selected.
12. Click Active to create and activate the MPLS RootedMP/Leaf. If you click
Save, the MPLS RootedMP/Leaf will be saved but not activated. To
MPLS RootedMP/Leaf then is activated.

MPLS RootedMP/Root Service

This section describes how to create an MPLS RootedMP/Root. It is supported
for the DMGE_2_L2, DMGE_4_L2 and DMGE_8_L2 card.
To create an MPLS RootedMP/Root service:

1. In the BG-30 NE shelf view window, select the Switch object under
DMGE_2_L2/DMGE_4_L2/DMGE_8_L2 card in the left object tree. Then
select the VSI List tab under the Services working mode.

opens.
3. To create an MPLS MPtMP, select MPLS RootedMP/Root from the

Service Type dropdown list.
enabled.
5. Enter the VSI ID, User Label, Customer, VC Label, S-VLAN, and BSC
Threshold values as required and select the VC Label Scheme in the left
areas of the window.
7. In the Objects Selections area, you can select the ports and Remote PEs in
the relevant list. Right-click an object to deselect, or you can select an
object in the lower-right list and click in the toolbar.

8. Select a P2MP head Tunnel that you have created in the Select P2MP
Head Tunnel list.

window. Click + to expand the UNI port and can enlarge the lower-right


attributes.
disabled.

you have selected.

13. Click Active to create and activate the MPLS RootedMP/Root. If you click
Save, the MPLS RootedMP/Root will be saved but not activated. To
MPLS RootedMP/Root then is activated.

Using the MPLS VSI List

Management for the MPLS VSI list is the same as for the PB VSI list.
For details about using the MPLS VSI list, refer to the DMFE_4_L2's Using
the VSI List (on page 6-107).
Managing Multicast Configuration for MPLS

RootedMP/Leaf Service
For the MPLS RootedMP/Leaf services, user can perform VSI multicast
configuration.
To manage multicast configuration:

1. In the NE shelf view window, select DMGE_2_L2 > Switch in the left
object tree. Then select the Services working mode, the VSI list is
displayed as shown in the following window.

2. Select a VSI with the type: MPLS_RootedMPLeaf in the list and right-
click on it, from the pop up menu, select VSI Multicast Configuration.
The Edit/View Multicast Parameters window opens.
3. In the Multicast Configuration tab, in the General Parameters field, you

can set Enable IGMP or Disable IGMP by selecting the relevant radio
button.
When Enable IGMP is selected, you can set the parameters for
Membership Interval and LQMT Interval. The range for
Membership Interval is 60- 1023 seconds. The default is 260 sec.
When Disable IGMP is selected, you can select the Flood All Groups
checkbox.

4. Input the IP multicast address in the Add/Remove Address field and click
Add.
5. Click Apply to finish the configuration.

6. To edit or view the multicast configuration, select the VSI in the VSI List
and right-click on it. The Edit/View Multicast Parameters window opens.

7. To view the multicast status, select the Multicast Status tab in the window.
MPLS Port Protection Switch

This section describes how to configure MPLS port protection switch.
1. In the NE shelf view window, select the MoT port under an MPLS card in
the left object tree. Then select the Maintenance working mode.

2. Set the protection mode by selecting the corrsponding radio botton.

Lockout of MPLS Interface: standby port is locked out and cannot be
used by protection.
Forced Switch: A forced switch has a higher priority than alarms,
which means that an alarm on one of the protected ports does not cause
the standby port to protect the port with the alarm on it.
Manual Switch: A manual switch has a lower priority than alarms,
which means that an alarm on one of the protected ports causes the
standby port to protect the port with the alarm on it.
Release: The release operation is used to release a lockout, a forced
switch, or a manual switch on a protection unit contained in the port.
Connectivity Fault Management

(CFM)
This section describes the Connectivity Fault Management (CFM).
Overview
The goal of Ethernet OAM is to allow service providers to manage each
customer service instance individually. Ethernet OAM defines proactive and
diagnostic fault localization procedures for point-to-point and multipoint
services that span one or more links. It is end-to-end within an Ethernet
network. Ethernet OAM functions for Connectivity Fault Management (CFM)
allow detection, verification, localization and notification of different defect
conditions.
Ethernet CFM relies on a functional model consisting of hierarchical
Maintenance Domains (MD). An MD is an administrative domain for the
purpose of managing and administering a network. An MD is assigned a
unique MD level (among eight possible) by the administrator, which is useful
for defining the hierarchical relationship of domains. Maintenance domains
may nest or touch, but cannot intersect. If two domains nest, the outer domain
must have a higher maintenance level than the one it contains.
A Maintenance Domain is defined by provisioning which switch/router ports
are interior to the Domain.
In addition, Maintenance End Points (MEP) are designated on the edge ports
for that domain for each EVC, and Maintenance Intermediate Points (MIP) are
designated on relevant interior ports.
The demarcation of these maintenance points is left to the discretion of the
administrator, based on what points in the network are of relevance.

The following figure shows the Multi-domain Ethernet Service OAM:
The service network in the above figure is partitioned into customer, provider,
and operator maintenance levels. The ETH Layer consists of customer service
Ethernet frames that may include both customer VLAN tags and provider.
The following terms are used to describe the entities that are managed:
Maintenance Entity (ME): an entity that requires management.
Maintenance Association (MA) (or Maintenance Entity Group -
MEG): a set of MEs that satisfy the following conditions:
MEs in an MA exist in the same administrative domain and have the
same ME level.
MEs in an MA belong to the same service provider VLAN (S-VLAN).
MA corresponds to a point-to-point or multipoint Ethernet connection. For
a point-to-point Ethernet connection/S-VLAN, an MEG contains a single
ME. For a multipoint Ethernet connection, a MEG contains n*(n-1)/2 MEs,
where n is the number of Ethernet connection end points.
Maintenance Entity Group End Point (MEP): a maintenance functional
entity that is implemented at the ends of a ME. It generates and receives
OAM frames. A ME represents a relationship between two MEPs.
Maintenance Entity Group Intermediate Point (MIP): a maintenance
functional entity that is located at intermediate points along the end-to-end
path where Ethernet frames are bridged to a set of transport links. It reacts
and responds to OAM frames. A MIP does not initiate OAM frames and
takes no action on the transit ETH flows.
Maintenance Point (MP): one of either MEP or MIP.

MD Level: in case MDs are nested, the OAM flow of each MD has to be
clearly identifiable and separable from the OAM flows of the other MDs.
MD Level in the OAM frame distinguishes between the OAM flows of
nested MDs. The MD Level determines the MEPs and MIPs that are
interested in the contents of a CFM PDU and through which the frame
carrying that CFM PDU is allowed to pass.
Eight MD Levels are available to accommodate different network
deployment scenarios. MEG that belongs to specific MD level has a default
MEG Level assignment amongst customer, provider, and operator roles is:
Customer role is assigned three MEG Levels: 7, 6, and 5.
Provider role is assigned two MEG Levels: 4 and 3.
Operator role is assigned three MEG Levels: 2, 1, and 0.
Supported Cards
The cards that can support CFM are the Layer 2 data cards in the MPLS
services:
MPS_6F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
MPS_2G_8F
ME_2G_4F
MPS_4F

Creating CFM MA
This section describes how to create MA in EMS-BGF.
To create CFM MA:

under an MPLS card. Then select the CFM Domain and Level tab under
the Configuration working mode.
2. Click in the toolbar to create MD. In the Create CFM Domain

window, input Domain Name and then select a level in the Domain Level
list. The Domain Name and Domain Level should both be unique. Domain
Level is from 0 to 7, so user can create at most 8 MDs.
Click Apply to save the MD.

3. Close the Create CFM Domain window, user can view the created MDs
from the MD list, as shown below.
User can do the following actions from the MD list:
Click to refresh the MD list, then you can click to overwrite the
MD list in the database with the data from equipment.
To delete a MD, select the MD you want to remove and click .
Click to clear the data both in database and equipment.

4. After creating the MDs, user can create CFM MIPs. In the same MPLS
card, select a LAN or WAN port of UNI/ENNI/INNI, or LAG port in the
left object tree, then select the CFM MIPs tab under Configuration
working mode.
5. Click in the toolbar to create MIPs. In the Create CFM MIP window,
select a domain you have created in the Domain Name list and then input a
MIP ID in the MIP ID area. Select the Enable checkbox if needed.
Click Apply to save the MIP in the CFM MIP list.

6. Close the Create CFM MIP window, user can view the created MIPs from
the MIP list, as shown below.
7. To edit an MIP, select the MIP you want to edit in the list and select
from the toolbar, the Edit CFM MIP window opens. You can enable or
disable the MIP from this window.
8. Repeat Step 1 to Step 7 to create Domains and MIPs for another MPLS
card. Only the MPLS cards with the same Domains and MIPs can create
MA.

9. To create MA, in the NE shelf view window, in the left object tree, select
the Switch object under an MPLS card. Then select the VSI List tab under
the Service working mode.
10. Click in the toolbar, the Create VSI window opens. Select a PB service
from the Service Type list. Set the VSI Parameters as needed and select the
ETY and EoS Ports from the Objects Selections area. Set the parameters
for the ports in Tag Type & C-VIDs area.

11. Select the CFM MA List tab from the Create VSI window.
12. Click from the toolbar. The Create CFM MA window opens.

In the Create CFM MA window, in the MA Parameter area, select a

Domain Name, set the MA Name and enable CCM if needed by selecting
the Enable CCM checkbox. In the MEPs area, select local MEPs and
remote MEPs from the corresponding lists. The selected MEPs will be
saved in the lists below.
Local MEPs: UNI/ENNI ports that have been added in VSI, including
LAGs.
Remote MEPs: UNI/ENNI ports under the MPLS card in the NE,
including LAGs. User can also add external NE as remote MEPs by
inputting MEP ID.
13. In the Local MEP and Remote MEP list, set MEP IDs for the selected
ports, as shown below.

14. Click Save to save the CFM MA.
Click Save&Close to save the MA and close the create window.

15. In the CFM MA List, to edit an MA, select the MA you want to edit and
click from the toolbar. The Edit CFM MA window opens.
To view the detail of an MA, click in the toolbar. The View CFM MA
window opens.
To delete an MA, select the MA you want to delete and click . An MA

with CCM enabled can't be removed. User can disable the CCM in Edit
CFM MA window.

16. In the CFM MA List, click Save to save the VSI . Click Activate to save
and activate the VSI.
17. To upload an MA, select the VSI in the list and click the MA Upload icon
from the toolbar. The CFM MA Upload window opens. Click Upload
to upload all the Tunnel XCs. The status bar shows the consistency status
between the NE and the database.

18. If the NE and the database are inconsistent, select the CFM MA Compare
tab to display the inconsistency results.
CFM Maintenance
Ethernet Service OAM includes the following Management functions:
CCM: Continuity Check OAM messages (CCM) are multicast messages to
each MEP in a MA/MEG. All MEPs in MEG receive CCMs, not respond
to them but maintain records about the status of other MEPs of the MEG.
MIPs are transparent to the CCM messages, as shown in the following
figure.
CCM transmission may be enabled or disabled in a MEG. When enabled,

MEPs periodically exchange Continuity Check OAM messages (CCM).
The Continuity Check Protocol has the following features:
Detect loss of continuity.
Detect incorrect network connections:
Unintended connectivity between two MEG (mis-merge)
Unintended connectivity within the MEG with an unexpected MEP
Detect other defect conditions:
Unexpected MEG Level
Unexpected CCM Period

Loopback: Loopback is a ping-like request/reply protocol. MEPs send

Loopback Messages (LBM) to verify connectivity with another MEP or
MIP for a specific MA. The target MEP or MIP generates a subsequent
Loopback Reply Message (LBR). LBMs / LBRs are used to verify
bidirectional connectivity. They are initiated by operator command.
Link Trace: Link Trace Protocol can be used to trace the path to the target
MEP and for fault isolation. MEPs send multicast Link Trace Message
(LTM) on a particular MEG to identify adjacency relationships with remote
MEPs and MIPs at the same administrative level. The message body of an
LTM includes a destination MAC address of a target MEP that terminates
the link trace.
When a MIP or MEP receives an LTM, it

Generates a unicast Link Trace Reply (LTR) to the initiating MEP and
forwards the LTM to the target MEP destination MAC address if the
network element is aware of the target MEP destination MAC address
in the LTM frame and associates it with a single egress port.
Otherwise the LTM frame is relayed unchanged to all egress ports
associated with the MEG, except for the one it was received at.
This section describes how to perform CFM maintenance functions from the
CFM MA list.

To perform CFM maintenance in CFM MA list:

under an MPLS card. Then select the CFM MA List tab under the
2. To define CCM, select the MA from the list and click from the toolbar.
The Define CCM window opens.
Modify the settings in CCM Definitions area. Click Apply & Close to
save the changes.

3. To perform CFM Loopback maintenance, select an MA from the list and

click in the toolbar. The CFM Loopback Maintenance Operations
window opens. In the Operation Definitions area, select Loopback as the
operation type you want to perform, then select Local MEP and Destination
MIP or MEP from the corresponding list. To select an external NE as
destination, input the MAC Address in the Select Destination area and
click the button .
4. Click Apply. User can view the results from the Operation Results area.

5. To perform CFM LinkTrace maintenance, select an MA from the list and

click in the toolbar. The CFM Loopback Maintenance Operations
window opens. In the Operation Definitions area, select LinkTrace as the
operation type you want to perform, then select Local MEP and Destination
MIP or MEP from the corresponding list. To select an external NE as
destination, input the MAC Address in the Select Destination area and
click the button .
6. Click Start to start the LinkTrace maintenance and user can view the result
in the Operation Results area. Click Stop the LinkTrace progress.

Configuring ACL Profile

Access Control List (ACL) is used for Deny of Service (DoS) prevention.
The ACL profiles can be applied to the UNI or E-NNI ports in MPLS cards.
To configure the ACL profile:

1. In a BG-20/BG-30 NE shelf view window, in the left object tree, select the
Switch object under an MPLS card. Then select the ACL Profile tab under
the Configuration working mode.

2. Click in the toolbar. The Create/Edit Profile window opens.
3. Enter the Profile ID, Profile Name in the ID and Name area, and select
the ACL Rule by selecting the Permit or Deny radio button. Then enter a
MAC Address and click Add.
4. Click to retrieve the information to the list to view.
5. Click to edit a selected ACL profile in the list.

6. Click to delete a selected ACL profile.

Port Mirror
Use the following procedure to configure the port mirroring.
To configure the port mirror:

1. In the NE shelf view window, select the Switch module in the left object
tree. Then select the Port Mirror tab under the Maintenance working
mode.

2. Click in the toolbar to define port mirroring. Select the ports from the
corresponding drop down list and click Create to create the port mirroring.
3. Click to refresh the port mirroring list.
4. To remove a port mirrroring, select the port mirroring in the list and click
.

Configuring Switch OAM

This section describes how to configure switch OAM settings.
To configure switch OAM settings:

tree. Then select the OAM Setting tab under the Maintenance working
mode.
2. Set the CV Interval and FDI Interval attributes from the corresponding
drop down list.
4. To configure the OAM settings as the default settings, click to display

the default settings to view and then click Apply to save.
5. Click to refresh the list.

Fast ReRoute (FRR)

The MPLS supports a protection mechanism called Fast Reroute (FRR). This
protects a tunnel against a failure of a link or node along its path.
With FRR, a backup LSP called a bypass tunnel is pre-established to go around
a network link or node failure to a downstream MPS, where its path merges
with the path of the protected tunnel. The switching to a bypass tunnel involves
pushing a third MPLS tag, called an FRR label, into the packet. This label
remains until the bypass tunnel remerges with the path of the protected tunnel,
where it is popped out of the packet. The primary advantage of FRR is the
speed of repair: thanks to the pre-establishment of the bypass tunnels and the
fast physical-layer-based failure detection, FRR can provide sub-50ms
switching time; this value is comparable to SDH/SONET protection
mechanisms.
With FRR link protection, the MPS upstream from the failure reroutes the
protected tunnel traffic to a bypass tunnel that merges with the original tunnel
at next hop (NH) MPS. With FRR node protection, the MPS upstream from the
failure reroutes the protected tunnel traffic to a bypass tunnel that merges with
the original tunnel at next-next-hop (NNH) MPS. In addition, FRR node
protection provides protection against link failure. By default, if you require
FRR node protection, attempts are made to provide node protection for every
MPS along the tunnel path. If this is not possible (as is always the case for the
destination PE), attempts are made to provide link protection. Thus, a tunnel
may have node protection at some hops and link protection at other hops.

To perform an MPLS port protection switch:

1. In the NE shelf view window, in the left object tree, select a MoT port of an
MPLS card. Then select the Maintenance working mode.
2. Select the MPLS port protection switch by selecting the corresponding

radio button.


8
Managing Network in Stand
Alone Mode
In this chapter:
Overview ......................................................................................................... 8-1
Workflow ......................................................................................................... 8-1
Managing the Topology................................................................................... 8-2
Managing Trails............................................................................................. 8-11
Managing Data Service ................................................................................. 8-28
Extended DCC ............................................................................................... 8-43
MS DCC Swap .............................................................................................. 8-49
Configuring DCC Over 2M ........................................................................... 8-49
Overview
The EMS-BGF supports the Stand Alone working mode, where the EMS-BGF
manages the BGF elements network. The EMS-BGF works as an SNMS under
this mode, and provides the end-2-end management.
Workflow
The following network management procedures can be performed in
standalone mode by the EMS-BGF:
Managing the topology (on page 8-2)
Managing trails (on page 8-11)
Managing data service (on page 8-28)

Managing Network in Stand Alone EMS-BGF User Manual
Mode
Managing the Topology

This section describes topology management procedures, including the
management of subnets and fiber connections.
EoS ASCII-files
Card Items Current PM EMS History VC4 MS EoS FE-LAN GE-LAN

Export Export
Rx Octets Y Y X
Rx Pkts Y N
Tx Octets Y Y X
Tx Pkts Y N
Rx Error Pkts Y Y X
Rx GFP EXI Field N N

Mismatch
Rx Drop Pkts N N
Rx FCS Error Pkts N N
Rx GFP Header Error N N

Pkts
ETY Port ASCII-files

Items Current PM EMS History VC4 MS EoS FE-LAN GE-LAN
Export Export
Rx Octets Y N
MPS_6F Rx Pkts Y N
Rx Broadcast Pkts Y Y X X
Rx Multicast Pkts Y Y X X
Tx Octets Y N
Tx Pkts Y N
Rx Error Pkts Y Y X X
Rx Pkts 64 Y N
Rx Pkts 65-127 Y N
Rx Pkts 128-255 Y N
Rx Pkts 256-511 Y N
Rx Pkts 512-1023 Y N
Rx Pkts >= 1024 Y N
Rx Pause Pkts Y N
Rx CRC Align Error Y Y X X
Rx undersize Pkts Y N
Rx Oversize Pkts Y N

EMS-BGF User Manual Managing Network in Stand Alone
Mode
EoS ASCII-files
Card Items Current PM EMS History VC4 MS EoS FE-LAN GE-LAN

Export Export
Rx Fragments N N
Rx JabberPkts N N
Collision Errors Y Y X X
NE Uploading
The NE icon color in the topology view changes to blue to indicate when NE
data is being uploaded from the NE. This occurs:
When making changes using the LCT-BGF
When performing a no recovery reset
After creating an NE if user select "Create and Upload" in the Create
window
When restore NE DB
When uploading has been completed, the NE icon color returns to its normal
color scheme, in which green indicates no alarm and red indicates a critical
alarm.
Group
Group creation enables you to divide the network into different areas. You can
define NEs belonging to the same area in the same subnet. One NE can only
belong to one group. The group can be either collapsed or expanded. In
addition, the alarm severity for the group is the highest alarm severity of the
NEs it contains.
The EMS-BGF is designed to manage up to 3000 NEs. When there are
numerous NEs, the display speed of the entire network topology may slow
down. Therefore, in this case, it is recommended to manage NEs on a group
basis. The number of NEs in a group should not exceed 100.
All NE operations can be performed in the group topology. To view the entire
network, you should collapse all groups to simplify the topology display and
increase the topology refresh speed.

Mode
To create a group:
1. In the EMS-BGF main topology view window, select Configuration >
Create > Group in the main menu. The Create Group window opens.
2. Enter the Group Name and Comments.

3. Select the NE to be added to this group, and click Apply to complete group
creation.

Mode
4. After creating the group, you can collapse it using the right-click menu.
When doing so, the alarm severity of the group is the highest alarm severity
of the NEs that are included.
The connection between NEs is through groups. For the cable, you specify
such attributes as the direction, diameter, and alarm color. The connections
between the subnet and NE, between groups, between the EMS-BGF and
the NE, and between the EMS-BGF and a group have no attributes.
5. Double-click the collapsed group icon to access the group. You can also
modify the group attributes by selecting a group and then selecting
Configuration > Modify > Group.
Fiber Connections
Fiber connection creation connects NEs in the topology view according to the
actual fiber connection relationship between them. Fiber connection refers to
the connection between aggregate optical interfaces or tributary optical
interfaces in the actual equipment. The EMS-BGF topology view reflects the
correct fiber connection of the NE equipment, which makes fiber maintenance
and management more convenient. Moreover, it also ensures that the program
can correctly calculate the automatic route and orderwire telephone route.
The NE connection operation is only valid for the EMS-BGF data structure,
and has no direct influence on the equipment. The NE connection relationship
influences the orderwire telephone route and automatic routing algorithm of the
service. Therefore, be sure to verify that fibers are connected correctly before
proceeding.

Mode
Only optical interface cards at the same rate can be connected with one another.
Card assignment must be completed before fiber connection creation can be
performed.
Creating Fiber Connections

This section describes how to create fiber connections.
To create fiber connections:

1. In the EMS-BGF main topology view, click the Create TopoLink shortcut
icon from the toolbar or select Configuration > Create > Topology
Link in the main menu. The Create TopoLink window opens.
2. Select the Create Topology Link radio button at the top of the window.
3. Select the corresponding optical interface according to the actual fiber
connection.

Mode
4. Click Connect. The corresponding optical interface displays grey, which

indicates that the connection has been set in both directions.
5. To create a topolink and automatically create a server trail, select the

Create Topology Link & Automatically Create Server Trail radio
button.
NOTE: The NE connection influences the route configuration

of the orderwire telephone and the automatic routing
algorithm of the service. Therefore, pay special attention to
verify the correctness of the connection.

Mode
Modifying Fiber Connection Attributes

You can modify several of the fiber connection attributes, as well as view the
alarm list for the fiber connection.
To modify fiber connection attributes:

1. Select a fiber connection in the topology view and right-click on it. From
the pop up menu, click View Topology Link Details. The TopoLink
Attributes window opens.
2. Modify the fiber connection attributes in this window.


Mode
Managing Fiber Connections

The Topology Link List window provides functions for the centralized
management of the fiber connection, including fiber creation, deletion, and
viewing of attributes. If too many fiber connections have been created, they can
be filtered by selecting the type, rate and NE to query the fiber connection
between them.
To access the Topology Link List window:

In the main menu, select Configuration > View > Topology Link List, or
click the View Topology Link List shortcut icon from the toolbar.
The Topology Link List window opens.

Mode
Performing TopoLink Discovery

You can use the Topolink discovery feature to compare the difference between
NE equipment and the EMS-BGF database.
To perform a TopoLink discovery:

1. In the EMS-BGF main window, select Configuration > Discovery >
Topology Link Discovery in the main menu. The TopoLink Auto
Discovery window opens.
2. Select the TopoLink in NE not in DB tab to view the topolinks that are in
the NE equipment but are not in the database. To create a topolink in
database, select the topolink in the list and click the Create Topolink
button in the toolbar.
3. In the TopoLink in DB not in NE tab, user can view the topolinks that exit
in the database but not in the equipment. To delete a topolink from the
database, select the topolink in the list and click the Delete button in the
toolbar.
4. In the TopoLink Both in NE and DB tab, user can view the topolinks that
exist both in the equipment and in the database. Select a topolink in the list
and click the Delete button in the toolbar to delete the topolink from the
database.

Mode
Managing Trails
Overview
The EMS-BGF server trail and client trail management provides end-to-end
service configuration and management. The following features are supported:
Trail Consistency
Ability to manage service in terms of client trails, thus enabling users to be
free of heavy XC.
Automatic circuit configuration with possible manual intervention, which
enables any configured client trail to be adapted to various complex
network topology and protection structures.
A detailed client trail and server trail information list that makes
information clear and accessible at a glance.
Graphical client/server trail and corresponding protection structure that
make the orientation of working and protection client trails clear at a
glance.
Fault and performance management based on a server/client trail,
facilitating the quick location of fault causes.
A powerful, flexible server/client trail filtering function to quickly locate
the trail you want to view.
Workflow
The following prerequisites apply for trail configuration:
The basic attributes of the NE have been configured.
The logic slot has been configured.
For equipment with bus reallocation, it is necessary to set the maximum
traffic of the card.
The following trail configuration procedures are available in the EMS-BGF:
Create a server trail
Activate a server trail
Create a service trail
Activate a service trail

Mode
Using Trail Creation Window

This section describes how to use the trail creation window.
To access the trail creation window:

1. In the EMS-BGF topology view window, select Services > Create Trail in
the main menu. The Create Trail window opens.
2. Use this window to create EMS-BGF trails, including server trails and
service trails.

Mode
Creating a Server Trail

The server trail is responsible for the planning of the network resources. After
configuring the NE and connecting the fiber, you can create the server trail to
plan the use of network VC-4 resources. The system completes a server trail
and the VC-4 cross connections in it, based on the optical fiber connection.
Note that before it is set as the start point and end point of the server trail, the
optical VC-4 port cannot be used by the client trail.
To create a server trail:

2. Set the trail type as server by selecting Server from the Trail Type
dropdown list.
3. Select the values of Customer, Rate, Trail Template, and Number of
Trails from the corresponding field.
4. In the Trail Details area, you can also set the Trail Name or Trail
Description, if needed.

Mode
5. From the right topology view, select a start point NE by right-clicking on it

and selecting Select Start Point from the pop up menu. The Select NE
Timeslot window opens.
Select the needed timeslot in the lists and click Apply.

Or you can select Auto Select Start Point from the right-click menu. The
start point NE has an S label at its top.
6. Select an end point NE by right-clicking on it and selecting Select End
Point from the pop up menu. Or you can select Auto Select End Point
from the right-click menu. The end point NE has an E label at its top.
7. Set the trail constraint. In automatic server trail creation, select another NE
and choose from the following constraints:
Set as Protection NE: set the NE as a protection NE in the trail.
Set as Exclude NE: exclude the selected NE.
Set as Include NE: include the NE.

Mode
Setting a server constraint is optional. If a trail is not selected, the system

preferentially selects the shortest trail with available timeslots.
8. Click Complete to generate a trail. If the system can find a trail and
available timeslots, the operating path is displayed in pink in the trail
topology map.
9. Click Save to save the server trail generated in the system.
10. Click Activate to activate the server trails.
NOTE: In creating a server trail, not all topology structures

can be used as a server trail for SNCP. For example, a simple
ring network cannot create the server trail of an SNCP server
trail automatically. An SNCP server trail can be implemented
in a ring network only when one ring has two links and its
start and end points are located in respective links.
Creating a Service Trail

A service trail is a transmission task of the optical transmission network.
Externally, it appears as the add/drop of electrical signals in the service
tributary. Within the NE, it is a series of cross connections. Service trails
enable you to view every end-to-end service of the optical transmission
network from the perspective of the network, thus simplifying the management
of each end-to-end service.
Creating a service trail automatically configures an end-to-end service. When
you select a start point timeslot, end point timeslot, and protection mode, the
system automatically calculates one optimized service trail conforming to the
cross-connection and protection rules and the XCs of this service trail.

Mode
This trail creation method also provides a user intervention mechanism. Before
calculating a trail, you can specify any NEs that cannot pass, a server trail, and
the timeslots in this server trail. The system uses this information to calculate
the service trail services.
To create a service trail:

2. Set the trail type as service by selecting Service from the Trail Type
dropdown list.

Mode

and selecting Select Start Point from the pop up menu. The Select NE
Timeslot window opens.
Select the needed timeslot in the lists and Click Apply.

Or you can select Auto Select Start Point from the right-click menu. The
start point NE has an S label at its top.
Point from the pop up menu. Or you can select Auto Select End Point
from the right-click menu. The end point NE has an E label at its top.
7. Set the trail constraint. In automatic service trail creation, select another NE
and choose from the following constraints:
Set as Protection NE: set the NE as a protection NE in the trail.
Set as Exclude NE: exclude the selected NE.
Set as Include NE: include the NE.
Setting a service constraint is optional. If a trail is not selected, the system
preferentially selects the shortest trail with available timeslots.

Mode
topology map.
9. Click Save to save the service trail generated in the system.

10. Click Activate to send a created service trail to the NE equipment, in which
the service information for this service trail is established.

Mode
Setting Trail Protection

This section describes how to set trail protection.
To set trail protection:

2. Set the trail type as server by selecting Server or Service from the Trail
Type dropdown list.
and selecting Select Start Point from the pop up menu. Or select Auto
Select Start Point from the right-click menu. The start point NE has an S
label at its top.
Point from the pop up menu. Or select Auto Select End Point from the
right-click menu. The end point NE has an E label at its top.

Mode
7. Select another NE and right-click on it. Select Set as Protection NE from

the pop up menu to set the NE as a protection NE in the trail. The
protection NE has a P label at its top.
topology map.
9. Click Save to save the server trail generated in the system.

10. Click Activate to send a created trail to the NE equipment.

Mode
Managing Trails
In the EMS-BGF trail list, you can perform the following trail management
actions:
Activate trails
Deactivate trails
Edit a trail
View details of a trail
Upload trails
Delete trails
Export trails
To manage trails:
1. In the EMS-BGF main window, select Services > Open Trail List in the
main menu, or select the Trail List shortcut icon in the toolbar. The
Trail List window opens.
2. To activate a trail, select the trails in the list that you want to activate and
click the Activate Trail button in the toolbar.
To deactivate a trail, select the trails in the list that you want to deactivate
and click the Deactivate Trail button in the toolbar.

Mode
3. To edit a trail, select the trail you want to edit and click the Edit Trail
button in the toolbar. The Edit Trail window opens.
Modify the Customer and Trail Template for the trail as required and
click Complete to save the changes.

Mode
4. To view details of a trail, select the trail in the list and click the Trail Info
button in the toolbar. The Trail Detail window opens.
From the window, you can view the details, current alarms and
performance on this trail.
5. To upload trails, select the Upload button in the toolbar.

6. To delete a trail, select the trail you want to delete in the list and click in
the toolbar.

Mode
7. To export trails, select the trails you want to export and click in the
toolbar. The Save window opens.
Select a folder to save the file, enter the name of the file, and click Save.

Mode
Exporting and Importing Trail Files

You can export a trail as an XML file and import trail XML files to the EMS-
BGF.
Exporting Trails
This section describes how to export trails in the EMS-BGF.
To export trails:
1. In the EMS-BGF main window, select Services > Export > Export Trails
in the main menu. The Export Trail window opens.
2. Select the trails you want to export. Click in the toolbar to select all the
trails in the list.

Mode
Select a folder to save the file, enter the file name, and click Save.
Importing Trail XML Files

This section describes how to import trail XML files to the EMS-BGF.
To import trails:
1. In the EMS-BGF main window, select Services >Import > Import Trails
in the main menu. The Import Trail window opens.

Mode
4. Select the trail in the list that you want import and click the Import button
in the toolbar.

Mode
Managing Data Service

Data Service Overview
This section describes the data services that can be configured in the EMS-
BGF.
Workflow
You can configure the following data services in the EMS-BGF:
For the EOP cards, configure the EOP service.
For the data cards, configure two Ethernet data services: the PB service and
the MPLS-PE service.
Configure the Overhead and DCC for the NEs.
Configure the OSPF.

Mode
Using Data Service Creation Window

You can use the Create VSI window to create both a PB service and an MPLS
service.
To access the Create VSI window:

1. In the NE shelf view window, in the left object tree, select the Switch
object under a Layer 2 data card. Then select the VSI List tab under the

Mode
2. Select the Create VSI button in the toolbar. The Create VSI window
opens.
3. Use this window to create data service for the cards in the EMS-BGF.
Configuring and Managing Data Service

The following cards only support PB data service in the EMS-BGF:
MESW_6F
ESW_2G_8F
ESW_2G_8F_E
The following cards can support both PB and MPLS services:
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
MPS_6F
MPS_4F
MPS_2G_8F
ME_2G_4F

Mode
To configure PB service, follow this procedure:

1. Define the Configuration Mode as PB.
bandwidth.
3. Create policer profiles.
4. Create PB VSI services in the VSI List window.
To configure MPLS service, follow this procedure:
1. Define the Configuration Mode as MPLS PE.
2. Assign PE ID and MPLS Network ID, each MPS requires a unique PE
ID.
3. Configure ports as MoT port type. MPS support hybrid of PB ports with
MPLS ports. User should set the port type as MoT for P2P tunnel.
bandwidth.
5. Create required tunnels.
6. Select ports and remote PEs for the services.
7. Set other attributes for the services.
Managing DCC and Overhead

This section describes the DCC and overhead configurations in the EMS-BGF.
Overhead and DCC Overview

The SDH network management function of the EMS-BGF needs support from
the ECC stack. As a managed object itself, the ECC stack also needs to be
manageable. ECC stack management information enables you to receive
prewarning signals in sufficient time before an NE is disconnected due to DCC
hardware channel performance deterioration, and to locate the problem for a
specific NE after disconnection. It also provides some necessary network test
measures. Every NE must be set with some communication parameters, such as
gateway attributes, the Ethernet ports IP address, the DCC ports IP address,
and the EMS-BGF computers IP address.
A gateway NE is an NE directly connected with the EMS-BGF. In terms of the
physical channel, the information exchange between the gateway NE and the
EMS-BGF does not pass the DCC channel and needs no forwarding via any
other NE. A nongateway NE is an NE that communicates with the EMS-BGF
via a gateway NE. Generally, it is connected with the gateway via an optical
channel for data transmission over the DCC channel.

Mode
DCC transparent transmission means that the DCC code stream passes the NE
transparently, meaning it is transmitted transparently from the STM-N Rx end
of the NE to another STM-N Tx end. In this context, transparent refers to
protocol independence and the physical connection rate is purely N x 64 Kbps.
In contrast, termination means local generation of DCC code streams at the
STM-N Tx end.
There are two possibilities for termination:
Access permitted: accesses the DCC code stream to the protocol processor
for processing
Access prohibited: does not process the DCC code stream at all
Configuring Communication Parameters

This section describes how to configure communication parameters.
To configure communication parameters:

1. In the NE shelf view window, select the NE in the left object tree, then
select Configuration > NE Connection Settings in the shelf menu. The
NE Communication window opens.

Mode
2. Use this window to set gateway attributes, the Ethernet port IP address, and
the MCUE Ethernet port IP. If Gateway is selected in the Connection
Model field, both local and remote NEs can be managed through the LCT-
BGF or the EMS-BGF.
Managing DCC and Overhead for BG-40

The DCC setting enables you to perform the following configuration for the
BG-40 NE:
VC12 to SM10
V3.5 Work Mode
DCC Swap Attribute
DCC Access

Mode
To manage DCC settings for BG-40:

1. In a BG-40 NE shelf view window, select Control and Physical Object >
MXC4X in the left object tree. Then select the DCC Settings tab under the
2. In the VC12 to SM10 area, set the attributes as below:

To set a VC-12-12 link to the SM10, you must check whether the
MXC4X V.35 is in Traffic Path mode. If it is, such a link is prohibited.
To set a VC-12-10 or VC-12-11 link, first check whether it has been
configured with any overhead. If it has, such a link is prohibited.
3. In the V3.5 Work Mode area, the following conditions apply when
configuring the V.35 interface:
VC-12-12 can only work in Traffic Path mode when it is not
connected to the SM10.
If V.35 has been configured with DCC or DCC access control, its
working mode cannot be modified and can only be DCC Mode.
Traffic can be set only when the working mode is Traffic Path.
The DCC Type can be set as RDCC or MDCC only when DCC Mode
is selected..

Mode
4. In the DCC Swap Attribute area, the optical port SWAP setting only
restricts its MS property. After a SWAP occurs, the optical ports MS can
only be cross connected with an RS (an alien RS or its own RS). In
addition, there is no restriction to the RS that supports transparent
transmission. Operation objects include the optical ports under all subcards
of the selected NE.
5. In the DCC Access area, two DCC access control modes are supported: six
RDCCs (default) and three RDCCs plus one MDCC.
The following conditions apply when configuring DCC access:

The accessed RDCC or MDCC can be selected from six SOHs, two
EOCs, and V.35.
V.35 can be selected for DCC access only when it works in Extended
DCC mode.
The DCC type (RDCC or MDCC) depends on the V.35 mode setting.
No transparently transmitted RDCC or MDCC can be accessed.
MDCC access used in SWAP is prohibited, but RDCC access of the
SWAP incoming MDCC is allowed.
Details about creating DCC XC, refer to Creating DCC XC (on page 10-10).

Mode
To perform DCC Overhead configuration for BG-40:

1. In the BG-40 NE shelf view window, select the NE in the left object tree.
Then select the OH XC List tab under the Services working mode.
2. Click in the toolbar. The Create OH XC window opens, as shown in


Mode
3. From this window, the following conditions apply for DCC overhead
configuration:
Only the following DS-0 timeslots can be cross connected: F1, U1,
V.24, and V.11 (when V.35 works in the V.11 mode).
VC-12-10 and VC-12-11 cannot be used for overhead configuration
when they are connected with the SM10.
V.11 can be used for overhead configuration only when V.35 uses V.11
Overhead Interface mode.
No cross connection is allowed between two V.24 channels and one
V.11 channel. Cross connection is permitted in all other cases.
The details about creating OH XC, refer to Creating OH XC (on page 10-8).
Managing DCC and Overhead for the BG-

20/BG-30/BG-64
DCC and overhead configuration for the BG-20, BG-30 and BG-64 use the
same concepts as a cross-connect. As such, you create cross connections
between RS-DCC/MS-DCC/SWAP MS-DCC/Clear Channel and HDLC.
The following figure shows the DCC cross-connect model for the BG-20 and
BG-30.

Mode
The following describes the types of DCC cross connections as shown in

figure:
1 R-DCC termination: connects between an STM-N R-DCC and a QMC R-
DCC
2 M-DCC termination: connects between an STM-N M-DCC and a QMC
M-DCC
3 R-DCC transparent: connects between an R-DCC of one STM-N and an
R-DCC of another STM-N
4 M-DCC transparent: connects between an M-DCC of one STM-N and an
M-DCC of another STM-N
5 Channelized MS_DCC termination (Terminal Mode): connects between
an STM-N MDCC_3B and a QMC DCC-R
6 Channelized MS_DCC transparent (Through Mode): connects between
an STM-N R-DCC (X) and another STM-N M-DCC_3B (Y)
7 Framed Clear Channel termination (RDCC): connects between a framed
clear channel RDCC and a QMC RDCC
8 Unframed Clear Channel termination: the entire 2 M is an HDLC that
connects to SCC4
9 Framed Clear Channel termination (MDCC): connects between a framed
clear channel MDCC and a QMC MDCC
10 COM-DCCx-1termination: general RDCC
The following cross-connect limitations apply:
A DCC cross connection is bidirectional.
Unidirectional and broadcast are not supported. A loopback requires JIG
support.
A DCC cross connection is between the source/sink with the same byte:
RDCC to RDCC
MDCC to MDCC
MDCC_3B to RDCC
Framed clear channel RDCC to QMC-RDCC
The EMS-BGF and LCT-BGF do not support connections between COM-
DCC. JIG does support such connections.
COM-DCCx can be terminated with any DCC, including RDCC, MDCC,
and unframed E1 clear channel.
An unframed clear channel can only connect with COM-DCCx.
When a clear channel is configured with a DCC cross connection, the clear
channels properties cannot be changed.

Mode
To manage DCC XC for BG-20/BG-30/BG-64:

1. In a BG-20/BG-30/BG-64 NE shelf view window, select the NE in the left
object tree. Then select the DCC XC List tab under the Services working
mode.
2. Click in the toolbar. The DCC XC window opens, as shown in the

following figure.

Mode
3. Select the DCC XC source timeslot in the Start Timeslot tree and the sink
timeslot in the End Timeslot tree.
4. Click Save to add the DCC XC list.
5. Click Activate to activate the DCC XC.
To manage Overhead XC for BG-20/BG-30/BG-64:

1. In a BG-20/BG-30/BG-64 NE shelf view window, select the NE in the left
object tree. Then select the OH XC List tab under the Services working
mode.

Mode
2. Click in the toolbar. The OH XC window opens, as shown in the

following figure.
3. Select the OH XC source timeslot in the Start Timeslot tree and the sink
4. Click Save to add the OH XC list.
5. Click Activate to activate the OH XC.

Mode
Managing DCC for the BG-20C

User can only manage DCC XC for BG-20C NE.
To manage DCC XC for BG-20C:

1. In a BG-20C NE shelf view window, select the NE in the left object tree.
Then select the DCC XC List tab under the Services working mode.

Mode
2. Click in the toolbar. The DCC XC window opens, as shown in the

following figure.
3. Select the DCC XC source timeslot in the Start Timeslot tree and the sink
4. Click Save to add the DCC XC list.
5. Click Activate to activate the DCC XC.
Extended DCC
In order to support in-band management for remote EOP sites, BG-20/BG-30 is
capable of supporting extended DCC channels over 10Base-T management
port.
Usually management port acts as an untagged Ethernet network interface with
a configurable IP. In order to support specific application, the management port
can be channelized based on VLAN ID so that it is able to support several
tagged interfaces besides untagged interface. For BG-20/BG-30, the
management port can support 16 tagged interfaces based on VLAN ID. These
tagged interfaces are called extended DCC channels.

Mode
Two operation modes (position) are defined for extended DCC Master and
slave. A master NE can connect several slave NEs through extended DCC
channels. Master to master and slave to slave connection is not allowed
when configuring extended DCC. For master mode, it is able to support up to
16 extended DCC channels with different VLAN ID, and IP address of all
remote slaves should be designated; for slave mode, it must be connected to a
master with a designated remote master IP, actually it can have only one
tagged interface.
The feature of extended DCC of management port can be enabled or disabled,
default is disabled.
Extended DCC application scenario:
EOP cards can only forward packets based on VLAN-ID, it does not support
MAC learning and L2 switching functionality (forwarding packets according to
MAC address), so the aggregation of management channels from several
remote sites can only be done based on VLAN-ID. So extended DCC channels
are required mainly for EOP applications, see below the extended DCC
application topology.
In the figure shown above, there is one aggregation site BG-20 and several
remote sites (BG-20 NEs). All management ports of remote NEs are connected
to management port of aggregation NE through an EoP network, each remote
site is assigned with a unique VLAN-ID for management channel in order to
separate the traffic and management flow. In this case, all management ports of
aggregation and remote sites are tagged and "extended DCC" enabled.

Mode
To configure Extended DCC:

1. In BG-20/BG-30 NE shelf view window, select the NE in the left object
tree and then select Service > Extended DCC from the menu. The
Extended DCC window opens.
2. Set the parameters in the window for Extended DCC:

The feature of extended DCC of management port can be Enable or
Disable, default is Disable.
Enable: support extended DCC channels.
Disable: untagged only, cannot support extended DCC channels.
NOTE: To enabled extended DCC, NE connection mode

should be "gateway" or "Ethernet only"; "DCC only" NE does
not support extended DCC.

Mode
When extended DCC is set Enable for management port, the Extended
DCC IP should be specified. This IP cannot be in the same subnet of
untagged interface and DCC/NE IP. Additionally, position attribute of
Master or Slave should also be specified:
Master: for aggregation site. It supports multiple extended DCC
channels and an extended DCC channel list should be defined
consequentially.
Slave: for remote site. It supports only one extended DCC channel and
user don't need to define the extended DCC channel explicitly, a
pertaining master IP should be specified.
NOTE: For the case that one aggregation/master NE connects

several remote/slave NEs through extended DCC, extended
DCC IPs of all aggregation and remote NEs MUST be in the
same subnet.
While the GW/Ethernet IP of master NE, Ethernet IP of slave
NEs and extended DCC IP should not be in the same subnet,
which means, three subnets should be allocated for the
extended DCC application.

Mode
3. If extended DCC is enabled with master mode, besides the untagged logical
interface, up to 16 logical interfaces(extended DCC channels) can be
created in the Ethernet port of management.

Mode
4. Click from the toolbar. The Create MCF Logical Interface window
opens.
Each extended DCC channel has the following attributes:

User Label: user label of extended DCC channel.
CVLAN ID (1~4094): is unique within NE.
Remote IP: is unique within NE.
5. To edit an extended DCC channel, select the extended DCC channel from
the Extended DCC Channel List and click in the toolbar.
6. To delete an extended DCC channel, select the extended DCC channel
from the Extended DCC Channel List and click in the toolbar.
7. For slave NE, remote Master IP should be specified:
Remote Master IP: the extended DCC IP of corresponding
master/aggregation site.
NOTE: The port on MEOP_4H or L2 card should be set to

"10M half-duplex" if it is connected to BG-20/30
management port or a HUB.

Mode
MS DCC Swap
This section describes how to set MS DCC Swap.
To set MS DCC Swap:

1. In the BG-20/BG-30/BG-64 NE shelf view window, select the MS object
in the left object tree and then select the Configuration working mode.
2. In the MS DCC Swap tab window, user can set Clear Channel as
Enabled or Disabled from the dropdown list.
Configuring DCC Over 2M

User can use the following steps to configure DCC over 2M:
1. Configure EME1_21 card VC12-21 Ch as Framed Clear Channel--
Standard.
2. Create DCC XC between VC12-21 RS or MS and COM card in BG-20.
3. Create VC12 XC between VC12-21 and any other VC12 on EME1_21 card
(for example VC12-20).
4. Do the same configuration in other BG-20.
5. Connect EME1_21 card physical port 20 with 2M cable between BG-20
NEs.

Mode

9
Managing Network in
Integrated Mode
In this chapter:
Overview ......................................................................................................... 9-1
Workflow ......................................................................................................... 9-1
Managing SDH Service in Integrated Mode ................................................... 9-2
Managing Tunnel Service in Integrated Mode ................................................ 9-2
Managing Ethernet Data Service in Integrated Mode ..................................... 9-3
Overview
The EMS-BGF supports the Integrated working mode, where the EMS-BGF is
managed by the NMS. The EMS-BGF does not provide the end-to-end
management under this mode.
NOTE: The users who are authorized a license have the

permission to use the integrated mode.
Workflow
You can manage the network in the following integrated modes:
Managing SDH service in integrated mode (on page 9-2)
Managing tunnel service in integrated mode (on page 9-2)
Managing Ethernet data service in integrated mode (on page 9-3)

Managing Network in Integrated EMS-BGF User Manual
Mode
Managing SDH Service in

Integrated Mode
To create SDH service in integrated mode, you should do as follows:
For BG-40 NE, configure the traffic settings.
In the EMS-BGF you can create:
VC4-4c/VC4/VC3/VC12 trail
EOS-VC12-X/EOS-VC3-X/EOS-VC4-X
MOT-VC12-X/MOT-VC3-X/MOT-VC4-X
To create EOS-VC12-X/EOS-VC3-X/EOS-VC4-X trail:
In the EMS-BGF, configure the bandwidth of the EOS. Then it can be
select when creating EOS trail on NMS.
To create the EOS trail on NMS, refer to the User Manual of NMS.
Managing Tunnel Service in

Integrated Mode
The following cards support MPLS-PE service in the EMS-BGF:
MPS_6F
MPS_4F
MPS_2G_8F
ME_2G_4F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
To create a tunnel service in integrated mode, you should do as follows:

Assign PE ID and MPLS Network ID, each MPS requires a unique PE ID.
Configure ports as MoT port type and configure the VCG bandwidth for
the MoT ports.
Create MoT trail on NMS.
Create End-to-End Tunnel on NMS.
For details about creating MoT trails and End-to-End Tunnels on the NMS,
refer to the NMS User Manual.

EMS-BGF User Manual Managing Network in Integrated
Mode
Managing Ethernet Data Service

in Integrated Mode
Following lists the data cards that supports the Ethernet data service:
There are data cards support PB Ethernet data service in the EMS-BGF:
MESW_6F
ME_2G_8F
MPS_6F
MPS_2G_8F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
ESW_2G_8F
ESW_2G_8F_E
The following cards support the both PB and MPLS service:
MPS_6F
MPS_4F
MPS_2G_8F
ME_2G_4F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
To manage Ethernet data service in integrated mode:
To create PB Ethernet data service:
Configure the ETY ports on EMS-BGF as UNI, E-NNI or I-NNI.
Create EOS trails on NMS.
To create a PB MPtMP service on the NMS, refer to the NMS User
Manual.

Managing Network in Integrated EMS-BGF User Manual
Mode
To create MPLS Ethernet data service:

Configure the ETY ports on EMS-BGF as UNI, E-NNI or I-NNI.
Create MoT trails on NMS.
Create End-to End Tunnels on NMS.
To create an MPtMP MPLS Ethernet service, refer to the NMS User
Manual.

10
Managing Cross Connections
In this chapter:
Overview ....................................................................................................... 10-1
Workflow ....................................................................................................... 10-1
Creating XC ................................................................................................... 10-2
Managing the XC List ................................................................................. 10-17
Configuring SNCP Attributes ...................................................................... 10-24
Exporting and Importing XC Files .............................................................. 10-25
Overview
One of the key benefits of SDH technologies is the ability to direct the flow of
traffic dynamically, using management software rather than hardware
switching. A cross-connection set (XC set, or XCS) is a set of cross-
connections with the same ID that form a trail along the network.
The cross-connection (XC) subsystem enables you to cross-connect traffic on
equipment. NEs feature an advanced Add/Drop Multiplexer (ADM)
architecture.
Workflow
This chapter describes the procedure for setting up cross-connects. It contains
the following sections:
Creating XC (on page 10-2)
Managing the XC List (on page 10-17)
Export and import XC files (on page 10-25)

Managing Cross Connections EMS-BGF User Manual
Creating XC
This section describes how to create XCs.
Creating Server XC
This section describes how to create a server XC.
To create a server XC:

1. In the NE shelf view window, select the NE in the left object tree. Then
select the XC List tab under the Services working mode.

EMS-BGF User Manual Managing Cross Connections
2. Select the Create XC button in the toolbar. The Create XC window

opens.
3. Set the XC type as server by selecting Server from the XC Type dropdown
list.
4. Select the values of Customer, Rate, XC Template, and Number of XCs
from the relevant fields.
5. Select the Create Bundle checkbox, if needed.

6. Select a source timeslot and a sink timeslot from the corresponding timeslot
list.
7. Click Save to save the XC to the Recent Saved XCs area. To activate the
XC, click Activate All.
8. Click Activate to activate the XC immediately.

Creating Service XC
This section describes how to create a service XC.
To create a service XC:

select the XC List tab under the Services working mode.

2. Select the Create XC button in the toolbar. The Create XC window

opens.
3. Set the XC type as service by selecting Service from the XC Type

dropdown list.
4. Select the values of Customer, Rate, XC Template, and Number of XCs
from the relevant fields.
5. Select the Create Bundle checkbox, if needed.

list.
Creating Tunnel XC
To create Tunnel XC, which is the data XC, refer to Creating P2P Tunnel XC
(on page 7-15) in the MPLS services.

Creating OH XC
This section describes how to create an OH XC.
To create an OH XC:
select the OH XC List tab under the Services working mode.

2. Select the Create XC button in the toolbar. The Create OH XC

window opens.
3. Set the direction type by selecting either the Bidirectional or Unidirectional

radio button in the XC Parameters area.
4. Select a start timeslot and an end timeslot from the corresponding timeslot
list.

Creating DCC XC
This section describes how to create a DCC XC.
To create a DCC XC:

select the DCC XC List tab under the Services working mode.

2. Select the Create XC button in the toolbar. The Create DCC XC

window opens.
3. For DCC XC, only bidirectional XC is supported.

4. Select a start timeslot and an end timeslot from the corresponding timeslot
list.

Creating PCM XC
This section describes how to create PCM XCs, including the SM10 XC and
the SM_10E XC.
Creating SM10 XC
This section describes how to create SM10 XCs.
To create an SM10 XC:

1. In a BG-40 NE shelf view window, select the SM10 card in the left object
tree. Then select the PCM XC List tab under the Services working mode.

2. Select the Create XC button in the toolbar. The Create PCM XC

window opens.
3. In the XC Parameters area, select the rate of the XC from the Rate
dropdown list:
64K
2M
4. Set the XC direction by selecting the corresponding radio button in the
Direction field:
Bidirectional
Unidirectional
Broadcast
5. Select the Bundle checkbox if needed.

list.

Creating SM_10E XC
This section describes how to create SM_10E XCs.
To create an SM_10E XC:

1. In a BG-20/BG-30 NE shelf view window, select the SM_10E card in the
left object tree. Then select the PCM XC List tab under the Services
working mode.

2. Select the Create XC button in the toolbar. The Create PCM XC

window opens.
3. In the XC Parameters area, select the rate of the XC from the Rate
dropdown list:
64K
2M
4. Set the XC direction by selecting the corresponding radio button in the
Direction field:
Bidirectional
Unidirectional
Broadcast
5. Select the Bundle checkbox if needed.

list.
Managing the XC List

In the XC list, you can perform the following XC management:
Filter XCs
Activate XCs
Deactivate XCs
Edit a XC
View details of a XC
Upload XCs
Delete XCs
Export XCs

To manage the XC list:

1. The following window shows the server and service XC list window.
2. To filter the XCs, click + to expand the Filter area, as shown in the
following figure.
Select the relevant elements in the area and click to filter.

3. To activate an XC, select the XC in the list that you want to activate and
click the Activate XC button in the toolbar.
4. To deactivate an XC, select the XC in the list that you want to deactivate
and click the Deactivate XC button in the toolbar.
5. Click the Activate All button to activate all XCs in the NE equipment.
6. Click the Deactivate All button to deactivate all XCs in the NE

equipment.
7. To perform activating increment of the XCs, select the Activate Increment
8. To edit a XC, select the XC you want to edit and click the Edit XC button
in the toolbar. The Edit XC window opens.
Modify the information of the XC and then click Save/Activate.

9. To view details of an XC, select the XC in the list and click the View XC
button in the toolbar. The Trail XC window opens.

10. To upload XCs, select the Upload XCs button in the toolbar.

Click Upload to upload XCs. The status bar shows the consistency status
between the NE and the database. If the NE and the database are
inconsistent, select the Policer Profile Compare tab to display the
inconsistency results.

11. To delete an XC, select the XC you want delete in the list and click in
the toolbar.

12. To export XCs, select the XCs you want to export and click in the
toolbar. The Save window opens.
13. Select a folder to save the file, enter the name of the file, and click Save.

Configuring SNCP Attributes

The EMS-BGF supports SNCP I/N. The default is SNCP N.
To define SNCP attributes:

1. In an NE shelf view window, select an object in the left object tree. Then
select the SNCP tab under the Services working mode.
2. Click in the toolbar to obtain the SNCP attribute of the selected double-
receive point on the NE side.
3. Set the SNCP attributes for each object.
4. Click Apply to send the SNCP attribute displayed in the list to the NE
equipment. When the SNCP attribute is successfully sent, it is saved to the
EMS-BGF database.

Exporting and Importing XC

Files
You can export a trail as an XML file and import XC XML files to the EMS-
BGF.
Exporting XCs
This section describes how to export XCs in the EMS-BGF.
To export XCs:
1. In the EMS-BGF main window, select Services >Export > Export SDH
XCs/Tunnel XCs/PCM XCs in the main menu. The Export XC window
opens.
2. Select the XCs you want to export. Click in the toolbar to select all the
XCs in the list.

4. Select a folder to save the file, enter the file name, and click Save.
Importing XC XML Files

This section describes how to import XC XML files to the EMS-BGF.
To import XCs:
1. In the EMS-BGF main window, select Services >Import > Import SDH
XCs/Tunnel XCs in the main menu. The Import XC window opens.

4. Select the XC in the list that you want import and click the Import button
in the toolbar.


11
Working with Protection
In this chapter:
Overview ....................................................................................................... 11-1
Workflow ....................................................................................................... 11-1
Working with TP ........................................................................................... 11-2
Working with MSP 1+1............................................................................... 11-14
Working with STP and MSTP ..................................................................... 11-20
MS Shared Protection Ring (MS-SPRing) .................................................. 11-26
Overview
The section discusses how to use the EMS-BGF to configure protection
schemes for NEs.
Workflow
This section describes the workflow for performing protection operations.
Implement the following workflow:
Working with TP (on page 11-2)
Working with MSP 1+1 (on page 11-14)
Working with STP and MSTP (on page 11-20)
MS Shared Protection Ring (MS-SPRing) (on page 11-26)

Working with Protection EMS-BGF User Manual
Working with TP
TP Overview
Tributary Protection (TP) is supported in the BG-30 NE in the EMS-BGF. TP
is one type of equipment protection that protects against card failure for
tributary cards, such as card power-off, card out, BIT fail, and so on.
The protection scheme can be 1:1 or 1:2. For a TP protection scheme, the
protection must be associated with the relevant tributary cards, meaning the
protecting card and the protected cards. In the EMS-BGF, this involves
defining a protection group (PG), as follows:
Protecting card: Only one tributary card can be selected as the protecting
card. This card should have no existing trails. The protecting card can be
located in any slot.
Protected cards: One or two tributary card(s) (one for a 1:1 scheme and two
for a 1:2 scheme) can be selected as protected cards. A protected card can
have existing trails, which means that tributary protection can be performed
for a traffic-carrying card without removing existing traffic.
Associate the protecting card and protected cards with a proper TP card.
There are three types of TP cards defined in the EMS-BGF that can be
managed: TP21_2, TPS1_1 and TP63_1.
Table 11-1: BG-30 Tributary Protection Group Options

No. TP Type Protection Protection Card Associated Protected Applicable system
Scheme TP card interfaces
Protected Protecting
1. 21xE1 1:2 2xPME1_21 PME1_21 TP21_2 42xE1 All (All means any
ADM rate with
XIO30-1/4/16 and
SMQ1&4)
1:1 PME1_21 PME1_21 TP21_2 21xE1 All
2. 63xE1 1:1 PE1_63 PE1_63 TP63_1 63xE1 All
PE1_63 3xPME1_21 TP63_1 63xE1 All
4. 1xSTM-1e 1:1 XIO30-1 XIO30-1 TPS1_1 1xSTM-1e ADM-1/4
XIO30-4 XIO30-4 TPS1_1 1xSTM-1e ADM-1/4
5. 4xSTM-1e 1:1 XIO30Q_1& XIO30Q_1&4 TPS1_1 4xSTM-1e 4xADM-1/4
4
SMQ1&4 SMQ1&4 TPS1_1 4xSTM-1e ADM-16
4xADM-1/4
6. 3xE3/DS3 1:1 PM345_3 PM345_3 TPS1_1 3xE3/DS-3 All
P345_3E P345_3E TPS1_1 3xE3/DS-3 All

EMS-BGF User Manual Working with Protection

No. TP Type Protection Protection Card Associated Protected Applicable
Scheme TP card interfaces system
1. 63xE1 1:1 PE1_63 PE1_63 TP63_1 63xE1 All
2. 4xSTM-1e 1:1 S1_4 S1_4 TPS1_1 4xSTM-1e All
3. 3xE3/DS3 1:1 P345_3E P345_3E TPS1_1 3xE3/DS-3 All
Managing TP
There are three types of TP cards defined in the EMS-BGF that can be
managed: TP21_2, TPS1_1 and TP63_1. Depending on the TP configuration, a
maximum of two TP cards can be inserted in one BG-30E shelf.

No. TP Type Protection Protection Card Associated Protected Applicable system
Scheme TP card interfaces
1. 21xE1 1:2 2xPME1_21 PME1_21 TP21_2 42xE1 All (All means any
ADM rate with
XIO30-1/4/16 and
SMQ1&4)
1:1 PME1_21 PME1_21 TP21_2 21xE1 All
2. 63xE1 1:1 PE1_63 PE1_63 TP63_1 63xE1 All
PE1_63 3xPME1_21 TP63_1 63xE1 All
4. 1xSTM-1e 1:1 XIO30-1 XIO30-1 TPS1_1 1xSTM-1e ADM-1/4
XIO30-4 XIO30-4 TPS1_1 1xSTM-1e ADM-1/4
5. 4xSTM-1e 1:1 XIO30Q_1&4 XIO30Q_1&4 TPS1_1 4xSTM-1e 4xADM-1/4
SMQ1&4 SMQ1&4 TPS1_1 4xSTM-1e ADM-16
4xADM-1/4
6. 3xE3/DS3 1:1 PM345_3 PM345_3 TPS1_1 3xE3/DS-3 All
P345_3E P345_3E TPS1_1 3xE3/DS-3 All

No. TP Type Protection Protection Card Associated Protected Applicable
Scheme TP card interfaces system
1. 63xE1 1:1 PE1_63 PE1_63 TP63_1 63xE1 All
2. 4xSTM-1e 1:1 S1_4 S1_4 TPS1_1 4xSTM-1e All
3. 3xE3/DS3 1:1 P345_3E P345_3E TPS1_1 3xE3/DS-3 All

Managing TP21_2
As an expansion card of the BG-30E, the TPS1_1 card can be assigned to any
slot of the Eslots.
To perform slot assignment for the TP21_2:

1. Select a BG-30 NE in the EMS topology map and select Configuration >
Slot Assignment in the main menu. In the opened Slot Assignment
window, select the BG-30E checkbox at the lower left corner.
2. Assign two or three PME1_21 cards in the BG-30B shelf's Tslots by right-
clicking a Tslot and selecting PME1_21 in the pop up menu.

3. Right-click any Eslot in the BG-30E shelf and select TP21_2 in the pop up
menu.
4. Click Apply to save the assignment, and click Close to close the Slot
Assignment window.
To manage the TP21_2:

1. Double-click the assigned BG-30E NE. In the opened NE shelf view
window, select the TP21_2 card in the left object tree. Then select the PG
Setting tab under the Configuration working mode. The following
window opens.

2. Configure the attributes in the window as described below:

Select a tributary PG type from the Tributary PG Type dropdown list.
For the TP21_2, you can only select PME1_21.
Set Not Revertive or Revertive in the Switch Mode dropdown list.
The default is Not Revertive.
If you set the Revertive switch mode, the WTR Time area will be
available. Set the wait-to-restore time by selecting a numeric value.
Set the protecting card, protected card in the respective fields. The
fields should not be set with the same selections. If you assigned only
two PME1_21 cards in the BG-30B shelf, you should set the Protected
Card 2 #.
4. To view the PG settings, click to retrieve the information in the list.

5. If there are two protected cards set in the list, you can click to select
which protected card to be monitored in the protection group.
Select a protected card by clicking the relevant radio button, and click
Apply to save the setting.
6. To delete the PG, click in the toolbar.
Managing TPS1_1
As an expansion card of the BG-30E/BG-64E, the TPS1_1 card can be
assigned to any slot of the Eslots.
To perform slot assignment for TPS1_1:

1. Select a BG-30/BG-64 NE in the EMS topology map and select
Configuration > Slot Assignment in the main menu. In the opened Slot
Assignment window, select the BG-30E checkbox at the lower left corner.
2. In the BG-30B shelf, you can assign the XS A and XS B slots as XIO30-1,
XIO30-4, XIO30-16 or XIO30Q_1&4 card by right-clicking the XS A slot
and selecting the card from the pop up menu.

Or you can assign two PM345_3 cards in any two TSlots.
3. Right-click any Eslot in the BG-30E shelf and select TPS1_1 in the pop up
menu.
Assignment window.

To manage TPS1_1:
1. Double-click the assigned BG-30E/BG-64E NE. In the opened NE shelf
view window, select the TPS1_1 card in the left object tree. Then select the
PG Setting tab under the Configuration working mode. The following
window opens.

Select a tributary PG type from the Tributary PG Type dropdown list.
Set Not Revertive or Revertive in the Switch Mode dropdown list.
Set the protecting card and the protected card in the respective fields.
The fields should not be set with the same selections.

Managing TP63_1
As an expansion card of the BG-30E/BG-64E, the TP63_1 card can only be
assigned to ESlot3.
To perform slot assignment for TP63_1:

1. Select a BG-30/BG-64 NE in the EMS topology map, and select
Configuration > Slot Assignment in the main menu. In the opened Slot
Assignment window, select the BG-30E checkbox at the lower left corner.
2. Set the protection cards according to TP group options described in
Managing TP (on page 11-3).

3. Right-click ES 3 in the BG-30E shelf and select TP63_1 in the pop up

menu.
Assignment window.
To manage TP63_1:
1. Double-click the assigned BG-30E NE. In the opened NE shelf view
window, select the TP63_1 card in the left object tree. Then select the PG
Setting tab under the Configuration working mode. The following
window opens.


Select a tributary PG type from the Tributary PG Type drop-down
list.
Set Not Revertive or Revertive in the Switch Mode drop-down list.
Set the protecting card, protected card in the respective fields. The
fields should not be set with the same selections.

TPG Maintenance
This section describes how to perform TPG maintenance.
To perform TPG maintenance:

1. In the BG-30 NE shelf view window, select the TP card in the left object
tree and then select the Maintenance working mode.
2. Set the switch mode for all the cards in the TPG Maintenance tab window.
3. Click Apply in corresponding areas to save your settings.

Working with MSP 1+1

MSP 1+1 Overview
The EMS-BGF supports both unidirectional and bidirectional MSP Linear 1+1.
The protection group (PG) must comprise two STM-N interfaces with the same
rate.
To create a PG, you can select the main port and the protection ports either in
the same card or in different cards, but it is recommended that you select them
in different cards. If you select ports in the same card, the PG does not work if
the card fails.
The MSP 1+1 is supported in the following cards:
MSP 1+1 for STM1
XIO30-1
SMQ1&4 (ports configured to STM-1)
SMD1B
S1_4
MSP 1+1 for STM4
XIO30-4
SMQ1&4 (ports configured to STM-4)
SMS4
SMD4
S4_1
MSP 1+1 for XIO30-16/XIO16-4
MSP 1+1 for XIO64
XIO30-16

Managing MSP 1+1

This section describes how to manage MSP 1+1.
To create PGs:
1. In the NE shelf view window, select the NE in the object tree. Then select
the MSP-Linear tab under the Configuration working mode. The window
opens as below:

2. To create a PG, click in the toolbar. The Create PG window opens.
3. In the Create PG window, select Unidirectional or Bidirectional mode in

the Protocol Mode field by selecting the relevant radio button.

4. In the Main and Protection area, click to expand the cards. Then select
a main port and a protection port, as shown in the following figure.
5. Click Apply to create the PG. If the PG creation is successful, the green
icons adjacent to the ports will turn gray.
If you select the main port and the protection port in the same card, a
reminder window opens prompting you to confirm the creation, as shown
below.
Click Yes to confirm, or click No to cancel.
6. Close the Create PG window, and click in the toolbar to retrieve the
information and to view the PG list.

To Upload the PGs:
1. In the PG list, click in the toolbar. The PG Upload window opens.

2. Select the Compare Result tab to view the results comparison.
To delete the PGs:

1. In the PG list, select the PG you want to delete and click in the toolbar.
2. If you want to delete all the PGs in the list, click to empty the MSP
Linear list.

Working with STP and MSTP

STP and MSTP Overview
The Spanning Tree Protocol (STP) is a Layer 2 link management protocol that
provides path redundancy while preventing undesirable loops in the network.
For a Layer 2 Ethernet network to function properly, only one active path can
exist between any two stations. STP operation is transparent to end stations,
which cannot detect whether they are connected to a single LAN segment or a
switched LAN of multiple segments.
When you create fault-tolerant internetworks, you must have a loop-free path
between all nodes in a network. The STP algorithm calculates the best loop-
free path through a switched Layer 2 network. Layer 2 LAN ports send and
receive STP frames at regular intervals. Network devices do not forward these
frames, but use the frames to construct a loop-free path.
Multiple active paths between end stations cause loops in the network. If a loop
exists in the network, end stations may receive duplicate messages and network
devices may learn end station MAC addresses on multiple Layer 2 LAN ports.
These conditions result in an unstable network.
STP defines a tree with a root bridge and a loop-free path from the root to all
network devices in the Layer 2 network. STP forces redundant data paths into a
standby (blocked) state. If a network segment in the spanning tree fails and a
redundant path exists, the STP algorithm recalculates the spanning tree
topology and activates the standby path.
When two Layer 2 LAN ports on a network device are part of a loop, the STP
port priority and port path cost setting determine which port is put in the
forwarding state and which port is put in the blocking state. The STP port
priority value represents the location of a port in the network topology and how
well located it is to pass traffic. The STP port path cost value represents the
media speed.
The Multiple Spanning Tree Protocol (MSTP) builds multiple spanning trees
(STs) in a region. Each S-VLAN is carried by a single ST. STs are referred to
as Multiple Spanning Tree Instances (MSTIs) and are denoted by MSTi (where
i ranges from 1 to N).
The key reason for using MSTP is to use all the links of the network. This is
important because a link may be blocked for one tree, but active for another.
Another key reason is to choose good roots per service. For example, a
broadcast should be rooted at the broadcasting node.
Regions are constructed autonomously by the MST protocol. A digest of the
mapping of S-VLAN IDs to MSTi is used as part of the region designator.
Changing this mapping influences the region definition. Therefore, the
mapping should only be changed when the regions and trees are to be changed
not when a service is added.

MSTP ensures that regions are contiguous. If there are noncontiguous islands
of MSTP-speaking elements, each island becomes a region and (multiple)
separate trees are created in each region.
Workflow
You can perform the following operations for STP and MSTP:
Obtain bridge STP/MSTP settings
Configure bridge STP/MSTP settings
Configure port MSTP settings
Supported Cards
Only the FE_12 card in the BG-40 NE supports STP.
All the L2 Data cards in the EMS-BGF support MSTP:
MPS_6F
MPS_4F
MPS_2G_8F
MESW_6F
ESW_2G_8F_E
DMFE_4_L2
DMFX_4_L2
DMGE _2_L2
DMGE_4_L2
DMGE_8_L2
ME_2G_4F

Configuring STP and MSTP

This section describes how to configure STP and MSTP in EMS-BGF.
To configure STP:
1. In the BG-40 NE shelf view window, in the left object tree, select the
Switch object under the FE_12 card. Then select the Configuration
working mode. The window opens as shown below.
2. To configure the STP settings, set the bridge parameters:

STP Enable: Enable/Disable. The default is Enable.
Max Age Time: determines the amount of time protocol information
received on a port is stored by the network device.
Hello Time: determines how often the network device broadcasts hello
messages to other network devices.
Forward Delay: determines how long each listening and learning state
lasts before the port begins forwarding.
Priority: The default is 32,768. This parameter is used for root bridge
selection. The lower the parameter, the higher the priority. The bridge
with the highest priority is the root bridge.
3. Click Apply to send the settings to the equipment and the database.
4. Click in the toolbar to retrieve the bridge STP settings.

The configuration of the MSTP settings includes bridge MSTP settings and
port MSTP settings.

To configure bridge MSTP settings:

1. In the NE shelf view window, in the left object tree, select the Switch
object under a Layer 2 data card. Then select the Configuration working
mode. There are three tabs connected to MSTP in the properties area:
MSTP, MSTP Ports, and MSTP Instance.
2. In the MSTP Configuration area, set the following parameters to

configure the MSTP settings:
Network ID: the default is 0.
Protocol Enable: Enable/Disable. The default is Enable.
Revision Level: the default is 0.
Forward Delay: determines how long each listening and learning state
lasts before the port begins forwarding.
Hello Time: determines how often the network device broadcasts hello
messages to other network devices.
Max Age: determines the amount of time protocol information received
on a port is stored by the network device.

3. To set MSTP instance, you should first select the default instance in the
MSTP Instance list. Then click in the toolbar to modify the S-VLAN,
as shown in the following window.
Click Apply to save the changes.
After this, you can click to add a new instance, or click to delete a
selected instance.
4. Click Apply to send the settings to the equipment and the database.
5. If you want to export the instance to a file, click in the toolbar.
6. Click in the toolbar to retrieve the bridge MSTP settings.
7. Click the default icon to set the configuration data as default.
To configure port MSTP settings:

1. In the MSTP Ports tab, set the port MSTP parameters.
Click Apply to save the settings.

2. In the MSTP Instance tab, click to retrieve the information.
Set the following two attributes in this window:

Priority: This priority is per instance. The lower the value, the higher the
priority. This is used to select the root port or a designated port.
Path Cost: This path cost is per instance. The higher the rate, the lower the
path cost. The path cost is 19 for 100BaseT ports.
3. Click Apply to send the port MSTP settings to the equipment and the
database.

MS Shared Protection Ring (MS-

SPRing)
This section describes functions of MS-SPRING for BG-30 and BG-64.
Overview
MS shared protection ring (MS-SPRing) is a protection scheme in which the
total capacity in a multiplex section is divided equally into working and
protection traffic. The protection traffic in a multiplex section is shared to
protect the working traffic carried in the working part of any multiplex section
in the ring. The notation of "sharing" refers to the fact that the ring protection
traffic can be shared by any multiplex section of a multi-node ring under a
section or node fault condition. Sharing of protection traffic may lead to better
traffic carrying capacity under normal conditions over other ring protection
types.
For MS shared protection rings, the working channels carry the normal traffic
signals to be protected while the protection channels are reserved for protection
of this service. When the protection channels are not being used to restore the
normal traffic signals, they can be used to carry Extra Traffic signals. In the
event of a protection switch, the normal traffic on the working channels will
access the protection channels causing any extra traffic to be removed from the
protection channels.
Two-fiber MS shared protection rings is a type of MS shared protection rings
currently supported in EMS-BGF.
Two-fiber MS switched rings require only two fiber for each span of the ring.
Each fiber carries both working channels and protection channels. On each
fiber, half the channels are defined as working channels and half are defined as
protection channels. The normal traffic carried on working channels in one
fiber are protected by the protection channels travelling in the opposite
direction around the ring. This permits the bidirectional transport of normal
traffic. Only one set of overhead channels is used on each fiber.
Two-fiber MS shared protection rings support ring switching only. When a ring
switch is invoked, the normal traffic is switched from the working channels to
the protection channels in the opposite direction.
If Non-pre-emptible Unprotected Traffic (NUT) is supported, selected channels
on the working bandwidth and their corresponding protection channels may be
provisioned as non-pre-emptible unprotected channels. The remaining working
channels are still protected by the corresponding protection channels. The non-
pre-emptible unprotected channels will have no MS-SPRing APS protection.

The following figure shows the view of entire ring.
Each fiber carries both working and protection traffic as shown in the exploded
view. The following figure shows the exploded view of the shaded portion of
the ring.
MS-SPRing protocols allow the available bandwidth to be partitioned into three

types of channels: working channel to carry working traffic, protection channel
which may be used to carry extra traffic, and Non-preemptible unprotected
traffic (NUT) channel to carry non-preemptible unprotected traffic.

Non-preemptible unprotected traffic is unprotected traffic that is carried on

channels with the MS-SPRing APS protection switching mechanism disabled
for certain HO VC channels (working channels and their corresponding
protection channels). Traffic carried on these channels is unprotected MS-
SPRing wise (but can be protected using other schemes) and non-preemptible.
When NUT is supported in two-fiber MS-SPRing, selected channels on the
working bandwidth and their corresponding protection channels (everywhere
along the ring) can be provisioned as non-preemptible unprotected channels.
The remaining working channels are still protected by the corresponding
protection channels.
NUT channels are the channels that are not protected by MS-SPRing. NUT can
be configured per ring, which means all nodes have the same NUT definition
for a ring.
Assume the ring rate is STM-N.
In default, there is no NUT channels; That is, channel[1~N/2] are protected
channels, and channel [(N/2+1)~N] are protecting channels.
Any AU-4(VC-4) of 1~N/2 can be defined as NUT channel regardless of
carrying traffic or not.
If AU-4[n] is defined as NUT, AU-4[n+N/2] automatically becomes NUT;
If contiguous concatenation (VC-4-Xc) is defined on working channels,
they will be defined as NUT together;
User can move AU-4 from protected to NUT or from NUT to protected.
Workflow
For a MS-SPRing, it may consist of 2~16 nodes, each node is located on one
NE. For a NE, it may be a node of different rings.
Creating a MS-SPRing needs to define following information:
1. Define a ring-ID and ring-label, which is used to identify the MS-SPRing.
Ring ID should be unique within the EMS domain
Ring label is a string to present the ring.
2. Select the ring rate: STM-16 or STM-64.
3. Define the ring type, currently 2 fibers only.
4. Designate all the NEs pertaining to this ring (by specifying the NE ID). The
maximum number of NEs that may be part of MS-SPRing is 16.

5. Define east MS and west MS ports for each node one by one.
East and west link must have the same rate for all nodes.
Only STM-16 and STM-64 links are capable of MS-SPRing.
No traffic in AU-4 for the selected east or west MS port except NUT
channels.
A MS port can only be used by one ring.
6. Define NUT channels for the ring. The NUT configuration is optional.
In default [1 to N/2] are protected (working) channels, and [N/2+1 to N] are
protecting channels. Any channel of protected channels can be defined as
NUT channel, and then corresponding channel on protecting channels is
automatically defined as NUT channel. For example, for a STM-64 ring, if
AU4[9] is defined as NUT channel, then AU4[41] becomes NUT channel
at the same time.
7. Allocate node ID and configure the ring map (move up/down).
In summary, the configuration of a MS-SPRing includes:
Ring ID, Ring label, Ring rate, Ring type
PG list (one PG per NE)
NUT channels
Ring map

Creating a MS-SPRing
This section describes how to create a MS-SPRing.
The Maximum number of rings that a BG NE can be supported:
BG-30 (XIO30-16): 1 x STM-16 ring
BG-64 (XIO64): 1 x STM-64 ring
BG-64 (XIO16-4): 4 x STM-16 rings
To create a MS-SPRing:
1. In the EMS-BGF main topology view, select the NEs you want to add to
the MS-SPRing, then select Configuration > MS-SPRing > Create MS-
SPRing from the main menu. The Create MS-SPRing window opens. If
none NE is selected, all the NEs will be displayed in the Select NE list by
default in the Create MS-SPRing window.
2. In the General area, configure the parameters as described below:

Ring ID (101~200): Ring ID is assigned automatically by EMS when a
new ring is created and can be edited by user if needed. Ring ID is
assigned by EMS, each time a new ring. The Ring ID should be unique.
Ring Label: Ring label is a string to present the ring.

WTR (1~720): Wait To Restore (WTR). The condition in which a

working unit meets the recovery condition after unit fault condition.
The working traffic is ready to be reverted to the working unit from the
protection unit. The wait to restore time ensures that a failed unit is
considered again as available by the protection process only if it is fault
free for a certain time. The wait to restore time is configurable in the
range of 0 to 720 seconds (12 minutes) in steps of 1 seconds. The
default value is 300 seconds (5 minutes).
Ring Rate: Only STM-16 and STM-64 links are capable of MS-
SPRing.
Ring Type: Currently 2 fibers only.
Revertive Mode: Currently Revertive mode only. In revertive mode of
operation, when the protection is no longer requested, the failed
working section is no longer in switch event condition, the normal
traffic is restored from the working section.
3. In the Select Resources area, define east MS and west MS ports for each
node one by one. Select an NE from the Select NE dropdown list and then
select select the east MS and west MS ports in the corresponding list.

4. Click Add to add the created PG to the PG List below.

5. Select another NE and define the west MS and the east MS ports with the
same procedures. The maximum number of NEs that may be part of MS-
SPRing is 16.

6. In the PG list, user can move the PG up or down, or delete the PG by

selecting the corresponding button in the toolbar, or from the right-click
menu, as described below.

7. To define NUT channels for the ring, in the NUT Channels Configuration
area, click the Configuration button.

8. In the Configure NUT Channels window, select the VC4s from the
Available NUT Channels list and click to add the selected VC4s to
the Selected NUT Channels list. In default [1~N/2] are protected
(working) channels, and [N/2+1~N] are protecting channels. Any channel
of protected channels can be defined as NUT channel, and then
corresponding channel on protecting channels is automatically defined as
NUT channel.

10. Click Save to save the ring in the database. Or Click Activate to activate
the PG to the NE.
Using the MS-SPRing List

In the MS-SPRing list, user can perform the following operations:
Viewing the information of a ring
Activating or de-activateing a ring
Creating, editing or deleting a ring
Performing HO/LO Squelch configuration
Viewing K1/K2 information
Performing maintenance operations

Accessing the MS-SPRing List

This section describes how to accessing the MS-SPRing list.
To access the MS-SPRing list:

In the EMS-BGF main topology view window, select Configuration >
MS-SPRing > MS-SPRing List from the main menu. The MS-SPRing
List window opens.

Viewing a MS-SPRing
In the MS-SPRing list window, user can view the information of a MS-SPRing.
To view a MS-SPRing:
1. To view the general information of a MS-SPRing, in the MS-SPRing List
window, select the ring in the left ring list, then select the General tab in
the right area of the window.
2. Click on the toolbar to get the information to view.

Activating and De-activating a MS-SPRing

This section describes how to activate or deactivate a MS-SPRing.
To activate/deactivate a MS-SPRing:
To activate/deactivate a ring, in the MS-SPRing List window, select
Operation > Activate Ring/De-Activate Ring from the main menu, or
right-click on the ring you want to delete in the left ring list, and then select
Activate Ring/De-Activate Ring from the right menu.
Creating, Editing and Deleting a MS-SPRing

User can create, edit or delete a MS-SPRing in the MS-SPRing list.
By editing a ring, user can:
Modify ring label
Update ring map
Add an NE to ring
Delete an NE from ring
Update NUT channels

To create a MS-SPRing:
To create a MS-SPRing, in the MS-SPRing List window, select Operation
> Create Ring from the main menu, or right-click on the left ring list and
select Create Ring from the right menu.
For details about creating a MS-SPRing, refer to Creating a MS-SPRing

(on page 11-30).

To edit a MS-SPRing:
1. To edit a MS-SPRing, in the MS-SPRing List window, select Operation >
Edit Ring from the main menu, or right-click on the ring you want to edit
in the left ring list and select Edit Ring from the right menu. The Edit MS-
SPRing window opens.
2. User can edit the Ring Label, WTR in the General area.
3. In the Select Resources area, user can add NEs into the ring.
4. In the PG List, user can move the PG up or down and can also delete NE(s)
from the ring.

5. In the NUT Channel Configuration area, user can update NUT channels
for the ring.
6. Click Save&Activate to save the changes.

To delete a MS-SPRing:
1. Before deleting a ring, make sure the ring is de-activated.
2. To delete a MS-SPRing, in the MS-SPRing List window, select Operation
> Delete Ring from the main menu, or right-click on the ring you want to
delete in the left ring list, and then select Delete Ring from the right menu.
Performing HO/LO Squelch Configuration

Squelching is the operation of inserting AIS in order to avoid mis-connection in
case of failure in the ring.
In the case of a node failure, isolated node (due to fiber cuts at both East and
West sides), or isolated chains (due to dual fiber cuts) squelching will be done.
The switching nodes determine the traffic affected by the protection switch
from information contained in their ring maps and from the identifications of
the requesting nodes.
Potential mis-connection shall be squelched by inserting appropriate AU-AIS
signal where mis-connected traffic could occur. The switching nodes shall
squelch an AU4 in the following cases:
The isolated node (chain) involves VC4 termination.
The isolated node (chain) performs Time Slots Interchanged(TSI) action.
Time Slot Interchange(TSI) allows better utilization of bandwidth of the ring.
When employed, the traffic having a timeslot interchange through the failed
location will be squelched.

Squelch configuration can be performed only when the MS-SPRing is

activated.
NOTE: Don't perform any trail/XC configuration during the

HO/LO squelch configuration in the same NE.
To perform HO squelch configuration:

1. In the MS-SPRing List window, select the ring in the left ring list, then
select the HO squelching tab in the right area of the window.

2. To create HO squelch items, click in the toolbar. The Create HO

Squelch window opens.
3. Configure the parameters for the HO squelch item:

Ring ID: the ID of the selected ring.
Ring Label: the label of the selected ring.
Drop Node: lists all the nodes of the selected ring. Select one as the
drop node from the dropdown list.
AU4: lists all the working AU4 of the selected ring. Select an AU4
from the dropdown list.
Direction: West or East.
Added From Node: lists all the nodes of the selected ring. Drop NE ID
can't be the same as added NE ID.

4. Click Apply to create the HO squelch item.

6. To delete an HO squelch item, select an HO squelch item you want to
delete and click in the toolbar.
7. To clear the squelch table, click in the toolbar.

To perform LO squelch configuration:

select the LO squelching tab in the right area of the window.
2. To create LO squelch items, click in the toolbar. The Create LO

Squelch window opens.

3. Configure the parameters for the HO squelch item:

Ring ID: the ID of the selected ring.
Ring Label: the label of the selected ring.
Drop Node: lists all the nodes of the selected ring. Select one as the
drop node from the dropdown list.
AU4: lists all the working AU4 of the selected ring. Select an AU4
from the dropdown list.
LO VC: lists all the working VC12/VC3 of the selected ring.
Direction: West or East.
Added From Node: lists all the nodes of the selected ring. Drop NE ID
can't be the same as added NE ID.
4. Click Apply to create the LO squelch item.

6. To delete a LO squelch item, select a LO squelch item you want to delete
and click in the toolbar.
7. To clear the squelch table, click in the toolbar.

Viewing K1/K2 Information

User can view the K1/K2 information of the activated PGs.
To view the K1/K2 information:

select the K1/K2 tab in the right area of the window.
Performing Maintenance Operations

User can perform the following maintenance operations for the activated PGs
from the MS-SPRing List window:
APS Controller: that part of a node that is responsible for generating and
terminating information carried in the APS protocol and implementing the
APS algorithm.
Lockout of Working Channels - Ring Switch
Lockout of Protection - Span:
Forced Switch to Protection - Ring
Manual Switch to Protection - Ring
Exercise - Ring
Clear
The maintenance operations have no effect on NUT channels.

To perform maintenance operations:

1. In the MS-SPRing List window, select an activated ring in the left ring list,
then select the General tab in the right area of the window.
2. In the PG list, right-click on a ring node, the maintenance list will be

displayed.
3. Select the maintenance operation you want to perform from the right menu.
4. To remove the maintenance, select Clear.


12
Ethernet Ring Protection
Switching (ERPS)
In this chapter:
Overview ....................................................................................................... 12-1
Workflow ....................................................................................................... 12-2
Creating PB Ring ERP Control VSI .............................................................. 12-4
Creating MPLS Ring ERP Control VSI ...................................................... 12-10
Viewing ERPS Instance............................................................................... 12-15
Overview
Ethernet Ring Protection Switching (ERPS) helps to achieve high reliability
and network stability. Links in the ring will never form loops that fatally affect
the network operation and services availability. The basic idea of an Ethernet
ring is to use one specific link to protect the whole ring. This special link is
called a Ring Protection Link (RPL). If no failure happens in other links of the
ring, the RPL blocks the traffic and is not used. RPL is controlled by a special
node called an RPL owner. There is only one RPL owner in a ring. The RPL
owner is responsible for blocking traffic over the RPL. Under ring failure
conditions, the RPL owner is responsible for unblocking traffic over the RPL.
A ring failure results in protection switching of the RPL traffic. An APS
protocol is used to coordinate the protection actions over the ring. Protection
switching blocks traffic on the failed link and unblocks the traffic on the RPL.
When the failure clears, revertive protection switching blocks traffic over the
RPL and unblocks traffic on the link on which the failure is cleared.

Ethernet Ring Protection Switching EMS-BGF User Manual
(ERPS)
The following figure is an example of ERPS operation.
In the figure, there are 6 nodes in this ring topology, and one node is called
RPL owner node which owns RPL. Other nodes are called Ring node. In this
ring, RPL is blocked on RPL owner node. When link/node failure is detected
by the nodes adjacent to the failure, the nodes adjacent to failure can block the
failed link and flush FDB and report the failure to ring nodes using the R-
APS(SF) message. When the ring nodes receive the R-APS(SF) message, they
flush the FDB. When the RPL owner node receive the R-APS(SF) message, it
unblocks the RPL and flush FDB. The ring is in protocol state and all nodes
remain connected in the logical topology.
Workflow
Following are the Layer 2 data cards that support ERP Control VSI.:
MPS_4F
MPS_6F
DMFE_4_L2
DMFX_4_L2
DMGE_2_L2
DMGE_4_L2
DMGE_8_L2
MPS_2G_8F
ME_2G_4F

EMS-BGF User Manual Ethernet Ring Protection Switching
(ERPS)
The procedure for creating PB Ring ERP Control VSI can be performed as
below:
Set the Interface type (I-NNI) for the ETY/EoS ports in a data card.
In the Create VSI window, select the PB Ring as the ERP Type.
In the Create VSI window, select the West port and East port for the
services.
In the Create VSI window, set the required VSI parameters and ERPS
parameters for the services.
Create the PB Ring ERP Control VSI .
MPLS Ring ERP Control VSI must have one ERP port and one remote PE. The
procedure for creating MPLS Ring ERP Control VSI can be performed as
below:
Define the Configuration Mode as MPLS.
Assign PE ID and MPLS Network ID. Each MPLS requires a unique PE
ID.
Configure ports as MoT port type.
Set the Interface type (I-NNI) for the ETY/EoS ports in the card.
Set the VCG attribute. In the Create VCGs window, configure the VCG
bandwidth.
Create required tunnels.
In the Create VSI window, select the MPLS Ring as the ERP Type.
In the Create VSI window, select one ERP port and one remote PE for the
services.
In the Create VSI window, set the required VSI parameters and ERPS
parameters for the services.
Create the MPLS Ring ERP Control VSI.

(ERPS)
Creating PB Ring ERP Control

VSI
This section describes how to create a PB Ring ERP Control VSI.
To create a PB Ring ERP Control VSI:

1. To set the ETY port attribute, select a layer 2 data card in the left object
tree, then select the ETY/EoS Ports tab under the Configuration working
mode.

(ERPS)
Select I-NNI in the Type list. Click Apply to save the settings.
2. To create the ERP Control VSI, select the Switch object under the data
card in the left object tree. Then select the VSI List tab under the Services
working mode.

(ERPS)
Click the Create VSI button in the toolbar. The Create VSI window
opens.
3. To create ERP Control service, select ERP VSI from the Service Type
dropdown list and select PB Ring as the ERP Type.
Enabled.
5. Enter the VSI ID, NMS VSI ID, User Label, Customer values as
required.
6. In the ERPS Parameters area, select RPL Owner or Ring Node from the
ERP Node Role dropdown list. Then set the ERP Instance ID, ERP
Instance Name, S_VLAN and other parameters as required.
ERP Type: To create PB Ring ERP Control VSI, select PB Ring.
ERP Node Role: Multiple nodes are used to form a ring. For each ring
node, there are two different node types: RPL Owner and Ring Node.
RPL owner node is an Ethernet Ring Node adjacent to the RPL that
is responsible for blocking itself of the RPL under normal
conditions.
Ring node is the node has no special role on the ring.
There can only one RPL owner for each ring.
ERP Instance ID: 0-31. The default is 0.
ERP Instance Name: the name of the ERP Instance.
S_VLAN: 1-4094.

(ERPS)
Protected S_VLAN: the S_VLAN protected by the ERPS. The

S_VLAN ID that doesn't belong to MSTP Instance 0 cannot be
protected by ERPS. The S_VLAN ID protected by ERPS must belong
to MSTP Instance 0.
Hold Off Time: the hold off time is used to coordinate timing of
protection switches at multiple layers. Its purpose is to allow, for
example, a server layer protection switch to have a chance to fix the
problem before switching at a client layer. The range of the hold off
timer is 0 to 10 seconds in steps of 100 ms with an accuracy of _5 ms.
The default value for hold off timer is 0 seconds.
WTR Time: In the revertive mode of operation, to prevent frequent
operation of the protection switch due to an intermittent defect, a failed
working transport entity must become stable in a fault-free state. After
the failed working transport entity meets this criterion, a fixed period of
time shall elapse before traffic channel uses it again. This period, called
the wait-to-restore (WTR) period.
In the revertive mode, when the protection is no longer requested: the
failure condition has been cleared, a wait-to-restore state will be
activated on the RPL owner node. This state will normally time out and
become a no-request state. The wait-to-restore timer is deactivated
when any request of higher priority pre-empts this state.
The WTR timer can be configured when the ERP Node Role is set as
RPL Owner, by the operator in 1 minute steps between 1 and 12
minutes. The default value is 5 minutes.
Guard Time: Ring-APS (R-APS) messages are transmitted . This,
combined with the R-APS messages forwarding method, in which
messages are copied and forwarded at every ring node around the ring,
can result in a message corresponding to an old request, which is no
longer relevant, being received by ring nodes. The reception of
messages with outdated information can result in erroneous
interpretation of the existing requests in the ring and lead to erroneous
protection switching decisions.
The guard timer is used to prevent ring nodes from receiving outdated
R-APS messages. During the duration of the guard timer, all received
R-APS messages are ignored by the ring protection control process.
This allows that old messages still circulating on the ring may be
ignored. This, however, has the side effect that, during the period of the
guard timer, a node will be unaware of new or existing ring requests
transmitted from other nodes.
The period of the guard timer can be configured by the operator in 10
ms steps between 10 ms and 2 seconds, with a default value of 500 ms.
This time should be greater than the maximum expected forwarding
delay for which one R-APS message circles around the ring.
Revertive Mode: Revertive.

(ERPS)
7. In the Objects Selections area, select one I-NNI port as the West port and
one I-NNI as the East port in the relevant list. Right-click an object to
deselect.
8. Set the Port Role for each selected port.

There are two ring ports in each ring node, and two different ring port roles
on each ring port:
RPL Port: the Ring Protection Link (RPL) is the ring link which under
normal conditions: without any failure or request, is blocked (at one
end or both ends) for traffic channel, to prevent the formation of loops.
Ring Port: the node has no special role on the ring.
If the ERP Node Role is set as Ring Node, both Port Roles can only be set
as Ring Port. If the ERP Node Role is set as RPL Owner, user can set
one of the selected ports as RPL Port and the other as Ring Port from the
Port Role dropdown list.

(ERPS)
9. Click Active to create and activate the ERP Control VSI. If you click Save,
the ERP Control VSI will be saved but not activated. To activate it, select
the Recent Saved VSIs tab.
PB Ring ERP Control VSI is then activated.

(ERPS)
Creating MPLS Ring ERP Control

VSI
This section describes how to create a MPLS Ring ERP Control VSI.
To create a MPLS Ring ERP Control VSI:

1. Before creating the MPLS Ring ERP Control VSI, using the procedures in
Creating Tunnel XCs (on page 7-8) to create tunnel XCs.
2. To set the ETY port attribute, select a layer 2 data card in the left object
tree, then select the ETY/EoS Ports tab under the Configuration working
mode.
Select I-NNI in the Type list. Click Apply to save the settings.

(ERPS)
3. To create the ERP Control VSI, select the Switch object under the data
card in the left object tree. Then select the VSI List tab under the Services
working mode.
Click the Create VSI button in the toolbar. The Create VSI window
opens.
4. To create ERP Control service, select ERP VSI from the Service Type
dropdown list and select MPLS Ring as the ERP Type.

(ERPS)
Enabled.
6. Enter the VSI ID, NMS VSI ID, User Label, Customer values as
required.
7. In the ERPS Parameters area, set the ERP Instance ID, ERP Instance
Name, S_VLAN and other parameters as required.
ERP Type: To create MPLS Ring ERP Control VSI, select MPLS
Ring.
ERP Node Role: Ring Node.
ERP Instance ID: 0-31. The default is 0.
ERP Instance Name: the name of the ERP Instance.
VC Label Scheme: only Same Incoming Label is supported here.
S_VLAN: 1-4094.
Protected S_VLAN: the S_VLAN protected by the ERPS. The
S_VLAN ID that doesn't belong to MSTP Instance 0 cannot be
protected by ERPS. The S_VLAN ID protected by ERPS must belong
to MSTP Instance 0.
Hold Off Time: the hold off time is used to coordinate timing of
protection switches at multiple layers. Its purpose is to allow, for
example, a server layer protection switch to have a chance to fix the
problem before switching at a client layer. The range of the hold off
timer is 0 to 10 seconds in steps of 100 ms with an accuracy of _5 ms.
The default value for hold off timer is 0 seconds.
WTR Time: In the revertive mode of operation, to prevent frequent
operation of the protection switch due to an intermittent defect, a failed
working transport entity must become stable in a fault-free state. After
the failed working transport entity meets this criterion, a fixed period of
time shall elapse before traffic channel uses it again. This period, called
the wait-to-restore (WTR) period.
In the revertive mode, when the protection is no longer requested: the
failure condition has been cleared, a wait-to-restore state will be
activated on the RPL owner node. This state will normally time out and
become a no-request state. The wait-to-restore timer is deactivated
when any request of higher priority pre-empts this state.
The WTR timer can be configured when the ERP Node Role is set as
RPL Owner, by the operator in 1 minute steps between 1 and 12
minutes. The default value is 5 minutes.

(ERPS)
Guard Time: Ring-APS (R-APS) messages are transmitted . This,

combined with the R-APS messages forwarding method, in which
messages are copied and forwarded at every ring node around the ring,
can result in a message corresponding to an old request, which is no
longer relevant, being received by ring nodes. The reception of
messages with outdated information can result in erroneous
interpretation of the existing requests in the ring and lead to erroneous
protection switching decisions.
The guard timer is used to prevent ring nodes from receiving outdated
R-APS messages. During the duration of the guard timer, all received
R-APS messages are ignored by the ring protection control process.
This allows that old messages still circulating on the ring may be
ignored. This, however, has the side effect that, during the period of the
guard timer, a node will be unaware of new or existing ring requests
transmitted from other nodes.
The period of the guard timer can be configured by the operator in 10
ms steps between 10 ms and 2 seconds, with a default value of 500 ms.
This time should be greater than the maximum expected forwarding
delay for which one R-APS message circles around the ring.
Revertive Mode: Revertive.
8. In the Objects Selections area, select one I-NNI port and one Remote PE
in the relevant list. Right-click an object to deselect.
9. For the selected remote PE, select a tunnel in the Tunnel list and set the In
VC Label and Out VC Label.

(ERPS)
10. Click Active to create and activate the ERP Control VSI. If you click Save,
the ERP Control VSI will be saved but not activated. To activate it, select
the Recent Saved VSIs tab.
MPLS Ring ERP Control VSI is then activated.

(ERPS)
Viewing ERPS Instance

This section describes how to view the ERPS Instance. ERPS instance is an
ERP attribute of a VSI-ERP control. They are one-to-one relationship.
The alarms of the ERPS Instance will be report on the ERP control VSI.
To view the ERPS Instance:

1. In the NE shelf view window, select the Switch object under the data card
in the left object tree, and then select the VSI List tab under the Services
working mode.

(ERPS)
2. To view the ERPS Instance, select an ERP control VSI in the VSI list and
then click the Edit VSI button or the View VSI Detail button in the
toolbar. The Edit VSI or View VSI window open.
3. Select the ERP Instance Status tab in the right area of the window and
click to get the ERP status to view.
4. There are three different states for each node of a specific ring:
init: not a participant of a specific ring.
idle: no failure on the ring, the node is performing normally. For Ring
node, traffic is unblocked on both ring ports. For the RPL owner, traffic
is blocked on the ring port that connects to the RPL and unblocked on
the other ring port.
protection: a failure occurred on the ring. For normal node, traffic is
blocked on the ring port that connects to the failing link and unblocked
on working ring ports. For the RPL owner, traffic is unblocked on both
ring ports if they connect to non-failure links.
5. There are two states on each ring port: Blocked and Forwarding.
6. The ERP counters in a ERP Instance can be described below:
RAPS TX: number of R-APS messages transmitted.
RAPS RX: number of R-APS messages received.
RAPS RX Invalid: number of invalid R-APS messages received.
Time Since ERP Topology Change: time since ERP topology change.
Counter of ERP Topology Changes: counter of ERP topology
changes.
7. To clear the ERP counters, click in the toolbar.

13
Fault Management
In this chapter:
Overview ....................................................................................................... 13-1
Workflow ....................................................................................................... 13-2
Configuring Fault Management..................................................................... 13-3
Managing Current Alarms ........................................................................... 13-18
Managing Alarms History ........................................................................... 13-25
Managing Cleared Alarms ........................................................................... 13-28
Monitoring Events ....................................................................................... 13-32
Managing Unreported Alarms ..................................................................... 13-35
Managing Archived Alarm Files ................................................................. 13-39
Managing NE Alarms Log .......................................................................... 13-44
BIT Codes .................................................................................................... 13-46
Viewing PPI Status ...................................................................................... 13-47
Troubleshooting Alarms .............................................................................. 13-48
Overview
This section discusses how to use the EMS-BGF for configuring, managing,
filtering, and troubleshooting NE alarms.
The EMS-BGF 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-BGF screen.
The EMS-BGF provides exceptionally powerful tools for viewing and
analyzing alarms, enabling you to optimize alarm-processing operations.

Fault Management EMS-BGF User Manual
The following five types of alarms are available:

Equipment alarms
Communication alarms
Service quality alarms
Processing error alarm
Environment alarms
Workflow
1. For proper alarm processing, first set up your alarm management
configuration to specify how alarms are to be treated in the system. This
stage includes defining severity profiles to assign to objects and
configuring audible alarm conditions.
2. After you have completed alarm management configuration, perform the
following operations, in any order, whenever required:
Managing Alarms
Using the Alarm Log

EMS-BGF User Manual Fault Management
Configuring Fault Management

A key step in initial system setup involves defining your alarm management
configuration.
Fault Setting
You can configure fault management through Fault Setting.
To access to the Fault Settings:

1. In the NE shelf view, select on the working mode Fault > Fault Setting.
2. The following window shows the NE shelf view with Fault Setting:
From this window, there are four tabs under the Fault Setting mode:
NE Settings
External Alarms
Severity Settings

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

1. In the NE shelf view window, select Fault > NE Settings. The following
window opens.
2. Modify the NE settings as required and click Apply to save the changes.
3. Click to refresh and retrieve the information of the NE settings.
4. Click to copy the settings from the selected NE to other NEs.

The areas of NE settings are described as follow:

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
save the events in RAM. Disabled mode means the alarm log is no
longer in use. The default setting is RAM logging only.
The Log Size defines the maximum number of records that can be
stored in a log on the NE equipment (valid value range: 0 to 1,000).
The default is 1,000.
When a log is full, it has two processing modes: Overwrite and Stop.
In Overwrite mode, new records replace the oldest records when the
log is full. In Stop mode, the alarm log stops collecting events when the
log is full. The default setting is Overwrite.
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 alarms 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 three to 30 seconds. The default is
three seconds.
For the alarm clearance hold-off period, any alarm clearance detected is
not considered as cleared unless the clearance status lasts three to 30
seconds. The default is three seconds.

To configure BG-20/BG-20C/BG-30/BG-64 NE settings:

1. Select the BG-20/BG-20C/BG-30 NE to be configured in the topology
view. Then, on the main menu, select Fault > NE Settings. The following
window opens.
2. For the BG-64 NE, the window displays as below:

3. Modify the NE settings as required and click Apply to save the changes.

In the AinS Timer area, the NEs define two AinS timer ranges from 0 to 1,800
seconds, with a step of one second. The default for Time1 is 10 seconds and
Time2 is 180 seconds.
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.

In the EMS-BGF, user 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. In this case, 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 you are currently using only part of
them. Unused service ports will 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-BGF, 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 database 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. Select a BG-40 NE in the topology view, then on the main menu, select
Fault > Monitoring and Reporting. The following window opens.
2. To set an alarm to be shielded, clear the Monitor attribute checkbox. The

default is checked.
3. Click Apply to send the settings information to the NE equipment.

To configure the settings for the BG-20/BG-20C/BG-30/BG-

64 NEs:
1. Select a BG-20/BG-20C/BG-30/BG-64 NE in the topology view. Then, on
the main menu, select Fault > Monitoring and Reporting. The following
window opens.
2. Set the attributes for each object as needed and click Apply to save the
changes.

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. In the Auto Report
attribute, you can select Report or No Report in the pull-down list.
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. The default is Timer1.
The AinS attribute applies only on the following interfaces:
PPI
FE LAN
GE LAN
Codirectional

External Alarms
The external alarm interface provides an input/output external alarm. An
external alarm interface 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-BGF 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. Select an NE in the topology view, then on the main menu, select Fault >
External Alarms. The following window opens.
There are two areas in the window: Input Ports and Output Ports.
The Input Port area displays the configuration for 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 Port tab displays configuration for the three output ports.
These ports are: major alarm, minor alarm, and sound alarm. You can set
the alarm output switch as on or off.

2. Click Apply to send the configuration data to the equipment and save it in
the database.
3. Click to retrieve port information from the equipment.
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 Fault > Severity Settings. The
following window opens.
2. Set alarm attributes as needed by selecting the relevant Severity attribute in

the pull-down list and checkbox in the Report attribute for each alarm title.
3. Click Apply to send the settings information to the NE equipment.
The functions of the icons on the toolbar are listed in the following table.
Table 13-1: Icons in the Severity Settings window
Icons Description
Refresh-retrieves the 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.

Performing Alarm Notification Settings

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

1. In the EMS-BGF main window, select Fault > Alarm Notification Setting
in the main menu. In the opened window, select the Visual Notifications
tab.
2. Configure the settings in the window by selecting the corresponding radio

button and checkbox.
4. The following figure shows the Alarm Notification window:

You can show or hide this window by selecting Fault > Display > Alarm
Notification in the EMS main window. The default is unselected.
To configure Audio Notifications:

1. In the EMS-BGF main window, select Fault > Alarm Configuration in
the main menu. In the opened window, select the Audio Notifications tab.
2. Select a sound file from each pull-down list and click Play to test the
sound.

To configure Alarm Counters:

the main menu. In the opened window, select the Alarm Counters tab.
2. Select which counter type and alarm type you want to display in the alarm
counter bar by selecting the corresponding radio buttons and checkboxes in
this window.
3. You can show or hide the alarm counter bar using any of the following
methods:
Select the Show Alarm Counter checkbox in the Alarm Counter
window.
Select Fault > Display > Alarm Counter in the EMS main window.

To report to NMS:
the main menu. In the opened window, select the Report to NMS tab.
2. Select the counter types you want to report to NMS by selecting the
corresponding checkboxes in this window.

Viewing Alarm Log File

This section describes how to view alarm log file.
To view alarm log file:

1. In the EMS-BGF main window, select Fault > View Alarm Log File in
the main menu. The Alarm-Import window opens.

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.
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. Select an NE whose alarm information you want to view in EMS topology
map. If no NE is selected, current alarm information for all NEs is
displayed by default.
2. Select Fault > Current Alarms in the main menu.
The icons on the alarm toolbar are listed in the following table.

Table 13-2: Icons on the current alarm toolbar
Icons Description
Acknowledges the alarms.
Displays alarm details.

Exports current alarms as an XML file.
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.
To view current alarms for a specific card:

1. Select an NE in the topology map.
3. In the opened window, in the left object tree, select the card whose alarm
information you want to view.

To view current alarms for a specific object:

3. In the opened window, in the left object tree, click before the tributary
card or port to display all the objects.
4. Select the object whose alarm information you want to view.

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. On the current alarm toolbar, click the Alarm Details icon to open the
Alarm Details window.
You can see from the window the details information of the alarm,
including Alarm Cause, NE, Card, Object and so on.

Filtering Current Alarms

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

1. Click + on the Filter bar to unfold the Filter area, as shown below.
2. Clear the checkbox that you do not want to view in the current alarms
window. By default, all objects are checked.
3. Click the Filter icon at the lower right corner.
Sorting Current Alarms

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

In the Current Alarms window, click the column heading in the current
alarm information list to sort the alarm information based on this column.

Acknowledge Current Alarms

Acknowledging an alarm means you are aware of the alarm and will eventually
take the necessary steps to 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 click on the toolbar. Or you can select a current alarm
and right-click on it, then click from the menu.
Export Current Alarms to Files

You can save the current alarms information as a file.
To export current alarms to files:
In the Current Alarms window, click to save the queried current alarm
records as an XML file.

Viewing a Chart for Current Alarms

You can choose to view a chart for current alarms.
To view a chart for current alarms:
In the Current Alarms window, click the icon on the toolbar. A

histogram is displayed showing current alarm information by alarm
severity. Colored blocks in the histogram represent alarms of different
severities.
Manually Synchronizing Alarms

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

To manually synchronize an alarm on an NE:

1. In the Current Alarms window, select the NE in the left object tree.
2. Click the green icon on the toolbar. If you synchronize successfully, a

message appears as shown below.
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 database.
Viewing Historical Alarms History

This section describes how to view historical alarms.
To view historical alarms for a specific NE:

1. Select an NE whose alarm information you want to view in the EMS
topology map. If no NE is selected, current alarm information for all NEs
are displayed by default.
2. Select Fault > Cleared Alarms in the main menu.

3. Click to get all the information to view.
The icons on the alarm toolbar are listed in the following table.
Table 13-3: Icons on the historical alarm toolbar
Icons Description
Gets the information from the equipment.
Displays alarm details.
Shows the current alarms as a list.
Shows the current alarms as a chart.
Selects all the alarms.
Deselects all the alarms.
Deletes the selected alarms.

Exports current alarms as an XML file.
To view historical alarms for a specific card:

3. In the opened window, in the left object tree, select the card whose alarm
information you want to view.

To view historical alarms for a specific object:

3. In the opened window, in the left object tree, click before the tributary
card or port to display all the objects.
4. Select the object whose alarm information you want to view.
Filtering Alarms History

This function is performed in the same way as for Filtering Current Alarms (on
page 13-22).
Sorting Alarms History

This function is performed in the same way as for Sorting Current Alarms (on
page 13-22).
Export Alarms History to Files

This function is performed in the same way as for Export Current Alarms to
Files (on page 13-23).

Managing Cleared Alarms

Cleared alarms refer to historical alarm records on an NE.
To manage cleared alarms:

1. Select an NE whose alarm information you want to view in EMS topology
map. If no NE is selected, cleared alarm information for all NEs is
displayed by default.
2. Select Fault > Cleared Alarms in the main menu. The following window
opens.
4. To view the alarms in a list, click the Show as List button in the
toolbar.

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

6. To view cleared alarm details, select a cleared alarm in the list and click the
Alarm Details button in the toolbar.

7. To export the cleared alarms to files, select in the toolbar. The Save
window opens.
Input a name in the File Name field and click Save to save the file.
8. To delete the cleared alarms records, select the alarms you want to delete in
the list and click in the toolbar.

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. Select an NE whose events you want to view in the EMS topology map. If
no NE is selected, events for all NEs are displayed by default.
2. Select Fault > Events in the main menu. The following window opens.

3. To view event details, select an event in the list and click the Event Details

4. To export the events to files, select in the toolbar. The Save window
opens.
Enter a name in the File Name field and click Save to save the file.
5. To delete events, select the events you want to delete in the list and click
in the toolbar.

Managing Unreported Alarms

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

topology map. If no NE is selected, unreported alarm information for all
NEs is displayed by default.
2. Select Fault > Unreported Alarms in the main menu. The following
window opens.
toolbar.

toolbar.

6. To view unreported alarm details, select a cleared alarm in the list and click
the Alarm Details button in the toolbar.

7. To export the unreported alarms to files, select in the toolbar. The Save
window opens.
8. To delete the unreported alarms records, select the alarms you want to
delete in the list and click in the toolbar.

Managing Archived Alarm Files

This section describes how to manage the archived alarm files.
To manage archived alarm files:

1. In the EMS-BGF main window, select Fault > Archived Files in the main
menu. The following window opens.

2. Click in the toolbar to open an archived file. The following window

opens.
3. Select the file in your local disk and click Open.
toolbar.

toolbar.

6. To view alarm details, select an alarm in the list and click the Alarm
Details button in the toolbar.

7. To export the cleared alarms to files, select in the toolbar. The Save
window opens.
8. To delete alarm records, select the alarms you want to delete in the list and
click in the toolbar.

Managing NE Alarms Log

The NE alarm log records the alarm and event information saved in the NE
equipment. You can view the NE alarm log to access this alarm and event
information. If an NE is disconnected during a certain period, all its alarms and
events generated during this period are recorded in the log.
Viewing NE Alarm Log

The NE alarm log records the alarm and event information saved in the NE
equipment. You can view the NE alarm log to access this alarm and event
information. If an NE is disconnected during a certain period, all its alarms and
events generated during this period are recorded in the log.
To view NE alarm log records:

topology map.
2. Select Fault > NE History in the main menu.
3. Click to retrieve NE alarm log records.

Export NE Alarm Log to Files

You can export NE alarm log as an XML file.
To export NE alarm log records to a file:
In the NE History window, click to save the NE alarm log as an XML

file.

BIT Codes
This section describes how to view the Built In Test (BIT) codes.
To view BIT codes:

1. In the NE shelf view window, select a card in the left tree and then select
Maintenance > BIT Code in the menu. The BIT Code window opens.

Viewing PPI Status

The EMS-BGF 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. Select an E1/E3 card in the object tree list in the NE shelf view window,
and then select the Maintenance working mode. In the opened window,
select the PPI Status tab on the properties area.
2. The PPI status can be refreshed automatically. Select the Refresh Data
Dynamically checkbox and then enter the refresh interval in the Refresh
Interval field. Click Start to refresh the PPI status.
3. Click Stop to terminate the refresh process.
4. Click to refresh the information manually.

Troubleshooting Alarms
This section provides a comprehensive list of EMS-BGF alarms and
maintenance operations relevant to each object in EMS-BGF.
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).
EMS-BGF alarm types include:
Equipment & Process Failure Alarm and Event
Communications Alarm
Service
TMU (Timing)
Threshold Crossing Alarm (TCAs)
External Alarms
PCM & EOP
MPLS Tunnel & tOAM
Ethernet Service (CFM)
Equipment Alarms
This section describes the Equipment & Process Failure Alarms and Events in
EMS-BGF.
Table 13-4: Equipment & Process Failure Alarms and Events

ID Alarm Name Cause Applicable Source Default Description Solutions
ID System Severity
1 Card-Out 75 BG-20, BG-20, BG-30, Critical Card out; no card Insert the card
BG-30, BG-64 all kinds of detected in the slot properly.
BG-64, slots, including as expected.
BG-40 Dslot, Eslot, Tslot
and other slots
which have a
present signal.
2 Unexpected- 77 BG-20, BG-20, BG-30, Warning Card detected in a Pull out the card
Card BG-30, BG-64, BG40 slot with no or shield the
BG-64, physical slots expected slot alarm.
BG-40 assignment.
3 Type- 76 BG-20, BG-20, BG-30, Critical Card type Check and insure
Mismatch BG-30, BG-64, BG-40 slots mismatch: Indicates the card is fixed
BG-64, which have an that the wrong card accurately.
BG-40 expected was inserted in the
assignment slot or D.B.


ID System Severity
4 XIO- 390 BG-30 XIO30 Slots Major Rate of actual
upgrade- XIO30 card is
mismatch higher than that of
expected XIO30
card.
5 Type- 389 BG-20, BG-20, BG-30, Critical Card type cannot be
unknown BG-30, BG-64slots, recognized by the
BG-64 including NVM and system due to:
SFP slots IDPROM
verification
fails. (Not
applicable to
SFP. SFP
IDPROM
verification
fail has a
separate alarm,
SFP-ID Fail.)
Unknown card
type read.
This alarm is
related only to
physical slots.
6 CBUS-Error 451 BG-20, Slot in which card Critical Communication Check and
BG-30, has CPU and real failure with Main ensure that
BG-64, CBUS Control Unit due to the card is
BG-40 CBUS fail or properly in
degrade. place.
Check
whether the
card has
failed, and if
so, reset it.
Upgrade the
card
software.
7 Communicat 658 BG-20, Slot in which card Major SW card does not
ion error BG-30, has no CPU and no respond to Main
BG-64 real CBUS. Control Unit.
BG-30B: XS/Tslot
cards w/o CPU
BG-20B: Dslot
cards w/o CPU


ID System Severity
8 Card-Fail 385 BG-20, Slot in which card Critical BIT-Fail is detected
BG-30, has no CPU and no on the MCP30.
BG-64 real CBUS. Possible reasons
BG-30B: XS/Tslot are: Each slot/card
cards w/o CPU has a BIT-Fail
signal connected to
BG-20B: Dslot
the MCP30. (Eslot
cards w/o CPU
card indicates BIT-
Fail via the PCM
bus.)
This alarm reflects
the BIT-Fail signal
status on the
MCP30.
Card Out should
squelch Card-Fail
alarm and start
monitoring the
alarm again 60 sec
after inserting the
card.
9 BIT-FAIL 381 BG-20, Actual card Critical BIT not passed due
BG-30, to Critical Failure.
BG-64,
BG-40
10 BIT-Not-OK 382 BG-20, Actual card Major BIT not passed due
BG-30, to Major Failure.
BG-64,
BG-40
11 BIT-Degrade 383 BG-20, Actual card Minor BIT not passed due
BG-30, to Performance
BG-64, Degrade.
BG-40
12 BIT- 384 BG-20, Actual card Warning BIT not passed due
Slightly- BG-30, to Performance
Degrade BG-64, Slight Degrade.
BG-40
13 Temperature 401 BG-20, Card which has Major Board temperature Check fan status if
-TC BG-30, temperature sensor. threshold has been there is any fan-
BG-64, BG-20, BG-30, crossed as card is fail alarm or wind
BG-40 BG-64, BG-40 too hot. inlet is blocked.
expansion card Check room
(excluding ESW_E) temperature.
and MXC-20,
XIO30, FCU_30B
should have this
alarm.
14 BG-30E- 393 BG-30, BG-30E Major BG-30E is defined
Not-Installed BG-64 by EMS but not
installed (BG-20,
BG-30, and BG-64
are actually
installed).
15 BG-20E- 386 BG-20 BG-20E Major BG-20E is defined
Not-Installed by the EMS but not
installed (BG-20,
BG-30, and BG-64
are actually
installed).


ID System Severity
16 BG-30E- 394 BG-30, MCP30 Warning BG-30E is not
Detected BG-64 defined but installed
(BG-20, BG-30, and
BG-64 actually
installed).
17 BG-20E- 387 BG-20 MXC-20 Warning BG-20E is not
Detected defined but installed
(BG-20, BG-30, and
BG-64 actually
installed).
18 DC-IN-Fail 391 BG-30, INF-30B /INF-30E Critical DC power-on
BG-64 /INF-64 failure is caused by
not being
connected, power
being off, or low
voltage.
19 DC-Out-Fail 392 BG-30, INF-30B /INF-30E Critical DC power-output
BG-64 /INF-64 failure is caused by
not being
connected, power
being off, or low
voltage.
20 DC-in A Fail 378 BG-20, INF-20B /INF-20E Critical DC power-on
BG-40 /INF-4X-DC Channel 1 failure is
caused by not being
connected, power
being off, or low
voltage.
21 DC-in B Fail 379 BG-20,BG- INF-20B /INF-20E Critical DC power-on
40 /INF-4X-DC Channel 2 failure is
caused by not being
connected, power
being off, or low
voltage.
22 Fan-FAIL 351 BG-20, FCU_30B, Critical The fan has stopped Reset fan
BG-30, FCU_30E, operating due to a unit.
BG-64, FCU_20B (1,2,3,4), fault. Change fan
BG-40 unit.
FCU_20E (1,2,3),
FAN-BG40 Cleaning the
dust mesh.
23 SFP-Out 355 BG-20, SFP slot Critical SFP module does
BG-30, not exist, because it
BG-64, was a) not inserted
BG-40 or b) not detected
because of an error.
24 SFP- 380 BG-20, SFP slot Critical There is a mismatch SFP module type
Mismatch BG-30, of the SFP module or application
BG-64, type or application code mismatch,
BG-40 code (the actual that means the
type or application actual type or
code is different application code is
from the expected different from
value). The SFP expected value.
module will not SFP module will
work by force laser not work by force
shutdown. laser shutdown
when mismatch
occurs.


ID System Severity
25 SFP-ID Fail 672 BG-20, SFP slot Critical It is verified that
BG-30, SFP IDPROM has
BG-64 failed.
26 Warm-Reset 461 BG-20, Card /module Event Warm reset has just
BG-30, occurred. This
BG-64 means that the CPU
and its control
circuit only have
been reset and that
traffic has not been
affected.
27 Cold-Reset 462 BG-20, Card /module Event Cold reset. A reset
BG-30, event means the
BG-64 card has
experienced reset
procedure just now.
Cold reset operation
reset all circuits,
traffic affected.
For
MCP30/MCP30B
cold reset, define
following
parameter: MCP
type.
28 Ver- 466 BG-20, MCP30 /MXC-20 Event The software
Mismatch BG-30, version cannot
BG-64 match the current
NE DB.
29 HS- 685 BG-20 MXC-20 Critical The SW package
Mismatch cannot match the
current HW
configuration.
30 Fan-Speed- 484 BG-20, FCU_30B, Event Fan speed change
change BG-30, FCU_30E
BG-64 FCU_20B,
FCU_20E
31 Alarm-Log- 452 BG-20, NE Event Alarm log overflow
overflow BG-30,
BG-64
32 LCT-Master- 550 BG-20, NE Event LCT login NE -
Login BG-30, occurs only when
BG-64 LCT works in
master mode.
33 LCT-Master- 551 BG-20, NE Event LCT request for
Request BG-30, master work mode.
BG-64
34 LCT-Master- 500 BG-20, NE Event LCT logout NE -
Logout BG-30, occurs only when
BG-64 LCT works in
master mode.
35 CLI-Login 688 BG-20, NE Event CLI log on to the
BG-30, NE
BG-64
36 CLI-Logout 689 BG-20, NE Event CLI log out from
BG-30, the NE
BG-64


ID System Severity
37 CLI-In- 690 BG-20, NE Event CLI enters
Config- BG-30, configuration mode
Mode BG-64
38 CLI-Exit- 691 BG-20, NE Event CLI exit from
Config- BG-30, configuration mode
Mode BG-64
39 Cfg-Restore- 485 BG-20, MCP30 /MXC-20 Event Configuration data
Success BG-30, /MCP64 successfully
BG-64 BG-20, BG-30, restored.
BG-64 traffic cards
40 XIO- 489 BG-30 XIO A Event XIO30-1/4/16
protection- protection switch
switch occurs due to a
detected failure or
maintenance
operations.
41 TP-switch 671 BG-30 Protected card in Event Tributary protection
TPG switch occurs due to
an automatic switch
or maintenance
operations (on the
protected card
only).
42 DB- 490 BG-30 MCP30 /MCP64 Event DB restored from
mismatch NVM is different
from equipment (the
CVW of the DB is
not equal to that of
XIO30).
43 DB-update 491 BG-20, MCP30 /MXC-20 Event NE configuration is
BG-30, synchronized with a
BG-64 new DB.
44 NE-Restart- 465 BG-20, MXC-20, MCP30, Event This event notifies Check
Notification BG-30, MCP64 management of the license.
BG-64 NE restart mode. Check SW.
compatibility
.
45 Cfg-Restore- 687 BG-20, Card Critical A configuration Check if is
Fail BG-30, data restore failure CBUS error.
BG-64 occurred on the card Check and
/module. insure the
version of
MCU unit
and the card
software.
Check and
insure
configuration
is right.
46 MS- 477 BG-40 MS Event An MS protection
Protection- switch event
Switch occurred (for MSP
1+1).
47 Fan-Stop 479 BG-40 Fan Event The fan stopped
working.
48 Fan-Start 480 BG-40 Fan Event The fan started to
work.


ID System Severity
49 SM10-Alarm 354 BG-40 SM10 Card Critical
50 NVM- 692 BG-64, MCP64 Event Inserted NVM card

Replaced BG-30 is not the one that is
extracted before.
51 Card 693 BG-64 MCP64, NVM card Critical NVM(CF) card or
Unlocked MCP64 is present
but not locked.
52 MCP-Start- 703 BG-64, MCP Critical Critical error is
Fail BG-30 detected, MCP SW
fails to start
normally, it enters
safe mode instead.
Parameters are
defined to indicate
detail reason.
53 SM-Ver- 704 BG-20 MXC-20 Critical SM_10E version in
Mismatch MXC-20 is not
consistent with
current system
version.
54 Card- 41 BG-64, MCP Event Card Reassignment
reassigned BG-30 is finished
successfully or fai.
Parameter:
success/fail.
55 Patch-update 724 BG-20, Card Event A hot-patch is
BG-30, activated this card
BG-64 and NE patch
version is updated.
56 PWR- 726 BG-30, MBP Critical The actual power
Consumption BG-64 consumption of the
-TC-Alarm shelf is crossing the
alarm threshold -
the total power
budget of the shelf.
57 PWR- 727 BG-30, MBP Warning The actual power
Consumption BG-64 consumption of the
-TC- shelf is crossing the
Warning warning threshold -
the total power
budget of the shelf
minus MSPC.
58 Cfg-Save- 728 BG-20, MCP/MXC Critical Error or failure
Fail BG-30, happened when NE
BG-64 is saving
configuration DB to
NVM, which may
result in fail to save
DB or DB
corruption.

Communications Alarms
This section describes the Communications Alarms in EMS-BGF.
Table 13-5: Communications Alarms

ID Alarm Cause Applicable Source Default Description Solutions
Name ID System Severity
SPI Layer
1 SPI-LOS 301 BG-20, BG-30, SPI Critical SDH Physical General Reason: Fiber
BG-64, BG-40 Interface Loss broken, Fiber
of Signal. attenuation is overmuch,
photic power over
loading, Card fault.
Check Fiber, check
connection of photic tie-
in, cleaning fiber linker.
If photic power is over
loading, please add
attenuator.
If Card failure, draw and
insert card or change
card.
2 SPI_TF 348 BG-20, BG-30, SPI Critical SDH Physical
BG-64, BG-40 InterfaceTrans
mit Failure.
RS Layer
1 RS-LOF 302 BG-20, BG-30, RS Critical Regenerator Check Fiber.
BG-64, BG-40 Section Loss of Check connection of
Frame. photic tie-in, cleaning
fiber connection.
If Card failed, draw and
insert card or change
card.
2 RS-OOF 303 BG-20, BG-30, RS Critical Regenerator General Reason: Fiber
BG-64, BG-40 Section Out of broken, Fiber
Frame. attenuation is overmuch,
photic power over
loading, Card fault.
Check Fiber, check
connection of photic tie-
in, cleaning fiber
connection.
If photic power is over
loading, please add
attenuator.
If Card failed, Reset or
Draw and insert card or
change card.
3 RS-TIM 304 BG-20, BG-30, RS Major Regenerator Check J0 byte of this
BG-64, BG-40 Section Trace site and this of the other
Identification(J site. If J0 byte of two
0) Mismatch. sites are different,
modify config to make
same. If same, then card
failed, change card.
Check fiber connection.


MS Layer
1 MS-AIS 305 BG-20, BG-30, MS Major Multiplex Check the line card of
BG-64, BG-40 Section Alarm the other site, Reset or
Indication Draw and insert card or
Signal change card to view if
alarm is clear or not.
Check the line card of
the this site, Reset or
Draw and insert card or
change card to view if
2 MS-RDI 306 BG-20, BG-30, MS Minor Multiplex If the line card of the
BG-64, BG-40 Section Remote other site has SPI-LOS
Defect /RS-LOF /MS-AIS
Indication alarm, then after
handling these alarms,
the MS-RDI alarm of
this site is clear.
If the line card of the
other site has not SPI-
LOS /RS-LOF /MS-AIS
alarm, then this card
failed. Reset or Draw
and insert card or
change card to view if
The feber is seldom
broked, because only
transmit fiber is broken
but receive fiber is well,
could have this alarm. If
fibers of BG-20, BG-30,
BG-64 are broked, it
could not have this
alarm, it is important to
check fiber connect
between this site and the
other site.

3 MS-REI 307 BG-20, BG-30, MS Mask Multiplex
BG-64, BG-40 Section Remote
Error Indication
4 MS-SD 617 BG-20, BG-30, MS Minor MS Signal Cleaning photic tie-in
BG-64 Degrade and check photic power
to check if photic power
attenuation is overmuch
or photic power is over
loading.
Check the clock config
of whole net.
Set loop option to
location fault of two
sites, then change card.


5 MS- 618 BG-20, BG-30, MS Major MS Excessive If it Has B1 error code,
EXC BG-64 Bit Error please Handle B1 error
code.
If it has only B1 error
code, generBG-20, BG-
30, BG-64y Line card
failed. Change card.
Check If the temperature
of NE is too High.
If no above, please
change card.
6 MSP- 642 BG-20, BG-30, MS Major MSP Protocol
PM BG-64, BG-40 mismatch
7 MS- 171 BG-20, BG-30, MS- Event MS protection

protectio BG-64 SPRing switch event
n-switch PG (for MSP 1+1)
8 MS- 709 BG-30, BG-64 MS- Event A MS-SPRing
SPRing- SPRing switching &
Switch PG bridge action
has been
executed
successfully
Parameter:
West/east
9 MS- 710 BG-30, BG-64 MS- Event A MS-SPRing
SPRing- SPRing switching &
Switch- PG bridge action is
Release released
Parameter:
West/east
10 West- 711 BG-30, BG-64 MS- Major Inconsistent
Inconsist SPRing APS codes
en-APS- PG received
Codes
11 West- 712 BG-30, BG-64 MS- Minor Default K1/K2
Default- SPRing bytes received
K-Bytes PG
12 West- 713 BG-30, BG-64 MS- Major Improper APS
Improper SPRing codes received
-APS- PG
Codes
13 East- 720 BG-30, BG-64 MS- Major Inconsistent
Inconsist SPRing APS codes
en-APS- PG received
Codes
14 East- 721 BG-30, BG-64 MS- Minor Default K1/K2
Default- SPRing bytes received
K-Bytes PG
15 East- 722 BG-30, BG-64 MS- Major Improper APS

Improper SPRing codes received
-APS- PG
Codes
16 APS- 714 BG-30, BG-64 MS- Critical Process fail in
Channel- SPRing APS controller
Proc-Fail PG


17 Node- 715 BG-30, BG-64 MS- Critical Node ID is
ID- SPRing unexpected and
Mismatc PG mismatched
h according to
ring map
18 MS- 716 BG-30, BG-64 MS- Warning HO or LO VC-
SPRing- SPRing 4 squelch action
Squelch PG happens
H15P Layer
1 AU-LOP 308 BG-20, BG-30, AU4 Major Administration Check the route
BG-64, BG-40 Unit Loss of configuration of the
Pointer other site,If it has error,
please set correct
configuration.
Check the status of CLK
or HBIX Card of the
other card. Switch over
it or reset it.
Set loop on STM-N card
to location the error site,
then handle it.
With the error
site,Swithc over the Bix
card or Reset or Draw
and insert card. If alarm
is not clear, then change
card.
2 HP- 309 BG-20, BG-30, VC4 Major High Order GenerBG-20, BG-30,
LOM BG-64, BG-40 Path Loss of BG-64y the other site
Multi-frame has fault, such as Bix
card failed or mismatch
of C2 byte.
Check route
configuration of two
sites. If configuration
error, modify
configuration.
Check if the other site
has other alarm. If has
error, set loop to locate
it, then change card.
Set STM-n card loop of
this site to check if has
fault. If has fault, then
change card.


3 HP-AIS 310 BG-20, BG-30, VC4 Major High Order If it Has MS-AIS /LOS
BG-64, BG-40 Path Alarm /RS-LOF , please
Indication Handle MS-AIS /LOS
Signal, i.e., /RS-LOF.
AU-AIS The other site has no
route configure.
The other site has error
route configure.
Set loop option to
sites, then handle on this
site.
With the error site,
Swithc over the Bix card
or Reset or Draw and
insert card. If alarm is
not clear, then change
card.
4 HP-RDI 311 BG-20, BG-30, VC4 Minor High Order If it has High order path
BG-64, BG-40 Path Remote Alarm, please handle
Defect these alarms.
Indication If it has AU-AIS or AU-
LOP on the line card of
the other site, handle this
these alarms.
If it has no alarm on the
other site, then card
failed, Reset or Draw
and insert card or
change card.
5 HP-REI 312 BG-20, BG-30, VC4 Mask High Order Check if the other site
BG-64, BG-40 Path Remote has B3 error code,if it
Error Indication has alse B1 /B2 error
code , then attenuation is
overmuch or Line card
failed. Location is same
whit the location of RS-
LOF.
If the other site only has
a little of B3 error code,
GenerBG-20, BG-30,
BG-64y no fiber fault, it
is the error of NE
equipment. Please check
the Bix card or tributary
card of the other site.
Check the Bix card or
tributary card of the this
site.
Check the connect to
earth of equipment.
Insure there is no
disturbance near the NE.


6 HP-TIM 313 BG-20, BG-30, VC4 Minor High Order Check trace identifier
BG-64, BG-40 Path Trace byte of this site and this
Identification of the other site. If trace
(J1) Mismatch identifier byte of two
sites are different,
Check route
error, modify
configuration. If no
error, then then card
7 HP- 314 BG-20, BG-30, VC4 Minor High Order Check configuration,
UNEQ BG-64, BG-40 Path insure the sending c2 is
Unequipped right. If error, modify
error, then card failed,
change card.
Set loop option to
sites, then handle on this
site.
8 HP-SLM 315 BG-20, BG-30, VC4 Minor High Order Check signal label of
BG-64, BG-40 Path Signal this site and this of the
Label(C2) other site. If signal label
Mismatch of two sites are different,
Check route
error, modify
error, then then card
9 HP-SD 619 BG-20, BG-30, VC4 Minor VC-4 Signal Cleaning photic tie-in
BG-64 Degrade and check photic power
to check if photic power
attenuation is overmuch
or photic power is over
loading.
Check the clock config
of whole net.
Set loop option to
sites, then change card.


10 HP-EXC 620 BG-20, BG-30, VC4 Major VC-4 Excessive If it Has B1 error code,
BG-64 Bit Error please Handle B1 error
code.
If it has only B1 error
code, generBG-20, BG-
30, BG-64y Line card
failed. Change card.
Check if the temperature
of NE is too High.
If no above, please
change card.
LP Layer
1 TU-LOP 316 BG-20, BG-30, TU3/TU Major Tributary Unit Check the configuration
BG-64, BG-40 12 Loss of Pointer of the tributary or Bix
card. If erroneous,
modify the
configuration.
Set a loop to check if it
has an inverse point. If
yes, interchange the
tributary and the Bix
card.
2 LP-AIS 317 BG-20, BG-30, VC3/VC Major Low Order Path If it has an HP alarm,
BG-64, BG-40 12 Alarm handle the HP alarm
Indication first.
Signal, i.e, TU- Check the route
AIS configuration of the two
sites. If there is a
configuration error,
modify the
configuration.
If the Bix or tributary
card failed, reset or
replace it.
3 LP-RDI 318 BG-20, BG-30, VC3/VC Minor Low Order Path Check the trace
BG-64, BG-40 12 Remote Defect identifier byte of this
Indication and the other site. If they
are different, modify the
configuration so both are
the same. If they are the
same, then the card
failed. Replace the card.
Check the route
configuration of the two
modify the
configuration. If not,
then the card failed.
Replace the card.
4 LP-REI 319 BG-20, BG-30, VC3/VC Mask Low Order Path Check the route
BG-64, BG-40 12 Remote Error configuration of the two
Indication sites. If there is a
modify the
configuration.
Check the attribute
tributary cards.


5 LP-TIM 321 BG-20, BG-30, VC3/VC Minor Low Order Path Check the trace
BG-64, BG-40 12 Trace identifier byte of this
Identification and the other site. If they
Mismatch are different, modify the
configuration so both are
same, then the card
Check the route
modify the
Replace the card.
6 LP- 322 BG-20, BG-30, VC3/VC Minor Low Order Path Check the route
UNEQ BG-64, BG-40 12 Unequipped configuration of the two
modify the
configuration.
Check the attribute
tributary cards.
7 LP-SLM 323 BG-20, BG-30, VC3/VC Minor Low Order Path Check the signal label of
BG-64, BG-40 12 Signal Label this and the other site. If
Mismatch it is different, modify the
configuration so they are
same, then the card
Check the route
modify the
Replace the card.
8 LP- 615 BG-20, BG-30, VC12 Minor Low Order Path
ESLM BG-64, BG-40 Extended
Signal Label
(K4) Mismatch
9 LP-SD 621 BG-20, BG-30, VC- Minor VC-3/VC-12
BG-64 3/VC-12 Signal Degrade
10 LP-EXC 622 BG-20, BG-30, VC- Major VC-3/VC-12
BG-64 3/VC-12 Excessive Bit
Error
11 SNC- 483 BG-20, BG-30, VC- Event SNCP Selector
Protectio BG-64 4/VC-3 switched due to
n- /VC-12 SD/SF or
Switch maintenance


PPI Layer
1 PPI-LOS 324 BG-20, BG-30, PPI(E1/ Critical PDH Physical Set the loop option to
BG-64, BG-40 E3/DS3) Interface Loss locate it:
, C37.94 of Signal Locate the card and path
port of the alarm on the GUI.
Set a self-loop on the
PDH port. If the alarm
does not clear, check the
connection of the PDH
card or replace the card.
If, after setting the loop
on the PDH port, the
alarm clears, the NE is
fine. Then set a loop on
the PDH port from the
DDF to the NE. If the
alarm does not clear, the
cable between the DDF
and the NE equipment
has failed.
If, after setting a loop on
the PDH port from the
DDF to the NE, the
alarm is clear, then the
cable between the DDF
to the NE equipment is
fine. Then set the loop
on the commutative
equipment and check if
that has failed.
2 PPI-AIS 325 BG-20, BG-30, PPI Major PDH Physical Check all the equipment
BG-64, BG-40 (E1/E3/ Interface connected with an NE,
DS3) Alarm such as the
Indication commutative/PCM
Signal equipment or router.
Set a self-loop on the
PDH port. If the alarm
clears, the equipment
connected with the NE
failed. If the alarm did
not clear, then the card
failed, Replace the card.
Check the cable
connections.
3 PPI-LOF 326 BG-20, BG-30, Framed Major Loss of Frame
BG-64, BG-40 PPI (only For
Framed Mode)
4 PPI- 668 BG-20, BG-30, Framed Major Loss of multi-
LOMF BG-64 PPI Frame (only
For Framed
Mode)
5 PPI-RAI 327 BG-20, BG-30, Framed Warning Remote Alarm Handle the alarm on the
BG-64, BG-40 PPI Indication (only PCM equipment.
For Framed It is possible that the
Mode) tributary card of this site


6 PPI-SD 623 BG-20, BG-30, Framed Minor 2M Signal
BG-64 PPI Degrade (only
For Framed
Mode)
7 PPI- 624 BG-20, BG-30, Framed Major 2M Excessive
EXC BG-64 PPI Bit Error (only
For Framed
Mode)
ETY LAN Port (FE /GE)
1 GE-LOS 637 BG-20, BG-30, LAN Critical Optical loss of

BG-40 Port signal on GE
(only GE port of
optical), ESW_2G_8F_E
only for
ESW_E
2 PHY- 673 BG-20, BG-30, LAN Critical Optical signal
LOS BG-64 port loss on receive
(optical side of GbE or
GE or FX optical port
FX)
3 Link- 42 BG-20, BG-30, LAN Major Link fail Check the Ethernet line
Fail BG-64, BG-40 Port (detected in the connection and change
Ethernet PHY) the line.
Reset the external
equipment and change
the external equipment.
Reset the Ethernet card
or change it.
4 AN 640 BG-20, BG-30, LAN Major Auto-
Ability BG-64 Port negotiation
Mismatc result in link
h capacity being
not fully
utilized
5 OAM 659 BG-20, BG-30, LAN Minor If Discovery
Discover BG-64 port (L2) process cannot
y fail successfully
complete,
Discovery
Failed alarm is
raised.
6 OAM 660 BG-20, BG-30, LAN Major After Discovery
Link- BG-64 port (L2) process
Lost completes, both
local and
remote ports
once per second
transmit
OAMPDUs to
each other. If
no OAMPDU is
received for 5
second Link
Lost alarm
rises.


7 OAM 661 BG-20, BG-30, LAN Minor If local port
Remote BG-64 port (L2) receives
Link OAMPDU with
Fault Link Fault flag
be set.
8 OAM 662 BG-20, BG-30, LAN Major when there are
Local BG-64 port (L2) problems
Link detected on the
Event link.
9 OAM 663 BG-20, BG-30, LAN Minor If local port
Remote BG-64 port (L2) receives Link
Link Event
Event OAMPDU from
the remote port.
10 OAM 664 BG-20, BG-30, LAN Event Issued when
Local BG-64 port (L2) port enters local
loop loopback mode
back as a result of
remote
loopback
request
11 OAM 670 BG-20, BG-30, LAN Event Issued when
Local BG-64 port (L2) port local
loop loopback is
back released as a
release result of remote
loopback
release request
12 Port-Is- 719 BG-20, BG-30, LAN Warning External loop
Looped BG-64 port (L2) back is detected
on the port.
This loop back
may be caused
by external
loopback cable,
facility
loopback on
partner port.
13 AN-Fail 678 BG-20, BG-30, ETY Major Auto-
BG-64 port (FE, negotiation fail
GE)
14 Remote- 679 BG-20, BG-30, ETY Major Remote link
Fault BG-64 port (FE, fault (PHY MII
GE) status
indication)
15 Master- 725 BG-20, BG-30, ETY Major Master/slave
Slave- BG-64 port configuration
Config- (GE/100 fault, local PHY
Fault 0BT) operating mode
is same as that
of remote/peer
PHY, i.e., both
are master or
slave.


WAN Port (VCG &EOS)
1 LOFD 335 BG-20, BG-30, EOS/EO Critical Loss of Frame Check and ensure the
BG-64, BG40 P Delineation route configuration,
encapsulation protocol,
and additional attribute
of the LCAS member
are the same on the two
sites.
Reset or replace the card
of the other site.
Set the VC-4 loop
option to locate the fault
on the two sites, and
then withdraw and
reinsert or replace the
card.
2 CSF-1 638 BG-20, BG-30, EOS/EO Major Client Signal
BG-64, BG40 P (GFP) Failure (Type 1,
loss of signal)
3 CSF-2 639 BG-20, BG-30, EOS/EO Major Client Signal
BG-64, BG40 P (GFP) Failure (Type 2,
loss of sync)
4 UPI- 654 BG-20, BG-30, EOS/EO Major User payload
Error BG-64 P (GFP) identifier error
5 EXI- 339 BG-20, BG-30, EOS/EO Major Extension
Mismatc BG-64, BG40 P (GFP) header
h indication
mismatch
6 LOA 340 BG-20, BG-30, VCG Critical VCG Loss of Check if the VCG
BG-64, BG40 Alignment member has multi-route
transmission and
whether the difference
of multi-route exceeds
the capability of the
card. If so, modify the
route configuration to
avoid it.
Set the renewed route
configuration.
Reset or replace the
Ethernet card of the
sites.
7 TLC 613 BG-20, BG-30, VCG/LA Critical Total Loss of
BG-64, BG40 G Capacity
8 PLC 641 BG-20, BG-30, LAG Major Partial Loss of
BG-64, BG40 Capacity
(bidirectional)
9 LAG- 643 BG-20, BG-30, LAG Critical LAG Link
Link- BG-64, BG40 down
down
10 PLCr 614 BG-20, BG-30, VCG Major Partial Loss of
BG-64, BG40 Capacity on RX
side
11 PLCt 616 BG-20, BG-30, VCG Major Partial Loss of
BG-64, BG40 Capacity on TX
side


12 LP-LOM 341 BG-20, BG-30, VC12/V Critical Low Order Path
BG-64, BG40 C3 Loss of Multi-
(VCAT) frame
13 LP-SQM 344 BG-20, BG-30, VC12/V Major Low Order Path GenerBG-20, BG-30, or BG-
BG-64, BG40 C3 SQ Number 64y route configuration
(VCAT) Mismatch failed. Please check it.
14 HP- 347 BG-20, BG-30, VC-4 Major High Order GenerBG-20, BG-30, or BG-
SQM BG-64, BG40 (VCAT) Path SQ 64y route configuration
Number failed. Please check it.
Mismatch
15 LCAS- 342 BG-20, BG-30, E1/VC1 Major LCAS member
Fail BG-64, BG40 2/VC3/V ADD/REMOV
C-4 E Failed
(VCAT)
16 LCAS- 343 BG-20, BG-30, E1/VC1 Major LCAS protocol
CRC- BG-64, BG40 2/VC3/V data package
Error C-4 CRC Error
(VCAT)
17 Bridge- 487 BG-20, BG-30, L2 Event Topology of
topo- BG-64 bridge span tree
change instance
changed
18 MhPG- 488 BG-40 MhPG Event Multi-homing
Switch access port
group Switch
19 New- 481 BG-40 FE_L12 Event New root
Root bridge
notification
20 Topolog 482 BG-40 FE_L12 Event Topology
y- change
Change notification
21 Root- 676 BG-20, BG-30, L2 Event Root port of
port- BG-64 bridge STP change
change
22 L2 677 BG-20 MESW_ Event MESW_6F
Traffic 6F traffic get
Recover recovered from
ed a fatal error
(Queue stops
working due to
unknown
reason)
23 Port-Q- 686 BG-20 MESW_ Critical FE LAN port of
Blocked 6F, MESW_6F and
ESW_2 ESW_2G_8F_E
G_8F_E get blocked due
FE LAN to a fatal error
port (Queue stops
working)

Service Alarms
This section describes the Service Alarms in EMS-BGF.
Table 13-6: Service Alarms

ID Alarm Name Cause Applicable Source Default Description
ID System Severity
1 SD 3 BG-40 VC4/MS Minor Signal Degrade
2 EXC 12 BG-40 VC4/MS Major Excessive Bit Error
3 LP-RFI 320 BG-40 VC3/VC12 Warning Remote failure indication
4 Link-Error 43 BG-40 PHY Major Link failure
5 CSF 337 BG-40 EOS Major Client signal fail
6 CID-Error 338 BG-40 EOS Major Channel ID mismatch
7 TS-LTI 328 BG-40 SPI/PPI/T3 Critical Loss of input of timing source
8 TS-OOR 334 BG-40 SPI/PPI/T3 Minor Out of range of timing source
Timing Alarms
This section describes the Timing (TMU) Alarms in EMS-BGF.
Table 13-7: Timing Alarms

ID System Severity
1 TS1-LTI 625 BG-20, BG-30, TMU/SM_10E Major Timing Source 1 Loss of
BG-64 Timing Input
2 TS1-OOR 626 BG-20, BG-30, TMU/SM_10E Major Timing Source 1 Frequency
BG-64 Out Of Range
3 TS2-LTI 627 BG-20, BG-30, TMU/SM_10E Major Timing Source 2 Loss of
BG-64 Timing Input
4 TS2-OOR 628 BG-20, BG-30, TMU/SM_10E Major Timing Source 3 Frequency
BG-64 Out Of Range
5 TS3-LTI 629 BG-20, BG-30, TMU Major Timing Source 3 Loss of
BG-64 Timing Input
6 TS3-OOR 630 BG-20, BG-30, TMU Major Timing Source 3 Frequency
BG-64 Out Of Range
7 TS4-LTI 631 BG-20, BG-30, TMU Major Timing Source 4 Loss of
BG-64 Timing Input
8 TS4-OOR 632 BG-20, BG-30, TMU Major Timing Source 4 Frequency
BG-64 Out Of Range
9 No- 630 BG-20, BG-30, TMU/SM_10E Critical No Available Timing source,
Available- BG-64, BG-40 BG-20, BG-30, BG-64 timing
TS source selected are lost or
Unusable
10 T3-LOF 633 BG-20, BG-30, TMU(2Mb/s) Minor Los of Frame, only for
BG-64 framed 2Mb/s T3 Input
11 T3-AIS 634 BG-20, BG-30, TMU(2Mb/s) Minor Alarm indication signal of
BG-64 2Mb/s T3 input
12 T3-1-LOS 635 BG-20, BG-30, TMU Minor 2Mb/s loss of Signal
BG-64


ID System Severity
13 T3-2-LOS 636 BG-20, BG-30, TMU Minor 2MHz loss of Signal
BG-64
14 T4-LTO 606 BG-20, BG-30, TMU Minor Loss of Timing Output (T4
BG-64, BG-40 Output is closed)
15 TM- 652 BG-30, BG-64 XIO30-A TMU Minor Timing mode of main TMU is
unsynchroni different from that of standby
zed TMU (e.g., main is locked to
T3 and standby is locked to
XIO30-A)
16 Timing- 163 BG-20, BG-30, TMU/SM_10E Event Timing source reference
Source- BG-64 switch
Switch
17 Timing- 164 BG-20, BG-30, TMU/SM_10E Event Timing mode switch (such as,
Mode- BG-64 freerun -> locked, locked-
Switch >holdover)
18 LOL 467 BG-20, BG-30, TMU/SM_10E Event Current Timing Source Loss
BG-64 of Locked
19 QL-Change 717 BG-20, BG-30, TMU Event Timing source quality level
BG-64 change
Threshold Crossing Alarms

This section describes the Threshold Crossing Alarms (TCAs) in EMS-BGF.
Table 13-8: Threshold Crossing Alarms

ID System Severity
1 Laser-Temp-High 362 BG-20, BG-30, SFP Critical Laser Temperature is
BG-64, BG-40 crossing high alarm
threshold
2 Laser-Temp-Low 363 BG-20, BG-30, SFP Minor Laser Temperature is
BG-64, BG-40 crossing low alarm threshold
3 SFP-VCC-High 364 BG-20, BG-30, SFP Critical SFP VCC is crossing high
BG-64, BG-40 alarm threshold
4 SFP-VCC-Low 365 BG-20, BG-30, SFP Critical SFP VCC is crossing low
BG-64, BG-40 alarm threshold
5 TX-LBC-High 366 BG-20, BG-30, SFP Major Laser TX Bias current is
threshold
6 TX-LBC-Low 367 BG-20, BG-30, SFP Minor Laser TX Bias current is
7 TX-oPower-High 368 BG-20, BG-30, SFP Major TX Optical Power is
threshold
8 TX-oPower-Low 369 BG-20, BG-30, SFP Critical TX Optical Power is
9 RX-oPower-High 609 BG-20, BG-30, SFP Major RX Optical Power is
threshold
10 RX-oPower-Low 610 BG-20, BG-30, SFP Critical RX Optical Power is


ID System Severity
11 Laser-Temp-H-Warning 370 BG-20, BG-30, SFP Minor Laser Temperature High
BG-64, BG-40 Warning
12 Laser-Temp-L-Warning 371 BG-20, BG-30, SFP Warning Laser Temperature Low
13 SFP-VCC-H-Warning 372 BG-20, BG-30, SFP Warning VCC High Warning
BG-64, BG-40
14 SFP-VCC-L-Warning 373 BG-20, BG-30, SFP Major VCC Low Warning
BG-64, BG-40
15 TX-LBC-H-Warning 374 BG-20, BG-30, SFP Warning Laser Bias High Warning
BG-64, BG-40
16 TX-LBC-L-Warning 375 BG-20, BG-30, SFP Warning Laser Bias Low Warning
BG-64, BG-40
17 TX-oPower-H-Warning 376 BG-20, BG-30, SFP Warning Output Optical Power High
18 TX-oPower-L-Warning 377 BG-20, BG-30, SFP Major Output Optical Power Low
19 RX-oPower-H-Warning 611 BG-20, BG-30, SFP Warning Input Optical Power High
20 RX-oPower-L-Warning 612 BG-20, BG-30, SFP Major Input Optical Power Low
21 UAT-NE 501 BG-20, BG-30, RS/MS/VC4 Major UAS Start Near End
BG-64, BG-40 /VC3/VC12/P
PI
22 UAT-FE 214 BG-20, BG-30, MS/VC4/VC Major UAS Start Far End
BG-64, BG-40 3 /VC12
23 ESTC-15M-NE 201 BG-20, BG-30, RS/MS/VC4 Minor ES in 15 Minutes Threshold
BG-64, BG- /VC3/VC12/P Crossing Near End
40BG-20, BG- PI
30, BG-64, BG-
40
24 SESTC-15M-NE 202 BG-20, BG-30, RS/MS/VC4 Major SES in 15 Minutes
BG-64, BG-40 /VC3/VC12/P Threshold Crossing Near
PI End
25 BBETC-15M-NE 203 BG-20, BG-30, RS/MS/VC4 Minor BBE in 15 Minutes
PI End
26 UASTC-15M-NE 215 BG-20, BG-30, RS/MS/VC4 Major UAS in 15 Minutes
PI End
27 CV-15M-NE 524 BG-20, BG-30, PPI Major CV in 15 Minutes
BG-64 Threshold Crossing Near
End
28 ESTC-15M-FE 207 BG-20, BG-30, MS/VC4/VC Warning ES in 15 Minutes Threshold
BG-64, BG-40 3 /VC12 Crossing Far End
29 SESTC-15M-FE 208 BG-20, BG-30, MS/VC4/VC Warning SES in 15 Minutes
BG-64, BG-40 3 /VC12 Threshold Crossing Far End
30 BBETC-15M-FE 209 BG-20, BG-30, MS/VC4/VC Warning BBE in 15 Minutes
BG-64, BG-40 3 /VC12 Threshold Crossing Far End
31 OFSTC-15M 502 BG-20, BG-30, RS Major OFS in 15 Minutes
BG-64, BG-40 Threshold Crossing
32 PPJCTC-15M 503 BG-20, BG-30, AU4/TU12 Minor PPJC in 15 Minutes


ID System Severity
33 NPJCTC-15M 504 BG-20, BG-30, AU4/TU12 Minor NPJC in 15 Minutes
34 ESTC-24H-NE 204 BG-20, BG-30, RS/MS/VC4 Minor ES in 24 Hours Threshold
BG-64, BG-40 /VC3/VC12/P Crossing Near End
PI
35 SESTC-24H-NE 205 BG-20, BG-30, RS/MS/VC4 Major SES in 24 Hours Threshold
PI
36 BBETC-24H-NE 206 BG-20, BG-30, RS/MS/VC4 Minor BBE in 24 Hours Threshold
PI
37 UASTC-24H-NE 216 BG-20, BG-30, RS/MS/VC4 Major UAS in 24 Hours Threshold
PI
38 CV-24H-NE 525 BG-20, BG-30, PPI Major CV in 24 Hours Threshold
BG-64 Crossing Near End
39 ESTC-24H-FE 210 BG-20, BG-30, MS/VC4/VC Warning ES in 24 Hours Threshold
BG-64, BG-40 3/VC12 Crossing Far End
40 SESTC-24H-FE 211 BG-20, BG-30, MS/VC4/VC Warning SES in 24 Hours Threshold
41 BBETC-24H-FE 212 BG-20, BG-30, MS/VC4/VC Warning BBE in 24 Hours Threshold
42 OFSTC-24H 505 BG-20, BG-30, RS Major OFS in 24 Hours Threshold
BG-64, BG-40 Crossing
43 PPJCTC-24H 506 BG-20, BG-30, AU4/TU12 Minor PPJC in 24 Hours Threshold
BG-64, BG-40 Crossing
44 NPJCTC-24H 507 BG-20, BG-30, AU4/TU12 Minor NPJC in 24 Hours
45 GFP-R-ErrPkts-TC-15M 526 BG-20, BG-30, EoS Major Rx Error Pkts 15min
46 R-ErrPkts-TC-15M 521 BG-20, BG-30, L1/L2 LAN Major Rx Error Pkts 15min
BG-64, BG-40 Port and L2 Threshold Crossing
WAN port
47 R-BCPkts-TC-15M 522 BG-20, BG-30, L1/L2 LAN Major Rx Broadcast Pkts 15min
WAN port
48 R-MCPkts-TC-15M 523 BG-20, BG-30, L1/L2 LAN Major Rx Multicast Pkts 15min
WAN port
49 McVpnDropOctets 665 BG-20, BG-30, VSI Warning Storm Control Dropped
BG-64 Octets, Number of multicast,
broadcast, and unknow
destination unicast bytes
dropped by BSC policer of
this VPN, exceeds threshold.
50 VPNQuotaDropPackets 666 BG-20, BG-30, VSI Warning Packets dropped due to FIB
BG-64 quota exceed threshold
51 LowClassDiscardPPS 667 BG-20, BG-30, VSI Warning Percentage of low class
BG-64 packets discards due to
throughput control
52 MAC-Move 723 BG-20, BG-30, VSI Major The number of MAC move
BG-64 events in 15-min counter
exceeds threshold


ID System Severity
53 DCC-Rcv-Deg 519 BG-20, BG-30, MCP30 Major Receive DCC Degrade
BG-64, BG-40 /MXC-20
COM DCC
channel
54 DCC-Src-Deg 520 BG-20, BG-30, MCP30 Major Send DCC Degrade
BG-64, BG-40 /MXC-20
COM DCC
channel
55 Pkt-Los 508 BG-40 PHY Minor
56 Pkt-Rcv-Bad 509 BG-40 PHY Minor
57 Pkt-Src-Bad 510 BG-40 PHY Minor
58 MAC-All-Collision 511 BG-40 PHY Minor
59 Pkt-CRC-Error 513 BG-40 PHY Minor
External Alarms
This section describes the External Alarms in EMS-BGF.
Table 13-9: External Alarms

ID System Severity
1 User-defined- 356 BG-20, BG-30, External Major User definition alarm 1
Alm-1 BG-64, BG-40 (External Alarm 1)
PCM and EOP Alarms

This section describes the PCM and EOP Alarms in EMS-BGF.
Table 13-10: PCM and EOP Alarms

ID System Severity
1 Codir-LOS 644 BG-20, BG-30, Co-directional Critical Loss of signal on
BG-64 64K interface of
SM_Codir_4E
2 E1-LOS 645 BG-20, BG-30, E1 (PCM, EOP, Major E1 loss of signal
BG-64 OW, etc.)
3 E1-AIS 646 BG-20, BG-30, E1 (PCM, EOP, Major Alarm indication signal
BG-64 OW, etc.) of E1
4 E1-LOF 647 BG-20, BG-30, Framed E1 Major Loss of Frame (only For
BG-64 Framed Mode)


ID System Severity
5 E1-CAS-LOMF 674 BG-20, BG-30, Framed E1 Major Loss of CAS multi-
BG-64 (PCM30) Frame (only For
PCM30), CAS means
channel associated
signaling
6 E1-CRC-LOMF 675 BG-20, BG-30, Framed E1 Major Loss of CRC-4 multi-
BG-64 (PCM30CRC or Frame (only For PCM
PCM31CRC) with CRC)
7 E1-RAI 649 BG-20, BG-30, Framed E1 Minor Remote Alarm
BG-64 Indication (only For
Framed Mode)
8 E1-SD 650 BG-20, BG-30, Framed E1 Minor 2M Signal Degrade
BG-64 (only For Framed
Mode)
9 E1-EXC 651 BG-20, BG-30, Framed E1 Major 2M Excessive Bit Error
BG-64 (only For Framed
Mode)
10 Yellow 705 BG-20, BG-30, C37.94 port Minor Remote defect
BG-64 indication
11 N-Mismatch 706 BG-20, BG-30, C37.94 port Major This alarm exists only
BG-64 in manual mode. When
received N from line is
bigger than N
configured, there alarm
should be declared
12 Line-N-Error 707 BG-20, BG-30, C37.94 port Major The N value received
BG-64 from line is not a valid
value. The valid value
should be 1~12
13 E1-N-Error 708 BG-20, BG-30, C37.94 port Major Unable to get valid OH
BG-64 (N and signaling) from
E1 channel (actually
from internal 4M-PCM)
and OH channel is not
all ones, exist only in
transparent mode. OH
channel not configured
or E1-LOF SHOULD
NOT result in this alarm

MPLS Tunnel and tOAM Alarms

This section describes the MPLS Tunnel and tOAM Alarms in EMS-BGF.
Table 13-11: MPLS Tunnel and tOAM Alarms

ID System Severity
1 OAM-LOCV 680 BG-20, BG-30, MPLS tunnel Major Loss of Connectivity
BG-64 Verification
2 OAM-TTSI- 681 BG-20, BG-30, MPLS tunnel Major Tunnel Trail Termination
Mismerge BG-64 Source Identifier Mismerge
3 OAM-TTSI- 682 BG-20, BG-30, MPLS tunnel Major Tunnel Trail Termination
Mismatch BG-64 Source Identifier Mismatch
4 OAM-Excess 683 BG-20, BG-30, MPLS tunnel Major Excessive CV or FFD packets
BG-64
5 PerfLspOutWredR 684 BG-20, BG-30, MPLS tunnel Minor WRED discard ratio in current
atioPpm-TC BG-64 out segment monitored interval for this out-
segment is crossing threshold
Ethernet Service Alarms

This section describes the Ethernet Service Alarms in EMS-BGF.
Table 13-12: Ethernet Service Alarms

ID System Severity
1 INVALID_MAID 694 BG-20, BG- MEP Major Invalid MA ID
30, BG-64 Receiving CCM frame with
invalid MA_ID or on port that is
not registered in VSI
2 LOW_LEVEL_CCM 695 BG-20, BG- MEP Major Received lower level CCM
30, BG-64 Receiving CCM frame with
valid MA_ID and invalid
MEP_ID,invalid CCM_Period
3 MEP_NOT_CONFIGUR 696 BG-20, BG- MEP Major Received unexpected MEP ID
ED 30, BG-64
4 MEP_SAME_MEPID 697 BG-20, BG- MEP Major Received duplicate MEP ID
30, BG-64
5 CCM_INTERVAL_MIS 698 BG-20, BG- MEP Major Incorrect CCM Interval
MATCH 30, BG-64
6 RX_CCM_TIMER_EXPI 699 BG-20, BG- MEP Major CCM timer expired
RED 30, BG-64 /Connectivity Loss
Failing to receive valid CCM
frame from one of the remote
MEPs of MA during the time
period of 3.5 x MA_CCMPeriod
7 MEP_INTERFACE_STA 700 BG-20, BG- MEP Minor AC interface down
TUS 30, BG-64 One or more of the remote
MEPs is reporting a failure in its
interface state (not isUp).
8 MEP_PORT_STATUS 701 BG-20, BG- MEP Minor AC port down


ID System Severity
30, BG-64
9 MEP_RDI 702 BG-20, BG- MEP Minor Received CCM with RDI bit
30, BG-64 Indicating the aggregate health
of the remote MEPs.
ERPS Alarms
This section describes the ERPS Alarms in EMS-BGF.
Table 13-13: ERPS Alarms

ID System Severity
1 ERPS-Topo- 718 BG-20, BG- ERPS-VSI Event Ring protection link (RPL) state
Change 30, BG-64 in Ethernet Ring is changed from
blocked to unblocked or
unblocked to blocked


14
Monitoring Performance
In this chapter:
Overview ....................................................................................................... 14-1
Performance Data .......................................................................................... 14-1
Workflow ....................................................................................................... 14-5
Viewing Performance Data ........................................................................... 14-5
Configuring Performance Attributes ........................................................... 14-11
PM Counters and TCA ................................................................................ 14-30
Performing Performance Export Configuration .......................................... 14-34
Overview
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 quality of service.
Performance Data
Performance data can be viewed for different monitored objects, as follows:
SDH: reflects digital bit stream errors, and the number of transferring
packets and error packages.
Port: reflects Ethernet MAC layer statistics, including the number of
received frames of varying length and type, and their error packets.
Ethernet over SDH (EOS): reflects the number of sent packets and error
packages.
DCC: reflects network traffic errors, and the number of monitored packets
and error packages.
L2 Extend: reflects the extend performance of the ports of Layer 2 cards.

Monitoring Performance EMS-BGF User Manual
BG20 supports Ethernet PM counters for the objects: Port, Switch, Policer,
VSI, Tunnel, MA, Local MEP and Remote MEP.
The following figure shows the PB Ethernet connection view.
The following figure shows the MPLS Ethernet connection view.

EMS-BGF User Manual Monitoring Performance
The VSI performs the learning and forwarding actions for specific L2VPN 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.
Figure of zoom-in on objects within PB PE is shown below.
Figure of zoom-in on objects within MPLS PE is shown below.
In the figure, the packet received from a UNI port will be counted by the
counter of port; If the packet is belong to the macro flow which has a policer,
Then the packet will be counted by the policer; If the packet is a broadcast
packet, and belong to a VSI of MP2MP, it will be counted by the BSC policer
of that VSI; The packet will be counted by tunnel if it is forwarded by a tunnel.
The MSTP topology change and FIB Utilization will be counted on the object
of switch.

Performance data is divided into the following monitoring periods:

15-minute performance data: 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-BGF. At the same
time, the performance data counter is reset and another round of 15-minute
performance statistics starts to accumulate.
24-hour performance data: 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-BGF. At the same time,
the counter is reset and another round of 24-hour performance statistics
starts to accumulate.
Instant performance data: current values of the 15-minute or 24-hour
performance data counters.
Through the analysis of historical performance data in the EMS-BGF, the
errors at each SDH section/layer can be conveniently 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-BGF provides a performance curve diagram, which visually shows
equipment performance changes during a specific period. This mechanism
provides a convenient way to analyze the communication link quality over
time.

Workflow
The EMS-BGF performance functions provide instant monitoring of 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 Current Performance (on page 14-6)
Viewing Performance History (on page 14-7)
Viewing Recent Performance (on page 14-10)
Managing Archived Performance Files (on page 14-11)
Setting Performance Threshold (on page 14-12)
Setting Performance Monitoring (on page 14-17)
Managing Threshold Settings (on page 14-24)
Reset Performance Counters (on page 14-25)
Setting Switch Performance Monitoring (on page 14-26)
Setting Switch Performance Threshold (on page 14-28)
Viewing Performance Data

The EMS-BGF 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 5 classes: SDH, Port, EoS, DCC and L2
Extend. When you select a class, the related performance data is displayed. The
default is SDH performance data.

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).
To view current performance data:

1. In the NE shelf view window, in the left object tree, select an object, then
select the Performance working mode. In the Current tab, you can view
the current performance data.
Before performing operations in this window, select the relevant radio

button in the Type and Display fields.
2. Click in the toolbar to retrieve the current performance data from the
NE equipment.
3. Select the Refresh data dynamically checkbox and set the Refresh
Interval.
4. Click Start Refresh to dynamically observe any performance data changes.
Data is refreshed, based on the Refresh Interval you specify.
5. Click Stop Refresh to cancel the refresh operation.

6. Click the List View icon to view the information in a list.
7. Click the Chart View icon to view the information in a chart.
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-BGF saves reported historical performance to a database.
Historical performance data is divided into 5 classes: SDH, Port, EoS, DCC
and L2 Extend. When you select a class, the related historical performance data
is displayed. The default is SDH performance data.

To view historical performance data:

1. In the NE shelf view window, in the left object tree, select the object whose
historical performance you want to view. Then select the EMS History tab
under the Performance working mode.
2. Select a performance class in the Display field.

3. Click + in the Filter field to expand the filter options.
Set the data counter and period definitions in the relevant field and click
to display historical performance data in the list
4. Click to retrieve the historical performance parameters from the NE

equipment.
5. Click in the toolbar to export the NE list as an XML file.
6. Click in the toolbar to export the NE list as a CSV file.
7. Click to delete the selected data. Click to select all and click to
deselect all.

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. 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-BGF can acquire values stored in the recent 15-minute and 24-hour
register.
To view recent performance data:

1. In the NE shelf view window, select an object in the left object tree. Then
select the NE History tab under the Performance working mode.
2. Select the relevant Display radio button.
3. Click to obtain and display the performance parameter values stored in

the recent performance registers of the NE equipment.

Configuring Performance
Attributes
The EMS-BGF enables you to configure the performance attributes, including
setting performance thresholds, setting performance monitor switches, and
resetting performance counters.
Managing Archived Performance Files

This section describes how to manage the archived Performance files.
To manage archived performance files:

1. In the NE shelf view window, select the NE in the left object tree, then
select the Archived Files tab under the Performance working mode. The
2. Click in the toolbar to open an archived file.

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. Monitored
performance indicators are ESs, SESs, BBEs, UASs, FEESs, FESESs,
FEBBEs, FEUASs, OFSs, PPJCs, NPJCs, PSCs, Rx Error Pkts, Rx Broadcast
Pkts, Rx Multicast Pkts, McVpnOctestsDropped, VPNQuotaDropPackets, and
Tx Wred Octets.
The Performance Type can be specified as either a 15-minute or 24-hour
period. See the following table for performance threshold value ranges.
Table 14-1: Performance threshold value ranges
Performance data and interval Value

ES (15-minute) 1 to 900
SES (15-minute) 1 to 900
BBE (15-minute) MS and RS: 1 to 16777215
Low-order and high-order: 1 to 65535
UAS (15-minute) 1 to 900
FEES (15-minute) 1 to 900
RS: N/A (Not Available)
FESES(15-minute) 1 to 900
RS: N/A
FEBBE(15-minute) MS: 1 to 16777215
RS: N/A
FEUAS (15-minute) 1 to 900
RS: N/A
OFS (15-minute) RS: 1 to 900
PPJC (15-minute) VC-4, VC-3 and VC-12: 1 to 900
NPJC (15-minute) VC-4, VC-3 and VC-12: 1 to 900
ES (24-hour) 1 to 86400
SES (24-hour) 1 to 86400
BBE (24-hour) MS and RS: 1 to 1610612735
UAS (24-hour) 1 to 86400
FEES (24-hour) 1 to 86400
RS: N/A
FESES (24-hour) 1 to 86400
RS: N/A

Performance data and interval Value

FEBBE (24-hour) MS: 1 to 1610612735
RS: N/A
FEUAS (24-hour) 1 to 86400
RS: N/A
OFS (24-hour) RS: 1 to 86400
PPJC (24-hour) VC-4, VC-3 and VC-12: Any Value
NPJC (24-hour) (15-minute) VC-4, VC-3 and VC-12: Any Value
Rx Error Pkts (15-minute) 10000
Rx Broadcast Pkts (15-minute) 30000000
Rx Multicast Pkts (15-minute) 30000000
McVpnOctestsDropped (15-minute) 0 to 100
VPNQuotaDropPackets (15-minute) 1 to 32000
Tx Wred Octets (15-minute) 0 to 1000000
To set SDH TCA thresholds:

1. In the NE shelf view window, select the NE in the left object tree and then
select Performance > Performance Settings in the working mode area. In
the opened window, select the SDH TCA Threshold tab.
2. Click to display the performance threshold value obtained from an NE.
3. Click to copy the performance threshold value to other NEs.

4. Click Apply to send performance threshold values to the NE, and save
them to the database.
5. To set the SD/EXC threshold, select the SD and EXC in the window.

To set Ethernet TCA thresholds:

1. To set the performance thresholds for ETY or EoS ports, in the NE shelf
view window, select the ETY or EoS port object in the left object tree
under a layer 2 card and then select Performance > Performance Settings
in the working mode area. In the opened window, select the Threshold
Setting tab.
Click to display the performance threshold value obtained from an NE

to view.

2. To set the performance thresholds for EoS, in the NE shelf view window,
select the EoS object in the left object tree under a layer 2 card and then
the opened window, select the Threshold Setting tab.
Click to display the performance threshold value obtained from an NE

to view.

3. To set the performance thresholds for VSI or tunnel, in the NE shelf view
window, select the Switch object in the left object tree under a layer 2 card
and then select Performance > Performance Settings in the working
mode area. In the opened window, select the Threshold Setting tab.
In the Display field, select the VSI or tunnel radio button and click to
display the performance threshold value obtained from an NE to view.
Setting Performance Monitoring

This operation enables you to monitor the performance of an NE by setting a
main switch for NE performance monitoring, and setting the start and end
times for monitoring. 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-BGF.
The following terms relate to the Performance Monitor Switch operation:
Main switch for NE performance monitoring: determines whether to
monitor the performance of an NE. When the NE performance monitoring
switch is disabled, the collection of statistics and the monitoring of all
performance objects in an NE are terminated. In this case, the EMS-BGF
cannot obtain any current performance counters, and the NE does not
automatically report any historical performance data. When enabled, the
NE performance monitoring switch monitors the performance of an NE
between the start time and the end time.

Performance object monitoring switch: determines whether to monitor the

performance of a specific functional block in an NE. If the performance
monitoring switch of a functional block is disabled, it terminates the
collection of statistics and the monitoring of all performance objects within
this functional block.
Autoreport switch: determines whether to automatically report to the EMS-
BGF, historical performance data for a specific functional block within an
NE. If the autoreport switch is enabled, historical performance data of a
functional block in an NE is automatically reported to the EMS-BGF.
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 functional block: includes RS, MS, VC-4, VC-3, and VC-12.
Specific Ethernet functional block: includes ETY port, EoS port, EoS, VSI,
tunnel.
To set the performance monitoring:

1. In the NE shelf view window, select the NE in the left object tree and then
the opened window, select the Monitoring and Reporting tab.
2. Click to obtain object data from the NE equipment.

3. Modify object parameters as required.

4. Click Apply to send settings to a piece of equipment and save them to the
EMS-BGF database.
5. To set monitoring switch parameters for an NE, select the Schedule tab.

Viewing Laser Performance Threshold

You can view laser performance threshold for an optical port.
To view laser performance threshold:

1. In an NE shelf view window, select an optical port in the left object tree.
Then select the Laser Performance Threshold tab under Performance >
Performance Settings working mode.
2. Click in the toolbar to retrieve the parameters.

Viewing/Exporting Laser Performance

This section describes how to view and export laser performance.
To view/export laser performance:

1. In an NE shelf view window, select an optical port in the left object tree.
Then select the Laser Performance tab under Performance working
mode.

2. To open the laser performance view list, select the NEs whose laser
performance you want to view in the main topology view, then select
Performance > Laser Performance from the main menu. The Laser
Current Performance window opens.
3. In the Filter area, you can select the port type by selecting the
corresponding checkboxes.
4. Click in the toolbar to retrieve the parameters to view.

5. To export the laser performance information as a CSV file, click in the

toolbar.
Select the location folder and enter the file name for the CSV file, then
click Save.
6. Click in the toolbar to exit the Laser Current Performance window.

Managing Threshold Settings

This section describes how to manage threshold settings.
To manage threshold settings:

1. In an NE shelf view window, select an Ethernet port in the left object tree.
Then select the Threshold Setting tab under Performance > Performance
Settings working mode.
2. Set the parameters as needed.

4. Click in the toolbar to retrieve the parameters.
5. To copy the settings to other ports, click the Propagate button in the
toolbar.


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

1. In the NE shelf view window, select the NE or a card in the left object tree.
Then select Performance > PM Reset Counters in the menu. A
confirmation message is displayed.
2. Click Yes to reset the performance counters.

Setting Switch Performance Monitoring

This section describes how to set performance monitoring for the switch
module.
To set the performance monitoring for the switch:

tree and then select Performance in the working mode area. In the opened
window, select the Monitoring and Reporting tab.

2. Select the corresponding radio button in the Display area and click to
obtain object data from the NE equipment. The following figure shows the
CoS settings for example.
3. Modify object parameters as required by select the checkboxes in Monitor

Active and Auto-Report.
EMS-BGF database.

Setting Switch Performance Threshold

This section describes how to set performance Threshold for the switch
module.
To set the performance threshold for the switch:

tree and then select Performance in the working mode area. In the opened
window, select the Threshold Setting tab.

2. Select the corresponding radio button in the Display area. The following
figure shows the Tunnel settings for example.
3. Select the corresponding checkboxes in the Filter area and click to

obtain object data from the NE equipment.

4. Modify object parameters as required in the corresponding area.
EMS-BGF database.
PM Counters and TCA

This section describes the performance counters and TCA in EMS-BGF. All
the counters have the same granularity (15min/24h).
Table 14-2: Port/Switch/Policer/VSI/Tunnel Level 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 Transmited total number of bytes for all good
packets (Unicast+Multicast+Broadcast).
Tx Pkts N Transmited total number of good packets
Rx Error Pkts Y Received total number of dropped packets,
Includes all bad packets and dropped good
packets.


Rx Pkts 64 N Received total number of good packets with size
of 64bytes.
Rx Pkts 65-127 N Received total number of good packets with size
of from 65 to 127 bytes.
Rx Pkts 1024-MTU N Received total number of good packets with size
of from 1024 to MTU bytes.
Rx CRC Align Error Pkts N Received total number of bad packet which meets
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 packet which meets

Packet length is less than 64bytes.
Packet has valid CRC.
Rx Oversize Pkts N Received total number of bad packet which meets

Packet length is larger than MTU.
Packet has valid CRC.
Rx Pause Pkts N Received total number of Pause frames.

PACL Dropped Packets N Packets discarded due to ACL rule.
Collision Errors N Number of late collisions
Rx MoE Header Error Pkts Y the number of frames received frames with header
error on MoE port.
VLAN filtering Discard N Per port counter for RX good packets discarded
packets due to VLAN filtering should be added for Ezchip
NP based cards.
Ingress classification N Per port Counter for packets discarded by NP due
Discard packets to ingress classification for EzChip NP based
cards.
Switch level
MSTP Topology Changes N The total number of topology changes detected by
the switch


FIB Full Seconds Counter N Number of seconds in which FIBActualSize was
in 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
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 unknow
destination unicast bytes received by all ports for
this VPN
BSC Dropped Octets Y Number of multicast, broadcast, and unknow
destination unicast bytes dropped by BSC policer
of this VPN
BSC Dropped Packets N Number of multicast, broadcast, and unknow
destination unicast packets dropped by BSC
policer of this VPN
BSC Average Rate N It is a rate
Average bit rate of conforming octets accepted by
BSC policer
BSC Utilization N Utilization of the permitted capacity of BSC
policer(CIR)
Quota Drop Packets Y Number of packets discarded due to FIB over
quota
Tunnel Queue level
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 It is an average bit rate of octets transmitted on this
Flow Per Cos Per Tunnel
Tunnel level
Rx Octets N Number of bytes received for this Tunnel /

CoS(PB)
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
Traffic Management level
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 It is an average bit rate of octets transmitted on this
Flow Per Cos Per Port
Table 14-3: EoS Mapper PM Counters and TCA
Counter Names TCA Description

Rx Octets N Received total number of bytes for all good packets
Rx Pkts N Received total number of good packets
Tx Octets N Transmited total number of bytes for all good packets
Tx Pkts N Transmited total number of good packets
Rx Error Pkts Y Received total number of dropped packets, Includes all
bad packets and dropped good packets.
Rx GFP EXI field N Received total number of packets which GFP EXI field
mismatch are mismatched.

Counter Names TCA Description

Rx Drop Pkts N Received total number of dropped good packets.
Rx FCS Error Pkts N Received total number of packets which have FCS error.
Rx GFP header Error Pkts N Received total number of packets which have GFP header
error.
Performing Performance Export

Configuration
To perform performance export configuration, open the file under the path:
EMS-BGF/etc/emsserver_config.xml
Configure the script as below:

<PMExportConfig>
<PMEnable>false</PMEnable>
<ExportPath>ASCIIPMLogs</ExportPath>
<IntervalHour>1</IntervalHour>
</PMExportConfig>
The parameters are described below:
PMEnable: enable the pm export. Default is "false", set "true" to enable.
ExportPath: the path of the pm file to export.
IntervalHour: interval of pm export. The unit is hour.
There are 5 types of ASCII-files with the same structure:
VC4
MS
EoS
FE-LAN
GE-LAN (BG-20/BG-30/BG-64)
Following shows an example of the file.

To view the file:

Double-click the exported file, as shown below.
NEID
;SlotNumber;SubSlotNumber;UpParentMONo;UpParentMOType;Pare
ntMONo ;ParentMOType;MOType;MONo ;Granularity;ReportTime
;BBE ;ES ;SES ;UAS ;FEES
;FESES ;FEBBE ;FEUAS ;OFS ;PPJC
;NPJC
;Selected;revBadPacketBytes;sendBadPacketBytes;rxTotalPayl
oadOct;totalFrameBytes;singleBitErrFrames;multiBitErrFrame
s;PSC ;Rx_Broadcast_Pkts
;Rx_Multicast_Pkts
;Rx_CRC_Align_Error_Pkts
;Collision_Errors
;Rx_Error_Pkts
;Rx_Octets
;Tx_Octets
-----------;----------;-------------;------------;--------
------;-----------;------------;------;------;-----------
;-----------------------;-----------;-----------;---------
--;-----------;-----------;-----------;-----------;-------
----;-----------;-----------;-----------;--------;--------
---------;------------------;-----------------;-----------
----;------------------;-----------------;-----------;----
----------------------------------------------------------
--;-------------------------------------------------------
---------;------------------------------------------------
----------------;-----------------------------------------
-----------------------;----------------------------------
------------------------------;---------------------------
-------------------------------------;--------------------
--------------------------------------------
20 ; 9 ; -1 ; -1 ; 18 ; -1
; 18 ; 3 ; 0 ; 0 ; 2008-10-24 14:01:20 ; 0
; 0 ; 0 ; 0 ; 900 ; 0 ; 0 ;
0 ; 0 ; 0 ; 0 ; 0 ; 0
; 0 ; 0 ; 0 ; 0 ;
0 ; 0 ; 0 ;0
; 0 ; 0
; 0 ; 0
; 0
(1 column
From the file, we can see that the text consists of the historical performance
parameters name and their values, which are divided into two parts by the
short lines and can be viewed in one line. They are in one-to-one relationship.
The names and values are seperated by a series of spaces and semicolons
between each other. In the file, there can be seen one copy of historical
performance data reported.
The following lists some of the parameters in the text and their explanations:

NEID: the ID of the monitored NE.

SlotNumber: the slot number.
SubSlotNumber: the sub slot number.
UpParent MONo: the Up-pararent MO number.
UpParent MOType: the type of the Up-pararent MO.
Parent MONo: the pararent MO number.
Parent MOType: the type of the pararent MO.
MOType: the type of the MO.
MONo: the MO number.
Granularity: the monitor periods (15-minute or 24-hour)
ReportTime: interval start time.
NOTE: MO here is defined into three types:

UpPararent MO
Pararent MO
MO
The following table describes the slot (subslot) numbers and the relevant slot
name the number represents.
Table 14-4: Slot names and relevant slot numbers
Slot (index from BG-40 BG-20 BG-30 BG-64

0 in db)
0 XTC MXC MS MS
1 OW OW BG_OW OW
2 TMU XS A XSA_TMU
3 XS B XSB_TMU
4 Subcard 1 A1 XS A XSA_SAM
5 Subcard 2 A2 XS B XSB_SAM
6 XS A XSA_XIO
7 IOM XS B XSB_XIO
8 Subcard 3 TS1 TS1
9 Subcard 4 EME1_21 TS2 TS2
10 Extended ES1 TS3 TS3
Slot 1
11 Extended ES2 ES1 TS4
Slot 2
12 ES3 ES2 TS5

Slot (index from BG-40 BG-20 BG-30 BG-64

0 in db)
13 ES3 TS6
14 TS7
18 CF
96 BG-20B BG-30B BG_64B
97 FAN FCU-B FCU-30B FS
98 INF-DC INF-20B PS_B A PSA
99 BG20-E BG-30E
101 PS_B B PSB
147 FCU-E FCU-30E FS_E
148 INF-20E PS_E A PSA_E
151 PS_E B PSB_E
The following table describes the MO numbers and the relevant MO name the
number represents.
Table 14-5: MO names and relevant MO numbers
MO Number MO String
3 VC12
4 TU12
5 VC3
6 AU3
7 VC4
8 AU4
9 SPI
10 SPI
11 MS
12 RS
13 PPI
14 DS0
15 VCG
16 EOS
17 PORT
18 Unknown
19 V.35
20 V.24
21 V.11

MO Number MO String
22 F1
23 U1
24 FE-WAN
25 FE-LAN
26 GE-LAN
27 CPUPort
28 COM_RDCC
29 COM_MDCC
30 MDCC_3B
31 COM_DCCx
32 F2
33 MS_F1
34 SFP
35 LAG
36 MhPG
37 E1
38 E2
39 MS_E1
40 MS_E2
41 OWTS
42 E1
43 E1
44 Codir
45 NVM
46 EOP
47 VC4_4c
48 SWITCH
49 VSI
50 Class
51 Tunnel
52 Policer
53 WREDProfile
There are 5 types of ASCII-files (VC4, MS, EoS, FE-LAN and GE-LAN).
The lists of counters (supported/in history/exported) are shown as below,
indicating the relation of counters. (Y: Supported; N:Not supported;
X:Exported.)

Table 14-6: Counter List - VC4
VC4 ASCII-files
Export
ES Y Y X
BBE Y Y X
SES Y Y X
UAS Y Y X
FEES Y Y X
FEBBE Y Y X
FESES Y Y X
FEUAS Y Y X
OFS/CV Y Y X
PPJC Y Y X
NPJC Y Y X
Table 14-7: Counter List - MS
MS ASCII-files
Export
ES Y Y X
BBE Y Y X
SES Y Y X
UAS Y Y X
FEES Y Y X
FEBBE Y Y X
FESES Y Y X
FEUAS Y Y X
Table 14-8: Counter List - EoS Port
EoS Port ASCII-files

Export
Rx Octets Y N
Rx Pkts Y N

Rx Broadcast Pkts Y Y X
Rx Multicast Pkts Y Y X
Tx Octets Y N
Tx Pkts Y N
Rx Error Pkts Y Y X
Rx Pkts 64 Y N
Rx Pkts 65-127 Y N
Rx Pkts 128-255 Y N
Rx Pkts 256-511 Y N
Rx Pkts 512-1023 Y N
Rx Pkts >= 1024 Y N
Rx Pause Pkts Y N X
Rx CRC Align Y Y X
Error
Rx undersize Pkts Y N
Rx Oversize Pkts Y N
Rx Fragments N N
Rx JabberPkts N N
Collision Errors Y Y X

Table 14-9: Counter List - EoS
EoS ASCII-files
Export
Rx Octets Y Y X
Rx Pkts Y N
Tx Octets Y Y X
Tx Pkts Y N
Rx Error Y Y X
Pkts
Rx GFP EXI N N
Field
Mismatch
Rx Drop N N
Pkts
Rx FCS N N
Error Pkts
Rx GFP N N
Header
Error Pkts
Table 14-10: Counter List - ETY Port

Export
Rx Octets Y N
Rx Pkts Y N
Rx Y Y X X
Broadcast
Pkts
Rx Multicast Y Y X X
Pkts
Tx Octets Y N
Tx Pkts Y N
Rx Error Y Y X X
Pkts
Rx Pkts 64 Y N
Rx Pkts 65- Y N
127


Export
Rx Pkts 128- Y N
255
Rx Pkts 256- Y N
511
Rx Pkts 512- Y N
1023
Rx Pkts >= Y N
1024
Rx Pause Y N
Pkts
Rx CRC Y Y X X
Align Error
Rx Y N
undersize
Pkts
Rx Oversize Y N
Pkts
Rx N N
Fragments
Rx N N
JabberPkts
Collision Y Y X X
Errors

15
Performing Maintenance
Operations
In this chapter:
Overview ....................................................................................................... 15-1
Workflow ....................................................................................................... 15-1
Preventive Maintenance Operations .............................................................. 15-2
Managing Database ..................................................................................... 15-18
Perform Card Maintenance .......................................................................... 15-20
MSP 1+1 Maintenance Operation ............................................................... 15-26
Managing SNCP Attributes ......................................................................... 15-27
Perform Transmission Object Maintenance Operations .............................. 15-28
Perform Maintenance on Timing ................................................................. 15-36
Trap Manager Table .................................................................................... 15-40
Link Loss Carry Forward (LLCF) ............................................................... 15-41
Overview
This section discusses how to perform routine maintenance operations on the
cards and internal objects.
Workflow
You can perform the following maintenance operations in any order, whenever
required:
Performing card maintenance (on page 15-20)
Performing MSP 1+1 maintenance operation (on page 15-26)
Managing SNCP attributes (on page 15-27)

Performing Maintenance Operations EMS-BGF User Manual
Performing transmission object maintenance operation (on page 15-28)

Performing maintenance on timing (on page 15-36)
Preventive Maintenance
Operations
This section describes how to perform preventive maintenance operations.
Saving NE Configuration Data

This operation is only available for the BG-40 NE. You can manually save all
configuration data in the BG-40 NE to the flash. Saved data can be used to
restore the BG-40 NE when necessary.
To save NE configuration data:

In the BG-40 NE shelf view window, select Maintenance > Save NE
configuration in the menu.
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 NE
configuration data and trail information.
To clear NE configuration data:

1. In the NE shelf view window, select Maintenance > Clear NE
Configuration Data in the main menu. A confirmation window opens
prompting you to confirm clearing the data.

EMS-BGF User Manual Performing Maintenance Operations
Configuration Consistency Checking

This section describes how to check the configuration consistency between the
EMS-BGF and the equipment. Key configuration data is traffic-affecting data,
such as slots, cards, VCGs allocation, XCs, and maintenance.
To configuration consistency checking:

1. If NE key configuration data is inconsistent with the EMS-BGF, the
consistency icon is displayed at the lower-right corner of the NE icon.
2. Select the inconsistently configured NEs in the topology view and then
select Maintenance > Full Upload NE Data in the main menu. The EMS-
BGF uploads all the configuration data from the equipment and saves it to
the database. If the operation succeeds, all NEs configuration is consistent
with the EMS-BGF, and the icons at the corner of the NEs disappear. If
the operation fails, the NEs configuration remains inconsistent with the
EMS-BGF.

To manage inconsistent NE list:

1. In the EMS-BGF main window, don't select any NE, then select
Maintenance > View Inconsistent NE List from the main menu. The
Inconsistent NE List window opens.
2. To check signature of the NEs, select the NEs in the window and click the
Check Signature button from the toolbar. In the opened Confirm
window, click Yes to check signature.

3. To upload NE data, select the NEs and click in the toolbar. In the
opened Confirm window, click Yes to upload the NE data.
Connectivity Testing
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 a connectivity testing:

1. Select an NE in the EMS topology view, and then select Maintenance >
Ping in the main menu. The following window opens.
2. Set the size of a ping test packet by entering a numeric value in the
Package Size.

3. Click Ping to conduct the ping test. The display shows the returned ping
results.
4. Click Stop Pinging to cancel the ping test. The display area shows the ping
statistics.
5. Click Clear Result to clear the contents in the display area.

Performing a Full 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-BGF database to maintain consistency between the EMS-BGF and the
equipment. An option is also available to optimize the full upload.
To perform a full upload:

1. In the EMS-BGF main window, select the NE you want to upload and
select Maintenance > Fully Upload NE Data from the main menu. Or in
the NE shelf view window, select the NE in the left object tree and then
select Maintenance > Fully Upload NE Data from the shelf view menu.
The following Confirm window opens.

3. To view the upload status, select Maintenance > View Upload Status
from the main menu.
4. Click the Details button to view the details information of the upload
status.

Performing a Full Download

This operation downloads all the configuration data from the equipment,
including SDH, Ethernet, and PCM configuration.
To perform a full download:

1. In the EMS-BGF main window, select the NE you want to download and
select Maintenance > Fully Download NE Data from the main menu. Or
in the NE shelf view window, select the NE in the left object tree and then
select Maintenance > Fully Download NE Data from the shelf view
menu. The following Confirm window opens.

3. To view the upload status, select Maintenance > View Download Status
from the main menu. The details will be displayed in about 10 minutes after
the fully download operation.
Performing Embedded Version Management

Equipment software can be upgraded from the EMS-BGF. The management
includes database backup, version load, version activation and correspondence
check operations.
Data Backup
To ensure the completeness of an upgrade, the EMS-BGF database should
be backed up before performing the upgrade. The EMS-BGF provides a
Get NE DB File feature, which can be used to back up an NEs database as
a binary file and to upload it to the EMS-BGF host. The EMS-BGF also
provides a Download NE DB File feature, which can be used to download
the NE database backup file from the EMS-BGF host to the NE.

Version Load
The following conditions apply to the version load process:
The EMS-BGF and the NE's embedded software verify the file to be
upgraded. An illegal file cannot be downloaded to the NE. The
verification procedure checks the version and other key fields.
To avoid a cross-version upgrade, the EMS-BGF checks that the
upgrade path is reasonable. You should verify the upgrade path if this
check fails. By default, an upgrade is not performed if the upgrade path
check fails.
An upgrade can be performed for one or more NEs. NEs should be of
the same type when upgrading multiple NEs concurrently.
Version Activation
The following conditions apply to the version activation process:
The Activation Time operation is used on BG-40 NEs.
The Version Activation operation is used on BG-20 NEs.
An upgrade confirmation should be performed before activation. The
EMS-BGF verifies that inactivated versions of the NEs to be upgraded
are of the same NE type, and that the upgrade path is reasonable. The
EMS-BGF displays any unqualified NEs.
An unqualified NE can be inactivated.
Activation is triggered by the activation time. The EMS-BGF can
configure an NE's activation time. The version activation process works
as follows. After the activation time has expired, the NE checks
whether the validated version exists in the Inactive bank. If the
validated version exists, the NE changes the Inactive bank to the Active
bank, changes the Activate bank to the Inactivate bank, and performs a
warm/cold restart automatically. The performance of a warm/cold
restart is determined by whether an FPGA upgrade is needed. If an
FPGA must be upgraded, the NE performs a cold restart. If the
validated version does not exist, activation fails and an Activate Fail
event is reported.
The EMS-BGF should synchronize the time on affected NEs before
setting the activation time, in order to ensure that the NE time is not
unsynchronized with the EMS-BGF.
The activation time can be retrieved from NEs and canceled. The
activation time is invalidated after an NE restart.
A version can also be activated manually. In this case, the EMS-BGF
sends an Activate New Version message to the NE, and the NE then
changes the Inactivate bank to the Activate bank, changes the Active
bank to the Inactive bank, and performs a warm/cold restart
automatically.

Correspondence Check
The EMS-BGF performs a correspondence check after an upgrade. The
correspondence check verifies that the NE version matches the expected
version of the EMS-BGF, in order to ensure that all NEs were upgraded.
To perform embedded version management:

1. In EMS-BGF main window, select Maintenance > Embedded Version
Management from the main menu. The Embedded Version Management
window opens.

2. In the left NE list, select the NEs you want to manage by selecting the
corresponding checkboxes. In the Bank Info tab window, click to
retrieve the status of the embedded software.
In this window, select the items in the list and click . in the opened
Confirm window, click Yes. The inactive embedded software version is
deleted.

3. In the Activate Time tab window, click to display the activation time
retrieved from the NE.

4. From this window, click to activate the NE new version immediately.

In the opened Upgrade Confirmation window, select the NEs you want to
upgrade and click Apply. Click to set version activate time. Click
to cancel activation time configuration.

5. In the Last Upgrade Info tab window, click to retrieve the last upgrade
information to view.
6. In the Correspondence Check tab window, click to select the version

file on the EMS-BGF host to be used as the basis for the correspondence
check.

The correspondence check verifies that the NE version matches the

expected version of the EMS-BGF, in order to ensure that all NEs were
upgraded.
7. Click to save the correspondence check results as an HTML file. To
export the result as a TXT file, click in the toolbar.
Performing an 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 an LED test:

1. Select an NE in the topology map and then select Maintenance > Test
LED in the main menu. A confirmation window opens.
2. Click Yes to perform test operations.
Preventive Maintenance Procedure

The following table describes the preventive maintenance procedures necessary
to ensure the proper operation.
Table 15-1: EMS-BGF preventive maintenance procedures
Procedure How often to perform

Save the NE database Once a week, or following major changes in network
configuration to hard disk topology
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-BGF to NE Once a week, or according to working procedures
communication
Save the EMS-BGF Once a week, or following major changes in network
configuration to hard disk topology

Procedure How often to perform

Check switching to protection Once a quarter, according to network administrator's
instructions
Note: This operation is traffic-affecting.
Export cross connections data Once per month, or according to working procedures
to XML files
Check optical parameters Once per month, or according to working procedures
Export topology data to an Once per month, or according to working procedures
XML file
Export card inventory data to Once per month, or according to working procedures
an XML file
Managing Database
You can back up the EMS database to simplify network management and
maintenance tasks.
To backup database:
1. In the EMS main window, select System > EMS DB > Backup
Immediately in the main menu. The Backup EMS Database
Immediately window opens.
2. Click Apply to backup the EMS database.

You can also set an automatic time for EMS backup, as described below.

To perform backup settings:

1. In the EMS main window, select System > EMS DB > Backup Settings in
the main menu. The EMS Database Backup Settings window opens.
2. Select a mode in the Backup Mode area by selecting one of the following
radio buttons:
Not Backup: the automatic backup is not allowed if this option is
selected.
Backup Date: automatically backup the database at the time you set.
Periodic Backup: automatically backup the database periodically at the
time you set.
3. Input the directory for saving the backup files in the Backup Directory
area.

Perform Card Maintenance

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 only resets the central processing unit of the cards, meaning 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, while cold resets do.
To reset a card:
1. In the NE shelf view window, select a card in the left object tree, then
select Maintenance > Reset in the menu. The Reset NE window opens.
2. Select the Cold reset or Warm reset radio button.

3. Click OK. A confirmation message is displayed after command execution.

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.
In addition, EMS-BGF supports viewing actual WDM information of the SFP
for the following cards:
XIO30-16
SMS16
XIO64
XIO16_4
SMQ1
To obtain the SFP type:

1. In the NE shelf view window, select an oPort in the left object tree and then
select the SFP Setting tab under the Configuration working mode. The

2. Select the required Expected SFP Type and the Application Code in the
respective dropdown lists.
The following SFP types are new for the STM-1/4 interface in BG-
20/20C/30/64 from EMS-BGF v11.3:
OTR1-V5
OTR1-X49BD
OTR1-X59BD
OTR4-V5

4. To view WDM information of the SFP, select an oPort under the card that
supports viewing actual WDM information in the left object tree and then
select the SFP Setting tab under the Configuration working mode.
5. User can view the WDM information as listed below:

Module sub-type
Application code
Number of supported channels
CWDM channel number
Channel spacing

Performing Basic Parameter Backup in SFP

This section describes how to backup basic parameters in SFP for BG-20 NEs.
To backup basic parameters in SFP:

1. In the EMS-BGF main topology view, select Maintenance > Backup
Basic Parameter in SFP from the main menu.

2. Select the NEs in the left NE list by selecting the corresponding

checkboxes. To select all NEs, select the All NEs checkbox. Click in
the toolbar to get the information to view.
3. Select the the checkboxes in the Backup NE Basic Parameter in SFP list
as required and click Apply to backup the corresponding parameters.
4. Click in the toolbar to get the information to view.

MSP 1+1 Maintenance Operation

You can perform maintenance operations on objects configured in MSP 1+1.
To perform MSP 1+1 maintenance operations:

1. In the NE shelf view window, select the MSP-Linear tab under the
2. Select a PG in the list and right-click on it. From the pop up menu, MSP
1+1 maintenance operation can be performed as described below:
For unidirectional MSP 1+1, you can perform the following
maintenance operations:
Delete PG
Force Switch to Protection
Force Switch to Main
Manual Switch to Protection
Manual Switch to Main
Release
For directional MSP 1+1, you can perform the following maintenance
operations:
Delete PG
Lockout of Protection
Release

Managing SNCP Attributes

The EMS-BGF supports SNCP I/N. The default is SNCP N.
To define SNCP attributes:

1. In the NE shelf view window, select the SNCP List tab under the Service
working mode.
2. You can set the attributes of Revertive, Monitor Type, and Hold Off
Time in the respective dropdown lists.
3. Select an SNCP in the list and right-click it. From the pop up menu, the
following maintenance operations can be performed:
Manual Switch to Protection
Manual Switch to Main
Release
5. Click to refresh the information in the list.

Perform Transmission Object

Maintenance Operations
The EMS-BGF enables you to perform maintenance operations on transmission
objects.
Using Maintenance List

The EMS-BGF conveniently provides a graphical symbol indicating that a
maintenance operation has been performed on an NE. In addition, it also
enables you to view a list of the maintenance operations performed on an NE.
Whenever a maintenance operation has been performed on an NE, the
Maintenance icon appears above the NE icon in the EMS-BGF main
window.
To use the maintenance list:

1. In the NE shelf view, select Maintenance > Maintenance List in the
menu. Or in the EMS main window, select an NE and then select
Maintenance > Maintenance List in the main menu.

3. To release maintenance operation data, select an operation from the list and
click on the toolbar or right-click on it and select Release in the pop up
menu.

Performing/Releasing Loopbacks
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-BGF.
After an end-to-end trail has been configured, a loopback can be used to test
whether the whole path works normally and whether meters receive and send
consistently. If there is no error code, it means that everything is working
normally.
The loopback operation includes:
Terminal (NE) loopback: looping back signals from the cross-connect unit
back to the same cross-connect 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, from the left object tree, select a card that
has undergone maintenance and requires a loopback. Then select the
Loopback tab under the Maintenance working mode.
2. Modify loopback parameters as required by selecting a loopback from the

Loopback Type list.

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. In the Operation attribute list, you can see the loopback operations you
performed. Select the loopback you want to release and click on the
toolbar, or right-click on the loopback and select Release in the pop up
menu.

Performing AIS/RDI
The EMS-BGF enables you to perform the Alarm Indication Signal (AIS) and
the Remote Defect Indication (RDI) operation.
To perform an AIS/RDI:
1. In an NE shelf view window, from the left object tree, select the VC-4/VC-
3/VC-12 or MS/RS module under all optical interface cards and service
cards. Then select the Force Signal tab under the Maintenance working
mode.
2. In the DownStream area, select the operation to be performed by selecting

either the None or AIS radio button from the dropdown list.
3. In the UpStream area, you can select None, AIS or RDI from the
dropdown list.
4. For the NE before the version v11, user can only release "Force AIS
Downstream" in the Maintenance list which is get from MS. When user
upload NE from v11 to v11.3, the "Force AIS Downstream" on MS will
change to "Force AIS Downstream" on RS in EMS-BGF.
5. Click Apply to insert the AIS/RDI.

Performing PRBS
The EMS-BGF enables you to perform the PRBS operation.
To perform a PRBS:
1. In the NE shelf view window, from the left object tree, select the required
card and select VC-4 or PPI. Then select the PBRS tab under the
2. In the Generator Side area, you can perform PRBS generation:

Set the Switch mode to On.
Specify the Generator Pattern.
Select the Invert Signal checkbox.
Select the Upstream or Downstream radio button in the Direction
field.
Click Apply to generate the PRBS.
Click the Add single bit error icon to insert an additional error bit.

3. In the Monitor Side area, you can perform monitoring PRBS:

Set the Switch mode to On.
Specify the Generator Pattern.
Select the Invert Signal checkbox.
Select the Upstream or Downstream radio button in the Direction
field.
Click Restart to begin monitoring PRBS. The error code is added to
the Counter.
Click Refresh to refresh the Counter value.
4. In the toolbar, click to retrieve the current status.
Switching to Protection
The EMS-BGF provides the following options for switching to protection:
Manual Switch: Made 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, select the Main XIO card
in the left object tree, then select the Maintenance working mode.
Set the protection switch by selecting a mode in the Switch Command

area and click 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, such as 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, such as 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
usedby 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, such as a forced switch, lockout, the XIO30 A is not
present, or the FPGA is not loaded.
Manual Switch to XS B: manually switches to XSB, 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, such as a forced switch, lockout, the XIO30 B is not
present, or the FPGA is not loaded.
2. For MSP 1+1, you can perform the switching from the right-click menu in
the PG list (see "MSP 1+1 Maintenance Operation" on page 15-26).
3. For SNCP, you can perform the switch to protection operation from the
right-click menu in the SNCP list (see "Managing SNCP Attributes" on
page 15-27).
Perform Maintenance on Timing

This section describes maintenance operations that can be performed on timing
objects and TMUs.
Viewing TMU Working Mode

You can determine the TMU work 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, select MXC4X under Control and
Physical Object in the left object tree, and then select the Timing
Maintenance tab under the Maintenance working mode. In the BG-20 NE
shelf view window, you should select the TMU object under Control and
Physical Object, and then select the Timing Maintenance tab under the
2. In the toolbar, click to retrieve the TMU work mode.

To view the TMU working mode for BG-30 NE:

1. In the BG-30 NE shelf view window, select the XS A:TMU object under
Control and Physical Object, while in BG-20C NE, select TMU. Then
select the Timing Maintenance tab under the Maintenance working
mode.
From the window, you can view the Main TMU Working Mode and the
Standby TMU Working Mode.
2. Click to retrieve the TMU work mode.

Forcing the Timing Source

The EMS-BGF enables you to force a specific timing source, even if the
system has made a different selection, 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 (on page 15-36).
2. Select an object in the Timing list and right-click on it, as shown in the
following figure:
The following operation can be performed form the right-click menu:

Lockout
Release Lockout
Forced Switch
Manual Switch
Clear

Trap Manager Table

When integrated with the third part SNMP network management, the port for
SNMP sending traps needs to be configured. This section describes how to
manage trap manager table in EMS-BGF.
To manage trap manager table:

1. In BG-20/BG-20C/BG-30/BG-64 NE shelf view window, select the NE in
the left object tree and then select Maintenance > Trap Manager Table
from the menu. The Trap Manager Table window opens.
In the trap manager table, only one item can be set as Administrator.
2. Click in the toolbar. The Create Trap Manager window opens.
3. Set the attributes of Manager IP, Trap Port Number and Administrator
as needed and click OK to save it.

4. Click in the toolbar. The Edit Trap Manager window opens.
5. To delete an item, select the one you want to delete from the trap manager
table and click in the toolbar.
Link Loss Carry Forward (LLCF)

This section describes Link Loss Carry Forward (LLCF) in EMS-BGF. The
LLCF can be illustrated clearly in the following figure.
Remote ETY or Tunnel defect can be a trigger for local ETY port down.

To enable LLCF:
1. In the NE shelf view window, select an ETY port in the left object tree,
then select the General tab under the Configuration working mode.
2. Select Disabled or Enabled from the LLCF Enable dropdown list as

required. Default is Disabled.

16
Managing Reports
In this chapter:
Overview ....................................................................................................... 16-1
Using the Report Window ............................................................................. 16-2
Overview
The Report feature generates reports for all EMS-BGF managed objects.

Managing Reports EMS-BGF User Manual
Using the Report Window

This section describes how to use the report window in the EMS-BGF.
To view the NE inventory list:

1. Select the NEs in the EMS topology view and then select Configuration >
View > NE Inventory in the main menu. The NE Inventory window
opens.
2. To export the NE inventory list as a CSV file, click in the toolbar.

EMS-BGF User Manual Managing Reports
To view the SFP inventory list:

1. Select the NEs in the EMS topology view and then select Configuration >
View > SFP Inventory in the main menu. The SFP Inventory window
opens.
2. To export the NE inventory list as a CSV file, click in the toolbar.

Managing Reports EMS-BGF User Manual

A
XML File
In this appendix:
Overview ........................................................................................................ A-1
XML and DTDs .............................................................................................. A-1
Example .......................................................................................................... A-3
Overview
The EMS-BGF uses XML files to perform trail operations in a batch, by
importing and/or exporting trail definitions from/to an XML file. This appendix
describes the structure of an XML file and provides a command reference and
examples of XML syntax.
XML and DTDs

XML is a markup language (much like HTML) designed to describe data,
where the data is described using XML tags.
XML tags are not predefined, you must define your own tags, and one of the
ways is using a DTD (Document Type Definition) file. The DTD is predefined,
and there is no need for user intervention.
Following is an example of an XML file, which could describe a simple note or
message:
<?xml version="1.0" encoding="utf-8" ?>
- <something-else-entirely>
- <proxool>
<alias>proxoolPool</alias>
<driver-url>jdbc:mysql://localhost/emsdb</driver-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
426006-2421-173-A00 ECI Telecom Ltd. Proprietary A-1

XML File EMS-BGF User Manual
- <driver-properties>
<property name="user" value="root" />
<property name="password" value="root" />
</driver-properties>
<house-keeping-sleep-time>90000</house-keeping-sleep-
time>
<maximum-new-connections>20</maximum-new-connections>
<prototype-count>5</prototype-count>
<maximum-connection-count>100</maximum-connection-count>
<minimum-connection-count>5</minimum-connection-count>
<trace>true</trace>
</proxool>
</something-else-entirely>
The XML file has a specific structure and elements it can and should contain.
XML Components
An XML element is defined within an opening XML tag and a closing XML
tag. This is an XML element:
<body>Get lost or I will get you</body>
This XML element is defined within the XML tag <body> and has a child
element, where child element is actually the tags data. XML element may have
an attribute, a child element, element siblings, and may be also empty:
<note date=27.3.2003>
<from>John</from>
<to>Jane</to>
<heading>Warning</heading>
<body>Dont be late for dinner</body>
</note>
"note" is an XML element. It has one attribute, "date". The attribute "date" has
a value, "27.3.2003". As you can see, "note" has NO child elements, unlike the
"from" element which has the child, or data, "John".
The element "note" has 4 siblings: "from", "to", "heading" and "body".
A-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual XML File
XML File Structure

An XML file has a header and a body.
The header contains two important pieces of information: the root of the file, in
this case its "messages", and the DTD file full path, in this example
"./messages.dtd".
Below is an example of an XML header:
<?xml version=1.0?>
<!DOCTYPE messages SYSTEM "messages.dtd>
The XML body contains the information you wish to convey. It starts with the
root tag, which is a regular XML element. Below is an example of an XML
body:
<messages>
<note date=27.3.2003>
<from>John</from>
<to>Jane</to>
<heading>Warning</heading>
<body>Dont be late for dinner</body>
</note>
</messages>
Example
The following is an example of an XML file with service XC.
<?xml version="1.0" encoding="UTF-8" ?>
- <root FileType="XCs">
- <XConnectInfo>
<SourceTimeSlot NEID="3" NEType="2" SlotNumber="0"
EBType="128" SubSlotNumber="-1" SubEBType="-1"
UpParentMOType="-1" UpParentMONo="-1" ParentMOType="-1"
ParentMONo="-1" MOType="3" MONo="1" PortNo="1"
PortType="0" />
<SinkTimeSlot NEID="3" NEType="2" SlotNumber="0"
PortType="0" />
<NEID>3</NEID>
<XCID>23</XCID>
<SNCID>23</SNCID>
426006-2421-173-A00 ECI Telecom Ltd. Proprietary A-3

XML File EMS-BGF User Manual
<TrailID>-1</TrailID>
<Rate>1</Rate>
<State>1</State>
<ServerLayer>0</ServerLayer>
<Protected>0</Protected>
<SNCName>23</SNCName>
<SNCDirection>1</SNCDirection>
<SNCType>1</SNCType>
<UserLabel>Default Name</UserLabel>
<CustomerName>Customer</CustomerName>
</XConnectInfo>
- <XConnectInfo>
<SourceTimeSlot NEID="3" NEType="2" SlotNumber="0"
PortType="0" />
<SinkTimeSlot NEID="3" NEType="2" SlotNumber="0"
PortType="0" />
<NEID>3</NEID>
<XCID>24</XCID>
<SNCID>23</SNCID>
<TrailID>-1</TrailID>
<Rate>1</Rate>
<State>1</State>
<ServerLayer>0</ServerLayer>
<Protected>0</Protected>
<SNCName>23</SNCName>
<SNCDirection>1</SNCDirection>
<SNCType>1</SNCType>
<UserLabel>Default Name</UserLabel>
<CustomerName>Customer</CustomerName>
</XConnectInfo>
</root>
A-4 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

B
Summary of Menu
Commands
In this appendix:
Overview ........................................................................................................ B-1
Overview
This section describes the EMS- BGF menu commands, their respective
functions, and the relevant window in which they appear:
Main window menus are listed with a checkmark () in the M column.
Shelf View menus are listed with a checkmark () in the S column.
For convenience, the following sections are divided per menu, listing related
menu options in alphabetical order.
Table B-1: View Menu
Menu Command Function M S

Align Makes the NEs align
top/bottom/left/right/horizontal/vertical
Collapse Collapses selected group
Collapse All Collapses all groups
Display Shows/hides toolbar/tree/overview, or displays full
screen
Expand Expands selected group
Expand All Expands all groups
Find Searches NEs in topology
426006-2421-173-A00 ECI Telecom Ltd. Proprietary B-1

Summary of Menu Commands EMS-BGF User Manual

Layout Makes the NEs as circular/hierarchic/symmetric/tree
layout
Moving Locks the topology or save the position
Print Prints the topology
Propagate Copies the settings from the selected NE to other
NEs.
Select All Selects all NEs
Zoom Changes the size of the topology view
Table B-2: Configuration Menu

Create Creates NE/group/topolink
Delete Deletes NE/group/topolink
Discovery Discovers NE/topology link
NE Connection Configures the NE communication parameters
Settings
NE Time Setting Sets NE clock
IP Networking Configures OSPF
Modify Modifies EMS/group/topolink
MS-SPRing Performs MS-SPRing management
Routing Table Displays NE routing table
Slot Assignment Assigns a slot in NE shelf
Synchronize NE Updates the NE time with EMS server time
Time
View Displays NE list/group list/topolink list window or
view the NE inventory
Table B-3: Services Menu

Create DCC XC Creates DCC XC
Create OH XC Creates OH XC
Create PCM XC Creates PCM XC
Create Policer Creates Policers
Create Trail Creates Trails
Create Tunnel XC Creates tunnel XC
Create VSI Creates VSI
B-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Summary of Menu Commands

Create XC Creates XC
DCC XC List Displays the XC list
Export Exports Trails/SDH XCs/Tunnel XCs/VSIs as a file
Extended DCC Manage MCF and Extended DCC
Import Exports Trails/SDH XCs/Tunnel XCs/VSIs as a file
OH XC List Displays the OH XC list
Open Trail List Displays the trail list
PCM XC List Displays the PCM XC list
Policer List Displays the policer list
Trail Consistency Makes server/service trail consistent with equipment
Tunnel XC List Displays the tunnel XC list
VSI List Displays the VSI list
XC List Displays the XC list
Table B-4: Fault Menu

Alarm Audio Turns the Audio Alarm on and off
Alarm Counter Shows or hides the alarm counter
Alarm Notification Sets the alarm notification configuration
Setting
Archived Files Displays the archived files
Cleared Alarms Displays cleared alarms
Current Alarms Displays current alarms
Display Shows or hides alarm counter and notification
Events Displays event list
External Alarms Sets external alarms configuration
Manually Synchronizes NE alarm manually
Synchronize NE
Alarm
Manually Synchronizes card alarm manually
Synchronize Card
Alarm
Monitoring and Sets alarms on which objects to be monitored and
Reporting reported
NE History Displays NE history alarm
NE Settings Configures NE alarm settings


Severity Settings Configures severity settings
Unreported Alarms Displays unreported alarms list
View Alarm Log Displays the alarm log
File
Table B-5: Performance Menu

Current Displays current PM data
Performance
EMS History Displays history PM data in EMS-BGF
Laser Performance Displays laser current performance
Monitoring and Sets performance on which object to be monitored
Reporting and reported
NE History Displays historical PM data on NE
Reset PM Counters Resets 15-minute or daily PM counters
Schedule Enables configuration of PM schedule
SD and EXC Sets SD and EXC for every entity
SDH TCA Sets SDH TCA threshold
Threshold
Table B-6: Maintenance Menu

Backup Basic Makes the backup of the basic parameters in SFP
Parameter in SFP
Bit Code Displays bit code list
Clear NE's Clears NE's configurations on the NE
Configuration
Debug Displays the debug window
Embedded Version Manages embedded versions
Management
Fast Upload NE Upload NE data of selected NEs to the EMS-BGF
Data database fast
Force Release LCT Forces release LCT connection for the NE
Master
Fully Download NE Downloads NE data of selected NEs from the EMS-
Data BGF database fully
Fully Upload NE Uploads NE data of selected NEs to the EMS-BGF
Data database fully
LCT Work Mode Enables activating LCT work mode on the NE

EMS-BGF User Manual Summary of Menu Commands

Login Logins to the selected NE
Maintenance List Displays maintenance list
NE DB Backups or restores NE DB file
NE Version Live Performs live update of the NE version
Update
Ping Pings IP address of the NE
Reset NE Enables warm reset or cold reset the NE
Software Upgrade Upgrades NEs, as well as BG40 card and SM10 card
Test LED Performs the NE's LED test
Trap Manager Table Manages traps
View Inconsistent Displays the inconsistent NEs in the list
NE List
View Download Displays download status of the selected NEs
Status
View Upload Status Displays upload status of the selected NEs
Table B-7: Security Menu

Action Log Displays action log files
Active Users Displays list of users currently working on the EMS-
BGF
Change Password Changes user password
Security Sets security configuration
Configuration
Security Log Displays security log files
Table B-8: System Menu

Alarm Export Performs the alarm export settings
Settings
EMS DB Performs EMS database backup and backup settings
Event Logs Performs EMS archive and archive settings
Exit Shuts down the EMS-BGF
License Manager Displays the license list
Lock EMS-BGF Locks the EMS-BGF until user logs in
Logout Enables user to log out

Table B-9: Help Menu

About Displays the EMS-BGF version number and
configuration information
Help Displays online help

C
Software Upgrade
In this appendix:
Software Upgrade Overview .......................................................................... C-1
Software Upgrade Workflow.......................................................................... C-2
Performing Software Upgrade ........................................................................ C-2
Software Upgrade Overview

This section discusses how to upgrade NE software in the EMS-BGF.
CAUTION: Only the administrator can use this function. It

cannot be assigned to other users. The software upgrade
procedures described in the following sections should only be
performed by qualified Telecom Network Solutions Division
personnel.
Inappropriate use of these procedures can cause damage both
to the traffic and the network management.
Be sure to consult Telecom customer support prior to
performing the operations described in these sections.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary C-1

Software Upgrade EMS-BGF User Manual
Software Upgrade Workflow

The software upgrade including the following steps:
Select NEs
Select version
Verify versions correspondence
Download
Set activation time
Upgrade
Report
Performing Software Upgrade

The NE software is resident on the NE xMCP card's nonvolatile memory
(NVM). You can update the NE software via the EMS-BGF by downloading
the software from the EMS-BGF disk.
To update NE software in a network:

1. In the EMS-BGF main window, on the menu bar, select Maintenance >
Software Upgrade. Then select which NE type or card you want to
upgrade in the pop up menu. Or, select Maintenance > Software Upgrade
in the NE shelf view window. The Software Upgrade Wizard window
opens.
C-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Software Upgrade
2. Select the NEs you want to upgrade in the checkboxes and click Next. In
the following window, click on the New Version File area and enter your
version file.
3. Verify version correspondence: Checks if all NEs of the same type store the
same software version in their NVMs. This operation generates a log file
that details on which NEs and cards the correspondence check failed. This
log provides an important troubleshooting tool for resolving problems that
occur during upgrades.
4. Download: Downloads a backed up database from EMS-BGF to the NE
NVM.
5. Set activation time: Sets the time when the new version is to become
effective. Date selection fields are displayed in a window, allowing you to
specify the time schedule for carrying out the operation.
6. Upgrade: Begins to upgrade NE software.
7. Report: Shows the result of the NE software upgrade.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary C-3

Software Upgrade EMS-BGF User Manual
C-4 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

D
NE Version Live Update
In this appendix:
Overview ........................................................................................................ D-1
Workflow ........................................................................................................ D-2
Embedded SW Patching ................................................................................. D-2
Activate NE Patches ....................................................................................... D-7
View Scheduled Activation Info .................................................................. D-11
Cancel Activate NE Patches ......................................................................... D-12
Clear NE Patches .......................................................................................... D-12
Overview
Live update is a patching mechanism, which is used to fix bugs of released
version without a need to release a new version and re-install the new version.
Following patch types are supported:
Hot function patch: can be activated without restart.
Warm function patch: require warm reset to be activated.
Cold function patch: require cold reset to be activated.
Warm card SW update: require warm reset to be activated.
In this case, function patches of this card cant coexist.
Cold card SW update: require cold reset to be activated.
In this case, function patches of this card cannot coexist.
Card FPGA update: always cold reset.
BG-20 can support function patch only, while BG-30 and BG-64 can support
all kinds of patch.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary D-1

NE Version Live Update EMS-BGF User Manual
The NE version information consists of two parts:

Current NE embedded SW package version, for example, 12.0.23.
Current NE embedded patch package version, for example, 01.
NE attribute should display the complete version information:
For example, V12.0.23-01 With Patch version 01
For example, V12.0.23 without any patch
NE version information is the patch version that be updated each time system
restart or patch activation.
Workflow
Following is the patching procedure from EMS:
1. Confirm current patch version.
2. Download the patch package.
3. Activate the patch.
4. Confirm patch version is updated successfully.
In this chapter, the NE version live update includes:
Embedded SW Patching (on page D-2)
Activate NE Patches (on page D-7)
View Scheduled Activation Info (on page D-11)
Cancel Activate NE Patches (on page D-12)
Clear NE Patches (on page D-12)
Embedded SW Patching
This section describes how to download patch packages.
Following are the procedure for downloading patch packages:
Select NEs
Select patch
Download
Patch verification
Set active time
Activation
Report
D-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual NE Version Live Update
To download patch packages:

1. In the EMS-BGF main topology view window, select Maintenance > NE
Version Live Update > Embedded SW Patching from the main menu.
The Embedded SW Patching Wizard window opens.
2. Select the NEs you want to patch by selecting the corresponding

checkboxes.

3. Click Next. The following window opens.
4. Select directory where the new patch file that you want to download is
located. You can only select one single patch to update all the NEs. A
confirmation window opens prompting you to confirm your selection. Click
Yes to confirm.

5. Click Next. The following window opens.
6. Wait for a few minutes while the wizard is downloading the patch file to
NE. Then click Next to continue.

7. Wait a few minutes during the patch verification. Click Next.
8. Set the target patch activation time as required and click Next to patch the
NE(s).

9. Click Next. The live update report displays.
10. Click Save to save the report to file.

11. Click Finish to exit the Embedded SW Patching Wizard window.
Activate NE Patches
This section describes how to activate NE patches.
Following are the procedure for activating NE patches:
Select NEs
Get patch
Patch verification
Set active time
Activation
Report

To activate NE patches:
Version Live Update > Activate NE Patches from the main menu. The
Activate Patch Wizard window opens.
2. Select the NEs you want to patch by selecting the corresponding

checkboxes and click Next. The following window opens.

3. Wait a few minutes during the patch verification. Click Next.
4. Set the target patch activation time as required and click Next to patch the
NE(s).

5. Click Next. The live update report displays.
6. Click Save to save the report to file.

7. Click Finish to exit the Embedded SW Patching Wizard window.

View Scheduled Activation Info

This section describes how to view the scheduled activation information.
To view the scheduled activation information:

Version Live Update > View Scheduled Activation Info from the main
menu. The View Scheduled Activation Info Wizard window opens.
2. Select the NEs that you want to view and click Next.
3. User can view the activation info from the window.

4. Click Finish to exit the wizard window.

Cancel Activate NE Patches

This section describes how to cancel activate NE patches.
To cancel activate NE patches:

1. In the EMS-BGF main topology view window, select the NEs that you
want to cancel the activate NE patches, then select Maintenance > NE
Version Live Update > Cancel Activate NE Patches from the main
menu. A reminder/confirmation window opens prompting you to confirm
your operation.
Clear NE Patches
This section describes how to clear NE patches.
To clear NE patches:
1. In the EMS-BGF main topology view window, select the NEs that you
want to clear the NE patches, then select Maintenance > NE Version Live
Update > Clear NE Patches from the main menu. A
reminder/confirmation window opens prompting you to confirm your
operation.

E
RDR
In this appendix:
Overview ......................................................................................................... E-1
RDR Solutions ................................................................................................. E-2
RDR Schemes .................................................................................................. E-2
Failover Processing.......................................................................................... E-4
Overview
The Remote Data Replicator (RDR) provides redundancy features for the
EMS-BGF. RDR implementation is based on replication of the EMS-BGF
database from one site to another. This replication is carried out automatically
at periodic intervals, as configured by the customer, and is not in real time. You
can restore the management database from a specified replication point.
The basic idea is to place a redundant management station at a remote site, and
to set up a direct data link between the working site and the remote site. A
special RDR software package periodically replicates the working stations
database onto a backup server on the redundant station. In case of a disaster at
the working site, the operator switches the redundant station to active mode,
and within minutes, full management capabilities are restored by the redundant
station.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary E-1

RDR EMS-BGF User Manual
RDR Solutions
There are three roles in the RDR:
Primary station: the station currently managing the network.
Mirror station: the remote redundant station replacing the primary station.
Backup station: the station running the backup server to store the backup
data.
Both the primary station and the mirror station are installed as part of the EMS-
BGF software.
RDR supports the following solutions:
Site protection: primary and mirror sites are connected via a long-distance
link.
Server protection: primary and mirror sites are connected via LAN.
Disk protection: the database replicas stay on the local station, but on
different disks.
RDR Schemes
RDR supports the following replication schemes:
1:1: One backup station supports one primary station. The primary station
runs the EMS-BGF, and the backup station stores the replicas.
E-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual RDR
1:N: One backup station can support multiple primary stations. Each
primary station is assigned a unique directory on the backup station. The
replicas of the primary station are placed under this directory.
N:1: One primary station can back up to multiple backup stations.

Failover Processing
The mirror station is in standby mode and must not actively manage the
network. When the primary station fails, the mirror station is manually
activated and instructed from which database replica it should recover data.
Upon completion of database synchronization, work can carry on as usual.
Once the primary station is back in working condition, you can revert to the
normal working configuration. A reverse replication (from the mirror station to
the primary station) is manually initiated. This updates the primary station with
all changes made during the failover period. Work can then resume as usual, as
the mirror station returns to standby mode.
To configure the RDR settings in EMS-BGF:

1. In the EMS-BGF main window, select System > EMS DB > RDR
Settings from the main menu. The EMS Database RDR Backup Setting
window opens.
RDR Enable: select the checkbox if you want it to work. If it is enabled,

the NE DB can be set to backup to the RDR server automatically.

2. To create a RDR server, click in the toolbar.
Set the areas as described below:

Server Name: set the RDR server name.
Server IP: the RDR Server IP.
Server Port: the RDR Server port.
User Name: type your user name.
Password: type your password.
Server Path: the path that the file will copy in the RDR server. Default
path is "c:\Program Files\RDR Server\" and inside you will have folder
serverPath.
Click Apply to create the server.

3. To edit a RDR server, in the server list, select the RDR server you want to
edit and click in the toolbar.
Modify it in the RDR Server Setting area. Click Apply to save the
changes.
4. To view the detail information of a RDR server, select the RDR server in
the server list and click in the toolbar.
5. To remove a RDR server, select the RDR server in the server list and click
. The RDR server will be removed from the list.
6. Click Apply to save the RDR backup settings before you close the EMS
Database RDR Backup Setting window.

To configure the Backup settings in EMS-BGF:

1. In the EMS-BGF main window, select System > EMS DB > Backup
Settings from the main menu. The EMS Database Backup Setting
window opens.
Config DB/Alarm DB: which DB you want to save.

Backup Mode: Select a mode in the Backup Mode area by selecting one of
the following radio buttons:
Not Backup: the automatic backup is not allowed if this option is
selected.
Backup Date: automatically backup the database at the time you set.
Periodic Backup: automatically backup the database periodically at
the time you set.
2. If select the Not Backup mode, the automatic backup is not allowed.

3. If select the Backup Date mode, setting the backup data. For backup the
DB only once at the time you set.

4. If select the Periodic Backup mode, setting the interval for which day you
want to save, for example: 1 will be every day, 2 will perform the DB
Backup in each second day and etc. Then set the Backup Time. The
database will backup automatically at the time you set periodically.
5. Input the directory for saving the backup files in the Backup Directory
area.
6. Click Apply to save the backup settings.

To run the RDR server:

1. Double-click run-RDRServer.bat from the RDR folder, the RDRServer
window opens.

2. To set parameters of the server, select File > Server Parameters Setting
from the window.

The RDR server is actually an FTP server that you configure the
communication port the file path and the user Setting fields:
All the settings should be equal to the setting of the RDR in the EMS-BGF
RDR setting and in the Max Days field, user can set how long the file saved
in the server system. If you set 365 days, the backup file will be saved for
365 days on the server and will automatically be removed after 365 days.
3. Select File > Refresh to refresh the files in the server list.
4. Select File > Start to run the RDR server.
5. Select File > Stop to stop the RDR server.
6. Select File > Exit to exit the RDR server.

To configure the RDR settings on Solaris:

1. On Solaris, to run the RDR server, run "runRDRServer.sh".
2. On Solaris, to stop the RDR server, run "stopRDRServer.sh".
3. To configure RDR settings on Solaris, open the configuration xml file of
RDR server under the path "/opt/EMS-BGF/rdrserver/etc/config.xml". User
can view the settings as below. All the settings are the same with the
settings on Windows.

<Config Name="RDRServerConfig">
<port>60022</port>
<userName>root</userName>
<passward>root</passward>
<dataPath>rdrbackup</dataPath>
<daysLimited>365</daysLimited>
</Config>


F
Alarm Export Using FTP
In this appendix:
Overview ......................................................................................................... F-1
Alarm Export Topology................................................................................... F-2
Alarm Export Mechanism ............................................................................... F-2
Alarm Format .................................................................................................. F-3
Using Alarm Export......................................................................................... F-5
Overview
The EMS-BGF supports the exporting of alarms via FTP. The alarm receiver
program installs an FTP server, which retrieves the exported alarm files from
the EMS-BGFs manager. The EMS-BGF manager sends the exported alarm
files to the receiver every X minutes, where the minimum value of X is 2.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary F-1

Alarm Export Using FTP EMS-BGF User Manual
Alarm Export Topology

The alarm export topology is shown in the following figure. The EMS-BGF
receives alarms from the network. The alarm export module transfers these
alarms to ASCII format and sends them to the alarm receiver via FTP.
Alarm Export Mechanism

A proxy program runs on the EMS-BGFs manager side. This obtains realtime
alarms from the manager, decodes them, converts them to a text record format,
saves them to a file, and then sends this file to the receiver program.
The receiver program installs an FTP server and retrieves the alarm export files
from the EMS-BGF manager.
F-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Alarm Export Using FTP
Alarm Format
The EMS-BGF manager sends alarm records in ASCII format. The alarm
export file consists of a header and alarm records. A blank line separates alarm
records. The header consists of two lines with the following format:
Export Time [1 space][dd/mm/yyyy hh:mm:ss]
Table F-1: Export title header
Event time Severity Object Probable cause

[21 characters] [13 characters] [42 characters] [44 characters]
Table F-2: Alarm record format
Event/EMS time Severity Object Probable cause

[21 characters] [13 characters] [42 characters] [44 characters]
Each alarm record consists of one line with the following attributes:
Time
Severity
Object
Probable cause
The following table describes the alarm record attributes.
Table F-3: Alarm record attributes
Attribute Format
Time [field delimiter of 2 spaces][dd/mm/yyyy hh:mm:ss]
Severity [field delimiter of 2 spaces][11 characters (left justified)]
Object [field delimiter of 2 spaces][42 characters (left justified)]
Probable cause [field delimiter of 2 spaces][44 characters (left justified)]
Severity Alarm Attribute

The alarm Severity attribute has one of the following values:
Critical
Major
Minor
Warning
Cleared

Object Attribute Format

The Object attribute has one of the formats listed in the following table.
Table F-4: Alarm Object attribute format
Format Example
NE NE-01
NE : XXX (Slot # YYY) NE-01 : TRS1_4RW (Slot # 205)
NE : XXX (Slot # YYY) XXX NE-01 : TPM1 (Slot # 1) TM2UB
NE : YYY-ZZ-A NE-01 : 209-SPI-1
NE : Slot # YYY NE-01 : Slot # 205
NE : YYY-ZZ-B NE-01 : 113-TG-E
NE : YYY-ZZ-AB NE-01 : 103-VC12-2W
NE : YYY-ZZ-B-A : ZZ-A-A-A NE-01 : 115-VC4-W-3 : TU12src-1-1-2
NE : YYY-ZZ-B : ZZ-A NE-01 : 113-MS-E : 113-AUG-1
Legend:
XXX: equipment or subequipment type, such as TRS1_4RW, TPM1, TR2AB,
and so on
YYY: slot number, such as 113, 209, 1, 5, 16, and so on
ZZ: object name, such as VC-4, VC-12, TG, SPI, and so on
A: object number, such as 1, 2, 3, 16, and so on
B: side

EMS-BGF User Manual Alarm Export Using FTP
Using Alarm Export

This section describes how to export alarms in the EMS-BGF.
Performing Alarm Export Settings

This section describes how to perform the alarm export settings.
To perform alarm export settings:

1. In the EMS-BGF main topology view window, select System > Alarm
Export Settings from the main menu. The Alarm Export Settings
window opens.

2. Enable the alarm export by selecting the Enable checkbox in the Alarm
Export Settings window.
3. Configure the settings as required to save the alarm export file.

Checking the Alarm Export Status

The alarm export file stored on the FTP server is named AlarmExport.txt.
Records are appended to the end of this file each time a new upload occurs.
Error information is written to a log file named AE_ErrLog.txt whenever a
connection to the FTP server cannot be made or when an alarm export file fails
to upload. The log file is located under the setup catalog.

G
Moving MEs on NMS
In this appendix:
Overview ........................................................................................................ G-1
Procedure of Moving MEs ............................................................................. G-1
Overview
This section describes how to move MEs from NMS in manual mode.
Procedure of Moving MEs

The procedure of moving MEs in manual mode can be performed as described
in this section.
To move MEs:
1. Login NMS client and select the Move ME operation from the toolbar.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary G-1

Moving MEs on NMS EMS-BGF User Manual
2. In the opened Move ME window, select the source EMS and target EMS
from the corresponding field, then click OK in the pop-up window.
3. After selecting related EMS, user can select some MEs from source EMS
and move them to target EMS side.
G-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Moving MEs on NMS
4. To change the ME ID, in the following window, enter a new ME ID and

then click Retry.
5. Click Validate. Then click OK in the opened confirmation window.

6. Click Apply. A status bar displays at the bottom of the window, showing
the procedure of moving MEs.
7. During the procedure, a Manual Mode window opens as below.

8. Before clicking Continue, you need to manually remove ME from the

source EMS and create ME on the target EMS through CLI.
a. At the source EMS, double-click /opt/EMS-BGF/server/sh/runCLI.sh
to run CLI. To get some helpful information about how to use it, you
can enter "Help".
b. Enter "Moveout NE" and reference parameters like "NEID" and

"FilePath" to export the information of the ME and delete it. The
exported file will be saved under the FilePath, and the file is named
by NEID.
If the ME ID has been changed, make sure that it is also changed in the
equipment. You can use the "Change NEID" command to perform the
operation.

c. At the target EMS side, run CLI the same as Step a, enter "Create NE"
and relevant parameters to create the ME in target EMS.
If ME ID has been changed, make sure that the value of the NE ID is

the new NE ID.
d. Import the saved information file which is exported at Step b. Enter
"Import NE" and related parameters like the NE ID and the files full
path.
9. Click Continue to complete the Move ME operation.

10. The result of the process displays in the Process Summary window.


H
Managing Event Logs
In this appendix:
Overview ........................................................................................................ H-1
Archive Settings ............................................................................................. H-2
Archive Immediately ...................................................................................... H-3
Viewing Archive Logs.................................................................................... H-4
Overview
User can manage all the logs in EMS-BGF. This section describes how to
manage the logs.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary H-1

Managing Event Logs EMS-BGF User Manual
Archive Settings
This section describes how to perform the archive settings.
To perform archive settings:

1. In the EMS-BGF main topology view window, select System > Event
Logs > Archive Settings in the main menu. The Archive Setting window
opens.
2. In the Parameter Setting area, set Auto Check, Interval Day and Check
Time as required.
Auto Check: If it is selected, EMS-BGF will automatically check the
parameters. If it is not selected, users have to check the parameters
manually.
Interval Day: Set the interval for which day you want to check, for
example: 1 will be every day, 2 will perform the DB Backup in each
second day and etc.
Check Time: Set the check time and then the parameters will be
checked automatically at the time you set periodically.
H-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Managing Event Logs
3. In the log type list, users can also set the Archive Over Max, Max Log
Count and Archive Directory as required.
Archive Immediately
This section describes how to archive logs immediately.
To archive logs immediately:

Logs > Archive Immediately in the main menu. The Archive
Immediately window opens.

2. Select the log types you want to archive and if the Clear After Archive
checkbox is selected, the corresponding Current Log Count will be
cleared after archive.
3. Click Apply to archive.
Viewing Archive Logs

This section describes how to view archive logs.
To view archive logs:

Logs > View Archive Logs in the main menu. The View Archive Logs
Files window opens.

EMS-BGF User Manual Managing Event Logs
2. Select the log types you want to view from the Select Log Type drop-down
list. The relevant log files will be displayed in the file list.
3. Select a log file in the file list and click Open, the View Archive Logs
window opens and lists the log detail for users to view.


I
Managing License
In this appendix:
License Overview ............................................................................................. I-1
License Control Mechanism ............................................................................. I-2
License Control Workflow ............................................................................... I-2
Managing Licenses in the EMS-BGF ............................................................... I-4
License Overview
EMS-BGF implements a new licensing control mechanism, which will monitor
and control the enabling/disabling of the licensing-controlled features.
The licensing-controlled features include the following objects:
Manageable NEs of EMS-BGF
BG-20 ADM4 pairs
Ethernet Ports of BG-20B_L2/L2M and BG-20C
MPLS Feature of L2 Cards
LCT licenses
MTNM I/F license
In EMS-BGF v11, a free 180-day evaluation with full management abilities is
provided to allow user using all the features of EMS-BGF. After that period,
the EMS-BGF will be expired and the NEs will be in unmanaged status. User
can only perform the 'Import License' operation in the EMS-BGF client.
When user imports the license, the evaluation stopped. The license manager
will control all the features according to the quota in the license bank, which is
the same as v10.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary I-1

Managing License EMS-BGF User Manual
The evaluation time is encrypted and recorded in the database. The license
manager will check the system time with evaluation time periodically to see
whether the evaluation has expired. Even if user reinstall the Operating System
or EMS-BGF, if he recovers the database, the evaluation time will be kept.
For more information about managing license, refer to <EMS-BGF License
Control>.
License Control Mechanism

EMS-BGF implements the licensing bank mechanism, which eliminate the
need of hardware protection device. The license is controlled by EMS-BGF for
the whole network, and is not bound with each individual NE.
The license can be purchased in packs, and added to the licensing bank. EMS
maintains the licensing bank, which is available for the whole network. When a
NE requires a license by enabling some licensing-control features, it should
apply the license from the EMS licensing bank. EMS licensing manager will
withdraw one license from the licensing bank and enable the required features
on the NE. If the licensing pool is empty, EMS licensing manager will reject
the request. Upon NE disabling, the license is returned to the licensing bank.
EMS will monitor the licensing bank and alert users when the licensing bank
reaches its limit (predefined threshold, such as 80%). Upon receive such alert,
user need purchase additional licenses and add it to the licensing bank.
User can also view the licensing bank content, including the number of each
license type, license usage.
License Control Workflow

The workflow for licensing management includes the below steps:
Install the EMS-BGF.
Sales force: use the Quotas and Host ID collection (QHI) tool to collect the
EMS-BGF host hardware identifier and all the quotas information (NEs,
ETY, SAM4 and LCT).
Sales force: import all the collected information into ERP system and send
to us.
Supply Chain: retrieve a Customer Order File (COF) from the ERP system.
Supply Chain: generate the license key with the License Generate Tool
according to the COF.
Supply Chain: burn the license key to the license CD and send it to the
customer.
I-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Managing License
Customer import the license key into the EMS-BGF licensing bank.
Customer can enable the licensing-control features from EMS-BGF.
The licensing management workflow is illustrated in the following figure.

Managing Licenses in the EMS-

BGF
This section describes how to manage licenses in the EMS-BGF.
To manage licenses in the EMS-BGF:

1. In the EMS-BGF main window, select System > License Manager from
the main menu. The License Manager View window opens.

EMS-BGF User Manual Managing License
2. Click the icon . The Open License File window opens. Select a license
file to import.
If the license is corrupted, the EMS-BGF displays a warning message.
3. To export the license file, click , the Save License File window opens.
Browse to the required folder and click Save. The EMS-BGF exports the
license file.


J
Fix Tool
In this appendix:
Using Fix Tool ................................................................................................. J-1
Using Fix Tool

Fix tool provides the fixes management under Windows. This section describes
how to use fix tool to manage the fixes in EMS-BGF.
To use fix tool:

1. Before run fix tool, make sure the EMS-BGF client and server are not
running in the computer.
426006-2421-173-A00 ECI Telecom Ltd. Proprietary J-1

Fix Tool EMS-BGF User Manual
2. Select Start > All Programs > EMS-BGF > Tools > Fix Tool in the
desktop. The EMS-BGF Fix Tool window opens.
J-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

EMS-BGF User Manual Fix Tool
3. In the Select Fix To Install area, click to select the fix file with the
format .tar or .zip.

Click Open to add the fix.

EMS-BGF User Manual Fix Tool
4. To install the fix, click the Install button.
5. The Installed Fixes List lists all the fixes that have been installed in EMS-
BGF, including the fix name and applicable version.
6. To remove the fix, select the fix in the Installed Fixes List and click
Remove.


Index
Changing a Password 3-21
A
Checking the Alarm Export Status F-6
About This Manual ix Clear NE Patches D-12
Accessing EMS-BGF 2-2 Clearing NE Configuration Data 15-2
Accessing the Create Tunnel XC Window Communications Alarms 13-55
7-8 Configuration Consistency Checking
Accessing the MS-SPRing List 11-38 15-3
Acknowledge Current Alarms 13-23 Configuration Management 1-2
Activate NE Patches D-7 Configuring ACL Profile 7-95
Activating and De-activating a MS- Configuring and Managing Cards 6-1
SPRing 11-40 Configuring and Managing Data Service
Adding New Domains 3-18 8-30
Adding New Roles 3-15 Configuring and Managing NEs 4-1
Adding New User Groups 3-11 Configuring Card Attributes 6-2
Adding New Users 3-4 Configuring Communication Parameters
Alarm Counter Bar 2-11 8-32
Alarm Export Mechanism F-2 Configuring DCC Over 2M 8-49
Alarm Export Topology F-2 Configuring Fault Management 13-3
Alarm Export Using FTP F-1 Configuring MSTP 6-73, 6-86
Alarm Format F-3 Configuring NE Attributes 4-24
Alarm Support of SM_10E from EMS Configuring OW Settings 6-17
6-150 Configuring PCM Timing 5-9
Archive Immediately H-3 Configuring Performance Attributes 14-
Archive Settings H-2 11
Auxiliary Features 2-16 Configuring SNCP Attributes 10-24
B Configuring STP and MSTP 11-22
Configuring Switch OAM 7-99
Batch Modify NE Names 4-25
Configuring the Synchronous Ethernet
BG-20 6-6 5-5
BG-20C 6-7 Configuring the Synchronous Timing
BG-30 6-7 Table 5-2
BG-40 6-4 Configuring the vFIB 6-70, 6-84, 6-133
BG-64 6-11 Configuring the VLAN 6-129
BIT Codes 13-46 Configuring Timing Source 5-1
C Configuring Tunnel XC WRED Profile
7-35
Cancel Activate NE Patches D-12
Connectivity Fault Management (CFM)
Card Layout Description 6-4 7-77
CFM Maintenance 7-90

Index EMS-BGF User Manual
Connectivity Testing 15-5 Deleting Users 3-9

Control Cards 6-152 Determining the Cause of an Alarm 13-
CoS Shapping and CoS WRED 6-77 21
Creating a MS-SPRing 11-30 DMEOP_4 6-142
Creating a Server Trail 8-13 DMFE_4_L1 6-36
Creating a Service Trail 8-15 DMFE_4_L2 6-73
Creating an EPL 6-58, 6-93 DMFX_4_L1 6-36
Creating CFM MA 7-80 DMFX_4_L2 6-120
Creating DCC XC 10-10 DMGE_1_L1 6-36
Creating Fiber Connections 8-6 DMGE_2_L2 6-120
Creating MPLS Ring ERP Control VSI DMGE_4_L1 6-38
12-10 DMGE_4_L2 6-121
Creating MPLS Services 7-43 DMGE_8_L2 6-121
Creating NEs 4-5 Document Contents x
Creating OH XC 10-8 Document Conventions xii
Creating P2MP Tunnel XC 7-20 Document Objectives x
Creating P2P Tunnel XC 7-15 Dual FRR 7-24
Creating PB MPtMP 6-61, 6-101 E
Creating PB PtP 6-96
Creating PB Ring ERP Control VSI 12- E1 Cards 6-20
4 E3 Cards 6-22
Creating PCM XC 10-12 Editing Domains 3-20
Creating Server XC 10-2 Editing Roles 3-16
Creating Service XC 10-5 Editing User Groups 3-13
Creating SM_10E XC 10-15 Editing Users 3-7
Creating SM10 XC 10-12 EFM Link OAM 6-81
Creating Tunnel XC 10-7 Embedded SW Patching D-2
Creating Tunnel XCs 7-8 EMS-BGF Architecture 1-5
Creating UMEs 4-2 EMS-BGF Client Icon Definition 2-13
Creating XC 10-2 EMS-BGF GUI Style 2-6
Creating, Editing and Deleting a MS- EMS-BGF Main Window 2-7
SPRing 11-40 EMS-BGF Overview 1-1
Customizing the Toolbar 2-16 EoP Cards 6-136
Equipment Alarms 13-48
D
ERPS Alarms 13-75
Data Cards 6-30 ESW_2G_8F/ESW_2G_8F_E 6-134
Data Management 1-3 Ethernet Ring Protection Switching
Data Service Overview 8-28 (ERPS) 12-1
DCC Terminations 4-22 Ethernet Service Alarms 13-74
Deleting Domains 3-20 Example A-3
Deleting Roles 3-17 Executing the VSI performance 6-110
Deleting User Groups 3-14 Export Alarms History to Files 13-27

EMS-BGF User Manual Index
Export Current Alarms to Files 13-23 L

Export NE Alarm Log to Files 13-45 L1 Cards 6-30
Exporting and Importing Trail Files 8- L1B_6F 6-30
25
L2 Cards 6-39
Exporting and Importing VSIs 6-117
License Control Mechanism I-2
Exporting and Importing XC Files 10-
25 License Control Workflow I-2
Exporting Trails 8-25 License Overview I-1
Link Loss Carry Forward (LLCF) 15-41
Exporting Tunnel XCs 7-34
Logging In/Logging Out of EMS-BGF
Exporting VSIs 6-117
2-3
Exporting XCs 10-25
Extended DCC 8-43 M
External Alarms 13-10, 13-72 Main EMS-BGF Tasks 1-2
F Main Menu Bar 2-8
Maintenance Management 1-3
Failover Processing E-4
Managing a Link Aggregation Group 6-
Fan Control Units 6-165 47, 6-79
Fast ReRoute (FRR) 7-100 Managing Alarms History 13-25
Fault Management 1-3, 13-1 Managing Archived Alarm Files 13-39
Fault Setting 13-3 Managing Archived Performance Files
FE_L12 6-122 14-11
Fiber Connections 8-5 Managing Cleared Alarms 13-28
Filtering Alarms History 13-27 Managing Cross Connections 10-1
Filtering Current Alarms 13-22 Managing Current Alarms 13-18
Filtering the Tunnel XC List 7-29 Managing Data Service 8-28
Fix Tool J-1 Managing Database 15-18
Forcing the Timing Source 15-39 Managing DCC and Overhead 8-31
Forcing User Logout 3-23 Managing DCC and Overhead for BG-40
G 8-33
Managing DCC and Overhead for the
General EMS-BGF Operational BG-20/BG-30/BG-64 8-37
Principles 1-6
Managing DCC for the BG-20C 8-42
Getting Started 2-1
Managing Domains 3-17
Group 8-3
Managing Ethernet Data Service in
H Integrated Mode 9-3
Hot Insertion 6-13 Managing Event Logs H-1
Managing Fiber Connections 8-9
I Managing License I-1
Importing Trail XML Files 8-26 Managing Licenses in the EMS-BGF I-4
Importing VSI XML Files 6-118 Managing MPLS Services 7-1
Importing XC XML Files 10-26 Managing MSP 1+1 11-15
Intended Audience ix Managing Multicast Configuration for
MPLS RootedMP/Leaf Service 7-73

Managing NE Alarms Log 13-44 Modifying Fiber Connection Attributes

Managing Network in Integrated Mode 8-8
9-1 Modifying NEs 4-28
Managing Network in Stand Alone Mode Monitoring and Reporting 13-7
8-1 Monitoring Events 13-32
Managing OSPF 4-16 Monitoring Performance 14-1
Managing Policers 6-53, 6-87 Moving MEs on NMS G-1
Managing Ports 6-39, 6-74, 6-123 MPLS BPDU Tunneling Service 7-56
Managing Reports 16-1 MPLS MPtMP Service 7-50
Managing Roles 3-14 MPLS Port Protection Switch 7-76
Managing SDH Service in Integrated MPLS PtP Service 7-44
Mode 9-2 MPLS RootedMP/Leaf Service 7-61
Managing Security Configuration 3-3 MPLS RootedMP/Root Service 7-67
Managing SNCP Attributes 15-27 MPLS Tunnel and tOAM Alarms 13-74
Managing Static Routes 4-15 MPS_2G_8F 6-135
Managing the Bandwidth Profile 6-52 MPS_4F 6-122
Managing the BG_OW 6-16 MPS_6F 6-122
Managing the Topology 8-2 MS DCC Swap 8-49
Managing the XC List 10-17 MS Shared Protection Ring (MS-SPRing)
Managing Threshold Settings 14-24 11-26
Managing TP 11-3 MSP 1+1 Maintenance Operation 15-26
Managing TP21_2 11-4 MSP 1+1 Overview 11-14
Managing TP63_1 11-10 MXC20 6-153
Managing TPS1_1 11-7 MXC4X 6-152
Managing Trails 8-11, 8-21
N
Managing Tunnel Service in Integrated
Mode 9-2 Navigator 2-11
Managing Tunnel XC Alarms 7-39 NE Data Backup 4-33
Managing Tunnels 7-4 NE Settings 13-4
Managing Unreported Alarms 13-35 NE Shelf View 2-12
Managing User Groups 3-10 NE Uploading 8-3
Managing Users 3-3 NE Version Live Update D-1
Managing Users and Security 3-1 Network Interfaces 4-20
Managing VSI Alarms 6-114 O
Managing VSI Services 6-58, 6-93
Object Attribute Format F-4
Manually Synchronizing Alarms 13-24
Object Tree 2-9
MCP30/MCP30B 6-154
Obtaining Technical Documentation xiii
MCP64 6-160
Obtaining the SFP Type 15-21
ME_2G_4F 6-135
OSPF Interfaces 4-23
MEOP_4/MEOP_4H 6-136
OSPF Overview 4-16
MESW_6F 6-39
Overall OSPF 4-18
MGE_1_L1 6-36
Overhead and DCC Overview 8-31

Overview ix, 2-1, 3-1, 4-1, 4-8, 5-1, 6-1, Preventive Maintenance Operations 15-
7-1, 7-4, 7-77, 8-1, 8-11, 9-1, 10-1, 2
11-1, 11-26, 12-1, 13-1, 14-1, 15-1, Preventive Maintenance Procedure 15-
16-1, A-1, B-1, D-1, E-1, F-1, G-1, 17
H-1 Procedure of Moving MEs G-1
P Properties Tab 2-10
PCM and EOP Alarms 13-72 R
PCM Cards 6-143 RDR E-1
PDH Cards 6-20 RDR Schemes E-2
Perform Card Maintenance 15-20 RDR Solutions E-2
Perform Maintenance on Timing 15-36 Reassignment Procedure 6-14
Perform Transmission Object Related Publications xi
Maintenance Operations 15-28
Removing NEs 4-31
Performance Data 14-1
Reset Performance Counters 14-25
Performance Management 1-4
Resetting a Card 15-20
Performing a Full Download 15-9
Resetting NEs 4-32
Performing a Full Upload 15-7
Routing Table 4-14
Performing AIS/RDI 15-32
Performing Alarm Export Settings F-5 S
Performing Alarm Notification Settings SAM-1/SAM-4 6-23
13-13 Saving NE Configuration Data 15-2
Performing an LED Test 15-17 SDH Cards 6-23
Performing Basic Parameter Backup in Searching for an NE 2-17
SFP 15-24 Searching the Topology Tree 2-19
Performing Embedded Version Security Management 1-4
Management 15-10
Service Alarms 13-68
Performing HO/LO Squelch
Setting NE Time 4-13
Configuration 11-44
Setting Performance Monitoring 14-17
Performing Maintenance Operations 11-
50, 15-1 Setting Performance Threshold 14-12
Performing NE Discovery 4-26 Setting Switch Performance Monitoring
14-26
Performing Performance Export
Configuration 14-34 Setting Switch Performance Threshold
14-28
Performing PRBS 15-33
Setting the Fan Work Mode 6-165
Performing Software Upgrade C-2
Setting the Laser On/Off Status 6-15
Performing TopoLink Discovery 8-10
Setting Trail Protection 8-19
Performing Tunnel XC Performance 7-
35 Severity Alarm Attribute F-3
Performing/Releasing Loopbacks 15-29 Severity Settings 13-11
PM Counters and TCA 14-30 Slot Assignment 4-8
Policer Value Rules 6-92 Slot Assignment for BG-20 and BG-30
4-8
Port Mirror 7-97
Slot Assignment for BG-40 4-10
Power Units 6-164

Slot Assignment for BG-64 4-11 U

Slot Assignment for OW 6-16 Uploading Tunnel XCs 7-32
Slot Reassignment 6-14 Using Alarm Export F-5
SM_10E Card 6-145 Using Data Service Creation Window 8-
SM_10E Card Overview 6-145 29
SM_10E Slot Assignment 6-147 Using Fix Tool J-1
SM_C37.94 6-149 Using Maintenance List 15-28
SM10 Card 6-143 Using Menus 2-5
SM10 Card Overview 6-143 Using Online Help 2-19
SM10 Slot Assignment 6-144 Using the EMS-BGF Graphic User
SMD4 6-24 Interface 2-6
SMQ1 6-25 Using the MPLS VSI List 7-73
SMQ1&4 6-26 Using the MS-SPRing List 11-37
SMS16 6-27 Using the Report Window 16-2
Software Upgrade C-1 Using the Tunnel XC List 7-27
Software Upgrade Overview C-1 Using the VSI List 6-67, 6-107
Software Upgrade Workflow C-2 Using Trail Creation Window 8-12
Sorting Alarms History 13-27
V
Sorting Current Alarms 13-22
Starting EMS-BGF 2-2 VC-4 Contiguous Concatenation 6-24
Status Bar 2-8 View Scheduled Activation Info D-11
STP and MSTP Overview 11-20 Viewing a Chart for Current Alarms 13-
24
Summary of Menu Commands B-1
Viewing a MS-SPRing 11-39
Supported Cards 7-3, 7-79, 11-21
Viewing Actual Routes 4-14
Supported Modules 6-143, 6-146
Viewing Alarm Log File 13-17
Switching to Protection 15-34
Viewing Archive Logs H-4
T Viewing Current Alarms 13-18
Technical Assistance xiv Viewing Current Performance 14-6
The Keyboard 2-5 Viewing ERPS Instance 12-15
The Security Configuration Window 3-2 Viewing Historical Alarms History 13-
Threshold Crossing Alarms 13-69 25
Timing Alarms 13-68 Viewing K1/K2 Information 11-50
Title Bar 2-7 Viewing Laser Performance Threshold
Toolbar 2-8 14-20
Topology View 2-8 Viewing NE Alarm Log 13-44
TP Overview 11-2 Viewing Performance Data 14-5
TPG Maintenance 11-13 Viewing Performance History 14-7
Trap Manager Table 15-40 Viewing PPI Status 13-47
Troubleshooting Alarms 13-48 Viewing Recent Performance 14-10
Viewing the Action Log 3-27
Viewing the Security Log 3-25

Viewing TMU Working Mode 15-36 Working with LCT-BGF 3-24

Viewing Tunnel XC OAM State 7-42 Working with MSP 1+1 11-14
Viewing/Editing/Deleting a Tunnel XC Working with Protection 11-1
7-30 Working with STP and MSTP 11-20
Viewing/Exporting Laser Performance Working with TP 11-2
14-21
X
W
XC and Trail Management 1-2
What is the EMS-BGF? 1-1 XIO30-1/XIO30-4/XIO30-
Workflow 3-2, 4-2, 6-1, 7-3, 7-7, 8-1, 8- 16/XIO30Q_1&4 6-27
11, 8-28, 9-1, 10-1, 11-1, 11-21, 11- XML and DTDs A-1
28, 12-2, 13-2, 14-5, 15-1, D-2
XML Components A-2
Working in the EMS-BGF Environment
XML File A-1
2-5
XML File Structure A-3
Working Mode Bar 2-10
Working with Cards 6-2

EMS-BGF UM A00 V12.1 en PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EMS-BGF UM A00 V12.1 en PDF

Uploaded by

Copyright:

Available Formats

EMS-BGF

Copyright by ECI Telecom, 2002-2010. All rights reserved worldwide.

EMS-BGF Overview ................................................................. 1-1

Getting Started......................................................................... 2-1

Managing Users and Security ................................................ 3-1

Configuring and Managing NEs ............................................. 4-1

426006-2421-173-A00 ECI Telecom Ltd. Proprietary i

Configuring NE Attributes ............................................................................... 4-24

Configuring Timing Source .................................................... 5-1

Configuring and Managing Cards .......................................... 6-1

Managing MPLS Services ....................................................... 7-1

Managing Network in Stand Alone Mode .............................. 8-1

ii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

Extended DCC ............................................................................................... 8-43

Managing Network in Integrated Mode .................................. 9-1

Managing Cross Connections .............................................. 10-1

Working with Protection ....................................................... 11-1

Ethernet Ring Protection Switching (ERPS) ....................... 12-1

Fault Management ................................................................. 13-1

426006-2421-173-A00 ECI Telecom Ltd. Proprietary iii

BIT Codes .................................................................................................... 13-46

Monitoring Performance ....................................................... 14-1

Performing Maintenance Operations ................................... 15-1

Managing Reports ................................................................. 16-1

XML File ................................................................................... A-1

Summary of Menu Commands .............................................. B-1

Software Upgrade ................................................................... C-1

iv ECI Telecom Ltd. Proprietary 426006-2421-173-A00

NE Version Live Update ......................................................... D-1

Alarm Export Using FTP ......................................................... F-1

Moving MEs on NMS .............................................................. G-1

Managing Event Logs ............................................................ H-1

Managing License .................................................................... I-1

Fix Tool ..................................................................................... J-1

Index .......................................................................................... I-1

426006-2421-173-A00 ECI Telecom Ltd. Proprietary v

vi ECI Telecom Ltd. Proprietary 426006-2421-173-A00

426006-2421-173-A00 ECI Telecom Ltd. Proprietary vii

Table 13-13: ERPS Alarms ..................................................................................... 13-75

viii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

426006-2421-173-A00 ECI Telecom Ltd. Proprietary ix

x ECI Telecom Ltd. Proprietary 426006-2421-173-A00

Monitoring Performance (on page 14-1) describes the EMS-BGF

426006-2421-173-A00 ECI Telecom Ltd. Proprietary xi

Note: Text set off in this manner presents clarifying

CAUTION: Text set off in this manner indicates that failure

WARNING: Text set off in this manner indicates that failure

LASER WARNING: Text set off in this manner indicates

xii ECI Telecom Ltd. Proprietary 426006-2421-173-A00

ESD: Text set off in this manner indicates information on

TIP: Text set off in this manner includes helpful information

IMPORTANT: Text set off in this manner presents essential

426006-2421-173-A00 ECI Telecom Ltd. Proprietary xiii

ECI Telecom's XDM and BroadGate product lines are

ECI Telecom's qualification lab is accredited by A2LA for

xiv ECI Telecom Ltd. Proprietary 426006-2421-173-A00

What is the EMS-BGF?

426006-2421-173-A00 ECI Telecom Ltd. Proprietary 1-1

Main EMS-BGF Tasks

XC and Trail Management

1-2 ECI Telecom Ltd. Proprietary 426006-2421-173-A00

426006-2421-173-A00 ECI Telecom Ltd. Proprietary 1-3

1-4 ECI Telecom Ltd. Proprietary 426006-2421-173-A00