BG 20 Eci Mux PDF

BroadGate LCT-BGF
User Manual
Version 7
426006-2413-013-A00
LCT-BGF User Manual
V7
Catalog No: X36346
May 2007
1st Edition
Copyright by ECI Telecom, 2005-2007. All rights reserved worldwide.

This is a legal agreement between you, the end-user, and ECI Telecom Ltd. (ECI Telecom). BY OPENING THE
DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS
AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE
UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING
WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU
OBTAINED THEM.
The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright,
patent, and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's
rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or
disk may be published, reproduced, or disclosed to third parties, in whole or in part, without the express prior
written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the
information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden.
ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or
specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no
responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which
may be affected in any way by the use and/or dissemination thereof.
Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for
informational purposes only and are not warranties of product performance or otherwise, either express or implied.
ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty
offered by ECI Telecom.
The documentation and/or disk is provided AS IS and may contain flaws, omissions, or typesetting errors. No
warranty is granted nor liability assumed in relation thereto, unless specifically undertaken in ECI Telecom's sales
contract or order confirmation. Information contained in the documentation and in the disk is periodically updated,
and changes will be incorporated in subsequent editions. If you have encountered an error, please notify ECI
Telecom. All specifications are subject to change without prior notice.
The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by
all relevant copyright, patent, and other applicable laws and international treaty provisions. Therefore, you must
treat the information contained in the documentation and disk as any other copyrighted material (for example, a
book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as
applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR
ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT
EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM.
All trademarks mentioned herein are the property of their respective holders.
ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever
caused, arising directly or indirectly in connection with this documentation and/or disk, the information contained
therein, its use, or otherwise. Notwithstanding the generality of the aforementioned, you expressly waive any claim
and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage which may arise
in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if
advised of the possibility of such damages.
Contents
About This Manual ................................................................... xv
Intended Audience ............................................................................................. xv
Document Organization......................................................................................xv
Document Conventions .................................................................................... xvii
Related Documentation.................................................................................... xvii
Obtaining Technical Documentation ................................................................xviii
Technical Assistance........................................................................................xviii
Introducing the LCT ................................................................ 1-1

Overview .......................................................................................................... 1-1
Hardware and Software Requirements ............................................................ 1-2
Installing the LCT .................................................................... 2-1

Overview .......................................................................................................... 2-1
Installing the LCT-BGF Application .................................................................. 2-2
Using the Boot Configuration Tool ........................................ 3-1

Overview .......................................................................................................... 3-1
Boot Configuration Tool Procedures ................................................................ 3-2
Downloading Embedded Software and the FPGA File .................................... 3-5
Obtaining IDPROM Data .................................................................................. 3-8
Configuring the No Recovery Next Startup Attribute........................................ 3-9
Configuring the Serial Port Close Attribute..................................................... 3-10
Getting Started with the LCT GUI........................................... 4-1

Overview .......................................................................................................... 4-1
Starting the LCT GUI........................................................................................ 4-2
Configuring Parameters ................................................................................... 4-4
Configuring Static IP Routes ............................................................................ 4-6
Managing NEs.......................................................................... 5-1

Configuring NEs ............................................................................................... 5-1
Resetting NEs .................................................................................................. 5-8
Configuring Orderwire Attributes ...................................................................... 5-9
Configuring Communication Parameters ....................................................... 5-13
Managing Cards....................................................................... 6-1

Configuring Card Attributes .............................................................................. 6-1
Resetting a Card .............................................................................................. 6-3
Viewing the Electronic Card Label ................................................................... 6-4
426006-2413-013-A00 ECI Telecom Ltd. Proprietary i

Contents LCT-BGF User Manual
Viewing Card Information ................................................................................. 6-5

Managing BG-20 Special Cards....................................................................... 6-6
Managing FE_L12 Card Special Attributes .................................................... 6-10
Configuring ESW_2G_8F Special Attributes.................................................. 6-20
Configuring Ethernet Attributes ...................................................................... 6-36
Managing Cross Connections ................................................ 7-1

Overview .......................................................................................................... 7-1
Configuring and Managing Server Trail XCs .................................................... 7-1
Configuring and Managing Client Trail XCs ................................................... 7-10
Setting Up MSP 1+1 XC Protection................................................................ 7-17
Configuring SNCP Attributes.......................................................................... 7-20
Exporting Trails as a File................................................................................ 7-22
Importing Trails from a File............................................................................. 7-24
Uploading XCs ............................................................................................... 7-25
Configuring Timing Sources .................................................. 8-1

Overview .......................................................................................................... 8-1
Configuring Synchronous Timing ..................................................................... 8-2
Configuring the Synchronous Timing Table ..................................................... 8-3
Viewing the SEC Work Mode and External Clock References ........................ 8-5
Calibrating the Clock Card Frequency ............................................................. 8-6
Managing Alarms..................................................................... 9-1

Overview .......................................................................................................... 9-1
Managing Current Alarms ................................................................................ 9-2
Managing Historical Alarms.............................................................................. 9-8
Masking Alarms.............................................................................................. 9-11
Using the NE Alarm Log................................................................................. 9-13
Configuring Alarm Attributes .......................................................................... 9-16
Correcting Alarms........................................................................................... 9-20
Managing External Alarms ............................................................................. 9-20
Monitoring Performance ....................................................... 10-1

Overview ........................................................................................................ 10-1
Viewing Current Performance ........................................................................ 10-5
Viewing Recent Performance......................................................................... 10-7
Setting Performance Thresholds.................................................................... 10-8
Using the Performance Monitoring Switch Operation .................................. 10-10
Resetting Performance Counters ................................................................. 10-13
Managing LCT-BGF Security................................................ 11-1

Overview ........................................................................................................ 11-1
Configuring the LCT Work Mode.................................................................... 11-2
ii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

LCT-BGF User Manual Contents
Performing Maintenance Operations................................... 12-1

Using the Maintenance List ............................................................................ 12-1
Performing Loopback Operations................................................................... 12-2
Performing AIS/PRBS/RDI Operations .......................................................... 12-5
Saving NE Configuration Data ....................................................................... 12-9
Clearing the NE Configuration........................................................................ 12-9
Downloading NE Database Files.................................................................. 12-10
Performing a Software Upgrade................................................................... 12-11
Performing Activation Time/Version Activate Operations............................. 12-13
Performing Other Maintenance Operations.................................................. 12-17
Performing Advanced Configuration................................... 13-1

Overview ........................................................................................................ 13-1
Enabling the BG-40 NE Proxy ARP ............................................................... 13-2
Configuring the BG-40 NE ARP List............................................................... 13-3
Displaying DCC MIB Counters ....................................................................... 13-5
Configuring the BG-40 NE Serial Port............................................................ 13-6
Clearing the Flash .......................................................................................... 13-7
Configuring the BG-20 NE Trap Manager Table ............................................ 13-7
Configuring BG-20 NE SNMP Agent Mode.................................................... 13-9
Configuring the PCM Card.................................................... 14-1

Overview ........................................................................................................ 14-1
Assigning a PCM Card ................................................................................... 14-4
PCM Configuration Management ................................................................... 14-7
Managing SM10 XCs ................................................................................... 14-35
Managing SM_10E XCs ............................................................................... 14-41
Managing PCM Faults.................................................................................. 14-47
Performing PCM Maintenance ..................................................................... 14-59
Managing Licenses ............................................................... 15-1

Overview ........................................................................................................ 15-1
License Control Mechanism ........................................................................... 15-2
License Control Workflow............................................................................... 15-3
License Format............................................................................................... 15-4
Managing Licenses in the LCT-BGF .............................................................. 15-6
Glossary of Terms .................................................................. G-1
Index .......................................................................................... I-1
426006-2413-013-A00 ECI Telecom Ltd. Proprietary iii

Contents LCT-BGF User Manual
iv ECI Telecom Ltd. Proprietary 426006-2413-013-A00

List of Figures
Figure 2-1: LCT-BGF Installation CD window................................................................ 2-2
Figure 2-2: LCT-BGF Setup - LCT Welcome window.................................................... 2-3
Figure 2-3: LCT-BGF Setup - Setup Status window ...................................................... 2-3
Figure 2-4: LCT-BGF Setup - LCT System Config window ........................................... 2-4
Figure 2-5: LCT-BGF Setup - Installation Complete window......................................... 2-4
Figure 3-1: Boot Configuration Tool menu..................................................................... 3-2
Figure 3-2: Boot Configuration Tool window.................................................................. 3-2
Figure 3-3: Input IP window ........................................................................................... 3-3
Figure 3-4: Information window showing autologin confirmation ................................... 3-3
Figure 3-5: Basic Parameter Configuration window....................................................... 3-5
Figure 3-6: Download Embedded Software window ...................................................... 3-6
Figure 3-7: BG-40 Download FPGA File window........................................................... 3-7
Figure 3-8: BG-20 IDPROM window.............................................................................. 3-8
Figure 3-9: BG-20 No Recovery Next Startup window .................................................. 3-9
Figure 3-10: BG-20 Serial Port Close Flag window ..................................................... 3-10
Figure 4-1: LCT GUI Login window................................................................................ 4-2
Figure 4-2: LCT-Login BG-40 NE window ..................................................................... 4-3
Figure 4-3: LCT-Login BG-20 NE window ..................................................................... 4-3
Figure 4-4: Basic Parameter Configuration window....................................................... 4-5
Figure 4-5: Static IP Routes Configuration window ....................................................... 4-6
Figure 5-1: NE Attributes window .................................................................................. 5-3
Figure 5-2: BG-40 Slot Assignment window .................................................................. 5-5
Figure 5-3: BG-20 Slot Assignment window .................................................................. 5-6
Figure 5-4: Card Max Traffic Setup window................................................................... 5-7
Figure 5-5: Device Reset Operation window ................................................................. 5-8
Figure 5-6: Orderwire Configuration window - Setting the Orderwire Attribute tab ..... 5-10
Figure 5-7: Orderwire Configuration window - Setting Orderwire Routing tab ............ 5-11
Figure 5-8: Orderwire Configuration window - BG-20.................................................. 5-12
Figure 5-9: NE Connection Settings window ............................................................... 5-14
Figure 5-10: DCC Configuration and DCC Overhead Management window .............. 5-15
Figure 5-11: DCC Configuration and DCC Overhead Management window -
DCC Access tab ........................................................................................................... 5-16
VC12 To SM10 tab....................................................................................................... 5-17
V.35 Work Mode tab .................................................................................................... 5-18
DCCSwap Attribute tab ................................................................................................ 5-19
426006-2413-013-A00 ECI Telecom Ltd. Proprietary v

List of Figures LCT-BGF User Manual

DCC Cross tab ............................................................................................................. 5-20
DCC Overhead Configuration tab ................................................................................ 5-21
Figure 6-1: Card Attributes Setup window ..................................................................... 6-2
Figure 6-2: Device Reset Operation window ................................................................. 6-3
Figure 6-3: Electronic Label window .............................................................................. 6-4
Figure 6-4: Card Information window............................................................................. 6-5
Figure 6-5: BG-20 slot assignment ................................................................................ 6-6
Figure 6-6: BG-20 NE Shelf View window ..................................................................... 6-7
Figure 6-7: BG-20 Slot Assignment window - Logical tab ............................................. 6-8
Figure 6-8: SAM1 internal view ...................................................................................... 6-9
Figure 6-9: SAM4 internal view ...................................................................................... 6-9
Figure 6-10: SAM pop-up menu................................................................................... 6-10
Figure 6-11: FE_L12 card window ............................................................................... 6-12
Figure 6-12: VCG Attribute window - Traffic tab .......................................................... 6-13
Figure 6-13: Get FEM Time Slot Resource window..................................................... 6-14
Figure 6-14: VCG Member Add Attribute Set window ................................................. 6-15
Figure 6-15: EOS Protocol window.............................................................................. 6-15
Figure 6-16: CID Table window.................................................................................... 6-16
Figure 6-17: Port Attributes window............................................................................. 6-17
Figure 6-18: Get Current Payload Rate window .......................................................... 6-18
Figure 6-19: MST Maintenance window ...................................................................... 6-19
Figure 6-20: ESW_2G_8F card.................................................................................... 6-21
Figure 6-21: ESW_2G_8F network architecture .......................................................... 6-21
Figure 6-22: ESW_2G_8F card window ...................................................................... 6-24
Figure 6-23: ESW_2G_8F card window ...................................................................... 6-26
Figure 6-24: VCG Attribute window - Traffic tab .......................................................... 6-27
Figure 6-25: VCG Attribute window - LCAS tab........................................................... 6-28
Figure 6-26: VCG Member Add Attribute Set window ................................................. 6-29
Figure 6-27: EOS Protocol window.............................................................................. 6-30
Figure 6-28: Port Attributes window for WAN ports ..................................................... 6-31
Figure 6-29: Port Attributes window for LAN ports....................................................... 6-32
Figure 6-30: Get Current Payload Rate window .......................................................... 6-33
Figure 6-31: Port Connected Neighbor window ........................................................... 6-34
Figure 6-32: MST Maintenance window ...................................................................... 6-35
Figure 6-33: Loopback Setup window.......................................................................... 6-36
Figure 6-34: FE_L12 card window showing how to access the Layer 2 Switch
Configuration Management window............................................................................. 6-37
Figure 6-35: L2 Switch Configuration Management window - Port Attributes tab ....... 6-39
Figure 6-36: L2 Switch Configuration Management window - VLAN tab..................... 6-42
Figure 6-37: Create a VLAN window ........................................................................... 6-43
Figure 6-38: Modify VLAN window............................................................................... 6-44
vi ECI Telecom Ltd. Proprietary 426006-2413-013-A00

LCT-BGF User Manual List of Figures
Figure 6-39: L2 Switch Configuration Management window - FDB tab ....................... 6-46
Figure 6-40: L2 Switch Configuration Management window - Bridge STP tab............ 6-51
Figure 6-41: L2 Switch Configuration Management window - Port STP tab ............... 6-53
Figure 6-42: L2 Switch Configuration Management window - Priority tab ................... 6-55
Figure 6-43: Up/Down Load Bridge Configuration Data window ................................. 6-57
Figure 6-44: Task window showing clear configuration data operation ....................... 6-59
Figure 6-45: Task window showing save configuration data operation ....................... 6-60
Figure 6-46: Bandwidth Profile window........................................................................ 6-61
Figure 6-47: Create Policer window............................................................................. 6-62
Figure 6-48: Policer List window .................................................................................. 6-63
Figure 6-49: Policer List window showing filters .......................................................... 6-64
Figure 6-50: Policer List window - editing the policer list ............................................. 6-65
Figure 6-51: Edit Policer window.................................................................................. 6-65
Figure 6-52: Policer Upload window - Policer Upload tab ........................................... 6-66
Figure 6-53: Policer Upload window - Policer Compare tab ........................................ 6-67
Figure 6-54: ESW_2G_8F - EPL.................................................................................. 6-68
Figure 6-55: ESW_2G_8F - EVPLAN .......................................................................... 6-68
Figure 6-56: Create VPN window (EPL) ...................................................................... 6-69
Figure 6-57: Create VPN window (EVPLAN)............................................................... 6-70
Figure 6-58: Create VPN window (EVPLAN) - select NNI ports.................................. 6-71
Figure 6-59: Create VPN window (EVPLAN) - add policer.......................................... 6-72
Figure 6-60: Create VPN window (EVPLAN) - mapped policer................................... 6-73
Figure 6-61: VPN List window...................................................................................... 6-74
Figure 6-62: VPN List window showing filter options................................................... 6-74
Figure 6-63: VPN Upload window - VPN Upload tab................................................... 6-75
Figure 6-64: VPN Upload window - VPN Compare tab ............................................... 6-76
Figure 6-65: VPN List window showing menu options................................................. 6-76
Figure 6-66: View VPN window.................................................................................... 6-77
Figure 6-67: Edit VPN window ..................................................................................... 6-78
Figure 6-68: Export VPN List window .......................................................................... 6-79
Figure 6-69: Select File window ................................................................................... 6-79
Figure 6-70: Import VPN List and Select File windows................................................ 6-80
Figure 6-71: Import VPN List window showing import results ..................................... 6-81
Figure 6-72: Global vFIB Attributes window................................................................. 6-82
Figure 6-73: Trace MAC window.................................................................................. 6-84
Figure 6-74: MSTP Configuration window - General tab ............................................. 6-86
Figure 6-75: MSTP Configuration window - Instance tab ............................................ 6-87
Figure 6-76: MSTP Port Configuration window - Port Attributes tab ........................... 6-89
Figure 6-77: MSTP Configuration window - Instance Attribute tab.............................. 6-90
Figure 6-78: Link aggregation ...................................................................................... 6-91
Figure 6-79: Create/Edit Aggregation Ports window.................................................... 6-92
Figure 6-80: ESW_2G_8F card window showing aggregation groups ........................ 6-93
426006-2413-013-A00 ECI Telecom Ltd. Proprietary vii

Figure 6-81: Trunk Mode window ................................................................................ 6-94

Figure 6-82: Up/Down Load Bridge Configuration Data window ................................. 6-97
Figure 7-1: Manual Trail Management - Create Server Trail XC window -
Create XC tab................................................................................................................. 7-2
Send List tab .................................................................................................................. 7-3
XC List tab...................................................................................................................... 7-4
Figure 7-4: Manual Trail Management - Create Server Trail XC window ...................... 7-6
Figure 7-5: Deactivate a client trail confirmation window............................................... 7-8
Figure 7-6: Confirmation message when deleting a server trail .................................... 7-9
Figure 7-7: Manual Trail Management - Create Client Trail XC window -
Create XC tab............................................................................................................... 7-10
Figure 7-8: Client Trail List window.............................................................................. 7-11
Figure 7-9: Client Trail List window.............................................................................. 7-13
Figure 7-10: Client Trail List window............................................................................ 7-15
Figure 7-11: Deactivate a client trail confirmation window........................................... 7-16
Figure 7-12: MSP 1+1 .................................................................................................. 7-17
Figure 7-13: Create PG window................................................................................... 7-18
Figure 7-14: MSP Linear 1+1 PG List window............................................................. 7-19
Figure 7-15: LCT Login BG-40 NE window.................................................................. 7-19
Figure 7-16: MSP Linear 1+1 PG List window............................................................. 7-20
Figure 7-17: SNCP Attributes window ......................................................................... 7-21
Figure 7-18: Export XCs to File window....................................................................... 7-22
Figure 7-19: Select File window ................................................................................... 7-23
Figure 7-20: Import Trail From File window ................................................................. 7-24
Figure 7-21: Import Trail From File window showing importing of a server trail .......... 7-25
Figure 7-22: XCs Upload window - Upload XCs tab .................................................... 7-26
Figure 7-23: XCs Upload window - Compare Result tab ............................................. 7-27
Figure 8-1: Timing configuration window - Timing Configuration tab............................. 8-2
Figure 8-2: Timing configuration window showing synchronous timing configuration ... 8-3
Figure 8-3: Timing Configuration window - Timing Maintenance tab............................. 8-5
Figure 9-1: Current Alarm View window ........................................................................ 9-2
Figure 9-2: Current Alarm View window - Show Data tab ............................................. 9-4
Figure 9-3: Current Alarm View window - Filter Option tab ........................................... 9-6
Figure 9-4: Current Alarm View window - Alarm Chart tab............................................ 9-7
Figure 9-5: History Alarm View window ......................................................................... 9-8
Figure 9-6: History Alarm View window ......................................................................... 9-9
Figure 9-7: Alarm Source Mask Configuration window................................................ 9-12
Figure 9-8: Alarm Log window ..................................................................................... 9-13
Figure 9-9: Alarm Log window ..................................................................................... 9-14
Figure 9-10: Severity window - Alarm Attributes Table tab.......................................... 9-16
Figure 9-11: Severity window - Alarm Miscellaneous Configuration tab...................... 9-17
viii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

Figure 9-12: External Alarm window ............................................................................ 9-21

Figure 10-1: Get Current Performance window ........................................................... 10-6
Figure 10-2: Recent Performance window................................................................... 10-7
Figure 10-3: Performance Threshold window .............................................................. 10-9
Figure 10-4: Performance Configuration window - Collecting Schedule tab ............. 10-11
Figure 10-5: Performance Configuration window - Object Attribute tab .................... 10-12
Figure 11-1: Information window showing LCT work mode......................................... 11-2
Figure 11-2: Task window for setting the LCT work mode as master.......................... 11-3
Figure 11-3: Information window for setting the LCT work mode as monitor .............. 11-3
Figure 12-1: Maintenance List window ........................................................................ 12-2
Figure 12-2: Loopback example................................................................................... 12-3
Figure 12-3: Loopback Setup window.......................................................................... 12-3
Figure 12-4: Insert PRBS ............................................................................................. 12-5
Figure 12-5: PRBS Insert and Monitor window............................................................ 12-6
Figure 12-6: Force AIS/RDI window ............................................................................ 12-7
Figure 12-7: Clear SDH Configuration window ............................................................ 12-9
Figure 12-8: Get/Download NE DB File window ........................................................ 12-10
Figure 12-9: Select Directory window ........................................................................ 12-11
Figure 12-10: Download Embedded Software window.............................................. 12-12
Figure 12-11: Download FPGA File window .............................................................. 12-13
Figure 12-12: Activation Time window ....................................................................... 12-14
Figure 12-13: Version Activate window...................................................................... 12-15
Figure 12-14: Upgrade Confirmation window ............................................................ 12-16
Figure 12-15: Remote Login window ......................................................................... 12-17
Figure 12-16: Telnet window...................................................................................... 12-18
Figure 12-17: Laser Switch Status window................................................................ 12-19
Figure 12-18: Fan Status window .............................................................................. 12-20
Figure 12-19: Power Type Management window ...................................................... 12-21
Figure 13-1: Example of ARP configuration................................................................. 13-2
Figure 13-2: Proxy ARP window .................................................................................. 13-3
Figure 13-3: Proxy ARP Table window ........................................................................ 13-4
Figure 13-4: IP Configuration window.......................................................................... 13-4
Figure 13-5: Channel MIB Counters window ............................................................... 13-5
Figure 13-6: Serial Port Configuration window ............................................................ 13-6
Figure 13-7: Confirm window ....................................................................................... 13-7
Figure 13-8: Trap Manager Table window ................................................................... 13-8
Figure 13-9: SNMP Agent Mode window..................................................................... 13-9
Figure 14-1: Slot Assignment window.......................................................................... 14-4
Figure 14-2: LCT-Login BG-40 NE window ................................................................. 14-5
Figure 14-3: PCM NE Shelf View window.................................................................... 14-5
Figure 14-4: BG-30 Shelf View window ....................................................................... 14-6
Figure 14-5: SM_10E Shelf View window.................................................................... 14-6
426006-2413-013-A00 ECI Telecom Ltd. Proprietary ix

Figure 14-6: Set Subcard Attributes window showing frame attribute for SM10 ......... 14-7
Figure 14-7: Set Subcard Attributes window - E1 Physical Connection Attribute tab.. 14-8
Figure 14-8: Set Subcard Attributes window - FE Board Attribute tab......................... 14-9
Figure 14-9: Set Subcard Attributes window - User Interface tab.............................. 14-10
Figure 14-10: Set Subcard Attributes window - SM_V35_2 ...................................... 14-11
Figure 14-11: Set Subcard Attributes window - SM_Omnicentor Card Attribute tab. 14-12
Figure 14-12: Set Subcard Attributes window............................................................ 14-13
Figure 14-13: Set Subcard Attributes window for SM_V24 card - 1 channel ............ 14-14
Figure 14-14: Set Subcard Attributes for SM_V24 card - 2 channels........................ 14-15
Figure 14-15: Set Subcard Attributes window for SM_V24 card - 8 channels........... 14-16
Figure 14-16: Set Subcard Attributes window - E1_PCM.......................................... 14-17
Figure 14-17: Set Subcard Attributes window - SM_EM_24W_6E............................ 14-18
Figure 14-18: Set Subcard Attributes window - SM_FXS_8E ................................... 14-19
Figure 14-19: Set Subcard Attributes window - SM_V35E ........................................ 14-20
Figure 14-20: Set Subcard Attributes window - SM_Omni_E.................................... 14-20
Figure 14-21: Set Subcard Attributes window - SM_10E .......................................... 14-21
Figure 14-22: Set Subcard Attributes window - SM_V24E - 2 channels ................... 14-22
Figure 14-25: Set Subcard Attributes window - SM_V24E card - point-to-multipoint 14-25
Figure 14-26: Board Assignment window .................................................................. 14-26
Figure 14-27: SM10E Slot Assignment window......................................................... 14-27
Figure 14-28: Sync Timing Configuration window ..................................................... 14-28
Figure 14-29: SM10E Timing Configuration window - SyncTiming
Configuration tab ........................................................................................................ 14-29
Figure 14-30: SM10E Timing Configuration window - Timing Trace tab ................... 14-30
Figure 14-31: Get Clock Work Mode window ............................................................ 14-31
Figure 14-32: Upload/Download PCM Configuration Data window ........................... 14-32
Figure 14-33: XCs Upload window - XCs Upload tab ................................................ 14-33
Figure 14-34: XCs Upload window showing comparison results............................... 14-34
Figure 14-35: Create XC window ............................................................................... 14-35
Figure 14-36: Create XC window - Send List tab....................................................... 14-36
Figure 14-37: XC Management window - XC List tab................................................ 14-37
Figure 14-38: Set Ethernet Timeslot Share Sign window .......................................... 14-38
Figure 14-39: Upload XCs window - XCs Upload tab ................................................ 14-39
Figure 14-40: Upload XCs window - Compare Result tab ......................................... 14-40
Figure 14-41: XCs Upload window - XCs In Local Database But Not In NE page .... 14-41
Figure 14-42: Create XC window - SM_10E.............................................................. 14-42
Figure 14-43: Create XC window - Send List tab - SM_10E ..................................... 14-43
Figure 14-44: XC Management window - SM_10E.................................................... 14-44
Figure 14-45: Upload XCs window - XCs Upload tab - SM_10E............................... 14-45
Figure 14-46: Upload XCs window - Compare Result tab - SM_10E ........................ 14-46
x ECI Telecom Ltd. Proprietary 426006-2413-013-A00

Figure 14-47: Upload XCs window - Compare Result tab - XCs in Local
Database but Not in NE page - SM_10E ................................................................... 14-47
Figure 14-48: PCM Event window.............................................................................. 14-49
Figure 14-49: PCM Alarm window - Current Alarm tab.............................................. 14-50
Figure 14-50: Alarm Filter (PCM) window.................................................................. 14-51
Figure 14-51: Select File window ............................................................................... 14-51
Figure 14-52: PCM Alarm window - History Alarm tab .............................................. 14-52
Figure 14-53: Set Alarm Attributes window................................................................ 14-54
Figure 14-54: Alarm Mask window............................................................................. 14-55
Figure 14-55: Alarm Severity window ........................................................................ 14-56
Figure 14-56: Current Alarm View window - SM_10E ............................................... 14-58
Figure 14-57: Return Command window displaying the run time .............................. 14-59
Figure 14-58: Run Time window - SM_10E ............................................................... 14-59
Figure 14-59: Run Command window displaying the SM10 card electronic label..... 14-60
Figure 14-60: SM_10E Shelf View window................................................................ 14-61
Figure 14-61: SM_10E Electronic Label window ....................................................... 14-61
Figure 14-62: Loopback Attribute window.................................................................. 14-62
Figure 14-63: Loopback Attribute window - SM_10E................................................. 14-63
Figure 14-64: PCM Ping window................................................................................ 14-64
Figure 14-65: Device Reset Operation window - SM_10E ........................................ 14-65
Figure 14-66: PCM NE Software Upgrade window.................................................... 14-66
Figure 14-67: Please select the file for upgrading window ........................................ 14-66
Figure 14-68: PCMNE Software Upgrade window after starting the upgrade ........... 14-67
Figure 15-1: License control workflow ......................................................................... 15-3
Figure 15-2: Workflow for manually inputting the license code ................................... 15-4
Figure 15-3: License File window ................................................................................ 15-6
Figure 15-4: Import License - Select File window ........................................................ 15-7
Figure 15-5: Export License - Select File window........................................................ 15-7
Figure 15-6: Activate License window ......................................................................... 15-8
Figure 15-7: BG-20 license sticker............................................................................... 15-8
Figure 15-8: Activate License window showing warning message.............................. 15-9
426006-2413-013-A00 ECI Telecom Ltd. Proprietary xi

xii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

List of Tables
Table 3-1: Basic parameters terminology ...................................................................... 3-4
Table 4-1: Parameter terminology ................................................................................. 4-4
Table 6-1: BG-20 slot assignment ................................................................................. 6-6
Table 6-2: Member status rules ................................................................................... 6-19
Table 6-3: Port attribute values .................................................................................... 6-20
Table 6-4: STP port status ........................................................................................... 6-50
Table 6-5: STP timers .................................................................................................. 6-52
Table 6-6: ESW_2G_8F MSTP timers......................................................................... 6-88
Table 10-1: Performance threshold value ranges........................................................ 10-8
Table 14-1: SM10 traffic modules ................................................................................ 14-2
Table 14-2: SM_10E traffic modules............................................................................ 14-3
Table 14-3: PCM alarm table ..................................................................................... 14-57
Table 15-1: License purchase order format ................................................................. 15-4
Table 15-2: License purchase order values................................................................. 15-5
Table 15-3: License file format..................................................................................... 15-5
Table 15-4: License file values..................................................................................... 15-6
426006-2413-013-A00 ECI Telecom Ltd. Proprietary xiii

List of Tables LCT-BGF User Manual
xiv ECI Telecom Ltd. Proprietary 426006-2413-013-A00

About This Manual
In this chapter:
Intended Audience............................................................................................ xv
Document Organization.................................................................................... xv
Document Conventions .................................................................................. xvii
Related Documentation .................................................................................. xvii
Obtaining Technical Documentation............................................................. xviii
Technical Assistance ..................................................................................... xviii
Intended Audience
The BroadGate LCT-BGF User Manual is intended for BG-40/BG-20
equipment installation personnel and field engineers.
Document Organization
The following list presents the information appearing in this guide:
| Chapter 1, Introducing the LCT-BGF - presents a general description of
the LCT-BGF and its main operational and technical features.
| Chapter 2, Installing the LCT-BGF - describes how to install the
LCT-BGF.
| Chapter 3, Using the Boot Configuration Tool - describes the procedures
available in the Boot Configuration Tool facility for configuring a new
element.
| Chapter 4, Getting Started with the LCT GUI - provides a
comprehensive description of GUI functionality for the LCT-BGF.
426006-2413-013-A00 ECI Telecom Ltd. Proprietary xv

About This Manual LCT-BGF User Manual
| Chapter 5, Managing NEs - describes how to configure NEs, Orderwire

attributes, and communication parameters, as well as how to reset NEs.
| Chapter 6, Managing Cards - describes how to view card-specific
information and how to configure card Ethernet attributes.
| Chapter 7, Configuring Cross Connections - describes cross-connection
(XC) configuration and management for both Server trails and Client trails.
| Chapter 8, Configuring Timing Sources - describes how to configure the
synchronous timing sources and timing table used by the system.
| Chapter 9, Managing Alarms - describes alarm management functions.
| Chapter 10, Monitoring Performance - describes the LCT-BGF
performance monitoring mechanisms, including viewing current and recent
performance.
| Chapter 11, Managing LCT-BGF Security - describes LCT-BGF
security measures and how to configure them.
| Chapter 12, Performing Maintenance Operations - describes how to
perform standard maintenance, such as loopback, path payload tests, and
consistency and connectivity checks.
| Chapter 13, Performing Advanced Configuration - describes the
advanced options available for advanced users.
| Chapter 14, Configuring the PCM Card - describes how to configure
and manage PCM equipment using the SM10 and SM_10E cards.
| Chapter 15, Managing Licenses - describes how to manage licenses for
the BG-20 NE, especially for Ethernet ports and the SAM module.
| Glossary of Terms - provides a list of frequently used terms and acronyms.
xvi ECI Telecom Ltd. Proprietary 426006-2413-013-A00

LCT-BGF User Manual About This Manual
Document Conventions
When applicable, this manual uses the following conventions.
Convention Indicates Example

Bold | Names of menus and In the Alarms menu...
commands
| User-typed
information
Menu > Option Selection from a menu, or Select Update > View
leading to another Objects
command
Italics New terms and emphasized Examples in text
text
Borders around text Notes, cautions, and See examples below
warnings
NOTE: Text set off in this manner presents clarifying

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

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

to follow directions could result in bodily harm or loss of life.
Related Documentation
The following publications may be of assistance to you regarding LCT-BGF
operations:
| BG-40 Miniature MSPP for Metro-Access General Description
| BroadGate BG-40 Installation, Operation, and Maintenance Manual
| BroadGate EMS-BGF Installation Guide
| BroadGate EMS-BGF User Manual
| LightSoft Network Management System User Manual
426006-2413-013-A00 ECI Telecom Ltd. Proprietary xvii

About This Manual LCT-BGF User Manual
Obtaining Technical
Documentation
To obtain technical documentation related to the LCT-BGF or any other ECI
Telecom product, please contact:
ECI Telecom Ltd.
Transport Networking Division
Documentation Department
30 Hasivim St.
Petach Tikva 49130
Israel
Fax: +972-3-9268060
Email: on.documentation@ecitele.com
Technical Assistance
The configuration, installation, and operation of the LCT-BGF and its
operation in a network are highly specialized processes. Due to the different
nature of each installation, some planning aspects may not be covered in this
manual.
If you have questions or concerns about your network design or if you require
installation personnel to perform the actual installation process, ECI Telecom
maintains a staff of design engineers and highly trained field service personnel.
The services of this group are available to customers at any time.
If you are interested in obtaining design assistance or a network installation
plan from ECI Telecom's Customer Support team, contact your ECI Telecom
sales representative. With any support related issues, technical or logistic,
please contact the ECI Telecom Customer Support center at your location. If
you are not familiar with that location, please contact our central customer
support center action line at:
Telephone +972-3-9266000
Telefax +972-3-9266370
Email on.support@ecitele.com
xviii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

1
Introducing the LCT
In this chapter:
Overview ......................................................................................................... 1-1
Hardware and Software Requirements ............................................................ 1-2
Overview
The LCT-BGF supplements the EMS-BGF 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-BGF system is based on the TCP/IP protocol and is connected to the
SDH network element (NE) via the Ethernet port provided by the MCU. It
implements element configuration and maintenance management functions and
coordinates with the EMS-BGF to perform management for error correction
facilities.
The LCT-BGF (V7) software is used to perform initial data configuration and
equipment software download for BG-40 and BG-20 network elements.
Maintenance personnel can modify parameters of an operating NE to detect and
solve specific problems within the element.
426006-2413-013-A00 ECI Telecom Ltd. Proprietary 1-1

Introducing the LCT LCT-BGF User Manual
Hardware and Software

Requirements
| Computer: PC or laptop with Pentium II 350 processor or higher, with
128 MB RAM and 1 GB hard disk memory
| Operating system: Windows 2000 Professional or Windows XP
Professional
| Interface protocol: TCP/IP-based socket communication
| Communication interface: Connects with the main control unit of the
equipment via a 10BaseT Ethernet interface
System Components
The system package consists of the following software and hardware modules:
| The LCT GUI and Boot Configuration Tool software running on the
Microsoft Windows operating system, which acts as a graphical user
interface between the BG-40 and BG-20 equipment and the user
| The boot software running on the BOOT ROM of the BG-40 or BG-20
equipment, which acts as a boot configuration server
| USB-based hardware license key
1-2 ECI Telecom Ltd. Proprietary 426006-2413-013-A00

2
Installing the LCT
In this chapter:
Overview ......................................................................................................... 2-1
Installing the LCT-BGF Application............................................................... 2-2
Overview
This section describes the installation procedure for the LCT-BGF.

Installing the LCT LCT-BGF User Manual
Installing the LCT-BGF

Application
The LCT-BGF can be installed on Windows 2000 Professional or Windows XP
Professional operating systems.
To install the LCT-BGF:

1. Make sure the hardware license key is plugged in to one of the USB ports
on the PC or laptop used for the LCT-BGF application.
2. Insert the supplied CD in the CD-ROM drive. The LCT-BGF Installation
CD window opens.
Figure 2-1: LCT-BGF Installation CD window

LCT-BGF User Manual Installing the LCT
3. Select Install LCT-BGF. The LCT Setup - Welcome window opens.
Figure 2-2: LCT-BGF Setup - LCT Welcome window
4. Click Next. The Setup Status window appears. A progress bar shows the
progress of the operation.
Figure 2-3: LCT-BGF Setup - Setup Status window

Installing the LCT LCT-BGF User Manual
When file copying is completed, the LCT System Config window opens.
Figure 2-4: LCT-BGF Setup - LCT System Config window
5. Click Config.
6. In the TU-TimeSlot Mapping Options area, select the Standard radio
button. The Installation Complete window opens.
Figure 2-5: LCT-BGF Setup - Installation Complete window
7. Click Finish. The LCT-BGF installation process is complete.
NOTE: Installation of the LCT-BGF can be done without the

license key. However, subsequent activation of the software
will be prevented.

3
Using the Boot Configuration
Tool
In this chapter:
Overview ......................................................................................................... 3-1
Boot Configuration Tool Procedures............................................................... 3-2
Downloading Embedded Software and the FPGA File ................................... 3-5
Obtaining IDPROM Data ................................................................................ 3-8
Configuring the No Recovery Next Startup Attribute ..................................... 3-9
Configuring the Serial Port Close Attribute .................................................. 3-10
Overview
This section describes how to login and utilize the Boot Configuration Tool,
which is used for the initial configuration of BG-40 and BG-20 NEs.

Using the Boot Configuration Tool LCT-BGF User Manual
Boot Configuration Tool

Procedures
Use the following procedure to log in to the Boot Configuration Tool.
To log in to the Boot Configuration Tool:

2. Connect your PC to the local BG-40 or BG-20 element via the dedicated
MNG Ethernet port.
3. On your Windows desktop, select Start > All Programs > LCT > Boot
Configuration Tool in the menu.
Figure 3-1: Boot Configuration Tool menu
The main Boot Configuration Tool window opens.
Figure 3-2: Boot Configuration Tool window

LCT-BGF User Manual Using the Boot Configuration Tool
4. Click Login in the upper-left corner of the window. The Input IP window
opens.
Figure 3-3: Input IP window
5. Select a card by selecting the relevant radio button.

6. Enter the IP address of the NE in the IP field and click OK.
7. The BG-40 NE assumes the boot status for approximately four to five
seconds after resetting. The Boot Configuration Tool logs in the NE
automatically and the following Information window appears, confirming
automatic login.
Figure 3-4: Information window showing autologin confirmation
After a main control reset or power-on restart, the Boot program is

initiated. When the Alarm LED of the main (MXC) board starts flashing,
you have five seconds to perform a login. Otherwise, you will miss the
login opportunity. The boot-state login can be performed on a local NE
only.
NOTE: If the hardware license key is not plugged in to one of

the USB ports, the software only works for two minutes
before freezing until the key is installed.

Configuring Parameters
After a successful login to the Boot Configuration Tool, you can configure
basic parameters, as described in the following table.
Table 3-1: Basic parameters terminology
Field name Description

NE ID The unique identification for a BG-40 or BG-20 element. NE ID
has two bytes, with a valid range from 1 to 4095, except for 2,
which is used by the XDM. The NE ID is in decimal format.
MAC address The MAC address is factory set and appears as read-only.
NE mode An NE has three modes: Gateway, DCC-only, and
Ethernet-only:
| Gateway mode - NE accessible via the Ethernet IP address
or the DCC IP address.
| DCC-only mode - NE accessible only via the DCC IP
address.
| Ethernet-only mode - NE accessible only via the Ethernet IP
address.
Ethernet port IP This address is valid for the gateway mode and Ethernet-only
mode. 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-BGF connected to it.
Basic parameters configuration procedure
NOTE: Some settings in this window are grayed out,

indicating that they are currently disabled in the NE.

To configure basic parameters:

1. In the Boot Configuration Tool main window, select Configuration >
Basic Parameter Configuration. The Basic Parameter Configuration
window opens.
Figure 3-5: Basic Parameter Configuration window
2. Click Get. The Boot Configuration Tool retrieves the configuration data
from the equipment and a confirmation window appears.
3. Click Apply. The Boot Configuration Tool sends the configuration data to
the equipment and a confirmation window appears.
Downloading Embedded
Software and the FPGA File
The embedded software is the control software on the element 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,
whereas the FPGA file is located in the file memory.

To download embedded software:

1. In the Boot Configuration Tool window (on page 3-2), select
Configuration > Download Embedded Software. The Download
Embedded Software window opens.
Figure 3-6: Download Embedded Software window
The fields in this window are:
Embedded Area - located in the Upper Area and Lower Area memories
Active Area - currently activated area used in conjunction with the
Embedded Area
2. Click Select File to select the filename to be downloaded, which appears in
the field to the right. Select the Upper Area or Lower Area radio button in
the Embedded Area for the software download location. This selection
should always be different from the Active Area when reverting back to the
original software.
3. Click Download to download the software to the equipment. A
confirmation window appears.
4. After software download, click Apply to activate the software.

To download an FPGA file:

1. In the Boot Configuration Tool window, select Configuration >
Download FPGA File. The Download FPGA File window opens.
Figure 3-7: BG-40 Download FPGA File window
2. Click Select File to select the FPGA filename to be downloaded, which

appears in the field to the right. For BG-40 NEs, select a BG-40 card in the
Select Card field.
3. Click Download.
4. Click Close to exit.

Obtaining IDPROM Data

Use the following procedure to obtain IDPROM data for the BG-20 NE.
IDPROM data is stored in the EEPROM, which records relevant hardware
information.
To get IDPROM:
| In the Boot Configuration Tool window (on page 3-2), select
Configuration > Get IDPROM. The Boot Configuration Tool retrieves
the IDPROM data from the equipment and displays it in the IDPROM
window.
Figure 3-8: BG-20 IDPROM window

Configuring the No Recovery

Next Startup Attribute
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:

Configuration > No Recovery Next Startup. The No Recovery Next
Startup window opens.
Figure 3-9: BG-20 No Recovery Next Startup window
2. Select the No Recovery Next Startup checkbox for the NE to restart using
the default configuration instead of the current configuration. Leave this
checkbox deselected for the NE to restart using the current configuration.
3. Click Get. The Boot Configuration Tool retrieves the No Recovery Next
Startup attribute from the equipment. A confirmation window is displayed.
4. Click Apply. The Boot Configuration Tool sends the No Recovery Next
Startup attribute to the equipment and a confirmation window is displayed.

Configuring the Serial Port Close

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

Configuration > Serial Port Close Flag. The Serial Port Close Flag
window opens.
Figure 3-10: BG-20 Serial Port Close Flag window
2. Select the Serial Port Close checkbox if you want the serial port to be
closed. Leave this checkbox deselected for the serial port to remain open,
which enables you to view debug information from the serial out port.
3. Click Get. The Boot Configuration Tool retrieves the Serial Port Close
attribute from the equipment. A confirmation window is displayed.
4. Click Apply. The Boot Configuration Tool sends the Serial Port Close
attribute to the equipment. A confirmation window is displayed.

4
Getting Started with the LCT
GUI
In this chapter:
Overview ......................................................................................................... 4-1
Starting the LCT GUI ...................................................................................... 4-2
Configuring Parameters ................................................................................... 4-4
Configuring Static IP Routes ........................................................................... 4-6
Overview
The LCT GUI is essentially an element management system (EMS) interface
for the BG-40 or BG-20 and performs typical management functions.
NOTE: Multiple methods are available in the LCT-BGF 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 right-click 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.

Getting Started with the LCT GUI LCT-BGF User Manual
Starting the LCT GUI

Use the following procedure to log in to the LCT-BGF interface.
To log in to the LCT GUI:

2. Connect the PC to the gateway BG-40 NE via the designated MNG
Ethernet port.
3. Double-click the shortcut icon on your desktop or select Start > All
Programs > LCT. The LCT GUI Login window opens.
Figure 4-1: LCT GUI Login window
NOTES: After starting the NE (its indicator LED flashes

slowly), you can use the LCT GUI to log in to the element via
the IP address. You can log in to a gateway NE via the
Ethernet IP or via the DCC IP address.
To log in to a DCC-only NE via the gateway NE, use the

DCC IP address. In this case, the DCC must be unblocked.
To log in to an Ethernet-only NE, use the Ethernet IP address

of the NE.
4. In the Login window, enter the NE IP address.

5. Click Ping for the LCT GUI to attempt to connect to the NE.

LCT-BGF User Manual Getting Started with the LCT GUI
6. If successful, click Login to log in to the NE. The LCT-Login BG-40 NE

(shelf view) window or LCT-Login BG-20 NE (shelf view) opens.
Figure 4-2: LCT-Login BG-40 NE window
7. Click Logout the NE to disconnect from the NE. The Login window
reappears and you can log in again.
NOTE: If the hardware license key is not plugged in to one of

the USB ports, the software only works for two minutes
before freezing until the key is installed.

Configuring Parameters
After successful login to the LCT software, you can configure the following
parameters:
| Basic parameters: NE ID, NE MAC address, NE mode, Ethernet port IP,
Ethernet port mask
| Static IP routes
Table 4-1: Parameter terminology
Field name Description

NE ID The unique identification for a BG-40 or BG-20 element. NE ID
has two bytes, with a valid range from 1 to 4095, except for 2,
which is used by the XDM. The NE ID is in decimal format.
MAC address The MAC address is factory-set and read-only.
NE mode An NE has three modes: Gateway, DCC-only, and Ethernet-only:
| Gateway mode - NE accessible via the Ethernet IP address or
the DCC IP address.
| DCC-only mode - NE only accessible via the DCC IP
address.
| Ethernet-only mode - NE only accessible via the Ethernet IP
address.
Ethernet port IP This address is valid for Gateway mode and Ethernet-only mode.
In a gateway NE, this mechanism provides internal router
functionality. It has two IP addresses: one for the DCC port (NE
IP address) and another for the Ethernet port. These two addresses
must belong to different subnets. When setting an Ethernet port IP
address, it must belong to the same subnet as the IP address for
the host LCT connected to it.

LCT-BGF User Manual Getting Started with the LCT GUI
To configure parameters:
1. In the LCT-Login BG-40 NE window, select Configuration > Basic
Parameter Configuration. The Basic Parameter Configuration window
opens.
Figure 4-4: Basic Parameter Configuration window
NOTE: Some parameters in this window are grayed out,

indicating that they are currently disabled in the NE.
2. Click Get to retrieve the configuration data from the equipment. A


Configuring Static IP Routes

When several NEs are managed by the EMS-BGF, you should set the static IP
Routes for the NE.
To configure static IP routes:

1. In the LCT-Login BG-40 NE window, select Configuration > Static IP
Routes Configuration. The Static IP Routes Configuration window
opens.
Figure 4-5: Static IP Routes Configuration window
2. In the Add Static IP Routes fields, enter the Destination Network IP,
Subnet Mask, and Next Hop IP.
3. Click Add to add the new static IP routes to the Existing Static IP Routes
area.
4. In the Existing Static IP Routes fields, select the static IP routes entry that
you want to delete and click Delete.
5. Click Get to retrieve the static IP routes from the equipment and display
them in the Existing Static IP Routes fields. A confirmation window
appears.
6. Click Apply to send the static IP routes to the equipment. A confirmation
window appears.

5
Managing NEs
In this chapter:
Configuring NEs.............................................................................................. 5-1
Resetting NEs .................................................................................................. 5-8
Configuring Orderwire Attributes ................................................................... 5-9
Configuring Communication Parameters ...................................................... 5-13
Configuring NEs
NE configuration configures attributes, services, and relevant functions for an
unconfigured (initial default status) NE, according to requirements of the
networking application. The NE's configuration data determines all the actions
of the NE.
During NE 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 card attribute. A
configuration wizard is provided for this purpose.
A single NE includes the following classified configuration contents:
| NE attributes
| Card assignment
| Service configuration
| Clock synchronization configuration
| Card attribute configuration
| Card electronic label

Managing NEs LCT-BGF User Manual
| Protection attribute configuration

| Alarm-related attributes configuration
| Performance-related attributes configuration
Configuration for all of these items is described in the sections and chapters
that follow.
Setting the NE Time

The start time in NE devices is not necessarily the actual time. The NE time
must be set so that it is consistent with the actual time after the NE starts to run.
Each NE has its own clock (that reflects the NE time). The generation time for
both alarms and events is determined by the NE time. The real time of the PC
refers to the current time of the LCT-BGF PC. The NE time and the LCT-BGF
PC time should be synchronized.
To set the NE time:

1. Select Configuration > NE Time in the main menu. The NE Time
Configuration window opens.
2. Click PC Time to directly read the system time of the PC, or manually
enter the time.
3. Click Apply to set the time. A confirmation message is displayed.

LCT-BGF User Manual Managing NEs
Setting NE Attributes
The common attributes of the NE include two parts: basic attributes and
management attributes.
Basic NE attributes include the NE name, NE ID (read-only), NE type, NE
working mode, and NE system software version (read-only). For the BG-40
NE, the NE type is BG-40, which is a read-only attribute. For the BG-20 NE,
the NE type is BG-20, which is a read-only attribute. The NE working mode
refers to different working modes of the same type of equipment.
NE management attributes refer to information used for management purposes,
such as the vendor, location, user label, run date, and notes. Management
attributes do not influence the work and service configuration of the NE.
To set NE attributes:
1. Select Configuration > NE Attributes in the main menu. The NE
Attributes window opens.
Figure 5-1: NE Attributes window
The NE common attributes are divided into basic attributes and

management attributes.

NE basic attributes include the NE name, NE ID, NE type, and system

software version.
Management attributes include vendor information, the launch date, NE

location, run time, user label, connection mode, Ethernet IP address of the
NE, DCC IP address of the NE, and descriptive information.
The read-only attributes cannot be changed and are grayed out.
2. After entering the above information, click Apply to send the information
to the NE. A confirmation message is displayed.
3. Click Close to exit the window.
NOTE: The setting of management attributes does not

influence the working and service configuration of the NE.
These attributes are for identification purposes only.
Performing Card Assignment

Card assignment involves assigning card types for various slots (or a subcard
slot) of the NE equipment, setting up objects corresponding to the physical
cards in the LCT-BGF and setting the corresponding values for them, and
displaying icons in the LCT-BGF window. Corresponding card attributes and
services can only be configured after card assignment is completed.
Card assignment makes offline configuration of the LCT-BGF 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. It is read-only.
| Card assignment - card assignment installs the logical slot. You can either
manually configure the logical slot, one slot after another, or first obtain the
actual physical slot and then install the logical slot in modification mode.

To perform card assignment:

1. Select Configuration > Slot Assignment or right-click an NE in the
topology view and then select Slot Assignment in the shortcut menu. The
Slot Assignment window opens.
Figure 5-2: BG-40 Slot Assignment window

Figure 5-3: BG-20 Slot Assignment window
2. After adding the corresponding card type in the corresponding slot, click
Apply. A confirmation message is displayed in the Operation Result area
of the window. If the logical configuration is inconsistent with the physical
configuration, alarms such as card out, card unexpected, card type
mismatch, and card fault (CBUS disconnection) will occur.
Setting the Card Maximum Traffic

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), FEL_12, and ESW_2G_8F. After slots are assigned on one of these
cards, you set the card's maximum traffic. You can also select one or all cards
to set the maximum traffic for various cards on an NE.
Card maximum traffic setup is not required for BG-20 NEs.

To set the maximum traffic for a card:

1. Select Configuration > Card Info > Card Max Traffic in the main menu.
The Card Max Traffic Setup window opens.
Figure 5-4: Card Max Traffic Setup window
This window displays the list of cards for this NE for which the maximum
traffic must be set. This list contains the following information:
Select - a checkbox indicating that you want to select this card. You
must select a card before conducting Query, Get, or Apply operations.
Card - card name.
Max - maximum traffic value.
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.

The Ethernet Card button is used to configure the maximum traffic for
FEL_12 and ESW_2G_8F Ethernet cards.
2. Select the card and enter the corresponding values in the Max column.
3. Click Apply and wait for a confirmation that the operation was completed
successfully.
4. Click Close to exit the window.
Resetting 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 not
only the main processing unit but also the peripheral chips. A cold reset
influences services on the card.
To reset an NE:
1. Select an NE in the topology view and then select Maintenance > NE
Reset in the main menu. The Device Reset Operation window opens.
Figure 5-5: Device Reset Operation window
2. Select the Warm Reset or Cold Reset radio button.

3. Click OK. The results of the operation are displayed.

Configuring Orderwire
Attributes
Orderwire attribute configuration configures the orderwire telephone, orderwire
attributes, and orderwire routing of all NEs. Orderwire telephone configuration
relates to the entire network and can only be performed on NEs in the
management domain. Operation authorities are needed from all NEs in the
network to perform orderwire configuration in the network.
BG-40/BG-20 NEs have Allow/Prohibit orderwire telephone attributes. When
set as Allowed, the orderwire telephone function of this NE is started. When set
as Prohibited, the orderwire telephone function of this NE is disabled.
The orderwire telephone is used for orderwire contacts between SDH NEs that
support the addressing call and conference calls. The orderwire number is a
three-digit integer number.
The Conference Telephone attribute refers to the NE conference telephone
when it is used in conversation. There are two options: Listen and Talk and
Listen Only.
The Conference Telephone Number attribute refers to the conference telephone
number for all NEs that support conference calling.
The Call Waiting Time attribute applies to the entire network. The unit is
seconds.
An orderwire routing table is saved in the MXC4X of each NE. The orderwire
routing table records the next hop and the outgoing direction (outgoing slot and
outgoing optical port) for each endpoint to which an orderwire call is to be
made. Since each NE knows the next hop NE, a path to the endpoint can be
established.
SDH orderwire provides communication for field engineers and equipment
maintenance personnel, and supports address-selective calls and conference
calls.
LCT-BGF orderwire configuration functions include:
| Setting the orderwire phone number for each NE
| Setting a uniform conference call number
| Setting the orderwire phone routing table. The LCT-BGF calculates
orderwire trails automatically, based on NE connection states in the
topology view. When configuring an orderwire phone, make sure that the
network topology is correctly connected.

To configure BG-40 orderwire attributes:

1. Select Configuration > Orderwire Configuration > BG-40 in the main
menu. The Orderwire Configuration window opens.
Figure 5-6: Orderwire Configuration window - Setting the Orderwire Attribute

tab
The left side of this window displays the NE tree listing all NEs already
created, including those created in the user management area. The right side
contains two tabs:
Setting the Orderwire Attribute - used to set the orderwire telephone

number and other orderwire attributes of the NE
Setting Orderwire Routing - used to set the NE orderwire routing
2. After selecting one or more NEs in the NE tree, click Get to display the NE
orderwire attributes obtained from the NE equipment.

3. Select the Setting Orderwire Routing tab.
Figure 5-7: Orderwire Configuration window - Setting Orderwire Routing tab
The orderwire routing information table is divided into seven columns:
Start NE - the NE from which this orderwire route starts

End NE - the destination NE of this orderwire route
Phone number - the orderwire number of the end NE
Next Hop NE - the first NE reached from the start NE using the shortest
path from the start NE to the end NE
Out NE slot - outgoing NE slot of the start NE used to connect the start
NE and next hop NE
Out NE Optical Port - outgoing optical interface of the start NE used to
connect the start NE and the next hop NE
Conference Call - identifies whether this route is added to the
conference call
4. After selecting NEs in the NE tree, click Get to display the orderwire
routing information of the selected NEs obtained from the equipment.

To configure BG-20 orderwire attributes:

1. Select the Configuration > Orderwire Configuration > BG-20 in the
main menu. The BG-20 Orderwire Configuration window opens.
Figure 5-8: Orderwire Configuration window - BG-20
The left side of this window displays the NE tree listing all NEs already
created, including those created in the user management area. The right side
is used to set the orderwire telephone number and other orderwire attributes
of the NE.
2. After selecting one or more NEs in the NE tree, click one of the following
buttons to configure the orderwire telephone number and orderwire
attribute:
Query - to display the NE orderwire attributes in the LCT-BGF
database
Get - to display the NE orderwire attributes obtained from the NE
equipment
Apply - to deliver the orderwire attributes of the selected NE to the NE
equipment and save them to the LCT-BGF database

Configuring Communication
Parameters
The powerful network management function of SDH needs strong support from
the ECC stack. As a managed object itself, the ECC stack should be
manageable. ECC stack management information enables you to receive
prewarning signals in sufficient time before an NE is disconnected due to DCC
hardware channel performance deterioration, and to locate the problem for a
specific NE after disconnection. It also provides some necessary network test
measures. Every NE must be set with some communication parameters, such as
gateway attributes, the Ethernet port's IP address, the DCC port's IP address,
and the LCT-BGF computer's IP address.
A gateway NE is an NE directly connected with the LCT-BGF. In terms of the
physical channel, information exchange between the gateway NE and the
LCT-BGF does not pass the DCC channel and needs no forwarding via any
other NE. A nongateway NE is an NE that communicates with the LCT-BGF
via a gateway NE. Generally, it is connected with the gateway via an optical
channel for data transmission over the DCC channel.
DCC transparent transmission means that the DCC code stream passes the NE
transparently, meaning it is transmitted transparently from the STM-N RX end
of the NE to another STM-N TX end. In this context, transparent refers to
protocol independence and the physical connection rate is purely N 64 Kbps.
In contrast, termination means local generation of DCC code streams at the
STM-N TX end.
There are two possibilities for termination:
| Access permitted - accesses the DCC code stream to the protocol processor
for processing
| Access prohibited - does not process the DCC code stream at all

To configure communication parameters:

| Select Configuration > Communication Mode in the main menu. The NE
Connection Settings window opens.
Figure 5-9: NE Connection Settings window
Use this window to set gateway attributes, the Ethernet port IP address, and
the MCUE Ethernet port IP. If Gateway is selected in the Gateway
Attribute field, both local and remote NEs can be managed through the
LCT-BGF or the EMS-BGF. If No Gateway is selected, only the local NE
can be managed through the LCT-BGF or EMS-BGF. The Save and Apply
operations can only be performed by an advanced operator or system
operator.

DCC and Overhead Configuration

The DCC Configuration and DCC Overhead Management window enables
you to perform DCC, overhead, and related configuration for the BG-40 NE.
To access the DCC Config and DCC Overhead Management

window:
| Select Configuration > DCC Configuration and DCC Overhead in the
main menu. The DCC Configuration and DCC Overhead Management
window opens.
Figure 5-10: DCC Configuration and DCC Overhead Management window
The left side of this window displays the NE tree, listing all BG-40 NEs.
On the right, there are six operation tabs:
DCC Access
VC12 to SM10
V.35 Work Mode
DCCSwap Attribute
DCC Cross
DCC Overhead Config

DCC access
At present, two DCC access control modes are supported: six RDCCs (default)
and three RDCCs +1 MDCC. The DCC Access tab is used to configure DCC
access.
Figure 5-11: DCC Configuration and DCC Overhead Management window - DCC
Access tab
Query, Get, and Apply operations can be performed in this window.
NOTE: U1 denotes SOH94, which is Line 9 and Column 4

information for overhead bytes.
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.
VC12 to SM10
The VC12 To SM10 tab, shown in the figure DCC Config and DCC Overhead
Management window (on page 5-15), is used to set the VC-12-10, VC-12-11,
and VC-12-12 access for the integrated mEP1subcard to the SM10. You can
perform Query, Get, and Apply operations on the NE selected in the NE tree.
To set a VC-12-12 link to the SM10, you must check whether the MXC4X
V.35 is in Traffic Path mode. If it is, such a link is prohibited. To set a
VC-12-10 or VC-12-11 link, first check whether it has been configured with
any overhead. If it has, such a link is prohibited.
Figure 5-12: DCC Configuration and DCC Overhead Management window - VC12
To SM10 tab

V.35 work mode

The V.35 Work Mode tab is used to select a working mode for the V.35
interface of a card.
Figure 5-13: DCC Configuration and DCC Overhead Management window - V.35
Work Mode tab
The MXC4X cross-connect clock control card provides one V.35 interface and
supports the following three working modes:
| Traffic path
| Extended DCC
| V.11 overhead interface
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 Extended DCC.

| Traffic can be set only when the working mode is Traffic Path.
| The DCC type can be set as RDCC or MDCC only when the working mode
is Extended DCC.
DCCSwap attribute
The DCCSwap Attribute tab is used to set the optical port SWAP type and
switch of each card in the NE.

DCCSwap Attribute tab
The optical port SWAP setting only restricts its MS property. After SWAP, its
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.
The operation objects include the optical ports under all subcards of the
selected NE. Query, Get, and Apply operations can be performed on these
ports.

DCC cross
Through cross connection, DCC transparent transmission and DCCSWAP
configuration can be performed using the DCC Cross tab.
Cross tab
Query, Get, Apply, Add Items, Remove, and Remove All operations can be
performed in this window.
The following conditions apply for DCC configuration:
| EOC can only be configured for DCC when the corresponding VC-12 is
not connected to the SM10.
| V.35 must be configured in Extended DCC mode. Then, its cross-connect
granularity can be determined according to the set DCC type.
| For DCC transparent transmission, cross connections (RSDCC&RSDCC or
MSDCC&MSDCC) between an identical cross connect can be in EOC,
V.35, and SOH. DCC access is prohibited for the granularity used in
transparent transmission.

| For DCCSWAP, RSDCC and MSDCC cross connections (such as

DCCSWAP) can be performed between six SOHs. In this case, the
following swaps can be performed to implement DCC and orderwire byte
penetration: D1~D3D7~D9, E1D11, and E2D12. MSDCC access in
DCCSWAP is prohibited, but RSDCC access is available.
| All cross connections are bidirectional.
DCC overhead configuration

Configuration of overhead interfaces can be performed for various DS-0 cross
connections that use overhead timeslots. The DCC Overhead Configuration tab
is used for this purpose.
Overhead Configuration tab
Query, Get, Apply, Add Items, Remove, and Remove All operations can be
performed in this window.

The following conditions apply for DCC overhead configuration:

| Only the following DS-0 timeslots can be cross connected: F1, U1, V.24,
and V.11 (when V.35 works in the V.11 mode).
| VC-12-10 and VC-12-11 cannot be used for overhead configuration when
they are connected with the SM10.
| V.11 can be used for overhead configuration only when V.35 uses V.11
Overhead Interface mode.
| No cross connection is allowed between two V.24 channels and one V.11
channel. Cross connection is permitted in all other cases.
| All cross connections are bidirectional.

6
Managing Cards
In this chapter:
Configuring Card Attributes ............................................................................ 6-1
Resetting a Card............................................................................................... 6-3
Viewing the Electronic Card Label ................................................................. 6-4
Viewing Card Information............................................................................... 6-5
Managing BG-20 Special Cards ...................................................................... 6-6
Managing FE_L12 Card Special Attributes .................................................. 6-10
Configuring ESW_2G_8F Special Attributes ............................................... 6-20
Configuring Ethernet Attributes .................................................................... 6-36
Configuring Card Attributes

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

Managing Cards LCT-BGF User Manual
To configure card attributes:

1. In the NE Shelf View window, select Configuration > Card Info > Card
Attributes in the main menu. The Card Attributes Setup window opens.
Figure 6-1: Card Attributes Setup window
2. Select a card in the Current Card drop-down list.
NOTE: You can configure attributes for multiple cards

without having to re-access this window each time. However,
you must click Apply for the attribute configuration on a card
to take effect.
3. Define the following card attributes and then click Apply for your changes
to take effect:
SDH interface card (OMD1, OMS4, ESM1_1, and so on) attributes:
J0 sent/J0 received to/from RS and whether to insert AIS downward
during mismatch
J1 sent/J1 received to/from VC-4 and whether to insert AIS
downward during mismatch
C2 sent/C2 received to/from VC-4 and whether to insert AIS
downward during mismatch

LCT-BGF User Manual Managing Cards
VC-4 loopback (near-end and far-end)

Other special attributes
PDH and Ethernet interface card (PE1-16/32, P345_3 , FE_L12, and so
on) attributes:
VC-side attribute
J2 sent/J2 received to/from VC-3/VC-12 and whether to insert AIS
downward
V5 sent/V5 received and whether to insert AIS during mismatch
PPI-side attributes - these attributes vary, depending on the card.
For example, for the 2 M card, attributes include impedance
selection, framing/nonframing, long hop/short hop, and more.
Loopback parameters (near-end, far-end).
Other special attributes.
Resetting a Card
When the physical device of a card does not work normally and needs to be
initialized, a card reset operation is performed. Both warm and cold resets are
available.
A warm reset only resets the central processing unit of the cards, meaning it
repositions the running of card usage programs. A cold reset resets both the
central processing unit and the peripheral hardware. Warm resets do not affect
traffic, while cold resets do.
To perform a card reset operation:

1. Right-click an NE in the topology and select Open NE. The NE Shelf
View window opens.
2. Select the card to be reset.
3. Select Maintenance > Card Reset. The Device Reset Operation window
opens.
Figure 6-2: Device Reset Operation window

4. Select the Cold Reset or Warm Reset radio button.

5. Click OK. A confirmation message is displayed after command execution.
Viewing the Electronic Card

Label
The electronic card label is typically used during engineering and production
maintenance, and displays the equipment hardware and software versions.
To view electronic label information:

1. Right-click an NE in the topology view and select Open NE, or
double-click an NE icon. The Shelf View window opens.
2. Select a card and then select Configuration > Card Info > Electronic
Label. The Electronic Label window opens.
Figure 6-3: Electronic Label window
This window displays the electronic information of the card, including the
card name, serial number, hardware version number, tester number, test
date, boot version, invalid date, programmer, software version, finish date,
and reservation byte.

For the BG-40/BG-20 NE subcard, an abbreviated electronic label is

displayed that contains the card name, hardware version number, software
version, and reservation byte.
Viewing Card Information

You can view descriptive information for each card.
To view card information:

| Select a card in the LCT-Login BG-40 NE (shelf view) window and then
select Card Description from the right-click menu. The Card
Information window opens.
Figure 6-4: Card Information window

Managing BG-20 Special Cards

The BG-20 supports several new cards not available on the BG-40. BG-20 slot
assignments are shown in the following figure.
Figure 6-5: BG-20 slot assignment
NOTE: The FCU and those slots marked in brown in the

preceding figure are fixed. When a BG-20 NE is created,
these slots are assigned.
Slot assignments for the BG-20 are listed in the following table.
Table 6-1: BG-20 slot assignment
Slot Available assignment V1 and V1.5 V2 support Default

support
DSlot None, M345_3, SMD1, None, M345_3, None, M345_3, None
OMS4B, ME1_42, ME1_42, ME1_42, ME1_21,
MGB_L1, and so on ME1_21 SMD1, OMS4B
A1 SAM1/4 SAM1/4 SAM1/4 SAM1/4
A2 SAM1/4 SAM1/4 SAM1/4 SAM1/4
L12 None, L1B_6F, None, L1B_6F None, L1B_6F, None
MESW_6F MESW_6F
OWI None, OW-2X None None None
PS INF-20, AC-CONV-20 INF-20, INF-20, INF-20
AC-CONV-20 AC-CONV-20
PSE None, INF-20E, NA INF-20E, None
AC-CONV-E AC-CONV-E
ESlot1 None, ESW_2G_8F, None None, None
PE1_42/63, and so on ESW_2G_8F_e,
PE1_63, P345_3E,
SM_10E

Slot Available assignment V1 and V1.5 V2 support Default

support
PE1_63, P345_3E,
SM_10E
PE1_63, P345_3E,
SM_10E
NOTES: SAM1/4 is not a physical card or module, but is an

abstract object of the BG-20B SDH interface. The BG-20B
SDH interface is STM-1/4-compatible, and can be switched
smoothly by software configuration.
L1B_6F is a very simple L1 card and does not contain

EoS/PHY features.
The following figures show the BG-20 shelf view and slot assignment,
respectively.
Figure 6-6: BG-20 NE Shelf View window

Figure 6-7: BG-20 Slot Assignment window - Logical tab
Managing the SAM1/4 Interface

SAM1/4 is not a physical card or module, but is an abstract object of the
BG-20B SDH interface. The BG-20B SDH interface is STM-1/4-compatible,
and can be switched between STM-1 and STM-4 smoothly by software
configuration without affecting traffic.

The following figures show the SAM1 and SAM4 windows, respectively.
Figure 6-8: SAM1 internal view
Figure 6-9: SAM4 internal view

To switch between SAM1 and SAM4:

1. Open the BG-20B Shelf View window and select the SAM block.
2. Right-click the SAM block and select Change Rate to SAM-1 in the pop-
up menu.
Figure 6-10: SAM pop-up menu
The SDH interface is smoothly switched to STM-1.
NOTE: Changing from STM-1 (SAM1) to STM-4 (SAM4)

or installing an STM-4 NE requires a special license based on
the NE serial number.
Details for handling license keys will be provided in a future

version of this manual.
Managing FE_L12 Card Special

Attributes
The Fast Ethernet Module (FE_L12) is a multi-EoS Ethernet interface card
providing up to eight EoS channels. The total bandwidth of the eight EoSs
cannot exceed 63 VC-12s and the EoS encapsulation protocol is optional.
Externally, eight 10BaseT/100BaseT Ethernet transparent transmission
interfaces can be provided. Internally, an eight-port L2 switching module is
integrated, which supports the L2 switching function through an external cable
connection.

The functional blocks contained in the FE_L12 card include eight VCGs, eight
EoSs, and 16 ports. The port involves two layers: MAC and PHY. VCG is the
collection of VC-12s or VC-3s. The specific number of VC-12s or VC-3s
depends on the VCG's virtual cascade mode and maximum traffic.
Attribute management for the FE_L12 card includes:
| Configuration management:
VCG configuration
Acquisition of VCG timeslot resources
Addition of VCG member attributes and LCAS status
EoS encapsulation protocol configuration
CID table configuration
Port attribute configuration
Port connection
| Fault management:
Current alarms
Historical alarms
| Performance management:
Current performance
Historical performance
Performance threshold
| Maintenance:
Real-time traffic view
MST maintenance

To configure FE_L12 card attributes:

1. In the LCT-Login BG-40 NE (shelf view) window, select and open the
FE_L12 card. The following window is displayed:
Figure 6-11: FE_L12 card window

2. To perform VGC configuration, select Configuration > VCG Attributes

in the menu. The VCG Attribute window opens.
Figure 6-12: VCG Attribute window - Traffic tab
Use this window to configure the virtual cascade mode (VC-12/VC-3) and
bandwidth of each VCG.

3. To acquire VCG timeslot resources, select Configuration > Get Time Slot
Resource in the menu. The Get FEM Time Slot Resource window opens.
Figure 6-13: Get FEM Time Slot Resource window
This window displays the virtual cascade mode of each VCG and the
timeslot number assigned to this VCG.
4. To configure VCG member Add attributes and LCAS Status, select a VCG
and then select Configuration > VCG Member Add Attribute Set and
LCAS Status in the menu.
The operation objects are VCGs in the FE_L12 card. For every member of
this VCG, an Add or Not Add attribute can be set. The FE_L12 card
determines whether to add or remove the corresponding LCAS member
according to variations of this attribute.
5. Click Get in the VCG Attribute window to acquire the Add attributes and
the added member status of all members of a VCG from the NE equipment:
Received CNTL domain value
Received MST status
Sent CNTL domain value
Sent MST status
Value ranges for these attributes are as follows:
CNTL domain value - FIXED, IDLE, NORM, EOS, ADD, and DNU
MST domain value - OK and FAIL

Descriptions for sending and receiving member status must adhere to the
rules described in the table Member status rules (on page 6-19). All other
combinations are considered abnormal.
Figure 6-14: VCG Member Add Attribute Set window
6. To configure the EOS encapsulation protocol, select Configuration > EOS

Attribute in the menu. The EOS Protocol window opens.
Figure 6-15: EOS Protocol window

This window contains the EOS encapsulation protocol, sending FCS

attribute, and receiving FCS attribute information. For the FE_L12 card's
EOS channel, one of four types of encapsulation protocol can be
designated:
Linear Extension Header GFP

Null Extension Header GFP (the default)
LAPS
LAPF
The sending FCS may be enabled or disabled (the default is enabled). The
receiving FCS may be enabled/disabled/adaptive (the default is enabled; if
adaptive is supported, the default is adaptive).
7. To configure the CID table, select Configuration > CID Table. The CID
Table window opens.
Figure 6-16: CID Table window
If an EOS channel has been set with Linear Extension Header GFP
encapsulation, you must configure the EOS GFP CID table. In this table,
8 indicates No (no MAC is added), and 0 through 7 correspond to MAC1
through MAC8. The default setting is 8.

The following principles apply when configuring this table:
The same MAC number cannot appear in the same line, but it can
appear repeatedly in the same line.
N cannot appear in the middle of a line (meaning, the values at both
sides are non-N), which can only appear at the end.
If the Null Extension Header GFP, LAPS, or LAPF encapsulation
protocol is adopted for an EOS channel, the corresponding MAC
cannot be used by any other EOS.
8. To configure the Port attribute, select Configuration > PORT Attribute.
The Port Attributes window opens.
Figure 6-17: Port Attributes window
The attribute value range and default values are shown in the table Port
attribute values (on page 6-20).
9. To configure the port connection, select Configuration > PORT Connect.

The Port Connect window opens. You can set up connections between
Ports 1 through 8 and Ports 9 through 16 according to actual needs, and
indicate whether Ports 1 through 8 are connected to L2 switching. The
connection relationship can be displayed on the LCT-BGF, but the
information is not delivered to the NE. It is only stored in the LCT-BGF
database.

10. To view real-time traffic, select the Maintenance > Get Current Payload.
The Get Current Payload Rate window opens.
Figure 6-18: Get Current Payload Rate window
In this window, you acquire the RX and TX traffic of EoS and MAC 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 can be specified
in B per second, Kbps, or Mbps. You can also select the adaptive option. In
this case, the system displays the data in the appropriate unit according to
the data size.

11. To perform MST maintenance, select Maintenance > MST Maintenance.

The MST Maintenance window opens. For LCAS members, the MST
FAIL force/release function can be performed. MST attribute values are
Auto and ForceFail (the default is Auto).
Figure 6-19: MST Maintenance window
Table 6-2: Member status rules
No. CNTL MST Rule

1 NORM OK Normal LCAS member
2 EOS OK Normal LCAS member
3 FIXED --- Non-LCAS member
4 IDLE --- Non-added member
5 ADD FAIL Member being added
6 DNU FAIL Member temporarily
removed due to failure

Table 6-3: Port attribute values

Port status Traffic CID Permitted Sending Receiving Pass-
control maximum through
status packet
length
1: Adaptive 1: On Value: Value: 1: Permitted 1: Permitted 1:
(default) (default) 0 through 64 through (default) (default) Permitted
2: 10M half- 2: Off 255 65535 2: Prohibited 2: Prohibited 2:
duplex Prohibited
3: Self- Default: 0 Default:
3: 10M full- negotiation 1536 (default)
duplex
4: 100M
half-duplex
5: 100M full-
duplex
Configuring ESW_2G_8F Special

Attributes
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's edge (PE) RS, in order to implement a
BG-based provider network. The customer's 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
local area network (Reference: IEEE 802.1Q) using 802.1Q/P encapsulation
(VLAN tags) and a switching/bridging algorithm (Reference: IEEE 802.1D).
The Layer 1/SDH topology of the network is transparent to the
Layer 2/Ethernet. Either a ring or mesh topology of SDH trails accommodates
point-to-point links in a switched Ethernet network. The same Layer 1 network
can accommodate multiple Layer 2 networks using separate SDH paths. The
basic rate of an EoS connection uses VC-12/VC-3 granularity, meaning
N x 2 Mbps or N x 50 Mbps.
NOTE: The MESW_6F card is a daughter card of the BG-20.

This card has the same features as the ESW_2G_8F card. The
MESW_6F card has six FE interfaces (RJ-45). Each port has
an LED indicator. The MESW_6F has eight FE WAN ports,
with an EoS bandwidth of 4 x VC-4. For more details about
MESW_6F operation, refer to the sections in this manual
relating to the ESW_2G_8F card.

ESW_2G_8F Hardware
The ESW_2G_8F is a front-access card containing the following interfaces:
| Two GE interfaces (SFP)
| Eight FE interfaces (RJ-45)
| An LED indicator for the ESW_2G_8F card: Alarm/Active/Fail
| An LED indicator for the ports: LINK/RX/SPEED
The following figure shows the ESW_2G_8F card.
Figure 6-20: ESW_2G_8F card
ESW_2G_8F Network Architecture

The following figure shows the ESW_2G_8F architecture.
Figure 6-21: ESW_2G_8F network architecture

The network architecture defines three roles for RSs:

| P: Provider's core RS
| PE: Provider's edge RS
| CE: Customer's edge RS
The ESW_2G_8F is applied as either a P or PE RS. The following connection
rules apply:
| PEs are the only meeting points of the customer and provider networks.
| A P RS connects to multiple P RSs (via ring/mesh/both Layer 1).
| A PE RS can connect to multiple P RSs (via ring/mesh/both Layer 1).
| A CE RS can connect to multiple PE RSs (via ring/mesh/both Layer 1).
ESW_2G_8F Ports
The ESW_2G_8F provides three types of ports:
| 16 x FE WAN ports - for connecting to P/PE RS (NNI) or Ethernet L1
cards (UNI) via CALLA (EoS Mapper) and the internal matrix to an
aggregate interface.
The WAN port contains three objects: WAN, EoS, and VCG.
WAN port main features are:
IEEE 802.3 802.1q-compliant MAC for Ethernet frame handling.

Full VLAN support for up to 4,000 VLANs.
Supports a maximum Ethernet frame of 9616 bytes.
Autonegotiation functionality is not required (fixed to 100 Mbps full
duplex).
Half duplex mode is not required.
Flow control support, as follows:
Transfers Pause frames from the WAN side to the LAN side
transparently.
Generates and sends Pause frames to the LAN side according to the
buffer status.
Handles and transfers Pause frames from the LAN side to the WAN
side.

Performs frame integrity checks (FCS and length).

Provides Ethernet statistics compliant with IEEE 802.3, SNMP SMON,
and RMON.
The main features of FEoS ports are:
Ethernet-over-SDH using VC-4 or virtual concatenation with

VC-3/VC-12 granularity. Each interface can be mapped over 1 x VC-4,
or N x VC-3 (3>=N>=1), or N x VC-12 (63>=N>=1).
Configurable allocation of the two (in BG-40) or four (in BG-20)
VC-4s to 16 FEoS ports.
Hitlessly increases/decreases the number of VC-3s/VC-12s in a group
(LCAS protocol).
Supports differential delay compensation of 64 ms for virtual
concatenation.
Mapping according to GFP and LAPS (LAPS has low priority in V1).
Performs VC-4/VC-3/VC-12 termination.
Provides availability statistics for the FEoS link.
| 8 x FE LAN ports (10/100BaseT, electrical interface) - for connecting to a
CE RS via Fast Ethernet.
| 2 x GE LAN ports (1000BaseSX/LX/ZX, optical interface) - for connecting
to a CE RS via Gigabit Ethernet.
The main features of FE and GE ports are:
IEEE 802.3 802.1q-compliant MAC for Ethernet frame handling.

Full VLAN support for up to 4,000 VLANs (both tagged and untagged
VLANs).
Supports a maximum Ethernet frame size of 9622 bytes.
Supports flow control.
Performs frame integrity checks (FCS and length).
Provides Ethernet statistics compliant with IEEE 802.3, SNMP, and
RMON.
Supports autonegotiation functionality.
FE ports support 10 Mbps/100 Mbps, full duplex/half duplex.
GE ports support 1000BaseSX/LX/ZX with an SFP module.

The following figure shows the ESW_2G_8F card window with its ports.
Figure 6-22: ESW_2G_8F card window
The ESW_2G_8F has the following managed objects that can be managed
through the EMS-BGF:
| LAN ports:
LAN
| WAN ports:
VCG
EoS
WAN
| Switch kernel:
Bridge

Attribute management for the ESW_2G_8F card includes:

| Configuration management:
VCG configuration
Acquisition of VCG timeslot resources
Addition of VCG member attributes and LCAS status
EoS encapsulation protocol configuration
Port attribute configuration
Link aggregation configuration
| Fault management:
Current alarms
Historical alarms
| Performance management:
Current performance
Historical performance
Performance threshold
Ethernet performance switch
| Maintenance:
Real-time traffic view
Loopbacks
Port-connected neighbors

To configure ESW_2G_8F card attributes:

1. In the NE Shelf View window, select and open the ESW_2G_8F card. The
following window is displayed:
Figure 6-23: ESW_2G_8F card window

2. To perform VGC configuration, select Configuration > VCG Attributes

in the menu. The VCG Attribute window opens.
Figure 6-24: VCG Attribute window - Traffic tab
Use this window to configure the virtual cascade mode (VC-12/VC-3) and
bandwidth of each VCG.

3. To configure the LCAS status, select the LCAS tab in the VCG Attribute
window. The following window is displayed:
Figure 6-25: VCG Attribute window - LCAS tab
Use this window to configure LCAS attributes.

4. To add a VCG member, select a VCG in the ESW_2G_8F card window

and then select Configuration > Member Add & Remove in the menu.
The VCG Member Add Attribute Set window opens.
Figure 6-26: VCG Member Add Attribute Set window
The operational objects in this window are the VCGs in the ESW_2G_8F
card. For every member of an VCG, an Add or Not Add attribute can be
set. The ESW_2G_8F card determines whether to add or remove the
corresponding VCG member according to variations of this attribute.

5. To configure the EoS encapsulation protocol, select Configuration > EOS

Attribute in the ESW_2G_8F card window menu. The EOS Protocol
window opens.
Figure 6-27: EOS Protocol window
This window contains EoS encapsulation protocol, sending FCS attribute,

and receiving FCS attribute information. For the ESW_2G_8F card's EoS
channel, one of two types of encapsulation protocol can be designated:
Null Extension Header GFP (the default)

LAPS
The sending FCS may be enabled or disabled. The default is enabled.
The Dedicate attribute value may be Yes or No. The default is No.

6. To configure the WAN Port attribute, select Configuration > PORT

Attribute > All WAN in the ESW_2G_8F card window menu. The WAN
Port Attributes window opens.
Figure 6-28: Port Attributes window for WAN ports
In this window, three attributes can be configured and three attributes are
read-only.
Read-only attributes are:
Duplex Status
Speed Status
Flow Control Status
Configurable attributes are:
NNI/UNI setting. Default settings are:

NNI for WAN1 through WAN8.
UNI for WAN9 through WAN16.
Max Package Length, which can be set for each WAN port.
SubNetwork ID, which can be set for each WAN port. It is used to
distinguish the VLAN subnetwork.

7. To configure the LAN Port attribute, select Configuration > PORT

Attribute > All LAN in the ESW_2G_8F card window menu. The LAN
Port Attributes window opens.
Figure 6-29: Port Attributes window for LAN ports
In this window, four attributes can be configured and three are read-only.
Read-only attributes are:
Duplex Status
Speed Status
Flow Control Status
Configurable attributes are:
Negotiation
Duplex
Speed
Flow Control

8. To view real-time traffic, select the Maintenance > Get Current Payload
in the ESW_2G_8F card window menu. The Get Current Payload Rate
window opens.
Figure 6-30: Get Current Payload Rate window
In this window, you acquire the RX and TX traffic of EoS and WAN ports
(ports 1 through 16). 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 can be specified
in bits per second (bps), Kbps, or Mbps. You can also select the adaptive
option. In this case, the system displays the data in the appropriate unit
according to the data size.

9. To view the neighbors connected to a WAN port, select a WAN port in the
ESW_2G_8F card window and then select Maintenance > Port
Connected Neighbor in the menu. The Port Connected Neighbor
window opens, which lists the neighbors connected by WAN ports.
Figure 6-31: Port Connected Neighbor window

10. To perform MST maintenance, select a VCG port in the ESW_2G_8F card
window and then select Maintenance > MST Maintenance in the menu.
The MST Maintenance window opens.
Figure 6-32: MST Maintenance window
For LCAS members, the MST FAIL Force/Release function can be

performed. MST attribute values are Auto and ForceFail. The default is
Auto.

11. To perform a loopback, select Maintenance > Loopback in the

ESW_2G_8F card window menu. The Loopback Setup window opens.
Figure 6-33: Loopback Setup window
12. Set the Loopback type for each VCG in this window, and click Apply to
save the configuration.
Configuring Ethernet Attributes

The FE_L12 card in BG-40 NEs supports Ethernet Layer 2. This section
introduces the basic principles and operational procedures for managing
Ethernet Layer 2 in the LCT-BGF. Configuration includes the port property,
VLAN, the address table, STP, packet priority, and Layer 2.

FE_L12 Ethernet Layer 2 Management

The Ethernet Layer 2 switch module is embedded in the FE_L12 card, and
provides manageable Layer 2 switch functions. This module does not require
configuration when the FE_L12 card only provides Layer 1 EOS services.
When the FE_L12 card provides the following functions, you should configure
the FE_L12 card in the L2 Switch Configuration Management window:
| Port convergence (server WAN/LAN port converge to one LAN port)
| Divide VLAN
| Packet priority
| Ethernet protection
To access the FE_L12 L2 Switch Configuration Management

window:
| In the LCT-Login BG-40 NE (shelf view) window, open the FE_L12 card
window. Select Ethernet > L2 Switch Configuration in the menu. The L2
Switch Configuration Management window opens.
Figure 6-34: FE_L12 card window showing how to access the Layer 2 Switch
Configuration Management window

Configuring port attributes

Port attributes include the rate (10 Mbps or 100 Mbps), mode (full or half), and
flow control (enabled or disabled). To communicate between Ethernet ports,
these port attributes must be the same. To simplify configuration, Ethernet
ports support an autonegotiation mechanism to automatically negotiate port
attributes. The FE_L12 supports the negotiation range of each attribute.
Autonegotiation is enabled by default for FE_L12 port attributes. You do not
need to configure port attributes manually.
Autonegotiation is based on the following principle: select the optimized
attributes according to the efficiency supported by the negotiation ranges. For
example, if two connected Ethernet ports support 10BaseT or 100BaseT with
either Full or Half mode and flow control enabled or disabled, then the final
optimized attributes for the two ports are: 100BaseT, full mode, and flow
control enabled.
If autonegotiation is disabled on the port connected to the FE_L12, there are
two options:
| Disable the FE_L12 port's autonegotiation and configure the port attributes
manually to be consistent with the connected port
| Enable the connected port's autonegotiation
NOTE:
| If the FE_L12 port's autonegotiation is enabled and the
connected port's autonegotiation is disabled, the FE_L12
port works in Half mode (even if the connected port is in
Full mode), and flow control is disabled (even if flow
control is enabled on the connected port).
| If the FE_L12 port's autonegotiation is enabled, all
attributes (rate, mode, and flow control) are
autonegotiated. Some attributes cannot be configured for
autonegotiation. Some equipment does not support flow
control autonegotiation. In this case, the FE_L12 must
configure the port attributes manually. Otherwise, the
FE_L12 works with flow control disabled.

To configure port attributes:

1. In the L2 Switch Configuration Management window, select the Port
Attributes tab.
Figure 6-35: L2 Switch Configuration Management window - Port Attributes

tab
2. Click Get to list the port attributes. The attributes' working values are
displayed in the Duplex Status, Speed Status, and Flow Control Status
columns.
3. Configure port autonegotiation. This configuration is only performed for
one specified port. For the eight ports in the FE_L12 card, some ports can
be set with autonegotiation enabled and some with autonegotiation
disabled.

4. Configure the attributes range. If a port has autonegotiation enabled, the

port's attribute range (Duplex, Speed, Flow Control in the port attributes
table) contains the optimized values in the autonegotiation range. For
example, if Speed is 100 Mbps, the range is 10 Mbps and 100 Mbps. If
Duplex is set to Full mode, the range is both Full mode and Half mode. If
Flow Control is enabled, the range is both enabled and disabled. If you
select 10 Mbps for the Speed, then the maximum rate is 10 Mbps. The
default settings for attributes range are: 100 Mbps, Full mode and Flow
Control enabled.
Manually set the port attributes. If port autonegotiation is disabled, set the
port attributes in the Duplex, Speed, and Flow Control columns.
Configuring the VLAN

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

1. In the L2 Switch Configuration Management window, select the VLAN
tab.
Figure 6-36: L2 Switch Configuration Management window - VLAN tab
2. Select the Static VLAN or Current VLAN radio button and then click Get
to retrieve the static VLAN table and current VLAN table.

To create a static VLAN:

tab.
2. Click Create. The Create a VLAN window opens.
Figure 6-37: Create a VLAN window
3. Input the VLAN name and VLAN ID.

4. Add the member ports by selecting ports in the VLAN Port area.
5. Define the untagged member ports in the Untagged Port area.

To edit a static VLAN:

1. In the L2 Switch Config Management window, select the VLAN tab.
2. Select the VLAN to be edited in the VLAN table and then click Edit. The
Modify VLAN window opens.
Figure 6-38: Modify VLAN window
3. Add or remove VLAN member ports or untagged ports as needed.
To delete a static VLAN:

tab.
2. Select the VLAN to be deleted in the VLAN table.
3. Click Delete.

To configure a port's default VLAN ID:

| 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. The LCT-BGF cannot
change this PVID. 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.
In the L2 Switch Configuration Management window, select the VLAN
tab and then set the port's default VLAN ID in the Port PVID field.
To configure the GVRP switch:

The GVRP protocol can be enabled or disabled. Each port also can be enabled
or disabled. The default value for GVRP is enabled, and enabled for the port. In
the network, GVRP should be enabled for switch interconnection ports and
disabled for ports connected to the LAN.
tab.
2. Click Get in the GVRP area to retrieve the GVRP settings.
3. Set the GVRP value and click Apply to save your settings.

Configuring the FDB

The FE_L12 Filter Database (vFIB) table length is 4 K. vFIB-related
operations include configuring the Aging Time, flushing the vFIB, configuring
the Static vFIB table, and configuring the Port Lock. These operations are
accessed from the vFIB tab in the L2 Switch Configuration Management
window.
Figure 6-39: L2 Switch Configuration Management window - FDB tab
Configuring the aging time
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.

To configure the Aging Time:

1. In the L2 Switch Configuration Management window, select the vFIB
tab.
2. Click Get in the Aging Times area to retrieve the aging time settings. The
default value for the aging time is 300 times.
3. Set the aging time value and click Apply to save the setting. The step value
for setting the aging time is 21 seconds.
Flushing the FDB
Flushing the vFIB:

| Removes old MAC addresses rapidly.
| Restarts the address-learning process.
| Uses new static MAC addresses.
To flush the vFIB:

tab.
2. Click Flush vFIB to flush the vFIB.
Configuring the static FDB table
Static MAC addresses are MAC addresses configured by the LCT-BGF that do
not age. These MAC addresses are unicast addresses. There are three relevant
fields in the Static FDB table: Port, MAC Address, and VLAN. For a specific
VLAN, a port's unicast MAC address must be unique. Different VLANs can
have the same MAC address.
To configure the static vFIB table:

tab.
2. Click Get in the Static vFIB Tables area to retrieve the static vFIB items.
3. Click Create to add new items to vFIB tables.
4. Select items to be deleted and click Delete to remove them.

Port Lock configuration
When the FE_L12 Layer 2 port's Port Lock is enabled, the address-learning
function is disabled. If a MAC frame contains a new source MAC address, this
frame is discarded.
Together, the Port Lock and the Static vFIB Table provide port access security.
If a port can only be accessed by two specific users, set these users' MAC
addresses in the Static vFIB Table and enable the Port Lock. Other network
devices cannot access this port.
To configure the Port Lock:

tab.
2. Click Get in the Port Lock area to retrieve the Port Lock status.
3. Modify the Port Lock status and click Apply to send the status to the
equipment.
Configuring STP
The Spanning Tree Protocol (STP) is a Layer 2 link management protocol that
provides path redundancy while preventing undesirable loops in the network.
For a Layer 2 Ethernet network to function properly, only one active path can
exist between any two stations. STP operation is transparent to end stations,
which cannot detect whether they are connected to a single LAN segment or a
switched LAN of multiple segments.
When you create fault-tolerant internetworks, you must have a loop-free path
between all nodes in a network. The STP algorithm calculates the best
loop-free path throughout a switched Layer 2 network. Layer 2 LAN ports send
and receive STP frames at regular intervals. Network devices do not forward
these frames, but use the frames to construct a loop-free path.
Multiple active paths between end stations cause loops in the network. If a loop
exists in the network, end stations may receive duplicate messages and network
devices may learn end station MAC addresses on multiple Layer 2 LAN ports.
These conditions result in an unstable network.
STP defines a tree with a root bridge and a loop-free path from the root to all
network devices in the Layer 2 network. STP forces redundant data paths into a
standby (blocked) state. If a network segment in the spanning tree fails and a
redundant path exists, the STP algorithm recalculates the spanning tree
topology and activates the standby path.

When two Layer 2 LAN ports on a network device are part of a loop, the STP
port priority and port path cost setting determine which port is put in the
forwarding state and which port is put in the blocking state. The STP port
priority value represents the location of a port in the network topology and how
well located it is to pass traffic. The STP port path cost value represents the
media speed.
IEEE defined the 802.1D specification in 1998. The STP protocol is the
spanning tree protocol supported by most current Ethernet switches. The
FE_L12 Layer 2 supports the 802.1D specification.
STP configuration sets STP parameters in order to select the proper spanning
tree topology and block nodes. STP configuration involves two tabs in the L2
Switch Configuration Management window: the Bridge STP tab and Port
STP tab. The parameters in these tabs set Layer 2 and port parameters,
respectively. The STP protocol can be enabled or disabled in the Bridge STP
tab.
STP algorithm
The following briefly describes basic STP algorithm (STA) concepts:

| Select root bridge
Networks using STA must select a root bridge. The bridge with the highest
priority is the root bridge. If the priorities are the same, the bridge with the
lowest node ID is the root bridge.
| Select root port

Each bridge (except the root bridge) should select a root port. The port with
the lowest path cost is the root port. If the path costs are the same, the port
with the lowest port ID is the root port. The path cost is the total cost from
the port to the root bridge.
| Select the designated bridge

Each network segment should have a designated bridge. The bridge with
the lowest path cost to the root bridge is selected, and the port connected to
this designated bridge is the designated port.
| Set port status

The STA sets the status of all root ports and designated ports as
Forwarding. Others are set to Blocking.

Each port has five statuses, which are described in the following table.
Table 6-4: STP port status
Port states Enable Enable frame Forward Receive Enable Forward

learning forwarding received BPDUs filtering BPDUs
frames
Disabled No No No No No No
Blocking No No No Yes No Yes
Listening No No No Yes No Yes
Learning Yes No No Yes No Yes
Forwarding Yes Yes Yes Yes Yes Yes
Obtaining bridge STP settings
The Bridge STP tab in the L2 Switch Configuration Management window

enables you to retrieve the following information for a bridge:
| Bridge MAC address
| Root path cost
| Time since last topology change
The following information about the root bridge can be retrieved in the Bridge
STP tab:
| Bridge priority
| Bridge MAC address
| Hello timer
| Forward delay timer
| Maximum age timer

To obtain bridge STP settings:

1. In the L2 Switch Configuration Management window, select the Bridge
STP tab.
Figure 6-40: L2 Switch Configuration Management window - Bridge STP tab
2. Click Get to retrieve the bridge STP settings.

Configuring bridge STP settings
Five parameters can be set in the Bridge STP tab:

| Bridge STP enable/disable. The default is enabled.
| Bridge priority. The default is 32768. This parameter is used for root bridge
selection. The lower the parameter, the higher the priority. The bridge with
the highest priority is the root bridge.
| Three STP protocol timers (see the following table)
Table 6-5: STP timers
Variable Description
Hello timer Determines how often the network device broadcasts hello
messages to other network devices
Forward delay timer Determines how long each listening and learning state lasts
before the port begins forwarding
Maximum age timer Determines the amount of time protocol information received
on a port is stored by the network device
To configure bridge STP settings:

1. In the L2 Switch Configuration Management window, select the Bridge
STP tab.
2. Set the bridge parameters in Bridge STP Configuration area.
3. Click Apply to send the settings to the equipment and the database.
Configuring port STP settings
The following information about a bridge's ports can be viewed in the Port STP
tab:
| Port STP enabled or disabled status.
| Port path cost. The higher the rate, the lower the path cost. The path cost is
19 for 100BaseT ports.
| Port STP priority. The lower the value, the higher the priority. This is used
for selecting the root port or a designated port.
| Port State (Disable, Blocking, Listening, Learning, Forwarding).

To view port STP settings:

STP tab.
Figure 6-41: L2 Switch Configuration Management window - Port STP tab
2. Click Get to obtain the port STP settings.
To configure port STP settings:

STP tab.
2. Set the port STP parameters.
3. Click Apply to send the port STP settings to the equipment and the
database.

Configuring port priority settings
The FE_L12 switch supports two priority queues on each of the eight
10BaseT/100BaseT ports, and two priority queues for packet transfers to the
CPU. The switch assigns a priority to each packet, based on the following
algorithm:
| The BPDU packets are always marked with high priority when forwarding
to the CPU.
| Unknown unicast destination addresses are always set to low priority.
| To determine the priority of the other packets received on one of the eight
ports, the following algorithm is applied:
If the <Priority_Override> is selected by the LCT-BGF, then priority is
determined by the <Default_Priority> configured by the LCT-BGF.
Otherwise, a packet is normally classified as Low priority unless at
least one of the following is true:
The packet contains a tag (per the IEEE 802.1Q definition), then the
three bits of the 802.1p user priority tag are used. If the
corresponding bit is set, the packet is assigned a high priority.
The input port default priority is high.
| A fixed mapping of the three-bit received priority tag to the priority queue
is used: 0 to 3 to the low Priority queue and 4 to 7 to the high priority
queue.
| The priority weight in the round-robin between the high- and low-priority
TX queues on the 10BaseT/100BaseT ports is as follows:
000 - one packet transmitted from high, one packet from low.
001 - two packets transmitted from high, one packet from low.
010 - four packets transmitted from high, one packet from low.
011 - six packets transmitted from high, one packet from low.
100 - eight packets transmitted from high, one packet from low.
101 - 10 packets transmitted from high, one packet from low.
110 - 12 packets transmitted from high, one packet from low.
111 - all packets transmitted from high, zero packets from low.

To configure port priority:

1. In the L2 Switch Configuration Management window, select the Priority
tab.
Figure 6-42: L2 Switch Configuration Management window - Priority tab
2. Set the port priority parameters, as follows:

Priority - 0 to 3: low priority; 4 to 7 high priority; the default is low
priority.
Bridge Priority Weight:
1:1 - one packet transmitted from high, one packet from low.
2:1 - two packets transmitted from high, one packet from low.
4:1 - four packets transmitted from high, one packet from low.
6:1 - six packets transmitted from high, one packet from low.
8:1 - eight packets transmitted from high, one packet from low.
10:1 - 10 packets transmitted from high, one packet from low.
12:1 - 12 packets transmitted from high, one packet from low.
All - all packets transmitted from high, zero packets from low.

The default is All.

Overwrite Priority
3. Click Apply to send the port priority settings to the equipment and the
database.
Managing the Ethernet configuration

The following Ethernet management operations can be performed:
| Uploading configuration data
| Downloading configuration data
| Querying configuration data
| Checking configuration data consistency
| Saving configuration data to the database
Ethernet configuration affects the following Ethernet-related data: bridge STP,
port STP, aging times, static FDB tables, NB priority, VLAN tables, port VID,
Port attribute, port lock, and GVRP.

To access the Up/Down Load Bridge Configuration Data

window:
1. In the LCT-Login BG-40 NE (shelf view) window, open the FE_L12 card
window.
2. Select Ethernet > L2 Switch Configuration Data Management in the
menu. The Up/Down Load Bridge Configuration Data window opens.
Figure 6-43: Up/Down Load Bridge Configuration Data window
To upload configuration data:

1. Access the Up/Down Load Bridge Configuration Data (on page 6-57)
window.
2. Select the configuration to be uploaded in Data Type field.
3. Click Upload to upload the configuration data from the equipment. The
uploaded data is displayed in the window.
To download configuration data:

window.
2. Select the configuration to be downloaded in the Data Type field.
3. Click Download to download the configuration data to the equipment.

To query configuration data:

window.
2. Select the configuration to be queried in the Data Type field.
3. Click Query to retrieve the configuration data. The retrieved data is
displayed in the window.
To check configuration data consistency:

window.
2. Click Compare with NM to compare the uploaded configuration data with
the LCT-BGF database. Comparison results are displayed in the window.
To save configuration data to the database:

1. After configuration data has been uploaded, open the Up/Down Load
Bridge Configuration Data (on page 6-57) window.
2. Click Save to DB to save the configuration data to the LCT-BGF database.

To clear configuration data:

window.
2. Select Ethernet > Clear L2 Switch Configuration Data in the menu to
clear the configuration data. A confirmation window opens.
Figure 6-44: Task window showing clear configuration data operation
After the Layer 2 configuration is cleared, the embedded software performs

a warm reset on the FE_L12 card. The configuration is restored to its initial
value two minutes after the warm reset completes.
3. Click Close to close the confirmation window.

To save configuration data:

window.
2. Select Ethernet > Save L2 Switch Configuration Data in the menu to
save the configuration data. A confirmation window opens.
Figure 6-45: Task window showing save configuration data operation
3. Click Close to exit the confirmation window.
ESW_2G_8F Ethernet Layer 2 Management

This section describes Ethernet Layer 2 management for the ESW_2G_8F card.
Managing the bandwidth profile

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

To access the bandwidth profile:

1. In the ESW_2G_8F card window, select Bridge > VPN Configuration >
Bandwidth Profile in the menu. The Bandwidth Profile window opens.
Figure 6-46: Bandwidth Profile window
2. Click Default to restore to the default bandwidth profile.

3. Click Get to retrieve the bandwidth profile from the equipment.
4. Change the Committed Information Rate (CIR) and Committed Burst Size
(CBS) values as required, and click Apply to save the settings.
NOTE: Due to the limitation of the hardware, the

ESW_2G_8F card only supports eight bandwidth profile
levels.
Configuring the policer

Policers follow the DiffServ model in order to ensure that the correct
bandwidth limitations defined in the Service Level Agreement (SLA) between
the provider and the provider's customers are enforced. Any traffic that exceeds
these limits is dropped at the ingress to the flow. Up to 128 policers can be
defined per ESW_2G_8F card.

When creating an EVPLAN, each UNI port must have a policer. Each policer
can be used only once. Policers values can be identical, except for the policer
name.
To create a policer:
Create Policer in the menu. The Create Policer window opens.
Figure 6-47: Create Policer window
2. Input the following parameters for the policer:

Policer ID: Enter a numeric value between 1 to 128 for the policer. Up
to 128 policers can be defined.
CIR: Select the Committed Information Rate (CIR) in the drop-down
list.
CBS: Select the Committed Burst Size in the CBS drop-down list.
S-VLAN CoS: Select the Class of Service (CoS) where the customers
traffic enters the providers network.
Service State: Select Enabled or Disabled in the drop-down list to
enable or disable the service. The default is Enabled.
Label: Enter a name for the policer.
3. Click Apply to create the policer.

To access the policer list:

| In the ESW_2G_8F card window, select Bridge > VPN Configuration >
Policer List in the menu. The Policer List window opens.
Figure 6-48: Policer List window

To filter the policer list:

1. In the Policer List window, specify the filter to be used in the Filter area by
selecting the relevant checkbox. Policers can be filtered by S-VLAN CoS,
Service State, or Occupied (used).
Figure 6-49: Policer List window showing filters
2. Specify your filter criteria by selecting the appropriate option in the

respective drop-down list.
3. Click Filter to display the filtered results.

To edit the policer list:

1. In the Policer List window, select the policer to be edited.
Figure 6-50: Policer List window - editing the policer list
2. Click Edit. The Edit Policer window opens.
Figure 6-51: Edit Policer window
3. Change the policer values as required, and click Apply to save the settings.

To delete a policer:
1. In the Policer List window, select the policer to be deleted and then click
Delete.
2. A confirmation window is displayed.
3. Click OK to delete the policer, or Cancel to abort the deletion operation.
NOTE: A policer used by a UNI port cannot be deleted.
To upload a policer:
1. In the Policer List window, click Upload. The Policer Upload window
opens.
Figure 6-52: Policer Upload window - Policer Upload tab
2. Click Upload for the LCT-BGF to upload policers from the ESW_2G_8F
card.
The status bar shows the consistency status between the NE and the
LCT-BGF database.

If the NE and the LCT-BGF database are inconsistent, select the Policer
Compare tab to display the inconsistency results.
Figure 6-53: Policer Upload window - Policer Compare tab
3. Click Overwrite to overwrite the database with the NE data.
Managing VPN services

The ESW_2G_8F supports a Virtual Private Network (VPN). VPNs define
policies and provide users' Service Level Agreements (SLAs).

The ESW_2G_8F supports the following VPN types:

| EPL - Ethernet Private Line (dedicated EoS link)
Figure 6-54: ESW_2G_8F - EPL
| EVPLAN - Ethernet Virtual Private LAN:

EPLAN - dedicated EoS link
EVPLAN - shared EoS link
Figure 6-55: ESW_2G_8F - EVPLAN

To create an EPL:
Create VPN in the menu. The Create VPN window opens.
Figure 6-56: Create VPN window (EPL)
2. In the Service Type field, select the EPL radio button.

3. Enter the Customer, User Label, and VPNID values in the respective fields.
4. Select the Client Signal Failure (CSF) Enable checkbox, if needed.
5. Select an EPL port in the Add Port drop-down list, and click >> to add it to
the Ports list. Repeat this step for all EPL ports.
6. Click Apply to create the EPL.

To create an EVPLAN:
To create an EVPLAN, you should configure the NNI ports, UNI ports, and
policers.
Create VPN in the menu. The Create VPN window opens.
2. In the Service Type field, select the EVPLAN radio button.
Figure 6-57: Create VPN window (EVPLAN)
3. Enter the Customer, User Label, VPNID, S-VLAN ID, and FDB Quota
values at the top of the window.

4. Select an NNI port in the Add Port and Map Policer drop-down list, and
click >> to add it to the Ports list. Repeat this step for each NNI port.
Figure 6-58: Create VPN window (EVPLAN) - select NNI ports

5. Select a UNI port in the Port drop-down list, and click >> to add it to the
Ports list. When selecting a UNI port, the Tag Type and C-VLAN ID
values should also be set.
Figure 6-59: Create VPN window (EVPLAN) - add policer
NOTE: The bandwidth values in the Add Port and Map

Policer area, including the CIR and CBS values, are read-
only.
6. Set the C-VID Range in the respective From and To boxes.

7. In the Map Policer area, select the Customer CoS values in the From and
To drop-down lists, and select a policer in the Policer drop-down list.

8. Click Add to add the policer to the C-VLAN.
Figure 6-60: Create VPN window (EVPLAN) - mapped policer
9. Click Apply to create the EVPLAN.

Using the VPN list
The VPN list is used to view and manage VPN items.
To access the VPN list:

| In the ESW_2G_8F card window, select Bridge > VPN Configuration >
VPN List in the menu. The VPN List window opens.
Figure 6-61: VPN List window
To filter the VPN list:

1. In the VPN List window (on page 6-74), select the filter to be used in the
Filter Options area. Policers can be filtered by the Service Type, which is
either EPL or EVPLAN.
Figure 6-62: VPN List window showing filter options
2. Click Filter. The filtered results are displayed in the window.

To upload the VPN list:

1. In the VPN List window (on page 6-74), click VPN Upload. The VPN
Upload window opens.
Figure 6-63: VPN Upload window - VPN Upload tab
2. Click Upload to display the results.

The status bar shows the consistency status between the NE and the
LCT-BGF database.

If the NE and the LCT-BGF database are inconsistent, select the VPN
Compare tab to display the differences.
Figure 6-64: VPN Upload window - VPN Compare tab
3. Click Overwrite to overwrite the database with the NE data.
To view a VPN:
| In the VPN List window (on page 6-74), right-click a VPN to select it, and
select View VPN in the pop-up menu.
Figure 6-65: VPN List window showing menu options

The VPN View window opens.
Figure 6-66: View VPN window
The VPN attributes are shown in the window, including the Service Type,
VPNID, Customer, User Label, and Ports.

To edit a VPN:
1. In the VPN List window (on page 6-74), right-click a VPN to select it, and
select Edit VPN in the pop-up menu. The Edit VPN window opens.
Figure 6-67: Edit VPN window
2. Modify the VPN settings as needed and click Apply to save the settings.
To delete a VPN:
1. In the VPN List window (on page 6-74), right click a VPN to select it, and
select Delete VPN in the pop-up menu.
2. A confirmation window is displayed.
3. Click OK to delete the VPN.

To export the VPN list:

Export VPN List in the menu. The Export VPN List window opens.
Figure 6-68: Export VPN List window
2. Click Save To File. The Select File window opens.
Figure 6-69: Select File window
3. Enter the file name and click Save to save the VPN export file.

To import the VPN list:

Import VPN List in the menu. The Import VPN List window opens.
Figure 6-70: Import VPN List and Select File windows

2. Select the VPN list file in the Select File window, and click Open. The
imported VPN list is displayed in the window.
Figure 6-71: Import VPN List window showing import results
3. Select the specific VPN to be imported, and click Apply to import it.
Configuring the vFIB

The ESW_2G_8F Filter Database table length is 6 K. vFIB-related operations
include configuring the Aging Time, flushing the vFIB, and configuring the
Port Lock.
Configuring the aging time
The ESW_2G_8F has a dynamic address-learning function. All the

dynamically learned addresses need aging.
The ESW_2G_8F has seven levels of aging time:
| 280 seconds
| 70 minutes
| 210 minutes
| 14 hours
| 64 hours

| One day
| 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 the Aging Time:

1. In the ESW_2G_8F card window, select Bridge > vFIB > Global vFIB
Attributes. The Global vFIB Attributes window opens.
Figure 6-72: Global vFIB Attributes window

2. Click Get in the Aging Time area to retrieve the aging time settings. The
default value for the aging time is five minutes.
3. Set the aging time value and click Apply to save the setting.
Flushing the vFIB
Flushing the vFIB:

| Removes old MAC addresses rapidly.
| Restarts the address-learning process.
| Uses new static MAC addresses.
To flush the vFIB:

| In the ESW_2G_8F card window, select Bridge > vFIB > Flush All vFIB
in the menu to flush the vFIB.
Configuring the port lock
When the ESW_2G_8F's Port Lock is enabled, the address-learning function is

disabled. If a MAC frame contains a new source MAC address, this frame is
discarded.
To configure the Port Lock:

1. In the ESW_2G_8F card window, select Bridge > vFIB > Global vFIB
Attributes in the menu. The Global vFIB Attributes window (on
page 6-82) opens.
2. Click Get in the Port Lock area to retrieve the Port Lock status.
3. Modify the Port Lock status and click Apply to send the status to the
equipment.

Tracing the MAC address
The Trace MAC Address feature enables you to show which ports/VPNs/NEs
correspond to the input MAC address.
To trace the MAC address:

1. In the ESW_2G_8F card window, select Bridge > vFIB > Trace MAC in
the menu. The Trace MAC window opens.
Figure 6-73: Trace MAC window
2. Input the MAC address in the Enter MAC address text box.
3. Click Trace MAC to display the results.

Configuring MSTP
The ESW_2G_8F supports the Multiple Spanning Tree Protocol (MSTP).
MSTP builds multiple spanning trees (STs) in a region. Each S-VLAN is
carried by a single ST. STs are referred to as Multiple Spanning Tree Instances
(MSTIs) and are denoted by MSTi (where i ranges from 1 to N).
The key reason for using MSTP is to use all the links of the network. This is
important because a link may be blocked for one tree but active for another.
Another key reason is to choose good roots per service. For example, a
broadcast should be rooted at the broadcasting node.
Regions are constructed autonomously by the MST protocol. A digest of the
mapping of S-VLAN IDs to MSTi is used as part of the region designator.
Changing this mapping influences the region definition. Therefore, the
mapping should only be changed when the regions and trees are to be changed
not when a service is added.
MSTP ensures that regions are contiguous. If there are noncontiguous islands
of MSTP-speaking elements, each island becomes a region and (multiple)
separate trees are created in each region.
Filtering identifier
Each S-VLAN belongs to a Filtering IDentifier (FID) that accommodates the

separate learning of MAC addresses per FID. Each FID is assigned to an
MSTI.
FIDs per MSTI must be unique. For the ESW_2G_8F, there is an FID for each
S-VLAN, so this distinction is not important.
RSTP/MSTP interworking and interregional

interworking
There is a Common and Internal Spanning Tree (CIST) common to all regions
and RSTP-only bridges. MSTIs are specific to regions.
In each region, there is a CIST regional root bridge, as well as an MSTI
regional root for each MSTI. Interregional traffic reaches the regional root on
the MSTi and then moves to the CIST regional root on the CIST until reaching
the destination (region).

To obtain bridge MSTP settings:

1. In the ESW_2G_8F card window, select Bridge > MSTP Configuration >
Bridge in the menu. The MSTP Configuration window opens.
Figure 6-74: MSTP Configuration window - General tab
2. In the General tab, click Get to retrieve the bridge MSTP general settings.

3. In the Instance tab, click Get to retrieve the MSTP instance information.
Figure 6-75: MSTP Configuration window - Instance tab
Configuring bridge MSTP settings
The following parameters can be set the MSTP Configuration window -

General tab (on page 6-86):
| MSTP Work Mode: MSTP is the only option.
| Protocol enable/disable. The default is enabled.
| Bridge Priority specifying the priority for each instance. The default is
32768.
| MSTP region parameters:
Region Name. The default is hetc.
Revision Level. The default is 0.
Network ID. The default is 0.

| Three MSTP protocol timers (see the following table).
Table 6-6: ESW_2G_8F MSTP timers
Variable Description
Hello timer Determines how often the network device broadcasts hello
messages to other network devices
Forward delay timer Determines how long each listening and learning state lasts
before the port begins forwarding
Maximum age timer Determines the amount of time protocol information received
on a port is stored by the network device
To configure bridge MSTP settings:

1. In the MSTP Configuration window, select the General tab.
2. Set the bridge parameters.
3. Select the Instance tab.
4. Set the instances bridge priority.
5. Click Apply to send the settings to the equipment and the database.
Configuring port MSTP settings
The following information about a bridge's ports can be viewed in the Port
MSTP tab:
| Port MSTP enabled/disabled status.
| Edge Port enabled/disabled status.
| Hold-off Time.
| Port path cost. This path cost is per instance. The higher the rate, the lower
the path cost. The path cost is 19 for 100BaseT ports.
| Port MSTP priority. This priority is per instance. The lower the value, the
higher the priority. This is used to select the root port or a designated port.
| Port State (Disable, Blocking, Listening, Learning, Forwarding).

To view port MSTP settings:

1. In the ESW_2G_8F card window, select Bridge > MSTP Configuration >
Port in the menu. The MSTP Port Configuration window opens.
Figure 6-76: MSTP Port Configuration window - Port Attributes tab
2. Click Get to obtain the port MSTP settings.

3. Select the Instance Attribute tab.
Figure 6-77: MSTP Configuration window - Instance Attribute tab
4. Click Get to obtain the instance attributes.
To configure port MSTP settings:

1. In the MSTP Port Configuration window, select the Port Attributes tab.
2. Set the port MSTP parameters.
3. Select Instance Attribute tab.
4. Set the path cost and priority.
5. Click Apply to send the port STP settings to the equipment and the
database.
Managing a link aggregation group

The Link Aggregation Control Protocol (LACP) is part of the IEEE
specification 802.3ad that enables the bundling of several physical ports
together to form a single logical channel. LACP allows a network switch to
negotiate an automatic bundle by sending LACP packets to the peer. LACP is a
protocol implemented in OSI Layer 2, which controls through which physical
links the traffic is routed.

The advantages of link aggregation, as described in IEEE 802.3ad, are:

| Increased bandwidth
| Failover when link status fails on a port
| Linearly incremental bandwidth
| Increased availability
| Load sharing
| Automatic configuration
| Rapid configuration and reconfiguration
| Low risk of duplication or disordering
| Support of existing IEEE 802.3 MAC clients
| Backwards compatibility with aggregation-unaware devices
| No change to IEEE 802.3 frame format
Figure 6-78: Link aggregation
The ESW_2G_8F supports up to 13 aggregation groups. An aggregation should

be supported in ESW_2G_8F, as follows:
| Two/four ports for NNI WAN FE ports
| Two/four ports for UNI LAN FE ports
| Two ports for UNI LAN GbE
| Two/four ports for UNI WAN FE ports

The following rules apply when adding ports to an aggregation group:

| NNI ports and UNI ports cannot be added to the same aggregation group.
| The number of ports in an aggregation group is two or four, and the port
numbers should be in sequence. For example, 1 and 2, or 3 and 4, or 1, 2, 3,
and 4 is permitted, and 3, 4, 5, and 6 is not permitted.
There are 13 existing aggregation groups. To configure an aggregation group,
you select a group and add ports to it.
To create/edit aggregation ports:

1. In the ESW_2G_8F card window, select Bridge > LAG > Create/Edit
Aggregation Ports in the menu. The Create/Edit Aggregation Ports
window opens.
Figure 6-79: Create/Edit Aggregation Ports window
2. Select an aggregation group from the Aggregation Group drop-down list.

3. Select ports in the Individual Port List and click > to add the ports to the
aggregation group.
4. To remove a port from an aggregation group, select the port(s) in the
Aggregation Port List and click <.

5. Click Apply to save the results. The aggregation group is added to the list
in the ESW_2G_8F card window.
Figure 6-80: ESW_2G_8F card window showing aggregation groups
Configuring the link aggregation group
Server load balancing and failover mechanisms are supported via flexible link
aggregation that is based on the MAC destination and source addresses. The
port within a Link Aggregation Group (LAG) that is to be used as a destination
can be selected based on the Ethernet source and/or destination address or the
IP source and/or destination address. The ESW_2G_8F card does not support
IP addresses.

To configure the LAG:

1. In the ESW_2G_8F card window, select Bridge > LAG > LAG
Configuration in the menu. The Trunk Mode window opens.
Figure 6-81: Trunk Mode window
2. Select the required aggregation groups in the Aggregation Group list.

3. Select the trunk mode in the Trunk Mode drop-down list. The supported
trunk modes are:
Source MAC
Destination MAC
Source XOR Destination MAC
4. Click Apply to save the settings.

NOTE: The port within a LAG to be used as a destination can

be selected on the basis of the Ethernet source and/or
destination address or the IP source and/or destination
address. The rule for selection is as follows:
If (PR_CTRL_REG.LS = 1 and IP_found = 1)

Trunk Destination = (IP_SA[2:0] AND
PR_CTRL_REG.TS) XOR (IP_DA[2:0]
AND
PR_CTRL_REG.TD);
Else
Trunk Destination = (SA[2:0] AND PR_CTRL_REG.TS)
XOR (DA[2:0]
AND PR_CTRL_REG.TD);
Operating the link aggregation group
When performing MSTP/VPN/vFIB operations on the member ports of a link

aggregation group, these ports are treated as one logical port. The following
conditions apply for such operations:
| Link Aggregation Group for VPN
A link aggregation group can be added to the EPL and EVPLAN. In this
case, the link aggregation group is used as a logical port, and the bandwidth
is the sum of all the member ports. Member ports of a link aggregation
group cannot be added to a VPN as independent ports.
| Link Aggregation Group for vFIB and MSTP

A link aggregation group supports vFIB and MSTP operations. When
performing vFIB or MSTP operations on a link aggregation group, the
managed object is the link aggregation group. The managed object cannot
be the member ports.

| Link Aggregation Groups Alarm

A link aggregation group can report alarms. These alarms include the link
aggregation group alarm and the highest severity alarms of the member
ports.
The alarms of a link aggregation group and its member ports can be
masked.
| Link Aggregation Groups Performance

A link aggregation group supports performance thresholds. The
performance thresholds of a link aggregation group are the same as those of
its member ports.
Managing the Ethernet configuration

The following Ethernet management operations can be performed for the
ESW_2G_8F card:
| Uploading configuration data
| Downloading configuration data
| Querying configuration data
| Checking configuration data consistency
| Saving configuration data to the database
Ethernet configuration affects the following Ethernet-related data: bridge STP,
port STP, aging times, static vFIB tables, NB priority, VLAN tables, port VID,
Port attribute, port lock, and GVRP.

To access the Up/Down Load Bridge Configuration Data

window:
1. In the BG-40 Shelf View window, select the ESW_2G_8F card to open the
ESW_2G_8F card window.
2. Select Bridge > Configuration Data Management in the menu. The
Up/Down Load Bridge Configuration Data window opens.
Figure 6-82: Up/Down Load Bridge Configuration Data window
To upload configuration data:

1. Access the Up/Down Load Bridge Configuration Data window (on
page 6-97).
2. Select the configuration to be uploaded in Data Type field.
3. Click Up Load to upload the configuration data from the equipment. The
uploaded data is displayed in the window.
To download configuration data:

page 6-97).
2. Select the configuration to be downloaded in the Data Type field.
3. Click Down Load to download the configuration data to the equipment.

To query configuration data:

page 6-97).
2. Select the configuration to be queried in the Data Type field.
3. Click Query to retrieve the configuration data. The retrieved data is
displayed in the window.
To check configuration data consistency:

page 6-97).
2. Click Compare with NM to compare the uploaded configuration data with
the LCT-BGF database. Comparison results are displayed in the window.
To save configuration data to the database:

1. After configuration data has been uploaded, open the Up/Down Load
Bridge Configuration Data window (on page 6-97).
2. Click Save to DB to save the configuration data to the LCT-BGF database.

7
Managing Cross Connections
In this chapter:
Overview ......................................................................................................... 7-1
Configuring and Managing Server Trail XCs ................................................. 7-1
Configuring and Managing Client Trail XCs ................................................ 7-10
Setting Up MSP 1+1 XC Protection.............................................................. 7-17
Configuring SNCP Attributes........................................................................ 7-20
Exporting Trails as a File............................................................................... 7-22
Importing Trails from a File .......................................................................... 7-24
Uploading XCs .............................................................................................. 7-25
Overview
LCT-BGF cross-connection (XC) management provides XC configuration at
the NE level.
Configuring and Managing

Server Trail XCs
The server trail is responsible for the planning of the network resources.
Creating a Server Trail XC Manually

Creating a manual server trail XC configures the cross connection of the server
trail by configuring the VC-4 service of a single NE. The server trail can only
be used by the client trail after all server trail XCs have been configured.

Managing Cross Connections LCT-BGF User Manual
To manually create a server trail XC:

1. In the main menu, select XC > ST XC. The Manual Trail Management -
Create Server Trail XC window opens.
Figure 7-1: Manual Trail Management - Create Server Trail XC window - Create
XC tab
2. Set the service type by selecting either the Working or Protection radio
button.
3. Specify the direction by selecting the Bidirectional, Unidirectional, or
Broadcast radio button.
4. Select the needed timeslots in the Source Time Slot and Sink Time Slot
lists. If multiple timeslots are selected, the number of source and sink
timeslots should be the same. Source/sink timeslot selection should comply
with cross-connection principles.
5. Click Add XC to add the selected source/sink timeslots to the send list. If
the number of selected timeslots is inconsistent or the timeslot selection
does not comply with cross-connection principles, an error message is
displayed.

LCT-BGF User Manual Managing Cross Connections
6. Select the Send List tab. This window displays the configured cross
connections.
Figure 7-2: Manual Trail Management - Create Server Trail XC window - Send
List tab
7. Click Activate to send the cross connections to the equipment. Successfully

sent cross connections have an active status.
You can also delete configured cross connections by clicking Remove or
Remove All.

Maintaining Server Trail XCs

Server trail XC maintenance includes filtering, activating, deactivating, and
locally deleting server trail XCs.
To perform server trail XC maintenance:

1. In the main menu, select XC > ST XC. The Manual Trail Management -
2. In the Manual Trail Management - Create Server Trail window, click
XC List to display all server trail cross connections for this NE.
Figure 7-3: Manual Trail Management - Create Server Trail XC window - XC

List tab
3. Perform the required maintenance operation on the server trail cross

connection, as follows:
Filter
Filtering enables you to quickly locate a specific cross connection or
type of cross connection.
In the filter options, select the active status (active/inactive), XC status
(used by trail/discrete trail), protected/unprotected (working/protecting)
status, source card, and sink card. Then, click Filter. The XC list
displays cross connections complying with the filtering criteria.

Activate
Select one or more Inactive cross connections in the XC list and then
click Activate. If the operation succeeds, the cross connection is set up
on the NE side, and the XC status in the LCT-BGF changes from
Inactive to Active.
Deactivate
Select one or more Active cross connections in the XC list and then
click Deactivate. If the operation succeeds, the cross connection is
deleted from the NE side, and the XC status in the LCT-BGF changes
from Active to Inactive.
Activating a Server Trail XC

Activating a server trail sends its corresponding VC-4-level service to the
equipment and establishes a VC-4-level transmission trail over the network.
You can activate one or multiple server trails at one time. The Activate
operation can be performed for server trails with a Not Activated or Not
Activated Completely status. Activating a server trail with a Not Activated
Completely status sends the VC-4-level service not activated but included in it,
to the equipment.

To activate a server trail XC:

1. Select XC > ST XC in the main menu. The Manual Trail Management -
Figure 7-4: Manual Trail Management - Create Server Trail XC window
This window contains a toolbar, filtering area, and server trail list area.
2. Click XC List to list all the server trail cross connections for this NE.
3. Select the server trail(s) to be activated. Use the Shift key to select multiple
trails. The selected server trail is highlighted.
4. Activate a server trail using one of the following methods:
Click Activate
OR
Right-click a server trail and select Activate

When activation is performed, the system displays the XC Task Sent

window. If the server trail is successfully activated, its status changes from
Not Active to Active.
NOTE: In sending a task, click Stop to cancel the Send

operation. In this case, the XCs of some server trails may not
have been sent to the NE equipment. If none of the XCs of a
server trail are activated, the server trail remains Not Active.
If all the XCs of a server trail are activated, the server trail has
an Active status. If some XCs of a server trail are activated
and some are not, the server trail has a Not All Active status.
Deactivating a Server Trail XC

Deactivating a server trail deletes the VC-4-level service corresponding to the
server trail from the equipment, in order to delete the transmission trail in the
network.
One or multiple server trails can be deactivated simultaneously. The Deactivate
operation can only be performed on a server trail whose status is Active or Not
All Active. You cannot perform this action on server trails with an Inactive
status. Deactivating a server trail with a Not All Active status sends the
VC-4-level service in Active status to the equipment and deletes these XCs
from the equipment.
To deactivate a server trail XC:

1. Select XC > ST XC in the main menu. The Manual Trail Management -
2. Click XC List to display all server trail cross connections for this NE.
3. Select the server trail XCs to be deactivated. You can select one or more
server trail XCs. Use the Shift key to select multiple trail XCs. The selected
server trail XCs are highlighted.

4. Click Deactivate to deactivate the XCs. A warning message is displayed.
Figure 7-5: Deactivate a client trail confirmation window
When deactivating a server trail XC, the system displays the Task Status
Monitor window. If the server trail XC is successfully deactivated, its
status changes from Active to Inactive.
NOTE: Deactivating a server trail may affect the configured

client trail service passing through it. Therefore, use caution
when deactivating server trails.
Deleting a Server Trail XC

Deleting a server trail XC removes it in the LCT-BGF from a local database.
This action does not affect the actual service in the equipment. However,
deleting a server trail with an Active status may lead to an inconsistency
between the data in the LCT-BGF database and the NE. Because this action
affects the configured client trail service passing through it, the server trail
cannot be deleted if it has any client trails. Only those server trails with no
client trails can be deleted.
To delete a server trail XC:

1. Open the Manual Trail Management - Create Server Trail XC window
using one of the following methods:
Select Trail > ST XC in the main menu
OR
Click the ST XC button in the toolbar

2. Select the server trail to be deleted and click Delete. The following
confirmation message is displayed:
Figure 7-6: Confirmation message when deleting a server trail
3. Click OK to delete the trail.
NOTE: If the system detects a server trail carrying any client

trail service, it displays an error message informing you that
the trail cannot be deleted.
Filtering Server Trail XCs

If the user network is large, there will be a considerable number of trails in the
server trail list, which makes it difficult to view and locate a server trail. Server
trail filtering enables you to quickly find and locate a server trail.
To filter a server trail:

1. Open the Manual Trail Management - Create Server Trail XC window
using one of the following methods:
Select Trail > ST XC in the main menu
OR
Click the ST XC button in the toolbar
2. Set filtering options. Filtering options contain commonly used server trail
attributes, such as:
Activation status - Active, Inactive, Not All Active
Creation category of a client trail - generated by an optical fiber
connection and created manually
Alarm status - alarms, no alarms
Source/sink - source NE, source card, source VC-4, sink NE, sink card,
sink VC-4
3. Click Filter to display the filtering results.

Configuring and Managing Client

Trail XCs
A client trail is a transmission task of the optical transmission network.
Externally, it appears as the add/drop of electrical signals in the service
tributary. Within the NE, it is a series of cross connections.
Manually Creating Client Trail XCs

Creating a client trail XC manually configures cross connections in a single
NE. A client trail is complete only after all of its client trail XCs have been
configured.
To manually create a client trail XC:

1. Select XC > CT XC in the main menu. The Manual Trail Management -
Create Client Trail XC window opens.
Figure 7-7: Manual Trail Management - Create Client Trail XC window - Create
XC tab
2. Select a rate of VC-12, VC-3, or VC-4 in the Rate drop-down list.

3. Set the service type by selecting either the Working or Protection radio
button.

4. Specify the direction by selecting the Bidirectional, Unidirectional, or

Broadcast radio button.
5. Select the required timeslots in the Source Time Slot and Sink Time Slot
lists. If multiple timeslots are selected, the number of source/sink timeslots
should be the same. Source/sink timeslot selection should comply with
cross-connection principles.
6. Click Add XC to add the selected source/sink slots to the send list. If the
number of selected source/sink timeslots is inconsistent or the timeslot
selection does not comply with cross-connection principles, an error
message is displayed.
7. Select the Send List tab to display the configured cross connections.
Figure 7-8: Client Trail List window

8. Click Delete to remove configured cross connections.

sent cross connections have an active status.
NOTES: The service configuration restrictions described here

apply.
Except in the following cases, cross connections cannot exist

in the same card:
If there are multiple optical interfaces, the start and end

points of the cross connection cannot be at the same
optical interface.
For a self-loop, the timeslots at the same optical interface
should be the same.
For the BG-40 NE:
VC-12 of the tributary card can be cross connected to

VC-12 of the optical card.
The timeslot number of the VC-12 source (sink) of the
tributary card can be different from the timeslot number of
the VC-12 sink (source) of the optical card.
Only a through connection instead of a cross connection is
allowed between VC-12, VC-3, and VC-4 of the optical
card. This means the VC-12, VC-3, and VC-4 source
(sink) timeslot numbers of the optical card should be the
same as the sink (source) numbers the optical card.

Maintaining Client Trail XCs

Client trail XC maintenance includes filtering, activating, deactivating, and
deleting client trail XCs.
To perform maintenance on client trail XCs:

1. In the Manual Trail Management - Create Client Trail XC window,
click XC List to display all the client trail cross connections of this NE.
2. Perform maintenance operations on the circuit cross connection, as follows:

Filter
Filtering enables you to quickly locate a specific cross connection or a
type of cross connection.
In the filter options, select the active status (active/inactive), XC status
(used by trail/discrete trail), working/protection status, source card, and
sink card. Then, click Filter. The XC list displays cross connections
complying with the filtering criteria.

Activate
Select one or more inactive cross connections in the XC list and then
click Activate. If the operation succeeds, the cross connection is set up
on the NE side, and the XC status in the LCT-BGF changes from
Inactive to Active.
Deactivate
Select one or more active cross connections in the XC list and then
click Deactivate. If the operation succeeds, the cross connection is
deleted from the NE side, and the XC status in the LCT-BGF changes
from Active to Inactive.
Activating a Client Trail XC

Activating a client trail sends its corresponding XC service to the equipment, in
order to enable this client trail to be validated in the equipment and begin
transmitting signals.
One or multiple client trails can be activated simultaneously. The Activate
operation cannot be performed for a client trail with an Active status. Only
client trails with an Inactive or Not All Active status can be activated.
Activating a client trail with a Not All Active status sends the XCs in Inactive
status included in it to the equipment.

To activate a client trail XC:

1. Click XC > CT XC in the main menu. The Manual Trail Management -
2. Click XC List to list all the client trail cross connections of this NE.
3. Select a client trail XC to be activated.
4. Click a client trail XC in the client trail list or use the Shift key to select
multiple client trail XCs. Any selected client trail is highlighted.
5. Activate a client trail XC by clicking Activate.
When a client trail XC is successfully activated, it status changes from
Inactive to Active.
Deactivating a Client Trail XC

Deactivating a client trail deletes an XC corresponding to the client trail from
the equipment, in order to invalidate it on the equipment side and terminate its
transmission task.

One or multiple client trails can be deactivated at one time. The Deactivate
operation cannot be performed for client trails with a Not Active status. Only
client trails with an Active or Not All Active status can be deactivated.
Deactivating a client trail in Not All Active status sends the XCs included in it
to the equipment and deletes these XCs in the equipment.
To deactivate a client trail XC:

2. Click XC List to list all the client trail cross connections of this NE.
3. Select a client trail XC to be deactivated.
4. Click a client trail XC in the client trail XC list or use the Shift key to select
multiple client trail XCs. The selected client trail is highlighted.
5. Click Deactivate to deactivate the client trail XC. The following message
is displayed:
Figure 7-11: Deactivate a client trail confirmation window
When a client trail is successfully deactivated, it status changes from

Active to Inactive.
Deleting a Client Trail XC

Deleting a client trail XC deletes it in the LCT-BGF from a local database. This
does not affect any actual service in the equipment. Deleting a client trail XC in
Active status may lead to inconsistency between data in the LCT-BGF and the
NE.
To delete a client trail XC:

2. Click XC List to display all the client trail cross connections of this NE.

3. Select the client trail XC to be deleted.

4. Click Delete to delete the trail.
Filtering Client Trail XCs

If the network is large, there will be too many trails in the client trail list, which
makes it difficult to view and locate a client trail. Filtering enables you to
quickly find and locate a client trail.
To filter client trail XCs:

2. Click XC List to display all the client trail cross connections of this NE.
3. Set filtering options. Filtering options contain commonly used client trail
attributes, such as:
Service level - VC-12, VC-3, VC-4, and VCG
Activation status - Active, Inactive, Not All Active
Alarm status - alarms, no alarms
Direction - unidirectional, bidirectional
Source/sink - source NE, source card, sink NE, sink card
4. Click Filter to display the filtering results.
Setting Up MSP 1+1 XC

Protection
The LCT-BGF supports both unidirectional and bidirectional MSP Linear 1+1.
The supported topology is illustrated in the following figure.
Figure 7-12: MSP 1+1

To create a protection group:

1. Select Configuration > MSP Linear 1+1 > Create PG in the main menu.
The Create PG window opens.
Figure 7-13: Create PG window
2. Select an NE in the NE list.

3. Set the Protocol Mode by selecting the relevant Unidirectional or
Bidirectional radio button.
4. Select the Main and Protection MS modules.
5. Click Apply.

To view a protection group:

1. Select Configuration > MSP Linear 1+1 > PG List in the main menu.
The MSP Linear 1+1 PG List window opens.
Figure 7-14: MSP Linear 1+1 PG List window
2. Select an NE in the NE list.

3. Click Get to retrieve protection group details from the NE.
4. In the NE Shelf View window, check the MSP 1+1 configuration, as
illustrated in the following figure.
Figure 7-15: LCT Login BG-40 NE window

To perform operations on a protection group:

| In the MSP Linear 1+1 PG List window (on page 7-19), right-click a
protection group and select the operation you want to perform in the pop-
up menu.
Figure 7-16: MSP Linear 1+1 PG List window
The following operations for unidirectional MSP 1+1 can be performed

from this window:
Delete a protection group

Force switch to protection
Force switch to main
Manual switch to protection
Manual switch to main
Release
Configuring SNCP Attributes

The LCT-BGF supports SNCP I/N. The default is SNCP N.
The SNCP attribute enables you to select the working path service or the
protection path service, based on service quality and SNCP attributes. SNCP
attributes can be obtained and set as needed.
The current path specifies whether the current service of the double-receive
point is from the working or protection path.

If the Switching attribute is set as Force, the double-receive point adopts the
service of specified paths in Mandatory mode, instead of switching
automatically, regardless of the status of the service. If this attribute is set to
Automatic, the double-receive point automatically switches, based on the
quality of service.
The Restoration attribute for SNCP has a switching mode that can be set to
either Restoration or No Restoration. For the No Restoration switching mode,
as long as the standby path maintains smooth service, it is not switched to the
original operating path, even if the original operating path restores to normal.
If both paths are working properly, the working path is used. If the Switching
attribute is set to Force, the Restoration attribute becomes invalid. The
Restoration attribute is not validated until the Mandatory attribute is set to
Automatic.
To define SNCP attributes:

| Select XC > Protection Attributes per MO in the main menu. The SNCP
Figure 7-17: SNCP Attributes window
The NE Navigation Tree displays the double-receive point configured with

routes.
The following operations can be performed in this window:
Get - obtains the SNCP attribute of the selected double-receive point on

the NE side.
Apply - sends the SNCP attribute displayed in the list to the NE
equipment. When the SNCP attribute is successfully sent, it is saved to
the LCT-BGF database.

Exporting Trails as a File

Exporting trails as a file saves the trail current configuration information in a
data file that can be used later for engineering maintenance. Exporting trails to
a file saves server trails, client trails, and single NE XCs.
To export trails as a file:

1. Select XC > Export Trail as a File in the system main menu. The Export
XCs to File window opens.
Figure 7-18: Export XCs to File window
2. Select the relevant Rate, Active Status, and Main/Protection checkboxes

and then click Next.

3. Select the XCs to be exported and click Save. The Select File window
opens.
4. Enter the file name in the corresponding field and click Save.

Importing Trails from a File

Trail data can be imported to the LCT-BGF database. You can import trail files
for server trails, client trails, and NE XCs.
To import trails from a file:

1. Select XC > Import Trail from file in the main menu. The Import Trail
From File window opens.
Figure 7-20: Import Trail From File window
2. Open the trail file.

3. Import the trail file.
Figure 7-21: Import Trail From File window showing importing of a server trail
4. Select the trail to be imported in this page and click Save to DB to save the
trail to the LCT-BGF. The procedure for importing client trail NE XCs is
the same as that for server trails.
Uploading XCs
This operation uploads current XC data from the BG-40 NE. Use this operation
to check the data consistency between the trail information on the equipment
and the trail information in the LCT-BGF.

To upload an XC:
1. Click XC > XCs Upload in the main menu. The XCs Upload window
opens.
Figure 7-22: XCs Upload window - Upload XCs tab
2. Click Upload. If successful, the trail data uploaded from the equipment is
displayed in the list and the number of NE XCs and trail consistency
information is displayed at the bottom of the window.
3. Click Overwrite. The NE's trail data is deleted in the LCT-BGF and the
uploaded trail data is saved to the database.

4. Select the Compare Result tab.
Figure 7-23: XCs Upload window - Compare Result tab
If the compare results are consistent, the four Compare pages are null and
the operation button in this tab is grayed out. If results are inconsistent, one
of the following is displayed, depending on the type of inconsistency
found:
XC information available to the equipment, but unavailable to the

LCT-BGF - in this case, click Delete Remotely to delete these XCs
from the equipment or Save to DB to save them to the LCT-BGF. After
saving, these XCs become Active.
XC information available to the LCT-BGF, but unavailable to the
equipment - click Delete Locally to delete these XCs from a local
database in the LCT-BGF. Click Modify DB Inactive to modify these
XCs saved in the LCT-BGF and change their status from Active to
Inactive. Click Send XC to send these XCs to the NE equipment. These
XCs become Active after they are sent.
XC information available to the equipment, but inactivated on the
LCT-BGF - click Modify DB Active to change the status of these XCs
in the LCT-BGF from Inactive to Active.
XCs with inconsistent trail labels - click Delete Remotely to delete
these XCs from the equipment, or click Modify RouteID in DB to
modify XC trail labels so that they are consistent with that on the
equipment.


8
Configuring Timing Sources
In this chapter:
Overview ......................................................................................................... 8-1
Configuring Synchronous Timing ................................................................... 8-2
Configuring the Synchronous Timing Table ................................................... 8-3
Viewing the SEC Work Mode and External Clock References ...................... 8-5
Calibrating the Clock Card Frequency ............................................................ 8-6
Overview
Synchronous timing configuration enables an NE to automatically select and be
synchronized with the highest-quality clock source in the network, in order to
achieve clock synchronization for the entire network.
The following operations can be performed:
| Configure synchronous timing
| Obtain the clock working mode
| Calibrate the clock card frequency
| Calibrate the active/standby switching of the clock card
These operations can be performed by the system operator level.
The NE synchronous timing table is accessed through the main menu and the
right-click menu of the NE. The window lists all the clocks for external
references that can be selected. You manually select options and set priorities
for them to form a synchronous clock table, and then send it to the equipment.

Configuring Timing Sources LCT-BGF User Manual
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 open the Timing Configuration window - Timing
Maintenance tab (on page 8-5) from the main menu to view the current clock
working mode and clock reference of the NE.
Configuring Synchronous Timing

Use the following procedure to configure synchronous timing for the NE.
To configure synchronous timing:

1. Select the NE to be configured.
2. Select Configuration > Timing Management > Timing Configuration in
the main menu. The Timing Configuration window opens.
Figure 8-1: Timing configuration window - Timing Configuration tab
3. Select the corresponding external references for the clock and click Apply
to send the external clock references to the NE.

LCT-BGF User Manual Configuring Timing Sources
Configuring the Synchronous

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

| Select an NE in the topology view and then select Configuration > Timing
Management > Timing Configuration in the main menu. The Timing
configuration window opens.
Figure 8-2: Timing configuration window showing synchronous timing

configuration

The following buttons are available in this window:
Query - queries the LCT-BGF database about the synchronous timing

information saved for this NE. Retrieved data is displayed in the
window.
Get - obtains the synchronous timing information for this NE from the
NE equipment and displays it in the window.
Apply - sends the synchronous timing information to the NE equipment
and saves it to the LCT-BGF database.
The clock availability status indicates whether the clock reference is
currently available. This field is read-only and cannot be modified.
The following values can be configured in this window:
Clock type
The selected clocks are based on assigned priorities. Unselected clocks
are not used.
Channel
For the OMD1 card, you should select the optical port as the clock
source.
Priority
The higher the priority value, the higher the priority.
Override SSM
The S1 byte has two statuses: Automatic and Forced. Automatic status
obtains the S1 byte from the line automatically. Forced status sets the
S1 byte manually. 2 MHz tributaries, 2 Mbps tributaries, and
Synchronous Equipment Timing Sources (SETSs) can only work in
Forced status, while others can work in both statuses.
Quality
Quality values are:
PRC (G.811 clock)
SSU-T (G.812 transit office clock)
SSU-L (G.812 local office clock)
SEC (synchronous equipment timing source clock)
DNU (not used as synchronous clock)
UNK (synchronization quality unknown)

LCT-BGF User Manual Configuring Timing Sources
Viewing the SEC Work Mode and

External Clock References
You can determine the TMU work mode by querying the current clock working
mode and the clock reference of the NE. The clock working mode can be one
of the following:
| Capture mode
| Tracing mode
| Holding mode
| Free oscillation mode
To view the work mode and external references for the

clock:
1. Select an NE in the topology view and then select Configuration > Timing
Management > Timing Configuration in the main menu. The Timing
2. Select the Timing Maintenance tab.
Figure 8-3: Timing Configuration window - Timing Maintenance tab
This window displays the timing work mode and current external
references for the clock.

Calibrating the Clock Card

Frequency
This operation records the voltage of the clock source, when working normally
as the standard working voltage of the clock source.
When the clock source is working normally, select an NE in the topology view
and then select Configuration > Timing Management > Calibrate the
Frequency of SEC. A confirmation message is displayed indicating that the
SEC frequency has been successfully calibrated.

9
Managing Alarms
In this chapter:
Overview ......................................................................................................... 9-1
Managing Current Alarms ............................................................................... 9-2
Managing Historical Alarms ........................................................................... 9-8
Masking Alarms ............................................................................................ 9-11
Using the NE Alarm Log............................................................................... 9-13
Configuring Alarm Attributes ....................................................................... 9-16
Correcting Alarms ......................................................................................... 9-20
Managing External Alarms............................................................................ 9-20
Overview
The equipment enters the normal running and maintenance phase immediately
after service trail configuration is completed. Therefore, you can view various
equipment alarms and performance data through the LCT-BGF, in order to
monitor the running status of the equipment.
Alarm data provides comprehensive service fault information. Alarm
processing is the major maintenance task for SDH equipment.
Alarms include alarm generation, alarm clearance, and time interval
information.
An event indicates that the equipment generated a certain action or process
under some condition, but that the action or process itself does not influence
the traffic. The equipment reports this action or process to the LCT-BGF as an
event. The event reflects the running status of the equipment. The occurrence
of many events may result in the generation of alarms. Although the event itself
does not influence the running of the equipment, the hidden causes are likely to
trigger alarms.

Managing Alarms LCT-BGF User Manual
The display of the equipment alarm status needs no user intervention. The
LCT-BGF will update the colors of indicators on the NE layer, card layer, and
functional unit layer according to the reported alarms. The alarm source and
level are denoted by colored indicators at all three operation layers. The alarms
at each layer represent the highest level of all alarms for the layer and the
objects belonging to it.
The LCT-BGF also provides an audio alarm.
Managing Current Alarms

A current alarm identifies an existing abnormal event caused by a problem in
the equipment or the communication line. The Current Alarm View window
can display all current alarms, all alarms for a specific NE, or alarms for a
specific card.
Figure 9-1: Current Alarm View window
This window contains three tabs, as follows:

| Show Data - used to view and perform operations on the current alarm.
Double-click an alarm to display its details.
| Filter Option - used to filter current alarms.
| Alarm Chart - provides statistics for current alarm information, according
to the classification of alarm severities in the bar chart. Colored blocks in
the bar chart represent alarms of different severities.

LCT-BGF User Manual Managing Alarms
The following terms apply regarding current alarms:

| Current alarm - the alarm record is generated, but not cleared.
| Alarm acknowledge - acknowledges the reported alarm record with an
Unacknowledged status, and changes its alarm status to Acknowledged.
The time for the acknowledgement is the current time. Any alarm can only
be acknowledged once.
| Delete - deletes an alarm from the current alarm database in the LCT-BGF.
| Manual clearance - deletes an alarm from the current alarm database in the
LCT-BGF and saves it to the historical alarm database in the LCT-BGF.
| Alarm severity - alarms are categorized by severity into four levels: critical,
major, minor, and warning.
| Alarm type - five alarm types are available, including:
| Equipment alarms
| Communication alarms
| Service quality alarms
Processing error alarms
Environment alarms

To access the Current Alarm View window:

| Click CurrAlarm in the toolbar or Fault > Current in the main menu. The
Current Alarm View window opens.
Figure 9-2: Current Alarm View window - Show Data tab
To view current alarms for a specific card:

1. In the LCT-Login BG-40 NE (shelf view) window, select the card whose
alarms you want to view.
2. Select Fault > Current in the menu.
To view current alarms for a specific object:

1. Select the group channel card or tributary card to open an object window.
2. Select the object whose current alarm information you want to view.
3. Select Fault > Current in the menu of the object window.
To sort current alarms:

| In the Current Alarm View window, click the column heading in the
current alarm information list to sort the alarm information based on this
column.

To view detailed information for a current alarm:

| In the Current Alarm View window, select a single alarm in the current
alarm list and click Detailed Information to open the Current alarm
Detail Info window for this alarm.
To delete a current alarm:

| In the Current Alarm View window, select one or more alarms in the
current alarm list and click Delete. Click Delete All to delete all alarms.
To acknowledge a current alarm:

current alarm list and click Acknowledgement. To acknowledge all current
alarms, do not select an alarm and then click Acknowledge all.
To manually clear a current alarm:

current alarm list and click Clear Manually.
To save current alarm information to a file:

| In the Current Alarm View window, click Save As to save the queried
current alarm records as an HTML file. To view the file at a later time,
open it using a browser.

To filter current alarms:

1. In the Current Alarm View window, select the Filter Option tab to specify
filtering criteria.
Figure 9-3: Current Alarm View window - Filter Option tab
2. Specify the filtering conditions you want by selecting the corresponding

checkbox(es). You can filter by alarm object, alarm severity, alarm type,
and acknowledge status.
3. Click Filter.

To view a chart for current alarms:

| In the Current Alarm View window, select the Alarm Chart tab. A
histogram is displayed showing current alarm information by alarm
severity. Colored blocks in the histogram represent alarms of different
severities.
Figure 9-4: Current Alarm View window - Alarm Chart tab
NOTE: Acknowledging, deleting, and manually clearing

current alarms are NE Write operations. You must apply for
operation rights on this NE before performing these
operations.

Managing Historical Alarms

Historical alarms refer to alarm records automatically cleared after the
equipment returns to normal status. As with current alarms, historical alarms
are saved in the LCT-BGF database. Use the History Alarm View window to
easily obtain the status of historical alarms for an object.
Figure 9-5: History Alarm View window
This window contains three tabs, as follows:

| Show Data - used to view and perform operations on historical alarms.
| Filter Option - used to filter historical alarms.
| Alarm Chart - provides statistics for the current history information
according to the classification of alarm severities in the bar chart. Colored
blocks in the bar chart represent alarms of different severities.
Historical alarms can be filtered. You can display all historical alarms, all
alarms for a selected NE, alarms for a selected card, or alarms for a selected
functional block.

The following terms apply regarding historical alarms:

| Historical alarm - an alarm record automatically cleared because the
equipment returns to normal after the alarm is generated, and the current
alarm is manually cleared.
| Clearance mode - identifies the clearance mode for the historical alarm:
either manually cleared or automatically cleared. Manually cleared alarms
are manually cleared by a user. For automatically cleared alarms, the alarm
record is automatically cleared when a fault returns to normal after an
alarm has occurred. No user intervention is involved in the latter type.
To access the History Alarm View window:

| Click Alarm > History in the main menu. The History Alarm View
window opens.
Figure 9-6: History Alarm View window
To view historical alarms for a specific card:

1. Select the card whose alarm information you want to view.
2. Select Fault > History in the menu.

To view historical alarms for a specific object:

1. Select the group channel card or tributary card to open an object window.
2. Select the object whose alarm information you want to view.
3. Select Fault > History in the menu bar of the object window.
To sort historical alarms:

| In the History Alarm View window, click the column heading in the
historical alarm information list to sort the alarm information based on this
column.
To view detailed information for an historical alarm:

| In the History Alarm View window, select a single alarm in the alarm list
and click Details to open the History Alarm Detail Info window for this
alarm.
To delete an historical alarm:

| In the History Alarm View window, select one or more alarms in the
alarm list and click Delete. Click Delete All to delete all alarms.
NOTE: An historical alarm can only be deleted by a senior

operator or system administrator.
To save historical alarm information to a file:

| In the History Alarm View window, click Save As to save the queried
historical alarm records as an HTML file. To view the file at a later time,
open it using a browser.
To filter historical alarms:

1. In the History Alarm View window, select the Filter Option tab to specify
filtering criteria.
2. Specify the filtering conditions you want by selecting the corresponding
checkbox(es). You can filter by alarm object, alarm severity, alarm type,
acknowledge status, clearance mode, and generation time.
3. Click Filter.

To view a chart for historical alarms:

| In the History Alarm View window, select the Alarm Chart tab. A
histogram is displayed showing historical alarm information by alarm
severity. Colored blocks in the histogram represent alarms of different
severity.
Masking Alarms
In some cases, the alarms of some ports and functional blocks are irrelevant to
the service. In this case, alarms can be masked to avoid confusing them with
the alarms caused by actual faults. Alarms that are masked (shielded) are not
monitored and do not affect card and equipment alarm indications (namely, the
card-level alarm status and NE-level alarm status). No alarm data is reported or
recorded for shielded alarms.
Generally, the following cases use alarm masks:
| Many service routes are open but you are only currently using part of them.
Unused service ports will send LOS alarms. In this case, you can mask the
alarms of the service ports not used, but configured with routes. Unmask
the alarms when necessary to use these service ports.
| For some ADM NEs, fiber connections at both optical interfaces are
planned. However, in actual engineering, one of the following may apply:
The fiber in one direction is not laid as planned, and only fibers at one
optical interface can be provided.
A protection network is planned, but the actual network has no
protection due to lack of fiber resources.
In these cases, the fibers at some optical interfaces need to be removed
because the signals at some optical interfaces are lost. In such situations,
the alarms at the unused optical interface can be masked.
In the LCT-BGF, alarms can be masked for the optical interface, electrical
interface, and SDH functional block. Generally, to mask optical interface
alarms, all SPI, RS, MS, AU-4, and VC-4 alarms are masked. To mask
electrical interface alarms, all VC and PPI alarms are masked.
When the alarms of a certain object are masked, the alarms related to this
object in the current alarm database are cleared. After the alarm mask is
released, the equipment reports the current alarm. Therefore, the NE equipment
for which the alarms have been masked should have no alarm indication.

To mask (shield) an alarm:

1. Select Fault > Mask in the main menu. The Alarm Source Mask
Figure 9-7: Alarm Source Mask Configuration window
2. To view alarm mask information for a managed object, select one or more
managed objects belonging to the same card in the NE tree and click
Query. The alarm mask information is displayed in the Data Display area
of the window. Operation results are displayed at the bottom of the
window.
3. To retrieve alarm mask information for an object, select one or more
objects belonging to the same card in the NE and click Get. Alarm mask
information is displayed in the Data Display area of the window. Operation
results are displayed at the bottom of the window.
4. Modify alarm mask parameters, as required.
Click Apply to send the settings information to the NE equipment.
Operation results are displayed at the bottom of the window.

Using the NE Alarm Log

The NE alarm log records the alarm and event information saved in the NE
equipment. You can view the NE alarm log to access this alarm and event
information. If an NE is disconnected during a certain period, all its alarms and
events generated during this period are recorded in the log.
Figure 9-8: Alarm Log window
A Query operation enables you to retrieve and process alarm logs on NE

equipment. This operation supports the following functions:
| Gets an event that failed to be reported due to unsuccessful communication,
such as active/standby changeover, multiplex section switching, reset, and
other important events.
| Provides the LCT-BGF with alarm history data that is missing due to
unsuccessful communication. History data for an alarm not reported
automatically must be obtained using an alarm query.
| In theory, continuous alarm querying ensures consistency of alarm data
between the LCT-BGF and the NE, as long as alarm logs do not overflow.
The following terms are relevant for NE alarm log queries:
| NE alarm log - the flow record table that records alarm events generated in
an NE and other events.
| NE alarm log query - queries the alarm log saved in the NE and displayed
in the LCT-BGF.
| Get - obtains alarm log records saved in an NE from the NE equipment.

| Clear NE - deletes all alarm log records saved in the NE equipment.

| Refresh - classifies the obtained records according to current alarm,
historical alarm, and event, and compares them with those saved in the
LCT-BGF. This action refreshes the LCT-BGF data to ensure its
consistency with the NE equipment.
To access the Alarm Log window:

| Select Fault > Alarm Log in the main menu. The Alarm Log window
opens.
Figure 9-9: Alarm Log window
To retrieve NE alarm log records:

| In the Alarm Log window, select an NE in the NE tree and click Get.
Retrieved alarm records are displayed in the Data Display area on the right
side of the window. Operation results are displayed in the Results area at
the bottom of the window. To the left of the Get button is a clearance
selection box. When this checkbox is selected and you perform a Get
operation, the alarm log records saved on the NE equipment are
automatically deleted.
To clear NE alarm records:

| In the Alarm Log window, select an NE in the NE tree and click Empty
NE. You must first obtain NE operation rights before you can perform this
operation.

The following operations relate to retrieved alarm log records:
Delete
Save
Open
Refresh
To delete alarm records:

| In the Alarm Log window, select a record in the Data Display area and
click Delete to delete the selected record.
To save alarm records:

1. In the Alarm Log window, select a record in the Data Display area.
2. Click Save. The selected record is saved as a file.
To open an alarm log file:

1. In the Alarm Log window, click Open. The Please select the file window
opens.
2. Select the file to open. Obtained alarm log records are displayed in the Data
Display area of the Alarm Log window.
NOTE: The records opened from a file cannot be refreshed.
To refresh alarm records:

| In the Alarm Log window, click Refresh. The records in the Data Display
area of the window are processed successively. Processing results are
displayed in the Results area of the window.
NOTE: You must obtain operation rights for this NE before

you can perform this operation.

Configuring Alarm Attributes

An alarm attribute table is used to record basic NE alarm information,
including all alarm causes. You can set the Alarm Severity and Autoreport
attributes for each alarm cause.
Alarm severity categories are: critical, major, minor, warning, and shielding. If
the severity of an alarm is set as shielding, the NE equipment cannot collect or
report this alarm.
When an alarm is set as Autoreport but is not shielded, the NE immediately
reports it to the LCT-BGF when the alarm is generated or cleared. Alarms set
as Nonautoreport are not reported to the LCT-BGF, but are recorded in the NE.
Alarms set as Nonautoreport can only be manually retrieved by the LCT-BGF.
The default setting for the Autoreport attribute is Autoreport.
To set alarm attributes:

1. Select Fault > Severity in the main menu. The Severity window opens.
Figure 9-10: Severity window - Alarm Attributes Table tab
2. Select the Alarm Attributes Table tab.

3. To view alarm attribute table information for an NE, select an NE in the NE
tree and click Query. Alarm attribute table information is displayed in the
Data Display area on the right side of the window. Operation results are
displayed in the Results area at the bottom of the window.

4. To retrieve alarm attribute table information for an NE from the NE

equipment, select an NE in the NE tree and click Get. The alarm attribute
table information is displayed in the Data Display area of the window.
Operation results are displayed in the Results area at the bottom of the
window.
5. Set alarm table attributes as needed by selecting the relevant Alarm
Severity radio button and Auto Report checkbox for each alarm cause.
6. Click Apply to send the settings information to the NE equipment. If
successful, the Save operation automatically executes. Operation results are
displayed in the Results area at the bottom of the window.
Setting the Alarm Preset Switch

The Alarm Preset function processes alarms generated by ports that have not
been loaded with traffic. When using this function, the alarm status is not
reported for ports not loaded with traffic. After ports are loaded with traffic, the
port automatically returns to the normal alarm reporting status.
To set the alarm preset switch:

2. Select the Alarm Miscellaneous Configuration tab.
Figure 9-11: Severity window - Alarm Miscellaneous Configuration tab
3. Select an NE in the window.

4. Click Query to obtain the information from the database. The alarm switch
configuration for the selected NE is displayed in the Alarm Switch area of
the window.
5. Click Get to obtain information from the NEs. The alarm switch
configuration for the selected NEs is displayed in the window.
6. Set the Alarm Switch as Close or Open by selecting the relevant radio
button.
7. Click Apply to send the settings information to the NE equipment.
Configuring Alarm Log Settings

Alarm log settings specify the working mode of logs on the NE equipment, and
include the log length setting and the log working status and processing mode
after a log is full.
The following terms relate to alarm log settings:
| The NE alarm log is a flow record table of alarm events and other events
generated in an NE.
| The alarm log length defines the maximum number of records that can be
stored in a log on the NE equipment (valid value range: 0 to 1,000). The
default is 1,000.
| The log working mode specifies whether the log is currently in use or has
been stopped. It has two modes: Working and Stopped. Working mode
means the alarm log keeps collecting events. Stopped mode means the
alarm log is no longer in use. The default setting is Working.
| When a log is full, it has two processing modes: Overwrite and Stop. In
Overwrite mode, new records replace the oldest records when the log is
full. In Stop mode, the alarm log stops collecting events when the log is
full. The default setting is Overwrite.
To specify alarm log settings:

1. Select Fault Management > Severity in the main menu. The Severity
window opens.
3. To view alarm log setting information, select one or more NEs in the NE
tree or select the All NEs checkbox.

4. Click Query. Alarm log setting information for the selected NE is

displayed in the Data Display area on the right side of the window.
5. To retrieve alarm log settings from the NE equipment, select one or more
NEs in the NE tree or select the All NEs checkbox.
6. Click Get. Alarm log setting information for the selected NE is displayed in
the Data Display area on the right side of the window. Operation results are
displayed at the bottom of the window.
7. Set alarm log settings by modifying the Log Counts, Log On/Off, and
Disposal When Log is Full values, as needed.
8. Click Apply to send the settings information to the NE equipment. If
successful, the Save operation automatically executes. Operation results are
displayed at the bottom of the window.
9. Click Default to display default configuration information for the NE log
setting.
Configuring the Alarm Hold-off Setting

To prevent alarm generation and clearance from being incorrectly reported and
to suppress excessively frequent alarm generation and clearance, you can set
the hold-off time for alarm generation and clearance. An alarms status change
is not validated until the hold-off time has elapsed. The hold-off time is defined
by the alarm generation hold-off period and the alarm clearance hold-off
period.
For the alarm generation hold-off period, an alarm event is not reported and the
current alarm status not updated until a generated alarm is detected and its
alarm status lasts three to 30 seconds. The default is three seconds.
For the alarm clearance hold-off period, any alarm clearance detected is not
considered as cleared unless the clearance status lasts three to 30 seconds. The
default is three seconds.
To set the alarm hold-off period:

3. To view alarm hold-off settings, select one or more NEs in the NE tree or
select the All NEs checkbox.
4. Click the Query button. Alarm hold-off setting information is displayed in
the Alarm Hold Off Time area of the window.

5. To retrieve alarm hold-off time settings from the NE equipment, select one
or more NEs in the NE tree or select the All NEs checkbox.
6. Click Get. If successful, alarm hold-off setting information is displayed in
the Alarm Hold Off Time area of the window.
7. Modify alarm hold-off settings, as required.
8. Click Apply to send settings information to the NE equipment.
Correcting Alarms
If LCT-BGF alarms and equipment alarms cannot be acknowledged as
consistent, alarm correction can be used to ensure consistency between them.
This operation refreshes the current alarm on the LCT-BGF side, based on the
current alarm on the equipment side.
Alarm correction is not affected by the Autoreport attribute.
Two types of alarm correction are available:
| NE alarm correction
| Card alarm correction
To correct an alarm on the NE:

| Select Fault > Correct in the main menu or click Correct Alarm in the
toolbar to correct an alarm on the NE.
To correct an alarm on a card:

| In the LCT-Login BG-40 NE (shelf view) window, select a card and then
select Fault > Correct in the menu or click Correct Alarm in the toolbar.
Managing External Alarms

The external alarm interface provides an input/output external alarm. An
external alarm interface is used to input external alarms, such as an ambient
temperature alarm, smog alarm, door warning, and so on. It can also be used to
input an alarm from other equipment, such as PCM equipment, so that the
LCT-BGF can manage and indicate various external alarms.

The external alarm interface, as a universal TTL-level input interface, can be

defined as required by any user. The output interface can be used to output the
control volume (for example, the control relay switch) and to provide alarm
output to an external piece of equipment.
The BG-40 input/output interface consists of four input interfaces and four
output interfaces.
To manage external alarms:

1. In the LCT-Login BG-40 NE (shelf view) window, select Fault >
External Alarm. The External Alarm window opens.
Figure 9-12: External Alarm window
The left side of this window shows the NE tree. The right side contains port
information, and consists of two tabs: Input Port and Output Port.
The Input Port tab displays the configuration for the four input ports of the
NE. You can assign a name to the port in the Name field and specify the
upper TTL level representing the alarm status or normal status in the
Contacts Status field.
The Output Port tab displays configuration for the three output ports. These
ports are: major alarm, minor alarm, and audio alarm. You can set the
alarm output switch as on or off.

2. Click Query to obtain port information from the LCT-BGF database.

3. Click Get to retrieve port information from the equipment.
4. Click Apply to send the configuration data to the equipment and save it in
the database.

10
Monitoring Performance
In this chapter:
Overview ....................................................................................................... 10-1
Viewing Current Performance....................................................................... 10-5
Viewing Recent Performance ........................................................................ 10-7
Setting Performance Thresholds.................................................................... 10-8
Using the Performance Monitoring Switch Operation ................................ 10-10
Resetting Performance Counters ................................................................. 10-13
Overview
Performance data reflects the network running quality. The LCT-BGF monitors
the bit errors for each section, the SDH layers, and the path.
Performance data can be viewed for different monitored objects, as follows:
| RS - reflects a B1 error and an RS failure
| MS - reflects a B2 error and an MS failure
| VC-4 - reflects a B3 error and a high-order path failure
| VC-12 - reflects a V5 error and a low-order path failure
| VC-3 - reflects a B3 error and a VC-3 path failure
| Ethernet over SDH (EOS) - reflects GFP errors, and the number of sent
packets and errored packages
| Port - reflects Ethernet MAC layer statistics, including the number of
received frames of varying length and type, and their error packets

Monitoring Performance LCT-BGF User Manual
The types of performance data that can be monitored are:

| BBE - background block errors. If there are errors in a frame of data, this
frame is counted as a block error. The background block error is the block
error with the number of severely errored seconds deducted from the
counting interval.
| ES - errored seconds. If errors occur within a certain second, this second is
called an errored second.
| SES - severely errored seconds. If there are errors in 30% of the frames, the
errors exceed the threshold, or the signal fails within a certain second, this
second is called a severely errored second. Errored seconds (ES) are not
counted when severely errored seconds occur.
| UAS - unavailable seconds. When an SES lasts for 10 seconds, it becomes
a UAS. When there are no severely errored seconds within 10 seconds, it is
no longer counted as a UAS. The UAS is not calculated in SES
calculations.
| FEES - far-end errored seconds.
| FESES - far-end severely errored seconds.
| FEBBE - far-end background block errors.
| FEUAS - far-end unavailable seconds.
| OFS - out-of-frame seconds.
| PPJC - positive pointer justification events.
| NPJC - negative pointer justification events.
The Port object of an FE_L12 card has the following performance data types:
| rx64LengthPackets - packet count of RX 0-64 bytes
| tx64kLengthPackets - packet count of TX 0-64 bytes
| tx127LengthPackets - packet count of TX 65-127 bytes

LCT-BGF User Manual Monitoring Performance

| RevSinglePackets - packet count of unicast received packets
| RevMultiPackets - packet count of multicast received packets
| RevBroadcastPackets - packet count of broadcast received packets
| SendSinglePackets - packet count of unicast sent packets
| SendMultiPackets - packet count of multicast sent packets
| SendBroadcastPackets - packet count of broadcast sent packets
| RevPauseFrames - frame count of Pause received frames
| SendPauseFrames - frame count of Pause sent frames
| RevGoodPacketBytes - byte count of received good packets
| SendGoodPacketBytes - byte count of sent good packets
| RevBadPacketBytes - byte count of received bad packets
| SendBadPacketBytes - byte count of sent bad packets
| CollisionErrors - count of collisions and errors
| DiscardPacketTimes - check count of monitor discard data packets
| CheckErrors - check error count
| SingleCollisionFrames - count of frames sent correctly after one collision
| MultiCollisionFrames - count of frames sent correctly after multiple
collisions
| SendTotalBytes - total byte count of the send path
| RecvTotalBytes - total byte count of the receive path
The EOS objects of FE_L12 cards have the following performance data types:
| RxTotalPayloadOct - RX total GFP frame payload octets
| RxTotalPayload - RX total GFP frame payloads
| RxCIDMismatch - RX CID mismatch

| rxEX1Mismatch - RX GFP EXI field mismatch

| rxPayloadMaxLen - RX GFP Payload Information field maximum length
violation
| rxClientFrame - RX GFP client management frame
| rxPT1Mismatch - RX GFP PTI field mismatch
| rxUP1Mismatch - RX GFP UPI field mismatch
| singleBitErrFrames - single bit-error frames (cHEC+tHEC+eHEC)
| multiBitErrFrames - multiple bit-error frames (cHEC+tHEC+eHEC)
| txTotalPayloads - TX total GFP frame payloads
| totalFrameBytes - TX total GFP frame bytes
Performance data divided according into the following monitoring periods:
| 15-minute performance data - equipment performance data is measured
in 15-minutes intervals. At the end of each 15 minutes, the value of the
15-minute performance data counter is reported to the LCT-BGF. At the
same time, the performance data counter is reset and another round of
15-minute performance statistics starts to accumulate.
| 24-hour performance data - equipment performance data is measured in
24-hour intervals. At the end of each 24 hours, the value of the 24-hour
performance data counter is reported to the LCT-BGF. At the same time,
the counter is reset and another round of 24-hour performance statistics
starts to accumulate.
| Instant performance data - current values of the 15-minute or 24-hour
performance data counters.
Analyzing Performance Data

Through the analysis of historical performance data in the LCT-BGF, the errors
at each SDH section/layer can be conveniently checked. If there are errors in
the RS, MS, and VC-4, the typical cause is poor aggregate (card) performance.
Possible causes are:
| Low laser power
| High laser power
| Excessive input jitter caused by a poor contact on the optical interface or a
relay-less distance of the fiber that is too long

Performance data can be used as an analytical tool, as follows:

| By examining the 15-minute performance data for a given day, you can
analyze the equipment performance for that day.
| By examining the 24-hour performance for a month, you can analyze the
equipment running status for that month.
By examining the 24-hour performance for a year or several years, you can
analyze the long-term running of the equipment. The LCT-BGF provides a
performance curve diagram, which visually shows equipment performance
changes during a specific period. This mechanism provides a convenient way
to analyze the communication link quality over time.
Performance-related Operations
LCT-BGF performance functions provide instant monitoring of and regular
statistics for the error codes of various SDH section layers and paths. Such data
is essential to ensure optimal network performance.
The following performance-related operations can be performed:
| Get current performance
| Set the performance threshold
| Set the performance monitoring task
| Reset performance counters
| Reset card performance counters
Viewing Current Performance

Current performance data refers to the present value of the current 15-minute or
24-hour performance data counter.
After you set the refresh interval and click Start Refresh, current performance
data is retrieved based on the specified monitoring cycle interval (15-minute or
24-hour).
Click Stop Refresh to cancel the refresh operation.

To view current performance data:

1. Select Performance > Current in the main menu. The Get Current
Performance window opens.
Figure 10-1: Get Current Performance window
Before performing operations in this window, you must first select the
object whose performance data you want to view in the window's
navigation tree, as well as select the relevant Performance Type radio
button (15-minute or 24-hour).
2. Click Get to retrieve current performance parameters from the NE

equipment.
3. Set the Refresh Interval.
4. Click Start Refresh to dynamically observe any performance data changes.
Data is refreshed, based on the Refresh Interval you specify.
5. Click Stop Refresh to cancel the refresh operation.
NOTE: Embedded software on the card gathers no

performance statistics for VC-12 objects not configured with
any trail. Therefore, the corresponding current performance
cannot be viewed in the LCT-BGF.

Viewing Recent Performance

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

1. Select Performance > Recent Performance in the main menu. The
Recent Performance window opens.
Figure 10-2: Recent Performance window
2. Select an object in the tree.

3. Select the relevant Performance Type radio button.
4. Click Get to obtain and display the performance parameter values stored in
the recent performance registers of the NE equipment.

Setting Performance Thresholds

A performance threshold is the allowable upper limit for performance data
when a system works normally. When a performance indicator crosses a
threshold, the system generates a corresponding event report. The
Performance Threshold window enables you to obtain and set the
performance threshold parameters of a network. Monitored performance
indicators are BBE, ES, SES, UAS, FEES, FESES, FEBBE, FEUAS, OFS,
PPJC, and NPJC.
The Performance Data Type can be specified as either a 15-minute or 24-hour
period. See the following table for performance threshold value ranges.
Table 10-1: Performance threshold value ranges
Performance data Value

BBE (15-minute) MS and RS: 1 to 16777215
Low-order and high-order: 1 to 65535
ES (15-minute) 1 to 900
SES (15-minute) 1 to 900
UAS (15-minute) 1 to 900
FEBBE (15-minute) MS: 1 to 16777215
Low-order and high-order: 1 to 65535
FEES (15-minute) 1 to 900
FESES (15-minute) 1 to 900
OFS (15-minute) 1 to 900
NPJC (15-minute) Any value
PPJC (15-minute) Any value
PSC (15-minute) 1 to 65535
BBE (24-hour) 1 to 65535
ES (24-hour) 1 to 65535
SES (24-hour) 1 to 65535
UAS (24-hour) 1 to 65535
FEBBE (24-hour) 1 to 65535
FEES (24-hour) 1 to 65535
FESES (24-hour) 1 to 65535
OFS (24-hour) 1 to 65535
NPJC (24-hour) Any value
PPJC (24-hour) Any value

To set performance thresholds:

1. Select Performance > Threshold in the main menu. The Performance
Threshold window opens.
Figure 10-3: Performance Threshold window
Before you can perform operations in this window, you must first select an
object in the NE tree and then select the relevant Performance Type radio
button.
2. Click Query to display the performance threshold value obtained from the
LCT-BGF database.
3. Click Get to display the performance threshold value obtained from an NE.
4. Click Apply to send performance threshold values to the NE, and save
them to the LCT-BGF database.
5. To set the Laser Threshold, select Performance > Threshold > Laser
Threshold in the main menu.
6. To set the SD/Exc Threshold, select Performance > Threshold > SD and
Exc Threshold in the main menu.

Using the Performance

Monitoring Switch Operation
This operation enables you to monitor the performance of an NE by setting a
main switch for NE performance monitoring, and setting the start time and end
time for monitoring. The performance object monitoring switch determines
whether to monitor the performance of a specific functional block in an NE.
The autoreport switch determines whether to allow historical performance data
for a specific functional block in an NE to be automatically reported to the
LCT-BGF.
The following terms relate to the Performance Monitoring Switch operation:
| Main switch for NE performance monitoring - determines whether to
monitor the performance of an NE. When the NE performance monitoring
switch is disabled, statistics collection on and monitoring of all
performance objects in an NE are terminated. In this case, the LCT-BGF
cannot obtain any current performance counters, and the NE does not
automatically report any historical performance data. When enabled, the
NE performance-monitoring switch monitors the performance of an NE
between the start time and the end time.
| Performance object monitoring switch - determines whether to monitor the
performance of a specific functional block in an NE. If the
performance-monitoring switch of a functional block is disabled, it
terminates statistics collection on and monitoring of all performance
objects within this functional block.
| Autoreport switch - determines whether to automatically report to the
LCT-BGF historical performance data for a specific functional block
within an NE. If the autoreport switch is enabled, historical performance
data of a functional block in an NE is automatically reported to the
LCT-BGF. When disabled, performance statistics collection and
monitoring are implemented within an NE, but there is no reporting.
Therefore, current performance counter values can still be obtained.
| Specific functional block - includes RS, MS, VC-4, VC-3, and VC-12.

To set the performance monitoring switch:

1. Select Performance > Performance Configuration in the main menu.
The Performance Configuration window opens.
Figure 10-4: Performance Configuration window - Collecting Schedule tab

Figure 10-5: Performance Configuration window - Object Attribute tab
This window consists of two tabs: the Collecting Schedule tab, which is
used to set an NE's monitoring switch parameters, and the Object Attribute
tab, which is used to set the performance object monitoring switch
parameters.
2. To modify object monitoring switch parameters, select the Object Attribute

tab.
3. Select an object in the tree.
4. Click Query to display the data for this object, as reflected in the database.
5. Click Get to obtain object data from the NE equipment. Operation results
are displayed at the bottom of the window.
6. Modify object parameters as required.
7. Click Apply to send settings to a piece of equipment, and save them to the
LCT-BGF database. Operation results are displayed at the bottom of the
window.
8. To set monitoring switch parameters for an NE, select the Collecting
Schedule tab.
9. Repeat steps 4 through 8.

Resetting Performance Counters

Use this operation to manually clear (reset) the near-term or current
performance registers on an NE or object. This operation should not be used
until system debugging is in service or the faulty equipment has been restored.
To reset performance counters:

1. Do one of the following:
Select an NE in the topology and then select Performance >
Performance Counter Reset in the main menu
OR
Select Performance > Performance Counter Reset in the menu of an
opened object window
A confirmation message is displayed before the reset is performed.
2. Click OK to perform the operation.


11
Managing LCT-BGF Security
In this chapter:
Overview ....................................................................................................... 11-1
Configuring the LCT Work Mode................................................................. 11-2
Overview
Only one EMS-BGF and one LCT-BGF are allowed to log in to the same NE
simultaneously. Both the EMS-BGF and the LCT-BGF can be in Master mode
to configure the NE.
When the LCT-BGF applies for Master mode, the embedded software on the
NE checks the LCT configuration of the EMS-BGF, as follows:
| If the EMS-BGF is not managing the NE, the LCT-BGF switches to Master
mode successfully.
| If the EMS-BGF is logged into the NE and the LCT-BGF configuration of
the EMS-BGF is approved, the LCT-BGF switches to Master mode
successfully.
the EMS-BGF is not approved, the LCT-BGF does not switch to Master
mode, but remains in the Monitor mode.
the EMS-BGF is waiting for approval, the LCT-BGF embedded software
on the NE sends an Apply Master notification to the EMS-BGF. If the
EMS-BGF returns approval, the LCT-BGF switches to Master mode. If the
EMS-BGF returns no approval, the LCT-BGF remains in Monitor mode.

Managing LCT-BGF Security LCT-BGF User Manual
Configuring the LCT Work Mode

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

| In the main menu, select Security > LCT Work Mode to display the LCT
work modes:
Monitor mode (offline)
Master mode (online)
An Information window opens showing the current LCT work mode.
Figure 11-1: Information window showing LCT work mode

LCT-BGF User Manual Managing LCT-BGF Security
To set the LCT-BGF work mode as Master:

| In the main menu, select Security > Request Login as Master to set the
LCT-BGF connection status in Master mode.
Figure 11-2: Task window for setting the LCT work mode as master
To set the LCT-BGF work mode as Monitor:

| In the main menu, select Security > Request Login as Monitor to set the
LCT-BGF connection status in Monitor mode.
Figure 11-3: Information window for setting the LCT work mode as monitor

Managing LCT-BGF Security LCT-BGF User Manual

12
Performing Maintenance
Operations
In this chapter:
Using the Maintenance List ........................................................................... 12-1
Performing Loopback Operations.................................................................. 12-2
Performing AIS/PRBS/RDI Operations ........................................................ 12-5
Saving NE Configuration Data...................................................................... 12-9
Clearing the NE Configuration...................................................................... 12-9
Downloading NE Database Files................................................................. 12-10
Performing a Software Upgrade .................................................................. 12-11
Performing Activation Time/Version Activate Operations ......................... 12-13
Performing Other Maintenance Operations................................................. 12-17
Using the Maintenance List

The maintenance list enables you to access, perform, and release system
maintenance operations.

Performing Maintenance Operations LCT-BGF User Manual
To access the maintenance list:

1. Select Maintenance > Maintenance List in the main menu. The
Maintenance List window opens.
Figure 12-1: Maintenance List window
2. To perform maintenance on a specific NE, select an NE in the NE list. The

maintenance operations of the selected NE are listed in the display area.
3. Filter the maintenance list by selecting Maintenance Type or Card in the
respective drop-down lists.
4. Click Release All to release all the maintenance operations on the selected
NE.
Performing Loopback Operations

The loopback operation is designed to aid in testing the service path and service
interface. In this context, loopback refers to a software loopback, meaning that
it is set through the LCT-BGF.
After an end-to-end trail has been configured, a loopback can be used to test
whether the whole path works normally and whether meters receive and send
consistently. If there is no error code, it means that everything is working
normally.

LCT-BGF User Manual Performing Maintenance Operations
The loopback operation includes:

| Terminal (NE) loopback - looping back signals from the cross-connect unit
back to the same cross-connect unit. The terminal loopback operation can
be used to test the flow of signals in the system.
| Facility (FE) loopback - directly looping back signals received by the
physical port to the output port corresponding to it, without changing the
signal structure. The facility loopback operation can be used to test the
connector.
Figure 12-2: Loopback example
To define loopback settings:

1. Select Maintenance > System > Loopback Attribute in the main menu.
The Loopback Setup window opens.
Figure 12-3: Loopback Setup window

2. In the NE tree, select the card that needs a loopback and click Query to
query the LCT-BGF database the about the loopback status of the timeslots
belonging to this card. Operation results are displayed at the bottom of the
window.
If a timeslot in the NE tree is in loopback status (near-end loopback or
far-end loopback), its card and NE node display the icon. Otherwise,
they display the icon.
3. Click Get to obtain from the NE side, the loopback status of the timeslots
belonging to this card. Operation results are displayed at the bottom of the
window.
4. Modify loopback parameters as required.
5. Click Apply to send the loopback configuration to the NE, and then to the
LCT-BGF database. If successful, operation results are displayed at the
bottom of the window.
NOTES: A VC-4 terminal loopback for a 155 Mbps optical

card will lead to the invalidation of this optical interface
DCC. Therefore, take great care when performing this
operation. An NE should not fail to be connected due to a
VC-4 terminal loopback. In a ring network, it is acceptable to
perform this operation, as long as no two NEs employ a
terminal loopback at the same time.
Generally, an NE optical interface in a chain and tree

topology employs no terminal loopback. However, a remote
optical interface may employ a terminal loopback. In this
context, terminal and remote indicate the direction of the NE
optical interface, relative to a gateway.
VC-12 and VC-4 loopback functions can be used to analyze

any service fault by troubleshooting segment by segment.

Performing AIS/PRBS/RDI
Operations
The AIS/PRBS/RDI operations obtain the EoS bit error statistics of the VC-12
bit errors for the ME1_8 card, and the VC-3 and VC-12 bit errors for the
P345_3 and ME1_8 cards by inserting different sequences of pseudo-random
codes, in order to judge the path quality of service (QoS).
Figure 12-4: Insert PRBS

To perform an Insert PRBS operation:

1. In the NE Shelf View window, open the required card and select VC-4 or
PPI, and then select Maintenance > PRBS Insert and Monitor in the
menu. The PRBS Insert and Monitor window opens.
Figure 12-5: PRBS Insert and Monitor window
NOTE: The Insert PRBS operation is supported for the

following cards:
P345_3
ME1_21/42
M345_2
SAM1/4

2. In the Insert area, select the Add or Drop radio button in the Direction field.
3. Set the Insert value to On.
4. Specify the Insert Pattern.
5. Set the Inverted field value.
6. Click Apply to insert the PRBS.
7. Click Add Single Bit Error to insert an additional error bit.
To perform a Monitor PRBS operation:

1. Access the PRBS Insert and Monitor window.
2. In the Monitor area, select the Add or Drop radio button in the Direction
field.
3. Click Get to retrieve the current status.
4. Click Start to begin monitoring PRBS. The error code is added to the
Counter.
5. Click Refresh to refresh the Counter value.
6. Click Stop to end PRBS monitoring.
To perform a Force Insert AIS/RDI test:

1. In the NE Shelf View window, open the card and select the
VC-4/VC-3/VC-12 module under all optical interface cards and service
cards. Then, select Maintenance > Force AIS/RDI in the main menu. The
Force AIS/RDI window opens.
Figure 12-6: Force AIS/RDI window

2. In the Downstream area, select the operation to be performed by selecting

either the None or AIS radio button.
3. Click Apply to insert the AIS/RDI.
4. Click Query or Get to obtain the settings from the database or the NE,
respectively.
NOTES:
For the ME1_8 card:
PRBS only supports source insertion, for which only one

pseudo-random code pattern is available: 2^15-1. During
saving and delivery, only a source can be selected
(controlled by the EMS-BGF).
Only one operation in source AIS insertion, sink AIS
insertion, and PRBS insertion is allowed (pairwise
exclusive).
None means to clear all AIS and PRBS operations. In this
case, there is no distinction between source and sink.
During saving and delivery, no source or sink can be
selected (controlled by the EMS-BGF).
For other cards:
Source AIS insertion and sink AIS insertion are

independent. Modification of the source (sink) AIS
Insertion attribute has no impact on the sink (source).
For all cards:
If the source and sink are set as AIS insertion, all buttons
on the EC Monitor and Get EC tabs are disabled.
If there is no AIS insertion for the source and sink, bit
errors can be acquired for the E100M card. For the
P345_3 and the ME1_8 cards, all buttons on the latter two
tabs are enabled.

Saving NE Configuration Data

This operation manually saves all configuration data in the NE to the flash.
Saved data can be used to restore the NE, when necessary.
To save NE configuration data:

| Select Maintenance > Advanced > Save NE Configuration in the main
menu to save the NE configuration data.
Clearing the NE Configuration

This operation restores all configurations within an NE to their initial status by
clearing all configuration data in the NE equipment, including NE
configuration data and trail information.
To restore the NE configuration:

1. Select Maintenance > System > Clear NE Configuration in the main
menu. The following window opens:
Figure 12-7: Clear SDH Configuration window
2. Click Clear NE's Configuration Data. Operation results are displayed at

the bottom of the window.

Downloading NE Database Files

NE configuration data files can be uploaded to the host of an LCT-BGF client
and downloaded to the NE when needed. These operations are supported by
BG-20 and BG-30 NEs.
The NE configuration data file is kept in binary format in the LCT-BGF client.
When downloading to an NE, the embedded software verifies the
configuration. If the verification fails, downloading is canceled. The download
operation can only be performed on one NE at a time.
To upload the NE database file:

1. Select Maintenance > Advanced > Get/Download NE DB File in the
main menu. The Get/Download NE DB File window opens.
Figure 12-8: Get/Download NE DB File window

2. Select an NE in the list and click Get. The Select Directory window opens.
Figure 12-9: Select Directory window
3. Select the file directory where the NE database file should be saved and
click OK.
To download the NE database file:

1. Select Maintenance > Advanced > NE DB File in the main menu. The
Get/Download NE DB File window (on page 12-10) opens.
2. Select an NE in the list and click Download.
3. In the window that opens, select the NE database file to be downloaded and
click OK to begin the download process.
Performing a Software Upgrade

The embedded software is the control software on the element 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,
whereas the FPGA file is located in the file memory.
NOTE: The Boot Configuration Tool can only upgrade the

MXC4X.

To download embedded software:

1. Select a card and then select Maintenance > Download Embedded
Software. The Download Embedded Software window opens.
Figure 12-10: Download Embedded Software window
Embedded software and FPGA terminology are as follows:
Active Area - currently activated area, used in conjunction with the

Embedded Area
Bank Info - displays Upper Area/Lower Area version information and
running version information
2. Click Get to retrieve the embedded software bank information from the
equipment and display it in the Bank Info area.
3. Click Select File to select the filename to be downloaded, which appears in
the field to the right. Select the Upper Area or Lower Area radio button in
the Embedded Area for the software download location. This selection
should always be different from the Active Area when reverting back to the
original software.
4. Click Download to download the software to the equipment. A
5. After software download, click Apply to activate the software.

To download an FPGA file:

1. Select a card and then select Maintenance > Download FPGA File. The
Download FPGA File window opens.
Figure 12-11: Download FPGA File window
2. Click Select File to select the FPGA filename to be downloaded, which

appears in the field to the right.
3. Click Download.
Performing Activation
Time/Version Activate
Operations
This section describes the procedure to set the activation time. For BG-40 NEs,
this operation is called Activation Time. For BG-20 NEs, this operation is
called Version Activate.

To set the activation time:

1. Do one of the following, depending on the NE type:
For BG-40 NEs, click Activation Time in the Software Upgrade and
Maintenance window. The Activation Time window opens.
Figure 12-12: Activation Time window

For BG-20 NEs, click Version Activate in the Software Upgrade and
Maintenance window. The Version Activate window opens.
Figure 12-13: Version Activate window
2. Click Get to display the Activation Time retrieved from the NE. A Task
window opens, displaying the status of the operation.

3. Click Close. The Upgrade Confirmation window opens, in which you can
verify the current version and new version of the NE.
Figure 12-14: Upgrade Confirmation window
4. Click Cancel to return to the Activation Time/Version Activate window,

or click OK to perform the activation time configuration task.
5. In the Activation Time/Version Activate window:
Click PC Time to read the system time of the LCT-BGF host PC, and
to synchronize the NE time with the system time of the LCT-BGF host
PC.
Set the Activation Time attribute with the time displayed in the
Activation Time/Version Activate window.
Click Cancel Apply to cancel activation time configuration.
Click Apply to send the Activation Time/Version Activate attribute to
the selected NEs. A Task window opens, indicating the status of the
operation.
Click Activate immediately to activate the NE new version
immediately.

Performing Other Maintenance

Operations
The LCT-BGF provides maintenance operations to manage the fan, laser, and
power, as well as to log in to a remote NE.
Logging in a Remote NE
Use the following procedure to log in a remote NE.
To log in a remote NE:

1. Select Maintenance > Debug in the main menu. The Remote Login
window opens.
Figure 12-15: Remote Login window

2. Check the NE IP address and click Login. The Telnet window opens and
displays the NE connection status.
Figure 12-16: Telnet window

Managing the Laser

Use the following procedure to configure the laser.
To manage the laser:

1. Select Maintenance > Laser Management > Laser Switch in the main
menu. The Laser Switch Status window opens.
Figure 12-17: Laser Switch Status window
2. Select an optical port in the NE tree.

3. Set the laser Work Mode and ALS Mode by selecting the relevant radio
buttons. Select the Automatic Restart radio button for the laser to turn on
automatically after a fiber is reconnected or repaired. Select the Manual
Restart radio button for the laser to turn on after an explicit command.
4. Click Apply to send the configuration to the NE and the LCT-BGF
database.

Managing the Fan

Use the following procedure to set the fan work mode.
To manage the fan:

1. Select Maintenance > Fan Status in the main menu. The Fan Status
window opens.
Figure 12-18: Fan Status window
2. Select one of the following to set the fan's work mode:

Temperature Auto Control
Force Turbo

Managing the Power

Use the following procedure to view the NE power type.
To manage the power:

1. Select Maintenance > Power Management in the main menu. The Power
Type Management window opens.
Figure 12-19: Power Type Management window
2. Click Get to retrieve the power information.


13
Performing Advanced
Configuration
In this chapter:
Overview ....................................................................................................... 13-1
Enabling the BG-40 NE Proxy ARP ............................................................. 13-2
Configuring the BG-40 NE ARP List............................................................ 13-3
Displaying DCC MIB Counters .................................................................... 13-5
Configuring the BG-40 NE Serial Port.......................................................... 13-6
Clearing the Flash.......................................................................................... 13-7
Configuring the BG-20 NE Trap Manager Table.......................................... 13-7
Configuring BG-20 NE SNMP Agent Mode................................................. 13-9
Overview
This chapter introduces the advanced configuration of the LCT, which provides
enhanced configuration options for advanced users.

Performing Advanced Configuration LCT-BGF User Manual
Enabling the BG-40 NE Proxy

ARP
The Proxy Address Resolution Protocol (ARP) enables a LAN-connected GNE
to automatically handle ARP requests for remote non-LAN NEs connected via
DCC to the GNE (can be configured in the NE ARP list). The following figure
illustrates this concept.
Figure 13-1: Example of ARP configuration
As shown in this figure, when the router R attempts to connect or send a packet
to a remote NE (for example, NE2), the router sees that this NE has the same
subnet (N1.N2) as the Ethernet that is attached to it and to the GNE. Therefore,
the router incorrectly assumes that the NE is sitting on the same subnet (the
same wire). As a result, the router sends an ARP request to determine the
physical address of the NE. The GNE receives this ARP request and sends its
own physical (MAC) address to the router. The router then makes the
connection or sends the IP packet to the GNE.

LCT-BGF User Manual Performing Advanced Configuration
To enable the BG-40 NE proxy ARP:

1. In the LCT-Login BG-40 NE (shelf view) window, select Advanced >
Proxy ARP Enable/Disable. The Proxy ARP window opens.
Figure 13-2: Proxy ARP window
2. Click Get to retrieve the proxy ARP setting from the equipment.
3. Set the proxy ARP property and click Apply to send the proxy ARP to the
BG-40 NE.
Configuring the BG-40 NE ARP

List
After enabling a GNE's proxy ARP, you should configure the ARP list. The
ARP list contains the NE IP address or the IP subnet for the GNE proxy. When
a GNE receives an ARP request for an IP address, it looks up the address in the
ARP list. If the ARP list contains this IP address, the GNE returns an ARP
acknowledgment.

To configure the BG-40 NE ARP list:

ARP List Configuration. The Proxy ARP Table window opens.
Figure 13-3: Proxy ARP Table window
2. To add proxy ARP items to the table:

Click Add. The IP Configuration window opens.
Figure 13-4: IP Configuration window
Enter the IP address and subnet mask in the respective fields.

Click OK to confirm and return to the Proxy ARP table window. The
new IP address is displayed in the IP list.

3. To modify the proxy ARP table:

Click Modify. The IP Configuration window opens.
Modify the IP address and subnet mask.
Click OK to confirm and return to the Proxy ARP table window.
4. To delete proxy ARP items from the table, select their IP addresses and
click Delete.
5. To obtain proxy ARP IP addresses from the BG-40 NE, click Get. The IP
addresses are displayed in the window.
6. Click Apply to send the proxy ARP IP addresses to the BG-40 NE.
Displaying DCC MIB Counters

DCC MIB counters show detailed information about the DCC channel
communication quality and the position of a DCC communication failure. If the
DCC MIB counters show a channel with many send/receive errors or stop/start
times, it indicates that one of the NEs at the ends of the channel has
communication problems.
To display DCC MIB counters:

Channel MIB Counters. The Channel MIB Counters window opens.
2. Click Refresh to display the Channel MIB Counters window, which
displays the counters in real time.
Figure 13-5: Channel MIB Counters window

Configuring the BG-40 NE Serial

Port
The BG-40 serial port is used to connect external equipment. To connect with
external equipment, set the property as External. To manage the PCM card in
the extension slot, set the property as Internal. The default is Internal.
To configure the BG-40 NE serial port:

Serial Port Configuration. The Serial Port Configuration window
opens.
Figure 13-6: Serial Port Configuration window
2. Click Get to obtain the serial port from the BG-40 NE in this mode.
3. Enter the Serial Port property by selecting the relevant radio button.
4. Click Apply to send the property to the BG-40 NE.

Clearing the Flash

The Clear Flash feature deletes the LCT configuration data from the flash
memory. Other areas are not affected.
To clear the flash:

1. In the LCT-Login NE (shelf view) window, select Advanced > Clear
Flash. A confirmation window appears.
Figure 13-7: Confirm window
2. Click OK to confirm.
Configuring the BG-20 NE Trap

Manager Table
SNMP agent can send trap messages to several managers simultaneously. Trap
messages contain SDH alarm information.
The administrator can modify the trap manager table using an SNMP Set
operation. Only one manager can be specified as the administrator.

To configure the trap manager table:

1. In the LCT-Login NE (shelf view) window, select Advanced > Trap
Manager Table. The Trap Manager Table window opens.
Figure 13-8: Trap Manager Table window
2. To add a new trap manager, enter values for the Manager IP, Trap port
number, and Administrator attributes at the top of the window, and click
Add. The new trap manager is added to the list of trap managers at the
bottom of the window.
3. To delete a trap manager, select it in the list and click Delete.
4. Click Get to retrieve the trap managers from the equipment and display
their details in the list of trap managers.
5. Click Apply to send the trap managers to the equipment.

Configuring BG-20 NE SNMP

Agent Mode
SNMP agent has two work modes: monitoring and full-control.
Some managers need a source IP address to identify an agent. BroadGate NEs
have two IP addresses: DCC and Ethernet. One of them should be selected.
To configure the BG-20 NE SNMP agent mode:

1. In the LCT-Login BG-20 (shelf view) window, select Advanced > SNMP
Agent Mode. The SNMP Agent Mode window opens.
Figure 13-9: SNMP Agent Mode window
2. Click Get to obtain the mode option and IP address for SNMP traps. In
Monitoring mode, the SNMP agent only responds to GET, GET-NEXT,
and GET-BULK operations. In Full-control mode, the SNMP agent
responds to all operations.
3. Enter the mode option and IP address for the SNMP Traps property by
selecting the relevant radio button. Select Ethernet IP when the NE is a
gateway. Otherwise, select DCC IP.
4. Click Apply to send the property to the BG-20 NE.


14
Configuring the PCM Card
In this chapter:
Overview ....................................................................................................... 14-1
Assigning a PCM Card .................................................................................. 14-4
PCM Configuration Management ................................................................. 14-7
Managing SM10 XCs .................................................................................. 14-35
Managing SM_10E XCs.............................................................................. 14-41
Managing PCM Faults................................................................................. 14-47
Performing PCM Maintenance .................................................................... 14-59
Overview
This chapter describes how to access, assign, and configure the SM10 and
SM_10E cards, as well as manage PCM alarms and perform PCM management
and maintenance operations.

Configuring the PCM Card LCT-BGF User Manual
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. In addition, it supports three
common traffic module slots and a special small traffic module slot for
Ethernet interfaces.
Table 14-1: SM10 traffic modules
Name Description
SM_FXO_8 Eight FXO or RD channels
SM_FXS_8 Eight FXS or FXD 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_V35_2 Two V.35 channels
SM_Omnicentor Supports the central side of an Omnibus type of service
(OW on PDH)
SM_Codir_4 Quad port 64 K codirectional, G.703 interface module for the
SM10 card
SM_FE_A Two 10/100BaseT channels (the bandwidth of each channel
can be E1 or N x 64 Kbps)
SM_10E Card
The SM_10E card is a PCM card for BG-20 and BG-30 NEs. The card has the
following features:
| Multiservice access through multiple daughter modules
| Nonblocking DS-0 1280 x 1280 crossing matrix
| 44 E1s mapper/demapper
| 32 E1s framer
| 12 Mbps traffic bandwidth for each module slot; traffic add-and-drop
capacity up to 24 Mbps
| 622 Mbps ESSI bus access to MXC20
| Fully loaded 40 W power consumption

LCT-BGF User Manual Configuring the PCM Card
| Dimensions:
Base card:
Size (height) 25.4 mm
Size (width) 265 mm
Size (depth) 210 mm
Module:
Size (height) 20.0 mm
Size (width) 67.4 mm
Size (depth) 154 mm
| Front-access connectors
Three module sots in the SM_10E, each with a capacity of 12 Mbps, can
accommodate the interface modules described in the following table.
Table 14-2: SM_10E traffic modules
Name Description
SM_FXO_8E Eight-channel foreign exchange office access module
SM_FXS_8E Eight-channel foreign exchange station access module
SM_EM_24W6E 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 Async with full controls V.24
| Two Sync with full controls V.24 that supports
point-to-multipoint
SM_V35E Two-channel V.35 data access module
SM_Omni_E Omnibus central unit with external 4W interfaces
SM_Codir_4E Four-channel 64 K codirectional data access module
SM_EOP Two channels of FE over E1 with a total WAN bandwidth of
8 x E1s
SM_V_COMBO Four channels of FXS and two channels of 2/4W E&M combo
module
SM_D_COMBO One channel of V.35 and 1/2 channels of V.24 combo module

Assigning a PCM Card

The SM10/SM_10E card is assigned in the NE's Slot Assignment window.
NOTE: The SM10 card can only be assigned in extension

slots.
To assign an SM10 card:

1. Select Configuration > NE Configuration > Assigning Slots in the menu.
The Slot Assignment window opens.
Figure 14-1: Slot Assignment window
2. Right-click an extension slot and select SM10.

3. Click Apply to send the configuration to the NE and the LCT-BGF
database.

To assign an SM_10E card:

| The procedure for assigning an SM_10E card is the same as that for
assigning an SM10 card.
To open the SM10 card:

| In the LCT-Login BG-40 NE (shelf view) window, right-click the SM10
card and select Open the Card.
The PCM NE Shelf View window opens.
Figure 14-3: PCM NE Shelf View window

To open the SM_10E card:

| In the BG-20/BG-30 Shelf View window, right-click the SM_10E card and
select Open.
Figure 14-4: BG-30 Shelf View window
The SM_10E Shelf View window opens.
Figure 14-5: SM_10E Shelf View window

PCM Configuration Management

PCM configuration management includes viewing and setting card attributes,
communication parameters, and timing configuration, assigning slots, and
uploading/downloading configuration data.
Viewing/Setting SM10 Card Attributes

Each card has its own attributes, which can be set by the user.
Card attributes include:
| Main SM10 card:
Frame attribute - PCM30, PCM31, or Unframed:
Figure 14-6: Set Subcard Attributes window showing frame attribute for
SM10
PCM30 - the LCT-BGF only processes TS1 through TS15 and

TS17 through TS31. The TS16 channel-associated signal is cross
connected with the service signal, and cannot be controlled by the
LCT-BGF. The LCT-BGF GUI only displays timeslots DS0_1
through DS0_15 and DS0_17 through DS0_31.

PCM31 - the LCT-BGF only processes TS1 through TS31. The

LCT-BGF GUI only displays timeslots DS0_1 through DS0_31.
Unframed - when an E1 is set as Unframed, this 2 Mbps timeslot
does not participate in the cross connection. It can only be
configured for 2 Mbps transparent services on an Ethernet card. The
LCT-BGF GUI cannot view or open this 2 Mbps timeslot.
E1 Physical Connection attribute:
Figure 14-7: Set Subcard Attributes window - E1 Physical Connection

Attribute tab
Front 4 E1s Link to Main Board Through an Adapter: E1s connect

to the adapter.
Front 4 E1s Link to Main Board Through the Back Board: E1s
connect to the backplane.

| Ethernet card (SM_FE_A):
Figure 14-8: Set Subcard Attributes window - FE Board Attribute tab
Port Work Mode - the SM10 transforms an Ethernet signal into an E1

signal. The work mode should be set for each Ethernet port. The Port
Work Mode includes negotiation, duplex mode, and speed settings:
Negotiation attribute - this attribute can be set as Auto-negotiation
or Non-Autonegotiation.
Duplex Mode - the duplex mode can be either Full Duplex or Half
Duplex.
Speed - the speed can be either 10 Mbps or 100 Mbps.
Port Transparent/Frame attribute - for the SM_FE_A card, the frame
attribute should be set for each port. If Framed is selected, you should
also set the bandwidth (N 64 Kbps [N = 1 to 31]) for each port. The
default is 6.
For the SM_FE_B card, you should also set the bandwidth (N 64 K
[N = 1 to 31]) for each port. The default is 6.

| 2/4W E&M card (SM_EMS_24W6):

User Interface Type:
Figure 14-9: Set Subcard Attributes window - User Interface tab
2WEM: two-wire VF and 1E1M; E&M is the signaling channel.

4WEM: four-wire VF and 1E1M; E&M is the signaling channel.
Input/output Level - the LCT-BGF can view and set the 2W/4W
input/output level. You should set the input/output level for each user
interface. Ranges for input/output levels are:
Input: -6 dB to +12 dB
Output: -12 dB to +6 dB
Interval: 0.5 dB
| SM_V24:
The SM_V24 card can be configured with one V.24 channel, two V.24
channels, or eight V.24 channels. You can view the interface type in the Set
Subcard Attributes window. For more details about configuring the card
with one, two or eight channels, see Setting channels on the SM_V24 card
(on page 14-14).

| SM_V35_2:
The SM_V35_2 card provides two V.35 channels. You can view the
interface type in the Set Subcard Attributes window.
Figure 14-10: Set Subcard Attributes window - SM_V35_2
| FXO/RD card (SM_FXO_8):

Interface Type: FXO/RD
| FXS/FXD card (SM_FXS_8):
8 Interface Type: FXS or FXD
| SM_Omnicentor card - SM_Omnicentor card properties define the
ring-back tone and conference call configuration, as follows:
Eight conference call groups.
The maximum number of conference groups for each SM_Omnicentor
card is 64. The default is 0.

A negative attenuation value denotes gain.

Input and output attenuation value ranges are:
Input: -15 dB to +15 dB; step = 1 dB; default = 0 dB
Output: -15 dB to +15dB; step = 1 dB; default = 0 dB
Figure 14-11: Set Subcard Attributes window - SM_Omnicentor Card

Attribute tab

To view/set card attributes:

1. In the PCM NE Shelf View window, select Configuration > Card
Attribute. The Set Subcard Attributes window opens.
Figure 14-12: Set Subcard Attributes window
2. Click Get to obtain the PCM NE attributes.

3. Set the card attributes and click Apply to send the configuration to the
LCT-BGF database and the NE.

Setting channels on the SM_V24 card

Use the following procedures to configure the channels on the SM_V24 card.
You can configure the card for one, two, or eight channels.
To configure the SM_V24 card with one channel:

| In the Set Subcard Attributes window, select Sync With Control (1 CH)
in the drop-down list in the V24 Module Selection field.
Figure 14-13: Set Subcard Attributes window for SM_V24 card - 1 channel

To configure the SM_V24 card with two channels:

| In the Set Subcard Attributes window, select Async with Control (2 CH)
in the drop-down list in the V24 Module Selection field.
Figure 14-14: Set Subcard Attributes for SM_V24 card - 2 channels
The following attributes can be set in this window:
RTS: Request to Send

DCD: Data Carrier Detect
CTS: Clear to Send
DSR: Data Set Ready
DTR: Data Terminal Ready

To configure the SM_V24 card with eight channels:

| In the Set Subcard Attributes window, select Transparent (8 CH) in the
drop-down list in the V24 Module Selection field.
Figure 14-15: Set Subcard Attributes window for SM_V24 card - 8 channels

Viewing/Setting SM_10E Card Attributes

Each card has its own attributes, which can be set by the user.
Card attributes include:
| E1_PCM card:
Figure 14-16: Set Subcard Attributes window - E1_PCM
Frame attribute - PCM30, PCM31:

PCM30 - the LCT-BGF only processes TS1 through TS15 and
TS17 through TS31. The TS16 channel-associated signal is cross
connected with the service signal, and cannot be controlled by the
LCT-BGF. The LCT-BGF GUI only displays timeslots DS0_1
through DS0_15 and DS0_17 through DS0_31.
PCM31 - the LCT-BGF only processes TS1 through TS31. The
LCT-BGF GUI only displays timeslots DS0_1 through DS0_31.

| SM_EM_24W_6E card:
Figure 14-17: Set Subcard Attributes window - SM_EM_24W_6E
Interface Type:
2W with EM: 2-wire VF and 1E1M; E&M is the signaling channel.
4W with EM: 4-wire VF and 1E1M; E&M is the signaling channel.
2W without EM: two-wire VF.
4W without EM: four-wire VF.
Input/output Gain - the LCT-BGF can view and set the input/output
gain for each user interface. Ranges for input/output gain are:
Input: -13 to +1 dB
Output: -1 to +13 dB
Interval: 0.5 dB
| FXO/RD card (SM_FXO_8E):
Use State: Idle, Busy

| FXS/FXD card (SM_FXS_8E):
Figure 14-18: Set Subcard Attributes window - SM_FXS_8E
Use State: Idle, Busy

| SM_V35E - the SM_V35E card provides two V.35 channels. You can view
the interface type in the Set Subcard Attributes window.
Figure 14-19: Set Subcard Attributes window - SM_V35E
| SM_Omni_E card:
Figure 14-20: Set Subcard Attributes window - SM_Omni_E

The SM_Omni_E card properties define conference call configuration, as

follows:
Eight conference call groups.

The maximum number of conference groups for each SM_Omni_E
card is 64. The default is 0.
A negative attenuation value denotes gain.
Input and output attenuation value ranges are:
Input: -15 to +15 dB; step = 1 dB; default = 0 dB
Output: -15 to +15 dB; step = 1 dB; default = 0 dB
| SM_V24E card - the SM_V24E card can be configured with two, four, or
eight channels. You can view the interface type in the Set Subcard
Attributes window. For more details about configuring the card with two,
four or eight channels, see Setting channels on the SM_V24E card (on
page 14-22).
To view/set card attributes:

1. In the SM_10E Card Shelf View window, select Configuration > Card
Attribute. The Set Subcard Attributes window opens.
Figure 14-21: Set Subcard Attributes window - SM_10E

2. Click Get to obtain the SM_10E subcard attributes.

3. Set the card attributes and click Apply to send the configuration to the
Setting channels on the SM_V24E card

Use the following procedures to configure the channels on the SM_V24E card.
You can configure the card for two, four or eight channels.
To configure the SM_V24E card with two channels:

| In the Set Subcard Attributes window, select Sync With Control (2
Channels) in the drop-down list in the V24 Module Selection field.
Figure 14-22: Set Subcard Attributes window - SM_V24E - 2 channels

To configure the SM_V24E card with four channels:

| In the Set Subcard Attributes window, select Async with Control (4
Channels) in the drop-down list in the V24 Module Selection field.
The following attributes can be set in this window:
RTS: Request to Send

DCD: Data Carrier Detect
CTS: Clear to Send
DSR: Data Set Ready
DTR: Data Terminal Ready

To configure the SM_V24E card with eight channels:

| SM_V24E setup of eight channels supports a transparent V.24 interface
without any control signals only TX and RX lines. In the Set Subcard
Attributes window, select Transparent (8 Channels) in the drop-down list
in the V24 Module Selection field.

Configuring the point-to-multipoint

attribute on the SM_V24E card
Use the following procedure to configure the point-to-multipoint attribute on
the SM_V24E card.
To configure the SM_V24E card with point-to-multipoint:

1. In the Set Subcard Attributes window, select P2MP in the Port Operation
mode field.
Figure 14-25: Set Subcard Attributes window - SM_V24E card - point-to-

multipoint
2. Select the rate in the Rate Adaption field.

3. Select Master or Slave in the Master/Slave field.
4. Click Apply to save the configuration.

Performing PCM Slot Assignment

PCM cards for the SM10/SM_10E can be assigned, as required.
To assign SM10 PCM cards:

1. In the PCM NE Shelf View window, select Configuration > Assign Slots.
The Board Assignment window opens.
Figure 14-26: Board Assignment window
2. Click Get to obtain the card assignment from the equipment.

3. Assign the cards and click Apply to send the configuration to the

To assign SM_10E PCM cards:

1. In the SM_10E Shelf View window, select Configuration > Assign Slots.
The SM10E Slot Assignment window opens.
Figure 14-27: SM10E Slot Assignment window
2. Click Get to obtain the card assignment from the equipment.

3. Assign the cards and click Apply to send the configuration to the

Configuring PCM Timing

Synchronous timing configuration enables an NE to automatically select and be
synchronized with the highest-quality clock source in the network, in order to
achieve clock synchronization for the entire network.
To configure the SM10 timing:

1. In the PCM NE Shelf View window, select Configuration > Timing
Configuration. The Sync Timing Configuration window opens.
Figure 14-28: Sync Timing Configuration window
2. Click Get to retrieve the timing configuration from the equipment.

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

To configure the SM_10E timing:

1. In the SM_10E Shelf View window, select Configuration > Timing
Configuration. The SM_10E Timing Configuration window opens.
Figure 14-29: SM10E Timing Configuration window - SyncTiming

Configuration tab
2. Select the SyncTiming Configuration tab.

3. Click Query to get the timing reference from the LCT-BGF database.
4. Click Get to retrieve the timing configuration from the equipment.
5. Set the timing parameters and click Apply to send the configuration to the
LCT-BGF database and the equipment.

6. Select the Timing Trace tab.
Figure 14-30: SM10E Timing Configuration window - Timing Trace tab
7. Click Get to retrieve the timing trace information.
Viewing the PCM Clock Mode

You can determine the clock working mode by querying the NE's current clock
mode. The clock mode can be one of the following:
| Internal timing mode
| Locked mode

To view the SM10 clock mode:

| In the PCM NE Shelf View window, select Configuration > Timing
Mode. The Get Clock Work Mode window opens.
Figure 14-31: Get Clock Work Mode window
Uploading/Downloading SM10 Configuration

Data
SM10 configuration data includes configuration attributes, alarm attributes, and
maintenance attributes. SM10 configuration data can be uploaded/downloaded
to/from the SM10 card.
Uploading configuration data retrieves SM10 configuration data from the NE.
Downloading configuration data sends the SM10 configuration data to the
element.
The following operations can be performed on the SM10 card:
| Upload configuration data
| Download configuration data
| Query configuration data

| Compare configuration data

| Save configuration data to the LCT-BGF
| Upload XCs
To access the Upload/Download PCM Configuration Data

window:
| In the PCM NE Shelf View window, select Configuration >
Upload/Download Configuration Data. The Upload/Download PCM
Configuration Data window opens.
Figure 14-32: Upload/Download PCM Configuration Data window
To upload PCM configuration data:

| Click Upload to upload PCM configuration data. A message box shows the
progress of this task. Data is displayed after uploading.
To download PCM configuration data:

| Select an object in the tree and click Download to download the
configuration data.
To query PCM configuration data:

| Select an object in the tree and click Query to retrieve the configuration
data from the database.

To check the consistency of PCM configuration data:

| After uploading PCM configuration data, click Compare with NM to
check the consistency of the data with the database.
To save PCM configuration data:

| After uploading PCM configuration data, click Save to Database to save
the data to the database.
To upload XCs:
1. In the Upload/Download PCM Configuration Data window, click XCs
Upload. The XCs Upload window opens.
Figure 14-33: XCs Upload window - XCs Upload tab
2. Select the XCs Upload tab and click Upload to upload the XCs from the
equipment.
3. Click Overwrite to save the XCs to the database.

5. Click XCs in NE But Not In Local Database to display the XCs that exist
in the equipment, but not in the LCT-BGF database, as shown in the
following figure.
Figure 14-34: XCs Upload window showing comparison results
6. Click XCs In Local Database But Not In NE to display the XCs that exist
in the LCT-BGF database, but not in the equipment.
7. Click Different Active State to display the XCs with an inconsistent active
state.
8. Click Delete remotely to delete XCs in the equipment.
9. Click Save to DB to save the uploaded XCs from the equipment to the
LCT-BGF database.

Managing SM10 XCs

This section describes how to create, manage, and upload SM10 XCs.
Creating an SM10 XC
Creating a client trail manually configures cross-connections in a single NE. A
client trail is complete only after all of its client trail cross-connections have
been configured.
To manually create an XC:

1. Select Trail > Create XC in the main menu. The Create XC window
opens.
Figure 14-35: Create XC window
2. Select a rate of 2M or 64K in the Rate drop-down list.

3. Specify the direction by selecting either the Bidirectional or Unidirectional
radio button.
4. When a shared timeslot is needed, click Shared Point.
5. Select the required timeslots in the Source Time Slot and Sink Time Slot
lists. If multiple timeslots are selected, the number of source/sink timeslots

7. Select the Send List tab to display the configured cross-connections.
Figure 14-36: Create XC window - Send List tab
8. Click Remove to delete configured cross-connections.

9. Click Activate to send the cross-connections to the equipment.
Successfully sent cross-connections have an Active status.

Managing SM10 XCs

Client trail cross-connection maintenance includes filtering, activating,
deactivating, and deleting XCs.
To access the XC Management window:

| In the PCM NE Shelf View window, select Trail > XC List in the main
menu. The XC Management window opens.
Figure 14-37: XC Management window - XC List tab
To activate XCs:
1. In the XC Management window, select the XCs to be activated.
2. Click Activate to activate the XCs. When a client trail is successfully
activated, it status changes from Inactive to Active.
To deactivate XCs:
1. In the XC Management window, select the XCs to be deactivated.
2. Click Deactivate to deactivate the XCs.

To delete XCs locally:

1. In the XC Management window, select the XCs to be deleted.
2. Click Delete Locally to delete the XCs.
To filter XCs:
1. In the XC Management window, set the filter options.
2. Click Filter to filter XCs.
Figure 14-38: Set Ethernet Timeslot Share Sign window
3. Click Set As Shared to set the shared point.

4. Click Remove Shared to remove the shared point.
Uploading SM10 XCs

Current XC data can be uploaded from the BG-40 NE, as needed. By
comparing the XC information on the equipment to XC information in the
LCT-BGF, you can check the data consistency between them.

To upload XCs:
1. Click Trail > XC Upload in the main menu. The Upload XCs window
opens.
Figure 14-39: Upload XCs window - XCs Upload tab
2. Click Upload to upload the XCs. If the operation succeeds, the trail data
uploaded from the equipment is displayed in the list and NE XC
consistency information is displayed at the bottom of the window.
3. Click Overwrite to overwrite the XC data in the LCT-BGF database with
the XC data uploaded from the equipment.

Figure 14-40: Upload XCs window - Compare Result tab
If the compare results are consistent, the three Compare pages are null and
the operation buttons in this tab are grayed out. If results are inconsistent,
one of the following is displayed, depending on the type of inconsistency
found:
XCs In NE But Not In Local Database - in this case, click Delete

remotely to delete these XCs from the equipment or Save to DB to
save them to the LCT-BGF. After saving, these XCs become Active.

XCs In Local Database But Not In NE - click Delete Locally to

delete these XCs from a local database in the LCT-BGF. Click Modify
DB Inactive to modify these XCs saved in the LCT-BGF and change
their status from Active to Inactive. Click Send XC to send these XCs
to the NE equipment. These XCs become Active after they are sent.
Figure 14-41: XCs Upload window - XCs In Local Database But Not In NE
page
Different Active State - click Modify DB Active to change the status

of these XCs in the LCT-BGF from Inactive to Active.
Managing SM_10E XCs

This section describes how to create, manage, and upload SM_10E XCs.
Creating SM_10E XCs

Creating a client trail manually configures cross connections in a single NE. A
client trail is complete only after all of its client trail cross connections have
been configured.

To manually create an XC:

1. Select XC > Create XC in the main menu. The Create XC window opens.
Figure 14-42: Create XC window - SM_10E
2. Select a rate of 2M or 64K in the Rate drop-down list.

3. Specify the direction by selecting either the Bidirectional or Unidirectional
radio button.
4. When a shared timeslot is needed, click Shared Point.
5. Select the required timeslots in the Source Timeslot and Sink Timeslot lists.
If multiple timeslots are selected, the number of source/sink timeslots

7. Select the Send List tab to display the configured cross connections.
Figure 14-43: Create XC window - Send List tab - SM_10E
8. Click Remove to delete configured cross connections.

sent cross connections have an Active status.

Managing SM_10E XCs

Client trail cross-connection maintenance includes filtering, activating,
deactivating, and deleting XCs.
To access the XC Management window:

| In the SM_10E Shelf View window, select XC > XC List in the main
menu. The XC Management window opens.
Figure 14-44: XC Management window - SM_10E
To activate XCs:
1. In the XC Management window, select the XCs to be activated.
2. Click Activate to activate the XCs. When a client trail is successfully
activated, it status changes from Inactive to Active.
To deactivate XCs:
1. In the XC Management window, select the XCs to be deactivated.
2. Click Deactivate to deactivate the XCs.

To delete XCs locally:

1. In the XC Management window, select the XCs to be deleted.
2. Click Delete Locally to delete the XCs.
To filter XCs:
1. In the XC Management window, set the filter options.
2. Click Filter to filter XCs.
Uploading SM_10E XCs

Current XC data can be uploaded from the BG-40 NE, as needed. By
comparing the XC information on the equipment to XC information in the
LCT-BGF, you can check the data consistency between them.
To upload XCs:
1. Click XC > Upload XCs in the main menu. The Upload XCs window
opens.
Figure 14-45: Upload XCs window - XCs Upload tab - SM_10E

2. Click Upload to upload the XCs. If the operation succeeds, the trail data
uploaded from the equipment is displayed in the list and NE XC
consistency information is displayed at the bottom of the window.
3. Click Overwrite to overwrite the XC data in the LCT-BGF database with
the XC data uploaded from the equipment.
Figure 14-46: Upload XCs window - Compare Result tab - SM_10E
If the compare results are consistent, the three Compare pages are null and
the operation buttons in this tab are grayed out. If results are inconsistent,
one of the following is displayed, depending on the type of inconsistency
found:
XCs in NE but Not in Local Database - in this case, click Delete

remotely to delete these XCs from the equipment or Save to DB to
save them to the LCT-BGF. After saving, these XCs become Active.

XCs in Local Database but Not in NE - click Delete Locally to delete

these XCs from a local database in the LCT-BGF. Click Modify DB
Inactive to modify these XCs saved in the LCT-BGF and change their
status from Active to Inactive. Click Send XC to send these XCs to the
NE equipment. These XCs become Active after they are sent.
Figure 14-47: Upload XCs window - Compare Result tab - XCs in Local
Database but Not in NE page - SM_10E
Different Active State - click Modify DB Active to change the status

of these XCs in the LCT-BGF from Inactive to Active.
Managing PCM Faults

The equipment enters the normal running and maintenance phase immediately
after service trail configuration is completed. Therefore, you can view various
equipment alarms and performance data through the LCT-BGF, in order to
monitor the running status of the equipment.
Alarm data provides comprehensive service fault information. Alarm
processing is the major maintenance task for SDH equipment.
Alarms include alarm generation, alarm clearance, and time interval
information.

An event indicates that the equipment generated a certain action or process

under some condition, but that the action or process itself does not influence
the traffic. The equipment reports this action or process to the LCT-BGF as an
event. The event reflects the running status of the equipment. The occurrence
of many events may result in the generation of alarms. Although the event itself
does not influence the running of the equipment, the hidden causes are likely to
trigger alarms.
The display of the equipment alarm status needs no user intervention. The
LCT-BGF will update the colors of indicators on the NE layer, card layer, and
functional unit layer according to the reported alarms. The alarm source and
level are denoted by colored indicators at all three operation layers. The alarms
at each layer represent the highest level of all alarms for the layer and the
objects belonging to it.
The LCT-BGF also provides an audio alarm.
Managing SM10 Faults

This section describes how to handle SM10 card alarms.
Monitoring Events
The event recorder provides a convenient, real-time mechanism for viewing
alarms and events. It faithfully records all notices from the equipment,
including alarms, alarm clearing actions, and events.

To monitor events:
1. In the PCM NE Shelf View window, select Fault > Event Monitor in the
main menu. The PCM Event window opens.
Figure 14-48: PCM Event window
2. Click Delete to delete the displayed alarm and event records.

3. Click Filter to filter the event records.
Managing Current Alarms

A current alarm identifies an existing abnormal event caused by a problem in
the equipment or the communication line. The PCM Alarm window can
display all current alarms, all alarms for a specific NE, or alarms for a specific
card.
The following terms apply regarding current alarms:
| Current alarm - the alarm record is generated, but not cleared.
| Alarm acknowledge - acknowledges the reported alarm record with an
Unacknowledged status, and changes its alarm status to Acknowledged.
The time for the acknowledgement is the current time. Any alarm can only
be acknowledged once.

| Delete - deletes an alarm from the current alarm database in the

LCT-BGF.
| Manual clearance - deletes an alarm from the current alarm database in the
LCT-BGF and saves it to the historical alarm database in the
LCT-BGF.
| Alarm severity - alarms are categorized by severity into four levels: critical,
major, minor, and warning.
To access the PCM Alarm window:

| In the PCM NE Shelf View window, select Fault > Current Alarm in the
main menu. The PCM Alarm window opens.
Figure 14-49: PCM Alarm window - Current Alarm tab
To acknowledge alarms:
| Select one or several alarms in the PCM Alarm window - Current Alarm
tab and then click Acknowledge to acknowledge them.
To clear alarms:
| Select one or several alarms in the PCM Alarm window - Current Alarm
tab and then click Clear Manually to clear the alarms.

To filter the alarms:

1. In the PCM Alarm window - Current Alarm tab, click Filter. The Alarm
Filter (PCM) window opens.
Figure 14-50: Alarm Filter (PCM) window
2. Set the filter and click Ok to filter the alarms.
To save alarms to a file:

1. In the PCM Alarm window - Current Alarm tab, click Save As. A file
selection window opens.
2. Input the file name and click Save to save the alarms to a file.

Managing Historical Alarms

Historical alarms refer to alarm records automatically cleared after the
equipment returns to normal status. As with current alarms, historical alarms
are saved in the LCT-BGF database.
Historical alarms can be filtered. You can display all historical alarms, all
alarms for a selected NE, alarms for a selected card, or alarms for a selected
functional block.
The following terms apply regarding historical alarms:
| Historical alarm - an alarm record automatically cleared because the
equipment returns to normal after the alarm is generated, and the current
alarm is manually cleared.
| Clearance mode - identifies the clearance mode for the historical alarm:
either manually cleared or automatically cleared. Manually cleared alarms
are manually cleared by a user. For automatically cleared alarms, the alarm
record is automatically cleared when a fault returns to normal after an
alarm has occurred. No user intervention is involved in the latter type.
To access historical alarms:

| Click Fault > History Alarm in the main menu. The PCM Alarm window
- History Alarm tab opens.
Figure 14-52: PCM Alarm window - History Alarm tab

To delete historical alarms:

1. In the PCM Alarm window - History Alarm tab, select the alarms to be
deleted.
2. Click Delete to delete alarms.
To filter historical alarms:

1. In the PCM Alarm window - History Alarm tab, click Filter. The Alarm
Filter window opens.
2. Set the filter and click OK.
To save historical alarm information to a file:

1. In the PCM Alarm window - History Alarm tab, click Save As to open a
file selection window.
2. Save the historical alarm records as an HTML file.
3. To view the file at a later time, open it using a browser.
Configuring Alarm Attributes

An alarm attribute table is used to record basic NE alarm information,
including all alarm causes. You can set the Alarm Severity and Autoreport
attributes for each alarm cause.
When an alarm is set as Autoreport but is not shielded, the NE immediately
reports it to the LCT-BGF when the alarm is generated or cleared.
Alarms set as Nonautoreport are not reported to the LCT-BGF, but are recorded
in the NE. Alarms set as Nonautoreport can only be manually retrieved by the
LCT-BGF. The default setting for the Autoreport attribute is Autoreport.

To set alarm attributes:

1. Select Fault > Alarm Attribute in the main menu. The Set Alarm
Figure 14-53: Set Alarm Attributes window
2. Click Get to retrieve the alarm attributes from the element.

3. Set the alarm attributes and click Apply to send the configuration to the
equipment and the database.
Masking Alarms
In some cases, the alarms of some ports and functional blocks are irrelevant to
the service. In this case, alarms can be masked to avoid confusing them with
the alarms caused by actual faults. Alarms that are masked (shielded) are not
monitored and do not affect card and equipment alarm indications (namely, the
card-level alarm status and NE-level alarm status). No alarm data is reported or
recorded for shielded alarms.
In the LCT-BGF, PCM alarms can be masked for the E1 port, Ethernet port,
and 64 Kbps port.
When the alarms of a certain object are masked, the alarms related to this
object in the current alarm database are cleared. After the alarm mask is
released, the equipment reports the current alarm. Therefore, the NE equipment
for which the alarms have been masked should have no alarm indication.

To mask (shield) an alarm:

1. Select Fault > Mask in the main menu. The Alarm Mask window opens.
Figure 14-54: Alarm Mask window
2. To view alarm mask information for a managed object, select one or more
managed objects and click Query. The alarm mask information is
displayed.
3. To retrieve alarm mask information for an object, select one or more
objects and click Get. Alarm mask information is displayed.
4. Modify alarm mask parameters, as required.
5. Click Apply to send the settings information to the equipment and
database.

Viewing Alarm Severity

You can query or obtain the SM10's alarm severity table, but cannot change it.
Figure 14-55: Alarm Severity window

Correcting Alarms
Alarm correction can be used to ensure alarm consistency between the
LCT-BGF and the SM10 card. This operation refreshes the current alarm on the
LCT-BGF side, based on the current alarm on the SM10 side.
To correct an alarm on an NE:

| Select Fault > Alarm Correction in the main menu to correct an alarm.
Table 14-3: PCM alarm table
Alarm type ID Probable cause Alarm source Severity

Equipment 1 (71) Unexpected card 13 subcard Critical
alarm 2 (72) Card out 13 subcard Critical
3 (73) Type mismatch 13 subcard Critical
4 (75) Card fault 13 subcard Critical
Service alarm 1 (1) E1 LOS 8 E1 signal Critical
2 (4) E1 LOF 8 E1 signal Critical
3 (7) E1 AIS 8 E1 signal Major
4 (10) E1 LOMF 8 E1 signal Major
5 (13) E1 RAI 8 E1 signal Major
6 (16) PPI LOS Ethernet service Critical
7 (19) PPI AIS Ethernet service Major
8 (22) Link off Ethernet service Major
9 (25) CLK LTI Clock module Critical
10 (26) No available TS Clock module Critical
11(28) CLK LOL Clock module Minor

Managing SM_10E Faults

Unlike the SM10, SM_10E fault management is integrated in the LCT-BGF
main fault management, with the filter option set to the SM_10E card.
Figure 14-56: Current Alarm View window - SM_10E

Performing PCM Maintenance

This section describes how to perform PCM maintenance tasks.
Viewing the Run Time

This section describes how to view the running time of the PCM card.
To view the SM10 run time:

| In the PCM NE Shelf View window, select Maintenance > Get
RunTime. The Return Command window opens displaying the run time.
Figure 14-57: Return Command window displaying the run time
To view the SM_10E run time:

| In the SM_10E Shelf View window, select Maintenance > Get RunTime.
The Run Time window opens displaying the run time.
Figure 14-58: Run Time window - SM_10E

Viewing the Electronic Label

The electronic card label is typically used during engineering and production
maintenance, and displays the equipment hardware and software versions.
To view the SM10 electronic label:

| In the PCM NE Shelf View window, right-click a card and select Get
Electronic Label in the pop-up menu to view the SM10 card's electronic
label.
Figure 14-59: Run Command window displaying the SM10 card electronic
label

To view the SM_10E electronic label:

| In the SM_10E Shelf View window, right-click the XC card and select Get
Electronic Label in the pop-up menu.
Figure 14-60: SM_10E Shelf View window
The SM_10E Electronic Label window opens, displaying the card's

electronic label.
Figure 14-61: SM_10E Electronic Label window

Performing a Loopback Operation

The loopback operation is designed to aid in testing the service path and service
interface. In this context, loopback refers to a software loopback, meaning that
it is set through the LCT-BGF.
After an end-to-end trail has been configured, a loopback can be used to test
whether the whole path works normally and whether meters receive and send
consistently. If there is no error code, it means that everything is working
normally.
The loopback operation includes:
| Terminal (NE) loopback - looping back signals from the cross-connect unit
back to the same cross-connect unit. The terminal loopback operation can
be used to test the flow of signals in the system.
| Facility (FE) loopback - directly looping back signals received by the
physical port to the output port corresponding to it, without changing the
signal structure. The facility loopback operation can be used to test the
connector.
To view a loopback example, see the figure Loopback example (on page 12-3).
To perform an SM10 loopback:

1. Select Maintenance > Loopback in the PCM NE Shelf View window.
The Loopback Attribute window opens.
Figure 14-62: Loopback Attribute window

2. Click Query to obtain the loopback status from the LCT-BGF database.
3. Click Get to obtain the loopback status from the equipment.
4. Set the loopback attributes and click Apply to send the loopback attributes
to the LCT-BGF database and the equipment.
NOTE: If the timeslot has a Loopback status, the loopback

icon is displayed.
To perform an SM_10E loopback:

1. Select Maintenance > Loopback in the SM_10E Shelf View window. The
Loopback Attribute window opens.
Figure 14-63: Loopback Attribute window - SM_10E
2. Click Query to obtain the loopback status from the LCT-BGF database.

3. Click Get to obtain the loopback status from the equipment.

4. Set the loopback attributes and click Apply to send the loopback attributes
to the LCT-BGF database and the equipment.
NOTE: If the timeslot has a Loopback status, the loopback

icon is displayed.
Performing a Connectivity Test on SM10

This operation sends a ping from the LCT-BGF to the NE equipment, in order
to verify the connection to the NE equipment. The ping checks the connection
between a local host and the network by sending one Internet Control Message
Protocol (ICMP) ECHO packet to the host over the network, and subsequently
monitoring the returned ECHO REPLY packet.
To perform a connectivity test:

1. In the PCM NE Shelf View window, select Maintenance > Ping. The
PCM Ping window opens.
Figure 14-64: PCM Ping window
2. Click Ping to test the connectivity. Ping results are displayed.

Resetting the Equipment

When the equipment works abnormally, a reset operation should be performed.
To reset the SM10:

| In the PCM NE Shelf View window, select Maintenance > Reset > Main
Card Reset to reset the SM10 main card.
To reset the SM_10E:

1. In the SM_10E Shelf View window, right click the XC card and select
Reset to reset the SM_10E main card. The Device Reset Operation
window opens.
Figure 14-65: Device Reset Operation window - SM_10E
2. Click OK to reset the SM_10E main card.

3. In the SM_10E Shelf View window, right click on other modules and
select Reset to reset the other modules.

Performing a Software Upgrade for SM10

You can upgrade the SM10 software from the LCT-BGF.
To upgrade software:
1. In the PCM NE Shelf View window, select Maintenance > PCM NE
Software Upgrade. The PCMNE Software Upgrade window opens.
Figure 14-66: PCM NE Software Upgrade window
2. Click Main Card ELabel to obtain the SM10 electronic label.

3. Check the label to ensure that it corresponds to the element to be upgraded.
4. Click Emb Upgrade to open an upgrade file selection window.
Figure 14-67: Please select the file for upgrading window

5. Click Start to begin the upgrade process.
Figure 14-68: PCMNE Software Upgrade window after starting the upgrade
6. If necessary, click Stop to terminate the upgrade.
Managing SM10 Configuration Data

The Save Configuration operation manually saves all configuration data in the
NE to the flash. Saved data can be used to restore the NE, when necessary.
The Clear Configuration operation restores all configurations within an NE to
their initial status by clearing all configuration data in the equipment.
To save the configuration data:

| In the PCM NE Shelf View window, select Maintenance > Save NE
Configuration Data to save the configuration to the equipment.
To clear the configuration data:

| In the PCM NE Shelf View window, select Maintenance > Clear NE
Configuration Data to clear the configuration on the equipment.


15
Managing Licenses
In this chapter:
Overview ....................................................................................................... 15-1
License Control Mechanism .......................................................................... 15-2
License Control Workflow ............................................................................ 15-3
License Format .............................................................................................. 15-4
Managing Licenses in the LCT-BGF ............................................................ 15-6
Overview
In the BG-20, the LCT-BGF uses a license-control mechanism for the
following cards and modules:
| STM-4 on the SAM module
| Ethernet ports on the L1B_6F card
The default configuration of the BG-20 NE is STM-1 with no Ethernet ports. If
you want to upgrade to STM-4 or use the Ethernet ports, licenses must be
purchased from ECI Telecom. These licenses include the serial number of the
BG-20 NEs, the ADM rate, and the number of ports. Use the license-control
feature of the LCT-BGF to download the licenses to BG-20 NEs and activate
them. STM-4 or Ethernet ports can only be used on BG-20 with the appropriate
license.

Managing Licenses LCT-BGF User Manual
License Control Mechanism

The BG-20 license is controlled by both the LCT-BGF and the BG-20
embedded software. The LCT-BGF is responsible for the following tasks:
| Providing a Purchase Order tool to generate a purchase order according to
the selected BG-20 serial number and the configuration
| Providing license file management functions, such as license file importing,
license viewing, and license file exporting
| Providing a license activation function
The BG-20 embedded software is responsible for the following tasks:
| Reporting the actual resource usage to the LCT-BGF
| Validating the license key and activating the license
Customers use the Purchase Order tool to generate the purchase order, which
includes the BG-20 NE's serial number, ADM rate, and number of ports. The
license file is generated according to the purchase order. The license file
contains records composed of the BG-20 serial number and the license key.
The license key is generated using an MD5 algorithm according to the BG-20
serial number and the purchase order.
License files must be imported to the LCT-BGF and then activated. The
LCT-BGF validates the license before its activation. If the license is invalid, for
example, if the number of ports specified in the license is less than the number
of currently enabled ports on the BG-20, the LCT-BGF does not activate the
license.
License activation transfers the license key to the BG-20 NE, where it is
validated by the embedded software. If there is a mismatch between the license
key and the NE serial number, the license key is not activated and an error is
reported to the LCT-BGF. After license key validation, the license key is
activated and the ports can be used.

LCT-BGF User Manual Managing Licenses
License Control Workflow

The LCT-BGF license control workflow is the same as that for the EMS-BGF,
and is shown in the following figure.
Figure 15-1: License control workflow
You should install the BG-20 NEs first and then generate the purchase order
using the LCT-BGF. ECI Telecom generates the license file according to the
purchase order and delivers it to you. Once received, you should import the
license file to the LCT-BGF and download the license key to the BG-20 NEs.
The BG-20 NEs check the license and activate it if all criteria match. Ports are
then available for use.
If the license file is not provided, you can manually input the license code in
the LCT-BGF. The license code is printed on a sticker on the NE packing box.
For more details, refer to the "To activate the license in the BG-20 Shelf View
window" procedure in Managing Licenses in the LCT-BGF (on page 15-6).

The following figure shows the workflow for inputting a license code
manually.
Figure 15-2: Workflow for manually inputting the license code
License Format
The license purchase order format is described in the following table.
Table 15-1: License purchase order format
SN Current ADM Expected Current Qty of Expected Qty

Rate ADM Rate E. Ports of E. Ports
111111111 STM-1 STM-4 0 3
111111114 STM-1 STM-1 0 6
111111115 STM-1 STM-4 0 0
Total 0 2 0 9

The license purchase order is composed of license records, where each record
contains the following values:
| SN
| Current ADM Rate
| Expected ADM Rate
| Current Qty of E. Ports
| Expected Qty of E. Ports
License purchase order values are described in the following table.
Table 15-2: License purchase order values
Attribute Description
SN Serial number of the BG-20 NE
Current ADM Rate Current rate of the SAM module
Expected ADM Rate Expected rate of the SAM module
Current Qty of E. Ports Current number of Ethernet ports
Expected Qty of E. Ports Expected number of Ethernet ports
The license file format is described in the following table.
Table 15-3: License file format
SN ADM Rate Eth Ports Key

111111111 STM-4 3 9CF2-3337-CBD0-1960
111111114 STM-1 6 BF18-EE76-2D00-8831
111111115 STM-4 0 9DB9-D207-25A7-E95D
No. of NEs: 3 No. of No. of Ethernet
STM-4s: 2 ports: 9
The license file is composed of license records, where each record contains the
following fields:
| SN
| ADM Rate
| Eth Ports
| Key

License file values are described in the following table.
Table 15-4: License file values
Attribute Value
SN Serial number of the BG-20 NE
ADM Rate STM-4 or STM-1
Eth Ports Number of Ethernet ports
Key License key
Managing Licenses in the

LCT-BGF
This section describes how to manage licenses in the LCT-BGF.
To access the License File window:

| Select License > License File in the main menu. The License File window
opens.
Figure 15-3: License File window

To import the license file:

1. In the License File window, click Import. The Select File window opens.
Figure 15-4: Import License - Select File window
2. Select the license file and click Open. The LCT-BGF imports the license
file. If the license file is corrupted, the LCT-BGF displays a warning
message.
To export the license file:

1. In the License File window, click Export. The Select File window opens.
Figure 15-5: Export License - Select File window
2. Browse to the required folder and click Save. The LCT-BGF exports the
license file.

To activate the license in the BG-20 Shelf View window:

1. Select License > Activate License Keys Manually in the Shelf View
window menu. The Activate License window opens.
Figure 15-6: Activate License window
2. Click View Resource in NE to check the resource.

3. The license code is printed on a sticker on the NE packing box. Input the
license code manually in the Activate License window.
Figure 15-7: BG-20 license sticker
4. Click Activate License to download the license key to the NE.

If the ports number or service type is less than the current configuration, a
warning message appears.
Figure 15-8: Activate License window showing warning message
The NE validates the license key by the NE serial number. Ports and
services are enabled if all criteria match.


Glossary of Terms
1
100BaseT
100 Mbps baseband data LAN transmission running over twisted pair copper cable
(also called Fast Ethernet). Three basic implementations of Fast Ethernet (100Base-FX,
-T, and -T4) are identical except for the interface circuitry.
10Base-T
Ethernet LAN transmitting data over twisted pair wiring at 10 Mbps baseband.
1U
One unit rack height = 1.75 inches or 44.4 mm.
A
AC_CONV-20B
AC power-supply module for the BG-20B
ACO
Alarm Cut Off
ADM
Add/Drop Multiplexer
System adding and dropping lower level signals to and from a higher level carrier
signal.
AIS
Alarm Indication Signal
ANSI
American National Standards Institute
ARP
Address Resolution Protocol
AWG
Array Waveguide Grating
Device used for wavelength demultiplexing in WDM applications.
B
BBE
Background Block Error
426006-2413-013-A00 ECI Telecom Ltd. Proprietary G-1

Glossary LCT-BGF User Manual
BER
Bit Error Ratio
Number of bit errors detected in a unit of time, usually 1 second.
Boot Configuration Tool

Initial configuration tool for BG-40 NEs
C
CAPEX
Capital Expenditure
CBS
Committed Burst Size
CE RS
Customer's edge RS
CECC
CENELEC Electronic Components Committee
CIR
Committed Information Rate
CIST
Common and Internal Spanning Tree
CMS
Central Monitoring Station
CORBA
Common Object Request Broker Architecture
CoS
Class of Service
CWDM
Coarse Wavelength Division Multiplexing
Form of optical wavelength division multiplexing (see WDM) with wider spacings
between channels leading to considerable savings in laser transponder costs, power
requirements, and footprints. Latest standards specify a channel separation of 20 nm
(2500 GHz), as compared with the 0.8 nm (100 GHz) separation in DWDM.
D
DB
Daughter Board
or
Database
G-2 ECI Telecom Ltd. Proprietary 426006-2413-013-A00

LCT-BGF User Manual Glossary
DBMS
Database Management System
DCC
Digital Communications Channel
or
Digital Control Channel
or
Data Communications Channel
Data channels in SDH/SONET overhead used for internode communications and
OAM&P communications between intelligent controllers and individual network
nodes.
DDF
Digital Distribution Frame
DeMux
Demultiplex, Demultiplexer
DIN
German Institute for Standardization
DMM
Digital Multimeter
DS
Digital Signal (bit stream)
or
Defect Second
DS-0
Digital Signal level 0
North American digital telephony signal format for transmission at 64 kbps.
DS-1
Digital Signal level 1 (= T1)
North American primary digital telephony signal format for transmission at 1.544
Mbps; carries 24 DS-0 signals.
DS-3
Digital Signal level 3
North American digital hierarchy signal format for transmission at 44.736 Mbps;
carries 28 DS-1 signals.

Dslot
Daughter Board Slot
DWDM
Dense Wavelength Division Multiplexing
Transmission of multiple optical signals over closely spaced wavelengths, usually in
the 1550 nm region, on a single strand of fiber. See also WDM.
DXC
Digital Cross Connect
DXS
Digital Cross-Connect Switch
E
E0
ITU-1 Standard Digital Signal level 0 (64 Kbps).
E1
European PDH digital signal level 1 (2.048 Mbps).
E3
European PDH digital signal level 3 (34.368 Mbps).
ECC
Embedded Control Channel
or
Embedded Communications Channel
or
Error Correcting Code
EM
Ear and Mouth
EMC
Electromagnetic Compatibility
EMF
Equipment Management Function
EML
Element Management Layer
Situated between the NEL and NML; controls many individual NEs.
or
Transmitter source type interface for STM-64/OC-192 I/O modules.

EML
Element Management Layer
Situated between the NEL and NML; controls many individual NEs.
or
Transmitter source type interface for STM-64/OC-192 I/O modules.
EMS
Element Management System
EMS-BGF
BG-40 and BG-20 Element Management System
eNM
ECI Telecom's Network Manager
EOC
End Of Chain
or
Embedded Overhead Channel
EoS
Ethernet over SDH/SONET
EPA
ESD Protected Area
or
US Environmental Protection Agency
EPL
Ethernet Private Line
ES
Errored Second
or
Electrical Section
ESD
Electrostatic Discharge
ESDS
Electrostatic Discharge Sensitive
ESW_2G_8F
Ethernet-over-SDH processing and Ethernet L2 switching card with 8 x 10/100BaseT
LAN interfaces , 2 x GBE LAN interfaces, and 16 Ethernet-over-SDH interfaces

Ethernet
Most widely used LAN transmission protocol, open, simple, and decentralized, for
connecting computers, printers, workstations, terminals, and so on, within the same
building/campus. Operates over twisted wire and coaxial cable at speeds beginning at
10 Mbps. Uses CSMA/CD techniques. See 10BaseT.
ETSI
European Telecommunications Standards Institute
EVPLAN
Ethernet Virtual Private Local Area Network
F
Fast Ethernet
100BaseT, Ethernet at 100 Mbps.
FC
Fiber Channel
FCU
Fan Control Unit
FDB
Filtering Database
or
Forwarding Database
FE
Fast Ethernet (see 100BaseT)
or
Far End
FE_L12
Ethernet-over-SDH processing and Ethernet L2 switching card with 8 x 10/100BaseT
L1 interfaces and 8 x 10/100BaseT L2 switching interfaces
FID
Filtering Identifier
FIFO
First In, First Out
FST
Fiber Storage Tray
FXO
Foreign eXchange Office

FXS
Foreign eXchange Station
G
GbE
Gigabit Ethernet
Ethernet running at one thousand million bits per second (1 Gbps) available as shared
or switched.
GCT
GUI Cut-through
GFP
Generic Framing Procedure
GNE
Gateway Network Element
GPRS
General Packet Radio Service
First implementation of packet switching within GSM.
GUI
Graphical User Interface
GVRP
Garp VLAN Registration Protocol
GW
Gateway
H
Half duplex
Two-way transmission where data can only travel in one direction at a time.
I
I/O
Input/Output
ICP
Interconnection panel
IEC
International Electrotechnical Commission
or
Incoming Error Count

IEC 825
International Electrotechnical Commission Laser Products Safety Standard
IEEE
Institute of Electrical and Electronics Engineers, Inc.
IETF
Internet Engineering Task Force
Committee concerned with short and medium term standards regarding the Internet.
IM
Installation Manual
INF_20B
Input Filter Module for BG-20B
IP
Internet Protocol
Network layer protocol in the TCP/IP stack originally defined in RFC 791, offering a
connectionless interhost service.
ITU-T
International Telecommunications Union Telecommunication
L
LACP
Link Aggregation Control Protocol
LAG
Link Aggregation Group
Lambda
WDM system channel assigned to a specific wavelength; sometimes used
interchangeably with wavelength.
LAN
Local Area Network
Communications network consisting of servers, workstations, network operating
system, and communications link serving users within a confined geographical area.
Widely used LAN technologies include Ethernet, FDDI, and Token Ring.
LAPS
Link Access Procedure for SDH
LCAS
Link Capacity Adjustment Scheme
Equivalent to IMA in ATM.

LCT
Local Craft Terminal
LCT-BGF
PC-based BG-40/BG-20 installation, maintenance, commissioning, and configuration
tool for field technicians
LightSoft
ECI Telecom's Network Management System.
Loopback
Diagnostic test returning the transmitted signal to the transmitting device after it has
passed through a network or across a particular link. The returned signal can then be
compared to the transmitted one. The discrepancy between the two helps trace the fault.
LOS
Loss Of Signal
Condition at the receiver/maintenance signal transmitted in the physical layer overhead,
indicating the receiving equipment has lost the signal.
M
M345_3
3 x E3/DS-3 Dslot module
MAC
Media Access Control
Sublayer of data link layer responsible for accessing a LAN.
or
Message Authentication Code
ME1_21
Electrical traffic daughter boards with 21 x E1 (2 Mbps) electrical interfaces
ME1_42
Electrical traffic daughter boards with 42 x E1 (2 Mbps) electrical interfaces
MET_L1
Ethernet L1 processing module with four 10/100BaseT interfaces
MIB
Management Information Base
Formal description of a set of network objects that can be managed by using SNMP.

MS
Main Slot
or
Manual Switch
or
Multiplex/Multiplexer Section - trail between and including two multiplex section trail
termination functions
MSP
Multiplex/Multiplexer Section Protection
MSPP
MultiService Provisioning Platform
MSTI
Multiple Spanning Tree Instance
MSTP
Multi Spanning Tree Protocol
MTTR
Mean Time To Repair
Mux
Multiplexer
Device merging several low-speed transmissions into one high-speed transmission, and
vice versa.
MXC20
Cross-connect Timing and Control Card for BG-20
MXC4X
Cross-connect, Timing, and Control Card
N
NE
Network Element
or
Near End
NEBS
Network Equipment Building System
NM
Network Management

NML
Network Management Layer
Highest management layer, over NEL and EML. Controls all main network
management functions (M.3010).
NMS
Network Management System
Between TMN and EMS in the management hierarchy.
NVM
Nonvolatile Memory
O
OADM
Optical Add/Drop Multiplexer
Receives simultaneous signals at different wavelengths sent down an optical fiber,
drops one, and adds a new signal at the same wavelength.
ODF
Optical Distribution Frame
OMD1
SDH daughter board with two STM-1 (155 Mbps) interfaces (either optical or
electrical)
OMS4
Optical SDH daughter board with one STM-4o (622 Mbps) interface (a pair of LC
optical connectors)
OPEX
Operational Expenditure
OPM
Optical Power Meter
or
Optical Performance Monitor
Orderwire
Dedicated voice channel for maintenance supported by overhead bytes E1/E2.
OW
Orderwire
P
P RS
Provider's core RS

P345_3
Electrical traffic card with 3 x E3/DS-3 (34 Mbps/45 Mbps) electrical interfaces
PCM
Pulse Code Modulation
PDH
Plesiochronous Digital Hierarchy
PE RS
Provider's edge RS
PE1
Electrical traffic cards with 16/32 x E1 (2 Mbps) electrical interfaces
PPI
PDH Physical Interface
PRBS
Pseudo Random Binary Sequence
PS
Path Selector
Selects the path of signals arriving from primary and secondary nodes in two-node
interworking rings. One applies to MS-SPRing and the other to SNPC (G.842).
Q
QoS
Quality of Service
Ability to define a level of performance in a communications system.
R
RAP
Rack Alarm Panel
RDI
Remote Defect Indication
Formerly FERF.
RDR
Remote Data Replicator
RFI
Remote Failure Indication
or
Radiofrequency Interference

Ring
Collection of nodes forming a closed loop whereby each node is connected to two
adjacent nodes via a duplex communications facility.
Ring topology
Layout scheme in which the network forms a closed loop with the devices attached into
the ring.
RS
Regenerator Section
RSTP
Rapid Spanning Tree Protocol
Rx
Receive, Receiver, Reception
S
SC
Subscriber Connection
SCSI
Small Computer System Interface
SDH
Synchronous Digital Hierarchy
Hierarchical set of digital transport structures standardized for the transport of suitably
adapted payloads over physical transmission networks.
SES
Severely Errored Second
SFP
Small Form Factor Pluggable
SLA
Service Level Agreement
SM10
Intelligent PCM card with high flexibility composed of a base card supporting eight E1
interfaces and the main 1/0 cross connect, three common slots for interface modules,
and one special slot for an Ethernet-over-PDH interface module
SNCP
Subnetwork Connection Protection
SOH
Section Overhead

SQL
Structured Query Language
ST
Spanning Tree
STA
STP Algorithm
STM
Synchronous Transfer Mode
or
Synchronous Transport Module
Structure in SDH transmission hierarchy. STM-1 is the SDH base level transmission
rate, 155.52 Mbps. Higher rates include STM-4, STM-16, STM-64, and STM-256.
STM-1
Synchronous Transport Module 1, 155.52 Mbps
STM-16
STM-256
STM-4
STM-64
STP
Spanning Tree Protocol
T
TCP/IP
Transmission Control Protocol/Internet Protocol
Common name for the suite of protocols developed by the US Department of Defense
in the 1970s to support the construction of worldwide internetworks. TCP and IP are
two of the best-known protocols in the suite. TCP corresponds to Layer 4 (transport) of
the OSI reference model and provides reliable transmission of data. IP corresponds to
Layer 3 (network) of the OSI reference model and provides connectionless datagram
service.

TM
Terminal Multiplexer
or
Transverse Magnetic
or
Transmission Matrix
TMN
Telecommunications Management Network
Management network interfacing with a telecommunications network at several points
in order to receive information and control its operation.
TRP
Transponder
TTL
Transistor-Transistor Logic
or
Time To Live
Number of NEs DCC packets can pass through before being terminated.
Twisted pair
Two insulated copper wires twisted together, with twists/lays of varying length to
reduce potential signal interference between the pairs. The most common medium for
electrically connecting phones, computers, and terminals.
Tx
Transmission/Transmitter/Transmit
U
Unidirectional
Operating in one direction only.
V
VC
Virtual Container
SDH defines a number of containers, each corresponding to an existing plesiochronous
rate. Information from a plesiochronous signal is mapped into the relevant container
along with control information known as the path overhead.
VC-12
Virtual Container 12, 2.048 Mbps (used on low-order path)
VC-3
Virtual Container 3 (used on low-order path)

VC-4
Virtual Container 4 (used on high-order path)
VCG
VC Group
VDF
Voice-frequency Distribution Frame
Virtual Machine
Used to support Cross-EMS functionality for LightSoft clients
VLAN
Virtual Local Area Network
VPN
Virtual Private Network
W
WAN
Wide Area Network
Physical or logical network enabling independent devices to communicate with each
other over a common transmission interconnected topology in geographic areas larger
than those served by local area networks.
X
XC
Cross Connect
xDDF-21
21 E1s DDF with balanced-to-unbalanced conversion

Index
A B
Activating Bandwidth Profile 6-60
Client Trail XCs 7-14 BG-20
Server Trail XCs 7-5 Special Cards 6-6
Activation Time 12-13 BG-40
Aging Time 6-46, 6-81 Proxy ARP 13-3
Alarm Attributes 9-16, 14-53 Proxy ARP List 13-3
Alarm Hold-off Setting 9-19 Serial Port Configuration 13-6
Alarm Log Settings 9-18 Boot Configuration Tool
Alarm Preset Switch 9-17 Configuring Parameters 3-4
Alarm Log 9-13, 9-18 Configuring the No Recovery Next
Alarm Severity 14-56 Startup Attribute 3-9
Alarms Configuring the Serial Port Close
Flag 3-10
Alarm Log 9-18
Obtaining IDPROM Data 3-8
Configuring Attributes 9-16, 14-53
Procedures 3-2
External Alarms 9-20
Bridge
Hold-off Setting 9-19
Port Priority Settings 6-54
Managing Current Alarms 9-2,
14-49 Port STP Settings 6-52, 6-87, 6-88
Managing Historical Alarms 9-8, C
14-52
Calibrating 8-6
Manually Synchronizing 9-20,
14-57 Cards
Masking 9-11, 14-54 Assigning 5-4
Overview 9-1 Configuring 6-20
SM10 14-47, 14-48, 14-58 Managing BG-20 Special Cards 6-6
Analzying Setting Maximum Traffic 5-6
Performance 10-4 Viewing Card Information 6-5
Assigning Viewing the Electronic Label 6-4,
14-60
Cards 5-4, 14-26
Clearing
PCM Card 14-4
Flash 13-7
NE Configuration 12-9
426006-2413-013-A00 ECI Telecom Ltd. Proprietary I-1

Index LCT-BGF User Manual
Client Trails Port Lock 6-48, 6-83

Activating XCs 7-14 Port STP Settings 6-88
Configuring XCs 7-10 Server Trail XCs 7-1, 14-35
Creating XCs Manually 7-10 SNCP 7-20
Deactivating 7-15 SNMP Agent Mode 13-9
Deleting 7-16 Static IP Routes 4-6
Filtering XCs 7-17 Static vFIB Table 6-47
Maintaining Cross Connections 7-1, STP 6-48
7-13 STP Algorithm 6-49
Communication Parameters Synchronous Timing 8-2
Configuring 5-13 Synchronous Timing Table 8-3
Configuring Timing 8-2, 14-28
Aging Time 6-46, 6-81 Trap Manager Table 13-7
Alarm Attributes 9-16, 14-53 V.35 Workmode 5-18
Bandwidth Profile 6-60 VC-12-to-SM10 Link 5-17
Basic Parameters 3-4 vFIB 6-46, 6-81
BG-40 Proxy ARP List 13-3 VLAN Attributes 6-40
BG-40 Serial Port 13-6 Connectivity Test 14-64
Bridge STP Settings 6-87 Correcting
Cards 6-1 Alarms 9-20, 14-57
Client Trail XCs 7-10, 14-37 Creating
Communication Parameters 5-13 Client Trail XCs Manually 7-10,
DCC Access 5-16 14-35
DCC and Overhead 5-15, 5-21 Server Trail XCs Manually 7-1
DCC Cross 5-20 SM_10E XCs 14-41
DCC Swap Attribute 5-19 SM10 XCs 14-35
ESW_2G_8F Attributes 6-20 Cross Connections
Ethernet 6-36 Activating Client Trail XCs 7-14
LCT Master Work Mode 11-2 Activating for Server Trails 7-5
LCT Monitor Work Mode 11-2 Configuring Client Trail XCs 7-10,
LCT Work Mode 11-2 14-35
Link Aggregation 6-90 Configuring for Server Trails 7-1
MSTP 6-85 Creating Client Trail XCs Manually
7-10, 14-35
NEs 5-1
Creating Server Trail XCs Manually
Orderwire 5-9 7-1
Parameters 3-4, 4-4 Deactivating Client Trail XCs 7-15
Port Attributes 6-38 Deactivating on Server Trails 7-7
I-2 ECI Telecom Ltd. Proprietary 426006-2413-013-A00

LCT-BGF User Manual Index
Deleting 7-8, 7-16 Ethernet Layer 2 Management 6-60,

Filtering Client Trail XCs 7-17 6-96
Filtering Server Trail XCs 7-9 Hardware 6-21
Maintaining Client Trail XCs 7-10 Link Aggregation 6-90
Maintaining Server Trail XCs 7-1 Network Architecture 6-21
Overview 7-1 Policer 6-61
Uploading 7-25, 14-38 Port Lock 6-83
Current Performance 10-5 Port STP Settings 6-88
vFIB 6-81, 6-83
D
VPN List 6-74
DCC 5-15, 5-16, 5-19, 5-20, 5-21, 13-5 Ethernet
Access 5-16 Configuring 6-36
DCC Cross 5-20 ESW_2G_8F Ethernet Layer 2 6-60,
DCC Overhead 5-15, 5-21 6-96
DCC Swap Attribute 5-19 Managing 6-10, 6-60, 6-96
DCC MIB Counters 13-5 Exporting
Deactivating Exporting Trails as a File 7-22
Client Trail XCs 7-15 External Alarms 9-20, 14-47
Server Trail XCs 7-7 F
Deleting
Fan Maintenance 12-20
Client Trails 7-16
FE_L12
Server Trails 7-8
Configuring Port Attributes 6-38
Displaying DCC MIB Counters 13-5
Configuring vFIB 6-46
Downloading
Configuring VLAN Attributes 6-40
Embedded Software 3-5
Ethernet Layer 2 Management 6-37
FPGA File 3-5
Managing 6-10
NE Configuration Data 12-9
Filtering
NE Database Files 12-10
Client Trail XCs 7-17
PCM Configuration Data 14-31
Server Trails 7-9
E Flash
Embedded Software 3-5 Clearing 13-7
Enabling BG-40 NE Proxy ARP 13-2 FPGA File 3-5
ESW_2G_8F 6-20 G
Bandwidth Profile 6-60
Getting Started 4-1
Bridge STP Settings 6-87
Configuring the Aging Time 6-81 H
Hardware Requirements 1-2

I M
IDPROM Data 3-8 Maintaining
Importing Client Trail XCs 7-13
Importing Trails from a File 7-24 Server Trail XCs 7-4
Installation Overview 2-1, 3-1 Maintenance
Installing AIS/PRBS/RDI Operations 12-5
LCT-BGF 2-1, 2-2 Clearing NE Configuration 12-9
L Connectivity Test 14-64
Fan 12-20
LACP 6-93, 6-95
Laser 12-19
Laser Maintenance 12-19
Loopbacks 12-2, 14-62
LCT-BGF
Maintenance List 12-1
Boot Configuration Tool 3-1
Other 12-17
Configuring Parameters 3-4, 4-4
Power 12-21
Getting Started Overview 4-1
Remotely Logging in to NE 12-17
Hardware and Software Requirements
1-2 Saving NE Configuration Data 12-9
Installation Overview 2-1 Software Upgrades and Maintenance
12-11, 14-66
Installing 2-1, 2-2
Viewing the Run Time 14-59
Logging In 3-2, 12-17
Managing
Master Mode 11-1, 11-2
BG-20 Special Cards 6-6
Monitor Mode 11-1, 11-2
Current Alarms 9-1, 14-47
Overview 1-1
Ethernet 6-10, 6-37, 6-56, 6-96
Starting the GUI 4-2
External Alarms 9-20
System Components 1-2
FE_L12 Attributes 6-10
Work Mode 11-1, 11-2
FE_L12 Ethernet Layer 2 Attributes
Licenses 6-37
Control Mechanism 15-2 Historical Alarms 9-8, 14-47, 14-52
Control Workflow 15-3 SAM1/4 Interface 6-8
Format 15-4 SM_10E XCs 14-41, 14-44
Managing 15-1, 15-6 SM10 XCs 14-35, 14-37
Overview 15-1 VPN Services 6-67
Link Aggregation 6-90, 6-93, 6-95 Masking Alarms 9-11, 14-54
Logging In Master Mode 11-1, 11-2
Remotely to NE 12-17 Monitor Mode 11-1, 11-2
To LCT GUI 3-2
Loopbacks 12-2, 14-62

MSTP 6-48, 6-85 Timing 14-28

Algorithm 6-49 XCs 14-35
Bridge Settings 6-50, 6-87 Performance
Bridge STP Settings 6-52 Analzying 10-4
Configuring 6-48 Operations 10-5
Filtering Identifier 6-85 Overview 10-1
Port Priority Settings 6-54 Performance Monitoring Switch
Port Settings 6-38, 6-52, 6-88 10-1, 10-10
Port STP Settings 6-88 Resetting Performance Counters
10-13
RSTP/MSTP Interworking and
Interregional Interworking 6-85 Setting Performance Thresholds
10-8
N Viewing Current 10-5
NEs Viewing Recent 10-7
Clearing the Configuration 12-9 Performance Monitoring Switch 10-10
Configuring 5-1 Performing
Downloading Database Files 12-10 Advanced Configuration 13-1
Remotely Logging In 12-17 AIS/PRBS/RDI Operations 12-5
Resetting 5-8, 14-65 Card Assignment 5-4, 14-26
Saving Configuration Data 12-9 Connectivity Test 14-64
Uploading/Downloading Loopbacks 12-2, 14-62
Configuration Data 14-31 NE Maintenance 12-1, 12-17, 14-59
No Recovery Next Startup Attribute 3-9 Software Upgrade 12-11, 14-66
O System Maintenance 12-17, 14-59
Policer 6-61
Orderwire
Port Lock 6-48, 6-83
Configuring 5-9
Power 12-21
P
Proxy ARP 13-2
Parameters Proxy ARP List 13-3
Configuring 3-4, 4-4, 5-13
R
PCM
Recent Performance 10-7
Alarms 14-47
Resetting
Clock Mode 14-30
NEs 5-8, 14-65
Configuration Data 14-31
Performance Counters 10-13
Maintenance 14-59
RSTP 6-85
Slot Assignment 14-26
Run Time 14-59
SM_10E Card 14-2
SM10 Card 14-2

S T
SAM1/4 Interface 6-8 Timing
Saving Calibrating the Clock Card Frequency
NE Configuration Data 12-9, 14-31 8-6
Security 11-1 Configuring 8-1, 14-28
Serial Port Close Flag 3-10 Configuring Synchronous Timing
8-2, 8-3
Server Trails
Overview 8-1
Configuring 7-1
Viewing the Clock Work Mode 8-5,
Creating Manually 7-1 14-30
Deactivating 7-7 Trace MAC Address 6-84
Deleting 7-8 Trails
Filtering 7-9 Deleting 7-8, 7-16
Maintaining Cross Connections 7-4 Exporting as a File 7-22
Setting Filtering 7-9, 7-17
Alarm Preset Switch 9-17 Importing from a File 7-24
Card Maximum Traffic 5-6 Trap Manager Table 13-7
NE Attributes 5-3
U
NE Time 5-2
Performance Thresholds 10-8 Uploading
SM_10E Card Attributes 14-17, SM10 Configuration Data 14-31
14-22, 14-25 XCs 7-25, 14-31, 14-38, 14-45
SM10 Card Attributes 14-7, 14-14
V
SM_10E Card 14-2
V.35 5-18
SM10 Card 14-1, 14-2, 14-4, 14-59
vFIB
SNCP 7-20
Configuring 6-46, 6-81
SNMP 13-9
Configuring Aging Time 6-46
Software Requirements 1-2
Configuring Static vFIB Table 6-47
Software Upgrade 12-11, 14-66
Configuring the Port Lock 6-48,
Starting
6-88
LCT GUI 4-2
Flushing 6-47, 6-83
Static IP Routes 4-6
Viewing
Static vFIB Table 6-47
Alarm Severity 14-56
System Components 1-2
Card Information 6-5, 14-7
System Maintenance 14-59
Clock Mode 8-5, 14-30

Current Performance 10-5

Electronic Card Label 6-4, 14-60
Recent Performance 10-7
VLAN 6-40
VPN 6-67
VPN List 6-74
X
XCs
Client Trail 7-10, 7-13, 7-14, 7-15,
7-16, 7-17, 14-35, 14-37
Server Trail 7-1, 7-4, 7-5, 7-7, 7-8,
7-9, 14-35
Uploading 7-25, 14-31, 14-38


BG 20 Eci Mux PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BG 20 Eci Mux PDF

Uploaded by

Copyright:

Available Formats

BroadGate LCT-BGF

Copyright by ECI Telecom, 2005-2007. All rights reserved worldwide.

Introducing the LCT ................................................................ 1-1

Installing the LCT .................................................................... 2-1

Using the Boot Configuration Tool ........................................ 3-1

Getting Started with the LCT GUI........................................... 4-1

Managing NEs.......................................................................... 5-1

Managing Cards....................................................................... 6-1

426006-2413-013-A00 ECI Telecom Ltd. Proprietary i

Viewing Card Information ................................................................................. 6-5

Managing Cross Connections ................................................ 7-1

Configuring Timing Sources .................................................. 8-1

Managing Alarms..................................................................... 9-1

Monitoring Performance ....................................................... 10-1

Managing LCT-BGF Security................................................ 11-1

ii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

Performing Maintenance Operations................................... 12-1

Performing Advanced Configuration................................... 13-1

Configuring the PCM Card.................................................... 14-1

Managing Licenses ............................................................... 15-1

Glossary of Terms .................................................................. G-1

Index .......................................................................................... I-1

426006-2413-013-A00 ECI Telecom Ltd. Proprietary iii

iv ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary v

Figure 5-15: DCC Configuration and DCC Overhead Management window -

vi ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary vii

Figure 6-81: Trunk Mode window ................................................................................ 6-94

viii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

Figure 9-12: External Alarm window ............................................................................ 9-21

426006-2413-013-A00 ECI Telecom Ltd. Proprietary ix

x ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary xi

xii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary xiii

xiv ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary xv

| Chapter 5, Managing NEs - describes how to configure NEs, Orderwire

xvi ECI Telecom Ltd. Proprietary 426006-2413-013-A00

Convention Indicates Example

NOTE: Text set off in this manner presents clarifying

CAUTION: Text set off in this manner indicates that failure

WARNING: Text set off in this manner indicates that failure

426006-2413-013-A00 ECI Telecom Ltd. Proprietary xvii

xviii ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary 1-1

Hardware and Software

1-2 ECI Telecom Ltd. Proprietary 426006-2413-013-A00

426006-2413-013-A00 ECI Telecom Ltd. Proprietary 2-1

Installing the LCT-BGF

To install the LCT-BGF:

Figure 2-1: LCT-BGF Installation CD window

2-2 ECI Telecom Ltd. Proprietary 426006-2413-013-A00

3. Select Install LCT-BGF. The LCT Setup - Welcome window opens.

Figure 2-2: LCT-BGF Setup - LCT Welcome window

Figure 2-3: LCT-BGF Setup - Setup Status window

426006-2413-013-A00 ECI Telecom Ltd. Proprietary 2-3

Figure 2-4: LCT-BGF Setup - LCT System Config window

Figure 2-5: LCT-BGF Setup - Installation Complete window

7. Click Finish. The LCT-BGF installation process is complete.

NOTE: Installation of the LCT-BGF can be done without the

2-4 ECI Telecom Ltd. Proprietary 426006-2413-013-A00