LCT-NPT User Guide

LCT-NPT®
Native Packet Transport

Version 6.1
User Guide
LCT-NPT User Guide
V6.1
Catalog No: X35813
Drawing No: 4BGHT6-EMSW-461
January 2018
Rev01
ECI's NPT-1800, NPT-1200, NPT-1050, NPT-1021, and NPT-1010 are CE2.0 certified.
ECI's qualification lab is accredited by A2LA for competence in electrical testing according to
the International Standard ISO IEC 17025-2005 General Requirements for the Competence of
Testing and Calibration Laboratories.
ECI's management applications run on VMWare virtualization hypervisors.
© Copyright by ECI, 2013-2018. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Ltd. (“ECI”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE
AGREEING TO BE 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's Proprietary"] is ECI'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's rights in the aforesaid information. Any use of ECI'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, is strictly forbidden.
ECI's Proprietary is provided "AS IS" and may contain flaws, omissions, or typesetting errors. No responsibility and or liability whatsoever are
assumed by ECI 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's Proprietary, which may be affected in any way by the use and/or
dissemination thereof. ECI reserves the right, without prior notice or liability, to make changes in equipment design or specifications including any
change in and to the ECI's Proprietary.
Any representation(s) in ECI's Proprietary concerning performance of ECI'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's sales contract or order confirmation. ECI'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 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'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.
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'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) and
that such instructions were understood by them. ECI shall not be liable to you or to any other party for any loss or damage whatsoever or
howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failure to fulfill in whole or in part the "Before You
Start/Safety Guidelines" instructions.
Contents
Useful information ............................................................................................... xiv
Related documents ............................................................................................................................. xiv
Contact information ............................................................................................................................ xiv
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-7
3.4 Download embedded software for BG-30/BG-64/NPT NEs ................................................ 3-10
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-12
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-13
3.9 Configure "No Recovery Next Startup" for BG-20 ............................................................... 3-14
3.10 Configure "Serial Port Close" for BG-20 ............................................................................... 3-14
3.11 Configure NE Restart Mode for
BG-64/NPT-1200/NPT-1020/NPT-1021/NPT-1050/NPT-1010 ............................................ 3-15
4 Get started .................................................................................................. 4-1

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

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

LCT-NPT® User Guide Contents
5.7 Configure RADIUS client settings ........................................................................................... 5-8
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-4
6.1.7 NPT-1020 ................................................................................................................................. 6-5
6.1.8 NPT-1021 ................................................................................................................................. 6-6
6.1.9 NPT-1030 ................................................................................................................................. 6-6
6.1.10 NPT-1050 ................................................................................................................................. 6-6
6.1.11 NPT-1800 ................................................................................................................................. 6-8
6.1.12 NPT-1200i .............................................................................................................................. 6-10
6.2 Assign slots........................................................................................................................... 6-11
6.3 NE frame mode definition ................................................................................................... 6-12
6.4 Reassign a shelf .................................................................................................................... 6-12
6.5 Set BG-20EH DC redundancy ............................................................................................... 6-14
6.6 Routing table management ................................................................................................. 6-15
6.6.1 View actual routes................................................................................................................. 6-15
6.6.2 Manage static routes............................................................................................................. 6-15
6.7 OSPF management............................................................................................................... 6-16
6.7.1 Configure overall OSPF settings ............................................................................................ 6-18
6.7.2 Manage OSPF network interfaces ......................................................................................... 6-19
6.7.3 Configure DCC terminations .................................................................................................. 6-23
6.7.4 View OSPF interfaces ............................................................................................................ 6-23
6.8 Configure NE attributes ....................................................................................................... 6-24
6.9 Manage DCC and overhead ................................................................................................. 6-26
6.9.1 Configure communication parameters ................................................................................. 6-27
6.9.2 Manage DCC and overhead for BG-40 .................................................................................. 6-29
6.9.3 Manage DCC and overhead for BG-20/BG-20C/BG-30/BG-64 and NPT NEs......................... 6-32
6.10 Reset NEs ............................................................................................................................. 6-35
6.11 Back up NE data ................................................................................................................... 6-36
6.12 View NE system resources ................................................................................................... 6-37
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-29
7.3.5 Manage OSPF key chain templates ....................................................................................... 7-33
7.3.6 View OSPF instance status .................................................................................................... 7-35
7.3.7 View OSPF LIF status ............................................................................................................. 7-35
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-37
7.3.11 View OSPF LDP FRR status ..................................................................................................... 7-37
7.4 IS-IS protocol management in IP/MPLS ............................................................................... 7-37
7.4.1 Manage IS-IS instances .......................................................................................................... 7-40
7.4.2 Manage IS-IS levels ................................................................................................................ 7-42
7.4.3 Manage IS-IS LIFs ................................................................................................................... 7-43
7.4.4 View the IS-IS instance status ............................................................................................... 7-45
7.4.5 View IS-IS LIF status ............................................................................................................... 7-45
7.4.6 View IS-IS adjacency .............................................................................................................. 7-45
7.4.7 View the IS-IS database ......................................................................................................... 7-45
ECI Telecom Ltd. Proprietary v

7.4.8 View IS-IS LDP FRR status ...................................................................................................... 7-45

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

7.8.9 View PIM statistics ................................................................................................................ 7-90

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

7.19 Manage MSTP .................................................................................................................... 7-140

7.19.1 Configure MSTP settings ..................................................................................................... 7-140
7.19.2 Manage MSTP interfaces .................................................................................................... 7-142
7.19.3 Manage MSTP instance ....................................................................................................... 7-143
7.20 Configure port mirroring.................................................................................................... 7-144
7.21 Manage profiles ................................................................................................................. 7-145
7.21.1 Create VLAN ID range profiles ............................................................................................. 7-145
7.21.2 Create vFIB quota profiles ................................................................................................... 7-146
7.21.3 Create port TPID profiles ..................................................................................................... 7-147
7.21.4 Create TPID profiles............................................................................................................. 7-148
7.21.5 Create MTU profiles ............................................................................................................ 7-148
7.21.6 Create CoS group profiles.................................................................................................... 7-149
7.21.7 Create QoS group profiles ................................................................................................... 7-150
7.21.8 Create BSC policer profiles .................................................................................................. 7-156
7.21.9 Create Policer profiles ......................................................................................................... 7-157
7.21.10 Create WRED profiles .......................................................................................................... 7-158
7.21.11 Create Firewall profiles ....................................................................................................... 7-159
7.21.12 Create Flow Block profiles ................................................................................................... 7-163
7.21.13 Create Slow Path policer profiles ........................................................................................ 7-164
7.21.14 Create Sampling profiles ..................................................................................................... 7-165
7.21.15 Create PM defects profiles .................................................................................................. 7-165
7.21.16 Create alarm profiles ........................................................................................................... 7-167
7.21.17 Manage profiles in the profile list ....................................................................................... 7-170
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-3
8.1.6 Card assignment for NPT-1200 ............................................................................................... 8-6
8.1.9 Card assignment for NPT-1010 ............................................................................................. 8-10
8.1.12 Card assignment for NPT-1200i............................................................................................. 8-13
ECI Telecom Ltd. Proprietary viii

8.2 Work with cards ................................................................................................................... 8-14

8.2.1 Card move ............................................................................................................................. 8-14
8.2.2 Configure card attributes ...................................................................................................... 8-18
8.2.3 Configure temperature thresholds ....................................................................................... 8-20
8.2.4 Hot insertion ......................................................................................................................... 8-22
8.2.5 Slot reassignment .................................................................................................................. 8-23
8.2.6 Set the laser on/off status ..................................................................................................... 8-26
8.2.7 Set user label and description per port ................................................................................. 8-28
8.3 Work with ports ................................................................................................................... 8-29
8.3.1 Configure EoS ports ............................................................................................................... 8-30
8.3.2 Configure MoT ports ............................................................................................................. 8-32
8.3.3 Configure GE/10GE/100GE ETY ports ................................................................................... 8-33
8.3.4 Configure GE/10GE/100GE MoE ports .................................................................................. 8-34
8.4 BG_OW management .......................................................................................................... 8-35
8.4.1 Assign OW slot ...................................................................................................................... 8-35
8.4.2 Configure OW settings .......................................................................................................... 8-36
8.5 Configure PDH cards ............................................................................................................ 8-37
8.6 SDH card configuration ........................................................................................................ 8-38
8.6.1 Configure SAM-1/SAM-4 cards ............................................................................................. 8-39
8.6.2 Configure VC-4 contiguous concatenation ............................................................................ 8-40
8.6.3 Configure SMQ1&4 cards ...................................................................................................... 8-41
8.7 L1 data card configuration ................................................................................................... 8-41
8.7.1 Configure L1B_6F cards ......................................................................................................... 8-43
8.7.2 Configure DMGE_4_L1 cards................................................................................................. 8-46
8.8 L2 data card configuration ................................................................................................... 8-46
8.8.1 MESW_6F .............................................................................................................................. 8-53
8.8.2 DMFE_4_L2 ........................................................................................................................... 8-66
8.8.3 Configure MSTP (MESW_6F and DMFE_4_L2) ...................................................................... 8-84
8.8.4 View and manage VSI objects (MESW_6F and DMFE_4_L2) ................................................ 8-84
8.8.5 DMXE_48_L2 ......................................................................................................................... 8-90
8.8.6 MPOE_12G ............................................................................................................................ 8-94
8.8.7 FE_L12 ................................................................................................................................... 8-97
8.9 Data hybrid cards ............................................................................................................... 8-112
8.9.1 Activate/Deactivate ports ................................................................................................... 8-115
8.9.2 Reassign DHXE_2 to DHXE_4/DHXE_4O .............................................................................. 8-116
8.10 EoP cards ............................................................................................................................ 8-118
8.10.1 MEOP_4/MEOP_4H ............................................................................................................. 8-118
ECI Telecom Ltd. Proprietary ix

8.10.2 DMEOP_4 ............................................................................................................................ 8-126

8.11 Matrix cards ....................................................................................................................... 8-126
8.11.1 XIO30-1/XIO30-4/XIO30-4B/XIO30-16/XIO30Q_1&4 ......................................................... 8-126
8.11.2 XIO64/XIO16_4 .................................................................................................................... 8-128
8.11.3 CPTS100/CPS100 ................................................................................................................. 8-136
8.11.4 CPTS320/CPS320 ................................................................................................................. 8-142
8.11.5 CPS50................................................................................................................................... 8-143
8.11.6 CS10 ..................................................................................................................................... 8-152
8.11.7 CS5 ....................................................................................................................................... 8-153
8.11.8 MCPTS100/MCPS100 .......................................................................................................... 8-156
8.12 Aggregate card ................................................................................................................... 8-164
8.12.1 AIM100/AIM100P................................................................................................................ 8-164
8.13 NFV cards ........................................................................................................................... 8-164
8.13.1 NFVG_4 ............................................................................................................................... 8-164
8.13.2 NFVX card ............................................................................................................................ 8-170
8.14 CES cards ............................................................................................................................ 8-170
8.14.1 DMCE1_32 ........................................................................................................................... 8-170
8.14.2 DMCES1_4 ........................................................................................................................... 8-183
8.14.3 MSE1_16 ............................................................................................................................. 8-207
8.14.4 TMSE1_8 ............................................................................................................................. 8-207
8.14.5 MSC_2_8 ............................................................................................................................. 8-208
8.14.6 MS1_4 (Ezchip) .................................................................................................................... 8-217
8.14.7 MSE1_32 (Ezchip) ................................................................................................................ 8-217
8.15 Optics cards........................................................................................................................ 8-217
8.15.1 Optical Base Card (OBC) ...................................................................................................... 8-217
8.16 PCM cards .......................................................................................................................... 8-225
8.16.1 SM10 card ........................................................................................................................... 8-225
8.16.2 SM_10E card ....................................................................................................................... 8-227
8.16.3 EM_10E ............................................................................................................................... 8-258
8.17 MXC cards .......................................................................................................................... 8-266
8.17.1 MXC4X ................................................................................................................................. 8-266
8.17.2 MXC-20/MXC-20C ............................................................................................................... 8-267
8.17.3 MXC-1020 ............................................................................................................................ 8-267
8.17.4 MXC-1021 ............................................................................................................................ 8-269
8.18 Control cards ...................................................................................................................... 8-270
8.18.1 MCP30/MCP30B .................................................................................................................. 8-270
8.18.2 MCP64 ................................................................................................................................. 8-276
ECI Telecom Ltd. Proprietary x

8.18.3 MCP-1200 ............................................................................................................................ 8-281

8.18.4 MCPS-1010 .......................................................................................................................... 8-285
8.18.5 MCP-1050 ............................................................................................................................ 8-286
8.19 Power units ........................................................................................................................ 8-287
8.19.1 Power units of BG-40 .......................................................................................................... 8-287
8.19.2 Power units of BG-20 .......................................................................................................... 8-287
8.19.3 Power units of BG-30 .......................................................................................................... 8-289
8.19.4 Power units of BG-64 .......................................................................................................... 8-289
8.19.5 Power units of NPT-1200 .................................................................................................... 8-290
8.19.6 Power units of NPT-1020/NPT-1021 ................................................................................... 8-292
8.19.9 Assign power units for BG-64/NPT-1200/NPT-1020/NPT-1021 .......................................... 8-297
8.20 Fan control units ................................................................................................................ 8-302
8.20.1 Set the fan work mode ........................................................................................................ 8-302
8.21 DMGE_8_POS card............................................................................................................. 8-305
8.21.1 Manage ports ...................................................................................................................... 8-306
8.21.2 Manage a LAG ..................................................................................................................... 8-313
8.21.3 POS mirroring ...................................................................................................................... 8-313
8.22 TSHU_48V card .................................................................................................................. 8-317
8.23 MXP10 card ........................................................................................................................ 8-317
8.23.1 MXP10 supported modules ................................................................................................. 8-320
8.23.2 MXP10 slot assignment ....................................................................................................... 8-321
8.23.3 Define port rate and density ............................................................................................... 8-324
8.23.4 Manage ports ...................................................................................................................... 8-327
8.23.5 Perform ODU MSI configuration ......................................................................................... 8-332
8.23.6 Perform latency measurement ........................................................................................... 8-334
8.24 TM10 .................................................................................................................................. 8-334
8.25 Tributary protection card................................................................................................... 8-334
8.25.1 TPEH8_1 .............................................................................................................................. 8-334
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-3
9.3 Manage OTN ports in DHXE_4O ............................................................................................ 9-6
9.4 Manage the CIPS1T card ...................................................................................................... 9-11
9.5 Manage MSC_2_8 (MS1_4/MSE1_32)................................................................................. 9-13
ECI Telecom Ltd. Proprietary xi

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-18
9.5.4 Manage MSP1+1 ................................................................................................................... 9-24
9.6 Perform port rate settings in MS1_4 ................................................................................... 9-29
9.7 Manage the MCP-1800 ........................................................................................................ 9-30
9.7.1 Manage the CF card .............................................................................................................. 9-33
9.8 Manage the MCIPS320 ........................................................................................................ 9-36
9.9 Manage the MCIPS560 ........................................................................................................ 9-36
9.10 Manage power units of IP/MPLS NEs .................................................................................. 9-38
9.11 Manage the fan units of IP/MPLS NEs ................................................................................. 9-39
9.11.1 Manage the fan units of NPT-1800 ....................................................................................... 9-39
9.11.2 Manage the fan units of NPT-1200i ...................................................................................... 9-42
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-30
10.5.2 Manage the PTP TMU ......................................................................................................... 10-31
10.5.3 View the PTP TMU state ...................................................................................................... 10-38
10.5.4 View the PTP port state for IP/MPLS ................................................................................... 10-38
10.5.5 Manage the PTP port .......................................................................................................... 10-39
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-45
10.5.9 View PTP slave statistics for OC slave ................................................................................. 10-46
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
ECI Telecom Ltd. Proprietary xii

10.5.15 Work in services .................................................................................................................. 10-55

10.6 Configure PCM timing ........................................................................................................ 10-58
10.7 Configure MXP10 timing .................................................................................................... 10-61
10.8 Quality Level and SSM Processing with Option II .............................................................. 10-62
ECI Telecom Ltd. Proprietary xiii

Useful information
The LCT-NPT User Guide is intended for MSPP/NPT/NPTi equipment installation personnel and field
engineers. It provides a detailed description of the LCT-NPT, including a general product overview,
description of the user interface, and guide to basic operations.
Related documents
 LCT-NPT Service Management Guide
 LCT-NPT Network Management Guide
 LCT-NPT Performance Management Guide
 LCT-NPT Supporting Information
 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 Documentation Group +972-3-9268145 techdoc.feedback@ecitele.com
ECI Customer Support +972-3-9266000 on.support@ecitele.com
ECI Telecom Ltd. Proprietary xiv

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 Server 2012 - Enterprise Edition 64 bits
 Windows Server 2016, Standard Edition
 Win7 SP1 (32/64bit)
 Win10 (32/64bit)
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.
3. Click Next.

LCT-NPT® User Guide Install the LCT-NPT
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.
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 the S/N dependent
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
normal case the IP is:
 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
normal case the IP is:
 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
One IP is fixed to 194.194.194.193/24 dependent
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
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
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
 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
 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
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-1
050/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.
 System initial configuration - Some NE and system parameters (such as framing mode, time zone,
router ID, etc.) must be configured during NE installation stage, and if some of them are not
configured correctly during installation stage, it is problematic to change it later in operation stage
because system restart is required. There is a new configuration page added for system initial
configuration in LCT-NPT. The mandatory parameters to be configured during NE installation are
displayed in the page (before being managed by EMS-NPT) and you can get and set these parameters
by LCT-NPT (no need to reboot system).
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: Including NPT-1800 and NPT-1200i.
 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.

 System initial configuration: Only available when Product Family is set as IP MPLS.
Click Login, the NE Initial Configuration window opens.
You can set the following NE basic attributes as required:

 Framing Mode: select SDH or Sonet. Changing the framing mode will cause system to
be restarted in no-recovery mode and all configuration will be cleared.
 NE ID: set an NE ID as required (no reboot required upon change).
 NE Name: set the host name of the NE (no reboot required upon change).
 Loopback0 IP: set the IP of loopback0 (no reboot required upon change).

 Router ID: should be set to lo0. System reboot is required upon change.
 Time Zone: select your time zone from the dropdown list. System reboot is required
upon change.
 Data and Time: set the date and time. (no reboot required upon change).
 EMS Server IP: automatically set and delete upon LCT-NPT log on and log off. It is
read only (no reboot required upon change).
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.

LCT-NPT® User Guide LCT-NPT security management
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.
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.
The BG-30 includes two units – the BG-30B (base unit) and the BG-30E (expansion unit). The BG-30B offers
a lower entry cost, while the BG-30E enables higher expandability. All expansion cards for the BG-20E can
be reused in the BG-30E.
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/MCIPS560 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/FCU-1200B 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
 NPT-1200i
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:

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.
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 OSPF 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 IS-IS 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 VRRP on 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 User configurable priority from 1-254

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 Actual Priority.
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 Master Down Time Computed from the Advertise interval + Skew time.
Skew Time VRRP V2: Skew Time Computed from the Current Priority.
VRRP V3: 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 create 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 current context, e.g., for the current peer group, neighbor, address family,etc.
 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
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.
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:
1. In the IP/MPLS NE Shelf View window, n the left object tree, select the CS module. Then in the
Performance working mode, select the Statistics tab.
OR
In the BGP Neighbors list window, right-click a BGF neighbor and click Performance Statistics.

2. In the Display area, select the 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: PIM-SM network running on single AS (Intra-AS)
The following window indicates the PIM application in V6.1.
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 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.1, 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-13: Typical application - IPTV broadcasting
LCT-NPT V6.1 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-14: 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-15: 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 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-16: 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-17: Another example of DHCP relay agent in L3VPN

Figure 7-18: 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 in IP/MPLS

To configure BFD protocol in IP/MPLS:
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 in IP/MPLS

To manage BFD section sessions in IP/MPLS:
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 in IP/MPLS

To manage IP BFD sessions in IP/MPLS:
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 in IP/MPLS

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

7.11.5 Manage multihop IP BFD sessions in IP/MPLS

To manage multihop IP BFD sessions in IP/MPLS:
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 in IP/MPLS

To view the BFD status in IP/MPLS:
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 in IP/MPLS

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

4. Click .


7.11.8 Manage BD-LSP BFD in IP/MPLS

You can configure BD-LSP BFD when creating MPLS TP tunnels in IP/MPLS.
To configure BD-LSP BFD in IP/MPLS:

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 in IP/MPLS

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 in IP/MPLS:

 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-19: 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:
2. In the Configuration working mode, select the Profiles > Policer Profile.
3. To create a new Policer profile, click .

The Create Policer Profile window opens.
4. 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.
5. 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 with Y Y
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-40X Power Conversion Unit Y
(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
ME1_21H Y
ME1_42 Y
ME1_42H 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
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


PS_A
A B
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
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


PS_A
A B
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
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

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
DMCES1_4 Y Y Y Y Y Y Y
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


PS A PS B FS MXSA MXSB TS1 TS2 TS3 EPS A EPS B EFS ES1 ES2 ES3
DHGE_24 Y
DHGE_24 Y
PME1_21 Y Y Y
PME1_63 Y Y Y
PM345_3 Y Y Y
SMQ1 Y Y Y
SMQ1&4 Y Y Y
SMS16 Y Y Y
DMCES1_4 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



Mod NPT-1800 EXT-2U
ule
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
MBP
-180
0
INF- Y Y
180
0
FCU- Y
180
0
MCP Y Y
-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
DHG Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
E_8S
DHG Y Y Y Y Y Y Y Y Y Y Y
E_4E
DHG Y Y Y Y Y Y Y Y Y Y Y
E_8
DHG Y Y Y Y Y Y Y
E_16
DHG Y Y Y Y Y Y Y
E_24
DHG Y Y Y Y Y Y Y Y Y Y Y Y
E_20
MS1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
_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
MSC Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
_2_8
MSE Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
1_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

Mod NPT-1800 EXT-2U

ule
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
INF- Y Y
E2U
AC-P Y
S-E2
U
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 with MCIPS560 EXT-2U
MCIPS320 MCIPS560
PS PS F M XS XS TS TS TS TS TS TS TS TS TS TS TS TS TS TS EP EP EF ES ES ES
A B S S A B 1 2 3 4 5 6 7 1 2 3 4 5 6 7 SA SB S 1 2 3
MBP-1200
INF-1200 Y Y
FCU-1200 Y
FCU-1200 Y
B
MCP-1200 Y
MCIPS320 Y Y
MCIPS560 Y
Y
DHXE_2 Y Y Y Y Y Y Y Y Y Y Y Y
DHXE_4 Y Y Y Y Y Y Y Y Y Y Y Y
DHXE_4O Y Y Y Y Y Y Y Y Y Y Y Y
DHGE_8S Y Y Y Y Y Y
DHCE_1Q Y Y Y Y
DHGE_8 Y Y Y Y Y Y Y
DHGE_4E Y Y Y Y Y Y Y

Module NPT-1200i with MCIPS320 with MCIPS560 EXT-2U

MCIPS320 MCIPS560
DHGE_16 Y Y Y Y
DHGE_24 Y Y Y Y
MSE1_32 Y Y Y Y Y Y Y Y Y Y Y Y
MSC_2_8 Y Y Y Y Y Y Y Y Y Y Y Y
MS1_4 Y Y Y Y Y Y Y Y Y Y Y Y
NFVG_4 Y Y Y Y Y Y Y Y Y Y Y Y
TSHU_48 Y Y
V
INF-E2U Y Y
AC-PS-E2 Y
U
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: following figure illustrates the 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.
2. Select the Maintenance working mode.
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 Work with ports

This section describes how to configure the following types of ports in LCT-NPT:
 EoS ports
 MoT ports
 GE/10GE/100GE ETY ports
 GE/10GE/100GE MoE ports

8.3.1 Configure EoS ports

1. In the NE Shelf View window, in the left object tree, select the an EoS port.
Summary information about the EoS port is displayed.
3. To configure EoS port attributes for all EoS ports on the selected card:
a. In the left object tree, select the card.
b. Select the EoS Ports tab.
A summary of all EoS port settings is displayed.

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

8.3.2 Configure MoT ports

1. In a NE Shelf View window, in the left object tree, select a MoT port.
Summary information about the MoT port is displayed.
3. To configure MoT port attributes for all MoT ports on the selected card:
b. Select the MoT Ports tab.
A summary of all MoT port settings is displayed.

8.3.3 Configure GE/10GE/100GE ETY ports

1. In the NE Shelf View window, in the left object tree, select a GE/10GE/100GE ETY port.
Summary information about the GE/10GE/100GE ETY is displayed.
3. To configure GE/10GE/100GE ETY port attributes for all GE/10GE/100GE ETY ports on the selected
card:
b. Select the GE ETY Ports/10GE ETY Ports/100GE ETY Ports tab.
A summary of all GE/10GE/100GE ETY port settings is displayed.

8.3.4 Configure GE/10GE/100GE MoE ports

1. In the NE Shelf View window, in the left object tree, select a GE/10GE/100GE MoE port.
Summary information about the GE/10GE/100GE MoE is displayed.
3. To configure GE/10GE/100GE MoE port attributes for all GE/10GE/100GE MoE ports on the selected
card:
b. Select the GE MoE Ports/10GE MoE Ports/100GE MoE Ports tab.
A summary of all GE/10GE/100GE MoE port settings is displayed.

8.4 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.4.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.4.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.5 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.6 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.6.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.6.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.6.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.7 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.7.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.7.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.8 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.
 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.


category
 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.
 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


category
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.
 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.


category
 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


category
 AMXE_4
 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.8.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.8.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.
The VCG Attribute window opens.
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.8.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.8.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.8.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:

Switch 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.8.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:

Switch 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:

Switch 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.8.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.8.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.8.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.8.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.8.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.
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. 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.
9. To remove a port from the right aggregation group, select the port(s) in the right list, and click .
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.8.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.
3. Set the parameters as required.
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.8.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.8.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.8.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:
b. Select the VSI you want to activate, and click Activate.
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.
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).
 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.
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.8.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.8.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 a VSI in the list, deactivate it and click .
8. To delete all of the VSIs in the list, click the Select All icon , deactivate them 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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.8.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.9 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-
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
DHCE_1Q
DHCE_1Q is a QSFP28 based single T-slot card with 1 x 100GE in NPT-1200i. It is an Ethernet IO card with
one 100GE port based on QSFP28 and full bandwidth connection to central packet switching matrix.
 Support 100GBase-SR4, CWDM4, LR4, ER4;
 Support CL91 RS FEC;
 Can be supported in TS2, TS3, TS4 and TS7, up to four DHCE_1Q can be assigned in MCIPS560 system.
By default, the 100GE-ETY ports of DHCE_1Q card is not activated. You can activate or deactivate the port
manually.
8.9.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.9.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. After
the reassignment, it is required to perform CPS/CPTS warm reset one by one manually.
Following is the process diagram of reassigning DHXE_2 to DHXE_4/4O.
Figure 8-2: Reassign DHXE_2 to DHXE_4/4O – Procedure
The procedures of the reassignment are:

1. EMS sends "reassign" command to MCP;
2. MCP performs L1/L2 data conversion after receiving reassign command:
 L1 MCP handling – Logical card type change in T-slot

 Fault/PM module update

 L2 MCP handling – Update L2 DB on MCP side only
 Port index update as per new card type and port attribute conversion.
 Set both CPS to “Un-Sync/offline” state – CFG-Inconsistency is expected to be reported on
CPS cards.
3. Perform CPS/CPTS warm reset – Manually;
 Reset standby CPS;
 Reset active CPS after standby CPS operational state =up;
 Replace DHXE_2 with DHXE_4/4O soon after active CPS reset.
4. Traffic-affecting starts from active CPS reset (and DHXE_2 plug out) and ends on DHXE_4/4O recovery.
NOTE: If CPS 1+0, reassignment is TA for whole NE. this is the most critical issue of this
reassignment concept. It may be acceptable if most CPS320/CPTS320 configuration is 1+1.
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.10 EoP cards

There are three EoP cards: the MEOP_4, the MEOP_4H, and the DMEOP_4. This section describes these
cards.
8.10.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.

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
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.10.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.11 Matrix cards

8.11.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.11.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.11.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-3: 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.11.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.11.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.
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.11.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-4: 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.11.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.11.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.11.4.2 AMXE_4
8.11.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.11.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.11.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.11.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.11.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.11.6 CS10
CS10 is the central packet matrix with 10G bps capacity in MXC-1020.
8.11.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-5: 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.11.7 CS5
CS5 is the Central PE in NPT-1010 NE.
8.11.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.
2. In the relevant Activate list, select checkboxes as required.


8.11.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-6: 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.11.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.11.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.11.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-7: 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-8: 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.11.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.12 Aggregate card

8.12.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.13 NFV cards

This section describes the Network Function Virtualization (NFV) card in LCT-NPT.
8.13.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
 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.
 Applicable to TS1~TS21, TS23, TS24


 Control interface: 1.25G SGMII (2x)
 NFVG_4 can be assigned in Tslot of NPT-1200i;
 Applicable to TS1, TS2, TS3, TS4, TS6, TS7
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
 Internal port
When you activate a port on NFVG_4, you must assign the port role – local port or internal port. Local port
of NFVG_4 has no L2 attributes. Internal ports are same as other DH card ports.
The internal ports of NFVG_4 on NPT-1800 & NPT-1200i can support LAG configuration.

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
Activate/Deactivate Port window opens.
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 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.13.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.13.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.14 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.14.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-9: 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
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.14.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-10: 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
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.14.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-11: 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.14.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.14.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.14.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.14.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.14.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.14.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.14.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.14.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.14.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.14.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.15 Optics cards

This section describes how to configure the SM10 and the OBC card Erbium Doped Fiber Amplifier (EDFA)
settings.
8.15.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.15.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.16 PCM cards

This section describes how to access, assign, and configure the SM10, SM_10E, and EM_10E cards.
8.16.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.16.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.16.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. The Slot Assignment window opens.
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.

8.16.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.16.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.
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.16.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


8.16.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.16.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,

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.16.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,


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.16.2.6 Reassign 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.16.2.7 Perform 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 Mode Rate Adaption
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.16.2.8 Perform SM_10E/EM_10E FXS hotline

Ring back tone for hot line is supported on FXS of SM_FXS_8E. A hotline is defined as a direct connection
between two FXS interfaces. In LCT-NPT V6.0 or higher, hotline is improved to support standard ring back
tone, disconnection signaling (busy tone) and howl tone.
To establish the hotline between two FXS interfaces:
1. The hot-line attribute of two FXS interfaces are enabled;
 Usually the two FXS are on different SM_10E/EM_10E cards on different sites.
2. Create VC-12/E1 connection between two SM_10E cards, for EM_10E cards, create CES service;
3. The E1 CAS signaling type is set to "E&M Type I with B=0";
4. Create bidirectional 64K XC between the FXS and E1 on each SM_10E.
Following are the example procedures about how to perform SM_10E FXS hotline.

To perform SM_10E/EM_10E FXS hotline:

1. Assign FXS to SM_10E/EM_10E in both NEs.
2. Set the Frame Attribute of E1 Port 1 as PCM30 (SM_10E) or PCM30-no-CRC (EM_10E).

Note that the two NEs must be consistent.

3. Configure PCM XC from FXS to E1_PCM on ES1 and ES3.
4. Configure XC from E1 PCM on SM_10E to SMQ or other port which can connect to peer NE.

5. For EM_10E FXS hotline configuration, configure CES VSI on EM_10E and configure to peer NE. CES
VSI is same to the other CES card.
6. Set the CAS signaling of configured E1 Port 1 as EM Type 1 With B=0.

7. Set FXS Hot Line as Enable on ES1 and ES3.

8.16.2.9 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.16.2.10 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.

2. 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).
3. 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.16.3 EM_10E
EM_10E can be assigned in NPT-1020/NPT-1021 and NPT-1200 (with CPTS100/CPS100 assigned).
8.16.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.16.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.16.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.


8.16.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.17 MXC cards

This section describes MXC4X and MXC-20/MXC-20C cards in LCT-NPT.
8.17.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.17.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.17.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.17.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.18 Control cards

This section describes the control cards.
8.18.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.18.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
working mode, select the Management Ports tab.

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.18.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 working mode, select the Management Ports tab.

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.18.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.18.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.19 Power units

This section describes the power units.
8.19.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.19.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,
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.19.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
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-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.

object tree, under Control and Physical Object, select INF-1010. In the Configuration working mode,

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.

object 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.19.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.20 Fan control units

8.20.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.21 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.21.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.

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

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.21.2 Manage a LAG

For details about managing LAGs in DMGE_8_POS, see LAG Improvement in the LCT-NPT Service
Management Guide.
8.21.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-12: 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.21.3.1 POS mirroring supported cards

POS mirroring is supported by the DMGE_8_POS card.
8.21.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.21.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.22 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.23 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-13: 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.23.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.23.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


8.23.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.23.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
working mode, select the General tab.

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.23.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.23.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.24 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.25 Tributary protection card

8.25.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
MCIPS560 Y Central packet switching card with timing unit and four SFP+ based 10GE ports.
560Gbit/s packet switch (fan out up to 560Gbit/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.
DHCE_1Q Y Ethernet IO card for T-slot with one QSFP28 based 100GE port
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)
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.

LCT-NPT® User Guide Configure and manage cards in IP/MPLS
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 (MS1_4/MSE1_32)

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 IP/MPLS NEs.
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.
This section describes the management of MSC_2_8 card in IP/MPLS NEs.
The management of MS1_4 or MSE1_32 in IP/MPLS NEs is the same with MSC_2_8.
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
Activate/Deactivate Port window opens.
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.
2. To retrieve the information to view, click .

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.
You can view the general information and inventory of the CF card.
2. To view CF card general information in NPT-1050 NEs, in the left object tree, select NVM under
MCPTS100, then in the Configuration working mode, select the General tab.


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 the MCIPS560

MCIPS560 is a new matrix card for NPT-1200i, which enables up to four 100GE ports in TS2/TS3/TS4/TS7 in
NPT-1200i shelf. With MCIPS560, NPT-1200i switch capacity (throughput) increased to 560Gbps.
Following lists the main features of MCIPS560:
 System controller unit (MCP)
 With front panel extractable NVM – 8GB micro SD;
 8GB DDR3L memory.
 560Gbps Packet processor and Traffic management with layer2 and layer 3 functionality;
 Sync-E timing unit and IEEE1588v2 timing unit;
 Built-in 4 x 10GE ports
 Support 1+1 and 1+0[1] configuration for MCIPS560;
 MP, CP and DP are fully redundant with MCIPS560 1+1.
 MCP and CIPS are both hot-standby
 Timing functionality:
 Sync-E timing unit (EEC)
 Comply with ITU-G.8262
 T3/T4 interface (2048KHz and 2048Kbit/s)
 IEEE1588v2 timing unit (PEC)
 ITU-T G.8265.1 profile (OC master and slave, BC)
 ITU-T G.8275.1 profile (T-GM, T-BC)
 1PPS/ToD interface

 Aggregate ports on MCIPS560

 Four SFP+ based 10GE ports, each can be configured as:
 10GBase-R
 10GBase-W
 10GBase-R with OTN wrapping – OTU2e, support RS FEC and EFEC (I4, I7)
 Full mesh connection to both active packet switch and standby packet switch for MCIPS redundancy
 Existing IO cards supported by MCIPS560:
Ethernet cards
 DHGE_8 – Ethernet IO card with 4/8 × 1000Base-X ports based on SFP/CSFP and full bandwidth
connection to central packet switching matrix;
When installed in TS2, TS3, TS4 and TS7 only SFP’s can be assigned.
 DHGE_4E – Ethernet IO card with 4 × 10/100/1000Base-T and full bandwidth connection to
central packet switching matrix;
 DHGE_16 – Ethernet IO card with 8 × 10/100/1000Base-T ports and 4/8 × 1000Base-X ports
based SFP/CSFP, with full bandwidth connection to central packet switching matrix;
 DHGE_24 – Ethernet IO card with 12/24 × 1000Base-X ports based on SFP/CSFP and full
bandwidth connection to central packet switching matrix;
Only 16 ports can be activated when DHGE_24 is working in MCIPS560 system, P17-P24 can't be
used.
 DHXE_4O – Ethernet IO card with four SFP+ based 10GE ports with optional OTU2e wrapping &
FEC/EFEC support and full bandwidth connection to central packet switching matrix;
 DHXE_4 – Ethernet IO card with four SFP+ based 10GE ports and full bandwidth connection to
central packet switching matrix.
 DHXE_2 – Ethernet IO card with two SFP+ based 10GE ports with optional OTU2e wrapping &
FEC/EFEC support and full bandwidth connection to central packet switching matrix.
CES cards
 MSC_2_8 – Combo CES card with 2 channelized STM-1/OC-3 interfaces and 8 E1/T1 interface
and 2 x 1G Ethernet connection to central packet switching matrix.
 MS1_4 – CES card with 4 x STM-1/OC-3 or 1 x STM-4/OC-12 interfaces
 DMCE1_32 – CES card with 32 x E1/T1
Other cards
 OBC – Optical base card with OM_BA/PA/ILA/LVM and OM_DCMxx support.
 NFVG_4 – NFV card with 4 GbE ports (local or internal).
All MPLS-TP, IP/MPLS and PTP/CES features of MCIPS320 in NPT-1200i is supported in MCIPS560.

9.10 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.11 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.11.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 fiollowing 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.11.2 Manage the fan units of NPT-1200i

The fan unit of NPT-1200i is FCU-1200/FCU-1200B.
From LCT-NPT V6.1, FCU-1200B is a new fan unit for NPT-1200i:
 The FCU-1200B is a pluggable fan control module with eight fans for cooling the NPT-1200 platform,
with enhanced feature – PWM (vs. FCU-1200) in order to optimize the cooling efficiency and increase
fan operation life;
 FCU-1200B is fully backward compatible with FCU-1200, it can replace FCU-1200 in any version;
 When the FCU-1200B is installed in NPT-1200/NPT-1200i V6.0 or old versions, the FCU-1200B behaves
same as FCU-1200 – totally 16 different levels can set for the fan speed control by adjusting the fan
power supply voltage.;
 When FCU-1200B is installed in NPT-1200i V6.1 or NPT-1200 V7.0 (or higher version), the PWM feature
will be enabled and fan speed control is based on PWM duty cycle – totally 8 levels can be set;
 By default, fan speed is controlled by SW according to installed cards temperature, and "force turbo" is
supported for maintenance purpose.
To manage FAN units of NPT-1200i:

1. To view the general information of FCU-1200/FCU-1200B, in the NPT-1200i NE Shelf View window, in
the left object tree, select the FCU-1200/FCU-1200B object, then select the General tab under the
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.

LCT-NPT® User Guide Configure timing source
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.
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. The following window opens.
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
(SFP only)
1000Base-T No
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
MGE_8
GbE 5#-8# 100Base-FX Yes
(MCPS_1010)
1000Base-X Yes
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.
The default value is 0.
 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,e 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.

LCT-NPT 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 User Guide

Uploaded by

Copyright:

Available Formats

LCT-NPT®

Native Packet Transport

ECI's management applications run on VMWare virtualization hypervisors.

© Copyright by ECI, 2013-2018. 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-8

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 IS-IS LDP FRR status ...................................................................................................... 7-45

ECI Telecom Ltd. Proprietary vi

7.8.9 View PIM statistics ................................................................................................................ 7-90

ECI Telecom Ltd. Proprietary vii

7.19 Manage MSTP .................................................................................................................... 7-140

8 Configure and manage cards ....................................................................... 8-1

ECI Telecom Ltd. Proprietary viii

8.2 Work with cards ................................................................................................................... 8-14

ECI Telecom Ltd. Proprietary ix

8.10.2 DMEOP_4 ............................................................................................................................ 8-126

ECI Telecom Ltd. Proprietary x

8.18.3 MCP-1200 ............................................................................................................................ 8-281

9 Configure and manage cards in IP/MPLS ..................................................... 9-1

ECI Telecom Ltd. Proprietary xi

9.5.1 Activate/Deactivate the MSC_2_8 ports ............................................................................... 9-14

10 Configure timing source ............................................................................ 10-1

ECI Telecom Ltd. Proprietary xii

10.5.15 Work in services .................................................................................................................. 10-55

ECI Telecom Ltd. Proprietary xiii

ECI Telecom Ltd. Proprietary xiv

Hardware and software requirements

ECI Telecom Ltd. Proprietary 1-1

To install the LCT-NPT:

2. Select Install LCT-NPT.

ECI Telecom Ltd. Proprietary 2-1

ECI Telecom Ltd. Proprietary 2-2

To log in to the Boot Configuration Tool:

3. Double-click the Boot Configuration Tool icon on your desktop.

5. Select a card by selecting the relevant button.

ECI Telecom Ltd. Proprietary 3-1

Select one of the login options as appropriate:

ECI Telecom Ltd. Proprietary 3-2

3.1 IP address in boot status

Table 3-1: IP address in boot status

ECI Telecom Ltd. Proprietary 3-3

NE MCP card Port IP in boot status Note

ECI Telecom Ltd. Proprietary 3-4

NE MCP card Port IP in boot status Note

3.2 Configure basic parameters

Table 3-2: Basic parameters terminology

ECI Telecom Ltd. Proprietary 3-5

To configure basic parameters:

2. For pure packet applications, disable DCC.

ECI Telecom Ltd. Proprietary 3-6

3.3 Download embedded software and FPGA file

To download embedded software:

ECI Telecom Ltd. Proprietary 3-7