LCT-NPT v6.0 User Guide

LCT-NPT®
Version 6.0
User Guide
LCT-NPT User Guide
V6.0
Catalog No: X35818
Drawing No: 4BGHT6-EMSW-461
April 2017
Rev01
ECI Telecom's NPT-1800, NPT-1200, NPT-1050, NPT-1021, and NPT-1010 are CE2.0 certified.
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.
ECI Telecom's management applications run on VMWare virtualization hypervisors.
© Copyright by ECI Telecom, 2013-2017. 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.
All documentation and/or disk and all information and/or data contained in the documentation and/or disk ["ECI Telecom's Proprietary"] is ECI
Telecom's proprietary and is subject to all copyright, patent, and other laws protecting intellectual property, and any international treaty provisions,
as well as any specific agreement protecting ECI Telecom's rights in the aforesaid information. Any use of ECI Telecom's Proprietary for any purposes
[included but not limited: published, reproduced, or disclosed to third parties, in whole or in part] other than those for which it was disclosed, without
the express prior written permission of ECI Telecom, is strictly forbidden.
ECI Telecom's Proprietary is provided "AS IS" and may contain flaws, omissions, or typesetting errors. No responsibility and or liability whatsoever are
assumed by ECI Telecom for you or any other party, for the use thereof, nor for the rights of third parties, nor for any loss or damage whatsoever or
howsoever caused, arising directly or indirectly in connection with ECI Telecom's Proprietary, which may be affected in any way by the use and/or
dissemination thereof. ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or specifications including
any change in and to the ECI Telecom's Proprietary.
Any representation(s) in ECI Telecom's Proprietary concerning performance of ECI Telecom's product(s) are for informational purposes only and are
not warranties of product performance or otherwise, either express or implied. No warranty is granted nor liability assumed in relation thereto, unless
specifically undertaken in ECI Telecom's sales contract or order confirmation. ECI Telecom's Proprietary is periodically updated, and changes will be
incorporated in subsequent editions. All graphics included in this document are for illustrative purposes only and might not correspond with your
specific product version.
The documentation and/or disk and all information contained therein is owned by ECI 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 ECI Telecom's Proprietary, 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.
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 ECI Telecom's Proprietary 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 (when provided by ECI
Telecom) and that such instructions were understood by them. 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 failure to fulfill in whole or in part the "Before
You Start/Safety Guidelines" instructions.
Contents
Useful information ............................................................................................... xxi
Related documents ............................................................................................................................. xxi
Contact information ............................................................................................................................ xxi
1 LCT-NPT overview ....................................................................................... 1-1
2 Install the LCT-NPT ...................................................................................... 2-1
3 Log in and configure NE with boot configuration tool .................................. 3-1

3.1 IP address in boot status........................................................................................................ 3-3
3.2 Configure basic parameters ................................................................................................... 3-5
3.3 Download embedded software and FPGA file for BG-40/BG-20/BG-20C ............................. 3-9
3.4 Download embedded software for BG-30/BG-64/NPT NEs ................................................ 3-11
3.5 Obtain MAC data for BG-30/BG-64/NPT NEs ...................................................................... 3-12
3.6 Obtain IDPROM data for BG-20/BG-20C/BG-30/BG-64/NPT NEs ....................................... 3-13
3.7 Format NVRAM for BG-30/BG-64/NPT NEs ......................................................................... 3-13
3.8 Obtain NVRAM information for BG-30/BG-64/NPT NEs...................................................... 3-14
3.9 Configure "No Recovery Next Startup" for BG-20 ............................................................... 3-14
3.10 Configure "Serial Port Close" for BG-20 ............................................................................... 3-15
3.11 Configure NE Restart Mode for BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-
1050/NPT-1010 .................................................................................................................... 3-16
4 Get started .................................................................................................. 4-1

4.1 Start the LCT client ................................................................................................................. 4-1
4.2 Configure parameters ............................................................................................................ 4-4
4.3 Configure static IP routes....................................................................................................... 4-4
4.4 Manage reports ..................................................................................................................... 4-6
4.5 Use online help ...................................................................................................................... 4-7
5 LCT-NPT security management .................................................................... 5-1

5.1 Configure the LCT-NPT work mode ....................................................................................... 5-1
5.2 Request to log in as master ................................................................................................... 5-2
5.3 Request to log in as monitor .................................................................................................. 5-2
5.4 View the security log.............................................................................................................. 5-3
5.5 View the action log ................................................................................................................ 5-4
5.6 Configure IEEE 802.1X port-based authentication ................................................................ 5-5
ECI Telecom Ltd. Proprietary iii

LCT-NPT® User Guide Contents
5.7 Configure RADIUS client settings ........................................................................................... 5-7
6 NE management .......................................................................................... 6-1

6.1 NE types overview ................................................................................................................. 6-1
6.1.1 BG-40 ....................................................................................................................................... 6-1
6.1.2 BG-20 ....................................................................................................................................... 6-2
6.1.3 BG-20C..................................................................................................................................... 6-3
6.1.4 BG-30 ....................................................................................................................................... 6-3
6.1.5 BG-64 ....................................................................................................................................... 6-4
6.1.6 NPT-1200 ................................................................................................................................. 6-5
6.1.7 NPT-1020 ................................................................................................................................. 6-6
6.1.8 NPT-1021 ................................................................................................................................. 6-6
6.1.9 NPT-1030 ................................................................................................................................. 6-7
6.1.10 NPT-1050 ................................................................................................................................. 6-7
6.1.11 NPT-1800 ................................................................................................................................. 6-9
6.1.12 NPT-1200i .............................................................................................................................. 6-11
6.2 Assign slots........................................................................................................................... 6-12
6.3 NE frame mode definition ................................................................................................... 6-13
6.4 Reassign a shelf .................................................................................................................... 6-13
6.5 Set BG-20EH DC redundancy ............................................................................................... 6-15
6.6 Routing table management ................................................................................................. 6-15
6.6.1 View actual routes................................................................................................................. 6-15
6.6.2 Manage static routes............................................................................................................. 6-16
6.7 OSPF management............................................................................................................... 6-17
6.7.1 Configure overall OSPF settings ............................................................................................ 6-19
6.7.2 Manage OSPF network interfaces ......................................................................................... 6-21
6.7.3 Configure DCC terminations .................................................................................................. 6-24
6.7.4 View OSPF interfaces ............................................................................................................ 6-25
6.8 Configure NE attributes ....................................................................................................... 6-26
6.9 Manage DCC and overhead ................................................................................................. 6-28
6.9.1 Configure communication parameters ................................................................................. 6-29
6.9.2 Manage DCC and overhead for BG-40 .................................................................................. 6-31
6.9.3 Manage DCC and overhead for BG-20/BG-20C/BG-30/BG-64 and NPT NEs......................... 6-33
6.10 Reset NEs ............................................................................................................................. 6-36
6.11 Back up NE data ................................................................................................................... 6-37
6.12 View NE system resources ................................................................................................... 6-38
6.13 Set card maximum traffic in BG-40 ...................................................................................... 6-39
ECI Telecom Ltd. Proprietary iv

6.14 View NE power consumption management status ............................................................. 6-40
7 NE configuration and management in IP/MPLS ........................................... 7-1

7.1 Logical interface management .............................................................................................. 7-1
7.1.1 Manage loopback interfaces ................................................................................................... 7-2
7.1.2 Manage IRB interfaces ............................................................................................................ 7-3
7.1.3 View IP interface list ................................................................................................................ 7-6
7.2 IP routing management ......................................................................................................... 7-7
7.2.1 View routing options ............................................................................................................... 7-7
7.2.2 View policy options ................................................................................................................. 7-8
7.2.3 Manage the routing policy ...................................................................................................... 7-8
7.2.4 View policy state ................................................................................................................... 7-11
7.2.5 Manage static routes............................................................................................................. 7-12
7.2.6 View actual routes................................................................................................................. 7-13
7.2.7 View forwarding table ........................................................................................................... 7-14
7.2.8 View multicast forwarding table ........................................................................................... 7-15
7.2.9 View the ARP table ................................................................................................................ 7-16
7.2.10 Perform IP ping and trace route ............................................................................................ 7-17
7.3 OSPF protocol management in IP/MPLS.............................................................................. 7-18
7.3.1 Manage OSPF instances ........................................................................................................ 7-20
7.3.2 Manage OSPF areas ............................................................................................................... 7-22
7.3.3 Manage OSPF LIFs ................................................................................................................. 7-27
7.3.4 Manage OSPF virtual links ..................................................................................................... 7-30
7.3.5 Manage OSPF key chain templates ....................................................................................... 7-32
7.3.6 View OSPF instance status .................................................................................................... 7-34
7.3.7 View OSPF LIF status ............................................................................................................. 7-34
7.3.8 View OSPF virtual link status ................................................................................................. 7-36
7.3.9 View OSPF neighbors ............................................................................................................ 7-36
7.3.10 View the OSPF database ....................................................................................................... 7-36
7.3.11 View LDP FRR status .............................................................................................................. 7-36
7.4 IS-IS protocol management in IP/MPLS ............................................................................... 7-36
7.4.1 Manage IS-IS instances .......................................................................................................... 7-39
7.4.2 Manage IS-IS levels ................................................................................................................ 7-41
7.4.3 Manage IS-IS LIFs ................................................................................................................... 7-42
7.4.4 View the IS-IS instance status ............................................................................................... 7-44
7.4.5 View IS-IS LIF status ............................................................................................................... 7-44
7.4.6 View IS-IS adjacency .............................................................................................................. 7-44
7.4.7 View the IS-IS database ......................................................................................................... 7-44
ECI Telecom Ltd. Proprietary v

7.4.8 View the LDP FRR status........................................................................................................ 7-44

7.5 LDP protocol management in IP/MPLS ................................................................................ 7-44
7.5.1 Manage the LDP instance ...................................................................................................... 7-46
7.5.2 Manage LDP/tLDP entities .................................................................................................... 7-48
7.5.3 Configure LDP for LIFs ........................................................................................................... 7-49
7.5.4 Manage LDP peer security .................................................................................................... 7-50
7.5.5 View LDP fixed attributes ...................................................................................................... 7-51
7.5.6 View hello adjacencies .......................................................................................................... 7-51
7.5.7 View LDP peers ...................................................................................................................... 7-51
7.5.8 View FEC ................................................................................................................................ 7-51
7.5.9 View LDP session status ........................................................................................................ 7-51
7.5.10 View distributed label ........................................................................................................... 7-51
7.5.11 View learned label ................................................................................................................. 7-52
7.6 VRRP management .............................................................................................................. 7-52
7.6.1 Manage VRRP configuration ................................................................................................. 7-53
7.6.2 View VRRP state .................................................................................................................... 7-57
7.6.3 View VRRP statistics .............................................................................................................. 7-58
7.7 BGP protocol management in IP/MPLS ............................................................................... 7-60
7.7.1 Manage BGP instances .......................................................................................................... 7-63
7.7.2 Manage BGP neighbor groups .............................................................................................. 7-66
7.7.3 Manage BGP neighbors ......................................................................................................... 7-68
7.7.4 View BGP instance state........................................................................................................ 7-69
7.7.5 View BGP neighbor group state ............................................................................................ 7-70
7.7.6 View BGP neighbor state ....................................................................................................... 7-71
7.7.7 View BGP route in state ........................................................................................................ 7-72
7.7.8 View BGP route out state ...................................................................................................... 7-73
7.7.9 View BGP route local state .................................................................................................... 7-74
7.7.10 View BGP statistics ................................................................................................................ 7-75
7.8 PIM protocol management in IP/MPLS ............................................................................... 7-76
7.8.1 Manage PIM instances .......................................................................................................... 7-77
7.8.2 Manage PIM interfaces ......................................................................................................... 7-79
7.8.3 Manage PIM rendezvous points ............................................................................................ 7-82
7.8.4 View PIM interface status ..................................................................................................... 7-83
7.8.5 View PIM join status .............................................................................................................. 7-84
7.8.6 View PIM neighbors .............................................................................................................. 7-85
7.8.7 View PIM RP status................................................................................................................ 7-86
7.8.8 View PIM source.................................................................................................................... 7-87
ECI Telecom Ltd. Proprietary vi

7.8.9 View PIM statistics ................................................................................................................ 7-88

7.9 IGMP protocol management in IP/MPLS ............................................................................. 7-89
7.9.1 Manage IGMP instances ........................................................................................................ 7-93
7.9.2 Manage IGMP interfaces ....................................................................................................... 7-94
7.9.3 Manage IGMP static database .............................................................................................. 7-96
7.9.4 View IGMP instance status .................................................................................................... 7-97
7.9.5 View IGMP interface status ................................................................................................... 7-98
7.9.6 View IGMP group status ........................................................................................................ 7-99
7.9.7 View IGMP statistics ............................................................................................................ 7-100
7.9.8 View group membership database records ........................................................................ 7-101
7.10 DHCP protocol management in IP/MPLS ........................................................................... 7-102
7.10.1 Manage DHCP relay agent................................................................................................... 7-104
7.10.2 View DHCP statistics ............................................................................................................ 7-107
7.11 BFD protocol management in IP/MPLS ............................................................................. 7-108
7.11.1 Configure BFD protocol ....................................................................................................... 7-108
7.11.2 Manage BFD section sessions ............................................................................................. 7-109
7.11.3 Manage IP BFD sessions ...................................................................................................... 7-110
7.11.4 View multihop IP BFD protocol ........................................................................................... 7-111
7.11.5 Manage multihop IP BFD sessions ...................................................................................... 7-112
7.11.6 View BFD status ................................................................................................................... 7-113
7.11.7 View BFD statistics .............................................................................................................. 7-114
7.11.8 Manage BD-LSP BFD ............................................................................................................ 7-114
7.11.9 Configure PW BFD ............................................................................................................... 7-116
7.12 Manage the slow path ....................................................................................................... 7-117
7.12.1 Configure the slow path ...................................................................................................... 7-117
7.12.2 View the slow path state ..................................................................................................... 7-119
7.13 View resource budgets ...................................................................................................... 7-120
7.14 Configure IP/MPLS connection settings............................................................................. 7-120
7.15 Perform interface management ........................................................................................ 7-123
7.15.1 Perform ETY interface configuration ................................................................................... 7-125
7.15.2 Create the LIF ...................................................................................................................... 7-127
7.15.3 Configure the LIF ................................................................................................................. 7-132
7.15.4 Delete the LIF ...................................................................................................................... 7-133
7.15.5 Manage INET LIF ARP entries .............................................................................................. 7-133
7.16 Create a LAG with LIFs ....................................................................................................... 7-134
7.17 Configure DiffServ block .................................................................................................... 7-135
7.18 Configure FRR block ........................................................................................................... 7-136
ECI Telecom Ltd. Proprietary vii

7.19 Manage MSTP .................................................................................................................... 7-136

7.19.1 Configure MSTP settings ..................................................................................................... 7-136
7.19.2 Manage MSTP interfaces .................................................................................................... 7-139
7.19.3 Manage MSTP instance ....................................................................................................... 7-140
7.20 Configure port mirroring.................................................................................................... 7-141
7.21 Manage profiles ................................................................................................................. 7-142
7.21.1 Create VLAN ID range profiles ............................................................................................. 7-142
7.21.2 Create vFIB quota profiles ................................................................................................... 7-143
7.21.3 Create port TPID profiles ..................................................................................................... 7-144
7.21.4 Create TPID profiles............................................................................................................. 7-145
7.21.5 Create MTU profiles ............................................................................................................ 7-145
7.21.6 Create CoS group profiles.................................................................................................... 7-146
7.21.7 Create QoS group profiles ................................................................................................... 7-147
7.21.8 Create BSC policer profiles .................................................................................................. 7-153
7.21.9 Create Policer profiles ......................................................................................................... 7-154
7.21.10 Create WRED profiles .......................................................................................................... 7-155
7.21.11 Create Firewall profiles ....................................................................................................... 7-156
7.21.12 Create Flow Block profiles ................................................................................................... 7-160
7.21.13 Create Slow Path policer profiles ........................................................................................ 7-161
7.21.14 Create Sampling profiles ..................................................................................................... 7-161
7.21.15 Create PM defects profiles .................................................................................................. 7-162
7.21.16 Create alarm profiles ........................................................................................................... 7-164
7.21.17 Manage profiles in the profile list ....................................................................................... 7-167
8 Configure and manage cards ....................................................................... 8-1

8.1 Card assignment tables .......................................................................................................... 8-1
8.1.1 Card assignment for BG-40 ..................................................................................................... 8-1
8.1.3 Card assignment for BG-20C ................................................................................................... 8-4
8.1.6 Card assignment for NPT-1200 ............................................................................................... 8-7
8.1.7 Card assignment for NPT-1020 ............................................................................................. 8-10
8.1.12 Card assignment for NPT-1200i............................................................................................. 8-15
ECI Telecom Ltd. Proprietary viii

8.2 Work with cards ................................................................................................................... 8-16

8.2.1 Card move ............................................................................................................................. 8-17
8.2.2 Configure card attributes ...................................................................................................... 8-20
8.2.3 Configure temperature thresholds ....................................................................................... 8-22
8.2.4 Hot insertion ......................................................................................................................... 8-24
8.2.5 Slot reassignment .................................................................................................................. 8-25
8.2.6 Set the laser on/off status ..................................................................................................... 8-28
8.2.7 Set user label and description per port ................................................................................. 8-30
8.3 BG_OW management .......................................................................................................... 8-31
8.3.1 Assign OW slot ...................................................................................................................... 8-31
8.3.2 Configure OW settings .......................................................................................................... 8-31
8.4 Configure PDH cards ............................................................................................................ 8-33
8.5 SDH card configuration ........................................................................................................ 8-34
8.5.1 Configure SAM-1/SAM-4 cards ............................................................................................. 8-35
8.5.2 Configure VC-4 contiguous concatenation ............................................................................ 8-36
8.5.3 Configure SMQ1&4 cards ...................................................................................................... 8-37
8.6 L1 data card configuration ................................................................................................... 8-37
8.6.1 Configure L1B_6F cards ......................................................................................................... 8-39
8.6.2 Configure DMGE_4_L1 cards................................................................................................. 8-42
8.7 L2 data card configuration ................................................................................................... 8-42
8.7.1 MESW_6F .............................................................................................................................. 8-47
8.7.2 DMFE_4_L2 ........................................................................................................................... 8-61
8.7.3 Configure MSTP (MESW_6F and DMFE_4_L2) ...................................................................... 8-81
8.7.4 View and manage VSI objects (MESW_6F and DMFE_4_L2) ................................................ 8-81
8.7.5 DMXE_48_L2 ......................................................................................................................... 8-86
8.7.6 MPOE_12G ............................................................................................................................ 8-91
8.7.7 FE_L12 ................................................................................................................................... 8-94
8.8 Data hybrid cards ............................................................................................................... 8-109
8.8.1 Activate/Deactivate ports ................................................................................................... 8-112
8.8.2 Reassign DHXE_2 to DHXE_4/DHXE_4O .............................................................................. 8-113
8.9 EoP cards ............................................................................................................................ 8-114
8.9.1 MEOP_4/MEOP_4H ............................................................................................................. 8-114
8.9.2 DMEOP_4 ............................................................................................................................ 8-123
8.10 Matrix cards ....................................................................................................................... 8-123
8.10.1 XIO30-1/XIO30-4/XIO30-4B/XIO30-16/XIO30Q_1&4 ......................................................... 8-123
8.10.2 XIO64/XIO16_4 .................................................................................................................... 8-125
8.10.3 CPTS100/CPS100 ................................................................................................................. 8-134
ECI Telecom Ltd. Proprietary ix

8.10.4 CPTS320/CPS320 ................................................................................................................. 8-140

8.10.5 CPS50................................................................................................................................... 8-140
8.10.6 CS10 ..................................................................................................................................... 8-149
8.10.7 CS5 ....................................................................................................................................... 8-150
8.10.8 MCPTS100/MCPS100 .......................................................................................................... 8-153
8.11 Aggregate card ................................................................................................................... 8-161
8.11.1 AIM100/AIM100P................................................................................................................ 8-161
8.12 NFV cards ........................................................................................................................... 8-161
8.12.1 NFVG_4 ............................................................................................................................... 8-161
8.12.2 NFVX card ............................................................................................................................ 8-167
8.13 CES cards ............................................................................................................................ 8-167
8.13.1 DMCE1_32 ........................................................................................................................... 8-167
8.13.2 DMCES1_4 ........................................................................................................................... 8-180
8.13.3 MSE1_16 ............................................................................................................................. 8-206
8.13.4 TMSE1_8 ............................................................................................................................. 8-206
8.13.5 MSC_2_8 ............................................................................................................................. 8-207
8.13.6 MS1_4 (Ezchip) .................................................................................................................... 8-216
8.13.7 MSE1_32 (Ezchip) ................................................................................................................ 8-216
8.14 Optics cards........................................................................................................................ 8-216
8.14.1 Optical Base Card (OBC) ...................................................................................................... 8-216
8.15 PCM cards .......................................................................................................................... 8-224
8.15.1 SM10 card ........................................................................................................................... 8-224
8.15.2 SM_10E card ....................................................................................................................... 8-227
8.15.3 EM_10E ............................................................................................................................... 8-254
8.16 MXC cards .......................................................................................................................... 8-263
8.16.1 MXC4X ................................................................................................................................. 8-263
8.16.2 MXC-20/MXC-20C ............................................................................................................... 8-264
8.16.3 MXC-1020 ............................................................................................................................ 8-264
8.16.4 MXC-1021 ............................................................................................................................ 8-266
8.17 Control cards ...................................................................................................................... 8-267
8.17.1 MCP30/MCP30B .................................................................................................................. 8-267
8.17.2 MCP64 ................................................................................................................................. 8-275
8.17.3 MCP-1200 ............................................................................................................................ 8-281
8.17.4 MCPS-1010 .......................................................................................................................... 8-286
8.17.5 MCP-1050 ............................................................................................................................ 8-287
8.18 Power units ........................................................................................................................ 8-288
8.18.1 Power units of BG-40 .......................................................................................................... 8-288
ECI Telecom Ltd. Proprietary x

8.18.2 Power units of BG-20 .......................................................................................................... 8-288

8.18.3 Power units of BG-30 .......................................................................................................... 8-290
8.18.4 Power units of BG-64 .......................................................................................................... 8-290
8.18.5 Power units of NPT-1200 .................................................................................................... 8-291
8.18.6 Power units of NPT-1020/NPT-1021 ................................................................................... 8-293
8.18.9 Assign power units for BG-64/NPT-1200/NPT-1020/NPT-1021 .......................................... 8-299
8.19 Fan control units ................................................................................................................ 8-304
8.19.1 Set the fan work mode ........................................................................................................ 8-304
8.20 DMGE_8_POS card............................................................................................................. 8-308
8.20.1 Manage ports ...................................................................................................................... 8-309
8.20.2 Manage a LAG ..................................................................................................................... 8-318
8.20.3 POS mirroring ...................................................................................................................... 8-318
8.21 TSHU_48V card .................................................................................................................. 8-323
8.22 MXP10 card ........................................................................................................................ 8-323
8.22.1 MXP10 supported modules ................................................................................................. 8-326
8.22.2 MXP10 slot assignment ....................................................................................................... 8-327
8.22.3 Define port rate and density ............................................................................................... 8-331
8.22.4 Manage ports ...................................................................................................................... 8-334
8.22.5 Perform ODU MSI configuration ......................................................................................... 8-340
8.22.6 Perform latency measurement ........................................................................................... 8-342
8.23 TM10 .................................................................................................................................. 8-343
8.24 Tributary protection card................................................................................................... 8-343
8.24.1 TPEH8_1 .............................................................................................................................. 8-343
9 Configure and manage cards in IP/MPLS ..................................................... 9-1

9.1 Card Description of IP/MPLS NEs ........................................................................................... 9-1
9.2 Perform CSFP management in DH cards................................................................................ 9-2
9.3 Manage OTN ports in DHXE_4O ............................................................................................ 9-6
9.4 Manage the CIPS1T card ...................................................................................................... 9-10
9.5 Manage MSC_2_8 ................................................................................................................ 9-13
9.5.1 Activate/Deactivate the MSC_2_8 ports ............................................................................... 9-14
9.5.2 Configure the MSC_2_8 card ................................................................................................ 9-16
9.5.3 Activate VC12/E1 and VT1.5/DS1 .......................................................................................... 9-17
9.5.4 Manage MSP1+1 ................................................................................................................... 9-24
9.6 Perform port rate settings in MS1_4 ................................................................................... 9-29
ECI Telecom Ltd. Proprietary xi

9.7 Manage the MCP-1800 ........................................................................................................ 9-30

9.7.1 Manage the CF card .............................................................................................................. 9-34
9.8 Manage the MCIPS320 ........................................................................................................ 9-35
9.9 Manage power units of IP/MPLS NEs .................................................................................. 9-36
9.10 Manage the fan units of IP/MPLS NEs ................................................................................. 9-38
9.10.1 Manage the fan units of NPT-1800 ....................................................................................... 9-38
9.10.2 Manage the fan units of NPT-1200i ...................................................................................... 9-41
10 Configure timing source ............................................................................ 10-1

10.1 Set NE time .......................................................................................................................... 10-1
10.2 Manage NTP configuration .................................................................................................. 10-2
10.2.1 Perform NTP configuration ................................................................................................... 10-3
10.2.2 Perform NTP configuration in IP/MPLS ................................................................................. 10-5
10.2.3 View NTP association and status ........................................................................................... 10-6
10.3 Configure the synchronous timing table ............................................................................. 10-7
10.4 Configure synchronous ethernet ....................................................................................... 10-14
10.5 Precision Time Protocol (PTP) ............................................................................................ 10-20
10.5.1 PTP TMU supported cards ................................................................................................... 10-29
10.5.2 Manage the PTP TMU ......................................................................................................... 10-30
10.5.3 View the PTP TMU state ...................................................................................................... 10-37
10.5.4 View the PTP port state for IP/MPLS ................................................................................... 10-38
10.5.5 Manage the PTP port .......................................................................................................... 10-38
10.5.6 View PTP port state ............................................................................................................. 10-41
10.5.7 View PTP master statistics for OC master ........................................................................... 10-44
10.5.8 View PTP slave PDV histogram for OC slave ........................................................................ 10-44
10.5.9 View PTP slave statistics for OC slave ................................................................................. 10-45
10.5.10 View PTP master statistics in BC mode ............................................................................... 10-47
10.5.11 View G.8275.1 PTP port statistics ....................................................................................... 10-48
10.5.12 Perform Sync-E Tx timing setting ........................................................................................ 10-49
10.5.13 Set timing configuration ...................................................................................................... 10-51
10.5.14 Manage PTP TC.................................................................................................................... 10-53
10.5.15 Work in services .................................................................................................................. 10-55
10.6 Configure PCM timing ........................................................................................................ 10-59
10.7 Configure MXP10 timing .................................................................................................... 10-61
10.8 Quality Level and SSM Processing with Option II .............................................................. 10-62
ECI Telecom Ltd. Proprietary xii

11 Services management in MSPP/NPT .......................................................... 11-1

11.1 MPLS services workflow ...................................................................................................... 11-2
11.2 MPLS services supported cards ........................................................................................... 11-2
11.3 Create and manage LAGs ..................................................................................................... 11-3
11.3.1 Create a LAG .......................................................................................................................... 11-4
11.3.2 Manage LAGs......................................................................................................................... 11-5
11.3.3 Manage LAG over MoE .......................................................................................................... 11-9
11.3.4 Manage MC-LAG ................................................................................................................. 11-10
11.4 Profile management .......................................................................................................... 11-19
11.4.1 Manage Policer profiles....................................................................................................... 11-19
11.4.2 Manage ACL profiles ........................................................................................................... 11-24
11.4.3 Manage EXP mapping profiles ............................................................................................ 11-26
11.4.4 Manage WRED profiles ....................................................................................................... 11-29
11.5 H-VPLS and E-Tree ............................................................................................................. 11-34
11.6 MPLS best-effort CoS ......................................................................................................... 11-36
11.7 Small bandwidth tunnel/queue ......................................................................................... 11-37
11.8 PW control word for NPT ................................................................................................... 11-38
11.9 Manage tunnels ................................................................................................................. 11-39
11.9.1 Tunnel workflow ................................................................................................................. 11-41
11.9.2 Create tunnel XCs ................................................................................................................ 11-43
11.9.3 Access tunnel XC list ............................................................................................................ 11-60
11.10 Manage LSP 1:1 for BD-LSP ................................................................................................ 11-78
11.10.1 LSP 1:1 for BD-LSP workflow ............................................................................................... 11-85
11.10.2 Create Linear Protection Domains ...................................................................................... 11-85
11.10.3 Manage the BD-LSP List....................................................................................................... 11-88
11.10.4 Perform MPLS-TP Tunnel Restoration................................................................................. 11-97
11.11 Manage DiffServ Block over MPLS-TP Port ...................................................................... 11-102
11.11.1 Configure DiffServ blocks .................................................................................................. 11-102
11.11.2 Enable DiffServ blocks for a tunnel ................................................................................... 11-103
11.12 Create MPLS services ....................................................................................................... 11-107
11.12.1 MPLS PtP service ............................................................................................................... 11-109
11.12.2 MPLS MPtMP service ........................................................................................................ 11-113
11.12.3 MPLS BPDU tunneling service ........................................................................................... 11-118
11.12.4 MPLS RootedMP/Leaf service ........................................................................................... 11-122
11.12.5 MPLS RootedMP/Root service .......................................................................................... 11-132
11.12.6 MPLS VSI list ...................................................................................................................... 11-140
ECI Telecom Ltd. Proprietary xiii

11.12.7 Configure multicast for MPLS RootedMP/Leaf service ..................................................... 11-140

11.12.8 MPLS FRR switch ............................................................................................................... 11-145
11.13 Configure PW redundancy for MSPP NEs ........................................................................ 11-147
11.14 Manage MS-PW and PW redundancy.............................................................................. 11-149
11.14.1 Configure the VC label scheme ......................................................................................... 11-150
11.14.2 View the MS-PW/PW redundancy budget ........................................................................ 11-153
11.14.3 Create MS-PW services ..................................................................................................... 11-154
11.14.4 Set PW/PWR configuration in MPLS VSIs .......................................................................... 11-156
11.14.5 Perform PWR operational command ................................................................................ 11-159
11.14.6 View PW status and statistics............................................................................................ 11-160
11.15 BFD management in MSPP/NPT ...................................................................................... 11-163
11.15.1 Manage BFD protocols ...................................................................................................... 11-164
11.15.2 Manage BFD templates ..................................................................................................... 11-165
11.15.3 Manage BFD tunnel sessions............................................................................................. 11-168
11.15.4 Manage BFD section sessions ........................................................................................... 11-170
11.15.5 Manage PW BFD sessions ................................................................................................. 11-171
11.15.6 BFD trigger......................................................................................................................... 11-174
11.16 Manage queue blocks ...................................................................................................... 11-177
11.16.1 Queue blocks supported cards .......................................................................................... 11-178
11.16.2 Create a queue block......................................................................................................... 11-178
11.16.3 Manage Queue Blocks in VSIs ........................................................................................... 11-184
11.16.4 Port-level shaping.............................................................................................................. 11-184
11.17 CFM 11-185
11.17.1 CFM supported cards ........................................................................................................ 11-187
11.17.2 Manage CFM MAs ............................................................................................................. 11-187
11.17.3 CFM related performance ................................................................................................. 11-201
11.17.4 Perform CFM maintenance ............................................................................................... 11-216
11.18 In-band MCC .................................................................................................................... 11-225
11.18.1 In-band MCC supported Cards .......................................................................................... 11-226
11.18.2 Configure In-band MCC ..................................................................................................... 11-227
11.18.3 Configure management VLANs ......................................................................................... 11-230
11.19 LSP over GRE .................................................................................................................... 11-238
11.19.1 LSP over GRE supported Cards .......................................................................................... 11-240
11.19.2 Enable GRE ........................................................................................................................ 11-241
11.20 CCN management ............................................................................................................ 11-243
11.20.1 CCN supported Cards ........................................................................................................ 11-245
11.20.2 Set CCN enabled and forwarding ...................................................................................... 11-245
ECI Telecom Ltd. Proprietary xiv

11.20.3 View CCN tunnel list .......................................................................................................... 11-246

11.21 Configure latency ............................................................................................................. 11-246
11.22 View available queue resources ...................................................................................... 11-247
11.23 Configure port mirroring.................................................................................................. 11-248
11.24 Configure switch OAM settings ....................................................................................... 11-250
11.25 Configure port protection ................................................................................................ 11-251
12 CES services management ......................................................................... 12-1

12.1 Standalone mode: CES services management ..................................................................... 12-1
12.1.1 Standalone mode: CES services workflow............................................................................. 12-2
12.1.2 Create CES PB PtP services .................................................................................................... 12-2
12.1.3 Create CESoIP services .......................................................................................................... 12-8
12.1.4 View CES service state ......................................................................................................... 12-14
12.1.5 Perform CESoETY maintenance ........................................................................................... 12-15
12.2 Integration mode: CES services management ................................................................... 12-18
12.2.1 Integration mode: CES services workflow ........................................................................... 12-18
12.2.2 L2 cards working with MSM cards ...................................................................................... 12-19
12.2.3 Define iEoS/iETY interfaces ................................................................................................. 12-20
12.2.4 Create CES PB PtP services .................................................................................................. 12-24
12.2.5 Create CES PB MPtMP services ........................................................................................... 12-34
12.2.6 Create CESoMPLS services .................................................................................................. 12-39
12.2.7 View CES service state ......................................................................................................... 12-49
12.3 CEP services management ................................................................................................. 12-50
12.3.1 Create CEP services ............................................................................................................. 12-51
12.3.2 View CEP service state ........................................................................................................ 12-53
13 Services management in IP/MPLS ............................................................. 13-1

13.1 IP/MPLS services workflow .................................................................................................. 13-1
13.2 Manage MPLS TP tunnels .................................................................................................... 13-2
13.2.1 Create MPLS TP tunnels ........................................................................................................ 13-3
13.2.2 Manage the MPLS TP tunnel list ........................................................................................... 13-7
13.3 Manage the VSI .................................................................................................................. 13-18
13.3.1 Create VSIs .......................................................................................................................... 13-18
13.3.2 View PW status ................................................................................................................... 13-53
13.3.3 Run PW ping and trace route .............................................................................................. 13-54
13.4 Manage the VRF ................................................................................................................. 13-55
13.4.1 Create the VRF .................................................................................................................... 13-56
13.4.2 View routing instances status ............................................................................................. 13-60
ECI Telecom Ltd. Proprietary xv

13.4.3 View VRF status ................................................................................................................... 13-61

13.4.4 View VRF interfaces status .................................................................................................. 13-63
13.4.5 View VRF forwarding table .................................................................................................. 13-64
13.4.6 View ARP table .................................................................................................................... 13-65
13.4.7 View VRF LIF statistics ......................................................................................................... 13-66
13.4.8 Run MPLS PHT ping and trace route ................................................................................... 13-67
14 Cross connections management ................................................................ 14-1

14.1 Concatenation support ........................................................................................................ 14-1
14.2 Create XC.............................................................................................................................. 14-2
14.2.1 Create server XC .................................................................................................................... 14-2
14.2.2 Create Service XC .................................................................................................................. 14-4
14.2.3 Create Tunnel XC ................................................................................................................... 14-6
14.2.4 Create OH XC ......................................................................................................................... 14-6
14.2.5 Create DCC XC ....................................................................................................................... 14-8
14.2.6 Create PCM XC ...................................................................................................................... 14-9
14.2.7 Create OTN XC ..................................................................................................................... 14-15
14.3 Manage the XC List ............................................................................................................ 14-19
14.4 Configure SNCP Attributes ................................................................................................. 14-23
14.5 Configure OTN SNCP settings ............................................................................................ 14-26
14.6 Export and import XC Files................................................................................................. 14-28
14.6.1 Export XCs ........................................................................................................................... 14-28
14.6.2 Import XC XML files ............................................................................................................. 14-29
15 Work with protection ................................................................................ 15-1

15.1 Work with TP........................................................................................................................ 15-1
15.1.1 Manage TP ............................................................................................................................. 15-2
15.1.2 TPG Maintenance .................................................................................................................. 15-7
15.2 Work with MSP 1+1 ............................................................................................................. 15-8
15.2.1 Manage MSP 1+1 .................................................................................................................. 15-8
15.2.2 MSP 1+1 Maintenance Operation ......................................................................................... 15-9
15.3 Work with Data Card IOP ................................................................................................... 15-11
15.3.1 Data Card IOP supported cards ........................................................................................... 15-11
15.3.2 Create a Data Card IOP ........................................................................................................ 15-12
15.3.3 Manage Data Card IOP ........................................................................................................ 15-17
15.3.4 Alarm/PM Behaviors in IOP PG ........................................................................................... 15-18
15.3.5 Data Card IOP maintenance operations .............................................................................. 15-18
15.3.6 Link Trigger for IOP .............................................................................................................. 15-20
ECI Telecom Ltd. Proprietary xvi

15.3.7 SFP Inventory in IOP ............................................................................................................ 15-24

15.4 Work with OTN Port IOP .................................................................................................... 15-25
15.4.1 Manage OTN Port IOP ......................................................................................................... 15-26
15.4.2 OTN Port IOP Maintenance Operation ................................................................................ 15-29
15.5 Work with NFV Card IOP .................................................................................................... 15-30
15.5.1 Create NFV Card IOP ........................................................................................................... 15-31
15.6 Work with STP and MSTP................................................................................................... 15-33
15.6.1 STP and MSTP supported cards ........................................................................................... 15-34
15.6.2 Configure STP and MSTP ..................................................................................................... 15-35
16 Ethernet ring protection switching ............................................................ 16-1

16.1 ERPS workflow ..................................................................................................................... 16-1
16.2 Create PB Ring ERP Control VSI............................................................................................ 16-3
16.3 Create MPLS Ring ERP Control VSI ....................................................................................... 16-6
16.4 View the ERPS Instance........................................................................................................ 16-9
17 Fault management .................................................................................... 17-1

17.1 Configure NE fault settings .................................................................................................. 17-2
17.2 Monitoring and Reporting Alarms ....................................................................................... 17-5
17.3 Set switch alarms for MSPP/NPT NEs .................................................................................. 17-9
17.4 Monitor and report L2 faults for IP/MPLS NEs .................................................................. 17-11
17.5 Manage external alarms .................................................................................................... 17-13
17.6 Configure severity settings ................................................................................................ 17-16
17.7 Configuring LCT Alarm/Event Polling Settings ................................................................... 17-18
17.8 Manage current alarms...................................................................................................... 17-19
17.8.1 Viewing Current Alarms ...................................................................................................... 17-19
17.8.2 Determine the cause of an alarm ........................................................................................ 17-21
17.8.3 Filtering Current Alarms ...................................................................................................... 17-22
17.8.4 Sort current alarms ............................................................................................................. 17-23
17.8.5 Acknowledge current alarms .............................................................................................. 17-24
17.8.6 Export current alarms to files .............................................................................................. 17-24
17.8.7 Viewing a Chart for Current Alarms .................................................................................... 17-25
17.8.8 Manually synchronize alarms .............................................................................................. 17-25
17.9 Manage alarms history ...................................................................................................... 17-26
17.10 Monitor events .................................................................................................................. 17-28
17.11 Managing Unreported Alarms ........................................................................................... 17-30
17.12 Manage the NE alarms log ................................................................................................. 17-34
ECI Telecom Ltd. Proprietary xvii

17.12.1 Viewing NE Alarms Log ........................................................................................................ 17-34

17.12.2 Export NE alarm logs to files ............................................................................................... 17-35
18 Performance management ........................................................................ 18-1

18.1 Performance data ................................................................................................................ 18-1
18.2 View performance data ....................................................................................................... 18-4
18.2.1 View current performance .................................................................................................... 18-4
18.2.2 View recent performance ..................................................................................................... 18-8
18.2.3 View current rate in IP/MPLS ................................................................................................ 18-9
18.3 Configuring Performance Attributes.................................................................................. 18-12
18.3.1 Open archived performance files ........................................................................................ 18-12
18.3.2 Set performance thresholds ................................................................................................ 18-12
18.3.3 Set DCC performance .......................................................................................................... 18-21
18.3.4 Manage performance settings ............................................................................................ 18-29
18.3.5 Manage PM monitoring and reporting in IP/MPLS ............................................................. 18-34
18.3.6 Manage statistics PM counters in IP/MPLS ......................................................................... 18-38
18.3.7 Manage performance history in IP/MPLS ........................................................................... 18-41
18.3.8 Manage threshold settings .................................................................................................. 18-44
18.3.9 View transceiver alarms and warning thresholds ............................................................... 18-44
18.3.10 View invalid MPLS-TP OAM statistics .................................................................................. 18-45
18.3.11 View TDM/packet engine utilization ................................................................................... 18-46
18.3.12 View and export laser performance .................................................................................... 18-49
18.3.13 Reset performance counters ............................................................................................... 18-51
18.3.14 Perform Ethernet interface traffic monitor ........................................................................ 18-51
18.3.15 Perform Ethernet LIF traffic monitor .................................................................................. 18-51
18.3.16 Built-in RFC2544 test management .................................................................................... 18-52
18.3.17 Build-in Y.1564 test management ....................................................................................... 18-61
19 Maintenance operations ........................................................................... 19-1

19.1 Preventive maintenance operations.................................................................................... 19-1
19.1.1 Save NE configuration data ................................................................................................... 19-1
19.1.2 Clear NE configuration data .................................................................................................. 19-1
19.1.3 Test connectivity ................................................................................................................... 19-1
19.1.4 Perform a full upload ............................................................................................................ 19-3
19.1.5 Perform a LED test ................................................................................................................ 19-4
19.1.6 View bit codes ....................................................................................................................... 19-4
19.1.7 Manage defined bit codes ..................................................................................................... 19-5
19.1.8 View PPI status ...................................................................................................................... 19-7
ECI Telecom Ltd. Proprietary xviii

19.1.9 Perform preventive maintenance ......................................................................................... 19-8

19.2 Card maintenance ................................................................................................................ 19-8
19.2.1 Reset a card ........................................................................................................................... 19-8
19.2.2 Manage OTN wrapping for STM-16/64 interface in CPTS100 ............................................... 19-9
19.2.3 Manage OTN wrapping for 10GE interface in CPTS100/CPS100 ......................................... 19-11
19.2.4 Manage OTN in XIO64 ......................................................................................................... 19-12
19.2.5 Performing Basic Parameter Backup in SFP ........................................................................ 19-16
19.3 SFP/SFP+/XFP/CSFP management ..................................................................................... 19-18
19.3.1 Obtain the SFP type ............................................................................................................. 19-19
19.3.2 Manage T-SFP+ settings ...................................................................................................... 19-22
19.3.3 Manage XFP ......................................................................................................................... 19-24
19.3.4 Configure SFP/CSFP settings ............................................................................................... 19-28
19.4 Transmission object maintenance operations................................................................... 19-31
19.4.1 Use the maintenance list ..................................................................................................... 19-31
19.4.2 Perform/release loopback................................................................................................... 19-32
19.4.3 Perform AIS/RDI .................................................................................................................. 19-35
19.4.4 Perform PRBS ...................................................................................................................... 19-36
19.4.5 Switch to protection ............................................................................................................ 19-37
19.4.6 Set the link down status ...................................................................................................... 19-38
19.4.7 CES maintenance ................................................................................................................. 19-40
19.5 Timing maintenance .......................................................................................................... 19-42
19.5.1 View TMU working mode .................................................................................................... 19-42
19.5.2 Forcing the Timing Source ................................................................................................... 19-44
19.6 SNMP configuration ........................................................................................................... 19-45
19.6.1 Enable/disable the SNMP V1/V2c agent ............................................................................. 19-45
19.6.2 Manage SNMP users ........................................................................................................... 19-46
19.6.3 Manage SNMP groups ......................................................................................................... 19-50
19.6.4 Manage SNMP views ........................................................................................................... 19-52
19.6.5 Manage SNMP contexts ...................................................................................................... 19-54
19.6.6 Manage SNMP access ......................................................................................................... 19-56
19.6.7 Manage SNMP traps............................................................................................................ 19-59
19.6.8 Overwrite SNMP configuration ........................................................................................... 19-61
19.6.9 Propagate SNMP configuration ........................................................................................... 19-61
19.7 Enable link loss carry forward (LLCF) ................................................................................. 19-64
19.8 View system fault details ................................................................................................... 19-65
19.9 Test Link OAM loopback .................................................................................................... 19-66
19.10 Setting NE Security Mode .................................................................................................. 19-69
ECI Telecom Ltd. Proprietary xix

20 Perform advanced configuration ............................................................... 20-1

20.1 Enabling the BG-40 NE Proxy ARP........................................................................................ 20-1
20.2 Managing the BG-40 NE ARP Table...................................................................................... 20-2
20.3 Displaying Channel MIB Counters for BG-40/BG-20/BG-20C .............................................. 20-4
20.4 Configuring the BG-40 NE Serial Port .................................................................................. 20-5
20.5 Performing Software Upgrade ............................................................................................. 20-5
20.6 NE version live update ......................................................................................................... 20-7
20.6.1 Workflow ............................................................................................................................... 20-8
20.6.2 Installing Patches................................................................................................................... 20-8
20.6.3 Activating Patches ............................................................................................................... 20-13
20.6.4 Viewing Patches Information .............................................................................................. 20-16
20.6.5 Clearing Patches .................................................................................................................. 20-17
20.6.6 Viewing Scheduled Patch Activation Task ........................................................................... 20-18
20.6.7 Canceling Scheduled Patch Activation Task ........................................................................ 20-20
20.7 Clearing the Flash for BG-40/BG-20/BG-20C ..................................................................... 20-20
20.8 Configuring SNMP Agent Mode ......................................................................................... 20-21
20.9 Calibrating SEC ................................................................................................................... 20-21
20.10 Restoring Default Center Frequency ................................................................................. 20-21
20.11 Clearing Reset .................................................................................................................... 20-22
21 License management ................................................................................. 21-1

21.1 License Control Mechanism ................................................................................................. 21-1
22 Use the fix tool .......................................................................................... 22-1
ECI Telecom Ltd. Proprietary xx

Useful information
The LCT-NPT User Guide is intended for MSPP/NPT equipment installation personnel and field engineers. It
provides basic operating instructions for the LCT-NPT platform.
Related documents
 NPT Product Line General Description
 NPT Product Line System Specifications
 NPT-1200 (ETSI) Installation and Maintenance Manual
 NPT-1200i (ETSI) Installation and Maintenance Manual
 EMS-NPT Installation Manual
 EMS-NPT (Native Packet Transport) User Guide
 LightSOFT Network Management System User Guide
Contact information
Telephone Email
ECI Telecom Documentation +972-3-9268145 techdoc.feedback@ecitele.com
Group
ECI Telecom Customer Support +972-3-9266000 on.support@ecitele.com
ECI Telecom Ltd. Proprietary xxi

1 LCT-NPT overview
The LCT-NPT supplements the EMS-NPT for several vital functions, including initial configuration of an
element, by providing the address IDs (it can also be used when performing software upgrades on element
cards).
The LCT-NPT system is based on the TCP/IP protocol and is connected to the Synchronous Digital Hierarchy
(SDH) NE via the Ethernet port provided by the MCU. It implements NE configuration and maintenance
management functions, and coordinates with the EMS-NPT to perform management for error correction
facilities.
The LCT-NPT software is used to perform initial data configuration and equipment software download for
MSPP/NPT NEs. Maintenance personnel can modify parameters of an operating NE to detect and solve
specific problems within the element.
Hardware and software requirements

The hardware and software requirements for the LCT-NPT are:
 Computer: PC or laptop with Core Duo CPU, with 2G memory and 250 GB hard disk memory
 Operating system:
 Windows Server 2008 - Enterprise Edition 32bits SP1
 Windows Server 2008 R2 - Enterprise Edition 64 bits
 Windows 7 - SP1 32/64 bits
 Windows 8.1 - 32/64 bits
 Windows 10 - 32/64 bits
 Windows Server 2012 - Enterprise Edition 64 bits
 Interface protocol: TCP/IP-based socket communication
 Communication interface: Connects with the main control unit of the equipment via a 10Base-T
Ethernet interface
System components
The system package consists of the following software and hardware modules:
 LCT GUI and Boot Configuration Tool software running on the Microsoft Windows operating system,
which acts as a GUI between the MSPP/NPT equipment and the user.
 Boot software running on the BOOT ROM of the MSPP/NPT equipment, which acts as a boot
configuration server.
 License key.
ECI Telecom Ltd. Proprietary 1-1

2 Install the LCT-NPT
The LCT-NPT can be installed on the following OSs:
 Windows Server 2008 - Enterprise Edition 32bits SP1
 Windows Server 2008 - Enterprise Edition 64 bits R2
 Windows 7 SP1 - 32/64 bits
 Windows 8.1 - 32/64 bits
 Windows 10 - 32/64 bits
 Windows Server 2012 - Enterprise Edition 64 bits
To install the LCT-NPT:

1. Insert the supplied CD in the CD-ROM drive.
The LCT-NPT Installation CD window opens.
2. Select Install LCT-NPT.

The Welcome window opens.

LCT-NPT® User Guide Install the LCT-NPT
3. Click Next.
The Choose Destination Location window opens. The default location is C:\LCT-NPT.
4. Click Change to select a specific folder for the installation files, if needed. Note that no spaces are
allowed in the name of the folder.
5. Click Next.
The Ready to Install the Program window opens.
6. Click Install to begin the installation. The bar in the Setup Status window shows the progress of the
installation.
7. When the installation is completed, the InstallShield Wizard Complete window opens.
8. Click Finish.
It takes a few minutes to initialize the LCT-NPT database.
When the initializing database process is completed, the LCT-NPT installation process is complete.

LCT-NPT® User Guide Install the LCT-NPT
NOTE: Installation of the LCT-NPT can be done without the license key. However, subsequent
activation of the software is prevented.

3 Log in and configure NE with boot
configuration tool
This section describes how to log in and utilize the boot configuration tool, which is used for the initial
configuration of MSPP/NPT NEs.
NOTE: After main controls reset or a power-on restart occurs, the Boot program is initiated.
When the MNR (Minor) Alarm LED of the main (MXC) board starts flashing, you have five
seconds to perform a login; otherwise, you miss the login opportunity. The boot-state login can
be performed on a local NE only.
To log in to the Boot Configuration Tool:

1. Make sure you have the license key for the LCT-NPT application.
2. Connect your PC to the local MSPP/NPT element via the dedicated MNG Ethernet port.
3. Double-click the Boot Configuration Tool icon on your desktop.

The main Boot Configuration Tool window opens.
4. Click Login in the upper left corner of the window.
The Input IP window opens.
5. Select a card by selecting the relevant button.

6. For an MSPP NE or NPT NE (except BG-40), enter the internet protocol (IP) address in the IP field, and
then click Connect.

LCT-NPT® User Guide Log in and configure NE with boot configuration tool
The IP address is similar to 192.100.ab.cd. "abcd" is the last four digits of the serial number on the
main control processor (MCP) card of BG-30/BG-64/NPT-1200/NPT-1030/NPT-1050 or chassis of BG-
20/BG-20C/NPT-1020/NPT-1021/NPT-1010. For details of how to set the IP address in Boot status, see
IP Address in Boot Status.
The MSPP/NPT NE assumes the boot status for approximately 5~20 seconds after resetting.
7. For NPT-1050 NEs, select the appropriate login option from the NPT-1050 Login Option window.
Select one of the login options as appropriate:

 Install New NE (Active Card)
 Install Standby Card
8. The Boot Configuration Tool logs in to the NE automatically. The following Information window opens,
confirming automatic login. Click OK.

3.1 IP address in boot status

The following are the definitions for setting the IP address in boot status:
 Boot status: When system power is switched on or MCP is restarted, the MCP card starts booting from
boot flash and/or NVM. Before it starts loading application SW (version image) from NVM, there is a
time window of 10 seconds during which the user can log in to the system to install SW and configure
some NE initial parameters (such as NE ID, NE IP, and NE connection mode) through the LCT boot
configuration tool or CLI. This period is called boot status. Usually the access port (either MNG or AUX
port) has fixed IP (either derived from the card serial number (S/N) or a constant). If the IP is derived
from S/N, it is different for each unit. When the MINOR LED (Yellow) on the front panel of the MXC or
MCP card starts blinking, boot status is available.
 MNG port: Management interface used to connect management tools (such as LCT, EMS). Usually it is
a 10BaseT or 10/100BaseT port on the front panel of the MCP card of the BG unit, and the IP address is
derived from S/N in boot status while it is configurable in the operational stage. In the operational
stage, the MNG port is available when NE connection mode is gateway or Ethernet only.
 AUX port: Auxiliary port used for local maintenance and debugging. Usually it is an Ethernet port
(10/100BaseT) with fixed IP address. Not all BG equipment has the AUX port.
WARNING: Care must be taken when using AUX port in NPT-1200 for versions<=V3.0 and BG-
64 for versions <=V15.1:
 AUX port has fixed MAC and IP address, it is mainly for on-site local debugging purpose;
this port should not be connected to any external DCN (L2 or L3);
 In any case when a laptop/PC is connected to AUX port during NE installation or on-site
investigation in order to use LCT or telnet/ftp, the IP of the laptop/PC must be set to an IP
larger than 169.254.0.10 (such as 169.254.0.100/24, 169.254.0.200/24) before it is
connected the AUX port. The IP from 169.254.0.1 to 169.254.0.10 have been occupied by
internal interfaces.
NOTE: From NPT-1200 V3.1 and BG-64 V16.1, the IP address of AUX port is still 169.254.0.1/24
in boot status; however, the IP address in running status is changed to 169.254.100.1/24.
Table 3-1: IP address in boot status

NE MCP card Port IP in boot status Note
BG-20 MXC-20 MNG The IP address depends on the S/N of MXC-20 printed on the bar code on S/N dependent
the front panel. Assume the S/N of MXC-20 is xx-xxxx-abcd (decimal), in a
normal case the IP is:
 If 'cd' is not "00", IP = 192.100.ab.cd/16
 If 'cd' is "00", IP = 192.100.ab.100/16
If the rule does not work, try 192.100.100.100 or 192.100.00.100.
BG-20C MXC-20C MNG The IP address depends on the S/N of MXC-20C printed on the bar code on S/N dependent
the front panel. Assume the S/N of MXC-20C is xx-xxxx-abcd (decimal), in a
 If 'cd' is "00", IP = 192.100.ab.100/16

BG-30 MCP30 MNG The IP address depends on the S/N of MCP printed on the bar code on the S/N dependent
front panel. Assume the S/N of MCP30 is xx-xxxx-abcd (decimal), in a normal
case the IP is:
 If 'cd' is "00", IP = 192.100.ab.100/16
If it does not work, try 192.100.100.100 or 192.100.00.100.
MCP30B MNG The IP address depends on the S/N of MCP30B printed on the bar code on S/N dependent
the front panel. Assume the S/N of MCP30B is xx-xxxx-abcd (decimal), in a
 If 'cd' is "00", IP = 192.100.100.100/16
If the rule does not work, try 192.100.100.100.
BG-64 MCP64 AUX 169.254.0.1/24 Const
MNG The IP address depends on the S/N of MCP printed on the bar code on the S/N dependent
case the IP is:
 If 'cd' is "00", IP = 192.100.100.100/16
NPT-1200 MCP-1200 AUX 169.254.0.1/24 Const
MNG The IP address depends on the S/N of MCP printed on the bar code on the S/N dependent
case the IP is:
 If 'cd' is "00", IP = 192.100.100.100/16
NPT-1020 MXC-1020 MNG MNG port has two IP addressed in boot status. Const and S/N
dependent
One IP is fixed to 194.194.194.193/24
The other IP address depends on the S/N of MXC-1020 printed on the bar
code on the front panel. Assume the S/N of MXC-1020 is xx-xxxx-abcd
(decimal), in a normal case the IP is:
 If 'cd' is "00", IP = 192.100.100.100/16
NPT-1021 MXC-1021 MNG MNG port has two IP addressed in boot status. Const and S/N
dependent
One IP is fixed to 194.194.194.193/24
The other IP address depends on the S/N of MXC-1020 printed on the bar
code on the front panel. Assume the S/N of MXC-1020 is xx-xxxx-abcd
 If 'cd' is "00", IP = 192.100.100.100/16

NPT-1010 MCPS-1010 MNG MNG port has two IP addressed in boot status. Const and S/N
dependent
One IP is fixed to 194.194.194.193/24
The other IP address depends on the S/N of MCPS-1010 printed on the bar
code on the front panel. Assume the S/N of MCPS-1010 is xx-xxxx-abcd
 If 'cd' is "00", IP = 192.100.100.100/16
NPT-1030 MCP30B MNG MNG port has two IP addressed in boot status. Const and S/N
dependent
One IP is fixed to 194.194.194.193/24
 If 'cd' is "00", IP = 192.100.100.100/16
NPT-1050 MCP-1050 MNG MNG port has two IP addressed in boot status. Const and S/N
dependent
One IP is fixed to 194.194.194.193/24
 If 'cd' is "00", IP = 192.100.100.100/16
3.2 Configure basic parameters

After a successful login to the Boot Configuration Tool, you can configure basic parameters, as described in
the following table.
Table 3-2: Basic parameters terminology

Field name Description
NE ID Unique identification for a MSPP/NPT element. NE ID has two bytes, with a
valid range from 1 to 65535 (BG-40 is from 1-4095), except for 2, which is
used by the XDM. The NE ID is in decimal format.
MAC Address MAC address is factory set and appears as read only.
NE Mode NE has three modes: Gateway, DCC-only, and Ethernet-only:
 Gateway: NE accessible via the Ethernet IP or data communications
channel (DCC) IP address
 DCC-only: NE accessible only via the DCC IP address
 Ethernet-only: NE accessible only via the Ethernet IP address

Field name Description

Ethernet Port IP This address is valid for the Gateway and Ethernet-only modes. In a gateway
NE, this provides internal router functionality. It has two IP addresses: one
for the DCC port (NE IP address) and the other for the Ethernet port. These
two addresses must belong to different subnets. The rule in setting an
Ethernet port IP address is that it must belong to the same subnet as the IP
address for the host LCT-NPT connected to it.
Framing Mode SDH/E1 or SONET/DS1.
DCC0 IP The IP of DCC0. DCC0 is a LAN-E Interface which is created by default and
cannot be deleted if DCC Mode is not Ethernet Only.
For details about DCC IP configuration, see Configuring Communication Parameters in EMS-NPT Network
Management Guide.
For details about other interface and IP creation/configuration, see Managing OSPF in EMS-NPT User Guide.
To configure basic parameters:

1. In the Boot Configuration Tool main window, select Configuration and then Basic Parameter
Configuration.
The Basic Parameter Configuration window opens. Fields and default field values may differ,
depending on the specific NE type. For example:
 MSPP NE configuration automatically includes DCC0 interface configuration.
 NPT-1200 and NPT-1020 NE configuration includes an option to enable or disable DCC0 interfaces.

 NPT-1021 and NPT-1010 NE configuration does not include DCC0 interface configuration.
(From NPT V3.1, DCC can be enabled/disabled during NE installation by the LCT boot configuration
tool.)
2. For pure packet applications, disable DCC.

3. Click Get.
The Boot Configuration Tool retrieves the configuration data from the equipment. The Basic Parameter
Configuration window is refreshed with the retrieved field values.
4. Click Set.
The Boot Configuration Tool sends the configuration data to the equipment and a confirmation window
opens.

3.3 Download embedded software and FPGA file

for BG-40/BG-20/BG-20C
The embedded software is the control software on the NE cards. The FPGA file is the programmable file
supporting hardware on the cards. Embedded software is located in the element’s upper/lower area
memories. The FPGA file is located in the file memory.
To download embedded software:

1. In the Boot Configuration Tool window, select Configuration and then Download Embedded Software.
The Download Embedded Software window opens, displaying multiple step areas. The specific window
options may differ, depending on the specific NE type. For example:
 The BG-40 window includes two steps: download and activate.
 The BG-20/20C window includes three steps: download, activate, and set restart mode. This
window is illustrated here.
2. Download the version in the Download version area:

a. To select the name of the version file to be downloaded, click Select version File.
b. In the Download version field, select the Up Bank or Down Bank button for the software
download location. This selection should always be different from the Active Area when reverting
to the original software.
c. To download the software to the equipment, click Download.

3. Activate the new version downloaded in the previous step:

a. Active bank should set to the same bank as in the previous step ("Download version to:"). The
currently activated area is used in conjunction with this area.
b. To retrieve the information, click Get.
c. If the information is all correct, click Apply to activate the software.
4. Set NE restart mode (for BG-20/20C):
 No recovery (Clear existing NE DB) - Usually selected for new NE installation.
 Recovered (Reserve existing NE DB) - Usually selected for upgrades of existing NEs, to reserve
existing traffic.
a. To retrieve the information, click Get.
b. If the information is all correct, click Apply to set the reset mode.
If you don't click Get or Apply, the NE Restart mode window opens when you close the window.
c. Select in which mode you want to restart the NE, and click Confirm.
To download an FPGA file for BG-40:

1. In the Boot Configuration Tool window, select Configuration and then Download FPGA File. The
Download FPGA File window opens.
2. To select the name of the FPGA file to be downloaded, click Select version File.

3. Click Download.
4. To exit, click Close.
3.4 Download embedded software for BG-

30/BG-64/NPT NEs
The embedded software is the control software on the NE cards, located in the NE's upper/lower area
memories. The embedded software includes the FPGA file, a programmable file supporting hardware on the
cards.
To download embedded software:

1. In the Boot Configuration Tool window, select Configuration and then Download Embedded Software.
The Software Upgrade window opens, including the following areas:
 Version Info: active and inactive versions, flash boot, and RAM boot information
 Version activation: currently activated area used in conjunction with the Embedded area
 Version download: used to download embedded software to the equipment
2. To retrieve the version information from the equipment, in the Version Info area, click View.
3. In the Version activation area:
a. To retrieve the version activation information from the equipment, click Get.
b. To activate the software, click Apply.

c. To delete the NE database, click Restart NE with default configuration.

d. If you don't select any operation in this area, the following window opens when you close the
window.
4. In the Version download area:

a. To select the name of the file to be downloaded, click Select File.
b. Select the Up or Down button in the Target Area for the software download location. This
selection must always be different from the Version activation area when reverting to the original
software.
c. To download the software to the equipment, click Download.
5. To activate the software, click Apply in the Version activation area.
3.5 Obtain MAC data for BG-30/BG-64/NPT NEs

To obtain MAC data:
 In the Boot Configuration Tool window, select Configuration and then Get MAC.
The Boot Configuration Tool retrieves the MAC data from the equipment and displays it in the MAC
Address window.

3.6 Obtain IDPROM data for BG-20/BG-20C/BG-

30/BG-64/NPT NEs
Use the following procedure to obtain IDPROM data for the BG-20/BG-20C/BG-30/BG-64/NPT NEs. IDPROM
data is stored in the EEPROM, which records relevant hardware information.
To obtain IDPROM data:

 In the Boot Configuration Tool window, select Configuration and then Get IDPROM.
The Boot Configuration Tool retrieves the IDPROM data from the equipment and displays it in the
IDPROM window.
3.7 Format NVRAM for BG-30/BG-64/NPT NEs

To format NVRAM:
1. In the Boot Configuration Tool window, select Configuration and then Format NVRAM.
The Format NVRAM window opens.
2. In the Format Area field, select either boot or data to indicate the area to be formatted.
3. Click Apply.
The Boot Configuration Tool sends the format command to the equipment.

3.8 Obtain NVRAM information for BG-30/BG-

64/NPT NEs
To obtain NVRAM information:
 In the Boot Configuration Tool window, select Configuration and then Get NVRAM Info.
The Boot Configuration Tool retrieves the NVRAM data from the equipment and displays it in the
NVRAM Info window.
3.9 Configure "No Recovery Next Startup" for

BG-20
When the No Recovery Next Startup attribute is enabled, the NE restarts using the default configuration
instead of the current configuration.
To configure the No Recovery Next Startup attribute:

1. In the Boot Configuration Tool window, select Configuration and then No Recovery Next Startup.
The No Recovery Next Startup window opens.
2. To retrieve the current No Recovery Next Startup attribute value from the equipment, click Get.
3. To restart the NE using the default configuration instead of the current configuration, select the No
Recovery Next Startup checkbox.
4. To restart the NE using the current configuration, clear this checkbox.

5. Click Apply.
The Boot Configuration Tool sends the No Recovery Next Startup attribute to the equipment.
3.10 Configure "Serial Port Close" for BG-20

When the Serial Port Close attribute is enabled, the serial port is closed in order not to disturb the main
board’s normal operation. When this attribute is disabled, the serial port is open and you can view debug
information from the serial out port.
To configure the Serial Port Close attribute:

1. In the Boot Configuration Tool window, select Configuration and then Serial Port Close Flag.
The Serial Port Close Flag window opens.
2. To retrieve the current Serial Port Close attribute value from the equipment, click Get.
3. To close the serial port, select the Serial Port Close checkbox.
4. To keep the serial port open and be able to view debug information from the serial out port, clear this
checkbox.
5. Click Apply.
The Boot Configuration Tool sends the Serial Port Close attribute to the equipment.

3.11 Configure NE Restart Mode for BG-64/NPT-

1200/NPT-1020/NPT-1021/NPT-1050/NPT-
1010
To configure NE restart mode:
1. In the Boot Configuration Tool window, select Configuration and then Restart Mode Control.
The NE Restart Mode Control window opens.
2. In the Force Cold Start field, set Yes or No as required.

3. Click Apply to send the command to the equipment.
4. If you want to restart the NE with the default configuration, click Restart NE with default configuration.

4 Get started
The LCT GUI is essentially an element management system (EMS) interface for the MSPP/NPT NEs, and
performs typical management functions.
NOTE: Multiple methods are available in the LCT-NPT for accessing and performing many
operations. The following standard methods are available:
 Selecting a menu command
 Clicking a toolbar icon
 Double-clicking an object
 Right-clicking an object (such as an NE) and then selecting the relevant shortcut menu
option
Operational procedures throughout this guide typically specify only one access method. Be
aware that other methods may apply when performing a given operation.
4.1 Start the LCT client

Use the following procedure to log in to the LCT-NPT interface.
You can select one of the upload options as you want:
 Upload basic configuration - Upload some NE level basic configuration only, such as NE attributes, slot
assignment, DCC XC, etc. The contents mainly include:
 NE attributes, NE connection settings
 Secure mode
 Slot assignment and sub card assignment
 DCC XC/UFCC XC
 Clear channel attributes – framed or unframed
 Upload cards, physical ports - Besides basic configuration, all ports and port attributes will be uploaded.
The contents mainly include:
 Basic Configuration contents
 IOP PG (data IOP and TP PG)
 MSP1+1 PG/MS-SPRING PG
 Maintenance operations for XIO/CPTS/CPS and IOP PG
 CES card work mode (integration and standalone) and attaching attributes
 HEOS_16/MEOS_8 activation;
 Data cards
 Switch level
 Port density

LCT-NPT® User Guide Get started
 Port activation
 Transceiver assignment of the port – SFP/SFP+/XFP/CSFP;
 Port attributes (physical layer and layer 2), MCC setting
 EoS/MoT – VCG size and LCAS attributes, EOS attributes;
 LAG
 SDH cards
 Port rate
 Transceiver assignment
 MXP10
 Port density
 Transceiver assignment
 Port type and GCC setting
 CES TDM port – selection from front panel or matrix.
 Management VLAN
 OSPF and IP networking configuration
 Fully upload - Same as previous versions.
To log in to the LCT:

1. Make sure you have the license key for the LCT-NPT application.
2. Connect the PC to the gateway NE via the designated MNG Ethernet port.
3. Double-click the LCT-NPT shortcut icon on your desktop.

The LCT-NPT Login window opens with a progress bar showing the progress of server startup.
After the server successfully starts, a small computer icon appears in the task bar.

4. Double-click the computer icon to open the LCT-NPT server and to view the status of each running LCT-
NPT service.
5. In the Login window, enter the appropriate information into the following fields.
 Product Family: The product family of the NEs:

 NPT/MSPP: Including all the MSPP and NPT NEs.
 IP MPLS: In V5.0, includes only NPT-1800.
 IP: The NE IP address. For the LCT to attempt to connect to the NE, click the ping button .
 User Name: The user name in the NE, mandatory for secure NE only.
 Password: The NE password. For secure NE, this is the password of the specified user.
 Upload Opts: The upload options, including:
 Upload basic configuration: Upload basic NE configuration data only, such as NE attributes,
slot assignment, DCC XC, etc.
 Upload cards, physical ports: In addition to basic configuration, all ports and port attributes
are uploaded.
 Fully upload: Complete upload, as described for previous versions.
6. After entering the appropriate field data, click Login to log in to the NE.
A Confirmation window opens, asking if you want to update the license.
7. Click Yes to continue.

The EMS Server IP and Port window opens.

8. If you are a valid user and EMS-NPT has been installed, enter the EMS-NPT Server IP and Port in the
relevant fields, and click OK.
After successful login to the LCT-NPT software, you can configure the following parameters:
 Basic parameters, including NE ID, NE mode, Ethernet port IP, and Ethernet port mask
 Static IP routes
4.2 Configure parameters

To configure parameters:
1. In the NE Shelf View window, select Advanced and then Basic Parameter Configuration.
The Basic Parameter Configuration window opens.
2. To retrieve the configuration data from the equipment, click .
4.3 Configure static IP routes

When several NEs are managed by the LCT-NPT, configure the static IP routes for the NEs.
To configure static IP routes:

1. In the BG-40 NE Shelf View window, select Advanced and then Static IP Route Table.

The Static IP Route Configuration window opens.
2. To add the new static IP route, click .

The Create Static Route window opens.
3. Enter the Destination Network IP, Subnet Mask, and Next Hop IP.
4. To delete a static IP route, select the static IP route entry that you want to delete, and click .
5. To edit a static IP route, select the route in the list, and click .
6. To retrieve the static IP routes from the equipment, click .

7. Click Apply to send the static IP routes to the equipment.

4.4 Manage reports

The report window generates reports for LCT-NPT managed objects.
To view the NE inventory list:

1. In the NE Shelf View window, on the menu, select Configuration > NE Inventory.
The NE Inventory window opens.
2. To export the NE inventory list as a CSV file, on the toolbar, click .
3. To print the NE inventory list, on the toolbar, click .

The NE Inventory Print Preview window opens, displaying a preview of how the printed file would
appear.
a. To save the NE inventory report as a PDF file, click .
b. To print the NE inventory report, click .
To view the SFP inventory list:

1. In the NE Shelf View window, on the menu, select Configuration > SFP Inventory.
The SFP Inventory window opens.
2. To export the NE inventory list as a CSV file, on the toolbar, click .

4.5 Use online help

A context-sensitive online help are both available for researching questions quickly and efficiently.
To use the online help:
1. To open the online help file, on the toolbar, click .

The Help window opens, displaying information relevant to the active window.
2. In the Table of Contents (left pane), click any topic.
The relevant topic appears in detail in the workspace (right pane) of the Help window.

5 LCT-NPT security management
Only one EMS-NPT and one LCT-NPT are allowed to log in to the same NE simultaneously. Both the EMS-NPT
and the LCT-NPT can be in Master mode to configure the NE.
When the LCT-NPT applies for Master mode, the embedded software on the NE checks the LCT configuration
of the EMS-NPT, as follows:
 If the EMS-NPT is not managing the NE, the LCT-NPT switches to Master mode successfully.
 If the EMS-NPT is logged into the NE and the LCT-NPT configuration of the EMS-NPT is approved, the
LCT-NPT switches to Master mode successfully.
 If the EMS-NPT is logged into the NE and the LCT-NPT configuration of the EMS-NPT is not approved,
the LCT-NPT does not switch to Master mode, but remains in the Monitor mode.
 If the EMS-NPT is logged into the NE and the LCT-NPT configuration of the EMS-NPT administrators
group is waiting for approval, the LCT-NPT embedded software on the NE sends an Apply Master
notification to the EMS-NPT administrators group. If the EMS-NPT administrators group returns
approval, the LCT-NPT switches to Master mode. If the EMS-NPT administrators group returns no
approval, the LCT-NPT remains in Monitor mode.
 When LCT Request Log in as Master, the LCT-Master-Login message will pop for all online administrator
group users.
 The administrators group users can click accept/reject button in the LCT accept window to accept
or reject the LCT Request.
 If no user click the accept/reject button, after 30 seconds, the client will automatically close the
window and accept LCT Request.
5.1 Configure the LCT-NPT work mode

When working with the LCT-NPT, you can view its current work mode and set it as either Master or Monitor
mode.
To view the LCT-NPT work mode:

 In the NE Shelf View window, select Advance and then LCT Work Mode to display the LCT-NPT work
mode: Monitor mode (offline) or Master mode (online).
A Message window opens showing the current LCT-NPT work mode.

LCT-NPT® User Guide LCT-NPT security management
5.2 Request to log in as master

To set the LCT-NPT work mode as master:
 In the main menu, select Advance and then Request Log In as Master to set the LCT-NPT connection
status in Master mode.
5.3 Request to log in as monitor

To set the LCT-NPT work mode as monitor:
 In the main menu, select Advance and then Request Log In as Monitor to set the LCT-NPT connection
status in Monitor mode.

5.4 View the security log

The LCT-NPT 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 the security log:

1. In the NE Shelf View window, from the menu, select Security and then Security Log.
The Security Log window opens, displaying the history login list.
2. In the Filter bar, click + to expand the filter area.

3. Set the filter options information in the Security Log list.
4. Click the filter button to refresh the list.
5. To delete the history logs, select the logs in the list you want to delete and then select File and Delete,
or on the toolbar click .

5.5 View the action log

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

1. In the NE Shelf View window, select Advanced and then Action Log.
The Action Log window opens.
2. To customize the table columns displayed by selecting the table columns to show or hide, click the blank
Configure Columns button located in the top right corner of the table.
The Field Chooser window opens.

3. Select the columns you want to display from the list of Available Fields on the left.
4. Click the right/left arrow buttons to move selected fields into the Selected Fields list on the right, or
back to the Available Fields list on the left.
5. Click the up/down arrow buttons to rearrange the order of the fields in the Selected Fields list on the
right.
6. Click Apply to save your selections.
7. Click Restore Default to display the default set of table columns.

5.6 Configure IEEE 802.1X port-based

authentication
802.1X is supported for the central PE of NPT NEs, and can work together with existing security packages
(public key and RADIUS server). 802.1X can be enabled on ETY ports with the following port types:
 PB UNI
 PB E-NNI
To configure 802.1X authentication at the card level:

1. In the NPT NE Shelf View window, select the relevant card.
2. In the Configuration working mode, select the 802.1x Authentication tab.
To configure 802.1X authentication at the port level:

1. In the NPT NE Shelf View window, select a PB UNI or E-NNI port in a central PE.
2. Click Configuration and then select the 802.1x Authentication tab.

3. In the PAE (Port Access Entity) Role dropdown list, select either None or Authenticator.
4. (Optional) If PAE Role is Authenticator, in the Port Control Mode, select one of the following:
 Force Unauthorized: The controlled Port is required to be held in the Unauthorized state.
 Force Authorized: The controlled Port is required to be held in the Authorized state.
 Auto: The controlled Port is set to the Authorized or Unauthorized state in accordance with the
outcome of an authentication exchange between the Supplicant and the Authentication Server.
5. Click Apply.
6. (Optional) To re-authenticate the PAE, in the toolbar, click .

5.7 Configure RADIUS client settings

Remote Authentication Dial in User Service (RADIUS) is a networking protocol that provides centralized
Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a
network service.
A Network Access Server (NAS) operates as a client of RADIUS. The client is responsible for passing user
information to designated RADIUS servers, and then acting on the response which is returned.
RADIUS servers are responsible for receiving user connection requests, authenticating the user, and then
returning all configuration information necessary for the client to deliver service to the user.
Transactions between the client and RADIUS server are authenticated through the use of a shared secret,
which is never sent over the network. In addition, any user passwords are sent encrypted between the client
and RADIUS server, to eliminate the possibility that someone snooping on an unsecure network could
determine a user's password.
The RADIUS server can support a variety of methods to authenticate a user. When it is provided with the user
name and original password given by the user, it can support PPP PAP or CHAP, UNIX login, and other
authentication mechanisms.
A summary of the RADIUS data format is shown below. The fields are transmitted from left to right.
Figure 5-1: Summary of the RADIUS data format
When RADIUS server is not available, the users in local DB will work.

To configure RADIUS client settings:

1. In the NE Shelf View window, on the menu, select Maintenance and then RADIUS Client Setting.
2. The RADIUS Client Setting window opens.
3. In the RADIUS Client Setting window, select the Primary RADIUS Server and Secondary RADIUS Server
checkboxes.
4. Configure the IP, Port, Security Code, and Confirm Security Code in relevant fields. For example:
5. Click Apply to save your settings.
6. Click Ping to ping an external IP address and verify that the AAA server is reachable from the client.
7. Click Refresh to refresh the window data.

6 NE management
This chapter describes how to configure and manage NEs supported in LCT-NPT.
6.1 NE types overview

The initial default status of NEs is not configured. The configuration process configures attributes, services,
and relevant functions for an NE, according to requirements of the networking application. The NE's
configuration data determines all the actions of the NE.
During configuration, the NE configuration database is defined and set up. Before service configuration can
be performed on an NE, relevant attributes and parameters must be set, such as the NE attribute and the
card attribute. A configuration wizard is provided for this purpose.
6.1.1 BG-40
The BG-40 is a compact STM-1/STM-4-compatible multiservice transmission system offering powerful
expansion capabilities. Within its 2U (88 mm) height, it can provide a maximum of either 88 E1 services, 10
E3/DS-3 services, or 36 10Base-T/100Base-T 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. Depending on networking requirements, it can flexibly be configured as TM, ADM, or multi-
ADM. In addition, it supports a variety of complete and flexible network-level protection mechanisms.
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 communications networks.
The BG-40 shelf layout is shown in the following figure.
Figure 6-1: BG-40 shelf layout
The card areas are:

 MS - main slot
 ES1 and ES2 - extension slots
 PS - power module slot
 DS1, DS2, and DS3 - three service daughterboard slots on the main board
 DS-OW - OW daughterboard slot on the main board

LCT-NPT® User Guide NE management
6.1.2 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 NE that supports ring, chain, and mesh network topologies.
The card areas are:

 Eslots (ES1/ES2/ES3) - extension slots
 FCU - fan slot
 INF - power module slot
 Dslot - service daughterboard slot on the main board
BG-20EH can be installed only on top of the BG-20B_L1/L2/L2M base unit.
Figure 6-3: BG-20EH diagram
The following designations apply in the BG-20EH diagram:

 Two power supply slots; can support INF redundancy.
 One slot for fan unit; fan unit is extractable.
 Three I/O slots for extending traffic interfaces for BG-20.
All the expansion cards supported by the BG-20E can be inserted in BG-20EH I/O slots.

6.1.3 BG-20C
The BG-20C is a new, very low cost miniature MSPP demarcation platform. The hardware architecture is
based on BG-20B_L2M, but without any extensibility.
The BG-20C is an MPLS-capable STM-1/4 TM/ADM product with fixed E1 and FE interfaces. The BG-20C design
is based on the BG-20B_L2M platform, removing unnecessary functions and interfaces and merging
everything on a single board.
6.1.4 BG-30
The BG-30 is a miniature, low-cost, flexible, redundant ADM-1/4/16 MSPP for access networks, offered as
part of the overall network solutions division. It supports full interoperability with the XDM and the BG-
40/BG-20, 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. Its very small size and ability to
operate in a wide temperature and humidity range make it ideal for mounting in street cabinets, indoors,
and on
walls.``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
``````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
````````````````````````-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.
The card areas are:

 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

6.1.5 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 shelf layout is shown in the following figure. The BG-30E platform can be assigned (default is not
assigned).
The card areas are:

 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, supported redundancy
 TS 1#~7# - tributary module slots for BG-64. The slot dimension is the same as the BG-30B Tslot

6.1.6 NPT-1200
NPT-1200 is a member of the NPT family, which is positioned in access layer or metro edge network. Since in
certain respects the NPT-1200 is an upgrade of BG-64, this enables smooth evolution of the network from
MSPP to NPT (single TDM core to dual-core).
NPT-1200 has the same shelf size and layout as BG-64 – 2RU, INF and matrix card redundancy, single MCP
and fan unit, and seven I/O slots. However it has a new backplane (MBP-1200), supporting new features such
as high-speed connections between matrix slots and I/O slots for packet plane. It also has a new power supply
and fan unit to enable larger capacity and higher performance.
The NPT-1200 shelf layout is shown in the following figure.
Figure 6-6: NPT-1200 shelf layout
The card areas are:

 MS - One slot for MCP1200
 XS A & XS B - Two slots for matrix cards
 PS A & B - Two slots for power supply (INF-1200)
 FS - One slot for fan unit (FCU-1200) on right side
 TS1~7 - Seven slots for I/O traffic cards
 Support EXT-2U as expansion unit:
 EPS A & B - Two slots for power supply
 EFS - One slot for fan unit
 ES1-3 - Three slots for expansion I/O cards

6.1.7 NPT-1020
NPT-1020 is a low cost All Native Hybrid+ solution based on the existing BG-20B TDM architecture and BG-
30 INFs, Tslots cards, expansion shelf and Eslot cards, by mainly adding a new central packet switch for
Ethernet/MPLS based applications.
NPT-1020 is a non-redundant, 1RU access edge NPT platform, with lower entry cost while keeping the
flexibility and extensibility with T-slot and expansion unit.
The card areas are:

 One base unit of MXC-1020, including main control unit, TMU with SyncE and 1588 support, central
TDM matrix, central packet switch with 10Gbps throughput, build-in 21 x E1s and 12 x GbE interfaces
and fans;
 One Tslot for existing BG-30 I/O cards, MSE1_16, DHGE_8, DHGE_4E, and CPS50;
 Three Eslot for all existing BG-30E/EXT-2U cards;
 Two slots for INF-B1U cards;
 The FAN control unit (with four levels: turbo, medium, low, stop) on MXC-1020 board.
 In NPT-1020, NVM (CF) card is extractable and supports hot-swapping. The CF card need not assignment
and is an indispensable part of MXC-1020. CF live-insertion is supported.
6.1.8 NPT-1021
NPT-1021 is a new NE type with pure packet support only. All native TDM (SDH) related modules and cards
are not supported, while only central PE, CES cards and optics cards are supported. The NE looks like NA
mode of NPT-1020 – native TDM is not supported in both cases; but NPT-1021 also supports NA and non-NA
option, and E1 CES or channelized STM-1/4 CES are supported in non-NA mode, while DS1 CES or channelized
OC-3/12 CES are supported in NA mode. Moreover, TMU (the Quality level and SSM definition) is different in
NA and non-NA mode.
NPT-1021 is a 1RU pure packet NPT with same chassis and packet functionality as NPT-1020. NPT-1021's
feature list is a subset of NPT-1020. It doesn't support all native TDM features (Native SDH interfaces/PDH
interfaces, EoS functionality, DCC, and OH) that NPT-1020 supports, and all packet features (MPLS-TP/PB,
CES, 1588) can be supported by NPT-1021.

6.1.9 NPT-1030
NPT-1030 is a new network element (NE) and managed element (ME) for NMS and EMS. Besides NE type,
the features of NPT-1030 are totally the same as BG-30.
6.1.10 NPT-1050
NPT-1050 is a member of the NPT family, which is positioned in access layer or metro edge network. Since in
certain respects the NPT-1050 is an upgrade of BG-30, it enables the smooth evolution of the network from
MSPP to NPT (single TDM core to dual-core).
NPT-1050 has the same shelf size as BG-30 – 1RU, INF, control, and matrix card redundancy, with three I/O
slots. It inherits the same TDM plane as BG-30 XIO30-16 system, the same packet plane as NPT-1200
CPTS/CPS system, and reuses the same SDH/PDH/Ethernet/CES/PCM/MXP10/OBC I/O cards as NPT-1200.
The NPT-1050 is like a compact NPT-1200 system with less slots and enhanced redundancy (MCP
redundancy).
NPT-1050 can support two framing modes – SDH/E1 and SONET/DS1. The platform's framing mode
determines the CES TDM interface type, EEC timing characteristic, and SSM/QL definition.
 When framing mode is SDH/E1:
 No limitation in card assignment;
 MSE1_16 works in E1 CES mode – support 16 x E1 interfaces;
 MSC_2_8 works in E1 CES mode – support two channelized STM-1 and 8 x E1 interface;
 EM_10E works in E1 mode;
 Support DMCES1_4 and DMCE1_32
 The system timing unit specification complies with ITU-T G.8262 option I;
 The SSM and timing source quality level (QL) definitions comply with G.781 option I;
 When framing mode is SONET/DS1:
 Only pure packet matrix card (MCPS100) can be assigned and MCPTS100 cannot be assigned.
Accordingly, native TDM based cards are not supported, which include PME1_21, PME1_63,
PM345_3, SMQ1, SMQ1&4, SMS16, PE1_63, P345_3E, EM_10E, S1_4 and MPoE_12G;
 MSE1_16 works in DS1 CES mode – support 16 x T1 interfaces;
 MSC_2_8 works in DS1 CES mode – support two channelized OC-3 interfaces and 8 x T1 interfaces;
 EM_10E works in DS1 mode;
 DMCES1_4 and DMCE1_32 are not supported;
 The system timing unit specification complies with ITU-T G.8262 option II;
 The SSM and timing source quality level (QL) definitions comply with G.781 option II.


The card areas are:

 MXS A & MXS B - Two slots for control and matrix card
 PS A & B - Two slots for power supply (INF-B1UH)
 TS1~3 - Three slots for I/O traffic cards
 Support EXT-2U as expansion unit:
 EPS A & B - Two slots for power supply
 EFS - One slot for fan unit
 ES1-3 - Three slots for expansion I/O cards

6.1.11 NPT-1800
NPT-1800 is a fully-redundant and high- capacity carrier-class MPLS-TP with dual stack based multiservice
packet optical transport platform, with IP/MPLS control plane and ODU cross connect. It supports 500G
(upgradable to 800G) and 1T (upgradable to 1.2T) with 40/100 Gbps per Tslot and only 8RU in height, and it
is optimized for high-capacity metro-core nodes. As a carrier-class packet optical transport platform, it
combines transport network reliability, survivability, and ease of management with packet efficiency.
Figure 6-9: NPT-1800 Traffic Model
As illustrated in the preceding figure, NPT-1800 is high-capacity packet optical (Packet/OTN) product for
metro-based networking. Comparing with other existed NPT products, it supports the following obvious
characteristics:
 First NPT product aimed at metro/core network
 Dual platform architecture
 Packet platform
 OTN XC platform (future versions)
 No TDM XC matrix, TDM via CES or OTN
 IP/MPLS control plane support
 High capacity XC capability
 Up to 800Gbps, 720Mpps with single Qumran-MX+ in CPS unit
 No aggregate interface in CPS cards
 First product with fully redundancy architecture
 Full MCP redundancy
 Full CPS redundancy
 Fully CLI support

Besides the preceding characteristics, NPT-1800 inherits:

 Inherits all existing MPLS-TP features and functionalities
 Inherits all existing Ethernet (PB) features and functionalities
 Inherits all existing CES features and functionalities
 Reuses many existing DH cards and CES cards
NPT1800 can support SDH/E1 and Sonet modes.
If NPT-1800 is SDH/E1 mode:
 MSC_2_8 works in E1 CES mode
Support two channelized STM-1 and 8 x E1 interfaces
 The system timing unit specification complies with ITU-T G.8262 option I
 The SSM and timing source quality level (QL) definitions comply with G.781 option I
If NPT-1800 is Sonet mode:
 MSC_2_8 works in DS1 CES mode
Support two channelized OC-3 interfaces and 8 x T1 interfaces
 The system timing unit specification complies with ITU-T G.8262 option II
 The SSM and timing source quality level (QL) definitions comply with G.781 option II
Figure 6-10: NPT-1800 shelf with EXT-2U
The card areas are:

 MS A & MS B - Two slots for MCP card
 CSA & CS B - Two slots for matrix card
 PS A & B - Two slots for power supply (INF-1800)

 The TS22 slot (ECB-1800):

 Support the AUX/LCT 10/1000/1000Base-T interface, support 1PPS monitor interface, and
support alarm input/output interfaces
 TS22 is a special slot only can assign the ECB-1800 card
 TS1~TS24 except for TS22 - Twenty-three slots for I/O traffic cards:
 Six HC Tslot (TS10~TS15), which supports maximum 100G interface cards with CIPS1T
 Other HC Tslot (TS7~TS9, TS16~TS18), which support maximum10G interface cards with CIPS1T
and support 100GE interface with CIPS1T
 Eleven LC Tslot (TS1~TS6, TS19~TS21, TS23, TS24), which support 10GE and GE interface cards
6.1.12 NPT-1200i
NPT-1200 is required to support IP/MPLS and L3VPN, but IP/MPLS and L3VPN come with following changes
as integral solution:
 BCM NP (DNX devices) based data path;
 ShadeTree based infrastructure (Juniper style CLI support);
 DSWP based control plane.
To adapt these changes, a new central switch card is developed in NPT-1200 to support IP/MPLS instead of
adding IP/MPLS plane over Ezchip based CPS cards (CPS100/CPS320). Moreover, to support management
and control plane redundancy, the MCP functionality should be moved to the matrix card because MCP card
is not redundant in NPT-1200.
As the result, NPT-1200 supports IP/MPLS by new control and central switch card – MCIPS320 in XS A and XS
B slots. NPT-1200i reuses same shelf as NPT-1200, and supports EXT-2U as the expansion unit. All common
cards (including INF/FCU and MCP1200) are same in NPT-1200i.
The NPT-1200i shelf layout is shown in the following figure.
Figure 6-11: NPT-1200i slot layout
The card areas are:

Base unit
 Two slots for INF – PS A and PS B

 One slot for FCU – FS

 One slot for MCP1200
 Two slots for MCIPS – XS A and XS B
 Six slots for IO cards – TS1-TS4, TS6-TS7
 With up to 4 x 10G connection to MCIPS
 Tslot5 has not high-speed connections, one SGMII connection to MCIPS.
EXT-2U
 Two slots for power supply (INF or AC_PS) – EPS A and EPS B
 One slot for FCU – EFS
 Three slots for IO card
 With one SGMII connection to MCIPS
Common cards supported in base unit
 INF-1200 for PS A and PS B
 FCU-1200 for FS
 MCP1200 for MS
Common cards supported in EXT-2U
 INF-E2U for EPS A and EPS B
 AC_PS-E2U for EPS A
 FCU-E2U for EFS
6.2 Assign slots

Card assignment assigns card types for various slots (or subcard slots) of NE equipment, setting up objects
corresponding to the physical cards in the LCT-NPT and setting their corresponding values, displaying icons
in the LCT-NPT window. Corresponding card attributes and services can only be configured after card
assignment is completed.
Card assignment makes offline configuration of the LCT-NPT possible. You can conduct all the offline
operations after saving the expected logical slots.
The following terms relate to the card assignment process:
 Logical slot: The logical slot is defined from the top down. This defines the expected configuration and
is both readable and writable.
 Physical slot: The physical slot is the actual configuration of the current NE equipment, and is read only.
 Card assignment: Card assignment installs the logical slot. You can configure the logical slot manually,
slot by slot, or you can first obtain the actual physical slot and then install the logical slot in modification
mode.

To assign cards to a slot:

1. In the NE Shelf View window, in the left object tree, right-click the NE and select Slot Assignment. The
Slot Assignment window opens.
2. Click Assign.
3. Select the checkbox for the relevant NE (BG-20E or BG-20EH).
4. Right-click a slot and then select the card you want to assign. The card is assigned.
5. Click Apply. The settings are saved.
6. To delete an assigned card, right-click a slot and select Delete.
7. Optionally, select one of the following:
 Get Logical Card: to obtain the expected configuration from the DB.
 Get Physical Card: to obtain the actual configuration from the equipment.
 Set As Logical: to set the physical cards as logical cards.
6.3 NE frame mode definition

Currently different countries in the world may have different standard for the legacy TDM interfaces in terms
of rate hierarchy, framing, and physical characteristic. For example, USA and Canada use SONET and DS1
while Europe uses SDH and E1; moreover, the network synchronization definitions may be different as well.
Framing mode is to define the NE behaviors for TDM and Timing when it is installed in different countries.
Two framing modes are defined for NPT – SDH/E1 and SONET/DS1. Framing mode is an installation option
which can be set during NE installation. It is a global attribute of the NE, and read-only to EMS.
The following NEs can support two framing modes:
 NPT-1200
 NPT-1020
 NPT-1021
 NPT-1010
 NPT-1050
 NPT-1800
Framing mode is configurable between SDH/E1 and SONET/DS1 during NE installation with LCT boot
configuration tool.
6.4 Reassign a shelf

Reassignment from a BG-20E to BG-20EH
Reassignment from a BG-20E to BG-20EH can be done without the need to delete existing traffic and slot
assignments of ES1~3. After the reassignment, only the platform type and relevant PS and FCU assignments
are updated.
Reassignment from BG-20EH to BG-20E is not supported.

Reassignment from BG-30E to EXT-2U

Reassignment from BG-30E to EXT-2U is a logical operation and can be done without the need to delete
existing traffic and slot assignments of ES1~3. After the reassignment, only the platform type and relevant PS
and FCU assignments are updated.
Reassignment from EXT-2U to BG-30E is not supported.
This section describes how to perform reassignment form BG-20E to BG-20EH for example. You can reassign
BG-30E to EXT-2U with the same procedure.
To perform reassignment from BG-20E to BG-20EH:

1. In the NE Shelf View window, in the left object tree, right-click the NE and select Slot Assignment.
The Slot Assignment window opens.
2. Check the BG-20E checkbox.

3. Select the Reassign radio button.
4. To reassign BG-20E to BG-20EH, select the Reassign to BG-20EH checkbox.
5. Click Apply.
6. Click Yes to confirm.

6.5 Set BG-20EH DC redundancy

To set BG-20EH DC redundancy:
1. In the BG-20EH NE Shelf View window, select Control and Physical Object and then BG-20EH.
2. In the Configuration working mode, select the DC Redundant tab.
3. Select the DC Redundant checkbox and click Apply.
DC redundancy is applied.
6.6 Routing table management

This section describes how to manage routing tables.
6.6.1 View actual routes

You can view the actual IP routes of a selected MSPP/NPT NE.

To view actual routes:

1. In the NE Shelf View window, in the Configuration work mode, select Routing Table.
The Routing Table window opens.
2. To retrieve and view information regarding actual routes, click .
6.6.2 Manage static routes

You can view, add, and delete static IP routing entries for a selected MSPP/NPT NE.
To manage static routes:

1. In the NE Shelf View window, in the Configuration working mode, select Routing Table.
2. In the Routing Table window, select the Static Routes tab.
3. To add a new IP route:
a. On the toolbar, select .

The Create Static IP Route window opens.

b. Enter the relevant IP values.

c. Click OK to apply the setting.
4. To delete a static route, select the route in the list you want to delete, and select .
5. To view route information, select the relevant static route, and click .
6.7 OSPF management

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.
Open Shortest Path First (OSPF) is a link state routing protocol for IP networks, and it is defined as OSPF
Version 2 in RFC 2328 for IPv4 and OSPF Version 3 in FRC 5340 for IPv6. OSPF uses Link State Advertisements
(LSAs) to exchange link state information with the same area. The LSA includes information of attached
interfaces, metrics, and other variables. OSPF routers accumulate link state information and use the Shortest
Path First (SPF) algorithm to calculate the shortest path to each node.
OSPF is an interior gateway protocol working within a single routing domain. Several concepts relate to OSPF:
 Autonomous System (AS): a collection of networks under a common administration that share a
common routing strategy. It also refers to domain.
 Area: AS can be divided into a number of areas, which are groups of contiguous networks and attached
hosts. Each area maintains a separate link state DB whose information may be summarized towards
the rest of the network by the area border router (ABR). Thus, the topology of an area is unknown
outside the area. This reduces the amount of routing traffic between parts of an AS.
 Backbone area: the backbone area (also known as area 0 or area 0.0.0.0) forms the core of an OSPF
network; all other areas are connected to it. The backbone area is responsible for distributing routing
information between nonbackbone areas.
 Area Border Router (ABR) is a router that connects one or more areas to the backbone area.
 Autonomous System Boundary Router (ASBR) is a router that is connected to more than one routing
protocol and exchanges routing information with routers in other protocols. ASBRs typically run an
exterior routing protocol, such as BGP, or use static routes.

The following figure shows an example of an internetwork with two ASs interconnected by an ASBR. The AS1
consists of areas 0, 1, and 2, interconnected by ABR.
Figure 6-12: Example of an internetwork with two ASs interconnected by an ASBR
OSPF supports the following network connections:

 DCC
 Gateway
 Clear Channel
The following functions are supported by OSPF:
 Point-to-Point (PtP) and Broadcast interfaces
 Up to four OSPF areas
 Address summarization
 ABR functionality
 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
OSPF management is supported for BG-30, BG-64 and NPT NEs.

To access the OSPF management window:

1. In the NE Shelf View window, select the NE.
2. In the Configuration working mode, select IP Networking.
The IP Networking window opens, displaying four tabs. The features of each tab are described in the
following sections.
6.7.1 Configure overall OSPF settings

Configuring of overall OSPF setting is only supported for BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-
1010 NEs.
The Overall OSPF tab window includes the following areas:
 Router ID: Router ID of OSPF.
 OSPF Enable: State of OSPF (Enable or Disable; default Disable).
 AS Border Router: State of ASBR (Enable or Disable; default Disable). When it is set, OSPF advertises
its static routes.
 Area ID: 1-4 distinct areas coded as 32-bit integers and displayed as IP addresses. By default, the
first row of the table shows the backbone area (0.0.0.0). You can add and remove OSPF areas
from the table. There are two constraints:
 There is at least one row in the table.
 Areas used in an area range or defined for an OSPF interface cannot be removed.
 Stub: Choosing this option makes the area a stub area. Stub areas do not have any routers or
areas beyond it. Stub areas prevent AS External LSAs (Type 5 LSAs) from being flooded into the
stub area. When you create a stub area, you have the option of preventing summary LSAs (Type
3 and 4) from being flooded into the area by unchecking the Summary check box.
 Summary: When the area being defined is a stub area, unchecking this check box prevents LSAs
from being sent into the stub area. This check box is selected by default for stub areas.
 OSPF Area Range Table: Supports up to 12 distinct area ranges used to summarize NEs advertised over
area boundaries. You can edit, add, or remove selected rows from the table. Range Address and Range
Mask fields define NE subnets. The Area ID dropdown list displays area IDs already defined. Pay close
attention to make sure the area IDs are configured correctly.
 In the LAN Emulation Interworking area, if the checkbox is selected, set the Management Address and
Management Mask in the corresponding fields. This attribute is not available when DCC is disabled. For
details about DCC enable/disable, see Configure Communication Parameters in the LCT-NPT Network
Management Guide.

To configure overall OSPF settings:

2. In the Configuration working mode, select OSPF Configuration.
3. In the IP Networking window, select the Overall OSPF tab.
4. Select OSPF Enabled and AS Border Router checkboxes as required.

5. In the OSFP Area, enter the following information:
 Area ID: enter the area ID.
 Stub: select the checkbox to make the area a stub area.
 Summary: unselect the checkbox to prevent LSAs from being sent into the stub area.
6. Set the states of OSPF and ASBR.
7. 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.
8. In the OSPF Area Range Table area, click + to add an area range to the table.
9. To save the settings, click Apply.

6.7.2 Manage OSPF network interfaces

This section describes how to create network interfaces. The network interfaces can be set as NE connection
IP, described in Configure communication parameters.
In the Network Interfaces tab window, you can create, modify, or delete network interfaces.
The in-band MCC Network Interface can be added to OSPF if required.
DCC LANE and PPP over DCC can be created only when NE is WAN Only/Gateway and DCC is enabled.
Network interfaces are supported for BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010/NPT-
1030/NPT-1050 NEs.
To manage network interfaces:

3. In the IP Networking window, select the Network Interfaces tab.
The DCC0 network interface is displayed in the tab by default. This value can be edited but it cannot be
deleted. xcc

4. To create a new Network Interface, click New .

The Create New Network Interface window opens.
5. Select a Network Interface from the Network Interface dropdown list.

The in-band MCC and Management VLAN can be selected as the Network Interface.
6. In the Network Interface Attributes area, configure the IP Address of the interface.
7. In the OSPF Interface Attributes area, configure the following attributes:
 OSPF Enable: Select/clear the checkbox to enable/disable OSPF (default disable).
 Passive: Select/clear the checkbox for OSPF to be set as passive/active:
 Passive: Relevant for OSPF-enabled interfaces. OSPF protocol is not performed over the
interface, but OSPF advertises hosts on the interface subnet. Area ID and Metric attribute
must be defined.
 Active: Active operational status.

 Area ID: Relevant only when OSPF is enabled. The dropdown list allows selection of an area from
one of four areas defined in the Overall OSPF tab.
 Authentication Type: four algorithm of OSPF encryption are supported per interface: None,
Simple Password, MD5, and HMAC-SHA256. If you select MD5 or HMAC-SHA256, the name of
Password will be changed to Key. If MD5 is selected, the length of Key is 16 characters, while if
HMAC-SHA256 is selected, the length of Key is 32.
8. Click OK.
The network interfaces are saved to the list.
9. To modify a network interface, select the interface you want to edit, and click Edit .
The Edit Network Interface window opens. Field values that cannot be edited are locked.

Edit the values as relevant in the fields that are open to editing and click OK.
10. To delete a network interface, select the interface you want to delete, and click .
6.7.3 Configure 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, which is only
supported for BG-30/BG-64/NPT-1200/NPT-1020/NPT-1030/NPT-1050 NEs.
To configure the terminate DCCs:

3. In the IP Networking window, select the DCC Terminations tab.

4. To set network interfaces for COM objects, select the interfaces from the dropdown lists.
5. Click Apply.
The settings are saved.
6.7.4 View OSPF interfaces

The OSPF interface is an extension of the network interface. The parameters of the OSPF interfaces can only
be viewed, and you cannot delete OSPF interfaces from the OSPF interfaces table. 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).
The parameters of OSPF interfaces can be described as follows:
 Router Priority - The priority of this interface. Used in multi-access networks, this field is used in the
designated router election algorithm. The value 0 signifies that the router is not eligible to become the
designated router on this particular network. In the event of a tie in this value, routers will use their
Router ID as a tie breaker. Range: 0~255, default is 1.
 Hello Interval - Specifies the interval, in seconds, between hello packets sent on an interface. The
smaller the hello interval, the faster topological changes are detected but the more traffic is sent on
the interface. This value must be the same for all routers and access servers on a specific interface.
Range: 1~3600s, default is 10 seconds.
 Retransmit Interval - Specifies the time, in seconds, between LSA retransmissions for adjacencies
belonging to the interface. When a router sends an LSA to its neighbor, it keeps the LSA until it receives
the acknowledgement message. If the router receives no acknowledgement, it will resend the LSA. Be
conservative when setting this value, or needless retransmission can result. The value should be larger
for serial lines and virtual links. Range: 1~3600s, default is 5 seconds.
 Transit Delay - Specifies the estimated time, in seconds, required to send an LSA packet on the
interface. LSAs in the update packet have their ages increased by the amount specified by this field
before transmission. If the delay is not added before transmission over a link, the time in which the LSA
propagates over the link is not considered. The value assigned should take into account the
transmission and propagation delays for the interface. This setting has more significance on very low-
speed links. Range: 1~3600s, default is 1 seconds.
 Dead Interval - Specifies the interval, in seconds, in which no hello packets are received, causing
neighbors to declare a router down. The default value of this setting is four times the interval set by
the Hello Interval field. Range: 1~65535s, default is 40 seconds.
 Metric - The metrics to be advertised for a specified interface at the various types of service. For the
purposes of this specification. The metric of loopback interface is fixed to 0 and not configurable.
OSPF interfaces are only supported for BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010/NPT-
1030/NPT-1050 NEs.

To view OSPF interfaces:

3. In the IP Networking window, select the OSPF Interfaces tab.
4. Select the OSPF interface you want to view, and click .

The relevant information is retrieved.
6.8 Configure NE attributes

You can configure NE attributes in the NE Settings window.
SDH/SONET Framing Mode
Framing Mode option is supported for NPT NEs. When NE is working in SONET mode, the native TDM (SDH)
is not supported, the NE works in pure packet mode and only DS1 CES is not supported.
Framing mode is defined to indicate the NE work mode:
 The Framing Mode attribute is a read-only attribute and decided during NPT unit installation and initial
setting.
 This attribute has two values:
 SDH/E1 (default)
 SONET/DS1
 It is Read-only from EMS – always got from NE; you can set this attribute when installing the NE:
 The Framing Mode can be set when installing the NE, together with other NE basic parameters
(such as NE ID, NE IP), by LCT boot configuration tool.
NOTE: When performing offline configuration, changes to NEs are only saved to the LCT-NPT
database and are not actually sent to the NE.

To configure NE attributes:
1. To view the general information of the NE, in the NE Shelf View window, in the left object tree, select
the NE.
2. In the Configuration working mode, select the General tab.

3. To configure the NE attributes, select the NE Settings tab.
Field values that cannot be edited are locked.

4. Edit the NE attribute values as relevant in the fields that are open to editing.
5. To send the information to the NE, click Apply.
6. To refresh the information in the window, click .
6.9 Manage DCC and overhead

This section describes the DCC and overhead configurations in the LCT-NPT.
The SDH network management function of the LCT-NPT 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 well in 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 port’s IP address, the DCC port's IP address, and the LCT-NPT computer's
IP address.
A gateway NE is an NE directly connected with the LCT-NPT. In terms of the physical channel, the information
exchange between the gateway NE and the LCT-NPT does not pass the DCC, and needs no forwarding via any
other NE. A non-gateway NE is an NE that communicates with the LCT-NPT via a gateway NE. Generally, it is
connected with the gateway via an optical channel for data transmission over the DCC.

DCC transparent transmission means that the DCC code stream passes the NE transparently (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; the physical connection rate is purely N x 64 Kbps.
In contrast, termination means the 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.
6.9.1 Configure communication parameters

This section describes how to configure communication parameters. If the Network Interface is configured
in OSPF, it can be set here as communication IP.
DCC mode is defined for both regular DCC and in-band MCC.
There are two parts of NE communication settings:
 Connection Mode Setting - which includes NE communication mode setting, DCC/Ethernet IP setting;
 Define Management IP - where you can select the available NIs, and an Other IP option, where user can
input any IP/Mask.
There is an attribute named DCC Enable in the WAN Only and Gateway modes, which indicates whether DCC
in TDM plane can be enabled:
 DCC XC, DCC LANE and PPP over DCC can be created only when DCC is enabled;
 If DCC is disabled, LAN Emulation Interworking configuration is not available.
DCC enable/disable is supported in both TDM plane and packet plane:
 BG-64
 NPT-1200
 NPT-1020
 NPT-1050
For other MSPP products, this attribute is not visible and is fixed to DCC enable. For NPT-1010, this attribute
is not visible and is fixed to DCC disable.
For the NPT NEs, following lists the cases:
 For NPT-1010, there is no DCC and DCC0 interface;
 For NPT-1020/NPT-1021/NPT-1200/NPT-1050 in SONET framing mode, there is no DCC, but only MCC;
 For pure packet application of NPT-1200/1020/NPT-1021/NPT-1050, there is no DCC, but only MCC.
NOTE: When you edit DCC enable/disable attribute:

 The edit will take effect only after MCP reset;
 If change DCC from enable to disable, all DCC XC, interfaces and routes belong to these
interfaces will be deleted automatically after reset;
 This edit may cause NE lost connection.

NOTE: If global DCC is disabled, and you want to downgrade to the version which does not
support this attribute, then DCC0 cannot be restored.
To configure communication parameters:

1. In the NE Shelf View window, in the left object tree, select the NE.
2. In the Configuration working mode, select NE Connection Settings.
The NE Communication window opens.
The options available in the Define Management IP tab may vary, depending on the option selected in
the Connection Setting tab. Available options may include one or more of the following. (Note that
these lists are not exclusive; more options may be available as relevant.)
 LAN only
 Ethernet IP
 Loopback IP
 Other IP
 WAN only
 DCC 0
 DCC 1
 Loopback IP
 MCC IP
 Management VLAN IP
 PPP 0
 etc.
 Gateway
 DCC 0
 DCC 1
 Ethernet IP
 Loopback IP
 MCC IP
 Management VLAN IP
 etc.
3. Edit the attribute values as relevant.
4. To save your settings, click Apply.
NOTE: Users with firewalls must use the Ethernet IP and not the DCC IP when managing G/W
BG devices.

6.9.2 Manage 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
To manage DCC settings for BG-40:

1. In a BG-40 NE Shelf View window, in the left object tree, select Control and Physical Object.
2. Select MXC4X.
3. In the Configuration working mode, select the DCC Settings tab.
4. In the VC12 to SM10 area, set the attributes as follows:

 To set a VC-12-12 link to the SM10, first 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.
5. In the V.35 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.
6. In the DCC Swap Attribute area, the optical port SWAP setting only restricts its MS property. After a
SWAP occurs, the optical port’s 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.
7. 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.
For details about creating DCC XCs, see Create DCC XC.
To perform DCC overhead configuration for BG-40:

1. In the BG-40 NE Shelf View window, in the left object tree, select the NE.
2. In the Services working mode, select the OH XC List tab.

3. On the toolbar, click .

The OH XC Create window opens.
4. In this window, configure DCC overhead, observing the following conditions:

 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.
For details about creating OH XC, see Create OH XC.
6.9.3 Manage DCC and overhead for BG-20/BG-20C/BG-

30/BG-64 and NPT NEs
DCC and overhead configuration for the BG-20, BG-30, BG-64 and NPT-1200/NPT-1020/NPT-1030/NPT-1050
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.
NOTE: You can only manage DCC XCs for the BG-20C NE; overhead configuration is not relevant
for the BG-20C.

The following figure shows the DCC cross connect model for the BG-20 and BG-30.
Figure 6-13: DCC cross connect model for BG-20/BG-30
The following types of DCC cross connections are shown in the figure (numbers refer to numbers in the
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: 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:
 DCC cross connection is bidirectional.

 Unidirectional and broadcast are not supported. A loopback requires JIG support.
 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 LCT-NPT and LCT-NPT 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 channel’s properties cannot
be changed.
To manage DCC XC for BG-20/BG-20C/BG-30/BG-64 and NPT NEs:

2. In the Services working mode, select the DCC XC List tab.

The Create DCC XC window opens. The following figure illustrates DCC XC creation for a BG-30 NE.
4. In the Start Timeslot tree, select the DCC XC source timeslot, and in the End Timeslot tree, the sink
timeslot.
5. To add the DCC XC list, click Save.
6. To activate the DCC XC, click Activate.

To manage overhead XC for BG-20/BG-30/BG-64 and NPT NEs:

2. In the Services working mode, select the OH XC List tab.

The Create OH XC window opens. This window is functionally similar to the Create DCC XC window
described previously.
4. In the Start Timeslot tree, select the OH XC source timeslot, and in the End Timeslot tree, select the
sink timeslot.
5. To add the OH XC list, click Save.
6. To activate the OH XC, click Activate.
6.10 Reset NEs

When an NE physical device does not work normally and needs to be initialized, an NE reset function is used.
The NE reset operation resets all the 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 the main processing unit and also the peripheral chips. A cold reset influences services on
the card.
To reset an NE:
1. In the NE Shelf View window, select Maintenance.
2. In the main menu, select Reset.
3. Select Warm Reset or Cold Reset.

4. Click OK. A confirmation window prompts you to confirm resetting.
5. Click Yes.

6.11 Back up NE data

This section describes NE data backup, which simplifies network management and maintenance tasks.
To back up the NE DB file:

1. In the NE Shelf View window, in the Maintenance working mode, select NE Configuration DB.
2. Select Backup.
The Backup NE DB File window opens.
3. To select a folder in which to save the file, click Set Backup File Path.
4. If you want to back up the NE data to the RDR Server, select the Backup to RDR Server checkbox.
5. To activate the NE data backup program, click Start.
6. To stop the program, click Stop.
To restore the NE data backup:

1. Select the NE whose backup you want to restore, and in the Maintenance working mode, select NE DB.
2. Select Restore.
3. To select the folder where the file is, click the button in the File Name list.
4. To activate the NE data backup program, click Start.
5. To stop the program, click Stop.

6.12 View NE system resources

Viewing NE system resources is supported in the following NEs (objects):
 BG-20 (MXC)
 BG-20C (MXC-20C)
 BG-30 (MCP30/MCP30B)
 BG-64 (MCP64)
 NPT-1200 (MCP-1200)
 NPT-1020 (MCP-1020)
 NPT-1021 (MXC-1021)
 NPT-1010 (MCPS-1010)
 NPT-1030 (MCP30)
 NPT-1050 (MCP-1050)
 NPT-1800 (MCP-1800)
 NPT-1200i (MCP-1200/MCIPS320)

To view NE system resources:

1. In the NE Shelf View window, in the object tree, select MXC/MCP.
2. In the Configuration working mode, select the NE System Resources tab.
This tab displays status information about memory used and about lack of memory.
3. When Refresh Data Dynamically is enabled (checkbox selected), you can set the Refresh Interval
(default 10 seconds).
6.13 Set card maximum traffic in BG-40

Card maximum traffic setup specifies the maximum number of VC-12s that can be assigned during the cross
connection for BG-40 NEs. This attribute must be set on the following cards: OMD1 (0~63), PE1_16 (0~16),
PE1_32 (0~32).
Card maximum traffic setup is only required for BG-40 NE.

To set the maximum traffic in BG-40:

1. In the BG-40 NE Shelf View window, select the NE in the left object tree.
2. In the Configuration working mode, select the Traffic Settings tab.
This window displays the cards for this NE for which maximum traffic must be set. The list contains the
following information:
 Card: card name.
 Max Traffic: maximum traffic value.
 Traffic Range: permitted setting range. If the card is configured with any timeslot, the permitted
setting range is the maximum serial number of the configured timeslot and the maximum value
of the card. If E1ML uses the eighth VC-12 as the maximum timeslot when being configured with
a cross connection, the maximum traffic range can be 8 through 21.
3. Set the max traffic in the Max Traffic field.
4. Click Apply to save the setting.
6.14 View NE power consumption management

status
User can view power consumption management status directly from CLI and EMS, in order to ease field
troubleshooting when there are power consumption management issues.
LCT-NPT support view the power consumption management status per NE.
This function is supported in the following NEs:
 NPT1800
 NPT1200i
 NPT1200
 NTP1050
Only NPT-1800 have both base upper cage and lower cage, other NPT have only base upper cage

To view NE power consumption management status:

 In the NE Shelf View window, in the left object tree, select the NE. Then in the Configuration working
mode, select the Chassis Power tab.

7 NE configuration and management in
IP/MPLS
This section describes how to configure and manage interfaces in the IP/MPLS NEs: NPT-1800 and NPT-1200i.
7.1 Logical interface management

Logical interface (LIF) is a channel that can send and receive packets. IP Routing deals with LIFs that can send
and receive IP packets, with additional differentiation between IPv4 and IPv6. This differentiation is provided
by assigning a suitable "address family" with an interface. It is possible to assign multiple Layer 3 families
(IPv4, IPv6, MPLS and ISO) to the same LIF.
An IP interface may be assigned with an IP address and subnet mask in the supported family, i.e., the same
LIF can be assigned with an IPv4 address and subnet mask as part of its IPv4 family configuration and with an
IPv6 address and subnet mask as part of its IPv6 configuration.
Each non-loopback IP interface is assigned with a specific MTU value. Default MTU values are derived from
the MTU of the supporting physical media using the following formula:
Default IP MTU = Default Supporting Media MTU – Encapsulation Size. MTU can be also explicitly configured
per family.
Logical interfaces can be created and deleted by explicit user configuration. This includes the following types
of interfaces:
 Loopback interfaces. These interfaces are always assigned with IP address and /32 (for Ipv4) or /128
(for Pv6) subnet mask. MTU for these interfaces is not relevant
 Ethernet port/LAG or VLAN-based interfaces. These interfaces can be explicitly defined as PtP, in which
case they can also be treated as unnumbered. Alternatively, they may be treated as LAN interfaces, in
which case they must be assigned with IP address and subnet mask in the relevant family. In the case
of a channelized Ethernet port/LAG there is no restriction on assigning different families (or
combinations of families) to different VLAN-based LIFs on this port/LAG.
 Ethernet PWs that are terminated in VRF (with L3VPN support). These interfaces typically will be
assigned with IP address and subnet mask in the relevant families.
In addition in IP/MPLS all tunnel LSPs (i.e., LSPs associated with /32 IPv4 prefixes) will be treated as
unnumbered PtP IP interfaces. In particular:
 The payload of a received labeled packet such that all its labels are popped and the BoS label has been
associated with a /32 IPv4 prefix will be treated as a received IPv4 packet and handled accordingly
 A tunnel LSP may be specified as the Next Hop of a host route with zero cost towards the /32 prefix
defining its FEC in the RIB and FIB. This will cause all IP packets with matching Destination IP to be sent
via this tunnel LSP.

LCT-NPT® User Guide NE configuration and management in IP/MPLS
7.1.1 Manage loopback interfaces

Loopback interface is an IP interface that is not associated with any physical media. A loopback interface
must be assigned with an IP address and a /32 subnet mask (.128 subnet mask for IPv6).
To manage loopback interfaces:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the CS module.
2. In the Configuration working mode, select the Logical Interfaces tab and then Loopback Interfaces.
3. To create a loopback interface, click .

The Create Loopback Interface window opens.
To configure the loopback interface:

 Unit: Set a unit for the loopback interface.
 Enabled: Enable/disable the loopback interface.
 (Optional) Description: Set a description for the loopback interface.
 Families:
 INET: INET must always be enabled. The INET address must meet the IP validity check and
the INET mask is always 32. INET address cannot be in the same subnet with other LIFs.

 ISO: Up to one loopback LIF can configure ISO address. The format of ISO address is like
xx.xxxx.yyyy.yyyy.yyyy.00 (by default). For example: 49.0000.0203.0203.0203.0203.00.
Blank for ISO address is permitted.
 xx - stands for Area address information. Its max length is defined in IS-IS protocol
instance.
 yy - stands for System ID information. Changing System ID requires disabling IS-IS
protocol.
 00 - network selection that must have value 00.
4. Click Apply.
The loopback interface is saved.
5. To edit a loopback interface, select the required loopback interface, then click .
6. To delete a loopback interface, select the required loopback interface, then click .
7.1.2 Manage IRB interfaces

An Integrated Routing and Bridging (IRB) interface is a new type of LIF that facilitates seamless interconnect
between routed IP connectivity in an IP/MPLS domain and IP connectivity (for in-band management purposes
only) in a PB domain comprised of legacy NPT devices that employ their "management VLAN" mechanism for
in-band management.
IRB interfaces are introduced for seamless interconnect between routed and switched IP connectivity for in-
band management purposes. The network reference model for this application is shown in the following
figure.
Figure 7-1: Network Reference Model for Interconnect of Routed and Switched Domains

This diagram shows a single management domain that is comprised of an IP/MPLS core sub-domain and a PB
sub-domain. Two management stations are connected to appropriate interfaces of devices in both sub-
domains, and each management station can access each of the managed NEs in both sub-domains.
With regard to management traffic:
 NPT-1800 devices forming the IP/MPLS domain treat it as any other IP traffic:
 Locally generated packets are transmitted in accordance with the current FIB.
 IP packets received from one of IP interfaces are forwarded via another such interface based on
the current FIB:
 As part of this forwarding their L2 encapsulation is terminated on ingress and regenerated
on egress.
 Packets with destination IP address being owned by the receiving node are ushered for local
processing in the Router IP stack and eventually passed to the appropriate management
application.
 Legacy devices forming the PB sub-domain treat management IP traffic as being propagated across a
dedicated MPtMP VSI (Management VLAN):
 Each devices possesses a single globally unique "Device MAC address".
 An internal interface connects the SW-based L3 forwarder in the MCP of the legacy device with
this VSI (from the VSI point of view this interface is just an attachment circuit).
 The VSI FIB is programmed with a static entry associating the device MAC address with the
internal interface.
 A L2 frame that is, upon reception, associated with the "Management VLAN VSI", handled in
accordance with the common L2 forwarding rules:
 If its Destination MAC address is unicast and can be found in the FIB (a known unicast frame),
it is forwarded via the port with which its Destination MAC address is associated in the VSI
FIB
 Otherwise (if the Destination MAC address is a Broadcast, Multicast or Unknown unicast), it
is flooded to all the ports of the VSI excluding the port from which it has been received
 Source MAC address of the received frame is learned, i.e., associated with the ingress port
in the VSI FIB.
Gateway NPT-1800 nodes in the diagram must combine routing and switching functionalities in treating IP
traffic. The IRB interface provides this functionality in accordance with the logical scheme shown in the
following figure.

To manage IRB interfaces:

2. In the Configuration working mode, select the Logical Interfaces tab and then IRB Interfaces.
3. To create an IRB interface, click .

The Create IRB Interface window opens.
4. To configure the loopback interface, enter the relevant information:
 Unit: Set a unit ID for the loopback interface.
 Enabled: Enable/disable the loopback interface.
 (Optional) Description: Set a description for the loopback interface.

 Families:
 INET: INET must always be enabled. The INET address must meet the IP validity check and
the INET mask can be 1~32. The INET address cannot be in the same subnet with other LIFs.
 ISO: Enable/disable the ISO family.
5. Click Apply.
The IRB interface is saved.
6. To edit an IRB interface, select the required IRB interface, then click .
7. To delete an IRB interface, select the required IRB interface, then click .
7.1.3 View IP interface list

You can view all the IP interfaces in the IP interface list, as described in this section.
To view the IP interface list:

2. In the Configuration working mode, select the Logical Interfaces tab and then LIF List.
3. To refresh the IP interfaces from NE to view, click .

7.2 IP routing management

This section describes how to manage routing.
7.2.1 View routing options

To view the routing options:
2. In the Configuration working mode, select IP Routing > Routing Options.
3. To refresh the information from NE to view, click .

7.2.2 View policy options

To view policy options:
2. In the Configuration working mode, select IP Routing > Policy Options.
3. To refresh the information from NE to view, click .
7.2.3 Manage the routing policy

Routing policies are filters that define how routes are handled based on the values of their attributes. The
filters contain a rule (that is applies to the values of specific attributes) and an action. The rules are commonly
split into "from" rules (applied to the attributes dealing with the route source, e.g., protocol, AS Path) and
"to" attributes (e.g., destination, RIB component etc.).
The following actions are common in routing policies:
 Accept – the route passes the filter
 Deny – the route does not pass the filter
 Tag – the Tag attribute of the route is changed to the value specified in the action

 Prepend AS Path – AS specified in the action will be prepended to the AS Path

 Local preference – sets local preference of this route (a common non-standard BGP attribute) to the
value specified in the action.
Routing policies can be used as import and export policies of routing protocols thus facilitating re-distribution
of routes learned via one protocol by some other protocol.
 When a routing policy is used as an export policy, matching routes are re-distributed by the protocol to
which this export policy applies.
 When a routing policy is used as an import policy, matching routes are installed in the local RIB.
To manage the routing policies:

2. In the Configuration working mode, select IP Routing > Routing Policy.
3. To create a new routing policy, click .

The Create Routing Policy window opens.
4. In the Policy Name field, set a name for the policy.

You can now configure one or more routing policy terms for the new routing policy.

5. To create a routing policy term:
a. Click .
The Create Routing Policy Term window opens.
Set the parameters as required.

b. Click Apply.
The policy term is saved.
6. In the Create Routing Policy window, click Apply.

The policy is saved.

7. To edit a policy, select the required policy, then click .
8. To delete a policy, select the required policy, the click .
7.2.4 View policy state

To view policy state:
2. In the Configuration working mode, select Protocols > IP Routing > Policy State.
The policy state information appears.

7.2.5 Manage static routes

To manage static routes:
2. In the Configuration working mode, select the IP Routing tab and then Static Routes.
3. To create a static route, click .

The Create Static Routes window opens.
4. Set the parameters as required.

5. Click Apply.
The static route is saved.
6. To edit a static route, select the required static route, then click .
7. To delete a static route, select the required static route, then click .

7.2.6 View actual routes

To view the actual routes:
2. In the Configuration working mode, select IP Routing > Actual Routes.
3. In the Filter area, set the parameters as required to filter the routes.
4. To refresh the actual routes from NE to view, click .

7.2.7 View forwarding table

To view forwarding table:
2. In the Configuration working mode, select the IP Routing > Forwarding Table.
4. To refresh the forwarding table to view, click .

7.2.8 View multicast forwarding table

To view multicast forwarding table:
2. In the Configuration working mode, select the IP Routing > Multicast Forwarding Table.
4. To refresh the multicast forwarding table to view, click .

7.2.9 View the ARP table

To view the ARP table:
2. In the Configuration working mode, select the IP Routing tab and then ARP Table.
4. To refresh the ARP table to view, click .
5. To clear all the entries, click .

7.2.10 Perform IP ping and trace route

To perform IP ping and trace route:
2. In the Maintenance working mode, select the IP Ping and Trace Route tab.
By default, the IP Ping and Trace Route tab opens with the Ping option selected.
3. To perform IP ping:
a. In the Operation Type field, select the Ping radio button.
b. Set the parameters as required.
c. Set the refresh interval.
d. To start IP ping, click .

4. To perform trace route:
a. In the Operation Type field, select the Trace Route radio button.
b. Set the parameters as required.
c. Set the refresh interval.
d. To start trace route, click .

7.3 OSPF protocol management in IP/MPLS

Open Shortest Path First (OSPF) protocol is one of a family of IP Routing protocols, and is an Interior Gateway
Protocol (IGP) for the Internet, used to distribute IP routing information throughout a single Autonomous
System (AS) in an IP network.
The OSPF protocol is a link-state routing protocol, which means that the routers exchange topology
information with their nearest neighbors. The topology information is flooded throughout the AS, so that
every router within the AS has a complete picture of the topology of the AS. This picture is then used to
calculate end-to-end paths through the AS, normally using a variant of the Dijkstra algorithm. Therefore, in a
link-state routing protocol, the next hop address to which data is forwarded is determined by choosing the
best end-to-end path to the eventual destination.
The main advantage of a link state routing protocol like OSPF is that the complete knowledge of topology
allows routers to calculate routes that satisfy particular criteria. This can be useful for traffic engineering
purposes, where routes can be constrained to meet particular quality of service requirements. The main
disadvantage of a link state routing protocol is that it does not scale well as more routers are added to the
routing domain. Increasing the number of routers increases the size and frequency of the topology updates,
and also the length of time it takes to calculate end-to-end routes. This lack of scalability means that a link
state routing protocol is unsuitable for routing across the Internet at large, which is the reason why IGPs only
route traffic within a single AS.
Each OSPF router distributes information about its local state (usable interfaces and reachable neighbors,
and the cost of using each interface) to other routers using a Link State Advertisement (LSA) message. Each
router uses the received messages to build up an identical database that describes the topology of the AS.
From this database, each router calculates its own routing table using a Shortest Path First (SPF) or Dijkstra
algorithm. This routing table contains all the destinations the routing protocol knows about, associated with
a next hop IP address and outgoing interface.

 It provides support for multiple paths of equal cost.

 It provides a multi-level hierarchy (two-level for OSPF) called "area routing", so that information about
the topology within a defined area of the AS is hidden from routers outside this area. This enables an
additional level of routing protection and a reduction in routing protocol traffic.
 All protocol exchanges must be authenticated so that only trusted routers can join in the routing
exchanges for the AS.
Figure 7-2: The OSPF Protocol
The protocol is running over IP as shown in the following figures.

Figure 7-3: Relationship between TCP and OSPF - 1

Figure 7-4: Relationship between TCP and OSPF - 2
7.3.1 Manage OSPF instances

An OSPF instance can be created only when a routing instance has configured router ID.
To manage OSPF instances:

2. In the Configuration working mode, select the Protocols, OSPF, and then OSPF Instances tabs.

3. To create an OSPF instance, click .
Configure the parameters for the OSPF instance:

 Enable: Enable or disable OSPF protocol.
 Version: OSPF version implemented (2 for OSPFv2 and in future 3 for OSPFv3).
 Max ECMP: Maximum number of Equal Cost Multi-Path (ECMP) paths. It is fixed to 8.
 External Preference: Set preference for external routes in order to prioritize protocols packets.
 Internal Preference: Set preference for internal routes.
 Reference Bandwidth: The attribute is used for calculating default interface metrics.
 Export Routing Policy: To apply a routing policy to routes exported from other protocols to OSPF,
include export statement.
 FRR Enable: Enable or disable the fast reroute.
 Remote LFA: set the remote loop-free alternate as disabled or MPLS LDP.
 Graceful Restart Enable: Enable/Disable graceful restart.
 Graceful Restart Time: The time a neighbor should wait for the router to restart when it loses
communication with the router.
 Graceful Helper Enable: It has no effect on the local restart behavior, so may be set independently
of Graceful restart enable value.
 Strict LSA Checking: Indicates if strict LSA checking is enabled for graceful restart. When it is
enabled, perform strict LSA checking stop acting as restart helper if it transmits an LSA to the
restarting node indicating a topology change. Set it disabled to disable strict LSA checking.
4. Click Apply.
The OSPF instance is saved.

5. To edit an OSPF instance, select the required OSPF instance, then click .
6. To view details of an OSPF instance, select the required OSPF instance, then click .
7. To overwrite the data to the database, click .
8. To delete an OSPF instance, select the required OSPF instance, then click .
7.3.2 Manage OSPF areas

The following describes the OSPF area types and the corresponding description:
Standard Area - Accepts link updates, route summaries, and external routes (the default).
Backbone Area (as known as area 0, called also "transit area") - The area responsible for distributing routes
between all other areas. All ABRs must be connected to the backbone area, although not every router in the
backbone area must be an ABR. The backbone is most often a physically contiguous network; however, virtual
links can be created between non-contiguous ABRs.
Non Backbone Area - Area that its area ID is other than area 0
Stub Area - An area on the edge of the OSPF routing domain that is not flooded with advertisements for AS-
external routes. Stub areas rely on default routing to forward traffic to external destinations and can use
default routing to forward traffic to inter-area destinations. This greatly decreases the size of the link state
database for the stub area. Stub area routers require less memory and processing resources. Routers in stub
areas cannot be AS boundary routers, and virtual links cannot be created through stub areas.
Figure 7-5: Stub Area
Totally Stubby Area - Does not accept external autonomous system routes or summary routes from other
areas internal to the autonomous system. The ABR of the totally stubby area blocks type 4 and 5 LSAs as well
as all summary LSAs (type 3), with an exception of a single type 3 LSA to advertise the default route. The
default route advertised by the ABR is used to reach destinations external to the autonomous system and all
destinations external to the area. Therefore, if the router needs to send a packet to a network external to
the area, it sends the packet using a default route. Totally stubby areas cannot contain ASBRs (except that
the ABRs may also be ASBRs).

Not-So-Stubby Area (NSSA) - Similar to a stub area, an NSSA allows external routes from a non-OSPF source
to be imported into the area. These external routes are advertised to other OSPF areas; however, external
routes from other OSPF areas are not advertised to an NSSA. The area serves as a one-way filter for external
routing information.
Figure 7-6: NSSA Area

The following describes the OSPF area and routing:

Figure 7-7: OSPF Area and Routing
Table 7-1: Explanations

Router Role Explanation
R2, R3 and R4 ABR router As they have links between backbone area and non-
backbone area.
R12 and R13 ABR router Support Virtual link to the backbone area.
R12 Also ABR for stub area R12 defines as a default gateway router for area 4 stub
area.
R3, R9 , R15 IR For OSPF: as the interfaces reside in the same non-
backbone area.
ASBR router Exchange routing information between different
Autonomous Systems.
R10, R11, R6, R7 and IR Their interfaces reside in the same non-backbone area.
R14

To manage OSPF areas:

2. In the Configuration working mode, select the Protocols, OSPF, and then OSPF Areas tabs.
3. To create an OSPF area, click . The Create OSPF Areas window opens.
Set the parameters as described here:

 Area ID: A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used for the OSPF
backbone. Note that the Area ID can be an integer or in IP address format. When defined as an
integer e.g. area 2 it is treated as area 0.0.0.2.
 Area Enable: Enable or disable OSPF area.
 Stub: One of the area types. The area type indicates if an area is a stub area, NSSA, or standard
area.
NOTE: EMS-NPT V5.1 supports only normal and stub area types.
 Default Metric: Defines the OSPF default metric value for LSA advertisement used by ABRs in
NSSA or Stub areas.
 Area Summary: Area summary controls the import of summary LSAs into stub and NSSA areas. It
has no effect on other areas. If it is noAreaSummary, the router will not originate summary LSAs
into the stub or NSSA area. It will rely entirely on its default route. If it is sendAreaSummary, the
router will both summarize and propagate summary LSAs.
 Area Range: Summarize routes matching address/mask (border routers only). Note that
network/mask-length is a range to match against reachable routes in the area. These routes are
not advertised at the area edge; instead, the ABR advertises a summary of these routes.
 Advertise: When advertise value is true, subnets subsumed by ranges trigger the advertisement
of the indicated summary. When advertise is false, it results in the subnet not being advertised at
all outside the area. Note that when advertise is false it prevents the ABR from advertising a
summary of the routes.
4. Click Apply.
The OSPF area is created.
5. To edit an OSPF area, select the required OSPF area, then click .
6. To delete an OSPF area, select the required OSPF area, then click .

7.3.3 Manage OSPF LIFs

If OSPF instances are not created, the OSPF LIF cannot be created.
To manage OSPF LIFs:

2. In the Configuration working mode, select the Protocols, OSPF and then OSPF LIFs.

3. To create an OSPF LIF, click .

The Create OSPF LIFs window opens.
Set the parameters as described here:

 LIF Name: Select a LIF from the dropdown list.
 Area ID: A 32-bit integer uniquely identifying the area to which the interface connects. Area ID
0.0.0.0 used for the OSPF backbone.
 OSPF LIF Enable: Enable/disable the OSPF LIF.
 LIF Type: Type of the OSPF LIF, which can be set as Point-To-Point or Broadcast.
 Passive: Defines if the OSPF LIF is in passive mode (OSPF not running, but network is advertised)
or not. Loopback LIF/IRB LIF can only be passive.
 Metric: The OSPF LIF metric is used when OSPF performs the link state calculation. Routes with a
lower metric value are preferred over routes with a higher metric value.
 Hello Interval: The length of time, in seconds, between the Hello packets the router sends on the
interface. This value must be the same for all routers attached to a common network.
 Dead Interval: The number of seconds that a router's Hello packets have not been seen before its
neighbors declare the router down. This should be some multiple of the Hello interval. This value
must be the same for all routers attached to a common network.
 Transmit Interval: Define the interval before sending a LSU packet, in order to add more LSAs to
the packet. Setting this correctly can reduce the network traffic.
 Transit Delay: The estimated number of seconds it takes to transmit a link state update packet
over this interface.

 Retransmit Interval: The number of seconds between link state advertisement retransmissions,
for adjacencies belonging to this interface. This value is also used when retransmitting database
description and Link State request packets. Note that minimal value must be 1 second.
 BFD Enable: Configure automatic BFD session for this OSPF interface.
 Strict: Preclude the establishment of adjacency based on BFD.
 FRR Exclude Adjacency: Enable or disable the FRR exclude adjacency.
 No Eligible Backup: Enable or disable the no eligible backup.
 Authentication Type: Defines the available authentication types:
 None – No authentication used.
 Key Chain – Allows keeping several keys per authentication scheme (e.g. MD5, SHA-256).
 Key Chain attributes – When selecting Key Chain the following attributes apply:
 Key Chain Name: Name of the key chain. Used for cases where different cryptography
schemes are required (e.g.: Simple Password, MD5, SHA-256). A chain can carry a list of keys
using the same cryptography scheme.
 Scheme: Authentication scheme including cryptographic schemes:
 Simple Password: The cleartext password (as known as simple password
authentication) uses key length up to 8 octets/bytes. If the key length is shorter than
8 octets, the agent will left adjust and zero fill to 8 octets. Note that the use of
simple Password authentication is NOT recommended when there is concern
regarding attack upon the OSPF system. Simple Password authentication is only
sufficient to protect against accidental misconfigurations because it re-uses cleartext
passwords.
 MD5: Authentication key maximum size is 16 bytes.
 SHA-256 (supported in v5.1): Authentication key maximum size is 32 bytes.
4. Click Apply.
The OSPF LIF is created.
5. To edit an OSPF LIF, select the LIF, then click .
6. To delete an OSPF LIF, select the LIF, then click .

7.3.4 Manage OSPF virtual links

Virtual links connect areas that do not have physical connections to the backbone, and are treated as
numbered point-to-point links. Virtual links are used for two purposes:
Linking an area that does not have a physical connection to the backbone:
Patching the backbone in case discontinuity of area 0 occurs:
An example of a virtual link is provided in the following figure:
This figure shows a virtual link established between area 0.0.0.3 and the backbone area through area 0.0.0.2.
The virtual link transits area 0.0.0.2. All outbound traffic destined for other areas is routed through area
0.0.0.2 to the backbone area and then to the appropriate ABR. All inbound traffic destined for area 0.0.0.3 is
routed to the backbone area and then through area 0.0.0.2.

To manage OSPF virtual links:

2. In the Configuration working mode, select Protocols > OSPF > Virtual Links.
3. To create a virtual link, click .

The Create OSPF Virtual Links window opens.
4. Configure the following parameters:

 Area ID: A 32-bit integer uniquely identifying the area to which the link connects. Area ID 0.0.0.0
used for the OSPF backbone.
 Virtual Area ID: The ID of the transit area that the virtual link traverses. This cannot be 0.0.0.0.
 Virtual Neighbor: The IP address of the virtual neighbor.
 Virtual Link Enable: Enables or disables the virtual link.
 Dead Interval: The number of seconds that a router's Hello packets have not been seen before its
neighbors declare the router down. This should be some multiple of the Hello interval. This value
must be the same for all routers attached to a common network.
 Transmit Interval: Defines the interval before sending a LSU packet, in order to add more LSAs to
the packet.
 Transit Delay: The estimated number of seconds it takes to transmit a link state update packet
over this interface.
 Retransmit Interval: The number of seconds between link state advertisement retransmissions,
for adjacencies belonging to this interface. The minimal value is 1 second.

5. To define security for the virtual link, select Key Chain from the Authentication Type dropdown list.
The key chain settings appear.
Select a template from the Key Chain Template dropdown list (see Manage OSPF key chain templates), or
define the key chain settings manually by clicking and defining the parameters in the Key Chain and
Key Entry tables:
 Name: Name of the key chain. Used for cases where required different cryptography
schemes (e.g. Simple Password, MD5, SHA-256). A chain can carry a list of keys using the
same cryptography scheme.
 Scheme: Authentication scheme, including cryptographic schemes:
 Simple Password: A cleartext password that uses a key length of up to 8
octets/bytes. If the key length is shorter than 8 octets, the agent will left-adjust and
zero-fill to 8 octets. Note that the use of simple password authentication is NOT
recommended when there is concern for an attack on the OSPF system. Simple
password authentication is only sufficient to protect against accidental
misconfigurations because it re-uses cleartext passwords.
 MD5: Authentication key, maximum size is 16 bytes.
 HMAC-SHA256: Authentication key, maximum size is 32 bytes.
6. Click Apply. The virtual link is saved.
7. To edit a virtual link, select the virtual link, then click .
8. To view details of a virtual link, select the virtual link, then click .
9. To delete a virtual link, select the virtual link, then click .
7.3.5 Manage OSPF key chain templates

OSPF authentication packets, when passing cryptography schemes, require the introduction of a key-id. This
is required for MD5 and SHA-256 authentication.
Following the introduction of RFC5709 for the OSPFv2 protocol, new authentication schemes were added,
which introduced the ability to support more than one key per interface.
Accordingly, new attributes were added as follows:
 Key-id: 8 bit attribute (0-255) used to uniquely identify OSPFv2 SA (Security Association)
 Authentication Algorithm: Used also to specify the cryptographic mode like UMAC-SHA-256
 Authentication key: The key value (not sent in clear text format)

In EMS-NPT V5.1 each interface supports a single key-chain consisting of a single key per authentication
scheme.
To manage OSPF key chain templates:

2. In the Configuration working mode, select Protocols > OSPF > Key Chain Templates.
3. To create a key chain template, click .

The Create Key Chain Template window opens.
4. Click to add key chains and define them in the Key Chain and Key Entry tables:
 Name: Name of the key chain. Used for cases where different cryptography schemes are required
(e.g.: Simple Password, MD5, SHA-256). A chain can carry a list of keys using the same
cryptography scheme.
 Scheme: Authentication scheme, including cryptographic schemes:
 Simple Password: A cleartext password that uses a key length of up to 8 octets/bytes. If the
key length is shorter than 8 octets, the agent will left-adjust and zero-fill to 8 octets. Note
that the use of simple password authentication is NOT recommended when there is concern
for an attack on the OSPF system. Simple password authentication is only sufficient to
protect against accidental misconfigurations because it re-uses cleartext passwords.
 MD5: Authentication key, maximum size is 16 bytes.
 HMAC-SHA256: Authentication key, maximum size is 32 bytes.
5. Click Apply. The key chain template is saved.
6. To edit a key chain template, select the template, then click .
7. To view details of a key chain template, expand the template row or select the template and click
.
8. To delete a key chain template, select the template, then click .

7.3.6 View OSPF instance status

To view OSPF instance status information:
 In the IP/MPLS NE Shelf View window, in the left object tree, select the CS module.
 In the Configuration working mode, select Protocols > OSPF > Instance Status.
The OSPF instance status information appears.
7.3.7 View OSPF LIF status

To view OSPF LIF status:
2. In the Configuration working mode, select Protocols > OSPF > LIF Status.
The default parameters of the LIF status are described here:
 Interface Name: Name of the interface. Reference to the interface within the Routing Instance.
 I/F State: The OSPF interface state.
 Admin State: The OSPF admin state.
 Area ID: A 32-bit integer uniquely identifying the area to which the interface connects. Area ID
0.0.0.0 used for the OSPF backbone.
 Area Type: The defined area type.
 Designated Router ID: IP Address of the designated router.
 Backup Designated Router ID: IP address of the Backup Designated router.

 Number of Neighbors: Number of neighbors the interface has.

3. To customize the table columns displayed by selecting the table columns to show or hide, click the blank
Configure Columns button located in the top right corner of the table.
The Field Chooser window opens.

4. Select the columns you want to display from the list of Available Fields on the left.
5. Click the right/left arrow buttons to move selected fields into the Selected Fields list on the right, or
back to the Available Fields list on the left.
6. Click the up/down arrow buttons to rearrange the order of the fields in the Selected Fields list on the
right.
7. Click Apply to save your selections.
8. Click Restore Default to display the default set of table columns.
9. To refresh the status to view, click .

7.3.8 View OSPF virtual link status

To view OSPF virtual link status:
 In the Configuration working mode, select Protocols > OSPF > Virtual Link Status.
The virtual link status information appears.
7.3.9 View OSPF neighbors

To view OSPF neighbors:
2. In the Configuration working mode, select Protocols > OSPF > Neighbors.
3. To refresh the parameters to view, click .
7.3.10 View the OSPF database

To view the OSPF database:
 In the Configuration working mode, select Protocols > OSPF > Database.
The OSPF database appears.
7.3.11 View LDP FRR status

To view LDP FRR status:
2. In the Configuration working mode, select Protocols > OSPF > LDP FRR Status.
3. To refresh the parameters to view, click .
7.4 IS-IS protocol management in IP/MPLS

Intermediate System-to-Intermediate System (IS-IS) is an interior gateway protocol (IGP) that uses link state
information to determine the availability of routes. IS-IS uses an SPF (Shortest Path First) algorithm, such as
Dijkstra’s, to compute the best path.
The International Organization for Standards (ISO) developed IS-IS as part of the Open Systems
Interconnection (OSI) protocol suite.
The ISO originally developed IS-IS to route data in an ISO Connectionless Network Protocol (CLNP) network
(ISO10589 or RFC 1142). Later on, it was adapted for IP Routing in addition to CLNP (RFC1195) as integrated
or dual IS-IS.

The protocol is conveyed directly on layer 2 and distributes routing information between routers belonging
to a single Autonomous System (AS), as shown in the following figure.
Figure 7-8: IS-IS Protocol
The IS-IS protocol runs over Layer 2 as shown in the following figures.

ISO addressing
Each node on a network has a unique address that conforms to the ISO addressing standard, and includes
the area to which the IS belongs.
The address where the network service can be accessed is known as the Network Service Access Point (NSAP)
for the CLNS packets.
There can only be one NSAP per router, and each NSAP can be from 8 to 20 bytes long.
The IS-IS protocol has the following addressing format:

7.4.1 Manage IS-IS instances

You can only create IS-IS instances if there are no OSPF instances.
To manage IS-IS instances:

2. In the Configuration working mode, select Protocols > IS-IS > IS-IS Instances.
3. To create an IS-IS instance, click .

The Create IS-IS Instance window opens.
4. Configure the following parameters for the IS-IS instance:

 Enable: Enables or disables the IS-IS protocol.
 Level Type: The type of IS-IS node.
 System ID: The system ID of the router.
 System ID Host Name: The name of the node.
 Max Area Address Length: The maximum number of areas supported.
 Area Address (read-only): The address part of the ISO address.
 Max ECMP: Maximum number of equal cost multi-paths. It if fixed to 8.
 Wait Time: Time (in seconds) to wait before entering.
 Reference Bandwidth: Used for calculating default interface metrics.
 IPV4 Routing Enable: Enables/disables IPV4 routing. Enabled by default.

 IPV6 Routing Enable (future): Enables/disables IPV6 routing. Disabled by default.

 Protocol Supported: Bit map used to specify additional supported protocols.
 Export Routing Policy: To apply a routing policy to routes exported from other protocols to IS-IS,
including export statement.
 LSP MTU: Size of the largest buffer.
 LSP Life Time: Aging period of LSP information. When it expires, LSPs are purged.
 LSP Refresh Time: Maximum interval, in seconds, between generated LSPs by this instance of the
protocol.
 FRR Option: Fast reroute option. Enables or disables the FRR option.
 Remote LFA: Remote loop free alternate, which can be set as Disable or MPLS LDP.
 Graceful Restart Enable: Enables or disables graceful restart.
 Graceful Restart Time: The time a neighbor should wait for the router to restart when it loses
communication with the router.
 Graceful Recovery Time: The maximum time that it takes to recover from a restart.
 Graceful Helper Enable: It has no effect on the local restart behavior, so may be set independently
of Graceful restart enable value.
5. Click Apply. The IS-IS instance is saved.
6. To edit an IS-IS instance, select the instance, then click .
7. To view details of an IS-IS instance, select the instance, then click .
9. To delete an IS-IS instance, select the instance, then click .

7.4.2 Manage IS-IS levels

To manage IS-IS levels:
2. In the Configuration working mode, select Protocols > IS-IS > IS-IS Level.
3. To create an IS-IS level, click .

The Create IS-IS Level window opens.
4. Define the following parameters for the IS-IS level:

 Level: IS-IS level identifier, where area(1) = L1 and domain(2) = L2.
 External Preference: Defines the preference for external routes in order to prioritize protocols
packets.
 Internal Preference: Defines the preference for external routes.
 Metric Type: The metric type.
 Default Metric Value: The IS-IS default metric value.
 Authentication Check Enable: Defines whether authentication of all PDUs on this level is
supported.
 Authentication Type: The authentication type, which can be:
 None: No authentication.
 Plaintext: A plaintext password is used for authentication.
 MD5-digest: Message-digest authentication.
 Authentication Key: Defines the authentication key.
 Overload Set Enable: Enables setting the overload bit for the level.
 Timeout: Defines the timeout for overload.
5. Click Apply. The IS-IS level is saved.

6. To edit an IS-IS level, select the level, then click .
7. To view details of an IS-IS level, select the level, then click .
9. To delete an IS-IS level, select the level, then click .
7.4.3 Manage IS-IS LIFs

You can only create an IS-IS LIF if IS-IS instances exist.
To manage IS-IS LIFs:

2. In the Configuration working mode, select Protocols > IS-IS > IS-IS LIFs.
3. To create an IS-IS LIF, click . The Create IS-IS LIFs window opens.
4. Define the following parameters:

 LIF Name: Select a LIF from the dropdown list.
 Enable: Enables/disables IS-IS LIF.
 Hello Padding: Enables/disables IS-IS hello padding.
 LIF Type: Type of IS-IS LIF, which can be Point-To-Point or Broadcast.
 Passive: Defines whether the IS-IS LIF is in passive mode (IS-IS is not running, but network is
advertised).

 Blocked: When enabled, prevents the interface from flooding LSPs to adjacent ISs.
 BFD Enable: Enables automatic BFD session for this IS-IS interface.
 Strict: Preclude the establishment of adjacency based on BFD.
 Level: The type of IS-IS interface level.
 Hello Authentication Type: The authentication type for hello messages, which can be:
 None: No authentication.
 Plaintext: A plaintext password is used for authentication.
 MD5-digest: Message-digest authentication.
 Hello Authentication Key: The authentication key for hello messages.
 Hello Multiplier: This value is multiplied by the corresponding Hello Timer and the result in
seconds (rounded up) is used as the holding time in transmitted hellos, to be used by receivers of
hello packets from this IS.
 LSP Pacing Interval: Minimum interval of time, in milliseconds, between transmissions of LSPs on
an interface at this level.
 Min LSP Retransmit Interval: Minimum interval, in seconds, between retransmission of an LSP at
this level.
 CSNP Interval: Minimum interval, in seconds, between sending Complete Sequence Number
PDUs at this level.
 PSNP Interval: Minimum interval, in seconds, between sending Partial Sequence Number PDUs
at this level.
 Metric: The wide metric value of this circuit for this level.
5. Click Apply. The IS-IS LIF is created.
6. To edit an IS-IS LIF, select the LIF, then click .
7. To delete an IS-IS LIF, select the LIF, then click .

7.4.4 View the IS-IS instance status

To view the IS-IS instance status information:
2. In the Configuration working mode, select Protocols > IS-IS > Instance Status.
The IS-IS instance status information appears.
7.4.5 View IS-IS LIF status

To view LIF Status:
2. In the Configuration working mode, select Protocols > IS-IS > LIF Status.
The IS-IS LIF status information appears.
7.4.6 View IS-IS adjacency

To view IS-IS adjacency:
2. In the Configuration working mode, select Protocols > IS-IS > IS-IS Adjacency.
The IS-IS adjacency information appears.
7.4.7 View the IS-IS database

To view the IS-IS database:
2. In the Configuration working mode, select Protocols > IS-IS > Database.
The IS-IS database appears.
7.4.8 View the LDP FRR status

To view IP FRR information:
2. In the Configuration working mode, select Protocols > IS-IS > LDP FRR Status.
The LDP FRR status information appears.
7.5 LDP protocol management in IP/MPLS

Label Distribution Protocol (LDP) LSPs are the infrastructure for IP-MPLS dynamic tunnels. In connectionless
technology (e.g. IP, UDP), packets are forwarded "hop by hop" based on information carried in the packet’s
header (e.g. destination IP address). Each node along the way takes a new independent forwarding decision
so the sender of the frame does not need prior arrangements with the destination before sending a packet.
MPLS makes the forwarding more efficient by looking at a short piece of data called a label that points
towards the interface to the next hop.
A connection in MPLS is referred by the concept of LSP (Label Switch Path) and is a unidirectional path. LDP
is one of the signaling protocols used in MPLS for setting up LSPs (connections) and exchanging connection
parameters before traffic can be sent over this LSP.
A frame is identified as MPLS frame by using the "MPLS label" concept. The value of the used label is signaled
between two nodes that want to hold a connection through MPLS Label Edge Routers (LER) are placed at the
edge of an MPLS domain and impose MPLS headers onto non-MPLS packets. This header contains a label
based on a FEC (Forwarding Equivalence Class) that the packet belongs to.
These packets are subsequently forwarded along an LSP. This forwarding allows the packets to be switched
through the MPLS network, so that they exit the network at the right destination. However, before the packet
can be forwarded along a label switched path, labels must be set along the path, and the path itself must first
be established.
Label switched paths can be established using a variety of mechanisms defined for MPLS, using a standard
signaling protocol or through manual configuration. LDP is one of the signaling protocols that may be used
for this task. LDP signaling protocol is used for setting up of LSP. These LSPs may be Tunnels or Pseudowires.
The basic LDP signaling protocol is defined by the IETF in RFC 5036. This RFC defines most of the protocol’s
procedures and messages.
LDP protocol realizes cross-connections between incoming labeled traffic into outgoing labeled at the right
direction towards its destination.
LDP relies on the Routing Information Base (RIB) to supply the information about routes towards
destinations.
A flavor of LDP is the targeted LDP (tLDP) that establishes LDP sessions between network-connected peers.
The network element uses the LSP-s and tunnels created by the tLDP to carry PW traffic and to support some
aspects of the LDP FRR feature. It may also be used for supporting IBGP connections between BGP routers.

7.5.1 Manage the LDP instance

To manage the LDP instance:
2. In the Configuration working mode, select Protocols > LDP > General.
3. To create an LDP instance, click .

The Create LDP Instance window opens.
4. Configure the following parameters for the LDP instance:

 LDP Protocol Enable: Enables/disables the LDP protocol on the NE level.
 LDP LIF Auto Enable: If enabled, the NE automatically creates an LDP entity on the LIF, when the
LIF’s MPLS and IP configuration is finalized.
 LDP FRR Enable: Enables/disables LDP FRR, which allows LSPs set up by LDP to follow the paths
modified by IP FRR.
 Graceful Restart: Enables/disables the graceful restart of the LDP protocol.
 Reconnect Timeout: The time (in milliseconds) that the sender of the TLV would like the receiver
of that TLV to wait after the receiver detects the failure of LDP communication with the sender.
Zero indicates that the NE does not preserve its MPLS forwarding over restart.
 Hello Hold Timer: The proposed maximum time the LDP hello will wait before declaring hello
adjacency down.
 LDP Initial Retry Delay: The delay of the first session establishment retry attempt after rejected
initialization message.

 Initialization Attempts Threshold: The number of session initialization attempts that if exceeded
trigger the Init Session Threshold Exceeded notification.
 Keep Alive Hold Timer: The NE-wide proposed maximum time that the LDP will wait before
declaring LDP session down.
 Local Label Binding: Defines label binding receive/transmit to/from local peers/LIFs.
If true (default) -
 This NE will accept/send label binding for FECs that do not appear in ldp-inbound/outbound-
label-policy, from/to local peers/ LIFs.
 This NE will accept/send FEC label bindings from/to local peers/ LIFs that do not appear in
ldp-inbound/outbound-label-policy.
If false -
 This NE will not accept/send label binding for FECs that do not appear in ldp-
inbound/outbound-label-policy, from/to local peers/ LIFs.
 This NE will not accept/send FEC label bindings from/to local peers/ LIFs that do not appear
in ldp-inbound/outbound-label-policy.
 Remote Label Binding: Defines label binding receive/transmit to/from remote peers.
If true (default) -
 This NE will accept/send label binding for FECs that do not appear in ldp-inbound/outbound-
label-policy, from/to remote peers.
 This NE will accept/send FEC label bindings from/to remote peers that do not appear in ldp-
inbound/outbound-label-policy.
If false -
 This NE will not accept/send label binding for FECs that do not appear in ldp-
inbound/outbound-label-policy, from/to remote peers.
 This NE will not accept/send FEC label bindings from/to remote peers that do not appear in
ldp-inbound/outbound-label-policy.
 Inbound Label Mapping Policy: List of term records. Each record defines the label binding action
with regards to incoming label bindings for peers list, FEC list and LIF list.
 Outbound Label Mapping Policy: List of term records. Each record defines the label binding action
with regards to label bindings to be advertised for peers list, FEC list and LIF list.
 Local Peers Security Policy: Defines response to basic discovery. If set, this NE will ignore basic
discovery messages (hello messages) originated by its peer that does not appear in the ldp-peer-
security list.
 Remote Peers Security Policy: Defines response to extended discovery. If set, this NE will ignore
extended discovery messages (targeted hello messages) originated by its remote peers.
 Allow Local Peer Hellos: Enables receiving hello messages from local peers.
 Allow Remote Peer Hellos: Enables receiving hello messages from remote peers.
5. Click Apply. The LDP instance is saved.
6. To edit an LDP instance, select the instance, then click .
7. To view details of an LDP instance, select the instance, then click .

9. To delete an LDP instance, select the instance, then click .
NOTE: There is only one LDP instance in the IP/MPLS.
7.5.2 Manage LDP/tLDP entities

To manage LDP/tLDP entities:
2. In the Configuration working mode, select Protocols > LDP > LDP/tLDP Entity Configuration.
3. To create an LDP/tLDP entity, click .

The Create LDP/tLDP Entity window opens.
4. To create an LDP entity, select LDP and define the following parameters:
adjacency down.
 Init Attempts Threshold: The number of session initialization attempts that if exceeded trigger
the Init Session Threshold Exceeded notification.
5. To create a tLDP entity, select tLDP and define the following parameters:
 Remote Peer Address: The address of the targeted LDP peer.
adjacency down.
 Init Attempts Threshold: The number of session initialization attempts that if exceeded trigger
the Init Session Threshold Exceeded notification.
 tLDP Entity Enable: Enables/disables the session associated with this tLDP entity. Applicable only
for targeted LDP entities.

 All Label Distribution: Enables distribution of labels for all /32 FEC to the remote peer of the
targeted session associated with this tLDP entity. By default, only PW labels are advertised.
Applicable only for targeted LDP entities.
6. Click Apply. The entity is saved.
7. To edit an entity, select the entity, then click .
8. To view details of an entity, select the entity, then click .
9. To delete an entity, select the entity, then click .
NOTES:
 There is a single LDP entity for all local peers in the IP/MPLS.
 There is one LDP per remote peer (targeted) LDP.
7.5.3 Configure LDP for LIFs

You can enable the LDP protocol on a LIF when both MPLS and IP are configured on it.
To configure LDP for a LIF:

2. In the Configuration working mode, select Protocols > LDP > LIF LDP.
3. Click .
The Create LIF LDP window opens.

 LIF: Select the LIF for which to enable LDP.
 LDP Enable: Enables the LDP protocol for the LIF.
 Explicit Null: If enabled, the NE advertises explicit null.
adjacency down.

5. Click Apply. LDP is enabled for the LIF, and it appears in the list.
6. To edit the LDP LIF configuration, select the LIF, then click .
7. To view the LDP LIF configuration, select the LIF, then click .
8. To delete the LDP LIF configuration, select the LIF, then click .
7.5.4 Manage LDP peer security

To manage LDP peer security:
2. In the Configuration working mode, select Protocols > LDP > Peers Security.
3. Click .
The Create Peer Security window opens.

 Peer Router ID: Enter the peer router ID.
 Banned Peer: Defines whether the NE will respond to discovery messages from this peer or
silently discard them (if enabled).
 Enable Security: If enabled, forces MD5 signature authentication by this peer.
 Shared Secret: Shared secret for securing communication using MD5.
5. Click Apply. The peer security configuration is saved.
6. To edit a peer security configuration, select it from the list and click .
7. To view details of a peer security configuration, select it from the list and click .
8. To delete a peer security configuration, select it from the list and click .

7.5.5 View LDP fixed attributes

To view fixed attributes:
2. In the Configuration working mode, select Protocols > LDP > LDP Fixed Attributes.
The LDP fixed attributes data appears.
7.5.6 View hello adjacencies

To view hello adjacencies:
2. In the Configuration working mode, select Protocols > LDP > Hello Adjacencies.
The hello adjacencies appear.
7.5.7 View LDP peers

To view LDP peers:
2. Then in the Configuration working mode, select Protocols > LDP > Peers.
The LDP peers appear.
7.5.8 View FEC

To view FEC information:
 In the Configuration working mode, select Protocols > LDP > FEC.
The FEC information appears.
7.5.9 View LDP session status

To view LDP session status:
2. In the Configuration working mode, select Protocols > LDP > Session Status.
The session status information appears.
7.5.10 View distributed label

To view distributed label information:

2. In the Configuration working mode, select Protocols > LDP > Distributed Label.
The distributed label information appears.
7.5.11 View learned label

To view learned label information:
2. In the Configuration working mode, select Protocols > LDP > Learned Label.
The learned label information appears.
7.6 VRRP management

The Virtual Router Redundancy Protocol (VRRP) provides redundant virtual gateways in the Local Area
Network (LAN), which is typically the first point of failure for end-hosts sending traffic out of a Local Area
Network (LAN) to which these hosts are connected (a.k.a. "upstream traffic").
The basic network reference model for VRRP is shown in the following figure.
Figure 7-9: Basic Network Reference Model for VRRP
In this model several IP hosts (H1, H2, H3 and H4) must send traffic to remote servers across a routed IP
network operated by an Internet Service Provider (ISP). These hosts are connected to a LAN, and this LAN is
connected to two (or more) edge devices of the ISP network (PE7 and PE8 in the diagram) so that:

1. A certain IP subnet is allocated for the LAN. This subnet will be later referred to as the "LAN subnet";
2. Interfaces (of both hosts and routers) connecting these devices to the LAN are assigned with IP
addresses from the LAN subnet.
In order to be able to send IP packets to remote servers, each host must be configured with some Gateway
IP address that can be reached directly via the LAN (i.e., belongs to the LAN subnet). This Gateway IP address
will be resolved by the host to the corresponding MAC address using ARP , and the resolved MAC address
would be used as the Destination MAC address (DMAC) in the Layer 2 encapsulation of the IP packet the
hosts sends to the remote server. LAN would then forward the packet to the corresponding edge router in
the ISP network, and from that moment it would be handled by this network.
If the host were configured, say, with IP address of PE7 as its Gateway IP address, all upstream traffic
generated by this host would be handled by PE7, so that if PE7 (or the interface that connects it to the LAN)
fails, the traffic would be black-holed even if the potential alternative gateway (PE8) and its connection to
the LAN remain intact.
7.6.1 Manage VRRP configuration

VRRP configuration is supported in the IP/MPLS NEs.
The following interfaces can configure VRRP:
 Single numbered IP LIF on an un-channelized Ethernet port/LAG
 Numbered IP LIF defined by a VLAN-tagged Ethernet port/LAG and any specific VLAN
 PHT interface
 IRB interface
 Interfaces used for connecting management stations (MNG port, AUX port)

To manage the VRRP configuration:

2. In the Configuration working mode, select the Protocols, VRRP and then Configuration.

3. To create a VRF, click .

The Create VRRP Configuration window opens.
Set the parameters as described in the table below.

4. Click Apply.
The VRF is created.
5. To edit a VRF, select the VRF, then click .
6. To view details of a VRF, select the VRF, then click .
7. To delete an OSPF LIF, select the LIF, then click .
Table 7-2: VRRP configuration attributes

VRRP attributes Description
VRID Unique in a given LAN.
VRRP Version Mix of different VRRP versions in the same group is not supported.
Virtual IP Address It must belong to the interface subnet.
Advertise Interval For VRRPv2 – uint8 (in seconds)
For VRRPv3 – uint16 in the range of 1 - 4095 (in hundreds of
milliseconds)
Preemption Mode If set to disabled and if the VIP is not equal to the interface IP
address, the VRRP Router in question will not preempt the current
Master even if its priority is higher.

Preemption Hold Time Only relevant if preemption mode is set to enabled. Indicates delay
in preemption following election of the interface as a new Master.
Priority 0 - the interface must not be selected as the Master in the VRRP
group.
255 – is implicitly set if Virtual IP matches the interface address.
Tracked Interfaces When the interface in the list leaves UP state, current priority is
decremented by the value in the corresponding pair. Negative
values are reverted to 0.
When an interface in the list transits to UP state, the current
priority value is increased by the decrement value in the
corresponding pair. Values that exceed 254 are reverted to 254.
The number of members in the list is limited to 8.
Tracked Prefixes If the RIB of the VRF to which the interface belongs does not
contain any active routes to a prefix in the list, the current priority
is decremented by the value in the corresponding pair. Negative
values are reverted to 0.
If the RIB acquires an active route to a prefix in the list, the current
priority is incremented by the decrement value in the
corresponding pair. Values that exceed 254 are reverted to 254.
Tracked Remote Interface An IPv4 multi-hop BFD session between the address of the VRRP
router and the specified address is set up and its state is
monitored. If this state is not UP, the priority of the VRRP router is
decremented by the specified value.
1-hop BFD Peers Contains IP addresses of the other interfaces in the same VRRP
Group.
If 1-hop IPv4 BFD to some address fails, and if this address belongs
to the current Master in the group, election of a new Master is
triggered.
BFD Mode In the Normal mode, a BFD session must first come to UP state to
be used for monitoring the peer.
In the Strict mode, if the session does not come up within some
hard-coded period, and if the peer for this session happens to be
Master, it will be considered as failed.
The same mode will be applied to all peers.
Accept Mode If set to enabled, and if the interface is the current Master in the
VRRP group, it will generate responses to received ICMP Echo
packets with destination IP address that matches the Virtual IP
address of the group.

7.6.2 View VRRP state

To view VRRP state:
2. In the Configuration working mode, select the Protocols, VRRP and then Configuration.
The VRRP state appears.
Table 7-3: VRRP state attributes

VRRP state attributes Description
Virtual MAC Address Computed from VRID.
Current Role Reflects the results of the Master election process.
Current Priority Reflects the results of object tracking.
Current Master If the current role is Backup - IP address that has been received as the
Source IP address in the last received VRRP Advertisement message.
Otherwise - IP address of the interface.
Last transition Date and time when the last change of Master has been detected.
Up Time The time when VRRP Router has exited from its "Initialize" state.

Master Down Time Computed from the Advertise interval.

Skew Time Computed from the Advertise interval and current priority.
7.6.3 View VRRP statistics

To view VRRP statistics:
1. In the following VRRP Configuration list, right-click a VRRP, from the shortcut menu, select
Performance Statistics.
Or
In the IP/MPLS NE Shelf View window, in the left object tree, select the CS module.

Then in the Performance working mode, select the Statistics tab.
2. In the Display area, select the VRRP LIF object.

3. In the Filter area, select an object as required.
4. Click .
You can view the data in the list.
5. To reset PM counters, click .

6. To refresh the data automatically:
a. Select the Refresh Data Dynamically checkbox.
b. Enter the refresh interval in the Refresh Interval field.
7. Click Start Refresh.

7.7 BGP protocol management in IP/MPLS

Border Gateway Protocol (BGP) is a standardized protocol designed to exchange routing and reachability
information between autonomous systems (AS) on the Internet. The protocol is often classified as a path
vector protocol but is sometimes also classed as a distance-vector routing protocol.
The Border Gateway Protocol makes routing decisions based on paths, network policies, or rule-sets
configured by a network administrator and is involved in making core routing decisions.
BGP can be used for routing within an AS. In this application it is referred to as Interior Border Gateway
Protocol, Internal BGP, or iBGP.
In contrast, the Internet application of the protocol may be referred to as Exterior Border Gateway Protocol,
External BGP, or EBGP.
NPT supports Multiprotocol Extensions for BGP (MBGP) that is needed for L3VPN implementation.
Layer 3 VPN
A Virtual Private Network (VPN) extends a private network across a public network, such as the Internet. It
enables a computer or network-enabled device to send and receive data across shared or public networks as
if it were directly connected to the private network, while benefiting from the functionality, security and
management policies of the private network.
A VPN connection across the Internet is similar to a wide area network (WAN) link between websites. From
a user perspective, the extended network resources are accessed in the same way as resources available
within the private network.
One major limitation of traditional VPNs is that they do not tend to support or connect broadcast domains.
Therefore communication, software, and networking, which are based on layer 2 and broadcast packets,
such as NetBIOS used in Windows networking, may not be fully supported or work exactly as they would on
a real LAN. Variants on VPN, such as Virtual Private LAN Service (VPLS), and layer 2 tunneling protocols, are
designed to overcome this limitation.
Layer 3 VPN utilizes layer 3 VRF (VPN/virtual routing and forwarding) to segment routing tables for each
"customer" utilizing the service. The customer peers with the service provider router and the two exchange
routes, which are placed into a routing table specific to the customer.
Multiprotocol BGP (MP-BGP) is required in the cloud to utilize the service, which increases complexity of
design and implementation. L3 VPNs are typically not deployed on utility networks due to their complexity;
however, a L3 VPN could be used to route traffic between corporate or datacenter locations.
In the following figure, there is an example of network that supports two customers' VPNs.
An eBGP session exists for each VRF, with the VPN eBGP peer.

A full mesh of iBGP sessions exists among all BGP speakers. Third party Route Reflector may function as if
there is a full mesh of iBGP session.
Figure 7-10: Layer 3 VPN Support
One VPN is in sites 2 and 4. The other VPN is in sites 1, 3 and 4.

Provider Edge router 4 (PE4) has two VRFs. It establishes one eBGP within each VRF.
PE4 learns routing and reachability information from site 4 about the two VPNs.
Using VPN-IPv4 address family it advertises the routes to all its iBGP peers.
According the labels and the Route Target associated with route, PE2 eBGP selects only the routes that were
learnt from the orange VPN to be informed to CE2.
In a similar way, eBGP of PE3 and PE4 select only the routes that were learnt from the blue VPN to be
informed to CE3 and CE4.
eBGP PE1, PE2 and PE3 perform the same activities for the routing and reachability information learnt from
CE1, CE2 and CE3.
The traffic that should traverse the service provider’s network does it via LDP LSP-s.
Policies for Layer 3 VPN
Implementation of the layer 3 VPN requires appropriate settings of import and export policies.
Implementation of the layer 3 VPN requires appropriate settings of import and export policies.
 VRF BGP Import Policy
The VRF BGP filters incoming routes according the supported VPN address families - IPv4-unicast. It
drops all incoming routes that do not belong to this address family.
 VRF Export Policy
By default, no routes are distributed from the VRF to the default/Global routing instance BGP (called
also VRF-0 or default routing instance).

 Global BGP Export Policy

Global BGP allows export all VPN-IPv4 address family routes to all internal BGP peers.
Inter-AS Routing for Management Reachability
LCT-NPT supports exchange routing and reachability information between autonomous systems (AS) to
enable management reachability.
In the following figure, AS-A connects to multiple neighboring Autonomous systems.
Each edge router runs eBGP session with its peer in the neighbor AS.
Full mesh iBGP sessions are established among all BGP speakers within AS domain. It may be implemented
by using Routes Reflector.
Figure 7-11: Management Reachability Inter-AS Routing
In the preceding figure, management system in AS-1 should manage ME-s in AS-A and AS-4.
R-1 advertises to ER1, via eBGP, route to the management system.
ER1 redistributes this route into the IGP. Thus, all AS-A ME-s can reach the management system.
AS-A ME messages traverse the AS-A towards ER1 according IGP route.
ER1 forwards the packets to R-1, and this forwards them according IGP to Management System.
ER1 advertises the route to the management system, via iBGP towards ER4.
ER4 advertises this route to R-4 via eBGP. ER4 redistribute this route into AS-4 IGP.
Thus, all AS-4 ME-s can reach the management station.
AS-4 ME messages traverse AS-4 towards R-4 using IGP route. R-4 forwards them to ER4. ER4 sends them via
LDP tunnel towards ER1.
ER1 forwards the packets to R-1, and this forwards them according IGP to Management System.
On the other direction, R-1 should get routes to each ME enabling messages forwarding from management
system to each ME.
R-4 advertises the ME-s prefixes via eBGP to ER4. ER4 advertises the route to all these prefixes using iBGP
with itself as next hop and with a label to be used in the LDP tunnel.

ER1 advertises the received route using eBGP to R-1. R-1 is the default gateway of the management system.
Thus – Management system messages are forwarded from R-1 to ER1, ER1 forwards them via LDP tunnel to
ER4. ER4 forwards them to R-4. R-4 uses IGP to send the messages to the correct ME.
7.7.1 Manage BGP instances

To manage BGP instances:
2. In the Configuration working mode, select Protocols > BGP > BGP Instances.

3. To create a BGP instance, click .

The Create BGP Instance window opens.
4. Configure the parameters for the BGP instance.

Following describes some of the attributes:
 Internal Preference: Administrative distance for routes learned from internal BGP (iBGP).
 External Preference: Administrative distance for routes learned from external BGP (eBGP).
 Always Compare Med: Compare multi-exit discriminator (MED) value from different ASes when
selecting the best route. The default behavior is to only compare MEDs for paths received from
the same AS.
 Ignore AS Path Length: Ignore the AS path length when selecting the best path. The default is to
use the AS path length and prefer paths with shorter length.
 Advertise Inactive Routes: Advertise inactive routes to external peers. The default is to only
advertise active routes.
 Graceful Restart Enable: Enable or disable the graceful-restart capability.

 Helper Only: Enable graceful-restart in helper mode only. When this leaf is set, the local system
does not retain forwarding its own state during a restart, but supports procedures for the
receiving speaker.
 State Routes Time(s):An upper-bound on the time that stale routes will be retained by a router
after a session is restarted. If an End-of-RIB (EOR) marker is received prior to this timer expiring
stale-routes will be flushed upon its receipt - if no EOR is received, then when this timer expires
stale paths will be purged.
 Export Policy: List of policy names in sequence to be applied on sending a routing update in the
current context, e.g., for the current peer group, neighbor, address family, etc.
 Default Export Policy: Explicitly set a default policy if no policy definition in the export policy chain
is satisfied.
 IPv4 Unicast: If enabled, set Enabled, Graceful Restart Enable and Advertise Inactive Route.
 L3 VPN IPv4 Unicast: If enabled, set Enabled, Graceful Restart Enable and Advertise Inactive
Route.
5. Click Apply. The BGP instance is saved.
6. To edit a BGP instance, select the instance, then click .
7. To view details of a BGP instance, select the instance, then click .
8. To view the whole BGP instance, select the instance, then click .

The whole information of the BGP instance with its groups and neighbors is displayed:
 View BGP Instance
 View BGP Neighbor Group
 View BGP Neighbor
9. To delete a BGP instance, select the instance, then click .
7.7.2 Manage BGP neighbor groups

To manage BGP neighbor groups:
2. In the Configuration working mode, select Protocols > BGP > BGP Neighbor Groups.
3. To create a BGP neighbor group , click .

The Create BGP Neighbor Group window opens.
4. Configure the parameters for the BGP neighbor group.

 Peer Type: Explicitly designate the peer or peer group as internal (iBGP) or external (eBGP).
 Peer AS: AS number of the peer.
 AS Override: Set as True or not.
 Remove Private AS: Remove private AS numbers from updates sent to peers.

 Community Type: Specify which types of community should be sent to the neighbor or group.
The default is to not send the community attribute
 Route Reflector Client: Configure the neighbor as a route reflector client.
 Authentication Type: Set as None or MD5.
 Authentication Key: Configures an MD5 authentication password for use with neighboring
devices.
 Description: An optional textual description (intended primarily for use with a peer or group).
 Connect Retry: Time interval in seconds between attempts to establish a session with the peer.
 Hold Time: Time interval in seconds that a BGP session will be considered active in the absence
of keepalive or other messages from the peer. The hold-time is typically set to 3x the keepalive-
interval.
 Keep-alive Interval: Time interval in seconds between transmission of keepalive messages to the
neighbor. Typically set to 1/3 the hold-time.
 Min Advertise Interval: Minimum time which must elapse between subsequent UPDATE
messages relating to a common set of NLRI being transmitted to a peer. This timer is referred to
as MinRouteAdvertisementIntervalTimer by RFC 4721 and serves to reduce the number of
UPDATE messages transmitted when a particular set of NLRI exhibit instability.
 AS Loop: Specify the number of occurrences of the local BGP speaker's AS that can occur within
the AS Path before it is rejected.
 Import Policy: List of policy names in sequence to be applied on receiving a routing update in the
 Default Import Policy: Explicitly set a default policy if no policy definition in the import policy
chain is satisfied.
 Export Policy: List of policy names in sequence to be applied on sending a routing update in the
 Default Export Policy: Explicitly set a default policy if no policy definition in the export policy chain
is satisfied.
5. Click Apply. The BGP neighbor group is saved.
6. To edit a BGP neighbor group, select the neighbor group, then click .
7. To view details of a BGP neighbor group, select the neighbor group, then click .
9. To delete a BGP neighbor group, select the neighbor group, then click .

7.7.3 Manage BGP neighbors

To manage BGP neighbors:
2. In the Configuration working mode, select Protocols > BGP > BGP Neighbors.
3. To create a BGP neighbor, click .

The Create BGP Neighbor window opens.
4. Configure the parameters for the BGP neighbor.

5. Click Apply. The BGP neighbor is saved.
6. To edit a BGP neighbor, select the neighbor, then click .
7. To view details of a BGP neighbor, select the neighbor, then click .
9. To delete a BGP neighbor, select the neighbor, then click .

7.7.4 View BGP instance state

To view BGP instance state:
2. In the Configuration working mode, select Protocols > BGP > Instance State.
The BGP instance state information appears.

7.7.5 View BGP neighbor group state

To view BGP group state:
2. In the Configuration working mode, select Protocols > BGP > Group State.
The BGP neighbor group state information appears.

7.7.6 View BGP neighbor state

To view BGP neighbor state:
2. In the Configuration working mode, select Protocols > BGP > Neighbor State.
The BGP neighbor state information appears.

7.7.7 View BGP route in state

To view BGP route in state:
2. In the Configuration working mode, select Protocols > BGP > Route In State.
The BGP route in state information appears.

7.7.8 View BGP route out state

To view BGP route out state:
2. In the Configuration working mode, select Protocols > BGP > Route Out State.
The BGP route out state information appears.

7.7.9 View BGP route local state

To view BGP route local state:
2. In the Configuration working mode, select Protocols > BGP > Route Local State.
The BGP route local state information appears.

7.7.10 View BGP statistics

To view BGP statistics:
2. In the Display area, select the BGP object.

4. Click .


7.8 PIM protocol management in IP/MPLS

Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging static routes or unicast
routing tables generated by any unicast routing protocol, such as OSPF, IS-IS or Border Gateway Protocol
(BGP). Independent of the unicast routing protocols running on the device, multicast routing is operating as
long as the corresponding multicast routing entries built by unicast routes.
PIM uses the reverse path forwarding (RPF) mechanism to implement multicast forwarding. When a multicast
packet arrives on an interface of the device, it is subject to an RPF check. If the RPF check succeeds, the device
creates the corresponding routing entry and forwards the packet; if the RPF check fails, the device discards
the packet.
Based on the implementation mechanism, PIM falls into two modes:
 Protocol Independent Multicast – Dense Mode (PIM-DM)
 Protocol Independent Multicast – Sparse Mode (PIM-SM)
IP/MPLS solution in NPT and Apollo use only on the PIM-SM mode.
PIM-SM: The receivers are sparsely situated, and usage of flood and prune is wastage. Multicast forwarding
path is a "shared based tree". Multicast traffic is forward only to receivers that ask for it via join and prune
messages.
Figure 7-12: IPv4 Multicast Architecture
The following window indicates the PIM application in V6.0.

Figure 7-13: PIM-SM network running on single AS (Intra-AS)

7.8.1 Manage PIM instances

To manage PIM instances:
2. In the Configuration working mode, select Protocols > PIM > Instance.

3. To create a PIM instance, click .

The Create PIM Instance window opens.
4. Configure the parameters for the PIM instance.

 Admin State: Enabled or disabled.
 IPv4 Family: Support Ipv4 routing or not.
 Keepalive Period: The duration of the Keepalive Timer. This is the period during which the PIM
router will maintain (S,G) state in the absence of explicit (S,G) local membership or (S,G) join
messages received to maintain it.
 Register Suppression Time: The duration of the Register Suppression Timer. This is the period
during which a PIM Designated Router (DR) stops sending Register-encapsulated data to the
Rendezvous Point (RP) after receiving a Register-Stop message. This object is used to run timers
both at the DR and at the RP.
 Register Probe Time: The time to wait for a PIM Register-Stop message after sending a PIM Null-
Register message, before resuming Register-encapsulation at a DR.
 Source to ASM Mapping: Mapping source to ASM configuration.
5. Click Apply. The PIM instance is saved.
6. To edit a PIM instance, select the instance, then click .
7. To view details of a PIM instance, select the instance, then click .
9. To delete a PIM instance, select the instance, then click .

7.8.2 Manage PIM interfaces

To manage PIM interfaces:
2. In the Configuration working mode, select Protocols > PIM > Interface.
3. To create a PIM interface, click .

The Create PIM Interfaces window opens.
4. Configure the parameters for the PIM interface.

 Interface Name: Set the interface name.
 IP Version: The IP version of this PIM interface. A physical interface maybe configured in multiple
modes concurrently, e.g., Ipv4 and Ipv6; however, traffic considered as a logically separate, and a
separate row must be configured in this table for each mode.
 Admin State: Enable or disable the admin state.
 DR Priority: The Designated Router Priority value inserted into the DR Priority option in PIM Hello
messages transmitted on this interface. Numerically higher values for this object indicate higher
priorities.
 Elect-DR on PtP: Whether this interface is a point-to-point interface on which we do not require
the neighbor to send PIM-Hello signals. Provided for back-compatibility with some older
implementations that do not send Hellos on point-to-point links. Changing the value of this object
while the interface is operational causes the interface to be de-activated and then reactivated.

 Passive: Whether this interface is a 'stub interface'. If Passive is set to Yes, there is single PIM
router using this interface, then no PIM packets are sent out this interface, and any received PIM
packets are ignored. Setting Passive to Yes is a security measure for interfaces towards untrusted
hosts. This allows an interface to be configured for use with IGMP only, which protects the PIM
router from forged PIM messages on the interface. To communicate with other PIM routers using
this interface, Passive must remain set to False. Changing the value of Passive while the interface
is operational causes PIM to be disabled and then re-enabled on this interface.
 Hello Interval: The frequency at which PIM Hello messages transmitted on this interface. This
object corresponds to the "Hello_Period" timer value defined in PIM-SM specification. A value of
zero represents an 'infinite' interval, and indicates that periodic PIM Hello messages should not
be sent on this interface.
 Trig Hello Interval: The maximum time before this router sends a triggered PIM Hello message on
this interface. This object corresponds to "Trigered_Hello_Delay" timer value defined in the PIM-
SM specification. A value of zero has no special meaning and indicates that triggered PIM Hello
messages should always sent immediately.
 Hello Hold Time: The value set in the Hold-time field of PIM Hello message transmitted on this
interface. A value of 65535 represents an "infinite" hold-time.
 Join Prune Hold Time: The value inserted into the Holdtime field of a PIM Join/Prune message
sent on this interface. A value of 65535 represents an "infinite" holdtime.
 Propagation Delay: The expected propagation delay between PIM routers on this network or link.
This router inserts this value into the Propagation_Delay field of the LAN Prune Delay option in
the PIM Hello messages sent on this interface.
 Override Interval: The value this router inserts into the Override_Interval field of the LAN Prune
Delay option in the PIM Hello messages it sends on this interface. When overriding a prune, PIM
routers pick random timer duration up to the value of this object. The more PIM routers that are
active on a network, the more likely it is that the prune will be overridden after a small proportion
of this time has elapsed.
5. Click Apply. The PIM interface is saved.

6. To choose the required attributes to view:
a. Click in the following window.
b. In the Field Chooser window, select the required attributes to display.
c. To save the changes, click Apply.
7. To edit a PIM interface, select the interface, then click .
8. To view details of a PIM interface, select the interface, then click .
10. To delete a PIM interface, select the interface, then click .

7.8.3 Manage PIM rendezvous points

To manage PIM rendezvous points:
2. In the Configuration working mode, select Protocols > PIM > Rendezvous Points.
3. To create a PIM rendezvous points, click .

The Create PIM Rendezvous Points window opens.
4. Configure the parameters for the PIM rendezvous points.

 RP Type: Set the rendezvous point type as Static RP or Anycast RP.
 Address Type: The address type of this entry.
 Admin State: Static RP administrative status.
 RP IP Address: The IP address of the RP to use for groups within this group prefix. The
InetAddressType is given by the pimStaticRPAddressType object.
 Group Address: The multicast group address that, when combined with
pimStaticRPGrpPrefixLength, gives the group prefix for this entry. The InetAddressType given by
pimStaticRPAddressType object. This address object is only significant up to
pimStaticRPGrpPrefixLength bits. The remainder of the address bits is zero. This is especially
important for this index field, which is part of the index of this entry. Any non-zero bits would
signify an entirely different entry.
5. Click Apply. The PIM rendezvous point is saved.

6. To edit a PIM rendezvous point, select the rendezvous point, then click .
7. To view details of a PIM rendezvous point, select the rendezvous point, then click .
9. To delete a PIM rendezvous point, select the rendezvous point, then click .
7.8.4 View PIM interface status

To view PIM interface status:
2. In the Configuration working mode, select Protocols > PIM > Interface Status.
The PIM interface status information appears.

7.8.5 View PIM join status

To view PIM join status:
2. In the Configuration working mode, select Protocols > PIM > Join Status.
The PIM join status information appears.

7.8.6 View PIM neighbors

To view PIM neighbors:
2. In the Configuration working mode, select Protocols > PIM > Neighbor.
The PIM neighbors information appears.

7.8.7 View PIM RP status

To view PIM RP status:
2. In the Configuration working mode, select Protocols > PIM > RP Status.
The PIM RP status information appears.

7.8.8 View PIM source

To view PIM source:
2. In the Configuration working mode, select Protocols > PIM > Source.
The PIM source information appears.

7.8.9 View PIM statistics

To view PIM statistics:
2. In the Display area, select the PIM object:

 PIM Instance
 PIM LIF
3. Click .


7.9 IGMP protocol management in IP/MPLS

IGMP-aware VSI functionality provides a solution for the delivery of routable IP multicast traffic for IPTV
applications.
The following diagram shows a simple network reference model for IGMP-aware VSI:
This diagram shows an IP/MPLS domain representing a single AS with IGP (IS-IS or OSPF) running on all intra-
AS links.
An MP2MP L2VPN service (VPLS) is set up between some PEs, with full mesh of PWs set up between all VSIs
representing this service in each of the affected NEs using tLDP. An edge multicast router is connected to one
of the PEs of an MP2MP L2VPN (VPLS) service, while multiple subscribers to this content are connected to
some other PEs participating in this VPLS instance via access LANs.
Each subscriber indicates its interest in one or more IPTV channels using IGMPv3 with each IPTV channel
mapped to exactly one SSM Multicast Channel. The VSI representing the VPLS service in question in each of
the affected PEs is marked as IGMP-aware. Its relevant ACs are marked as Upstream or Downstream.
Each PW that connects the VSI that is directly connected to the edge multicast router to a VSI that is directly
connected to a subscriber LAN is treated as an Upstream interface in the former and as a Downstream
interface in the latter.
An IGMP Proxy instance is associated with this VSI and treats its Downstream and Upstream ACs and PWs as
if they were Upstream and Downstream.
When an Ethernet frame is received from the Upstream AC or PW associated to an IGMP-aware VSI, it is
checked for belonging to one of the following traffic types:

 IGMP packets: Identified by Ethertype being IPv4 and IP Protocol number being IGMP. These packets
are trapped to the IGMP Proxy instance for processing.
 Routable IP Multicast packets: Identified by Ethertype being IP, IP protocol being different from IGMP,
and Destination IP address being a routable IP multicast address. These packets undergo normal VPLS
flooding subject to additional filtering based on the contents of the Group Membership DB built by the
corresponding IGMP Proxy instance.
 The rest: These frames receive normal VSI forwarding in accordance with the L2 FIB of the VSI created
by the normal MAC Learning process.
IGMP intends to support primarily IP-TV streams towards subscribers. Using this protocol helps reducing the
bandwidth usage of broadcast streaming.
IP-TV stream is IP multicasting to subscribers. It is the transmission of an IP datagram to a "host group", a set
of zero or more hosts identified by a single IP destination address.
A multicast datagram is delivered to all members of its destination host group with the same "best-efforts"
reliability as regular unicast IP datagrams, i.e., the datagram is not guaranteed to arrive intact at all members
of the destination group or in the same order relative to other datagrams.
The membership of a host group is dynamic; that is, hosts may join and leave groups at any time. There is no
restriction on the location or number of members in a host group. A host may be a member of more than
one group at a time.
A host need not be a member of a group to send datagrams to it.
In V6.0, the platform will use the PIM protocol for IP multicast, to reduce more bandwidth on the network
for the same set of streams.
The main application that uses IGMP is IP-TV broadcasting for paying subscribers. In the source of all TV
stream is IPTV contents server.
Figure 7-14: Typical Application - IPTV Broadcasting

LCT-NPT V6.0 supports two solutions for this application: IGMP-Aware VSI and PIM supported routed
multicast traffic.
IGMP-Aware VSI
The operator configured PW-s, PW Sets or AC-s for passing traffic to each subscriber via IGMP proxy devices.
It means that in only the following PW interfaces IGMP/ multicast traffic enabled:
 From device 1 to device 2 and vice versa
 From device 2 to device 7 via device 5 and vice versa
The following figure shows the IGMP Proxy tasks in the simple tree topology.
Figure 7-15: IGMP-Aware VSI Tree Topology Example
The NPT-proxy presents multicast router to the hosts (subscribers) and host towards the tree root.
Each interface (LIF) is configured explicitly to its IGMP task.
IGMP Proxy has only a single upstream LIF (host interface) and may have multiple downstream interfaces.
These interfaces may AC, PW or PW set. A PW set is considered as a single interface. AC may reside within
MC-LAG.
PIM SM usage for routing multicast groups
The operator configures PIM on the routers in the network. He also enables IGMP on AC-s facing the multicast
traffic subscribers.

The following figure shows an example of the created topology. Two subscribers subscribe to the entire group
traffic while the other two subscribed to source specific traffic. According these, PIM built the described
topology.
Figure 7-16: PIM Topology Example
Traffic of G1 multicast traffic from S2 is forwarded by NPT1 towards a subscriber via NPT2 and towards the
Rendezvous Point (RP)-NPT8.
NPT5 forwards G1 multicast traffic from source S1 towards a subscriber via NPT6 and NPT9 and towards the
RP – NPT8.
RP – NPT8 forwards the G1 traffic from both sources via the shared tree towards a subscriber via NPT4.
RP- NPT8 forwards the G1 traffic from S2 via the shared tree towards a subscriber via NPT9.
The traffic is forwarded natively after phase III of the PIM is completed.
See MPLS MPtMP service for information about enabling IGMP support for an MPtMP service.
See Configure multicast for MPLS RootedMP/Leaf service for information about enabling/disabling IGMP
Snooping in a multicast configuration.

7.9.1 Manage IGMP instances

To manage IGMP instances:
2. In the Configuration working mode, select Protocols > IGMP > Instance.
3. To create an IGMP instance, click .

The Create IGMP Instance window opens.
4. Configure the parameters for the IGMP instance.


 Admin State: Setting this attribute to Disable stops the protocol. Setting it to Enable after it has
been disabled restarts the protocol.
 IGMP Version: Default IGMP version for all IGMP-aware interfaces of the related VSI. Default
IGMP version for all IGMP enabled interfaces of the default routing instance. In V3-SSM, only SSM
is supported and IGMPv2 compatibility mode is disabled. Subscription of router LIF to non-
specific-source of a multicast group will be ignored.
 Query Interval: Interval between Queries, used as default for all router (downstream) interfaces.
 Max Query Response Time: Default Max. Query response time to be transmitted in the IGMP
Queries transmitted via router interfaces.
 Robustness Variable: Used as the default number of specific IGMP Queries for which no Report
has been received prior to deciding to remove the group membership record for the affected
group.
 Last Member Query Interval: Max Response Time to Group-Specific Queries sent in response to
Leave Group messages. It is also the Max Response Time to Group-and-Source- Specific Query
messages. This is the default value used in queries.
5. Click Apply. The IGMP instance is saved.
6. To edit an IGMP instance, select the instance, then click .
7. To view details of an IGMP instance, select the instance, then click .
9. To delete an IGMP instance, select the instance, then click .
7.9.2 Manage IGMP interfaces

To manage IGMP interfaces:
2. In the Configuration working mode, select Protocols > IGMP > Interface.
3. To create an IGMP interface, click .

The Create IGMP Interfaces window opens.
4. Configure the parameters for the IGMP interface.


 Interface Name: The IGMP interface name.
 Admin State: Enables/Disables IGMP on the interface.
 IGMP Version: Current version of IGMP protocol on this VSI interface.
 Query Interval: The frequency at which IGMP Host-Query packets are transmitted on this
interface.
 Max Query Response Time: The maximum query response interval advertised in IGMP queries
on this interface.
 Robustness Variable: The statically configured number of retransmissions. Routers adopt the
robustness value from the most recently received Query as their own [Robustness Variable] value,
unless that most recently received value was zero, in which case the receivers use the statically
configured value.
 Last Member Query Interval: Max Response Time to Group-Specific Queries sent in response to
Leave Group messages. It is also the Max Response Time to Group-and-Source - Specific Query
messages.
 Router Alert Setting Ignore: If set, ignore router alert setting on incoming IGMP messages. Should
be set for certain Cisco routers, According standard if router alert clear, IGMP message should be
discarded. By default, NPT will behave according standard.
5. Click Apply. The IGMP interface is saved.
6. TTo edit an IGMP interface, select the interface, then click .
7. To view details of an IGMP interface, select the interface, then click .
9. To delete an IGMP interface, select the interface, then click .

7.9.3 Manage IGMP static database

To manage IGMP static database:
2. In the Configuration working mode, select Protocols > IGMP > Static Database.
3. To create an IGMP static database, click .

The Create IGMP Static Database window opens.
4. Configure the parameters for the IGMP static database.

 Group Address: From SSM range for source specific groups. From 224.0.1.0 to 239.255.255.255
for non-specific multicast group.
 Source Address: The host address that originates this record multicast traffic. IP address 0.0.0.0
represents a group membership database record for a non-source-specific multicast group.
 Interface Name: Set the IGMP interface name.
5. Click Apply. The IGMP static database is saved.
6. To edit an IGMP static database, select the static database, then click .
7. To view details of an IGMP static database, select the static database, then click .
9. To delete an IGMP static database, select the static database, then click .

7.9.4 View IGMP instance status

To view IGMP instance status:
2. In the Configuration working mode, select Protocols > IGMP > Instance Status.
The IGMP instance status information appears.

7.9.5 View IGMP interface status

To view IGMP interface status:
2. In the Configuration working mode, select Protocols > IGMP > Interface Status.
The IGMP interface status information appears.

7.9.6 View IGMP group status

To view IGMP group status:
2. In the Configuration working mode, select Protocols > IGMP > Group Status.
The IGMP group status information appears.

7.9.7 View IGMP statistics

To view IGMP statistics:
2. In the Display area, select the IGMP object:

 IGMP Aware (Downstream)
 IGMP LIF
 IGMP Aware (Upstream)
3. Click .


7.9.8 View group membership database records

To view group membership database records:
2. In the Services working mode, select VSI List.
3. Select an existing MPtMP service and click View VSI detail .
4. Select Group Membership Database Records.
The group membership database records appear.
5. You can filter the records by origin, VSI, port/remote PE, and/or group address.

7.10 DHCP protocol management in IP/MPLS

DHCP Relay Agent
The L3VPN allows to use the provider network in order to provide VPN ser-vices to the customer, or another,
smaller, provider in the case of carrier of carriers - these are layer 3 VPN services. The client perceives the
VPN as one logical router (even if physically distributed), same as L2VPN is perceived by a client as a switch.
The devices (CEs) connected on the customers side to the IP interfaces of the L3VPN, are IP capable devices
which, more often than not, rely on DHCP protocol in order to get their IP address and other configuration.
Since the NPT is not acting as DHCP Server by itself, it must allow the client to bootstrap itself using DHCP by
relaying the clients DHCP requests to the DHCP server and sending the DHCP replies back to the client.
Figure 7-17: Basic L3VPN Topology
DHCP Snooping Agent

LCT-NPT supports DHCP snooping in order to enhance the L2-VPN security by performing Dynamic ARP
Inspection:
 NPT traps all DHCP packets passing through the VSI to the DHCP snooping agent.
 The agent learns assignment of IP addresses to MAC-s.
 The agent ignores server DHCP packets from untrusted interfaces.
 The agent stores also lease expiration time.
 The agent updates the filtering database.
 The agent requests the data-plane to forward the DHCP packets to their original destinations.
DHCP Relay Agent Applications

There are two major applications for the DHCP Relay Agent which are depicted in the following three figures.
In both application the NPT is used for as a DHCP Relay agent in order to mediate between a DHCP client, an
IP host which wants to receive or renew its IP configuration, and a remote DHCP Server, or several servers,
which should allocate or renew the IP configuration. In the first application (the first and second figure), the
DHCP Client is connected to a L3VPN (non-default VRF), while in the second application (the third figure), the
DHCP client is a set-top-box used for IPTV and connected to the global/default VRF.
Figure 7-18: Another Example of DHCP Relay Agent in L3VPN

Figure 7-19: DHCP Relay Agent in IPTV (IGMP+PIM MC Solution) Application
DHCP Snooping Applications

Current planned DHCP snooping scope is limited to of Dynamic ARP Inspection (DAI) support. DHCP snooper
builds its own (interface, IP address) to MAC address mapping table (Binding Table) and passes the table to
the ARP filtering mechanism.
7.10.1 Manage DHCP relay agent

DHCP relay agent is supported with the following interfaces families:
 IPv4 IP interface with inet family (may be PHT interfaces)
 (Future) IPv6 IP interface with inet6 family.
DHCP relay agent is supported with the numbered IP interfaces only and is not supported on loopback LIFs,
tunnel LIFs or IRB LIFs.
DHCP relay agent is supported with the following routing instances:
 Global/Master routing instance (VRF0),
 Any other non-default VRF.
DHCP relay agent support is required on VRF0 in order to bootstrap the set top boxes which are used in the
IPTV application. LCT-NPT can support one DHCP relay agent per IP interface, and up to 1000 DHCP relay
agents per NE, and support two DHCP servers per DHCP relay agent.

To manage DHCP relay agent:

2. In the Configuration working mode, select Protocols > DHCP > DHCP Relay Agent.
3. To create a DHCP relay agent, click .

The Create DHCP Relay Agent window opens.
4. Configure the parameters for the DHCP relay agent.


 VRF: Select a VRF for the DHCP relay agent.

 LIF Name: Select a numbered IP interfaces.
 DHCP Server1/DHCP Server2: Valid IPv4 address of DHCP Server.
 Max Hops: Max allowed value in the "hops" field. Arriving messages with higher value in the
"hops" field will be discarded.
 Circuit ID: Enable/disable inserting Circuit ID in the communication between the Relay Agent and
the DHCP servers. If enabled, DHCP Relay Agent will insert the Circuit ID sub-option in the DHCP
option.
 Remote ID: Enable/disable inserting Remote ID in the communication between the Relay Agent
and the DHCP servers. If enabled, DHCP Relay Agent will insert the Remote ID sub-option in the
DHCP option.
 VSS: Enable/disable inserting VSS in the communication be-tween the Relay Agent and the DHCP
servers. If enabled, DHCP Relay Agent will insert the VSS sub-option in the DHCP option.
 VPN ID: ASCII string identifying the VPN for VSS aware DHCP servers, which is the same for all LIFs
of a VRF/VPN (for NE/NMS respectively). The attribute is valid only when VSS is enabled.
5. Click Apply. The DHCP relay agent is saved.
6. To edit a DHCP relay agent, select the DHCP relay agent, then click .
7. To view details of a DHCP relay agent, select the DHCP relay agent, then click .
8. To delete a DHCP relay agent, select the DHCP relay agent, then click .

7.10.2 View DHCP statistics

To view DHCP statistics:
2. In the Display area, select the IGMP object:

 DHCP Relay Agent
 DHCP Snooping Interfaces
3. Click .


7.11 BFD protocol management in IP/MPLS

This section describes how to manage BFD in IP/MPLS.
7.11.1 Configure BFD protocol

To configure BFD protocol:
2. In the Configuration working mode, select Protocols > BFD > BFD Protocol.
3. Set the Admin State as enabled or disabled as required (default is enabled).

4. Set the Minimum Receive Interval, Minimum Transmit Interval, and Multiplier.
5. Click Apply. The changes are saved.

7.11.2 Manage BFD section sessions

To manage BFD section sessions:
2. In the Configuration working mode, select Protocols > BFD > BFD Section Sessions.
3. To create a BFD section session, click .

The Create BFD Section Session window opens.
4. Set the attributes as required.

5. Click Apply.
The BFD section session is saved.
6. To edit a BFD section session, select a BFD section session in the list, then click .
7. To view a BFD section session, select a BFD section session in the list, then click .
8. To delete a BFD section session, select a BFD section session in the list, then click .
9. To synchronize the BFD section sessions, then click .

7.11.3 Manage IP BFD sessions

To manage IP BFD sessions:
2. In the Configuration working mode, select Protocols > BFD > IP BFD Session.
3. To create an IP BFD session, click .

The Create IP BFD Session window opens.

 LIF: Select the LIF for the BFD session.
 Remote IP: Remote IP address of the next hop for the BFD session.
 Admin State: Enables/disables the BFD session.
 Minimum Receive Interval: The minimum RX interval that can be supported by the session.
 Minimum Transmit Interval: The minimum TX interval that can be supported by the session.
 Multiplier: Used for detection time calculation.
5. To edit an IP BFD session, select it from the list and click .
6. To view details of an IP BFD session, select it from the list and click .
7. To delete an IP BFD session, select the instance, then click .

7.11.4 View multihop IP BFD protocol

To view multihop IP BFD protocol:
2. In the Configuration working mode, select Protocols > BFD > Multihop IP BFD Protocol.

7.11.5 Manage multihop IP BFD sessions

To manage multihop IP BFD sessions:
2. In the Configuration working mode, select Protocols > BFD > Multihop IP BFD Session.
3. To create a multihop IP BFD sessions, click .

The Create Multihop IP BFD Session window opens.

 VRF Name: VRF to which an IP BFD session is locally scoped.
 Local IP Address: Local IP address of an IP BFD session.
 For an single hop IP BFD session it is derived from IP address of the interface.
 For a multi-hop IP BFD session is explicitly configured and MUST be owned by the network
element.
 Remote IP: Remote IP address of the next hop for the BFD session.
 Admin State: Enables/disables the BFD session.
 Minimum Receive Interval: The minimum RX interval that can be supported by the session.
 Minimum Transmit Interval: The minimum TX interval that can be supported by the session.
 Multiplier: Used for detection time calculation.
5. To edit a multihop IP BFD sessions, select it from the list and click .
6. To view details of a multihop IP BFD sessions, select it from the list and click .
7. To delete a multihop IP BFD sessions, select the instance, then click .

7.11.6 View BFD status

To view the BFD status:
2. In the Configuration working mode, select Protocols > BFD > BFD Status.
3. In the Filter area, select the required BFD type to view.
4. To refresh the BFD status, click .

7.11.7 View BFD statistics

To view BFD statistics:
2. In the Display area, select one of the BFD object.

4. Click .

7.11.8 Manage BD-LSP BFD

You can configure BD-LSP BFD when creating MPLS TP tunnels.

To configure BD-LSP BFD:

1. The following window shows the PW BFD attributes in the MPLS TP tunnel:
2. Select the checkbox to enable BFD.

3. Configure the PW BFD parameters as required.

7.11.9 Configure PW BFD

You can configure PW BFD when creating VSIs with PW. The same set of PW BFD attributes are configured
for MPtMP VSI and MS-PW services. The following window shows the PW BFD attributes in the MPtMP
service:

To configure PW BFD:
 Select the BFD Enable checkbox for a specific service and then you can configure the parameters for
BFD as required.
7.12 Manage the slow path

This section describes how to manage the slow path, which includes creating, configuring the slow path and
view the state of slow path.
7.12.1 Configure the slow path

To perform slow path configuration:
2. In the Configuration working mode, select Slow Path > Configuration.
3. To create a slow path, click .

The Create Slow Path window opens.
4. Set the Queue Priority and Type as required.

5. In the Slow Path Policer Profile dropdown list, select a slow path policer profile.

6. To show type details, click Show Type Details.

You can view descriptions of each type through this window. The same type cannot be re-created.
7. Click Apply.
The slow path is created.
8. To edit a slow path, select the required slow path, then click .
9. To view details of a slow path, select the required slow path, then click .
10. To synchronize the data between NE and database, click .
11. To delete a slow path, select the required slow path, then click .

7.12.2 View the slow path state

To view the slow path state:
2. In the Configuration working mode, select Slow Path > State.
3. To refresh the state to view, click .

7.13 View resource budgets

To view resource budgets:
2. In the Configuration working mode, select Resource Budgets.
3. To refresh the resources list, click .
7.14 Configure IP/MPLS connection settings

This section describes how to configure NE communication parameters for IP/MPLS.
There are four parts of IP/MPLS NE communication settings:
 Define Management IP
 Mng Interface
 AUX Interface
 Alarm Server

To configure IP/MPLS NE connection settings:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE.
2. From the menu, select the Configuration > NE Connection Settings.
The NE Communication window opens.
3. In the Define Management IP tab:
a. Set the IP address for the address type Inet; choose either Select from LIF or Other IP.
b. If Select from LIF is selected, you can select all the LIF of Inet4 or Inet6 (future), including loopback
interfaces. Note that Inet4 must be numbered.
c. Click Apply.

4. In the Mng Interface tab, only one Mng interface is supported.

a. To add an Mng interface, click the Add button.
b. Set the parameters for the Mng interface as required.
Note that the value of MTU cannot be larger than the MTU value defined in L3 MTU Profile.
c. Click Apply.
The Mng interface is saved.
d. To delete a created Mng interface, click .

5. In the Aux Interface tab, only one Aux interface is supported.
a. To add an Aux interface, click the Add button.
b. Set the parameters for the Aux interface as required.
Note that the value of MTU cannot be larger than the MTU value defined in L3 MTU Profile.
c. Click Apply. The Aux interface is saved.

d. To delete a created Aux interface, click .

6. In the Alarm Server tab:
a. To add an alarm server, set the Server Name and IP Address as required.
The server name and IP address should be unique.
b. Click Add. The alarm server is added into the server list.
c. Click Apply.
7.15 Perform interface management

Figure 7-20: Interface, Logical interface and Address Families

 Port
 Port object mainly includes attributes of L1 (physical layer)
 A LAG may include a group of port members.
 Interface
 An interface object may be over a port or a LAG
 We will use interface ID of the master port in a LAG to identify the interface for LAG
 Interface Mode
 Non-channelized
 Vlan-tagged
 E-NNI
 I-NNI
 LIF
 A Logical Interface is either a L2 or a L3 interface.
 L3 LIFs are: RIF of VRFs , or MPLS LIF
 L2 LIFs are interfaces of VSIs
 LIF over NE level
 Loopback interface
 Tunnel interface
 PW interface
 LIF over interface level
 Up to one L2 LIF and/or one L3 LIF over a non-channelized interface
 Up to one L2 LIF and/or one L3 LIF over an I-NNI interface
 Multiple L2 LIFs and/or multiple L3 LIFs over Vlan-tagged or E-NNI interface, LIFs are
identified by outer VLAN ID.
 LIF families
 L2 Family – L2 AC
 L3 Families – IP and MPLS
 Each such family deals with a specific group of Ethertypes
 Multiple L3 Families may be combined on the same LIF
 Well-known L3 families:
 Inet (IPv4 and ARP Ethertypes)
 Inet6 (IPv6 Ethertype)
 MPLS (Downstream and upstream-allocated labels)
 ISO (for IS-IS only)

7.15.1 Perform ETY interface configuration

The following steps explain how to configure the interface over an Ethernet port:
1. Activate the Ethernet port;
2. Create a LAG object;
3. Create an "Interface" for the selected port or the master port of a LAG;
 For CLI, Interface is created by user explicitly;
 For EMS, Interface is created by EMS implicitly during port activation;
 The name and ifIndex of an interface can be viewed from both EMS and CLI after the interface
creation:
 The interface name is unique, and as a key used by other service and protocols;
 The ifIndex is unique (assigned by NE automatically), and as a key for SNMP/Netconf
application.
4. Set the "Interface Mode":
 Non-channelized (the default mode)
 VLAN-tagged
 E-NNI
 I-NNI
Note that Transition between modes is not allowed if logical interfaces exist on top of the Interface.
5. Ingress untagged/priority tagged frame handling for interface which might be used by legacy UNI AC
(for VLAN-tagged interface mode only):
 Untagged frame handling, forward by default
 Priority tagged frame handling, forward by default
 Port-based VLAN ID for untagged frame or priority frame
 Default priority for untagged frame, 0 by default
6. TM configuration per interface;
7. MAC filtering enable for L2CP frames, disable by default;
8. Firewall filtering configuration;
9. TPID configuration;
10. MTU configuration;
11. DEI bit remarking configuration for E-NNI/I-NNI interface;
12. Enable/Configure port level protocols if required, such as:
 IEEE 802.1x
 Link OAM
 Section BFD
 LACP

13. Enable/Configure interface level protocols if required, such as

 LLCF
Note that for the typical interface creation over a port, only the step [1] and [3.a] are mandatory. All the
other configurations are optional.
To perform ETY interface configuration:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select an ETY port.
2. In the Configuration working mode, select the Interface tab.
3. Configure the parameters for the ETY interface as required.

4. Click Apply to save the settings.

7.15.2 Create the LIF

LIF over Ethernet interface – L2 address family (UNI/E-NNI AC)
1. Define the unit number over the selected interface (not required by NMS user);
 LIF name is "<interface name>#<unit number>"
2. Configure the LIF classification:
 For UNI AC LIF over Vlan-tagged interface, select either
 Vlan ID
 Untagged
 Vlan list
 For UNI AC LIF over Non-channelized interface, no need to configure the classification, the whole
interface will be used by only one AC LIF;
 For E-NNI AC LIF, select one S-VLAN ID;
3. Set the address family (L2-transport or vpls);
4. Configure CoS mapping per AC LIF:
 Ingress 802.1p bits to internal CoS
 Ingress DSCP bits to internal CoS
5. Configure policers per AC LIF;
6. Add the AC LIF to a service;
 An AC LIF must be associated with a service;
 AC LIF is created implicitly as part of service configuration via EMS/NMS, rather than explicitly via
the CLI;
7. The name and ifIndex of LIF can be viewed from both EMS and CLI:
 The LIF name is unique, and as a key used by other service and protocols;
 The ifIndex of LIF is unique, and as a key for SNMP/Netconf application;
8. Firewall filtering configuration per LIF;
9. MTU configuration per LIF family (only one address family for the AC LIF).
NOTE: For the L2 LIF:

 L2 LIF cannot be created in EMS, but it exist in CLI;
 L2 LIF is created when VSI configured;
 L2 LIF is not displayed in the EMS NE-Tree.
LIF over Ethernet interface – L3 address families

11. A L3 LIF can be created explicitly via CLI/EMS/NMS;

12. Configure the LIF classification:

 For L3 LIF over Vlan-tagged interface, select a VLAN ID;
 For L3 LIF over Non-channelized interface, no need to configure the classification, the whole
interface will be used by one L3 LIF.
13. Set the address families (MPLS, INET, ISO), each L3 LIF can have multiple address families;
 Configure EXP mapping for MPLS LIF
 Configure IP address for INET LIF
 Configure ARP for INET LIF
14. Associate the inet LIF with a specific VRF, only VRF0 is supported in V5;
15. The name and ifIndex of LIF can be viewed from both EMS and CLI;
 The LIF name is unique, and as a key used by other service and protocols
 The ifIndex of LIF is unique, and as a key for SNMP/Netconf application
16. Firewall filtering configuration per LIF;
17. MTU configuration per LIF family;
18. Enable protocols over the L3 LIF;
 OSPF or IS-IS
 LDP
19. LIF disable/enable.
LIF over CES interface – AC for CES
 Only unit 0 supported per CES interface in LCT-NPT V5
21. Set the address family (L2-transport or vpls);
22. Add the AC LIF to a service;
 An AC LIF must be associated with a service
 AC LIF is created implicitly as part of service configuration via EMS/NMS, rather than explicitly via
the CLI
23. The name and ifIndex of LIF can be viewed from both EMS and CLI;
 The LIF name is unique, and as a key used by other service and protocols
 The ifIndex of LIF is unique, and as a key for SNMP/Netconf application
24. MTU configuration per LIF family (only one address family for the AC LIF).

To create the LIF:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select an ETY port.
2. In the Configuration working mode, select the Interface tab.
Configure the UI type for the ETY interface as required:

 I-NNI: cannot create LIF.
 E-NNI: can create one LIF. The E-NNI port cannot support MPLS LIF.
 VLAN-Tagged: can create multi LIFs, with the parameter VLAN ID.
 Unchannelized: can create one LIF.
3. In the left object tree, right-click the ETY port.

4. From the shortcut menu, select Create Logical Interface.

The Create Logical Interface window opens.
Configure the parameters for the LIF as required:

 Unit: set a unit number as required. The created LIF name is "<interface name>#<unit number>".
 VLAN ID: set a VLAN ID as required. VLAN ID is only available for VLAN-Tagged interfaces.
 Families:
 MPLS: can be enabled/disabled. MPLS LIF cannot be created when Switching Mode is PB.
 INET: can be enabled/disabled. If MPLS family is not enabled, INET family must be enabled.
When INET is enabled, set IP Address/Mask as required. If it is set as Unnumbered, you
must select an Unnumbered Source LIF from the dropdown list.
 ISO: International Standards Organization. It can be enabled/disabled.

5. Click Create.
The LIF is created. You can view the created LIF from the left object tree.

7.15.3 Configure the LIF

LIF is a unit under the interface. You can configure the parameters of the created LIF as described in this
section.
To perform LIF configuration:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select a LIF that has been created under
an ETY port.
3. Configure the LIF parameters as required.

Note that the value of MTU cannot be larger than the value defined in MTU Profile.
4. Click Apply.
The changes are saved.

7.15.4 Delete the LIF

To delete the LIF:
1. In the IP/MPLS NE Shelf View window, in the left object tree, right-click the LIF you want to delete.
2. From the shortcut menu, click Delete Logical Interface.
7.15.5 Manage INET LIF ARP entries

To manage INET LIF ARP entries:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select a LIF.
2. In the Configuration working mode, select the Static ARP Entries tab.
3. Set IP Address and MAC Address for the static ARP entry.
The MAC address only supports unicast address.
4. Click Add or Delete to add/remove a static ARP entry.

7.16 Create a LAG with LIFs

The following describes the steps of how to add the port carrying LIFs and services to a LAG:
1. In the following figure, there is a non-LAG port carrying LIFs and services;
2. Create a LAG object;

3. Add the port carrying LIFs and services to the LAG as the master port. Note that only the port that
becomes the master can carry LIFs.
4. Add the slave ports to the LAG.
This section describes how to create a LAG with LIFs. For the other management of the LAG, including LAG
configuration/editing/deleting and MC-LAG are the same as MSPP NEs.
To create a LAG with LIFs:

1. In the IP/MPLS NE Shelf View window, in the left object tree, right-click the CS module.
2. From the shortcut menu, click Create LAG.
The Create Aggregation window opens.
3. Create the LAG:
a. Enter a name for the LAG;
b. Add the port carrying LIFs and services to the LAG as the master port;
c. Add the slave ports to the LAG;
d. Set the other parameters for the LAG and the selected ports as required.

4. Click Create.
The LAG is created and you can view the created LAG in the left object tree.
7.17 Configure DiffServ block

DiffServ block configuration is supported for Ethernet ports (GE port/10GE port). It is not supported for the
LAG slave port.
To perform DiffServ block configuration:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the ETY port.
2. In the Configuration working mode, select the DiffServ Block tab.
3. Configure the parameters as required.

4. Click Apply.

7.18 Configure FRR block

FRR block configuration is supported for Ethernet ports (GE port/10GE port). It is not supported for the LAG
slave port.
To perform FRR block configuration:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the ETY port.
2. In the Configuration working mode, select the FRR Block tab.
3. Configure the parameters as required.
4. Click Apply.
7.19 Manage MSTP

This section describes how to manage MSTP in NTP-1800, including:
 Configure MSTP settings
 Manage MSTP interfaces
 Manage MSTP instance
7.19.1 Configure MSTP settings

To configure MSTP settings:
2. In the Configuration working mode, click Protocols > MSTP > MSTP.

3. In the MSTP Configuration area, set the following parameters:

 Protocol Enable: Enable or Disable (default is Enable).
 Region Name: Name of region.
 Revision Level: Default is 0.
 Forward Delay: How long each listening and learning state lasts before the port begins
forwarding.
 Hello Time: How often the network device broadcasts hello messages to other network devices.
 Max Age: Amount of time protocol information received on a port stored by the network device.

4. To add a new instance:
a. Click in the MSTP Instances area.

The Add MSTP Instance window opens.
b. Set the Instance number, S-VLAN, and Priority as required.

5. To edit an instance:
a. Select the instance in the MSTP Instance list.
b. Click .
The Edit MSTP Instance window opens.
c. Modify the Priority as required.
6. To delete a selected instance, click .

7. To send the settings to the equipment and the DB, click Apply.

7.19.2 Manage MSTP interfaces

To configure MSTP interfaces:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select CS module.
2. In the Configuration working mode, click Protocols > MSTP > MSTP Interfaces.
3. To create the MSTP interface, click .

The Create MSTP Interface window opens.
4. In the left port list, select required port(s).

5. In the MSTP Interface Properties area, configure the parameters for the interface.
6. Click Apply.
The MSTP interface is created and saved in the MSTP Interfaces list.
7. To delete the MSTP interface, select the MSTP interface you want to delete, click .
8. To synchronize the data between NE and database, click .

7.19.3 Manage MSTP instance

To manage MSTP instance:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select CS module.
2. In the Configuration working mode, click Protocols > MSTP > MSTP Instance.
Each port is added in Instance 0.
3. To retrieve the information to view, click .

4. To send the MSTP settings to the equipment and the DB, click Apply.

7.20 Configure port mirroring

To configure port mirroring:
2. In the Maintenance working mode, select the Port Mirror tab.
3. To create the port mirroring, click .

The Define Port Mirroring window opens.
Configure the parameters:

 Enter a name for the instance;
 Select a source port from the Source Port dropdown list;
 Mirror Egress/Ingress traffic to destination ports.
4. Click Apply.
The port mirroring is saved.
5. To remove the port mirroring, select it in the list, and click .

7.21 Manage profiles

This section describes how to create and manage profiles in IP/MPLS NE.
TIP: Most of the following profiles are configured for the CS module. These profiles are
managed through the Profiles management tab, within which different parameter values are
defined for each profile. The procedure steps for managing these profiles are therefore almost
identical, differing only in the specific parameter fields that are relevant for each profile. The
Alarm and PM profiles are managed through different window tabs.
7.21.1 Create VLAN ID range profiles

To create VLAN ID range profiles:
2. In the Configuration working mode, select the Profiles tab.
3. In the left area, select VLAN ID Range Profile.
4. To create a new VLAN ID Range profile, click .

The Create Profile - VLAN ID Range Profile window opens.

5. Configure the parameters for the profile as required.

6. Click Apply.
The profile is saved in the list.
7.21.2 Create vFIB quota profiles

To create vFIB quota profiles:
3. In the left area, select vFIB Quota Profile.
4. To create a new vFIB quota profile, click .

The Create Profile - vFIB Quota Profile window opens.

6. Click Apply.

7.21.3 Create port TPID profiles

To create port TPID profiles:
3. In the left area, select Port TPID Profile.
4. To create a new port TPID profile, click .

The Create Profile - Port TPID Profile window opens.

6. Click Apply.

7.21.4 Create TPID profiles

To create TPID profiles:
3. In the left area, select TPID Profile.
4. To create a new TPID profile, click .

The Create Profile - TPID Profile window opens.

6. Click Apply.
7.21.5 Create MTU profiles

To create MTU profiles:
3. In the left area, select MTU Profile.
4. To create a new MTU profile, click .

The Create Profile - MTU Profile window opens.


6. Click Apply.
7.21.6 Create CoS group profiles

To create CoS group profiles:
3. In the left area, select CoS Group Profile.
4. To create a new CoS group profile, click .

The Create Profile - CoS Group Profile window opens.

6. Click Apply.

7.21.7 Create QoS group profiles

To create QoS profiles:
3. In the left area, select QoS Group Profile.
4. To create a new QoS group profile, click .

The Create Profile - QoS Profile window opens.
5. Configure the parameters for the profile as required. Select the appropriate profiles from the
corresponding dropdown list.
6. Click Apply.

7.21.7.1 Create DSCP to CoS-Color mapping profiles

To create DSCP to CoS-Color mapping profiles:
3. In the left area, expand QoS Profile and then select DSCP to CoS-Color Mapping Profile.
4. To create a new DSCP to CoS-Color mapping profile, click .

The Create Profile - DSCP to CoS-Color Mapping Profile window opens.

6. Click Apply.

7.21.7.2 Create Priority to CoS profiles

To create Priority to CoS profiles:
3. In the left area, expand QoS Profile and then select Priority to CoS Profile.
4. To create a new Priority to CoS mapping profile, click .

The Create Profile - Priority to CoS Mapping Profile window opens.

6. Click Apply.

7.21.7.3 Create CoS to Priority profiles

To create CoS to Priority profiles:
3. In the left area, expand QoS Profile and then select CoS to Priority Profile.
4. To create a new CoS to Priority Mapping profile, click .

The Create Profile - CoS to Priority Mapping Profile window opens.

6. Click Apply.

7.21.7.4 Create EXP to CoS-Color profiles

To create EXP to CoS-Color profiles:
3. In the left area, expand QoS Profile and then select EXP to CoS-Color Profile.
4. To create a new EXP to CoS-Color mapping profile, click .

The Create Profile - EXP to CoS-Color Mapping Profile window opens.

6. Click Apply.

7.21.7.5 Create CoS-Color to EXP profiles

To create CoS-Color to EXP profiles:
3. In the left area, expand QoS Profile and then select CoS-Color to EXP Profile.
4. To create a new CoS-Color to EXP mapping profile, click .

The Create Profile - CoS-Color to EXP Mapping Profile window opens.

6. Click Apply.

7.21.8 Create BSC policer profiles

To create BSC policer profiles:
3. In the left area, select BSC Policer Profile.
4. To create a new BSC Policer profile, click .

The Create Profile - BSC Policer Profile window opens.

6. Click Apply.

7.21.9 Create Policer profiles

To create policer profiles:
3. In the left area, select Policer Profile.
4. To create a new Policer profile, click .

The Create Policer Profile window opens.
5. Configure the parameters for the profile as required:

 CIR: Committed Information Rate.
 CBS: Committed Burst Size.
 EIR: Excess Information Rate.
 EBS: Excess Burst Size.
 Color Mode: Whether the color of ingress packet will be ignored (Color Blind) or not (Color
Aware).
 Coupling Flag: Has negligible effect in color-blind mode. Determine whether the yellow packet
can use the idle token in green bucket.
6. Click Apply.

7.21.10 Create WRED profiles

To create WRED profiles:
3. In the left area, select WRED Profile.
4. To create a new WRED profile, click .

The Create User-Defined WRED Profile window opens.

6. Click Apply.

7.21.11 Create Firewall profiles

To create firewall profiles:
3. In the left area, select Firewall Profile.
4. To create a new firewall profile, click .

The Create Firewall Profile window opens.

5. To create firewall profile terms:
a. Click .
The Create Firewall Profile Term window opens.
b. Enter a name for the term.

c. In the Action tab window, set Type, CoS, Color, Count and Policing Profile for the ACL Rule as
required.

d. In the Match Conditions tab window:
i. In the MAC List tab, set Source Mac and Destination Mac settings as required.
ii. Click the Ethertype tab and enter an Ethertype or select an Ethertype Item. Click Add.
iii. Click the Inner Ethertype tab and enter an inner Ethertype or select an inner Ethertype item.
Click Add.
iv. Click the CoS tab and select a CoS value from the dropdown list.
v. Click the Instance tab and select a instance from the dropdown list.

vi. Click Apply.

The term is saved in the Firewall Profile list.
6. Enter a name for the Firewall profile.

7. Select Basic or Extended for the type.
8. Select L2 or Inet (L3 IPv4) for the family.
9. Deselect Implicit Discard Enable if required.
10. Click Apply.

7.21.12 Create Flow Block profiles

To create Flow Block profiles:
3. In the left area, select Flow Block Profile.
4. To create a new Flow Block profile, click .

The Create Flow Block Profile window opens.

6. Click Apply.

7.21.13 Create Slow Path policer profiles

To create Slow Path policer profiles:
3. In the left area, select Slow Path Policer Profile.
4. To create a new Slow Path policer profile, click .

The Create Profile - Slow Path Policer Profile window opens.

6. Click Apply.
7.21.14 Create Sampling profiles

To create Sampling profiles:
3. In the left area, select Sampling Profile.
4. To create a new Sampling profile, click .

The Create Sampling Profile window opens.

6. Click Apply.
7.21.15 Create PM defects profiles

For a SDH NE, you can manage the following PM defects profiles:
 STM Defects Profile
 VC4 Defects Profile
 VC12 Defects Profile
 E1 Defects Profile
 E1 PPI Defects Profile
 CES Defects Profile
 Ethernet Port Defects Profile
 Interface Defects Profile
 Switch Defects Profile
 VPN Defects Profile
 LIF Defects Profile
 OTU Defects Profile
 ODU Defects Profile
 Tunnel Defects Profile
For a SONET NE, the following defects profiles can be managed:
 OC Defects Profile
 STS1 Defects Profile
 VT-15 Defects Profile
 DS1 Path Defects Profile
 DS1 Line Defects Profile
 CES Defects Profile
 Ethernet Port Defects Profile
 Interface Defects Profile
 Switch Defects Profile
 VPN Defects Profile
 LIF Defects Profile
 OTU Defects Profile
 ODU Defects Profile
 Tunnel Defects Profile

This section describes how to create the E1 defects profile in LCT-NPT. You can use the same steps to manage
the other defects profile.
To create E1 defects profiles:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the IP/MPLS NE.
2. In the Performance working mode, select Performance Settings.
3. Select the PM Profiles tab.
4. In the left area, select E1 Defects Profile.

5. To create a new E1 defects profile, click .

The Create E1 Defects Profile window opens.
6. Set the attributes for the profile in the corresponding fields.

7. Click Apply.
7.21.16 Create alarm profiles

For an SDH NE, you can manage the following alarm profiles:
 MCP alarm profile
 Card alarm profile
 TMU alarm profile
 PTP-TMU alarm profile
 L2-Ethernet-Port profile
 ODUK alarm profile
 OTUK alarm profile
 STM alarm profile

 VC-4 alarm profile

 VC-12 alarm profile
 E1 alarm profile
 E1-PPI alarm profile
 CES-Service alarm profile
 LAG alarm profile
 Switch alarm profile
 LIF alarm profile
 Interface alarm profile
 Tunnel alarm profile
 VPN alarm profile
 MA alarm profile
 PW alarm profile
 ISIS alarm profile
 OSPF alarm profile
 LDP alarm profile
 BGP alarm profile
 VRRP alarm profile
 VRF alarm profile
 EDFA alarm profile
 PIM alarm profile
For a SONET NE, you can manage the following alarm profiles:
 MCP alarm profile
 Card alarm profile
 TMU alarm profile
 PTP-TMU alarm profile
 L2-Ethernet-Port Profile
 ODUK alarm profile
 OTUK alarm profile
 OC alarm profile
 STS-1 alarm profile
 VT-15 alarm profile
 DS1-Path alarm profile
 CES-Service alarm profile
 DS1-Line alarm profile

 LAG alarm profile

 Switch alarm profile
 LIF alarm profile
 Interface alarm profile
 Tunnel alarm profile
 VPN alarm profile
 MA alarm profile
 PW alarm profile
 ISIS alarm profile
 OSPF alarm profile
 LDP alarm profile
 BGP alarm profile
 VRRP alarm profile
 VRF alarm profile
 EDFA alarm profile
 PIM alarm profile
This section describes how to create the MCP alarm profile in LCT-NPT. You can use the same steps to manage
the other alarm profiles.
To create MCP alarm profiles:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the IP/MPLS NE.
2. In the Fault working mode, select Fault Settings.
3. Select the Alarm Profile tab.
4. In the left area, select MCP.

5. To create a new MCP alarm profile, click .

The Create MCP Alarm Profile window opens.
6. Set the attributes for the profile in the corresponding fields.

7. Click Apply.
7.21.17 Manage profiles in the profile list

In the profile list, you can:
 Edit a profile
 View a profile
 Delete profiles
 Export profiles
 Import profiles
 Synchronize the profile data between NE equipment and database

To manage profiles in the profile list:

3. Select a profile in the profile list.
4. To edit a profile:
a. Select the profile in the list and click .

The Edit Profile window opens, displaying the parameters relevant for the selected profile.
b. Modify the parameters as required.
c. Click Apply.
5. To view details of a profile, click .

The View Profile window opens, displaying the parameters relevant for the selected profile.

6. To export profiles to an XML file, click .
7. To import profiles from an XML file:
a. In the Profiles tab of the main window, click .

The Profile Import window opens.
b. In the Profile Import window, click .
c. Select the relevant XML file and click Open.

d. The profiles included in the XML file are listed in the Profile Import list window.
e. Click . The profile is imported and you can view the import result from the window.
8. To synchronize the profile data from NE equipment and database, click .

8 Configure and manage cards
This section discusses how to use the LCT-NPT to configure and manage cards.
You can configure and manage the following types of cards in the LCT-NPT:
 SDH cards: including E1, E3, and STM-1/STM-4 cards.
 Optical cards: including SAMQ, SMQ1_4, SMS4, OMD1, and S1_4 cards.
 XIO cards: including XIO30-1/4/16, XIO30Q_1&4, and XIO64 cards.
 Data cards: including Layer 1, Layer 2, MPLS, and EOP cards.
 PCM cards: including SM10 and SM_10E cards.
 MSM cards: including DMCE1_32 and DMCES1_4.
 Optics card: OBC.
 TP card: TPEH8_1.
8.1 Card assignment tables

This section describes the card assignment for the NEs in LCT-NPT.
8.1.1 Card assignment for BG-40

The card applicable to each slot in the BG-40 is shown in the following table.
Table 8-1: BG-40 cards and applicable slots

Module Description MS DS1 DS2 DS3 DS-OW ES1 ES2 PS
MXC4X Cross connect, timing, Y
and control card
OMD1 2 x STM-1 optical or Y Y Y
electrical module
OMS4 1 x STM-4 module Y Y Y
MET_L1 4 x 10/100Base-T Y
module
OW_4X Orderwire module Y
M345_2 3 x E3/DS-3 module
Y Y Y
ME1_8F 8 x E1 module
Y Y Y
PE1_32 32 x E1 card Y Y
PE1_16 16 x E1 card Y Y
P345_3 3 x E3/DS-3 card Y Y
FE_L12 Ethernet card with L2 Y Y
switch (16 x
10/100Base-T)

LCT-NPT® User Guide Configure and manage cards
Module Description MS DS1 DS2 DS3 DS-OW ES1 ES2 PS

ESW_2G_8F L1/2 Ethernet card Y Y
with 2 x GbE and
8 x 10/100Base-T
interfaces
SM10 Intelligent PCM card Y Y
(26-channel N x 64
Kbps)
Note: Only one card
can be installed in a
BG-40 platform.
INF_40X Power Filter Unit Y
(-48 VDC)
AC_CONV- Power Conversion Unit Y
40X (220 VAC)


Module BG-20B BG-20E BG-20EH
PS_B FS_B MS L12 Dslot PS_E FS_E ES1 ES2 ES3 PSA_E PSB_E FS_E ES1 ES2 ES3
INF_20B Y
AC_CONV_20B Y
FCU_20B Y
MXC-20 Y
L1B_6F Y
MESW_6F Y
MPS_6F Y
M345_3 Y
SMD1 Y
SMD1H Y
OMS4B Y
OMS4H Y
MEOP_4 Y
MEOP_4H Y
MGE_1_L1 Y
ME1_21 Y

Module BG-20B BG-20E BG-20EH
PS_B FS_B MS L12 Dslot PS_E FS_E ES1 ES2 ES3 PSA_E PSB_E FS_E ES1 ES2 ES3
ME1_21H Y
ME1_42 Y
ME1_42H Y
ME_2G_4F Y
INF-20E Y
INF-E2U Y Y
AC_CONV_20E Y
AC_PS_E2U Y
FCU-20E Y
FCU-20EH Y
ESW_2G_8F_E Y Y Y Y Y Y
DMCE1_32 Y Y Y Y Y Y
MPOE_12G Y Y Y Y Y Y
MPS_2G_8F Y Y Y Y Y Y
PE1_63 Y Y Y Y Y Y
P345_3E Y Y Y Y Y Y
SM_10E Y Y Y Y Y Y
S1_4 Y Y Y Y Y Y
BG-OW

8.1.3 Card assignment for BG-20C

The BG-20C is a new, very low cost miniature MSPP demarcation platform. The hardware architecture is
based on BG-20B_L2M, but without any extensibility.
The BG-20C is an MPLS-capable STM-1/4 TM/ADM product with fixed E1 and FE interfaces. The BG-20C design
is based on the BG-20B_L2M platform, removing unnecessary functions and interfaces and merging
everything on a single board.


Module BG-30B BG-30E EXT-2U
PS_B FS_B MS XSA XSB TS1 TS2 TS3 PSA_E PSB_E FS_E ES1 ES2 ES3 EPS EPS EFS ES1 ES2 ES3
PS_A
A B
INF-30B Y Y
INF-30BH Y Y
INF-B1U Y Y
AC_CONV_30B Y
AC_PS-B1U Y
FCU_30B Y
FCU-30BH Y
MCP30 Y
MCP30B Y
XIO30-1 Y Y
XIO30-4 Y Y
XIO30-4B Y Y
XIO30Q_1&4 Y Y
XIO30-16 Y Y
PME1_21 Y Y Y
PME1_63 Y Y Y
PM345_3 Y Y Y
SMD1B Y Y Y
SMS4 Y Y Y
SMD4 Y Y
SMQ1&4 Y Y Y
SMQ1 Y Y Y

PS_A
A B
SMS16 Y Y Y
DMFE_4_L1 Y Y Y
DMFX_4_L1 Y Y Y
DMFE_4_L2 Y Y Y
DMFX_4_L2 Y Y Y
DMGE_1_L1 Y Y Y
DMGE_4_L1 Y Y
DMGE_2_L2 Y Y Y
DMGE_4_L2 Y Y
DMXE_22_L2 Y Y
DMCES1_4 Y Y
DMEOP_4 Y Y Y
INF_30E Y Y
INF_E2U Y Y
AC_CONV_30E Y
AC_PS_E2U Y
FCU_30E Y
FCU_E2U Y
PE1_63 Y Y Y Y Y Y
P345_3E Y Y Y Y Y Y
S1_4 Y Y Y Y Y Y
S4_1 Y Y Y Y Y Y
SM_10E Y Y Y Y Y Y
ESW_2G_8F_E Y Y Y Y Y Y
OBC Y Y Y Y Y Y
TP21_2 Y Y Y Y Y Y
TP63_1 Y Y
TPS1_1 Y Y Y Y Y Y
TPEH8_1 Y Y

PS_A
A B
BG_OW


Module BG-64 BG-30E EXT-2U
P P F M XS XS TS TS TS TS TS TS TS PSA_ PSB_ FS_ ES ES ES PSA_ PSB_ FS_ ES ES ES

S S S S A B 1 2 3 4 5 6 7 E E E 1 2 3 E E E 1 2 3
A B
INF-64 Y Y
FCU_64 Y
MCP64 Y
XIO64 Y Y
XIO16_4 Y Y
PME1_21 Y Y Y Y Y Y Y
PM345_3 Y Y Y Y Y Y Y
SMQ1 Y Y Y Y Y Y Y
SMQ1&4 Y Y Y Y Y Y Y
SMS16 Y Y Y Y Y Y Y
DMFE_4_L1 Y Y Y Y Y Y Y
DMFX_4_L1 Y Y Y Y Y Y Y
DMGE_4_L1 Y Y Y Y Y Y
DMGE_2_L2 Y Y Y Y Y Y Y
DMGE_8_L2 Y Y
DMXE_22_L Y Y Y Y Y Y
2
DMXE_48_L Y Y
2
DMCES1_4 Y Y Y Y Y Y Y

Module BG-64 BG-30E EXT-2U
P P F M XS XS TS TS TS TS TS TS TS PSA_ PSB_ FS_ ES ES ES PSA_ PSB_ FS_ ES ES ES

S S S S A B 1 2 3 4 5 6 7 E E E 1 2 3 E E E 1 2 3
A B
DMEOP_4 Y Y Y Y Y Y Y
DMGE_8_P Y Y
OS
INF_30E Y Y
INF_E2U Y Y
AC_CONV_3 Y
0E
AC_PS_E2U Y
FCU_30E Y
FCU_E2U Y
PE1_63 Y Y Y Y Y Y
P345_3E Y Y Y Y Y Y
S1_4 Y Y Y Y Y Y
SM_10E Y Y Y Y Y Y
OBC Y Y Y Y Y Y
TP63_1 Y Y
TPS1_1 Y Y Y Y Y Y
TPEH8_1 Y Y
MXP10 Y Y Y
BG_OW
8.1.6 Card assignment for NPT-1200

The card applicable to each slot in the NPT-1200 is shown in the following table.
Table 8-5: NPT-1200 cards and applicable slots

Module NPT-1200 EXT-2U
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-1200 Y Y
FCU-1200 Y
MCP1200 Y

XIO64 Y Y
XIO16_4 Y Y
CPTS100 Y Y
CPS100 Y Y
CPTS320 Y Y
CPS320 Y Y
DHXE_2 Y Y Y Y Y Y
DHXE_4 Y Y Y Y Y Y
DHXE_4O Y Y Y Y Y Y
DHGE_8 Y Y Y Y Y Y
DHGE_4E Y Y Y Y Y Y
DHGE_16 Y Y
DHGE_24 Y Y
PM345_3 Y Y Y Y Y Y Y
SMQ1 Y Y Y Y Y Y Y
SMQ1&4 Y Y Y Y Y Y Y
SMS16 Y Y Y Y Y Y Y
DMGE_2_L2 Y Y Y Y Y Y Y
DMGE_8_L2 Y Y
DMXE_22_L2 Y Y Y Y Y Y
DMXE_48_L2 Y Y
DMCES1_4 Y Y Y Y Y Y
MSE1_16 Y Y Y Y Y Y
MSC_2_8 Y Y Y Y Y Y
MS1_4 Y Y Y Y Y Y

MSE1_32 Y Y Y Y Y Y
NFVG_4 Y Y Y Y Y Y
NFVX Y Y Y Y Y Y
DMEOP_4 Y Y Y Y Y Y Y
TSHU_48V Y Y Y
DMGE_8_POS Y Y
INF-E2U Y Y
AC-PS-E2U Y
FCU-E2U Y
PE1_63 Y Y Y
P345_3E Y Y Y
S1_4 Y Y Y
SM_10E Y Y Y
EM_10E Y Y Y
MPS_2G_8F Y Y Y
OBC Y Y Y
DHFE_12 Y Y Y
DHFX_12 Y Y Y
MXP10 Y Y Y
TP63_1 Y
TPS1_1 Y Y Y
TPEH8_1 Y
DMCE1_32 Y Y Y
MPOE_12G Y Y Y
BG_OW



PS A PS B Tslot EPS A EPS B EFS Eslot1 Eslot2 Eslot3
INF-B1U Y Y
INF-B1U-D Y
INF-B1U-24V Y Y
AC-PS-B1U Y
MXC-1020
CPS50 Y
PME1_21 Y
PME1_63 Y
PM345_3 Y
SMD1B Y
SMS4 Y
DMCES1_4 Y
MSE1_16 Y
MSC_2_8 Y
MS1_4 Y
DHGE_8 Y
DHGE_4E Y
NFVG_4 Y
MSE1_32 Y
INF-E2U Y Y
AC-PS-E2U Y
FCU-E2U Y
PE1_63 Y Y Y
P345_3E Y Y Y
S1_4 Y Y Y
SM_10E Y Y Y
EM_10E Y Y Y
OBC Y Y Y
MPOE_12G Y Y Y

DMCE1_32 Y Y Y
MXP10 Y Y Y
DHFE_12 Y Y Y
DHFX_12 Y Y Y


INF-B1U Y Y
INF-B1U-D Y
INF-B1U-24V Y Y
AC-PS-B1U Y
MXC-1020
CPS50 Y
DMCES1_4 Y
MSE1_16 Y
DHGE_8 Y
DHGE_4E Y
MSC_2_8 Y
MS1_4 Y
NFVG_4 Y
MSE1_32 Y
INF-E2U Y Y
AC-PS-E2U Y
FCU-E2U Y
EM_10E Y Y Y
OBC Y Y Y
DMCE1_32 Y Y Y
MXP10 Y Y Y

DHFE_12 Y Y Y
DHFX_12 Y Y Y

The card applicable to each slot in NPT-1010 is shown in the following table.

Module BS DS
MCPS-1010DC Y
MCPS-1010AC Y
TMSE1_8 Y
TM10 Y


PS A PS B FS MXSA MXSB TS1 TS2 TS3 EPS A EPS B EFS ES1 ES2 ES3
INF-B1UH Y Y
FCU-1050 Y
MCPTS100 Y Y
MCPS100 Y Y
AIM100 Y Y
DHXE_2 Y Y Y
DHGE_8 Y Y Y
DHGE_4E Y Y Y
DHGE_16 Y
DHGE_16 Y
DHGE_24 Y
DHGE_24 Y
PME1_21 Y Y Y
PME1_63 Y Y Y

PS A PS B FS MXSA MXSB TS1 TS2 TS3 EPS A EPS B EFS ES1 ES2 ES3
PM345_3 Y Y Y
SMQ1 Y Y Y
SMQ1&4 Y Y Y
SMS16 Y Y Y
MSE1_16 Y Y Y
MSE1_32 Y Y Y
MSC_2_8 Y Y Y
MS1_4 Y Y Y
NFVG_4 Y Y Y
NFVX Y Y Y
INF-E2U Y Y
AC-PS-E2U Y
FCU-E2U Y
PE1_63 Y Y Y
P345_3E Y Y Y
S1_4 Y Y Y
SM_10E Y Y Y
EM_10E Y Y Y
OBC Y Y Y
DHFE_12 Y Y Y
DHFX_12 Y Y Y
MXP10 Y Y Y
TP63_1 Y
TPS1_1 Y Y Y
DMCE1_32 Y Y Y
MPOE_12G Y Y Y



Mo NPT-1800 EXT-2U
dul
e P P F M M C C T T T T T T T T T T T T T T T T T T T T T T T T E E E E E E
S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S P P F S S S
A B A B A B 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 S S S 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 A B
MB
P-
180
0
INF- Y Y
180
0
FCU Y
-
180
0
MC Y Y
P-
180
0
CIPS Y Y
1T
DHC Y Y Y Y Y Y
E_1
DHC Y Y Y Y Y Y
E_1
C
ECB Y
-
180
0
DHX Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
E_4
O
DH Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
GE_
8S
DH Y Y Y Y Y Y Y Y Y Y Y
GE_
4E
DH Y Y Y Y Y Y Y Y Y Y Y
GE_
8
DH Y Y Y Y Y Y Y
GE_
16

Mo NPT-1800 EXT-2U
dul
e P P F M M C C T T T T T T T T T T T T T T T T T T T T T T T T E E E E E E
S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S P P F S S S
A B A B A B 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 S S S 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 A B
DH Y Y Y Y Y Y Y
GE_
24
DH Y Y Y Y Y Y Y Y Y Y Y Y
GE_
20
MS Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
1_4
DHX Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
E_4
C_2
_8
E1_
32
NFV Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
G_4
INF- Y Y
E2U
AC- Y
PS-
E2U
FCU Y
-
E2U
OBC Y Y Y
8.1.12 Card assignment for NPT-1200i

The card applicable to each slot in the NPT-1200i is shown in the following table.
Table 8-11: NPT-1200i cards and applicable slots

Module NPT-1200i with MCIPS320 EXT-2U
PSA PSB FS MS XS XSB TS1 TS2 TS3 TS4 TS5 TS6 TS7 EPS A EPS B EFS ES1 ES2 ES3
A
MBP-1200
INF-1200 Y Y
FCU-1200 Y

Module NPT-1200i with MCIPS320 EXT-2U
PSA PSB FS MS XS XSB TS1 TS2 TS3 TS4 TS5 TS6 TS7 EPS A EPS B EFS ES1 ES2 ES3
A
MCP-1200 Y
MCIPS320 Y Y
DHXE_2 Y Y Y Y Y Y
DHXE_4 Y Y Y Y Y Y
DHXE_4O Y Y Y Y Y Y
DHGE_8S Y Y
DHGE_8 Y Y Y Y
DHGE_4E Y Y Y Y
DHGE_16 Y Y
DHGE_24 Y Y
MSE1_32 Y Y Y Y Y Y
MSC_2_8 Y Y Y Y Y Y
MS1_4 Y Y Y Y Y Y
NFVG_4 Y Y Y Y Y Y
INF-E2U Y Y
AC-PS-E2U Y
FCU-E2U Y
OBC Y Y Y
8.2 Work with cards

This section describes operations related to the cards in LCT-NPT, including:
 Card move
 Configure card attributes
 Hot insertion
 Slot reassignment
 Set the laser on/off status

8.2.1 Card move

Card move is supported when the LCT work mode is master.
In LCT-NPT, an assigned card can be moved from current slot to a new slot (must be blank) without deleting
existing traffic and configuration.
Before starting card move on EMS, you should delete the relative trails/tunnels/services/links from the NMS
(versions before V8) first. Otherwise the objects will be unsynchronized on NMS.
When performing card move, keep the following restrictions in mind:
 Real card move (move physical card from original slot to destination slot) should be done before moving
from LCT-NPT. Because some configuration is not supported in case of "card out", for example,
configuring VCG size. Note that for the ESW_2G_8F_E card which is special, both the original and
destination slots must have physical cards in slots during card move from LCT-NPT.
 Backup NE Database before performing card move from LCT-NPT.
 When the NE is managed through the DCC channel on the card to be moved, card move may result in
loss of management. In such case, card move should be done locally or by LCT.
Card move is supported for the following NEs:
 BG-20:
 Support card move from E-slot to E-slot in BG-20E or BG-20EH shelf
 BG-30:
 Support card move from T-slot to T-slot in BG-30B shelf
 Support card move from E-slot to E-slot in BG-30E or EXT-2U shelf
 BG-64:
 Support card move from T-slot to T-slot in BG-64 shelf
 NPT-1200:
 Support card move from T-slot to T-slot in NPT-1200 shelf
 Support card move from E-slot to E-slot in EXT-2U shelf
 NPT-1020/NPT-1021:
 NPT-1030:
 Support card move from T-slot to T-slot in BG-30B shelf
 NPT-1050:
 Support card move from T-slot to T-slot in NPT-1050 shelf

Limitations:
 TP card move is not supported in BG-30/BG-64/NPT-1200/NPT-1050.
 SM_10E card move is not supported in BG-20/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1050.
 Double-slot card (including DMGE_8_L2, DMGE_8_POS and DMXE_48_L2) move is not supported in
BG-64/NPT-1200.
 Move of PDH and SDH card with IOP is not supported in BG-30/BG-64/NPT-1200.
NOTE: When you perform card move, only one card can be moved at a time.
To perform card move:

2. Select the Card Move radio button at the left lower corner of the window.
3. Right-click a slot with card assigned.
4. From the shortcut menu, select Move, and then select a destination slot.
When you move out a card, the card in the original slot is marked gray.

5. Click Apply.
A confirmation window opens.

The following status window opens.
You can view the detail status or errors from the window.

To view card move status:

 In the main topology view, select the NE(s) whose status you want to view, then select Maintenance >
Advanced > View Card Move Status.
The Card Move Status window opens, listing details or error tasks.
8.2.2 Configure card attributes

Card attributes depend on the configuration requirements of 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, in the left object tree, select a card.
2. Select the Configuration working mode.
Descriptive information for each card is displayed in the General tab.
3. To configure the overhead parameters, select the TTI and TSL tab.
4. To batch edit TTI Detection, from the toolbar, click .

5. To configure the attribute for a single VC-4/VC-12, in the object tree under the selected card, select the
VC-4/VC-12 option, and then select the Configuration working mode.
The General tab opens.
6. Configure the fields as required.

8. To view the overhead information of a single VC-4/VC-12, select the VCs tab.
9. To retrieve the information, click .
8.2.2.1 Configure SF2AIS/SD2AIS

Since EoS mapper (VSC9135/9138 and PM5337) don't have EXC (TSF) and SD (TSD) detection, the EoS port
may get continuous packet loss/packet error in case some VC members have EXC/SD defect. The expected
behavior is that the severely errored VC member (the member with SD/EXC defect) can be removed from
VCG by LCAS.
In order to support such requirement, the AIS insertion function upon TSF/TSD on HOPP & LOPP of STM-N
interface can be used – if EXC or SD is detected on HOPP/LOPP, AIS will be inserted downstream to EoS
mapper so that LCAS will remove this failed member.
For each VC-4, VC-3 and VC-12 of STM-N port (which have source XC), two new attributes are configurable
to enable/disable AIS insertion in case of EXC/SD:
 SF2AIS: When SF2AIS is enabled, downstream AU/TU AIS will be inserted as consequent action of EXC
defect; otherwise consequent action is disabled.
 SD2AIS: When SD2AIS is enabled, downstream AU/TU AIS will be inserted as consequent action of SD
defect; otherwise consequent action is disabled.
The following lists the NEs and cards for whom this feature is relevant:
 BG-64/NPT-1200: XIO16_4, XIO64, CPTS100, SMQ1, SMQ1&4, SMS16, S1_4;

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

 NPT-1050: MCPTS100, SMQ1, SMQ1&4, SMS16, S1_4
To configure SF2AIS/SD2AIS
1. In the NE Shelf View window, in the left object tree, select a card that supports configuring
SF2AIS/SD2AIS.
3. Select the TTI and TSL tab.
4. Enable or disable the attributes as required. Default is disabled.
8.2.3 Configure temperature thresholds

Temperature thresholds can be configured in the following NEs:
 NPT NEs: NPT1200/NPT1050
Supported cards: XIO64, XIO16_4, CPTS100, CPS100, CPTS320, CPS320; MCPTS100, MCPS100.
 IP/MPLS NEs: NPT1200i/NPT1800
Supported cards: The cards that have temperature: DH card, CPS card, MCP card, MSM card, FCU card,
OBC card.

To configure temperature thresholds:

1. In the NE Shelf View window, in the left object tree, select a card that supports configurable
temperature thresholds, then click Configuration > General.
2. Right-click the Temperature area.

3. From the shortcut menu, click Threshold Setting. The Card Temperature Threshold Setting window
opens.

4. Configure High-Alarm Threshold/High-Warning Threshold for the card.

6. To return the default value that define in the file, click .
8.2.4 Hot insertion

Hot insertion enables you to insert cards without powering off the platform. To increase system availability,
hot insertion is used to reduce downtime and facilitate system upgrades.
The following cards and modules in the BG-20 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 different card type.
 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 different card type.
 OMS4H: Single STM-4 module for a Dslot that supports hot insertion. The card supports full
interchangeability with the current OMS4B, but has a different card type.
 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.

8.2.5 Slot reassignment

Reassignment is a logical operation, which changes the expected card type in a slot (from source card type
to target re-assignable card type) without the need to delete existing traffic and configuration. All service and
configuration of all MOs in source card are moved to the target card with predefined MO mapping
relationship between source and target cards, and card assignment is updated to target card. It is a pure data
conversion procedure.
Features of reassignment include:
 The current logical card is deleted and a new logical card is assigned.
 Traffic existing on the old card is kept and smoothly moved to the new card (unlike the Delete
operation).
 The existing cross connections and properties are automatically moved to the new card.
 Reassignment applies to a logical card (not a physical card).
 There are strict requirements regarding the order in which the operations are performed. You must
first change the physical card and then reassign the required logical card. Reassignment fails if the
physical card is not changed to the required card.
8.2.5.1 Reassignment procedure

The following figure illustrates the BG-30 reassignment procedure.
Figure 8-1: BG-30 reassignment procedure
The Expected Card is the logical card and the Actual Card is the physical card.
Several reassignment status issues exist in the system. They are:
1. Initial status (traffic on the old card is normal).
2. Card is reassigned but not replaced (not permitted).
3. Card is reassigned and replaced (traffic on the new card is normal).
4. Card is replaced but not reassigned (compatible; traffic OK).
The proper reassignment procedure is 1, 4, 3.

8.2.5.2 Reassign cards

Reassignment is changing the expected equipment type to a new but compatible type, logically in a slot. It is
actually an "edit" operation. Unlike an "assign" or "unassign" procedure, reassignment can be done without
deleting existing traffic and configurations. All the traffic is recovered automatically if the actual equipment
is compatible with the new equipment type after reassignment.
Reassignment is based on the expected card type and has no relationship to the actual card type in the slot
and the card status.
The following lists the card reassignment supported in LCT-NPT:
 BG-30 with XIO30-1/4, XIO30Q_1&4, or XIO30-16 cards can support:
 Reassignment from PME1_21 to PME1_63
 Reassignment from SMD1B to SMQ1
 BG-30 with XIO30Q_1&4 or XIO30-16 can support:
 Reassignment from DMGE_2_L2 to DMGE_4_L2
 BG-64/NPT-1200 with XIO64 or XIO16_4 can support:
 Reassignment fromDMGE_2_L2 to DMGE_4_L2
 NPT-1200 with CPS100/CPTS100 can support:
 Reassignment from CPS100 to CPS320
 Reassignment from CPTS100 to CPTS320
 NPT-1020 can support:
 NPT-1050 can support:
 Reassignment from MCPTS100 to MCPS100
 Reassignment from MCPS100 to MCPTS100
The reassignment from CPS100 to CPS320 should be done as explained in the following steps:
1. Reassign CPS100 to CPS320 from EMS
 It is expected that "Card-mismatch" alarm will occur on XS A and XS B slots, but traffic is not
affected;
2. Replace CPS100 card with CPS320 card one by one
a. Replace standby card first;
b. Replace active card after standby CPS320 is operational;
3. Note that no new configuration should be made during this period (from reassignment till card
replacement finished).

NOTE: When reassigning DMGE_2_L2 to DMGE_4_L2, the total quantity of Customer Virtual
LAN (C-VLAN) and Service Virtual LAN (S-VLAN) should be less than 8 * 1024 - 128.
Before starting card reassignment on EMS, you must delete the relative trails/tunnels/services/links from the
NMS (versions before V8) first. Otherwise the objects will be unsynchronized on NMS.
To perform card reassignment:

2. Select the Reassign radio button at the left lower corner of the window.
3. Right-click the card you want to reassign.
4. From the shortcut menu, select Reassign, and then select the card.
5. Click Apply.
A confirmation window opens, prompting you to confirm the reassignment.
6. Click Yes to perform the reassignment.
TIP: You must decide when and how to replace a card. If the card is first replaced physically,
existing traffic is down until card reassignment is done, unless the new card is compatible with
the expected card. If reassignment is done first, existing traffic is not affected until the card is
extracted.
If you want to perform reassignment without affecting the existing traffic, perform the
reassignment operation first and then replace the physical card.

8.2.6 Set 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 detected loss of signal (LOS) is received. Laser on/off status is configured slightly
differently for optical and ETY ports. For ETY ports, laser configuration and laser maintenance are configured
separately.
To set the laser on/off status for optical ports:

1. In the NE Shelf View window, in the left object tree, select an optical interface.
2. Select the Maintenance working mode.
The following window opens.
3. To obtain the laser control attribute of this optical interface from the NE, click .
4. Set the laser attribute values, as required.
5. To send the attribute value to the NE and save it to the DB, click Apply.

To set the configuration aspect of laser control for ETY ports:

1. In the NE Shelf View window, in the left object tree, select an ETY port.
3. Select the SFP Setting tab
4. Set the laser configuration in the ALS Configuration area as required.


To set the maintenance aspect of laser control for ETY ports:

1. In the NE Shelf View window, in the left object tree, select an ETY port.
3. Select the Laser Control tab
4. Set the maintenance command as required.

8.2.7 Set user label and description per port

Two management attributes are available from LCT-NPT to be configured:
 User Label: up to 32 characters
 Description: up to 256 characters
The two attributes can be supported in the following ports:
 SDH Port
 E1/E3 Port
 ETY Port (FE/GE/10GE/MOE/10GE, MOE and ETY)
 EoS/MoT/EoP Port
 OTN Port
To set user labels and description for a port:

1. In the NE Shelf View window, in the left object tree, select a port.
Descriptive information for each port is displayed in the General tab. The specific fields included
depend on the type of port.
3. In the User Label and Description fields, set the attributes as required.

4. Click Apply.
8.3 BG_OW management

The external OW box provides orderwire (OW) 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, 4-wire interfaces to the handset, and so on.
8.3.1 Assign OW slot

To assign the OW card:
1. In the NE Shelf View window, in the left object tree, right-click the NE.
2. Select Slot Assignment.
3. Right-click the OW slot, and in the shortcut menu, select OW.
4. To send the configuration to the NE and the DB, click Apply.
8.3.2 Configure OW settings

Orderwire attribute configuration configures the OW telephone, OW attributes, and OW routing of all NEs.
OW telephone configuration relates to the entire network and can only be performed on NEs in the
management domain. Operation authorities are needed from all network NEs to perform OW configuration
in the network.
The OW telephone is used for OW contacts between SDH NEs that support the addressing and conference
calls. The OW number is a 3-digit integer.
SDH OW provides communications for field engineers and equipment maintenance personnel, and supports
address selective calls and conference calls.

To configure BG-40 OW settings:

1. In the BG-40 NE Shelf View window, in the left object tree, select Control and Physical Object and then
OW.
2. In Configuration working mode, select the OW Setting tab.
3. Configure the parameter settings as required:

 Phone Number 1/Phone Number 2: OW number of the end NE.
 Conference Call Attribute: NE conference telephone when used in conversation. The two options
are Listen Only and Listen and Talk.
 Conference Call Number: conference telephone number for all NEs that support conference
calling.
 Conference call waiting time: in sec, applies to the entire network.
4. To deliver the OW attributes of the NE to the NE equipment and save them to the DB, click Apply.
5. To display the NE OW attributes obtained from the NE equipment, click .
To configure BG-20/BG-30/BG-64/NPT-1200 OW settings:

1. In the NE Shelf View window, in the left object tree, select Control and Physical Object and then OW.
2. In the Configuration working mode, select the OW Setting tab.
3. Configure the settings in the window.
4. To deliver the OW attributes of the NE to the NE equipment and save them to the DB, click Apply.
5. To display the NE OW attributes obtained from the NE equipment, click .

8.4 Configure PDH cards

PDH cards include E1 and E3 cards.
E1 cards
E1 cards include the following:
 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/NPT-1020.
 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/NPT-1200/NPT-1020.
 PME1_63: 61_E1 card for BG-30B and BG-64/NPT-1200/NPT-1020.
 PE1_63: 63_E1 card for BG-20/BG-30/BG-64/NPT-1200/NPT-1020.
You can configure overhead attributes and port attributes for E1 cards.
E3 cards
E3 cards include the following:
 P345_3: three configurable E3/DS-3 cards for BG-40.
 M345_3: three configurable E3/DS-3 cards for BG-20.
 M345_2: two configurable E3/DS-3 cards for BG-40.
 PM345_3: three configurable E3/DS-3 cards for BG-30B and BG-64/NPT-1200/NPT-1020.
 P345_3E: three configurable E3/DS-3 extension cards in BG-30E/EXT-2U.
To configure PDH (E1/E3) cards:

1. In the NE Shelf View window, in the left object tree, select the PDH card (E1 or E3).
2. In the Configuration working mode, select the port tab (E1 Ports or E3/DS3 Ports).
3. Configure the relevant port fields, as required.
4. For E1 cards, to batch enable or disable the Retiming attribute, click in the toolbar.
6. To retrieve information, click .

8.5 SDH card configuration

SDH cards include the following objects.
NOTE: Some of these cards are logical configuration variations of an object. Configuration
procedures for each type of card, including all the logical variants of that card, as well as
configuration of VC-4 contiguous concatenation, relevant for some of these cards, are all
described in this section.
 SAM-1/SAM-4: The SAM-1/4 is not a physical card or module, but an abstract object of the BG-20B SDH
interface. The BG-20B SDH interface is STM-1/4-compatible, and can smoothly be switched between
STM-1 and STM-4 by software configuration without affecting traffic, as described in Configure SAM-
1/SAM-4 cards.
 SMQ1: The SMQ1 card is a new I/O card with 4 x STM-1 that can be inserted in any Tslot of the BG-30B
and BG-64/NPT-1200/NPT-1050.
 SMD4: The SMD4 provides two STM-4 ports. It can only be inserted in Tslot #2 and Tslot #3 of the BG-
30B, and can only be assigned in ADM-16 configurations.
 SMQ1&4: The SMQ1&4 card can be inserted in any Tslot of the BG-30 and BG-64/NPT-1200/NPT-1050
but can be assigned in ADM-16/ADM-64 configurations. It has four SDH ports. Each port rate is STM-
1/4 compatible, as described in Configure SMQ1&4 cards.
 SMS16: SMS16 is a single STM-16 I/O card with an SFP-based STM-16 interface. It has the same PCB as
SMQ1&4 and can only be assigned in the BG-30B ADM-16 system and in the BG-64/NPT-1200/NPT-
1050. Features of the SMS16 card include:
 Supports 1 x STM-16 and can be inserted in the BG-30B ADM-16 system and BG-64/NPT-
1200/NPT-1050.
 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 support the switching between two XIO
cards with ACT signals from two XIO cards.
 Provides one timing reference to each XIO card.
 Provides the conversion between RS&MS bytes and System Overhead interface (8M PCM).
 Has no local CPU and is controlled by the CPU in MCP30/MCP30B.
 Outputs one timing reference clock to TMU.
 External interfaces include:
 1 x STM-16: SFP
 Channel LEDs: 1 x laser On
 Card level LEDs: ACT, FAIL
 SAM10: SAM10 is a virtual card in CPTS100 that contains a STM-64 port with optional OTU2
encapsulation. The STM-64 port contains a XFP module.

 SAM25_2: SAM25_2 is a virtual card in CPTS100 which contains two STM-1/4/16 with optional OTU1
encapsulation (OTU1 is for STM-16 only). Each STM-1/4/16 port contains a SFP module.
 SAM4_2: SAM4_2 is a virtual card in MXC-1020 in NPT-1020 NE.
8.5.1 Configure SAM-1/SAM-4 cards

The SAM-1/4 is not a physical card or module, but an abstract object of the BG-20B SDH interface. The BG-
20B SDH interface is STM-1/4-compatible, and can smoothly be switched between STM-1 and STM-4 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, see Manage Licenses in the
LCT-NPT Supporting Information.
To switch between SAM-1 and SAM-4:

2. Right-click the A1 or A2 slot, and from the shortcut menu, select SAM4.
3. To save the change, click Apply.

The SDH interface is smoothly switched to STM-4.

8.5.2 Configure VC-4 contiguous concatenation

The following cards support VC-4 concatenation:
 SMS4
 SMD4
 SMQ1
 SMQ1&4
 SMS16
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 a card that supports VC-4 concatenation.
2. In the Configuration working mode, select the VC-4 Concatenation tab.
3. Select the VC-4-4c concatenation checkbox per port, as required.

4. To save your changes, click Apply.

8.5.3 Configure SMQ1&4 cards

The SMQ1&4 card can be inserted in any Tslot of the BG-30 and BG-64/NPT-1200/NPT-1050 but can be
assigned in ADM-16/ADM-64 configurations. It has four SDH ports. Each port rate is STM-1/4 compatible.
To change the rate for SMQ1&4:

1. In the NE Shelf View window, in the left object tree, select a port under the SMQ1&4 card.
2. In the Configuration working mode, select the Rate Setting tab.
3. To obtain and view information from the DB, click .

4. Select the appropriate Change rate option (to STM-4 or to STM-1) as required.
8.6 L1 data card configuration

Layer 1 data cards include the following objects.
NOTE: While specific attributes values and capabilities differ between the L1 data cards, they
are all configured in a similar manner. The basic steps in L1 data card configuration are described
in Configure L1B_6F cards. Specific fields, options, and values will differ, depending on the
specific card being configure.
 L1B_6F: The L1B_6F is a Layer 1 data card in BG-20B. Card attribute configuration is described in
Configure L1B_6F cards.
 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.

 DMFE_4_L1: The DMFE_4_L1 is a Layer 1 data card that supports 4 x 10/100Base-T LAN interfaces and
4 x EoS WAN interfaces for the BG-30B/BG-64/NPT-1200. It supports live insertion. You can manage the
DMFE_4_L1 as per the L1B_6F, as described in Configure L1B_6F cards.
 DMFX_4_L1: The DMFX_4_L1 is a Layer 1 card that can be inserted into any Tslot in BG-30B/BG-64/NPT-
1200. Apart from the physical interfaces, most of its functions are the same as those of the DMFE_4_L1:
 Four 100BaseFX interfaces.
 Optical connector type SFP and LC.
 An SFP module that supports laser parameters monitoring and relevant TCAs.
 Laser control: Force on, Force off (default is on).
 DMGE_1_L1: The DMGE_1_L1 card supports one GbE interface with a total bandwidth of 4 x VC-4. It
can be inserted into any Tslot in BG-30B. The functionality of the DMGE_1_L1 is very similar to
DMFE_4_L1, except that it has only one VCG and one port, and supports only one LAN interface (GbE).
The DMGE_1_L1 supports the following:
 1 x GbE interface based on the SFP module.
 1000BaseSX, 1000BaseLX, 1000BaseZX, 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 switchover scheme as 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), both controlled by the setting of CSF.
 BIT.
 DMGE_4_L1: The DMGE_4_L1 supports four GbE interfaces with standard EoS L1 functionality. The
total bandwidth is 16 x VC-4. The DMGE_4_L1 card can be inserted into Tslot 2/Tslot 3 in the BG-
30B/BG-64/NPT-1200, but can only be used in the ADM-16 system, including the XIO30Q_1&4 system.
Card attribute configuration is described in Configure DMGE_4_L1 cards. The DMGE_4_L1 supports the
following:
 VC-4/VC-3/VC-12 virtual concatenation, LCAS, and GFP
 Optical and electrical SFP
 Four GbE LAN interfaces based on SFPs and four EoS WAN interfaces
 Local CPU to improve survivability

8.6.1 Configure L1B_6F cards

The L1B_6F is a Layer 1 data card in BG-20B. This section describes how to configure L1B_6F card attributes.
NOTE: While specific attributes values and capabilities differ between the L1 data cards, they
are all configured in a similar manner. The basic steps in L1 data card configuration are described
in this section. Specific fields, options, and values will differ, depending on the specific card
being configure.
Select the specific card or port of interest from the object tree and configure the attribute values
as relevant. For example, to configure L1B_6F card attributes, select the L1B_6F card in the
object tree. To configure DMGE_1_L1 port attributes, select an EoS port of the DMGE_1_L1 card
in the object tree.
To configure L1B_6F card attributes:

1. In the BG-20 NE Shelf View window, in the left object tree, select the L1B_6F card.
Summary information about the L1B_6F card is displayed.
3. To configure the EoS encapsulation protocol:
a. Select the EoS Ports tab.
This window contains the EoS protocol and general information settings.
b. To retrieve information from NE equipment, click .

c. Set the parameters as required.
d. Click Apply to save your changes.
4. To perform VCG configuration:
a. In the left object tree, right-click the L1B_6F card or an EoS port. In the shortcut menu, select
Create VCG.
The VCG Attribute window opens.
b. To retrieve information from NE equipment, click .

c. Configure the virtual cascade mode (E1), the bandwidth of each VCG, and the LCAS attributes
through the fields in the Traffic and LCAS window tabs.
5. To add or remove a VCG member:
a. Select the VCG in the object tree.
b. Select the Configuration working mode.
c. To retrieve information from NE equipment, click .

d. For every member of this VCG, the E1s can be activated or deactivated, as required.
6. To configure port attributes:

a. Select an EoS port in the object tree.

d. Configure attributes as required.
7. To view real-time traffic:
a. Select the L1B_6F card in the left object tree.
b. Select the Maintenance working mode.
c. Select the EoS Payload tab.
In this window, you acquire the Rx and Tx traffic of EoS and FE ports (ports 1 through 6). Traffic
here refers to the average traffic within the first 15 minutes in the acquisition process, displayed
in bps.
d. To retrieve information from NE equipment, click .

8. To perform loopback maintenance:

a. Select the L1B_6F card in the left object tree.
c. Select the Loopback tab.
The Loopback Type options include Terminal Loopback, Facility Loopback, and No Loopback
(default).
d. To retrieve information from NE equipment, click .

e. To batch edit the loopback type:
i. Click from the toolbar.
ii. Click to select the required operations, as relevant (All No Loopback, All Terminal
Loopback, or All Facility Loopback).
9. To perform MST maintenance:
a. Select VCG in the left object tree.
MST FAIL force/release functionality is available for LCAS members.

d. Select the appropriate MST Attribute value (Auto (default) or Force Fail).
e. To batch edit the MST attribute, click from the toolbar.

8.6.2 Configure DMGE_4_L1 cards

The DMGE_4_L1 supports four GbE interfaces with standard EoS L1 functionality. The total bandwidth is 16
x VC-4. The DMGE_4_L1 card can be inserted into Tslot 2/Tslot 3 in the BG-30B/BG-64/NPT-1200, but can
only be used in the ADM-16 system, including the XIO30Q_1&4 system.
The DMGE_4_L1 supports the following:
 VC-4/VC-3/VC-12 virtual concatenation, LCAS, and GFP
 Optical and electrical SFP
 Four GbE LAN interfaces based on SFPs and four EoS WAN interfaces
 Local CPU to improve survivability
To configure DMGE_4_L1 port attributes:

1. In a BG-30/BG-64/NPT-1200 NE Shelf View window, in the object tree, select an EoS port of the
DMGE_4_L1 card.
A summary of the card configuration is displayed.
3. To retrieve the information from NE equipment, click .

4. Set the parameters as required, and click Apply to save your changes.
5. When Negotiation is set to Enable, to restart auto-negotiation, click .
8.7 L2 data card configuration

This section describes L2 data card configuration.
NOTE: While specific attributes values and capabilities differ between the L2 data cards, cards
within the same category are often configured in a similar manner. The basic steps in L2 data
card configuration are described in the following sections. These general instructions can also
be accessed through the links in the following table. Specific fields, options, and values will
differ, depending on the specific card being configure.
The L2 card in LCT-NPT can be classified into the following categories.
Table 8-12: L2 data card classification

Card Card types Description
category
Purple cards
 MESW_6F The MESW_6F is a data card on the BG-20B that provides EPL and
EVPLAN services. The MESW_6F can also manage the Ethernet quality
of service (QoS) and bandwidth.


category
 ESW_2G_8F_E ESW_2G_8F cards placed in the BG-40/BG-20 chassis can operate as
either a provider’s core (P) RS or a provider edge (PE) RS, in order to
implement a BG-based provider network. The customer edge (CE) RS
and the customer’s 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 LAN (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
P2P 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:
 2 x GE interfaces (SFP)
 8 x ETY interfaces (RJ-45)
 LED indicator for the ESW_2G_8F card: Alarm/Active/Fail
 LED indicator for the ports: LINK/RX/SPEED
When the ESW_2G_8F card is reused in the BG-20E platform, 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 features 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, see the sections in
this manual relating to the MESW_6F.
LSI cards (App300 and App3000)

App300  DMFE_4_L2 The DMFE_4_L2 is a Layer 2 data card that provides Ethernet-switched
cards service and also supports MPLS services.
 DMFX_4_L2 The DMFX_4_L2 is a Layer 2 data card with 4 x 100BaseFX that can be
inserted into any BG-30B/BG-64/NPT-1200 Tslot. The only difference
between the DMFX_4_L2 card and the DMFE_4_L2 card is that the
DMFX_4_L2 card has four SFP blocks.
The DMFX_4_L2 card also supports MPLS services; see the LCT-NPT
Service Management Guide.


category
 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 MESW_6F card, except
for the number of 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; see the LCT-NPT Service
Management Guide.
 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, 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
App3000  DMGE_2_L2 The DMGE_2_L2 is supported in both the ADM-1/4, ADM-16, and 4 x
cards ADM-1/4 systems, and can be assigned to any Tslot in BG-30B/BG-
64/NPT-1200. When the card 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 include:
 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.5 Gbps or 622 Mbps, depending on XIO30
type.
 No local XC capability. When working with the ADM-1/4 system,
dynamic bandwidth adjustment results in a 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. Switching
between two XIO cards is supported with ACT signals from two XIO
cards.
The DMGE_2_L2 Layer 2 functionality is the same as the DMFE_4_L2
but with higher capacity and larger throughput.
The DMGE_2_L2 card also supports MPLS services; see the LCT-NPT
Service Management Guide.


category
 MPS_2G_8F MPS_2G_8F is a substitute of ESW_2G_8F_E, with richer features and
capability. It is an L2 data expansion card with 2 x GbE and 8 x
10/100Base-T interfaces and at least 16 EoS WANs. Both PB and MPLS
are supported.
MPS_2G_8F has 64 EoS ports and 2 GbE COMBO and 8 FE Ethernet LAN
ports. It has a local XC supporting VC-12/VC-3/VC-4 cross connect, so it
can support timeslot reallocation (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 to the DMGE_2_L2 except
that it has eight FE ports.
 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 four 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, INF-20BE or
AC_CONV_20B 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 the 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 in BG-30B.
EZchip cards
 DMGE_4_L2 DMGE_4_L2 is a single Tslot module supporting four GbE interfaces
based on SFP which can be inserted in the Tslot 1~7 (except Tslot 5) of
BG-30B (with any XIO) and BG-64/NPT-1200. It has up to 64 EoS
channels with total bandwidth of 2.5 Gbps, and supports L2
functionality: both MPLS and PB, IEEE1588, and Synchronous Ethernet.
 MPLS and PB functionality
 16 x VC-4 WAN bandwidth and 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. The
Layer 2 features and functionality are similar. DMGE_4_L2 supports all
the features that the DMGE_2_L2 does.


category
 DMGE_8_L2 DMGE_8_L2 is a double Tslot module supporting two GE combo ports
and six GE ports based on SFP which can be inserted to Tslot 1~7
(except Tslot 5) in BG-64/NPT-1200. Combo ports support both SFP and
the RJ45 interface. It has up to 96 EoS ports with total bandwidth of 5
Gbps, and supports L2 functionality: both MPLS and PB, IEEE1588, and
Synchronous Ethernet.
 8 x GbE interface (2 of them are COMBO)
 IEEE1588
DMGE_8_L2 has larger throughput, more GbE interfaces, higher EoS
and MoT bandwidth, and larger service capacity than DMGE_2_L2.
Layer 2 features and functionality are similar. DMGE_8_L2 supports all
the features that DMGE_2_L2 does.
 MPOE_12G MPOE_12G is an expansion-slot module supporting 12 GbE interfaces
(4 100M/1000M GbE LAN ports based on SFP modules and 8
10/100/1000M GbE LAN ports based on RJ45 connector) and layer 2
functionality with embedded Power over Ethernet technology support.
MPOE_12G supports PB and MPLS functionality, and it supports all the
features of DMGE_8_L2.
 DMGE_8_POS
 DMXE_22_L2 DMXE_22_L2 is a layer 2 module for the Tslot of BG30B, BG-64 and
NPT-1200 with 2 GE ports based on SFP and 2 10GE ports based on
SFP+, which can be assigned to any Tslot of BG-30B and Tslot 1~7
(except Tslot 5) in BG-64/NPT-1200. It is designed for triple-play
application and aggregation card for mobile backhaul and business
connectivity application, they provide higher bandwidth (10G port) and
larger throughput than DMGE_4_L2 cards.
DMXE_22_L2 is supported only in XIO30-16 and XIO30Q_1&4 system of
BG-30 and XIO64 and XIO16_4 systems of BG-64/NPT-1200.
Basically, DMXE_22_L2 has larger throughput, 2 10GbE interfaces, and
larger service capacity than DMGE_4_L2, while layer 2 features and
functionality are similar. DMXE_22_L2 supports all features that
DMGE_4_L2 supports, and the port attributes are the same as the 10
GE ports of the DMXE_48_L2.
 DMXE_48_L2
DMXE_48_L2 is a double-slot Tslot module supporting 8 x GbE interfaces,
4 x 10 GbE interfaces and L2/MPLS functionality. Basically, DMXE_48_L2
has larger throughput, 4 x 10 GbE interfaces, and larger service capacity
than DMGE_8_L2, while Layer 2 features and functionality are similar.
DMXE_48_L2 supports all features that DMGE_8_L2 supports.
 AMXE_2
 AMXE_4


category
 AMXE_24
 DHGE_4E
 DHGE_8
 DHGE_16
 DHGE_24
 MGE_8
 MGE_12
MGE_12 is a virtual card which includes 4 electric GbE ports with PoE
supporting, 4 electric GbE ports without PoE supporting and 4 Optical GE
ports.
By default, the ETY ports of MGE_12 are not activated. You can activate
or deactivate the ETY ports manually; see Activate/Deactivate ports.
 HEOS_16
 MEOS_8
 DHXE_2
 DHXE_4
 DHFE_12
 DHFX_12
 CPTS100
 CPS100
 CPS50
 CS10
 CS5
 CS320
 CS100_1050

### Where is the FE_L12 in this list? It's in the chapter - where does it belong in the card categories? and how
should all the cards WITHOUT descriptions be described? ###
8.7.1 MESW_6F
The MESW_6F is a data card on the BG-20B that provides EPL and EVPLAN services. The MESW_6F can also
manage the Ethernet’s quality of service (QoS) and bandwidth.
MESW_6F card management objects can be:
 ETY interfaces
 Switches
 EoS interfaces (ports, EoSs, VCGs)

8.7.1.1 Manage MESW_6F ports

The MESW_6F card has 14 FE ports, 6 of which are ETY ports connecting to the local side and 8 EoS ports
connecting to the remote side through an EoS mapper.
To configure MESW_6F card attributes:

1. In a BG-20 NE Shelf View window, in the left object tree, select the MESW_6F card.
Summary information about the MESW_6F is displayed.
3. To configure the ETY port attribute:
a. Select the ETY Ports tab.
b. Configure the following attributes:

 Auto-Negotiation: Values are Auto-negotiation (default) and No Auto-negotiation.
 Local Pause Mode: Default No Pause.
 Speed: 100M (default) or 10M.
 Duplex: Full (default) or Half.
4. To configure the EoS encapsulation protocol and port attribute settings:
a. Select the EoS Ports tab.

b. For the MESW_6F card's EoS channel:

 the encapsulation protocol can be GFPF (default) or LAPS.
 The Send FCS may be Enabled or Disabled (default).
 The Dedicate attribute value may be Yes or No.
c. For the EoS port attributes, three can be configured and three are read only.
 Read-only attributes are Duplex Status, Speed Status, and 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: Valid values range from 1518 bytes to 9022 bytes (default).
 Subnetwork ID: Can be set for each WAN port. Used to distinguish the VLAN
subnetwork.
5. To configure the port licenses of the ETY ports:
a. Select the Port License tab.
b. To enable an FE-ETY port, in the License State list, select the relevant Enabled radio button.
c. To save the settings, click Apply.

6. To perform VCG configuration:

a. In the left object tree, right-click the MESW_6F card or an EoS port.
b. From the shortcut menu, select Create VCG.
c. Configure the virtual cascade mode (VC-12/VC-3/VC-4) and bandwidth of each VCG.
d. Configure the attributes listed under the LCAS tab, as relevant.
7. To add or remove a VCG member:
a. In the object tree, select the VCG.
c. For each member of this VCG, a Deactivated attribute can be set. This entails removing the
member from the VCG.
8. To configure a single EoS port attribute:
a. In the object tree, select an EoS port.
b. Select the Configuration working mode General tab.
c. Configure the relevant attributes as required.

9. To view real-time traffic:

a. In the left object tree, select the MESW_6F card.
b. In the Maintenance working mode, select the EoS Payload tab.
Through this window you acquire the Rx and Tx traffic of EoS ports (ports 1 through 8), specified
in bps. The traffic here refers to the average traffic within the first 15 minutes of the acquisition
process.
10. To perform loopback maintenance:
a. In the left object tree, select the MESW_6F card.
b. In the Maintenance working mode, select the Loopback tab.
The Loopback Type values are Terminal Loopback, Facility Loopback, and No Loopback (default).
c. Set the Loopback Type for each VCG.
d. To save the configuration in the DB and the NE, click Apply.
e. To batch edit the loopback type, from the toolbar, click .

11. To perform MST maintenance:
a. In the left object tree, select a VCG.
For LCAS members, the MST FAIL force/release function can be performed. MST attribute values
are Auto (default) and Force Fail.
c. Set the MST attribute value for each VCG.
d. To save the configuration in the DB and the NE, click Apply.
e. To batch edit the MST attribute, from the toolbar, click .

8.7.1.2 Manage LAGs for MESW_6F

The MESW_6F supports up to 13 Ling Aggregation Groups (LAGs). 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
You can also configure a LAG. 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 a LAG 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 a LAG:
1. In the BG-20 NE Shelf View window, in the left object tree, right-click the MESW_6F card.
2. From the shortcut menu, select Create LAG.
The Create/Edit Aggregation Ports window opens.
3. Select an aggregation group from the Aggregation Group dropdown list.
4. Select ports in the left list and click to add them to the right aggregation group.
5. To remove a port from the right aggregation group, select the port(s) in the right list, and click .
6. To retrieve the information of the LAG to view, click the Get button.
7. To save the results, click Apply.

To configure a LAG:
1. In the BG-20 NE Shelf View window, in the left object tree, select the MESW_6F card.
2. In the Configuration working mode, select the LAGs tab.
3. Select the required aggregate groups in the Aggregation Group list.

4. Select the trunk mode in the Trunk Mode dropdown list.
Trunk mode is used to select a physical port on a LAG to 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 (default mode).
Although all three modes ensure the packet order in each service, they differ in the level of load sharing.
Source XOR Destination MAC provides the best load sharing between physical ports of the LAG.

8.7.1.3 Manage the bandwidth profile for MESW_6F

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.
To access the bandwidth profile:

1. In the BG-20 NE Shelf View window, in the left object tree, expand the MESW_6F and select the Switch
module.
2. In the Configuration working mode, select the Profiles tab and then Bandwidth Profile.
3. To restore the default bandwidth profile, click .
4. To retrieve the bandwidth profile from the equipment, click .

5. Change the committed information rate (CIR) and committed burst size (CBS) values as required.
NOTE: Due to a hardware limitation, the MESW_6F card only supports eight bandwidth profile
levels

8.7.1.4 Manage policer profiles for MESW_6F

When creating VSIs, each UNI port must have a policer. Each policer can only be used once. Except for the
name, policer values can be identical. Up to 128 policers can be defined per MESW_6F card.
To access the policer profile:

module.
2. In the Configuration working mode, select the Profiles tab and then Policer Profile.
3. To restore the default policer profile, click .
4. To retrieve the policer profile from the equipment, click .

5. Change the attribute values as required.
8.7.1.5 Manage VSI services for MESW_6F

The MESW_6F supports a virtual private network (VPN). VSIs define policies and provide user SLAs.
The MESW_6F supports the following VSI types:
 EPL
 PB MPtMP
Create an EPL for MESW_6F
To create an EPL for the MESW_6F:

module.
2. In the Services working mode, select the VSI List tab.
3. Click the Create VSI icon .

The Create VSI window opens.
4. To create an EPL service:
a. From the Service Type dropdown list, select EPL.
b. In the respective fields, enter the values for VSI ID, NMS VSI ID, User Label, and Customer.

c. (Optional) Select the Enabled CSF checkbox. You can add a description in the VSI Description field.
d. In the Objects Selections area on the right, in the relevant list, select one ETY port and one or two
EoS ports. To deselect, right-click an object, or select the object in the list, and click .
5. To create a policer, click .

6. To save and activate the EPL, click Activate.
7. If you click Save, the EPL is saved but not activated.
8. To activate a VSI that has been saved but not activated:
a. Select the Recent Saved VSIs tab.
b. Select the VSI you want to activate, and click Activate.
The EPL is activated.
Create PB MPtMP for MESW_6F
To create PB MPtMP for the MESW_6F:

module.

4. From the Service Type dropdown list, select PB MPtMP.
5. Enter the VSI ID, NMS VSI ID, User Label, Customer, S-VLAN, and vFIB Quota values in the relevant
fields.
The vFIB Total Reserved Entries field indicates the total number of reserved entries in the vFIB.

6. (Optional) Add a description in the VSI Description field.

7. In the Objects Selections panel on the right, select ETY and EoS ports as required in the relevant list. To
deselect an object, right-click, or select it in the lower-right list, and click .
8. To create a policer:
a. Click .
b. Set the Tag Type and C-VLAN ID values for the selected UNI ports.
 Click "+" to expand the UNI port.
 To enlarge the lower-right area, click above the toolbar.
c. In the Tag Type & C-VIDs panel:
i. Select the Specific C-VIDs checkbox and define the C-VID range.
ii. Select the Untagged checkbox if needed.

iii. Select the Priority Tagged checkbox if needed.

iv. To add PVID for an untagged FE-ETY port, select the Double tag checkbox and set the
number in the adjacent field.
9. To map policers:
a. Click .
b. Select the port where you want to perform CoS mapping.
c. Input the tags listed in Available Tags in the Add Tags field and click Add.
d. To delete the C-VLANs, select the Delete Priority & Policer Mapping button.

e. Click "+", and in the expanded area:

 Select the Priority values in the From and To dropdown lists.
 Select a policer in the Policer dropdown list.
f. Click Add to add the policer to the C-VLAN.
g. Repeat this operation for the other C-VLANs. Up to 16K C-VLANs can be added to all VSIs of the
card, calculated as follows:
 If C-VLAN range 1~2000 is selected, the C-VLAN number is equal to 2000.
 If "All Tags" is selected, the C-VLAN number is equal to 1.
10. Repeat the preceding step to map policers for other UNI ports.
11. To create and activate the PB MPtMP, click Activate.
12. If you click Save, the PB MPtMP is saved but not activated.
13. To activate a PB MPtMP that has been saved but not activated:
b. Select the VSI in this window you want to activate, and click Activate.
The PB MPtMP is activated.
8.7.1.6 Configure 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 the MESW_6F:

1. In the NE Shelf View window, in the left object tree, expand the MESW_6F and select the Switch
module.
2. In the Configuration working mode, select the vFIB Setting tab.
3. Set the Aging Time value and the Port Lock status.
When Port Lock is enabled, the address-learning function is disabled. If a MAC frame contains a new
source MAC address, this frame is discarded.
4. To save the setting, click Apply.
To manage the vFIB list:

1. In the NE Shelf View window, in the left object tree, expand the MESW_6F and select the Switch
module.
2. In the Services working mode, select the vFIB List tab under the vFIB tab.

3. To add new items to vFIB tables:

a. In the Filter area, select the Static button.
b. Click .
The Create New Static vFIB Entry window opens.
c. Set the VSI ID, MAC, and Port fields.
d. Click Apply.
4. To view the vFIB items:
a. In the Filter area, select the attributes you want to view.
b. Click Get & Filter.
5. To retrieve static vFIB items, click Query.
6. To flush a specific VSI:
a. In the Filter area, select the VSI from the VSI dropdown list.
b. Click the Flush icon .
7. To flush all the VSIs, select the Flush All icon .
8.7.2 DMFE_4_L2
The DMFE_4_L2 is a Layer 2 data card that provides Ethernet-switched service and also supports MPLS
services. 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
For details on MPLS services, see the LCT-NPT Service Management Guide.

8.7.2.1 Manage DMFE_4_L2 ports

The DMFE_4_L2 card has 12 FE ports, 4 ETY ports that connect to the local side through an RJ-45 connector,
and 8 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 in 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, in the left object tree, select the DMFE_4_L2 card.
Summary information about the DMFE_4_L2 is displayed.
3. To configure the ETY port attributes:
a. Select the ETY Ports tab.
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 (default), or forward with PVID.
 Priority Tagged Frame: Frames can be block, forward (default), or forward with PVID.
 PVID: The range is 0-4094; 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 (default 0). The Default CD priority is the Default Priority
for untagged frames in both port-based and non-port-based applications.
If a port is configured as forwarded with PVID, it is dedicated as an Untagged type and can only
be added once.
4. To configure the EoS encapsulation protocol and the EoS port attribute settings:
 Select the EoS Ports tab.
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, I-NNI.
5. If there are MoT ports defined in the DMFE_4_L2 card, you can view or edit the relevant attributes in
the MoT Ports tab.
6. To configure a single ETY/EoS port attribute:
a. In the object tree, select the ETY/EoS port.
b. In the Configuration working mode, select the General tab.
c. For the ETY/EoS ports that can be added in services, you can configure the Scheduling Mode as
Strict Priority or Enhancement:
 Scheduling Mode: Each port has 8 priority (0~7 from low to high) queues. The scheduling
mode defines the behavior of scheduling between 8 CoS queues of the port.
 Strict Priority: The queue with higher priority will occupy the whole bandwidth. The packet
in lower priority queue are sent only when the queue with higher priority is empty.

 WRR Mode: Weight Round Robin mode. Packets in all queues are sent in order based on
the weight value for each queue. This mode cannot be set in LCT-NPT.
 Enhancement: It is "Strict Priority + WRR" mode. The 8 queues will be separated into 2
groups based on the CoS delimiter configured by user: The scheduling mode between queue
in higher priority group and queue in lower priority group is Strict Priority mode, and the
scheduling mode between queues within the same priority group is WRR mode.
For more details about port management for the DMFE_4_L2, see Manage ports in the MESW_6F.
8.7.2.2 Configure CoS bandwidth

The CIR granularity of high CoS shaper and low CoS bandwidth is configurable between 128Kbps and 512Kbps
in steps of 128Kbps.
LCT-NPT adds new grids for tunnel/queue bandwidth configuration. The new tunnel/queue bandwidth
granularity is shown as follows:
 128K~512Kbps@128Kbps
 1~16Mbps@1Mbps
 16~64Mbps@2Mbps
 64~256Mbps@4Mbps
 256~1280Mbps@8Mbps
You can configure CoS bandwidth, which includes CoS shaping for each ETY port and both CoS shaping and
CoS WRED for each EoS port. You can configure manual WRED profile for each CoS.

To configure CoS bandwidth:

1. In the DMFE_4_L2 Shelf View window, in the left object tree, select an ETY or EoS port.
2. In the Configuration working mode, select the CoS Bandwidth tab.
3. To retrieve information to view, click .

4. Set the parameters for each CoS as needed.
5. When the Bind Mode is set as Manual, you can configure a WRED profile from the Latency Profile
Name dropdown list.
8.7.2.3 Manage LAGs for DMFE_4_L2

Use the following procedure to configure a LAG in the DMFE_4_L2 card. The procedure can also be used for
other MSPP Layer 2 cards.
LAG n:m redundancy is supported. You can configure the maximum number of active interfaces in a multilink
bundle (max-active-links); the default max-active-links is the number of interfaces in a multilink bundle. The
range of max-active-links is 1 to the maximum number of members of the LAG.
For LAG 1:1, max-active-links should be set to 1.
LCT-NPT also supports configuring LAG-down threshold, so that the min. number of interfaces in a multilink
bundle must be active for the entire bundle to be considered up.
The default minimum number of links is 1.
Link Aggregation Control Protocol (LACP) allows port and system information to be exchanged between two
partner systems as well as information between partner bundles. It sends LACP protocol data units (PDUs)
between partner bundles to help maintain the links within the bundles.
LACP can indicate if a bundle is misconfigured (links on one side of the bundle are not the same as links on
another side), if the link is ready, and if there are loops in the bundle. By default, Ethernet bundles do not
send out LACP PDUs.

To create a LAG:
1. In a BG-30/BG-64/NPT-1200 NE Shelf View window, in the left object tree, right-click the DMFE_4_L2
card.
2. From the shortcut menu, select Create LAG.
3. Select an aggregation group from the Aggregation Group dropdown list.
4. Select ports in the left list and click to add them to the right aggregation group.
5. Set the parameters as follows:
 Max Active Links: From 1 to the number of members in the LAG (default is number of members
in LAG).
 Min Active Links: From 1 to max-active-links (default 1).
 LACP Enable: Enabled or Disabled (default Disabled).
 Mode: Active or Passive (default Active).
 Priority: From 1 to 65535 (default 128).
 Time Out: Short or Long (default Short).
If a port is added to a LAG with the LAG Distribution Enable value set to disabled, or the LAG port
member is changed from LAG Distribution enabled to disabled, the LAG’s traffic is not distributed to
that port and packets received from it are not discarded.
6. Select the LAG Distribution Enable checkbox as required.
7. Set the Hold Off Time as required.
8. To retrieve the information of the LAG to view, click the Get button.
10. To remove the whole LAG, remove all the ports in the LAG.
11. To save the results, click Apply.

To configure a LAG:
1. In the NE Shelf View window, in the left object tree, select the LAG object.
2. In the Configuration working mode, select the LAG Member tab.
3. Modify the LAG as needed.

5. To view the states of a LAG member port:
a. In the Configuration working mode, select the LAG Member Port State tab.
b. To get the LAG state information, select a LAG member port in the LAG Member Port dropdown
list and click .
6. To view the LAG member port statistics:
a. In the Configuration working mode, select the LAG Member Port Statistics tab.
b. To get the LAG member port statistics information, select a LAG member port in the LAG Member
Port dropdown list and click .
c. To clear the information, click .
To set LAG system configuration:

1. In the NE Shelf View window, in the left object tree, expand the DMFE_4_L2 card and select the Switch
module.
3. Set the value of LACP System Priority as required.
The LACP System Priority attribute is used to assign system priority. System priority can be set from 1
to 65535 (default 32768), where the higher the value, the lower the priority.

8.7.2.4 EFM Link OAM

Ethernet in the First Mile (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:

2. In the Maintenance working mode, select the ETY Maintenance tab.
3. Set the parameters for each ETY port.
To manage ETY link OAM events and threshold:

2. In the Maintenance working mode, select the ETY Link OAM Window and Threshold tab.
To view ETY link OAM events statistics:

1. In a BG-30 NE Shelf View window, in the left object tree, select an ETY port.
2. In the Maintenance working mode, select the ETY Link OAM Events Statistics tab.
8.7.2.5 Configure the vFIB

The DMFE_4_L2 Fiber DB (vFIB) table length is 32K.
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
vFIB utilization is supported and the utilization percentage indicates the current vFIB/applicable vFIB Quota.

To manage the vFIB list:

1. In the BG-20 NE Shelf View window, in the left object tree, expand the DMFE_4_L2 and select the
Switch module.
2. In the Services working mode, select the vFIB List tab under the vFIB tab.
3. To add new items to vFIB tables:

a. In the Filter area, select the Static button.
b. Click .
The Create New Static vFIB Entry window opens.
c. Set the VSI ID, MAC, and Port values.
d. To save changes, click Apply.
4. To view the vFIB items:
a. In the Filter area, select the attributes you want to view.
b. Click Get & Filter.
5. To retrieve the static vFIB items, click Query.
6. To flush a specific VSI:
a. In the Filter area, select the VSI from the VSI dropdown list.
b. Click the Flush icon .
7. To flush all the VSIs, click the Flush All icon .

8. To view the vFIB utilization, select the vFIB Utilization tab under the vFIB tab.
a. In the Filter area, select VSI, User Label, and Customer as required.
b. Click .
The Utilization percentage indicates the current vFIB/applicable vFIB Quota.

8.7.2.6 Manage policer profiles for DMFE_4_L2

For details about managing policer profiles in DMFE_4_L2, see the LCT-NPT Service Management Guide.
8.7.2.7 Manage VSI services for DMFE_4_L2

The DMFE_4_L2 supports the following VSI types:
 EPL
 PB PtP
 PB MPtMP
 MPLS PtP
 MPLS MPtMP
 MPLS BPDU Tunneling
 ERPS VSI
This section describes how to create EPL, PB PtP, and PB MPtMP VSIs.
For details on creating MPLS VSIs, see Services management in MSPP/NPT in the LCT-NPT Service
Management Guide
For details on creating CES VSIs, see CES services management in the LCT-NPT Service Management Guide.
For details on creating ERPS VSIs, see Ethernet ring protection switching in the LCT-NPT Network
Management Guide.
Create an EPL for DMFE_4_L2

This section describes how to create an EPL for DMFE_4_L2.
To create an EPL:
Switch module.

4. From the Service Type dropdown list, select EPL.
5. Select the VSI State (Enabled (default) or Disabled).
When disabled, all policers block their traffic, including NNI ports. When enabled, all policers enable
traffic flow. This field is editable with no constraints.
6. In the respective fields, enter the values VSI ID, User Label, and Customer.

7. (Optional) Select the Enabled CSF checkbox. You can add a description in the VSI Description field.
8. In the Objects Selections area on the right, in the relevant list, select one ETY port and one or two EoS
ports. To deselect, right-click an object, or select it in the lower-right list and click .
9. To create a policer, click .

10. To create and activate the EPL, click Activate.
11. If you click Save, the EPL is saved but not activated.
12. To activate a VSI that has been previously saved but not activated:
The EPL is activated.
Create PB PtP for DMFE_4_L2
To create PB PtP for DMFE_4_L2:

Switch module.

4. From the Service Type dropdown list, select PB PtP.
6. Enter the VSI ID, User Label, Customer, and S-VLAN values in the left side of the window.


8. In the Objects Selections area on the right, select one ETY port and one or two EoS ports from the
relevant lists. To deselect an object, right-click, or select the object in the lower-right list and click .
a. Click .
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.
b. Click "+" to expand the UNI port.
c. To enlarge the lower-right area, click above the toolbar.
d. Apply the following when defining the CoS mapping:
 For each priority (0 to 7), select only one provider CoS (default is CoS0 for all priorities).
 All priority values must 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."
e. In the DSCP Mapping area, all the VSI UNI/E-NNI ports have the option to enable the same DSCP
to provider CoS mapping policy. Set Map DSCP to Disabled (default) or Enabled.
When Map DSCP is enabled, you can set the Map Option as By Name or By Value.

i. If you select By Name, you can set CoS mapping individually for the 21 named DSCPs.
ii. If you select By Value you can set the CoS mapping by groups of DSCP values.
Figure 8-2: By value mapping definition
iii. Input the DSCP values in the following format (same as that of the C-VID):
 Single number, for example, 21.
 Multiple numbers, separated by comma (,), for example, 1,3,5,7.
 A scope, identified by two numbers connected by dash (-), for example, 1-7.
 Any combinations of the preceding, for example, 1-5,8,19-21.

The last line All Others means all DSCP values except for the ones listed here will be mapped
to the selected CoS in the right side. If all the DSCP values (0~63) have been listed already,
the All Others option will be gray out and not editable.
f. For the selected UNI port:
i. In the Tag Type & C-VIDs field, select the Specific C-VIDs checkbox and define the C-VID
range.
ii. Select the Untagged, Priority Tagged, Tag Translation and All tag Translation to one
checkboxes as required.
Up to 16K C-VLANs can be added to all VSIs of the card, calculated as follows:

10. To edit the mapping:
a. Click .
b. Add, move, delete tags, or delete groups by selecting the corresponding button.
11. For the selected E-NNI port, set Extern-SVLAN ID as required.
12. To create and activate the PB PtP, click Activate.

13. If you click Save, the PB PtP is saved but not activated.
14. To activate a PB PtP that has been saved but not activated:
The PB PtP is activated.
Create PB MPtMP for DMFE_4_L2

This section describes how to create PB MPtMP for the DMFE_4_L2 card.

To create PB MPtMP:
Switch module.

4. From the Service Type dropdown list, select PB MPtMP.
6. Enter the VSI ID, User Label, Customer, S-VLAN, BSC Threshold, and vFIB Quota values as required.
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 (the Switch Quota is forwarded) or unknown addresses
are dropped (when the action is dropped).
7. (Optional) Select the Enable MAC Address Learning checkbox.
9. To enable E-Tree, select the E-Tree Enable checkbox.
10. In the Objects Selections area on the right, select the ETY and EoS ports you want from the relevant
lists. To deselect, right-click the object, or select it in the lower-right list, and click .

a. Click .
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.
b. Click "+" to expand the UNI port.
c. To enlarge the lower-right area, click above the toolbar.
d. Apply the following when defining the CoS mapping:
 For each priority (0 to 7), select only one provider CoS (default is CoS0 for all priorities).
 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
is displayed, "A policer is associated with this CoS."
e. In the DSCP Mapping area, all the VSI UNI/E-NNI ports have the option to enable the same DSCP
to provider CoS mapping policy. Set Map DSCP to Disabled (default) or Enabled.
When Map DSCP is enabled, you can set the Map Option as By Name or By Value.
i. If you select By Name, you can set CoS mapping individually for the 21 named DSCPs.

ii. If you select By Value you can set the CoS mapping by groups of DSCP values.
Figure 8-3: By value mapping definition
iii. Input the DSCP values in the following format (same as that of the C-VID):
 Single number, for example, 21.
 Multiple numbers, separated by comma (,), for example, 1,3,5,7.
 A scope, identified by two numbers connected by dash (-), for example, 1-7.
 Any combinations of these, for example, 1-5,8,19-21.
The last line All Others means all DSCP values (except for the ones listed here) will be
mapped to the selected CoS on the right side. If all the DSCP values (0~63) have already
been listed, the All Others option will be grayed out and not editable.

f. For the selected UNI ports:

i. In the Tag Type & C-VIDs field, select the Specific C-VIDs checkbox and define the C-VID
range.
ii. Select the Untagged, Priority Tagged, Tag Translation and All tag Translation to one
checkboxes as required.
Up to 7000 C-VLANs can be added to all VSIs of the card, calculated as follows:

12. To edit the mapping:
a. Click .
b. Add, move, delete tags, or delete groups by selecting the corresponding button.
13. For the selected E-NNI ports, set the Extern-SVLAN ID as required.
14. To set the port role, in the ServicePortRole list, set the selected port role as Root or Leaf from the
dropdown list.
Note that the port role can be configured as Root or Leaf when the service type is PB MPtMP or MPLS
MPtMP.
15. To create and activate the PB MPtMP, click Activate.
16. If you click Save, the PB MPtMP is saved but not activated.

17. To activate a PB MPtMP that has been saved but not activated:
The PB MPtMP is activated.
8.7.3 Configure MSTP (MESW_6F and DMFE_4_L2)

The MESW_6F and DMFE_4_L2 cards support MSTP.
For details about configuring MSTP, see the LCT-NPT Network Management Guide.
8.7.4 View and manage VSI objects (MESW_6F and

DMFE_4_L2)
The VSI list enables you to view and manage VSI objects. These tasks are relevant for both MESW_6F and
DMFE_4_L2 cards. The actions highlighted in the screenshots in this section are relevant for both cards.
To view and manage VSI objects:

1. In the NE Shelf View window, in the left object tree, expand the relevant card and select the Switch
module.
3. To activate a VSI, select the VSI in the list, and click .
4. To deactivate a VSI, select the VSI in the list, and click .

5. To edit a VSI:
a. Select the VSI in the list.
b. Click Edit VSI .

The Edit VSI window opens.
c. Modify the VSI attributes as required.
d. Click Apply to save the settings.

6. To view the details of a VSI:

a. Select the VSI in the list.
b. Click .
The View VSI window opens.
7. To delete a VSI, select the VSI in the list, and click .
8. To delete all of the VSIs in the list, click the Select All icon and then click .
9. Click to deselect all.

10. To upload VSIs:
a. Click the VSI Upload icon .

The VSI Upload window opens.
b. To upload VSIs from the selected card, click Upload.
The status bar shows the consistency status between the NE and the DB.
c. If the NE and the DB are inconsistent, select the VSI Compare tab to display the inconsistency
results.
d. To send the data from the NE to the DB, click Save To DB.
e. To delete the data from the DB, click Delete from DB.
11. Some actions described here can also be accessed from the right-click menu, as shown in the following
window.

8.7.4.1 Manage VSI performance data for DMFE_4_L2

This section describes how to manage VSI performance data, including:
 Current Performance
 Recent Performance
 History Performance
 TCA Threshold
 Monitor and Report
 Reset Performance Counters
Policer performance can also be managed, including:
 Current Performance
 Recent Performance
 History Performance
 Reset Performance Counters
To manage VSI performance:

1. In the VSI list, select a VSI and right-click. From the shortcut menu, select VSI Performance.

2. To view the current performance of the selected VSI:

a. From the shortcut menu, select Current.
b. Click .
3. To view the recent performance of the selected VSI:

a. From the shortcut menu, select NE History.
b. Click .
4. To view the historical performance of the selected VSI:
 From the shortcut menu, select EMS History.
5. To set the threshold of the selected VSI:
a. From the shortcut menu, select Threshold Setting.
b. Click .
6. To set monitoring and reporting:
a. From the shortcut menu, select Monitoring and Reporting.
b. Select the Monitor Active and Auto-Report checkboxes as relevant to monitor and/or auto-report
the VSI.
c. To batch edit the Monitor Active/Auto-Report attributes:
i. From the toolbar, click .

ii. Click to select the required operation.
8.7.4.2 Manage VSI alarms for DMFE_4_L2

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

1. In the VSI list, select a VSI, and right-click.
2. From the shortcut menu, select VSI Alarm.
3. To view current alarms:

 From the shortcut menu, select Current.
4. To view historical alarms:
a. From the shortcut menu, select History.
b. Click .

5. To mask the alarms of the selected VSI:

a. From the shortcut menu, select Monitoring and Reporting.
b. Edit the settings are required.
c. To batch edit the TTI Detection attribute, from the toolbar, click .
8.7.5 DMXE_48_L2
DMXE_48_L2 is a double-slot Tslot module supporting 8 x GbE interfaces, 4 x 10 GbE interfaces and L2/MPLS
functionality.
DMXE_48_L2 is applicable only in the BG-64/NPT-1200 system and can only be assigned to TS1 or TS6 of the
BG-64/NPT-1200 platform. It is a double slot card that occupies two slots (similar to DMGE_8_L2).
Basically, DMXE_48_L2 has larger throughput, 4 x 10 GbE interfaces, and larger service capacity than
DMGE_8_L2, while Layer 2 features and functionality are similar. DMXE_48_L2 supports all features that
DMGE_8_L2 supports.
Main features of the DMXE_48_L2 include:
 8 x GbE interface and 4 x 10 GbE interface
 IEEE1588

8.7.5.1 Manage DMXE_48_L2 ports

To manage DMXE_48_L2 ports:
1. In a BG-64/NPT-1200 NE Shelf View window, in the left object tree, select the DMXE_48_L2 card.
Summary information about the DMXE_48_L2 is displayed.
3. To configure GE ETY port attributes for all GE ETY ports on the selected card:
a. Select the GE ETY Ports tab.
A summary of all GE ETY port settings is displayed.
b. Edit attribute values as required.
TIP: Usually, the tab options displayed on the right side of the window reflect the object
selected in the left object tree. The GUI generally focuses on the information relevant for your
work.
For example, if you select a DMXE_48_L2 card in the object tree, the port tabs on the right side
would list configuration data for all ports on that card, organized by port type (GE ETY, 10 GE
ETY, EoS, etc.). If you select an individual port in the object tree, the port tabs would list only
the display options and configuration data relevant for that port. The attributes listed in the
General tab for a GE ETY port would differ from the attributes listed for a 10 GE ETY port.
4. To configure the 10 GE ETY port attributes for all 10 GE ETY ports on the selected card:
a. Select the 10 GE ETY Ports tab.
A summary of all 10 GE ETY port settings is displayed.
Note that the 10GE ports of the DMXE_48_L2 support two port modes: LAN (10GBASE-R) by
default and WAN (10GBASE-W).

5. To configure port attributes for a specific port:

a. Select a port in the left object tree.
A summary of the configuration settings relevant for the selected port is displayed.
c. Edit the relevant attributes as required.
6. To configure the EoS encapsulation protocol and EoS port attributes port attributes for all EoS ports on
the selected card:
a. Select the EoS Ports tab in the window.
7. To configure the MoT port attributes for all MoT ports on the selected card:
a. Select the MoT Ports tab in the window.
8. To configure the MoE port attributes for all MoE ports on the selected card:
a. Select the MoE Ports tab in the window.
9. To configure the 10 GE MoE port attributes for all 10 GE MoE ports on the selected card:
a. Select the 10GE MoE Ports tab in the window.
10. To check the port status:
a. Select the Port Physical Status tab.
b. Click to retrieve the information to view:

 Link Status: actual link status of the PHY.
 Laser Tx: actual status of TX Disable of SFP/SFP+. NA for copper interface.
 LOS Status: actual status of LOS output of SFP/SFP+. NA for copper interface.
 AN: if auto-negotiation is enabled or not.
 AN Status: the actual negotiation result. NA if AN is disabled or not supported.
 Remote Fault: if remote fault is detected or not.
 PHY Type: the actual PHY type configured.
 Admin Status: enabled or not.
 IOP Trigger: whether this port is an IOP trigger. NA in case of no IOP created.

8.7.5.2 WAN interface sublayer (WIS)

The WAN interface sublayer (WIS) is an optional PHY sublayer that can be used to create a 10GBase-W PHY
that is data-rate and format compatible with the SONET STS-192c transmission format defined by ANSI, as
well as the SDH VC-4-64c container specified by ITU. The purpose of the WIS is to allow 10GBASE-W
equipment to generate Ethernet data streams that may be mapped directly to STS-192c or VC-4-64c streams
at the PHY level, without requiring MAC or higher-layer processing.
Ethernet 10 GE ports support two modes: LAN (10GBase-R) and WAN (10GBase-W). The default is LAN mode.
When management configures it to WAN mode, the WIS MO is created.
To configure the WIS MO:

1. In the BG-64/NPT-1200 NE Shelf View window, select a 10GE port in the left object tree.
3. Select 10GBase-W as the PHY Type.
4. Click Apply.
The WIS MO is created in the left object tree.

5. To configure the WIS MO attributes:

a. Select the new WIS object in the left object tree.
c. Edit the attribute values as required.

6. To configure the force signal:
a. Select the Maintenance working mode.
b. Select the Force Signal tab.
c. Edit the attribute values as required.
8.7.5.3 Manage LAGs for DMXE_48_L2

In the DMXE_48_L2 card, GE ports, 10GE ports, and EoS ports support LAG function. There are at most 32
LAGs for the DMXE_48_L2 card. 10GE ports and GE ports cannot be added into one LAG.
For details about managing LAGs in DMXE_48_L2, see LAG Improvement in the LCT-NPT Service Management
Guide.
8.7.5.4 Configure SFP and SFP+ settings

DMXE_48_L2 supports eight SFP GE ports and four SFP+ 10GE ports. The eight SFP GE ports are similar to the
3~8 GE ports of DMGE_8_L2.
To configure SFP port settings:

1. In the BG-64/NPT-1200 NE Shelf View window, in the left object tree, expand the DMXE_48_L2 card
and select a GE port.
2. In the Configuration working mode, select the SFP Setting tab.
3. Set the parameters as required in the relevant field.

To configure SFP+ port settings:

1. In the BG-64/NPT-1200 NE Shelf View window, in the left object tree, expand the DMXE_48_L2 card
and select a 10 GE port.
2. In the Configuration working mode, select the SFP+ Setting tab.
3. Set the parameters as required in the relevant field.
When the port is configured as 10GBase-X or 1000Base-X, ALS and laser control are supported.
8.7.6 MPOE_12G
Power over Ethernet (PoE) simplifies network installation and maintenance by using the switch as a central
power source for other network devices.
 One equipment type provides all substation services.
 Reduced cabling costs: Adding power circuits at the point of need can be a significant expense, so one
cable provides both power and data.
Power over Ethernet feature is implemented in the MPOE_12G card, which is applicable to BG-20E, BG-20EH,
BG-30E (BG-30/BG-64/NPT-1200/NPT-1020) and EXT-2U (BG-30/BG-64/NPT-1200/NPT-1020/NPT-1050)
system and can be inserted to any Eslot of these systems.
MPOE_12G is an expansion-slot module supporting 12 GbE interfaces (4 100M/1000M GbE LAN ports based
on SFP modules and 8 10/100/1000M GbE LAN ports based on RJ45 connector) and layer 2 functionality with
embedded Power over Ethernet technology support.
MPOE_12G supports PB and MPLS functionality, and it supports all the features of DMGE_8_L2.
NOTE: BG-30E is not recommended for PoE applications due to following limitations:
 Total PoE power is limited in 50W;
 When INF-30E redundancy is configured in BG-30E, power loss or disconnecting power
cable to one INF-30E will result in seconds of shutdown of PoE ports.
PoE systems require power budget management, because the total power consumption of a shelf may
exceed the maximum power consumption that power supply unit (INF or AC_CONV) can support.
PoE power budget and power consumption management is different for EXT-2U shelf with different power
supply:
 DC – When EXT-2U shelf is equipped with INF-E2U
 AC – When EXT-2U shelf is equipped with AC_PS-E2U
For EXT-2U shelf with INF-E2U:
 Dedicated power for PoE in each slot (2A per slot);
 Total PoE power budget per shelf is 270W (fixed, not configurable);
 Maximum PoE power budget per MPoE_12G card is 90W.

For EXT-2U shelf with AC_PS-E2U:

 No dedicated power for PoE, and all cards and PoE share the same power budget;
 Total PoE power budget per shelf is 90W (configurable between 0~90W, default is 0);
 Maximum PoE power budget per MPoE_12G card is 90W.
There are two different layers of PoE power budget management:
 Configure card level power budget management
 Configure port level power budget management
8.7.6.1 Configure card level power budget management

Card level power budget management is supported in the BG-20E/BG-30E/BG-64E/NPT-1200E/NPT-
1020E/NPT-1010/NPT-1050E NEs.
To configure card level power budget management:

1. In the NE Shelf View window, in the left object tree, select the relevant PoE card, one of the following:
 MPOE_12G
 MGE_12
 MGE_8
2. In the Configuration working mode, select the PoE Setting tab.
3. In the Card PoE field, you can configure the following parameters:
 Maximum PoE Power:
 For the MPOE_12G card in BG-20E and BG-30E shelf, the Maximum PoE Power is
configurable when the Total PoE Power in Shelf level is not 0, with the range from 0 to 50W,
in steps of 0.1W. The default value is 0. The PoE power sum of all the PoE cards in the shelf
must be less than Total PoE Power Budget (TPPB) of the shelf.
 For the MPOE_12G card in BG-20EH and EXT-2U shelf, the Maximum PoE Power is
configurable, fixed to 270W (default), with the range from 0 to 90W, in steps of 0.1W. The
default value is 0.
 PoE Enable: Enable or disable PoE function of the card. The default is disabled.
 Priority Policy: If the priority policy is enabled, the PoE port with high priority will get power first.
The default is disabled.
 Power Budget Left: The power that is not allocated to any ports.
 Actual PoE Power: Sum of real time power of all the PoE ports in the card.
4. View the port PoE information in the NE from the Port PoE List in the window.
5. Click Apply.

8.7.6.2 Configure port level power budget management

Port level power budget management is supported in BG-20E/BG-30E/BG-64E/NPT-1200E/NPT-1010/NPT-
1050E.
 For MPOE_12G, only port 5~12 can support PoE setting.
 For MGE_12 in NPT-1020 NE, only port 1~4 can support PoE setting.
 For MGE_8 in NPT-1010 NE, only port 1~4 can support PoE setting.
To configure port level power budget management:

1. In the NE Shelf View window, in the left object tree, select the relevant port, one of the following:
 Port 5~12 under the MPOE_12G card
 Port 1~4 under the MGE_12 or MGE_8 card
2. In the Configuration working mode, select the PoE Setting tab.
3. You can configure the following parameters:
 Maximum PoE Power: The maximum PoE power of the port. It can be set as 0 (default), 4W, 7W,
15.4W or 30W from the dropdown list.
 PoE Enable: Enable or disable PoE function of the card. The default is disabled.
 Legacy: Power Device (PD) includes standard PD and non-standard PD which is legacy. You can
enable and disable discovering legacy PD function, and the default is disabled. If a legacy PD is
connected, the port is fixed to class 0, which is 15.4W.
 PD Description: Description of the PD connected to the PoE port.
 Priority: PoE port has three priority levels: Critical, High and Low. The default value is Low.
4. You can view the following PoE power information for the port:
 Power Status: Whether power is applied to the PD. It can be power Off or power On.
 Power Good: Whether power supply works. It can be Not Good or Good.
 Current: The current value of PoE port real time. The max theoretical current value is 8A.
 Voltage: The voltage value of PoE port real time. The max theoretical voltage value is 382V.
 Power: The power of PoE port real time. The max theoretical power value is 3060W.
 Detection Status: Last detection result for the PoE port.
 Class: Last classification result for the PoE port.
 Disconnect Mode: PoE port disconnect mode has two modes: DC Disconnect mode and AC
Disconnect mode. Our Power Sourcing Equipment (PSE) is fixed to DC Disconnect mode.
 Power Pairs: PoE port power pairs has two alternatives: PSE pinout Alternative A and PSE pinout
Alternative B. Our power pairs are fixed to PSE pinout Alternative A.
 Power Denied Counter: The counter of power denied times.
 Over Load Counter: The counter of power over load times.
 Short Counter: The counter of power short current times.
 Power On Seconds: The counter of port power on seconds.

5. Click Apply.
8.7.7 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 10Base-T/100Base-T Ethernet transparent transmission interfaces can be provided.
Internally, an 8-port L2 switching module is integrated that supports the L2 switching function through an
external cable connection.
The functional blocks contained in the FE_L12 card include 8 VCGs, 8 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 VCG’s virtual cascade mode and maximum traffic.
8.7.7.1 Manage FE_L12 ports

To manage FE_L12 Ports:
1. In a BG-40 NE Shelf View window, in the left object tree, select the FE_L12 card. In the Configuration
working mode General tab, you can view the general information of the FE_L12.

2. To perform switch configuration, in the left object tree, select the Switch object in the FE_L12 card.
Then in the Configuration working mode, select the General tab. Configure the attributes as required,
and click Apply to save the settings.

3. To configure the ETY port attribute, select the ETY Ports tab in the preceding window.

4. To configure the EoS encapsulation protocol and the EoS port attribute settings, select the EoS Ports
tab.

5. To perform VCG configuration, in the left object tree, right-click the FE_L12 card or an EoS port. From
the shortcut menu, select Create VCG. The VCG Attribute window opens.

6. In this window configure the virtual cascade mode (VC-12/VC-3), the bandwidth of each VCG, and the
LCAS attributes.
7. To add or remove a VCG member, in the object tree, select the VCG, and then select the Configuration
working mode.
For every member of this VCG, a Deactivated attribute can be set. This removes the member from the
VCG.

8. To view real-time traffic, in the left object tree, select the FE_L12 card. In the Maintenance working
mode, select the EoS Payload tab.
In this window, you acquire the Rx and Tx traffic of EoS ports (ports 1 through 8). 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.

9. To view real-time traffic for ETY ports, in the left object tree, select the FE_L12 card. In the Maintenance
working mode, select the ETY Payload tab.

10. To perform loopback maintenance, in the Maintenance working mode, select the Loopback tab. The
Loopback Type values are Terminal Loopback and No Loopback (default No Loopback).

11. Set the Loopback Type for each VCG in this window, and click Apply to save the configuration in the DB
and the NE.
12. To perform MST maintenance, in the left object tree, select a VCG, 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 (default Auto).
8.7.7.2 Configure the VLAN

A VLAN is a logical network topology that 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, port-based and TAG-based. 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 port’s
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, in the left object tree, select FE_L12 and then Switch. Select the
Services working mode.
2. To create a VLAN, in the VLAN List tab window, click Create. A Create window opens.

3. Enter 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, in the VLAN list, select the VLAN to be edited or deleted, and click Edit or
Delete.
To configure a port’s default VLAN ID:

 In the BG-40 NE Shelf View window, in the left object tree, select FE_L12 and then Switch. In the
Services working mode, select the Port VID tab.
The FE_L12 card’s 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.

8.7.7.3 Configure the vFIB for FE_L12

The FE_L12 filter DB (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.
You 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, see Configure the vFIB of the MESW_6F.

8.7.7.4 Configure the VCG mapping mode

You can configure the VCG mapping mode as VC12_VC3 or EOS VC12_VC3 for the FE_L12 and MGE_1_L1
card.
To configure the VCG mapping mode:

1. In the BG-40 NE Shelf View window, in the left object tree, select the FE_L12 or MGE_1_L1 card. Then
in the Configuration working mode, select the VCG Mapping Mode in NMS tab.
2. In the Mapping Mode list, set the VCG as VC12_VC3 or EOS VC12_VC3, as required.

8.8 Data hybrid cards

The NPT and IP/MPLS platforms support a set of data hybrid GE-based cards. The cards are described in this
section. For details about how to activate or deactivate the ports, see Activate/Deactivate ports.
DHGE_4E/DHGE_8/DHGE_16/DHGE_24
NOTES:
 DHGE_4E/DHGE_8/DHGE_16/DHGE_24 can be assigned in NPT-1800/NPT-1200i.
 DHGE_4E/DHGE_8 can only be assigned in NPT-1200/NPT-1020/NPT-1021 when
CPTS100/CPS100 is assigned.
 DHGE_16/DHGE_24 can only be assigned in NPT-1200 when CPTS100/CPS100 is assigned.
The DHGE card mainly functions PHY of GbE ports, the MAC is located on CPTS/CPS card.
 DHGE_4E is a Data Hybrid card that supports up to 4 x 10/100/100BaseT ports with connection to the
packet switching matrix, with PoE functionality.
 Supported PHY types – 10/100/1000Base-T only
 Support POE functionality
 DHGE_8 is a Data Hybrid card that supports up to 8 x GbE/FX ports with connection to the packet
switching matrix (CSFP for 8 ports, SFP for 4 ports).
 Transceiver (SFP/CSFP) assignment determines the available PHY types.
 By default, DHGE_8 has only 4 ports (Port1~Port4) with OTGBE-SX SFP as default assignment.
 SFP port configuration:
 Supported PHY types: 1000Base-X, 100Base-FX, 1000Base-T, 10/100/1000Base-T
 CSFP port configuration:
 When CTGBE is assigned, Port[n+4] is created.
 Supported PHY types: 1000Base-X, 100Base-FX
 DHGE_16 is a Data Hybrid card that supports up to 8 x 10/100/1000BaseT ports and 8 x GbE/FX ports
with connection to the packet switching matrix (CSFP support for 8 optical ports, SFP for 4 optical ports).
It is a double slot card.
 Port1~Port8: RJ45, 10/100/1000Base-T only, without PoE function.
 Port9~Port12: OTGBE-SX SFP, 1000Base-X as default configuration.
 Same as DHGE_8
 DHGE_24 is a Data Hybrid card supports up to 24 x GbE/FX ports with connection to the packet
switching matrix (CSFP support for 24 optical ports, SFP for 12 optical ports), double slot card with 12
SFP/CSFP slots.
 By default, DHGE_24 has only 12 ports (P1-P12) with OTGBE-SX SFP as default assignment;
 SFP ports:
 PHY types: 1000Base-X, 100Base-FX, 10/100/1000Base-T [P2], 1000Base-T [P2];
 Available SFP assignment per PHY type;

 CSFP ports:
 When CTGBE is assigned, P[n+12] is created;
 Supported PHY types: 1000Base-X, 100Base-FX
 DHGE_20 is a T-slot card with 10/20 x GE/FX ports (SFP/CSFP).
 Support 10x GbE interface Based on SFP modules;
 Support 20x GbE interface Based on CSFP modules;
 Can be assigned in NPT-1800 Platform.
These cards can support Timing Group configuration; see Managing GE Port Groups.
The configuration of GE ETY ports is the same as DMXE_48_L2. By default, the ETY ports of DHGE card are
not activated. You can activate or deactivate the ETY ports manually.
DHFE_12
DHFE_12 can be assigned in NPT-1200/NPT-1020/NPT-1021 when CPTS100/CPS100 is assigned.
Port attributes of DHFE_12 are similar to DMFE_4_L2, except:
 100M half-duplex, 10M half-duplex is not supported;
 Maximum frame length of DHFE_12/DHFX_12 is up to 9736 bytes;
 Port 7#~12#, management and in-band control channel cannot support enhanced scheduling mode;
 Port MCC cannot be enabled (port can be added into the Management VLAN);
 ESMC can be supported.
L2 functionality over DHFE_12 port is similar as DHGE port, except MoE and in-band MCC which are not
supported.
By default, the FE-ETY ports of DHFE_12 card are not activated. You can activate or deactivate the FE-ETY
ports manually.
DHFX_12
DHFX_12 can be assigned in NPT-1200/NPT-1020/NPT-1021 when CPTS100/CPS100 is assigned.
Port attributes of DHFX_12 are similar to DMFX_4_L2, except:
 Maximum frame length of DHFX_12 is up to 9736 bytes;
 Port 7#~12#, Management and in-band control channel cannot support enhanced scheduling mode;
 Port MCC cannot be enabled (port can be added into the Management VLAN);
 ESMC can be supported.
L2 functionality over DHFX_12 port is similar as DHGE port, except MoE and in-band MCC which are not
supported.
By default, the FX-ETY ports of DHFX_12 card are not activated. You can activate or deactivate the FX-ETY
ports manually.

DHXE_2
DHXE_2 is an Ethernet PHY I/O card for Tslot with two SFP+ based 10GE ports, each is configurable between
10GBase-R and 10GBase-W. Sync-E and one-step TC capable are supported in DHXE_2.
By default, the two 10GE-ETY ports of DHXE_2 card are not activated. You can activate or deactivate the ports
manually.
From V6.0, OTN wrapping is supported for 10GE interfaces in DHXE_2.
 Support OTN wrapping for 10GE interfaces in DHXE_2;
 10Gbase-R over OTU2e with BMP mapping to ODU2e;
 Supported FEC types:
 ITU-T G.709 FEC, ITU-T G.975.1 I.4 EFEC, ITU-T G.975.1 I.7 EFEC.
For details about how to activate or deactivate the ports of DHXE_2, see Activate/Deactivate ports.
DHXE_2 with OTN wrapping (Ezchip)

In the NPT-1050/NPT-1200 NEs, add a new PHY type in 10GE ETY port configuration of the DHXE_2 card:
 10GBase-R with OTU2e Mapping
Then the corresponding OTU and ODU objects will be created:
 10GBase- e, ODU2e
The port configuration of OTU2e and ODU2e is the same with MXP10.
DHXE_4
DHXE_4 is an Ethernet PHY I/O card with four SFP+ based 10GE ports that can be configured as 10G Base-R.
It can be assigned in TS slot (except TS5) of NPT-1200 with CPTS320 or CPS320.
By default, the four 10GE-ETY ports of DHXE_4 card are not activated. You can activate or deactivate the
ports manually.
DHCE_1
DHCE_1 is a single HC T-Slot 100GbE card for NPT-1800 without OTN wrap:
 Support 100GbE client interface based on CFP2 and QSFP28 modules
 Available in TS10~TS15 on CIPS1T
 Support 100GBASE-R
 Transceivers Support
 Support CFP2
 OTR100P2_LR4
 Support QSFP28
 QSFP28 PSM4
 QSFP28 CWDM4
 Support terminal/facility loopback
 Support CL91

DHCE_1C
DHCE_1C is a single HC T-Slot 100GbE card for NPT1800 with OTN wrap.
 Support 100GE long distance interface, to provide 80Km and above 100GE link, based on CFP modules
 Available in TS10~TS15 on CIPS1T
 Support 100GBASE-R
 Support 100GBASE-R mapping to OTU4
 Transceivers Support
 Support coherent 100G transceiver
OTR100PT_C1200 (AC100-M CFP)
 Support non coherent 100G transceiver
 OTR100_SR10/SR10DR
 OTR100_LR4/LR4DR
 OTR100_ER10DR/ZR10DR
 Support terminal/facility loopback
8.8.1 Activate/Deactivate ports

This section describes how to activate/deactivate the ports of the DH cards in NPT-1200/NPT-1020/NPT-
1021/NPT-1800/NPT-1200i NEs. The process is also relevant for MGE_12 cards.
To activate/deactivate card ports:

1. In the NE Shelf View window, in the left object tree, right-click one of the following, as relevant:
 DH card
 ETY port under a DH card
 MGE_12 card
 ETY port under MGE_12
2. From the shortcut menu, select Activate/Deactivate Port.
The Activate/Deactivate Port window opens.
3. In the Activate list, select the required checkbox(es) to activate or deactivate the port(s).

4. To batch edit the mode:
a. Click .
b. Click to select the required operation.
5. Click Apply.
8.8.2 Reassign DHXE_2 to DHXE_4/DHXE_4O

DHXE_2 can be reassigned to DHXE_4/DHXE_4O in NPT-1200 with CIPS320, NPT-1800 and NPT-1200i.
To reassign DHXE_2 to DHXE_4/DHXE_4O:

1. In the NE Slot Assignment window, at the lower left-hand corner, select the Reassign radio button.
Then right-click the DHXE_2 card, in the short-cut menu, click Reassign > DHXE_4/DHXE_4O.
2. To save the changes, click Apply.

8.9 EoP cards

There are three EoP cards: the MEOP_4, the MEOP_4H, and the DMEOP_4. This section describes these cards.
8.9.1 MEOP_4/MEOP_4H
The MEOP_4/MEOP_4H is a Dslot module designed for the BG-20B that supports up to four 10/100Base-T
interfaces for Ethernet service with standard Ethernet over PDH (EoP) technology. It maps Ethernet packets
to E1 or E1 virtual concatenation group first, and then maps E1s to VC-12s which are connected to the SDH
matrix of the ADM. The total bandwidth of MEOP_4H is up to 32 E1s.
With limited L2 features, MEOP_4H/MEOP_4 supports both EPL and PB PtP service. It can support two
aggregation groups, each with eight VCGs/EoP channels at the WAN side and two FE ports at the LAN side;
the maximum bandwidth of WAN ports is 16 E1s 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.
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 PtP 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 and it also supports live insertion.

To configure a MEOP_4 card attribute:

1. In a BG-20 NE Shelf View window, in the left object tree, select the MEOP_4 card. In the Configuration
working mode General tab, view the general information of the MEOP_4.

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

a. Set the parameters as required.

b. Click Apply. The settings are saved.
3. To perform VCG configuration, in the left object tree, right-click the MEOP_4 card or an EoP port. From
the shortcut menu, select Create VCG. The VCG Attribute window opens.
In this window configure the virtual cascade mode (E1) and bandwidth of each VCG.

working mode.
For every member of this VCG, the E1s can be deactivated.

5. To view real-time traffic of EoP ports, in the left object tree, select the MEOP_4 card. In the
Maintenance working mode, select the EoP Payload tab.
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.
For the acquired traffic information, the data display unit is specified in bps.

6. To view real-time traffic for ETY ports, in the left object tree, select the MEOP_4 card. In the
Maintenance working mode, select the ETY Payload tab.

7. To perform loopback maintenance, in the Maintenance working mode, select the Loopback tab.
The Loopback Type values are Terminal Loopback, Facility Loopback, and No Loopback (default No
Loopback). To batch edit the loopback type, from the toolbar, click .

8. To configure the link down status for a specific EoP port, in the left object tree, select an EoP port. Then
in the Maintenance working mode, select the Force Link Down tab.
You can set the Link Down Status as Force Link Down or release the force link down maintenance, by
selecting the corresponding radio button.

8.9.2 DMEOP_4
The DMEOP_4 can be inserted into any Tslot in the BG-30B. It is very similar to the MEOP_4 module for the
BG-20B Dslot, except for backplane interface. It has:
 Two ESSI buses: one connected to XIO30 A and the other to XIO30 B.
 The same redundancy design as the BG-30B module (like the PME1_21).
8.10 Matrix cards

8.10.1 XIO30-1/XIO30-4/XIO30-4B/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. From a
logical perspective, therefore, there is always one main XIO30 card and one standby XIO30 card.
In order to distinguish the XIO30-4 card supporting 6 x VC-4 and the XIO30-4 card supporting 8 x VC-4, XIO30-
4 is redefined and a new card type, XIO30-4B, is created. XIO30-4B is created for management purposes only;
it is not a true new card type.
In the LCT-NPT, features of XIO30-4B are exactly the same as XIO30-4.
XIO30-4 can be reassigned to XIO30-4B without affecting traffic.
The ADM rate is decided by the XIO30 card type:
 XIO30-1: ADM-1
 XIO30-4: ADM-4
 XIO30-4B: 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 (the same
as SMQ1&4).
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, XIO30-4B, or XIO30-16 without removing existing traffic.
 XIO30-4 can be reassigned to XIO30-1, XIO30-4B, or XIO30-16 without removing existing traffic.
 XIO30-4B can be reassigned to XIO30-16 without removing existing traffic.
You can perform reassignment from the Slot Assignment window.

To reassign XIO30-1 and XIO30-4:

3. Right-click the XIO30-1/XIO30-4 card in the XS A slot and select a card in the popup list to reassign.

4. Click Apply. A confirmation popup opens.
8.10.2 XIO64/XIO16_4
There are two types of XIO cards in BG-64/NPT-1200, each supporting different aggregate bandwidth and
matrix capacity. The XIO types are as follows:
 XIO64: supports a 40 Gbps matrix and an STM-64 XFP-based aggregate interface with OTN support.
 XIO16_4: supports a 40 Gbps matrix and 4 x STM-1/4/16 SFP-based aggregate interface.
In BG-64, you can perform the reassignment from XIO16_4 to XIO64.
In NPT-1200, you can perform the following reassignment:
 XIO16_4 to XIO64
 XIO64 to CPTS100 with SAM10
 XIO16_4 to CPTS100 with SAM25_2 (supports configuring port mappings)
NOTE: The reassignment is not allowed when there is MSP 1+1 PG or MS-SPRing PG created on
XIO16_4.

To reassign from XIO16_4 to XIO64 in BG-64/NPT-1200:

1. In the NE Shelf View window, in the left object tree, select the NE, and select Configuration and then
Slot Assignment.

3. Right-click the XIO16_4 card in the XS A or XS B slot and from the shortcut menu, select Reassign and
then XIO64.
4. Click Apply. A confirmation window opens prompting you to confirm this reassignment.
NOTE: For Ethernet Only NE connection mode, reassignment from XIO16_4 to XIO64 can be
performed without any other configuration. For Gateway or DCC Only NE connection mode,
reassignment of XIO16_4 is not allowed due to port 1 must have termination DCC XC.

To reassign from XIO64 to CPTS100 with SAM10 in NPT-1200:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select the NE, and select Configuration
and then Slot Assignment.

3. Right-click the XIO64 card in the XS A or XS B slot and from the shortcut menu, select Reassign and then
CPTS100.

To reassign from XIO16_4 to CPTS100 with SAM25_2 in NPT-1200:

1. Before performing the reassignment from XIO16_4 to CPTS100, you can configure the reassignment
option settings for the reassignment, as required.
2. In the NPT-1200 NE Shelf View window, in the left object tree, select the NE, and select Configuration
and then Reassignment Option Settings. The Reassignment Option Settings window opens.

3. Configure the port mappings for the reassignment as required, by selecting the ports from the
dropdown lists.
Click OK to save your settings.

4. To perform reassignment, in the NPT-1200 NE Shelf View window, in the left object tree, select the NE,
and select Configuration and then Slot Assignment.

6. Right-click the XIO16_4 card in the XS A or XS B slot and from the shortcut menu, select Reassign and
then CPTS100.
Click Yes to confirm.

8.10.3 CPTS100/CPS100
CPTS100 is a dual-matrix card for NPT-1200, which consists of central SDH matrix, central packet matrix, SDH
and Ethernet aggregate ports, system timing unit, IEEE1588v2 PTP clock unit, and an EOS module between
SDH and packet matrix.
CPS100 is a pure central packet switch card with 2 x 10GE aggregate interfaces, packet switching matrix and
timing unit, without TDM functionality. CPS100 is simplified CPTS100 by partially assembling CPTS100 card,
with following modules moved from CPTS100: SDH matrix, SDH aggregate ports and EoS module.
The following window shows the CPTS100 management objects containment relationship.
Figure 8-4: CPTS100 management objects containment relationship
CPTS100 is equipment object and equipment holder, it represents the card (circuit Pack) itself (the physical
attributes), and contains a number of virtual cards (functional blocks). The equipment CTPS100 operational
state affects the operational state of all virtual cards it contains.
 TMU100 is a virtual card which represents the SEC & EEC function and contains T3/T4 interfaces;
 SAM is equipment holder which can contain either SAM10 or SAM25_2:
 SAM10 is a virtual card which contains a STM-64 port with optional OTU2 encapsulation; The STM-
64 port contains a XFP module;
 SAM25_2 is a virtual card which contains two STM-1/4/16 with optional OTU1 encapsulation
(OTU1 is for STM-16 only); each STM-1/4/16 port contains a SFP module;
 HLXC40 is a virtual SDH cross-connect card which represents the 45G Ho/Lo matrix ("fabric"), which
may contains a connection-list (XC list);
 HEOS_16 is a virtual EoS card which contains 16 EoS ports;
 CPS100 represents the 100G packet switch of central PE;
 AMXE_2 is a virtual card which contains two 10GE ports with optional OTU2/OTU2e/OTU1e
encapsulation; each port contains a SFP+ module;
 PTP-TMU100 represents the 1588 PTP function block and contains 1pps and ToD interfaces.

8.10.3.1 Reassign CPTS100 to CPS100

You can reassign CPTS100 to CPS100 when no native TDM is configured.
To reassign CPTS100 to CPS100:

Then right-click the CPTS100 card, in the short-cut menu, click Reassign > CPS100.
8.10.3.2 AMXE_2
AMXE_2 is a virtual card which contains two 10GE ports with optional OTU2/OTU2e/OTU1e encapsulation,
which is created by default with CPTS100/CPS100. Each port of AMXE_2 contains a SFP+ module. By default,
the two ETY ports of AMXE_2 are not activated. You can activate the ports as required.
To activate/deactivate ports for AMXE_2:

1. In the NPT-1200 NE Shelf View window, in the left object tree, right-click the AMXE_2 card, or right-
click an ETY port under AMXE_2, and from the shortcut menu, select Activate/Deactivate Port. The
Activate/Deactivate Port window opens.

2. In the relevant Activate dropdown list, select Active/Inactive as required.
3. To batch activate/deactivate the ports, on the toolbar, click . Then click to select the required
operation as you need.
8.10.3.3 HEoS_16
HEoS_16 is a logical card in NPT-1200, which is created implicitly when CPTS100/CPTS320 card is assigned.
Figure 8-5: EoS subsystem management - HEoS_16
HEoS_16 belongs to the central PE. With HEoS_16 the central PE of NPT-1200 can support MoT and EoS ports
as well, like the EoS of DMXE card in terms of features.

 Defined as regular MoT/EoS port of CPTS100/CPTS320;

 Defined as internal MoT/EoS to connect two PEs (CPTS100/CPTS320 to other MPLS card).
Besides the regular attributes of EoS ports (same as the EoS ports of DMXE_48_L2), each port of HEoS_16
has a special attribute - Connection Domain, which specifies the target matrix that the EoS port will connect.
By default, the EoS ports of HEoS_16 are not activated. You can activate or deactivate the EoS ports manually.
To activate/deactivate ports for HEoS_16:

1. In the NPT-1200 NE Shelf View window, in the left object tree, right-click the HEoS_16 card, and from
the shortcut menu, select Activate/Deactivate EoS Module. The Activate/Deactivate EoS Module
window opens.
2. Select Activated or Deactivated radio button as required.


To configure the VCG attributes of HEoS_16:

1. Assign the CPTS100/CPTS320 card in NPT-1200 NE. In the NE Shelf View window, in the left object tree,
right-click the HEoS_16 card and select Create VCG.

2. In the Traffic tab, you can set the Map Level (can only be VC-4), Bandwidth, and Connection Domain as
required.
The Connection Domain can be set as Central SDH Matrix or Special for E-slots (default is Central SDH
Matrix).
 Central SDH Matrix: the EoS port is connected to CORE SDH XC matrix WSE40.
 Special for E-slots: the EoS port is specially for connecting E-slot card through TSE matrix.

8.10.4 CPTS320/CPS320
CPTS320 is a central packet and TDM hybrid switching matrix card with timing unit, one XFP based STM-64
aggregate interface or two SFP based STM-1/4/16 aggregate interfaces, four SFP+ based 10GE ports.
CPS320 is a central packet switching card with timing unit and four SFP+ based 10GE ports. If CPS320 is
assigned, the NPT-1200 NE is pure packet.
8.10.4.1 Reassign CPTS320 to CPS320

You can reassign CPTS320 to CPS320 when no native TDM is configured.
To reassign CPTS100 to CPS100:

Then right-click the CPTS320 card, in the short-cut menu, click Reassign > CPS320.
8.10.4.2 AMXE_4
8.10.5 CPS50
CPS50 card is a L2 data card in Tslot of NPT-1020/NPT-1021. It upgrades the system packet switching capacity
to 50Gbps (based on Single PE model), supports 2 x 10GE (SFP+) and 2 flexible SFP house (each can support
1 x 10GE SFP+, or 1 x GE SFP or 2 x GE CSFP).
CPS50 includes following two built-in ETY interfaces:
 2 x SFP+ with 10GbE interface;
 2 x SFP+/CSFP/SFP. It is two flexible SFP house, each one can support 1 x 10GbE SFP+, or 1 x GbE SFP or
2 x GbE CSFP according to SFP setting.
8.10.5.1 Enable CPS50 switch engine

After CPS50 is assigned, and CS10 is in Bslot, only information of card general, SFP inventory and alarms can
be viewed. You need an additional command of "Enable Switch Engine" to switch CS10 to CS50 to manage
the CPS50 card.
This section describes how to enable CPS50 switch engine.

To enable CPS50 switch engine:

1. In the NPT-1020/NPT-1021 NE Shelf View window, assign CPS50 in Tslot.
2. In the NE Shelf View window, you can view the CPS50 in Tslot and CS10 in Bslot.

3. To enable switch engine, in the left object tree, right-click CPS50 and from the shortcut menu, select
Enable Switch Engine.
4. A confirmation window opens prompting you to confirm the operation.

5. Click Yes to confirm, and the CS10 is switched to CS50 in the Bslot, as shown in the following figure.

8.10.5.2 Activate/Deactivate the ports

After CS10 is switched to CS50 as described in Enabling Switch Engine, you can manage the CPS50 card.
By default, the ETY ports of DHGE card are not activated. You can activate or deactivate the ETY ports
manually. For details about activating or deactivating the CPS50 ports, see Activating/Deactivating the Ports.
8.10.5.3 Configure SFP/SFP+/CSFP settings

In CPS50, Port1 and Port2 are fixed SFP+ interfaces; and for Port3 and Port4, the expected SFP type is
configurable to SFP, SFP+ and CSFP. Comply with CSFP common management rule, once the expected SFP
type is CSFP on GE Port1/2, GE Port 3/4 will be created from LCT-NPT.
To configure SFP/SFP+/CSFP settings:

1. You can configure the SFP/SFP+/CSFP settings for the Port 3 and Port 4 of CPS50, with port activated.
2. To define port rate and density, in the left object tree, right-click CPS50 and select Define Port Rate and
Density. The Define Port Rate and Density window opens.
Cage1 and Cage2 are not editable. Cage3 and cage4 are editable, and there are three options:

 Single GE --SFP
 Single 10GE --SFP+
 Dual GE --CSFP
Note that the expected SFP type should be configurable before the port is activated.
3. For Cage3 and Cage4, set the port rates as SFP, SFP+ or CSFP from the dropdown lists and click Apply
to save the settings.

4. Once the expected SFP type is CSFP on GE Port1/2, GE Port 3/4 is created. You can view the new created
port (Port 7 under DHGE_8) in the left object tree, as shown in the following figure.

5. In the NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select an activated GE/10GE
port of CPS50. Then in the Configuration working mode, select the SFP Setting/SFP+ Setting tab.
6. Set Expected SFP Type and Expected Application Code as required from the corresponding dropdown
list.
8.10.5.4 Roll back CS50 to CS10

LCT-NPT enables you to roll back CS50 to CS10, as described in this section.

To roll back CS50 to CS10:

1. In the NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select the NE. Then in the
shelf menu, select Maintenance, Advanced and then Rollback to CS10.
2. A Confirmation window opens prompting you to confirm the rollback operation.

3. To confirm rollback, click Yes. The CS50 is rolled back to CS10 in Bslot as shown in the following figure.
8.10.6 CS10
CS10 is the central packet matrix with 10G bps capacity in MXC-1020.
8.10.6.1 MEoS_8
MEOS_8 module is embedded in MXC-1020, which supports up to 8 EOS channels with a total bandwidth of
622M.
Figure 8-6: EoS subsystem management - MEoS_8
In the preceding figure, MEOS_8 module supports up to 8 EoS ports, the port role can be as MoT port for
MPLS NE or EoS port for PB NE.
By default, the EoS ports of MEoS_8 are not activated. You can activate or deactivate the EoS ports manually.

To activate/deactivate ports for MEoS_8:

1. To activate/deactivate the ports, in the NPT-1020 NE Shelf View window, in the left object tree, right-
click the MEoS_8 card, and from the shortcut menu, select Activate/Deactivate EoS Module. The
Activate/Deactivate EoS Module window opens.
2. Select Activated or Deactivated radio button as required.

8.10.7 CS5
CS5 is the Central PE in NPT-1010 NE.
8.10.7.1 MGE_8
MGE_8 is a virtual card with 8 GbE interfaces in CS5. It has four POE+ 10/100/1000Base-T ports and four SFP
based Gbe ports. By default, the ETY ports of MGE_8 are not activated. You can activate or deactivate the
ETY ports manually.
L2 function of the ETY GE ports in MGE_8 is the same as the ETY GE ports in DHGE_8, which can support:
 Management VLAN
 VSI
 Tunnel XC
 MSTP Port
 BFD Section Session
 Port Mirror
 QB
 vFIB

To activate/deactivate ports for MGE_8:

1. In the NPT-1010 NE Shelf View window, in the left object tree, right-click the MGE_8 card, or right-click
an ETY port under MGE_8, and from the shortcut menu, select Activate/Deactivate Port. The

2. In the relevant Activate list, select checkboxes as required.

8.10.8 MCPTS100/MCPS100
In NPT-1050, control module (MCP) and matrix cards (including TDM & packet) and TMU module are located
on same card – MCPTS100 or MCPS100, which can be assigned in MXS A and MXS B. MCPTS100/MCPS100 is
the control and hybrid matrix card with TMU-100G fan out in NPT-1050.
Control and Matrix card assignment will decide the system traffic model – hybrid (dual core) or pure packet
(single core); redundant or non-redundant of MCP and CPTS. Aggregate Interface Module (AIM) can be
assigned in MXS slot as well in order to support ADM in 1+0 configuration.
Figure 8-7: NPT-1050 NE Matrix card configuration
Pure Packet Mode

Pure packet mode means supporting packet plane only, not native TDM (SDH) is supported.
Pure packet mode is decided by:
 NE type (which is decided by backplane type ID). If NE type is NPT-1051, it is pure packet.
 Framing mode. If framing mode = SONET/DS1, it must be pure packet.
 If NE type is NPT-1050 and framing mode is SDH/E1, it is decided by MXS A and MXS B assignment. If
MCPS is assigned, it is pure packet.
The following verification rules are applied in pure packet mode:
 Only MCPS/AIM can be assigned in MXS A/MXS B;
 Native TDM cards cannot be assigned in TS and ES:
PME1_63, PME1_21, PM345_3, SMQ1, SMQ1&4, SMS16
PE1_63, P345_3E, S1_4, MPoE_12G, SM_10E
TPS1_1, TP63_1
 Ethernet I/O cards (DH cards), CES cards, optics/OTN cards can be assigned:
DHGE_4E, DHGE_8, DHGE_16, DHGE_24, DHXE_2, DHXE_4 (MCPS200);
DHFE_12, DHFX_12
MSC_2_8, MSE1_16, DMCE1_32, EM_10E
OBC, MXP10

SONET/DS1 Framing Mode

All pure packet verification rules are followed. CES cards that don't support OC-n/T1 interface cannot be
assigned:
 DMCE1_32
 DMCES1_4
The following table lists the assignments supported in MXS A and MXS B in NPT-1050.
Table 8-13: MXS A and MXS B assignment

Valid Assignment SONET/DS1 Mode NE Configuration
MXS A MXS B
MCPTS100 None Not supported 1+0 100G Hybrid
MCPTS100 AIM100 Not supported 1+0 100G Hybrid
None MCPTS100 Not supported 1+0 100G Hybrid
AIM100 MCPTS100 Not supported 1+0 100G Hybrid
MCPTS100 MCPTS100 Not supported 1+1 100G Hybrid
MCPS100 None Supported 1+0 100G Pure Packet
MCPS100 AIM100 Supported 1+0 100G Pure Packet
None MCPS100 Supported 1+0 100G Pure Packet
AIM100 MCPS100 Supported 1+0 100G Pure Packet
MCPS100 MCPS100 Supported 1+1 100G Pure Packet
NOTE: Double card (DHGE_24 and DHGE_16) can be assigned in TS1 or TS2:
 If it is assigned in TS1, then TS2 must be empty (unassigned);
 If it is assigned in TS2, then TS3 must be empty (unassigned).
8.10.8.1 SAM16T
SAM16T is the SDH module with one SFP based STM-1/4/16 aggregate interface, which is contained in
MCPTS100 or AIM100. Rate of SAM16T can be configured between STM-16, STM-4 and ATM-1.
8.10.8.2 AMXE_24
AMXE_24 is the Ethernet aggregate module with two SFP+ based 10 GE ports and four Gbe ports (CSFP
based), which is contained in MCPS100/MCPTS100 of NPT-1050.
Management of AMXE_24 is generally the same as AMXE_2, while the GE ETY port configuration of AMXE_24
is the same as DHGE_8.
By default, the four ETY ports of AMXE_2 are not activated. You can activate the ports as required.

To activate/deactivate ports for AMXE_24:

1. In the NPT-1050 NE Shelf View window, in the left object tree, right-click the AMXE_24 card and then
select Activate/Deactivate Port. The Activate/Deactivate Port window opens.

2. In the relevant Activate dropdown list, select Active/Inactive as required.
3. To batch activate/deactivate the ports, on the toolbar, click . Then click to select the required
operation as you need.

8.10.8.3 Manage MNG port
Manage MNG port protection mode

The MNG port is a 10/100/1000Base-T Ethernet port connected to MCP CPU.
The MNG port protection mode includes:
 1:1 Protection (L2 based) – default
 1+1 Protection (L3 based)
MNG Port 1+1 Protection
In MCPTS100/MCPS100 1+1 configuration, each MCPTS100/MCPS100 has one MNG port, MNG port
protection is supported. When NPT-1050 NE is the gateway, either MNG port can be used to connect
DCN/EMS, or two MNG ports can be connected to L2/L3 DCN (DCN switch/router needs to allocate two ports
for gateway NE) simultaneously for MNG port redundancy. For local maintenance, the management laptop
(EMS/LCT/CLI) can be connected to either MNG port.
In 1+1 configuration, both MNG ports are actually connected to the active MCP, and the MNG interface on
standby MCP should be set to "down".
Figure 8-8: MNG port protection
The following describes some definitions from the view of active MCPTS100/MCPS100:
 Local MNG port – the MNG port on local card (P0 of the switch)
 Mate MNG port – the MNG port on mate card (P1 of the switch, connected to P0 of mate switch)
 Port failed – means the port is physically disconnected to the switch on active card.
 "Local MNG port failed" is usually caused by link down on PHY or port disabled;
 "Mate MNG port failed" may have following reasons: port disabled, link down on mate PHY or link
down detected on SGMII link between two switches (link down on local P1).
 Port OK – means the port link is up and free of physical failure from the switch to cable.

MNG Port 1:1 Protection

This protection mode can be used if two MNG ports are connected to a L2 switch (or two switches in L2 DCN)
in order to eliminate the possible Ethernet loop.
Figure 8-9: MNG port 1:1 protection
In this protection mode, both MNG ports are working as usual, no Ethernet loop elimination mechanism is
supported.
MNG Port redundancy can be achieved via:
 OSPF without VRRP (with two Edge routers)
 VRRP (with two Edge routers) – OSPF (or other IGP) is not mandatory
To manage MNG port protection mode:

1. In the NPT-1050/NPT-1800/NPT-1200i NE Shelf View window, in the left object tree, select NPT-
1050/NPT-1800/NPT-1200i.
2. Click the Configuration menu and then select Mng Port Protection Mode. The Mng Port Protection
Mode window opens.
3. Select a protection mode as required by selecting the corresponding radio button.


Configure MNG port parameters

The MNG port is automatically created under MCPS100/MCPTS100 in NPT-1050.
To configure MNG port:

1. In the NPT-1050 NE Shelf View window, in the left object tree, under MCPS100/MCPTS100, select MNG
Port.
2. Click Configuration and then select the General tab.
3. To enable or disable the MNG port, from the Port Enable dropdown list, select Enable or Disable as
required.

8.10.8.4 Perform redundancy

To perform redundancy:
1. In the NPT-1050 NE Shelf View window, in the left object tree, select MCPTS100/MCPT100 in MXS A
slot.
2. Click Configuration and then select the Redundancy tab. The parameters of redundancy are displayed.
3. Configure the settings as required.

4. To synchronize the data, click .

8.11 Aggregate card

8.11.1 AIM100/AIM100P
Two logical card types are defined for AIM100:
 AIM100 – Represents the AIM100 in hybrid NPT
 AIM100P – Represents the AIM100 in pure packet NPT
AIM100/AIM100P is the aggregate interface module card for NPT-1050, with two SFP+ based 10GE ports,
four CSFP based Gbe ports and one SFP based STM-1/4/16 interface.
AIM100 must be assigned together with MCPTS100, while AIM100P must be assigned together with
MCPS100. Note that physical card type is always AIM100; there is no actual card type of AIM100P. It means
the logical card types of AIM100 and AIM100P are compatible with the physical card of AIM100.
8.12 NFV cards

This section describes the Network Function Virtualization (NFV) card in LCT-NPT.
8.12.1 NFVG_4
NFVG_4 is a Network Function Virtualization (NFV) card with 4 x GE, each can be from either front panel SFP
or from SGMII of backplane.
NFVG_4 can be installed and assigned in following slots and shelves:
 NFVG_4 can be assigned in Tslot of NPT-1020 and NPT-1021;
 Applicable to TS1 only
 Backplane Bandwidth: 4 x 1.25G SGMII
 Control interface: FE and MPC
 NFVG_4 can be assigned in Tslot of NPT-1050;
 Applicable to TS1, TS2, TS3
 Control interface: MPC
 NFVG_4 can be assigned in Tslot of NPT-1200;
 Applicable to TS1, TS2, TS3, TS4, TS6, TS7
 Control interface: FE and MPC
 Note that NFVG_4 can be assigned regardless of the matrix card type in NPT-1200, it means
NFVG_4 can be supported in XIO16_4/XIO64/CPTS/CPS system.

By default, all ports of NFVG_4 are deactivated. NFVG_4 supports up to four GE ports, each port can be
assigned as one of following roles during creation (activation):
 Local port
 Service port
 Internal port
When you activate a port on NFVG_4, you must assign the port role – service port or local port or internal
port. Local port of NFVG_4 has no L2 attributes. Service port and internal port are same as other DH card
ports. The service port can be defined as any type (UNI, I-NNI, E-NNI, MoE, etc.), and any service can be
created on service port. For service created on service port, it is same as service created on DH port.
It is not allowed to change the port role from service port to local port or from local port to service port
directly, and you must deactivate the port first.
To activate the ports of NFVG_4:

1. In the NE Shelf View window, in the left object tree, right-click an NFVG_4 card, or right-click an ETY
port under the NFVG_4 card, then from the shortcut menu, select Activate/Deactivate Port. The

2. In the port list, select a port you want to activate. In the area illustrated in the following figure, select
the Activate checkbox and then from the Port Role dropdown list, set the port role as Local Port,
Service Port or Internal port as required.

3. To save the settings, click Apply. Then you can view the relevant attributes of the activated ports from
the window.

To deactivate a port of NFVG_4:

1. In the Activate/Deactivate Port window, in the port list, select an activated port, then in the following
area of the window, unselect the Activate checkbox.
8.12.1.1 Create an NFV LAG

This section describes how to create an NFV LAG for service ports of NFVG_4 in NPT-1200. If the ports of
NFVG_4 are activated as Internal port, the NFV LAG is created automatically.
1. In the NPT-1200 NE Shelf View window, assign the NFVG_4 cards.

2. Activate the ports of NFVG_4 as Service port.

To create an NFV LAG:

1. In the NPT-1200 NE Shelf View window, right-click the CS module, and then select Create LAG. The
Create/Edit Aggregation Ports window opens.
2. From the Aggregation Group dropdown list, select a LAG name.

3. Select Master and Slave port members for the NFV LAG.
Refer Create a LAG for details.
4. Click Apply to save the NFV LAG.

8.12.2 NFVX card

The NFVX card has no physical port. There are two 10GE ports in the card, and only internal port can be
activated.
Other features are similar as NFVG_4.
8.13 CES cards

This section describes the CES cards which can provide CES services.
The CES cards can work in standalone or integration mode (default is Integration mode.):
 When CES cards work on integration mode, iETY, iEOS, SGMII interface can be used for network
interface for CES service. CES card and L2 (or CPTS) card work together to setup CES services.
 When CES cards work on standalone mode, only the ETY port in front panel (named eETY port) can be
used. It is for CES over ETY application. The CES card always interconnects with 3rd party device directly.
 For the MSE1_16 and EM_10E card, only integration work mode is supported.
8.13.1 DMCE1_32
DMCE1_32 is a multiservice E1 CES card that can be assigned in any Eslot of BG-20E/BG-30E/EXT-2U/BG-
20EH.
In DMCE1_32, each E1 interface can be mapped to an E1 port. The E1 port can be PPI (Front Panel) or VC-12
(Central XC Matrix), as indicated in the following figure.
Figure 8-10: E1 Interface of DMCE1_32
When an E1 channel from Central XC Matrix is selected, the corresponding VC-12 object can be managed,
including configuration, maintenance, PM, and alarms. You can also further configure an XC for the VC-12
(like a VC-12 in a regular E1 of a PDH card).

To configure DMCE1_32 card attributes:

1. In the NE Shelf View window, select the DMCE1_32 card in the left object tree. In the General tab under
Configuration working mode, view the general information of the DMCE1_32 card.

2. To set the work mode of DMCE1_32, in the Configuration working mode, select the Card Parameters
tab. Set the Work Mode as Integration or Standalone and enable/disable the MAC SA Check if required.
The following window shows the Integration work mode view (by default).

The following window shows the Standalone work mode view of DMCE1_32. There is a Switch module
under the DMCE1_32 card, which can be viewed from the left object tree.

3. To perform Switch configuration, in the left object tree, select the Switch module. In the Configuration
working mode, select the General tab.
a. Set the Encapsulation Mode as CESoETH or CESoIP as required, and then set the Ethernet
Network ID.

4. To configure the eETY port:

a. When the Encapsulation Mode is set as CESoETH, in the left object tree, select the GE-ETY port
under DMCE1_32, then in the Configuration working mode, select the General tab.
In the CESoETY Attributes area, set the parameters for the eETY port. Click Apply to save the
settings.

b. When the Encapsulation Mode is set as CESoIP, in the left object tree, select the GE-ETY port
under DMCE1_32, then in the Configuration working mode, select the General tab.
In the CESoETY Attributes area, set the parameters for the eETY port. Click Apply. The settings
are saved.

5. To set the traffic path for the E1 ports of DMCE1_32, in the Configuration working mode, select the
Traffic Path tab.
To batch edit the traffic path, on the toolbar, click .

Or, in the left object tree, select the E1 port, then in the Configuration working mode, select the Traffic
Path tab.

 From the dropdown lists, set the Traffic Path as Front Panel or Central XC Matrix (default Front
Panel). If you set the Traffic Path of an E1 port as Central XC Matrix, the VC12 MO of the E1 port
can be managed.
6. To configure the E1 port, in the left object tree, select the E1 object under an E1 port. In the
Configuration working mode, select the General tab.

a. From the relevant dropdown lists, configure the frame mode and Tx clock mode.
b. Click Apply.
7. To manage the E1 PM threshold, select the NE in the left object tree, and then select Performance,
Performance Settings, and SDH TCA Threshold tab.

a. Set the threshold for MSM E1.

8. To configure the SD or EXC for the E1, select the SD/EXC tab.

a. Set the value for E1 as required.

9. To set the VC12, in the Configuration working mode, select the TTI and TSL tab.
a. To acquire the information to view and set the parameters as required, on the toolbar, click
.
b. To batch edit the relevant attributes, on the toolbar, click .


10. To configure the timing settings, select the Timing Setting tab under the Configuration working mode.
From the dropdown list, the Differential Timestamp Frequency can be set as 19.44 MHz or 25 MHz
(default is 19.44).
8.13.2 DMCES1_4
DMCES1_4 is a multiservice STM-1 CES card. It can be assigned in the Tslots of BG-30B and BG-64/NPT-
1200/NPT-1020/NPT-1021, with the following limitations:
 DMCES1_4 can be assigned in any free Tslot (except Tslot 5) in BG-64.
 DMCES1_4 can be assigned in the Tslot in NPT-1020/NPT-1021.
 DMCES1_4 can be assigned in Tslot 1~7 (except Tslot 5) in NPT-1200.
 DMCES1_4 can be assigned in BG-30 only when the MCP is MCP30B.
 DMCES1_4 can be assigned in BG30 with any XIO card.

In DMCES1_4, each STM-1 interface can be defined as External (Front Panel) or Internal (Central XC Matrix),
as indicated in the following figure.
Figure 8-11: STM-1 Interface of DMCES1_4
If an STM-1 from Front Panel is selected, the corresponding SFP, SPI, RS, MS, VC-4, 63 VC-12, and E1 objects
can be managed. If a VC-4 from Central XC Matrix is selected, only the corresponding 63 VC-12 and E1 objects
can be managed, and you can configure XC for each VC-12 inside (like a VC-12 in a regular STM-1 SDH
interface card).
STM-4 is support in DMCES1_4 from LCT-NPT v3 (v16). STM-1/STM-4 mode is configurable and only the first
SFP port of DMCES1_4 can support STM-4 mode.

To change the rate for DMCES1_4:

1. In a BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select
the oport1 under DMCES1_4. In the Configuration working mode, select the Rate Setting tab.
2. To obtain and view information from the DB, on the toolbar click .
3. Select the Change rate to STM-4 button as required.

To configure DMCES1_4 card attributes:

1. In the NE Shelf View window, select the DMCES1_4 card in the left object tree. In the General tab under
Configuration working mode, you can view the general information of the DMCES1_4 card.

2. To set the work mode of DMCES1_4, in the Configuration working mode, select the Card Parameters
tab. Set the Work Mode as Integration or Standalone and enable/disable the MAC SA Check if required.
The following window shows the Integration work mode view (by default).

The following window shows the Standalone work mode view of DMCES1_4. There is a Switch module
under the DMCES1_4 card, which can be viewed from the left object tree.

3. To perform Switch configuration, in the left object tree, select the Switch module. In the Configuration
a. Set the Encapsulation Mode as CESoETH or CESoIP as required, and then set the Ethernet
Network ID.

4. To configure the eETY port:

a. When the Encapsulation Mode is set as CESoETH, in the left object tree, select the GE-ETY port
under DMCES1_4, then in the Configuration working mode, select the General tab.
settings.

b. When the Encapsulation Mode is set as CESoIP, in the left object tree, select the GE-ETY port
under DMCES1_4, then in the Configuration working mode, select the General tab.
settings.

5. To set the traffic path for the optical ports of DMCES1_4, in the Configuration working mode, select
the Traffic Path tab.

Or, in the left object tree, select the optical port, and in the Configuration working mode, select the
Traffic Path tab.

 From the dropdown lists, set the Traffic Path as Front Panel or Central XC Matrix (default Front
Panel).
6. To configure the E1 port, in the left object tree, select the E1 object under an E1 port. In the

a. From the relevant dropdown lists, configure the frame mode and Tx clock mode.
b. Click Apply.
7. To configure the TTI and TSL settings of RS and VC4s, in the Configuration working mode, select the TTI
and TSL tab.
a. To acquire information to view and set the parameters as required, on the toolbar, click .
b. To batch edit the TTI Detection attribute, on the toolbar, click .


8. To configure the timing settings, select the Timing Setting tab under the Configuration working mode.
From the dropdown list, the Differential Timestamp Frequency can be set as 19.44 MHz or 25 MHz
(default 19.44).
8.13.2.1 DMCES1_4 Cross Card APS1+1

DMCES1_4 cross card APS1+1 (X-MSM) can be support in NPT-1200. In NPT-1200 with CPTS100/CPS100,
DMCES1_4 card in any two Tslots except Tslot5 can comprise one cross card APS 1+1 PG.
Two DMCES1_4 cards can be defined as a protection group to provide full protection for TDM interfaces and
CES IWF:
 Supporting cross-card MSP1+1 for STM-1/4 port protection;
 Supporting card protection in case of card failure (card out, card reset, card BIT, etc.).
Four STM-1 MSP1+1 PGs or one STM-4 MSP1+1 PG can be supported with two DMCES1_4 cards.
Cross card PG can be created only when:
 MSM card is working on integration mode;
 MSM card is attached to central PE by SGMII;
 STM-n/OC-n ports are only from front panel.

Cross card PG cannot be created when:

 MSM card is working on standalone mode;
 MSM card is attached to other PE by external Ethernet cable (iETY);
 Any VC-4 interfaces on MSM card are from Central XC Matrix.
Cross card PG can be created even if one MSM card carries traffic, but cannot be created when both two
MSM cards carry traffic.
Figure 8-12: CES packet traffic SGMII interface in DMCES1_4
Refer to upper figure, two SGMII interfaces at one DMCES1_4 card, are connected to active/standby
CPTS/CPS card respectively.
For cross card APS1+1 Scheme, SGMII from both working and protection DMCES1_4 card are using as the CES
traffic interface. When active DMCES1_4 card is switching over, the active SGMII interface won't be changed.
NOTE: Limitations:
 The port number of two STM-1 ports in the PG must be same, that means the two ports in
MSP1+1 PG are fixed to P1-P1, P2-P2, P3-P3 and P4-P4;
 TDM interface must be from front panel;
 Standalone mode is not supported;
 Integration with central PE only - the DMCES1_4 must be attached to central switch
through SGMII backplane connection;
 This feature is supported in NPT-1200 CPTS100 or CPS100 system only.

1. Check both cards are working in Integration mode.

2. Check both cards are attached to central PE by SGMII.

a. In the NPT-1200 NE Shelf View window, right-click the central PE and select Attach CES Cards.

b. In the Associate CES Cards window, set both Attaching Connection of CES cards as Backplane HW
connection.

3. Check STM-n/OC-n ports of both cards are only from front panel.

4. Check protection cards has no VSI, no maintenance or no timing sources.

5. Check Differential Timestamp Frequency are the same for both cards.

To create a cross card PG:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select the NE. Then in the Configuration
working mode, select the MSP-Linear tab.

2. To create a cross card PG, from the toolbar, click . The Create PG window opens.

3. Select one DMCES1_4 card as main card, and one as protecting card.

4. Click Apply to create the PG.

5. Close the Create PG window, you can view the created cross card PG and all the port-level PGs in the
MSP-Linear list.

6. To perform maintenance commands, right-click one of the port-level PGs and then select a command
as required.
The following switch commands are provided:

 Release – Clears all of the switch commands listed below, for the channel or channels specified in
the command.
 Lockout of Protection – Prevents any of the main channels from switching to the protection line
by issuing a Lockout of Protection request.
 Forced Switch to Protection – Switches the specified main channel to the protection line unless
a request of equal or higher priority is in effect by issuing a Forced Switch request.
 Forced Switch to Main – Switches the main channel back from the protection line to the main
line unless a request of equal or higher priority is in effect, by issuing a Forced Switch request for
the null channel.
 Manual Switch to Protection – Switches the main channel to the protection line unless a request
of equal or higher priority is in effect, by issuing a Manual Switch request.
 Manual Switch to Main – Switches the main channel back from the protection line to the main
line unless a request of equal or higher priority is in effect, by issuing a Manual Switch request for
the null channel.

8.13.3 MSE1_16
In order to provide low cost CES service capability for NPT-1020/NPT-1021 product, a Tslot MSM card
integrated with E1 interfaces is necessary. MSE1_16 is a multi-service card for Tslots in NPT-1200/NPT-
1020/NPT-1021 with 16 x E1 interfaces in front panel, which can be assigned to the Tslot of NPT-1020/NPT-
1021 and Tslot 1~7 (except Tslot 5) in NPT-1200.
Main features of MSE1_16 card are as follows:
 Support 16 balanced E1/T1 interfaces. External xDDF_21 is used to provide unbalanced E1 interfaces;
 Support CESoETH and CESoMPLS mode;
 Support SAToP and CESoPSN Emulation formats without cas or with cas;
 Support 16 clock domains;
 Support adaptive and differential clock recovery and meet the ITU-T G.8261 requirements;
 Support the compensation of a minimum of 32 msec PDV;
 Based on WP3-SL platform, no UFE3 logic is necessary, WP3-SL will provides 16 TDI interfaces directly;
 Without ETY port as CES traffic port in front panel, so MSE1_16 does not support standalone work
mode;
 Only SGMII interface in Backplane is provided, so it can only be used in NPT platform.
MSE1_16 is managed as a CES card and can support CES services only when it is associated with CS100/CS10.
Compared with DMCE1_32, MSE1_16 does not support Standalone work mode. The other CES configuration
of MSE1_16 is the same as DMCE1_32.
8.13.4 TMSE1_8
The TMSE1_8 card has all TM10 functionality and integrated with 8 E1 interfaces for CES capability.
TMSE1_8 has the following features:
 Support 8 balanced E1/T1 interfaces. External xDDF_21 is used to provide unbalanced E1 interfaces;
 Support CESoETH and CESoMPLS mode;
 Support SAToP and CESoPSN Emulation formats without CAS or with CAS;
 Support 8 clock domains;
 Support adaptive and differential clock recovery and meet the ITU-T G.8261 requirements;
 Support the compensation of a minimum of 32 msec PDV;
 Based on WP3-SL platform, no UFE3 logic is necessary, WP3-SL will provides 16 TDI interfaces directly;
 Without ETY port as CES traffic port in front panel, and Standalone work mode is not supported.
 Support creating CES service directly and doesn't need to associate MSM cards to Switch module.
From CES point of view, TMSE1_8 has the same functionality with MSE1_16 in NPT-1020/NPT-1021, except
E1 numbers.

8.13.5 MSC_2_8
MSC_2_8 is a Tslot module that provides CES function for 2 x STM1/OC3 and 8 x E1/T1 interface. It supports
8 balanced E1/T1 interfaces and 2 STM-1/OC-3 interfaces. External xDDF_21 provides unbalanced E1
interface.
MSC_2_8 can be assigned to the T-slot of NPT-1020/NPT-1021/NPT-1050/NPT-1200 (except Tslot5) and NPT-
1800 (except Tslot22).
MSC_2_8 card main features are as follows:
 Interfaces
 Supports 8 balanced E1/DS1 interfaces and 2 STM-1/OC-3 interfaces.
 External xDDF_21 is needed to provide unbalanced E1 interface.
 STM-1 channelized to 63 * VC-12 (E1) interfaces.
 OC-3 channelized to 84 * VT-1.5 (DS1) interfaces.
 CES Service
 Support CESoETH and CESoMPLS mode
 Support SAToP and CESoPSN (without CAS and with CAS) Emulation formats
 Clock recovery
 Support adaptive and differential clock recovery and meet the ITU-T G.8261 requirements
 For 8 * E1/T1 interfaces, each E1/DS1 have an independent clock domain in Differential or
Adaptive clock recovery mode as usual.
 For 2 * STM-1/OC-3 interfaces, each E1/DS1 channel have an independent clock domain in
Differential or Adaptive clock recovery mode too.
 Support the compensation of a minimum of 32 msec PDV
 Protection
 Support MSP1+1 between two STM-1/OC-3 port Intra-card
 Support MSP1+1 between STM-1/OC3 ports cross-card
 STM-1/OC-3 Framer
 No TEMUX chip
 Based on UFE4 other than UFE3, STM-1/OC-3 interfaces are supported by UFE4.
 Support both SDH and SONET Framer
 Difference
 Without ETY port as CES traffic port in front panel, don’t support standalone work mode. Don’t
support CESoIP/UDP traffic.
 No ESSI bus from central XC Matrix, TDM interfaces are from local front panel only.
 CEP (RFC4842)
 HW ready for supporting for VC-4/VC-3 over packet (CEP)
 HW ready for supporting for STS-3c/STS-1 over packet (CEP)

 Platform
 Support in NPT-1020/NPT-1021 without cross card protection
 Support in NPT-1050, support cross card protection between Tslot2 and Tslot3
 Support in NPT-1200, support cross card protection between any two Tslots
 Support in NPT-1800/NPT-1200i, support cross card protection between any two vertical
neighbor Tslots have interconnection.
 Support live insertion
8.13.5.1 Configure MSC_2_8

This section describes how to configure the MSC_2_8 card in NPT-1020/NPT-1021/NPT-1050/NPT-1200 NEs.
To configure MSC_2_8:
1. In the NE Shelf View window, in the left object tree, select the MSC_2_8 card. Then in the Configuration
working mode, click the General tab.
You can view the general information of MSC_2_8 from the window.

2. To set the card parameters of MSC_2_8, click the Card Parameters tab.
You can enable/disable MAC SA Check in this window. The Work Mode is read only.

3. To set Different Timestamp Frequency for MSC_2_8, click the Timing Setting tab.

4. To view and modify TTI and TSL settings, click the TTI and TSL tab.

8.13.5.2 Configure traffic path of MSC_2_8

To configure traffic path of MSC_2_8
1. In the NE Shelf View window, in the left object tree, select an oPort of MSC_2_8. Then click
Configuration and then select the General tab.
2. Configure the attributes as required:

 Admin State: select Disable or Enable from the dropdown list.
 User Label: enter required user label for the port.
 Description: set required description.
8.13.5.3 Attach to central PE

MSC_2_8 card can only support CES traffic path from SGMII interface to Central PE.
For MSC_2_8 card, two Backplane HW connections (SGMII) are using for CES packet interface. While
attaching CES card from management, one or two of the following connections can be selected:
 Backplane HW connection (SDH/SONET)
This is for STM-1/OC-3 ports

 Backplane HW connection (E1/DS1)

This is for 8*E1/DS1 ports
The following new attachment types are supported for MSC_2_8 in NPT-1200/1050 in SDH mode:
 Backplane HW connection (STM-1)
 Backplane HW connection (E1)
 Backplane HW connection (STM-1 & E1)
The following attachment types are supported for MSC_2_8 in SONET mode:
 Backplane HW connection (OC3)
 Backplane HW connection (DS1)
 Backplane HW connection (OC3 & DS1)
For MSC_2_8 in NPT-1020, the old attachment type is used: Backplane HW connection.
To attach MSC_2_8 to central PE:

1. In the NPT NE Shelf View window, in the left object tree, right-click the central PE and select Attach
CES Cards. The Associate CES Cards window opens.

2. Select a required connection for MSC_2_8 from the Attaching Connection dropdown list.
8.13.5.4 Support MSP1+1

Linear APS1+1 is supported in MSC_2_8:
 STM-1/OC-3 interfaces support Intra-card Linear MSP1+1/APS1+1.
 MSC_2_8 supports Intra-card Linear MSP1+1/APS1+1 in NPT-1020/NPT-1050/NPT-1200/NPT-1800.
 MSC_2_8 supports cross-card Linear MSP1+1/APS1+1 in SDH mode or SONET mode.
 MSC_2_8 supports cross-card Linear MSP1+1/APS1+1 in NPT-1050/NPT-1200/NPT-1800.
MSC_2_8 cross-card Linear APS1+1 in NPT-1050, is different with that in NPT-1200, including:
 MSC_2_8 only support cross-card Linear APS1+1 between Tslot2 and Tslot3 only;
 Direct communication between the X-MSM card pair via SGMII_C3 is supported;
 Card status indication, even port defects indication between cross-cards can be supported by PCM8M
bus.

8.13.5.5 View MAC statistics

MAC statistics especially for the error packet statistics are useful for locating customer field issues.
MAC statistics are supported in all the CES cards in standalone mode, or the CES cards that have already been
attached to L2 card/Central.
To view MAC statistics:

1. In the NE Shelf View window, in the left object tree, select a CES card (in standalone mode, or already
attached to L2 card/Central). Then click Performance and then select the MAC Statistics tab.
2. To retrieve the parameters to view, click .
3. To clear the data, click .

8.13.6 MS1_4 (Ezchip)

In NPT NEs, MS1_4 is a CES card for Tslot with four STM-1/OC-3 or one STM-4/OC-12 interfaces.
 Support SAToP and CESoPSN services and various encapsulations including CESoETH and CESoMPLS;
 Support CEP service based on VC-3, VC-4 and VC-4-4c;
 Support CEP service based on STS-1, STS-3c and STS-12c.
The other function of MS1_4 is the same with the card MSC_2_8.
MS1_4 (Ezchip) is supported in the following NEs:
 NPT1200
 NPT1050
 NPT1020
 NPT1021
8.13.7 MSE1_32 (Ezchip)

MSE1_32 is an E1/T1 CES card for Tslot with 32 E1 interfaces, which can support SAToP and CESoPSN services
and various encapsulations including CESoETH and CESoMPLS.
The other function of MSE1_32 is the same with the card MSE1_16.
MSE1_32 (Ezchip) is supported in the following NEs:
 NPT1200
 NPT1050
 NPT1020
 NPT1021
8.14 Optics cards

This section describes how to configure the SM10 and the OBC card Erbium Doped Fiber Amplifier (EDFA)
settings.
8.14.1 Optical Base Card (OBC)

The OBC is an extension card supported for STM-64/STM-16 long distance optical links. For long distance
transportation, booster and pre-amp EDFA modules are added into fiber links between optical module Tx
and Rx to compensate for the attenuation from long fibers. The modularized design is used in order to
support different applications flexibly and with the lowest cost.
OBC supports two daughterboard (DB) slots for EDFA DB and one DB slot for DCM DB:
 OM_BA: A DB for OBC that provides a Booster Amplifier.
 OM_PA: A DB for OBC that provides a Pre-Amplifier.

 OM_ILA: A DB for OBC that provides an in-line full C-band Dense Wavelength Division Multiplexing
(DWDM) Amplifier, and supports in-line amplifier mode only.
 OM_LVM: A DB for OBC that provides two stage VGA C-Band amplifier and 20.5dBm variable gain EDFA
with mid-stage access (MSA).
 OM_DCMxx: Dispersion Compensation Module (DCM) based on dispersion compensation grating for
small size and low insertion loss. Several types of OM_DCM DB is supported for different compensation
capabilities, including 40 km, 60 km, 80 km, and 100 km.
To perform slot assignment for the OBC:

2. At the left lower corner of the window, select the Assign radio button.
3. Right-click an Eslot and in the popup list, select the OBC card.
4. To assign subcards in the OBC card, right-click the subslot you want to assign, and then in the shortcut
menu, select a card to assign.
5. To save your assignment, click Apply.

6. To obtain the expected configuration from the DB, click Get Logical Card. 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.
7. To view the information of the assigned subcards, select the object in the object tree. In the

8.14.1.1 Erbium Doped Fiber Amplifier

This section describes the EDFA functions in OBC.
To perform EDFA configuration:

1. To view the general information of the EDFA, in the NE Shelf View window, in the left object tree, select
OBC, OM_BA/OM_PA/OM_ILA/OM_LVM, and then EDFA. In the Configuration working mode, select
the General tab.

2. To perform the EDFA settings, in the Configuration working mode, select the EDFA Setting tab.
3. In the Power Setting area, you can view the Gain, Power In Degrade Threshold, Actual Output Power,
Max Output Power, Input Power, and Power Supply; the value of Gain and Gain Tilt is configurable.
 For OM_BA, the gain is from 10dBm to 15dBm.
 For OM_PA, the gain is fixed to -12dBm.
 For OM_ILA, the gain range is: 10~21dBm with a step of 0.5dBm (default is 10dBm).
Gain Tilt is configurable between 0 and -2.0 dB in step of 0.1dB. Default is 0.
Power in Degrade Threshold is configurable between -27 ~ -5 dBm in step of 0.1dBm. Default is -24
dBm.

4. You can also view the other information in the Pump Status area.
5. To perform maintenance operations for EDFA, in the left object tree, select OBC,
OM_BA/OM_PA/OM_ILA/OM_LVM, and then EDFA. In the Maintenance working mode, select the
Amplifier tab. For OM_BA and OM_ILA, the maintenance options are shown as follows.
You can perform the maintenance operations as described here:

 When Amplifier is shut down, the EDFA output signal will have a little bit lower power than the
input signal due to insert loss of EDFA.

 When Amplifier output is Mute, the EDFA output power will be set to below 0dBm. This operation
is for OM_BA and OM_ILA only.
For OM_PA, the maintenance options are shown in the following figure.
Set the relevant maintenance operation as required, and click Apply to save the setting.

6. To view EDFA alarm threshold, in the left object tree, select the EDFA module under
OM_BA/OM_PA/OM_ILA, then under Fault Settings working mode, select the EDFA Alarm Threshold
tab.
The values of input LOS threshold are:

 LOS threshold of OM_BA: -10dBm
 LOS threshold of OM_PA: -40dBm
 LOS threshold of OM_ILA: -27dBm

8.15 PCM cards

This section describes how to access, assign, and configure the SM10, SM_10E, and EM_10E cards.
8.15.1 SM10 card

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.
8.15.1.1 SM10 supported modules

The SM10 supports three common traffic module slots, as well as a special small traffic module slot for
Ethernet interfaces.
Table 8-14: 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 (PtMP) 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 64K codirectional G.703 interface module for the SM10 card.
SM_FE_A Two 10/100Base-T channels (the bandwidth of each channel can be E1 or N x 64
Kbps).

8.15.1.2 SM10 slot assignment

To perform slot assignment for the SM10:
1. In the BG-40 NE Shelf View window, in the left object tree, right-click the NE and select Slot Assignment.
2. Right-click an Eslot and in the popup list, select the SM10 card.

3. To assign subcards in the SM10 card, right-click the subslot you want to assign, and then in the shortcut
menu, select a card to assign.

Set As Logical.

8.15.2 SM_10E card

The SM_10E card is a PCM card for BG-20, BG-30, BG-64 and NPT-1200/NPT-1020 NEs. The card has the
following features:
 Multiservice access through multiple daughter modules
 Non-blocking 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:
 height: 25.4 mm
 width: 265 mm
 depth: 210 mm
 Module:
 height: 20 mm
 width: 67.4 mm
 depth: 154 mm
 Front-access connectors
8.15.2.1 Supported modules

There are three module slots in the SM_10E, each with a capacity of 12 Mbps. They can accommodate the
interface modules described in the following table.
Table 8-15: SM_10E traffic modules

Name Description
SM_FXO_8E Eight-channel FXO access module.
SM_FXS_8E Eight-channel FXS access module.
Ring back tone for hot line is supported on FXS of SM_FXS_8E.
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 PtMP
SM_V35E Two-channel V.35 data access module.

Name Description
SM_Omni_E Omnibus central unit with external 2 x 24 W interfaces. SM_OMNI_E cannot be
assigned to a SM_10E card if another SM_10E card has already be assigned one
or more SM_OMNI_E modules.
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 supports V.35 over both framed and unframed E1.
SM_V35_V11 Two-channel V.35 module supports V.35/V.11 over both framed and unframed
E1.
SM_C37.94 Two optical ports for teleprotection.
SM_C37.94S The service module for SM_10E/EM_10E with two SFP based C37.94 optical
interfaces.
SM_IO18 A sub card for SM_10E and EM_10E with 18 dry contact interfaces.
8.15.2.2 SM_10E slot assignment

To perform slot assignment for SM_10E:
1. In the BG-20E/BG-30E/BG-64E/NPT-1200E/NPT-1020E NE Shelf View window, in the left object tree,
right-click the NE and select Slot Assignment. The Slot Assignment window opens.

2. Right-click an Eslot and in the popup list, select the SM_10E card.

3. To assign subcards in the SM_10E card, right-click the subslot you want to assign, and then in the
shortcut menu, select a card to assign.

Set As Logical.
8.15.2.3 User Defined E1 CAS signaling type

The User Defined E1 CAS signaling type is supported in SM_10E/EM_10E.
When User Defined CAS profile is configurable per card, following parameters can be configured:
 In direction from FXO to FXS:
 Tx CAS when No Ring is detected on FXO interface
 Tx CAS when Ringing is detected on FXO interface
 Rx Mask
 In direction from FXS to FXO
 Tx CAS when loop open is detected
 Tx CAS when loop closure is detected
 Rx Mask

To set the User Defined E1 CAS signaling type:

1. In the NE Shelf View window, in the left object tree, select E1_PCM under SM_10E, or CES_16 under
EM_10E. Then in the Configuration working mode, select the E1 Ports tab.
From the CAS Signaling dropdown list, you can select User Define and click Apply to save the settings.

2. To view the parameters of the user defined CAS, in the left object tree, select E1_PCM under SM_10E,
or CES_16 under EM_10E. Then in the Configuration working mode, select the User Define CAS tab.
3. You can configure the CAS encoding as required and click Apply to save the changes.

8.15.2.4 SM_C37.94
SM_C37.94 is a module of SM_10E/EM_10E. This section describes how to configure the SM_C37.94 ports.
To configure the SM_C37.94 ports:

1. In the NE Shelf View window, in the left object tree, select SM_C37.94 under SM_10E/EM_10E. In the
Configuration working mode, select the C37.94 Port tab.

Or, in the left object tree, select a port in the SM_C37.94. Then in the Configuration working mode,
select the General tab.
2. To retrieve the information from the NE equipment, on the toolbar, click .

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

8.15.2.5 SM_C37.94S
SM_C37.94S is a module of SM_10E/EM_10E. This section describes how to configure the SM_C37.94S ports.
To configure the SM_C37.94S ports:

1. In the NE Shelf View window, in the left object tree, select SM_C37.94S under SM_10E/EM_10E. In the
Configuration working mode, select the C37.94S Port tab.

Or, in the left object tree, select a port in the SM_C37.94S. Then in the Configuration working mode,
select the General tab.

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


5. To manage the SFP settings for the ports, select a port of SM_C37.94S and then in the Configuration
working mode, select the SFP Setting tab.
The SFP can be assigned as other optical port and SFP types can be assigned are:
 None
 OTR2M w/o DDM (Non-enhanced 2M SFP)
 OTR2M (SFF-8472 compliant, with DDM – Digital diagnosis monitoring)

8.15.2.6 Reassigning from SM_C37.94 to SM_C37.94S

SM_C37.94 can be reassigned to SM_C37.94S as described in this section.
To reassign from SM_C37.94 to SM_C37.94S:



3. Right-click the SM_C37.94 subcard, then from the popup menu, select Reassign and then SM_C37.94S.
4. Click Apply. A confirmation window opens prompting you to confirm the reassignment.

8.15.2.7 V.24 configuration

The SM_V24E subcard can support the following three modes.
Table 8-16: V.24 Attributes Settings

Rate Grade Mode TC Mode Band Rate Operation Rate Adaption
Mode
LOW Transparent (8 Sampling / / /
channels) TC 0 ~ 19200 / /
Async with / 600 ~ 38400 Duplex V110/HCM
Control
Sync with / 600 ~ 38400 Duplex V110/HCM
Control
HIGH Transparent (8 Sampling / / /
channels) TC 0 ~ 19200 / /
Async with / 57600 Duplex HCM
Control
Sync with / 56000, 64000 Duplex V110/HCM
Control
There are four steps to configure V.24, as described in this section.
To configure V.24:
1. To configure E1 attributes:
 Frame Attribute: Generally V.24 need not CAS signaling, you can set Frame Attribute as PCM31,
and PCM30 is also OK.
 CAS Signaling: not change.
 CRC-4: both Support and Not Support are OK.
2. To configure V.24 attribute:
 V24 Mode Supported: three modes that Transparent (8 channels), Async with Control (4
channels), Sync with Control (2 channels).

 V24 Rate Grade: two rate grades that Low and High.
 Transparent: both Low and High are same, which include Sampling mode and TC mode. When
works at Sampling, the maximum baud rate support 19200bps. When works at TC, the baud rate
must be in accordance with setting value.
 Synchronous: the maximum baud rate under Low support 600pbs ~ 38400bps, it under High
support 56000bps and 64000bps.

 Rate Adaption: V110 protocol is designed by Nokia, and HCM protocol is designed by Alcatel.
3. Create VC12/E1 XC. It is same as other E1 card.
4. Create DS0 XC from SM_V24E card to E1_PCM module:
a. Rate: 64K
b. Direction: Bidirectional
c. Bundle: mark means multi XC can be created, and unmark means one XC can be created.
d. Select Source Timeslot: select one or some V.24 port.

e. Select Sink Timeslot: select one or some DS0 under E1 port.

f. Activate DS0 XC: after you select source and sink completely, click Save and then Activate All.

8.15.2.8 Alarm support for SM_10E from the EMS

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

 In the NE Shelf View window, right-click a service port with XCs of SM_10E, and in the shortcut menu,
click View Correlative E1 Alarm.

The associated E1/VC-12 port and its alarms are displayed, as shown in the following window.
8.15.2.9 Manage SM_IO18

SM_IO18 is a sub card for SM_10E/EM_10E to support 18 dry contact (DC) IO ports. It is mainly designed to
provide high fan out dry contact ports:
 The dry contact port can be defined as input or output on per port basis;
 It is used for substation alarm monitoring and control.
Following shows an example of substation alarms.

Actually, the dry contacts functions similarly as NPT alarm input/output ports. The problem is that alarm
interface has only four inputs and three outputs, which are not enough for substation application. SM_IO18
provides higher fan out of dry contact ports – 18 in/out per module, 8 x 3 in/out per SM_10E/EM_10E, and
24 x 3 per EXT-2U.
SM_IO18 is supported in the following NEs and base cards:
 NPT-1200 (SM_10E & EM_10E)
 NPT-1020 (SM_10E & EM_10E)
 NPT-1021 (EM_10E)
 NPT-1050 (SM_10E & EM_10E)

Activate/deactivate ports of SM_IO18

SM_IO18 has 18 dry contact ports while each port can be configured as either input or output. By default, all
ports are input. You can activate or deactivate the ports manually. The port definition is card level
configuration.
To activate/deactivate ports of SM_IO18:

1. In the NE NE Shelf View window, in the left object tree, right-click the SM_IO18 card, then from the
shortcut menu, select Activate/Deactivate Port. The Activate/Deactivate Port window opens.
1. In the Activate list, select the required checkbox(es) to activate or deactivate the port(s), and then set
Input/Output type for the relevant port(s).
2. To batch edit the mode, click . Then click to select the required operation as you need.

Configure an input port of SM_IO18
To configure an input port of SM_IO18:

1. In the NE Shelf View window, in the left object tree, select an activated input port under a SM_IO18
card, then select Configuration > General.
2. Configure the attributes as described in the table below.

Table 8-17: Input port attributes of SM_IO18

Attribute name Description
Port The input port number.
User Label User label of the input port.
Description Description of the input port.
Port Name Specify the alarm or event name of the external input signal.
Monitor Type Define the monitor mechanism to be used for input port monitoring. Two
options: Alarm or Event.
Alarm Severity Specify the alarm severity: Critical, Major, Minor, Warning. Effective only when
monitor type is Alarm.


DC Status in Alarm Define which status of the dry contact represents alarming.
 If Monitor Type is Alarm, then it can be set as Close or Open.
 Close: means dry contact in close status represents alarming status.
 Open: means dry contact in open status represents alarming status.
 If Monitor Type is Event, then it can be set as Open to Close or Close to
Open.
 Open to Close: means effect edge to generate event is change from
open to close.
 Close to Open: means effect edge to generate event is change from
close to open.
Alarm Raise Delay The persistency time to declare an external alarm.
Time
Alarm Clear Delay The persistency time to clear an external alarm.
Time
Alarm Status Indicate current alarming status as per definition.
Actual DC Status Indicate the dry contact port physical status.

Configure an output port of SM_IO18

The output port is used to control external devices, such as turn on/off air condition. The control can be
manual (user requested command) or automatic (decided by predefined rules according to input status).
To configure an output port of SM_IO18:

1. In the NE Shelf View window, in the left object tree, select an activated output port under a SM_IO18
card, then select Configuration > General.
2. Configure the attributes as described in the table below.

Table 8-18: Output port attributes of SM_IO18

Port The output port number.
User Label User label of the output port.
Description Description of the output port.
Port Name Specify the name of the output port (user defined name to represent specific
function).
DC Status in Port Define which status of the dry contact represents enabled (or ON).
Enabled


Automatic Control Define the mode to control the output (enable or disable automatic control).
Mode Default is disabled.
When it is enabled, the output is controlled by the status of associated input
port(s).
Associated input port list:
 When the automatic output control is enabled, the associated input port(s)
must be specified;
 In V6.0, only one port can be associated;
 In future, multiple ports can be associated;
 The input port can be in any SM_IO18 sub card within same
SM_10E/EM_10E.
 When the input port is selected as associated port, the effective status to
enable output must be specified:
 Enable the output when Input port is in alarming status;
 Enable the output when input port is in non-Alarming status.
Hold-off Time to Specify the hold-off time to enable a port when associated input port status
Enable changes.
Hold-off Time to Specify the hold-off time to disable a port when associated input port status
Disable changes.
Associated Input Port Select the input port number to be associated with this output port. When the
automatic output control is enabled, the associated input port(s) must be
specified:
 In V6.0, only one port can be associated;
 In future, multiple ports can be associated;
 The input port can be in any SM_IO18 sub card within same
SM_10E/EM_10E.
Alarm Status to Enable Specify the condition to enable the output when the output is associated to an
input port – input alarming status is true or false. When the input port is selected
as associated port, the effective status to enable output must be specified:
 Enable the output when input port is in alarming status;
 Enable the output when input port is in non-Alarming status.
Set switch command of an output port

The switch command of an output port is available only when automatic control mode is set as disabled.

To set switch command of an output port:

1. In the NE Shelf View window, in the left object tree, select an output port under a SM_IO18 card.
2. Enable or disable the port as you need.

3. Click Apply. The changes are saved.
Table 8-19: Switch command attributes of an output port

Port The output port number.
Actual Port Enable Indicate the real output status.
Status
Actual DC Status Indicate the dry contact port physical status.
Switch Enable Enable or disable the port.

8.15.3 EM_10E
EM_10E can be assigned in NPT-1020/NPT-1021 and NPT-1200 (with CPTS100/CPS100 assigned).
8.15.3.1 EM_10E card overview

The EM_10E card is a PCM card for NPT-1200/NPT-1020/NPT-1021 NE, which can be assigned in the Eslots
of NPT-1020/NPT-1021 and NPT-1200 (with CPTS100/CPS100 is assigned).
EM_10E is a PCM service card that supports 16 E1/DS1 CES and varies PCM service interfaces via 3 pluggable
daughter boards.
8.15.3.2 EM_10E supported modules

There are three module slots in the EM_10E. They can accommodate the interface modules described in the
following table.
Table 8-20: EM_10E traffic modules

Name Description
SM_FXO_8E Eight-channel FXO access module.
SM_FXS_8E Eight-channel FXS access module.
Ring back tone for hot line is supported on FXS of SM_FXS_8E.
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 PtMP
SM_Omni_E Omnibus central unit with external 2 x 24 W interfaces. SM_OMNI_E cannot be
assigned to a SM_10E card if another SM_10E card has already be assigned one
or more SM_OMNI_E modules.
SM_Codir_4E Four-channel 64 K codirectional data access module.
SM_V35_V11 Two-channel V.35 module supports V.35/V.11 over both framed and unframed
E1.
SM_C37.94 Two optical ports for teleprotection.
SM_C37.94S The service module for SM_10E/EM_10E with two SFP based C37.94 optical
interfaces.
SM_IO18 A sub card for SM_10E and EM_10E with 18 dry contact interfaces.

8.15.3.3 EM_10E slot assignment

To perform slot assignment for EM_10E:

2. In NPT-1200, before assigning EM_10E cards, make sure that CPTS100/CPS100 is assigned.
3. Right-click an Eslot and in the popup list, select the EM_10E card.

4. To assign subcards in the EM_10E card, right-click the subslot you want to assign, and then in the
shortcut menu, select a subcard to assign.

Set As Logical.
8.15.3.4 CES_16
CES_16 is the CES card in EM_10E which can support CES services, including CES PB PtP, CES PB MPtMP and
CESoMPLS. The configuration of CES_16 CES service is same as DMCE1_32.
CES_16 consists of 16 E1 ports, and each E1 port has one E1 object – The termination sink/source point of
E1.
Basically, the functionality of E1 ports of CES_16 is same as EME1_21 of BG-20C, which supports transparent
E1 only.

To manage CES_16:
1. To view the CES_16 card information, in the NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in
the left object tree, select the CES_16 card under EM_10E. In the Configuration working mode, select
the General tab.

2. To configure card timing settings of CES_16, in the Configuration working mode, select the Timing
Setting tab.
Set the Differential Timestamp Frequency as required and click Apply to save the settings.

3. To define CAS manually, in the Configuration working mode, select the User Define CAS tab.
Configure the CAS Encoding as required and click Apply to save the settings.

4. To view the port status of CES_16, in the Configuration working mode, select the Port Status tab.

5. To configure the E1 port settings of CES_16, in the left object tree, select an E1 Port, then in the
You can configure the Frame Mode, TxClock Mode and CAS Signaling attributes for the E1 port. Click
Apply to save your settings.

8.16 MXC cards

This section describes MXC4X and MXC-20/MXC-20C cards in LCT-NPT.
8.16.1 MXC4X
The MXC4X is the cross-connect, timing, and control unit of the BG-40.
To view the MXC4X card:

1. In a BG-40 NE Shelf View window, in the left object tree, select Control and Physical Object and then
MXC4X. Select the Configuration working mode General tab to view the description of the MXC4X card.

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

MXC. Select the Configuration working mode General tab to view the description of the MXC20 card.
8.16.3 MXC-1020
Once NPT-1020 NE is created, MXC-1020 in BS slot is created mandatory.
The base unit of MXC-1020 mainly includes following units:
 The main control unit of MCP1020;
 Timing unit of TMU1020 and TMU1588-1020;
 Central TDM matrix of XC-2.5G, SAM4_2, EME1_21;
 EoS unit of MEoS_8;

 Central packet switch of CS10;

 12 GbE interfaces of MGE_12;
 On-board fan unit of FCU-1020.
To manage MXC-1020:
 In the NPT-1020 NE Shelf View window, in the left object tree, select Control and Physical Object and
then MXC-1020. Select the Configuration working mode General tab to show the description of the
MXC-1020 card.

8.16.4 MXC-1021
Once NPT-1021 NE is created, MXC-1021 in BS slot is created mandatory.
To manage MXC-1021:
then MXC-1021. Select the Configuration working mode General tab to show the description of the
MXC-1021 card.

8.17 Control cards

This section describes the control cards.
8.17.1 MCP30/MCP30B
The performance of the MCP30 (original main control card of the BG-30) is not sufficient to manage the BG-
30 element. Some deficiencies have been exposed in testing and real applications, including:
 Inefficient internal communications
 Very slow startup procedure
 Slow operating response to complex commands
 Uptight memory allocation
When more and more new cards and features are added, especially new L2 cards, the MCP performance
(CPU, communications, memory, etc.) becomes a bottleneck in the system. This may produce more
limitations for NE configuration and applications.
MCP30B is an enhanced substitute for MCP30, designated to overcome the deficiencies of MCP30 and
significantly increasing the overall performance of the control unit, including the microprocessor and
communications. Besides enhancing performance, and depending on the cost and necessity, some
improvements and optimization can also improve the system reliability and maintainability.
The BG-30B MS slot can therefore support two kinds of cards: MCP30 and MCP30B.

To manage the MCP30 card:

MCP30. Select the Configuration working mode General tab to show the description of the MCP30
card.

2. To set the VC12 objects, in the object tree, select Control and Physical Object and then MCP30. In the
Configuration working mode, select the TTI and TSL tab.

3. To set the attribute of a VC12, in the left object tree, select a VC12 under MCP30, then in the
Configuration working mode, select the Clear Channel tab.
From this window, the VC-12 can be set to the following modes:
 Framed Clear Channel--Standard
 Framed Clear Channel--BG-40 2nd Channel Compatible
 Unframed Clear Channel
When XIO30 is assigned as XIO30Q_1&4, only the Unframed Clear Channel mode is supported.

To manage the MCP30B card:

MCP30B. Select the Configuration working mode General tab to show the description of the MCP30B
card.

2. To manage the ports, select Control and Physical Object and then MCP30B. In the Configuration
working mode, select the Management Ports tab.

Alternatively, you can select Control and Physical Object and then MCP30B from the left object tree,
and then the Configuration working mode.

3. To set the VC12, in the object tree, select Control and Physical Object and then MCP30B. In the

4. In the object tree, select Control and Physical Object, MCP30B, and then VC12. In the Configuration
working mode, select the Clear Channel tab.
8.17.2 MCP64
MCP64 is the main control unit for the BG-64 platform. It is responsible for both internal and external
communications, equipment, and NE management and control.
The main functions of the MCP64 are:
 To provide the NE management interface for management stations, LCT-NPT, and LCT-NPT
 Internal communications and control for all cards and components
 DCC, clear channel processing and routing for network communications
 SDH OH process and interface
 NE management, including configuration, alarm, PM, and various maintenance functionalities

 T3/T4 interface
 NE alarm indication and alarm outputs/inputs
The MCP64 CF card is extractable from the front panel, and supports hot swapping. Data integrity protection
is supported in case of power loss. The power supply system supports 10 msec hold-up time. When the power
input is down, an interrupt is produced to inform the CPU of the power failure. When the CF card is being
accessed, LED indication is supported.
The MCP64 can be reset by a button on the front panel (warm reset).
To manage the MCP64 card:

MCP64. Select the Configuration working mode General tab to show the description of the MCP64
card.

2. To manage the ports, select Control and Physical Object and then MCP64, and in the Configuration

Alternatively, in the left object tree, select Control and Physical Object and then MCP64, and select the
Configuration working mode.

3. To set the VC-12, in the object tree, select Control and Physical Object and then MCP64. In the

4. In the object tree, select Control and Physical Object, MCP64, and then VC12. In the Configuration

8.17.3 MCP-1200
MCP-1200 is the main control processor for NPT-1200 (based on MCP64).
To manage MCP-1200:
1. In the NPT-1200 NE Shelf View window, in the left object tree, select Control and Physical Object and
then MCP-1200. Select the Configuration working mode General tab to show the description of the
MCP-1200 card.

2. To manage the ports, select Control and Physical Object and then MCP-1200, and in the Configuration

Alternatively, in the left object tree, select Control and Physical Object, MCP-1200 and then Mng Port,
and select the Configuration working mode.

3. To set the VC-12, in the object tree, select Control and Physical Object and then MCP-1200. In the

4. In the object tree, select Control and Physical Object, MCP-1200, and then VC12. In the Configuration

8.17.4 MCPS-1010
MCPS-1010 is the main control processor for NPT-1010.
To manage MCPS-1010:
then MCPS-1010. Select the Configuration working mode General tab to show the description of the
MCPS-1010 card.

8.17.5 MCP-1050
MCP-1050 is the main control processor for NPT-1050.
To view general information of MCP-1050:

then MCP-1050.
2. Click Configuration and then select the General tab. The general information of MCP-1050 is displayed.

8.18 Power units

This section describes the power units.
8.18.1 Power units of BG-40

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 110W.
You can refresh the power type of BG-40 NE from the right-click menu of the power unit.

The INF/AC_CONV is the power module for the BG-20 NE. Power consumption is 60 W for BG-20B and 150
W for BG-20E.
For BG-20, the power unit type can be:
 INF_20B
 AC_CONV_20B

 INF_20BH
 INF_20BE
For BG-20E, the power unit type can be:
 INF_20E
 AC_CONV_20E
For BG-20EH, the power unit type can be:
 INF_E2U


The BG-30 NE's power units are as follows:
 INF-30B/INF-30BH/INF-30E/INF-E2U: single input DC power supply module with input filtering and a
fan power supply.
 AC_CONV_30B/AC_CONV_30H/AC_CONV_30E/AC_CONV_WE: single input AC power supply card, with
AC to -48 V converter and fan power supply.

INF-64 is the BG-64 DC power supply with input filtering. It supports 1+1 with analog protection for -48 V and
Fan PS. One INF-64 can serve the power supply for the whole BG-64 platform. INF-64 can provide 48 V power
for all the cards in the BG-64. The maximum power consumption of the BG-64 supported by INF-64 is 360 W.
In order to support more high-power cards in BG-64 shelf, INF-64H with more power consumption is
supported in BG-64.

8.18.5 Power units of NPT-1200

INF-1200 is the input DC power supply for NPT-1200, and INF-E2U is the DC power supply for BG-20EH/EXT-
2U.
In addition to automatic power shutdown due to overheating, overvoltage or under-voltage, INF-1200
supports manual power shutdown for maintenance purposes. When power output is cut off, it will restart in
a few seconds.
You can perform slot assignment for the power unit shelf in NPT-1200.
To manage power units of NPT-1200:

1. To view the general information of INF-1200, in the NPT-1200 NE Shelf View window, in the left object
tree, under Control and Physical Object, select INF-1200. In the Configuration working mode, select
the General tab.

2. To view the general information of INF-E2U, in the left object tree, under Control and Physical Object,
select INF-E2U. In the Configuration working mode, select the General tab.
To restart power of NPT-1200:

1. In the NPT-1200 NE Shelf View window, in the left object tree, select the NPT-1200 NE, and then from
the shelf view menu select Restart Power under Maintenance.


8.18.6 Power units of NPT-1020/NPT-1021

The following sections describe the power units in NPT-1020/NPT-1021:
 INF-B1U: Single input DC power supply
 INF-B1U-D: Dual input DC power supply
 INF-B1U-24V: Single input DC with 24V power supply
 AC-PS-B1U: Single input AC to DC converter
Once INF-B1U-24V is working, due to the power limitation, CPS50 card and DMCES1_4 card in T-slot cannot
be supported.
You can perform slot assignment for the power units in NPT-1020/NPT-1021, as described in the following
table.
Table 8-21: Power units assignment in NPT-1020/NPT-1021

Slot Type Available assignments Assignable from Default assignment
name (expected) management
PS A Physical INF-B1U, Yes INF-B1U, INF-B1U-24V
INF-B1U-D,
INF-B1I-24V,
AC-PS-B1U,
None
PS B Physical INF-B1U, Yes INF-B1U, INF-B1U-24V
INF-B1U-24V,
None
EPS A Physical INF-E2U, Yes INF-E2U
AC-PS-E2U,
None
EPS B Physical INF-E2U, Yes INF-E2U
None

To manage power units of NPT-1020/NPT-1021:

1. To view the general information of the power unit, in the NPT-1020/NPT-1021 NE Shelf View window,
in the left object tree, under Control and Physical Object, select the power unit. In the Configuration

2. To view the general information of INF-E2U, in the left object tree, under Control and Physical Object,
select INF-E2U. In the Configuration working mode, select the General tab.
To restart power of NPT-1020/NPT-1021:

1. In the NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select an MXC-1020/MXC-
1021 card.
2. Select Maintenance and then Reset. The Reset Card window opens.
3. Select Power on reset and click OK. A confirmation window opens, prompting you to confirm the reset.
4. To confirm reset, click Yes.


INF-1010 is the power supply unit for NPT-1010. It represents the -48V DC power supply unit of NPT-1010
which is built in MCPS-1010DC.

tree, under Control and Physical Object, select INF-1010. In the Configuration working mode, select
the General tab.

INF-B1UH is the DC power supply unit for NPT-1050. It supplies 450W power to the shelf (including the power
of fans).
You can perform slot assignment for the power unit shelf in NPT-1050.


tree, under Control and Physical Object, select INF-B1UH.

3. To view the status of INF-B1UH, in the Configuration working mode, select the Status tab.
To restart power of NPT-1050:

1. In the NPT-1050 NE Shelf View window, in the left object tree, select the NPT-1050 NE, and then on
the shelf view menu select Restart Power under Maintenance.


8.18.9 Assign power units for BG-64/NPT-1200/NPT-

1020/NPT-1021
You can perform slot assignment for the power units for BG-64/NPT-1200/NPT-1020/NPT-1021, with the
following restrictions:
 EPS A, EPS B and EFS must be assigned together;
 When both EPS A and EPS B are assigned with INF, the card type must be same;
 None is not allowed in EFS;
 Both none is not allowed in EPS A and EPS B.
To assign AC-CONV-30E in BG-64:

1. In the BG-64 NE Shelf View window, in the left object tree, select the BG-64 NE. Then from the shelf
menu, select Configuration, and then Slot Assignment.

2. In the BG-30E shelf, right-click the INF-30E module and from the shortcut menu, select AC-CONV-30E.

3. The AC-CONV-30E occupies two EPS slots, as shown in the following figure.

To assign AC-PS-E2U in BG-64/NPT-1200/NPT-1020/NPT-1021:

1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select the
BG-64/NPT-1200/NPT-1020/NPT-1021 NE. Then from the shelf menu, select Configuration, and then
Slot Assignment.

2. In the EXT-2U shelf, right-click the INF-E2U module and from the shortcut menu, select AC-PS-E2U.

3. The AC-PS-E2U occupies two EPS slots, as shown in the following figure.
8.19 Fan control units

8.19.1 Set the fan work mode
The LCT-NPT can manage the NE fan's work mode. Fan work modes are:
 Temperature Auto Control: The fan is controlled by the temperature sensor.
 Force Turbo: The user starts the fan manually.
When the temperature exceeds the threshold, the fan starts.
For details of the specific fan unit of each NE, see Describing Card Layout.

For BG-40/BG-20/BG-30 NEs, you can refresh the fan type from the right-click menu of the fan unit.

To access the fan control window:

1. In an NE Shelf View window, in the left object tree, select the fan unit under Control and Physical
Object. In the Configuration working mode, select the Fan Control tab.

2. For the NPT-1200/NPT-1050 NE, you can also view the current fan power level and voltage of FCU-
1200/FCU_1050, as shown in the following figure.

3. For the NPT-1020/NPT-1021 NE, you can view the current fan speed status of FCU-1020, as shown in
the following figure.
4. Modify the fan work mode for the NE as required, and click Apply to save your settings.
5. To retrieve the information to view, on the toolbar, click .
8.20 DMGE_8_POS card

The DMGE_8_POS can be inserted in the TS1-2 or TS6-7 of BG-64 and NPT-1200.
The main features of DMGE_8_POS are:
 Unidirectional traffic flow (always from WAN to LAN).
 Up to 32 PPP over Sonet/SDH (POS) ports and 8 ETY ports.
 POS port supports VC-4 Contiguous Concatenation (CCAT) only. VCG can be configured as VC-4, VC-4-
4c, or VC-4-16c.
 Mirror POS traffic to Ethernet port (GbE or GbE LAG).
DMGE_8_POS includes the following maintenance functions:
 Maintenance list
 Loopback

 ETY payload
 POS payload
The maintenance list, loopback, and ETY payload are the same as those of the DMGE_8_L2. POS payload is
similar to the EoS payload.
8.20.1 Manage ports

This section describes how to manage the ports in the DMGE_8_POS.
To configure DMGE_8_POS card attributes:

1. In a BG-64/NPT-1200 NE Shelf View window, in the left object tree, select the DMGE_8_POS card. In
the Configuration working mode General tab, view the general information of the DMGE_8_POS.

2. To configure the ETY port attribute, select the ETY Ports tab.

3. To configure POS port attribute settings, select the POS Ports tab in the window.

4. To perform VCG configuration, in the left object tree, right-click the DMGE_8_POS card, and from the
shortcut menu, select Create VCG. The VCG Attribute window opens.

working mode.
For each member of this VCG, a Deactivated attribute can be set. This entails removing the member
from the VCG.

6. To configure a single POS port attribute, in the object tree, select the POS port, and then select the

7. To view the ETY payload, in the left object tree, select the DMGE_8_POS card, and in the Maintenance
working mode, select the ETY Payload tab.

8. To view the POS payload, in the left object tree, select the DMGE_8_POS card, and in the Maintenance
working mode, select the POS Payload tab.

9. To perform loopback maintenance, in the Maintenance working mode, select the Loopback tab.
The Loopback Type values are Terminal Loopback, Facility Loopback, and No Loopback (default is No
loopback).
10. Set the Loopback Type for each port in this window, and click Apply to save the configuration in the DB
and the NE.

8.20.2 Manage a LAG

For details about managing LAGs in DMGE_8_POS, see LAG Improvement in the LCT-NPT Service
Management Guide.
8.20.3 POS mirroring

In customer networks where packets are transmitted/received on POS ports, it is necessary to provide the
POS mirroring function in order to sniffer these flows. The POS mirroring function provides the ability to
mirror the flow on a PPP port to a GE port or GE LAG or 10G port. A POS mirroring application sample is
shown in the following figure.
Figure 8-13: POS mirroring application sample
As shown, when POS mirroring is configured, one or two POS mirroring instances can be created. Each
instance includes one PPP port and one GE port or GE LAG or 10G port. The PPP port is used as a source port
of the mirrored flow and the GE/GE LAG/10G port is used as a destination port.

8.20.3.1 POS mirroring supported cards

POS mirroring is supported by the DMGE_8_POS card.
8.20.3.2 Create POS mirroring instances

To create POS mirroring instances:
1. In the BG-64/NPT-1200 NE Shelf View window, in the left object tree, select the DMGE_8_POS card,
and in the Services working mode, select the POS Mirroring tab.

2. On the toolbar, click . The Create POS Mirror window opens.
a. In the General Parameters area, enter the Name for the POS mirroring instance, and in the
relevant fields, set the State, Destination MAC Address and Strip MPLS Label.
 State: Enable or Disable. If enabled, switch performs POS Mirroring function which Mirror
PPP port to GE/LAG/10GE port.
 Strip MPLS Label: It indicates that if the MPLS Label should be stripped or not.
b. In the Mirrored Service Parameters area, select a VLAN tag as required, and then set the
Mirrored Source IP and Mirrored Destination IP.
c. In the Ports Selection area, select a POS port and an ETY port from the lists.
3. To create the POS mirroring instance, click Apply.

8.20.3.3 Manage POS mirroring instances

To manage POS mirroring instances:
1. You can view the POS mirroring instance list in the following window.

2. To enable a POS mirroring instance, select the POS mirroring instance in the list, and on the toolbar,
click . Click to disable it.
3. To edit a POS mirroring instance, select the POS mirroring instance in the list, and on the toolbar, click
. The Edit POS Mirror window opens.
4. Modify the parameters as required, and click Apply to save the settings.
5. To delete a POS mirroring instance, select the POS mirroring instance in the list, and on the toolbar,
click .
6. To synchronize POS mirroring instances, on the toolbar, click .

7. In the open Confirmation window, click Yes to synchronize data and No to cancel.

8.21 TSHU_48V card

In order to solve power supply issue of NPT-1200 in Bharti, there is a possibility to deploy large number of
hold-up cards (TSHU_48V) in Bharti in order to stabilize the power supply. HSHU_48V has no software or
FPGA, only one IDPROM to be managed.
8.22 MXP10 card

The purpose of MXP10 card is to add a low cost, OTN based optical solution into BG-64 and NPT products. It
can support Muxponder, Transponder and Regeneration applications.
MXP10 card is an Eslot card in EXT-2U shelf, with two types of modules OM_AOC4 and OM_AOCP4 (not
supported yet).
2 x 10G Muxponder (AoC10): MXP10 + OM_AOC4 (Line: 2 x OTU-2; Client: 16 any except CPRI)
 2 x 10G Muxponder with 4 x CPRI : MXP10 + OM_AOCP4 (Line: 2 x OUT-2; Client: 16 any, including CPRI
in 4 of 16) (Future functionality)
 1 x 10G Transponder (TRP2)
 1 x 10G Regeneration (REG2)
 Up to 4 x 2.5G Muxponder (AoC25): support 4 groups of client ports to other client OTU1 port
Muxponder mode.
 Up to 5 x 2.5G Transponder (AoC25): when working on 2.5G rate, CSFP cannot be using, so at most 10
client ports are available.
 Up to 5 x 2.5G Regenerator (AoC25): when working on 2.5G rate, CSFP cannot be using, so at most 10
client ports are available
 Flexible combined traffic so long as the HyPHY resource is enough.
AoC10 supports 10 Gbps muxponder service on MXP10 card, it supports up to 16 client interfaces, which are
multiplexed into the G.709 multiplexing structure and sent via two independent OTU2 line interfaces. Any of
the client interfaces can be configured to accept any of a range of signals.
To AoC10, any of the client interfaces can be configured to accept any of a range of signals. Signal mapping
options include:
 STM-1(e)/OC-3(e), STM-4/OC-12, ETY1G(e), FC100, DVB-ASI, and SDI are mapped to ODU0
 OTU1, FC200, STM-16/OC-48, and HD-SDI (1.5G) are mapped to ODU1
 FC400, HD-SDI (3G) are mapped to ODUflex
The AoC10 maps services to the ODU layer and combines them into an OTU2 uplink, thereby increasing
wavelength utilization and enhancing the financial advantages of the optical transport infrastructure. The
AoC can be configured for the following applications:
 As a single ADM on a card with up to 16 clients multiplexed into East/West OTU2 lines. Subnetwork
Connection Protection (SNCP) mechanisms allow the system to select the better signal for each service
transmitted over two paths.

 As a dual multirate combiner with sets of eight clients multiplexed into a single OTU2 line. Services in
this mode can be configured as either unprotected or with full equipment protection.
 As a Y-protected combiner/muxponder with sets of eight clients multiplexed to double OTU2 lines.
AoC25 provides services between client ports. The client port type in WAN side will be OTU1. AoC25 supports
any combination of 2.5G Muxponder, Transponder, Regenerator application. It supports 2 client ports map
to 2_ODU0, then multiplex to ODU1 structure, or one 1G client port maps to ODU1 structure, or two OTU1
Regenerator application with ODU1 XC directly.
The AoC card provides GFEC, EFEC (I.4 and I.7), and no FEC modes towards the line. GFEC is also available on
the client side when it is configured to OTU1.
TRP2 supports 10Gbps Transponder service on MXP10 card, the transponder acts as a mediating device which
is connected to the client’s network on one side (usually "client port") and to the OTN network on the other
side (usually "OTU port"). The transponder maps the client signal onto an OTN signal. Multiplexing several
client signals together is not supported by transponders.
TRP2 application maps the client signal to G.709 and transmits a colored signal towards the network. The
transponder provides multiple mapping options, including:
 STM-64/OC-192/10GBASE-W maps to OTU2
 ETY10G (10GBASE-R) maps to OTU2 with extended OPU2 (G.709, G.Sup43 7.3)
 ETY10GOC (10GBASE-R) maps to OTU2e (G.709, G.Sup43 7.1)
 FC800 maps to OTU2 with ODU Flex
 FC1200 maps to OTU2e
REG2 supports one Regenerator between two line ports with OTU2/OTU2e interconnection directly.
Mapping to OTN the signal's ability to pass long distances is significantly improved due to the FEC added by
OTN. The ability to manage the signals in a common method is also provided by the OTN layer.
MXP10 supports flexible combined service models, including one of the following combinations:
 AoC10 + AoC25
 TRP2 + AoC25
 REG2 + AoC25

Based on the resources on the MXP10 card, not all the preceeding services can be supported at the same
time. For example, the following figure illustrates one TRP2 and several AoC25 services coexisting.
The following figure illustrates one AoC10 and several 2.5G AoC25 services coexisting.
Two GCC channels are supported on MXP10 card, one per OTU2 line port. Two OTN line interface is
independently, each OTU2/OTU2e interface support GCC0, GCC1 or GCC2 which is user configurable.
 For GCC0 channel, the Overhead byte is at OTU field.
 For GCC1/GCC2 channel, the Overhead byte is at ODU field.
Mechanics - Front panel
Mechanics of MXP10 with OM_AOC4 are illustrated in the following figure.
Figure 8-14: Mechanics of MXP10 with OM_AOC4
 Client port from P1 to P12 in MXP10 main card

 Physical port from P1 to P6 is always existed. P7~P12 is existed while the corresponding port is installed
with CSFP module.
 Line ports include Line1 and Line2 in MXP10 main card, which is 10Gbps port.
 Physical port from P13 to P16 is existed when OM_AOC4 subcard is installed.
 LED indicators
 ACTIVE , FAIL and ALARM indication in MXP10 main card
 ACT, FAIL indication in OM_AOC4 sub card
 LSR ON indication per each physical port
8.22.1 MXP10 supported modules

MXP10 card is an Eslot card in EXT-2U shelf of BG-64/NPT-1200/NPT1020, with two types of modules:
OM_AoC4 and OM_AoCP4 (not supported yet).
2 x 10G Muxponder: MXP10 + OM_AoC4 ( Line: 2 x OTU-2; Client: 16 any except CPRI)
 2 x 10G Muxponder with 4 x CPRI : MXP10 + OM_AoCP4 (Line: 2 x OUT-2; Client: 16 any, including CPRI
in 4 of 16)
 1 x 10G Transponder: MXP10
 1 x 10G Regeneration: MXP10
MXP10 supports following ODUk interfaces:
 ODU0
 ODU1
 ODU2
 ODU2e
 ODU2f
 ODUFlex
MXP10 supports following client signals:
 STM1/OC3
 STM4/OC12
 STM16/OC48
 STM64/OC192
 ETY1G(e)
 ETY10G WAN/LAN
 FC100/FC200/FC400/FC800/FC1200
 Video270/HDSDI1485/HDSDI3G
Once MXP10 is assigned, several virtual sub cards are created, including OM_TMU, OM10_2, and OM_AoC12.
 OM10_2 includes two line port;

 OM_AoC12 includes up to 12 clients ports, only port1 ~ port6 are shown in the initialization status.
 OM_TMU is the TMU module.
8.22.2 MXP10 slot assignment

To perform slot assignment for MXP10:

2. Right-click an Eslot and in the popup list, select the MXP10 card.

3. To assign subcards in the MXP10 card, right-click the subslot you want to assign, and then in the
shortcut menu, select a card to assign.

Set As Logical.

8.22.3 Define port rate and density

To define port rate and density:
1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, right-click
the OM_AoC12 card under MXP10 and from the shortcut menu, select Define Port Rate and Density.

2. From the Type dropdown list, set the type as Signal-SFP/SFP+ or Dual-CSFP as required.

3. Click Apply to save your settings. For if the port is set as the port rate type Dual-CSFP, then Port[n+6]
of the OM_AoC12 card will be created.

8.22.4 Manage ports

This section describes how to manage the ports in MXP10 card.
To manage ports in MXP10:

1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select the
MXP10 card. In the Configuration working mode General tab, you can view the general information of
MXP10.

2. To define the port type for the subcards OM10_2/OM_AoC12/OM_AoC4 in MXP10, right click the
subcard and from the shortcut menu, select Define Port Type. The Define Port Type window opens.

3. In the Port Type dropdown list, select a port type for the port as required, and then from the Container
Type dropdown list, select a relevant container type.

4. Click Apply and then you can view the configured ports in the left object tree.

5. To configure the ports in MXP10, in the left object tree, select the port and then in the Configuration
Configure the port as required and click Apply to save the settings.

6. To configure the MOs under the ports, in the left object tree, select the MO and then in the
Configure the parameters as required and click Apply to save the settings.

8.22.5 Perform ODU MSI configuration

ODU MSI configuration is only supported in the Muxponder mode, and is available only for the ODU2 module
under OM10_2 subcard.
To perform ODU MSI configuration:

1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, under the
OM10_2 subcard, select the ODU2 MO. Then in the Configuration working mode, select the MSI tab.

2. Enable or disable the MSI Monitor as required by selecting the corresponding radio button.
3. You can also configure the TPN of the Expected MSI as required.

8.22.6 Perform latency measurement

To perform latency measurement:
1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, under the
OM10_2 subcard, select the ODU2 MO. Then in the Maintenance working mode, select the Latency
Measurement tab.
2. To start latency measurement, click the Start Latency Measurement button.

8.23 TM10
TM10 is a 1588v2 timing card for D-slot of NPT-1010 NE, with the following features:
 Supporting IEEE1588 OC and TC capability
 1PPS+ToD interface
8.24 Tributary protection card

8.24.1 TPEH8_1
Electrical ETY ports can be protected in IOP with a new Tributary Protection (TP) card - TPEH8_1.
TPEH8_1 is a 1:1 Tributary Protection card for two groups of 4 x 10/100/1000 Base-T. It can only be assigned
in the Eslot 3 in the BG-30E/EXT-2U platform.
For details of managing TPEH8_1, see Working with Data Card IOP in the LCT-NPT Network Management
Guide.

9 Configure and manage cards in IP/MPLS
This section discusses how to use the LCT-NPT to configure and manage cards in IP/MPLS NEs.
9.1 Card Description of IP/MPLS NEs

This section lists card description of IP/MPLS NEs.
Table 9-1: Card description of IP/MPLS NEs

Card Name Supported in IP/MPLS NEs Description
NPT-1800 NPT-1200i
INF-1800 Y Input DC power supply for NPT-1800, provides 1800W.
FCU-1800 Y Fan unit for NPT-1800 with optional dust filter.
MCP-1800 Y Main control card for NPT-1800.

Provide control and management function to NPT-1800, support 1+1 Redundant
configuration, provide support to L3VPN.
CIPS1T Y Central Packet & OTN Switch card for NPT-1800, with 500G~800G Packet Processing & OTN
X.C and timing unit (SyncE & 1588V2).
No dedicate TCAM support interfaces.
MCIPS320 Y Central packet switching card with timing unit and four SFP+ based 10GE ports.
320Gbit/s packet switch (fan out up to 320Gbit/s) with IP/MPLS and MPLS-TP and PB
functionality.
IEEE1588v2 PTP and Sync-E
ECB-1800 Y External Connection Module for NPT-1800.
DHCE_1 Y Single HC Tslot 100Gbe card for NPT-1800 without OTN wrap, to support 100Gbe client
interface based on CFP2 and QSFP28 modules.
Sync-E supported.
DHCE_1C Y Single HC Tslot 100Gbe card for NPT-1800 with OTN wrap, to support 100GE long distance
interface, to provide 80km and above 100GE link, based on CFP modules.
Sync-E supported.
DHXE_2 Y Ethernet PHY IO card for T-slot with two SFP+ based 10GE ports, each is configurable between
10GBase-R and 10GBase-W.
Sync-E supported.
DHXE_4 Y Y Ethernet interface card supports up to 4 x 10GE without OTN ports.
DHXE_4O Y Y Ethernet interface card supports up to 4 x 10GE with OTN ports.
DHGE_4E Y Y Ethernet interface card supports up to 4 x 10/100/100BaseT ports.

Support PoE function (same with NPT-1200).
DHGE_8 Y Y Ethernet interface card supports up to 8 x GE/FX ports (CSFP support for 8 ports);
Two logic cards:
DHGE_8 (2*QSGMII)
DHGE_8S (4*SGMII)

LCT-NPT® User Guide Configure and manage cards in IP/MPLS
Card Name Supported in IP/MPLS NEs Description
NPT-1800 NPT-1200i
DHGE_8S Y Y Ethernet I/O card with 4 x 100/1000Base-X ports based on SFP and full bandwidth connection
to central packet switching matrix.
DHGE_16 Y Y Double-slot Ethernet interface card supports up to 4/8 x GE/FX ports (SFP/CSFP) and 8 x
10/100/1000BaseT ports.
DHGE_24 Y Y Double-slot Ethernet interface card supports up to 12/24 x GE/FX ports (SFP/CSFP).
DHGE_20 Y Ethernet PHY IO card for Tslot with 10 SFP/CSFP housing, each can be defined as one Gbe port
(with SFP) or two Gbe ports (with CSFP).
Sync-E supported.
MS1_4 Y Y CES card for Tslot with four STM-1/OC-3 or one STM-4/OC-12 interfaces.
Support SAToP and CESoPSN services and various encapsulations including CESoETH and
CESoMPLS;
Support CEP service based on VC-3, VC-4 and VC-4-4c;
Support CEP service based on STS-1, STS-3c and STS-12c.
MSC_2_8 Y Y Multiservice (mainly CES) Combo card with 2 x STM-1/OC-3 channelized or Bulk interfaces and
8 x E1/DS1 interfaces.
MSE1_32 Y Y MSE1_32 is an E1/T1 CES card for Tslot with 32 E1 interfaces, which can support SAToP and
CESoPSN services and various encapsulations including CESoETH and CESoMPLS.
NFVG_4 Y Y Cyber card with four optical Gbe ports.
INF_E2U Y Y Single feeding -48VDC power supply unit with input filtering for EXT-2U shelves.
AC_PS_E2U Y Y A double card of power supply unit for EXT-2U shelves.
FCU_E2U Y Y Fan control unit for EXT-2U shelf.
OBC Y Y Modularized Optical base card for Eslot with one sub slot for DCM and two sub slots for
amplifier modules.
9.2 Perform CSFP management in DH cards

In IP/MPLS NEs, for the Port 1~4 of DHGE_8/DHGE_16 and the port 1~12 of DHGE_24, the expected SFP type
is configurable to Single-SFP/SFP+ or Dual-CSFP. Comply with CSFP common management rule, once the
expected SFP type is Dual-CSFP on GE Port [n], GE Port [n+4] of DHGE_8/DHGE_16 and GE Port [n+12] of
DHGE_24 will be created from LCT-NPT.
This section describes how to configure Single-SFP/SFP+ and Dual-CSFP settings for DHGE_8. You can use the
same steps to configure Single-SFP/SFP+ and Dual-CSFP settings for DHGE_16/DHGE_24.

To perform CSFP management:

1. To define port rate and density, in the IP/MPLS NE Shelf View window, in the left object tree, right-click
DHGE_8, then select Define Port Rate and Density. The Define Port Rate and Density window opens.

Cage1 ~ Cage4 are editable, and there are two options:

 Single-SFP/SFP+
 Dual-CSFP
2. Set the port rates as Single-SFP/SFP+ or Dual-CSFP from the dropdown lists and click Apply to save the
settings.

3. Once the expected SFP type is set as Dual-CSFP on GE Port [n], GE Port [n+4] is created. You can view
the new created ports in the left object tree, as shown in the following figure.

4. In the IP/MPLS NE Shelf View window, in the left object tree, select an activated GE port of DHGE_8.
Then in the Configuration working mode, select the SFP/CSFP Setting tab.
5. Set Expected SFP Type and Expected Application Code as required from the corresponding dropdown
list.
9.3 Manage OTN ports in DHXE_4O

DHXE_4O is an Ethernet interface card that supports up to 4 x 10GE with OTN ports.
OTN wrapping is supported for 10GE ports in DHXE_4O. Different PHY types will create corresponding OTU
and ODU objects:
 10GBase-R
 10GBase-W - WIS
 10GBase-R over OTU2e Mapping - OTU2e, ODU2e
 10GBase-W over OTU2 Mapping - WIS, OTU2, ODU2

To manage OTN ports in DHXE_4O:

1. In the IP/MPLS NE Shelf View window, select a 10GE port of DHXE_4O in the left object tree, and then
in the Configuration working mode, select the General tab.
In the PHY Type field, you can select:

 10GBase-R: no object will be created under the 10GE port.
 10GBase-W: the WIS MO will be created under the 10GE port.
 10GBase-R with OTU2e Mapping: OTU2e and ODU 2e will be created under the 10GE port.

 10GBase-W with OTU2 Mapping: OTU2, ODU2 and WIS will be created under the 10GE port.
2. To configure the attributes for the WIS MO, select the Configuration working mode, and then select
the General tab.

3. To configure the OTU port, in the left object tree, select the OTU2/OTU2e object. Then click
Configuration and then the General tab.

4. To configure the ODU port, in the left object tree, select the ODU2/ODU2e object. Then click
Configuration and then the General tab.
9.4 Manage the CIPS1T card

CIPS1T is the Central Packet and OTN Switch card for NPT-1800, with 500G~800G Packet Processing and OTN
XC and timing unit (SyncE and 1588V2).
CIPS1T supports the following functions:
 Central Packet Processing Block
 Based on BCM Qumran-MX and X-point
 800 Gbps packet processor
 720 Mpps processing rate
 CPU Bock
 T1042 Processor with 4GB memory (DDR3L) + ECC
 16MB boot flash, 32MB file flash

 Communication interface:
 1G SGMII from CPS to both MCPs, for CBUS and in-band communication
 2.5G SGMII from CPS to both MCPs for HA
 1G SGMII between 2 CPS for communication
 1G SGMII between 2 FPGA in CPS for PTP
 Management data input/output (MDIO) to each Tslot
 Signals between CPS for Redundancy
 Interfaces for traffic
 4 lanes to each Tslot
 1 SGMII to each Eslot
 External interfaces:
 1PPS & ToD(RJ-45)
 T3/T4(RJ-45)
 1PPS monitor to ECB
 TMU Block
 SyncE TMU based on IDT3380
 1588 OC/BC based on IPC9000
 Master/slave indicate interface
 Active signal to each T/Eslot, ECB and both MCPs

To manage CIPS1T:
1. To view general information of a CIPS1T card, in the NPT-1800 NE Shelf View window, in the left object
tree, click Control and Physical Object and then CIPS1T. Then click the Configuration working mode
and then the General tab.

2. If two CIPS1T cards are assigned, you can perform equipment protection switch:
a. In the left object tree, select CS A: CIPS1T. Then click Maintenance and then the Equipment
Protection Switch tab.
b. You can view the working status of the two CIPS1T cards and set the switch command as required.
9.5 Manage MSC_2_8

MSC_2_8 is a multiservice (mainly CES) Combo card with 2 x STM-1/OC-3 channelized or Bulk interfaces and
8 x E1/DS1 interfaces in NPT-1800.
The following lists the main features of MSC_2_8 in IP/MPLS NEs:
 Intra-card MSP1+1 is supported;
 Cross-card MSP1+1 is supported, and vertical neighbor Tslots have interconnection for cross-card
MSP1+1;
 SDH/SONET framing mode is supported:
 When framing mode is SDH/E1:
 MSC_2_8 works in E1 CES mode – support two channelized STM-1 and 8 x E1 interfaces
 The system timing unit specification complies with ITU-T G.8262 option I;

 The SSM and timing source quality level (QL) definitions comply with G.781 option I.
 When framing mode is SONET/DS1:
 MSC_2_8 works in DS1 CES mode – support two channelized OC-3 interfaces and 8 x T1
interfaces;
 The system timing unit specification complies with ITU-T G.8262 option II;
 The SSM and timing source quality level (QL) definitions comply with G.781 option II.
9.5.1 Activate/Deactivate the MSC_2_8 ports

In IP/MPLS NEs, by default, the ports of MSC_2_8 are not activated. You can activate or deactivate the ETY
ports manually. This section describes how to activate/deactivate the ports of MSC_2_8 in IP/MPLS NEs.
To activate/deactivate ports of MSC_2_8:

1. In the IP/MPLS NE Shelf View window, in the left object tree, right-click a MSC_2_8 card, or right-click
an ETY port under a MSC_2_8 card, and from the shortcut menu, select Activate/Deactivate Port. The

2. In the Activate list, select the required checkbox(es) to activate or deactivate the port(s).
3. To batch edit the mode, on the toolbar, click . Then click to select the required operation as
you need.

9.5.2 Configure the MSC_2_8 card

To configure MSC_2_8 in IP/MPLS NEs:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the MSC_2_8 card. Then in the
Configuration working mode, click the General tab.
You can view the general information of MSC_2_8 from the window.

2. To set the card parameters of MSC_2_8, click the Card Parameters tab.
You can configure Different Timestamp Frequency, MAC SA Check in this window, which are only for
CES card. The MAC Address is read only.
9.5.3 Activate VC12/E1 and VT1.5/DS1

For NPT-1800 in SDH/E1 framing mode, you can activate/deactivate the VC12/E1 in MSC_2_8 card.
For NPT-1800 in SONET/DS1 framing mode, you can activate/deactivate the VT1.5/DS1 in MSC_2_8 card.

To activating VC12/E1 in SDH framing mode:

1. In the IP/MPLS NE Shelf View window, in the left object tree, click MSC_2_8, STM Port and then right-
click a VC4.

2. From the shortcut menu, click Activate/Deactivate VC12/E1. The Activate/Deactivate VC12/E1
window opens.
3. Select the VC12 you want to activate and click Apply. The corresponding VC12 will be activated.

4. To configure parameters of activated VC12 object:

a. In the left object tree, select the VC12, then click Configuration working mode and then the
General tab.
b. Set the TTL and SLM attributes as required.


To activating VC12/E1 in SONET framing mode:

1. In the IP/MPLS NE Shelf View window, in the left object tree, click MSC_2_8, OC3 Port and then right-
click the STS.

2. From the shortcut menu, click Activate/Deactivate VT1.5/DS1. The Activate/Deactivate VT1.5/DS1
window opens.
3. Select the VT1.5 you want to activate and click Apply. The corresponding VT1.5 will be activated.

4. To configure parameters of activated VT1.5 object:

a. In the left object tree, select the VT1.5, then click Configuration working mode and then the
General tab.
b. Set the TTL and SLM attributes as required.


9.5.4 Manage MSP1+1

To manage the MSP1+1 in IP/MPLS NEs:
1. In the IP/MPLS NE Shelf View window, in the object tree, select the NE. In the Configuration working
mode, select the MSP-Linear tab.

2. To create a PG:
a. On the toolbar, click . The Create PG window opens.

b. Set a PG name in the PG Name field.

c. To create an intra-card PG, select the relevant STM ports in one MSC_2_8 card.
Click Apply. If the PG creation is successful, the green icons adjacent to the ports turn gray.

d. To create a cross-card PG, select two MSC_2_8 card in the Main and Protection lists.
Click Apply. If the PG creation is successful, the green icons adjacent to the ports turn gray.

3. Close the Create PG window, you can view the PG list.
4. To overwrite the data to the database, on the toolbar, click .

5. To clear the PGs in the list, on the toolbar, click .

6. To delete a PG, right-click the PG you want to delete and click Delete PG/Delete Card PG. Or on the
toolbar, click .
7. You can also perform MSP 1+1 maintenance operation for the port level PGs, including:
 Lockout of Protection
 Force Switch to Protection
 Force Switch to Main
 Manual Switch to Protection
 Manual Switch to Main
9.6 Perform port rate settings in MS1_4

This section describes how to perform port rate settings in MS1_4 card of IP/MPLS NEs.
Make sure that all the ports of MS1_4 are deactivated.

To perform port rate settings:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the MS1_4 card. Then select
Configuration > Rate Setting. The Rate Setting window opens.

3. To change the port rate, click Apply.
9.7 Manage the MCP-1800

MCP-1800 is the main control card for NPT-1800. It provides control and management function to NPT-1800,
supports MCP 1+1 redundancy configuration, and provides support to L3VPN.
MCP-1800 1+1 or 1+0 configuration is supported:
 MCP 1+0 configuration
 Only one MCP is assigned
 MCP 1+1 configuration
 Two MCP are assigned in MS A and MS B

To manage the MCP-1800:

then MCP.
2. To view the general information of MCP-1800, click Configuration and then select the General tab. The
general information of MCP-1800 is displayed.

3. If two MCP-1800 cards are assigned, you can perform MCP 1+1 Redundancy configuration:
a. Under the Configuration working mode, click the Redundancy tab.
Configure the MCP Redundancy attribute configuration as described here:

 Primary Card: indicate MCP in which slot is as primary card. It determines which one is selected
to be Active if other voting conditions are identical.
 High Availability (HA) Administration Status: enable or disable. No switch over and no sync if HA
is disabled.
 Auto SwitchOver: enable or disable automatic switchover. When Auto Switchover is disabled, HW
and SW failures will not trigger switch over.
 Auto Configuration Synchronization: enable or disable automatic configuration synchronization
of standby card.
 When it is disabled, no DB sync will be done automatically.
 When it is enabled, synchronize the configuration file on the active MCP to the standby MCP
every time you commit a configuration.
 High Availability Retry: set the HA retry time between 0~1440 minutes. )
b. To save the settings, click Apply.

c. To synchronize the information, on the toolbar, click .

d. You can view the redundancy status in the Status field.

4. To view system resources, under the Configuration working mode, select the NE System Resources
tab.
You can view the system resources information which includes CPU, Memory and File System.

5. If two MCP-1800 cards are assigned, you can perform equipment protection switch:
a. In the left object tree, select MS A: MCP-1800. Then click Maintenance and then the Equipment
Protection Switch tab.
b. You can view the working status of the two MCP cards and set the switch command as required.
9.7.1 Manage the CF card

NVM (CF) card is extractable and supports hot-swapping. It can be managed in the similar way like a card. CF
card need not assignment, and it is an indispensable part of IP/MPLS NEs. CF live-insertion is supported.
CF card management includes:
 CF card is extractable from front panel and supports hot-swapping;
 CF card has a present signal connected to GPIO;
 Once the cover of the CF card is taken out, a HW signal will be connected to interrupt to inform CPU of
extraction;
 CF card has a cover with push button and two LEDs: ACT. (Green) and Fail (Red).

To view the information of the CF card:

1. In the NPT-1800/NPT-1200i NE Shelf View window, in the left object tree, select MCP-1800/MCIPS320.
Then click the Configuration working mode and then the CF Card tab.
2. You can view the general information and inventory of the CF card.
9.8 Manage the MCIPS320

MCIPS320 is a control and 320Gbps central switch card for NPT-1200i to support IP/MPLS and L3VPN. It
consists of main controller (MCP), 320G central packet switch, EEC timing unit and IEEE1588v2 timing unit,
and four 10GE aggregate ports (SFP+ based). It is the main card of NPT-1200i IP/MPLS system.
The management of MCIPS320 including:
 View System Resources: include CPU/Memory/File System;
 If two MCIPS320 cards assigned:
 Support configuring MCP Redundancy;
 Support configuring Equipment Protection Switch.
For details about viewing system resources, see View NE system resources.
For details about performing MCP Redundancy configuration, see Manage the MCP-1800.
For details about configuring equipment protection switch, see Manage the CIPS1T Car d.

9.9 Manage power units of IP/MPLS NEs

INF-1800 is the input DC power supply for NPT-1800. It provides 1800W Power supply. You can perform slot
assignment for the power unit shelf in IP/MPLS NEs.
NPT-1800 supports INF-1800 1+1 or 1+0 configuration for DC power supply: both redundant INF (1+1 mode)
and non-redundant INF (1+0 mode).
The power function of NPT-1200i is the same with NPT-1800.
To manage power units of NPT-1800/NPT-1200i:

1. To view the general information of INF-1800/INF-1200, in the NPT-1800/NPT-1200i NE Shelf View
window, in the left object tree, under Control and Physical Object, select INF-1800/INF-1200i.

3. To view the status of INF-1800, in the Configuration working mode, select the Status tab.

9.10 Manage the fan units of IP/MPLS NEs

This section describes how to manage the fan units of IP/MPLS NEs - NPT-1800 and NPT-1200i NEs.
9.10.1 Manage the fan units of NPT-1800

The fan unit of NPT-1800 is different from FCU in NPT-1200/NPT-1050/NPT-1020, the fan control is more
flexible in NPT-1800. It is similar as Apollo product.
FCU-1800 has 8 FANs, which are arranged in FAN shelf as illustrated in the following figure.
Figure 9-1: FCU-1800 FAN number and arrangement
FANs in FCU-1800 are arranged in the following manner:

 View from management, eight FANs are managed independently.
 View from control, eight FANs are managed by four fan pair, each pair is controlled independently:
 Pair1 (fan1, fan2)
 View from FAN power, separated to two group at physical level, each group has independent power
control:
 Pow_group1 (1, 4, 5, 8)
 Pow_group2 (2, 3, 6, 7)
Arranged by this way, even if one tributary power if failed, the other four fans can still work.

To manage FAN units of NPT-1800:

1. To view the general information of FCU-1800, in the NE Shelf View window, in the left object tree,
select the FCU-1800 object, then select the General tab under the Configuration working mode.

2. To manage the Fan control of NPT-1800:

a. Select the Fan Control tab.
b. FCU-1800 supports controlling fan rate per pair (up to 4 pairs).


9.10.2 Manage the fan units of NPT-1200i

To manage FAN units of NPT-1200i:
1. To view the general information of FCU-1200, in the NPT-1200i NE Shelf View window, in the left object
tree, select the FCU-1200 object, then select the General tab under the Configuration working mode.

2. To manage the Fan control of NPT-1200i:

a. Click the Fan Control tab.
b. (Optional) Configure the Fan Speed Control Mode as Automatic or Force Turbo.

10 Configure timing source
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 to form a synchronous clock table, which is then sent 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 Timing Settings window.
10.1 Set 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 NE time, and
it is this time that determines alarms and events. The real time of the PC refers to the current time of the
LCT-NPT PC. The NE time and the LCT-NPT PC time must 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 and then NE Time Setting. The NE Time Setting
window opens.

LCT-NPT® User Guide Configure timing source
2. To read the system time of the PC directly, click , or enter the time manually.
3. To get the NE time, click .

4. Click Apply. The settings are applied.
10.2 Manage NTP configuration

Network Time Protocol (NTP) is a protocol used to synchronize the clocks in computers, routers, and other
network devices. There are many stratum-1 and stratum-2 time servers on the Internet that are synchronized
to UTC via radio, satellite or modem. Stratum-1 servers are synchronized to a reference clock, while stratum-
2 servers are synchronized to stratum-1 servers.
From NPT V4, Network Time Protocol (NTP) version 4 is supported in NPT NEs and EMS server in order to
synchronize the time of date of the network more accurately. The time and date of EMS can be synchronized
to other clock source through NTP.
The following NTP functions are supported in NTP-V4:
 NTP Enabled/Disabled
 Configurable NTP version for each server or client
 NTP operational Modes
 Server
 Client
 NTP Protocol Modes
 Client/Server
 NTP message transmission and reception
In IP/MPLS NEs:
 NTP protocol supported in IP/MPLS NEs is configurable, and it is enabled by default;
 One or more NTP servers can be configured;

 NTP broadcast and multicast protocols are supported;

 NTP Authentication is supported.
10.2.1 Perform NTP configuration

SNTP configuration is supported in NPT-1200, NPT-1020, NPT-1050 and NPT-1010 NEs.
To perform NTP configuration:

1. In the NE Shelf View window, in the left object tree, select the NE, and then in the Configuration menu,
select NTP Configuration.
2. In the opened NTP Configuration window, select the Configuration tab.
3. In the General area, select the NTP Enable checkbox to enable NTP function.
4. In the NTP Setting area:
a. Select the NTP Unicast Client Enable checkbox to enable NTP unicast client.
b. Click + to add a server in unicast client. Up to 4 servers can be added in unicast client.
c. Set one or more of the following parameters for the added server:
 Server Address: set the IP address of the remote NTP system.
 Preferable: it indicates the NTP Server is preferred over any other configured.

 Version: it indicates the version of NTP packets you want the switch router to send, from
version 1 to version 4.
 Min Poll: it indicates the minimum polling interval, from 16 to 16,384 seconds. The
minimum polling interval must be less than the maximum polling interval.
 Max Poll: it indicates the maximum polling interval, from 16 to 16,384 seconds. The
maximum polling interval must be greater than the minimum polling interval.
d. Select the NTP Server Enable checkbox to enable NTP server mode. In V4, only Unicast server
mode is supported.
5. Click Apply. The NTP configuration settings are applied.
6. To synchronize EMS time to NE, click .
7. To propagate the attributes of the NE to other NEs, click . The Propagate Properties Window opens.
8. From the left NEs list, select one or more NEs to propagate, and click Propagate to complete the
propagate operation.

10.2.2 Perform NTP configuration in IP/MPLS

To perform NTP configuration in IP/MPLS:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE, and then in the
Configuration menu, select NTP Configuration.
2. In the opened NTP Configuration window, select the Configuration tab.
3. In the General area, the NTP function is enabled by default.

4. In the Authentication Key area, click + to add authentication keys. Then set the parameters for each key
as required.

5. In the NTP Setting area:

a. NTP Unicast Client Enable: If it is enabled, click + to add a server in unicast client. Up to 4 servers
can be added in unicast client.
b. Symmetric Mode Configuration: Up to 4 servers can be added in unicast client.
c. Boot Server: Click + to add a boot server.
6. Click Apply. The NTP configuration settings are applied.
7. To synchronize EMS time to NE, click .
8. To propagate the attributes of the NE to other NEs, click .
10.2.3 View NTP association and status

You can view the following SNPT association attributes per association:
 Remote Address: IP address or host name of the remote NTP peer.
 Reference ID: Reference ID of the remote peer. If the reference ID is unknown, the field displays 0.0.0.0.
 Reference Time: Reference time of the remote peer.
 Stratum: Stratum of the remote peer.
 Type: Type of peer.
 When: Number of seconds since the last packet was received.
 Poll: Polling interval.
 Reach: Reachability register, in octal.
 Delay: Estimated delay of the peer, in seconds.
 Offset: Estimated offset of the peer, in seconds.
 Disp: Estimated dispersion of the peer, in seconds.
 Peer Selection Status: Indicates specifics about peer selection:
 (Space) – not used because of high stratum value or failed sanity check
 x – designated falseticker by the intersection algorithm
 . – culled from the end of the candidate list
 - – discarded by the clustering algorithm
 + – included in the final selection set
 # – selected for synchronization but distance exceeds maximumallowed distance
 * – selected for synchronization
 o – selected for synchronization, PPS signal in use.

To view NTP association and status:

1. In the NE Shelf View window, in the left object tree, select the NE, and then in the Configuration menu,
select NTP Configuration.
2. In the opened NTP Configuration window, select the Status tab.
3. To retrieve the NTP status from NEs, click . The NPT association attributes and status are displayed.
10.3 Configure the synchronous timing table

A Synchronous Timing Table determines synchronous timing for SDH equipment. The table enables you to
determine the selection range of NE references, and customize the attributes of each external reference. It
also 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 NE’s current configuration. The NE equipment can select as its synchronous timing source the
reference in this table with the optimum quality.
Each clock reference has multiple 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 LCT-NPT.
NOTE: No configuration change is required to extract 2 MHz clock output. If an internal timing
source is selected, the other settings are ignored.

To configure synchronous timing for the BG-40:

1. In the BG-40 NE Shelf View window, in the left object tree, select Control and Physical Object and then
MXC4X, and in Configuration working mode, select the Timing Settings tab. The following window
opens. The Clock Availability Status list indicates whether the clock reference is currently available.
This list is read only and cannot be modified.
2. To retrieve the information to view, click , and select the relevant external references for the clock.
3. To send the external clock references to the NE, click Apply.
4. To set the external clock configuration, on the toolbar, click . The External Clock Configuration
window opens.

5. Select 2MHz or 2Mbps as required, and click Apply to save the setting.
To configure synchronous timing for the BG-20/BG-20C:

1. In BG-20/BG-20C NE Shelf View window, in the left object tree, select Control and Physical Object and
then TMU, and in Configuration working mode, select the Timing Settings tab. The following window
opens.
2. For each timing priority, select the corresponding external references for the clock.

To configure synchronous timing for the BG-30:

1. In BG-30 NE Shelf View window, in the left object tree, select Control and Physical Object and then XS
A: TMU, and in Configuration working mode, select the Timing Settings tab. The following window
opens.

To configure synchronous timing for the BG-64/NPT-1200:

1. In the BG-64/NPT-1200 NE Shelf View window, in the left object tree, select Control and Physical
Object and then XS: TMU, and in Configuration working mode, select the Timing Settings tab. The
following window opens.

To configure synchronous timing for the NPT-1020/NPT-1010:

1. In the NPT-1020/NPT-1010 NE Shelf View window, in the left object tree, select Control and Physical
Object and then BS: TMU, and in Configuration working mode, select the Timing Settings tab.
a. The following window shows the timing settings of NPT-1020.
b. The following window shows the timing settings of NPT-1010.


To configure synchronous timing for IP/MPLS NEs:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select Control and Physical Object and
then CS: TMU-1800, and in Configuration working mode, select the Timing Settings tab. The following
window opens.
10.4 Configure synchronous ethernet

In LCT-NPT, the GE/10GE ports of the following cards can support synchronous Ethernet:
 ME_2G_4F
 MPS_2G_8F
 DMGE_4_L2
 DMGE_8_L2
 DMXE_48_L2
 MPOE_12G
 DMXE_22_L2

 AMXE_2 (CPTS100/CPS100)
 DHGE_4E
 DHGE_8
 DHGE_16
 DHGE_24
 DHXE_4
 MGE_12
 CPS50
 MGE_8 (MCPS_1010)
The following figure indicates the hybrid SDH/synchronous Ethernet/Radio/PTP Synchronous Equipment
Timing Source (SETS) function with two timing domains.
Figure 10-1: Equivalent selection mechanism of an SDH SETS function
The figure shows the equivalent selection mechanism of an SDH SETS function that has been adapted to
hybrid SDH/synchronous Ethernet equipment with synchronous Ethernet and SDH interfaces. ETY and STM-
N input (TE and T1) and output (T0) represent the various Ethernet traffic interfaces (100Base-X, 1000Base-
T, etc.) and SDH traffic interfaces. The Synchronous Equipment Timing Generator (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 SONET 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 synchronous Ethernet:

1. In the NE Shelf View window, in the topology tree, select a GE-ETY/10 GE-ETY port under the card that
supports synchronous Ethernet, and then in the Configuration working mode, select the General tab.
2. To configure the synchronous Ethernet, select the following related attributes:

 PHY Type: The synchronous Ethernet attributes are effective only when this field is configured as
1000Base-X or 10/100/1000Base-T. For Optical port of MPS_2G_F, ME_2G_4F, MPOE_12G,
DHGE_8, DHGE_16, DHGE_24, MGE_8 and MGE_16, the 100Base-FX can also support SyncE, and
for AMXE_2, DMXE_22_L2 and DMXE_48_L2, the 10GE port can also support SyncE.
 Master-slave Manual Configuration: Options are enable (master-slave configuration is
configured manually) or disable (configuration is negotiated automatically (auto-negotiated)).
 Local Master-slave Mode: Only available when Master-slave Manual Configuration is enabled.
Defines the value of local PHY during negotiation (Master or Slave).
 Master-slave Resolution: Read-only attribute indicating the current status of PHY master/slave
resolution. Can be Master or Slave depending on real resolution of current 1000BaseT link. It is
N/A when current PHY is not working in 1000BaseTx mode.

 ESMC Generation: For an ETY port, Synchronization Status Message (SSM) is carried through the
Ethernet Synchronization Messaging Channel (ESMC). SSM definition is the same as the SDH port
per ITU-T G.781, and the rules of SSM generation and reception are the same as G.781 (such as
loop prevention, QL change, SSM delay, etc.). It should be configured as Enable when the ETY port
is selected as timing source and SSM is enabled. Otherwise, DNU cannot be sent out.
3. To set the TMU configuration for supporting synchronous Ethernet, in the left object tree, select
Control and Physical Object and then XS:TMU, and in the Configuration working mode, select the
Timing Settings tab.
4. From the Timing Source dropdown list, select a timing source and then set its relevant parameters as
required.
The timing sources are named as TS1 and TS2 in LCT-NPT. TS1 or TS2 can be derived from any Sync-E
port in the card by setting Channel. For example, for the timing source "TS1: DMXE_48_L2_TS2", TS1 is
the slot number and TS2 means the 2nd timing source of TS1.
In the following table, only the ports whose Sync-E support field is Yes can be selected as a timing
source. Sync-E support means being able to be selected as a nominated TE/T4 timing source of TMU.
Only T1 (SDH Port), T3 (2Mbps\2MHz), TE (Sync_E) and PTP can be selected as T4 timing source of TMU.
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/NPT-1200E E-slot

 2 for BG-30B/BG-64/NPT-1200 T-slot

If a GE port has been selected as a timing source, the current PHY Type cannot be changed to the PHY
Type whose TE Capable is No in the preceding table, and the Local Master-slave Mode cannot be set
as Master.
NOTE: 1000Base-T can be effective synchronization source only when it works in slave mode.
If ETY is defined an internal port - iETY, it cannot be selected as timing source.
Table 10-1: Synchronous Ethernet capability of Layer 2 cards

Card type ETY port PHY type Sync-E support
DMGE_4_L2 GbE 1#~4# 1000Base-X Yes
(SFP only) 1000Base-T No
10/100/1000Base-T No
DMGE_8_L2 GbE 3#~8# 1000Base-X Yes
10/100/1000Base-T No
ME_2G_4F GbE 1#~2# 1000Base-X Yes
(COMBO) 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# 1000Base-X Yes
(COMBO) 100Base-FX Yes
10/100/1000Base-T Yes
FE 1#~8# 10/100Base-T No
DMXE_48_L2 10GE 1#~4# 10GBase-R Yes
10GBase-W Yes
GbE 2#~7# 1000Base-X Yes
10/100/1000Base-T No
MPOE_12G GbE 1#~4# 1000Base-X Yes
(SFP only) 100Base-FX Yes
1000Base-T No
10/100/1000Base-T No
GbE 5#~12# 10/100/1000Base-T Yes
(RJ45 only)
DMXE_22_L2 10GE 1#~2# 10GBase-R Yes
10GBase-W Yes


GbE 1#~2# 1000Base-X Yes
10/100/1000Base-T No
AMXE_2 10GE 1#~2# 10GBase-R Yes
(CPTS100/CPS100) 10GBase-W Yes
DHGE_4E Gbe 1#~4# 10/100/1000Base-T Yes
DHGE_8 Gbe 1#~4# 100Base-FX Yes
1000Base-X Yes
10/100/1000Base-T No
1000Base-T No
Gbe 5#~8# 10000Base-X Yes
DHGE_16 Gbe 1#~8# 10/100/1000Base-T Yes
Gbe 9#~12# 100Base-FX Yes
1000Base-X Yes
10/100/1000Base-T No
1000Base-T No
Gbe 13#~16# 100Base-FX Yes
10000Base-X Yes
DHGE_24 GbE 1#-12# 100Base-FX Yes
1000Base-X Yes
10/100/1000Base-T No
1000Base-T No
GbE 13#-24# 100Base-FX Yes
10000Base-X Yes
GbE 1#-8# 10/100/1000Base-T Yes
MGE_12
(MXC-1020) GbE 9#-12# 100Base-FX Yes
1000Base-X Yes
10/100/1000Base-T No
1000Base-T No
CPS50 10GE 1#-4# 10GBase-R Yes
10GBase-W Yes
GE 1#-2# 1000Base-X Yes
GE 3#-4# 1000Base-X No
DHFE_12 FE 1#-12# 10/100Base-T No
DHFX_12 FX 1#~12# 100Base-FX No
GbE 1#-4# 10/100/1000Base-T Yes


GbE 5#-8# 100Base-FX Yes
MGE_8
1000Base-X Yes
(MCPS_1010)
10/100/1000Base-T No
1000Base-T No
10.5 Precision Time Protocol (PTP)

IEEE1588 is named Precision Time Protocol. The PTP standard specifies a clock synchronization protocol. This
protocol is applicable to distributed systems consisting of one or more nodes, communicating over a network.
Nodes are modeled as containing a real-time clock that may be used by applications within the node for
various purposes such as generating timestamps for data or ordering events managed by the node. The
protocol provides a mechanism for synchronizing the clocks of participating nodes to a high degree of
accuracy and precision.
The following mainly describes the PTP functions.
PTP Domain
The protocol executes within a logical scope called a domain. Unless otherwise specified, all PTP messages,
data sets, state machines, and all other PTP entities are always associated with a particular domain. A given
physical network and individual devices connected to the network can be associated with multiple domains.
Within this standard, the time established within one domain by the protocol is independent of the time in
other domains. A domain consists of a logical grouping of clocks communicating with each other using the
PTP protocol.
PTP domains are used to partition a network within an administrative domain. The PTP messages and data
sets are associated with a domain and therefore the PTP protocol is independent for different domains. For
the purpose of this profile, PTP domains are established by using unicast messaging to ensure isolation of
grandmaster clocks. A clock (slave or master) must not take any information from a PTP domain and use it to
influence the behavior of a clock in another PTP domain. Note that there is only a single packet master clock
per PTP domain. Within a PTP domain, the domain number will be the same for all clocks.
PTP Device Types
There are five basic types of PTP devices, as follows:
 Ordinary Clock (OC)
 Boundary Clock (BC)
 End-to-end Transparent Clock
 Peer-to-peer Transparent Clock (not supported)
 Management Node (not supported)

All five types implement one or more aspects of the protocol. The following figure shows the examples of
different types of PTP devices.
Figure 10-2: Examples of different types of PTP devices
The two supported devices can be described as follows:

 Ordinary Clock - An ordinary clock communicates with the network via two logical interfaces (Event and
General) based on a single physical port. An ordinary clock can be either a slave (Ordinary Clock 2 ~ 5)
or a master (Ordinary Clock 1) when there is only one slave communicates with this master).
 End-to-End Transparent Clock - End-to-end transparent is a transit node between Master and Slave, it
measures the delay (the time the PTP event message takes to traverse the node) and updates the
CorrectionField in the PTP event packages by adding this delay. E.g., End-to-end Transparent Clock 1 in
the preceding figure updates the CorrectionField in the PTP event packages from Boundary Clock 1 to
Ordinary clock 2 by adding the timing stamping difference between event packages sending towards C
and receiving from B, and updates the CorrectionField in the PTP event packages from Ordinary clock 2
to Boundary Clock 1 by adding the timing stamping difference between event packages sending
towards B and receiving from C. The purpose of End-to-End transparent clock is to reduce the effects
from the PDV and network asymmetries for the slave node. The following figure shows an example of
End-to-End Transparent Clock.
Figure 10-3: Example of End-to-End Transparent Clock
<residenceTime> = egress timestamp – ingress timestamp.

The following shows a model of an E2E TC.

Figure 10-4: Model of an E2E TC
The E2E TC forwards all messages just as a normal bridge, router, or repeater. However for PTP event
messages (including Sync and Delay_Req), the residence time bridge, shown in the preceding figure,
measures the residence time of PTP event messages (the time the message takes to traverse the
transparent clock). These residence times are accumulated in a special field, the correction field, of the
PTP event message (Sync or Delay_Req) or the associated follow up message (Follow_Up or
Delay_Resp). This correction is based on the difference in the timestamp generated when the event
message enters and leaves the transparent clock. Any updates to checksums required by the network
protocol are made. Note that the value of the correction update and checksums are specific to each
output port and message since the residence times are not necessarily the same for all paths through
the transparent clock or for successive messages on the same path.
An E2E TC may be used as a network element or it may be associated with an ordinary clock.
There are two types of TC: One-step TC and Two-step TC. Note that, the mode here is related to TC,
rather than Master. Usually Slave should be able to intemperate with One-step Master or Two-Step
Master automatically (no need to configure one-step/two-step mode to Slave). Some Master can work
in Two-step mode only due to HW limitation. E.g. the IPClock FPGA based solution currently supported
in our products as a Master can work in Two-step mode only. Some Master may be able to work in
either Two-step or One-step mode, thus a configuration of the working mode may be needed.
For One-step E2E TC, the <residence_time> shall be added to the correctionField of the Sync/
Delay_Req message by the egress port of the clock as the Sync/Delay_Req message is being
transmitted.

For Two-step E2E TC, the <residence time> shall be added to the correctionField of the
Follow_Up/Delay_Resp message associated with the Sync/Delay_Req message prior to transmission on
the egress port.
PTP Messages
The section defines event and general PTP messages. Event messages are timed messages in that an accurate
timestamp is generated at both transmission and receipt. General messages do not require accurate
timestamps.
The set of event messages consists of:
 Sync
 Delay_Req
 Pdelay_Req
 Pdelay_Resp
The set of general messages consists of:
 Announce
 Follow_Up
 Delay_Resp
 Pdelay_Resp_Follow_Up
 Management
 Signaling
The Sync, Delay_Req, Follow_Up, and Delay_Resp messages are used to generate and communicate the
timing information needed to synchronize ordinary and boundary clocks using the delay request-response
mechanism. The Pdelay_Req, Pdelay_Resp, and Pdelay_Resp_Follow_Up messages are used to measure the
link delay between two clock ports implementing the peer delay mechanism. The link delay is used to correct
timing information in Sync and Follow_Up messages in systems composed of peer-to-peer transparent clocks.
Ordinary and boundary clocks that implement the peer delay mechanism can synchronize using the
measured link delays and the information in the Sync and Follow_Up messages. The Announce message is
used to establish the synchronization hierarchy.
The management messages are used to query and update the PTP data sets maintained by clocks. These
messages are also used to customize a PTP system and for initialization and fault management. Management
messages are used between management nodes and clocks. The signaling messages are used for
communication between clocks for all other purposes. For example, signaling messages can be used for
negotiation of the rate of unicast messages between a master and its slaves. All messages can be extended
by means of a standard type, length, value (TLV) extension mechanism. For example, the PATH_TRACE
message extensions can be used to detect rogue frames.
Message Rates
The message rate values are only defined for protocol interoperability purposes. It is not expected that any
system clock shall meet the relevant target performance requirements at all packet rates within the given
range, specifically at the lower packet rate. The appropriate value depends on the clock characteristics and
on the target performance requirements. Different packet rate needs may also apply during the stabilization
period.

The following messages can be used and the corresponding indicated rates must be respected for unicast
messages:
 Sync messages (if used, Follow_up messages will have the same rate)
 Delay_Req/Delay_Resp message
 Announce messages
PTP Modes
The following describes several modes of operation between a master and a slave, with respect to
functionality needed to be compliant with this profile.
 One-step vs Two-step clock mode
PTP defines two types of clock behaviors: the "one-step clock" and the "two-step clock". In a one-step
clock, the precise timestamp is transported directly in the Sync message. In a two-step clock, a
Follow_Up message is used to carry the precise timestamp of the corresponding Sync message. The use
of Follow_Up messages is optional in the PTP protocol.
 Unicast and Multicast mode (In LCT-NPT, only unicast mode is supported.)
PTP allows the use of unicast and multicast modes for the transmission of the PTP messages. Depending
on the way multicast is used in a network, the use of the multicast mode for the PTP Delay_Req and
Delay_Resp messages may not be appropriate in a telecom environment. In some cases, it could lead
to a situation where the Delay_Req and Delay_Resp messages would be replicated and potentially
distributed to multiple nodes, consuming network resources. It other cases, this issue may not occur.
Moreover, multicast may not always be supported in all the parts of a telecom network. Multicast may
also generate additional PDV when compared to unicast. Unicast mode solves those issues, but has
some drawbacks for the sync, Follow_Up and Announce messages; instead of having a unique flow for
those messages that is sent to all slaves, one dedicated flow per slave has to be sent by the master.
Therefore, depending on the network environment, the use of multicast for sync, follow up and
Announce messages may sometimes be a better option in order to reduce the traffic load on the
master. However, the use of multicast messages for Delay_Req and Delay_Resp messages requires
further study in a telecom environment, in order to avoid the replication issues described here.
Two modes may be suitable for transporting the PTP timing messages in a telecom environment:
 Unicast mode: where the PTP Sync, Follow_up, Delay_Req, Delay_Resp, Announce and Signaling
messages are sent in unicast.
 Mix of unicast and multicast modes: where the Sync, Follow_Up and Announce messages are sent
in multicast, and the Delay_Req, Delay_Resp and Signaling messages are sent in unicast.
Transport of PTP
PTP is an application layer protocol, and it can be transported over various underlying network protocols,
including UDP/IPv4, UDP/IPv6, and IEEE802.3/Ethernet etc. Transport encapsulation of PTP over UDP/IPv4 is
supported. The following figure shows the PTP Stack over UDP/IPv4/Ethernet.

Figure 10-5: PTP stack over UDP/IPv4/Ethernet
In PB network, we create L2 MPtMP service to connect the PTP Masters and Slaves. PTP message
encapsulation we support is PTP over UDP over IPV4 over Ethernet (can be untagged, or with 1 or 2 VLAN
tagged). PTP messages are forwarded in VSI in each node between Master and Slave hop-by-hop. Thus E2E
TC is applicable in all Nodes between Master and Slaves.
E2E TC enabling should be on per VSI basis. In order to enable the E2E TC for the VSI, you should create "For
PTP" VSI which is usually dedicatedly for PTP.
In MPLS network, we create VPLS/H-VPLS service to connect PTP Masters and Slaves. PTP master and slave
are connected via PWs that passes through many transit nodes (Ps). The PTP message encapsulation we
support is PTP over UDP over IPv4 over Ethernet (untagged or with 1 VLAN tagged) over PW over Tunnel over
Ethernet.
Timing PWs for E2E TC
If E2E TC cannot be implemented for PTP flow in Ps, the value of E2E TC in MPLS network is reduced
significantly. But in transit nodes, to detect PTP messages inside LSPs require special hardware to do deep
packet inspection at line rate.
We use a new approach based on Timing PWs:
 Dedicated VPLS/H-VPLS for PTP with Timing PWs
 Define a continuous VC Label space (within Regular + VC Label space) for Timing PWs for easy HW
parser : 0x3E00~0x3FFF, referred to as Timing VC Labels
 Timing PW should have in VC Label and out VC Label in Timing VC Label space
 VPLS/H-VPLS for PTP can have ETY via "PTP Aware" ports, and Timing PWs only, and cannot have
regular PWs
 Regular VPLS/H-VPLS cannot have Timing PW
 Keep "PTP Aware" attribute for Bidi-LSP
 This attribute is R/W
 1588-aware Bidi-LSPs do not require new and continuous label space
 1588-aware Bidi-LSPs must be via "PTP Aware" ports

 1588-aware Bidi-LSPs can be protected by FRR

 For LSP1:1 Bidi-LSP, Primary and Secondary Bidi-LSP must have the same value in attribute "PTP
Aware"
 Timing PW must go via "PTP Aware" Bidi-LSP
 Regular PW can go via "PTP Aware" Bidi-LSP as well
 This attribute has two purposes:
 Give better visibility of PTP distribution for NMS
 Might make NPU parser more efficient (for transit XC, VC-Label inspection should be done
for "PTP Aware" LSPs) – BG will not take this advantage while XDM might
 BG will do E2E TC processing for all PWs with VC label in the range 0x3E00~0x3FFF, regardless whether
the PW is in "PTP Aware" LSP or "none PTP Aware" LSP
 As packet analyzer in VSC PTP PHY can support up to 8 flows per port for ETY port, we can support up
to 8 "For PTP" VPLS/H-VPLS
PTP Synchronization
There are two phases in the normal execution of the protocol: Establishing the master-slave hierarchy and
Synchronizing the clocks.
 Establishing Master-Slave Hierarchy
Within a domain, each port of an ordinary and boundary clock executes an independent copy of the
protocol state machine. For "state decision events", each port examines the contents of all Announce
messages received on the port. Using the best master clock algorithm, the Announce message contents
and the contents of the data sets associated with the ordinary or boundary clock are analyzed to
determine the state of each port of the clock.
 PTP state machine
Each port of an ordinary and boundary clock maintains a separate copy of the PTP state machine.
This state machine defines the allowed states of the port and the transition rules between states.
The principal "state decision events" determining the master−slave hierarchy are the receipt of
an Announce message and the end of an announceInterval (the interval between Announce
messages). The port states determining the master − slave hierarchy are as follows:
 MASTER: The port is the source of time on the path served by the port.
 SLAVE: The port synchronizes to the device on the path with the port that is in the MASTER
state.
 PASSIVE: The port is not the master on the path nor does it synchronize to a master.
 Best master clock algorithm
The best master clock algorithm compares data describing two clocks to determine which data
describes the better clock. This algorithm is used to determine which of the clocks described in
several Announce messages received by a local clock port is the best clock. It is also used to
determine whether a newly discovered clock—a foreign master—is better than the local clock
itself.

 Sample of Master-Slave Hierarchy

The following figure shows master slave clock hierarchy of a simple topology.
Figure 10-6: Master slave clock hierarchy of a simple topology
In this example, ordinary clock-1 is at the root of the hierarchy and is called the grandmaster clock.
Port-1 of boundary clock-1 is a slave (as indicated by the S) to the grandmaster clock. All other
ports on boundary clock-1 are masters to the clocks connected to them. Thus, port-1 of boundary
clock-2 is a slave to boundary clock-1 and so forth. Only ordinary and boundary clocks maintain
this form of state, and only boundary clocks establish the branch points in the master−slave
hierarchy (i.e., paths 1, 2, 3, 4, and 5 may contain transparent clocks, but these clocks do not
participate in the master − slave hierarchy and do not maintain this form of state).
 Unicast message negotiation
Within a telecommunications network there are benefits to allowing PTP slave devices to request
synchronization service from PTP masters. The IEEE1588™-2008 standard offers a mechanism to allow
slaves to request this service within a unicast environment. This profile supports the unicast message
negotiation in accordance with the IEEE1588™-2008 standard and as described here.

An example of the message exchange to initiate the unicast synchronization service is shown here.
Figure 10-7: Example of the message exchange to initiate the unicast synchronization service
This timing diagram example represents the exchange of unicast messages for a one-step clock (i.e. no
Follow_up messages) using one-way mode (i.e. no Delay_Req or Delay_Resp).
The example shows a unicast negotiation phase for a Packet Slave sending Signaling messages for
Announce and Sync requests; a Packet Master granting the Packet Slave the requested message rates;
a Packet Master transmitting the requested Announce and Sync message rates and the renewal of
Announce and Sync before the expiration of durationField.

 Synchronizing Ordinary and Boundary Clocks

The following figure shows the basic synchronization message exchange.
Figure 10-8: Basic synchronization message exchange
The nominal value of the <meanPathDelay> is computed as <meanPathDelay> = [(t2 – t1) + (t4 – t3)]/2
= [(t2 –t3) + (t4 – t1)]/2.
1PPS + ToD Interface
A PTP device can get accurate ToD information (including the accurate frequency) from the 1 pps + ToD input
interface. When the PTP device is synchronized to the grandmaster, it can send accurate time and frequency
information to external devices via the 1 pps + ToD output interface, in order to provide frequency
synchronization for external device. External device use these frequency information to keep frequency
synchronization with our device or master device. Supporting 1 pps + ToD is a must for some mobile backhaul
applications that require time synchronization in addition to frequency synchronization (for example,
CDMA2000, TD-SCDMA, and WiMAX). It is important to have the port, which can be as either input interface
or output interface, because for some mobile backhaul applications, they require time synchronization in
addition to frequency synchronization for E2E service. Otherwise, E2E service can cause some problems.
10.5.1 PTP TMU supported cards

The following cards can support PTP TMU:
 DMXE_22_L2
 DMXE_48_L2
 MPOE_12G
 CS100

 CS320
 CS50
 CS10
 CS100_1050
 TMSE1_8
 TM10
 CS:PTPTMU-1200
 CS:PTPTMU-1800
10.5.2 Manage the PTP TMU

10.5.2.1 Configure PTP TMU for MSPP
You can configure PTP TMU for BG-20, BG-30 or BG-64 NE with the following cards assigned:
 DMXE_48_L2
 DMXE_22_L2
 MPOE_12G

To configure the PTP TMU for an MSPP NE:

1. In the NE Shelf View window (with DMXE_48_L2/DMXE_22_L2/MPOE_12G), in the left object tree,
select PTP TMU under DMXE_48_L2/DMXE_22_L2/MPOE_12G. Then in the Configuration working
mode, select the PTP Config tab.

2. The following window shows the OC Master configuration in the MSPP NE.
For the OC Master configuration, the following parameters can be configured:

 Priority1: A user configurable designation that a clock belongs to an ordered set of clocks from
which a master is selected. The value is from 0 to 255, lower values take precedence.
 Priority2: A user configurable designation that provides finer grained ordering among otherwise
equivalent clocks. The value is from 0 to 255, lower values take precedence.
 Timing Source: Available timing sources, including: T0, TCXO and ETY ports.
 Override SSM: Define SSM override for the PTP master synchronization source. The default value
is decided by the source type.

 Quality Level: Available level PRC, SSU-A, SSU-B and SEC. The default is SSU-B.
3. For OC Slave configuration, you can add up to 8 Unicast Masters by entering IP address of each Unicast
Master, as shown in the following figure.
10.5.2.2 Configure PTP TMU for NPT

For NPT-1200 NE (with CS100/CS320)/NPT-1050 (CS100_1050), Ordinary Clock (OC) and Boundary Clock (BC)
mode are supported. For NPT-1020 and TMSE1_8/TM10 in NPT-1010 NE, only OC clock mode is supported.
To configure the PTP TMU for NPT NEs:

1. To configure the PTP TMU for NPT-1020/NPT-1021, in the NPT-1020/NPT-1021 NE Shelf View window,
in the left object tree, select PTP TMU under BS: CS10. Then in the Configuration working mode, select
the PTP TMU Config tab.
The clock mode can be set as OC Master or OC Slave in NPT-1020/NPT-1021.
2. To configure the PTP TMU for NPT-1010, in the NPT-1010 NE Shelf View window, in the left object tree,
select PTP TMU under TMSE1_8 or TM10. Then in the Configuration working mode, select the PTP TMU
Config tab.

The clock mode is fixed to OC Slave in NPT-1010.

3. To configure the PTP TMU for NPT-1200 (with CS100/CS320)/NPT-1050 (with CS100_1050):
a. In the NE Shelf View window, in the left object tree, select PTP TMU under XS: CS100/CS320.
Then in the Configuration working mode, select the PTP TMU Config tab.
b. Set the PTP Profile as Default or G.8275.1.
4. For the OC Slave configuration with Default PTP profile, in NPT-1200/NPT-1050, you can set the
following parameters as required:
 PTP TMU Protocol: This attribute enable/disable PTP protocol. The default is disable. When PTP
protocol is changed from disable to enable, a PTP license will be used.
 Clock Mode: This attribute indicates the clock mode of PTP.
 Clock Domain: This attribute indicates the clock domain of PTP. The default value is 0.
 OC Work Mode: Master or Slave. The default is Slave.
 Announce Message Mode: This attribute indicates OC announce message work mode. The value
is Unicast.
 Frequency Recovery From T0: This attribute is only for PTP TMU slave mode or BC mode of central
PEs of NPT-1200 CS100/CS320 and NPT-1050 CS100_1050. When you enable it, you must make
sure this NE's TMU and Master's TMU are synced, and PTP cannot send PTP system clock to this
NE's TMU.
 Phase Offset: The unit is ns. The valid value of Offset is from -10000 to 10000 with a step of 10.
The default value is 0.
 Sync Rate: Packet per second.
 Min Delay Request Interval: Times of sync interval.
 Announce Interval: Set Request Unicast Transmission Signaling (RUTS) Announce packets
interval.
 RUTS Tx Period: Set the RUTS Tx period for all packet types.
 RUTS Duration: Set the RUTS duration field for all packet types.
 Master IP Address List: The Master IP Address list.
 Designated Master ID: The IP Address can be configured when the Work Mode is set as Slave.
5. To configure the PTP TMU for NPT-1800:
a. In the NE Shelf View window, in the left object tree, select CS:PTPTMU-1800. Then in the
Configuration working mode, select the PTP TMU Config tab.
b. Set the PTP Profile as Default or G.8275.1.
6. For the OC Slave configuration with Default PTP profile, in NPT-1800/NPT-1200/NPT-1020/NPT-1021,
you can set the following parameters as required:
 PTP TMU Protocol: This attribute enable/disable PTP protocol. The default is disable. When the
PTP protocol is changed from disable to enable, a PTP license will be used.
 OC Work Mode: Master or Slave. The default is Slave.

 Frequency Recovery From T0: This attribute is only for PTP TMU slave mode or BC mode of central
PEs of NPT-1800. When you enable it, you must make sure this NE's TMU and Master's TMU are
synced, and PTP cannot send PTP system clock to this NE's TMU.
 Phase Offset: The unit is ns. The valid value of Offset is from -10000 to 10000 with a step of 10.
 Sync Rate: Packet per second.
 Announce Interval: Set Request Unicast Transmission Signaling (RUTS) Announce packets
interval.
 RUTS Duration: Set the RUTS duration field for all packet types.
 Designated Master ID: The IP Address can be configured when the Work Mode is set as Slave.
7. For the OC Master configuration in NPT-1800/NPT-1200/NPT-1020/NPT-1021, you can set the
parameters as required:
 Steps Mode: Set for sending Follow Up messages.
 It can be set as One Step or Two Steps in NPT-1800/NPT-1200.
 The valid mode is Two Steps in NPT-1020/NPT-1021.
 Priority1: A user configurable designation that a clock belongs to an ordered set of clocks from
which a master is selected. The value is from 0 to 255, lower values take precedence.
 Current Time: Set as PTP or GPS time. The default value is GPS.
 PTP Time: Only valid when Current Time is PTP.
 GPS Weeks: Only valid when Current Time is GPS.
 GPS Second in Last Week: Only valid when Current Time is GPS.
 Timing Source: Available timing sources, including: T0, TCXO, ETY ports and 1PPS input.
 When Timing source is 1PPS: TOD input enable/disable is valid, Clock Accuracy is valid, Time
Source is valid, and there is no Override SSM and Quality Level.
 When Timing source is T0 or ETY Port: You can configure Override SSM and Quality Level.
 When Timing source is TCXO, there is no other configuration.
 ToD Input: Only valid when Timing Source is 1PPS input. Setting PTP Time or GPS Time will not
take effect when ToD input is enabled.
 Clock Accuracy: Only valid when Timing Source is 1PPS input
 Time Source: Only valid when Timing Source is 1PPS input. When 1PPS input is selected as clock
reference, the Time Source is configurable.
 Override SSM: It is invalid when Timing Source is 1PPS input.
 Quality Level: It is invalid when Timing Source is 1PPS input.

8. For the BC mode in NPT-1800/NPT-1200, you can set the parameters as required:
 Steps Mode: Set for sending Follow Up messages. It can be set as One Step or Two Steps.
 Frequency Recovery From TO: Enable / Disable. The default is disabled.
 Phase Offset: The phase Offset for 1PPS output.
 Sync rate: Packet per second.
 Announce Interval: Set RUTS Announce packets interval.
 RUTS Duration: Set the RUTS durationField for all packet types.
 Designate Master ID: This attribute is used to enable/disable designate master ID.
9. For the NPT-1800/NPT-1200/NPT-1050/NPT-1200i PTP Profile, you can select G.8275.1 with the
following parameters as required:
 G.8275.1 MC DA MAC:
 Forwardable: Forwardable multicast address: 01-1B-19-00-00-00.
 Non-forwardable: Non-forwardable multicast address: 01-80-C2-00-00-0E.
 Steps Mode: Set for sending Follow Up messages.
 Local Priority: A user configurable designation that a clock belongs to an ordered set of clocks
from which a master is selected. The value is from 0 to 255, lower values take precedence.
 Current Time: Set as PTP or GPS time. The default value is GPS.
 PTP Time: Only valid when Current Time is PTP.
 GPS Weeks: Only valid when Current Time is GPS.
 GPS Second in Last Week: Only valid when Current Time is GPS.
 Timing Source: Available timing sources, including: T0, TCXO, and 1PPS input.
 When Timing source is 1PPS: TOD input enable/disable is valid, Clock Accuracy is valid, Time
Source is valid, and there is no Override SSM and Quality Level.
 When Timing source is T0 Port: You can configure Override SSM and Quality Level.
 When Timing source is TCXO, there is no other configuration.
 ToD Input: Only valid when Timing Source is 1PPS input. Setting PTP Time or GPS Time will not
take effect when ToD input is enabled.
 Clock Accuracy: Only valid when Timing Source is 1PPS input
 Time Source: Only valid when Timing Source is 1PPS input. When 1PPS input is selected as clock
reference, the Time Source is configurable.

 Override SSM: It is invalid when Timing Source is 1PPS input.

 Quality Level: It is invalid when Timing Source is 1PPS input.
11. To configure the PTP port for NPT-1800/NPT-1200i, in the NE Shelf View window, in the left object tree,
select CSPTPTMU-1800/CSPTPTMU-1200. Then in the Configuration working mode, select the PTP Port
Config tab.
Click Create to create a PTP port, select the port in the left pane, and set the parameters as required:
 Enabled: Select to enable the PTP port.
 Not Slave: Select to enable Not Slave.
NOTE: For T-GM you must enable Not Slave. For T-BC, Not Slave can be either enabled or
disabled.
 Priority: Set the priority value. Default is 128.

 PTP Port Number: Set the PTP Port number.
10.5.2.3 Reset PTP TMU

PTP TMU cold reset can be supported in NPT-1010/NPT-1200/NPT-1050. You can select cold reset Active or
Standby PTP TMU.
To reset PTP TMU:

1. In the NPT NE Shelf View window, in the left object tree, select the PTP TMU. Then select the
Maintenance menu and then select Reset. The Reset PTP TMU window opens.
2. Select the reset object as required:

 Reset Active PTP: cold reset the active PTP TMU.
 Reset Standby PTP: cold reset the standby PTP TMU.
3. Click OK. The settings are applied.
10.5.3 View the PTP TMU state

To view the PTP state:

1. In the NE Shelf View window, in the left object tree, select the PTP TMU. Then in the Configuration
working mode, select the PTP TMU State tab.
2. To get active status, on the toolbar, click .

3. To get standby status, on the toolbar, click .
10.5.4 View the PTP port state for IP/MPLS

To view the PTP port state for IP/MPLS:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the PTP TMU. Then in the
Configuration working mode, select the PTP port State tab.
2. Click the Refresh icon on the toolbar.
10.5.5 Manage the PTP port

This section describes how to manage the PTP port.

To manage the PTP port:

1. In the NE Shelf View window, in the left object tree, select PTP Port under PTP TMU. Then in the
Configuration working mode, select the PTP Port Config tab.

2. The following window shows the PTP Port Config window in NPT-1200.
The Mate IP and Default Gateway IP attributes are for NPT-1200 CS100 and NPT-1050 CS100_1050
only. IP and Mate IP must be in the same subnet.
3. The PTP port can be configured as disable or enable by selecting Enable checkbox. The default is disable.
The Port MAC address is read only.
4. Set the other parameters as required and click Apply to save the settings.

10.5.6 View PTP port state

You can view the PTP port state in NPT-1020/NPT-1021/NPT-1010, NPT-1200 NE with CS100 and NPT-1050
with CS100_1050.
To view the PTP port state:

1. When PTP TMU is in Master mode, in the NE Shelf View window, in the left object tree, select the PTP
Port under PTP TMU. Then in the Configuration working mode, select the PTP Port State tab.
2. For the OC mode PTP port, the PTP port state is displayed as below.

3. For the BC mode PTP port, the PTP port state is displayed as below.
To get active status, on the toolbar, click .

To get standby status, on the toolbar, click .

4. The PTP port state of NPT-1020 is displayed.
To get active status, on the toolbar, click .

10.5.7 View PTP master statistics for OC master

In NPT-1020 or NPT-1200 NE with CS100, when PTP TMU is in OC Master mode, you can view and clear the
statistics counters per slave in master.
To view the PTP master statistics:

1. In the NPT-1200/NPT-1020 NE Shelf View window, in the left object tree, select the PTP TMU. Then in
the Performance working mode, select PTP Statistics > PTP Master Statistics tab.
A filter of Slave (by Slave IP) is provided to get and clear its statistics.
2. To clear the statistics, on the toolbar, click .
10.5.8 View PTP slave PDV histogram for OC slave

In NPT-1010/NPT-1200 NE (with CS100)/NPT-1050 (with CS100_1050)/NPT-1800/NPT-1200i, when PTP TMU
is in OC Slave mode, you can view the PTP slave PDV histogram, with the type Tx or Rx.
Viewing PTP Slave PDV Histogram is not supported for OC Slave mode in NPT-1020.

To view PTP slave PDV histogram:

1. When PTP TMU is in Slave mode, in the NE Shelf View window, in the left object tree, select the PTP
TMU. Then in the Performance working mode, select PTP Statistics > PTP Slave PDV Histogram tab.
2. You can select the type as TX or RX from the Type field, by select the corresponding radio button.
3. The default PDV Bin List is shown as list. To view as chart, on the toolbar, click . Then click the Create
Chart button.
4. To clear the statistics, on the toolbar, click .
10.5.9 View PTP slave statistics for OC slave

In NPT-1010/NPT-1200 NE (with CS100)/NPT-1050 (with CS100_1050)/NPT-1800, when PTP TMU is in OC
Slave mode, you can view the PTP slave statistics.
Viewing PTP slave statistics is not supported for OC Slave mode in NPT-1020.

To view PTP slave statistics for OC slave:

1. When PTP TMU is in Slave mode, in the NE Shelf View window, in the left object tree, select the PTP
TMU. Then in the Performance working mode, select PTP Statistics > PTP Slave Statistics tab.
2. To clear the statistics, click .

10.5.10 View PTP master statistics in BC mode

In NPT-1200 NE (with CS100)/NPT-1050 (with CS100_1050), when PTP TMU is in BC mode, both PTP Master
Statistics and PTP Slave PDV Histogram are supported.
To view the PTP master statistics:

 In the NPT-1200/NPT-1050 NE Shelf View window, in the left object tree, select the PTP TMU. Then in
the Performance working mode, select PTP Statistics > PTP Master Statistics tab.

10.5.11 View G.8275.1 PTP port statistics

The G.8275.1 PTP port statistics is supported in NPT-1800, NPT-1200 (with CPS, CPTS, MCPTS matrix) and
NPT-1050.
To view G.8275.1 PTP port statistics:

1. In the NE Shelf View window, in the left object tree, select the PTP TMU, then in the Performance
working mode, select the PTP Port Statistics tab.

2. In the NPT1800 NE Shelf View window, in the left object tree, select the PTP TMU, then in the
Performance working mode,e select the PTP Port Statistics tab.
10.5.12 Perform Sync-E Tx timing setting

In NPT-1200/NPT-1020/NPT-1021/-NPT-1050, the system timing unit is located on matrix card. It is an SEC,
EEC and PTP hybrid TMU, while it can be divided to two separate parts – system TMU (TMU100) and PTP
TMU (PTP-TMU100).
In general, system TMU functionality of NPT-1200/NPT-1020/NPT-1021/NPT-1050 is same as that of BG-64;
the only difference is the number and types of available synchronization source.
Sync-E Tx timing setting is supported for the following cards:
 DMXE_48_L2
 MPOE_12G
 DHGE_4E
 DHGE_8
 DHGE_16
 DHGE_24
 AMXE_2
 DHXE_4

To perform Sync-E Tx timing setting:

1. In the NE Shelf View window, in the left object tree, select a card that supports Sync-E Tx timing setting.
Then in the Configuration working mode, select the Sync-E Tx Timing Setting tab.
2. If the PTP TMU is not in Slave mode, the Tx Timing cannot be set as PTP System Clock.
3. Set the other parameters as required and click Apply to save the settings.

10.5.13 Set timing configuration

PTP system clock can be selected as TMU timing source if PTP is enabled and T0 is not defined as master
synchronization source if PTP is configured as OC master. It is applicable to PTP of all central PEs: NPT-1200
CS100/CS320, NPT-1020 CS10/CS50, NPT-1010 CS5, NPT-1050 CS100_1050.
To set the timing configuration:

1. In the NE Shelf View window, in the left object tree, select Control and Physical Object and then XS:
TMU. Then in the Configuration working mode, select the Timing Settings tab.

2. If the PTP TMU of DMXE_48_L2/DMXE_22_L2/MPOE_12G is enabled, the Timing Source can be set as
PTP Recovery.
3. If PTP System Clock is selected as the timing source by the system TMU, then the PTP TMU cannot be
disabled.

10.5.14 Manage PTP TC

You can manage PTP Transparent Clock (TC) for all central PEs (NPT-1200 CS100/CS320, NPT-1020 CS10/CS50,
NPT-1010 CS5, NPT-1050 CS100_1050) and DMXE_22_L2/DMXE_48_L2/MPOE_12G.
To manage PTP TC:

1. To set E2E TC configuration, in the NE Shelf View window, in the left object tree, select a card or central
PE that supports PTP TC. In the Configuration working mode, select the General tab.
a. For the Central PE in NPT-1200, the E2E TC can be set as: Disable or Two-Step.
b. For the L2 cards that E2E TC is supported or the Central PE in NPT-1020/NPT-1021, the E2E TC can
be set as: Disable or Two-Step.


2. To view E2E TC status, select the E2E TC Status tab. The E2E TC Status are displayed.
10.5.15 Work in services

The PTP port can be added in the PB MPtMP and MPLS MPtMP service, as the Untag of the UNI port.
The PTP port can only be used once in creating VSIs.

To work in services:
1. In the NE Shelf View window, in the left object tree, select all central PEs (NPT-1200 CS100/CS320,
NPT-1020 CS10/CS50, NPT-1010 CS5, NPT-1050 CS100_1050) or
DMXE_22_L2/DMXE_48_L2/MPOE_12G switch. In the Services working mode, select the VSI List tab.

2. On the toolbar, click the Create VSI icon . The Create VSI window opens. From the Service Type
dropdown list, select PB MPtMP (or MPLS MPtMP).
3. In the VSI Parameters area, enter the VSI ID, NMS VSI ID, User Label, Customer, S-VLAN, and vFIB
Quota values in the relevant fields. The vFIB Total Reserved Entries field indicates the total number of
reserved entries in the vFIB. You can also add a description in the VSI Description field.
4. (Optional) To enable E-Tree, select the E-Tree Enable checkbox.

5. (Optional) Select the For PTP checkbox. For the For PTP enabled VSIs, E2E TC handling will be done if
E2E TC is enabled in the Switch module.
6. In the Objects Selections area, select the PTP Port and the EoS/EoR port(s) from the corresponding list.
7. Configure the required parameters for the selected ports and click Activate to save and activate the
VSI.
For more information about creating VSIs, refer to Services management in MSPP/NPT.

10.6 Configure 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. In the BG-40 NE Shelf View window, in the left object tree, select SM10, and then under the
Configuration working mode, select the Timing Setting tab.
2. Click to retrieve the timing configuration from the equipment.

3. Set the timing parameters and click Apply to send the configuration to the LCT-NPT DB and the
equipment.

To configure SM_10E timing:

1. In the BG-20/BG-30/BG-64/NPT-1200/NPT-1020 NE Shelf View window, in the left object tree, select
TMU under SM_10E, and then under the Configuration working mode, select the Timing Setting tab.

equipment.

To configure EM_10E timing:

1. In the NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select TMU under
EM_10E, and then under the Configuration working mode, select the Timing Setting tab.

equipment.
10.7 Configure MXP10 timing

This section describes how to configure MXP10 timing.

To configure MXP10 timing:

1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select TMU
under MXP10, and then under the Configuration working mode, select the Timing Setting tab.

equipment.
10.8 Quality Level and SSM Processing with

Option II
The synchronization Quality Level (QL) definition and SSM coding can support option II of ITU-T G.781. When
you create an NPT NE of North America mode (Framing Type is SONET/DS1), the default Internal Timing
Quality will be set to
 NPT-1200: ST3E
 NPT-1020: ST3
 NPT-1010: SMC

Quality available for external timing sources: PRS, STU, ST2, TNC, ST3E, ST3, SMC, PROV (Quality available for
PTP Master Timing is the same).
T3 and T4 are not supported.
To configure timing settings for a SONET NPT NE:

1. In the SONET NPT NE Shelf View Window, in the left object tree, select the TMU object. Then in the
Configuration working mode, select the Timing Settings tab.

2. In the Timing Maintenance tab window, you can view the Current Timing Quality.

11 Services management in MSPP/NPT
This section describes the Multiprotocol Label Switching (MPLS) services.
A label is assigned for an IP packet at the MPLS edge router (LER: Label Edge Router-PE). When the packet
enters the MPLS network and the MPLS core network routers (LSR: Label Switching Router-P), it makes
forwarding decisions based on the label. The MPLS has a Control Plane and a Data Plane.
Figure 11-1: MPLS with Control and Data plane
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 (TE). The major goal of the 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.
A 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. A 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, set all the InVClabels and OutVClabels the same. The range is 1024~waterline
(default 4096).
 Same Incoming Label: In this mode, set all the InVClabels the same. All the OutVClabel settings can be
different.

LCT-NPT® User Guide Services management in MSPP/NPT
To define the waterline, open the file emsserver.properties under the folder \LCT-NPT\etc. The
following line sets the waterline:
VC_Label_Waterline = 4096
Modify the setting as required and save it 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.
From LCT-NPT v3.1, tunnel/queue with small bandwidth (such as 256kbps) and new grids for all EZchip cards
and BG MSPP are supported, which is supporting granularity with range 128~512 in a step of 128kpbs for
each Cos of Tunnel/BD Tunnel/QB/Port for all EZchip cards in NPT and BG MSPP.
11.1 MPLS services workflow

The procedure for creating Ethernet services over an MPLS includes the following steps:
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.
4. Set the VCG attribute. In the Create VCGs window, configure the VCG bandwidth.
5. Create required tunnels.
6. Select ports and remote PEs for the services.
7. Set the other required attributes for the services.
11.2 MPLS services supported cards

The following Layer 2 data cards support MPLS services:
 MPS_4F
 MPS_6F
 DMFE_4_L2
 DMFX_4_L2
 DMGE_2_L2
 DMGE_4_L2
 DMGE_8_L2
 DMXE_48_L2
 DMXE_22_L2
 MPOE_12G
 MPS_2G_8F
 ME_2G_4F
 CPTS100
 CPS100

 CS50
 CS10
 CS5
 CS320
 CPTS320
 CS100_1050
The MPLS supports the following types of Ethernet services:
 MPLS PtP
 MPLS MPtMP
 MPLS RootedMP/Leaf
 MPLS RootedMP/Root
The MPLS RootedMP/Leaf and MPLS RootedMP/Root can be supported in DMGE_2_L2, DMGE_4_L2,
DMGE_8_L2, DMXE_48_L2, MPOE_12G, CPTS100/CPS100, CS50/CS10, CS320, CPTS320, CS100_1050.
11.3 Create and manage LAGs

In previous versions, editing L2 attributes of LAG object is blocked. This limitation is removed by adding
Master/Slave attribute for port member.
 Select a master port when you create the LAG;
 Each LAG must have one master port member, and all other port members are in slave mode;
 The Master/Slave attribute is R-create when a port is added to the LAG, not editable;
 The port attributes between Master and Slave ports can be different during LAG creation;
 The Slave port member can be added or deleted during LAG edit;
 The Master port can be deleted only when there is no slave port in the LAG, delete the master port is
equal to delete the LAG.
LAG improvement is supported for the all the EZchip cards.
NOTE: From implementation point of view, the L2 attributes of the LAG object will be saved on
the master port, and the slave ports will use the same attributes of the master port
automatically.

11.3.1 Create a LAG

To create a LAG:
1. In the NE Shelf View window, in the left object tree, right-click an EZchip card/Central PE module, then
select Create LAG.
2. From the Aggregation Group dropdown list, select an aggregation group.
3. To add the ports to the right aggregation group, select ports in the left list, and click .
4. Set one master port member for the LAG by selecting Master, and all other port members are in slave
mode.
The master port can be deleted only when there is no slave port in the LAG.
5. Set the other parameters as follows:
 Actor Key: This attribute is only available when create LAGs on Central PE of NPT NEs, which
indicates unique identifier of the LAG within the PE. It must be unique per switch. Default value
is the LAG ID (if LAG ID is LAG1, then default value is 1).
 Max Active Links: from 1 to the number of members in the LAG (default is number of members
in LAG).
 Min Active Links: from 1 to max-active-links (default 1).
 LACP Enable: Enabled or Disabled (default Disabled).
 Mode: Active or Passive (default Active).
 Priority: from 1 to 65535 (default 128).
 Time Out: Short or Long (default Short).
Note that: If a port is added to a LAG with the LAG Distribution Enable value set to disabled, or the LAG
port member is changed from LAG Distribution enabled to disabled, the LAG's traffic is not distributed
to that port and packets received from it are not discarded.

6. Select the LAG Distribution Enable checkbox if needed, set the Hold Off Time.
7. To retrieve the information of the LAG to view, click Get.
9. To remove the whole LAG, remove all the ports in the LAG, then click Apply.
NOTE: The in-band MCC enabled port or a port with Management VLAN cannot be added into
a LAG.
11.3.2 Manage LAGs

To manage a LAG:
1. To configure L2 interface attributes of a LAG:
a. In the NE Shelf View window, in the left object tree, select the LAG object. )
b. Select Configuration and then select the General tab.

c. Configure LAG attributes as required.

d. Click Apply. The settings are saved.

2. To view the port members of the LAG:

a. Select the LAG Member tab in the Configuration working mode.
The LAG Member window opens.
b. Edit the attributes for the port members as required.

c. Click Apply to save the changes.

3. To view the state of a LAG member port:

a. Select the LAG Member Port State tab in the Configuration working mode.
b. In the LAG Member Port dropdown list, select a LAG member port and then click .

4. To view the LAG member port statistics:

a. In the Configuration working mode, select the LAG Member Port Statistics tab.
b. In the LAG Member Port dropdown list, select a LAG member port and then click .
c. To clear the information, click .
11.3.3 Manage LAG over MoE

LCT-NPT can support LAG n:m redundancy and MoE over LAG port with LACP. A number of MoE ports with
same rate (1G or 10G) can be defined as LAG MoE to support N_1G or N_10G MPLS port (MPLS over LAG).
Up to 2 MoE ports can be added to the LAG.
 LAG MoE support LACP and n:m redundancy;
 MPLS tunnel and LSP 1:1 linear protection is supported on LAG MoE.
 FRR is not supported on LAG MoE.
MoE over LAG is supported by following Central PEs:

 CS100
 CS100_1050
 CS50
 CS10
 CS5

 CS320
 CPTS320
Create a LAG over MoE in the same way as you create a LAG. See Creating and managing LAGs for information.
Following figure provides an example of the Create LAG window with MoE ports.
11.3.4 Manage MC-LAG

Network availability is a critical metric for service providers as it has a direct bearing on their profitability.
Outages translate not only to lost revenue but also to potential penalties mandated by contractual
agreements with customers running mission-critical applications that require tight SLAs. This is true for any
carrier network, and networks employing Layer 2 Virtual Private Network L2VPN) technology are no
exception. Network high-availability can be achieved by employing intra and inter-chassis redundancy
mechanisms. The focus of this document is on the latter. The document defines an Inter-Chassis
Communication Protocol (ICCP) that allows synchronization of state and configuration data between a set of
two or more PEs forming a Redundancy Group (RG). The protocol supports multi-chassis redundancy
mechanisms that can be employed on either the attachment circuit or pseudowire front.
Figure 11-2: Differences between regular LAG and MC-LAG
In the MC-LAG figure above, there are two devices (PE#1, PE#2) – this is because MC-LAG provides equipment
protection and there are two devices/PEs.

 Each device has number up to N member ports (for example N=8). There is no validation that the
number of port is equal on both devices, though in practice it will be identical).
 The number of MC-LAG per VSI should be limited to 1. Otherwise we need to invent a majority-vote
mechanism that will decide how many failed LAGs & MC-LAG ports are considered a failure that should
be reported as trigger to PWR.
MC-LAG Application
Following describes the MC-LAG application in LCT-NPT.
 Dual Homing to PW Redundancy
The 2-PE solution is based on dual homing of CEs and PEs using two technologies – MC-LAG in the
Ethernet segment toward the Customer Edge (CE) and PW Redundancy in the provider’s network to
remote PEs. This application is shown in Figure 4.
For this application, MC-LAG enabled of LAG is enabled on PE1 and PE2. And an ICCP channel is selected
to transmit mLACP message between PE1 and PE2. And this channel can be detected based on BFD.
PW status can be enabled to transmit and receive PW status message and run PW state machine in PE1
and PE2. PWR is enabled in PE3 and PE4. PWR is enabled also on PE1 and PE2. PW status messages are
sent by PE1 is almost the same as saying that PE1 supports PWR.
When MC-LAG switchover occurs, it can trigger AC status change of PW and trigger protection switching
actions in PW Redundancy. PW status message can be used to notify this change for PWR.
Figure 11-3: Dual Homing to PW Redundancy

 Dual Homing to VPLS Network

Another application is CE dual homing to a VPLS network. The CE is dual homed using MC-LAG. Changes
in the LAG link status are reported to the VPLS network by means of CCN in order to flush the FDB at
the appropriate PEs. PW Redundancy is not used in this application. ICCP Channel can be detected by
BFD
Figure 11-4: Dual Homing to VPLS Network
 Dual Homing to H-VPLS Network with PWR

A typical application is CE dual homing to an H-VPLS network with PWR. In one end, The CE is dual
homed using MC-LAG. Changes in the LAG link status are reported to the VPLS network by means of
CCN in order to flush the FDB at the appropriate PEs. In another end, CE is dual homed using PW
Redundancy. In this case, MC-LAG and PWR are irrelevant. MC-LAG switchover shall not trigger PWR
switchover, and vice versa.
Figure 11-5: Dual Homing to H-VPLS network with PWR
MC-LAG Architecture
The MC-LAG includes the following logical function modules:
 LAG Controller
 mLACP Controller

 Remote PE State Controller

 LAG Distribution Function
 ICCP and ICCP Channel
LAG Controller and LAG Distribution Function mainly implement IEEE802.3ad Link Aggregation function.
mLACP Controller, Remote PE State Controller and ICCC Channel mainly implement MC-LAG function which
are depicted in the following sections.
mLACP Controller
mLACP Controller mainly include the following functions:
 maintain MC-LAG Configuration
 maintain MC-LAG switchover state machine
 trigger CCN
 Notify LAG status to PWR
 Activate/Deactivate LAG ports, and update LACP state machine
 Receive /Transmit mLACP message from/to Remote LAG
 Maintain remote LAG information.
MC-LAG switch state machine can use the following inputs:
 MC-LAG Configuration
 LAG Link Down Indication including static LAG and LACP
 MC-LAG Remote PE Operation state
 Receiving mLACP message
Remote PE Controller
Remote PE Controller mainly maintains remote PE status which can be detected by the following ways:
 BFD on BD-LSP
 LDI (Link Status)
ICCP and ICCP Channel
Inter-Chassis Communication Protocol (ICCP) is defined in this section.
ICCP allows synchronization of state and configuration data between a set of two or more PEs forming a
Redundancy Group (RG) according to standard, but in NPT V4, only two PEs is supported. The protocol
supports multi-chassis redundancy mechanisms that can be employed on either the attachment circuits or
pseudowires.
The PEs in an RG offer multi-homed connectivity to either individual devices (e.g. CE, DSLAM, etc.) or entire
networks (e.g. access network). ICCP applications include PWR application and mLACP application in
standard.

11.3.4.1 Enable MC-LAG

Following are some limitations about enabling the MC-LAG:
 Only PB ETY LAG can be able to enable MC-LAG.
 LACP enabled attribute of the member ports in local MC-LAG must be same.
 MC-LAG cannot exist with MSTP/ERPS/PWR in one VSI.
 The LAG cannot be deleted when MC-LAG is enabled.
To Enable the MC-LAG:

1. In the NPT NE Shelf View window, in the left object tree, select the LAG under the Central PE.
2. Select Configuration and then the MC-LAG tab.
3. To enable the MC-LAG, select the MC-LAG Enable checkbox.

The following displays as below, with detailed information about LAG configuration, status, and
statistics.

4. To clear the configured parameters, click .

5. In the Local LAG Attributes area, enter the following information:
 Redundancy Group ID: This attribute indicates The Redundant Group Identifier (RGID) is a generic
opaque handle that uniquely identifies a Redundant Group which means one MC-LAG. This is the
ID that associates the correct instance of MC-LAG in the local PE with an instance of MC-LAG in
the peer PE. LAG objects on two PE's will be regarded as a pair in MC-LAG if they have the same
RG ID and Actor KEY.
 Trigger CCN: This attribute indicates to transmit CCN when switchover occurs.
 Protection Role: This attribute indicates protection role of MC-LAG. It is only valid when the
protection type is Link Protection.
 Hold Off Timer: This attribute indicates LAG Link Down shall not take effect until this timer
expired.
 Revertive: This attribute indicates that the transmitting end point is configured to work in
revertive mode. It is only valid when the protection type is Link Protection.
 WTR Timer: This attribute indicates MC-LAG shall not recovery from failure conditions on the
primary LAG in revertive mode until WTR expired. It is only valid when protection role is Primary
and protection type is Link Protection.
6. In the Remote LAG Attributes area, enter the following information:
 Associate Channel: Click the box to enable associate channel settings.

 Remote PE ID: This attribute describes the remote PE ID of mate LAG. It is remote PE ID of BD-LSP
and is read only.
 ICCP Channel ID: This attribute describes the channel between two multi-chassis LAG. For ICCP
Channel Type is BD Tunnel, it means Tunnel ID.
 ICCP Channel Hold Off Timer: This attribute indicates ICCP Channel Fail shall not take effect until
this timer expired.
7. Click Apply to save the changes.
11.3.4.2 View MC-LAG status and statistics

To view MC-LAG status and statistics:
1. In the NPT NE Shelf View window, in the left object tree, under the Central PE, select the LAG with MC-
LAG enabled.
2. Select Configuration and then the MC-LAG tab.
The following displays as below, with detailed information about LAG configuration, status, and
statistics.


All the attributes are refreshed and display the relevant parameters, as described in the following
tables.
Table 11-1: Local LAG status related to MC-LAG

Attribute Name Description
Actor Key This attribute describes actor key of local LAG.
Protection Role This attribute describes local LAG protection role.
System ID This attribute describes the system ID of Local LAG.
System Priority This attribute describes the system priority of local LAG.
Operational State This attribute describes local LAG operational state.
Protection State This attribute describes the local LAG state of MC-LAG.
Active Operational This attribute describes the active operational command in primary LAG
Command and secondary LAG.
Time Since Last Change This attribute describes the time elapsed since "Local Protection State" was
last changed.
Number of Switching Number of switching since MC-LAG enabled.
Table 11-2: Remote LAG status related to MC-LAG

LAG ID This attribute describes the Aggregator ID of mate LAG in one MC-LAG.
RG ID This attribute describes the RD ID of mate LAG.
Actor Key This attribute describes the actor key of mate LAG.
Protection Role This attribute describes mate LAG protection role.
System ID This attribute describes the system ID of mate LAG.
System Priority This attribute describes the system priority of mate LAG.
Operation State This attribute describes mate LAG operational state.
Protection State This attribute describes the mate LAG state of MC-LAG.
ICCP Channel State This attribute describes ICCP Channel state.
Table 11-3: ICCP Channel Statistics per Remote LAG related to MC-LAG
MC-LAG Frames Tx This attribute describes the number of mLACP PDUs transmitted on ICCP.
MC-LAG Frames Rx This attribute describes the number of mLACP PDUs received on ICCP
Channel.
Invalid MC-LAG Frames Rx This attribute describes the number of invalid mLACP PDUs received on
ICCP Channel.

11.3.4.3 Perform MC-LAG operation commands

The MC-LAG includes following operation commands:
 Release - clear current active command.
 Lockout - traffic is prevented switching to the peer LAG.
 Force Switch - traffic is switched to peer LAG.
 Manual Switch - traffic is switched to peer LAG. This is only relevant if there is no currently active fault
condition or other operator command.
To perform MC-LAG operation commands:

1. In the NPT NE Shelf View window, in the left object tree, select the LAG under the Central PE.
2. Select Maintenance and then the MC-LAG Operation Commands tab.
3. Select an MC-LAG operation command.


11.4 Profile management

This section describes how to create and manage the profiles.
11.4.1 Manage Policer profiles

When creating VSIs, each UNI port must have a policer. You can use each policer once.
To create a policer:
1. In the NE Shelf View window, in the left object tree, select the Switch module under a data card.
2. In the Configuration working mode, select Policer Profile List under the Profiles tab.

3. On the toolbar, click the Create Policer icon .

The Create Policer Profile window opens.
4. In the Create Policer Profile window, enter the following parameters for the policer:
 Policer Name: Enter a name for the policer. The Policer name must be unique.
 Policer 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.
 CBS: Set the committed burst size.
 CM: Select the color mode (CM) from the dropdown list.
 CF: Select coupling flag (CF) from the dropdown list.
5. To create the policer, click Apply.
The following table describes the rules for defining Policer values.
Table 11-4: Policer value rules

Profile name Policer value rule
CIR/EIR Step of: 64 Kbps for 0~2 Mbps (excluding 64Kbps, 128Kbps, 192Kbps); 1 Mbps for 2
Mbps~full port rate (400 Mbps, 1 Gbps or 10Gbps).
0~80M bytes, step of 1KB for EZchip cards. Can be configurable by EMS/NMS.
CBS/EBS
Default CBS/EBS on EMS:
 If CIR is less than 1 Mbps, the CBS is equal to 16 KB. Otherwise, CBS is equal to
Min (CIR/128, 12M bytes).
 If EIR is less than 1 Mbps, the EBS is equal to 16 KB. 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
the EMS user) is Min (CIR/32, 4M bytes) and no less than 32 KB.

Profile name Policer value rule

CM Color-blind/Color-aware.
CF Enabled/Disabled.
Policer lists
You can view the policer list in the following window.

To edit the policer list:
1. Select the policer, and then click the Edit Policer icon .
The Edit Policer Profile window opens.
2. Change the policer values as required, and click Apply to save the settings.
To view the details of a policer:
3. Select the policer, and then click .

The View Policer Profile window opens.

To delete a policer:
1. Select the policer, and then click .
2. To delete all of the policers in the list, click the Select All icon and then click .
Click to deselect all.
To upload policers:
1. Click the Policer Upload icon .

The Policer Profile Upload window opens.
2. To upload policers from the DMFE_4_L2 card, click Upload.
3. If the NE and the DB are inconsistent, select the Policer Profile Compare tab to display the inconsistency
results.
4. To overwrite the DB with the NE data, click Overwrite.

11.4.2 Manage ACL profiles

The Access Control List (ACL) is used for Denial of Service (DoS) prevention. ACL profiles can be applied to the
UNI or E-NNI ports in all Data L2 cards except ESW_2G_8F_E and MESW_6F.
To manage the ACL profiles:

1. In the NE Shelf View window, in the left object tree, select a Data L2 card and then the Switch object.
2. In the Configuration working mode, select ACL Profile under the Profiles tab.

3. To create an ACL profile, on the toolbar, click .

The Create/Edit ACL Profile window opens.
4. Enter the ACL fields, and then click Add.

5. You can carry out the following functions:
 To retrieve information to view, click .
 To edit a selected ACL profile in the list, click .

 To delete a selected ACL profile, click .

11.4.3 Manage EXP mapping profiles

To manage the EXP mapping profiles:
1. In the NE Shelf View window, in the left object tree, select the Switch object of a data card.
2. In the Configuration working mode, select EXP Mapping Profile under the Profile tab.

3. To create an EXP mapping profile, on the toolbar, click .

The Create EXP Mapping Profile window opens.

4. Set the following information, and then click Apply:

 Profile Name
 Exp to Cos Mapping list; you can define a maximum of five CoS mappings.
5. You can carry out the following functions:
 To retrieve information to view, click .
 To view a selected profile, select the profile in the list, and on the toolbar click .
 To edit a selected profile, select the profile in the list, and on the toolbar click .
 To export the profile list as an XML file, on the toolbar, click .
 To import profiles from an XML file, on the toolbar, click .
 To propagate the settings to other NEs, on the toolbar, click .
 To synchronize the data between database and the NE, click .

 To delete a selected profile, click .

The EXP mapping profiles can be configured for the MoT/MoE ports of the data cards.
11.4.4 Manage WRED profiles

This section describes how to manage Rated Random Early Detection (WRED) profiles.

To create a WRED profile:

1. In the NE Shelf View window, in the left object tree, select the Switch module under a data card.
2. In the Configuration working mode, select WRED Profile under the Profile tab.

3. To create a WRED profile, on the toolbar, click .

The Create User-Defined WRED Profile window opens.

4. Set the WRED Profile Name, Profile ID and the other parameters as required, and click Apply to save
the profile.

To configure the tunnel XC WRED profile:

1. In the tunnel XC list, right-click an L-LSP tunnel XC and select Tunnel XC WRED Profile.
The Tunnel State WRED Profile window opens.
2. You can configure the WRED profile when Mode is set as Manual.

11.5 H-VPLS and E-Tree

The E-Tree function is only supported for the PB MPtMP and MPLS MPtMP services.
VPLS VSI provides connectivity between non-MPLS interfaces (i.e., service ports) and Pseudowire (PW)
connecting to the VPLS core. Traffic between VSI PWs is not allowed in VPLS, enforced using the Split Horizon
rule. Therefore, connecting between VPLS domains/MPLS interfaces requires using QinQ Ethernet-based
interfaces.
MPLS Hierarchical-VPLS (H-VPLS) provides a solution by creating a hierarchy of VPLS domains and allowing
MPLS-level connectivity between them.
The following terminology is used for H-VPLS:
 H-VPLS VSI: A VSI that supports and is part of an H-VPLS service.
 Split Horizon Group (SHG): A group of VSI interfaces belonging to the same split horizon.
 Spoke: A VSI interface that typically connects between VPLS domains.
Every VSI interface is assigned a number (SHG) that represents the domain this interface belongs to. There is
no forwarding within the same domain. Forwarding between different domains is allowed.
A special SHG is called null SHG and has a value of 0. This group does not belong to any domain and traffic
from and to this PW is always allowed.
Figure 11-6: Example of SHG configuration (H-VPLS)
The MPLS card #1 is connected to two SHGs numbered #1 and #2. Any number between 1~7 can be used,
but the SHGs connected to the same "VPLS domain" must use the same number. The connection to a spoke
is not configured by the user and functions as defined for SHG = Null.
The SHG numbering is local to the MPLS card. Therefore, in the connection of MPLS card #1 to MPLS card #6,
the same SHG is numbered as SHG = 2 in MPLS card #1 and SHG = 1 in MPLS card #6.
Figure 11-7: Example of SHG configuration (E-Tree)

The MPLS card #1 is connected to one SHG numbered #7 and the Root ETY port (in Null SHG). All PWs to the
remote leaves and a local ETY leaf are added into this SHG. So the local leaf and all remote leaves are isolated.
The MPLS card #2 (or #6) is connected to two SHGs numbered #1 and leaf. The traffic between CEs connecting
to Leaf SHG is isolated. Each VSI in MPLS card #2 to #8 has PW connected to the VSI in MPLS card #1. However,
there is no PW connection between them. In this way, traffic forwarding between leaves is blocked, and
traffic from Root can be forwarded to any leaf.
LCT-NPT allows H-VPLS VSIs only for the VSIs with tunnel type E-LSP, or VSIs with the tunnel type L-LSP and
the VSI VC Label Scheme is Same Incoming Label.
H-VPLS VSIs are supported for the following VSI type:
 MPLS MPtMP VSIs
E-Tree VSIs are only supported for the following VSI types:
 PB MPtMP VSIs
 MPLS MPtMP VSIs
For the configuration of the SHG/Port Role value:
 For the E-LSP VSI and the L-LSP VSI with the VC Label Scheme Same Incoming Label, the PW SHG can
be configured.
 For the L-LSP Single VC Label VSI, the PW SHG can only be 1.
To enable the E-Tree function:

 In the PB MPtMP or MPLS MPtMP service window, in the left configuration area, select the E-Tree
Enable checkbox.

11.6 MPLS best-effort CoS

This section describes MPLS best-effort (BE) CoS configuration.
Figure 11-8: Best Effort forwarding
Propagation in the figure is shown as follows:

 The CoS that belongs to L-LSP or E-LSP+CoS is designated as BE CoS.
 The network provides E2E L-LSP, or E-LSP+CoS bandwidth is 0.
 The service is carried over the L-LSP or the E-LSP+CoS.
The following are some limitations for configuring BE CoS:
 BE CoS is supported in bridge level and can be selected from low CoS.
 If there is no service (Tunnel or MPLS VSI) in the low CoS, the user can change the CoS from low to BE
or BE too low.
 If there are services in the low CoS, changing the CoS from low to BE or BE to low is forbidden.
 If there is PB service in the CoS but no tunnel in this CoS, this CoS can be configured as BE CoS.
 Editing is allowed only when no XCs are configured on the CoS.
 The BE CoS cannot be selected from high CoS.
LCT-NPT supports multiple BE CoS.

To set the MPLS BE CoS:

1. In the NE Shelf View window, in the left object tree, select the Switch module of a MPLS data card.
3. Set MPLS PE as the Switching mode.

4. In the CAC Configuration area, set the MPLS best effort CoS as required.
11.7 Small bandwidth tunnel/queue

CIR granularity of high CoS shaper and low CoS bandwidth is configurable between 128Kbps and 512Kbps in
step of 128Kbps. New grids for tunnel/queue bandwidth configuration are added.
The new tunnel/queue bandwidth granularity can be shown as below:
 128K~512Kbps at a step of 128Kbps
 1~16Mbps at a step of 1Mbps

The new bandwidth granularity are supported for each Cos of Tunnel/BD Tunnel/QB/Port for all EZchip cards
in NPT and BG MSPP.
11.8 PW control word for NPT

The control word attribute is supported per PW. Only PW with regular VC scheme can support control word.
New in-VC-label space is defined for PW with control word.
In VC Label space and control word rules:
 For CESoMPLS, PW control word is always enabled, but it always use in VC label space without control
word because CESoMPLS in CIPS is similar with MS-PW in S-PE
 For MS-PW VSI in S-PE, PW control word can be configurable, but it always use in VC label space without
control word because MS-PW in S-PE not care control word.
 For other MPLS VSI, PW control word can be configurable, it use different in VC label space according
to PW control word configuration.
In VC label space with control word is 16384 to 32767.
To configure the control word attribute:

1. You can configure the Control Word attribute in the Create/Edit VSI window, as shown in the following
figure.
2. The Control Word attribute can be set as enabled or disabled. The default is disabled.
3. In VC label space with control word is 16384 to 32767.

11.9 Manage tunnels

A tunnel is composed of tunnel segments. Each tunnel segment is associated with a single MPS card.
Figure 11-9: Tunnel model
A tunnel segment is subdivided into in-segment CTP and out-segment(s) CTP objects that are interconnected
by a single XC object:
 In-segment CTP is analogous to [Ingress I/F, MPLS Label].
 Out-segment CTP is analogous to [Egress I/F, MPLS Label].
 XC or SNC describes the conceptual connection between one in-segment and one or more out-
segments, where multiple out-segments can exist in a PtMP tunnel segment.
Both PtP and PtMP tunnel XCs are supported in LCT-NPT:
 PtP Tunnel: A tunnel that originates at the source PE, traverses through Transit Ps, and terminates at
the destination PE.
Figure 11-10: PtP tunnel model
 The source PE pushes two MPLS labels into each customer's Ethernet packet entering the tunnel.
The inner MPLS label is called the VC label, which represents the VPN to which the packet belongs.
The VC label serves as a demultiplexer 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.
 PtMP Tunnel: A PtMP tunnel at an LSR modeled as in-segment and out-segment(s) interconnected by
a XC.
Figure 11-11: PtMP 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 XC is analogous to [Tunnel ID] and contains parameters such as ingress PE. It also contains a
list of attributes per subtunnel where each subtunnel is analogous to [Tunnel ID, Egress PE].
 Subtunnel: A PtMP tunnel constructed from subtunnels. Each subtunnel starts at the same source PE
and ends at a different destination PE. Subtunnels may share a branch, in which case the data plane
forwards only one packet copy to that link.
Properties of subtunnels belonging to a same PtMP tunnel XC:
 They share the common properties of the branch tunnel, such as In-Segment object. When adding
subtunnels to the PtMP tunnel XC, these properties are read only.
 Each subtunnel has one Out-Segment connecting to a unique remote PE. When adding a
subtunnel, the user must configure the Out-Segment, by:
 Selecting an out MoT port.
 Changing the label.
 Subtunnels can share the Out-Segment. The link between this transit PE and the next hop (NH)
becomes the shared branch.
 Subtunnels may share the bypass tunnel.
 Tail Subtunnel: Transit PEs contain many subtunnels but only one tail subtunnel. The tail subtunnel
terminates at this PE.
 For PtMP Transit&Tail PE, you can configure only one tail subtunnel for the tunnel XC.

 A Transit&Tail PE can be configured without a tail subtunnel.

 Tail subtunnel connects to any MoT port. When configuring the tail subtunnel, you just need to
mark that the PtMP XC has a tail subtunnel.
11.9.1 Tunnel workflow

E-LSP and L-LSP tunnels are supported in LCT-NPT.
To create an E-LSP or L-LSP tunnel:

1. Define the Configuration Mode as MPLS PE.
2. Assign PE ID and MPLS Network ID. Each MPLS must have a unique PE ID.
3. Configure ports as MoT port type. The GE ports in all the MPLS cards can be defined as MoE ports. MoE
ports support the creation of the E-LSP tunnel, while MoT ports support the creation of the E-LSP and
L-LSP tunnels.
4. Create EXP Mapping profile.
6. To define a Destination PE or Source PE, make sure there is at least one other MPLS switch object that
has the same MPLS Network ID as the switch that you are configuring.
7. Create a tunnel XC for the selected MoT or MoE port.
In the Create Tunnel XC window, configure the following parameters:
 Input the XC Name, Customer, CoS, and Bandwidth.
 Select the Tunnel Mode: E-LSP or L-LSP.
 Select the Tunnel Type: PtP or PtMP.
 For PtP tunnels, select the Tunnel Role as one of the following values:
 Head. Configure the Out-Segment: set the 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.
 For PtMP tunnels, select Head or Transit&Tail as Tunnel Role.
 Configure the Protection Type. A tunnel XC can be configured as:
 Unprotected
 Bypass
 Protected
 Configure other advanced parameters.

To create a subtunnel:
1. Create the PtMP tunnel XC; the tunnel role can be Head or Transit&Tail.
2. The Head tunnel XC needs not configure the In-Segment.
3. The Transit&Tail tunnel XC needs to configure the In-Segment, which is shared by the subtunnels.
4. For the Head tunnel XC, you can add a subtunnel.
5. For Transit&Tail tunnel XC, you can add a subtunnel or edit it as a tail subtunnel.
6. For the MoT port, the Out Label on all of the subtunnels must be the same.
7. The Adding Sub-Tunnel window displays the common properties of the subtunnels as read only.
You must configure the following:
 The remote PE.
 The Out-Segment connects the remote PE.
For all the MPLS cards, you can add or remove CoS with Bandwidth for unprotected/protected/bypass E-LSP
tunnels;
Tunnel CoS can be removed in the following cases:
 Exists in the tunnel.
 Not used by any service and OAM (BFD session CoS/Tunnel OAM CoS)
 Not used by any protected tunnel (for bypass)
Tunnel CoS can be added in the following cases:
 Not exists in the tunnel
 Exists in EXP mapping profile of the out port
 For a protected tunnel, the CoS should have been added to the protecting bypass tunnel

11.9.2 Create tunnel XCs

To create Tunnel XCs:
1. In the NE Shelf View window, in the left object tree, select the Switch object under an MPLS card.
3. Set the Switching Mode to MPLS PE.

4. In the MPLS PE Configuration section, assign a PE ID.
5. Set the other configurations as required, and click Apply to save your settings.

6. In the left object tree, right-click the MPLS card, and then select Define MoT Port.
The Define MoT Port window opens.
7. Set the ports as MoT ports, and click Apply.

8. To define MoE ports, in the left object tree, right-click the MPLS card and then select Define MoE Port.
The Define MoE Port window opens.

9. To configure the VCG bandwidth, in the left object tree, right-click the MPLS card.
10. To define a destination PE or source PE, repeat the operation from Step 1 to Step 4 for another MPLS
switch object.
This switch can either be in another 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 be set with the
same MPLS Network ID.
11. Create EXP mapping profiles.
For details of creating EXP Mapping profiles, see Manage EXP mapping profiles.

12. To configure the attributes of the MoT/MoE port, in the left object tree, select the relevant MoT/MoE
port, and in the Configuration working mode, select the General tab.

The attribute Exp Map Profile cannot be empty (default is default_mapping_name).

14. In the NE Shelf View window, in the left object tree, select the Switch object, and in the Services
working mode, select the Tunnel XC List tab.

15. To create a tunnel XC, on the toolbar, click the Create Tunnel XC icon .
The Create Tunnel XC window opens.
11.9.2.1 Create PtP tunnel XC

This section describes the procedure for creating a PtP tunnel XC.
When label swap is supported, the MPLS In Label and MPLS Out Label of the PtP transit tunnel XC can be
different. When dual fast reroute (FRR) is disabled, the MPLS In Label and MPLS Out Label of the PtMP transit
tunnel XC can be different. When dual FRR is enabled, the MPLS In Label and MPLS Out Label of the PtMP
transit tunnel XC must be the same.
Next to Next Hop (NNH) Label Value

When the Protection Type is Protected and is protected by NNH mode, this label will be used as the second
label of bypass tunnel.
Figure 11-12: Example of NNH label value
In the figure, the working tunnel label swap on node MCS1-MCS2-MCS3 are:
 MCS1: 10000 in, 10001 out
 MCS2: 10001 in, 10002 out
 MCS3: 10002 in, 10003 out
The NNH label value of Bypass 1 in MCS1 should be configured to 10002 which is in tunnel label of working
tunnel on MCS3.
To create an unprotected/bypass tunnel XC:

1. In the Create Tunnel XC window, configure the following:
 Select the Protection type. A tunnel XC can be configured as Unprotected or Bypass.
 Select the Tunnel Mode, E-LSP or L-LSP.
 Select PtP as Tunnel Type.
 Select the XC Role as 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 Tunnel Name, Tunnel ID, Customer, NMS Tunnel ID, and MID in the corresponding
fields.
 (Optional) Select the Enable Tunnel OAM checkbox, and set the Tunnel OAM CoS as required.

 The bandwidth of the E-LSP (PIR) can only be configured for the E-LSP PtP tunnel. You can set the
bandwidth of E-LSP by selecting the PIR No Rate Limiting checkbox or clearing the checkbox and
setting the BW Limitation (Mbps) attribute.
 In the CoS Bandwidth area, define CoS bandwidth, bind mode (Auto/Manual) and WRED profile
name (if Bind Mode is Manual).

2. For Transit and Tail of a Bypass tunnel XC, you can also configure the dual FRR. Select the Bypass Dual
FRR checkbox if needed.
3. In the Select Port list, select a MoT/MoE/MoE LAG port, and in the Select Destination PE list, select a
destination PE.
4. To save the tunnel to the Recent Saved XCs area, click Save.
5. To activate the XC, click Activate.
6. 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. In the Tunnel XC List tab, select an unprotected head or unprotected transit or unprotected transit&tail
tunnel XC.

2. On the toolbar, click the Add/Remove Bypass Tunnel XC icon .

The Add/Remove Bypass XC window opens.

3. The Select Bypass Tunnel XC field lists the entire bypass tunnel XCs that protect the selected Out Port
with the same CoS as the configuring bypass XC. Select an XC from the Select Bypass Tunnel XC list, set
the NNH Out Label value, and then click Add Bypass.
4. To remove the bypass tunnel XC, select the bypass XC that you want to remove in the Recent Saved
Bypass XCs list, and click Remove Bypass.

5. Close the Add Bypass XC window.

You can view the protected tunnel XC and its bypass tunnel XC highlighted in the list.

6. To remove the bypass tunnel XC of a protected tunnel XC, select the protected tunnel XC in the Tunnel
XC List, and click .
7. In the Recent Saved Bypass XCs area, select the bypass XC that you want to remove, and then click
Remove Bypass.
11.9.2.2 Create PtMP tunnel XC

This section describes the procedure for creating PtMP tunnel XC. A PtMP tunnel is constructed from
subtunnels. Each subtunnel starts at same source PE and ends at a different destination PE. Subtunnels may
share a branch, in which case the data plane forwards only one packet copy to that link.
PtMP tunnel XC can be supported in the following cards:
 DMGE_2_L2
 DMGE_4_L2
 DMGE_8_L2
 DMXE_48_L2
 MPOE_12G
 CS100
 CS320
 CS100_1050
 CS50
 CS10

To create the PtMP tunnel XC:

1. In the Create Tunnel XC window, configure the following:
 Select the Protection type. A tunnel XC can be configured as Unprotected or Bypass.
 Select the Tunnel Mode: E-LSP or L-LSP.
 Select PtMP as Tunnel Type.
 Select the XC Role as Head or Transit&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.
 Transit&Tail. Configure both the In-Segment and Out-Segment: MPLS In Label, MPLS Out
Label, In Port, Out Port, and select a Destination PE.
 Input the Tunnel Name, Tunnel ID, Customer, NMS Tunnel ID, and MID in the corresponding
fields.
name (if Bind Mode is Manual). An E-LSP tunnel of type PtMP supports only a single CoS.
2. Select a MoT/MoE/MoE LAG port in the Select Port list, and then select a destination PE in the Select
Destination PE list.
3. To save the tunnel to the Sub Tunnel list, click Add Sub Tunnel.
4. Add more subtunnels if required.

5. To create a PtMP tunnel XC in the Sub Tunnel list with the role Transit&Tail, enable the dual FRR for
subtunnels as needed by selecting the Dual FRR checkbox.
6. To save the tunnel to the Recent Saved XCs area, click Save.
7. To activate the XC, click Activate.
8. To activate a tunnel XC, select the tunnel XC in the Recent Saved XCs list, and click Activate All.
11.9.2.3 Enable dual FRR

Dual FRR defines 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-and-continue.
Figure 11-13: Dual FRR
As illustrated in the figure, the PtMP tunnel flows from PE1 (PLR) to PE2 (L-MP), where it splits towards PE3
(N-MP). This PtMP tunnel is protected as follows:
 Bypass B1 protects the subtunnels to PE2 against the failure of link PE1-PE2 (Link protection).
 Bypass B1 protects the subtunnels to PE3 against the failure of PE2 (Node protection).
Dual FRR is enabled as follows:
 Bypass Dual FRR needs to be enabled at Transit and Tail and not at Head:
B1 XC at PE2 (L-MP) and PE3 (N-MP)
 PtMP subtunnels Dual FRR needs to be enabled at Transit&Tail:
Subtunnels to PE3/PE5 at Transit&Tail (PE2/PE3)

To enable Dual FRR:

1. Create a PtMP tunnel XC.
2. In the Sub Tunnel list with the role Transit&Tail, enable the Dual FRR for subtunnels as needed by
selecting the Dual FRR checkbox.
11.9.3 Access tunnel XC list

Perform the following tunnel XC 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 OAM state.
 Tunnel XC performance, including:
 Current
 NE History
 EMS History
 Threshold Settings
 Monitoring and Reporting
 Resetting Performance Counters

 Tunnel XC Alarms, including:

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

1. In the NE Shelf View window, in the left object tree, select the MPLS Switch object.
2. In the Services working mode, select the Tunnel XC List tab.

11.9.3.1 Filter the tunnel XC list

To filter the tunnel XC list:
1. In Services working mode Tunnel XC List tab, click + to expand the Filter area.
2. Set the attributes in the area as required, and click to filter the list.

11.9.3.2 Manage tunnel XCs

This section describes how to view, edit, or delete a tunnel XC. You can add or remove the CoS from the Edit
Tunnel XC window.
To manage a tunnel XC:

 To view a tunnel XC, in the Tunnel XC List tab right-click the tunnel and then select View Tunnel XC.
The Tunnel XC Detail window opens.

 To edit a tunnel XC, in the Tunnel XC List tab right-click the tunnel and then select Edit Tunnel XC.
The Edit Tunnel XC window opens.
In the Edit Tunnel XC window, you can add or remove the CoS.
 To delete a tunnel XC:
a. Deactivate the XC. In the Tunnel XC List tab, right-click the tunnel and then select Deactivate
Tunnel XC.
b. Right-click the tunnel, and then select Delete Tunnel XC.
You can also perform these operations by clicking the tool icons on the toolbar.

11.9.3.3 Upload tunnel XCs

To upload tunnel XCs:
1. In the tunnel XC list, on the toolbar click the Upload icon .

The Tunnel XC Upload window opens.
2. To upload all the tunnel XCs, click Upload.

3. If the NE and the DB are inconsistent:
a. Select the Compare Result tab to display the inconsistency results.
b. To overwrite the DB with the NE data, click Overwrite.
11.9.3.4 Export and import tunnel XCs

This section describes how to export tunnel XCs to an XML file, and import an XML file into the tunnel list.
To export a tunnel XC:
1. In the tunnel XC list, select a tunnel XC and then click .

The Save window opens.
2. To export the selected XC as an XML file, click Save.

To import a tunnel XC:
1. In the tunnel XC list, select a tunnel XC, and on the toolbar, click .
The Import Tunnel XC window opens.
2. To open a file, on the toolbar, click .

The Open window opens.

3. Select a file from the disk, and click Open.

The Import Tunnel XC window displays all the tunnel XCs in the file.
4. Select the XC that you want to import, and then click the Import icon .

11.9.3.5 View tunnel XC OAM state

To view a tunnel XC OAM state:
 In the tunnel XC list, right-click a tunnel XC and then select Tunnel OAM State.
The Tunnel XC State window opens.
11.9.3.6 Manage tunnel XC performance

This section describes how to manage the tunnel XC performance, including:
 View current, recent, and history performance
 Set TCA threshold
 Monitor and reporting
 Reset performance counters

You can view tunnel XC performance from the Tunnel XC List tab.
To manage the tunnel XC performance:

 In the tunnel XC list, right-click a tunnel XC and then select Tunnel XC Performance.

To view the current performance of the selected tunnel XC:

1. Right-click the tunnel XC, and then select Tunnel XC Performance > Current.
2. Click to retrieve the information.

To view the recent performance of the selected tunnel XC:

1. Right-click the tunnel XC, and then select Tunnel XC Performance > NE History.

To view the historical performance of the selected tunnel XC:

1. Right-click the tunnel XC, and then select Tunnel XC Performance > EMS History.

To set a threshold for the selected tunnel XC:

1. Right-click the tunnel XC, and then select Tunnel XC Performance > Threshold Setting.

To set monitoring and reporting:

 Right-click the XC and then select Tunnel XC Performance > Monitoring and Reporting.
In this window you can set monitoring and auto-reporting for the tunnel XC.
To reset the performance counters:

1. Right-click the tunnel XC, and then select Tunnel XC Performance > Reset Performance Counters.
A Confirmation window opens.
2. Select counters to reset, and then click Yes.
11.9.3.7 Manage tunnel XC alarms

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

You can view tunnel XC alarms from the Tunnel XC List tab.
To manage tunnel XC alarms:

 In the tunnel XC list, right-click the tunnel XC and then select Tunnel XC Alarm.

To view current alarms:

 Right-click the tunnel XC, and then select Tunnel Alarm > Current.

To view historical alarms:

1. Right-click the tunnel XC, and then select Tunnel Alarm > History.

To mask the alarms of the selected tunnel XC:

 Right-click the tunnel XC and then select Tunnel Alarm > Monitoring and Reporting.
11.10 Manage LSP 1:1 for BD-LSP

Linear protection provides rapid and simple protection switching. In a mesh network, linear protection
provides a very suitable protection mechanism because it can operate between any pair of points within the
network. It can protect against a defect in an intermediate node, a span, a transport path segment, or an
end-to-end transport path.
Protection switching is a fully allocated survivability mechanism. It is fully allocated in the sense that the
route and resources of the protection path are reserved for a selected working path or set of working paths.
It provides a fast and simple survivability mechanism that allows the network operator to easily grasp the
active state of the network and that can operate between any pair of points within the network.
A protection domain is introduced for a point-to-point LSP as consisting of two Label Edge Routers (LERs) and
the transport paths that connect them.

Protection Domain
Figure 11-14: Protection domain
In MPLS-TP Linear Protection, the following the protection types be considered:

 1+1 unidirectional
 1+1 bidirectional
 1:1 unidirectional
 1:1 bidirectional
 1:n
 PtP
 PtMP
In LCT-NPT, only 1:1 bidirectional is supported.
1+1 Protection
Figure 11-15: 1+1 unidirectional architecture
In the 1+1 unidirectional architecture, a protection transport path is dedicated to the working transport path.
Normal traffic is bridged and fed to both the working and the protection paths by a permanent bridge at the
source of the protection domain. The sink of the protection domain uses a selector to choose either the
working or protection path from which to receive the traffic, based on predetermined criteria, e.g., server
defect indication. When used for bidirectional switching the 1+1 protection architecture must also support a
Protection State Coordination (PSC) protocol. This protocol is used to help coordinate between both ends of
the protection domain in selecting the proper traffic flow.

1:1 Protection
Figure 11-16: 1:1 protection architecture
In the 1:1 architecture, a protection transport path is dedicated to the working transport path of a single
service, and the traffic is only transmitted on either the working or the protection path, by using a selector
at the source of the protection domain. A selector at the sink of the protection domain then selects the path
that carries the normal traffic. Since the source and sink need to be coordinated to ensure that the selector
at both ends select the same path, this architecture must support a PSC protocol.
The 1:n protection architecture extends the 1:1 architecture above by sharing the protection path among n
services. Again, the protection path is fully allocated and disjoint from any of the n working transport paths
that it is being used to protect. The normal data traffic for each service is transmitted either on the normal
working path for that service or, in cases that trigger protection, may be sent on the protection path. The
switching action is similar to the 1:1 case where a selector is used at the source. In cases where multiple
working path services have triggered protection switching, it should be noted that some services, dependent
upon their Service Level Agreement (SLA), may not be transmitted as a result of limited resources on the
protection path. In this architecture, there may be a need for coordination of the protection switching and
for resource allocation negotiation.
Protection State Control Logic
Protection switching processes the local triggers together with inputs received from the far-end LER. Based
on these inputs, the LER will take certain protection switching actions, e.g., switching the selector to transmit
on the working or protection path for 1:1 protection or switching the selector to receive the traffic for either
1:1 or 1+1 protection and transmit different protocol messages.

Figure 11-17: Logical decomposition of the protection state control logic into different logical processing
units
 Local Request logic

The Local Request logic unit accepts the triggers from the OAM, server layer, external operator
commands, local control plane (when present), and the Wait-to-Restore timer. By considering all of
these local request sources, it determines the highest priority local request. This high-priority request
is passed to the PSC Control logic.
The Local Request logic processes input triggers from five sources.
 Operator command - the network operator may issue local administrative commands on the LER
that trigger protection switching. The commands Forced Switch, Manual Switch, Clear, Lockout of
protection are supported. An implementation could provide a command to manually set off a
"WTR Expires" trigger input without waiting for the duration of the WTR timer; as this merely
hastens the transition from one state to another and has no impact on the state machine itself, it
would be perfectly valid.
 Server-layer alarm indication - the underlying server layer of the network detects failure
conditions at the underlying layer and may issue an indication to the MPLS-TP layer. The server
layer may employ its own protection switching mechanism; therefore, this input may be
controlled by a hold-off timer that SHOULD be configurable by the network operator.
 Control-Plane Indication - if there is a control plane active in the network (either signaling or
routing), it may trigger protection switching based on conditions detected by the control plane. If
the control plane is based on GMPLS, then the recovery process shall comply with the process.
 OAM indication - OAM fault management or performance measurement tools may detect a
failure or degrade condition on either the working or protection transport path. This must input
an indication to the Local Request logic.

 WTR Expires - The Wait-to-Restore timer is used in conjunction with recovery from failure
conditions on the working path in revertive mode. The timer shall signal the PSC control process
when it expires, and the end point shall revert to the normal transmission of the user data traffic.
The input from these sources should be retained persistently for the duration of the condition that
initiated the trigger. The Local Request logic processes these different input sources and, based on the
priorities between them, produces a current local request. If more than one local input source
generates a trigger, then the Local Request logic selects the higher priority indicator and ignores any
lower priority indicator. As a result, there is a single current local request that is passed to the PSC
Control logic. The different local requests that may be output from the Local Request logic are as
follows:
 Clear - if the operator cancels an active local administrative command, i.e., LO/FS/MS.
 Lockout of protection (LO) - if the operator requested to prevent switching data traffic to the
protection path, for any purpose.
 Signal Fail (SF) - if any of the server-layer, control-plane, or OAM indications signaled a failure
condition on either the protection path or one of the working paths.
 Signal Degrade (SD) - if any of the server-layer, control-plane, or OAM indications signaled a
degraded transmission condition on either the protection path or one of the working paths. The
determination and actions for SD are for further study and may appear in a separate document.
All references to SD input are placeholders for this extension.
 Clear Signal Fail (SFc) - if all of the server-layer, control plane, or OAM indications are no longer
indicating a failure condition on a path that was previously indicating a failure condition.
 Forced Switch (FS) - if the operator requested that traffic be switched from one of the working
paths to the protection path.
 Manual Switch (MS) - if the operator requested that traffic be switched from the working path to
the protection path. This is only relevant if there is no currently active fault condition or operator
command.
 WTR Expires (WTRExp) - generated by the WTR timer completing its period.
 No Request (NR) - If none of the input sources have generated any triggers, then the Local Request
logic should generate a No Request (NR) as the current local request.
 Remote Requests
In addition to the local requests, generated as a result of the local triggers, indicated in the previous
subsection, the PSC Control logic SHALL accept PSC messages from the far-end LER of the transport
path. Remote messages indicate the status of the transport path from the viewpoint of the far-end LER.
These messages may drive state changes on the local MEP, as defined later in this document. When
using 1+1 unidirectional protection, an LER that receives a remote request shall not perform any
protection switching action, i.e., will continue to select traffic from the working path and transport
traffic on both paths.
The following remote requests may be received by the PSC process:
 Remote LO - indicates that the remote end point is in Unavailable state due to a Lockout of
protection operator command.

 Remote SF - indicates that the remote end point has detected a Signal Fail condition on one of
the transport paths in the protection domain. This remote message includes an indication of
which transport path is affected by the SF condition. In addition, it should be noted that the SF
condition may be either a unidirectional or a bidirectional failure, even if the transport path is
bidirectional.
 Remote SD - indicates that the remote end point has detected a Signal Degrade condition on one
of the transport paths in the protection domain. This remote message includes an indication of
which transport path is affected by the SD condition. In addition, it should be noted that the SD
condition may be either a unidirectional or a bidirectional failure, even if the transport path is
bidirectional.
 Remote FS - indicates that the remote end point is operating under an operator command to
switch the traffic to the protection path.
 Remote MS - indicates that the remote end point is operating under an operator command to
switch the traffic from the working path to the protection path.
 Remote WTR - indicates that the remote end point has determined that the failure condition has
recovered and has started its WTR timer in preparation for reverting to the Normal state.
 Remote DNR - indicates that the remote end point has determined that the failure condition has
recovered and will continue transporting traffic on the protection path due to operator
configuration that prevents automatic reversion to the Normal state.
 Remote NR - indicates that the remote end point has no abnormal condition to report.
 PSC Control logic
The PSC Control logic receives the high-priority request from Local Request Logic and cross-check this
local request with the information received from the far-end LER. The PSC Control logic uses this input
to determine what actions need to be taken, e.g., local actions at the LER, or what message should be
sent to the far-end LER, and the current status of the protection domain.
The PSC Control logic accepts the following input:
 The current local request output from the Local Request logic
 The remote request message from the remote end point of the transport path
 The current state of the PSC Control logic (maintained internally by the PSC Control logic).
Based on the priorities between the different inputs, the PSC Control logic determines the new state of
the PSC Control logic and what actions need to be taken.
The new state information is retained by the PSC Control logic, while the requested action should be
sent to the PSC Message Generator to generate and transmit the proper PSC message to be transmitted
to the remote end point of the protection domain.
 PSC Control States
The PSC Control logic should maintain information on the current state of the protection domain.
Information on the state of the domain is maintained by each LER within the protection domain. The
state information would include information of the current state of the protection domain, an
indication of the cause for the current state (e.g., unavailable due to local LO command, protecting due
to remote FS), and, for each LER, should include an indication if the state is related to a remote or local
condition.

It is noted that when referring to the "transport" of the data traffic, in the following descriptions and
later in the document that the data will be transmitted on both the working and the protection paths
when using 1+1 protection, and on either the working or the protection path exclusively when using
1:1 protection. When using 1+1 protection, the receiving LER should select the proper transmission,
according to the state of the protection domain.
The protection domain states that are supported by the PSC Control logic are as follows:
 Normal state - Both the protection and working paths are fully allocated and active, data traffic is
being transported over (or selected from) the working path, and no trigger events are reported
within the domain.
 Unavailable state - The protection path is unavailable – either as a result of an operator Lockout
command or a failure condition detected on the protection path.
 Protecting failure state - The working path has reported a failure/degrade condition and the user
traffic is being transported (or selected) on the protection path.
 Protecting administrative state - The operator has issued a command switching the user traffic to
the protection path.
 Wait-to-Restore state - The protection domain is recovering from an SF/SD condition on the
working path that is being controlled by the Wait-to-Restore (WTR) timer.
 Do-not-Revert state - The protection domain has recovered from a Protecting state, but the
operator has configured the protection domain not to automatically revert to the Normal state
upon recovery. The protection domain remains in this state until the operator issues a command
to revert to the Normal state or there is a new trigger to switch to a different state.
Bidirectional Tunnel
The bidirectional Co-Routed tunnel may contain only the Main bidirectional LSP, which passes through the
same port in both directions. Bidirectional tunnel endpoints are Head and Tail: Head for PW attachment to
go to the tail, and tail for PW which is attached at the remote Head.
Figure 11-18: Co-Routed bidirectional tunnel without LSP 1:1 protection
The Co-Routed bidirectional tunnel may contain the Main bidirectional LSP and a Protection LSP.
Figure 11-19: Co-Routed bidirectional tunnel with LSP 1:1 protection
You can add a Protection Bidirectional LSP to Bidirectional Tunnel which includes only one Main Bidirectional
LSP to support LSP 1:1 protection.
You can delete Protection Bidirectional LSP from Bidirectional Tunnel which includes Main and Protection
Bidirectional LSPs to delete LSP 1:1 protection.

11.10.1 LSP 1:1 for BD-LSP workflow

MPLS-TP Linear Protection can be managed in the 1:1 Bidirectional tunnels (Primary Bi-LSP and Secondary
Bi-LSP). LCT-NPT supports Co-routed BD-LSP on Head/Tail and Transit node in the EZchip data cards for E-LSP
tunnels. BD-LSP is for working PtP tunnel only.
To create Linear Protection Domain:

1. Set the Path Type as "Main", create the Primary Bi-LSP with BD Tunnel ID and Primary Bi-LSP Number;
2. Create Secondary Bi-LSP with "Protection" type and the same BD Tunnel ID and remote PE ID as Primary
Bi-LSP, and secondary Bi-LSP Number (different with Primary Bi-LSP Number);
3. Configure Linear Protection Domain attributes in Linear Protection Domain tab window.
11.10.2 Create Linear Protection Domains

To create Linear Protection Domains:
1. In the NE Shelf View window, in the left object tree, select the Switch object of an EZchip/LSI card.
2. In the Services working mode, select the BD LSP List tab.
3. To create a Linear Protection Domain, on the toolbar, click .

The Create BD Tunnel window opens.

4. To define a main (protected) Head/Tail BD-LSP:

 In the MPLS XC Parameters area:
 Select Main from the Path Type dropdown list.
 Select Head/Tail from the Tunnel Role dropdown list.
 (Optional) Check the PTP Aware checkbox to enable PTP aware.
 (Optional) Check the DiffServ Enable checkbox to enable DiffServ.
 In both A-Z and Z-A tab:
 Set the MPLS In Label and MPLS Out Label in the relevant fields.
 Set PIR as required.
name (if Bind Mode is Manual).
 In the MPLS XC Information area, configure the parameters in the relevant field.
 Select a port and a Remote PE from the right area lists. The Remote PE must be same as primary
BD LSP Remote PE.
5. To add the main Head/Tail BD-LSP, click the Add button.
The main Head/Tail BD-LSP is added into the Recent Added BD LSPs list.
6. To define a Protection Head/Tail BD-LSP, the BD Tunnel ID and Remote PE must be the same as Main
Head/Tail BD-LSP.
 In the MPLS XC Parameters area:
i. Select Protection from the Path Type dropdown list.
ii. Select Head/Tail from the Tunnel Role dropdown list.
iii. Set the MPLS In Label and MPLS Out Label in the relevant fields.
iv. (Optional) Enable PTP Aware/DiffServ and set PIR as required.
 In the CoS Bandwidth area, select one or more CoS and configure the relevant bandwidth for the
selected CoS.
 In the MPLS XC Information area: )
v. In the Tunnel ID field, set the Secondary Bi-LSP Tunnel ID, which must be the same as the
Primary Bi-LSP Tunnel ID.
vi. In the LSP Number field, set the Secondary Bi-LSP number, which must be different with the
Primary Bi-LSP number.
vii. Set NMS Tunnel ID and MID in the relevant fields.
viii. In the Tunnel Name field, set a name for the tunnel.
ix. Enter a Customer name and set the Tunnel Description as required.
 Select a port and a Remote PE from the right area lists.
7. To add the Protection Head/Tail BD-LSP, click the Add button.
The Protection Head/Tail BD-LSP is added into the Recent Added BD LSPs list.

8. To configure the Linear Protection Domain attributes, in the right area of the window, select the Liner
Protection Domain tab.
You can view the BD Tunnel information and set the parameters in the Liner Protection Domain area.
9. In the Create BD Tunnel tab, click the Save button to save the BD-LSP tunnels.
You can click Activate to save and activate the BD-LSP tunnels.
10. You can also create a Linear Protection Domain with Main/Protection Transit BD-LSPs.
When you select the Tunnel Role as Transit:
 The LDI Enable attribute is available for Transit BD-LSPs. The default is enabled, which enables LDI
function to transmit LDI messages on the BD-LSP.
 Set MPLS In Label, MPLS Out Label, PIR and CoS Bandwidth for the selected A side port and Z
side port.
The other configuration is the same as Main/Protection Head/Tail BD-LSPs.

11.10.3 Manage the BD-LSP List

The BD LSP List tab displays a list of the bidirectional LSP tunnels.
The Alarm column indicates the alarm status of the BD-LSP.
To manage the BD-LSP list:
 To activate BD-LSPs, select the BD-LSPs that you want to activate and then click .
 To deactivate BD-LSPs, select the BD-LSPs that you want to activate and then click .
 To edit a BD-LSP:
a. Select a BD-LSP in the list and then click .

The Edit BD Tunnel window opens.
b. Modify the settings and change the settings in the Liner Protection Domain tab.
c. Click Apply to save the changes.
 To add or remove protection BD-LSPs, select a Main BD-LSP and then click .
 To create BFD Tunnel Session, select a BD-LSP and then click .
 To synchronize the BD-LSP, click .

 To export the BD-LSPs to an XML file, select the BD-LSPs that you want to export and then click .
 To import BD-LSPs from an XML file, click .

 To delete a BD-LSP, select a BD-LSP and then click .
 To view a BD-LSP, select a BD-LSP and then click .

The View BD Tunnel window opens.
From the View BD Tunnel window:
 To view the selected port and Remote PE, select the View BD Tunnel tab.
 To view the Liner Protection Domain attributes, select the Liner Protection Domain tab.
 To view the fault management statistics, select the Fault Management Statistics tab.

 To view LDI source list of a Head/Tail BD-LSP, select the LDI Source List tab.
The LDI Source List is not supported for the Transit BD-LSPs.

 If you right-click a BD-LSP, you can also perform the following actions:

11.10.3.1 Manage Linear Protection Domain Command

To manage Linear Protection Domain Command:
1. Right-click a BD-LSP, and from the shortcut menu, select Linear Protection Domain Command.
2. The Linear Protection Domain Command tab window is shown as below.
From the Linear Protection Domain Command tab window,

 You can perform Lockout, Force Switch and Manual Switch for the BD-LSPs.
 To set WTR Expires Command, on the toolbar, click .
11.10.3.2 Perform MPLS-TP LSP ping and traceroute

LCT-NPT supports a new MSTP-OAM-LSP ping.
LSP Ping - Label Switched Path Ping, which is an existing and widely deployed Operations, Administration,
and Maintenance (OAM) mechanism for MPLS LSPs; is RFC6426 based, the LSP ping is used for on-demand
connectivity verification and route tracing functions required in RFC5860 and specified in RFC6371 of MPLS-
TP LSPs and PWs.
You can perform LSP ping for a Head/Tail BD-LSP and view the result of the ping operation.

To perform MPLS-TP LSP ping and traceroute:

1. In the BD-LSP list, right-click a Head/Tail BD-LSP and then select MPLS-TP LSP Ping & TraceRoute.
The MPLS-TP LSP Ping & TraceRoute window opens.
2. Set the Mode as Ping or TraceRoute.

3. In the Object area, set the Destination PE and Destination BD Tunnel ID:
 BD Tunnel ID: This attribute specifies the Source BD Tunnel ID.
 BD LSP Number: This attribute specifies the Source BD LSP Number.
 Destination Network ID: This attribute specifies the destination Network ID.
 Destination PE ID: This attribute specifies the destination PE ID.
 Destination BD Tunnel ID: This attribute specifies destination BD tunnel ID.
4. In the Parameters area, configure the parameters as described below:
 CoS: This attribute specifies the MPLS experimental field value in the MPLS header for an MPLS
echo request/reply. Valid values are from 0 to 7. Default is 0.
 TTL: This attribute specifies a time-to-live (TTL) value.
 Count: This attribute specifies the number of send the packets. The range is from 1 to
2147483647. The default is 5.
 Interval (available for the Ping mode): This attribute specifies the time, in milliseconds (ms),
between successive MPLS echo requests. This parameter allows you to pace the transmission of
packets so that the receiving router does not drop packets. Default is 1000ms.

 Timeout (available for the Ping mode): This attribute specifies the timeout interval in seconds for
an MPLS request packet. The range is from 0 to 60. The default is 2 seconds.
 PAD TLV Size: This attribute specifies the size of the packet with the label stack imposed.
 Reply Pad TLV: This attribute specifies the first octet of value field of Pad TLV.
 No:1-Drop Pad TLV from reply which means no Pad TLV in reply message.
 Yes:2-Copy Pad TLV to reply which means there is Pad TLV in reply message.
 Validate FEC Stack: This attribute specified the V (Validate FEC Stack) flag of Global flags. It is set
to 1 if the sender wants the receiver to perform FEC Stack validation; if V is 0, the choice is left to
the receiver. The V flag MAY be set in the echo response when reverse-path connectivity
verification is being performed.
 Validate Reverse Path: This attribute specifies the R flag of Global flags. When Validate Reverse
Path (R) flag is set in the echo request, the Responder SHOULD return reverse-path FEC
information.
5. To start the ping, on the toolbar, click .
6. To stop the ping, click .
7. To clear the parameters, click .

11.10.3.3 View LSP ping results

You can view ping results of all ping sessions per BD-LSP/switch.
To view LSP ping results:

1. In the NE Shelf View window, in the left object tree, select the Switch object.
2. In the Maintenance working mode, select the MPLS-TP Ping Result tab.
3. To view the LSP ping result, select a BD-LSP from the dropdown list and then click .
4. The parameters of LSP ping result are described as below.
 Number of Tx: This attribute indicates number of packets transmitted.
 Number of Rx: This attribute indicates number of packets received.
 FLR: This attribute indicates packet loss ratio.
 Round-Trip Min: This attribute indicates the minimum round trip time.
 Round-Trip Avg: This attribute indicates the average round trip time.
 Round-Trip Max: This attribute indicates the maximum round trip time.

11.10.3.4 Manage MPLS-TP echo statistics

You can get and clear MPLS-TP Echo statistics per BD-LSP.
To manage MPLS-TP echo statistics:

1. In the BD-LSP list, right-click a BD-LSP and then select MPLS-TP Echo Statistics.
The MPLS-TP Echo Statistics window opens.
2. To view the parameters, select a BD Tunnel ID and BD LSP Number from the relevant dropdown list and
then click .
3. The parameters of MPLS-TP Echo statistics can be described as below:
 Echo Request Pkts Transmitted: This attribute indicates number of MPLS echo request packets
transmitted.
 Echo Request Pkts Received: This attribute indicates number of MPLS echo request packets that
the router received on this.
 Echo Request Pkts Timeout: This attribute indicates number of MPLS echo request packets that
timed out.
 Echo Reply Pkts Transmitted: This attribute indicates number of MPLS echo reply packets
transmitted.
 Echo Reply Pkts Received: This attribute indicates number of MPLS echo reply packets received.

 Invalid Echo Request Pkts Received: This attribute indicates total number of discarded MPLS Echo
Request packets due to invalid values.
 Invalid Echo Reply Pkts Received: This attribute indicates total number of discarded MPLS Echo
Reply packets due to invalid values.
4. To clear the parameters, on the toolbar, click .
11.10.4 Perform MPLS-TP Tunnel Restoration

LCT-NPT supports MPLS-TP tunnel restoration over NPT central PEs. MPLS-TP tunnel Restoration and
Reversion is based on Bidirectional LSP 1:1 tunnel model. The restoration repaves a tunnel LSP on a new valid
path in case that the current path is failed, and by that, assures the availability of the inactive protection
mate LSP to protect for additional new failure. Hence the restoration makes a tunnel more immune to
multiple failures and improves the carried services availability.
MPLS-TP tunnel restoration can be supported in:
 NPT-1200 with CPTS100/CPTS320
 NPT-1020/NPT-1021 with CS10/CS50
 NPT-1050 with MCPTS100
 NPT-1010

To perform MPLS-TP tunnel restoration:

 To add main BD LSP for a transit BD tunnel with protection BD LSP:
a. In the NPT NE Shelf View window, in the left object tree, select the Central PE.
b. Select Services and then select the BD LSP List tab.

c. Select one transit BD tunnel with protection BD LSP, and then click .
The Add BD Tunnel Protection window opens.
d. Configure the following parameters for the Main BD LSP tunnel:

i. In the Path Type dropdown list, select Main.
ii. Set MPLS In Label and MPLS Out Label in both A-Z and Z-A tabs.
iii. Set the LSP Number for the main BD LSP. The LSP number must be unique.

iv. Click Add.

The main BD LSP is added to the Recent Added BD LSPs list.

v. Click Apply.
The main BD LSP is added for the transit BD tunnel.
 To remove main/protection BD LSP from 1:1 transit BD tunnel: )
e. In the BD LSP list, select the 1:1 transit BD Tunnel and then click .
A confirmation window opens.
f. Select the type of BD LSP to remove, and then click Yes.

11.11 Manage DiffServ Block over MPLS-TP Port

DiffServ QoS architecture can provide better scalability by dividing traffic into a small number of classes, and
allocating network resources not per flow but per-class basis.
NPT can support DiffServ in MPLS network with the following functions:
DiffServ Tunnel - No bandwidth, no WRED buffer, no CAC for DiffServ tunnel and tunnel CoS.
DiffServ Block - Each MPLS port can have up to one DiffServ Block, which carries all DiffServ tunnels egressed
from this port.
Figure 11-20: BW allocation – Aggregation ring example
The CAC configuration is 100:0 – 100 for allocated and 0 for reserved for all the links.
If without supporting DiffServ tunnels, user need to allocate BW for each LSP, and if user want to keep the
same LSP BW configuration per aggregation node (PEn), then user may meet the issue: cannot add/insert
new node if total CIRs of all LSPs exceed the link BW, even the real network utilization is low, unless reducing
BW for all existed LSPs.
If DiffServ block is supported, and all LSPs in above figure are DiffServ LSPs, then it's no need to allocate BW
for each DiffServ LSP. Only need to allocate BW per DiffServ block per port: DiffServ LSPs just represent the
path & traffic is mapped as per QOS definition on port. User can add as many DiffServ LSPs as he wants, so
can achieve better network utilization. There is no limitation for add/insert/remove NE and no need to
change BW for other existed NE when add/insert/remove NE.
Regarding the BW management, user can monitor the utilization and choose to increase or decrease the
percentage of BW allocated to CoS at DiffServ block of that port.
11.11.1 Configure DiffServ blocks

DiffServ Block configuration is supported for MPLS-TP port (MoT/MoE/10G MoE) of NPT central PE.

To configure a DiffServ block:

1. In the NPT NE Shelf View window, in the left object tree, select an MoT/MoE/10G MoE of central PE.
2. Select Configuration and then select the DiffServ Block tab.
3. Select one or more CoS checkboxes as required. Up to 8 CoS can be selected in one DiffServ Block.
4. Configure Bandwidth and Bind Mode as required.
5. Click Apply.
6. Click Yes to create the DiffServ block.
11.11.2 Enable DiffServ blocks for a tunnel

Following LSP types can be configured as DiffServ tunnel (except L-LSP):
 E-LSP
 Bidirectional LSP (not support one direction regular and the other direction Diffserv)
 PtP LSP
 PtMP LSP
 Working LSP
 Protection LSP (FRR, Dual FRR and Secondary LSP)

NOTE: DiffServ Enable attribute must be same for main and protection BD LSP. If DiffServ Enable
attribute is enabled, PIR and CoS Bandwidth for each direction will initialized and cannot be
configured.
To enable DiffServ attribute for E-LSP tunnels:

1. In the NPT NE Shelf View window, in the left object tree, select the Central PE.
2. Select Configuration and then select the Tunnel XC List tab.

3. Click .
4. Select the DiffServ Enable checkbox.

The DiffServ attribute is enabled.

To enable DiffServ attribute for BD LSP tunnels:

2. Select Configuration and then select the BD LSP List tab.

3. Click .
4. Select the DiffServ Enable checkbox.

The DiffServ attribute is enabled.
11.12 Create MPLS services

Once you have created the tunnels, you can create MPLS services.
For the MPS_4F, MPS_6F, DMFE_4_L2, DMFX_4_L2, DMXE_48_L2, DMXE_22_L2, MPOE_12G, ME_2G_4F,
MPS_2G_8F, CPTS100/CPS100, CPS50, CS10 and CS5 cards, you can create the following three MPLS
services:
 MPLS PtP service
 MPLS MPtMP service
 MPLS BPDU Tunneling service
For the DMGE_2_L2, DMGE_4_L2, DMGE_8_L2, DMXE_48_L2, MPOE_12G, CPTS100/CPS100,
CPS50/CS10/CS5/CS320/CPTS320/CS100_1050 cards, you can create the following five MPLS services:
 MPLS PtP service
 MPLS MPtMP service

 MPLS BPDU Tunneling service

 MPLS RootedMP/Leaf service
 MPLS RootedMP/Root service
The following table describes the relationship between the service types and the tunnel modes.
Table 11-5: Service type and tunnel mode relationships

Service type Tunnel mode
MPLS PtP L-LSP, E-LSP
MPLS MPtMP L-LSP, E-LSP
MPLS BPDU Tunneling L-LSP, E-LSP
MPLS RootedMP/Leaf service  PtMP tunnel: L-LSP, E-LSP (one CoS tunnel)
 PtP tunnel: L-LSP, E-LSP
MPLS RootedMP/Root service PtP tunnel: L-LSP, E-LSP

11.12.1 MPLS PtP service

To create an MPLS PtP service:
1. In the NE Shelf View window, in the left object tree, select an MPLS card and then the Switch object.

3. On the toolbar click the Create VSI icon .

4. From the Service Type dropdown list, select MPLS PtP.

5. Complete the following fields:
a. Select the Admin State (default is Enabled). When disabled, all policers block their traffic,
including NNI ports. When enabled, all policers enable traffic flow. This field is editable with no
constraints.
b. Enter the VSI Name, VPN ID, NMS Service ID, User Label, Customer, S-VLAN, MTU, and PW Type
values as required.

c. (Optional) You can also add a description in the Description field.

d. In the Objects Selections area, select one port and one Remote T-PE, or two ports with the same
port type. To deselect an object, right-click and select Deselect, or select the object in the Port
List, and on the toolbar click .
6. To create a policer, click "+" to expand the selected port. You can enlarge the lower-right area by clicking
the icon above the toolbar, as shown below.
7. All selected VSI UNI or E-NNI ports have the same Ethernet priority, which is determined by the provider
CoS mapping policy. Click + to add the CoS/CoS Group. Select the desired group and Policer Profile.

The following apply when defining the CoS mapping:

 For each priority (0 to 7), select only one provider CoS. The default is CoS0 for all priorities.
 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".
8. For the selected port, if required, change the values for QoS Profile, Flow Block Profile, Proactive
Policer Profile, and Firewall Profile.
9. In VLAN Configuration, configure Discrete VLAN ID, VLAN ID Range Profiles, Ingress All-to-One VLAN
Translation, and Egress All-to-One VLAN Translation as required.
10. Click the PW List tab.
For the Remote T-PE configure, as required, Is MS PW, Peer PE, SHG, Admin State, Setup Method, PW
ID, In VC Label, Out VC Label, Refresh Timer, LSP Type, Tunnel, Control Word, OAM CoS, BFD Enable,
BFD Admin State, Min Transmit Interval, Min Receive Interval, Multiplier, PW Mode, and TTL.

NOTE: In V5.1, Dynamic PW is available as a Setup Method. To use Dynamic PW, select the
tLDP setup method.
11. Configure PW Type, Holdoff Timer, if needed.

12. Select PW Status Enabled.
13. If PW Redundancy is desired, then select PW Redundancy Enable, and complete the configuration.
14. Click Activate to create and activate the MPLS PtP service.
If you click Save, the MPLS PtP service is saved, but is not activated. To activate it later, select the Recent
Saved VSIs tab. Select the VSI you want to activate in this window, and click Activate. The MPLS PtP
service is then activated.
11.12.2 MPLS MPtMP service

To create an MPLS MPtMP service:


4. To create MPLS MPtMP:

a. From the Service Type dropdown list, select MPtMP.
b. Select the Admin State (default is Enabled).
When disabled, all policers block their traffic, including NNI ports. When enabled, all policers
enable traffic flow. This field is editable with no constraints.
c. Enter the VSI Name, VPN ID, NMS Service ID, User Label, Customer, S-VLAN, MTU, and PW Type
values as required.
For MPtMP the only available options for PW Type are Ethernet and Ethernet Tagged.
d. 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).
e. (Optional) You can also add a description in the VSI Description field.
f. (Optional) Select the E-Tree Enable checkbox if you want to enable the E-Tree function.

g. (Optional) Select the Is IGMP-aware checkbox if you want to enable IGMP support for this MPtMP
service. Enable Admin State, if desired, so that all policers enable traffic flow. Configure IGMP
options as required.
h. In the Objects Selections area, select the ports and Remote PEs in the relevant list.
To deselect an object, right-click and select Deselect, or select the object in the Port List, and on
the toolbar click .
5. To create a policer, click + to expand the selected port. You can enlarge the lower-right area by clicking
the icon above the toolbar, as shown below.

CoS mapping policy. Click + to add the CoS/CoS Group.
7. Select the desired group and Policer Profile.

 For each priority (0 to 7), only one provider CoS must be selected. The default is CoS0 for all
priorities.
 Any change that conflicts with an already defined policer, or that is set with No Rate Limit, is
rejected.
8. In the Port Role dropdown list, select Root or Leaf for the selected port(s). Note that the port role can
be configured as Root or Leaf when the service type is PB MPtMP or MPLS MPtMP.
9. From the QoS Profile dropdown list, select a QoS profile for the selected port(s).
10. From the Flow Block Profile dropdown list, select the Flow Block profile for the selected port(s).

11. From the Proactive Policer Profile dropdown list, select the Proactive Policer profile for the selected
port(s).
12. From the Firewall Profile dropdown list, select the Firewall profile for the selected port(s).
13. For the selected E-NNI port(s), you can also configure the Extern-SVLAN attribute as required.
15. Click the PW List tab. For the Remote T-PE configure, as required, Is MS PW, Peer PE, SHG, Admin State,
Setup Method, PW ID, In VC Label, Out VC Label, Refresh Timer, LSP Type, Tunnel, Control Word,
OAM CoS, BFD Enable, BFD Admin State, Min Transmit Interval, Min Receive Interval, Multiplier, PW
Mode, and TTL.
tLDP setup method.
16. Configure PW Type, Holdoff Timer, if needed. Select PW Status Enabled.

18. If IGMP Interface configuration is required, follow these steps:
a. Click the IGMP Interface Configuration tab.
b. Click the Add icon, select an available port and remote T-PE from the list, and then click Apply.

c. From the Direction dropdown list select DownStream or UpStream.

d. Modify other IGMP Interface options, if required.
19. Click Activate to create and activate the MPLS MPtMP service.
If you click Save, the MPLS MPtMP is saved, but is not activated. To activate it later, select the Recent
Saved VSIs tab. Select the VSI you want to activate in this window, and click Activate. The MPLS MPtMP
service is then activated.
11.12.3 MPLS BPDU tunneling service

To create an MPLS BPDU tunneling service:


4. Select the following parameters:

a. From the Service Type dropdown list, select MPLS BPDU Tunneling.
b. Select the Admin State (default is Enabled). When disabled, all policers block their traffic,
including NNI ports. When enabled, all policers enable traffic flow. This field is editable with no
constraints.
c. Enter the VSI Name, VPN ID, NMS Service ID, User Label, Customer, S-VLAN, and MTU values as
required. For MPLS BPDU Tunneling the only available option for PW Type is Ethernet.
d. (Optional) You can also add a description in the Description field.

e. In the Objects Selections area, select one port and one Remote T-PE, or two ports with the same
port type.
the toolbar click .
5. To create a policer, click + to expand the selected port.

You can enlarge the lower-right area by clicking the icon above the toolbar, as shown below.

CoS mapping policy. Click + to add the CoS/CoS Group.
7. Select the desired group and Policer Profile.

 Any change that conflicts with an already defined policer, or that is set with No-Rate-Limit, is
rejected.
8. For the selected port, if required, change the values for QoS Profile, Flow Block Profile, Proactive
Policer Profile, and Firewall Profile.

10. Click the PW List tab. For the Remote T-PE configure, as required, Is MS PW, Peer PE, SHG, Admin State,
Setup Method, PW ID, In VC Label, Out VC Label, Refresh Timer, LSP Type, Tunnel, Control Word,
OAM CoS, BFD Enable, BFD Admin State, Min Transmit Interval, Min Receive Interval, Multiplier, PW
Mode, and TTL.
tLDP setup method.
11. PW Type is limited to Ethernet for BDPU Tunneling. Configure Holdoff Timer, if needed. Select PW
Status Enabled.
13. Click Activate to create and activate the MPLS BPDU tunneling service.
If you click Save, the MPLS BPDU tunneling service is saved, but is not activated. To activate it later,
select the Recent Saved VSIs tab. Select the VSI you want to activate in this window, and click Activate.
The MPLS BPDU tunneling service is then activated.
11.12.4 MPLS RootedMP/Leaf service

This section describes how to create an MPLS RootedMP/Leaf service. It is supported for the DMGE_2_L2,
DMGE_4_L2, DMGE_8_L2, MPOE_12G, DMXE_48_L2 and CPTS100/CPS100/CS50/CS10/CS320/CS100_1050
cards.
To create an MPLS RootedMP/Leaf service:

1. In the BG-20/BG-30/BG-64/NPT-1200 NE Shelf View window, in the left object tree, select the
DMGE_2_L2/DMGE_4_L2/DMGE_8_L2/MPOE_12G/DMXE_48_L2 and then the Switch object.
Or in the NPT-1200 NE Shelf View window, in the left object tree, select the CS100/CS320 module.
Or in the NPT-1020/NPT-1021/NPT-1050 NE Shelf View window, in the left object tree, select the
CS50/CS10/CS100_1050 module.




a. From the Service Type dropdown list, select MPLS RootedMP/Leaf.
b. Select the VSI State (default is enabled). When disabled, all policers block their traffic, including
NNI ports. When enabled, all policers enable traffic flow. This field is editable with no constraints.
c. (Optional) Select the Enable MAC Address Learning, Enable BSC and SVLAN Enable checkboxes
as required. You can also add a description in the VSI Description field.

d. Enter the VSI ID, User Label, Customer, In VC Label, S-VLAN, BSC Threshold, and vFIB Quota
values as required, and select the Tunnel Mode and VC Label Scheme in the left areas of the
window.
e. In the Objects Selections area, select the ports and, at most, two Remote PEs in the relevant list.
To deselect an object, right-click, or select an object in the lower-right list and on the toolbar click
.

f. To create a policer, on the toolbar click .

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 you can enlarge the lower-right area by clicking above the toolbar, as shown
below.

rejected.
 A CoS can only be removed or discarded from the mapping when it is not associated with No Rate

6. In the DSCP Mapping area, all the VSI UNI/E-NNI ports have the option to enable the same DSCP to
provider CoS mapping policy. The Map DSCP can be disabled and enabled (default is disabled). When
Map DSCP is Enabled, you can set the Map Option as By Name or By Value.
a. If you select the By Name mapping option, you can set CoS mapping for the 21 named DSCPs.
b. If you select the By Value mapping option, define the mapping.
You can input the DSCP values in the following format (same to that of the C-VID):
 Single number, for example, 21
 Multiple numbers, separated by comma (,), for example, 1,3,5,7
 A scope, identified by two numbers connected by dash (-), for example, 1-7
 Any combinations of the above, for example, 1-5,8,19-21

 The last line All Others means the DSCP values except for the listed above will be mapped
to the selected CoS in the right side. If all the DSCP values (0~63) have been listed above
already, the All Others option will be gray out and not editable.
7. In the Tag Type & C-VIDs field:
a. Select the Specific C-VIDs checkbox and define the C-VID range.
b. (Optional) Select the Untagged, Priority Tagged, and Tag Translation checkboxes if needed.
Up to 7000 C-VLANs can be added to all VSIs of the card. The rule of C-VLAN number calculation
as below:

c. On the toolbar click .

d. In the Edit Multi CoS Mapping window you can add, move, delete tags, or delete groups by
selecting the corresponding button.
8. For the selected E-NNI port(s), the Extern-SVLAN can be configured.

9. From the Queue Block dropdown list, set a Queue Block for the selected ports.
10. For the selected Remote PE, select a head tunnel XC that can reach the Remote PE from the CoS
dropdown 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 Activate to create and activate the MPLS RootedMP/Leaf.

If you click Save, the MPLS RootedMP/Leaf is saved but not activated. To activate it, select the Recent
Saved VSIs tab.
12. In this window select the VSI you want to activate, and click Activate.
The MPLS RootedMP/Leaf is then activated.

11.12.5 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, DMGE_8_L2, MPOE_12G, DMXE_48_L2 and CPTS100/CPS100 and
CS50/CS10/CS320/CS100_1050 cards.
To create an MPLS RootedMP/Root service:

1. In the BG-20/BG-30/BG-64/NPT-1200 NE Shelf View window, in the left object tree, select a
DMGE_2_L2/DMGE_4_L2/DMGE_8_L2/MPOE_12G/DMXE_48_L2 card and then the Switch object.
Or in the NPT-1200 NE Shelf View window, in the left object tree, select the CS100/CS320 module.
Or in the NPT-1020/NPT-1021/NPT-1050 NE Shelf View window, in the left object tree, select the
CS50/CS10/CS100_1050 module.



a. From the Service Type dropdown list, select MPLS RootedMP/Root.
b. Select the VSI State (default is enabled). When disabled, all policers block their traffic, including
NNI ports. When enabled, all policers enable traffic flow. This field is editable with no constraints.
c. (Optional) Select the Enable MAC Address Learning, Enable BSC, and SVLAN Enable checkboxes
if needed. You can add a description in the VSI Description field.
d. Enter the VSI ID, User Label, Customer, Out VC Label, S-VLAN, BSC Threshold, and vFIB Quota
values as required, and in the left areas of the window, select the Tunnel Mode and VC Label
Scheme.

e. In the Objects Selections area, select the ports and Remote PEs in the relevant list. To deselect
an object, right-click, or select an object in the lower-right list and on the toolbar click .
f. In the Select PtMP Head Tunnel list, select a PtMP head tunnel that you have created.

g. To create a policer, on the toolbar click .

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. You can enlarge the lower-right area by clicking above the toolbar, as shown below.

rejected.
 A CoS can only be removed or discarded from the mapping when it is not associated with No Rate

6. In the DSCP Mapping area, all the VSI UNI/E-NNI ports have the option to enable the same DSCP to
provider CoS mapping policy. The Map DSCP can be disabled and enabled (default is disabled). When
Map DSCP is Enabled, you can set the Map Option as By Name or By Value.
a. If you select the By Name mapping option, you can set CoS mapping for the 21 named DSCPs in
the figure below.
b. If you select the By Value mapping option, as shown in the figure below.
You can input the DSCP values in the following format (same to that of the C-VID):
 Single number, for example, 21
 Multiple numbers, separated by comma (,), for example, 1,3,5,7
 A scope, identified by two numbers connected by dash (-), for example, 1-7

 Any combinations of the above, for example, 1-5,8,19-21

 The last line All Others means the DSCP values except for the listed above will be mapped
to the selected CoS in the right side. If all the DSCP values (0~63) have been listed above
already, the All Others option will be gray out and not editable.
7. In the Tag Type & C-VIDs field:
a. Select the Specific C-VIDs checkbox and define the C-VID range.
b. (Optional) Select the Untagged, Priority Tagged, and Tag Translation checkboxes if needed.
Up to 7000 C-VLANs can be added to all VSIs of the card. The rule of C-VLAN number calculation
as below:

c. On the toolbar click .

d. In this window you can add, move, delete tags, or delete groups by selecting the corresponding
button.

8. For the selected E-NNI port(s), the Extern-SVLAN can be configured, as shown in the following figure.
9. From the Queue Block dropdown list, set a Queue Block for the selected ports.
10. For the selected Remote PE, select a head tunnel XC that can reach the Remote PE from the CoS
dropdown 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 Activate to create and activate the MPLS RootedMP/Root.

If you click Save, the MPLS RootedMP/Root is saved but not activated. To activate it, select the Recent
Saved VSIs tab.
12. In this window select the VSI you want to activate, and click Activate.
The MPLS RootedMP/Root is then activated.
11.12.6 MPLS VSI list

Management of the MPLS VSI list is the same as of the PB VSI list.
For details about using the MPLS VSI list, see Using the VSI List.
11.12.7 Configure multicast for MPLS RootedMP/Leaf service

For the MPLS RootedMP/Leaf services, you can configure VSI multicast.

To configure multicast:
2. In the Services working mode VSI List tab, the VSI list is displayed.

3. Right-click a VSI in the list with the type MPLS RootedMP/Leaf, and then select VSI Multicast
Configuration.
The Edit/View Multicast Parameters window opens.
4. In the Multicast Configuration tab, in the General Parameters area, set Enable IGMP or Disable IGMP:
 When Enable IGMP (International Group Multicast Protocol) is selected, and you can set the
parameters for Membership Interval and LQMT Interval. The range for Membership Interval is
60- 1023 seconds (default 260).
 When Disable IGMP is selected, you can select the Flood All Groups checkbox.

5. In the Add/Remove Address field, enter the IP multicast address, and then click Add.
6. Click Apply to finish the configuration.

7. To edit or view the multicast configuration, in the VSI List, right-click the VSI that you want to view.
The Edit/View Multicast Parameters window opens.

8. To view the multicast status, select the Multicast Status tab.
11.12.8 MPLS FRR switch

This section describes how to configure the MPLS port protection switch.

To configure the MPLS FRR switch:

1. In the NE Shelf View window, in the left object tree, select an MPLS card and then the MoT/MoE/10GE
MoE port.
3. Set the protection mode by selecting one of the following:

 Lockout of MPLS Interface: Standby port is locked out and cannot be used by protection.
 Forced Switch: Has a higher priority than alarms, which means that a standby port does not
protect a port with an alarm.
 Release: Releases a lockout, a forced switch, or a manual switch on a protection unit contained
in the port.
4. Click Apply.

11.13 Configure PW redundancy for MSPP NEs

This section describes how to configure PW redundancy for MSPP NEs.
The Pseudo-wire (PW) is implicit from the association between a remote PE and a tunnel while the VC label
is defined at the VSI level. There is a new object: secondary remote-PE.
PW can connect between Attachment Circuits (ACs) or between VSI interfaces (or between an AC and a VSI
interface).
Figure 11-21: A PW connecting between two ACs over MPLS network
Figure 11-22: A PW connecting between two VSIs over MPLS network

To configure PW redundancy for MSPP NEs:

1. In an MSPP NE, you can configure the PW redundancy for selected remote PEs in the Create MPLS
MPtMP VSI window.
2. To enable PW Redundancy, select the PW Redundancy checkbox.

3. Configure the attributes for PW redundancy:
 Secondary Remote PE: Secondary remote PE ID should be different from primary remote PE ID.
 Secondary Tunnel: The secondary tunnel label must be different from the primary tunnel label.
 Secondary Out VCLabel: Secondary remote PE out VC label is decided by peer node. (Secondary
remote PE in VC label is the same as primary remote PE in VC label.)
 PWR Trigger: Trigger PWR by PW status messages on BFD. It can only be set as BFD.
4. Click either:
 Activate: To save and activate the VSI.
 Save: To save the VSI.
 Close: Exit the window without saving any settings.

To view PW redundancy status:

1. In the NE Shelf View window, in the VSI list, right-click the MPLS MPtMP VSI with PW redundancy
enabled and then select PW Status and Statistics.
The View PW Redundancy Status window opens.
11.14 Manage MS-PW and PW redundancy

Multi-Segment Pseudowire (MS-PW) extends pseudowires across more than one packet switched network
(PSN) domain and/or more than one PSN tunnel.
Following are description of some attributes in MS-PW:
 MS-PW: Multi-Segment Pseudowire
 SS-PW: Single-Segment Pseudowire
 S-PW: Segment Pseudowire of a MS-PW
 PW Segment: A single-segment or a part of a multi-segment PW
 PWR: PW Redundancy
 S-PE: PW Switching Provider Edge of MS-PW
 T-PE: PW Terminating Provider Edge of MS-PW

A MS-PW reference model can be indicated in the figure below:

 S-PE1 runs two separate control planes: one toward T-PE1, and one toward T-PE2.
 The PW switching point (S-PE) is configured to connect PW Segment 1 and PW Segment 3 together to
complete the multi-segment PW between T-PE1 and T-PE2.
 PW Segment 1 and PW Segment 3 MUST be of the same PW type, but PSN Tunnel 1 and PSN Tunnel 2
need not be the same technology.
 In the latter case, if the PW is switched to a different technology, the PEs must adapt the PDU
encapsulation between the different PSN technologies.
 In the case where PSN Tunnel 1 and PSN Tunnel 2 are the same technology, the PW PDU does not need
to be modified, and PDUs are then switched between the pseudowires at the PW label level.
Figure 11-23: MS-PW reference model
The general approach taken for MS-PWs is to connect the individual control planes by passing along any
signaling information immediately upon reception. The S-PE is configured to switch a PW segment from a
specific peer to another PW segment destined for a different peer. No control messages are exchanged yet,
as the S-PE does not have enough information to actually initiate the PW setup messages. However, if a
session does not already exist, a control protocol (LDP/L2TP) session MAY be setup. In this model, the MS-
PW setup is starting from the T-PE devices. Once the T-PE is configured, it sends the PW control setup
messages. These messages are received by the S-PE, and immediately used to form the PW setup messages
for the next SS-PW (Single-Segment Pseudowire) of the MS-PW (Multi-Segment Pseudowire).
MS-PW is supported in Central PEs of NPT-1200, NPT-1020, NPT-1050 and NPT-1010.
11.14.1 Configure the VC label scheme

For all the MPLS VSI of Central PEs in NPT NEs, the VC Label Scheme attribute is supported, with a new value
Regular.
Following are some limitations for the VC label scheme:
 In VC Label with "Regular" must be unique in local;
 For MS-PW in S-PE, VC Label Scheme must always be "Regular";
 If PW is MS-PW in T-PE, "Regular" VC Label Scheme is used;
 If PW is SS-PW in T-PE, any VC Label Scheme can be used;
 The L-LSP tunnel Mode cannot exist with "Regular" VC Label Scheme in one VSI.

To configure the VC label scheme:

2. Select Service and then select the VSI List tab.
3. Click .
The Create VSI window opens:

4. In the Service Type dropdown list, select a MPLS service type.

The VC Label Scheme can then be configured as Same Incoming Label or Regular VC Label.
If you selected the MS-PW service type, the VC Label Scheme is fixed to Regular VC Label, as shown in
the following figure:

11.14.2 View the MS-PW/PW redundancy budget

To view the MS-PW/PW redundancy budget:
2. Select Configuration and then select the General tab.
3. View the PW redundancy budget and MS-PW budget in relevant area, which are described in the
following table.
Table 11-6: PW Redundancy Budget

Max number of PWR with The Maximal number of PWR with enabled Static PW Status supported by
Static PW Status the system.
Max number of PWR Group The Maximal number of PWR group with disabled Static PW Status
without Static PW Status supported by the system.
One PWR group means all PWRs with same Primary tunnel and secondary
tunnel and PW Status Disabled.
Current number of PWR with The current number of PWR with Static PW Status enabled.
Static PW Status


Current number of PWR The current number of PWR group with disabled Static PW Status
Group without Static PW supported by the system.
Status One PWR group means all PWRs with same Primary tunnel and secondary
tunnel and PW Status Disabled.
Current number of PWR The current number of PWR with disabled Static PW Status supported by
without Static PW Status the system.
Table 11-7: MS-PW Budge

Max Number of MS-PW VSIs maximum of MS-PW VSIs.
Current Number of MS-PW the current number of MS-PW VSIs.
VSIs
11.14.3 Create MS-PW services

To create an MS-PW service:

3. Click .
4. In the VSI Parameter area, enter the following information:

 Service Type: select MS-PW.
 VSI State: select Enabled or Disabled as required.
 VSI ID: set MS-PW ID.
 NMS VSI ID: set NMS VSI ID.
 (Optional) User Label: enter user label of the VSI.
 (Optional) Customer: enter the name of customer.
 (Optional) Description: enter description of the VSI as required.
5. In the Objects Selections list, select two Peer PEs you want to add to the MS-PW VSI.
6. For each selected Peer PE, configure the following parameters:
a. Select a BD LSP tunnel from the Tunnel dropdown list;
b. Set the In VC Label and Our VC Label in relevant area;
c. Set the PW configuration as described in the MS-PW VSI Configuration Attributes table.

7. Click either:
11.14.4 Set PW/PWR configuration in MPLS VSIs

This section describes the PW/PWR configuration in other MPLS VSIs in NPT NEs, which includes:
 MPLS PtP
 MPLS MPtMP
 CESoMPLS
To set PW/PWR configuration in MPLS VSIs:


3. Click .
4. In the Service Type list, select one of the following:

 MPLS PtP
 MPLS MPtMP
 CESoMPLS
5. Configure the other parameters as described in Creating MPLS Services.

6. For the selected Peer PE, set the PW/PWR configuration in corresponding area, as described in the MS-
PW VSI Configuration Attributes table.
 If "Is MS-PW" is enabled, in the Remote T-PE area, click .

The Define Remote T-PE window opens.
7. Click either:

11.14.5 Perform PWR operational command

PWR operational command is maintenance protection switching commands for PW Redundancy. It is
applicable in Dual Homing H-VPLS topology, and only for pivot PE.
To perform PWR operational command:

2. Select Maintenance and then select the PWR Operational Command tab.
3. Click + and then select one or more of the following filter options:
 VSI ID: select a specific VSI from the dropdown list.
 Primary Remote PE: select a primary remote PE from the dropdown list.
4. Click Apply.
The PWR operational command is applied.

11.14.6 View PW status and statistics

To view PW status and statistics:

3. Right-click a VSI with PW, and then select View PW Status and Statistics.
The View PW Status and Statistics window opens.
4. To get the parameters to view, click .
5. To clear the statistics counters, click .
Table 11-8: PW status attributes per PW

Forwarding Status The current forwarding role of the PW as determined by PW Redundancy
controller.
This attribute is a dynamic data; it is stored per each member PW (it is stored
in PW Redundancy Object and not in VSI IF object).
For NULL member this attribute is set to Irrelevant.
Advertised Status The local Preferential Forwarding Status (Active/Standby) which is advertised
for the PW.
For NULL member this attribute is set to Irrelevant.
Remote Status If PW Status Signaling is Enabled, it is the Remote Preferential Forwarding
Status (Active/Standby) as received in Static PW Status messages for this PW.
Before the first Static PW Status message is received from the far end, the
remote status is set to Unknown.
If PW Status Signaling is Disabled, It is always Active.
For NULL member this attribute is set to Unknown.


MC-LAG Status The status of the MC-LAG configured in the VSI where PW Redundancy is
configured.
If MC-LAG is not configured in the VSI, the value of this attribute shall be
Undefined.
PW Operational State The operational state of the PW, as derived from OAM mechanisms, given
that BFD Trigger is Enabled.
Core PWs Status The status of Core PWs of this PW.
Number of PW State This attribute indicates the number of PW state changed.
Changed
Time Expired of Since PW This attribute indicates the time of since PW state changed.
State Changed
Table 11-9: PW statistics per PW

Tx PW Status Messages This attribute indicates the number of PW status message transmitted.
Rx PW Status Messages This attribute indicates the number of PW status message received.
Rx Invalid PW Status This attribute indicates the number of invalid PW status message received.
Table 11-10: MS-PW VSI configuration attributes

Is MS-PW In S-PE, it is always invisible.
In T-PE: if the next PE of PW is T-PE, then it is "No"; if the next PE of PW is S-
PE, then it is "Yes".
It is only applied to MPLS PtP/MPtMP and CESoMPLS. Other MPLS VSIs
(RootMP Leaf/Root VSI, ERPS VSI with MPLS Ring type, BPDU tunneling) are
support.
Remote T-PE ID The remote T-PE ID of MS-PW in T-PE. It is only valid for MS-PE in T-PE, and is
invisible for MS-PW in S-PE and SS-PW.
Peer PE ID The peer PE ID of PW. It is only valid for SS-PW and MS-PW in S-PE.
In VC Label This attribute indicates the In VC Label of PW. If VC Label Scheme is "Same
Incoming Label", it is same for all PWs in this VSI; if VC Label Scheme is
"Regular", it is unique and different in local.
Our VC Label This attribute indicates the Out VC Label of PW.
Tunnel This attribute indicates ID of out tunnel which is connected to Peer PE.
Static PW Status Enabled This attribute indicates PW status message transmitted and received on PW.
For MS-PW in S-PE, it is always Enabled.


Static PW Status CoS The CoS used by PW Status messages. This CoS is used on all PWs in the PW
Redundancy.
Valid values: common CoSs of primary and secondary tunnels.
Default value: common highest CoS.
Hold Off Timer Hold off timer for PW redundancy protection switching upon server-layer
defect indications.
Core PWs Trigger PW This attribute indicates if Core PWs state is an input of PW or not. It is invalid
Status and invisible for MS-PW in S-PE.
Is Core PW This attribute indicates if this PW is Core PW which will affect the other PWs
state or not. It is invalid and invisible for MS-PW in S-PE.
11.15 BFD management in MSPP/NPT

An increasingly important feature of networking equipment is the rapid detection of communication failures
between adjacent systems, in order to more quickly establish alternative paths. Detection can come fairly
quickly in certain circumstances when data link hardware comes into play (such as Synchronous Optical
Network (SONET) alarms). However, there are media that do not provide this kind of signaling (such as
Ethernet), and some media may not detect certain kinds of failures in the path, for example, failing interfaces
or forwarding engine components.
Networks use relatively slow "Hello" mechanisms, usually in routing protocols, to detect failures when there
is no hardware signaling to help out. The time to detect failures ("Detection Times") available in the existing
protocols are no better than a second, which is far too long for some applications and represents a great deal
of lost data at gigabit rates. Furthermore, routing protocol Hellos are of no help when those routing protocols
are not in use, and the semantics of detection are subtly different -- they detect a failure in the path between
the two routing protocol engines.
The goal of Bidirectional Forwarding Detection (BFD) is to provide low-overhead, short-duration detection of
failures in the path between adjacent forwarding engines, including the interfaces, data link(s), and, to the
extent possible, the forwarding engines themselves.
BFD is a simple Hello protocol that, in many respects, is similar to the detection components of well-known
routing protocols. A pair of systems transmit BFD packets periodically over each path between the two
systems, and if a system stops receiving BFD packets for long enough, some component in that particular
bidirectional path to the neighboring system is assumed to have failed. Under some conditions, systems may
negotiate not to send periodic BFD packets in order to reduce overhead.
Continuity Check, Proactive Connectivity Verification, and Remote Defect Indication functionalities are
required for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM).
 Continuity Check monitors a Label Switched Path for any loss of continuity defect. Connectivity
Verification augments Continuity Check in order to provide confirmation that the desired source is
connected to the desired sink.
 Remote Defect Indication enables an end point to report, to its associated end point, a fault or defect
condition that it detects on a pseudowire, Label Switched Path, or Section.
 Remote Defect Indication (RDI) is an indicator that is transmitted by a MEP to communicate to its peer
MEP that a signal fail condition exists.

This section describes the Bidirectional Forwarding Detection (BFD) and the configuration of the BFD.
BFD management can be supported for all the data cards that with a Switch module.
Regarding BFD support capability, BG MSPP cards have following limitations:
 MPS_6F, MPS_4F, DMFE_4_L2, DMFX_4_L2, DMGE_2_L2, MPS_2G_8F, ME_2G_4F
 Supported BFD intervals: 100ms, 1000ms;
 Maximum number of 100ms BFD sessions: 10
 Maximum number of 100ms and 1000ms BFD sessions: 100
 DMGE_4_L2, DMGE_8_L2, DMXE_48_L2, DMXE_22_L2, MPoE_12G, CS100, CS320, CS50, CS10,
CS100_1050
 Supported BFD intervals: 3.33ms, 10ms, 100ms, 1000ms;
 Maximum number of BFD sessions over bidirectional LSP: 256
 Maximum number of 3.33ms BFD sessions: 100
11.15.1 Manage BFD protocols

This section describes how to manage BFD protocol in the data cards in LCT-NPT.
To manage BFD protocol:

2. In the Configuration working mode, select BFD > BFD Protocol.

3. You can enable or disable all BFD sessions by setting the BFD Protocol enabled or disabled.
4. Set the attributes as required for the BFD protocol.
5. Click Apply.
11.15.2 Manage BFD templates

This section describes how to manage BFD templates, including:
 Create BFD templates
 Edit BFD templates
 View BFD templates
 Delete BFD templates
 Synchronize

To manage BFD templates:

2. In the Configuration working mode, select BFD > BFD Template.
The BFD Template tab lists all the BFD templates.

3. To create a BFD template, click on the toolbar.

The Create BFD Template window opens.
Set the parameters for the BFD template as required and click Apply to save the settings.
 The minimum values mean that NE can support minimum interval or higher value by configuring
the values. If you configure 100ms, then the NE can support >=100ms interval by negotiation.
 Multiplier is times of negotiation interval for detecting dLOC. For example, if negotiation interval
is 100ms and multiplier is 3, then if there are no BFD packets received during 3 x 100ms, dLOC will
be reported.
4. To edit a BFD template, select a template in the list and then click .
5. Modify the settings in the window and click Apply to save the changes.
6. To view a BFD template, select a template in the list and click on the toolbar.
7. To delete a BFD template, select a template in the list and click .
8. To synchronize the BFD templates, click .

11.15.3 Manage BFD tunnel sessions

To manage BFD tunnel sessions:
2. In the Configuration working mode, select BFD > BFD Tunnel Session.
3. To create a BFD tunnel session, click .

The Create BFD Session window opens.
4. Set the attributes as described as below:

 BFD Session ID: ID of the BFD session, can be set from 1 to 500.
 Template Name: select a created BFD template from the dropdown list.
 BD Tunnel ID: select a BD-LSP tunnel from the dropdown list.
 BD LSP Number: select a BD-LSP number you set the BD-LSP tunnel.
 CoS: lists the CoS that belongs to the bi-directional tunnel.
 Admin State: can be set as Enable or Disable.
5. Click Apply.
6. To edit a BFD tunnel session, select a BFD tunnel session in the list and then click .

8. To view the BFD tunnel session status, select a BFD tunnel session in the list and then click .
The following BFD tunnel session status parameters are displayed:

 BFD Tunnel Session ID: ID of the BFD tunnel session.
 Template Name: name of the BFD template.
 BD Tunnel ID: ID of BD tunnel.
 BD LSP Number: number of BD LSP.
 Session Up Time: time of BFD tunnel session up.
 Local Status: local BFD status.
 Remote Status: remote BFD status.
 Desired Tx: desired Tx interval of BFD packet.
 Desired Rx: desired Rx interval of BFD packet.
 Negotiation Tx: negotiation Tx interval of BFD packet.
 Negotiation Rx: negotiation Rx interval of BFD packet.
 Diagnostic Local/Remote: the diagnostic reason of BFD down/up.
 Packets CC Tx/Rx: number of CC (one packet type of BFD) packets transmitted/received.
 Packets Invalid CC Rx: number of invalid CC (one packet type of BFD) packets
transmitted/received.
9. To delete a BFD tunnel session, select a BFD tunnel session in the list and then click .
10. To synchronize the BFD tunnel sessions, click .

11.15.4 Manage BFD section sessions

To manage BFD section sessions:
2. In the Configuration working mode, select BFD > BFD Section Session.
3. To create a BFD section session, click .

The Create BFD Section Session window opens.

 BFD Session ID: ID of the BFD session. It is unique in the switch and can be set from 1 to 500.
 Template Name: Select a created BFD template from the dropdown list.
 Interface: The Interface ID and Name, including MoT/MoE/10GE MOE ports and PB INNI ports.
One port can be used in BFD section sessions only once.
5. Click Apply. The BFD section session is saved.
6. To edit a BFD section session, select a BFD section session in the list and then click .

8. To view the BFD section session status, select a BFD section session in the list and then click .
9. To delete a BFD section session, select a BFD section session in the list and then click .
10. To synchronize the BFD section sessions, click .
11.15.5 Manage PW BFD sessions

PW BFD session is supported for the following services:
 MPLS PtP
 MPLS MPtMP
 MPLS RootedMPLeaf
 MPLS RootedMPRoot
 ERPS VSI
In LCT-NPT V6.0, only end to end PW BFD is supported. CESoMPLS and MSPW don't support PW BFD.

 For the end to end BFD, the Control Word attribute in the Create VSI window must be enabled. For
details about PW control word, see PW control word for NPT.

To manage PW BFD sessions:

2. In the Configuration working mode, select BFD > PW BFD sessions.
3. To create a PW BFD session, click .

The Create PW BFD Session window opens.

 Session ID: The BFD session ID of PW.
 VSI ID: VSI ID which PW belongs to.
 Remote T-PE: Remote T-PE ID if VSI is non-MS-PW VSI.
 PW Role: The PW role.
 BFD Mode: The BFD mode.
 TTL: TTL of VC.
 CoS: Describes Cos of BFD packets transmitted.
 Template Name: Select a created BFD template from the dropdown list.
5. Click Apply. The PW BFD session is saved.
6. To edit a PW BFD session, select a PW BFD session in the list and then click .

8. To view the PW BFD session status, select a PW BFD session in the list and then click .
9. To delete a PW BFD session, select aPW BFD session in the list and then click .
10. To synchronize the PW BFD sessions, click .
11.15.6 BFD trigger

BFD Trigger attribute can be configured for:
 FRR (MoT/MoE/10GE MoE port)
 ERP (PB INNI port)
 PW Redundancy

11.15.6.1 Configure BFD trigger for fast reroute (FRR)

To configure BFD Trigger for FRR:
1. In the NE Shelf View window, in the left object tree, select a MoT/MoE/10GE MoE port of a data card.
3. In the MPLS FRR area, you can enable or disable BFD to trigger protection switching.

11.15.6.2 Configure BFD Trigger for ERP

To configure BFD Trigger for ERP (ethernet ring protection):
 In the Create ERPS VSI window, You can enable or disable the BFD trigger for the selected PB I-NNI
ports, as shown in the following window.
For details of Creating ERPS VSIs, see Ethernet Ring Protection Switching in the LCT-NPT Network
Management Guide.

11.15.6.3 Configure BFD trigger for PW redundancy

To configure BFD Trigger for PW redundancy:
3. At the bottom of the window, you can enable or disable the BFD for PW redundancy.
11.16 Manage queue blocks

Queue Blocks (QB) is an object which used by PB ports. Each QB has up to 8 CoSs of queues, just like E-LSP
on MPLS port. One QB can be mapped to one L3 of Traffic Manager (TM) on EZchip cards. So the total L3
resource will be shared by QB on PB ports and E-LSP on MPLS ports.
Up to 1024 Queue Blocks can be supported on PB ports per cards.

11.16.1 Queue blocks supported cards

QB management can be supported for all the EZchip cards.
For DMXE_22_L2, only GE ports support QB. 10GE ports don't support.
11.16.2 Create a queue block

To create a queue block:
1. In the NE Shelf View window, in the left object tree, select the Switch object of an EZchip card.
2. In the Configuration working mode, select the Queue Block tab.

3. To create a Queue Block, click .

The Create Queue Block window opens.

 Queue Block ID: set an ID for the Queue Block, which is unique in a NE.

 Queue Block Name: set a name for the Queue Block, which is unique in a NE.
 Out Interface: select a port as an out interface for the Queue Block. QB cannot be created on a
PB port with Strict Priority scheduling mode, and VCG Bandwidth of the selected port cannot be
0.

 PIR: can be set as No Rate Limit or BW Limitation(Mbps). The default value is 50Mbps for PIR BW
Limitation.
 CoS: At least one CoS must be selected.
5. Click Apply.


6. To edit a Queue Block, select a Queue Block in the list, and click .
The Edit Queue Block window opens.
8. To view a Queue Block, select a Queue Block in the list, and then click .
9. To delete a Queue Block, select a Queue Block in the list, and then click .
10. To overwrite the Queue Blocks, click .

11.16.3 Manage Queue Blocks in VSIs

To set a Queue Block in VSIs:
1. In the create VSI window, you can set QB configuration for the selected ports for the VSI (except EPL,
ERPS and CESoMPLS).
2. For the selected port(s), select a QB in the corresponding Queue Block dropdown list.
For details of creating the VSI, see the following:
 Services management in MSPP/NPT
 CES services management
11.16.4 Port-level shaping

Port-level shaping can be supported by EZchip cards for:
 PB ETY port, including FE/GE/10GE ports
 MoE/10G MoE ports

To configure port-level shaping:

1. In the NE Shelf View window, in the left object tree, select a port.
3. In the Port Level Shaping area, set the parameters as required.
11.17 CFM
As references from ITU-T Recommendation Y.1731 (a reference number of a standard which defines
functionality) OAM functions and mechanisms for Ethernet based networks, the goal of Ethernet Operations,
Administration, and Maintenance (OAM) is to allow service providers to manage each customer service
instance individually. Ethernet OAM defines proactive and diagnostic fault localization procedures for PtP
and multipoint services that span one or more links, and functions end to end within an Ethernet network.
Ethernet OAM applies to CFM detect, verify, localize, and notify different defect conditions.
Ethernet CFM (connectivity fault management) relies on a functional model consisting of hierarchical
maintenance domains (MDs). An MD is an administrative domain for 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. MDs 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.
An MD is defined by provisioning which switch/router ports are interior to the domain.

In addition, maintenance endpoints (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 the
relevant points in the network.
Figure 11-24: Multidomain 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 describe the managed entities:
 Maintenance Entity (ME): Entity that requires management.
 Maintenance Association (MA) (or Maintenance Entity Group - MEG): 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 PtP or multipoint Ethernet connection. For a PtP 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 endpoints.
 Maintenance Entity Group EndPoint (MEP): Maintenance functional entity that is implemented at the
ends of an ME. It generates and receives OAM frames. An ME represents a relationship between two
MEPs.
 Maintenance Entity Group Intermediate Point (MIP): Maintenance functional entity located at
intermediate points along the E2E 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): Either MEP or MIP.

 MD Level: If 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. A MEG that
belongs to a specific MD level has a default MEG level assignment amongst customer, provider, and
operator roles, as follows:
 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.
This section describes the aspects of Connectivity Fault Management (CFM).
11.17.1 CFM supported cards

CFM can be supported in all the Layer 2 data cards in LCT-NPT.
11.17.2 Manage CFM MAs

To create CFM MAs:
4. Create CFM Domains (MDs);
5. Create CFM MIPs;
6. Create CFM MAs.

11.17.2.1 Create CFM Domains

To create CFM domains:
2. In the Configuration working mode, select the CFM Domain tab.

4. In the Create CFM Domain window, enter the Domain Name, and from the dropdown list, select the
Domain Level.
The Domain Name and Domain Level must both be unique. The Domain Level is from 0 to 7, so you
create at most 8 MDs.
5. Click Apply to save the MD and close the Create CFM Domain window.

6. From the MD list, you can carry out the following functions:
 View the created MDs.
 Refresh the MD list (click ). Click to overwrite the MD list in the DB with the data from
the equipment.
 Delete an MD (select it and click ).
 Clear the data in both the DB and the equipment (click ).
11.17.2.2 Create CFM MIPs

After creating the MDs, you can create CFM MIPs.
MIPs can be created on MoE port, and you can perform loopback and trace a MIP within an MA. The MIP is
valid only for Head/Tail XC on MoE port.
MIP on MoE can conveniently detect the connectivity of service and locate the fault in VPLS network and H-
VPLS network.
To create CFM MIPs:

1. In the same MPLS card, select a LAN/WAN/MoT/MoE/10GE MoE port of UNI/ENNI/INNI or a LAG port
in the left object tree.
2. In the Configuration working mode, select the CFM MIPs tab.


4. In the Create CFM MIP window, in the Domain Name list, select a domain you have created.
5. In the MIP ID area, input an MIP ID.
6. (Optional) Select the Enable checkbox.
7. Click Apply to save the MIP in the CFM MIP list.
8. Close the Create CFM MIP window and view the created MIPs in the MIP list.
9. To edit a MIP, in the list select the MIP you want to edit and then click .
The Edit CFM MIP window opens.

10. Select the Enable checkbox to enable the MIP.
11. Repeat Steps 1-3 to create Domains and MIPs for another MPLS card. Only the MPLS cards with the
same Domains and MIPs can create an MA.

11.17.2.3 Create CFM MAs

To create CFM MAs:
1. To create an MA, in the NE Shelf View window, in the left object tree, select an MPLS card and then the
Switch object.

4. From the Service Type list, select a PB or MPLS service.
5. Set the VSI Parameters as needed and from the Objects Selections area.

6. Select the ETY and EoS ports. Set the parameters for the selected port and remote PE.

7. In the Create VSI window, select the CFM MA List tab.


The Create CFM MA window opens.
a. In the MA Parameter area, select a Domain Name, enter the MA Name, and select the Enable
CCM checkbox.
b. In the MEPs area, select local and remote MEPs from the corresponding lists.
The selected MEPs are saved as follows:
 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. You can also
add external NEs as remote MEPs by entering the MEP ID.

c. In the Local MEPs and Remote MEPs lists, set MEP IDs for the selected ports.
9. To save the CFM MA, click Save, or click Save & Close if you want to save the MA and close the window.

10. To edit an MA in the CFM MA list, select the MA you want to edit, and click .
The Edit CFM MA window opens.
11. To view the details of an MA, click .

The View CFM MA window opens.
12. To delete an MA, select the MA you want to delete, and click .

An MA with CCM enabled cannot be removed. First disable the CCM in the Edit CFM MA window.
13. To save the VSI, in the CFM MA List, click Save.
To save and activate the VSI, click Activate.
14. To upload an MA, select the VSI in the list, and on the toolbar, click the MA Upload icon .
The CFM MA Upload window opens.

15. Click Upload to upload all the MAs. The status bar shows the consistency status between the NE and
the DB.

16. To overwrite the DB with the NE data, click Overwrite.

If the NE and the DB are inconsistent, select the CFM MA Compare tab to display the inconsistency
results.
11.17.3 CFM related performance

This section describes how to view CFM performance.
11.17.3.1 View CFM MA attributes

To view CFM MA attributes:
2. In the Performance, Performance Settings working mode, select the Threshold Setting tab.

3. In the Display field, select the MA radio button.
4. In the Filter area, select a VSI and an MA from the corresponding dropdown lists and then click .
Table 11-11: MA attributes related to Service OAM

MA Target FD Target Frame Delay value
MA Target FD Percent Target Frame Delay Percent value
MA Target FDV Target Frame Delay Variation value
MA Target FDV Percent Target Frame Delay Variation Percent value
Unavailability Threshold Used in evaluating the availability/unavailability status
Enables MEP to receive and reply to Frame Loss Ratio messages
Respond to SLM Messages
SLM Availability Window
The configurable number of consecutive availability Frame Loss Ratio
measurements to be used to determine Availability/Unavailability
transitions

11.17.3.2 View CFM PM switch counters

To view CFM PM switch counters:
2. In the Performance working mode, select the Current tab.
3. In the Display dropdown list, select CFM PM Switch.
4. In the Type field, select 15 minutes PM or 24 hours PM and then click .

5. To observe any performance data changes dynamically:
a. Select the Refresh data dynamically checkbox and set the Refresh Interval.
b. Click the Start Refresh button.
Data is refreshed, based on the Refresh Interval that you specified.
c. To cancel the refresh operation, click Stop Refresh.
Table 11-12: Switch counters related to Service OAM PM

Monitored Seconds Time of monitoring
Suspect Flag The current register suspect interval flag will be set to True to indicate that
data stored in the register may not be reliable


SOAM PM Frames Discarded Total number of (Ethernet) Service OAM PM frames discarded by NPU for
by NPU various reasons
Invalid DMM Discarded Total number of discarded invalid Delay Measurement Message frames
Invalid DMR Discarded Total number of discarded invalid Delay Measurement Response frames
Invalid SLM Discarded
Total number of discarded invalid Synthetic Loss Message frames
Total number of discarded invalid Synthetic Loss Reply frames
Invalid SLR Discarded
11.17.3.3 View CFM DM sessions

This section describes how to view the DM session attributes.
To view CFM DM sessions:

2. In the Performance, Performance Settings working mode, select the CFM DM Session tab.
3. In the Filter area, select a VSI, MD Level, MA and Remote MEP from the corresponding dropdown lists
and then click .

Table 11-13: CFM DM Session related to Service OAM PM

Remote MEP The ID of the Remote MEP
DM Enable Enables MEP to transmit DMM messages and receive DMR message
DM Period Configuration of the transmission period of the DMM messages:
 100 ms
 1000ms
 10000ms
DM Frame Size DM Frame size in bytes for Dual-Ended ETH-DM measurements
DM CoS Configuration of the transmission period of the DMM messages. It must be
in this service VSI and not be used by other sessions in this MA and remote
MEP.
Destination MAC Option of remote MEP
DMac Option
DMac
Destination MAC of remote MEP if DMAC Option is Yes. If DMAC Option is
No, then this attribute is grayed.
11.17.3.4 View CFM LM status

You can view the CFM DM/LM status for the active VSIs that have MA and remote MEP, including:
 Status of Delay Measurement (DM) - measurement of Frame Delay (FD) and Frame Delay Variation
(FDV) - not supported yet.
 Status of Loss Measurement (LM) - measurement of Frame Loss Ratio (FLR) and Availability

To view CFM LM status:

1. In the VSI list, right-click an active VSI that has MA and remote MEP, and then select Remote MEP
Status > CFM LM Status.
The View CFM LM Status window opens.
2. To view the status, select an MA and a remote MEP from the corresponding dropdown lists, and click
.
3. To reset the data in NE equipment, on the toolbar, click .

The remote MEP attributes related to LM status are described in the following table.
Table 11-14: Remote MEP attributes related to CFM LM status

Session ID Received Last Session ID received by a Responder MEP for the first Frame Loss Ratio
session.
SLM CoS Received Synthetic Loss Message CoS received by a Responder MEP.
SLM Frames Received Number of received Synthetic Loss Message frames.
SLR Frames Transmitted Number of transmitted Synthetic Loss Reply frames.

11.17.3.5 View CFM DM status

To view CFM DM status:
1. In the VSI list, right-click an active VSI that has MA and remote MEP, and select Remote MEP Status >
CFM DM Status.
The View CFM DM Status window opens.
2. To view the status, select an MA and a remote MEP from the corresponding dropdown lists, and then
click .
3. To reset the data in NE equipment, on the toolbar, click .

The remote MEP attributes related to DM status are described in the following table.
Table 11-15: Remote MEP attributes related to CFM DM status

DMM Frames Transmitted Number of transmitted Delay Measurement Message (DMM) frames (i.e.,
number of initiated measurements)
DMR Frames Received Number of received Delay Measurement Response (DMR) frames (i.e.,
number of completed measurements)


Current FD Frame Delay (usec) of the last time
Average FD Average Frame Delay (usec) during the interval
Maximum FD Maximum Frame Delay (usec) during the interval
Minimum FD Minimum Frame Delay (usec) during the interval
Current FDV-FWD Direction Frame Delay Variation (usec) of the last time in forward direction
Average FDV-FWD Direction Average Frame Delay Variation (usec) during the interval in forward
direction
Maximum FDV-FWD Maximum Frame Delay Variation (usec) during the interval in forward
Direction direction
Current FD-BCK Direction Frame Delay Variation (usec) of the last time in backward direction
Average FDV-BCK Direction Average Frame Delay Variation (usec) during the interval in backward
direction
Maximum FDV-BCK Direction Maximum Frame Delay Variation (usec) during the interval in backward
direction

11.17.3.6 View CFM DM session counters

To view CFM DM session counters:
3. In the Display dropdown list, select CFM DM Session.

4. In the Type field, select 15 minutes PM or 24 hours PM.
5. In the Filter area, select a VSI, MD Level, MA and Remote MEP from the corresponding dropdown lists
and then click .
Data is refreshed, based on the Refresh Interval you specify.

Table 11-16: CFM DM Session counters related to Service OAM PM

Monitored Seconds Indicate how many seconds of the interval have been processed.
data stored in the register may not be reliable.
DMM Frames Transmitted Number of transmitted Delay Measurement Message frames (i.e. number
of initiated measurements)
DMR Frames Received Number of received Delay Measurement Response frames (i.e. number of
completed measurements)
Not Compliant FD Number of Frame Delay measurements which fell above the threshold
Not Compliant FDV-FWD Number of Frame Delay Variation measurements in forward direction
Direction which fell above the threshold
Number of Frame Delay Variation measurements in backward direction
Not Compliant FDV-BCK
which fell above the threshold
Direction
Average Frame Delay (usec) during the interval
Average FD
Maximum Frame Delay (used) during the interval
Maximum FD
Minimum Frame Delay (usec) during the interval
Minimum FD
Average Frame Delay Variation (usec) during the interval in forward
Average FDV-FWD Direction
direction
Average Frame Delay Variation (usec) during the interval in backward
Average FDV-BCK Direction
direction
Minimum Frame Delay Variation (usec) during the interval in forward
Minimum FDV (forward
direction
direction)
Maximum Frame Delay Variation (usec) during the interval in forward
Maximum FDV (forward
direction
direction)
Minimum Frame Delay Variation (usec) during the interval in backward
Minimum FDV (backward
direction
direction)
Maximum Frame Delay Variation (usec) during the interval in backward
Maximum FDV (backward
direction
direction)

11.17.3.7 Manage CFM LM sessions

This section describes how to create a CFM Loss Message (LM) session, and how to view the LM session
attributes.
To manage CFM LM sessions:

2. In the Performance, Performance Settings working mode, select the CFM LM Session tab.

3. To create a CFM LM session, on the toolbar, click .

The Create CFM LM Session window opens.

4. Select a VSI from the VSI dropdown list, set the attributes as required for the CFM LM Session and then
click Apply to create the session.
5. To view the CFM LM session attributes, in the Filter area, select a VSI, MD Level, MA and Remote MEP
from the corresponding dropdown lists and then click .
Table 11-17: CFM LM session attributes related to Service OAM PM

Session ID The Session ID to use by the Controller MEP for the SLM session
SLM Enable Enables MEP to transmit SLM messages and receive Synthetic Loss Reply
message
SLM Period Configuration of the transmission period of the SLM messages:
 100 ms
 1000ms
 10000ms
SLM Frame Size SLM Frame size in bytes for Dual-Ended ETH-SLM measurements


Configuration of the transmission period of the SLM messages. It must be
SLM CoS
in this service VSI and not used by other sessions in this MA and remote
MEP
SLM FLR Window
The number of transmitted SLM PDUs used for each Frame Loss Ratio
calculation
11.17.3.8 View CFM LM session counters

To view CFM LM session counters:
3. In the Display dropdown list, select CFM LM Session.

4. In the Type field, select 15 minutes PM or 24 hours PM.
5. In the Filter area, select a VSI, MD Level, MA, Remote MEP and SLM Session from the corresponding
dropdown lists. On the toolbar, click .


Data is refreshed, based on the Refresh Interval you specify.
Table 11-18: CFM LM Session counters related to Service OAM PM

SLM Test ID Synthetic Loss Message Test ID of this session on this MEP (PtP session) or
MA with this MEP (PtMP session)
Monitored Seconds Indicate how many seconds of the interval have been processed.
data stored in the register may not be reliable.
SLM Frames Transmitted Number of transmitted Synthetic Loss Message frames (i.e. number of
initiated measurements)
SLR Frames Received Number of received Synthetic Loss Reply frames (i.e. number of completed
measurements)
Last Far End FLR Last Far End Frame Loss Ratio for the remote MEP
Min Far End FLR The minimum Far End Frame Loss Ratio for the remote MEP during this
Measurement Interval
Max Far End FLR The maximum Far End Frame Loss Ratio for the remote MEP during this
Avg Far End FLR The average Far End Frame Loss Ratio for the remote MEP during this
Last Near End FLR Last Near End Frame Loss Ratio for the remote MEP
Min Near End FLR The minimum Near End Frame Loss Ratio for the remote MEP during this
Max Near End FLR The Maximum Near End Frame Loss Ratio for the remote MEP during this
Avg Near End FLR The average Near End Frame Loss Ratio for the remote MEP during this
Far End SEW Number of Far End Severely Errored Windows
Near End SEW Number of Near End Severely Errored Windows
Far End Unavailable seconds Number of seconds evaluated as unavailable in the forward direction
Near End Unavailable Number of seconds evaluated as available in the backward direction
seconds

11.17.4 Perform CFM maintenance

Ethernet service OAM includes the following management functions:
 CCM: Continuity Check OAM messages (CCMs) are multicast messages to each MEP in an MA/MEG. All
MEPs in a MEG receive CCMs. They do not respond but maintain records about the status of other MEPs
of the MEG. MIPs are transparent to the CCM messages.
Figure 11-25: CCM protocol
CCM transmission may be enabled or disabled in a MEG. When enabled, MEPs periodically exchange
CCMs. The Continuity Check Protocol has the following features:
 Detects loss of continuity.
 Detects incorrect network connections:
 Unintended connectivity between two MEG
 Unintended connectivity within the MEG with an unexpected MEP
 Detects other defect conditions:
 Unexpected MEG level
 Unexpected CCM period
 Loopback: Loopback is a ping-like request/reply protocol. MEPs send loopback messages (LBMs) 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.
Figure 11-26: Loopback protocol

 Link Trace: Link Trace Protocol can be used to trace the path to the target MEP and for fault isolation.
MEPs send a 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.
Figure 11-27: Link trace protocol
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 NE is aware of this address in
the LTM frame and associates it with a single egress port. If not, the LTM frame is relayed unchanged
to all egress ports associated with the MEG, except to the one where it was originally received.
This section describes how to perform CFM maintenance functions from the CFM MA list.

To perform CFM maintenance in the CFM MA list:

1. In an NE Shelf View window, in the left object tree, select an MPLS card and then the Switch object.
2. In the Maintenance working mode, select the CFM MA List tab.

3. To define CCM:
a. Select the MA from the list, and then click .

The Define CCM window opens.
b. Modify the settings in the CCM Definitions area, and then click Apply & Close to save the changes.

4. To perform CFM loopback maintenance:
a. Select an MA from the list, and then click .

The CFM Loopback Maintenance Operations window opens.

b. To view the MEP status, click .
In the CFM MA Status area, you can view the status of the local MEP and remote MEP.
c. In the Operation Definitions area, select Loopback.

d. Select the Local MEP and Destination MIP/MEP from the corresponding lists.
e. To select an external NE as destination, enter the MAC Address in the Select Destination area,
and click the icon.
f. Click Apply.
You can view the results in the Operation Results area.
5. To perform CFM linktrace maintenance:
a. Select an MA from the list, and click .

The CFM Loopback Maintenance Operations window opens.

b. To get the MEP status to view, click .
In the CFM MA Status area, you can view the status of the local MEP and remote MEP.
c. In the Operation Definitions area, select Link Trace.

d. Select the Local MEP and Destination MIP/MEP from the corresponding lists.
e. To select an external NE as destination, input the MAC Address in the Select Destination area,
and click the icon .
f. To start the link trace maintenance, click Start.

You can view the result in the Operation Results area.
g. Click Stop to stop the linktrace progress.

11.18 In-band MCC

In-band Management Control Channel (MCC) is supported on the ETY ports of Ethernet Overlay Cards. The
in-band MCC will be mainly used when the NE is connected by ETY link without any TDM link.
The typical in-band MCC network applications are as below:
 In-band MCC over MoE in MPLS network
 In-band MCC over PB ETY network
 Dual plane application: In-band MCC over data plane with DCC over TDM plane
Following figure is an example of network topology for dual plane application.
Figure 11-28: MCC&DCC network topology example
 In-band MCC Router Mode

One central router mode which can be shared by both in-band MCC and regular DCC. (NI: Network
Interface)
Figure 11-29: In-band MCC router mode

 In-band MCC packet format

Following shows the 802.1q tagged MCC packet format on MoE link or PB UNI link. (DA: Destination
MAC Address; SA: Source MAC Address)
Figure 11-30: 802.1q tagged MCC packet format on MoE link or PB UNI link
 DA/SA are same as the traffic packet on that MoE.

 The C-Tag is configurable by user.
Following shows the 802.1ad tagged MCC packet format on PB NNI ETY link.
Figure 11-31: 802.1ad tagged MCC packet format on PB NNI ETY link
 In-band MCC enabled on Management VLAN

Normally, management VLAN shall be used for pure PB application, based on L2 forwarding, MCC traffic
can be CPU off-loaded. Each management VSI is mapped to one NI(network interface), each NI has an
IP address.
 In-band MCC enabled on single PB port
Just like when enabled on an MoE port, in-band MCC can be enabled on a single PB port. It is mainly
used on the gateway PE when the MCC traffic is routed between the MPLS-TP network and PB DCN
network.
11.18.1 In-band MCC supported Cards

In-band MCC can be supported for the following cards in BG-64/NPT1200/NPT-1020/NPT-1021/ NPT-
1010/NPT-1050:
 For BG-64, DMXE_48_L2, DMXE_22_L2, DMGE_8_L2, DMGE_4_L2 cards support MCC.
 For NPT-1200, CSS100/CS320 (AMXE_2, DH cards), DMXE_48_L2, DMXE_22_L2, DMGE_8_L2,
DMGE_4_L2 cards support MCC.
 For NPT-1020/NPT-1021, MXC-1020/MXC-1021 supports MCC.
 For NPT-1010, MGE_8 supports MCC.
In-band MCC over PB ETY (UNI/E-NNI) is supported for all the above cards and products.
Management VLAN which includes PB UNI or LAG ports can also support MCC.

11.18.2 Configure In-band MCC

This section describes how to configure in-band MCC. The in-band MCC Network Interface can be added to
OSPF if required, which is described in OSPF management.
Following are the restrictions for enabling MCC in LCT-NPT:
 The member of a LAG cannot enable MCC.
 If MoE/PB Network Interface (NI) has been added to OSPF, then MCC cannot be disabled.
 Only MCC enabled MoE can enable GRE. Vice versa, if GRE is enabled, then MCC cannot be disabled.
From LCT-NPT v3.1:
 Unnumbered PPP interface for both DCC and GCC is supported.
 No need to configure the "borrowed IP address", unnumbered PPP will always borrow IP address
from loopback interface.
 Unnumbered for MCC IP interface is supported.
 No need to configure the "borrowed IP address", unnumbered MCC interface will always borrow
IP address from loopback interface.
 Management VLAN interface is always numbered.
 To support unnumbered MCC, a new attribute is configurable when MCC is enabled on the port:
Numbered/Unnumbered. Default is numbered.
NOTE: In-band MCC cannot be enabled when the NE connection mode is Ethernet Only.

To configure in-band MCC for an MoE port:

1. In the NE Shelf View window, in the left object tree, select a MoE port of an in-band MCC supported
card.
3. In the In-band MCC area, you can enable in-band MCC and configure the relevant parameters for it.
The in-band MCC is disabled by default.
4. Configure the parameters for the in-band MCC:
 Enable the in-band MCC on the MoE port;
 Set the interface as numbered or unumbered;
 If the interface is set as numbered, assign IP Address and Mask.
 If the interface is set as unumbered, the IP Address and Mask will use loopback IP/Mask.
 Set a C-VLAN if required;
 Set Network Interface MTU and the other attributes as required.

To configure in-band MCC for a PB ETY port:

1. In the BG-64 and NPT NE Shelf View window, in the left object tree, select a PB ETY port (with the port
type UNI or E-NNI) of an in-band MCC supported card.
3. In the In-band MCC area, you can enable in-band MCC and configure the relevant parameters for it.
The in-band MCC is disabled by default.
4. Configure the parameters for the in-band MCC:
 Enable the in-band MCC on the PB port;
 Set the interface as numbered or unumbered;
 If the interface is set as numbered, assign IP Address and Mask.
 If the interface is set as unumbered, the IP Address and Mask will use loopback IP/Mask.
 If the PB port is E-NNI, the VLAN (S-VLAN) must be selected, and this S-VLAN cannot be added to
other VSI. Untagged MCC is not supported for PB E-NNI port.
 Set the Network Interface MTU.
 Set Tx Rate Limit and Rx Rate Limit as required. Default is 4M (NPT except NPT-1010) or 1M (NPT-
1010) for single port MCC network interface. The Rate limit range and step of each MCC NI is:
256Kbps~4Mbps in a step of 256Kbps for all NPT products, and for 256Kbps~1Mbps in a step of
256Kbps for NPT-1010.

 The ARP for management VLAN and MCC enabled PB port is always enabled.
11.18.3 Configure management VLANs

The management VLAN is supported for the following cards:
 DMGE_4_L2
 DMGE_8_L2
 DMXE_22_L2
 DMXE_48_L2
 CS100
 CS320
 CS10
 CS50
 CS5
 CS100_1050
NOTE: Management VLAN cannot be created when the NE connection mode is Ethernet Only.
LCT-NPT supports only one management VLAN for one card.

To create a management VLAN:

1. In the NE Shelf View window, in the left object tree, select the Switch module of a management VLAN
supported card.
2. In the Services working mode, select the Management VLAN tab.

3. To create a management VLAN, on the toolbar, click .

The Create Management VLAN window opens.
4. Set the Name, VSI ID, S-VLAN, NMS VSI ID and Customer in the respective fields. The S-VLAN ID cannot
be the same with the S-VLAN ID in the VSI list.
5. Set the IP Address, IP Mask and Network Interface MTU in the corresponding fields.
6. Set Enable MAC Address Learning and V-FIB Quota as required.
7. Select one or more ETY ports in the Objects Selections area:
 All ETY PB ports/LAGs can be added to Management VLAN;
 Only Untagged UNI can be added to Management VLAN.
 To deselect a port, right-click the port.
8. Click Activate to create and activate the management VLAN.
If you click Save, the management VLAN is saved but not activated.

To use the management VLAN list:

1. To access the management VLAN list, select the NE in the left object tree, then select the Management
VLAN List tab under the Service working mode.
2. To activate a management VLAN, select a VSI in the list and click . Click to deactivate it.
3. To enable a management VLAN, select a VSI in the list and click . Click to disable it.

4. To Edit a management VLAN, select the management VLAN in the list and select on the toolbar.
The Edit Management VLAN window opens.
5. Modify the management VLAN as required, and click Apply to save the settings.
6. To view the details of a management VLAN, select the management VLAN and click .
The View Management VLAN window opens.
7. To delete the management VLAN, select the management VLAN in the list and on the toolbar, click
.
8. To delete all of the VSIs in the list, click the Select All button and then click . Click to
deselect all.
9. To upload the management VLAN, on the toolbar, on the toolbar, click .
10. To export the management VLAN as an XML file, on the toolbar, click .

To import a management VLAN from an XML file, on the toolbar, click .

11. Right-click a management VLAN, and then select vFIB List.
The vFIB List tab window opens.
12. To create a new vFIB entry, on the toolbar, click .

13. In the opened Create New Static vFIB Entry window, from the VSI ID dropdown list, select a
Management VLAN.

14. Set MAC and Port for the vFIB entry and click Apply to save.
You can view the created vFIB in the vFIB list.
You can also query VSI and Management VLAN in the Filter area.

15. To view the vFIB utilization, select the vFIB Utilization tab under the vFIB tab.
16. In the Filter area, you can selected VSI, User Label and Customer as required and click .
The Utilization percentage indicates the current vFIB/applicable vFIB Quota.
11.19 LSP over GRE

Label switched path (LSP) over Generic Routing Encapsulation (GRE) is to provide a solution for MPLS-TP
connectivity over 3rd party's L3VPN domain through MoE with GRE encapsulation.
Application scenarios:
 Connecting MPLS-TP PEs via L3VPN - by PtP MoE interface. Figure below shows MoE Section over GRE
application - PtP MoE interface.
Figure 11-32: MoE section over GRE application - P2P MoE interface

 Connecting MPLS-TP PEs via L3 VPN - by PtMP MoE interface. Figure below shows LSP over GRE
application – PtMP MoE interface.
Figure 11-33: LSP over GRE application – P2MP MoE interface
The frame formats for MPLS traffic and OAM packets are:
 MPLS over GRE as per RFC4023:
MPLS over GRE over IP encapsulation.
Figure 11-34: MPLS over GRE over IP encapsulation
 The GRE header as per RFC2784:

Figure 11-35: GRE header as per RFC2784
C=0; Reserved0=0; Ver=0; Protocol Type=0x8847.

Figure 11-36: LSP over GRE L3VPN solution – Protocol stack

11.19.1 LSP over GRE supported Cards

LSP over GRE with OAM is supported for following cards:
 DMGE_4_L2
 DMGE_8_L2
 DMXE_22_L2
 DMXE_48_L2
 MPOE_12G
 MGE_12
 MGE_8
 CS100
 CS320
 CPS50
 CS10
 CS100_1050

11.19.2 Enable GRE

To enable GRE:
1. In the BG-64/NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select an
MoE port of a GRE supported card.
3. You can enable the GRE attribute with the following restrictions:
 Only in-band MCC enabled MoE can enable GRE.
 If ESMC is enabled on GRE disabled MoE, the MoE port cannot be changed to GRE enabled.
 If Link OAM is enabled on GRE disabled MoE, the MoE port cannot be changed to GRE enabled.

4. When GRE is enabled and the Interface Type is PtP Interface, you can set the Peer IP, Destination IP and
Destination Mask as required for the GRE

11.20 CCN management

This section describes the main concepts of Customer Change Notification (CCN).
For MSTP dual-homing topology
Access networks that are dual homed on a BG VPLS network may run their own RSTP/MSTPs or may be
connected to the BG VPLS network with a PB that runs MSTP. MSTP topology change notifications stimulate
FDB flush in the ingress BG (BG1). However, egress BG of the service (BG4) does not perform flush as a result
of the topology change in PB. Change in FDB happens as a result of the aging process that takes 5 minutes.
It is important to flush customer MAC addresses in the remote BG upon the topology change in the PB in
order to avoid black holing of customer frames.
Figure 11-37: MSTP Dual-homed network
To address this issue, topology change must be detected at the ingress bridge of the VPLS network. Detection
of the topology change is a part of MSTP protocol and BPDU tunneling. Topology change is detected when
the bridges (BG1 and BG2) receive a topology change notification (TCN). On detection of the topology change,
the ingress bridge transmits a CCN, and upon receiving the CCN, the egress bridge flushes all the customer
MAC addresses.

In the QinQ H-VPLS network, The number of CCN domains (in the core and in the metro access rings) provides
adequate FDB flushes when the topology changes in the PBs.
Figure 11-38: CCN domains in Q-in-Q based H-VPLS
For ERP dual-homing topology

Figure 11-39: ERP Dual-homed network

To address this issue, topology change must be detected at the ingress bridge of the VPLS network. Detection
of the topology change (R-APS(SF)) is a part of the ERP protocol. Topology change is detected when ERP in
BG-PE1 and BG-PE2 receive an R-APS (SF) message. On detection of the topology change, the ingress bridge
transmits a CCN. Upon receiving the CCN, the egress bridge flushes all the customer MAC addresses.
11.20.1 CCN supported Cards

All the LSI and EZchip network processor (NP) cards can support CCN.
11.20.2 Set CCN enabled and forwarding

To set CCN enabled and CCN forwarding:
1. In the NE Shelf View window, in the left object tree, select the data card that supports CCN and then
the Switch module.
3. Set the Switching Mode as MPLS PE.

4. In the MPLS PE Configuration area, you can set the CCN Enabled and CCN Forwarding attributes as
required:
 CCN Enabled: If enabled, switch performs Forwarding Database (FDB) flush in response to
received CCN if CCN Source PE ID is in CCN Remote PE List.
 CCN Forwarding: If enabled, switch transmits CCN Messages with Forwarding bit set to 1,
otherwise Forwarding bit is set to 0.
11.20.3 View CCN tunnel list

You can view the tunnels in which CCN is enabled in the CCN tunnel list.
To view the CCN tunnel list:

1. In the NE Shelf View window, select the data card that supports CCN and then the Switch module.
2. In the Services working mode, select the CCN Tunnel List tab.
The CCN tunnel list is displayed.
11.21 Configure latency

Some data network application cannot work with large latency. There are large size of buffer in MPLS-TP
cards. The current WRED configuration for EZChip cards has more than 30ms latency for Green packets during
congestion, which is 3 times as that in MCS. For LSI cards, the WRED buffer for Green packets may be around
50ms. These buffer may be filled by a large burst and it may cause steady latency phenomena if the buffer is
keep filling.
To deal with this issue:
 The latency caused by WRED buffer should be configurable
 5~30ms with a step of 5ms, default is 30ms for EZchip cards;
 5~50ms with a step of 5ms, default is 50ms for LSI cards;
 Accuracy should be within 2ms for each card.
 The latency caused by EoS/MoT buffer should be keep small (sub 5ms)
 The buffer for EOS/MOT in ADM622 is very large, and it will introduce large latency. Moreover if
the EOS/MOT port is congested with low CoS traffic, high CoS traffic will have big latency as well.
The buffer size in EOS mapper should be reduced in ADM622 as well.

To configure latency:
1. In the NE Shelf View window, in the left object tree, select the Switch object of an EZchip or LSI card.
3. In the General area, configure the Queue Limit attribute as required.

4. Click Apply.
11.22 View available queue resources

For the EZchip cards in LCT-NPT, you can view the available queue resource attributes.

To view available queue resource:

1. In the NE Shelf View window, in the left object tree, select the Switch object of an EZchip card.
In the Available Queue Resource area, you can view the available queue resource attributes.
11.23 Configure port mirroring

Port mirroring is supported in all layer2 cards and NPT central PEs:
 Up to 2 port mirroring groups can be supported per PE, each group includes a source flow and a
destination port.
 The source flow can be either ingress traffic of a source port or egress traffic of a source port.
 For the versions before NPT V3.1, there are below restrictions on source port type and destination port
type for port mirroring:
 MPLS port(MoT/MoE) cannot be as source port
 Only ETY port can be as destination port
From NPT V3.1, above 2 restrictions are removed.
 There may have 4 bytes of internal header added for the source flows over MoT/EoS port, and these
source will be mirrored without stripping the internal header.

To configure port mirroring:

1. In the NE Shelf View window, in the left object tree, select the Switch module.
2. In the Maintenance working mode, select the Port Mirror tab.

4. To create the port mirroring, select the ports from the corresponding dropdown list, and click Create.
5. To remove a port mirroring, select it in the list, and click .

11.24 Configure switch OAM settings

To configure switch OAM settings:
1. In the NE Shelf View window, in the left object tree, select the Switch module.
2. In the Maintenance working mode, select the Tunnel OAM Setting tab.
3. Set the CV Interval and FDI Interval attributes from the corresponding dropdown lists, and click Apply
to save your settings.
4. To configure the OAM settings as default setting:
a. Click to display the settings to view.

b. Click Apply to save.

11.25 Configure port protection

The MPLS supports a protection mechanism called Fast ReRoute (FRR) that protects a tunnel against a link or
node failure 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-50 msec switching time. This 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 the 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 the 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 always in the case of the destination PE), attempts are made
to provide link protection. Thus, a tunnel may have node protection at some hops and link protection at
others.

To configure MPLS port protection:

1. In the NE Shelf View window, in the left object tree, select an MPLS card and then a MoT/MoE/10GE
MoE port.
The General tab opens.
3. Select the MPLS port protection switch, and click Apply to save your settings.

12 CES services management
For the CES services, there are two work modes: Standalone mode and Integration mode.
 Standalone mode
 When MSM card works on standalone mode, it means CES service is supported by MSM card
alone, including CESoETH and CESoIP service, and MSM card always interconnects with 3rd party
device directly through its ETY interface.
 Only the ETY port in front panel of MSM card is used.
 Integration mode
 CES service is implemented by MSM card together with L2 card.
12.1 Standalone mode: CES services management

There is no Central PE or L2 card involved in the CES service configuration in Standalone mode. The MSM
card works like a PE node, but it is just a simple PE. The CES packet is transmitted or received from 3rd party
device directly.
The following encapsulation mode are supported for CES over ETY application:
 CESoETH
 CES service is identified by the Destination MAC Address (DA), Source MAC Address (SA) and
Emulated Circuit Identifier (ECID), an optional VLAN ID can be configured.
 CESoIP
 CES service is identified by the IP address and UDP port, an optional VLAN ID can be configured.
 Usually default gateway IP address is necessary, default gateway MAC address is got by ARP.
Figure 12-1: CES over ETY application
The CES over ETY application can be in MEF network or IP network:

LCT-NPT® User Guide CES services management
 CESoETH is selected in MEF PSN network

 CESoIP is selected in IP network
Only one of the encapsulation can be used at the same time. CES over ETY functionality is implemented under
DMCES1_4 and DMCE1_32 cards.
12.1.1 Standalone mode: CES services workflow

VSI configuration for CES services in Standalone mode includes CES PB PtP and CESoIP services.
The CES PB PtP service can only be created in CESoETH encapsulation mode, and CESoIP service can only be
created in CESoIP encapsulation mode.
The procedure for creating CES PB PtP service contains the following steps:
 Define the Work Mode of the MSM card as Standalone.
 For the Switch module of the MSM card, set the Encapsulation mode as CESoETH.
 Configure VSI, set the VLAN ID and add an eETY port to the VSI.
 Create the VSI.
The procedure for creating CESoIP service contains the following steps:
 Define the Work Mode of the MSM card as Standalone.
 For the Switch module of the MSM card, set the Encapsulation mode as CESoIP.
 Set IP Address and Mask on eETY port.
 Configure VSI, set the Destination IP Address, Source/Destination UDP Port and then add an eETY port
to the VSI.
 Create the VSI.
12.1.2 Create CES PB PtP services

This section describes how to create a CES PB PtP service in an MSM card with Standalone work mode.

To create a CES PB PtP service:

1. In the NE Shelf View window, in the left object tree, select an MSM card.
2. In the Configuration working mode, select the Card Parameters tab.
a. Set the Work Mode of the MSM card as Standalone.

b. Enable or disable the MAC SA Check as required.
c. Click Apply.
3. In the left object tree, select the Switch object under the MSM card.

a. Set the Encapsulation Mode as CESoETH.

b. Set the Ethernet Network ID as required.
c. Click Apply.
5. In the left object tree, select the MSM card or the Switch object under the MSM card.


7. To create a VSI, on the toolbar, click .

8. To create a CES PB PtP service:

a. From the Service Type dropdown list, select CES PB PtP.
b. In the VSI Parameters area, set the other VSI parameters as required.
c. Set a VLAN ID for the CES PB PtP service.
d. Select a CES port and an eETY port from right area of the window.
e. Set the relevant parameters for the selected E1 port.
f. In the Family VPLS tab, set the Peer MAC Address as required.


9. To save the VSI, click Save.

You can view the saved VSI in the Recent Saved VSI tab, or you can click Activate to save and activate
the VSI.
10. To activate the saved VSI in the Recent Saved VSI tab, click Activate.
12.1.3 Create CESoIP services

This section describes how to create a CESoIP service in an MSM card with Standalone work mode.

To create a CESoIP service:

a. Set the Work Mode of the MSM card as Standalone.

b. Enable or disable the MAC SA Check as required.
c. Click Apply to save the settings.

3. In the left object tree, select the Switch object under the MSM card.
a. Set the Encapsulation Mode as CESoIP.

b. Set the Ethernet Network ID as required.
c. Click Apply. The settings are saved.

5. In the left object tree, select the MSM card or the Switch object under the MSM card.

7. To create a VSI, on the toolbar, click .

8. To create a CESoIP service:

a. From the Service Type dropdown list, select CESoIP.
b. In the VSI Parameters area, set the other VSI parameters as required.
c. In the CESoIP Parameters area, set the Destination IP Address and Source/Destination UDP Port
as required.

d. Select a CES port and an eETY port from right area of the window.
e. Set the relevant parameters for the selected E1 port.

9. To save the VSI, click Save.

You can view the saved VSI in the Recent Saved VSI tab. You can also click Activate to save and activate
the VSI.
10. To activate the saved VSI in the Recent Saved VSI tab, click Activate.
12.1.4 View CES service state

For CES timing, there are five clock recovery states: Normal, PMSM, CSM, Holdover, and FreeRun. PMSM and
CSM is the middle state between holdover and steady state (normal state).
 Normal: The clock recovery is entered to steady state.
 PMSM: Phase Measurement State Machine, only available in ACR.
 The state machine is entered to PMSM from holdover state once normal packet is received;
 The state machine is entered to PMSM from steady state once phase error above threshold.
 CSM: Convergence State Machine, only available in ACR.
 The state machine is entered to CSM from PMSM once service clock frequency is changing;
 The state machine is entered to steady state from CSM after the phase error lower than threshold.
 CSM will go to holdover state once packet loss is detected.

 Holdover: The clock recovery is entered to holdover state. Enter to holdover state from CSM or Normal
state if packet loss is detected.
 FreeRun: E1/DS1 clock is working at the nominal clock, no clock recovery is working from CES PW.
To view CES service state:

1. In the NE Shelf View window, in the left object tree, under a CES card, select an E1 port with CES service.
2. In the Services working mode, select the CES Service State tab.
12.1.5 Perform CESoETY maintenance

To perform CESoETY maintenance:
1. For an MSM card with Standalone work mode, ETY payload is supported, which is same to that of L2
card.
a. In the left object tree, select the MSM card with Standalone work mode. )
b. In the Maintenance working mode, select the ETY Payload tab.

c. Select the Refresh Data Dynamically checkbox if required and set the Refresh Interval second.
d. Click Start to refresh the data.
e. To refresh manually, on the toolbar, click .

2. For an MSM card with Standalone work mode, IP Ping and Traceroute is supported.
a. In the left object tree, select the eETY port under the MSM card with Standalone work mode.
b. In the Maintenance working mode, select the IP Ping and Tracert tab.
c. To start Tracert or Ping, select the Operation Type and set the IP Address as required and then
click .
d. To stop the operation, on the toolbar, click .
e. To clear the operation result, on the toolbar, click .

12.2 Integration mode: CES services management

This section describes the CES services in Integration mode in LCT-NPT.
CES is based on a PtP connection between two interworking functions (IWFs). Essentially, CES uses the
PSN/MPLS as an intermediate network (or virtual wire) between two TDM networks. It provides emulation
of TDM services, such as N x 64 kbit/s, T1, E1, T3, E3, OC-3, and OC-12, across a metropolitan Ethernet
network (MEN) or MPLS network.
Figure 12-2: Network reference model for CESoMPLS mode according to ITU_T Y.1413
The actual TDM circuit service is emulated between IWF through the MPLS network.
Figure 12-3: Network reference model for CESoETH mode according to MEF3
The actual TDM circuit service is emulated between IWFs through the MEN.
12.2.1 Integration mode: CES services workflow

VSI configuration for CES services in Integration mode includes CES PB PtP, CES PB MPtMP, and CESoMPLS
services.
CES PB PtP and CES PB MPtMP services can only be created in PB switching mode, and CESoMPLS service can
only be created in MPLS PE switching mode.
The procedure for creating CES PB PtP/CES PB MPtMP services contains the following steps:
 Define the Work Mode of the MSM card as Integration.
 In a specific L2 card, select an EoS interface as iEoS interface or an ETY interface as iETY interface.
 Configure EoS or ETY port in the L2 card as INNI interface.
 In the Create VCGs window, configure the VCG bandwidth for the EoS port(s).

 Configure E1 interface CES parameters. Set the Frame Mode of the E1 ports as Unframed (default
Unframed).
 Configure VSI, and add E1 interface to VSI.
 Create the VSI.
The procedure for creating CESoMPLS service contains the following steps:
 Define the Work Mode of the MSM card as Integration.
 In a specific L2 card, configure iEoS interface or iETY interface. Select an EoS interface as iEoS interface
or an ETY interface as iETY interface, which is used to connect to the MSM card.
 In the L2 card, configure the Switch Mode as MPLS PE mode, and set the other attributes of the Switch
block if necessary.
 Create the Exp Mapping Profile.
 Define MoE port for the GE port in the L2 card.
 Configure the attributes of the defined MoE interface. The attribute of Exp Map Profile cannot be
empty. The default is default_mapping_name.
 Configure E1 interface CES parameters. Set the Frame Mode of the E1 ports as Unframed (default
Unframed).
 Create required tunnels.
 Configure VSI, and add E1 interface to VSI.
 Create the VSI.
12.2.2 L2 cards working with MSM cards

In LCT-NPT, the following L2 cards can work with the MSM cards in Integration work mode:
 In BG-20, ME_2G_4F, MPS_2G_8F and MPOE_12G can work with DMCE1_32.
 In BG-30 with MCP30B, DMGE_4_L2, DMXE_22_L2 and MPOE_12G can work with DMCE1_32 and
DMCES1_4.
 In BG-64/NPT-1200, DMGE_4_L2, DMGE_8_L2, DMXE_48_L2, DMXE_22_L2, MPOE_12G and
CPTS100/CPS100 can work with DMCE1_32 and DMCES1_4.
 In NPT-1200, CPTS100/CPS100 can work with MSE1_16/EM_10E.
 In NPT-1020/NPT-1021, CS10/CS50 can work with DMCE1_32/DMCES1_4/MSE1_16/EM_10E.
 In NPT-1010, CS5 can work with TMSE1_8.

12.2.3 Define iEoS/iETY interfaces

EoS implements the Ethernet over SONET/SDH function. It provides both high-order and low-order virtual
concatenation to improve bandwidth efficiency, and implements link capacity adjust scheme to enable hitless
addition and removal of bandwidth. An internal EoS link between the MSM and L2 cards can be created.
Figure 12-4: Internal EoS link between MSM and L2 cards
To an internal EoS interface, the new conventions are:

 iEoS Link: Internal EoS connection between two IO cards in order to establish direct traffic path
between two cards (simulating an L1 connection).
 iEoS Interface: Internal EoS interface, a type of logical backplane interface, which is used for connecting
another card with the same interface. iEoS Link is a logical link between two iEoS interfaces.
One of the ETY interfaces in a specific L2 card can be selected as iETY interface.
DMCE1_32 only supports iEoS, while DMCES1_4 only supports iETY.
Once MSM card works on integration mode, iETY, iEoS, SGMII interface may be selected as CES traffic port.
In BG-MSPP:
 DMCE1_32 card can be associated to L2 card with iEOS port.
 DMCES1_4 card can be associated to L2 card with iETY port.
In NPT-1200:
 DMCE1_32 card can be associated to Central PE with SGMII or iEOS, and associated to L2 card with iETY
port.
 DMCES1_4 card can be associated to Central PE with SGMII, and associated to L2 card with iETY port.

To define an iEoS/iETY interface:

3. Configure the Work Mode of the MSM card as Integration and click Apply.
4. In the left object tree, right-click a specific L2 card and then select Attach CES Cards. (The Auto-
Negotiations between the MSM card and the L2 card port should be the same.)
The Associate CES Cards window opens.
5. From the Attaching Connection dropdown list, select iEoS or iETY as required.

6. Select a Designated CES Port for the selected iEoS/iETY.


8. To view the general information of the iEoS/iETY port, select the iEoS/iETY port in the left object tree,
then select the General tab under the Configuration working mode.

12.2.4 Create CES PB PtP services

This section describes how to create a CES PtP service.
Before creating a CES PB PtP service, assign both specific L2 and MSM cards in the NE; see L2 cards working
with MSM cards.
CES PB PtP and CES PB MPtMP services can only be created in PB switching mode, and CESoMPLS service can
only be created in MPLS PE switching mode.

1. In the NE Shelf View window, define the iEoS/iETY interface in a specific L2 card, as described in Define
iEoS/iETY interface.
2. To configure EoS or ETY port in the L2 card as INNI interface, in the left object tree, select the L2 card,
and then select the GE ETY Ports/10 GE ETY Ports/EoS Ports tab under the Configuration working
mode.
3. Set the ETY/EoS port types as I-NNI, and click Apply to save the settings.

4. To create VCG:
a. Right-click the L2 card, and then select Create VCG.
b. In the VCG Attribute window, set the Map Level and Bandwidth for the EoS port as required.

5. To set E1 port attribute for the MSM card:

a. Select the E1 port object in the left object tree, and then select the General tab under the
b. In the Frame Mode field, select Unframed in the dropdown list.


6. To create a VSI:
a. In the left object tree, select the Switch module of the L2 card.
b. Select the VSI List tab under the Services working mode.

c. From the toolbar, click the Create VSI button .

d. To create CES PB PtP service, from the Service Type dropdown list, select CES PB PtP.
e. Select the VSI State by selecting the radio button (default Enabled).
f. In the Path field for the VSI, select the path (can be set as Only Primary or Primary & Secondary).
g. Enter the VSI ID, NMS VSI ID, User Label, and Customer values in the left areas of the window.
You can also input additional description into the VSI Description field.

h. For the CES PB PtP VSI with the path Primary & Secondary, the Hold Off Time field can be
configured.
i. In the right Objects Selections area, select one or more E1s as a CES port and one I-NNI port in
the relevant list. For the VSI with the path Primary & Secondary, set the path of I-NNI ports by
selecting the Set as Primary Path or Set as Secondary Path checkbox. Right-click an object to
deselect.
j. Click + to expand the CES Port area.

k. Configure the CES Port General, RTP Header, Jitter Butter, Timing, Family VPLS in the
corresponding tab window.
l. Set the S-VLAN ID for the Primary and Secondary port. Each S-VLAN ID must be unique.

m. For the selected PB ports, select a QB in the corresponding Queue Block dropdown list.

n. To create and activate the CES PB PtP VSI, click Activate. If you click Save, the CES PB PtP is saved
but not activated. To activate it, select the Recent Saved VSIs tab.
o. In this window, select the VSI you want to activate, and click Activate.

To configure a switch command:

1. In the VSI list, right-click a CES PB PtP service with the Primary & Secondary path and then select Switch
Command.
The Switch Command window opens.
2. Perform the following operations by selecting the relevant option:

 Force Switch to Working
 Manual Switch to Working
 Release

12.2.5 Create CES PB MPtMP services

To create CES PB MPtMP service:
1. Before creating CES PB MPtMP service, perform the same configurations from Step 1 to Step 4 in CES
PB PtP service.
2. To create a CES PB MPtMP VSI, in the left object tree, select the Switch module of the L2 card, and then
select the VSI List tab under the Services working mode.

3. In the toolbar, click the Create VSI button .

4. From the Service Type dropdown list, select CES PB MPtMP.

5. Select the VSI State by selecting the radio button (default Enabled).
6. In the left areas of the window, set the VSI ID, NMS VSI ID, User Label, Customer, S-VLAN, and BSC
Threshold values as required.
The vFIB Quota can only be set for a CES PB MPtMP VSI. 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. (Optional) Select the Enable MAC Address Learning checkbox. You can also write additional text in the
VSI Description field.

8. In the right Objects Selections area, select one or more E1s as CES ports and I-NNI ports in the relevant
list. Right-click an object to deselect.
9. Click + to expand the E1 area.

10. Configure the CES Port General, RTP Header, Jitter Butter, Timing, Family VPLS in the corresponding
tab window.

11. For the selected PB port(s), select a QB in the corresponding Queue Block dropdown list.
12. To create and activate the CES PB MPtMP VSI, click Activate.
13. If you click Save, the CES PB MPtMP is saved but not activated. To activate it:
The CES PB MPtMP VSI is activated.

12.2.6 Create CESoMPLS services

To create a CESoMPLS services:
1. In the NE Shelf View window, define the iEoS/iETY interface in a specific L2 card, as described in Define
iEoS/iETY interfaces.
2. To configure the attributes of the Switch block, in the NE Shelf View window, select the Switch object
in the left object tree, and then select the General tab under the Configuration working mode.
3. Set MPLS PE mode as the switching mode. Set the other parameters as required, and click Apply to
save the settings.
To create Exp mapping profiles, select the NE in the left object tree, and select Profile and then Exp Mapping
Profile. See Create tunnel XCs.
4. To define the MoE port:
a. Right-click the L2 card in the left object tree, and from the shortcut menu, select Define MoE Port.
)
b. Set the GE port as MoE port by selecting the corresponding radio button, and click Apply to save
the settings.


5. To configure the attributes of the MoE port:

a. Select the MoE port in the left object tree, and then select the General tab under the
b. Set the parameters as required. The attribute of Exp Map Profile cannot be empty (default
default_mapping_name).
c. Click Apply to save the settings.

6. Set E1 port attribute for the MSM card:

a. Select the E1 port object in the left object tree, and then select the General tab under the
b. In the Frame Mode field, select Unframed in the dropdown list (default Unframed), and click
Apply to save your setting.
7. To create the tunnel XC, in the NE Shelf View window, select the Switch module of the L2 card in the
left object tree.

8. Select the Tunnel XC List tab under the Services working mode.
For details about creating tunnel XCs, see Creating Tunnel XCs.

9. To create the CESoMPLS VSI:

a. Select the VSI List tab under the Services working mode.

b. In the toolbar, click the Create VSI button .

c. To create CESoMPLS service, from the Service Type dropdown list, select CESoMPLS.
d. Select the VSI State by selecting the radio button (default Enabled).
e. In the left areas of the window, enter the VSI ID, NMS VSI ID, User Label, and Customer values as
required.
f. Set the Tunnel Mode as E-LSP or L-LSP (default E-LSP).
When the Tunnel Mode is set as L-LSP, the VC Label Scheme can be set as Single VC Label or Same
Incoming Label.

g. In the right Objects Selections area, select one E1 as CES port and one remote PE in the relevant
list. Right-click an object to deselect.
h. Click + to expand the E1 area.

i. Configure the CES Port General, RTP Header, Jitter Butter, and Timing in the corresponding tab
window.
j. For the selected Remote PE, select a head tunnel XC that can reach the Remote PE, and set the
InVCLabel and OutVCLabel in the relevant field.

k. To create and activate the CESoMPLS VSI, select the Recent Saved VSIs tab, and click Activate.
If you click Save, the CESoMPLS VSI is saved but not activated.

12.2.7 View CES service state

To view CES service state:
1. In the NE Shelf View window, in the left object tree, under a CES card, select an E1 port with CES service.
2. In the Services working mode, select the CES Service State tab.

12.3 CEP services management

Circuit Emulation over Packet (CEP) provides emulation of TDM services. it transports SONET/SDH circuits
through a packet-oriented network, such as STM-1/OC-3 and STM-4/OC-12 across a Metropolitan Ethernet
Network or MPLS Network.
The CEP is based on a point-to-point connection between two Interworking Functions (IWFs). Essentially, CEP
uses the PSN/MPLS as an intermediate network between two TDM networks.
Figure 12-5: CEP Network Refer Model
CEP uses the common CES VSIs.

 CESoMPLS VSI for CEP interface, per CEP service per VSI;
 CES PB PtP VSI for CEP interface, many CEP service can be added to one VSI;
 CES PB MPtMP VSI for CEP interface, many CEP service can be added to one VSI;
 For one VSI, doesn't support to add CES interface or CEP interface from different CES card;
 To CEP VSI, any CEP interface from one CES card can be added to the same VSI.
CEP supports:
 CEP mode
 CEPoMPLS
 CEPoETH
 CEP VSI
 CESoMPLS with CEP interface
 CES PB PtP VSI with CEP interface
 CES PB MPtMP VSI with CEP interface
 SPE Type
 VC-3 (future)
 VC-4, VC-4-4c

 STS-1, STS-3c, STS-12c

 CEP Pointer Management
 Jitter buffer and Payload time
 DBA support
CEP is supported in the card:
 MSC_2_8
 MS1_4
12.3.1 Create CEP services

To create CEP services:
1. In the NPT or IP/MPLS NE Shelf View window, in the left object tree, select the CS module. Then in the
Services working mode, select the VSI List tab.

2. To create a CEP service, click .

3. From the Service Type dropdown list, select a CES service type: CES PB PtP/CES PB MPtMP/CESoMPLS.
4. Set the other parameters for the CEP service, which is same with the CES services configuration.
5. In the right Objects Selections area, select SPE(S) and I-NNI port(s) for the CEP serice.
6. In the Port List:
a. Click + to expand the selected SPE and configure the CES Port General, RTP Header, Jitter Butter,
Family VPLS (not support for CESoMPLS) in the corresponding tab window.
b. Configure the parameters of the selected I-NNI port(s).
7. To create and activate the service, click Activate.
If you click Save, the service is saved but not activated. You can activate it in the Recent Saved VSIs tab
or in the VSI list.

12.3.2 View CEP service state

To view CEP service state:
1. In the NE Shelf View window, in the left object tree, under a CES card, select an SEP with CES service.
2. In the Services working mode, select the CEP Service State tab.

13 Services management in IP/MPLS
In the IP/MPLS NEs (NPT-1800/NPT-1200i), the switching mode of CS module can be set as PB or IP/MPLS
PE.
When the switching mode is set as PB, you can create following services:
 PB PtP
 MPtMP
 CES PB PtP
 CES PB MPtMP
 ERPS VSI
 VRF
When the switching mode is set as IP/MPLS PE, you can create MPLS TP tunnels and then following services
can be created:
 PB PtP
 MPLS PtP
 MPtMP
 CES PB PtP
 CES PB MPtMP
 CESoMPLS
 ERPS VSI
 MS-PW
 VRF
13.1 IP/MPLS services workflow

The procedure of creating PB services in IP/MPLS NEs includes the following steps:
4. Assign DH cards in the NE (for CES PB services, also need to assign MSC_2_8);
5. Activate the ports of the DH cards/MSC_2_8;
6. Set the Interface Type of ETY ports in the DH cards as I-NNI/E-NNI/VLAN-Tagged;
7. In the Create VSI window, create required PB services.
The procedure of creating MPLS services in IP/MPLS NEs includes the following steps:
8. Assign DH cards in the NE (for CES MPLS services, also need to assign MSC_2_8);
9. Activate the ports of the DH cards/MSC_2_8;
10. Define the Switching Mode of CS module as IP/MPLS PE;
11. Set the Interface Type of required ETY ports in the DH cards as VLAN-Tagged/Unchannelized;
12. Create MPLS family LIFs and other LIFs as required;

LCT-NPT® User Guide Services management in IP/MPLS
13. Create MPLS TP tunnels;

14. In the Create VSI window, create required MPLS services.
13.2 Manage MPLS TP tunnels

IP-MPLS (the classic MPLS) tunnels are the infrastructure for transporting traffic of services in a pre-defined
route. There are static configured tunnels and dynamically configured tunnels. The static configured tunnels
are MPLS-TP tunnels.
Dynamically configured (signaled) tunnels may be plain MPLS tunnels, TE tunnels or TP tunnels. Signaling of
tunnels may be done by Labels Distribution Protocol (LDP) or by Resource Reservation Protocol (RSVP). LDP
signal plain MPLS tunnels while RSVP may signal plain, TE or TP MPLS tunnels. LDP protocol realizes cross-
connections between incoming labeled traffic into outgoing labeled at the right direction towards its
destination. LDP relies on the Routing Information Base (RIB) to supply the information about routes towards
destinations.
MPLS-TP Tunnel Information Models
 Tunnel Object
A tunnel object contains one LSP object (for tunnel with no linear protection and for unidirectional tunnel)
or two LSP objects (for tunnel with linear protection). A tunnel with linear protection contains a protection
group object (called protection domain in NPT and TPG in XDM).
 LSP Object
An LSP object associated with unidirectional tunnel contains one MPLS XC object. An LSP object, associated
with bidirectional tunnel, contains two MPLS XC objects. BFD may be associated with bidirectional LSP. An
LSP associated with linear protected tunnel must have associated BFD object.
 Protection Group
A protection group should be associated with a linear protected tunnel object to contain all linear protection
attributes and status.
 Tunnel Id uniqueness
Tunnel-id must be unique in NE scope. Note that the embedded application treats one bidirectional tunnel
as two unidirectional tunnels at opposite directions. The embedded application associates these two tunnels
to one bidirectional tunnel by assigning the same tunnel-id for both. Imposed limitation to any management
layer is taking into account the above fact when configuring bidirectional tunnel. It means that assigned
tunnel-id for a new bidirectional tunnel should be free at A-end and Z-end NEs of the tunnel.

Figure 13-1: IP/MPLS MPLS-TP Bidirectional Tunnel
Figure 13-2: IP/MPLS MPLS-TP Protected Tunnel
13.2.1 Create MPLS TP tunnels
15. Assign DH cards in the NE;

16. Activate the ports of the DH cards;
17. Define the Switching Mode of CS1T as IP/MPLS PE;
18. Set the Interface Type of required ETY ports in the DH cards as VLAN-Tagged/Unchannelized;
19. Create MPLS family LIFs and other LIFs as required.

To create MPLS TP tunnels:

2. In the Configuration working mode, click the General tab.
3. In the Switching Mode field, select the IP/MPLS PE option.

4. Configure other parameters as required and then click Apply to save your settings.

5. In the Services working mode, click the MPLS TP Tunnel List tab.

6. To create an MPLS TP tunnel, click .

The Create MPLS TP Tunnel window opens.
7. To configure the MPLS TP tunnel:

a. In the MPLS TP Tunnel Parameters area, set the following attributes:
 Tunnel Type: Select Bidirectional or Unidirectional.
 Tunnel Role: Select Head/Tail or Transit.
 Protection Type: Select Unprotected or Linear Protection.
 Protection Role: Main.
 OAM CoS: Set a value of OAM CoS as required. The default value is 7.
 LDI Enabled: Enable or disable the LDI. This attribute is only available when creating
bidirectional transit tunnels.
 DiffServ Enabled: Enable or disable the DiffServ (default is disabled).
 A-Z/Z-A: Configure the MPLS In/Out Label, PIR settings and CoS Bandwidth as required.
 BFD: Enable or disable the BFD (default is disabled). If BFD is enabled, set the parameters
for BFD as required.

b. In the MPLS Tunnel Information area, set the following attributes:

 Tunnel Name: Set a name for the tunnel.
 Tunnel ID: Set a tunnel ID for the tunnel.
 Tunnel Number: Set a unique tunnel number for the tunnel.
 LSP ID: The LSP ID is fixed and cannot be configured.
 NMS Tunnel ID: Set the NMS Tunnel ID as required. The default value is 1.
 MID: Set the MID as required. The default value is 1.
 (Optional) NMS Tunnel Name: Set a name for the NMS tunnel.
 (Optional) Customer: Select a customer.
 (Optional) Tunnel Description: Set description for the tunnel.
8. In Port list, select a LIF.
9. In the Destination/Source PE area, set a required PE either by Router ID, Network ID and PE ID, or select
from the PE list.
10. Click Add. The MPLS TP LSP is added in the Recent Added MPLS TP LSPs list.
11. Click either:
 Activate: To save and activate the tunnel.
 Save: To save the tunnel.
13.2.2 Manage the MPLS TP tunnel list

You can perform the following management actions in the MPLS TP tunnel list:
 Filter the tunnel list
 Activate/Deactivate tunnels
 View/Edit/Delete a tunnel
 Upload tunnels
 Export/Import tunnels
 Add/Remove MPLS TP tunnel protection
 View MPLS TP tunnel protection status
 View LDI source list
 Perform MPLS-TP ping and trace
This section mainly describes how to:
 Add/Remove MPLS TP tunnel protection
 View MPLS TP tunnel protection status
 View LDI source list
 Perform MPLS-TP ping and trace

For other details about managing the tunnel list, refer to Using the Tunnel XC List.
To access the MPLS TP tunnel list:

2. In the Services working mode, click the MPLS TP Tunnel List tab.
13.2.2.1 Change MPLS TP tunnel protection

You can add MPLS TP tunnel protection for the following tunnels:
 Unprotected Bidirectional Head/Tail tunnels
 Unprotected Bidirectional Transit tunnels
 Linear Protection Bidirectional Transit tunnels

To add MPLS TP tunnel protection:

1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, select a Bidirectional Head/Tail or
Transit tunnel.

2. Click .
The Add MPLS TP Tunnel Protection window opens.
3. To add MPLS TP tunnel protection:

a. In the Protection Role dropdown list, select Protection.
b. (Optional) In the A-Z/Z-A/BFD area, configure the MPLS In/Out Labels, CoS Bandwidth, PIR and
BFD settings.
c. In the Port list, select a LIF.

d. Click Add. The Protection LSP is saved in the Recent Added MPLS TP LSPs list.

4. To configure parameters of the protection group, click the Protection Group tab.

6. Click Apply.
The MPLS TP tunnel protection is added.
To remove MPLS TP tunnel protection:

1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, select an MPLS TP tunnel with
protection added.
2. Click .
3. In the confirmation window, click Yes to confirm removing.
4. For the Linear Protection Bidirectional Transit tunnels with protection added, an additional
confirmation window opens. Select a BD LSP to remove, and then click Yes.
The protection is removed.

13.2.2.2 View MPLS TP tunnel protection status

In IP/MPLS NEs, for the Bidirectional Head/Tail Linear Protection tunnels, you can view the MPLS TP tunnel
protection status.
To view MPLS TP tunnel protection status:

1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, select a Bidirectional Head/Tail Linear
Protection tunnel, then click .
The View MPLS TP Tunnel window opens.
2. In the right area of the window, click the Protection Group tab.
3. Click .
In the Protection Group Status area, you can view the tunnel protection status.

13.2.2.3 View the LDI source list

To view the LDI source list:
1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, right-click a Bidirectional tunnel and
then select LDI Source List.
2. In the LDI Source List tab, click to retrieve the list to view.

13.2.2.4 View fault management status

To view fault management status:
1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, right-click a Bidirectional tunnel and
then select Fault Management Statistics.
2. In the Fault Management Status tab, click to retrieve the list to view.

13.2.2.5 Run MPLS TP Ping and Trace Route for LSP

To run MPLS TP ping and trace route for LSP:
1. In the IP/MPLS NE Shelf View window, in the MPLS TP tunnel list, right-click a Bidirectional Head/Tail
tunnel and then select MPLS-TP LSP Ping & TraceRoute.
2. Configure the attributes as described below:

 Mode: Ping or Trace Route.
 Protection Role: Main or Protection.
 Target FEC Prefix: Pointer to profile with BFD session parameters.
 CoS: CoS of transmitted Echo packet within LSP.
 TTL: Time-To-Live.
 Ping mode: TTL for Echo Request.
 Trace Route mode: Maximum TTL value for Echo Request.
 Relay Mode: IPv4, Router Alert or Application Level Control (ALCC). For static LSP/PW, only ALCC
is supported.
 Repeat: Number of consequent LSP Ping (iterations). Relevant for LSP Ping mode only.
 Interval: Interval between LSP Ping iterations (not relevant for TR mode).
 Timeout: Value for timeout timer.
 Validate Reverse Path: Specifies for the receiver of Echo Request packet whether to perform
reverse path validation when Echo Reply packet is sent or not. Relevant for static LSP/PW only.

3. Set the refresh interval as required.
4. To start MPLS-TP ping or trace route, click .

The ping or trace route output is displayed in the bottom frame.
5. To stop the ping or trace route, click .
13.2.2.6 Run LDP LSP Ping and Trace Route

To run LDP LSP ping and trace:
2. In the Maintenance working mode, click the LDP LSP Ping & TraceRoute tab.

 Select the Destination Router ID and Subnet Mask.
 CoS: CoS of transmitted Echo packet within LSP.

 Reply Mode: IPv4, Router Alert, or Application Level Control (ALCC). For static LSP/PW, only ALCC
is supported.
 Repeat: Number of consequent LSP Ping (iterations). Relevant for LSP Ping mode only.
 Interval: Interval between LSP Ping iterations (not relevant for TR mode).
5. To start the LDP LSP ping or trace route, click .

6. To stop the LDP LSP ping or trace route, click .
13.3 Manage the VSI

This section explains how to create VSIs and manage PWs.
13.3.1 Create VSIs

This section describes how to create services in IP/MPLS NEs.
13.3.1.1 Create a PB PtP service

To create a PB PtP service:
2. In the Services working mode, click the VSI List tab.
3. Click .

4. In the VSI Parameters area:

a. In the Service Type dropdown list, select PB PtP.
b. Set the Admin Status as enabled or disabled.
c. Set VSI Name, VPN ID and NMS Service ID as required.
d. (Optional) Set User Label, Customer and Description as required.
5. In the PB PtP Parameters area set S-VLAN as enabled or disabled.
When it is enabled, set the S-VLAN value as required.
6. From the right port list, select two ports to add into the service.

7. Configure the attributes of the added ports as required.
8. Click either:
 Activate: To save and activate the service.
 Save: To save the service.

13.3.1.2 Create an MPLS PtP service

To create an MPLS PtP service:

3. Click .

a. In the Service Type dropdown list, select MPLS PtP.
5. In the MPLS PtP Parameters area:
a. Set S-VLAN as enabled or disabled (default is enabled). When it is enabled, set the S-VLAN value
as required.
b. Set the MTU value as required.
c. Set the PW Type as Ethernet or Ethernet Tagged.
6. From the right area of the window, select a port and a remote T-PE (with tunnel) to add to the service.
7. In the Port List tab, configure the attributes of the added port as required.

8. In the PW List tab, set the attributes of the remote T-PE and PW parameters as required.
9. Click either:
Flow Aware Transport (FAT) support in IP/MPLS

For MPLS PtP, MPtMP, and MPLS BPDU Tunneling VSIs, the FAT attribute is supported for primary and
secondary dynamic PWs when Is-MSPW is set as false. The FAT configuration can be applied to SS-PW for all
types of Ethernet services only (VPLS, VPWS, BPDU).
 To enable the imposition and disposition of flow labels for a pseudowire for virtual private L2 services.
Applicable for dynamic PW only.
Both Static - NE handle the flow label in the pseudowire packet, irrespective of the information exchanged in
the signaling plane

To configure the FAT attribute:

1. In an IP/MPLS NE Shelf View window, in the Create VSI window, in the Service Type dropdown list,
select MPLS PtP, MPtMP or MPLS BPDU Tunneling.
2. In the PW List tab, when the Is-MSPW is set as false the Setup Method attribute is set as tLDP, the FAT
can be set as Disabe or Both Static.
 To enable the imposition and disposition of flow labels for a pseudowire for virtual private L2
services. Applicable for dynamic PW only.
 Both Static: NE handle the flow label in the pseudowire packet, irrespective of the information
exchanged in the signaling plane.

13.3.1.3 Create an MPtMP service

To create an MPtMP service:

3. Click . The Create VSI window opens.

 In the Service Type dropdown list, select MPtMP.
 Set the Admin Status as enabled or disabled.
 Set VSI Name, VPN ID and NMS Service ID as required.
 (Optional) Set User Label, Customer and Description as required.
5. In the MPtMP Parameters area:
 Set S-VLAN as enabled or disabled (default is enabled). When it is enabled, set the S-VLAN value
as required.
 Enable or disable the MAC Address Learning attribute (default is enabled). When it is enabled,
select a vFIB Quota Profile from the dropdown list.
 Enable or disable E-Tree.
 Set the MTU value as required.
 Set the PW Type as Ethernet or Ethernet Tagged.
 Enable or disable DAI Enable. Default is disabled.
 If DAI Enable is enabled, the creation of DHCP snooping Agent and ARP filtering module and
entities required for statistics collection within a VSI is supported.
 If DAI Enable is disabled, the deletion of DHCP snooping Agent and ARP filtering module and
entities required for statistics collection is supported.
 Enable or disable Is IGMP-aware. If the IGMP-aware attribute is enabled, you can configure the
parameters as shown in the following figure.

The IGMP-aware attributes are:

 Admin State: It can be set as enabled or disabled. The default is disabled.
 IGMP Proxy Mode: It can be set as ASM or SSM.
 IGMP Version:
 If the IGMP proxy mode is set as ASM, the IGMP version can be set as V2 or V3.
 If the IGMP proxy mode is set as SSM, the IGMP version can be set as V3-SSM.
 Graceful Restart Enable: It can be set as enabled or disabled.
 Graceful Restart Time: The range is 10~3600s.
 Query Interval: The range is 1~2550s.
 Max Query Response Time: The range is 0.1~255s.
 ASM Max Group Membership Records: The range is 1~8000.
 SSM Max Group Membership Records: The range is 1~8000.
 Robustness Variable: The range is 2~7.
 Last Member Query Internal: The range is 0.1~25.5s.
 SSM Range: The range is 224.0.2.0~239.255.255.255.
6. From the right area of the window, select port(s) and remote T-PE(s) (with tunnel) to add to the service.
7. In the Port List tab, configure the attributes of the added ports as required.

8. In the PW List tab, set the attributes of the remote T-PEs and PW parameters as required.
9. Click either:
Manage the manual binding table

LCT-NPT verifies whether the new configured IP address is associated with a MAC address. If associated, the
system will reject the configuration. If you want to overwrite the existing association, he can clear the specific
entry using the clear specific record maintenance command.
Router does not get its IP address from DHCP. It must be connected to a trusted interface or its IP-MAC need
to be manually associated.

To manage the manual binding table:

1. In the MPLS/IP NE Shelf View window, in the Create MPtMP VSI window, select the Manual Binding
Table tab.
2. To add available port(s):
a. Click .
b. Select the available port(s).

c. Click Apply to add.
3. Set the IP Address and MAC Address for the added port.
4. Click Apply.
The settings is saved.

View the VSI binding table
To view the VSI binding table:

1. In the IP/MPLS NE Shelf View window, in the VSI list, right-click an MPtMP VSI with manual binding
table configured, then from the shortcut menu, select View VSI Binding Table.
The View VSI Binding Table window opens.
3. To clear selected records, click .
4. To all dynamic records, click .
View dropped ARP messages

LCT-NPT supports retrieval of dropped ARP messages from dropped ARP messages database, filtered
according VSI, VSI interface, event time range, IP address, and MAC address.

To view dropped ARP messages:

1. In the IP/MPLS NE Shelf View window, in the VSI list, right-click an MPtMP VSI, then from the shortcut
menu, select Dropped ARP Messages.
The Dropped ARP Messages window opens.

Manage IGMP interface configuraion
To manage IGMP interface configuration:

1. In the MPLS/IP NE Shelf View window, in the Edit MPtMP VSI window, select the IGMP Interface
Configuration tab.
2. To add available port(s) and remote T-PE(s):
a. Click .
b. Select the available port(s)/T-PE(s).


3. Configure the parameters in the relevant field.
4. Click Apply.
Manage IGMP static database
Before you start:

 Configure the IGMP interface configuration before you mange the IGMP static database.

To manage IGMP static database:

1. In the MPLS/IP NE Shelf View window, in the Edit MPtMP VSI window, select the Manual IGMP Static
Database tab.
2. To add available port(s) and remote T-PE(s):
a. Click .
b. Select the available port(s) and remote T-PE(s).


3. Set the IP Address and MAC Address for the added port.
4. Click Apply.

13.3.1.4 Create a CES PB PtP service


3. Click .

a. In the Service Type dropdown list, select CES PB PtP.
5. In the CES PB PtP Parameters area, set the S-VLAN value as required.
6. From the right area of the window, select CES port(s) and an I-NNI port(s) to add to the service.

7. In the Port List tab, configure the attributes of the added ports as required. For the selected E1 ports,
in the Family VPLS tab, the Peer MAC Address must be configured.
8. Click either:

13.3.1.5 Create a CES PB MPtMP service

To create a CES PB MPtMP service:

3. Click .

a. In the Service Type dropdown list, select CES PB MPtMP.
5. In the CES PB MPtMP Parameters area:
a. Set the S-VLAN value as required.
b. Enable or disable the MAC Address Learning attribute (default is enabled). When it is enabled,
select a vFIB Quota Profile from the dropdown list.
6. From the right area of the window, select CES port(s) and an I-NNI port(s) to add to the service.

7. In the Port List tab, configure the attributes of the added ports as required. For the selected E1 ports,
in the Family VPLS tab, the Peer MAC Address must be configured.
8. Click either:
13.3.1.6 Create a CESoMPLS service

Before creating a CESoMPLS service, make sure that MPLS TP tunnels are created.

To create a CESoMPLS service:


3. Click .

a. In the Service Type dropdown list, select CESoMPLS.
5. From the right area of the window, select a CES port and a remote T-PE (with tunnel) to add to the
service.
6. In the Port List tab, configure the attributes of the added port as required.
7. In the PW List tab, set the attributes of the remote T-PE and PW parameters as required.

tLDP setup method.
8. Click either:
13.3.1.7 Create an ERPS VSI

This section describes how to create ERPS VSIs in IP/MPLS.
For details about configuring ERPS parameters, refer to Ethernet Ring Protection Switching.

To create an ERPS VSI:


3. Click .

a. In the Service Type dropdown list, select ERPS VSI.
5. In the ERPS Parameters area:
a. Set ERP Type as PB Ring or MPLS Ring.
b. Set the ERP Node Role as Ring Node or RPL Owner. For MPLS rings, only Ring Node is available.
c. (Optional) Set the ERP Instance ID, ERP Rang Name, S_VLAN, and other parameters as required.

6. For a PB Ring ERPS:

a. In the Objects Selections area, select two I-NNI ports to add to the VSI.
b. Set the Port Role for each selected port.

 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, one of the selected ports can be set as RPL Port
and the other as Ring Port from the Port Role dropdown list.

7. For an MPLS Ring ERPS VSI:

a. Select an I-NNI port and a remote T-PE to add to the service.
b. In the Port List tab, configure the attributes of the added port as required.
c. In the PW List tab, set the attributes of the remote T-PE and PW parameters as required.
8. Click either:
13.3.1.8 Create an MS-PW VSI

Before creating an MS-PW service, make sure that MPLS TP tunnels are created.

To create an MS-PW VSI:


3. Click .

a. In the Service Type dropdown list, select MS-PW.
5. In the MS PW Parameters area:
a. Set the MTU value as required.
b. Set the PW Type as Ethernet or Ethernet Tagged.
6. From the Peer PEs list, select one or more peer PEs (with tunnels) to add to the service.
7. In the PW List tab, set the attributes of the peer PEs as required.
tLDP setup method.

8. Click either:
13.3.1.9 Create a bridge domain service

To create a Bridge Domain service:


4. To create Bridge Domain:

a. From the Service Type dropdown list, select Bridge Domain.
b. Select the Admin State (default is Enabled). When disabled, all policers block their traffic,
including NNI ports. When enabled, all policers enable traffic flow.
This field is editable with no constraints.
c. Set the Admin Status as enabled or disabled.
d. Set VSI Name, VPN ID and NMS Service ID as required.
e. (Optional) Set User Label, Customer and Description as required.
f. Set the S-VLAN, MTU, and PW Type as required.
g. 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).
h. (Optional) You can also add a description in the VSI Description field.
i. In the Objects Selections area, select the ports and set the IRB address and mask.
the toolbar click .
5. Click Activate to create and activate the Bridge Domain service.
If you click Save, the Bridge Domain is saved, but is not activated.

To activate it later:
b. Select the VSI you want to activate in this window, and click Activate.
The Bridge Domain service is then activated.
13.3.2 View PW status

For the services with PW, you can view the PW status.
To view PW status and statistics:

1. In the IP/MPLS NE Shelf View window, in the VSI list, right-click a VSI with PW and then View PW Status.
The View PW Status window opens.
2. Select remote T-PE and PW role from the Primary Remote T-PE and PW Role dropdown list.

13.3.3 Run PW ping and trace route

To run PW ping and trace route:
1. In the IP/MPLS NE Shelf View window, in the Services working mode, select the VSI List tab.
2. Right-click an existing VSI name, and then select PW Ping & TraceRoute.
The PW TP Ping & TraceRoute window opens.

 Select the Remote T-PE.
 Select the PW Role (e.g. Primary).
 CoS: CoS of transmitted Echo packet within PW.
 Reply Mode: IPv4, Router Alert or Application Level Control (ALCC). For static PW, only ALCC is
supported.
 Interval: Interval between PW Ping iterations.
 Validate Reverse Path: Specifies for the receiver of Echo Request packet whether to perform
reverse path validation when Echo Reply packet is sent or not. Relevant for static PW only.

5. To start PW ping or trace route, click .

6. To stop the PW ping or trace route, click .
13.4 Manage the VRF

In L3VPN, routes of different VPNs are identified by VRFs managed by PE. VRF is local representative of the
VPN in PE. A PE creates and maintains a separate VRF for each VPN at a connected site. Each VRF contains
the VPN membership and routing rules of the corresponding site. If a user at a site belongs to multiple VPNs
at the same time, the multiple VRFs are defined containing information about all the VPNs.
For independency and security of VPN data, each VRF on a PE maintains a relatively independent routing
table and a separate label forwarding information base (LFIB). VRF information contains these items: the
LFIB, IP routing table, interfaces bound to the VRF, and administration information of the VRF. The
administration information of the VRF includes the route distinguisher (RD), route filtering policy, and
member interface list.
You can create the VRF with L3 LIFs, loopback interfaces and Pseudo Wire Headend Termination (PHT).
PHT is a technology that allows termination of access pseudo wires (PWs) into a Layer 3 (VRF or global)
domain or into a Layer 2 domain. PWs provide an easy and scalable mechanism for tunneling customer traffic
into a common IP/MPLS network infrastructure. PHT allows customers to provision features such as QOS on
a per PHT interface basis, on a service Provider Edge (PE) router.
Figure 13-3: Network Diagram for Pseudo Wire Headend Termination
 New numbered L3 interface defined based on PHT

 PHT interface associated with VRF
 Multiple PHT interfaces may be provisioned for single VRF
 Head End PW may be part of VPWS or VPLS in the L2VPN domain

13.4.1 Create the VRF

To create the VRF:
1. In the IP/MPLS NE Shelf View window, in the left object tree, click the CS module, then in the Service
working mode, select the VRF List tab.

2. To create a VRF, click .

The Create VRF window opens.
3. In left area of the window, configure the following parameters:

 Name: The name of this VRF. This name must be unique within the containing NE.
 Autonomous System: Set the AS as Auto or Manual. The default is Auto.
 Router ID: Router ID for the VRF.
 Description: The description of this VRF.
 Route Distinguisher: The route distinguisher for this VRF.
 Maximum Routes: Denotes maximum number of routes that this VRF is configured to hold. Value
of zero means that there is no configuration limit.
 High Route Threshold: Denotes high-level water mark for the number of routes which this VRF
may hold as percentage of the maximum routes number for this VRF. A value of zero or value of
Maximum Routes as zero indicates that there is no threshold.
 QoS Mapping Profile: Select a QoS mapping profile.
 Routing Policy: Add routing policies to the VRF.
 Route Targets: Add routing targets to the VRF.
4. To create a VRF with L3 LIFs:
a. In the right area of the window, select the L3 LIFs tab.
b. From the port list, select Vlan-Tagged port(s) or unchannelized port(s).
c. Configure the parameters for the selected port(s).

d. To create the VRF, click Apply.

5. To create a VRF with loopback interfaces:
a. In the right area of the window, select the Loopback Interfaces tab.
b. Click "+" to add loopback interfaces to the VRF.

c. Configure the parameters for the added loopback interfaces.

6. To create a VRF with PHT:

a. In the right area of the window, select the PHT tab.
b. Click "+" to add PHT LIF(s) to the VRF.

c. Configure the parameters for the added PHT LIF(s).

13.4.2 View routing instances status

To view routing instances status:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the CS module, then in the Services
2. Select the VRF in the list, then click .

The View Routing Instances Status window opens.

13.4.3 View VRF status

To view VRF status:

2. Right-click a VRF, then from the shortcut menu, select View VRF Status.
The View VRF Status window open.

13.4.4 View VRF interfaces status

To view VRF interfaces status:
2. Right-click a VRF, then from the shortcut menu, select View VRF Interfaces Status.
The View VRF Interfaces Status window open.

13.4.5 View VRF forwarding table

To view VRF forwarding table:
 In the IP/MPLS NE Shelf View window, in the left object tree, select the CS module. Then in the
Configuration working mode, select IP Routing > Forwarding Table.

13.4.6 View ARP table

To view ARP table:
2. Right-click a VRF, then from the shortcut menu, select View ARP Table.
The View ARP Table window open.
3. In the LIF Type field, select a LIF type:

 L3 LIF
 PHT LIF
 All
4. In the LIF Name dropdown list, select a LIF.
6. To clear all VRF dynamic ARP, click .
7. To clear all LIF dynamic ARP, click .

13.4.7 View VRF LIF statistics

To view VRF LIF statistics:
 In the Display area, select the VRF LIF object.
2. Click .


13.4.8 Run MPLS PHT ping and trace route

To run MPLS PHT ping and trace route:
1. In the IP/MPLS NE Shelf View window, in the Services working mode, select the VRF List tab.
2. Right-click a VRF with PHT configuraion, then from the shortcut menu, select MPLS PHT Ping &
TraceRoute.
The MPLS PHT Ping & TraceRoute window opens.
3. Configure the attributes in the relevant field.

5. To start MPLS PHT ping or trace route, click .

6. To stop the MPLS PHT ping or trace route, click .

14 Cross connections management
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 XC subsystem enables you to cross connect traffic on equipment. NEs feature an advanced Add/Drop
Multiplexer (ADM) architecture.
This chapter describes the procedure for setting up XCs. It contains the following sections:
 Create XC
 Manage the XC list
 Configure SNCP attributes
 Export and import XC files
14.1 Concatenation support

In LCT-NPT, the VC-4-4c/VC-4-16c supporting in MSPP/NPT can be described as follows:
 BG-64/NPT-1200
 VC-4-4c/VC-4-16c – full support (including XC and SNCP, PM, Alarm, Maintenance)
 VC-4-64c – XC only
 BG-30
 VC-4-4c XC – full support (including XC and SNCP, PM, Alarm, Maintenance)
 VC-4-16c – XC only. SNCP can be configured and automatic switch is OK; but SNCP lockout/force
switch is not supported, Path overhead/PM/alarm is not supported.
NOTE: VC-4-16c SNCP is officially not supported in BG-30.

LCT-NPT® User Guide Cross connections management
14.2 Create XC
This section describes how to create XCs for MSPP/NPT NEs.
14.2.1 Create server XC

To create a server XC:
1. In the NE Shelf View window, in the left object tree, select the NE. In the Services working mode, select
the XC List tab.
2. On the toolbar, click the Create XC icon .

3. In the Create XC window, from the XC Type dropdown list, set the XC type as Server.
4. Select the values of Customer, Rate, XC Template, and Number of XCs from the relevant fields.
5. (Optional) Select the Create Bundle checkbox.

6. From the corresponding timeslot lists, select a Source Timeslot and a Sink Timeslot.
7. To save the XC to the Recent Saved XCs area, click Save.

8. To activate the XC, click Activate All.
9. To activate the XC immediately, click Activate.

14.2.2 Create Service XC

To create a service XC:
1. In the NE Shelf View window, in the left object tree, select the NE. In the Services working mode, select
the XC List tab.

3. In the Create XC window, from the XC Type dropdown list, set the XC type as Service.
4. Select the values of Customer, Rate, XC Template, and Number of XCs from the relevant fields.



14.2.3 Create Tunnel XC

To create a tunnel XC, which is the data XC, see Services management in MSPP/NPT in the LCT-NPT Service
Management Guide.
14.2.4 Create OH XC
To create an OH XC:
1. In the NE Shelf View window, in the left object tree, select the NE, and in the Services working mode,
select the OH XC List tab.

3. In the Create OH XC window, in the XC Parameters area, set the direction type by selecting
Bidirectional or Unidirectional.

4. Select a Start Timeslot and an End Timeslot from the corresponding list.


14.2.5 Create DCC XC

To create a DCC XC:
1. In the NE Shelf View window, in the left object tree, select the NE, and in the Services working mode,
select the DCC XC List tab.

3. In the Create DCC XC window, in the XC Parameters area, select Bidirectional. (For DCC XC, only
bidirectional XC is supported.)

4. From the corresponding timeslot lists, select a Start Timeslot and an End Timeslot.

14.2.6 Create PCM XC

This section describes how to create PCM XCs, including the SM10, SM_10E and EM_10E XCs.

14.2.6.1 Create SM10 XC

To create an SM10 XC:
1. In a BG-40 NE Shelf View window, in the left object tree, select the SM10 card, and in the Services
working mode, select the PCM XC List tab.

3. IN the Create PCM XC window, in the XC Parameters area, from the Rate dropdown list, select the rate
of the XC:
 64K
 2M
4. In the Direction field, set the XC direction by selecting one of the following:
 Bidirectional
 Unidirectional
 Broadcast
5. (Optional) Select the Bundle checkbox.



14.2.6.2 Create SM_10E XC

To create an SM_10E XC:
1. In a BG-20/BG-30/BG-64/NPT-1200/NPT-1020 NE Shelf View window, in the left object tree, select the
SM_10E card, and then in the Services working mode, select the PCM XC List tab.

3. In the PCM XC Create window, in the XC Parameters area, from the Rate dropdown list, select the rate
of the XC:
 64K
 2M
 Bidirectional
 Unidirectional
 Broadcast



14.2.6.3 Create EM_10E XC

To create an EM_10E XC:
1. In the NPT-1200/NPT-1020/NPT-1021 NE Shelf View window, in the left object tree, select the EM_10E
card, and then in the Services working mode, select the PCM XC List tab.

3. In the Create PCM XC window, in the XC Parameters area, from the Rate dropdown list, select the rate
of the XC:
 64K
 2M
 Bidirectional
 Unidirectional
 Broadcast


14.2.7 Create OTN XC

Only Service XC type is supported for OTN XC in MXP10.

To create an OTN XC:

1. In the BG-64/NPT-1200/NPT1020/NPT-1050 NE Shelf View window, in the left object tree, select the
MXP10 card, and in the Services working mode, select the OTN XC List tab.

3. In the Create DCC XC window, select the values of Rate, XC Template, and Number of XCs from the
relevant fields.

5. Set Customer and XC Name as required.

In the MXP10 Muxponder mode, to add ODU timeslot for ODU2 module, right-click the ODU2 and from
the shortcut menu, select Add ODU0.
7. To edit the TS list, right-click an ODU module and from the shortcut menu, click Edit.
The Edit TS window opens.
The TS number you can select decided by the ODU type:

 ODU0: select 1 TS
 ODU1: select 2 TS
 ODUF-FC400: select 4 TS

 ODUF-SDI3G: select 3 TS
8. Select the Source Timeslot and Sink Timeslot from the corresponding lists.

11. To activate the XC, click Activate All. You can view the created XCs in the OTN XC List as shown below.
14.3 Manage the XC List

You can perform the following management functions in the XC list:
 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:

a. To expand the Filter area, click +, as shown in the following figure.
b. Select the relevant elements in the area, and click to filter.

3. To activate an XC, in the XC list, select the XC you want to activate, and on the toolbar click the Activate
XC icon .
4. To deactivate an XC, in the XC list, select the XC you want to deactivate, and on the toolbar click the
Deactivate XC icon .
5. To activate all the XCs in the NE equipment, click the Activate All icon .
6. To deactivate all the XCs in the NE equipment, click the Deactivate All icon .
7. To perform activating increment of the XCs, on the toolbar click the Activate Increment icon .
8. To edit a XC:
a. Select the XC you want to edit, and on the toolbar click the Edit XC icon .
b. In the XC Edit window, modify the information of the XC, and then click Save/Activate.

9. To view details of an XC, in the list, select the XC, and on the toolbar click the View XC icon .
10. To view XC details, in the XC View window, select a XC in the list, then on the toolbar, click .
You can view the details of the selected XC at the bottom of the window.
11. To upload XCs:
a. On the toolbar click the Upload XCs icon .

b. In the XC Upload window, click Upload. The status bar shows the consistency status between the
NE and the DB. If the NE and the DB are inconsistent, select the Compare Result tab to display
the inconsistency results.
c. Click Overwrite to overwrite the DB with the NE data.
12. To delete an XC, in the list select the XC you want delete, and on the toolbar click .
13. To export XCs:
a. Select the XCs you want to export, and on the toolbar click .
b. Select a folder to save the file, enter the name of the file, and click Save.

14.4 Configure SNCP Attributes

To configure SNCP attributes:
1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1050 NE Shelf View window, in the left
object tree, select the NE, and then in the Configuration working mode, select the NE Settings tab.
2. In the SNCP Default Setting area, you can set the following attributes:
 Wait-to-restore Time: Set the wait-to-restore time by selecting a numeric value. The default is
300s.
 Default Operation Mode: Revertive or non-revertive. This attribute defines the operation mode
(revertive or non-revertive) of new SNCP trails. The default is non-revertive.
 Default SNCP Monitoring: SNCP/I or SNCP/N. This attribute defines the SNC monitoring scheme
of new SNCP trails. The default is SNCP/N.
 LP-TIM Detection for SNCP/N: It can be enabled/disabled per RS and HP (VC-4, VC-4-XC). When
LP-TIM detection for SNCP/N is disabled, LP-TIM defect will not be the trigger of SNCP/N
protection in SDH port.

3. In the TTI and TSL tab, you can view and configure the TIM detection settings.
4. To obtain the SNCP attribute of the selected object, on the toolbar, click .
5. To send the SNCP attribute displayed in the list to the NE equipment, click Apply. When the SNCP
attribute is successfully sent, it is saved to the LCT-NPT DB.
NOTE: Only new created SNCP XC will be affected by SNCP default setting. Existing SNCP XC
attributes will not be affected when SNCP default setting changes.

To define SNCP attributes:

1. In the NE Shelf View window, in the Services working mode, select the SNCP tab.
2. From the respective dropdown lists, set the attributes of Revertive, Monitor Type, and Hold Off Time.
3. Select an SNCP in the list and right-click. From the shortcut menu, you can perform the following
maintenance operations:
 Release

14.5 Configure OTN SNCP settings

An ODUk cross connection from client to line can be protected by SNCP. The following figure illustrates an
example in which the OCH and ODU2 trails are unprotected while the ODU1 trail is protected via the SNCP.
Figure 14-1: ODU1 protected by SNCP between two MXP10

To configure OTN SNCP settings:

1. To configure NE OTN SNCP settings, in the NE Shelf View window, in the left object tree, select the NE.
Then in the Configuration working mode, select the NE Settings tab.
At the bottom of the window, you can set OTN SNCP settings as required.

2. To configure SNCP attributes, in the left object tree, select the MXP10 card. Then in the Services
working mode, select the SNCP tab.
3. To switch to Protection/Main, right-click the SNCP XC. From the shortcut menu, select one of teh
following maintenance operations as required.
 Get State from NE
 Release
14.6 Export and import XC Files

You can export a trail as an XML file and import XC XML files to the LCT-NPT.
14.6.1 Export XCs

This section describes how to export XCs in the LCT-NPT.

To export XCs:
1. In the main topology view, select Services, Export, and then Export SDH XCs/DCC XCs/OH XCs/PCM
XCs/Tunnel XCs.
The XC Export window opens.
2. Select the XCs you want to export. On the toolbar click to select all the XCs in the list.
3. On the toolbar click .

4. Select a folder to save the file, enter the file name, and click Save.
14.6.2 Import XC XML files

This section describes how to import XC XML files to the LCT-NPT.

To import XCs:
1. In the main topology view, select Services, Import, and then Import SDH XCs/DCC XCs/OH XCs/PCM
XCs/Tunnel XCs.
2. To open a file, on the toolbar click .

3. Select a file from the disk and click Open.
4. Select the XC in the list that you want to import, and on the toolbar click the Import icon .

15 Work with protection
This chapter describes how to use the LCT-NPT to configure protection schemes for NEs.
The workflow for performing protection operations includes:
 Work with TP
 Work with MSP 1+1
 Work with Data Card IOP
 Work with OTN Port IOP
 Work with STP and MSTP
 MS Shared Protection Ring (MS-SPRing)
15.1 Work with TP

Tributary Protection is supported in the BG-30 NE in the LCT-NPT, and is one type of equipment protection
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 scheme, the protection must be associated with the
relevant tributary cards, meaning the protecting and the protected cards. In the LCT-NPT, 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. This means that TP can be
performed for a traffic-carrying card without removing existing traffic.
 Associate the protecting card and protected cards with a proper TP card.
Three types of TP cards defined in the LCT-NPT can be managed: TP21_2, TPS1_1, and TP63_1.
Table 15-1: BG-30 tributary PG options

TP type Protection Protection card Associated TP Protected Applicable system
scheme card interfaces
Protected Protecting
21 x E1 1:2 2 x PME1_21 PME1_21 TP21_2 42 x E1 All (All means any ADM rate
with XIO30-1/4/16 and
SMQ1&4)
1:1 PME1_21 PME1_21 TP21_2 21 x E1 All
63 x E1 1:1 PE1_63 PE1_63 TP63_1 63 x E1 All
PE1_63 3 x PME1_21 TP63_1 63 x E1 All
1 x STM-1e 1:1 XIO30-1 XIO30-1 TPS1_1 1 x STM-1e ADM-1/4
XIO30-4 XIO30-4 TPS1_1 1 x STM-1e ADM-1/4

LCT-NPT® User Guide Work with protection

4 x STM-1e 1:1 XIO30Q_1&4 XIO30Q_1&4 TPS1_1 4 x STM-1e 4 x ADM-1/4
SMQ1&4 SMQ1&4 TPS1_1 4 x STM-1e ADM-16

4 x ADM-1/4
3 x E3/DS-3 1:1 PM345_3 PM345_3 TPS1_1 3 x E3/DS-3 All
P345_3E P345_3E TPS1_1 3 x E3/DS-3 All
Table 15-2: BG-64/NPT-1200 tributary PG options

63 x E1 1:1 PE1_63 PE1_63 TP63_1 63 x E1 All
4 x STM-1e 1:1 S1_4 S1_4 TPS1_1 4 x STM-1e All
3 x E3/DS-3 1:1 P345_3E P345_3E TPS1_1 3 x E3/DS-3 All
4 x STM-1e 1:1 S1_4 S1_4 TPS1_1 4 x STM-1e All
3 x E3/DS-3 1:1 P345_3E P345_3E TPS1_1 3 x E3/DS-3 All
15.1.1 Manage TP
Depending on the TP configuration, a maximum of two TP cards can be inserted in one BG-30E platform.
15.1.1.1 Manage TP21_2

As an expansion card of the BG-30E, the TP21_2 card can be assigned to any of the Eslots.
To perform slot assignment for the TP21_2:

1. In the BG-30 NE Shelf View window, in the left object tree, right-click the NE and select Slot Assignment.
2. Select the BG-30E checkbox in the lower left corner.
3. Assign two or three PME1_21 cards in the BG-30B platform's Tslots by right-clicking a Tslot and selecting
PME1_21 in the shortcut menu.
4. Right-click any Eslot in the BG-30E platform and select TP21_2 in the shortcut menu.
5. 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, in the left object tree, select
the TP21_2 card. In the Configuration working mode, select the PG Setting tab.
2. Configure the attributes as follows:
 From the Tributary PG Type dropdown list, select a tributary PG type. (For the TP21_2, you can
only select PME1_21.)
 In the Switch Mode dropdown list, select Not Revertive or Revertive (default Not Revertive).
 If you set Revertive switch mode, the WTR Time area is available. Set the wait-to-restore (WTR)
time by selecting a numeric value.
 Set the protecting and protected cards 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 platform, set the
Protected Card 2 #.
3. To save your settings, click Create.
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, to select which is to be monitored in the PG, click .
6. Click the relevant button, and then click Apply.
7. To delete the PG, on the toolbar, click .

15.1.1.2 Manage TPS1_1

As an expansion card of the BG-30E/BG-64E/NPT-1200E, the TPS1_1 card can be assigned to any of the Eslots.
To perform slot assignment for TPS1_1:

1. In the BG-30/BG-64/NPT-1200 NE Shelf View window, in the left object tree, right-click the NE and
select Slot Assignment.
3. In the BG-30B platform, 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 shortcut menu.
Or, you can assign two PM345_3 cards in any two TSlots.
4. Right-click any Eslot in the BG-30E platform, and in the shortcut menu, select TPS1_1.
5. To save the assignment, click Apply, and to close the Slot Assignment window, click Close.
To manage TPS1_1:
1. Double-click the assigned BG-30E/BG-64E/NPT-1200 NE. In the opened NE Shelf View window, in the
left object tree, select the TPS1_1 card. In the Configuration working mode, select the PG Setting tab.
2. Configure the following attributes:
 From the Tributary PG Type dropdown list, select a tributary PG type.
 If you set the Revertive switch mode, the WTR Time area is available. Set the WTR time by
selecting a numeric value.
 Set the protecting card and the protected card in the respective fields. The fields should not be
set with the same selections.

15.1.1.3 Manage TP63_1

As an expansion card of the BG-30E/BG-64E/NPT-1200, the TP63_1 card can only be assigned to ESlot3.
To perform slot assignment for TP63_1:

3. Set the protection cards according to TP group options described in Manage TP.
4. In the BG-30E platform, right-click ES 3, and in the shortcut menu, select TP63_1.
5. To save the assignment, click Apply, and to close the Slot Assignment window, click Close.

To manage TP63_1:
1. Double-click the assigned BG-30E NE. In the opened NE Shelf View window, in the left object tree, select
the TP63_1 card. In the Configuration working mode, select the PG Setting tab.
2. Configure the following attributes:
 From the Tributary PG Type dropdown list, select a tributary PG type.
 If you set the Revertive switch mode, the WTR Time area is available. Set the WTR time by
selecting a numeric value.
 Set the protecting and protected cards in the respective fields. The fields should not be set with
the same selections.

15.1.2 TPG Maintenance

To perform TPG maintenance:
1. In the BG-30 NE Shelf View window, in the left object tree, select the TP card, and then select the TPG
Maintenance tab in the Maintenance working mode.
2. Set the Switch Mode for all the cards, as follows:

 Release: Clear current maintenance operation.
 Lock out: Protection switch from protected to protecting card will not happen in any case.
 Force switch: Switches traffic from selected protected card to protecting card, whether protecting
card is operational or not.
 Manual switch: Takes effect only when protecting card is good (is a very safe operation).
3. To save your settings, click Apply in the corresponding areas.

15.2 Work with MSP 1+1

The LCT-NPT supports both unidirectional and bidirectional MSP Linear 1+1. The PG must comprise two STM-
N interfaces with the same rate.
To create a PG, select the main port and the protection ports either in the same card or in different cards (it
is recommended to 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 STM-1:
 XIO30-1
 SMQ1&4 (ports configured to STM-1)
 SMD1B
 S1_4
 MSP 1+1 for STM-4:
 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
15.2.1 Manage MSP 1+1

To manage the PGs:
1. In the NE Shelf View window, in the object tree, select the NE. In the Configuration working mode,
select the MSP-Linear tab.
2. To create a PG, on the toolbar, click .

The Create PG window opens.
3. In the Create PG window, in the Protocol Mode field, select Unidirectional or Bidirectional.
4. In the Main and Protection area, click to expand the cards. Then select a main port and a protection
port.
5. To create the PG, click Apply. If the PG creation is successful, the green icons adjacent to the ports turn
gray.

6. Close the Create PG window. To retrieve the information and view the PG list, on the toolbar, click
.
7. To overwrite the data to the database, on the toolbar, click .

8. To delete a PG, select the PG you want to delete, and on the toolbar, click .
9. To clear the PGs in the list, on the toolbar, click .
15.2.2 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, in the Configuration working mode, select the MSP-Linear tab.
2. Select a PG in the list, and right-click. Select the MSP 1+1 maintenance operation from the shortcut
menu. For unidirectional MSP 1+1, you can:
 Delete PG
 Release

15.3 Work with Data Card IOP

Electrical ETY ports can be protected in IOP with a new TP card, the TPEH8_1.
The BG MSPP L2 Data IOP topology is illustrated in the following figure.
Figure 15-1: BG MSPP L2 Data IOP topology
EoS ports switch in the TDM matrix.

ETY ports:
 Optical ports: Use "Y" fiber, no TP card needed.
 Electrical ports: Use TP card, switch over is done in relays.
15.3.1 Data Card IOP supported cards

Data Card IOP is only supported in the DMGE_2_L2, DMGE_4_L2, DMGE_8_L2, DMXE_48_L2 and
DMXE_22_L2 card.
The details of the Data Card IOP options for each card are described in the following table.
Table 15-3: Data Card IOP Options

TP Type Protection Protection card Associated TP Protected interfaces Applicable system
scheme card
Data IOP 1:1 DMGE_2_L2 DMGE_2_L2 Y fiber 2 x GbE optical BG-30/BG-64/NPT-1200
DMGE_4_L2 DMGE_4_L2 Y fiber 4 x GbE optical BG-30/BG-64/NPT-1200
TPEH8_1 4 x GbE optical
DMGE_8_L2 DMGE_8_L2 Y fiber 8 x GbE optical BG-64/NPT-1200
TPEH8_1 8 x GbE optical
DMXE_48_L2 DMXE_48_L2 Y fiber 8 x GbE optical + BG-64/NPT-1200

4 x 10GE optical
TPEH8_1 8 x GbE copper
DMXE_22_L2 DMXE_22_L2 Y fiber 2 x GbE optical + BG-30/BG-64/NPT-1200

2 x 10GE optical
TPEH8_1 2 x GbE copper

NOTE: When the DMGE_8_L2 port is working with 1000BaseX type and Auto-Negotiation
enabled, and the card is switched from protected to protecting, the traffic will be down. The
solution is to set the port to Disable and then to Enable. There is no problem when the
DMGE_8_L2 port is working with 1000BaseX type and Auto-Negotiation disabled, and the card
is switched from protected to protecting.
15.3.2 Create a Data Card IOP

Before creating Data Card IOP:
1. Define the ETY port type of the data card:
a. In the NE Shelf View window, in the left object tree, select the data card you want to define. )
b. For DMGE_2_L2/DMGE_4_L2/DMGE_8_L2, in the Configuration working mode, select the ETY

Ports tab.

The port type can be defined as Optical or Copper:

 Optical: 1000Base-X, 100Base-FX.
 Copper: 10/100/1000Base-T, 1000Base-T, 10/100Base-T.
c. For DMXE_48_L2/DMXE_22_L2, to configure the GE ETY ports, in the Configuration working
mode, select the GE ETY Ports tab.

To configure the 10 GE ETY ports, in the Configuration working mode, select the 10 GE ETY Ports
tab.
All the 10 GE ports are optical ports.

To create data card IOP:

1. In the object tree, select the NE. In the Configuration working mode, select the Data Card IOP tab.

2. To create a PG, on the toolbar, click .
3. In the Create Data Card IOP window, in the Select Protected Card and Select Protecting Card areas,
select a protected port and a protecting port.
4. To configure the attributes:
a. Set the Switch Mode as Not Revertive or Revertive (default Not Revertive).
b. Set the WTR Time (only in Revertive switch mode). The range is 0~720s (default 300s).
c. Set the Associated TP Card. In the case of pure optical ports, the Associated TP Card can be set
as None. For the copper ports or mix IOP, select TPEH8_1 from the dropdown list.
One TPEH8_1 can support up to two IOP PGs. The TPEH8_1 has two groups of relays - Group 1
and Group 2. Each group has four ports and can be controlled separately to select four ports from
either protecting card or protected card.
d. In the ETY port protection & mapping area, set the Protection type as Unprotected or Protected.
e. The Media Type is read only and can be Copper or Optical (decided by the PHY type set in Step
1).
f. Set the Associated TP Card in the ETY port protection & mapping area (available only when the
port is Copper and Protected).
g. Set the TP Port (available only when the port is Copper and Protected):
 If TP Card Group1 is selected, the TP Port option can be set as Group1 port1~4 or
Unspecified.

 If TP Card Group2 is selected, the TP Port option can be set as Group2 Port1~4 or
Unspecified.
 If TP Card Group1 and Group2 both are selected, the TP Port option can be set as Group1
Port1~4, Group2 Port1~4 and Unspecified.
5. To create the PG for optical ports, click Apply. If the process is successful, the green icons adjacent to
the ports turn gray.
15.3.3 Manage Data Card IOP

To manage PGs in the PG list:
1. Select the Configuration working mode and then the Data Card IOP tab to display the data PG list.
2. To edit a PG:
a. In the list, select a PG, and click .

b. In the Edit Data Card IOP window, edit the Switch Mode and WTR Time as required, and to save
your changes, click Apply.
3. To view details of a PG, select the PG in the list, and click .

The View Data Card IOP window opens, displaying the TP Operation Status.
4. To delete a PG, select the PG you want to delete, and on click .

NOTE: After an IOP PG is created successfully for two Layer 2 cards, wait a few minutes until a
protecting card becomes operational before starting any configuration on the protected card.
15.3.4 Alarm/PM Behaviors in IOP PG

Check alarms and PM of Layer 2 cards in case of IOP
IOP is equipment protection, when IOP is created with two layer 2 cards (such as DMGE_4_L2, DMGE_8_L2,
DMXE_22_L2 or DMXE_48_L2) – one protected card and one protecting card, the alarms and PM are handled
differently according to MO types:
 Equipment alarms
 Equipment alarms are handled independently per card and can be checked separately for each
card in the PG, such as card alarms (card-out, type-mismatch, BIT-Fail, Card-Ctrl-Fail, Temp-High,
etc.) and SFP/transceiver alarms (SFP-Out, SFP-ID-Fail, SFP-Rx-LOS, SFP TCAs, etc.);
 You can check LOS alarm of each ETY port in both cards by examining SFP-Rx-LOS alarms on each
card, so that you can check if Y fiber is connected correctly or not.
 Traffic alarms
 All traffic alarms of transmission objects are reported to protected card only, please check alarms
on protected card when checking the service alarming status;
 The traffic alarms on protected card actually reflect the alarms of the currently-active card, the
active card may be the protected card or protecting card, depending on the PG switch status;
 In some case, if you want to check traffic alarm status of the standby card, please view the
unreported alarms of the protecting card. The invisible (unreported) alarms on protecting card
actually reflect the traffic alarms of standby card, which include the EoS/MoT alarms but L2 alarms
are excluded.
 PM
 PM of transmission objects are available on protected card only;
 The PM counters of the service on protected card represent the PM of the service on currently-
active card.
15.3.5 Data Card IOP maintenance operations

You can perform maintenance operations on the created PGs.
To perform Data Card IOP maintenance operations:

1. In the NE Shelf View window, in the left object tree, select the NE, and in the Configuration working
mode, select the Data Card IOP tab.
2. In the list, right-click a PG.

From the shortcut menu, perform the following maintenance operations:

 Edit
 View
 Delete
 Protected Maintenance:
 Release
 Force Switch
 Manual Switch
 Lock Out
 Protecting Maintenance:
 Release
 Force Switch
 Manual Switch
 Lock Out
 IOP Trigger

15.3.6 Link Trigger for IOP

The BG Product Line data cards DMGE_4_L2/DMGE_8_L2/DMXE_48_L2 and DMXE_22_L2 cards support
Enhanced IOP (eIOP) functionality, with switchover triggered by link failures (LOS) in addition to the standard
node failure triggers. Adding LOS as an IOP trigger enhances IOP functionality, freeing up a port on each
participating DMXE card for carrying additional traffic. This is explained in the following example.
The following figure illustrates two DMXE/DMGE cards used in a network gateway node, between a PB/MPLS
network cloud and the customer equipment. The DMXE/DMGE cards are associated for IOP protection. The
network configuration is similar to that of the figure illustrating traditional.
Figure 15-2: eIOP protection example
With traditional Fast IOP, a link failure between DMXE/DMGE #1 and the router would result in traffic loss,
since DMXE/DMGE #2 remains designated as standby. This means that the router would not be able to find
any route available for traffic. To prevent this loss of traffic, the links are configured over splitter/coupler
cables that link both DMXE/DMGE cards to the router ports, as illustrated in the figure in Fast IOP: 1+1 Card
Protection.
DMXE/DMGE cards resolve this problem through the use of eIOP, by adding LOS as an IOP trigger on selected
LAN ports. With eIOP, a failure on the link to the active DMXE/DMGE card triggers an IOP switchover.
DMXE/DMGE #2 becomes active and activates transmissions on the LAN ports. The router detects this link is
now up and sets/advertises a new traffic route. Traffic is restored.
With eIOP, the splitter/coupler cable is no longer required. A regular fiber cable can be used between the
DMXE cards and the router, as illustrated in the preceding figure. This frees a port on each DMXE/DMGE card
to carry additional traffic.
IOP with link fail trigger is only supported for DMGE_4_L2, DMGE_8_L2, DMXE_48_L2 and DMXE_22_L2. It
can be supported on up to the number of ETY ports, with port type as follows:
 ETY UNI, I-NNI, E-NNI
 ETY MoE
 LAG ETY UNI, I-NNI, E-NNI
Link trigger for IOP is supported on optical transceiver only.

To manage link trigger for IOP:

1. In the NE Shelf View window, in the left object tree, select the NE, and in the Configuration working
mode, select the Data Card IOP tab.
2. In the list, right-click on a PG and select IOP Trigger.
The IOP Trigger window opens.
The IOP Trigger window enables you to define the following parameters:
 IOP-Port-Fail Threshold: a threshold that defines the severity of link failure(s) when used as
trigger to IOP switchover. Degraded severity means the number of failures is below the threshold,
and failed severity means the number equal or higher than this threshold, then IOP switchover is
performed. The valid value can be: 1 (the number of ETY pots), 4 (DMGE_4_L2) or 8 (DMGE_8_L2).
 IOP Ports State: an attribute to describe IOP Port status for both protected and protecting card.
The valid value can be: OK, Failed or Degraded. Default is NA.
 IOP Trigger: can be Disabled or Enabled. When Enabled, link fail condition on the port will be
reported to MCP as trigger to IOP switchover. Applicable for ETY UNI/NNI, ETY MoE and ETY LAG
ports. If on LAG, it is configurable only on LAG. Default is Disabled.
 Operational State: status of the port for both protected and protecting card. The status is
applicable only to 1GbE optical ports and it is derived from LOS indication on the Rx port and
SFP_OUT. If IOP trigger is Enabled, it can be OK or Failed. If IOP trigger is Disabled, then it is NA.


4. To view the IOP port attributes of a port or a LAG, in the object tree, select the port or LAG. In the
You can view the attributes in the IOP Port Attributes area.

5. To check the port status on both working and standby card, in the object tree, select the protecting or
protected data card. In the Configuration working mode, select the Port Physical Status tab.
6. Click to retrieve the information to view:

 Link Status: actual link status of the PHY.
 Laser Tx: actual status of TX Disable of SFP/SFP+. NA for copper interface.
 LOS Status: actual status of LOS output of SFP/SFP+. NA for copper interface.
 AN: if auto-negotiation is enabled or not.
 AN Status: the actual negotiation result. NA if AN is disabled or not supported.
 Remote Fault: if remote fault is detected or not.
 PHY Type: the actual PHY type configured.
 Admin Status: enabled or not.
 IOP Trigger: whether this port is an IOP trigger. NA in case of no IOP created.

15.3.7 SFP Inventory in IOP

Only the protecting card supports the SFP Inventory.
To view SFP inventory in IOP:

 In the NE Shelf View window, in the left object tree, select the protecting card. In the Configuration
working mode, select the SFP Inventory tab.

15.4 Work with OTN Port IOP

Client port protection as shown in the figure below is supported in LCT-NPT, which is based on duplication of
services with a paired MXP10 located in an Odd/Even slots using splitter/coupler or Y-Fiber.
Figure 15-3: MXP10 Port protection with splitter/coupler
Port protection is basically intended to protect against card/module failures. The role of NE port protection
is to allow service continuation in the event of failure or extraction of the service source/sink card or
Module/Transceiver. By nature, port protection requires two cards, protecting each other.
Port protection is activated on a per-service basis, using external splitter/coupler to connect two client-side
ports (one on each card) to the client’s equipment. A pair of cards which are mutually assigned to protect at
least one service, shall be considered as protection card pair. It can be deduced from this definition that on
the same protection card pair, some services might have port protection, while other services might be
unprotected (or protected with other protection types, such as Client traffic protection).
Figure 15-4: Port Protection source/sink model
Refer to upper figure, MXP10 port protection is used to protect one or more physical port, by the
corresponding port of an adjacent card. To provide protection for at least one service, two cards must be
manually associated and assigned as a protection card pair. From client to line direction (ingress, Splitter to
card direction), traffic are always sent to both OTU ports on a pair of MXP10 cards. From line to client
direction at client port, select the working port to receive traffic, the protecting port shall be laser off.
Port protection when WAN side is OTU2
Refer to below figure, signals on client ports are multiplexed to OTU2 line port. In this case, port protection
for client port is supported.

Figure 15-5: Port protection when WAN side is OTU2
Port type on client port can be OTU1 port, STM/OC port, ETY port, FC port and cannot be CBR Video port.
Port protection cannot be configured on electrical ports (STM1e, OC3e, ETY1Ge).
For REG application, one line port is client signal (STM-64/OC-192, ETY10G/ETY10GOC, FC800/FC1200), port
protection for client side is supported.
Port protection when WAN side is OTU1
For client port mapping/multiplex to OTU1 WAN side service, port protection on client port is support.
Client port can support STM-1/STM-4/STM-16, OC-3/OC-12/OC-48, ETY1G, FC100/FC200.
15.4.1 Manage OTN Port IOP

Following are the limitations/rules for creating OTN port IOP:
 Only MXP10 in ES1 and ES2 can create PG;
 PG must exist on different MXP10 cards;
 Following lists the OTN port types that support creating PG:
 OTU1 port
 STM-1/STM-4/STM-16/OC-3/OC-12/OC-48 port,
 ETY-1G
 FC100/FC200/FC400 port
 STM-64/OC-192
 ETY10G/ETY10GOC
 FC800/FC1200
 Electric port and CBR port cannot support PG: Electrical interface and CBR port does not support
creating PG：
 STM1e
 OC3e
 ETY1Ge

 OTN_HDSDI_1485Port
 OTN_VIDEO_270Port
 OTN_HDSDI_3GPort
 OTN_HDSDI_3GNAPort
 The two port in a PG must have the same subcards, the same port types and the same port numbers.
 If both Main/Protection ports carry traffic, create port protection PG is acceptable. But in this case, the
traffic will be affected at the protection ports.
 If different port parameters have been configured on a pair of ports, it is permitted to create the port
PG. The configuration of the Main port will be duplicated to the protection port directly.
To create OTN port IOP:

1. To define port type for subcards of MXP10:
a. In the NE Shelf View window, in the left object tree, right-click a subcard of MXP10 and then
select Define Port Type. )
b. Set required port types and relevant container types from corresponding drop down list.
d. To define port types for other subcards with the same configuration.
2. In the left object tree, select the NE. Click Configuration and then select the OTN Port IOP tab.

3. To create OTN port PG, on the toolbar, click .

4. Follow these steps to create an OTN port PG:
a. Set the Revertive mode as Not Revertive or Revertive.
b. Set the Wait-to-restore Time.
c. Set the Hold-off Time.
d. Select a main port and a protecting port from the relevant port lists.
e. Click Apply. The OTN port PG is saved to the PG list.
5. To edit an OTN port PG:
a. On the toolbar, click .

b. Modify the settings as required.
c. Click Apply. The changes are saved.
6. To clear the PGs in the list, click .
7. To overwrite all the PGs from the NE equipment to database, click

8. To delete an OTN port PG, select the PG you want to delete and click .

15.4.2 OTN Port IOP Maintenance Operation

The following switch commands are supported for OTN port IOP:
 Release – Clears all of the switch commands listed below, for the channel or channels specified in the
command.
 Lockout of Protection – Prevents any of the working channels from switching to the protection line by
issuing a Lockout of Protection request [unless a request of equal priority (i.e., a Lockout of Protection)
is already in effect].
 Forced Switch to Protection – Switches the specified working channel to the protection line unless a
request of equal or higher priority is in effect by issuing a Forced Switch request.
 Forced Switch to Main – Switches the working channel back from the protection line to the working
line unless a request of equal or higher priority is in effect, by issuing a Forced Switch request for the
null channel.
 Manual Switch to Protection – Switches the working channel to the protection line unless a request of
equal or higher priority is in effect, by issuing a Manual Switch request.
 Manual Switch to Main – Switches the working channel back from the protection line to the working
line unless a request of equal or higher priority is in effect, by issuing a Manual Switch request for the
null channel.
To perform OTN port IOP maintenance operations:

 In the OTN port IOP list, right-click a PG and then select the required maintenance operation.

15.5 Work with NFV Card IOP

LCT-NPT support NFV card 1+1 protection by NFV LAG mechanism. The LAG mechanism can work based on
that, NFV cards can support cross-card LAG, or the standby NFV card can set the port to link down to indicate
CIPS not transmit the traffic to it.
Only two same type NFV cards can be added to NFV Card IOP PG.
A PG is complete when:
 Both cards have no active ports; or
 Both cards have active ports, and they are activated on the same port number, with same port role;
 Both cards have Internal Ports, and all of them are in a single LAG; or
 Both cards have Service Ports, and the ports on the same port number are in the same LAG.
Following may make a PG incomplete:
 When activating port on the working card, some step fails;
 When deactivating port on the working card, some step fails;
 User modifies the ports on the working card or protecting card manually.
To check whether a PG is complete:
 Both cards have no active ports; or
 Both cards have active ports, and they are activated on the same port number, with same port role; or
 Both cards have Internal Ports, and all of them are in a single LAG; or
 Both cards have Service Ports, and the ports on the same port number are in the same LAG.
When deleting a PG, all ports in the protecting card will be removed from the lag, and all new
activated/deactivated ports in protected card will not be synchronized to the protecting card.

15.5.1 Create NFV Card IOP

To create NFV Card IOP:
1. In the object tree, select the NPT-1200/NPT-1200i/NPT-1800 NE. In the Configuration working mode,
select the NFV Card IOP tab.
2. To create an NFV Card PG, click .

3. In the Create NFV PG window, select main and protection ports in the Main and Protection areas.
4. To create the PG for optical ports, click Apply. If the process is successful, the green icons adjacent to
the ports turn gray.

5. Close the window. View the created PG in the following window.
15.6 Work with STP and MSTP

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.
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.
15.6.1 STP and MSTP supported cards

Only the FE_12 card in the BG-40 NE supports STP.
All the L2 Data cards in the LCT-NPT 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
 DMXE_48_L2
 DMXE_22_L2
 MPOE_12G
 ME_2G_4F
 CPTS100
 CPS100
 CS10

15.6.2 Configure STP and MSTP

This section describes how to configure STP and MSTP in LCT-NPT.
To configure STP:
1. In the BG-40 NE Shelf View window, in the left object tree, select the FE_12 card and then the Switch
object. Select the Configuration working mode. The following window opens.
2. Set the bridge parameters:

 STP Enable: Enable or Disable (default Enable).
 Max Age Time: Amount of time protocol information received on a port stored by the network
device.
forwarding.
 Priority: Parameter used for root bridge selection: the lower the parameter, the higher the
priority. The bridge with the highest priority is the root bridge. Default is 32,768.
4. To retrieve the bridge STP settings, on the toolbar, click .

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 a Layer 2 data card and then its Switch
object. Select the Configuration working mode. Three tabs are connected to MSTP in the properties
area: MSTP, MSTP Ports, and MSTP Instance. Select the MSTP tab.
2. In the MSTP Configuration area, set the following parameters:

 Network ID: The attribute is only available for ESW_2G_8F_2E and MESW_6 card. Default value
is 0.
 Protocol Enable: Enable or Disable (default is Enable).
 Region Name: Name of region.
 Revision Level: Default is 0.
forwarding.
 Max Age: Amount of time protocol information received on a port stored by the network device.
3. To set the MSTP instance:
a. Select the default instance in the MSTP Instance list.
b. To modify the S-VLAN, on the toolbar, click .

d. Click to add a new instance, or to delete a selected instance.

5. If you want to export the instance to a file, on the toolbar, click .
6. To retrieve the bridge MSTP settings, on the toolbar, click .
To configure port MSTP settings:

1. In the MSTP Ports tab, set the port MSTP parameters, and click Apply to save the settings.
Fast/Slow link detection configuration on EoS ports is supported. The maximum of fast detection EoS
ports is 16 for MSTP.

2. In the MSTP tab, click to retrieve the information.
Set the following two attributes in this window:

 Priority: Per instance. The lower the value, the higher the priority. Used to select the root port or
a designated port.
 Path Cost: Per instance. Configurable value.
3. To send the port MSTP settings to the equipment and the DB, click Apply.

16 Ethernet ring protection switching
ERPS helps to achieve high reliability and network stability. Links in the Ethernet ring never form loops that
fatally affect network operation and services availability. The basic idea of an Ethernet ring is to use one
specific link to protect the entire ring. This special link is called a Ring Protection Link (RPL). If no failure occurs
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 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.
The following figure is an example of ERPS operation.
Figure 16-1: Example of ERPS operation
In this ring topology are six nodes, one of which is called the RPL owner node. The other nodes are called ring
nodes. In this ring, RPL is blocked on the RPL owner node. When link/node failure is detected by the nodes
adjacent to the failure, they can block the failed link, 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 receives the R-APS (SF) message, it unblocks the RPL and flushes the FDB. The ring is in protocol
state and all nodes remain connected in the logical topology.
16.1 ERPS workflow

The following Layer 2 data cards support ERP Control VSI:
 MPS_4F
 MPS_6F
 DMFE_4_L2
 DMFX_4_L2
 DMGE_2_L2
 DMGE_4_L2
 DMGE_8_L2
 DMXE_48_L2

LCT-NPT® User Guide Ethernet ring protection switching
 DMXE_22_L2
 MPOE_12G
 MPS_2G_8F
 ME_2G_4F
 CS100
 CS50
 CS10
 CS5
 CS320
 CS100_1050
The procedure for creating PB Ring ERP Control VSI is as follows:
4. Set the Interface type (I-NNI) for the ETY/EoS ports in a data card.
5. In the Create VSI window:
 Select the PB Ring as the ERP Type.
 Select the West and East ports for the services.
 Set the required VSI parameters and ERPS parameters for the services.
6. Create the PB Ring ERP Control VSI.
An MPLS Ring ERP Control VSI must have one ERP port and one remote PE. The procedure for creating MPLS
Ring ERP Control VSI is as follows:
7. Define the Configuration Mode as MPLS.
8. Assign PE ID and MPLS Network ID. Each MPLS requires a unique PE ID.
9. Configure ports as MoT port type.
10. Set the Interface type (I-NNI) for the ETY/EoS ports in the card.
12. Create required tunnels.
13. In the Create VSI window:
 Select the MPLS Ring as the ERP Type.
 Select one ERP port and one remote PE for the services.
 Set the required VSI parameters and ERPS parameters for the services.
14. Create the MPLS Ring ERP Control VSI.

16.2 Create PB Ring ERP Control VSI

To create a PB ring ERP control VSI:
1. To set the ETY port attribute:
a. In the left object tree, select a L2 data card, and in the Configuration working mode, select the
GE ETY Ports/10 GE ETY Ports tab.
b. In the Type list, select I-NNI.


2. To create the ERP control VSI:

a. In the left object tree under the data card, select the Switch object. In the Services working mode,
select the VSI List tab.
b. On the toolbar, click the Create VSI icon .

c. In the Create VSI window, from the Service Type dropdown list, select ERPS VSI, and select PB
Ring as the ERP Type.
d. Select the VSI State (default Enabled). When disabled, all policers block their traffic, including NNI
ports. When enabled, all policers enable traffic flow. This field is editable with no constraints.
e. Enter the VSI ID, NMS VSI ID, User Label, and Customer values as required.
f. In the ERPS Parameters area, select the following:
 From the ERP Node Role dropdown list, select RPL Owner or Ring Node. 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
the RPL under normal conditions. There can only be one RPL owner for each ring.
Ring node has no special role on the ring.
 ERP Instance ID: 0-31 (default is 0).

 ERP Instance Name

 Tunnel Mode: E-LSP or L-LSP.
 S_VLAN: 1-4094.
 Protected S_VLAN: The S_VLAN protected by the ERPS. The S_VLAN ID that does not 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: 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-10 sec in steps
of 100 msec with an accuracy of 5 msec (default 0 sec).
 WTR Time: In the revertive mode of operation, in order 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 elapses before the traffic channel uses it again. This period
is called the WTR period.
In the revertive mode, when the protection is no longer requested and the failure condition
has been cleared, a WTR state is activated on the RPL owner node. This state normally times
out and becomes a no-request state. The WTR timer is deactivated when any request of
higher priority preempts this state.
When the ERP Node Role is set as RPL Owner, the WTR timer can be configured by the
operator between 1 and 12 min in 1-min steps (default 5 min).
 Guard Time: Ring-APS (R-APS) messages are transmitted and forwarded by a method in
which messages are copied and forwarded at every node around the ring. This can result in
a message corresponding to an old request, 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 old messages still circulating on the ring to be
ignored. The side effect, however, is that during the period of the guard timer, a node is
unaware of new or existing ring requests transmitted from other nodes.
The period of the guard timer can be configured by the operator between 10 msec and 2
sec in 10 msec steps (default 500 msec). This time should be greater than the maximum
expected forwarding delay for which one R-APS message circles around the ring.
 Revertive Mode: Revertive.
3. In the Objects Selections area, from the relevant lists, select one I-NNI port as the West port and one
I-NNI as the East port. Right-click an object to deselect.
4. 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 link which, under normal conditions without any failure or request, is blocked
for traffic channel (at one or both ends), 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, one of the selected ports can be set as RPL Port and the other as Ring Port
from the Port Role dropdown list.
5. Enable the BFD Trigger for the selected PB I-NNI ports by selecting the BFD Trigger checkboxes if
required.
6. Click Activate to create and activate the ERP control VSI. If you click Save, the ERP control VSI is saved
but not activated. To then activate it, select the Recent Saved VSIs tab, select the VSI you want to
activate, and click Activate.
16.3 Create MPLS Ring ERP Control VSI

To create an MPLS ring ERP control VSI:
1. Before creating the MPLS ring ERP control VSI, follow the procedures in Create Tunnel XCs to create
tunnel XCs.
2. To set the ETY port attribute:
a. In the left object tree, select a L2 data card, and in the Configuration working mode, select the
GE ETY Ports/10 GE ETY Ports tab.
b. In the Type list, select I-NNI.

3. To create the ERP control VSI:

a. In the left object tree under the data card, select the Switch object. Then in the Services working
mode, select the VSI List tab.
b. On the toolbar, click the Create VSI icon .

c. To create the ERP control service, from the Service Type dropdown list, select ERP VSI, and select
MPLS Ring as the ERP Type.
d. Select the VSI State (default Enabled). When disabled, all policers block their traffic, including NNI
ports. When enabled, all policers enable traffic flow. This field is editable with no constraints.
e. Enter the VSI ID, NMS VSI ID, User Label, and Customer values as required.
f. In the ERPS Parameters area, select the following:
 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 (default 0).
 ERP Instance Name: Name of the ERP Instance.
 Tunnel Mode: E-LSP or L-LSP.
 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 does not 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: 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-10 sec in steps
of 100 msec with an accuracy of 5 msec (default 0 sec).
 WTR Time: In the revertive mode of operation, in order 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 elapses before the traffic channel uses it again. This period
is called the WTR period.
In the revertive mode, when the protection is no longer requested and the failure condition
has been cleared, a WTR state is activated on the RPL owner node. This state normally times
out and becomes a no-request state. The WTR timer is deactivated when any request of
higher priority preempts this state.
When the ERP Node Role is set as RPL Owner, the WTR timer can be configured by the
operator in 1-12 min in 1-min steps (default 5 min).
 Guard Time: Ring-APS (R-APS) messages are transmitted and forwarded by a method in
which messages are copied and forwarded at every node around the ring. This can result in
a message corresponding to an old request, 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 old messages still circulating on the ring to be
ignored. The side effect, however, is that during the period of the guard timer, a node is
unaware of new or existing ring requests transmitted from other nodes.
The period of the guard timer can be configured by the operator between 10 msec and 2
sec in 10-msec steps (default 500 msec). This time should be greater than the maximum
expected forwarding delay for which one R-APS message circles around the ring.
 Revertive Mode: Revertive.
4. In the Objects Selections area, from the relevant lists, select one I-NNI port and one Remote PE. Right-
click an object to deselect.
5. For the selected remote PE, select a tunnel in the Tunnel list and set the In VC Label and Out VC Label.

6. Enable the BFD Trigger for the selected PB I-NNI port by selecting the BFD Trigger checkbox if required.
The default is enabled.
7. Click Activate to create and activate the ERP control VSI. If you click Save, the ERP control VSI is saved
but not activated. To then activate it, select the Recent Saved VSIs tab, select the VSI you want to
activate, and click Activate.
16.4 View the ERPS Instance

This section describes how to view the ERPS instance. The ERPS instance is an ERP attribute of a VSI-ERP
control on a one-to-one relationship.
The alarms of the ERPS instance are reported on the ERP control VSI.

To view the ERPS instance:

1. In the NE Shelf View window, in the left object tree under the data card, select the Switch object. In
the Services working mode, select the VSI List tab.
2. In the VSI list, select an ERP control VSI, and on the toolbar, click the Edit VSI icon or the View VSI
Detail icon .
The Edit VSI or View VSI window opens.

3. In the right area of the window, select the ERP Instance Status tab, and click to view the ERP
status.
Parameters include:
 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: 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.
 Two states on each ring port: Blocked and Forwarding.
 ERP counters in an ERP instance, as follows:
 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.
4. To clear the ERP counters, on the toolbar, click .

17 Fault management
This section discusses how to use the LCT-NPT for configuring, managing, filtering, and troubleshooting NE
alarms.
The LCT-NPT 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 LCT-NPT screen.
The LCT-NPT provides exceptionally powerful tools for viewing and analyzing alarms, enabling you to
optimize alarm-processing operations.
For details about troubleshooting alarms, see Troubleshooting Alarms in the LCT-NPT Supporting Information.

LCT-NPT® User Guide Fault management
17.1 Configure NE fault settings

This section describes how to configure NE settings. For the BG-40 NE, NE settings include NE History Log
Setting and Alarm Hold-Off Time. For the other NEs, there is an additional AinS Timer setting.
To configure BG-40 NE settings:

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

a. NE History Log Settings: Alarm log settings specify the working mode of logs on the NE equipment
and include the log length setting, the log working status, and the processing mode after a log is
full. The following terms relate to alarm log settings:
 The NE alarm log is a flow record table of alarm events and other events generated in an
NE.
 The NE History specifies whether the log is currently in use or has been stopped. It has two
modes: Disabled and RAM logging only. RAM logging only mode means the alarm log keeps
collecting events and saves the events in RAM. Disabled mode means the alarm log is no
longer in use. Default is RAM logging only.

 The Log Size defines the maximum number of records that can be stored in a log on the NE
equipment, from 0 to 1,000 (default 1,000).
When a log is full, it has two processing modes: Overwrite and Stop (default Overwrite). In
Overwrite mode, new records replace the oldest records. In Stop mode, the alarm log stops
collecting events.
b. Alarm Hold-Off Time: You can set the hold-off time for alarm generation and clearance, to
prevent alarm generation and clearance from being incorrectly reported and to suppress
excessively frequent alarm generation and clearance. An alarm’s status change is not validated
until the hold-off time has elapsed. The hold-off time is defined by the alarm generation hold-off
period and the alarm clearance hold-off period.
For the alarm generation hold-off period, an alarm event is not reported and the current alarm
status is not updated until a generated alarm is detected and its alarm status lasts 3-30 sec
(default 3 sec).
For the alarm clearance hold-off period, any alarm clearance detected is not considered as cleared
unless the clearance status lasts 3-30 sec (default 3 sec).
3. To copy the settings from the selected NE to other NEs, click .
To configure BG-20/BG-20C/BG-30/BG-64/NPT NE settings:

1. In the topology view, in the object tree list, select the BG-20/BG-20C/BG-30/BG-64/NPT NE to be
configured.
2. Select working mode Fault, Fault Settings and then the NE Settings tab.

For the BG-64/NPT NE, the following window opens.
3. Modify the NE settings as required.

In the AinS Timer area, the NEs define two AinS timer ranges from 1-1,800 sec, in steps of 1 sec. Default
for Time1 is 10 sec and Time2 180 sec.
The settings in NE History Log Settings and Alarm Hold-Off Time areas are performed in the same
manner as for the BG-40 NE.

17.2 Monitoring and Reporting Alarms

In the LCT-NPT, you 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. These alarms can
be masked to avoid confusion 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 send
LOS alarms. You can mask these alarms of 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 LCT-NPT, alarms can be masked for the optical interface, electrical interface, and SDH functional
block. Generally, to mask optical interface alarms, all SPI, RS, MS, AU-4, and VC-4 alarms are masked.
To mask electrical interface alarms, all VC and PPI alarms are masked.
When the alarms of a certain object are masked, the alarms related to this object in the current alarm DB are
cleared. After the alarm mask is released, the equipment reports the current alarm. Therefore, the NE
equipment for which the alarms have been masked should have no alarm indication.

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

1. In the BG-40 NE Shelf View window, select Fault and then 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. To send the settings information to the NE equipment, click Apply.
4. To refresh and retrieve the information of the NE settings, click .

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

NEs:
1. Select a BG-20/BG-20C_L2M/BG-30/BG-64/NPT NE in the topology view. Then, on the main menu,
select Fault and then Monitoring and Reporting. The following window opens.
2. Set the attributes for each object as needed, and click Apply to save the changes.
You can set three attributes for each object:
 Monitor attribute: Setting is the same as for the BG-40 NE.
 Auto Report attribute: Either Report or No Report in the dropdown list.
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 attribute is
enabled, which can be selected from Timer1 or Timer2 (default Timer1).
 AinS attribute applies only on the following interfaces:
 PPI
 FE LAN
 GE LAN
 Codirectional

3. To refresh and retrieve the information of the NE settings, click .
To configure monitoring/reporting settings for NPT-1800 NEs:

1. In the NPT-1800 NE Shelf View window, in the left object tree, select the NPT-1800 NE. Then in the
working mode, click Fault, Fault Settings, and then select the Monitoring and Reporting tab.
2. You can set two attributes for each object:

 For the Monitor attribute, the setting is the same as for the BG-40 NE.

 For the Severity Profile attribute, from the dropdown list, select an alarm profile as required.
3. To view details of a selected alarm profile, click the button next to the selected alarm profile.
For details about how to create alarm profiles, see Creating Alarm Profiles.
17.3 Set switch alarms for MSPP/NPT NEs

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

To set an alarm for the switch module:

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

3. To obtain object data from the NE equipment, in the Display dropdown list, select a required class and
click .
The following figure shows, for example, the VSI settings.
4. Modify object parameters as required in Monitor and Auto Report lists.

5. To send settings to a piece of equipment and save them to the LCT-NPT DB, click Apply.
17.4 Monitor and report L2 faults for IP/MPLS NEs

In IP/MPLS NEs, you can configure L2 fault monitoring and reporting for the following classes:
 Switch
 Tunnel
 VSI
 VSI Eth Interface
 CES Interface
 PW
 MA
 IGMP Proxy
 OSPF

 ISIS
 VRRP
 BGP
 PIM
 VRF
 PHT PW
To set alarm for the CS module:

1. In the IP/MPLS NE Shelf View window, select the CS module. In the Fault and Fault Settings working
mode, select the Monitoring and Reporting tab.
2. To obtain object data from the NE equipment, in the Display dropdown list, select a required class and
click .

3. Modify object parameters as required in Monitor and Severity Profile lists.

4. To view details of a selected alarm profile, in the Severity Profile list, click the button next to the
selected profile.
5. Click Apply.
17.5 Manage external alarms

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

To manage external alarms:

1. In the NE Shelf View window, select the NE, and select Fault and then External Alarms.

For IP/MPLS NEs, the External Alarm window is shown as below.
The window has two areas: Input Ports and Output Ports:
 The Input Ports area displays the configuration of the four input ports of the NE. You can assign
a name to the port in the Port Name field and specify the upper TTL level representing the alarm
status or normal status in the Contacts field.
 The Output Ports area displays configuration of the three output ports. These ports are: major
alarm, minor alarm, and sound alarm. You can set the alarm output switch as Yes or No.
2. To send the configuration data to the equipment and save it in the DB, click Apply.
3. To retrieve port information from the equipment, click .

17.6 Configure severity settings

This section describes how to configure severity settings.
Each alarm has the following four attributes in the Severity Settings window:
 Severity
 Report
 Alarm Cause
 Reason ID
Only the Severity and Report attributes can be configured.
Alarms are categorized into five levels by the Severity attribute:
 Mask
 Critical
 Major
 Minor
 Warning

To configure the severity settings:

1. In the NE Shelf View window, select the working mode Fault and then the Severity Settings tab.
2. Set alarm attributes as needed for each alarm title by selecting the relevant Severity attribute from the
dropdown list, and selecting or clearing the checkbox in the Report attribute.
3. To send the settings information to the NE equipment, click Apply.
The functions of the icons on the toolbar are set out in the following table.
Table 17-1: Icons in the Severity Settings window

Icon Description
Refresh - retrieves information from the equipment.
Set as default - views alarm attribute table information for the NE.
Propagate - copies the settings from the selected NE to other NEs.
Open a profile file - imports a profile file from your computer disk.
Save as a profile file - exports the settings as a profile file.

17.7 Configuring LCT Alarm/Event Polling Settings

MCP can report alarms/events to LCT-NPT automatically, and LCT-NPT can receive alarms/events from NE.
To configure LCT alarm/event polling settings:

1. In the NE Shelf View window, in the Left object tree, select the NE. Then select the Fault menu and
then select Alarm/Event Polling Setting.
2. To configure alarm polling settings, in the Alarm Polling area:

a. Select the Enable checkbox. The alarm polling is enabled.
b. Set polling interval as required. The default interval is 20 seconds.
3. To configure event polling settings, in the Event Polling area:
a. Select the Enable checkbox. The event polling is enabled.
b. Set polling interval as required. The default interval is 30 seconds.

17.8 Manage 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.
17.8.1 Viewing Current Alarms

Current alarms are represented on the screen as LEDs on each NE icon. The color of the LED corresponds to
the most severe alarm affecting it.
The current NE alarms in LCT-NPT cannot be updated automatically. To view real alarms on the NE, click
on the toolbar to synchronize the current alarms manually.
To view current alarms for a specific NE:

1. In the NE Shelf View window, select Fault and then Current Alarms in the main menu. The following
window opens.
2. Click to synchronize the alarms to view.

The icons on the alarm toolbar are described in the following table.

Table 17-2: Icons on the alarm toolbar

Icons Description
Acknowledges alarms.
Displays alarm details.
Exports current alarms as an XML file.
Exports current alarms as a CSV file.
Shows current alarms as a list.
Shows current alarms as a chart.
Selects all the alarms.
Deselects all the alarms.
To view current alarms for a specific card:

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

To view current alarms for a specific object:

1. Select an NE in the topology map.
2. In the main menu, select Fault and then Current Alarms.
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.
17.8.2 Determine the cause of an alarm

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

To determine the cause of an alarm:

1. In the Current Alarms window, click a specific alarm.
The alarm row is highlighted.
2. To see detailed information of the alarm in the Alarm Details window (including Alarm Cause, NE, Card,
Object, etc.), on the current alarm toolbar click the Alarm Details icon .
The Alarm Details window opens.
17.8.3 Filtering Current Alarms

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

To filter current alarms:

1. Click + on the Filter bar to unfold the Filter area, as shown below.
2. In the Current Alarms window, clear the checkbox of the alarm you do not want to view (by default, all
objects are checked).
3. Click the Filter icon in the lower right corner.
17.8.4 Sort current alarms

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

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

17.8.5 Acknowledge current alarms

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

 In the Current Alarms window, select one or more alarms in the current alarm list, and on the toolbar,
click .
Or, select a current alarm and right-click, and from the shortcut menu, click .
17.8.6 Export current alarms to files

You can save the current alarms information to an XML or CSV file.
To export current alarms to a file:

1. On the toolbar of the Current Alarms window, click the type of file to which you want to export the
alarms.
You can select the following file types:
 XML -
 CSV -
2. Select the location folder.
3. Enter a name for the exported file, and then click Save.

17.8.7 Viewing a Chart for Current Alarms

To view a chart for current alarms:
 In the Current Alarms window, on the toolbar, click the icon . A histogram is displayed, showing
current alarm information by alarm severity. Colored blocks represent alarms of different severities.
17.8.8 Manually synchronize alarms

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

To manually synchronize an alarm on an NE:

1. In the Current Alarms window, select the NE.
2. On the toolbar click the green icon .

A message indicates that synchronization was successful.
17.9 Manage 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.
To manage historical alarms for a specific NE:

1. In the main topology view, select an NE whose alarm information you want to view.
If no NE is selected, current alarm information for all NEs is displayed by default.
2. Select Fault and then Cleared Alarms.
3. To display the information, click .

The following figure provides an example of cleared alarms:
The icons on the alarm toolbar are listed in the following table.

Table 17-3: Icons on the historical alarm toolbar

Icon Description
Obtains the information from the equipment.
Displays alarm details.
Shows the historical alarms as a list.
Shows the historical alarms as a chart.
Selects all the alarms.
Deselects all the alarms.
Deletes the selected alarms.
Exports historical alarms as an XML file.
Exports historical alarms as a CSV file.
To manage historical alarms for a specific card:

1. In the main topology view, select an NE.
2. Select Fault, and then Cleared Alarms.
3. In the open window, select the card whose alarm information you want to view.
To manage historical alarms for a specific object:

1. In the main topology view, select an NE.
2. Select Fault, and then Cleared Alarms.
3. In the open window, click before the tributary card or port to display all the objects.
4. Select the object whose alarm information you want to view.

17.10 Monitor events

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

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

a. On the toolbar select the type of file to which you want to export the alarms.
You can export to the following file types:
 XML -
 CSV -
b. Select the location folder.
c. Enter the file name for the exported file, and then click Save.
5. To delete events, select the events in the list that you want to delete, and then click .

17.11 Managing Unreported Alarms

To manage unreported alarms:
1. In the NE Shelf View window, select Fault and then Unreported Alarms. The following window opens.
2. To retrieve information to view, in the toolbar, click .

3. To view the alarms in a list, in the toolbar, click the Show as List button .
4. To view the alarms in a chart, in the toolbar, click the Show as Chart button .

5. To view unreported alarm details, select a cleared alarm in the list, and in the toolbar, click the Alarm
Details button .

6. To export the unreported alarms as an XML file:
a. On the toolbar click . The Save window opens.
b. Select the location folder, enter the file name for the XML file, and click Save.
7. To export the unreported alarms as a CSV file:
a. On the toolbar click . The following window opens.

b. Select the location folder, enter the file name for the CSV file, and click Save.
8. To delete the unreported alarms records, select the alarms you want to delete in the list, and in the
toolbar, click .
17.12 Manage the NE alarms log

The NE alarms log records the alarm and event information saved in the NE equipment. If an NE is
disconnected during a certain period, all its alarms and events generated during this period are recorded in
the log.
17.12.1 Viewing NE Alarms Log

To view NE alarms log records:
1. In the NE Shelf View window, select Fault and then NE History.
2. To retrieve NE alarms log records, click .

17.12.2 Export NE alarm logs to files

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

1. On the toolbar select the type of file to which you want to export the alarms.
You can export to the following file types:
 XML -
 CSV -
3. Enter the file name for the exported file, and then click Save.

18 Performance management
Performance data reflects the network running quality. This section discusses how to monitor the bit errors
for each section, the SDH layers, and the path for evaluating QoS.
The LCT-NPT performance functions provide instant monitoring and regular statistics for the error codes of
various SDH and Ethernet section layers and paths. Such data is essential to ensure optimal network
performance.
For details about performance counters lists, see Manage PM Counters Lists in the EMS-NPT Supporting
Information.
18.1 Performance data

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

LCT-NPT® User Guide Performance management
The following figure shows the PB Ethernet connection view.

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

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

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

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

Figure 18-4: Zoomed-in illustration of objects within MPLS PE
In the figure, the packet received from a UNI port will be counted by the counter of port: If the packet belongs
to the macro flow which has a policer, the packet will be counted by the policer; if the packet is a broadcast
packet and belongs to a VSI of MP2MP, it will be counted by the BSC policer of that VSI. The packet will be
counted by the tunnel if it is forwarded by a tunnel. The MSTP topology change and FIB utilization will be
counted on the object of the switch.
Performance data is divided into the following monitoring periods:
 15-minute: Equipment performance data is measured in 15-minute intervals. At the end of each 15
minutes, the value of the 15-minute performance data counter is reported to the LCT-NPT. At the same
time, the performance data counter is reset and another round of 15-minute performance statistics
starts to accumulate.
 24-hour: Equipment performance data is measured in 24-hour intervals. At the end of each 24 hours,
the value of the 24-hour performance data counter is reported to the LCT-NPT. At the same time, the
counter is reset and another round of 24-hour performance statistics starts to accumulate.
 Instant: current values of the 15-minute or 24-hour performance data counters.

Through the analysis of historical performance data in the LCT-NPT, the errors at each SDH section/layer can
conveniently be checked. If there are errors in the RS, MS, and VC-4, the typical cause is poor aggregate (card)
performance.
Possible causes are:
 Low laser power.
 High laser power.
 Excessive input jitter caused by a poor contact on the optical interface, or a relay less distance of the
fiber that is too long.
Performance data can be used as an analytical tool, as follows:
 By examining the 15-minute performance data for a given day, you can analyze the equipment
performance for that day.
 By examining the 24-hour performance for a month, you can analyze the equipment running status for
that month.
 By examining the 24-hour performance for a year or several years, you can analyze the long-term
running of the equipment.
The LCT-NPT provides a performance curve diagram, which shows equipment performance changes during a
specific period visually. This mechanism provides a convenient way to analyze the communication link quality
over time.
18.2 View performance data

The LCT-NPT 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 four classes: SDH, Port, EoS, and
DCC. When you select a class, the related performance data is displayed. The default is SDH performance
data.
18.2.1 View current performance

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

 PTP Port
 MCC NI
 CES Extend
 OTN
 SFP
When you select a class, the related current performance data is displayed.
To view current performance data:

1. In the NE Shelf View window, in the left object tree, select 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. To retrieve the current performance data from the NE equipment, in the toolbar, click .
3. Select the Refresh data dynamically checkbox, and set the Refresh Interval.
4. To observe any performance data changes dynamically, click Start Refresh. Data is refreshed, based on
the Refresh Interval you specify.
5. To cancel the refresh operation, click Stop Refresh.

6. To view the information in a list, click the List View icon .
7. To view the information in a chart, click the Chart View icon . In the Filter area, select the object
you want to view, the chart type you want to generate, and click Get & Create Chart. The following
window opens, showing the chart view of the information.
18.2.1.1 View switch performance data

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

 CFM LM Session
 CES Interface
 Queue Block
 BD LSP
 Management VLAN
 NPT Central PE
 Diffserv Block
To view the PM data:

8. In the NE Shelf View window, select the central PE or Switch module.
10. Select the relevant Type in the Display dropdown list.
The current performance data of the corresponding object is shown.
11. To retrieve the current performance data from the NE equipment, on the toolbar, click .

18.2.2 View recent performance

For all functional block performance objects, the NE provides a recent performance register which is a first-
in first-out (FIFO) queue used to save the latest performance data (meaning, historical performance data) of
the NE. There are N (N = 16) recent 15-minute registers and M (M = 6) recent 24-hour registers. (For Data
cards, N=4, M=2.) 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 LCT-NPT can acquire values stored in the recent 15-minute and 24-hour registers.
Recent performance data is divided into the following classes:
 SDH
 Port
 EoS
 DCC
 L2 Extend
 PoS
 PTP TMU
 PTP Port
 MCC NI
 CES Extend
 OTN
 SFP
When you select a class, the related recent performance data is displayed. The default is SDH performance
data.

To view recent performance data:

1. In the NE Shelf View window, in the left object tree, select an object. Then select the NE History tab
under the Performance working mode.
2. Select the relevant Display radio button.

3. To obtain and display the performance parameter values stored in the recent performance registers of
the NE equipment, click .
18.2.3 View current rate in IP/MPLS

In the IP/MPLS NEs, for the E1 objects with services of MSC_2_8, you can view current rate.

To view current rate in IP/MPLS:

1. In the IP/MPLS NE Shelf View window, under the MSC_2_8 card, select an E1 object with services.
2. In the Performance working mode, select the Current Rate tab.
3. To refresh the data, click Start Refresh.

4. To stop refreshing the data, click Stop Refresh.
5. To view the data as a chart:
a. On the toolbar, Click .

b. In the Filter area, select the chart type as Line Chart or Bar Chart.

c. Select required parameters to view.

d. Click the Create Chart button to create the chart.

18.3 Configuring Performance Attributes

The LCT-NPT enables you to configure the performance attributes, including setting performance thresholds,
setting performance monitor switches, and resetting performance counters.
18.3.1 Open archived performance files

To open archived performance files:
1. In the NE Shelf View window, select the NE, and then in the Performance working mode.
2. Select the Archived Files tab.
3. To open an archived file, on the toolbar click .

4. Select the file that you want to open, and then click Open.
18.3.2 Set performance thresholds

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

To set TDM TCA thresholds:

2. In the Performance and Performance Settings working mode, select the TDM TCA Threshold tab.
3. To display the performance threshold value obtained from an NE, click .
4. To copy the performance threshold value to other NEs, click .

5. To send performance threshold values to the NE and save them to the DB, click Apply.
6. To set the SD/EXC threshold, select the SD/EXC tab.

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

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

4. To set the performance thresholds for EoS, in the NE Shelf View window, under a Layer 2 card, select
the EoS object.
6. To display the performance threshold value obtained from an NE for viewing, click .

7. To set the performance thresholds for switch, in the NE Shelf View window, select the Switch object or
CS module.
9. In the Display field, select the relevant button, and to display the performance threshold value obtained
from an NE for viewing, click .
18.3.2.1 Set the switch performance threshold

You can set the switch performance threshold for the following classes:
 VSI
 Tunnel
 MA
 CES Interface
 Queue Block
 BD LSP
 Management VLAN
 Diffserv Block

To set the performance threshold for the switch:

1. In the NE Shelf View window, select the Switch/CS module.
2. In the Performance working mode, select the Threshold Setting tab.

3. In the Display area, select the corresponding button (for example, the Tunnel settings).
4. To obtain object data from the NE equipment, select the corresponding checkboxes in the Filter area,
and then click .
5. Modify object parameters as required in the corresponding area, and to send settings to a piece of
equipment and save them to the LCT-NPT DB, click Apply.

18.3.2.2 Set the OTN TCA threshold

To set OTN TCA thresholds:
2. In the Performance and Performance Settings working mode area, select the OTN TCA Threshold tab.

18.3.2.3 Set the SONET TCA threshold

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

To set SONET TCA thresholds:

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

18.3.3 Set DCC performance

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

To set DCC TCA thresholds:

2. In the Performance and Performance Settings working mode area, select the DCC TCA Threshold tab.

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

To set DCC PM and reporting:

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

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

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

To view DCC current/recent PM:

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

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

To reset DCC PM counters:

1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1050 NE Shelf View window, select a
DCC object.
2. Select Performance and then Reset PM Counters.

Or, in the DCC Current PM window, on the toolbar, click the Reset PM Counters button .

3. Select the type of counter that you want to reset, and then click Yes.
18.3.4 Manage performance settings

This operation enables you to monitor the performance of an NE by setting a main switch for NE PM and
setting the start and end times for the monitoring process. The performance object monitoring switch
determines whether to monitor the performance of a specific functional block in an NE. The autoreport
switch determines whether to allow historical performance data for a specific functional block in an NE to be
automatically reported to the LCT-NPT.
The following terms relate to the Performance Monitor Switch operation:
 Main switch for NE PM: Determines whether to monitor the performance of an NE. When this switch
is disabled, the collection of statistics and the monitoring of all performance objects in an NE are
terminated. In this case, the LCT-NPT cannot obtain any current performance counters and the NE does
not automatically report any historical performance data. When enabled, the switch monitors the
performance of an NE between the start and end times.
 Performance object monitoring switch: Determines whether to monitor the performance of a specific
functional block in an NE. If this switch is disabled, it terminates the collection of statistics and the
monitoring of all performance objects within this functional block.

 Autoreport switch: Determines whether to report to the LCT-NPT automatically historical performance
data for a specific functional block within an NE. If this switch is enabled, historical performance data
of a functional block in an NE is automatically reported to the LCT-NPT. When disabled, performance
statistics collection and monitoring are implemented within an NE, but there is no reporting. Therefore,
current performance counter values can still be obtained.
 Specific SDH and Ethernet functional block.
To manage performance settings:

2. In the Performance and Performance Settings working mode, select the Monitoring and Reporting
tab.
3. To obtain object data from the NE equipment, click .

4. To batch edit the TTI Detection attribute, on the toolbar, click .
5. Modify object parameters as required.

7. To set monitoring switch parameters for an NE, select the Schedule tab.
18.3.4.1 Set switch performance for MSPP/NPT

In the MSPP/NPT NEs, you can set the performance monitoring and reporting for the following classes:
 Switch
 VSI
 Policer
 CoS
 Tunnel
 MA
 Local MEP
 Remote MEP
 CFM PM Switch
 CFM DM Session
 CFM LM Session
 CES Interface

 Queue Block
 BD LSP
 Management VLAN
 DiffServ Block
To set performance for the switch module in MSPP/NPT:

1. In the MSPP/NPT NE Shelf View window, select the Switch/CS module.
tab.

3. To obtain object data from the NE equipment, in the Display area, select the corresponding button,
and click .
The following window opens, showing, for example, the VSI settings.
4. Modify object parameters as required by selecting the checkboxes in Monitor Active and Auto-Report.

18.3.5 Manage PM monitoring and reporting in IP/MPLS

To manage PM monitoring and reporting for IP/MPLS:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE.
tab.
3. To batch edit the Monitor and Collection attributes, click .

4. Set Statistics as required by selecting the checkboxes.
5. In the Defects Profile dropdown list, select required PM defects profiles for each object.
6. To view details of a selected PM profile, click the button next to the selected profile.
7. Click Apply.
18.3.5.1 Manage L2 PM monitoring and reporting in IP/MPLS

In IP/MPLS NEs, you can view the L2 PM data for the following classes:
 Switch
 VSI
 Tunnel
 MA

 VSI Ethernet Interface

 CES Interface
 VRF LIF
 PW
 PHT PW
To manage L2 PM monitoring and reporting for IP/MPLS:

1. In the IP/MPLS NE Shelf View window, select the CS module.
tab.
3. In the Display area, select the corresponding object.

4. Modify object parameters as required by select the relevant checkboxes.
7. Click Apply.

Manage Ethernet interface PM monitoring and reporting in IP/MPLS
To manage Ethernet IF PM monitoring and reporting for IP/MPLS:

1. In the IP/MPLS NE Shelf View window, select a card or a port.
tab.
3. In the Display area, select Ethernet IF.

7. Click Apply.

Manage LIF PM monitoring and reporting in IP/MPLS
To manage LIF PM monitoring and reporting for IP/MPLS:

1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE, a card or a port.
tab.

3. In the Display area, select LIF.

7. Click Apply.
18.3.6 Manage statistics PM counters in IP/MPLS

Statistics PM counter means the PM is counting continuously, and need not clear the PM counters for each
15 minutes or 24 hours clock boundary.
You can manage statistics PM counters for the following classes:
 AC LIF
 ARP DAI - Interface
 BFD - BDLSP
 BFD - IP
 BFD - Multi Hop IP
 BFD - PW
 BFD - Section

 BFD - Switch
 BGP
 DHCP Relay Agent
 DHCP Snooping Interface
 ERPS
 Firewall Filter
 IGMP Aware VSI (DownStream)
 IGMP LIF
 IGMP Aware VSI (Upstream)
 ISIS Level
 ISIS LIF Level
 ISIS LIF
 LDI - BDLSP
 LDP Entity
 LDP Session
 MSTP
 OSPF Instance
 OSPF LIF
 OSPF Virtual Link
 PHT PW
 PIM Instance
 PIM LIF
 PSC - BDTunnel
 PW
 Switch
 Tunnel
 VRRP LIF
 VRF LIF
 VSI

To manage statistics PM counters in IP/MPLS:

1. In the IP/MPLS NE Shelf View window, select the CS module/card/LAG/port.
2. In the Performance and Performance Settings working mode, select the Statistics tab.
3. In the Display area, select the corresponding object.

5. Click .

c. Click Start Refresh.

18.3.7 Manage performance history in IP/MPLS

In IP/MPLS NE, Unified PM (UMP) is supported. At the end of an interval (15 minutes or 24 hours), MCP
fetches PM information of each object in each IO card and appends it into a single historical PM file. Each
historical PM file is in ASCII CSV format, and stored zipped file in non-volatile memory (e.g. SD). The files are
saved on predefined locations in the NE to allow upload PM files (via FTP and/or SFTP) by other applications
and/or management systems as follows:
Interval period Location Number of files

15 minutes /var/laurel/perfmon/fifteenmin Up to 96 files
1 day /var/laurel/perfmon/oneday Up to 7 files
Current PM counters are recorded per MO by NE, they can be got on-demanded by EMS/CLI. Previous 15
minutes/24 hours PM counters are stored per IO card or per MO by NE in file format. EMS can get Previous
15 minutes/24 hours PM counters by ftp in file format directly.
The unified PM can be supported for the following objects:
 GE/10GE/100GE
 MSME1/PPI/SFP
 Line/Section/STS-1/DS1-Line/DS1-Path

To manage performance history in IP/MPLS:

1. In the IP/MPLS NE Shelf View window, select the CS module/card/LAG/port.
2. In the Performance working mode, select the EMS History tab.

3. In the Display field select a performance class.
5. To view the information in a chart, click .
6. To view the information in a list, click .
7. To export the NE list as an XML file, click .

18.3.8 Manage threshold settings

To manage threshold settings:
1. In an NE Shelf View window, select an Ethernet port.
2. In the Performance working mode, select the Threshold Setting tab.
3. Set the parameters as needed, and click Apply to save your changes.
4. To retrieve the parameters, on the toolbar, click .
5. To copy the settings to other ports, on the toolbar, click the Propagate icon .
18.3.9 View transceiver alarms and warning thresholds

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

To view transceiver alarms and warning thresholds:

1. In an NE Shelf View window, select an optical port.
2. In the Performance working mode, select the Transceiver alarm and warning thresholds tab.
3. To retrieve the parameters, on the toolbar, click .
18.3.10 View invalid MPLS-TP OAM statistics

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

To view invalid MPLS-TP OAM statistics:

1. In an NE Shelf View window, select the Switch Object.
2. In the Performance working mode, select the Invalid MPLS-TP OAM Statistics tab.
 To retrieve the parameters, on the toolbar, click .
 To clear the data, on the toolbar, click .
18.3.11 View TDM/packet engine utilization

You can view the TDM and Packet engine utilization from LCT-NPT via graphical indicator.
Packet Engine Utilization
For packet engine utilization, there are two pointers supported on packet engine dash board:
 One is for "Occupied Network Processor (NP) table or memory resource /maximum NP table or memory
resource on devices", which does not move without change configuration.
 NP shall detect 5 table and memory resources utilization which related to VSI, tunnel /Queues, C-
VLAN groups etc.
 PB Classifications Utilization
 MPLS Classifications Utilization

 PB VSI Interfaces Utilization

 MPLS VSI Interfaces Utilization
 Ingress Tunnel Label Mapping Utilization
 EMS only shows the biggest value with one pointer on the dash board.
 You can also select to view all the 5 table/memory resource utilization.
 The other is for "current real throughput/ maximum switch capacity", which is always moving.
Packet Engine Utilization is supported for the following PEs:
 Central PE of NPT-1200
TDM Engine Utilization
TDM Engine Utilization reflects the utilization of the SDH cross-connect matrix.
TDM engine utilization definition:
 The utilization of NE SDH XC matrix is the ratio of configured total XC bandwidth/physical matrix
capacity. It is a read-only attribute, always taken from NE/MCP, and calculated by MCP according to
system matrix card capacity.
 Deactivated XCs are not included for TDM engine utilization – in case XC is cleared (deactivate all), the
utilization is 0.
 Add/drop VC-4 server XCs are not included for TDM engine utilization.
This attribute is available for TDM or hybrid configuration. Pure packet configuration does not have such
attribute. Following are the NEs without TDM engine utilization:
 NPT-1200 with CPS100/CPS320
 NPT-1021
 NPT-1010
 NPT-1050 with MCPS100

To view TDM/Packet engine utilization:

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

4. To refresh the information automatically:
c. To refresh the TDM/Packet Engine Utilization, click Start Refresh.

18.3.12 View and export laser performance

To view and export laser performance:
1. In an NE Shelf View window, select an optical port.
2. In the Performance working mode, select the Laser Performance tab.

3. To open the laser performance view list:

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

6. To export the laser performance information as a CSV file:

The export window opens.
b. Select the folder location.
c. Enter the file name for the CSV file, and then click Save.
7. To exit the Laser Current Performance window, on the toolbar, click .

18.3.13 Reset performance counters

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

1. In the NE Shelf View window, select the NE or card whose performance counters you want to reset.
2. Select Performance and then PM Reset Counters.
3. Select a type of the PM counters that you want to reset, and then click Yes.
18.3.14 Perform Ethernet interface traffic monitor

To perform Ethernet Interface traffic monitor:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE. Then in the shelf menu,
select Performance > Ethernet Traffic Monitor > Interface.
The Ethernet Interface Traffic Monitor window opens.
2. To add interfaces to the monitor list, click .

3. Click Start Refresh to dynamically observe any data changes.
4. To stop refresh, click Stop Refresh.
5. To clear counters, click .
18.3.15 Perform Ethernet LIF traffic monitor

To perform Ethernet LIF traffic monitor:
1. In the IP/MPLS NE Shelf View window, in the left object tree, select the NE. Then in the shelf menu,
select Performance > Ethernet Traffic Monitor > LIF.
The Ethernet LIF Traffic Monitor window opens.
2. To add LIFs to the monitor list, click .

3. Click Start Refresh to dynamically observe any data changes.
4. To stop refresh, click Stop Refresh.
5. To clear counters, click .

18.3.16 Built-in RFC2544 test management

The built-in RFC2544 tester includes packet generator and analyzer which enable RFC2544 test between two
access ports for any E2E service; it provides an on-demand service OAM mechanism to measure the service
performance (throughput). The RFC2544 test port can connect to one UNI port of any VSI in central PE and
simulate the external LAN analyzer to perform RFC2544 test.
Figure 18-5: Support one-way test between 2 built-in testers
In the above figure:

 The tester above is supported by FPGA;
 The tester will send packets to NP through an internal SGMII port, just simulate the test traffic from the
access port of the VSI;
 One-way mode: Test traffic generated from CPE#1 will be terminated in CPE#2, vice versa.
Built-in RFC2544 tester in central switch for below products can be supported:
 NPT-1200 – 2 test ports
 NPT-1020/NPT-1021 – 1 test port
 NPT-1010 – 1 test port
 NPT-1800
 NPT-1200i
The port of built-in RFC2544 tester can be enabled or disabled (default is disabled.). Only the enabled tester
port can be connected to a VSI access (PB UNI/ENNI) port.
 If port is enabled, both directions are enabled, the port can generate or terminate packets.
 If port is disabled, the port can neither generate nor terminate packets.
NOTE: Since loopback with MAC or IP address swapping is not supported in V6.0, only one-way
test is supported, round-trip test is not supported.

18.3.16.1 Configure test connections in NPT

The following services support RFC2544 test connection configuration:
 EPL
 PB PtP
 PB MPtMP
 MPLS PtP
 MPLS MPtMP
The following ports with E-NNI/UNI port type support RFC2544 test connection configuration:
 FE port
 GE port
 10GE port
 WAN port
This section describes how to configure test connection for NPT-1200 and NPT-1020. Test connection
configuration in NPT-1010/NPT-1050/NPT-1021 is the same as NPT-1200.

To configure test connections in NPT-1200:

1. In the NPT-1200 NE Shelf View window, select the NE.
2. In the Performance working mode, select the RFC2544 Test Port 1/RFC2544 Test Port 2 tab, and then
the Test Connection sub-tab.
3. You can enable the test port, select the Enabled checkbox in the Port Enable field.
4. To connect the enabled tester port to a VSI access:
a. Select the Connected checkbox.
b. Select the relevant VSI and Tested Port.
5. Click Apply.

To configure test connections in NPT-1020:

1. In the NPT-1020 NE Shelf View window, select the NE.
2. In the Performance working mode, select the RFC2544 Test Port 1 tab, and then the Test Connection
sub-tab.
3. To enable the test port, in the General area, select the Enabled checkbox in the Port Enable field.
4. Select an Idle EoS Port from the dropdown list.
UNI EoS ports without VCG/LAG/MIP of activated MEoS_8 card are available in idle EoS port attribute
for NPT-1020 with CS10/CS50.
5. To connect the enabled tester port to a VSI access:
a. In the Test Connection Configuration area, select the Connected checkbox.
b. Select the relevant VSI and Tested Port.
For the attributes of the test connection:
 EPL/PB PtP/PB MPtMP/MPLS PtP/MPLS MPtMP activated VSIs are available in VSI attribute.
 PB UNI/ENNI (LAG is not supported) ports (including FE/GE/10GE/EoS) are available in Tested Port
attribute.
 Only the enabled tester port can be connected to a VSI access (PB UNI/ENNI) port.
6. Click Apply.

18.3.16.2 Manage RFC2544 tests in IP/MPLS

To manage RFC2544 tests:
2. In the Performance working mode, click the RFC2544 Test tab.

3. To create RFC2544 test, click .

The Create RFC2544 Test window opens.

4. Click Apply.
The RFC2544 test is created.
 To connect a RFC2544 test, select the RFC2544 test, then click .

 To disconnect a RFC2544 test, select the RFC2544 test, then click .
 To edit a RFC2544 test, select the RFC2544 test, then click .
 To view a RFC2544 test, select the RFC2544 test, then click .

 To delete a RFC2544 test, select the RFC2544 test, then click .
5. To synchronize the data between NE and database, select the RFC2544 test and then click .
6. To view the test result:
a. Select the RFC2544 test.
b. Set the Refresh Interval as required.
18.3.16.3 Configure test parameters

Test parameters can be configured only when this test port is connected to a service port to be tested.
It is supported in the NPT-1200/NPT-1020/NPT-1021/NPT-1010/NPT-1050/NPT-1800 NEs.

To configure test parameters:

1. In the NPT NE Shelf View window, select the NE. In the Performance working mode.
2. Select the RFC2544 Test Port tab, and then the Test Parameters sub-tab.
3. Configure the test parameters as required.

18.3.16.4 View test statistics

Viewing test statistics is supported in the NPT-1200/NPT-1020/NPT-1021/NPT-1010/NPT-1050/NPT-1800.

To view test statistics:

1. In the NPT NE Shelf View window, select the NE.
2. In the Performance working mode, select the RFC2544 Test Port tab, and then the Test Statistics sub-
tab.
 To start transmit, click .
 To stop, click .
 To clear transmit counters, click .
 To clear receive counters, click .

3. To refresh data dynamically:
a. Select the Refresh data dynamically checkbox.
b. Set the Refresh Interval, and then click the Start Refresh button.
To stop refresh, click Stop Refresh.

18.3.17 Build-in Y.1564 test management

Y.1564 allows simultaneous testing of multiple Ethernet services and measures. It also validates the different
QoS mechanisms provisioned in the network to prioritize different service types - allowing faster deployment,
easier service and network troubleshooting.
One alternative measurement connection is to use a port loopback at one measurement point and make all
measurements in a round-trip connection performed by a single built-in Y.1564 tester. There are significant
issues and limitations inherent to loopback connectivity, including:
 The network device performing the loopback may dominate the performance levels measured.
Overload testing on shared devices can affect the performance of other services.
 Unless symmetrical link speeds, traffic profile, QoS configuration, and frame routing are present
throughout the measured path, measurement errors can occur in any of the performance parameters.
 It is unreliable and likely inaccurate to perform tests of excess traffic or bursts and attempt to infer
results for the return-from-loopback direction.
Where the precision of a one-way test is not needed, a logical loopback device can be used at one end in
combination with built in test equipment at the other end to provide a round-trip measurement of service
performance.
Round-trip test can avoid the clock synchronization between the different NEs.
If MAC swap is supported at the remote device with port or EVC loopback, then the round-trip test can be
used for both PtP and MPtMP service.
If MAC swap is not supported at the remote device with port or EVC loopback, then the round-trip test can
only be used for PtP service.
The map between test mode and GTF/CTF resources per test profile whose connection is enabled:
 One-way-Tx - 1 GTF
 One-way-Rx - 1 CTF
 One-way-TxRx - 1 GTF + 1 CTF
 Round-trip-TxRx - 1 GTF + 1 CTF
 Round-trip-loopback - 1 GTF + 1 CTF
built-in Y.1564 test is supported in following NEs:
 NPT-1800
 NPT-1200i with MCIPS320

18.3.17.1 Manage Y.1564 tests in IP/MPLS

To manage RFC2544 tests:
2. In the Maintenance working mode, click the Y.1564 > Test Configuration & Result.

3. To create Y.1564 test, click .

The Create Y1564 Test window opens.

4. Click Apply.
The Y.1564 test is created.
 To connect a Y.1564 test, select the Y.1564 test, then click .

 To disconnect a Y.1564 test, select the Y.1564 test, then click .
 To edit a Y.1564 test, select the Y.1564 test, then click .
 To view a Y.1564 test, select the Y.1564 test, then click .

 To delete a Y.1564 test, select the Y.1564 test, then click .
5. To synchronize the data between NE and database, select the RFC2544 test and then click .
6. To view the test result:
a. Select the Y.1564 test.
b. Set the Refresh Interval as required.

18.3.17.2 View Y.1564 test report

To view Y.1564 test report:
1. In the IP/MPLS NE Shelf View window, select the NE.
2. In the Maintenance working mode, select Y.1564 > Test Report.
4. To export the report data, click .

18.3.17.3 View Y.1564 test report from EMS

To view Y.1564 test report from EMS:
1. In the LCT-NPT main window, from the menu, select Maintenance > Y.1564 Test Report.
The Y.1564 Test Report window opens.
3. To export the report data, click .

19 Maintenance operations
This section discusses how to perform routine maintenance operations on the cards and internal objects.
19.1 Preventive maintenance operations

This section describes how to perform preventive maintenance operations.
19.1.1 Save NE configuration data

This operation is only available for the BG-40 NE. You can manually save all BG-40 NE configuration data to
the flash and use it to restore the BG-40 NE when necessary.
To save NE configuration data:

 In the BG-40 NE Shelf View window, select Maintenance and then Save NE Configuration.
19.1.2 Clear NE configuration data

This operation restores all configurations within an NE to their initial status by clearing all configuration data
in the NE equipment, including data and trail information.
To clear NE configuration data:

1. In the NE Shelf View window, select Maintenance and then Clear NE's Configuration.
2. In the confirmation, click Yes to confirm.
19.1.3 Test connectivity

This operation sends a ping to the NE equipment to verify the connection to the NE equipment. The ping
checks the connection between a local host and the network by sending one Internet Control Message
Protocol (ICMP) ECHO packet to the host over the network, and subsequently monitoring the returned ECHO
REPLY packet. This operation can only be performed at the system operation level.
To perform connectivity testing:

1. In the EMS topology view, select an NE, and select Maintenance and then Ping.
The following Ping window opens.

LCT-NPT® User Guide Maintenance operations
2. Set the size of a ping test packet by entering a numeric value in the Package Size field.
3. Click Ping.
The returned ping results are displayed.
4. To cancel the ping test, click Stop Pinging.

5. To clear the contents in the display area, click Clear Result.

19.1.4 Perform 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 LCT-NPT DB to maintain consistency between the LCT-
NPT and the equipment. An option is available to optimize the fully upload.
To perform a full upload:

1. In the NE Shelf View window, in the left object tree, select the NE, and from the menu, select
Maintenance and then Fully Upload NE Data. The following Confirmation window opens.

3. To view the upload status, from the main menu, select Maintenance and then View Upload Status.
4. To view the detailed information of the upload status, click the Details button.

19.1.5 Perform a LED test

All LEDs within an NE can be tested to verify the quality of the indicator hardware, and to improve the
reliability of the alarm indicator indications.
To perform a LED test:

1. In the NE Shelf View window, select Maintenance and then Test LED.
2. In the confirmation window, click Yes to perform test operations.
19.1.6 View bit codes

Built-In Test (BIT) provides the ability to reveal hardware failures in real time. There are three types of BIT:
 Power Up BIT: Power up BIT must take power up time into consideration (not to exceed power up time
limitation). Note that Power up BIT does not have traffic considerations (since there is no traffic in
power up), and can be destructive (can run tests that require initialization of HW devices on test
complete), can use devices testing mode, can consume most of the CPU resources (there is no other
important activity running on this time), etc.
 Periodic BIT: Periodic BIT must be non-traffic affecting.
 Maintenance BIT
This section describes how to view the Bit codes in LCT-NPT.
To view Bit codes:

1. In the NE Shelf View window, select a card.
2. Select Maintenance and then Bit Code.
The Bit Code window opens.

3. To retrieve the information, click .
19.1.7 Manage defined bit codes

You can manage defined BIT code for the following cards:
 All XIO cards
 MXC-1020
 MXP10
 DHFE_12
 DHFX_12
 CPTS100
 CPS100
 DMGE_4_L2
 DMGE_8_L2
 DMXE_22_L2
 DMXE_48_L2
 MPS_2G_8F
 MPoE_12G
 S1_4

To manage defined Bit code:

2. Select Maintenance and then Defined Bit Code.
The Defined Bit Code window opens.
3. To reload the information to view, on the toolbar, click .
4. To export the defined BIT code list to a CSV file, on the toolbar, click .
The export window opens.
6. Enter the file name for the CSV file, and then click Save.

19.1.8 View PPI status

The LCT-NPT supports a Get PPI Status feature, which queries a loss of signal on each PDH interface. The PPI
status can be used to verify the cable connection status when installing the equipment. The PPI status is
obtained directly from the hardware and is not affected by the alarm filter.
To view the PPI status:

1. In the NE Shelf View window, select an E1/E3 card.
2. In the Maintenance working mode, select the PPI Status tab.
3. To refresh the information manually, click .

4. To refresh the information automatically:
c. To refresh the PPI status, click Start.
d. To terminate the refresh process, click Stop.

19.1.9 Perform preventive maintenance

The following table describes the preventive maintenance procedures you must carry out to ensure proper
operation.
Table 19-1: LCT-NPT preventive maintenance procedures

Procedure When to perform
Save the NE DB configuration to Once a week, or following major changes in network topology
hard disk
Check version correspondence Once a week, or whenever major changes are made to system
configuration
Delete old system files Once a week, or following major changes in network topology
Check performance Once a week, or according to working procedures
Check LCT-NPT to NE Once a week, or according to working procedures
communications
Save the LCT-NPT configuration Once a week, or following major changes in network topology
to hard disk
Check switching to protection Once a quarter, according to network administrator's instructions
Note: This operation is traffic-affecting.
Export XC data to XML files Once a month, or according to working procedures
Check optical parameters Once a month, or according to working procedures
Export topology data to an XML Once a month, or according to working procedures
file
Export card inventory data to Once a month, or according to working procedures
an XML file
19.2 Card maintenance

This section explains how to reset and maintain cards.
19.2.1 Reset a card

When the physical device of a card does not work normally and needs to be initialized, a Card Reset operation
is performed. Both warm and cold resets are available.
A warm reset resets only the central processing unit of the cards, namely, it repositions the running of card
usage programs. A cold reset resets both the central processing unit and the peripheral hardware. Warm
resets do not affect traffic; cold resets do.
MXC-1020 supports Power on reset, which means the software can be used to power on the MXC-1020
directly.

To reset a card:
2. Select Maintenance and then Reset. The Reset Card window opens.
3. Select the reset mode, and then click OK.
4. A confirmation window opens, prompting you to confirm the reset.
To perform Power on reset:

1. In the NPT-1020 NE Shelf View window, select an MXC-1020 card.
2. Select Maintenance and then Reset.
The Reset Card window opens.
3. Select Power on reset, and then click OK.
A confirmation window opens, prompting you to confirm the reset.
19.2.2 Manage OTN wrapping for STM-16/64 interface in

CPTS100
For OTU1 interface:
You can set OTN enable/disable for SAM25_2 STM-16 interface. The attribute "OTU1 Wrapper" defines
whether STM-16 will be mapped to ODU1/OTU1 and becomes an OTU1 uplink. When OTU1 Wrapper is
enabled, the port becomes an OTU1 port, and relevant OTN objects shall be created:
 ODU1
 OTU1
For OTU2 interface:
You can set OTN enable/disable for SAM10 STM-64 interface. The attribute "OTU2 Wrapper" defines whether
STM-64 will be mapped to ODU2/OTU2 and becomes an OTU2 uplink. When OTU2 Wrapper is enabled, the
port becomes an OTU2 port, and relevant OTN objects are created:
 ODU2
 OTU2

To configure OTN Wrapping for STM-16/64 interface:

1. In the NPT-1200 NE Shelf View window, select the oPort (STM-64)/oPort (STM-16) under
SAM10/SAM25_2.
2. In the Configuration working mode, select the OTN Setting tab.
3. You can enable the OTN Wrapper as required.

The default is disabled.


You can view the oPort (OTN) in the object tree.
19.2.3 Manage OTN wrapping for 10GE interface in

CPTS100/CPS100
From NPT-1200 V3, CPTS100 10GE ports support OTN encapsulation. The two 10GE ports of CPTS100
(AMXE_2) can support OTN encapsulation based on the 10GE PHY.
Following are the PHY types supported in 10GE port of AMXE_2:
 10GBase-R
 10GBase-W
 10GBase-R with OTU2e Mapping
 10GBase-W with OTU2 Mapping
You can activate or deactivate OTN by changing the PHY type. Relevant OTN objects will be created if the PHY
type is set as OTN mapping:
 10GBase-R with OTU2e Mapping --> OTU2e, ODU2e
 10GBase-W with OTU2 Mapping --> OTU2, ODU2

To activate/deactivate OTN for 10GE interface:

1. In the NPT-1200 NE Shelf View window, select the activated 10GE port under AMXE_2.
3. You can activate or deactivate OTN by changing the PHY type.

4. Click Apply to activate the OTN for the 10GE interface.
19.2.4 Manage OTN in XIO64

The OTN-XFP module can work in two modes:
 OTN mode: OTN enabled
 OTN Bypass mode: OTN disabled. FEC is not supported in this mode.
When the OTN is enabled, the following objects are created:
 OPS: with alarm monitor; not displayed in the object tree.
 OTU2: with default OTU2 setting, alarm monitor, performance monitor, and TCA.
 ODU2: with default ODU2 setting, alarm monitor, performance monitor, and TCA.

To manage OTN-XFP:
1. In the BG-64/NPT-1200 NE Shelf View window, select the oPort under XS A:SAM64.
2. In the Configuration working mode, select the XFP Setting tab.

3. From the Expected SFP Type dropdown list, select OTRN10.
4. In the OTN XFP area, configure the attributes as described below:

 Operation Mode:
 OTN Enable
 OTN Bypass
 FEC Control: GFEC, EFEC or Off. It is only configurable when OTN is enabled.
 Selected Wavelength: 20 (192.0THz) or 21 (192.1THz).
6. A warning window opens, prompting you to confirm this action. Click Yes to continue.

To configure the parameters for OTU2:

1. In the object tree, select the OTU2 object.
3. Configure the parameters, and then click Apply.

To configure the parameters for ODU2:

1. In the object tree, select the ODU2 object.
3. Configure the parameters, and then click Apply.
19.2.5 Performing Basic Parameter Backup in SFP

This section describes how to back up basic parameters in SFP for BG-20 NEs.

To back up basic parameters in SFP:

1. In the BG-20 NE Shelf View window, on the menu, select Maintenance and then Backup Basic
Parameter in SFP. The following window opens.

2. In the left-hand NE list, select the NE by checking the corresponding checkbox.
3. To obtain information to view, on the toolbar, click .
4. In the Backup NE Basic Parameter in SFP list, select the checkbox as required, and click Apply to back
up the corresponding parameters.
19.3 SFP/SFP+/XFP/CSFP management

The Small Form-factor Pluggable (SFP) is a compact, hot-pluggable transceiver used for both
telecommunication and data communications applications. The form factor and electrical interface are
specified by a multi-source agreement (MSA). It interfaces a network device motherboard (for a switch,
router, media converter or similar device) to a fiber optic or copper networking cable.
The enhanced small form-factor pluggable (SFP+) is an enhanced version of the SFP that supports data rates
up to 16 Gbps.
The 10 Gigabit small form-factor pluggable (XFP) is a standard for transceivers for high-speed computer
network and telecommunication links that use optical fiber.
The Compact Small Form Factor Pluggable (CSFP) optical transceiver is a bidirectional single fiber optical
module designed for point-to-point application. The CSFP includes two SFP channels in one socket, and two
ports can be associated with one CSFP module.

19.3.1 Obtain the SFP type

The SFP type has two parameters that can be configured:
 Expected SFP Type
 Application Code
This section describes how to obtain the SFP type.
To obtain the SFP type:

1. In the NE Shelf View window, select an oPort.
2. In the Configuration working mode, select the SFP Setting tab.
3. Select the required Expected SFP Type and the Application Code from the respective dropdown lists.

5. To view WDM information of the SFP:

a. Select an oPort under the card that supports viewing actual WDM information.
b. In the Configuration working mode, select the SFP Setting tab.
The following WDM information is displayed:

 Module sub-type
 Application code
 Number of supported channels
 WDM first channel number
 Channel spacing
19.3.1.1 Support for 3rd party SFP

From V4, LCT-NPT supports 3rd party SFPs that have no vendor ID programmed in A2 128. In some cases, you
can buy SFPs from additional vendors. You can use 3rd party SFPs in all cards in NPT-1010/1020/1200/1050,
if your license supports it.

19.3.1.2 Support GPON stick SFP

GPON stick SFPs are identified as GTGBE_L3BD. GPON stick SFP can be supported on SFP ports of MGE_12
and MGE_8 in NPT V4.
For MGE_12 and MGE_8 cards, if port PHY type is 1000base-X, the SFP type can be set as GTGBE. When
GTGBE is set, the ALS is set to disable and is grayed out.
To set GPON stick SFP:

1. In the NPT NE Shelf View window, select port 9~12 of MGE_12 or port 5~8 of MGE_8.
2. Click Configuration and then select the SFP Setting tab.
3. In the Expected SFP Type dropdown list, select GTGBE.

When GTGBE is set, the ALS is set to Disable and is grayed out.

19.3.2 Manage T-SFP+ settings

T-SFP+ is tunable Dense wavelength division multiplexing (DWDM) SFP+ module, which wavelength (or
frequency) is configurable between full ITU-T C-band channels with channel spacing of 50GHz.
Following lists the T-SFP+ supported cards:
 CPTS100 – two 10GE ports of AMXE_2 (NPT-1200)
 DMXE_48_L2 – four 10GE ports (NPT-1200)
 DMXE_22_L2 – two 10GE ports (NPT-1200)
 CPS50 – two 10GE ports (NPT-1020/NPT-1021)
To manage T-SFP+ settings:

1. In the NPT-1200 NE Shelf View window, select a 10GE port under the T-SFP+ supported cards.
2. In the Configuration working mode, select the SFP+ Setting tab.
3. From the Expected SFP Type list, select OTP10T/OTP10T_2/OTP10T_17.

The T-SFP area is displayed.

The parameters are described as below:

 Channel Selection
 Channel Frequency (f): Laser frequency of desired DWDM channel.
 Wavelength: Corresponding laser wavelength in nm concluded from the frequency input.
 Tuning Capability
 Frequency Tuning: Tunable DWDM (selection by channel, bytes 144-145).
 Wavelength Tuning: Tunable DWDM (selection in 50pm steps, bytes 146-147).
 Tx Dither Support: Support for Tx dithering.
 Tunable Range
 First Frequency: Laser first frequency in THz, read from actual SFP+.
 Last Frequency: Laser last frequency in THz, read from actual SFP+.
 Minimum Supported Grid Spacing: Laser minimum supported grid spacing in GHz, read
from actual SFP+.
 Tx Dither Setting
 Tx Dither: Enable Tx Dither or disable Tx Dither.

19.3.3 Manage XFP

This section describes the management of the tunable-XFP (T-XFP) and OTN-XFP in STM-64, including:
 Manage T-XFP
 Manage OTN-XFP
 View Serial ID
OTR10T_AL is a tunable DWDM XFP, and its wavelength (or frequency) is configurable between full ITU-T C
band channels with channel spacing of 50 GHz.
When OTN-XFP is assigned to a STM-64 port with OTN enabled, the port becomes an OTN interface (ONNI).
It can be connected to a port with the same OTN rate (OTU2) and it cannot be connected to an STM-64 port
without OTN XFP.
NOTE: From CPTS100 in LCT-NPT V3, OTN-XFP (OTRN10_AL) can be assigned but OTN function
cannot be enabled – always work in “OTN pass through” mode, DWDM relevant configuration
remains as before. OTRN10 is handled as a regular tunable DWDM XFP.

To manage T-XFP:
1. In the BG-64/NPT-1200 NE Shelf View window, select the oPort under XS A:SAM64.
2. In the Configuration working mode, select the XFP Setting tab.

3. From the Expected SFP Type list, select OTR10T.

View the relevant parameters in the window that opens.

To view XFP serial ID:

 In the BG-64/NPT-1200 NE Shelf View window, select the oPort under XS A:SAM64.
 In the Configuration working mode, select the Serial ID tab.

19.3.4 Configure SFP/CSFP settings

You can configure the SFP/CSFP settings for the Port1~Port4 of DHGE_8, or Port9~Port12 of DHGE_16, or
Port1~Port12 of DHGE_24 with port activated.
To configure SFP/CSFP settings:

1. To define port rate and density, right-click the DH card and select Define Port Rate and Density.
The Define Port Rate and Density window opens.
2. Set the port rates as Signal-SFP/SFP+ or Dual-CSFP from the lists, and then click Apply.

3. In the NPT-1200 NE Shelf View window, select an activated GE port of DHGE_8/DHGE_16/DHGE_24.

4. In the Configuration working mode, select the SFP/CSFP Setting tab.
5. Set Expected SFP Type and Expected Application Code as required.

6. If the port with the port rate type Dual-CSFP and CTGBE is assigned as Expected SFP Type, then Port[n],
Port[n+4] of the DH card will be created.
7. You can view the new created port (Port 7 under DHGE_8) in the left object tree, as shown in the
following figure.

19.4 Transmission object maintenance operations

The LCT-NPT enables you to perform maintenance operations on transmission objects.
19.4.1 Use the maintenance list

The LCT-NPT conveniently provides a graphical symbol above the NE icon in the main topology view,
indicating that a maintenance operation has been performed on it. In addition, it also enables you to view a
list of the maintenance operations performed on an NE.
To use the maintenance list:

1. In the NE Shelf View window, select the working mode Maintenance and then the Maintenance List
tab.
Or

In the main topology view, select one or more NEs, and select Maintenance and then Maintenance
List. You can manage the NEs in the Muti-NE window.
2. To release maintenance operation data, select an operation from the list, and on the toolbar click
, or right-click and select Release from the shortcut menu.
19.4.2 Perform/release loopback

The loopback operation is designed to aid in testing the service path and service interface. In this context,
loopback refers to a software loopback, meaning that it is set through the LCT-NPT.
After an E2E trail has been configured, a loopback can be used to test whether the whole path works normally
and whether meters receive and send consistently. The absence of an error code indicates that everything is
working normally.
The loopback operation includes:
 Terminal (NE) loopback: Looping back signals from the XC unit to the same unit. The terminal loopback
operation can be used to test the flow of signals in the system.
 Facility (FE) loopback: Directly looping back signals received by the physical port to the output port
corresponding to it, without changing the signal structure. The facility loopback operation can be used
to test the connector.

NOTE: The loopback operation affects traffic.
To perform a loopback:
1. In the NE Shelf View window, select a card that has undergone maintenance and requires a loopback.
2. In the Maintenance working mode, select the Loopback tab.
3. Modify loopback parameters as required by selecting a loopback from the Loopback Type list.

4. To batch edit the loopback type:

b. Click to select the required operation.
To release a loopback:
1. Select the Maintenance List tab.
2. Next to the Loopback tab, click to refresh the data in the list.
From the list, you can see the loopback operations that you performed.
3. Select the loopback you want to release, and click , or right-click the loopback and then select
Release.

19.4.3 Perform AIS/RDI

To perform AIS/RDI:
1. In an NE Shelf View window, under all optical interface and service cards, select the VC-4/VC-3/VC-12
or MS/RS module.
2. In the Maintenance working mode, select the Force Signal tab.
3. From the DownStream list, select the operation to be performed (None or AIS).
4. From the UpStream list, select None, AIS, or RDI.
5. To insert the AIS/RDI, click Apply.

19.4.4 Perform PRBS

To perform a PRBS:
1. In the NE Shelf View window, select the required card and then select VC-4 or PPI.
2. In the Maintenance working mode, select the PRBS tab.
3. In the Generator Side area, perform PRBS generation as follows:

a. Set the Switch mode to On.
b. Specify the Generator Pattern.
c. Select the Invert Signal checkbox.
d. In the Direction field, select the Upstream or Downstream button.
e. Click Apply.
f. To insert an additional error bit, click the Add single bit error icon .
4. In the Monitor Side area, perform PRBS monitoring as follows:
a. Set the Switch mode to On.
b. Specify the Generator Pattern.
c. Select the Invert Signal checkbox.

d. In the Direction field, select the Upstream or Downstream button.

e. Click Restart. The error code is added to the Counter.
f. To refresh the Counter value, click Refresh.
5. To retrieve the current status, on the toolbar click .
19.4.5 Switch to protection

The LCT-NPT provides the following options for switching to protection:
 Manual Switch: Only if the protected object has no alarms on it. Manual switch is a persistent command
and can be removed only by clearing it. It has a lower priority than alarms, which means that a manual
switch returns to the main object if the protected object has an alarm on it.
 Force Switch: Switching to protection is made from the active object to the backup object. In this mode,
traffic is switched permanently, even if conditions do not require automatic switching.
 Lockout: Switching to protection is prevented, even if conditions require automatic switching. Lockout
remains in effect until the action is released.
To switch to protection:
1. For the XIO cards, in the NE Shelf View window, select the Main XIO card.
2. In the Maintenance working mode, select the Equipment Protection Switch tab.

3. Set the protection switch by selecting a mode in the Switch Command area and then click Apply to save
the settings:
 Release: Removes current maintenance operations and enters automatic mode.
 Force Switch to XS A: Switches XIO30 A to active state and XIO30 B to standby state, regardless
of a failure in XIO30 A, unless high-priority conditions exist (e.g. a lockout, the XIO30 A is not
present, or the FPGA is not loaded).
 Force Switch to XS B: Switches XIO30 B to active state and XIO30 A to standby state, regardless
of a failure in XIO30 B, unless high-priority conditions exist (e.g. a lockout, the XIO30 B is not
present, or the FPGA not loaded).
 Lock out of Protection: Standby card is locked out and cannot be used by protection.
 Manual Switch to XS A: Switches XIO30 A to active state and XIO30 B to standby state, unless
XIO30 A is in a failure state or high-priority conditions exist (e.g. a forced switch, lockout, the
XIO30 A is not present, or the FPGA is not loaded).
 Manual Switch to XS B: Manually switches to XS B, which means that XIO30 B is switched to active
state and XIO30 A is switched to standby state, unless XIO30 B is in a failure state or high-priority
conditions exist (e.g. a forced switch, lockout, the XIO30 B is not present, or the FPGA is not
loaded).
19.4.6 Set the link down status

For an EoP port, the link down status can be set as:
 Force Link Down
 Release

To set the link down status for an EoP port

1. In the left object tree, select an EoP port.
2. In the Maintenance working mode, select the Force Link Down tab.
3. Select the Link Down Status as and then click Apply.

19.4.7 CES maintenance

This section describes the CES maintenance that can be performed on the E1 objects with CES service.
19.4.7.1 Force CES signal

To force CES signal:
1. In the NE Shelf View window, under a CES card, select an E1 port with CES service.
2. In the Maintenance working mode, select the Force CES Signal tab.
3. You can force L bit or force R bit by selecting the corresponding checkbox.

19.4.7.2 Configure timing commands

To configure timing commands:
1. In the NE Shelf View window, under a CES card, select an E1 port with CES service.
2. In the Maintenance working mode, select the Timing Commands tab.
3. You can set the timing command by selecting the corresponding radio button:
 None
 Reset clock recovery mechanism
 Move clock recovery state to FreeRun
 Force clock recovery state to Holdover
 Release clock recovery state from Holdover
4. Click Apply.

19.5 Timing maintenance

This section describes maintenance operations that can be performed on timing objects and TMUs.
19.5.1 View TMU working mode

You can determine the TMU working mode by querying the current clock working mode and the clock
reference of the NE.
The clock working mode can be one of the following:
 Capture mode
 Tracing mode
 Holding mode
 Free oscillation mode
To view the TMU working mode for BG-40/BG-20 NE:

1. In the BG-40 NE Shelf View window, select Control and Physical Object and then MXC4X. In the
Maintenance working mode, select the Timing Maintenance tab.
Or
In the BG-20 NE Shelf View window, select Control and Physical Object and then the TMU object. In the
Maintenance working mode, select the Timing Maintenance tab.

2. To retrieve the TMU work mode, on the toolbar click .
To view the TMU working mode for BG-30/BG-64/NPT NE:

1. In the BG-30/BG-64/NPT NE Shelf View window, select Control and Physical Object and then the XS
A:TMU/BS:TMU object.
Or
In the BG-20C NE, select TMU. In the Maintenance working mode, select the Timing Maintenance tab.
The following window opens, in which you can view the Main TMU Working Mode and the Standby
TMU Working Mode.
2. To retrieve the TMU work mode, click .

19.5.2 Forcing the Timing Source

Even if the system has made a different selection, the LCT-NPT enables you to force a specific timing source
based on the quality of the sources and the priorities assigned.
To force the timing source:

1. In the NE Shelf View, select the Timing Maintenance tab as described in Viewing TMU Working Mode.
2. In the Timing list, select an object and right-click, as shown in the following figure.
The following operations can be performed from the right-click menu:

 Lockout
 Release Lockout
 Forced Switch
 Manual Switch
 Clear

19.6 SNMP configuration

This section describes how to manage SNMP configuration for BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-
1020/NPT-1021/NPT-1010/NPT-1050 NEs. This includes managing users, managing groups, managing views,
managing contexts, managing accesses, and managing traps.
When integrated with third party SNMP network management, you can manage the SNMP V3 configuration
as described in this section.
All SNMP configuration functions are performed from the SNMP Configuration window that displays the
following information:
 General
 Users
 Groups
 View
 Context
 Access
 Traps
19.6.1 Enable/disable the SNMP V1/V2c agent

To enable/disable SNMP V1/V2c agent:
1. In NE Shelf View window, select the NE.
2. Select Configuration and then SNMP User.
The SNMP Configuration window opens.

3. Select the checkbox to enable the V1/V2c agent.

To disable the agent, clear the checkbox.
4. To get community from NE, click .

If community is blank, it cannot be applied to NE.
5. Click Apply.
19.6.2 Manage SNMP users

To manage an SNMP user:
1. In NE Shelf View window, select the NE.
2. Select Configuration and then SNMP User.

3. To add a user, in the left-hand list, select User, or select SNMP V3 and then User, and then click Add.
The Add User window opens.

 User Name: name of user (must be unique). At most, you can add 20 users.
 Authentication Protocol: can be set as None, MD or SHA (default None).
 Authentication Key: only available when Authentication Protocol is MD or SHA. The length of
the string cannot be less than 8 and not more than 32.
 Privacy Protocol: can be set as None or DES (default None).
 Privacy Key: only available when Privacy Protocol is MD or SHA. The length of the string cannot
be less than 8 and not more than 32.
5. Click Apply.

To edit a user:
1. In the user list, select the user you want to edit, and click Edit.
The Edit window opens.
2. Edit the information that you want to change, and click Apply.

To view detailed information of a user:

 Select the user in the left-hand list. The information is displayed in the right area of the window.
To delete a user:
 In the SNMP user list, select the user you want to delete and then click Delete.

19.6.3 Manage SNMP groups

To manage SNMP groups:
1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window,
select the NE.
2. Select Configuration and then SNMP V3.

3. To add a group, in the left-hand list, select Group, or select SNMP V3 and then User Group, and then
click Add.
The Add Group window opens.
4. Complete the fields as required:

 Group Name: the name of the group (must be unique). At most, you can add 20 groups.
 User: Select at least one user for the group.
To edit a group:
1. In the group list, select the group you want to edit, and then click Edit.
2. Edit the information you want to change, and then click Apply.
To view detailed information of a group:

 Select the group in the left-hand list. The information is displayed in the right area of the window.
 To view the users in the group, select the User List tab.
To delete a group:
 In the SNMP group list, select the group you want to delete and then click Delete.

19.6.4 Manage SNMP views

To manage SNMP views:
1. In the NE Shelf View window, select the NE. Select Configuration and then SNMP V3. The SNMP
Configuration window.

2. To add a view, in the left-hand list, select View, or select SNMP V3 and then View and then click Add.
The Add View window opens.

 View Name: name of the view (must be unique). At most, you can add 20 views.
 Oid Name: The Oid name should start with dot and only allow number such as .1.2.3.
 Include: Select the checkbox as required.
4. Click Apply.
To edit a view:
1. In the view list, select the view you want to edit and then click Edit. T
The Edit View window opens.
2. Edit the information that you want to change, and then click Apply.
To view detailed information of a view:

 Select the view in the left-hand list. The information is displayed in the right-hand side of the window.
To delete a view:
 In the SNMP view list, select the view you want to delete and then click Delete.

19.6.5 Manage SNMP contexts

To manage SNMP contexts:
1. In the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window,
select the NE.
3. To add a context, in the left-hand list, select Context, or select SNMP V3 and then User Context.

4. In the right area of the window, click Add.

The Add Context window opens.
5. Enter the Context Name (must be unique). You can add a maximum of 20 contexts.
To view detailed information of a context:

 Select the context in the left-hand list.
The information is displayed in the right-hand area of the window.
To delete a context:
 In the SNMP context list, select the context that you want to delete and then click Delete.

19.6.6 Manage SNMP access

To manage SNMP access:
1. In the BG-20/BG-20C/BG-30/BG-64/NPT NE Shelf View window, select the NE.
3. To add an access, in the left-hand list, select Access, or select SNMP V3 and then User Access.

4. In the right area of the window, click Add.

The Add Access window opens.
5. Complete the fields as required:

 Access Name: Name of the access (must be unique). At most, you can add 20 accesses.
 Group Name: Select a group you have created.
 Context: Select a context you have created.
 Security Level: Can be set as None, AuthNoPriv, or AuthPriv (default None).
 Read View: Select a view you have created as read view.
 Write View: Select a view you have created as write view.
 Trap View: select a view you have created as trap view.

To edit the access:

1. In the access list, select the access you want to edit, and then click Edit.
The Edit Access window opens.
2. Edit the information you want to change, and click Apply.
To view detailed information of an access,

 Select the access in the left-hand list. The information is displayed in the right-hand area of the window.
To delete an access:
 In the SNMP access list, select the access you want to delete and then click Delete.

19.6.7 Manage SNMP traps

To manage SNMP traps:
1. In the BG-20/BG-20C/BG-30/BG-64/NPT NE Shelf View window, select the NE.
3. To add a trap, in the left-hand list, select Trap, or select SNMP V3 and then User Trap.

4. Click Add.
The Add Trap window opens.
Complete the fields as required:

 Version: Can be set as V1, V2C, or V3. If it is set as V1 or V2C, the User Name and Security Level
are disabled.
 IP Address: Set the IP address for the trap.
 Port Number: Set the port number for the trap.
 User Name: Select a user that you have created.
 Security Level: None, AuthNoPriv, or AuthPriv (default None).
 Is Administrator: Select the checkbox if you want to set it as administrator.
To edit a trap:
1. In the trap list, select the trap you want to edit and then click Edit.
The Edit Trap window opens.
2. Edit the information you want to change, and then click Apply.

To view detailed information of a trap:

 Select the trap in the left-hand list.
The information is displayed in the right-hand area of the window.
To delete a trap:
 In the SNMP trap list, select the trap you want to delete and then click Delete.
19.6.8 Overwrite SNMP configuration

You can overwrite all the SNMP configuration from the NE equipment to the DB.
To overwrite SNMP configuration:
 In the SNMP Configuration window, on the toolbar, click .
19.6.9 Propagate SNMP configuration

You can propagate the SNMP configuration from one NE to one or more other NEs of the same NE type.

To propagate SNMP configuration:
1. In the SNMP Configuration window, on the toolbar, click .

The Propagate window opens.

2. From the left-hand NE list, select the NEs to which you want to propagate the SNMP configuration, and
then click Add.
The NEs are added to the Selected Objects list.

3. Click Propagate.
You can view the results in the Task Monitor window.
19.7 Enable link loss carry forward (LLCF)

This section describes LLCF in LCT-NPT, as illustrated in the following figure.
Figure 19-1: LLCF module
Remote ETY or Tunnel defect can be a trigger for local ETY port down.

To enable LLCF:
1. In the NE Shelf View window, select an ETY port.
3. Select the LLCF Enable checkbox.

19.8 View system fault details

You can view the detailed system error information in LCT-NPT.

To view system fault details:

1. In the NE Shelf View window, select Maintenance and then View System Fault Details.
The System Fault Details window opens.
19.9 Test Link OAM loopback

The Link OAM Loopback Testing function can be supported for the PB ETY and MoE ports in all the LSI and
EZchip cards.
To start the Link OAM Loopback Testing, you must enable Link OAM and Link OAM remote loopback.

To test Link OAM loopback:

1. To enable the Link OAM and the Link OAM remote loopback, in the NE Shelf View window, select a port
of a data card.
2. In the Configuration working mode, select the ETY Maintenance tab.
 To enable the Link OAM, select the Enable OAM checkbox. The default is disabled.
 To enable the Link OAM remote loopback, select the Remote Loopback Request checkbox. It can
only be set when the Link OAM is enabled.
3. Click Apply.

4. To perform Link OAM Loopback Testing function, in the Maintenance working mode, select the Link
OAM Loopback tab.
The following parameters can be configured as required:

 Destination MAC: The destination MAC address of testing packets that generated by CPU.
 Packets Count: The number of packets sent in the storm operation. The default value is 100
packets.
 Delay Between Packets: Delay between packets in the range of 0~600,000ms. The default value
is 0.
 Size: The size of the test packet. The default value is 64 bytes.
 Timeout: Wait for response in seconds. The default value is 2,000ms.
5. To start the Link OAM Loopback Testing, on the toolbar, click .

When the Link OAM Loopback Testing is started, the parameters cannot be edited.
6. To restart the Link OAM Loopback Testing, on the toolbar, click .

You can restart the Link OAM Loopback Testing When it has already been started.
7. To stop the Link OAM Loopback Testing, on the toolbar, click .

8. You can also view the Link OAM Loopback Testing status, as follows:
 Running Status: This attribute describes the running status of this session. If the session is started,
then the status is "Running", otherwise if it is stopped or the session has been ended, then the
status is "End".
 Running Time: This attribute describes running time of Link OAM testing session.
 Number of Tx Packets: Total number of Link OAM testing packets transmitted by CPU.
 Number of Rx Packets: Total number of Link OAM testing packets received by CPU.
 Number of Invalid Rx Packets: Total number of Link OAM testing packets received with invalid
ethernet type by CPU.
 Frame Loss Ratio: This attribute describes average FLR of Link OAM testing session.
19.10 Setting NE Security Mode

In Non-secure Mode of NE, the insecure ports (like FTP/TELNET) are open, and the public key is not checked
when EMS connects to the NE; correspondingly, in Secure Mode, the insecure ports (like FTP/TELNET) will be
closed, and the public key will be checked when EMS connects to the NE.
To set NE security mode:

1. In the NE Shelf View window, from the menu, select Maintenance and then NE Security Mode. A
confirmation dialog box opens, prompting you to confirm the operation.
2. To confirm, click Yes.

20 Perform advanced configuration
20.1 Enabling the BG-40 NE Proxy ARP

The Proxy Address Resolution Protocol (ARP) enables a LAN-connected GNE to automatically handle ARP
requests for remote non-LAN NEs connected via DCC to the GNE (can be configured in the NE ARP list). The
following figure illustrates this concept.
Figure 20-1: BG-40 NE Proxy ARP
When the router R attempts to connect or send a packet to a remote NE (for example, NE2), the router sees
that this NE has the same subnet (N1.N2) as the Ethernet that is attached to it and to the GNE. Therefore,
the router "incorrectly" assumes that the NE is sitting on the same subnet (the same wire). As a result, the
router sends an ARP request to determine the physical address of the NE. The GNE receives this ARP request
and sends its own physical (MAC) address to the router. The router then makes the connection or sends the
IP packet to the GNE.
To enable the BG-40 NE proxy ARP:

1. In the BG-40 NE Shelf View window, select Advanced and then Proxy ARP Enable/Disable. The Proxy
ARP window opens.
2. To retrieve the proxy ARP setting from the equipment, click .

3. Set the proxy ARP property, and click Apply to send the proxy ARP to the BG-40 NE.

LCT-NPT® User Guide Perform advanced configuration
20.2 Managing the BG-40 NE ARP Table

After enabling a GNE's proxy ARP, configure the ARP table. The ARP table contains the NE IP address or the
IP subnet for the GNE proxy. When a GNE receives an ARP request for an IP address, it looks up the address
in the ARP table. If the ARP table contains this IP address, the GNE returns an ARP acknowledgment.
To configure the BG-40 NE ARP table:

1. In the BG-40 NE Shelf View window, select Advanced and then Proxy ARP Table. The Proxy ARP Table
window opens.
2. To add proxy ARP items to the table, click . The Create Proxy ARP window opens.

3. Enter the IP address and subnet mask in the respective fields, and click OK to confirm and return to the
Proxy ARP Table window. The new IP address is displayed in the IP list.
4. To modify the proxy ARP table, click . The Modify Proxy ARP window opens.
5. Modify the IP address and subnet mask, and click OK.

6. To delete proxy ARP items from the table, select their IP addresses, and click .
7. To obtain proxy ARP IP addresses from the BG-40 NE, click . The IP addresses are displayed in the
window.
8. To send the proxy ARP IP addresses to the BG-40 NE, click Apply.

20.3 Displaying Channel MIB Counters for BG-

40/BG-20/BG-20C
Channel MIB counters show detailed information about the channel communication quality and the position
of a channel communication failure. Channel MIB counters showing many send/receive errors or stop/start
times indicate that one of the NEs at the ends of the channel has communication problems.
To display channel MIB counters:

1. In BG-40/BG-20/BG-20C NE Shelf View window, select Advanced and then Channel MIB Counters. The
Channel MIB Counters window opens.
2. To display the counters in real time, click .

20.4 Configuring the BG-40 NE Serial Port

The BG-40 serial port is used to connect external equipment. To connect with external equipment, set the
property as External. To manage the PCM card in the extension slot, set the property as Internal. The default
is Internal.
To configure the BG-40 NE serial port:

1. In the BG-40 NE Shelf View window, select Advanced and then Serial Port Configuration. The NE Serial
Port Configuration window opens.
2. To obtain the serial port from the BG-40 NE in this mode, click .
3. To send the property to the BG-40 NE, click Apply.
20.5 Performing Software Upgrade

Software upgrade can only be performed by a system administrator. Before carrying out this operation, the
LCT-NPT automatically checks the FTP server configuration. If no FTP server is installed, the LCT-NPT prompts
you to install it. If the FTP service is not running, the LCT-NPT starts this service automatically. If the FTP
service cannot be started, the LCT-NPT prompts you to start the service manually.
This section describes how to perform software upgrade for the BG-20/BG-20C/BG-30/BG-64/NPT-1200/
NPT-1020/NPT-1021/NPT-1010/NPT-1050 NE in LCT-NPT.
For details about performing software upgrade for NPT-1800 NEs in LCT-NPT, refer to Procedure of Software
Upgrade in EMS-NPT V5 Supporting Information.

To perform software upgrade for an MSPP/NPT NE:

1. In the NE Shelf View window, from the main menu, select Advanced and then Download Embedded
Software. The Software Upgrade window opens.
2. To retrieve the embedded software version information from the equipment, click Get. The information
is displayed in the Version Info area.
3. To select the file name to be downloaded, in the Version Download area, click . Also in the Version
Download area, the Target Area cannot be configured and always selects the inactive area.

4. To download the software to the equipment, click Download.

5. To set the activation time, click Activate. The following window opens.
6. From this window:

a. Set the Activation Time attribute with the time displayed in the window.
b. To send the Activation Time/Version Activate attribute to the selected NEs, click Apply.
c. To activate the NE new version immediately, click Activate Immediately.
20.6 NE version live update

Software patch management is a patching mechanism used to fix bugs of a released version without releasing
and installing a new version.
The following patch types are supported:
 Hot function patch: Can be activated without restart.
 Warm function patch: Requires warm reset to be activated.
 Cold function patch: Requires cold reset to be activated.
 Warm card SW update: Requires warm reset to be activated. Function patches of this card cannot
coexist.
 Cold card SW update: Requires cold reset to be activated. Function patches of this card cannot coexist.
 Card FPGA update: Always cold reset.
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.
The NE attribute should display the complete version information, for example:

 V12.0.23-01, with patch version 01

 V12.0.23, without any patch
NE version information is the patch version that is updated each time the system is restarted or a patch is
activated.
20.6.1 Workflow
The patching procedure from LCT includes these steps:
7. Confirm current patch version.
8. Download the patch package.
9. Activate the patch.
10. Confirm patch version is updated successfully.
In this section, the NE version live update includes:
 Installing Patches
 Activating Patches
 Viewing Patches Information
 Clearing Patches
 Viewing Scheduled Patch Activation Task
 Canceling Scheduled Patch Activation Task
20.6.2 Installing Patches

This section describes how to download patch packages. The procedure includes these steps:
11. Select NEs.
12. Select patch.
13. Download the patch.
14. Verify the patch.
15. Set activation time.
16. Activate.
17. Report.

To download patch packages:

1. In the NE Shelf View window, from the main menu, select Advanced and then Install Patches. The
Embedded SW Patching Wizard window opens.
2. Select the NE you want to patch by selecting its checkbox, and click Next. The following window opens.

3. Select the directory where the new patch file 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.
4. Click Next. The following window opens.

5. Wait a few minutes while the wizard downloads the patch file to the NE. Then click Next to continue.
6. Wait a few minutes during the patch verification. Click Next.

7. Set the target patch activation time as required, and click Next to patch the NE(s).
8. Click Next. The live update report opens.
9. To save the report to file, click Save.

10. To exit the Embedded SW Patching Wizard window, click Finish.

20.6.3 Activating Patches

This section describes how to activate NE patches. The procedure includes these steps:
11. Select NEs.
12. Get the patch.
13. Verify the patch.
14. Set activation time.
15. Activate.
16. Report.
To activate NE patches:
1. In the NE Shelf View window, from the main menu, select Advanced and then Activate Patches. The
Activate Patch Wizard window opens.

2. Select the NE you want to patch and click Next. The following window opens.
3. Wait a few minutes during the patch verification, and then 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 opens.
6. To save the report to file, click Save.

7. To exit the Embedded SW Patching Wizard window, click Finish.

20.6.4 Viewing Patches Information

To view the patches information:
1. In the NE Shelf View window, from the main menu, select Advanced and then View Patches Info. The
View Patch Info Wizard window opens.

2. Select the NEs that you want to view, and click Next. The following window opens, displaying
information about the patches.
3. To exit the wizard window, click Finish.
20.6.5 Clearing Patches

To clear NE patches:
1. In the NE Shelf View window, from the main menu, select Advanced and then Clear Patches. A
Confirmation window opens, prompting you to select the bank whose patches you want to delete and
confirm your operation.
2. Select Active or Inactive, and then click OK.

20.6.6 Viewing Scheduled Patch Activation Task

To view the scheduled patch activation task:
1. In the NE Shelf View window, from the main menu, select Advanced and then View Scheduled Patch
Activation Task. The View Scheduled Activation Info Wizard window opens.

2. Select the NEs that you want to view, and click Next. The following window opens, displaying the
scheduled activation information.
3. To exit the wizard window, click Finish.

20.6.7 Canceling Scheduled Patch Activation Task

To cancel scheduled patch activation task:
 In the NE Shelf View window, from the main menu, select Advanced and then Cancel Scheduled Patch
Activation Task.
20.7 Clearing the Flash for BG-40/BG-20/BG-20C

The Clear Flash feature deletes the LCT-NPT configuration data from the flash memory. Other areas are not
affected.
To clear the flash:

1. In the BG-40/BG-20/BG-20C NE Shelf View window, select Advanced and then Clear the Flash. A
Confirmation window opens.

20.8 Configuring SNMP Agent Mode

The SNMP agent operates in two work modes: monitoring and full control. Some managers need a source IP
address to identify an agent. The NEs have two IP addresses: DCC and Ethernet. You must select one of them.
You can configure the SNMP agent mode for the BG-20/BG-20C/BG-30/BG-64/NPT-1200/NPT-1020/ NPT-
1021/NPT-1010 NEs
To configure the SNMP agent mode:

1. In the NE Shelf View window, select Advanced and then SNMP Agent Mode Configuration. The SNMP
Agent Mode window opens.
2. To obtain the mode option and IP address for SNMP traps, click .
3. In Monitoring Mode, the SNMP agent only responds to GET, GET-NEXT, and GET-BULK operations. In
Full Control Mode, the SNMP agent responds to all operations.
4. Select IP address as Ethernet IP when the NE is a gateway; otherwise, select DCC IP.
5. Select the mode option and IP address for the SNMP Traps property, and click Apply to send the
property to the NE.
20.9 Calibrating SEC

To calibrate SEC:
 In the NE Shelf View window, select Advanced and then Calibrating SEC.
20.10 Restoring Default Center Frequency

To restore default center frequency:
 In the NE Shelf View window, select Advanced and then Restoring Default Center Frequency.

20.11 Clearing Reset

To clear reset:
1. In the BG-30/BG-20/BG-20C/BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1010 NE Shelf View window,
select Advanced and then Clearing Reset. A Confirmation window opens.
2. Click Yes to confirm clearing reset.

21 License management
Each LCT in the network requires a license to activate it. This chapter describes the license management in
LCT-NPT.
21.1 License Control Mechanism

Features of the LCT license control mechanism are:
 Each LCT in the network requires a license to activate it.
 The LCT license is only bound with the total number of LCT hosts, and is activated by the EMS-NPT.
 EMS-NPT maintains the LCT license bank; each LCT activation withdraws one license from the bank.
 After installing the LCT, the user must connect the LCT host to the EMS. The EMS checks whether the
LCT license bank has a spare license:
 If yes, the EMS activates the LCT license.
 If not, the EMS refuses to activate the LCT license.
 When there is no connection to the EMS-NPT, a temporary license (90 days) is provided to allow the
user to use LCT.
If the EMS-NPT is not installed, carry out the following procedure to manage the LCT license.
To manage the LCT license without installing EMS-NPT:

1. Run the Host ID Collection tool on the PC that has the LCT-NPT installed in order to collect the host ID
information, and then send the generated file to the sales force.
2. Upon receiving the Host ID information file, the Supply Chain generates the license key using the License
Generate Tool. Supply Chain completes the fields of the Generate PO window as follows:
 MAX NE Numbers: 2
 MAX SAM4 NE Numbers (increment): 2
 MAX Ethernet Port Numbers (increment): 200
 MAX MPLS Cards Numbers (increment): 200
 MTNM I/F License: disable
 LCT license: 0
 PTP license: 12
3. After the license key has been generated, Supply Chain sends it to the customer.
4. Upon receiving the license key, the customer must copy the license.dat file to the folder: \LCT-
NPT\etc\.config, replacing the old license.dat file.

22 Use the fix tool
The fix tool provides the fixes management under Windows. This section describes how to use the fix tool to
manage the fixes in the LCT-NPT.
Before running the fix tool, make sure the LCT-NPT client and server are not running on the computer.
To use the fix tool:

1. On the desktop, select Start, All Programs, LCT-NPT, Tools, and then Fix Tools.
The LCT-NPT Fix Tool window opens.
2. In the Select Fix To Install field, click to select the fix file with the format .tar or .zip.
3. Click Open to add the fix.
4. To install the fix, click Install.
The Installed Fixes List lists all the fixes that have been installed in LCT-NPT, including their name and
version number.
5. To remove a fix, select it in the Installed Fixes List, and then click Remove.

LCT-NPT v6.0 User Guide

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

LCT-NPT v6.0 User Guide

Uploaded by

Copyright:

Available Formats

LCT-NPT®

ECI Telecom's management applications run on VMWare virtualization hypervisors.

© Copyright by ECI Telecom, 2013-2017. All rights reserved worldwide.

1 LCT-NPT overview ....................................................................................... 1-1

2 Install the LCT-NPT ...................................................................................... 2-1

3 Log in and configure NE with boot configuration tool .................................. 3-1

4 Get started .................................................................................................. 4-1

5 LCT-NPT security management .................................................................... 5-1

ECI Telecom Ltd. Proprietary iii

5.7 Configure RADIUS client settings ........................................................................................... 5-7

6 NE management .......................................................................................... 6-1

ECI Telecom Ltd. Proprietary iv

6.14 View NE power consumption management status ............................................................. 6-40

7 NE configuration and management in IP/MPLS ........................................... 7-1

ECI Telecom Ltd. Proprietary v

7.4.8 View the LDP FRR status........................................................................................................ 7-44

ECI Telecom Ltd. Proprietary vi

7.8.9 View PIM statistics ................................................................................................................ 7-88

ECI Telecom Ltd. Proprietary vii

7.19 Manage MSTP .................................................................................................................... 7-136

8 Configure and manage cards ....................................................................... 8-1

ECI Telecom Ltd. Proprietary viii

8.2 Work with cards ................................................................................................................... 8-16

ECI Telecom Ltd. Proprietary ix

8.10.4 CPTS320/CPS320 ................................................................................................................. 8-140

ECI Telecom Ltd. Proprietary x

8.18.2 Power units of BG-20 .......................................................................................................... 8-288

9 Configure and manage cards in IP/MPLS ..................................................... 9-1

ECI Telecom Ltd. Proprietary xi

9.7 Manage the MCP-1800 ........................................................................................................ 9-30

10 Configure timing source ............................................................................ 10-1

ECI Telecom Ltd. Proprietary xii

11 Services management in MSPP/NPT .......................................................... 11-1

ECI Telecom Ltd. Proprietary xiii

11.12.7 Configure multicast for MPLS RootedMP/Leaf service ..................................................... 11-140

ECI Telecom Ltd. Proprietary xiv

11.20.3 View CCN tunnel list .......................................................................................................... 11-246

12 CES services management ......................................................................... 12-1

13 Services management in IP/MPLS ............................................................. 13-1

ECI Telecom Ltd. Proprietary xv

13.4.3 View VRF status ................................................................................................................... 13-61

14 Cross connections management ................................................................ 14-1

15 Work with protection ................................................................................ 15-1

ECI Telecom Ltd. Proprietary xvi

15.3.7 SFP Inventory in IOP ............................................................................................................ 15-24

16 Ethernet ring protection switching ............................................................ 16-1

17 Fault management .................................................................................... 17-1

ECI Telecom Ltd. Proprietary xvii

17.12.1 Viewing NE Alarms Log ........................................................................................................ 17-34

18 Performance management ........................................................................ 18-1

19 Maintenance operations ........................................................................... 19-1

ECI Telecom Ltd. Proprietary xviii

19.1.9 Perform preventive maintenance ......................................................................................... 19-8

ECI Telecom Ltd. Proprietary xix

20 Perform advanced configuration ............................................................... 20-1

21 License management ................................................................................. 21-1

22 Use the fix tool .......................................................................................... 22-1

ECI Telecom Ltd. Proprietary xx

ECI Telecom Ltd. Proprietary xxi

Hardware and software requirements

ECI Telecom Ltd. Proprietary 1-1

To install the LCT-NPT:

2. Select Install LCT-NPT.